There is a new update out. Is there anything special we need to do to preserve root if we are rooted? I don't have CWM installed.
Would it be advisable to use OTA rootkeeper?
EDIT - OTA rootkeeper didn't work and root was lost. The update must wipe /system. I guess I'll have to try rooting when I get home again. Hopefully that remains the same. I didn't want to have to flash recovery and jump through hoops updating the Shield which is why I left the stock recovery on there... Oh well. Bootloader remains unlocked so I suppose it should be easy as entering the one fastboot line I used from Gnurou...
Edit 2 - Root using Gnurou's instructions worked.
Evo_Shift said:
There is a new update out. Is there anything special we need to do to preserve root if we are rooted? I don't have CWM installed.
Would it be advisable to use OTA rootkeeper?
EDIT - OTA rootkeeper didn't work and root was lost. The update must wipe /system. I guess I'll have to try rooting when I get home again. Hopefully that remains the same. I didn't want to have to flash recovery and jump through hoops updating the Shield which is why I left the stock recovery on there... Oh well. Bootloader remains unlocked so I suppose it should be easy as entering the one fastboot line I used from Gnurou...
Click to expand...
Click to collapse
I have an idea that might help keep root, let me check it out.
UPDATE
It won't work in this case. The update patches recovery and flashes a new boot.img
UPDATE2
If you have CWM Recovery installed, after flashing the update it will ask if you want to disable recovery flash and then if you want to root.
Yes, you will have to re-run the fastboot command after each OTA. Preserving root after an OTA would require a custom recovery (like CWM). I tried to apply this OTA with the version of CWM agrabren uploaded and it failed, so until this is fixed I guess the best thing to do it just re-root after each OTA
Gnurou said:
Yes, you will have to re-run the fastboot command after each OTA. Preserving root after an OTA would require a custom recovery (like CWM). I tried to apply this OTA with the version of CWM agrabren uploaded and it failed, so until this is fixed I guess the best thing to do it just re-root after each OTA
Click to expand...
Click to collapse
Did it fail with status 7?
EDIT
It would have (failed with status 7) agrabren called the shield thor in his recovery and nvidia called it roth in the update. So the update was expecting roth for the device name and got thor.
Thats why it worked for me because i renamed it roth when i modded the recovery.
IF agrabren complains I will remove the link but for now.
Modded version is here
The ota zip is here
So I unrooted my Shield Tablet a while back without changing the stock recovery, and found out that whenever I try to install an OTA update it shows an error during instalation, rendering me unable to aquire the 2.2 and 2.2.1 updates. Already tried unrooting it, locking back the bootloader and so on. I can still sideload updates to the tablet but would like to gain back the convenience of OTA updates. Has anyone encountered similar issues? Could anyone help me fix this issue?
Saw the probable solution on another post.
mdecaminop said:
So I unrooted my Shield Tablet a while back without changing the stock recovery, and found out that whenever I try to install an OTA update it shows an error during instalation, rendering me unable to aquire the 2.2 and 2.2.1 updates. Already tried unrooting it, locking back the bootloader and so on. I can still sideload updates to the tablet but would like to gain back the convenience of OTA updates. Has anyone encountered similar issues? Could anyone help me fix this issue?
Click to expand...
Click to collapse
In these forums somewhere I read that the unroot was done using Super su's full unroot option. However it apparently left behind a few files that caused the OTA to fail. So what he did was to uninstall Supersu, reinstall Supersu and update the binary. Then use full unroot function... Maybe it will work for you if you have unrooted using SUpersu...
Unrooting, locking the bootloader, and flashing the stock recovery doesn't allow you to take OTA's.
There is THIS thread, providing OTA files that can be flashed in TWRP or CWM. And are official files from Nvidia.
You have to flash these every time there's an OTA, or just flash a full stock image through fastboot, and never root or flash a recovery.
I'm having similar issues. I was rooted with CMW recovery but unable to install OTA update. I unrooted, and did a factory reset of the OS.
I tried to install stock recovery 2.2.1 (found on another thread here) with adb sideload command with the following result:
"cannot read "update.zip" (I tried the original filename and changed it to update.zip. Neither worked.) To test adb, I installed Supersu via the same method.
Trying to install the OTA update I receive the following:
Invalid command argument
Finding update package...
E: unknown volume for path [@/cache/recovery/block.map]
E: Can't mount @/cache/recovery/block.map
Installation aborted
I do apologize if I've missed something. Some of the other threads I've been using to learn are many pages long. Any help is appreciated.
mycologik said:
I'm having similar issues. I was rooted with CMW recovery but unable to install OTA update. I unrooted, and did a factory reset of the OS.
I tried to install stock recovery 2.2.1 (found on another thread here) with adb sideload command with the following result:
"cannot read "update.zip" (I tried the original filename and changed it to update.zip. Neither worked.) To test adb, I installed Supersu via the same method.
Trying to install the OTA update I receive the following:
Invalid command argument
Finding update package...
E: unknown volume for path [@/cache/recovery/block.map]
E: Can't mount @/cache/recovery/block.map
Installation aborted
I do apologize if I've missed something. Some of the other threads I've been using to learn are many pages long. Any help is appreciated.
Click to expand...
Click to collapse
Well it seems my second hand tablet has been rooted as well ... I've got the exact same problem that yours ...
Is there a way to go back as out of the box ?
I bought a China set of OPO last month. I thought this phone originally installed Color Os rom and then re-installed to CM11s 44s version when it selling. When I turned on the phone for the first time, I already get the update notification for the 05q version. So, I tried to update it but it failed to update it for many times that I tried. My phone rebooted when I clicked "flash updates" and loading for a while then failed in cyanogen recovery. I also tried with manually update with downloaded zip file and installed it in cyanogen recovery. It still failed with mentioned "system 7..." message. Is there any way to fix this problem if I want to flash cm11s latest update firmware, rather than use other custom roms? ??
It's impossible to know what the seller did to the phone before you got it so it's probably a good idea to flash the stock images and start from scratch. Go to my guide thread here:
http://forum.xda-developers.com/showthread.php?t=2839471
If your bootloader is locked you'll need to unlock it, but be aware that doing so wipes all user data. Install TWRP recovery and make a nandroid backup of your current setup just in case. Then flash the stock images using fastboot.
Transmitted via Bacon
Actually, what does "system error 7" means when installation?
Here you go
johnsin5393 said:
Actually, what does "system error 7" means when installation?
Click to expand...
Click to collapse
Here you will find what is System 7 error and how to fix it.
http://forum.xda-developers.com/showthread.php?t=2522762
Hi,
I've got TWRP 3.0.2-0 recovery installed with CM12.1.1 YOG7DAS2K1 and am receiving the OTA update for CM13.0 ZNH0EAS2JK Incremental but the installation fails with an error message in recovery saying it's expecting "YOGDAS2K1" level but finds "YOG4PAS1N0". This happens whether I re-enable the CM Recovery update or not.
I found a thread here on XDA linking to all CM official updates. I flashed the recovery from "cm-12.1-YOG7DAS2K1-bacon-signed-fastboot" successfully and then tried the update again but it still failed. Again, happens whether I have CM Recovery update enabled or not.
Verifying current system...
system partition has unexpected contents
E : Failed to install @/cache/recovery/block.map
Click to expand...
Click to collapse
So now I flashed TWRP again. Does someone know what I should do to install the update ? Preferably without returning to stock first.
Solved
Feeling a bit stupid really...
Right under my post in the list was this post which deals with my problem exactly. I just updated my phone using that guide.
So this morning i finally got the Nougat update. I downloaded it and waited for it to get verified. Got a pop-up saying install now, install later and don't install. I pressed install now waited and... Nothing happend. Went to software update in the settings and tried there, the same thing happened. Help is appreciated.
XenosRi said:
So this morning i finally got the Nougat update. I downloaded it and waited for it to get verified. Got a pop-up saying install now, install later and don't install. I pressed install now waited and... Nothing happend. Went to software update in the settings and tried there, the same thing happened. Help is appreciated.
Click to expand...
Click to collapse
i think you must install firmware first
look at here https://forum.xda-developers.com/showpost.php?p=71609608&postcount=3
XenosRi said:
So this morning i finally got the Nougat update. I downloaded it and waited for it to get verified. Got a pop-up saying install now, install later and don't install. I pressed install now waited and... Nothing happend. Went to software update in the settings and tried there, the same thing happened. Help is appreciated.
Click to expand...
Click to collapse
Do you have stock recovery or did you install TWRP? Have you ever mounted /system read/write?
To take an OTA (besides flashing it in TWRP and the firmware seperate) you need stock recovery and an untouched /system image.
Phildu91 said:
i think you must install firmware first
look at here https://forum.xda-developers.com/showpost.php?p=71609608&postcount=3
Click to expand...
Click to collapse
No, only to update from MM to N using a RUU. Not needed when updating with OTA.
JohnRogers23 said:
Do you have stock recovery or did you install TWRP? Have you ever mounted /system read/write?
To take an OTA (besides flashing it in TWRP and the firmware seperate) you need stock recovery and an untouched /system image.
Click to expand...
Click to collapse
I didn't find out why i couldn't install it, also i wasn't rooted, but i did a factory reset and that seemed to fix it! Now im on Nougat with no problems!
trying to update from Marshmallow 1.56.73.70(Orange France) to Nougat via OTA and i can't install...what must i do?
HTC One A9 non rooted , bootloader unlocked and S-On
Phildu91 said:
trying to update from Marshmallow 1.56.73.70(Orange France) to Nougat via OTA and i can't install...what must i do?
HTC One A9 non rooted , bootloader unlocked and S-On
Click to expand...
Click to collapse
Might want to restore your phone with the 1.56.73.70 ruu, after the ota should install fine since everything will be back to stock.
Trying to update my sprint a9 from 1.10.651.1 to nougat, what do i need to do? Im trying to system update via ota to 1.57 but always failed to verified my device?
My phone got supercid, s-off, bootloader unlocked, and non rooted. Can i convert it to global unlock?
imtawakkal said:
Trying to update my sprint a9 from 1.10.651.1 to nougat, what do i need to do? Im trying to system update via ota to 1.57 but always failed to verified my device?
My phone got supercid, s-off, bootloader unlocked, and non rooted. Can i convert it to global unlock?
Click to expand...
Click to collapse
I believe you need to put your CID back to the Sprint one, and make sure you have an untouched (not even mounted r/w) system partition with stock recovery.
JohnRogers23 said:
I believe you need to put your CID back to the Sprint one, and make sure you have an untouched (not even mounted r/w) system partition with stock recovery.
Click to expand...
Click to collapse
I alrd got cid back to sprint one, trying to update my phone with ruu, but always got error 132, and my phone already locked from the black screen bootloader, what did i do wrong from that?
imtawakkal said:
I alrd got cid back to sprint one, trying to update my phone with ruu, but always got error 132, and my phone already locked from the black screen bootloader, what did i do wrong from that?
Click to expand...
Click to collapse
Are you updating to Nougat from the RUU or are you trying to get back to stock to take an OTA? Those are two different but similar processes. Make sure you've got the right RUU for sprint and your version as well.
JohnRogers23 said:
Are you updating to Nougat from the RUU or are you trying to get back to stock to take an OTA? Those are two different but similar processes. Make sure you've got the right RUU for sprint and your version as well.
Click to expand...
Click to collapse
First i want to update to nougat via ruu, but always getting error when flashing the firmware.zip, then im trying to use ruu method to back to stock so i can use the ota, im alrd got the right ruu, but it seems it doesnt works
imtawakkal said:
First i want to update to nougat via ruu, but always getting error when flashing the firmware.zip, then im trying to use ruu method to back to stock so i can use the ota, im alrd got the right ruu, but it seems it doesnt works
Click to expand...
Click to collapse
Did you try flashing the entire RUU for the version you're on right now?
My phone is UK version, i was rooted but flashed the following RUU so that i could return to stock
HTC AERO UHL
1.56.91.71
2PQ9IMG_H[email protected]60122.4_43.05_F_release_471092_signed.zip
EE UK
modelid: 2PQ910000
cidnum: ORANG001
Link: https://www.androidfilehost.com/?fid=24457741883932916
md5: d9fb062162157e6d40adfaa057947f9e
Yesterday i finally recieved the OTA update for NOUGAT but when it downloaded and i pressed install, it loaded halfway in bootloader and eventually failed ending up with triangle and exclamation sign.
I am unrooted and bootloader relocked.
Please help, i have already waited months for this update
Please help anyone!!
flash stock recovery or RUU.
I have similar problem of receiving an error (signarure error:132) while trying update my device by using RUU side load, i have the right RUU for my device but i still receive errors please help me with this
---------- Post added at 06:25 PM ---------- Previous post was at 06:21 PM ----------
I have similar problem of receiving an error (signarure error:132) while trying update my device by using RUU side load, i have the right RUU for my device but i still receive errors please help me with this or if there is any chance i can flash stock recovery please tell me how b'se my device seems to have a modified system and recovery may be this is the problem preventing me from update my device by using RUU side load