ughtechnology
Lurker
Hi Guys,
Will to live lost here! I've spent upwards of 12 hours over 3 days trying to work through things without resorting to asking for help...but I'm done.
I couldn't afford a new phone so I'm still on my Nexus 4 and the OS it came with, bought from the google store.
I'm not a fan of updates as in my experience they tend to break things. And so that is how I've gone 5+ years without updating the OS, ignoring the OTA notification from the menu all this time.
Suddenly the lock screen starting behaving a little weird. I managed to get in but then out of nowhere the phone rebooted and was suddenly updating to I imagine 4.3.
It never made it, just looping the progress bar for hours on end. Cue the start of research. I found my way to this thread (forums.androidcentral.com/google-nexus-4/300300-nexus-4-stuck-after-4-3-update-fail-even-after-hard-reset.html) amongst many others and began attempting the following.
I tried the bootloader > recovery > cache clear but no difference.
I didn't want to resort to factory reset as I need my apps & would like to rescue the messages.
The particular advice I read was to download Unified Nexus Toolkit, TWRP, Android Studio for SDK & USB drivers, 4.3 image from google (or 4.2.2 or any more up to date and supported one, whichever I wish). I thought 4.3 would be a good start.
UNT though alerted Avira to a particular Trojan, so I left that considering that part was supposedly only for backing up data. And apparently I could carry on to flashing just bootloader/radio/boot/recovery/system img files without losing data.
Now to my brickwall. The advice said to extract both the TWRP & 4.3 mako file to the SDK platform-tools folder, which I did. However it said the TWRP file was supposed to be a IMG file to flash (via ADB or fastboot?), but it was an APK file.
Simply then this is where I'm at. Despite downloading USB Drivers from within the SDK Manager I cannot get the Powershell to respond to "adb devices", or "fastboot devices" queries. So I cannot get to even trying to flash 4.3 images despite the bricked Nexus 4 showing up in my device manager as "Android Composite ADB Interface".
There were some other pieces of advice, but after reading so many things most of which only partially relate to my problem, and after having to borrow another laptop to try this stuff on as mine doesn't even load .exe files amongst other problems....overall I'm just deaded out and need a helping hand if possible.
So thank you for reading this lump of info about an old device. And if you can offer any help it would be much much appreciated.
Will to live lost here! I've spent upwards of 12 hours over 3 days trying to work through things without resorting to asking for help...but I'm done.
I couldn't afford a new phone so I'm still on my Nexus 4 and the OS it came with, bought from the google store.
I'm not a fan of updates as in my experience they tend to break things. And so that is how I've gone 5+ years without updating the OS, ignoring the OTA notification from the menu all this time.
Suddenly the lock screen starting behaving a little weird. I managed to get in but then out of nowhere the phone rebooted and was suddenly updating to I imagine 4.3.
It never made it, just looping the progress bar for hours on end. Cue the start of research. I found my way to this thread (forums.androidcentral.com/google-nexus-4/300300-nexus-4-stuck-after-4-3-update-fail-even-after-hard-reset.html) amongst many others and began attempting the following.
I tried the bootloader > recovery > cache clear but no difference.
I didn't want to resort to factory reset as I need my apps & would like to rescue the messages.
The particular advice I read was to download Unified Nexus Toolkit, TWRP, Android Studio for SDK & USB drivers, 4.3 image from google (or 4.2.2 or any more up to date and supported one, whichever I wish). I thought 4.3 would be a good start.
UNT though alerted Avira to a particular Trojan, so I left that considering that part was supposedly only for backing up data. And apparently I could carry on to flashing just bootloader/radio/boot/recovery/system img files without losing data.
Now to my brickwall. The advice said to extract both the TWRP & 4.3 mako file to the SDK platform-tools folder, which I did. However it said the TWRP file was supposed to be a IMG file to flash (via ADB or fastboot?), but it was an APK file.
Simply then this is where I'm at. Despite downloading USB Drivers from within the SDK Manager I cannot get the Powershell to respond to "adb devices", or "fastboot devices" queries. So I cannot get to even trying to flash 4.3 images despite the bricked Nexus 4 showing up in my device manager as "Android Composite ADB Interface".
There were some other pieces of advice, but after reading so many things most of which only partially relate to my problem, and after having to borrow another laptop to try this stuff on as mine doesn't even load .exe files amongst other problems....overall I'm just deaded out and need a helping hand if possible.
So thank you for reading this lump of info about an old device. And if you can offer any help it would be much much appreciated.
