How to reload OTA update after clearing cache? - Nexus 7 Q&A, Help & Troubleshooting

I described here my failed attempt to update to 4.4.4
I've restored the device back to stock 4.3 JRW66Y, not rooted, and the cache has been cleared.
But the system remembers that it had an OTA to 4.4.2. If I try to install it it hangs 'rebooting now'.
logcat says E/SystemUpdateService( 961): 'OTA package doesn't exist'
Can I, without rooting it, get the system to forget that it had this OTA so that it will download a new one?

Dave_Ro said:
I described here my failed attempt to update to 4.4.4
I've restored the device back to stock 4.3 JRW66Y, not rooted, and the cache has been cleared.
But the system remembers that it had an OTA to 4.4.2. If I try to install it it hangs 'rebooting now'.
logcat says E/SystemUpdateService( 961): 'OTA package doesn't exist'
Can I, without rooting it, get the system to forget that it had this OTA so that it will download a new one?
Click to expand...
Click to collapse
You could do a factory reset then it should be able to download the OTA but the factory reset will completely wipe your device and you need to have the correct bootloader for the OTA to work. What version bootloader do you have?

wantabe said:
You could do a factory reset then it should be able to download the OTA but the factory reset will completely wipe your device and you need to have the correct bootloader for the OTA to work. What version bootloader do you have?
Click to expand...
Click to collapse
I don't want to do a factory reset - I'd rather live with 4.3
The installed bootloader is 4.23. Although the installed system is JRW66Y the bootloader is from JRW66V (see this thread).
I wonder whether deleting Google Services Framework data will do the trick, but this may have undesirable consequences (see this thread).
Maybe I'll wait a bit and have another go at flashing 4.4.4 - see my OP; nobody has suggested yet why that didn't work.

Dave_Ro said:
I don't want to do a factory reset - I'd rather live with 4.3
The installed bootloader is 4.23. Although the installed system is JRW66Y the bootloader is from JRW66V (see this thread).
I wonder whether deleting Google Services Framework data will do the trick, but this may have undesirable consequences (see this thread).
Maybe I'll wait a bit and have another go at flashing 4.4.4 - see my OP; nobody has suggested yet why that didn't work.
Click to expand...
Click to collapse
Sorry! I should have received a notification email that you had responded. For whatever reason, lately, the notification works some of the time but not always. I had no idea the bootloaders had gotten so effing screwed up! I bought my daughter a 2012 N7 for Christmas and no wonder I had to let it do an OTA before it would let me flash a factory image. I vaguely remember getting a bootloader invalid state error. My brothers bone stock 2012 N7 is on 4.4.4 with no issues, he would have called me otherwise. ; )
If you don't want to do a factory reset you CAN flash the factory image without wiping your device, as long as your bootloader is already/still unlocked. If you modify the flash_all.bat, which is inside the factory image the userdata.img which wipes your device won't be flashed. If you open the flash_all.bat with whatever text editor you use (I use editpad lite or notepad) and remove the -w from the text it won't wipe your device. You will keep your settings, installed apps and storage. Extract the factory image into the same folder as your adb.exe and fastboot.exe, you should see these files if you have the 3G version;
bootloader-tilapia-4.23.img
flash-all.bat
flash-all.sh
flash-base.sh
image-nakasig-krt16s.zip
radio-tilapia-1231_0.18.0_0409.img
The 4.4 (krt16s) is the newest factory image that has the exact same bootloader as jwr66v. From there you can let it do some OTA's or flash the 4.4.4 factory image. If you need help getting the sdk installed or have any questions let me know, hopefully the notification will work.

wantabe said:
...I had no idea the bootloaders had gotten so effing screwed up!
Click to expand...
Click to collapse
I'm not sure whether these bootloaders are as screwed up and some posts suggests. A corrupt bootloader in one release - JRW66Y - I can understand, but I'd have thought it would get corrected. But no, and the next version is also suspect. There's something going on that I don't understand. Files with the same name but different MD5s - why is that? I don't understand the 'signatures' that people mention - is there are explanation of that? In the post above mine at the end of this thread (post #98) he refers to a signature mismatch. I got the same error (post #100) but no mention of signatures. And that bootloader failed to flash despite others presumably having been successful and it having the 'correct' MD5 (which the OP has changed in the original post!). All very odd.
]If you don't want to do a factory reset you CAN flash the factory image without wiping your device, as long as your bootloader is already/still unlocked. If you modify the flash_all.bat, which is inside the factory image the userdata.img which wipes your device won't be flashed. If you open the flash_all.bat with whatever text editor...
Click to expand...
Click to collapse
I use Linux and flash the partitions individually rather than using their script, but essentially It's what I did with 4.4.4 KTU84 - at least I'm pretty sure I did.
The 4.4 (krt16s) is the newest factory image that has the exact same bootloader as jwr66v. From there you can let it do some OTA's or flash the 4.4.4 factory image. If you need help getting the sdk installed or have any questions let me know, hopefully the notification will work.
Click to expand...
Click to collapse
I might try KRT16S instead of KTU84P - it's a smaller step. But it would be better to go straight to the latest.
But I'd like to understand what's happening before I try again - and nobody's suggesting anything on that other thread. I guess the world's move on from the Nexus 7 2012! But thanks for your full replies and suggestions.
Going back to the object of this thread, here must be some way to just tell GFS to forget that it once downloaded that OTA! Any suggestions on that?

