[Q]OTA KitKat Update Failed, won't complete boot process now. - Nexus 10 Q&A, Help & Troubleshooting

Tried to update my wife's Nexus 10 tonight. It's unlocked and rooted, formerly on the stock version of Jelly Bean. I thought this would be an easy update since it was stock jellybean to kitkat with the official OTA file but I guess I was wrong. Got the OTA update notification so I allowed it to reboot and install. CWM Touch Recovery picked it up and I told it to install the unsigned zip. Got near the end and it had an error. Now it's stuck in boot (appears to be Kit Kat boot). Just sits on the 4 colored circles going in/out in the middle of the screen.
I need to fix this without wiping data. It's her only computer that she uses daily so she's got a million things on there she uses all the time. If I have to wipe data, she'll be pissed (and I'll lose my hard earned game saves).
Attached is a picture of the error. I've got WUG's toolkit if it's necessary to use to fix this. Any ideas what's going on and how to fix it? Thanks.

Stinger2300 said:
Tried to update my wife's Nexus 10 tonight. It's unlocked and rooted, formerly on the stock version of Jelly Bean. I thought this would be an easy update since it was stock jellybean to kitkat with the official OTA file but I guess I was wrong. Got the OTA update notification so I allowed it to reboot and install. CWM Touch Recovery picked it up and I told it to install the unsigned zip. Got near the end and it had an error. Now it's stuck in boot (appears to be Kit Kat boot). Just sits on the 4 colored circles going in/out in the middle of the screen.
I need to fix this without wiping data. It's her only computer that she uses daily so she's got a million things on there she uses all the time. If I have to wipe data, she'll be pissed (and I'll lose my hard earned game saves).
Attached is a picture of the error. I've got WUG's toolkit if it's necessary to use to fix this. Any ideas what's going on and how to fix it? Thanks.
Click to expand...
Click to collapse
I have a rooted/unlocked Nexus 10, I used wugfresh's kit also. I got the OTA update last night. it installed. CWM never came up or did anything. During one of the boots after the green droid bot was saying "installing" the boot finished, but my green bot is now on his side. stomach open and it says "Error" in red bold letter.
I had to go to work, so I couldnt trouble shoot, but power off/on and soft reset (power+volume up select reset) didnt help. always comes to that "error".
I have data that is also not currently backed up with TBpro. hindsight I should have made sure I turned the scheduler on.
So I'm stuck also. not sure how to proceed. Got one recommendation to flash stock back on. But I think that will for sure wipe all my data. And beyond that, I dont know how, unless WUGs kit will do that.

Your best bet it is to sideload. Grab the OTA and the FULL 4.4
Pull the recovery.img from the full 4.4 rar (its in the zip), fastboot flash it, reboot into bootloader, go to recovery and sideload the OTA and that should restore it just fine
EDIT: http://forum.xda-developers.com/showpost.php?p=47656450&postcount=8
my detailed instructions there for sideloading

planet_x69 said:
Your best bet it is to sideload. Grab the OTA and the FULL 4.4
Pull the recovery.img from the full 4.4 rar (its in the zip), fastboot flash it, reboot into bootloader, go to recovery and sideload the OTA and that should restore it just fine
EDIT: http://forum.xda-developers.com/showpost.php?p=47656450&postcount=8
my detailed instructions there for sideloading
Click to expand...
Click to collapse
I was about to say. whaaaaat? then saw the link with some details. Never done that stuff before, just used other tools kits, like wugs. But doesnt sound to bad. Will try when I get home. I presume when you say into a adb directory, its something on the desktop pc you are connected to. outside of perhaps some drivers, do I need other applications on the PC to facilitate the adb stuff you mention?

jetguat said:
I was about to say. whaaaaat? then saw the link with some details. Never done that stuff before, just used other tools kits, like wugs. But doesnt sound to bad. Will try when I get home. I presume when you say into a adb directory, its something on the desktop pc you are connected to. outside of perhaps some drivers, do I need other applications on the PC to facilitate the adb stuff you mention?
Click to expand...
Click to collapse
Well if you are unfamiliar with the process you will need to get the android SDK installed or find one of the pre-packaged current adb loads. It's very simple, get this package here: http://downloadandroidrom.com/file/Nexus10/Nexus10RootNew.zip# (yes its a crappy ad link but hey the guy packaged it all up so...).
If you are on a PC extract these to a folder of your choice.
Open file manager
Navigage to the folder you extracted the files to
on the left pan select the folder, press SHIFT and Right Click mouse, then select "Open command window here"
You can now follow my instructions from the other page - Do the following below FIRST
If you are prompted to accept security allowance on your device do so. you will likely only see this once you are back into the Android OS not in recovery.
This folder has all the basics you need to fastboot and run adb.
Connect your device to your pc and run >fastboot reboot-bootloader.
If your device restarts and goes into the bootloader you can relax and follow my instructions.
Hope this helps.
One other thing, that su zip is dated, you will need to flash the 1.51 version and you should be good to complete root process.

Wow, this seems about 3 miles over my head but I guess I'll dive in and try it. Thanks for the info. I'm sure I'll be back with problems/questions.

planet_x69 said:
Well if you are unfamiliar with the process you will need to get the android SDK installed or find one of the pre-packaged current adb loads. It's very simple, get this package here: http://downloadandroidrom.com/file/Nexus10/Nexus10RootNew.zip# (yes its a crappy ad link but hey the guy packaged it all up so...).
If you are on a PC extract these to a folder of your choice.
Open file manager
Navigage to the folder you extracted the files to
on the left pan select the folder, press SHIFT and Right Click mouse, then select "Open command window here"
You can now follow my instructions from the other page - Do the following below FIRST
If you are prompted to accept security allowance on your device do so. you will likely only see this once you are back into the Android OS not in recovery.
This folder has all the basics you need to fastboot and run adb.
Connect your device to your pc and run >fastboot reboot-bootloader.
If your device restarts and goes into the bootloader you can relax and follow my instructions.
Hope this helps.
One other thing, that su zip is dated, you will need to flash the 1.51 version and you should be good to complete root process.
Click to expand...
Click to collapse
OK, I downloaded the packaged linked above and extracted it to the desktop. Then I used file manager to "open command window here". Where do I get su zip 1.51? I tried to google a link but they all seemed newer (1.75 for example). Does it matter if it's 1.51 exactly or can it be any version 1.51 or newer? One last question regarding su zip, does that need to be updated after this whole process is complete and I'm up and running again, or does it need to be done before I move on to the instructions you linked to above? Thanks.

