If I root the latest stock 4.4.2, will I still be able to get future OTA Updates without braking the root or custom recovery, well if root gets lost I can always root it again. Just asking, maybe I won't be able to get OTA Updates at all after rooting but I don't know so that's why I'm asking it here.
KuGeL94 said:
If I root the latest stock 4.4.2, will I still be able to get future OTA Updates without braking the root or custom recovery, well if root gets lost I can always root it again. Just asking, maybe I won't be able to get OTA Updates at all after rooting but I don't know so that's why I'm asking it here.
Click to expand...
Click to collapse
Yes!
SWTR said:
Yes!
Click to expand...
Click to collapse
Indeed.
KuGeL94 said:
If I root the latest stock 4.4.2, will I still be able to get future OTA Updates without braking the root or custom recovery, well if root gets lost I can always root it again. Just asking, maybe I won't be able to get OTA Updates at all after rooting but I don't know so that's why I'm asking it here.
Click to expand...
Click to collapse
The OTA will download but not install. You need stock recovery AND any system file that is updated by the OTA needs to be stock as well otherwise OTA install will fail.
Plenty of threads on XDA speak of this.
If you look at the OTA updater file you will see if uses MD5 (or similar) to check each system file it updates to make sure its as it was originally.
When you root it alters some system files.
Best thing is to install custom recovery and take a backup before rooted. Then root. When you get an OTA just restore backup and flash stock recovery. Then OTA will re-download. Let it install, then flash custom recovery and re-root.
Thanks, well I'll just stay unrooted and make the best out of it, the Moto G is just as amazing as Motorola developed it to be.
No stock recovery it's no need. I updated last ota with Philz recovery without problems.
denzel09 said:
No stock recovery it's no need. I updated last ota with Philz recovery without problems.
Click to expand...
Click to collapse
Do you mean you downloaded OTA and flashed manually via recovery. You can do that I agree, but what you can't do is let OTA install naturally the way Motorola intended.
No. I had Philz recovery. System stock partition. Downloaded ota normally, reboot like ota update ask, phone reboots in philz recovery and this last flash ota automatically without any problem. There is not need to reflash stock recovery or flash ota update manually with custom rec, only need a non root stock system partition. I dont know if stock cwm or other rec like twrp work in same way but i doubt, always used only philz recovery.
You do not need stock recovery, I don't know who made this stupid rumour up. I use twrp and it flashes fine.
Sent from my Google Nexus G -
Related
I just received my Asus back from being repaired for light bleed. It still has bleed but what can i do? It came back loaded with 8.6.5.9. Should I try to OTA update to 8.6.5.13 and root with the universal root? It is a B30 rooted previously.
Thanks
As far as the light bleed...I would say let it go. Most of us are dealing with the light bleed as well....its not a great thing but it really isn't a big deal either. Be happy that you have a TF that's rootable at this point. The root kit v7.1 claims to be able to root 8.6.5.x. So if all you want is root, then go ahead and update first, then root using that method. If you do not install clockworkmod recovery, you may be able to receive OTA updates, but will loose root and will have to be re-rooted. Another option is to root, install clockworkmod recovery, and update via a zip flash posted in the dev section. Once you install clockworkmod reovery, you won't be able to receive OTA updates and will have to rely on getting a cwm recovery flashable zip for updates. Or you can root, ainstall CWM recovery, and install a custom rom, which they will always include the latest OTA update builds. Its up to you.
Thank you. I should have known, but I did not know that the CVM was the reason I could not OTA update. I always thought it was the root itself.
Thanks for this info. I'm on it.
Yes you should be able to get it to work correctly
frankc123 said:
Yes you should be able to get it to work correctly
Click to expand...
Click to collapse
Thanks frankc123. Did it. Rooted and back in business!
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
Hey guys. So I am running 4.4.4 right now on my XT1033. Waiting for 5.0 now. However, I wanna root my phone now but I have some questions related to the update that I wanna clear first.
1, I already have unlocked my boot loader, will that affect my phone in receiving the OTA update?
2, Can I root my phone without removing the stock recovery, since I won't be flashing ROMs now and I wouldn't need it.
3, If I can't root without removing the stock recovery, how can I go back to stock recovery?
4, In order to update, do I have to unroot and lock the boot loader again or is that not necessary?
That's all. Keep in mind that my main concern is that I want root along with, when the time comes, the OTA update installation without any problems.
I am new at this so please bear with me. Hoping for an early reply, thank you.
Anyone?
drag00n619 said:
Hey guys. So I am running 4.4.4 right now on my XT1033. Waiting for 5.0 now. However, I wanna root my phone now but I have some questions related to the update that I wanna clear first.
1, I already have unlocked my boot loader, will that affect my phone in receiving the OTA update?
2, Can I root my phone without removing the stock recovery, since I won't be flashing ROMs now and I wouldn't need it.
3, If I can't root without removing the stock recovery, how can I go back to stock recovery?
4, In order to update, do I have to unroot and lock the boot loader again or is that not necessary?
That's all. Keep in mind that my main concern is that I want root along with, when the time comes, the OTA update installation without any problems.
I am new at this so please bear with me. Hoping for an early reply, thank you.
Click to expand...
Click to collapse
1. There's no problem with unlocked bootloader in order to receive the OTA.
2. There's a method to root without modifying recovery. Search for "root moto g modaco" on google, and choose "option 1, superboot". (Since I am a junior member I cannot submit links) :crying:
3. You can also change recovery using fastboot or Mototools, flash supersu.zip and then flash stock recovery again using mototools, which is prepared to flash cwm, twrp or stock recovery,
4. You don't need to re-lock bootloader in order to update
Anyway, I read that you can receive the OTA being root, but only if you have not modifyied system (i.e removing system apk's) nor modifying kernel.
Hope this was useful!
arya5 said:
1. There's no problem with unlocked bootloader in order to receive the OTA.
2. There's a method to root without modifying recovery. Search for "root moto g modaco" on google, and choose "option 1, superboot". (Since I am a junior member I cannot submit links) :crying:
3. You can also change recovery using fastboot or Mototools, flash supersu.zip and then flash stock recovery again using mototools, which is prepared to flash cwm, twrp or stock recovery,
4. You don't need to re-lock bootloader in order to update
Anyway, I read that you can receive the OTA being root, but only if you have not modifyied system (i.e removing system apk's) nor modifying kernel.
Hope this was useful!
Click to expand...
Click to collapse
Thank you, that really helped. And yea, I won't be messing around with the system apps, just gonna install Xposed.
2 more questions though
1, Is it possible to flash the stock recovery from CWM?
2, I read somewhere that the stock recovery can be extracted from the ROM of your phone. Is that true? That means that I can make a backup of my current ROM and also have the stock recovery with me, right?
Once again, thanks!
drag00n619 said:
Thank you, that really helped. And yea, I won't be messing around with the system apps, just gonna install Xposed.
2 more questions though
1, Is it possible to flash the stock recovery from CWM?
2, I read somewhere that the stock recovery can be extracted from the ROM of your phone. Is that true? That means that I can make a backup of my current ROM and also have the stock recovery with me, right?
Once again, thanks!
Click to expand...
Click to collapse
A recovery can be flashed from recovery, but only if you have it on a flashable zip, if you have it on img format, you need to use mototools or fastboot from pc. This second option is more recommendable
Concerning second question, I think I don't understand you. Original recovery can be found at the original firmware, this means that if you flash the original stock firmware it comes with the stock recovery, but I am not sure that you will recover stock recovery restoring a previous backup. Sorry
So I'm having an issue with updating my phone.
I have tried reading all of the threads, but so many things are still a mystery and are confusing. I haven't been able to get a full understanding of all of this.
I have a LG G5 H830 10a T-Mobile variant.
I am running Android 6.0.1
I have a custom recovery of TWRP
My phone is rooted with SuperSU also.
All I want to do, is to update my phone to Nougat. What is the process I have to go through? After reading all about it, here is my assumption:
I download Flashfire and use DisableService to disable my root and SuperSu, then I run the OTA Nougat update...
That didn't work. I got an error from TWRP that said:
"unable to flash update.zip from cache/update.zip, update is meant for "h1" device, your device is an H830"
Or something along those lines.
I have a Nandroid backup, so I'm not worried if I brick or soft brick it.
Any help please?
Thanks!
technocrat7 said:
So I'm having an issue with updating my phone.
I have tried reading all of the threads, but so many things are still a mystery and are confusing. I haven't been able to get a full understanding of all of this.
I have a LG G5 H830 10a T-Mobile variant.
I am running Android 6.0.1
I have a custom recovery of TWRP
My phone is rooted with SuperSU also.
All I want to do, is to update my phone to Nougat. What is the process I have to go through? After reading all about it, here is my assumption:
I download Flashfire and use DisableService to disable my root and SuperSu, then I run the OTA Nougat update...
That didn't work. I got an error from TWRP that said:
"unable to flash update.zip from cache/update.zip, update is meant for "h1" device, your device is an H830"
Or something along those lines.
I have a Nandroid backup, so I'm not worried if I brick or soft brick it.
Any help please?
Thanks!
Click to expand...
Click to collapse
You're not going to be able to update to Android N yet if you want to keep twrp and root. Only way to do it currently is if you have 100% stock phone and update via ota or using the zip file that was posted. If you don't care about root or twrp, update to 10j using the complete zip that autoprime posted and don't install SuperSU or dm-verity and let boot. You will have 100% stock and can take ota or use zip method. *** There is no current way to get root or twrp for t mobile version once on official android N yet *** So if root and twrp are important just wait until autoprime gets a chance to upload the flashable zip files for N to flash in twrp. You could also use cm or cm based Roms if you want android N, plus those are 7.1 stock is only 7.0, but if you want stock rooted just have to wait until it's released.
jeffsga88 said:
You're not going to be able to update to Android N yet if you want to keep twrp and root. Only way to do it currently is if you have 100% stock phone and update via ota or using the zip file that was posted. If you don't care about root or twrp, update to 10j using the complete zip that autoprime posted and don't install SuperSU or dm-verity and let boot. You will have 100% stock and can take ota or use zip method. *** There is no current way to get root or twrp for t mobile version once on official android N yet *** So if root and twrp are important just wait until autoprime gets a chance to upload the flashable zip files for N to flash in twrp. You could also use cm or cm based Roms if you want android N, plus those are 7.1 stock is only 7.0, but if you want stock rooted just have to wait until it's released.
Click to expand...
Click to collapse
Ohh okay, perfect thank you!
With that in mind, I had another question..
I have an LG V20 as well.
One thing I was thinking of doing was the following:
Unlocking the bootloader, putting a custom recovery like TWRP on it.
Make a Nandroid backup.
Then root it, and then go about my business. If something like this happens again and I want to update, I can simply do a Titanium Backup go to my Nandroid backup, restore it. Then update OTA, then reroot, run titanium backup restore, and then I'll be back where I left off.
will that work?
And one last question:
How would I go back to factory settings on my LG G5?
technocrat7 said:
Ohh okay, perfect thank you!
With that in mind, I had another question..
I have an LG V20 as well.
One thing I was thinking of doing was the following:
Unlocking the bootloader, putting a custom recovery like TWRP on it.
Make a Nandroid backup.
Then root it, and then go about my business. If something like this happens again and I want to update, I can simply do a Titanium Backup go to my Nandroid backup, restore it. Then update OTA, then reroot, run titanium backup restore, and then I'll be back where I left off.
will that work?
And one last question:
How would I go back to factory settings on my LG G5?
Click to expand...
Click to collapse
I'm not 100% sure but I don't think that would work as once you install twrp it modifies the recovery. IMG which would cause ota to fail. But on the other hand, you could most likely do the same method as the g5 to go back to official and take ota. Flashing the complete zip (if those are being created for the v20, haven't checked that thread as I don't own that device) and not re-installing the dm-verity or SuperSU will always reinstall the original boot.img and recovery.img and be 100% official stock. Hope this helps.
jeffsga88 said:
I'm not 100% sure but I don't think that would work as once you install twrp it modifies the recovery. IMG which would cause ota to fail. But on the other hand, you could most likely do the same method as the g5 to go back to official and take ota. Flashing the complete zip (if those are being created for the v20, haven't checked that thread as I don't own that device) and not re-installing the dm-verity or SuperSU will always reinstall the original boot.img and recovery.img and be 100% official stock. Hope this helps.
Click to expand...
Click to collapse
Thanks!
That helps a ton.
What is dm-verity though?
technocrat7 said:
Thanks!
That helps a ton.
What is dm-verity though?
Click to expand...
Click to collapse
The zip file we flash to disable force encryption (now this is part of the latest SuperSU zips).
jeffsga88 said:
The zip file we flash to disable force encryption (now this is part of the latest SuperSU zips).
Click to expand...
Click to collapse
Can you link to the latest superuser? Just wanna have it on hand for when the H830 N zip drops
carnivalrejectq said:
Can you link to the latest superuser? Just wanna have it on hand for when the H830 N zip drops
Click to expand...
Click to collapse
Here's the link to chainfires thread which will always have the latest beta supersu versions:
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Hello, will it be possible to return from custom firmware to the original one and continue to receive OTA update ?
Uxlewl said:
Hello, will it be possible to return from custom firmware to the original one and continue to receive OTA update ?
Click to expand...
Click to collapse
Yes, if you used TWRP to create a backup of your stock ROM before you flashed a custom ROM, you just use TWRP to restore the backup of stock ROM.
Or, if you didn't use TWRP to backup your stock ROM, you can flash your device's stock firmware using the flashtool designed to be used with devices made by your device's manufacturer.
But to install TWRP you need Root, and if you get it, then OTA updates stop coming or am I wrong?
Uxlewl said:
But to install TWRP you need Root, and if you get it, then OTA updates stop coming or am I wrong?
Click to expand...
Click to collapse
No, installing TWRP does not require root. Yes, TWRP and root prevent the installation of OTA updates.
That is, to make a backup copy of the original firmware, you need TWRP, but if you install it, you lose the ability to receive OTA updates, and if you restore the original after the custom firmware, there will be no updates? Or can TWRP be removed and OTA updates will come again? I'm sorry I do not understand.
Uxlewl said:
That is, to make a backup copy of the original firmware, you need TWRP, but if you install it, you lose the ability to receive OTA updates, and if you restore the original after the custom firmware, there will be no updates? Or can TWRP be removed and OTA updates will come again? I'm sorry I do not understand.
Click to expand...
Click to collapse
To be more specific, installing TWRP does not necessarily prevent a device from actually receiving/downloading OTA updates, it prevents the actual installation of OTA updates because part of the OTA update includes automatically booting into stock recovery to apply the update. If you have TWRP installed, the OTA update can possibly be downloaded to the device but when the device automatically tries to reboot into recovery, it is trying to boot into stock recovery but if you have TWRP installed, it can't boot into stock recovery to apply the update and when it tries to boot into TWRP, it will try to apply the update but it will fail, resulting in a bricked device and the device will have to be restored.
When it comes to OTA updates, all that is required is an unmodified stock system partition(meaning, no root or any other kind of modifications to the system partition), stock recovery(meaning, no TWRP) and the update has to be offered by your carrier if they offer the update for your specific device.
If a device is rooted, has other system modifications and/or has TWRP installed and you want to apply a stock OTA update, you have to remove root and any other system modifications and you must replace TWRP with the original stock recovery before you can apply the update. If you have TWRP and or root and you remove them to apply an OTA update, you can root the device again and install TWRP again after the update, provided that the OTA does not come with a locked bootloader that can not be unlocked, in this case, you will not be able to reinstall TWRP or root because the bootloader will be locked, which prevents you from installing TWRP again. Sometimes, users remove root and TWRP to apply OTA updates with the intention of rooting and/or installing TWRP again after the update but then get stuck in a position where they can no longer root the device or install TWRP because the bootloader gets locked during the update and there is no way to unlock the newly updated bootloader, from then on, they are stuck with stock with no way to get root, TWRP and custom ROMs reapplied to the device because they were not aware that the update came with a locked bootloader that can not be unlocked by any means.