Dave_Ro said:
I'm not sure whether these bootloaders are as screwed up and some posts suggests. A corrupt bootloader in one release - JRW66Y - I can understand, but I'd have thought it would get corrected. But no, and the next version is also suspect. There's something going on that I don't understand. Files with the same name but different MD5s - why is that? I don't understand the 'signatures' that people mention - is there are explanation of that? In the post above mine at the end of this thread (post #98) he refers to a signature mismatch. I got the same error (post #100) but no mention of signatures. And that bootloader failed to flash despite others presumably having been successful and it having the 'correct' MD5 (which the OP has changed in the original post!). All very odd.
I use Linux and flash the partitions individually rather than using their script, but essentially It's what I did with 4.4.4 KTU84 - at least I'm pretty sure I did.
I might try KRT16S instead of KTU84P - it's a smaller step. But it would be better to go straight to the latest.
But I'd like to understand what's happening before I try again - and nobody's suggesting anything on that other thread. I guess the world's move on from the Nexus 7 2012! But thanks for your full replies and suggestions.
Going back to the object of this thread, here must be some way to just tell GFS to forget that it once downloaded that OTA! Any suggestions on that?
Click to expand...
Click to collapse
Out of curiosity I looked at the bootloaders and even though they say v4.23 a crap load of them are different sizes. Just as an example jwr66v is 2,150,992 bytes and ktu84p is 2,151,068 bytes. Don't have a clue what is going on. I can tell you that the bootloaders on the N5 and 2013 N7 are the exact same size across os versions that state the same bootloader version number.
---------- Post added at 02:19 AM ---------- Previous post was at 02:00 AM ----------
The vast majority of the time I also fastboot flash the images separately, I make a few too may changes in the system files to be able to use an OTA unless it's a very small one. I would flash the images for krt16s, bootloader, boot, system, recovery and radio. Then let it do a couple OTA's. 4.4.2 has a different size bootloader (4,005,632 bytes) and 4.3, 4.4.3 and 4.4.4 have the same size (2,151,068 bytes).
---------- Post added at 02:26 AM ---------- Previous post was at 02:19 AM ----------
Dave_Ro said:
Going back to the object of this thread, here must be some way to just tell GFS to forget that it once downloaded that OTA! Any suggestions on that?
Click to expand...
Click to collapse
I would think flashing the system image would clear it out but I guess not. If you were rooted you could run SDMaid and I think that would clear it. If you were rooted you could sideload the OTA and put it in /cache and see it that works. Sorry, I don't have a lot of experience running OTA updates, I usually have to fastboot flash images.

Well, in the end I successfully reflashed it to 4.4 (KRT16S), erasing user data. It then did 3 OTAs to 4.4.4 in quick succession.
Along the way it said:
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'tos.img'
tos? ISTR that was on the Atari ST
Thanks for the suggestion. I don't need half these apps anyway - it's good to have a clearout!
Dave

Related

Can't update to 4.1.1. Please Help!!!