Stinger2300 said:
OK, I downloaded the packaged linked above and extracted it to the desktop. Then I used file manager to "open command window here". Where do I get su zip 1.51? I tried to google a link but they all seemed newer (1.75 for example). Does it matter if it's 1.51 exactly or can it be any version 1.51 or newer? One last question regarding su zip, does that need to be updated after this whole process is complete and I'm up and running again, or does it need to be done before I move on to the instructions you linked to above? Thanks.
Click to expand...
Click to collapse
You don't need to root at all but the updated supersu 1.75 will be just fine as its universal. You can get the official from here: http://download.chainfire.eu/368/SuperSU/UPDATE-SuperSU-v1.75.zip
You will install that ONLY after you have installed the OTA's and your custom recovery and only if you want root.
good luck!

planet_x69 said:
Your best bet it is to sideload. Grab the OTA and the FULL 4.4
Pull the recovery.img from the full 4.4 rar (its in the zip), fastboot flash it, reboot into bootloader, go to recovery and sideload the OTA and that should restore it just fine
EDIT: http://forum.xda-developers.com/showpost.php?p=47656450&postcount=8
my detailed instructions there for sideloading
Click to expand...
Click to collapse
In this link, you said to do the following:
Pull the full stock 4.4 image from here : https://developers.google.com/androi...mages#mantaray
open it and pull out from the zip in the rar the recovery.img, move a copy to your adb folder along with a copy of your custom recovery ( for discussion sake I'll use twrp.recovery.img)
Put copy of the patch in the adb folder and rename it to a short name like krt16s.zip
I got the full stock 4.4 image downloaded, extracted it, extracted the zip file inside (image-mantaray-krt16s.zip) and that provided me with "recovery.img" you mentioned above.
Now I have 2 problems, where is this "adb folder" you say to put the recovery.img in, and where is the custom recovery? I assume it's on the N10 after I connect it to my laptop. Is there a preferred custom recovery I should use? I saw mention of TWRP not working with Kit Kat elsewhere. Not sure if that is dated info or not.
Lastly, just to confirm this is true, none of this whole process will wipe my data correct?

planet_x69 said:
You don't need to root at all but the updated supersu 1.75 will be just fine as its universal. You can get the official from here: http://download.chainfire.eu/368/SuperSU/UPDATE-SuperSU-v1.75.zip
You will install that ONLY after you have installed the OTA's and your custom recovery and only if you want root.
good luck!
Click to expand...
Click to collapse
OK, downloaded that and will hold it for later. Hopefully after the questions I just asked are answered, I'll have enough info to proceed. Thanks for the help so far.

Stinger2300 said:
In this link, you said to do the following:
Pull the full stock 4.4 image from here : https://developers.google.com/androi...mages#mantaray
open it and pull out from the zip in the rar the recovery.img, move a copy to your adb folder along with a copy of your custom recovery ( for discussion sake I'll use twrp.recovery.img)
Put copy of the patch in the adb folder and rename it to a short name like krt16s.zip
I got the full stock 4.4 image downloaded, extracted it, extracted the zip file inside (image-mantaray-krt16s.zip) and that provided me with "recovery.img" you mentioned above.
Now I have 2 problems, where is this "adb folder" you say to put the recovery.img in, and where is the custom recovery? I assume it's on the N10 after I connect it to my laptop. Is there a preferred custom recovery I should use? I saw mention of TWRP not working with Kit Kat elsewhere. Not sure if that is dated info or not.
Lastly, just to confirm this is true, none of this whole process will wipe my data correct?
Click to expand...
Click to collapse
Correct - if you SIDELOAD the OTA it will UPGRADE and retain all data and application settings etc...
If you run the 4.4 update from the factory image it will WIPE ALL. So do not do that ....just pull the recover.img from it and get rid of the rest.
If you downloaded this: http://downloadandroidrom.com/file/N...10RootNew.zip#
and extracted it to a new folder - do this first!!!
then copy the recovery.img you just extracted from the factory 4.4 rar to the same folder as the adb and fastboot commands
copy the OTA file to same folder and rename it ota.zip to make your life easier
>fastboot reboot-bootloader to validate your computer can see the device and that the next steps will go as planned
If you are now back bootloader then:
>fastboot flash recovery recover.img
wait till its done..will take about 15 seconds tops
>fastboot reboot-bootloader again and go to recovery using the volume buttons
select and enter recovery mode
wait for dead droid to appear
press both Volume UP and Power at same time and you should get the load menu
select "apply updated from adb" and press power after selecting
orange colored type will now appear at the bottom of the screen
on your PC
>adb sideload ota.zip
wait till you see its completed successfully
then reboot
(you can also apply the smaller ota (1.7MB) this same way)
If all went well you have now booted up successfully and see that your ass has been saved from eternal hell from your wife's wrath...
reboot and fastboot flash your favorite custom recovery reboot again to recovery and apply the su update for root access
I hope this helps
You can also read this: http://www.androidpolice.com/2013/1...-download-and-install-android-4-4-now-krt16o/

You said: "just pull the recover.img from it and get rid of the rest."
So is your instruction from the original link to: "Put copy of the patch in the adb folder and rename it to a short name like krt16s.zip" replaced by the OTA file I renamed to ota.zip in order to retain all data? For reference, krt16s.zip is 390mb, ota.zip is 225mb.

Stinger2300 said:
You said: "just pull the recover.img from it and get rid of the rest."
So is your instruction from the original link to: "Put copy of the patch in the adb folder and rename it to a short name like krt16s.zip" replaced by the OTA file I renamed to ota.zip in order to retain all data? For reference, krt16s.zip is 390mb, ota.zip is 225mb.
Click to expand...
Click to collapse
not sure i follow you but from the 4.4 factory image you will need the recovery.img file thats it. You will also need the OTA upgrade that takes you from 4.3 to 4.4. You need the OTA so that you wont lose your wifes data and will upgrade only and not image the device.
I have to leave and wont be back on till later this weekend.

Going well so far...had an issue but figured it out.

Got to sideloading ota.zip, then after it got to 100% it started verifying the update package. Got an error:
'/system/app/BasicDreams.apk" has unexpected contents
E:Error in /tmp/update.zip
(status 7)
Installation aborted.
Now what?
I found this in the Nexus 7 section but not sure if it applies here or if there is a better way, if it's guaranteed to not wipe data, etc.: http://forum.xda-developers.com/showpost.php?p=47474021&postcount=26

Did you try this solution? I'm stuck on the "Error in /tmp/update.zip" as well. Having the same issues, and I hope to update without loosing data.

No, I haven't tried it as I can't risk losing data by randomly trying stuff I don't understand. I need someone who knows what they are doing to confirm that the steps in this link http://forum.xda-developers.com/showpost.php?p=47474021&postcount=26 won't wipe data or do anything that will require wiping data to finish this process.

have well
Stinger2300 said:
No, I haven't tried it as I can't risk losing data by randomly trying stuff I don't understand. I need someone who knows what they are doing to confirm that the steps in this link http://forum.xda-developers.com/showpost.php?p=47474021&postcount=26 won't wipe data or do anything that will require wiping data to finish this process.
Click to expand...
Click to collapse
I just tried it. And it worked. Didn't loose any data.
Flashing the img files, and then proceeding to sideload the OTA zip. Booting didn't take too long, Android then started upgrading ("Optimizing app..."), and booted successfully. It took a while to open de app drawer though... But everything was still there.
Regaining root access is something I'll try later. I'm just happy to have my N7 booting again.
Just a small disclaimer. I don't really know what I'm doing (I kinda like messing around with my device, it's only way to learn something), so I cannot guarantee it will work for you.

Glad it worked for you, it didn't work for me. I got another error after doing the following commands:
Then, run the following commands:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase system
fastboot flash system system.img
then I rebooted back to bootloader, then "apply updated from adb" and then from the command line: >adb sideload ota.zip
It again loaded 100% and then started verifying the package. Then I got this error:
Package expects build fingerprint of google/mantaray/manta:4.3/JWR66Y/776638:user/release-keys or google/mantaray/manta:4.4/KRT160/907817:user/release-keys; this device has google/mantaray/manta:4.4/KRT16S/920375:user/release-keys.
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
What a F***ing nightmare...
Why do I apparently have the wrong version?

Hmm, might be the wrong OTA zip idd...
I downloaded mine from here: http://www.droid-life.com/2013/11/2...ial-update-for-nexus-7-2012-and-nexus-7-2013/

Related

4.4.2 (KOT49H) update fails on rooted device

Received the update today but it failed to install. I'm running the stock rom KRT16S. My Nexus 10 is rooted and my recovery is TWRP 2.6.3.1. I have added nothing else to this rom except a few apps from the google play store. I wanted to try again but couldn't find where the OTA is stored. It wasn't in the /cache/fota folder. So I downloaded a flashable zip from the net. But this update file failed to install also. I've seen a few others have success installing the update. I just don't know what's preventing me from updating. I welcome your suggestions. Thanks.
Same here on my Nex5.
It seems, that some custom zips changed my stock (rooted) rom in this way that I am not able to install the 4.4.2 update.
I got similar issue on my Nex4 in the past, I could help me out by flashing full rom (rooted) deodexed, but where can I find the full rom of 4.4.2 for my Nex5 now?
Anybody can give me a clue?
Thank u very much.
Greetz from Germany.. Fred
Lexus One said:
Received the update today but it failed to install. I'm running the stock rom KRT16S. My Nexus 10 is rooted and my recovery is TWRP 2.6.3.1. I have added nothing else to this rom except a few apps from the google play store. I wanted to try again but couldn't find where the OTA is stored. It wasn't in the /cache/fota folder. So I downloaded a flashable zip from the net. But this update file failed to install also. I've seen a few others have success installing the update. I just don't know what's preventing me from updating. I welcome your suggestions. Thanks.
Click to expand...
Click to collapse
amplifier1980 said:
Same here on my Nex5.
It seems, that some custom zips changed my stock (rooted) rom in this way that I am not able to install the 4.4.2 update.
I got similar issue on my Nex4 in the past, I could help me out by flashing full rom (rooted) deodexed, but where can I find the full rom of 4.4.2 for my Nex5 now?
Anybody can give me a clue?
Thank u very much.
Greetz from Germany.. Fred
Click to expand...
Click to collapse
Hi Fred, and greetz from Ohio. I'm not aware of anything in the 4.4.2 flavor right now for the Nex10. I'm not sure about the Nex5. I think we're just going to have to wait. But I'd like to have the same thing. A lean & clean deodexed stock rooted 4.4.2 rom with a few performance tweaks. Like the old "Cleanrom" by scrosler. As for right now, did you try an ADB Sideload update to 4.4.2 using Wug's Toolkit? http://www.wugfresh.com/faqs/how-to-update-ota-not-working/
Lexus One said:
Hi Fred, and greetz from Ohio. I'm not aware of anything in the 4.4.2 flavor right now for the Nex10. I'm not sure about the Nex5. I think we're just going to have to wait. But I'd like to have the same thing. A lean & clean deodexed stock rooted 4.4.2 rom with a few performance tweaks. Like the old "Cleanrom" by scrosler. As for right now, did you try an ADB Sideload update to 4.4.2 using Wug's Toolkit?
Click to expand...
Click to collapse
Hi. Meanwhile i found a thread in nexus5 Android development area which contains both deodexed and odexed stock rooted full rom . so i just flashed odexed Version over my 4.4... Now i am on 4.4.2 finally... And still rooted..
Thank u anyway..
Greetz, fred
Lexus One said:
Received the update today but it failed to install. I'm running the stock rom KRT16S. My Nexus 10 is rooted and my recovery is TWRP 2.6.3.1. I have added nothing else to this rom except a few apps from the google play store. I wanted to try again but couldn't find where the OTA is stored. It wasn't in the /cache/fota folder. So I downloaded a flashable zip from the net. But this update file failed to install also. I've seen a few others have success installing the update. I just don't know what's preventing me from updating. I welcome your suggestions. Thanks.
Click to expand...
Click to collapse
Hi,
You can try performing a full unroot in the SuperSU app if it still doesn't work... I had to adb sideload mine to work, don't know how it works with toolkit, but you have to first set your tablet to receive it. As you are on TWRP you simply go to advanced and select adb sideload, then try using the tool, or following the instructions on it to do so .
You cannot install a OTA zip like a Custom ROM zip, they are a little bit different hehe.
Hope this helps,
~Lord
PS.: This will work for N5 too.
I somehow got the idea that rooted Nexus devices with a custom recovery could handle OTA's without trashing the recovery. I guess I expected that I would lose root. I think I'm just going to wait for someone to put together a "CleanROM" based on 4.4.2 or newer. I've been waiting for a rom like this since I bought my Nex10 anyway. I don't think I'll suffer too much running on 4.4 until then.
Thanks to those who contributed, I'll remember your suggestions. Especially if I end up waiting a long time for a 4.4.2 based Cleanrom.
Update: Thanks to Wug's toolkit. I'm now running 4.4.2..
I should ask for a sticky for this but these instruction will work EVERY TIME if you are running either custom recovery or Root.
You will need the latest adb/fastboot from google, you can either install the SDK or download any of the many smaller adb/fastboot and libs for your os
You will need STOCK 4.4/4.3/4.2 recovery depending on what version of android you are currently on. Download the factory image from here. Open the zip within the package and pull out recovery.img and rename it stockrecovery.img
Copy your custom recovery to the adb folder name it twrp.zip or short name for whatever you are using I am using twrp.
You will need the correct OTA you are seeking to apply - rename it to something short simple and obvious - for this example I will use otaupdate.zip
If you wish to root get the latest patch (I believe its up to 1.75 now) and copy it to the adb/fastboot folder.
BACKUP YOUR DEVICE FIRST AND COPY IT TO YOUR PC
If you are already Rooted:
If you are using SuperSU - go to the application options and completely unroot and reboot if needed
BACKUP YOUR DEVICE FIRST AND COPY IT TO YOUR PC
If not rooted start here:
I am assuming most of you are Windows users. Open your file explorer and open the ADB folder.
On the left hand folder where ADB is located press shift and right click the ADB folder and select "Open command window from here". This will open a command prompt window for you to run all your adb/fastboot commands from. This is the same folder where you copied your recoveries and updates to.
BACKUP YOUR DEVICE FIRST AND COPY IT TO YOUR PC
Copy your custom recovery and stock recovery to your adb folder
Copy and rename the OTA to the adb folder
Copy your root.zip patch to the /sdcard downloads folder (if you wish root)
>adb reboot bootloader
>fastboot flash recovery stockrecovery.img
>fastboot reboot-bootloader
Go into recovery and wait till dead droid appears
Press power and Volume Up at same time to go into the stock recovery menu
Using the volume buttons move and down the blue list of options and select: Apply update from ADB
You will now have orange text at the bottom of the screen - follow the instructions to side load by typing >adb sideload otaupdate.zip in your command prompt window
Wait and watch the progress, at this point you should see the ota processing steps of which there a few and will vary depending on the package. When its complete there will be a "install complete" or similar message
Reboot and let the update complete the system optimizations and go in validate your device is working and the version is what you wanted
>adb reboot bootloader
>fastboot flash twrp.zip
>fastboot reboot-recovery
Using your newly installed custom recovery you can now apply zips/root etc
Reboot as needed and update root if using older .zip to current binaries and enjoy your updated device.
And yes you only need to backup once prior to starting but many people skip that step -DON'T BE ONE OF THOSE PEOPLE.
Hopefully I've not missed a bit.
You can also use these same instructions if you're stuck in boot loop or applied a patch without first replacing stock or unrooting - just boot to bootloader using fastboot and replace recovery and apply the patches. This will usually work just fine and prevent much heart ache on your part.

How I got the 4.4.2 update to actually update...

When I tried to update my rooted stock N7 to 4.4.2 from 4.4.0, the script always failed saying "debuggerd has unexpected content."
This is apparently a known issue revolving around stickmount. Unfortunately, I didn't have a replacement debuggerd and didnt' want to take the time to find and install the right one... So, if you need a quick list of things to do to get the update working (Used Windows 7)
Please note that
:
1) Download
the stock 4.4.0 image from https://developers.google.com/android/nexus/images#nakasi
the Android SDK bundle from here: https://developer.android.com/sdk/index.html
SuperSU from http://forum.xda-developers.com/showthread.php?t=1538053
The actual update file if you don't have it already (mine was already in /cache when I started down this road)
Install the Android SDK.
Run the Android SDK manager and make SURE you get the USB drivers.
Enable Android debugging on the N7 and plug it in via USB to the computer.
Once it fails to find a driver for one of the options, open the device manager.
Locate the "Nexus 7" in "other devices"
Right click and select "update driver"
Tell Windows to look in the ...\adt-bundle-windows-x86_64-20131030\sdk\extras\google\usb_driver directory
Once the driver is installed, open a command prompt and CD to the ...\adt-bundle-windows-x86_64-20131030\sdk\platform-tools directory
Run "adb devices"
You should get a prompt on the N7 asking for permission. Allow it.
You should see your device in the list.
put the SuperSU update file on the N7 by running:
adb push {downloadpath}\UPDATE-SuperSU-v1.80.zip /sdcard/​
if needed, push the OTA file to the same place.
adb push {downloadpath}\{taht awfully long name} /sdcard/​
run adb reboot bootloader
You should be in the bootloader.
Another device driver should install. After that "fastboot devices" should show your device.
Extract the 4.4 factory image to its own directory
Locate the "image-nakasi-krt16s.zip" file in the "nakasi-krt16s" subdirectory.
extract that .zip file to it's own directory
CD to that last directory in the command prompt
run fastboot flash-image system system.img
use the bootloader interface to boot into recovery
Flash the OTA file
Flash the SuperSU update
wipe cache and Dalvik
reboot normally.
In my case, I used TWRP and created a flash queue to flash both the OTA file and SuperSu. When I rebooted, everything came up. The first boot was a little long, and I got the normal post-OTA "Optimizing app n of 200" count.
I just take the OTA, unzip it, edit the update script and remove where it patches boot, recovery-from-boot, power.grouper.so, and in this case, debuggerd. Zip it back up, flash with twrp.
khaytsus said:
I just take the OTA, unzip it, edit the update script and remove where it patches boot, recovery-from-boot, power.grouper.so, and in this case, debuggerd. Zip it back up, flash with twrp.
Click to expand...
Click to collapse
Well, I'm not that up on editing update scripts. Then someone posts the factory image URLs.... That would have been SOOO much faster. That's how I got to 4.3. I used fastboot to flash the 4.3 system image....
Sent from my Nexus 7 using Tapatalk 4
khaytsus said:
I just take the OTA, unzip it, edit the update script and remove where it patches boot, recovery-from-boot, power.grouper.so, and in this case, debuggerd. Zip it back up, flash with twrp.
Click to expand...
Click to collapse
I have the zip, where is the script located?
Sent from my Nexus 7 using Tapatalk
redmonke255 said:
I have the zip, where is the script located?
Click to expand...
Click to collapse
./META-INF/com/google/android/updater-script
Remove every line related to power.grouper.so and LNX:5109760 (part partition reference). There's two of each, one apply_check_patch and one apply_patch plus a set_metadata for the power.grouper.so
I could put the file on Dropbox but I think it's more useful to see what's going on than just handing it out. As they say, give a man a fish and you'll feed him for a day. Teach a man to fish and he'll sit out in a boat drinking beer all day.
khaytsus said:
./META-INF/com/google/android/updater-script
Remove every line related to power.grouper.so and LNX:5109760 (part partition reference). There's two of each, one apply_check_patch and one apply_patch plus a set_metadata for the power.grouper.so
I could put the file on Dropbox but I think it's more useful to see what's going on than just handing it out. As they say, give a man a fish and you'll feed him for a day. Teach a man to fish and he'll sit out in a boat drinking beer all day.
Click to expand...
Click to collapse
That's good information. I know last time someone posted details exactly what lines in updater-script needs to be removed (i believe it was 4.3 OTA update). it would be wonderful if someone posts an updated updater-script here, so avoid any kind of other issues.
looking forward to see updater-script attached here!
bunch of thanks!!
small correction on command: run fastboot flash system system.img
in my case, I had to flash boot as well (wrong kernel I guess), otherwise TWRP was giving the emmc error, when flashing the OTA "emmc /dev/block/platform/msm_sdcc.1/by-name/boot 71"
I did fastboot flash boot boot.img
and then flashed the OTA in recovery, followed by SuperSU. And everything was back to normal, including xposed framework, which I had disabled prior to starting the OTA flashing.

Easily Apply OTA Update To Rooted Nexus 6

I had a hard time finding this information, so thought I would post a new thread!
After you root your phone, even if using standard recovery, the OTA updates will no longer install. You may get the notifications, but after it reboots to install, you will get a failed notification. Even if you uninstall root. This is because if there is any change to the system image at all, the OTA update will fail.
To install it is actually easy, just requires some legwork. I assume you understand what the bootloader is, and what adb and fastboot tools are since your phone is already rooted. If you used a toolkit, there are plenty of guides on XDA on how to install these tools manually.
Step 1 - Collect Needed Files:
Visit the Google System Images page and download the image for your existing ROM. Check your About Device page to get the exact ID, it should say something like LVY48E.
Extract the system.img file so you can flash it later.
Download the OTA image. All OTA images are listed on the Nexus 6 OTA Images thread. Find the file which upgrades "From" your current ROM id. It will only work if from matches your current image version. It will be named something like 2bef78c4a5ec8dbaa3df9d94e78af8622cd2a394.signed-shamu-LVY48F-from-LVY48E.2bef78c4.zip, and this file in particular flashes to the new LVY48F version from LVY48E version.
Step 2 - Flash Stock System Image:
This step replaces your system image with the stock system image. This will not delete your apps or other personal data, only the information stored on the system partition. The only exception is if you rooted and stored any data on this partition. Plug your phone into your computer. There is no way to do this without a PC.
Reboot into bootloader mode either from booting with POWER+VOLDOWN or via adb:
Code:
adb reboot bootloader
and flash the image
Code:
fastboot erase system
fastboot flash system system.img
At this point your system is stock again (unrooted).
Step 3 - Flash Update Image:
Enter the recovery mode. You can also do this via TWRP but I will cover with stock recovery. Press Volume Up/Down until you see RECOVERY and press power to choose. You are now in recovery.
Press and hold Power and tap Volume Up once to get the recovery menu. Then use Volume Up/Down to select "apply update from ADB" and then Power to select
I had to unplug and plug my phone back in at this point to get it to show up to adb. You can confirm it is visible with the command adb devices.
Apply the OTA update file using the following command, replacing the file name with your own:
Code:
adb sideload 2bef78c4a5ec8dbaa3df9d94e78af8622cd2a394.signed-shamu-LVY48F-from-LVY48E.2bef78c4.zip
After a few minutes the sideload will complete, the phone will reboot and optimize apps, and you can verify the update worked by checking your about system page again.
To root your device again, re-install SuperSU and you're good to go.
I actually just asked about this in the T-Mobile thread, but thanks for making this. My question is, when installing system.img is there anything else you NEED to flash as well, specifically boot and/or cache?
Google has the latest stock image for T-Mobile so I was planning on flashing system and radio, but I wasn't sure if there was anything else required when flashing system.img.
I know I don't want recovery or userdata as that would replace TWRP and all my data, so I'd of course leave those out.
hayzooos said:
I actually just asked about this in the T-Mobile thread, but thanks for making this. My question is, when installing system.img is there anything else you NEED to flash as well, specifically boot and/or cache?
Google has the latest stock image for T-Mobile so I was planning on flashing system and radio, but I wasn't sure if there was anything else required when flashing system.img.
I know I don't want recovery or userdata as that would replace TWRP and all my data, so I'd of course leave those out.
Click to expand...
Click to collapse
Nope, system.img was all that I flashed, verified it worked fine with just that.
So you just have to re-root after right?
JTheAppMerchant said:
So you just have to re-root after right?
Click to expand...
Click to collapse
Correct
Thanks for this guide. I've been trying to figure out how to do this exact thing. When I do the command:
adb sideload 4458964f84d2e44ecd2c1c31c301d47eec4b080e.signed-shamu-LMY48M-from-LMY48I.4458964f
Click to expand...
Click to collapse
it gets to about 50%, then gives a Error message,
E:Error in /sideload/package.zip (Status 7) Installation aborted.
Click to expand...
Click to collapse
Any suggestions?
falconfox said:
Thanks for this guide. I've been trying to figure out how to do this exact thing. When I do the command:
it gets to about 50%, then gives a Error message,
Any suggestions?
Click to expand...
Click to collapse
First try a different USB cable and port.
Thanks for the guide. Does it wipe all the data and files in internal storage?
I did this successfully
torecdude said:
Thanks for the guide. Does it wipe all the data and files in internal storage?
Click to expand...
Click to collapse
I wanted to say thanks first of all for putting this up. It helps those rooted users out there that do actually want security patches applied to the system image. To answer the question above, No it does not wipe data or storage if you follow the instructions to only modify /system partition.
A note about the LMY48M update file and the above comments in the OP : This update changes the kernel (in other words), the boot.img file as well. So if you have flashed a non-stock kernel, you will need to go back to stock during the update (and I suggest just leaving it). That is the partition called boot where boot.img lives. It mainly is the kernel. The way to go back to stock (say if you flashed franco with the FKupdate tool and did not do it manually) is to simply do like above and flash it from the factory image he mentions above for 48I file.
You reboot to the bootloader (*I assume you know how*) with power and vol down button. And then the following command after flashing system.img:
fastboot flash boot boot.img
This takes you to stock LMY48I and should allow you to update now to 48M. I learned this by watching the update failure messages as well as noticed it has boot.img changed in the zip file. Hope this helps others. :good:
bitpushr said:
First try a different USB cable and port.
Click to expand...
Click to collapse
I'm having the exact same issue/error. Already tried new USB ports and cables.
falconfox said:
When I do the command:
it gets to about 50%, then gives a Error message, Any suggestions?
Click to expand...
Click to collapse
confused2much said:
I'm having the exact same issue/error. Already tried new USB ports and cables.
Click to expand...
Click to collapse
Open the update .zip file and go to META_INF > COM > GOOGLE > ANDROID. You will find the "updater-script" file.
Open that file using a text editor like notepad or notepad++ and delete the following text; starting from "assert ....... till the semicolon of the last getprop command.
Place that file back into the update .zip file and reflash. This should remove the status 7 error.
jase33 said:
Open the update .zip file and go to META_INF > COM > GOOGLE > ANDROID. You will find the "updater-script" file.
Open that file using a text editor like notepad or notepad++ and delete the following text; starting from "assert ....... till the semicolon of the last getprop command.
Place that file back into the update .zip file and reflash. This should remove the status 7 error.
Click to expand...
Click to collapse
I'll try this now, thanks for the response!
Honest question: why would you flash a system image and an ota when you could just flash the new system image?
jhotmann said:
Honest question: why would you flash a system image and an ota when you could just flash the new system image?
Click to expand...
Click to collapse
By flashing just the current system image your data stays in tact. Then you can take the OTA, it will see the system image unmodified, and it will update everything for that new version without wiping data.
jase33 said:
Open the update .zip file and go to META_INF > COM > GOOGLE > ANDROID. You will find the "updater-script" file.
Open that file using a text editor like notepad or notepad++ and delete the following text; starting from "assert ....... till the semicolon of the last getprop command.
Place that file back into the update .zip file and reflash. This should remove the status 7 error.
Click to expand...
Click to collapse
I do not have the text "assert" anywhere in that file....
jase33 said:
By flashing just the current system image your data stays in tact. Then you can take the OTA, it will see the system image unmodified, and it will update everything for that new version without wiping data.
Click to expand...
Click to collapse
Easier to just flash the new system image that gets you to the same place as the OTA.
jhotmann said:
Honest question: why would you flash a system image and an ota when you could just flash the new system image?
Click to expand...
Click to collapse
I was wondering this same exact thing, but I was assuming it was because the OTA was hitting people before that matching Google Factory Image was available. This would bring you almost back a version (to being stock) so you could take the OTA.
If the OTA is to match the same Factory Image you can get from Google, I have no idea why you'd do both steps.
Hi, I have the LNX07M, and I don't find it in the google page. Can you help me? please!
hayzooos said:
I was wondering this same exact thing, but I was assuming it was because the OTA was hitting people before that matching Google Factory Image was available. This would bring you almost back a version (to being stock) so you could take the OTA.
If the OTA is to match the same Factory Image you can get from Google, I have no idea why you'd do both steps.
Click to expand...
Click to collapse
I think the only reason to do both steps is to apply the update ASAP. If you are ok waiting, then only flash the new system.img. That's definitely what I always do. I don't mind waiting. I have Google Play Services notifications hidden now anyway, so those update notifications don't show up and bug me.
Thanks for the walk through though, @bitpushr, I'm sure many can make use of it.
confused2much said:
I do not have the text "assert" anywhere in that file....
Click to expand...
Click to collapse
Honestly, you shouldn't edit those files as that can be dangerous, and disabling the filesystem check can be dangerous, and it probably won't work because then the zip would fail signing verification.
If you followed all of the instructions in OP and still get error 7, try, on top of erasing and flashing the stock system.img, also extract and erase then flash boot.img and recovery.img. You will get error 7 if your recovery and kernel (boot.img) aren't stock.

[ GUIDE ] [ Marshmallow Firmware Upgrade ROM install including ViperOneM9 4.x.x ]

Dummy friendly guide how to upgrade, flash and install the latest Marshmallow Firmware and the latest ROM’s such as the ViperOne ROM 4.x.x, this guide is intended for those who are already slightly familiar with the flashing process and have previously managed to flash a ROM on their HTC One M9 device…
CHECKLIST BEFORE STARTING:
1) Phone is S-OFF
2) Unlocked Bootloader
3) Rooted
4) Latest TWRP recovery
5) SUPER CID changed to 11111111
6) External SD Card
7) NANDROID Backup and any or every other form of backup
8) Device drivers, Android SDK Platform Tools including ADB & FASTBOOT.
9) USB Debugging enabled.
10) BACK UP OF ALL YOUR DATA !!!
Before we begin make sure you back up all your data on both the internal and external SD card.
For the purpose of this tutorial we will be installing the latest ViperOneM9 ROM…
a) Downloaded and place the latest ViperOne ROM - ViperOneM9_4.x.x.zip on your External SD card,
Main Thread by j to the 4n is found here:
http://forum.xda-developers.com/one-m9/development/rom-viperonem9-1-0-0-tweaks-hub-t3072773
Latest ViperOne ROM for download is here:
http://venomroms.com/htc-one-m9/
b) If you are currently on ViperOneM9 3.5.0 or older and wish to upgrade to the latest 4.x.x than the latest Marshmallow firmware is required (3.35.401.12 or 3.35.617.12 firmware)… This can be found here and within Sneakyghost original thread.
https://docs.google.com/spreadsheets/d/1ZaiJ3F_f76sVa4daU5H62OYi5Bj23LEBBv4xDTQ8y-M/pubhtml
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
Now download the latest version of either:
NO WIPE ZIP
or
FULL STOCK WIPE ZIP
For this tutorial we will use the FULL STOCK WIPE ZIP (to archive a clean install – this will wipe everything on your phone excluding the External SD card)
c) Place the downloaded M9_3.35.401.12_FullStock_wipe.zip into your Android SDK Platform Tools Folder (for example C:\Android\ if this is where all your tools are found)
d) Download the latest version of TWRP recovery from
http://www.teamw.in/devices/htconem9.html
Place the downloaded twrp-2.8.7.0-hima.img in your Android SDK Platform Tools Folder
e) Once you are 101% ready to begin the process start by connecting your device and launching the command window (hold shift, right click in window with all the required ADB/FASTBOOT aps and select "open command window here) once the black terminal window appears start by typing in
adb devices
if your phone appears in the list we can continue by typing:
adb reboot download
wait a few seconds for the screen to appear and type:
fastboot oem rebootRUU
your phone should now be in the RUU mode with a silver HTC logo, now type
(if you renamed the original file type its current name, by default it is as follows)
fastboot flash zip M9_3.35.401.12_FullStock_wipe.zip
f) you will most likely receive something like this towards the end after running the above command...
FAIL90 hboot pre-update! please flush image again immediate
FAILED (remote: FAIL90 hboot pre-update! please flush image again immediate)
For "hboot-preupdate" response, restart the same procedure for device...
just type the above command again and phone will flash the update again and hopefully it will take at least a minute or more to complete, hopefully there will be no more errors, just in case repeat the above command... Just in case you do see errors try looking them on Sneakyghost's thread found here
g) Once this is done and everything passed than we have successfully upgraded our firmware to Marshmallow... Since we selected the FULL STOCK WIPE option we need to flash TWRP once again (as it was wiped) and don't bother resetting or hoping for the phone to boot normally as it won’t...
(if you renamed the original file type its current name, by default it is as follows)
Type:
fastboot flash recovery twrp-2.8.7.0-hima.img
and once it’s done
adb reboot-bootloader
*if for any reason you need to reset your phone and gain access to the bootloader menu, download mode, recovery etc. you can always do this manually by holding vol up, vol down and power buttons at the same time for a few seconds to reset the device, to get into the bootloader, recovery, download mode etc. After the phone resets continue holding the vol down and power button until you reach the bootloader menu.
*if you type adb devices and you see multiple devices or emulators that prevent the commands from working I suggest running the following:
adb kill-server
adb devices
Now only your connected device should appear…
h) It is now time to enter our recently flashed recovery to finally install our latest ROM.
Enter the recovery manually or by typing
adb reboot recovery
From there you may select the wipe option (swipe to factory Reset) and proceed to the Install section, browse for your ROM file and select it.
i) Within Aroma installer select all your preferred options and begin to install, once the flashing completes your device should reboot and now you keep your fingers crossed and wait (will take several minutes so just be patient…. And DONE!!! You now have the latest Marshmallow firmware and ViperOneM9 ROM installed.
#Please note that I’m no expert when it comes to these matters, this guide is here to help anyone who is unsure what to do, I tried to write it up the best way possible (sorry that there are no fancy pictures) if there any errors or issues with my methods please feel free to correct them but so far they worked for me and hopefully will also work for you. (This guide will also help you flash other ROM's) If you need more help please feel free to ask, there is always someone here on xda who knows the answers 
Excellent write up !!
Many thanks !!!....g
glad i could help
GODSPD said:
glad i could help
Click to expand...
Click to collapse
Very nice writeup. Just got an M9 for the wife. I've been around the block so I get everything, but I've been away from HTC since the One X...well, there's the N9 but it's a nexus. What are the RUU mode and Download mode. If I remember correctly there was only the bootloader to go to on the One X. If it's complicated is there somewhere I can read about the modes?
Can you write instructions for s-on and unlocked boatloader? Thanks.
Sent from my HTC One M9 using Tapatalk
Excellent write-up! For extra-completeness, could you please cover changing the mid in android-info and dealing with error 22 (stuff about headers). I'm still fighting that one...
Thanks for your time.
CrazyRom said:
Excellent write-up! For extra-completeness, could you please cover changing the mid in android-info and dealing with error 22 (stuff about headers). I'm still fighting that one...
Thanks for your time.
Click to expand...
Click to collapse
PM sent, hope it helps.
zrzhu said:
Can you write instructions for s-on and unlocked boatloader? Thanks.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Have you received the official Marshmallow OTA yet on your device? the S-OFF method is available for those who don't want to wait for official updates, I will gladly write up a S-ON method once more people receive the official update...
GODSPD said:
PM sent, hope it helps.
Click to expand...
Click to collapse
Also try the following as error 22 was not covered in the error handling section...
http://forum.xda-developers.com/showpost.php?p=59783531&postcount=3
Download 7zip, open the zip inside of the program, right click on the Android text file and open within. Change the mid to yours hit save. It will ask if you want to update the zip, hit yes. Then try and flash.
SneakyGhosts post explains this:
Error 22 is new to me too but the string is kind of self explanatory: every archive has a header where the archive-program finds info about what type of archive and what compression. If the error says anything about this header, the logical conclusion is either a corrupted, broken archive or an unsupported archive type.
I suspect the latter simply due to the fact that the zip was unpacked and repacked, which then easily creates an incompatible zip.
GODSPD said:
Have you received the official Marshmallow OTA yet on your device? the S-OFF method is available for those who don't want to wait for official updates, I will gladly write up a S-ON method once more people receive the official update...
Click to expand...
Click to collapse
No, I've att m9. I'm still I viperone 3.5. Why do we need to wait for the official update?
Sent from my HTC One M9 using Tapatalk
zrzhu said:
No, I've att m9. I'm still I viperone 3.5. Why do we need to wait for the official update?
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
because you need the latest firmware in order to install 4.x.x and the only way to get the latest firmware is via the OTA or by flashing it with the s-off method.
GODSPD said:
because you need the latest firmware in order to install 4.x.x and the only way to get the latest firmware is via the OTA or by flashing it with the s-off method.
Click to expand...
Click to collapse
Thanks. Hopefully ATT will release Marshmallow soon then.
Hi guys i dont have anymore pc. Can i flash new firmware without pc? Plz help
Can you put here your all c:\android folder in .zip file? Of course you can't put here all venom rom zip, but only all your files in that folder
BLEK0TA said:
Can you put here your all c:\android folder in .zip file? Of course you can't put here all venom rom zip, but only all your files in that folder
Click to expand...
Click to collapse
which exact files are you after, the android sdk?
thanks bro!! nice collection!
zrzhu said:
Thanks. Hopefully ATT will release Marshmallow soon then.
Click to expand...
Click to collapse
I'm still kind of "fuzzy" on this whole firmware thing.... IF I don't want to wait (on ATT) and IF I go S-OFF, which firmware can I/should I use for Marshmallow?
Delete
HI, can you please tel me how long does the firmware flash take as mine has been at it for over 2 hours? Not sure if it is stuck?
I am on sprint. How do i get the new firmware? It isnt on the list. Thank you

After OTA 3.0 update, TWRP screen shows up after reboot?

So, I just downloaded the OTA 3.0 update and it said to reboot to continue? So, I let it reboot but after rebooting, it loaded up the TWRP screen?
What should I do?
Neo3D said:
So, I just downloaded the OTA 3.0 update and it said to reboot to continue? So, I let it reboot but after rebooting, it loaded up the TWRP screen?
What should I do?
Click to expand...
Click to collapse
Navigate to /data/user/0/com.nvidia.ota/app_download
There should be your downloaded ota zip and install manually through twrp. If that would be native stock recovery the process of installation would be automatic
Izsūtīts no manas Nokia 3310 используя бесплатную xda app
visitor29 said:
Navigate to /data/user/0/com.nvidia.ota/app_download
There should be your downloaded ota zip and install manually through twrp. If that would be native stock recovery the process of installation would be automatic
Izsūtīts no manas Nokia 3310 используя бесплатную xda app
Click to expand...
Click to collapse
Thank you! But, my machine doesn't have a subfolder called, "0" after /data/user/?
Follow the guide i provided below my text. I merely ran through the process, but roughly followed the guide mentioned. Also, What I did was a clean install method
I dont know about visitor29's post, as I didn't go that route. But for me personally, I clean installed the previous 2.1 update, by connecting to my pc, rebooting into fastboot, then sending fastboot commands to flash the images for 2.1. once this reverted back the recovery image to stock. once finished i booted back into shield and allowed it to update, which, with the proper recovery installed, managed to update to 3.0. i then did a factory reset (just to be sure everything was fresh. thats usually how i do major version updates, personally). After that, I went back into fastboot, BOOTED twrp (not flashed recovery) and installed the supersu.zip i previously put on the shield when i did the 3.0 refresh.
Sorry this is just a quick dirty rundown on what i did. Make sure to follow proper steps provided here:
MAKE SURE YOU KNOW WHAT YOU ARE DOING
http://nvidiashieldzone.com/shield-android-tv/root-shield-android-tv-2/
unvaluablespace said:
Follow the guide i provided below my text. I merely ran through the process, but roughly followed the guide mentioned. Also, What I did was a clean install method
I dont know about visitor29's post, as I didn't go that route. But for me personally, I clean installed the previous 2.1 update, by connecting to my pc, rebooting into fastboot, then sending fastboot commands to flash the images for 2.1. once this reverted back the recovery image to stock. once finished i booted back into shield and allowed it to update, which, with the proper recovery installed, managed to update to 3.0. i then did a factory reset (just to be sure everything was fresh. thats usually how i do major version updates, personally). After that, I went back into fastboot, BOOTED twrp (not flashed recovery) and installed the supersu.zip i previously put on the shield when i did the 3.0 refresh.
Sorry this is just a quick dirty rundown on what i did. Make sure to follow proper steps provided here:
MAKE SURE YOU KNOW WHAT YOU ARE DOING
http://nvidiashieldzone.com/shield-android-tv/root-shield-android-tv-2/
Click to expand...
Click to collapse
Thanks!
I just started looking in all the folders and found the ota.zip file. Mine was located in:
Code:
/data/data/com.nvidia.ota/cache/
However, I have a new problem now. I keep getting this error:
Code:
This package is for "foster" devices; this is a "shieldtablet"
E:Error executing updater library in zip '@/cache/recovery/block.map'
E:Error installing zip file '@/cache/recovery/block.map'
I don't want to do a stock reset because that means I'll have to reinstall Kodi again. I don't want to lose all my preferences and settings in Kodi.
unvaluablespace said:
Follow the guide i provided below my text. I merely ran through the process, but roughly followed the guide mentioned. Also, What I did was a clean install method
I dont know about visitor29's post, as I didn't go that route. But for me personally, I clean installed the previous 2.1 update, by connecting to my pc, rebooting into fastboot, then sending fastboot commands to flash the images for 2.1. once this reverted back the recovery image to stock. once finished i booted back into shield and allowed it to update, which, with the proper recovery installed, managed to update to 3.0. i then did a factory reset (just to be sure everything was fresh. thats usually how i do major version updates, personally). After that, I went back into fastboot, BOOTED twrp (not flashed recovery) and installed the supersu.zip i previously put on the shield when i did the 3.0 refresh.
Sorry this is just a quick dirty rundown on what i did. Make sure to follow proper steps provided here:
MAKE SURE YOU KNOW WHAT YOU ARE DOING
http://nvidiashieldzone.com/shield-android-tv/root-shield-android-tv-2/
Click to expand...
Click to collapse
(little bit browsing for appropriate folder then walk through factory reset procedure for automatic upgrade ??? !!!!) yes u can do that if you already on 2.1, but if you on 3.0 vulkan without stock recovery? and my way bit faster is (just navigate to appropriate folder for ota) ---- after upgrading 3.0 you can do factory reset through twrp or through system it self.
---------- Post added at 06:26 PM ---------- Previous post was at 06:09 PM ----------
Neo3D said:
Thanks!
I just started looking in all the folders and found the ota.zip file. Mine was located in:
Code:
/data/data/com.nvidia.ota/cache/
However, I have a new problem now. I keep getting this error:
Code:
This package is for "foster" devices; this is a "shieldtablet"
E:Error executing updater library in zip '@/cache/recovery/block.map'
E:Error installing zip file '@/cache/recovery/block.map'
I don't want to do a stock reset because that means I'll have to reinstall Kodi again. I don't want to lose all my preferences and settings in Kodi.
Click to expand...
Click to collapse
start downloading ota....when its over dont restart just press home button on remote and go to es file explore (first enable root exlorer) ---- navigate device/data/data/com.nvida.ota/app_download/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.zip
copy that long name file with ending with .zip to somewhere like download folder ------------reboot to recovery and reflash
p.s. ota location path is from 16gb i have 500gb i have same path, should be on yours tooo. try
p.s. sorry for gave you wrong path first, didnt check personally my self
Thanks, I just had to flash the recovery image again for the update to work.
Nice. glad to hear thats all you needed to do. I had a feeling that might be the case, but i didn't want to suggest that in case it was wrong. lol

Categories

Resources