Related
I have sucessfully converted my AT&T HTC One to the Developers Edition. If install TWRP and root the device, then re-install the stock recovery, can I maintain the ability to receive OTA Updates?
Also can someone confirm that the 4.06.1540 recovery is the latest for 4.4.2 sense 6? (Found Here http://forum.xda-developers.com/showthread.php?t=2545227)
Or if there is a better way to accomplish root etc.
Thank you in advance.
sednafx said:
I have sucessfully converted my AT&T HTC One to the Developers Edition. If install TWRP and root the device, then re-install the stock recovery, can I maintain the ability to receive OTA Updates?
Also can someone confirm that the 4.06.1540 recovery is the latest for 4.4.2 sense 6? (Found Here http://forum.xda-developers.com/showthread.php?t=2545227)
Or if there is a better way to accomplish root etc.
Thank you in advance.
Click to expand...
Click to collapse
That is a good recovery to have in place *before* you start checking for the latest 5.x.x.x OTA. Technically it's not the "latest" (the latest one would be the one you will end up with *after* the OTA) but it's the right one for your situation.
Overall the short answer to your question is yes, you can get OTA's with this plan.
If you remove anything from /system you might not.
If you do more stuff (like downgrading HBOOT, installing a custom kernel, whatever) you might not.
But for most people in your situation, you'll get OTA's.
Generally.
Enjoy.
sednafx said:
I have sucessfully converted my AT&T HTC One to the Developers Edition. If install TWRP and root the device, then re-install the stock recovery, can I maintain the ability to receive OTA Updates?
Also can someone confirm that the 4.06.1540 recovery is the latest for 4.4.2 sense 6? (Found Here http://forum.xda-developers.com/showthread.php?t=2545227)
Or if there is a better way to accomplish root etc.
Thank you in advance.
Click to expand...
Click to collapse
The best thing to do is a nandroid of your stock rom & recovery prior to installing TWRP and obtaining root. If you need to go back to stock you will have it. I haven't seen the stock recovery for 4.4.2 sense 6, it should be 5.11.1540.9.
majmoz said:
The best thing to do is a nandroid of your stock rom & recovery prior to installing TWRP and obtaining root. If you need to go back to stock you will have it. I haven't seen the stock recovery for 4.4.2 sense 6, it should be 5.11.1540.9.
Click to expand...
Click to collapse
Sure it is but unfortunately if has not been possible to (fastboot boot recovery.zip) since hboot 1.44
The best most people can do is after taking the update reflash TWRP and make a backup including recovery. then download and keep the stock recovery with it.
Thank you all for the response. Here is what I would like to do:
1. Backup my existing recovery through adb using the #dd command. Anyone know the correct syntax?
2. Install TWRP and backup the existing unrooted ROM.
3. Root the device. Do not remove any files from /system, no custom kernels (doesn't really matter since I will restore backup). Simply use titanium back to restore my apks and freeze the ones I don't use. I would like to install Xposed though.....
4. See OTA Update. Backup apks, restore unrooted. Restore stock recovery through adb. Anyone know why the syntax??
5. Run the OTA Update.
6. Profit.... Go back to step 1.
What do you all think? Any help with the syntax to dump and restore stock recovery?
Sent from my HTC One using Tapatalk
sednafx said:
1. Backup my existing recovery through adb using the #dd command. Anyone know the correct syntax?
Click to expand...
Click to collapse
doesn't know the #dd command but recovery can be extracted from the firmware package inside the ota.zip
anyway, I have all the latest dev edition recovery so you'll save a little time:
4.06.1540.2 MD5: 2bb3d9df9ce8c8329db8d22781613e2c
4.06.1540.3 MD5: 87eaf7d4a9c4ba1108bf26164b1f3f3d
4.19.1540.4 MD5: 6e25ef0e614c41722b2fb4afbdde5d7c
4.19.1540.9 MD5: b4d31a181a9e44225dc83282bc1bf134
5.11.1540.9 MD5: c487a17382e2e1c207efae66fed00925
you need the one that match your actual version
2. Install TWRP and backup the existing unrooted ROM.
Click to expand...
Click to collapse
Always a good thing to do, also make a copy of that backup on your computer.
3. Root the device. Do not remove any files from /system, no custom kernels (doesn't really matter since I will restore backup). Simply use titanium back to restore my apks and freeze the ones I don't use. I would like to install Xposed though.....
Click to expand...
Click to collapse
no problem using xposed and receiving ota updates
4. See OTA Update. Backup apks, restore unrooted. Restore stock recovery through adb. Anyone know why the syntax??
Click to expand...
Click to collapse
no need to restore your backup if you didnt modified/deleted /system or /preload files and your kernel is stock. Just restore your recovery
Code:
fastboot flash recovery name_of_file.img
fastboot erase cache
fastboot reboot
5. Run the OTA Update.
6. Profit.... Go back to step 1.
Click to expand...
Click to collapse
Sent from my HTC One using Tapatalk[/QUOTE]
More Questions on Receiving OTA's
@alray On Step 4, to receive the OTA's, in addition to restoring stock recovery, wouldn't it be necessary to unroot the device and disable Xposed?
gingerlindsey said:
@alray On Step 4, to receive the OTA's, in addition to restoring stock recovery, wouldn't it be necessary to unroot the device and disable Xposed?
Click to expand...
Click to collapse
no need to unroot to be able to apply the ota but you might loose root after the update, in that case, root again after the update.
I have updated mine many times with xposed still enabled and didnt have any issue. But you might want to disable module like ''sense 5 toolbox'' when updating to sense 6... Anyway if you want to be safe, yes you can disable xposed but this is not required.
@alray Thank you very much! I was unrooting and disabling Xposed, etc. Good to know I can "Keep it Simple"!
@alray The link for the latest recovery is 404ed. Can you repost? EDIT: Nevermind. Removed the [/HIDE] from the link and it worked.
Where is the OTA saved BTW?
Thanks again for all the advise. I may update the OP to outline these in detail.
The ota is saved to /sdcard/downloads
Sorry for the bad link, it should work now
Sent from my HTC One using XDA Free mobile app
alray said:
The ota is saved to /sdcard/downloads
Sorry for the bad link, it should work now
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
That path makes perfect sense.... I feel like captain obvious smacked me in the face..... Thanks!!!!!
Sent from my HTC One using Tapatalk
Hello everyone, I'm new here, my nexus 6 is on stock 5.0.1 and waiting for update to 5.1, here are my concerns.
1. How can I root my phone without unlock boot loader or flash a twrp recovery( I Know if I got a twrp recovery, I can not get OTA).
2. If I need unlock boot loader in order to root, could this affect ota?
3. If I rooted my phone, can I get ota in the future?
Thanks.
Dennypalace said:
Hello everyone, I'm new here, my nexus 6 is on stock 5.0.1 and waiting for update to 5.1, here are my concerns.
1. How can I root my phone without unlock boot loader or flash a twrp recovery( I Know if I got a twrp recovery, I can not get OTA).
2. If I need unlock boot loader in order to root, could this affect ota?
3. If I rooted my phone, can I get ota in the future?
Thanks.
Click to expand...
Click to collapse
1. You can't 2. No can be unlocked and still do the ota 3. YES!
nms247 said:
1. You can't 2. No can be unlocked and still do the ota 3. YES!
Click to expand...
Click to collapse
Thanks. So this means if I want to root my phone, I will have to unlock boot loader. And is there anything I can do if I want to update through OTA after I rooted and unlocked my phone?
Dennypalace said:
Thanks. So this means if I want to root my phone, I will have to unlock boot loader. And is there anything I can do if I want to update through OTA after I rooted and unlocked my phone?
Click to expand...
Click to collapse
As long as you flash the stock recovery before an ota you'll be fine
Actually any system modification including root on Lollipop will prevent an OTA so in answer to question 3, no.
Basically need to flash stock system.img, recovery.img and stock boot (if you changed the kernel).
At least thats what I'm about to do.
y2whisper said:
Basically need to flash stock system.img, recovery.img and stock boot (if you changed the kernel).
At least thats what I'm about to do.
Click to expand...
Click to collapse
Correct. That's exactly what I did, and it worked.
rootSU said:
Actually any system modification including root on Lollipop will prevent an OTA so in answer to question 3, no.
Click to expand...
Click to collapse
Weird as I took the OTA while rooted.
Still working on it on my end. Drivers aren't installed for add sideboard trying to figure it out
OK so I rooted my 6 but no longer need it. I want to unroot and relock soI can get OTA updates for my 6. I also have a nexus 7 I need to do the same with.
Can someone help please.
Flash factory image.. Guide in general forum.
Kildimo89 said:
OK so I rooted my 6 but no longer need it. I want to unroot and relock soI can get OTA updates for my 6. I also have a nexus 7 I need to do the same with.
Can someone help please.
Click to expand...
Click to collapse
And don't relock your bootloader. It is not necessary to take the OTA.
rootSU said:
Flash factory image.. Guide in general forum.
Click to expand...
Click to collapse
I flashed stock 5.1 on my Nexus 7 the other night so should it be able to get OTA now?
I am currently in 5.1 for my Nexus 6 so should I just re flash 5.1 again to remove root and re-enable OTA?
Thanks for your help guys and I will not lock seeing as its not necessary.
http://forum.xda-developers.com/nexus-6/general/guide-safely-lock-bootloader-android-5-1-t3067302
Kildimo89 said:
I flashed stock 5.1 on my Nexus 7 the other night so should it be able to get OTA now?
I am currently in 5.1 for my Nexus 6 so should I just re flash 5.1 again to remove root and re-enable OTA?
Thanks for your help guys and I will not lock seeing as its not necessary.
Click to expand...
Click to collapse
"Removing" root via SuperSU app is insufficient. You will need to fastboot flash the system.img. If you have a modified kernel, you will have to fastboot flash the stock boot.img
I have a Verizon Nexus 6 that is rooted, unlocked, custom TWRP recovery and stock running 5.1 build LMY47E and I am getting the OTA notification for the 5.1.1 update. I have searched a good deal of places and haven't found the answer to how I might go about getting the update. I have been out of the rooting game for several years, so I am rusty and need a little help. I wasn't sure if there was a way to take the update and stay rooted or if I have to completely undo everything back to stock. Any info would be a great help and appreciated.
I could be mistaken, but I don't think that you can take an OTA amd remain rooted. I think it will break root, and you will have to re-root.
What I would suggest is to just flash a custom ROM that is build on 5.1.1 like Beans' PureNexus. That is what I am running, and it is great.
http://forum.xda-developers.com/nexus-6/development/rom-pure-nexus-project-t3148214
evolefty said:
I have a Verizon Nexus 6 that is rooted, unlocked, custom TWRP recovery and stock running 5.1 build LMY47E and I am getting the OTA notification for the 5.1.1 update. I have searched a good deal of places and haven't found the answer to how I might go about getting the update. I have been out of the rooting game for several years, so I am rusty and need a little help. I wasn't sure if there was a way to take the update and stay rooted or if I have to completely undo everything back to stock. Any info would be a great help and appreciated.
Click to expand...
Click to collapse
a.demarco said:
I could be mistaken, but I don't think that you can take an OTA amd remain rooted. I think it will break root, and you will have to re-root.
What I would suggest is to just flash a custom ROM that is build on 5.1.1 like Beans' PureNexus. That is what I am running, and it is great.
http://forum.xda-developers.com/nexus-6/development/rom-pure-nexus-project-t3148214
Click to expand...
Click to collapse
When installing a recovery, the updater script looks at system and boot. This means that you can not be rooted and and have the stock, encrypted kernel. You also need to have stock recovery to install the OTA.
You can download the 5.1.1 factory image from Google and flash the boot.img, system.img, bootloader.img, and radio.img. Then, while still in bootloader, select "recovery" and you will boot to TWRP where you can flash the SuperSU.zip.
a.demarco said:
I could be mistaken, but I don't think that you can take an OTA amd remain rooted. I think it will break root, and you will have to re-root.
What I would suggest is to just flash a custom ROM that is build on 5.1.1 like Beans' PureNexus. That is what I am running, and it is great.
http://forum.xda-developers.com/nexus-6/development/rom-pure-nexus-project-t3148214
Click to expand...
Click to collapse
The OTA will not install when the device is rooted
cam30era said:
When installing a recovery, the updater script looks at system and boot. This means that you can not be rooted and and have the stock, encrypted kernel. You also need to have stock recovery to install the OTA.
You can download the 5.1.1 factory image from Google and flash the boot.img, system.img, bootloader.img, and radio.img. Then, while still in bootloader, select "recovery" and you will boot to TWRP where you can flash the SuperSU.zip.
Click to expand...
Click to collapse
Just checked again and yes I am rooted, with TWRP and I also checked and the device is not encrypted, so maybe that is why I am getting the notification. I really appreciate your input on getting the update installed.
evolefty said:
Just checked again and yes I am rooted, with TWRP and I also checked and the device is not encrypted, so maybe that is why I am getting the notification. I really appreciate your input on getting the update installed.
Click to expand...
Click to collapse
You'll get the notification. You just can't flash it.
I'm not sure there's been a full, satisfactory answer to this thread (or a few others). Would using something like Nexus Root Toolkit to 1) unroot 2) restore stock recovery, 3) accept the OTA. Will this work?
- Does this relock the bootloader? (Would we then have to unlock, thus wiping the device?)
- Can we successfully re-root and flash recovery? (Or will new 5.1.1 versions be needed?)
At some point, to get 5.1.1 going, should I just backup and flash the whole bloody image from Google?
DogzOfWar said:
I'm not sure there's been a full, satisfactory answer to this thread (or a few others). Would using something like Nexus Root Toolkit to 1) unroot 2) restore stock recovery, 3) accept the OTA. Will this work?
- Does this relock the bootloader? (Would we then have to unlock, thus wiping the device?)
- Can we successfully re-root and flash recovery? (Or will new 5.1.1 versions be needed?)
At some point, to get 5.1.1 going, should I just backup and flash the whole bloody image from Google?
Click to expand...
Click to collapse
- OTA`s will not install if the sytem, boot and recovery are modified in any way.
- Reflashing the stock image will NOT lock the bootloader
- And yes you can flash a custom recovery and reroot after updating.
Or flash the latest stock rom with TWRP from here http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052.
gee2012 said:
- OTA`s will not install if the sytem, boot and recovery are modified in any way.
- Reflashing the stock image will NOT lock the bootloader
- And yes you can flash a custom recovery and reroot after updating.
Or flash the latest stock rom with TWRP from here http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052.
Click to expand...
Click to collapse
So the question that started this thread: My system is technically modified. Can I unroot and replace recovery, and now be in a sufficiently "unmodified" state? OR, do I have to lock the bootloader in order for the OTA to continue?
I think the OP and myself are trying to do the same thing: We're lazy, we don't want to wipe, we don't want to lose data, we just want the OTA without having to reflash the whole thing. Does anyone know if this is possible?
DogzOfWar said:
So the question that started this thread: My system is technically modified. Can I unroot and replace recovery, and now be in a sufficiently "unmodified" state? OR, do I have to lock the bootloader in order for the OTA to continue?
I think the OP and myself are trying to do the same thing: We're lazy, we don't want to wipe, we don't want to lose data, we just want the OTA without having to reflash the whole thing. Does anyone know if this is possible?
Click to expand...
Click to collapse
Best/easiest is to:
- fastboot erase system
- fastboot flash system system.img
- flash the stock boot and recovery.img if needed
- adb sideload the OTA in stock recovery
This will not wipe your device
And you don`t have to lock the bootloader ever unless you have too RMA it or send it in for service, OTA`s will even install with a unlocked bootloader.
DogzOfWar said:
So the question that started this thread: My system is technically modified. Can I unroot and replace recovery, and now be in a sufficiently "unmodified" state? OR, do I have to lock the bootloader in order for the OTA to continue?
I think the OP and myself are trying to do the same thing: We're lazy, we don't want to wipe, we don't want to lose data, we just want the OTA without having to reflash the whole thing. Does anyone know if this is possible?
Click to expand...
Click to collapse
Supplementing that: using the "unroot" function in SuperSU is not sufficient with Lollipop. It still leaves the vestiges of a few modified files that will cause an OTA to fail.
gee2012 said:
Best/easiest is to:
- fastboot erase system
- fastboot flash system system.img
- flash the stock boot and recovery.img if needed
- adb sideload the OTA in stock recovery
This will not wipe your device
And you don`t have to lock the bootloader ever unless you have too RMA it or send it in for service, OTA`s will even install with a unlocked bootloader.
Click to expand...
Click to collapse
gee2012 said:
Best/easiest is to:
- fastboot erase system
- fastboot flash system system.img
- flash the stock boot and recovery.img if needed
- adb sideload the OTA in stock recovery
This will not wipe your device
And you don`t have to lock the bootloader ever unless you have too RMA it or send it in for service, OTA`s will even install with a unlocked bootloader.
Click to expand...
Click to collapse
Thanks for the info and I really appreciate your input. What are your feelings on using Wug's toolkit to unroot and go back stock, take the update, then re-root and flash the custom recovery. I have never used a toolkit before, but that seems to be the popular method. Like I said at the beginning I am new to all of this, the last device I rooted and really messed around with was the droid x so bear with me as I am learning. I am currently reading about Wug's and will look at the method you just spoke of, but any info would be great.
evolefty said:
Thanks for the info and I really appreciate your input. What are your feelings on using Wug's toolkit to unroot and go back stock, take the update, then re-root and flash the custom recovery. I have never used a toolkit before, but that seems to be the popular method. Like I said at the beginning I am new to all of this, the last device I rooted and really messed around with was the droid x so bear with me as I am learning. I am currently reading about Wug's and will look at the method you just spoke of, but any info would be great.
Click to expand...
Click to collapse
I don`t like Toolkits tbh because like with all automated applications the unexperienced user has no idea whats going/has zero control over whats happening and if something goes wrong they can`t fix the issue. Imo its best to learn adb/fastboot/sideload.
gee2012 said:
I don`t like Toolkits tbh because like with all automated applications the unexperienced user has no idea whats going/has zero control over whats happening and if something goes wrong they can`t fix the issue. Imo its best to learn adb/fastboot/sideload.
Click to expand...
Click to collapse
Gotcha, and completely understand. I will do some reading on that method and again thanks for your help.
evolefty said:
Gotcha, and completely understand. I will do some reading on that method and again thanks for your help.
Click to expand...
Click to collapse
Read the sticky threads http://forum.xda-developers.com/nexus-6/general/nexus-6-sticky-roll-thread-t3061066, this is a good start. Adb and fastboot isn`t that hard but its very safe and effective
gee2012 said:
Read the sticky threads http://forum.xda-developers.com/nexus-6/general/nexus-6-sticky-roll-thread-t3061066, this is a good start. Adb and fastboot isn`t that hard but its very safe and effective
Click to expand...
Click to collapse
Will do, and that is the method I used to root for the simple fact to learn.
evolefty said:
Will do, and that is the method I used to root for the simple fact to learn.
Click to expand...
Click to collapse
Good luck
gee2012 said:
- OTA`s will not install if the sytem, boot and recovery are modified in any way.
- Reflashing the stock image will NOT lock the bootloader
- And yes you can flash a custom recovery and reroot after updating.
Or flash the latest stock rom with TWRP from here http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052.
Click to expand...
Click to collapse
In that link you sent I am not seeing the VZW version of 5.1.1. Can we use the "International" version?
Thank you.
needoZ said:
In that link you sent I am not seeing the VZW version of 5.1.1. Can we use the "International" version?
Thank you.
Click to expand...
Click to collapse
Yes, use the LMY47Z build.
DogzOfWar said:
So the question that started this thread: My system is technically modified. Can I unroot and replace recovery, and now be in a sufficiently "unmodified" state? OR, do I have to lock the bootloader in order for the OTA to continue?
I think the OP and myself are trying to do the same thing: We're lazy, we don't want to wipe, we don't want to lose data, we just want the OTA without having to reflash the whole thing. Does anyone know if this is possible?
Click to expand...
Click to collapse
Bootloader does not have to be locked to take an OTA. You can not be rooted or modified in any way however.
gee2012 said:
I don`t like Toolkits tbh because like with all automated applications the unexperienced user has no idea whats going/has zero control over whats happening and if something goes wrong they can`t fix the issue. Imo its best to learn adb/fastboot/sideload.
Click to expand...
Click to collapse
While I agree, once you have "paid your dues" and flashed without automation then the NRT is a great tool, so long as you have an understanding of what it is doing.
I did do a search for "November Security Update" but didn't find anything.
Specifically I just received the November Security Update from Google but cannot apply it.
I am running a modified boot image to allow me to root the phone.
Is it possible all I have to do is return to unrooted status (disable SuperSU) and apply this patch?
UPDATE: LOL, that would be a resounding NO. It does say "Error in Recovery" but now the Update is gone.... and the Security Patch level still says 10/1
You have to fastboot flash system.img from factory image. Any OTA is not possible unless you are full stock, unmodified.
Not sure if the security updates end up packaged into system.img or not. If not, you will have to flash stock recovery, system and boot, then accept the OTA then re-flash custom recovery and re-root.
danarama said:
You have to fastboot flash system.img from factory image. Any OTA is not possible unless you are full stock, unmodified.
Not sure if the security updates end up packaged into system.img or not. If not, you will have to flash stock recovery, system and boot, then accept the OTA then re-flash custom recovery and re-root.
Click to expand...
Click to collapse
That's probably what will be needed as the security update is pretty fresh and proabably not in the stock system I would think. And then, to get back to rooted status, I would have to revert to the modified image, thus undoing the application of the security update? Ehhh, not going unrooted, oh well.
And thanks btw
Can't you adb sideload? Isn't that possible when the boot image is modified?
Sent from my Nexus 6 using Tapatalk
swa100 said:
Can't you adb sideload? Isn't that possible when the boot image is modified?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
No.. OTA checks for stock recovery, boot and system. Any amendment it will fail. It's in the zip file regardless of how you apply that zip, it will always fail.
Sent from my Nexus 6 using Tapatalk
I'm lost...please help
So I bought my unlocked Nexus 6 from Amazon. I was probably stupid, and was to impatient to wait for the OTA to Android 6. So I followed the Andriod Central instructions on how to do the basic download adb tools, unlock phone, flashed. the stock Andriod 6 image (MRA58K). And everything went great. I failed to relock, but it didn't seem to be a big deal.
Then I noticed I didn't get the November Security update.
Then I thought I needed to relock the phone. So I booted into the recovery and ran fastboot oem lock.
So now I am back to a fresh phone and I am downloading my apps in Google Play.
But the November Updates didn't come through.
What did I do wrong?
http://forum.xda-developers.com/nexus-6/help/nexus-6-mra58k-n-r-forced-encryption-t3242664/page2
jgriesshaber said:
So I bought my unlocked Nexus 6 from Amazon. I was probably stupid, and was to impatient to wait for the OTA to Android 6. So I followed the Andriod Central instructions on how to do the basic download adb tools, unlock phone, flashed. the stock Andriod 6 image (MRA58K). And everything went great. I failed to relock, but it didn't seem to be a big deal.
Then I noticed I didn't get the November Security update.
Then I thought I needed to relock the phone. So I booted into the recovery and ran fastboot oem lock.
So now I am back to a fresh phone and I am downloading my apps in Google Play.
But the November Updates didn't come through.
What did I do wrong?
Click to expand...
Click to collapse
Locked bootloader has nothing to do with it.