Let me start off by saying that I have tried everything I can find. I have tried the ADB sideload method. I have tried to go to the firmware it's trying to upgrade from. I've tried both stock recovery and CWM. I'm not a n00b when it comes to unlocking, rooting, flashing etc. Anyway, here's the story. My dad bought a Nexus 7 32GB and it kept asking him to update to 4.1.1 for the landscape rotation. The first time he tried it, it failed because it was trying to update from a specific firmware that he didn't have. He has JRO03S. It was trying to update from JRO03D to the new 4.1.1 update. It fails every time no matter what. Like I stated earlier, I've tried both stock recovery and CWM, but they both error out. I've included some pictures of the error in CWM and the about device screen, but nothing from stock recovery. I was too lazy to put the stock recovery back on there to take a picture, but if it's necessary for a solution then I will. Yes, I have searched here and google. Every solution that I have found has not worked. If anyone can help me then you would be a lifesaver. Thanks for taking the time to read through all this. If I'm not being specific enough then please let me know what else you need to know.
The assert() failure you see in the custom recovery is to be expected - it is the installer script checking to make sure that someone is attempting to apply the update to an exact version of the factory software. In this case, exact also means the version of the recovery boot in use which is trying to process the update.
In general, you can not use a custom recovery with an unmodified OTA installer file because of that first assert.
The OTA updates are NOT complete re-installs; they use a patching tool to fix up existing files on the device. That allows their size to be quite a bit smaller than a full new install. Read that again - existing files!.
It is my impression (someone correct me if I am wrong) that the installer scripts also do checksums on each individual target files that are intended to be patched, and if a single one of them fails, the install will spontaneously abort - part way through the process.
That has serious consequences, as now a failed partial install will block a subsequent attempt - if any of the target files get successfully patched, they will no longer have the checksum expected by the update script - they will no longer have the (old file) checksum. [ note I might be fuzzy on whether the individual file checks cause a wholesale abort of the installation session, or they cause a per-file abort ]
In general, you can only use an OTA patch kit on a modified phone if you have not altered any of the files involved in the patching process, and you are using the stock recovery. If you want to use a custom recovery, for certain you need to diddle the update .zip file at a minimum to remove that initial assert(), and also verify that you have not removed or fooled with any of the files from the original distro that are involved in the patching process.
Given where you are, I suggest you make backups (possibly including using Titanium Backup), and start over with the phone (flash a stock 4.1.x or 4.2.x installation or a custom ROM). OR, if you happen to have a near bone-stock backup (meaning the only thing you have done is install the Superuser.apk and su binary), you could restore that, restore the stock recovery, and then proceed with the update from there.
good luck
bftb0 said:
The assert() failure you see in the custom recovery is to be expected - it is the installer script checking to make sure that someone is attempting to apply the update to an exact version of the factory software. In this case, exact also means the version of the recovery boot in use which is trying to process the update.
In general, you can not use a custom recovery with an unmodified OTA installer file because of that first assert.
The OTA updates are NOT complete re-installs; they use a patching tool to fix up existing files on the device. That allows their size to be quite a bit smaller than a full new install. Read that again - existing files!.
It is my impression (someone correct me if I am wrong) that the installer scripts also do checksums on each individual target files that are intended to be patched, and if a single one of them fails, the install will spontaneously abort - part way through the process.
That has serious consequences, as now a failed partial install will block a subsequent attempt - if any of the target files get successfully patched, they will no longer have the checksum expected by the update script - they will no longer have the (old file) checksum. [ note I might be fuzzy on whether the individual file checks cause a wholesale abort of the installation session, or they cause a per-file abort ]
In general, you can only use an OTA patch kit on a modified phone if you have not altered any of the files involved in the patching process, and you are using the stock recovery. If you want to use a custom recovery, for certain you need to diddle the update .zip file at a minimum to remove that initial assert(), and also verify that you have not removed or fooled with any of the files from the original distro that are involved in the patching process.
Given where you are, I suggest you make backups (possibly including using Titanium Backup), and start over with the phone (flash a stock 4.1.x or 4.2.x installation or a custom ROM). OR, if you happen to have a near bone-stock backup (meaning the only thing you have done is install the Superuser.apk and su binary), you could restore that, restore the stock recovery, and then proceed with the update from there.
good luck
Click to expand...
Click to collapse
I appreciate your response. I think I may have left some things out. I am not rooted. I have only flashed the custom recovery and unlocked the bootloader. That's it. If I have to start completely over then I will. I have already tried that though. I'm willing to try any solutions that anyone has. Thanks again for your response.
Evo4eva said:
I appreciate your response. I think I may have left some things out. I am not rooted. I have only flashed the custom recovery and unlocked the bootloader. That's it. If I have to start completely over then I will. I have already tried that though. I'm willing to try any solutions that anyone has. Thanks again for your response.
Click to expand...
Click to collapse
OK. I saw the "ClockworkMod Recovery v6.0.1.0" banner and assumed rooting.
Well, let's look at the assert that you show failing (first image)
assert failed: apply_patch_check("EMMC: /dev/block/platform/sdhci-tegra.3/by-name/LNX:5007....)
Click to expand...
Click to collapse
The "LNX" partition is the "boot.img" area of the device - the kernel and ramdisk for your regular OS boot.
The fact that the assert fails means one of two things:
- that your boot partition has been modified from "stock", or
- the update .zip file is intended for some other version of a factory rom.
One of those two things. Would be sort of surprising if the OTA process mis-judged which factory release was currently on the phone. From the first image, it sure looks like the update package is intended for a from/to migration of:
JRO03S -> JZ054K
and your status screen does show JRO03S. Are you sure don't have a slightly modified boot partition?
I'm not sure what the four parameters in the assert statement are - I would think that at least one of them has to be a checksum. As the LNX (boot) partition is just a binary blob there is no filesystem present; perhaps the shorter numbers are byte lengths within the partition.
If you want to download the same OTA and fool with it (for instance to omit that first assert in META-INF/com/google/android/updater-script, re-zip it & try with TWRP), this link seems to be working:
http://android.clients.google.com/p...signed-nakasi-JZO54K-from-JRO03S.d41da8f6.zip
That's the same place the OTA process gets it from (and stuffs it into /cache along with a recovery-command file).
good luck
---------- Post added at 02:22 PM ---------- Previous post was at 02:04 PM ----------
Update -
On a lark I downloaded the OTA (referenced in the URL above) and took a look at
META-INF/com/google/android/updater-script
the assert that you see failing is the very last check before it actually begins the patching process!
That means that all the other checks (things in the /system partition) passed before that last check failed.
That certainly seems to imply a boot image that has been diddled with. Since you still show JRO03S (I'm not sure about the kernel string - I don't know what it is supposed to be), most likely this would have been a flashable zip that modified something only in the ramdisk. Does that sound familiar?
bftb0 said:
OK. I saw the "ClockworkMod Recovery v6.0.1.0" banner and assumed rooting.
Well, let's look at the assert that you show failing (first image)
The "LNX" partition is the "boot.img" area of the device - the kernel and ramdisk for your regular OS boot.
The fact that the assert fails means one of two things:
- that your boot partition has been modified from "stock", or
- the update .zip file is intended for some other version of a factory rom.
One of those two things. Would be sort of surprising if the OTA process mis-judged which factory release was currently on the phone. From the first image, it sure looks like the update package is intended for a from/to migration of:
JRO03S -> JZ054K
and your status screen does show JRO03S. Are you sure don't have a slightly modified boot partition?
I'm not sure what the four parameters in the assert statement are - I would think that at least one of them has to be a checksum. As the LNX (boot) partition is just a binary blob there is no filesystem present; perhaps the shorter numbers are byte lengths within the partition.
If you want to download the same OTA and fool with it (for instance to omit that first assert in META-INF/com/google/android/updater-script, re-zip it & try with TWRP), this link seems to be working:
http://android.clients.google.com/p...signed-nakasi-JZO54K-from-JRO03S.d41da8f6.zip
That's the same place the OTA process gets it from (and stuffs it into /cache along with a recovery-command file).
good luck
---------- Post added at 02:22 PM ---------- Previous post was at 02:04 PM ----------
Update -
On a lark I downloaded the OTA (referenced in the URL above) and took a look at
META-INF/com/google/android/updater-script
the assert that you see failing is the very last check before it actually begins the patching process!
That means that all the other checks (things in the /system partition) passed before that last check failed.
That certainly seems to imply a boot image that has been diddled with. Since you still show JRO03S (I'm not sure about the kernel string - I don't know what it is supposed to be), most likely this would have been a flashable zip that modified something only in the ramdisk. Does that sound familiar?
Click to expand...
Click to collapse
All I did was use the nexus 7 toolkit to unlock the bootloader and flash CWM touch. Yes, I do think CWM was a zip file. I'm not sure though. It's been a while since I did all that. I didn't flash anything else though.
Evo4eva said:
All I did was use the nexus 7 toolkit to unlock the bootloader and flash CWM touch. Yes, I do think CWM was a zip file. I'm not sure though. It's been a while since I did all that. I didn't flash anything else though.
Click to expand...
Click to collapse
Well, I don't know what to tell you then. Everything looks kosher except for the fact the installer is complaining about the existing boot partition not matching what it is looking for. If you took that check out, and let the patcher-thingy do its work, it could easily bork your boot image and render your tablet OS unbootable.
At this point, if you are intent on staying on 4.1.x, I suggest you install Titanium Backup, back up all your User apps & data (not the system apps), and install the full factory image for JZO54K from here
To be on the safe side, make a backup of everything on your "SD card" - after you have done the Titanium Backup.
bftb0 said:
Well, I don't know what to tell you then. Everything looks kosher except for the fact the installer is complaining about the existing boot partition not matching what it is looking for. If you took that check out, and let the patcher-thingy do its work, it could easily bork your boot image and render your tablet OS unbootable.
At this point, if you are intent on staying on 4.1.x, I suggest you install Titanium Backup, back up all your User apps & data (not the system apps), and install the full factory image for JZO54K from here
To be on the safe side, make a backup of everything on your "SD card" - after you have done the Titanium Backup.
Click to expand...
Click to collapse
Well, unfortunately I have already tried that factory image on stock recovery and through ADB. It failed also. I appreciate all the help so far, but it looks like my dad has a bunk tablet. I'll just flash the stock recovery and have him get an exchange. I don't see another option. Thanks again!
Evo4eva said:
Well, unfortunately I have already tried that factory image on stock recovery and through ADB. It failed also. I appreciate all the help so far, but it looks like my dad has a bunk tablet. I'll just flash the stock recovery and have him get an exchange. I don't see another option. Thanks again!
Click to expand...
Click to collapse
Well I would think that is a failure with a different root cause as the factory installs don't really care about what is on the tablet - well, except maybe for a version check of the bootloader, and I do see that JZO54K did have the older v3.41 bootloader. That's a possibility.
What error occurs when you try to flash that factory image?
FWIW, oldblue910 mantains an archive of Nexus 7 factory images. You didn't mention whether or not you were on the WiFi only version (nakasi) or 3G version (nakasig), but he has both on his site.
good luck
PS I note that I never checked if there was a different OTA depending on whether or not the unit in question was 3G vs. WiFi-only, although TBH it would be weird if the wrong one got delivered over the air to the tablet. It does seem quite odd though, that the only thing which doesn't pass the initial OTA assert checks (checksums) is the boot image.
bftb0 said:
Well I would think that is a failure with a different root cause as the factory installs don't really care about what is on the tablet - well, except maybe for a version check of the bootloader, and I do see that JZO54K did have the older v3.41 bootloader. That's a possibility.
What error occurs when you try to flash that factory image?
FWIW, oldblue910 mantains an archive of Nexus 7 factory images. You didn't mention whether or not you were on the WiFi only version (nakasi) or 3G version (nakasig), but he has both on his site.
good luck
PS I note that I never checked if there was a different OTA depending on whether or not the unit in question was 3G vs. WiFi-only, although TBH it would be weird if the wrong one got delivered over the air to the tablet. It does seem quite odd though, that the only thing which doesn't pass the initial OTA assert checks (checksums) is the boot image.
Click to expand...
Click to collapse
It's the WiFi only version. I know this whole situation is weird. I've been rooting and flashing since the G1 and have never encountered anything like this. I did make sure I tried the one that was for the WiFi version and it still didn't work though. Thanks again for all your help.

[HOW TO] Downgrade from 19.6.3 to 19.5.3 RSD Lite or Fastboot

Alright so to start off here's the usual, I'm not responsible if you brick your phone or if your computer starts spitting corrosive acid at you, you know the general anything and everything that can happen on this planet.
So basically I have two files I'm uploading right now. The flash.zip that you have to download and the RSD lite zip that is optional.
You need to download the flash.zip or both and extract them and install RSD. After doing so you'll have to put your phone into fastboot by powering it off and holding the power button and vol - key together until it pops up in AP flash. (YOU DON'T NEED TO DO THIS IF YOUR USING THE LAUNCH.bat)
After all of that you need to plug in your phone to your desktop and assuming you have all the drivers installed you need to either open RSD and select the xml in the folder you extracted from the flash.zip and select your phone and start the flashing process.
Now if your phone is not recognized by RSD you need to run the LAUNCH.bat and it will do the whole process in about 5-15 minutes (rough estimate)
After everything is done your phone will reboot and your on 19.5.3 and can root your phone permanently and gain system r/w permissions with my other thread HERE.
Credits:
Credit for the downgrade through fastboot go to myself and Google for fastboot of course.
Credits for the other stuff in the other thread are in the link up above.
Download Section:
FLASH.zip
RSD 5.7
Is this for unlocked bootloaders only? I just tried it and it keeps failing because I get this:
downgraded security version
update gpt_main version failed
preflash validation failed for GPT
RSD Lite says:
Failed flashing process. 2/17 flash partition "gpt.bin"
Really hope this isn't for unlocked users only cause I just wiped my phone for this to test it and root
Jay_P11 said:
Is this for unlocked bootloaders only? I just tried it and it keeps failing because I get this:
downgraded security version
update gpt_main version failed
preflash validation failed for GPT
RSD Lite says:
Failed flashing process. 2/17 flash partition "gpt.bin"
Really hope this isn't for unlocked users only cause I just wiped my phone for this to test it and root
Click to expand...
Click to collapse
Its for the non-dev Droid Maxx/Droid Ultra's with locked bootloaders. It sounds like your on a os lower than 4.4 or higher than 4.4. Can you give me your system specs? (Android version, System version, and phone model)
TheOriginalist said:
Its for the non-dev Droid Maxx/Droid Ultra's with locked bootloaders. It sounds like your on a os lower than 4.4 or higher than 4.4. Can you give me your system specs? (Android version, System version, and phone model)
Click to expand...
Click to collapse
Android 4.4.4
Build SU4.21
System Version 21.11.21.obake_verizon.Verizon.en.US
The update said it was 19.6.3 when I downloaded it so now I'm really confused
Jay_P11 said:
Android 4.4.4
Build SU4.21
System Version 21.11.21.obake_verizon.Verizon.en.US
The update said it was 19.6.3 when I downloaded it so now I'm really confused
Click to expand...
Click to collapse
Yeah it said that probably from a previous download or something whats important is that you didnt brick your device. Can you boot?
TheOriginalist said:
Yeah it said that probably from a previous download or something whats important is that you didnt brick your device. Can you boot?
Click to expand...
Click to collapse
All is well. I backed up my pics and stuff as I always do before trying something like this, so nothing major was lost. Just gotta re-install all my apps cause google backup somehow chose to not help me in my time of need but I guess the version I came from was what it said was 19.6.3 and I never bothered to double check before trying anything. Man would it be great if this worked on 4.4.4 though. Have you or anyone else tried the root method on 4.4.4? If not (unless you're sure it won't work) I'm willing to try the root process.
Jay_P11 said:
All is well. I backed up my pics and stuff as I always do before trying something like this, so nothing major was lost. Just gotta re-install all my apps cause google backup somehow chose to not help me in my time of need but I guess the version I came from was what it said was 19.6.3 and I never bothered to double check before trying anything. Man would it be great if this worked on 4.4.4 though. Have you or anyone else tried the root method on 4.4.4? If not (unless you're sure it won't work) I'm willing to try the root process.
Click to expand...
Click to collapse
No but I've tried my own exploits on other Android versions like 4.4 and 4.2.2 on this phone. I just wont risk updating to 4.4.4.
Thread is not needed. The simple process would be to simply download the fxz from the reputable sbfdevelopers and flash. Nothing else is needed. Again repost.
Topsnake said:
Thread is not needed. The simple process would be to simply download the fxz from the reputable sbfdevelopers and flash. Nothing else is needed. Again repost.
Click to expand...
Click to collapse
Again I am just trying to simplify things for people. Especially if they have issues with RSD Lite.

