Struggling to Update - Help Needed - Nexus 7 Q&A, Help & Troubleshooting

So my son's 2012 Nexus 7 (32 GB Wi-Fi) is struggling to update. I was checking to see if he got the 5.0 update and noticed he's still on 4.4.2. When I tried to update to 4.4.3 it won't reboot and install the update.
I then tried to sideload the update and it failed due to some certificate issue. Maybe because it's unlocked? I then rooted it again (lost it after the last update apparently) and also installed TWRP. I was going to attempt to sideload from within TWRP but adb doesn't see the device in sideload mode for me for some reason.
Bottom line... Can I just flash the OTA zip file like any other file within TWRP? If not, does anyone have any over ideas of what I can do to update this this without wiping it clean?

I think you will have to flash the 5.0 and images using fastboot. Can you get into ap fastboot mode?

before that though, and to answer your questions:
- unlocked bootloader does not cause issues
- I've used twrp to flash all of the KitKat ota updates directly. simply put the update zip in the internal storage of the device (I always put it in sdcard0/) and flash. the only reason that would fail with KitKat is if you have xposed installed, which was fixed by flashing xposed Disabler zip first. I don't think having root mattered.
- for the lollipop update flashing from twrp didn't work for me. I had to first return 4.4.4 to stock system and recovery (by flashing the system.img and recovery.img files from stock 4.4.4) then adb sideload 5.0 ota update. In your case tho you'd have just updated to 4.4.4 so you can just go straight to sideloading.
All the ota update links are in the second sticky in the general section. make sure you follow the correct to:from build numbers.
I'd prefer this longer route of ota updates, but if nothing works then you can probably just flash system, recovery, and boot directly from the lollipop firmware, and leave userdata untouched. I'd also Not flash the bootloader, as it's reported to have issues.

Related

Need lollipop ota

