Related
Probably there is a thread about my problem, but I really need your help.I have the official 4.2.2,(I have removed some system apps like Google current etc), unlocked and rooted with custom recovery(twrp).I recently have received the notice for the ota update.I want to update to 4.3 , hopefully without losing root, but if there is no other way,I don't have problem.so I would really appreciate a step-by-step guide.thank you all in advanced and forgive my bad English
Στάλθηκε από το Nexus 7 μου χρησιμοποιώντας Tapatalk 2
steliosamos said:
Probably there is a thread about my problem, but I really need your help.I have the official 4.2.2,(I have removed some system apps like Google current etc), unlocked and rooted with custom recovery(twrp).I recently have received the notice for the ota update.I want to update to 4.3 , hopefully without losing root, but if there is no other way,I don't have problem.so I would really appreciate a step-by-step guide.thank you all in advanced and forgive my bad English
Στάλθηκε από το Nexus 7 μου χρησιμοποιώντας Tapatalk 2
Click to expand...
Click to collapse
Hi, steliosamos....
If you've removed any system apps (like Currents), then there's a good chance the OTA will fail, as it expects to find them in order to update them. It does this by running a checksum test on all files in system. If even one fails that test (either due to modification or it's absence), the OTA will abort, with no changes made.
So you need to restore any missing system apps first... but this might be tricky. It largely depends on the extent of your modifications to system... what apps you've removed, and other changes you may have made.
If they are considerable, and you can't either remember them in order to reverse them, or you can't remove those modifications for other reasons, you may be left with little alternative but to fastboot flash the full factory image for your device... available here, https://developers.google.com/android/nexus/images.
Anyway... upon successful updating via the OTA, you will likely loose TWRP... and you will certainly have to re-root again. This is because root under JellyBean 4.3 works completely differently than 4.2.2. So, you will loose root (and even if, by some unlikely miracle you didn't, it wouldn't work anyway).
Unlike under pre-4.3 versions of JellyBean, where root was just a 'static' su binary dropped into /system/xbin, root is now a 'dynamic' process, called a daemon, specifically, 'sudaemon'.
--------------------------------
You can the get UPDATE-SuperSU-v1.51.zip from here.
Fastboot flash TWRP (for 'Grouper'/WiFi or 'Tilapia'/3G, make sure you get the correct one for your device)... and then using TWRP, flash the SuperSU root package.
Good luck.
Rgrds,
Ged.
Yes,Ged,i really cant remember which system apps i have removed,so as far i understand the safer way is flashing the factory image and returning to official 4.2.2.Then i can update to 4.3 OTA and later to flash again the twrp and root it one more time.Do i understand right?The first time when i unlocked my nexus and root it,i used sdk tools.I am thinking this time to use nexus root toolkit,hoping that it will be more safe and quick.Do you agree?Thanx either way for your responce and help
steliosamos said:
Yes,Ged,i really cant remember which system apps i have removed,so as far i understand the safer way is flashing the factory image and returning to official 4.2.2.Then i can update to 4.3 OTA and later to flash again the twrp and root it one more time.Do i understand right?The first time when i unlocked my nexus and root it,i used sdk tools.I am thinking this time to use nexus root toolkit,hoping that it will be more safe and quick.Do you agree?Thanx either way for your responce and help
Click to expand...
Click to collapse
Hi, steliosamos...
Yeah... you pretty much have it right. There are two ways you could go...
1) Flash 4.3 straight off.
2) Flash 4.2.2 and then take the 4.3 OTA update.
Practically, there is no difference regarding the end result... you'll have a Nexus 7 running Jellybean 4.3.
But the second way is safer... the reason why revolves around the bootloader.
Jellybean 4.3 will update the bootloader from v4.18 to v4.23. Theoretically, there should be no difference in how this is accomplished... but updating via fastboot, flashes the bootloader directly to the bootloader partition... which is an inherently risky procedure. And if anything goes wrong (bad USB connection, some glitch with your PC, etc) you have a dead Nexus 7, generally known as a hardbrick... from which there is no known recovery.
However, updating via an OTA update, the bootloader is updated differently.
As I explained previously, an OTA will run a checksum on files in system to ensure everything is present and correct (no modifications and/or absences). The OTA then 'patches' them, meaning it updates them. The last thing the OTA does is it drops a file called BOOTLOADER.RAW into a temporary holding partition called USP/Staging. Upon automatic reboot after the OTA has completed, this new bootloader is then copied to the bootloader partition proper, presumably after running a similar checksum to compare it with the old(current) bootloader... and it inherits the crypto-signed data that the old bootloader holds and is unique to your specific device. This seems to me a safer way of upgrading the bootloader, than fastboot flashing it directly.
You mention in your post, you might use a toolkit. Well, I've never used one - so I'm unable to give advice on their use. And personally, I don't recommend them. With toolkits, you relinquish control on how a factory image is flashed. With fastboot you have complete control (you can 'pick' and 'mix' which elements you want to flash.. eg., boot.img, system.img, etc), and you also have greater transparency.
Now, coming back to your specific case...
Here's what I would do. (The following assumes you're using Windows and have a WiFi only Nexus 7).
Download the factory image for Jellybean 4.2.2 for your device from here.
Unzip it accordingly...
Edit the flash-all.bat to remove the line fastboot flash bootloader bootloader-grouper-4.18.img. There's no point in needlessly re-flashing a bootloader that you already have (with the risks that entails).
So, after editing, you should have the following in the flash-all.bat file...
Code:
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot reboot-bootloader
ping -n 10 127.0.0.1 >nul
fastboot -w update image-nakasi-jdq39.zip
echo Press any key to exit...
pause >nul
exit
You can of course, just type all of this in manually (with the exception of the ping command, which just pauses everything while the bootloader reboots).
From a fully shut down condition, boot your Nexus 7 into the bootloader (in fastboot mode), by pressing VOL DOWN and hold, whilst holding, press the POWER BUTTON. Open a command prompt window on whichever folder you have downloaded and unzipped the factory image files to.
First type....
Code:
fastboot devices
You should expect to see something like this...
Code:
015dxz2oxxxxx fastboot
Your device's unique serial ID followed by the word 'fastboot'. This is essentially diagnostic, and confirms you have a working fastboot connection. If you don't see this, you likely have a driver problem which needs to be attended to before you can proceed.
You're now ready to run the flash-all.bat file or manually type in the commands it contains.
----------------------------------------
Another possibility/option that occurs to me (although I've never tried it myself)...
You might able to get away with just fastboot flashing the system.img file (extract it from image-nakasi-jdq39.zip), and flash as follows...
Code:
fastboot erase system
fastboot flash system system.img
As I say, I've never tried this, so I've no idea if it will work... but it seems a logically easier way of restoring all your system apps with minimal hassle.
One last point about system.img... in my experience, it can (but not always) be notoriously fussy/difficult (a bloody pain in the ar#*!:' actually) when 'sending'. If this happens, just disconnect the USB lead from your PC, reconnect to another port, and reboot the bootloader and try again. It should take no more than 2 minutes to go across... any longer than 3 minutes and you've probably lost your fastboot connection. Once you see 'Writing system...', you know it's worked. You can check the integrity of your fastboot connection at any time by opening another command prompt window and typing fastboot devices. If you DON'T see a serial number, then the fastboot connection has died.
----------------------------------------
Right... all things being equal... you should now be be running stock JellyBean 4.2.2 and ready to accept the 4.3 OTA update (assuming a WiFi connection)... and which you will get pestered with every time you turn on the device.
Accept it... the update should go smoothly (although with tech, one can never be sure until after the event - (...and the new bootloader v4.23, safely ensconced in the bootloader partition).
The bootloader being still unlocked, it's now a relatively trivial matter to fastboot flash TWRP (or CWM if you prefer), and then root via Chainfire.
Good luck.
Rgrds,
Ged.
i got a question here
i hav a nexus 7 3g 32gb. was running stock rom rooted with twrp recovery and few days bak i got the 4.3 update and i chose to update and after the update it was stuck at the boot logo never switched on. i tried factory reset also but it never worked probably something went bad in the OTA update or it happened cuz i was rooted with unlocked bootloader and custom recovery i donno.. anyways i had no choice i used the N-cry toolkit for nexus ( http://forum.xda-developers.com/showthread.php?t=2171401 ) and flashed the factory image and got it bak to life and with the same toolkit i rooted it n flashed custom recovery so right now i hav a nexus 7 running android 4.3 stock rooted with custom rom n unlocked bootloader. everything was fine until i started getting a notification for 4.3 update again even though i hav 4.3 on the device. i havent done much to it other than rooting and having a custom rom so my system apps are intact so updating with the OTA shouldnt be a problem for me. but i wanted to know what caused the problem the first time! i dont want my tablet to die again after the update!
Does OTA update mess up if we are rooted with unlocked boot loaders and custom recoveries??
and as far as i know OTA update will remove root so i can just reroot after the update? probably by using the toolkit or is there any better way? and even twrp recovery... u gave the link for the file but how do i flash the recovery? i know how to flash the root files via twrp but how to get twrp.
forgot to attach the screenshots
GedBlake said:
Yeah... you pretty much have it right. There are two ways you could go...
1) Flash 4.3 straight off.
2) Flash 4.2.2 and then take the 4.3 OTA update...
Click to expand...
Click to collapse
Thank you for this excellently-written tutorial. I learned something about bootloaders that I didn't know.
Sent from my Nexus 7 using xda app-developers app
I have a Nexus 4 with TWRP and root, I have 4.4.2 and want to get to 4.4.4. Unfortunately, I can't update to 4.4.3 OTA. It says the update downloads, I hit restart, and it fails in TWRP. When I reboot, it says I'm up to date for a couple hours and then says I have an update again.
I'm not sure if it's because I have a custom recovery or what but if I need to revert I'd need help with doing that since I did all this about a year ago and don't remember how I did it. I also vaguely remember deleting something in the cache to stop update available messages. I'm not sure if that's to blame, but I'm positive the updates are downloading at the very least. They're just failing to install.
I'm sure this has been answered a number of times but I'm having trouble navigating some of the topics.
Hey,
Download the stock nexus 4 factory image and flash only the system image through fastboot. This will revert your system partition to stock and it will allow the installation of the ota to continue without any loss of user data. You can wait for the next update prompt or you can just download the ota from the ota thread and flash it yourself through TWRP.
Devices:
LG Optimus 2X P990
LG Nexus 4
LG Optimus 2X:
ROM: Tonyp TheROM Build 26 New Bootloader
Kernel: Kowalski Kernel M1 New Bootloader 2.6.39.4 W/ RAM Hack
Bootloader:ICS Bootloader
Recovery: TWRP 2.6.0.0 For New BL
Baseband: 1035.21
Nexus 4:
ROM: Stock 4.4.4 W/ Root (Xposed, GPU Drivers, Dalvik/Bionic Patches)
Kernel: Franco r213
Bootloader: Stock Bootloader (Unlocked)
Recvoery: PhilZ Touch CWM-Based Recovery
Radio:Radio (1.03)
ninjames said:
I have a Nexus 4 with TWRP and root, I have 4.4.2 and want to get to 4.4.4. Unfortunately, I can't update to 4.4.3 OTA. It says the update downloads, I hit restart, and it fails in TWRP. When I reboot, it says I'm up to date for a couple hours and then says I have an update again.
I'm not sure if it's because I have a custom recovery or what but if I need to revert I'd need help with doing that since I did all this about a year ago and don't remember how I did it. I also vaguely remember deleting something in the cache to stop update available messages. I'm not sure if that's to blame, but I'm positive the updates are downloading at the very least. They're just failing to install.
I'm sure this has been answered a number of times but I'm having trouble navigating some of the topics.
Click to expand...
Click to collapse
The update process usually goes through even if you have TWRP.
You can try flashing the stock recovery through fastboot.
Which is the stock Nexus 4 factory image? You mean what it launched with, or do you mean the factor 4.4.2 image since that's what I'm on? Also I'm not sure how to flash through fastboot at this point. Will that remove my custom loader or just remove my root?
You can get the latest factory image from here https://developers.google.com/android/nexus/images
Flashing only the recovery will not remove root. It'll only replace the custom recovery (loader).
Sent from my Nexus 4
---------- Post added at 10:44 PM ---------- Previous post was at 10:34 PM ----------
You can follow this guide http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
Flash only the recovery (refer section D, sl no.12 in the above guide)
Sent from my Nexus 4
I don't believe the reason for your OTA failure is a custom recovery, it is most likely a modification to the system partition. You should extract the system partition image from the factory image and flash that through fastboot, which will remove your root but you can get that back by flashing the SuperSU zip. Then after restoring back to a stock /system partition, take your OTA like normal.
Devices:
LG Optimus 2X P990
LG Nexus 4
LG Optimus 2X:
ROM: Tonyp TheROM Build 26 New Bootloader
Kernel: Kowalski Kernel M1 New Bootloader 2.6.39.4 W/ RAM Hack
Bootloader:ICS Bootloader
Recovery: TWRP 2.6.0.0 For New BL
Baseband: 1035.21
Nexus 4:
ROM: Stock 4.4.4 W/ Root (Xposed, GPU Drivers, Dalvik/Bionic Patches)
Kernel: Franco r213
Bootloader: Stock Bootloader (Unlocked)
Recvoery: PhilZ Touch CWM-Based Recovery
Radio:Radio (1.03)
I'm not sure how to do what you just described. How do I extract a system partition image and how do I flash things through fastboot? Also what version of the system image? The one I'm on? The one it launched with? So what I want to do is flash a factory image, yes? I can't just do that through TWRP? I thank you guys for your help thus far but as to the specifics of what I need to do, I'm not finding much by searching, it all implies specific levels of knowledge that I don't have.
I appreciate the help thus far and going forward.
ninjames said:
I'm not sure how to do what you just described. How do I extract a system partition image and how do I flash things through fastboot? Also what version of the system image? The one I'm on? The one it launched with? So what I want to do is flash a factory image, yes? I can't just do that through TWRP? I thank you guys for your help thus far but as to the specifics of what I need to do, I'm not finding much by searching, it all implies specific levels of knowledge that I don't have.
I appreciate the help thus far and going forward.
Click to expand...
Click to collapse
So, have you got your adb and fastbooot drivers set up?
Sent from my Nexus 4
I think so, yeah. Sorry for the delay in my posting but I'd really like to get this figured out in advance of 5.0 so I can, you know, use it.
So I mean, I'm willing to wipe everything, go back to stock, whatever I need to do to set myself up for getting all the OTAs all the way to 5.0. I just need a little bit of help with that ... I backed up all my stuff, so.
Why don't you just go ahead and flash android lollipop? Since you've already backed up all your data, you can start afresh.
1. Download the factory image from Google's developer site.
2. Extract the contents to the folder android/SDK/platform tools.
3. Connect your phone via USB, boot into bootloader and check if it is recognized by using a command prompt and using command fastboot devices, it should return a value.
4. Run the file flash-all.bat which you can find from the extract.
5. It'll take care of the rest and you'll be good to go.
But it'll wipe all data and bring it to an out of the box state.
Sent from my Nexus 4
Will that work? Don't I need to be on the latest build for that?
And by using "command fastboot devices" what exactly does that mean? What's the step-by-step once I get it all plugged in and all of that?
ninjames said:
Will that work? Don't I need to be on the latest build for that?
And by using "command fastboot devices" what exactly does that mean? What's the step-by-step once I get it all plugged in and all of that?
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=ZK6hYVuKNlw - This one works perfect just replace the file he tells you with
https://dl.google.com/dl/android/aosp/occam-lrx21t-factory-51cee750.tgz < Factory 5.0
Hope this helps
Hit The Thanks if it did
I couldn't really figure out that video .. he was talking about installing APKs and stuff and I didn't know which file from the factory image I was supposed to use? So I extracted it into a directory with the fastboot stuff as per another guide, hit flash all and it said it all worked ... and it did! So ya'll got me started and I stumbled my way to the finish. THANKS SO MUCH!
Hi, I have a Nexus 7 2012 wifi nakasi & my 5.1.1 OTA just landed. As my Nexus is rooted using CF-auto-root & had a TWRP 2.8.5.1 recovery flashed, I fastboot flashed the recovery.img from the 5.1.0 archive & then clicked the button to install the OTA.
It gets half way through, then just says "error". How do I get it to be more informative & could I fix it by just flashing the system partition from my 5.1.0 archive before running the OTA, then re-rooting & re-flashing TWRP?
Thanks
Had the same issue.... Just flashed the update without wiping the use info, so far seems to have worked... Not yet noticing much improvement though so don't get to excited.... Will keep watching it to see if it still crashes in sleep mode whilst sitting in the desk doc/charger...
Sent from my Nexus 7 using XDA Free mobile app
---------- Post added at 07:40 AM ---------- Previous post was at 07:32 AM ----------
Update: loads of system & none system apps still hanging and force closing some without the usual report/wait/OK option
So far:
- Google map
- Android System
- Facebook
- BBC iPlayer
- Chrome
Probably worth a full wipe and re flash to remove any gremlins.....
Sent from my Nexus 7 using XDA Free mobile app
FIXED
JustinSB said:
It gets half way through, then just says "error". How do I get it to be more informative & could I fix it by just flashing the system partition from my 5.1.0 archive before running the OTA, then re-rooting & re-flashing TWRP?
Click to expand...
Click to collapse
I just flashed the system.img from my 5.1.0 archive (the recovery had already been flashed from the first time I tried it), waited half an hour for the OTA to flag up again & it all worked perfectly & upgraded exactly as it should. I haven't tried to root it again yet, as I want to see if it makes a difference.
So that's it, if your Nexus 7 2012 wifi won't let you install the 5.1.1 OTA, flash system.img & recovery.img from the 5.1.0 archive & you will be good to go, with all of your existing software, settings & data still intact. Naturally, you will need to re-root it though.
I flashed the 5.1.1 recovery, boot, and system images and then did a full wipe in recovery. Upon booting into the system, I was offered to restore my previous apps and data which all worked well but took a while to download and install the apps. I had to spend some time setting up the screens but 5.1.1 is running very well (better than 5.1) and I've since flashed twrp to get root. I do believe the wipe is important to get the best performance from the update.
I agree with the poster above me. Not wiping the device, cobbling together some unapproved update scheme pulled out of your ass, then complaining the performance sucks is just plain stupid. Do it right, and it will run butter smooth. But hey, I'm perfectly OK with snapping up several N7's DIRT CHEAP when all the idiots who can't follow instructions start dumping them on eBay and Craigslist thinking they're "broken". I have two cars that could use an in-dash install.
JustinSB said:
Hi, I have a Nexus 7 2012 wifi nakasi & my 5.1.1 OTA just landed. As my Nexus is rooted using CF-auto-root & had a TWRP 2.8.5.1 recovery flashed, I fastboot flashed the recovery.img from the 5.1.0 archive & then clicked the button to install the OTA.
It gets half way through, then just says "error". How do I get it to be more informative & could I fix it by just flashing the system partition from my 5.1.0 archive before running the OTA, then re-rooting & re-flashing TWRP?
Thanks
Click to expand...
Click to collapse
JustinSB,
Since you've already flashed your ROM's stock recovery, I *think* the problem you're encountering is the same one I had when I moved from 5.0.1 to 5.1: The rooting procedure you're using installs a non-stock kernel, which resides in the boot.img partition and is detected in the pre-flash checking phase of things in the OTA update.
If it were me, and I wanted to save a significant amount of time on the update (i.e. keep my userdata and bootloader partitions the same), I'd download the 5.1.1 image archive, uncompress/untar/unzip all the archives, and do the steps outlined here. They involve wiping the cache, recovery, boot, and system partitions and flashing the latter three with the updated images. Definitely do not fail to do any of those steps. Fwiw, and as I note later in that thread, I didn't re-flash the bootloader as it's the same in both ROMs.
All I did to finalize things was to boot to twrp via fastboot and generate a Nandroid back up, and then re-root using the CF-Auto-Root procedure. Afterwards I was set and experienced no particular system slowdowns. The whole process took about 15 minutes, including waiting for the dalvik-cache to reinitialize. I typically do not flash twrp, I just boot to it from fastboot as needed.
As a poster has pointed out in his non-diplomatic way, this is not the recommended path to updating, so if you encounter problems going this route, you can always do the full reset thing and re-load all of your userdata from a back up as a second option.
Which ever path you decide to follow, I wish you good luck.
cheers,
john
Well, I guess I'm going to do the unthinkable and reply to my own post to say that I've just followed the procedure I described above, this time to update from 5.1 to 5.1.1. It also took a total of 15 minutes with the longest portion of that time taken by the dalvik-cache reinitializing during the first reboot.
Good luck to you, OP. I hope that you upgrade goes as smoothly.
cheers,
john
I am currently on stock rom but rooted. An Ota update popped up can I update without bootloop
I would like to know the same thing
Naruto101 said:
I am currently on stock rom but rooted. An Ota update popped up can I update without bootloop
Click to expand...
Click to collapse
stkman32 said:
I would like to know the same thing
Click to expand...
Click to collapse
No you can't take an OTA if you have any modifications to /system (root). Have a look at my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
I got an 8MB update for the november patch. Being on TWRP and root i need to convert back to stock before i can have it leave me alone? Is there a way to flash the patch without doing that?
Thanks for answering my question
roughriduz said:
I got an 8MB update for the november patch. Being on TWRP and root i need to convert back to stock before i can have it leave me alone? Is there a way to flash the patch without doing that?
Click to expand...
Click to collapse
No way around it, any modifications will cause the update to fail.
Heisenberg said:
No way around it, any modifications will cause the update to fail.
Click to expand...
Click to collapse
@amoeller had me flash the modified boot.img for MDB08M then flash the MDB08M system.img and vendor.img from the factory image. I rebooted bootloader, the booted to TWRP and re-flashed supersu. I am now on the November patch without having to remove TWRP and all works well. My user data was also untouched.
roughriduz said:
@amoeller had me flash the modified boot.img for MDB08M then flash the MDB08M system.img and vendor.img from the factory image. I rebooted bootloader, the booted to TWRP and re-flashed supersu. I am now on the November patch without having to remove TWRP and all works well. My user data was also untouched.
Click to expand...
Click to collapse
User data should never be affected during an OTA anyway.
This is actually the first time I've unlocked a phones bootloader and stuck with the stock rom. I usually use some kind of popular rom with it's own built in OTA (CM/Viper One)
How often do you guys actually update your phones for OTA? It seems like a real hassle
GloriousGlory said:
This is actually the first time I've unlocked a phones bootloader and stuck with the stock rom. I usually use some kind of popular rom with it's own built in OTA (CM/Viper One)
How often do you guys actually update your phones for OTA? It seems like a real hassle
Click to expand...
Click to collapse
I am rooted now so I'll wait a while before updating an ota until there's a big deal of info. However, in the past if I was sticking with stock there's usually at least one developer who posts the updates with root and stuff built in so you can easily flash with twrp. So I'm kind of waiting for that. That or cataclysm or another awesome rom that's close to stock.
GloriousGlory said:
This is actually the first time I've unlocked a phones bootloader and stuck with the stock rom. I usually use some kind of popular rom with it's own built in OTA (CM/Viper One)
How often do you guys actually update your phones for OTA? It seems like a real hassle
Click to expand...
Click to collapse
I wait for factory image for that build and flash over the new images when they become available (provided that root can still be achieved). Some will do a clean wipe and start fresh with the new build and reload in their apps and user data, others will just dirty flash the updated system (and boot/bootloader or whatever else was changed too).
If you think about it, it really isn't all that different from taking an OTA, the difference is that we're applying the commands to flash instead of having it automated. It's not that big of a trade off in my book.
I have 2 questions...
What is the easiest way to make flashing updates a breeze if I have mods in /system partition? I have heard of "freezing" them. Or is the only option... to delete every mod and flash updates? If so, should I keep a note of every change I make to/system?
And last... Should I make a backup of any file i am replacing or overwriting in /system? And if so, do I have to put them back how they were before flashing an update?
Delete
If you're rooted then you need to download the full factory image, extract system and vendor and flash those. Reflash SuperSU.
roughriduz said:
@amoeller had me flash the modified boot.img for MDB08M then flash the MDB08M system.img and vendor.img from the factory image. I rebooted bootloader, the booted to TWRP and re-flashed supersu. I am now on the November patch without having to remove TWRP and all works well. My user data was also untouched.
Click to expand...
Click to collapse
It’s probably easier and quicker just to flash stock factory images separately instead of having to jump through hoops with OTAs. Like I told @roughriduz just flash the updated partition(s) that were updated like system.img, vendor.img, or whatever and just flash SuperSU in TWRP after.
The steps @roughriduz took was
1. Download and extract latest factory image.
2. Download matching modified boot.img for that build (For example MDB08M).
3. Flash system, vendor, and any other partitions (like radios, etc) with fastboot if they were updated in the OTA. Don’t bother to flash stock recovery because we’re not using an OTA. Flashing userdata.img is just like a factory reset.
4. Boot directly into TWRP and flash SuperSU.
5. Reboot and profit.
This method gives you the latest stock build rooted with TWRP while keeping your data because I hate having to redo my phone.
amoeller said:
It’s probably easier and quicker just to flash stock factory images separately instead of having to jump through hoops with OTAs. Like I told @roughriduz just flash the updated partition(s) that were updated like system.img, vendor.img, or whatever and just flash SuperSU in TWRP after.
The steps @roughriduz took was
1. Download and extract latest factory image.
2. Download matching modified boot.img for that build (For example MDB08M).
3. Flash system, vendor, and any other partitions (like radios, etc) with fastboot if they were updated in the OTA. Don’t bother to flash stock recovery because we’re not using an OTA. Flashing userdata.img is just like a factory reset.
4. Boot directly into TWRP and flash SuperSU.
5. Reboot and profit.
This method gives you the latest stock build rooted with TWRP while keeping your data because I hate having to redo my phone.
Click to expand...
Click to collapse
A couple questions:
1. Step 1 refers to the latest factory image that contains the update, correct?
2. Step two refers to the boot.img that contains root?
3. At what point in this process do you flash the modified boot.img, before or after applying the other images?
Thanks for your help!
JimmyJunk said:
A couple questions:
1. Step 1 refers to the latest factory image that contains the update, correct?
2. Step two refers to the boot.img that contains root?
3. At what point in this process do you flash the modified boot.img, before or after applying the other images?
Thanks for your help!
Click to expand...
Click to collapse
1. Latest factory image is the latest factory image from the nexus factory images page. It's not an update like ota, but rather the entire image they would return you to stock if all is flashed.
2. Flashing a modified boot does not give you root. You still have to flash SU, so saying the modified boot contains root isn't right.
3. I flash boot first unless there is an updated bootloader.
JimmyJunk said:
A couple questions:
1. Step 1 refers to the latest factory image that contains the update, correct?
2. Step two refers to the boot.img that contains root?
3. At what point in this process do you flash the modified boot.img, before or after applying the other images?
Thanks for your help!
Click to expand...
Click to collapse
1. This can be whatever the latest factory image is at the moment. It’s currently MDB08M. All the OTA does is update your phone to whatever build it was made for. Factory images already have previously released updates built into them. You can upgrade but avoid downgrading unless you want to factory reset your phone.
2. I’m referring to the boot.img without root by @mrRobinson found https://www.androidfilehost.com/?fid=24269982086992320 although this process can be used for systemless root also. For systemless root you wouldn’t flash SuperSU in TWRP but instead sideload the SuperSU APK as per Chainfire’s instructions and use the matching systemless root boot.img
3. I don’t think it matters but as long as you have the matching modified boot.img with the system.img installed before you restart, you should be fine.
amoeller said:
It’s probably easier and quicker just to flash stock factory images separately instead of having to jump through hoops with OTAs. Like I told @roughriduz just flash the updated partition(s) that were updated like system.img, vendor.img, or whatever and just flash SuperSU in TWRP after.
The steps @roughriduz took was
1. Download and extract latest factory image.
2. Download matching modified boot.img for that build (For example MDB08M).
3. Flash system, vendor, and any other partitions (like radios, etc) with fastboot if they were updated in the OTA. Don’t bother to flash stock recovery because we’re not using an OTA. Flashing userdata.img is just like a factory reset.
4. Boot directly into TWRP and flash SuperSU.
5. Reboot and profit..
Click to expand...
Click to collapse
What the heck did I do wrong here? I just tried to apply the November OTA update to my MBD08K build, it didn't work, and now I am in the process of doing a full reset and rebuild of my phone (flash-all of factory images from Google)
Here are the notes I made as I attempted to follow the procedure in this thread:
Code:
- Download latest build for MBD08K from https://developers.google.com/android/nexus/images?hl=en
- Extract boot.img, system.img, vendor.img to C:\adb (or wherever where adb and fastboot are
installed). You have to
- Right-click, open command window here
- Ensure USB debugging is enabled on phone (grant permissions on phone if you get the popup)
- In command prompt, "adb devices"
- Should see serial number and "device"
- type "adb reboot bootloader"
- Should get to bootloader screen with little android man lying down with hatch open
- type "fastboot devices" - should see your serial # again and "fastboot" beside it.
- type "fastboot flash boot boot.img"
- type "fastboot flash system system.img"
- type "fastboot flash vendor vendor.img"
- Use volume keys to boot into recovery (in my case TWRP)
- Swipe to allow modifications
- Install -> SuperSU.zip that you should have on your phone from last time.
- Reboot system
I saw a red "your phone is corrupt" scary message on startup... took a while to boot. Couldn't get past the dancing circles.
Interrupted boot, rebooted to fastboot, tried to flash old modified boot.img
Booted again, got encryption unsuccessful warning
Flashed most recent boot.img again, stuck booting forever
try again:
- flash system.img
- flash vendor.img
- flash boot.img (modified)
reboot to recovery - your device can't be checked for corruption (yellow warning instead of red)
- swipe to allow modifications
- reboot with TWRP, swipe to install SuperSU
- Encryption unsuccessful. Prompt to factory reset. Click OK. Boots through TWRP.
Give up, start flashing factory images.
EDIT: I might be the stupidest person alive. I think I should have been using the files for MDB08M. Arggghhhh. Someone please confirm I am an idiot.
Edit 2: Factory reset worked, I am at MDB08M. Now rooting again... grr. At least I backed up all my apps & settings to Google Drive with TB.
Edit 3: Rooted and restoring all apps with TB. If anyone has any insight into where I F'ed up I'd appreciate it.
Any ideas?
Im rooted, the update downloads and appears to install but then reboots and its back to where it was, not installed.
Same for me. I did a factory reset and tried to install it again. Same thing.. It just stalls and reboots. Guess I am lucky it don't freeze there at least.. Thought I'd mention that factory reset don't help. That way it will save u the trouble.. I guess I am going to lock the bootloader and try again... I'll let u know how that works... It shouldn't matter though... All prev. Updates went fine with unlocked bootloader.. I just had to reinstall root after update...
Essentially though... I'm pissed at the moment cause I factory reset for Nada.. :/
Going through the same loops now trying second time now but I'm not rooted ... May have TWRP installed though but I don't think so as last time I updated I didn't bother rooting
I don't have twrp installed on mine but it was rooted. Not now after factory reset... My bootloader is unlocked though... I was going to try relocking it and try again but at this point I'm just like... Screw it
I don't think its the issue anyways as I have updated before with it unlocked.
When rooted before, I just booted the twrp image. It seemed the safest approach and worked just fine that way for installing su.. And that's basically all I needed twrp for so...
I'm sure they will fix it or get to the bottom of it.. It seems to be an issue for some people on geforce forums, here and redit
If anyone finds a solution please post here
I am in the same boat. Unlocked bootloader, rooted, but recovery is stock. The only other thing I did was flash a kernel for USB TV tuner support.
https://forums.geforce.com/default/...ficial-usb-tv-tuner-support-to-live-channels/
But I don't think it's related. And just like the rest of you I have never had an issue taking an update. This update goes through the usual process, then reboots, but it just reboots to the same version.
I suspect we'll need to wait for nvidia to post the full firmware on their developer site, so we can flash it via fastboot. Rooting modifies the system partition and is probably why the OTA won't take.
I have not flashed a kernal to mine so I'd rule the kernal out as well. Stock recovery as well
I seen somewhere else its an issue with root. Perhaps so a root removal then try... I factory reset and no dice... Maybe I'll try rerooting and then remove root... Then try installing
bradleyw801 said:
I am in the same boat. Unlocked bootloader, rooted, but recovery is stock. The only other thing I did was flash a kernel for USB TV tuner support.
https://forums.geforce.com/default/...ficial-usb-tv-tuner-support-to-live-channels/
But I don't think it's related. And just like the rest of you I have never had an issue taking an update. This update goes through the usual process, then reboots, but it just reboots to the same version.
Click to expand...
Click to collapse
Same boat, downloads but will not install, I am rooted
Confirmed on the official forum that ota update won't work on root. Firmware available on nvidia developer site in about a week
adam_ky said:
I seen somewhere else its an issue with root. Perhaps so a root removal then try... I factory reset and no dice... Maybe I'll try rerooting and then remove root... Then try installing
Click to expand...
Click to collapse
Don't waste your time, it won't work. I did unroot, then updated and after reboot same pop up coming upgrade notification. Then I did factory reset, updated and after reboot same pop up coming upgrade notification.
aankkurr said:
Don't waste your time, it won't work. I did unroot, then updated and after reboot same pop up coming upgrade notification. Then I did factory reset, updated and after reboot same pop up coming upgrade notification.
Click to expand...
Click to collapse
I'm stock everything and also got loops last night, then just gave up.
I'll add to your list... Don't install stock recovery images either.
I followed accompanied directions to a T. I tried to flash stock 5.1 on top of 5.1. Everything flashed fine, no errors. But upon reboot from flash, shield is dead. No green lights, no boot.
My theory is its an indicator that something is wrong with your shield if it won't take the update..
Some faulty hardware or something perhaps..
Luckily I'm still under warranty and got a replacement coming. Just be careful.
The fail of the update is not strictly related to root. But logically you need a stock firmware to install the update, without root.
Nvidia pushed a progessive update and you need the stock boot.img system.img vendor.img recovery.img to install the 5.2 update
I have two Shield TV 16GB 2015 and a Shield TV 16GB 2017
on the two 2015 models, i reinstalled the stock 5.1 firmware ( all stock ) and i started the update.
on one shield tv the update fail, while on the other the update went well.
the progressive update ( this is the first time that Nvidia published a progressive update ) fail if your internal sdcard have some bad sectors. Can be the only explaination.
To solve we need soon the 5.2 stock complete recovery image.
For the Shield TV 2017 model the update went well, but after the 5.2 update TWRP not work anymore. Therefore you can't do almost nothing.
TWRP instead work on the 2015 model with the last 5.2 firmware.
Yep. Nvidia said they'd post the full 5.2 image in a week or so. Until then we twiddle our thumbs.
Before I got the preview update for 5.2 I was rooted with the kernel that allowed USB TV tuner.
I flashed factory 5.1 image, locked bootloader and once Shield booted back up I did a factory reset since I was still getting the warning about my bootloader being unlocked. After factory reset I no longer had warning and the update went smooth.
This is on 2017 16GB Shield.
The progressive update needs to be undone.... That was a stupid move and looks to have caused tons of problems. The last update to 5.1 I did while rooted.... I don't see the issue... But like I said in my experience... I don't think it was my core issue.. I flashed all the stock 5.1 images and it killed my shield... I would say that some other problem was lurking in the background on my particular device.. But they are sending me a new one... So all is good
Well, I have the 2015 16gb model. I had it with custom ROM (full Android nougat), stock recovery and rooted with SuperSU.
I also had that loop when attempting to upgrade to 5.2, the install would get stuck at the same spot each time I tried and then device rebooted automatically afterwards without upgrading, but that's because I forgot to flash stock boot.img to completely remove root, once I did the upgrade installed successfully.
What I did in fastboot to go back to stock 5.1 was:
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot -w (very important)
fastboot reboot
* Word of advice Do Not Use flash-all.bat * Flash manually running each command and preferably do a clean install.
Note i didn't flash the bootloader (blob file) as there was no need plus it is a sensitive file which can hard brick your device if wrongly flashed or corrupted.
Also the bootloader version hasn't changed so no update on that matter.
Sent from my Tapatalk beta Hub
If I helped hit the Thanks button. Follow Me! ~ DroidMote user ~ Full Android for Shield TV and Nexus Player
unrooted 2015 16gb here. still can't update. Hell, i can't even restore the factory image since it tells me that the data is too large for system.img and vendor.img. Anyone ever see that?
---------- Post added at 04:15 PM ---------- Previous post was at 03:54 PM ----------
not rooted, still won't install
pendragon666 said:
unrooted 2015 16gb here. still can't update. Hell, i can't even restore the factory image since it tells me that the data is too large for system.img and vendor.img. Anyone ever see that?
---------- Post added at 04:15 PM ---------- Previous post was at 03:54 PM ----------
not rooted, still won't install
Click to expand...
Click to collapse
Yeah, the shield is picky. Just try with other usb cables and/or other usb port in your PC, preferably usb 2.0 as some 3.0 can cause interference.
I myself have flashed on Windows 10 x64 with stock usb cable and usb 2.0 and 3.0 ports on my devices without issues but it is well known what i mentioned above, those tips most of the times help. I remember a user that even formatted his Windows laptop and then finally he could install drivers and flash.
Sent from my Tapatalk beta Hub
If I helped hit the Thanks button. Follow Me! ~ DroidMote user ~ Full Android for Shield TV and Nexus Player