[Q] 5.1.1 OTA error on install

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

Stop !!! Do not upgrade to lollipop via twrp !!!

Update : Oct 24, 2015 It looks like the bricking scare is over, and there is an updated guide on how to upgrade to the latest Lollipop without bricking :
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
PUBLIC SERVICE ANNOUNCEMENT :
There are now several reports of super hard bricks (not even Amazon logo shows up) when people attempted to load 5.2.2 version via TWRP.
My best guess is that it has something to do with the 5.x update from Amazon that people request before downgrading to 4.5.3. If Amazon is providing a newer 5.x. update, it can be blocking the older 5.2.2 from working after the downgrade-upgrade procedure. When it bricked before, it would at least show "Amazon" logo, but now even the logo is gone.
One would have to capture this current 5.x update, and see what's in it. It's probably updating another partition out of those that were previously untouched :
http://forum.xda-developers.com/fire...idden-t3122246
All the downgrade-upgrade guides are on hold for now ... You are still safe to exist in the 4.5.x space (with root).
bibikalka said:
One would have to capture this current 5.x update, and see what's in it.
Click to expand...
Click to collapse
I assume I can capture file by reversing rename of DeviceSoftwareOTA.apk but leaving OTA updating blocked. Is that the method?
EDIT: Well, just did rename. No download yet. I've got otaverifier blocked. If nothing soon, I'll enable that and block dcp.
This update was strange and left a very small .data file in cache after saying a download was complete, ready to upgrade. Could not locate a bin file. I will/would try capturing a link via adb logcat.
could be a small update that just preps us to move back to the normal releases.
Just educated guesses.
siegesoldier said:
This update was strange and left a very small .data file in cache after saying a download was complete, ready to upgrade. Could not locate a bin file. I will/would try capturing a link via adb logcat.
could be a small update that just preps us to move back to the normal releases.
Just educated guesses.
Click to expand...
Click to collapse
All that downloaded for me were apk update files, no .data, but device>updates shows:
10.0.42-D-20150925-NA-4 is ready to install
I ran logcat during download and a couple of manual installs (pressing Install button, but I do have updates blocked). I didn't see anything obviously related to update in the logcats, but not sure what to look for. Since I didn't get the .data, will I find anything helpful in logcat? What should I look for? thx
p.s., Or must I unblock updating to capture?
siegesoldier said:
This update was strange and left a very small .data file in cache after saying a download was complete, ready to upgrade. Could not locate a bin file. I will/would try capturing a link via adb logcat.
could be a small update that just preps us to move back to the normal releases.
Just educated guesses.
Click to expand...
Click to collapse
Yep, this is weird. I wonder if one should flash 4.5.3 bootloaders with TWRP in Lollipop first as per this post http://forum.xda-developers.com/showpost.php?p=62011272&postcount=2 , and let it try to upgrade. This way whatever files it downloads, they will be sitting in /cache. But nothing will be run as it is a non-Amazon recovery.
Another poster indicated that the tablet rebooted about 3 times, and then he got new icons and Amazon launcher :
http://forum.xda-developers.com/showpost.php?p=63116048&postcount=141
bibikalka said:
I wonder if one should flash 4.5.3 bootloaders with TWRP in Lollipop first as per this post http://forum.xda-developers.com/showpost.php?p=62011272&postcount=2 , and let it try to upgrade. This way whatever files it downloads, they will be sitting in /cache. But nothing will be run as it is a non-Amazon recovery.
Click to expand...
Click to collapse
I'm more than willing to try to capture this if one of you can tell me how.
I don't quite follow the above. I'm running rooted 5.2.2. So I'd flash bootloaders and TWRP per guide, install OS 4.5.5, boot to OS and try to upgrade? Is this any different from someone already on 4.5.5 trying to upgrade? thx
DoLooper said:
I'm more than willing to try to capture this if one of you can tell me how.
I don't quite follow the above. I'm running rooted 5.2.2. So I'd flash bootloaders and TWRP per guide, install OS 4.5.5, boot to OS and try to upgrade? Is this any different from someone already on 4.5.5 trying to upgrade? thx
Click to expand...
Click to collapse
Not this complicated. I think you could flash 4.5.3 bootloaders + TWRP under 5.2.2, enable OTA updates, and continue working. When it decides to self-reboot (after the update is copied to /cache), it won't find stock 5.2 recovery. Instead, it'll hang (4.5.3 bootloaders cannot boot 5.2.2). At this point you can manually reboot into TWRP, and see what's in /cache. Then you just reapply 5.2.0 bootloaders + 5.2.0 recovery, and boot back into 5.2.2 (and do disable OTA here !!!) Hopefully it does not write into recovery partition before auto-rebooting, so that TWRP survives intact.
bibikalka said:
Not this complicated. I think you could flash 4.5.3 bootloaders + TWRP under 5.2.2, enable OTA updates, and continue working. When it decides to self-reboot (after the update is copied to /cache), it won't find stock 5.2 recovery. Instead, it'll hang (4.5.3 bootloaders cannot boot 5.2.2). At this point you can manually reboot into TWRP, and see what's in /cache. Then you just reapply 5.2.0 bootloaders + 5.2.0 recovery, and boot back into 5.2.2 (and do disable OTA here !!!) Hopefully it does not write into recovery partition before auto-rebooting, so that TWRP survives intact.
Click to expand...
Click to collapse
OK, I'll try this later or tomorrow. Still wonder though, couldn't you--anyone on 4.5.5--leave OTA package blocked but rename OTAsoftware extension back to apk, allowing the update to download but not install?
)':
Hello, I am french sorry for my english
My kindle fire is bricked
how to repair !! :crying::crying:
help me please :/
bibikalka said:
. . . At this point you can manually reboot into TWRP, and see what's in /cache. Then you just reapply 5.2.0 bootloaders + 5.2.0 recovery, and boot back into 5.2.2 (and do disable OTA here !!!) Hopefully it does not write into recovery partition before auto-rebooting, so that TWRP survives intact.
Click to expand...
Click to collapse
@bibikalka OK, ready to do this and (more or less) prepared to get replacement Fire . Just one question: Why do you think there will be anything in cache after the update and reboot attempt? i.e., wouldn't deleting it be part of the update process? Thanks! (Edit: NVM--I see your explanation above.)
EDIT @bibikalka, @everyone Thought the update was out for my region, but guess not: With DeviceSoftareOTA.apk named as originally and otaverifier enabled, Device>Updates just returns "no updates." Disabled otaverifier again and will wait on this.
I believe the update will download with DeviceSoftwareOTA.apk properly named--and hope it won't update with otaverifier disabled. So maybe I can get it. Anyway, I'll check for it over next few days, but maybe someone else will try this method first. (I am west-coast US and it seems always last to get updates.)
DoLooper said:
@bibikalka OK, ready to do this and (more or less) prepared to get replacement Fire . Just one question: Why do you think there will be anything in cache after the update and reboot attempt? i.e., wouldn't deleting it be part of the update process? Thanks!
Click to expand...
Click to collapse
I think it will prepare to update by staging the required files in /cache, but then it'll try to reboot to apply those files (usually updates are applied in recovery ...). So when reboot fails (as it should with TWRP & 4.5.3 bootloaders which don't boot Lollipop), you intercept the stuff in /cache and see what it has.
Added: If this works, do wipe /cache before leaving TWRP (when you restore 5.2 bootloaders). This way it won't pick up the scripts and run them ...
See edit here. Forgot that I'm always last to get an upgrade. Hope someone who might get it sooner will use bibkalka's method so we can get this show back on the road.
After downloading the 5.0.1 update once I have been unable to get it again. My build number has not updated so its possible they pulled it. Root etc still works so it doesn't look like it applied.
Hello, just wanted to say that I can testify to the fact that after updating to 5.2.2, then downgrading and going into TWRP, flashing all the zips, and then wiping cache before rebooting..... gets you a BRICK!! I've stupidly done it.... to my replacement from Amazon! Hopefully sometime in the future someone can get me out of this one....
hello there recently my rooted fire os 5 with xposed playstore just updated to 5.0.1 by it self and i swear i did have com.amazonotaverifier blocked its weird because it updated when i left my fire hd 6 on charge
it just updated itself to fire os 5.0.1 il stay on that fire os because people are saying you get bricked if you do the whole procedure like downgrade back to 4.5.3 and root and get custom recovery and flash all the zips = brick
2nd try to get 5.0.1 update
I didn't capture the update, but maybe learned something about OTA. Two things I hope someone can explain.
First, I've had extension of DeviceSoftwareOTA.apk renamed back to (plain) .apk since last attempt to capture update. Today:
1. "Check for updates" returned: 10.0.43.-D-20151007-NA-5 is ready to install
(last week there was one named: 10.0.42-D-20150925-NA-4)
2. I dd'd the 4.5.3 bootloaders and twrp (with otaverifier blocked)
3. Unblocked otaverifier, but the only thing that downloaded to /cache was "amazonmp3_10004310.apk" (update to mp3 player, i guess).
(last week they were apks for map and photo apps)
4. Hit "check for updates" again, but now it said "none" and /cache was empty.
(same thing last week)
Does anyone know about updates named like "10.0.43.-D-20151007-NA-5?" I've only seen them since I "corrected" the deviceSoftwareOTA.apk extension, and only apk files get downloaded. A couple logcats I got, however, have many more update entries than I've seen before, but I don't understand logcats very well. If someone who knows logcats could have a look, I'd appreciate it. Just tell me where to post. I think it would help us to know if these updates do more than update the accompanying apks.
------------------------
EDIT: NVM below! I'm getting # prompt because I recently set "adbd insecure" app to start at boot <doh> .
Second, I decided to start over and see if there was a different update waiting. So:
1. Went to twrp and flashed 5.2.0_stock_recovery_uboot.zip (for 5.0 stock recovery and bootloaders, i hope), wiped cache, and booted to OS.
2. Got l o o o n g startup. When OS finally loaded, "adb shell" hung CMD. I had to run TASKKILL /F /IM adb* >nul 2>&1 before adb shell was recognized. And when it was, it consistently returned # prompt: ([email protected]:/ #)
I'm definitely rooted, all google works, version still shows 5.0.0, build date July 20, but even after rebooting both tablet and computer, "adb shell" still always returns # prompt.
Can anyone tell me what's going on here? (Sorry this is tldr; hope a few of you slog through.) Thanks.
EDIT: it's late, maybe I'm nuts, but seems "adb shell" should return $ prompt, then "su" returns #.
DoLooper said:
I didn't capture the update, but maybe learned something about OTA. Two things I hope someone can explain.
First, I've had extension of DeviceSoftwareOTA.apk renamed back to (plain) .apk since last attempt to capture update. Today:
1. "Check for updates" returned: 10.0.43.-D-20151007-NA-5 is ready to install
(last week there was one named: 10.0.42-D-20150925-NA-4)
2. I dd'd the 4.5.3 bootloaders and twrp (with otaverifier blocked)
3. Unblocked otaverifier, but the only thing that downloaded to /cache was "amazonmp3_10004310.apk" (update to mp3 player, i guess).
(last week they were apks for map and photo apps)
4. Hit "check for updates" again, but now it said "none" and /cache was empty.
(same thing last week)
Does anyone know about updates named like "10.0.43.-D-20151007-NA-5?" I've only seen them since I "corrected" the deviceSoftwareOTA.apk extension, and only apk files get downloaded. A couple logcats I got, however, have many more update entries than I've seen before, but I don't understand logcats very well. If someone who knows logcats could have a look, I'd appreciate it. Just tell me where to post. I think it would help us to know if these updates do more than update the accompanying apks.
.
Click to expand...
Click to collapse
These updates appear to be just individual apps, nothing to do with the system. You can google the version numbers, and it'll find that stuff.
The only hope is to checksum all partitions, and find the one that was updated in the latest version 5, but otherwise does not change in earlier versions. One could right a script for that. Then we could overwrite it.
But I suspect the new update may have written into one of the partitions that have other stuff, so the checksum identification won't help.
bibikalka said:
The only hope is to checksum all partitions, and find the one that was updated in the latest version 5, but otherwise does not change in earlier versions. One could right a script for that. Then we could overwrite it.
But I suspect the new update may have written into one of the partitions that have other stuff, so the checksum identification won't help.
Click to expand...
Click to collapse
Would that mean 5.0.1 would not be rootable?
Hello, I am curious, would it be possible to use "fastboot boot recovery.img" instead of actually flashing it in order to get root in the new 5.2.2 (build date sep 23)? It seems this would solve the hard brick problem with flashing twrp.
I'm on a never-rooted 2014 HD6 with gapps & OS 5.2.2. Very interested in rooting this tablet.
hi,
my Eng is not good, i don't understand the title
Stop !!! Do not upgrade to lollipop via twrp !!!
on today i'm receive Fire HD 7 from my phone provider. This is free.
i was rooted it with kingroot. It was succesfull. But i want setup it with android with vietnames because my boy are 10 age.
it run fire os 4.5.3 now.
can i upgrade to android 5.x?
thank for read