Hey what's up happy thanksgiving I'm trying to update my nexus to the latest version lollipop I'm currently on 4.4.4 I have my boot loader unlocked but I'm not rooted is there a way to rush the update to my phone without rooting
Yeah dude it's called adb sideload update and you don't need to be rooted to do it (or probably even unlocked, but you are anyway, doesn't matter).
You can get the link to the nexus 7 OTA zip from the second sticky in the general section.
Then either google "how to adb sideload update" or see what I wrote here: http://forum.xda-developers.com/nexus-7/general/lollipop-ota-update-via-adb-data-t2941175 if you didn't install a custom recovery or never rooted and messed with your system folder, you can skip the part about flashing stock 4.4.4 system and recovery.

Unable to OTA nor SIDELOAD from 5.0.1 to 5.1

Yesterday my Nexus 4 (rooted & CWM recovery) prompted to install 5.1 update. Once the phone reboots, enter to recovery and begin installation proccess, it throws an error (in short, build expects fingerprint of 5.0.1 but gets 4.3 fingerprint instead) and abort. Already tried all below:
unroot, stock recovery and OTA > Fail
Stock recovery sideload > Fail
TWRP recovery sideload > Fail
CWM recovery sideload > Fail
I am stuck here. I allways can flash the stock rom, but I really want to avoid it if possible, i dont want to (one more time) spend hours restoring all my config, apps, data, layouts....Any hint, my wise fellows?
Thanks a lot
Pocket_rocket said:
Yesterday my Nexus 4 (rooted & CWM recovery) prompted to install 5.1 update. Once the phone reboots, enter to recovery and begin installation proccess, it throws an error (in short, build expects fingerprint of 5.0.1 but gets 4.3 fingerprint instead) and abort. Already tried all below:
unroot, stock recovery and OTA > Fail
Stock recovery sideload > Fail
TWRP recovery sideload > Fail
CWM recovery sideload > Fail
I am stuck here. I allways can flash the stock rom, but I really want to avoid it if possible, i dont want to (one more time) spend hours restoring all my config, apps, data, layouts....Any hint, my wise fellows?
Thanks a lot
Click to expand...
Click to collapse
I followed the steps in this guide https://gist.github.com/eyecatchup/ec0a852428c19705380e for updating to 5.1.
I obiously replaced the relevant files with the ones for Nexus 4. I downloaded the 5.0.1 factory image and flashed recovery, boot and system, then installed the OTA and then flashed new recovery and supersu.
ollegut said:
I followed the steps in this guide for updating to 5.1.
I obiously replaced the relevant files with the ones for Nexus 4. I downloaded the 5.0.1 factory image and flashed recovery, boot and system, then installed the OTA and then flashed new recovery and supersu.
Click to expand...
Click to collapse
When you say "installed the OTA" I assume, by itself, not sideloading, isn't it?
Thanks
Pocket_rocket said:
When you say "installed the OTA" I assume, by itself, not sideloading, isn't it?
Thanks
Click to expand...
Click to collapse
Sorry for the laterespone. Yes, like in the guide I used 'adb sideload ...'.
Have you tried flashing it with the stock 5.0.1 images directly, and then going back and flashing with the 5.1 images (or OTA?) If you have rooted, simply factory resetting will not work due to the way 5.+ authentication checks. A single modified byte, and the OTA Sideload will fail (I have been through the same issue as you have, and flashing the 5.0.1 images in Wug's NRT, booting, and then installing the 5.1 OTA (this was before the images were out yet and I was impatient), did the trick for me.

Unable to install OA 6.0.1

hi,
I have a rooted moto x play (indian version)
I downloaded the OTA update, which reboots to recovery and fails. I use twrp as recovery.
And then it keeps failing. I want to install OTA update but don't want to reset my mobile.
Screenshot. ( boot loader is unlocked)
Maybe do a search prior to posting about installing an ota when rooted and running a custom recovery. There's more than a few threads regarding this specific situation.
All you're really doing is cluttering the MXP threads with non needed threads.
I'm not even going to help you out because I hate spoon feeding people who can't even or are to lazy to do either a search on XDA or google.
I did try searching for. no help
can anyone help?
Rooting means you're modifying the system. The system will not be like before. You may be able to download the update but that won't get installed. The modification of system files won't allow you to patch them with the OTA update. So the only way is to flash the firmware manually
since Lollipop, Google doesn't let the OTA install on top of a modified system. (any modification at all). If you were rooted, and you unroot, the system is still considered "modified".
you want to install an official update from your manufacturer, the recommended process is to first return your device to completely stock including replacing TWRP with a copy of the stock recovery.
If you have nandroid backup before install SuperSU, first flash that and flash stock recovery and boot into stock and get ota and flash then you can re root and flash recovery again.

updating rooted phone

Hi all,
I am using XT1643 indian version. I have successfully rooted it using TWRP recovery. However, I haven't changed the rom. Today, it is showing OTA update of security fixes. Should I update it or is there any particular method for updating or should I ignore the update.
Thanks.
ankit.hinsu said:
Hi all,
I am using XT1643 indian version. I have successfully rooted it using TWRP recovery. However, I haven't changed the rom. Today, it is showing OTA update of security fixes. Should I update it or is there any particular method for updating or should I ignore the update.
Thanks.
Click to expand...
Click to collapse
flash stock recovery and then update
FlashFire
or Just use Flashfire A handy Application for updating rooted phone. but remember one thing always keep backup and stock rom file to your pc if something goes wrong you can easily re flash your stock rom.
Both options doesn't work.
With FlashFire, it is impossible to find the update file, and with stock recovery, its gives an error when updating
If FlashFire doesn't work, you should first unroot your device, uninstall xposed if you already installed it, also remember to use stock kernal after that.. flash stock recovery than update via ota. Let us update what happen
Edit :- I tried my self
1. unistalled xposed
2. un rooted
3. wiped all data, dalvik cache, and other stuf..exclude system
4. rebooted
5. flashed stock recovery
6. reboot again
7. download ota
8. device reboot again in stock recovery
9. And failed to update
10. So we cant update our phone unless new updated stock images available...

Strange OTA behaviour after installing Magisk

After a long time I finally decided to upgrade to PIE (stock).
The latest official Fastboot ROM I could find is from May (V10.0.9.0) - so this is what I used to install.
Everything went fine, and as expected I was prompted for an OTA upgrade to August which I performed. The Build number become ...V10.0.12.0
Afterwards I installed Magsik (V19.3) via Boot to TWRP - also with no problem.
But surprise: I was prompted for another OTA-upgrade this time to July2019, and the Build number shows V10.0.9.0 !
Ok, I uninstalled Magisk to get this upgrade done, but the upgrade failed..
Went back to re-flash the Fastboot ROM for May and .. and ... and the story repeated.
Any idea what's going on?
I would reflash whole ROM with the latest official Fastboot ROM again (do not forget to remove bootloader lock command from the flashing script or you'll lose your data) and flash Magisk from TWRP. For the OTA update follow this guide, you don't really need to mess up with TWRP more than once https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md.
One thing to keep in mind - do NOT allow system modifications in TWRP as it will mount system partition as R/W and prevent future OTA updates to install. If you allowed it somewhere in the past (or you don't remember) - delete TWRP settings from /sdcard/TWRP and pay attention on the first boot of TWRP.

Categories

Resources