root and OTA's - T-Mobile HTC One (M9)

Hello guys. Need to root m9 t-mobile and get OTA's in future. Is it real? Thanks in advance.

Sirocco.ukr.lviv said:
Hello guys. Need to root m9 t-mobile and get OTA's in future. Is it real? Thanks in advance.
Click to expand...
Click to collapse
Once you root, the system partition gets modified and OTA's will fail.
What you can do is flash TWRP 2.8.6.4 first and make a system backup BEFORE rooting. Once you make a backup, go flash super su in TWRP so you have root. Now when an OTA comes out, you can use TWRP to restore the backup and the system image becomes stock again and the OTA will flash... after you can re-root in TWRP.

Related

[Q] Verizon DE Software Upgrade Q

If I have the Verizon DE Moto X, do I need to be stock (no root) and re-locked bootloader to get software updates? Or just one or the other? Neither?
Thanks,
Mike
Mike7143 said:
If I have the Verizon DE Moto X, do I need to be stock (no root) and re-locked bootloader to get software updates? Or just one or the other? Neither?
Thanks,
Mike
Click to expand...
Click to collapse
You need stock /system partition and stock recovery. It doesn't matter whether the bootloader is locked or unlocked.
Mike7143 said:
If I have the Verizon DE Moto X, do I need to be stock (no root) and re-locked bootloader to get software updates? Or just one or the other? Neither?
Thanks,
Mike
Click to expand...
Click to collapse
To install? or to be notified and receive the update?
To receive the update you'll need to be running the "stock" Verizon firmware, rooted/unrooted and bootloader locked/unlocked doesn't matter.
For it to install successfully, to expand on what kbluhm posted...
Keep in mind that usually OTA updates will look for certain files to be present on your phone and verify their size and check sums (MD5 or the like) before the OTA update will install. If files are missing or changed, the ota update will fail. That is why "stock /system" is required.
And "stock recovery" is needed because when the phone reboots to install the update, it tries to boot to stock recovery and run the install script. The 3rd party recoveries don't seem to work, or have errors, when installing the OTA update zips.
If you've rooted with SlapMyMoto, RockMyMoto, or thel like, you may have other issues to deal with in order to take any OTA updates since those processes can touch other files/partitions on the phone which will cause problems with the OTA Updates.
So in order to install the update I need to re-flash the stock recovery over TWRP, correct? How do I go about doing this?
Ah okay, thanks guys. What a hassle. I'm unlocked and using TWRP, flashed a new boot logo, and am rooted. Probably just easiest to just SBF back to stock and re-do everything.
Thanks!
You could grab the factory image from Motorola and flash only system and recovery using fastboot. That is my plan. You can find the zip file on Motorola's site or there is a topic here on XDA.
Sent from my XT1060 using Tapatalk
guitarbedlam said:
So in order to install the update I need to re-flash the stock recovery over TWRP, correct? How do I go about doing this?
Click to expand...
Click to collapse
Mike7143 said:
Ah okay, thanks guys. What a hassle. I'm unlocked and using TWRP, flashed a new boot logo, and am rooted. Probably just easiest to just SBF back to stock and re-do everything.
Thanks!
Click to expand...
Click to collapse
There are several threads about using Fastboot to flash recovery or parts of the rom rather than having to use RSDLite and flash the SBF of everything..
Example: see option 2 in -> http://forum.xda-developers.com/showthread.php?t=2536735
KidJoe said:
There are several threads about using Fastboot to flash recovery or parts of the rom rather than having to use RSDLite and flash the SBF of everything..
Example: see option 2 in -> http://forum.xda-developers.com/showthread.php?t=2536735
Click to expand...
Click to collapse
Thus, all I'd have to flash (I'm stock unlocked rooted) is the recovery and I'd be good to install the update. Then install the custom recovery and install the superuser zip. and BAM. But first I need the whole 4.4.2 update thing...
guitarbedlam said:
Thus, all I'd have to flash (I'm stock unlocked rooted) is the recovery and I'd be good to install the update. Then install the custom recovery and install the superuser zip. and BAM. But first I need the whole 4.4.2 update thing...
Click to expand...
Click to collapse
Sure, we need the 4.4.2 update.
And as long as you didn't delete any stock apps/apk's, freeze them with Titanium Backup or something similar, or rename them manually (and forgot to rename them back)... then yes.. just flash stock recovery, take update, flash TWRP and use SuperSU to re-root.
KidJoe said:
Sure, we need the 4.4.2 update.
And as long as you didn't delete any stock apps/apk's, freeze them with Titanium Backup or something similar, or rename them manually (and forgot to rename them back)... then yes.. just flash stock recovery, take update, flash TWRP and use SuperSU to re-root.
Click to expand...
Click to collapse
You can freeze them all you want and leave them frozen. They are still there, untouched, waiting to be checked/verified against and patched/updated. Once you obtain root again and grant it to Titanium Backup it will be re-frozen.
You just can't delete, rename or swap out.....frozen apps are still right there as normal.
tcrews said:
You can freeze them all you want and leave them frozen. They are still there, untouched, waiting to be checked/verified against and patched/updated. Once you obtain root again and grant it to Titanium Backup it will be re-frozen.
You just can't delete, rename or swap out.....frozen apps are still right there as normal.
Click to expand...
Click to collapse
Interesting. One of the issues reported with the Kit Kat update was the OTA failing due to apps frozen with Titanium Backup. I only "disable" via the stock app manager, so I haven't had a problem.
Most likely those with failures had modified/deleted/renamed something else that was causing the issues and blaming it on the frozen apps. I have updated every device I've had with frozen apps. Freezing, at least in Titanium Backup, tells the OS the app is not available. In recovery, the OS is not loaded and knows nothing about frozen apps. Titanium doesn't touch the actual files so they are still present to be patched by the OTA.
Sent from my Nexus 10