[How-To] Applying Monthly Security Patches if you're Rooted (Magisk)

So, since once a month I find myself having to click a bunch of links and read how to do a bunch of commands, I wanted to create a thread that (rather generically) explains how to manually flash the OTA monthly updates if you're rooted with Magisk. So, minimally, here's a thread for me to review every month... if it helps you all out, all the better!
Pre-requisites:
Download Latest OTA zip file from Google.
Obtain the STOCK boot.img (required) and dtbo.img (optional) of the System ROM you are currently running. This can be done if you already have the full System Image file downloaded, downloading it currently, or just obtaining the stock boot and dtbo image files elsewhere. (NOTE: This can be skipped if you successfully uninstall Magisk BEFORE you start the process and choose to restore the Stock images in the uninstall process.)
Download Latest Magisk Zip file
Download latest TWRP recovery image
If applicable, have latest USB drivers, adb/fastboot/ files etc.
Preparation:
1) Extract or open the Full Image file and locate the boot.img and dtbo.img files. You will want these on your PC in the platform-tools folder (I usually put the Month name at the beginning, ex. - Jan_boot.img). Again, you can skip if you successfully uninstall Magisk prior to all of this.
2) Copy your OTA zip file to the platform-tools folder, again naming it after the month helps (ex. - Feb_Pixel2XL_OTA.zip)
3) Put your TWRP recovery in platform-tools folder.
4) Place the latest Magisk zip on your Pixel's internal storage (what used to be the SDCard on phones so equipped).
Commands:
1) From PC, open command prompt and change directory to your platform-tools folder.
2) If your phone is on, "adb reboot bootloader" If powered off, press power and Vol Down button to get to Bootloader. Plug your phone into your PC.
3) [If Magisk is not uninstalled first] Command: fastboot flash boot {Name_of_boot.img File}
4) [If Magisk is not uninstalled first] Command: fastboot flash dtbo {Name_of_dtbo.img File}
5) On your phone, hit Vol Down until you see Recovery, then press power button.
6) Once in recovery mode, press power and Vol Up to bring up menu
7) Scroll to item: "Apply update from ADB" and press power
8) Command: adb sideload {Name_of_OTA.zip file}
9) After the OTA finishes flashing, exit recovery back into the Bootloader
10) Command: fastboot boot {twrp_filename.img}
11) Install Magisk Zip file (and any other Zip files you want installed... Kernels, etc.) within TWRP
Then after flashing your zip files, reboot to system and you should be all set.
I believe everything above is correct, but if I've made a glaring mistake, please let me know. I also realize there may be other methods to this madness, but this is what works for me.
With this method do you have to worry about removing your password from your phone before you try to go into twrp?
uofirob said:
With this method do you have to worry about removing your password from your phone before you try to go into twrp?
Click to expand...
Click to collapse
Yes. Mine is set to pin, which I had to put in and it let me finish.
Sweet. I'll give this method a try tonight!
WorldOfJohnboy said:
Yes. Mine is set to pin, which I had to put in and it let me finish.
Click to expand...
Click to collapse
Thank you for this. Just to be clear in step 2 under prerequisites you say more on this later. Then in step 1 for preparation you prefix your boot and dtbo with Jan xx.img. I get what your saying, but for the newer noobs they may get confused. Maybe reword to say, extract or open the factory image your currently using or the previous months image. Obviously you do this first so that you can sideload the ota. I don't mean any disrespect.
I believe you also need remove the -w from the end of the .bat file after you extract the OTA; otherwise, all of your data will be wiped.
But great job of getting all this info in one place!
So I did this, and now I'm bootlooping. I guess I'll re-flash the Jan factory image and wait a little longer... **UPDATE** I fixed the bootloop by re-trying the process again (after re-verifying the MD5 hash on the update.zip. I rebooted after installing the update,
but before the TWRP flash to install MAGISK. Maybe this allowed the "update"
to finish processing. I also had to remove the pin from my lock screen in order to allow me to get into twrp. After rebooting into the system and removing the pin, I adb reboot bootloader and then flashed twrp. Thanks for the guide!
---------- Post added at 07:58 AM ---------- Previous post was at 07:50 AM ----------
PuffDaddy_d said:
I believe you also need remove the -w from the end of the .bat file after you extract the OTA; otherwise, all of your data will be wiped.
But great job of getting all this info in one place!
Click to expand...
Click to collapse
You don't need to remove the -w from the .bat file since you aren't using it at all to do the update. That is only if you're flashing your factory image.
Fe Mike said:
Thank you for this. Just to be clear in step 2 under prerequisites you say more on this later. Then in step 1 for preparation you prefix your boot and dtbo with Jan xx.img. I get what your saying, but for the newer noobs they may get confused. Maybe reword to say, extract or open the factory image your currently using or the previous months image. Obviously you do this first so that you can sideload the ota. I don't mean any disrespect.
Click to expand...
Click to collapse
I changed some wording under prerequisite...
I agree with everything on this guide...
just teasing...
I'm actually glad you created this thread...I wanted to create one also and try and help out as much as I could, but I don't have the cahones and didn' t think I had experience enough to start a "guide" thread :silly:
I mean no disrespect, but this seems awful complicated compared to just flashing the full image with the removed (-w). Especially since your downloading it anyway. I do that then boot the TWRP image and flash the TWRP zip. Reboot into recovery and flash kernel and magisk and reboot system. Again I'm asking for clarity, not dumping on you. Great write up btw!
CyberpodS2 said:
I mean no disrespect, but this seems awful complicated compared to just flashing the full image with the removed (-w). Especially since your downloading it anyway. I do that then boot the TWRP image and flash the TWRP zip. Reboot into recovery and flash kernel and magisk and reboot system. Again I'm asking for clarity, not dumping on you. Great write up btw!
Click to expand...
Click to collapse
Well...I can't speak for the OP, but I wrote my extremely similar identical one because, for whatever reason, many users would choose OTAs over flashing full factory images. I/me & you understand the benefits of the factory images over the OTAs; especially understanding the process you must go through to install the OTAs as-of-current is almost the same as flashing the factory images anyways...
But if I were to give a possible explanation to their reasoning is that, like many of them, I come from a non-Google phone (S5 for me), and OTA's were simpler, takes less bandwidth (which still remains true today), they were significantly simpler to install vs. factory images, and with a lot of popular phones you only flash factory images to recover your phone; i.e. muniz_ri's OTA's for the S5 and FlashFire were loads simpler than flashing a whole factory image. But, again, understanding the difference for Pixel 2 and Oreo's OTA & factory images (or the small difference thereof), it's probably better to do a few extra steps and/or downloads to do the whole image than sideloading an OTA.
In the end, this is for people who insist for OTA updates most likely because that's how they are familiar (and therefore more comfortable) with; whether it being explained to them or not...
Cheers!:good:
Fair enough, thanks for the input!
CyberpodS2 said:
I mean no disrespect, but this seems awful complicated compared to just flashing the full image with the removed (-w). Especially since your downloading it anyway. I do that then boot the TWRP image and flash the TWRP zip. Reboot into recovery and flash kernel and magisk and reboot system. Again I'm asking for clarity, not dumping on you. Great write up btw!
Click to expand...
Click to collapse
It may seem awful complicated, but to be honest, to me is less complicated than having to edit a script file (which if you forget to do, will lose all of your data). Also, though the steps I wrote out seem like a lot more if you were to write out a process using the full image, it actually works out to be almost the same number of steps.
Lastly, as someone else hinted at, the OTA file size is smaller. The only full image you need is what you are currently running (which in most cases I have on my phone in case the sh__ hits the fan with my phone), not the new full image. (To be even more precise, you only need the boot.img and dtbo.img from the full image file--there may be places to get just those two files out there.)
As I put in the last sentence, I realize there are other methods to this madness, this is basically what works for me. I wanted to get it in writing so I wouldn't forget this down the road, and if it helps anyone here, just icing on the cake. Clearly I'm no Dev and not forcing anyone to perform the updates this way!
WorldOfJohnboy said:
It may seem awful complicated, but to be honest, to me is less complicated than having to edit a script file (which if you forget to do, will lose all of your data). Also, though the steps I wrote out seem like a lot more if you were to write out a process using the full image, it actually works out to be almost the same number of steps.
Lastly, as someone else hinted at, the OTA file size is smaller. The only full image you need is what you are currently running (which in most cases I have on my phone in case the sh__ hits the fan with my phone), not the new full image. (To be even more precise, you only need the boot.img and dtbo.img from the full image file--there may be places to get just those two files out there.)
As I put in the last sentence, I realize there are other methods to this madness, this is basically what works for me. I wanted to get it in writing so I wouldn't forget this down the road, and if it helps anyone here, just icing on the cake. Clearly I'm no Dev and not forcing anyone to perform the updates this way!
Click to expand...
Click to collapse
Hey bud, wonder I I could pick your brain just a little. When doing monthly Google updates, are most of their proprietary files located in the boot, dtbo, and vendor images?? Your posts have intrigued me a little, and are very well written BTW. My reasoning is this. On my old 6p, about all we needed to do was flash the new vendor, and of course the bootloader and radio if there were any worthwhile improvements. Would the same possibly apply to the P2XL?? I'm just wondering because, now that we're starting to see custom roms, if this would be a viable option, and simplify the updating process. Thank again for your great write up ??
Badger50 said:
Hey bud, wonder I I could pick your brain just a little. When doing monthly Google updates, are most of their proprietary files located in the boot, dtbo, and vendor images?? Your posts have intrigued me a little, and are very well written BTW. My reasoning is this. On my old 6p, about all we needed to do was flash the new vendor, and of course the bootloader and radio if there were any worthwhile improvements. Would the same possibly apply to the P2XL?? I'm just wondering because, now that we're starting to see custom roms, if this would be a viable option, and simplify the updating process. Thank again for your great write up
Click to expand...
Click to collapse
I'll be perfectly honest with you, I haven't taken a dive to see what is in the OTA files and would imagine that it varies depending on the monthly updates.... that said, the only reason why I have stated to re-flash the stock boot.img is because if you are rooted with Magisk, it takes the stock boot.img and modifies it. In order to take an OTA sideload, you need to be on stock boot.img and stock recovery. dtbo is only in my process because there was one time when I tried to sideload and my dtbo wasn't stock (or corrupt). You may not need to flash the stock dtbo.img, but it doesn't hurt to do so.
WorldOfJohnboy said:
I'll be perfectly honest with you, I haven't taken a dive to see what is in the OTA files and would imagine that it varies depending on the monthly updates.... that said, the only reason why I have stated to re-flash the stock boot.img is because if you are rooted with Magisk, it takes the stock boot.img and modifies it. In order to take an OTA sideload, you need to be on stock boot.img and stock recovery. dtbo is only in my process because there was one time when I tried to sideload and my dtbo wasn't stock (or corrupt). You may not need to flash the stock dtbo.img, but it doesn't hurt to do so.
Click to expand...
Click to collapse
I'm really happy to see our device has graduated to this level of discussion, instead of the random guessing and 14 different "possible" routes to a solution. Lol
Custom roms abound, once TWRP gets squared away and someone master's the art of turning monthly updates into zip installs we'll pretty much be there!
Btw OP, great write up... Clear and precise!
I do not understand the purpose for downloading the full system image and then flashing only the OTA zip - what am I missing? There is a widely distributed method for performing monthly OTA updates by uninstalling Magisk, updating OTA normally, then flashing Magisk again - seems much simpler, any reason why it would not work?
Brenneke said:
I do not understand the purpose for downloading the full system image and then flashing only the OTA zip - what am I missing? There is a widely distributed method for performing monthly OTA updates by uninstalling Magisk, updating OTA normally, then flashing Magisk again - seems much simpler, any reason why it would not work?
Click to expand...
Click to collapse
Downloading the full system image is not required. You only need the Stock versions of boot.img (required) and dtbo.img (optional) of the ROM version your phone is currently running. I actually keep a full system image on my phone in case something goes awry.
I'm going to update the OP to more clearly state that you only need the stock boot.img file--how you obtain it is up to you. Uninstalling Magisk will do the same exact thing, however I tried to do that a couple of months ago and it created more issues for me than if I had just flashed the stock boot.img in the first place.
WorldOfJohnboy said:
Downloading the full system image is not required. You only need the Stock versions of boot.img (required) and dtbo.img (optional) of the ROM version your phone is currently running. I actually keep a full system image on my phone in case something goes awry.
I'm going to update the OP to more clearly state that you only need the stock boot.img file--how you obtain it is up to you. Uninstalling Magisk will do the same exact thing, however I tried to do that a couple of months ago and it created more issues for me than if I had just flashed the stock boot.img in the first place.
Click to expand...
Click to collapse
I have not tried the uninstall Magisk method but plan to do so at next update. What kind of issues did it create for you?
Thanks.
Brenneke said:
I have not tried the uninstall Magisk method but plan to do so at next update. What kind of issues did it create for you?
Thanks.
Click to expand...
Click to collapse
For some reason, I don't think it restored the correct (or not corrupted) boot.img version. Then, there were remnants of the Magisk APK and other files so I ended up having to do a full TiBu of my apps and flashed (with wipe) a full System image. It may have been something I did or just my bad luck, but I prefer not to chance it and instead manually flash the Stock image as my "guide" here states.

Categories

Resources