Related
Sorry, I'm a bit cautious when dealing with rooting and whatnot...
I currently have ICS installed on my US Wifi Xoom. It has been rooted after the last update before JB, but is using the stock ROM otherwise.
What I'm wondering first is: Do I NEED to unroot before attempting the OTA update to JB, or is it just recommended? And then after I update to JB, do I use the same method to root? I believe I used this guide: http://www.xoomforums.com/forum/mot...ooting-flashing-unrooting-under-one-roof.html
Thanks!
You don't have to unroot to receive the ota. Get vodoo ota root keeper app it will protect root during the update
The Universal Root Method does not work on 4.1.1 does anyone have a fix.....
gmanunited said:
The Universal Root Method does not work on 4.1.1 does anyone have a fix.....
Click to expand...
Click to collapse
ok,,after many tries i finally figured a way to get to stock rooted Jb with the Ota...it was a long process but i was able to do it.
step 1. i re flashed the xoom stock images HC 3.0
step 2. update the xoom from 3.0 to 4.0.4 using the over the air updates.
step 3. fastboot flash the eos r6 recovery while still on 4.0.4
step 4 create a nandroid of the stock 4.0.4 system
step 5. install the Universal Xoom root zip
step 6. log into google account to have access to market
step 7 update superuser app, download ota rootkeeper
step 8 use ota and create a copy of su, then click temp unroot
IMPORTANT
make sure that you have a copy of the jelly bean ota on your internal sd(http://forum.xda-developers.com/showthread.php?t=1736634)
step 9 turn off xoom, then boot into eos recovery
NEXT FEW STEPS ARE CRUCIAL
step 10 choose advance restore from internal (not regular restore option) and select the nandroid of the stock 4.0.4
step 11 select the option to restore only the boot.img
step 12 now install the JB Ota ( when it boots you will lose the eos reovery and the stock recovery will be flashed back,, so you can always fastboot flash back the eos recovery, just make sure to delete the recovery boot.p file in the system folder using root explorer or something similar.)
step 13 once you have flashed the JB ota, boot back into android, open the ota rootkeeper app and restore the su,, then use titanium backup or some other root app to verify that you have root.
optional step 14 after verifying that you do indeed have root access perform a factory wipe so you can start fresh. that's what i did and all was good.
hope that helps some people.
edit : if you are on a stock 4.0.4 than you can continue from step 3 as basically you need to be there in order to follow the rest.
Thanks. I will try this method.
I used the method above with one minor change and it worked perfectly. In place of step 12, I powered down and then booted into fastboot and flashed the stock recovery image. After that I rebooted and was then able to accept the JB 4.1.1 OTA directly without having to download and install it manually. The statement in parenthesis in step 12 still applies.
Tito2007 said:
ok,,after many tries i finally figured a way to get to stock rooted Jb with the Ota...it was a long process but i was able to do it.
step 1. i re flashed the xoom stock images HC 3.0
step 2. update the xoom from 3.0 to 4.0.4 using the over the air updates.
step 3. fastboot flash the eos r6 recovery while still on 4.0.4
step 4 create a nandroid of the stock 4.0.4 system
step 5. install the Universal Xoom root zip
step 6. log into google account to have access to market
step 7 update superuser app, download ota rootkeeper
step 8 use ota and create a copy of su, then click temp unroot
IMPORTANT
make sure that you have a copy of the jelly bean ota on your internal sd(http://forum.xda-developers.com/showthread.php?t=1736634)
step 9 turn off xoom, then boot into eos recovery
NEXT FEW STEPS ARE CRUCIAL
step 10 choose advance restore from internal (not regular restore option) and select the nandroid of the stock 4.0.4
step 11 select the option to restore only the boot.img
step 12 now install the JB Ota ( when it boots you will lose the eos reovery and the stock recovery will be flashed back,, so you can always fastboot flash back the eos recovery, just make sure to delete the recovery boot.p file in the system folder using root explorer or something similar.)
step 13 once you have flashed the JB ota, boot back into android, open the ota rootkeeper app and restore the su,, then use titanium backup or some other root app to verify that you have root.
optional step 14 after verifying that you do indeed have root access perform a factory wipe so you can start fresh. that's what i did and all was good.
hope that helps some people.
edit : if you are on a stock 4.0.4 than you can continue from step 3 as basically you need to be there in order to follow the rest.
Click to expand...
Click to collapse
Based on your steps it sounds like the only real important piece is the rooted boot.img file from ICS.
If someone were to post it, I'd imagine people could simply do this for rooting JB
fastboot oem unlock (unlock bootloader if not already done)
fastboot flash boot /path/to/<boot>.img
Click to expand...
Click to collapse
No guarantees this would work, but in theory it seems right to me.
Are you serious ? the traditional root method doesn't work anymore on JB ??
kinder771 said:
Are you serious ? the traditional root method doesn't work anymore on JB ??
Click to expand...
Click to collapse
Honestly not really a big surprise. Things change and what security flaw that allowed rooting on previous versions of Android for a device may be patched in future releases.
Okay completed this method and worked fine.
I also on step 12 flashed the stock recovery then performed the update through OTA and after verifying ROOT access with Titanium Backup I OEM unlocked which wipes the device but not Root Access. Its a lot OTA's but a good way to keep root on JellyBean 4.1.1.....
Thanks
kinder771 said:
Are you serious ? the traditional root method doesn't work anymore on JB ??
Click to expand...
Click to collapse
After doing the traditional root method, flash the latest super user using cwr, that is what i did and i now have root.
Sent from my SAMSUNG-SGH-I747 using xda premium
Great to know there maybe an easier method.
JB update
So wait the officials JB OTA is out already?! And if it did how come I can't update on my rooted xoom. Anybody
dough30i said:
So wait the officials JB OTA is out already?! And if it did how come I can't update on my rooted xoom. Anybody
Click to expand...
Click to collapse
Yes, i have been on official 4.1.1 for 2 weeks now, i say official because i updated via OTA.
Sent from my Xoom using xda premium
I think Universal Root Method and flashing latest Superuser working. I have not tried but would love to know if it works.
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
I have 3 RAZR HD phones from Rogers in Canada that are on 4.1.2 that are Rooted but the bootloader has not been unlocked and they have chainfire SuperSU on them. My wife got the OTA update notice days ago and said yes to it. She showed me her phone yesterday with the message that the software update failed. When it failed she was told by a friend at work that it failed because she had a SU on it so she did an uninstall on SU through the playstore and tried the update again that failed. I had told them (wife and daughter) not to make changes to them until i have a look at them, but well I guess that didn't work for one anyway. I let mine download the OTA update but said install later. I have a copy of the zip file now on my PC. She then did a factory reset (work friend) and tried the OTA update again. that failed.
Coupel questions.
1: I have been trying to find out how to unroot the phones so that the OTA update works but am getting a lot of conflicting info and not sure if it applies to my Rogers phones. Do they need to be unrooted to update? Do they need the bootloader unlocked to work around the OTA update After update how do i get Root again?
2: My wifes phone now is "stuck" partially unrooted? What i mean is I tried to put chainfire SU back on but it fails saying the binary cannot install and quits. It will not accept the OTA update from Rogers also. Apps that require Root on her phone do not work properly now also.
MECH_TECH said:
I have 3 RAZR HD phones from Rogers in Canada that are on 4.1.2 that are Rooted but the bootloader has not been unlocked and they have chainfire SuperSU on them. My wife got the OTA update notice days ago and said yes to it. She showed me her phone yesterday with the message that the software update failed. When it failed she was told by a friend at work that it failed because she had a SU on it so she did an uninstall on SU through the playstore and tried the update again that failed. I had told them (wife and daughter) not to make changes to them until i have a look at them, but well I guess that didn't work for one anyway. I let mine download the OTA update but said install later. I have a copy of the zip file now on my PC. She then did a factory reset (work friend) and tried the OTA update again. that failed.
Coupel questions.
1: I have been trying to find out how to unroot the phones so that the OTA update works but am getting a lot of conflicting info and not sure if it applies to my Rogers phones. Do they need to be unrooted to update? Do they need the bootloader unlocked to work around the OTA update After update how do i get Root again?
2: My wifes phone now is "stuck" partially unrooted? What i mean is I tried to put chainfire SU back on but it fails saying the binary cannot install and quits. It will not accept the OTA update from Rogers also. Apps that require Root on her phone do not work properly now also.
Click to expand...
Click to collapse
Would I be able to get a copy of the 4.4.2 Rogers firmware from you? I'm in the same boat and would need a copy of this firmware to force an update with the Motorola tools. If it works out for me I'll definitely share the process.
Your best bet is to backup your data, RSDLite back to stock 4.1.2 and take the OTA. Make sure your bootloader is unlocked. Do not root or install custom recovery before the OTA has completed.
Rogers 4.4.2 OTA file
daswunderkid said:
Would I be able to get a copy of the 4.4.2 Rogers firmware from you? I'm in the same boat and would need a copy of this firmware to force an update with the Motorola tools. If it works out for me I'll definitely share the process.
Click to expand...
Click to collapse
I tried posting a link to 4shared to the file but since i am new to this forum i cannot post links.
link to OTA file
MECH_TECH said:
I tried posting a link to 4shared to the file but since i am new to this forum i cannot post links.
Click to expand...
Click to collapse
will this work with spaces in it?
h t t p: // w w w. 4shared.c o m/zip/PUw0K63Ace/Blur_Version9821122002XT925RCI.h t m l
OTA file link
MECH_TECH said:
I tried posting a link to 4shared to the file but since i am new to this forum i cannot post links.
Click to expand...
Click to collapse
check the post now i put in a link with spaces and it posted.
Bootloader unlocked now
I have the bootloader unlocked now from Moto website. If I boot into AP Fastboot it is confirmed "Device is UNLOCKED. Status Code: 3" I am trying to flash a cmwrecovery.img to the phone. I get the following
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (6824 KB)...
OKAY [ 0.530s]
writing 'recovery'...
OKAY [ 1.997s]
finished. total time: 2.527s
I am not sure that the img is working. I execute the fastboot reboot and hold volume up/down and power select recovery and it stays on the boot logo for a long time then goes black logo comes back and boots normally. Not sure why its not working and do not know what i am doing wrong.
Any advise out there on this Rogers XT926 O.T.A. update fails
Now that the bootloader is unlocked I still cannot get the Rogers OTA to work. I got the 4.1.2 rooted again now and installed chainfire SuperSU onto the phone did a full unroot with SuperSU checked with root checker and now it says it is not rooted. I did a full factory reset wipe all data and downloaded the OTA update, let the OTA update try and it got 3/4 way through and failed. it keeps saying there is a critical update to run will download it and try but fails. I even tried to use the CWM custom recovery to run the update file and it gets error messages and fails. Not sure what to change in the OTA.img file to get this to take. Did anyone else figure out how to force it to complete?
Where is the Rogers stock 4.1.2
I found lots of 4.1.2 img files but I cannot be sure that any are for Rogers. How do I know that they are really plain stock files with now changes made to them, so that I can proceed?
RSDlite problems
CWGSM3VO said:
Your best bet is to backup your data, RSDLite back to stock 4.1.2 and take the OTA. Make sure your bootloader is unlocked. Do not root or install custom recovery before the OTA has completed.
Click to expand...
Click to collapse
I found the Rogers 4.1.2 file called
9.8.2Q-8-XT925_VQL-12.2_CANADA_VANQJBLTEFRCI_P004_CFC_fb.xml.zip
I installed RSDlite 6.1.5
I ran the RSDlite and it sees my phone on USB port 1 info below
MEI/ESN/MEID: N / A
Technology: UMTS
Software Version: 9.8.2Q-8-XT925_VQL-12.2
Flex Version: N / A
Bootloader Version: 109b
DRM Version: N/A
I put the above zip file in the firmware folder
I pick it screen shows
Filename: 9.8.2Q-8-XT925_VQL-12.2_CANADA_VANQJBLTEFRCI_P004_CFC_fb.xml
Creation Date: 12/20/2012 21:34:28
File size: 2640
Sofware Version: XT925_rcica-user 4.1.2 9.8.2Q-8-XT925_VQL-12.2 1356031681 release-keysVANQUISH_U_BP_100700.220.65.33P
For Phone Model: VANQUISH_U
It asks to decompress or decompress and flash.
I picked decompress and flash
It says switching device to flash mode
phone reboots to ap fastboot I see device is UNLOCKED Status Code: 3
I get an error symbol and RSDlite says
Failed flashing process. Unknow fastboot command... Result FAIL
I cannot get the 4.1.2 to flash so I can continue with the OTA update.
What am I doing wrong
daswunderkid said:
Would I be able to get a copy of the 4.4.2 Rogers firmware from you? I'm in the same boat and would need a copy of this firmware to force an update with the Motorola tools. If it works out for me I'll definitely share the process.
Click to expand...
Click to collapse
Here is the Link to 4.4.2 - Rogers Rom, been using it for some time, works flawless
So, I rooted my HTC One M7, and I was wondering if I can update it.
I'm at the new OTA Update Lollipop 5.0.2
I have TWRP.
S-ON, TAMPERED, UNLOCKED.
If I can't update it, can someone tell me how to unroot this?
I appreciate everyone's help.
mohsinsomeone said:
Hope this helpsssss
How to Unroot HTC One, relock the bootloader and restore to stock JB 4.2.2 Firmware
Download the toolkit from this
http://forum.xda-developers.com/showthread.php?t=2242635
Save the file on your computer and unzip the same on desktop.
Extract the file into your C: drive.
Install the HTC One drivers on your computer via toolkit – only if the drivers are not installed on your computer.
For installing the drivers, open the toolkit.
On the left you will have the option for installing the drivers, select the same.
Then, follow the steps from below for learning how to relock the bootloader
How to Relock HTC One bootloader
Run the toolkit once more.
Connect your HTC One with the computer by using its USB cable.
On the app you will have the “relock bootloader” option.
Click on the same and then select “go”.
A command prompt window will be displayed – close it.
Your handset will reboot into fastboot mode.
Close the new command prompt window; a new one will then be displayed.
Now, your device will be relocked.
In the end your phone will reboot automatically; you can close the cmd window once more as you are done.
dont forget to hit thanks button plzz
Click to expand...
Click to collapse
I'll try this once I get back on my laptop. And on relocking, does it say RELOCKED or LOCKED. And if either one of them, do they have a difference? And also, it's fine for me to unroot my Lollipop 5.0.2 to Jellybean 4.2.2 then update it back to Lollipop with the official OTA Update?
Hi there,
No, you can't. Don't try installing an OTA if you're using CWM, TWRP or Philz as it won't work. It will only install via the stock recovery.
You'll also need to make sure that you're on the stock ROM and stock kernel.
For a more detailed explanation of how to receive an OTA, what an OTA updater-script does and what will interfere with OTA's, check out the following post : OTA updates variables
For any other questions please use this thread from your device forum: So you came at XDA-Developers to find help? (Beginners Thread)
Good luck
I bought a Nexus 5 (refurbished) from Freedom Pop. I can't remember what version is came with, maybe 4.4.4. First thing I did with it was install CWM (6.0.4.7) and flash the Google Nexus 5 factory image (5.1.1 / LMY48B) and root the device. Now that LMY48I is out, I got a OTA notification about a system update. When I try to do the OTA update, it fails. So I downloaded the update zip to take LMY48B->LMY48I from http://www.droid-life.com/2015/08/10/download-nexus-4-5-6-7-9-10-ota-stagefright-patches/ . I boot into CWM and install zip, but it fails with:
Package expects build fingerprint of google/hammerhead/hammerhead:5.1.1/LMY48B/1863243:user/release-keys; this device has google/hammerhead/hammerhead:4.4.2/KOT49H/937116 Instllation aborted.
When I go to Settings, System, it shows I have LMY48B. Why does the install think I have KOT49H? When I flashed the factory image it did it not update some file somewhere and if so, how can I get that file to accurately report what I'm running?
Thanks,
exhibit679 said:
I bought a Nexus 5 (refurbished) from Freedom Pop. I can't remember what version is came with, maybe 4.4.4. First thing I did with it was install CWM (6.0.4.7) and flash the Google Nexus 5 factory image (5.1.1 / LMY48B) and root the device. Now that LMY48I is out, I got a OTA notification about a system update. When I try to do the OTA update, it fails. So I downloaded the update zip to take LMY48B->LMY48I from http://www.droid-life.com/2015/08/10/download-nexus-4-5-6-7-9-10-ota-stagefright-patches/ . I boot into CWM and install zip, but it fails with:
Package expects build fingerprint of google/hammerhead/hammerhead:5.1.1/LMY48B/1863243:user/release-keys; this device has google/hammerhead/hammerhead:4.4.2/KOT49H/937116 Instllation aborted.
When I go to Settings, System, it shows I have LMY48B. Why does the install think I have KOT49H? When I flashed the factory image it did it not update some file somewhere and if so, how can I get that file to accurately report what I'm running?
Thanks,
Click to expand...
Click to collapse
You must return to stock before you attempt to install that zip. That means you cannot be rooted or have custom recovery in place
I've got a stock N5 I bought from Google on LMY48B and there's still no update for me.
Does anyone know what the roll-out timeline is for the LMY48I?
When should I conclude that I'm not going to get it OTA and resign myself to factory wipe and flashing the image?
I have a stock Nexus 5, rooted w/ cf-auto-root, re-locked , no custom recovery or bootloaders, and all i see is Error when trying to install this OTA. I'm stuck at the moment myself. Installing the OTA should just unroot my phone, but it won't install. Currently running on 5.1.1 (LMY48B) myself.
Nemesis02 said:
I have a stock Nexus 5, rooted w/ cf-auto-root, re-locked , no custom recovery or bootloaders, and all i see is Error when trying to install this OTA. I'm stuck at the moment myself. Installing the OTA should just unroot my phone, but it won't install. Currently running on 5.1.1 (LMY48B) myself.
Click to expand...
Click to collapse
Mine is stock, un-rooted, but I too keep getting an Error when trying to install the OTA. Stuck on LMY48B at the moment.
moeREM said:
Mine is stock, un-rooted, but I too keep getting an Error when trying to install the OTA. Stuck on LMY48B at the moment.
Click to expand...
Click to collapse
I have the same problem her as well with my nexus 5 it keeps saying error with little droid I've tried side loading manually but it didn't work also tried hard reset and wiping cache but nothing solved the problem so i just figured out the problem is the package it self
Same problem here
Same thing here, error with little droid picture on rooted android 5.1.1.
Has anyone found the reason for this ?
Try flashing system image directly
Sent from my Nexus 5 using Tapatalk
lpganesh said:
Try flashing system image directly
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
This possibility makes me spend a lot of time, becouse i have lcd_density changed and all apps when i restore a backup are not in the main screen.
walt disney said:
Same thing here, error with little droid picture on rooted android 5.1.1.
Has anyone found the reason for this ?
Click to expand...
Click to collapse
This method is for anyone with lmy48b that's rooted or has a radio, kernel or recovery custom flashed.
Condensed version but here's the important pieces. You will lose root if you are unrooted. You will not lose any data or settings if done this way.
Step 1. Download lmy48b from google
Step 2. Unzip lmy48b package
Step 3. Copy bootloader, radio and system.img from lmy48b package (unzip zipped file for bootloader and system.img)
Step 4. Connect phone and boot into bootloader
Step 5. Type in fastboot flash recovery [recovery].img replace [recovery] with the actual file name
Step 6. Type in fastboot flash radio [radio].img
Step 7. Type in fastboot flash system [system].img
Step 8. Reboot
Step 9. Update via OTA
Working - confirmed
cloney said:
This method is for anyone with lmy48b that's rooted or has a radio, kernel or recovery custom flashed.
Condensed version but here's the important pieces. You will lose root if you are unrooted. You will not lose any data or settings if done this way.
Step 1. Download lmy48b from google
Step 2. Unzip lmy48b package
Step 3. Copy bootloader, radio and system.img from lmy48b package (unzip zipped file for bootloader and system.img)
Step 4. Connect phone and boot into bootloader
Step 5. Type in fastboot flash recovery [recovery].img replace [recovery] with the actual file name
Step 6. Type in fastboot flash radio [radio].img
Step 7. Type in fastboot flash system [system].img
Step 8. Reboot
Step 9. Update via OTA
Click to expand...
Click to collapse
Thanks, confirmed that this method worked. Managed to update my rooted nexus 5 to LMY48I
Tried to install ota update after reverting to stock recovery using Simple Recovery Switcher app. However, also the error message, with little Android picture also appears. Please help
I assume this removed your root, though.
It seems we are getting a new factory image en september to properly solve the stagefright bug
"A second patch has been sent out. "We’ve already sent the fix to our partners to protect users, and Nexus 4/5/6/7/9/10 and Nexus Player will get the OTA update in the September monthly security update"
I have decided i will stay at 5.1.1 untill Android M maybe september also. In the meanwhile i have disabled MmsService and OTA.
Pastorelli's said:
It seems we are getting a new factory image en september to properly solve the stagefright bug
"A second patch has been sent out. "We’ve already sent the fix to our partners to protect users, and Nexus 4/5/6/7/9/10 and Nexus Player will get the OTA update in the September monthly security update"
I have decided i will stay at 5.1.1 untill Android M maybe september also. In the meanwhile i have disabled MmsService and OTA.
Click to expand...
Click to collapse
I'm with you, not going to try to flash these things, there are a few zip files out there dated a couple days ago, apparently the zips aren't tested prior to release since everyone is getting failure when flashing the zip file.
Is there really no method to apply OTA updates on rooted/modified devices (e.g. modify the update.zip itself to bypass whatever checks it performs)?
Same problem here- only had a custom recovery and root. brought back the stock recovery and did full unroot from SuperSu.
OTA update installtion stops with "Error".
Just flash the system image from the update.
Sent from my Nexus 5 using Tapatalk
Thanks, I ended up doing this http://forum.xda-developers.com/showpost.php?p=62288667&postcount=196
(flashing stock system, boot and recovery from my current version, letting OTA update install and re-rooting according to http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905)
I guess i could have flashed the new version just the same.