[Q] Dev Edition - Root but keep OTA?

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

[Closed] Root and OTAs

Noob question: Will root and custom recovery break stock ROM?
NoobER question: How about play store updates?
xtalks said:
Noob question: Will root and custom recovery break stock ROM?
NoobER question: How about play store updates?
Click to expand...
Click to collapse
you need stock recovery to install ota updates
unlocking the bootloader will wipe /data/preload content and you'll be unable to install ota (except if you restore the content of that folder)
any modification to /system files will also prevent ota to install.
root and custom recovery will not prevent playstore updates.
Thanks @alray
Follow up question though, will it say that I have an OTA update in settings/about but won't be able to install it or totally no notifications?
xtalks said:
Thanks @alray
Follow up question though, will it say that I have an OTA update in settings/about but won't be able to install it or totally no notifications?
Click to expand...
Click to collapse
you'll still have notification and you'll also be able to download the ota but it will fail if you are using a custom recovery. It can also fail with stock recovery if some files were modified or deleted in /system or in /data/preload. you'll see a red triangle with an exclamation mark inside : ota install failed

[Q] Install 5.1 OTA if rooted and bootloader unlocked?

Hi guys !
I unlocked my bootloader and rooted my device, and i don't know if i can upgrade my Nexus 6 by ota (received this morning on the phone) without brick it.
Is it dangerous?
Thank you
EDIT : I'm on stock Lollipop 5.0.1
Unlocked is fine. If you have root or any other system mods, you'll need to remove them.
Oh thanks for the quick answer
So if I unroot it with Nexus Root Toolkit it will be ok?
Midsylen said:
Oh thanks for the quick answer
So if I unroot it with Nexus Root Toolkit it will be ok?
Click to expand...
Click to collapse
Nexus toolkit doesn't unroot. It reflashes the entire phone which also means root disappears. If you're going to do that, no point taking the ota. Just flash full update.
You can indoor via the SuperSU app.
Oh ok I just saw that.
So if I unroot via SuperSU it's ok i can install?
Midsylen said:
Oh ok I just saw that.
So if I unroot via SuperSU it's ok i can install?
Click to expand...
Click to collapse
As long as you do the full unroot and made no other modifications. Oh and everything must be 100% stock, including recovery
I've installed TWRP...
So, what is the best way for me to install 5.1 without losing my data?
Midsylen said:
I've installed TWRP...
So, what is the best way for me to install 5.1 without losing my data?
Click to expand...
Click to collapse
download the factory image that you want to update to.
extract the system.img, boot.img and radio.img
Fastboot flash them.
You could also flash the bootloader if you want though I dont see any point.
Ok, thank you for your quick answers

[Q] rooted, unlocked, TWRP recovery, stock, Verizon OTA help

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.

Categories

Resources