I believe I just rooted very new to this but now I was wondering if i can use a custom recovery.
also i am rooted with superuser and put busybox on too. is there a way to update to new firmware and keep root. I just got this thing today and dont want to mess anything up
shawnten said:
I believe I just rooted very new to this but now I was wondering if i can use a custom recovery.
Click to expand...
Click to collapse
Nope, since we do not have available an unlocked bootloader yet. Once that's availble, you can install custom recoveries and custom ROMs. We're all waiting for that to happen, so join on in. Will take just a few weeks, as most think.
also i am rooted with superuser and put busybox on too. is there a way to update to new firmware and keep root. I just got this thing today and dont want to mess anything up[/QUOTE]
The new firmware will delete root access, but for now, you can just reroot by following the same procedure again. Do not forget to uninstall Superuser/Busybox/SuperSu/whatever other trace may remain, and reinstall from the Play Store as necessary, and you'll be fine.
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!
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 -
Hi, first post on xda. Lurked for over two years and well, you gotta start somewhere
I'm on rooted stock 4.4.2 ROM with unlocked bootloader.
The OTA is constantly reminding me to update to 4.4.4. I'd like to, but I need to know if I can safely re-root after upgrading and wether anything that uses root right now will break or if they'll just continue working after a sucessful re-root. I'm thinking about Busybox, xPosed framework with GravityBox and MotoGuide.
Help me?
gnayug said:
Hi, first post on xda. Lurked for over two years and well, you gotta start somewhere
I'm on rooted stock 4.4.2 ROM with unlocked bootloader.
The OTA is constantly reminding me to update to 4.4.4. I'd like to, but I need to know if I can safely re-root after upgrading and wether anything that uses root right now will break or if they'll just continue working after a sucessful re-root. I'm thinking about Busybox, xPosed framework with GravityBox and MotoGuide.
Help me?
Click to expand...
Click to collapse
After the update you will be able to root again. If you flash Phil's recovery it will ask you to root the device for you.
I would recommend to uninstall xposed and its modules, unroot the device and flash stock recovery before installing the update. You'll need to reinstall your root apps after. Others have had success installing updates using CWM or TWRP but it didn't work for me so.
Hi,
I will be getting my new OPO in the next few days (very excited!) my question is; If i unlock the booloader and root the phone but NOT flash a custom rom will i still receive the OTA updates from Cyanogen?
There's a few rooted apps i like to use and stock CM11S will be the perfect rom for me.
Thanks
Levy
levy9 said:
Hi,
I will be getting my new OPO in the next few days (very excited!) my question is; If i unlock the booloader and root the phone but NOT flash a custom rom will i still receive the OTA updates from Cyanogen?
There's a few rooted apps i like to use and stock CM11S will be the perfect rom for me.
Thanks
Levy
Click to expand...
Click to collapse
Yes you will rooting does not affect OTS updates, the only thing is that after each OTA you will have to flash the SU zip again to get back root. The only thing that will mess up OTS is if you play with system files ( forum Masters correct me if i'm wrong here ). Make a backup before you do anything and you should be good. Have fun.
Cholerabob said:
Yes you will rooting does not affect OTS updates, the only thing is that after each OTA you will have to flash the SU zip again to get back root. The only thing that will mess up OTS is if you play with system files ( forum Masters correct me if i'm wrong here ). Make a backup before you do anything and you should be good. Have fun.
Click to expand...
Click to collapse
Yeah this is all true
Download the SuperSU zip to your phone and be ready to flash it after the ota installs
Sent from my A0001 using XDA Free mobile app
Currently have an Rooted S8 which runs TWRP.. whats the best method for unrooting the device as I want OTA updates?
minalm said:
Currently have an Rooted S8 which runs TWRP.. whats the best method for unrooting the device as I want OTA updates?
Click to expand...
Click to collapse
It depends on whether you're using SuperSU or Magisk.
To unroot if you have SuperSU, open SuperSU app, then open its app settings, find the setting that says something like "cleanup for unroot and uninstall". That will remove the su binaries and uninstall the SuperSU app.
To unroot if you have Magisk, use the Magisk uninstaller.zip(might cause bootloop which then requires flashing stock firmware via Odin)
Or you can just flash the stock firmware via Odin to remove root. You're going to have to get rid of TWRP also which would require you to flash a copy of stock recovery to replace TWRP. Flashing stock firmware via Odin will replace TWRP and remove root all in one shot, no need for extra steps or tricks.
Then you can do the OTA update.
OR
An even better option is as follows.
The OTA update might even be available to the public to download, if so, you can download the update manually(not via OTA) then flash the update via Odin, this will replace TWRP, remove root and update the device all in one shot. This way, you won't have to do anything except flash the update and you're done. No need to replace TWRP and unroot before doing the OTA update. This method skips all of that and gets you the update without having to do all the extra work. You'll have to root the device again and flash TWRP after the update has been applied.
If you choose to do the OTA instead, make sure you are completely unrooted and are back on stock recovery, you can't have root or TWRP when you do the OTA, it will not work that way.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
It depends on whether you're using SuperSU or Magisk.
To unroot if you have SuperSU, open SuperSU app, then open its app settings, find the setting that says something like "cleanup for unroot and uninstall". That will remove the su binaries and uninstall the SuperSU app.
To unroot if you have Magisk, use the Magisk uninstaller.zip(might cause bootloop which then requires flashing stock firmware via Odin)
Or you can just flash the stock firmware via Odin to remove root. You're going to have to get rid of TWRP also which would require you to flash a copy of stock recovery to replace TWRP. Flashing stock firmware via Odin will replace TWRP and remove root all in one shot, no need for extra steps or tricks.
Then you can do the OTA update.
OR
An even better option is as follows.
The OTA update might even be available to the public to download, if so, you can download the update manually(not via OTA) then flash the update via Odin, this will replace TWRP, remove root and update the device all in one shot. This way, you won't have to do anything except flash the update and you're done. No need to replace TWRP and unroot before doing the OTA update. This method skips all of that and gets you the update without having to do all the extra work. You'll have to root the device again and flash TWRP after the update has been applied.
If you choose to do the OTA instead, make sure you are completely unrooted and are back on stock recovery, you can't have root or TWRP when you do the OTA, it will not work that way.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
you have given a very detailed explanation and i fell like a simple thank you would be enough. you helped me out now and i feel somewhat obliged to thank you this way.
cheers
Is the things still the same... namely unrooting will not return KNOX and can not use Samsung warranty?
hi
i have a rotted phone s8..i flashed a stock rom, but phone is still rooted. Some apps like us google pay,mcdonalds tell me that phone is rooted..What i can do?