Hi all - I've read that in order to root it is necessary to unlock the bootloader and then root, but I've also read some threads where the bootloader can be re-locked. My question is whether I can still be rooted then, maybe with the use of OTA rootkeeper or some such. I haven't rooted yet (my prime uses would initially be for adblocking and wifi tether), but I'm thinking I will soon. However, I'd really like to be able to hold out until the 4.2/4.3 OTA comes out before flashing ROMS (need stable bluetooth in a bunch of areas, and want to wait and see if there are problems with that update in stock).
So, any way to be stock, re-locked and rooted?
Can't you just root using the normal method then flash stock recovery to remove "*** Tampered***" and then re-lock with fastboot? You're system partition wont be stock obviously because it will have the su binary. You're boot loader will say "*** Relocked ***" though. I'm thinking it might be possible to remove "*** Relocked ***" using JTAG if someone can find the area in memory where the history of unlocking is stored.
Unlock bootloader, flash custom recovery, use Aroma File manager to copy su to /system/bin and set permissions, reflash stock recovery, relock bootloader, install Superuser from play store. This should work but I haven't tried it.
Related
I get this error when trying to unlock my bootloader. I have c6903 and rooted it before moving up to 4.3. I then unlocked my bootloader on 4.3 (or I think I did). However, when I try to install supersu it says my phone is not rooted. However, when I try to unlock my bootloader I get the message "error phone is already rooted". I attached a screenshot below. Does this mean my phone bootloader is unlocked and my phone is properly rooted to then install a recovery? I want to ultimately install ihackers rom but want to be sure I have everything ready for a proper install.
Thanks
antmantucan said:
I get this error when trying to unlock my bootloader. I have c6903 and rooted it before moving up to 4.3. I then unlocked my bootloader on 4.3 (or I think I did). However, when I try to install supersu it says my phone is not rooted. However, when I try to unlock my bootloader I get the message "error phone is already rooted". I attached a screenshot below. Does this mean my phone bootloader is unlocked and my phone is properly rooted to then install a recovery? I want to ultimately install ihackers rom but want to be sure I have everything ready for a proper install.
Thanks
Click to expand...
Click to collapse
I'm not sure why it says "rooted" in fastboot, but the commands you're sending are to unlock the bootloader, not root the phone. Your bootloader must already be unlocked, per the error you see. I hope you backed up your TA partition before BL unlocking.
Check out the Root on 4.3 dev discussion for more details on a 4.3 root (which is only possible with an unlocked BL currently).
Just try to use Flashtool to unlock the bootloader.
I have a Moto X -Xt1052 in India. I would like to root it and install Xposed framework. I am running kitkat 4.4.4
I would like to know is there any rooting method that wont affect OTA upadtes Because some people say thay if you unlock bootloader and You try OTA you brick your device. is it true???
and is there any way to reverse all this : Bootloader unlocking> getting back stock recovery> unroot complely so that there is no harm when you Update via OTA.
M really confused as there are mixed view over internet..
a few items to clear up....
The ability to root, and how you root vary depending on if you have unlocked your bootloader (or can you) or not, and what rom you have.
Being rooted itself does not impact the ability or inability to take an OTA. Its additional mods like custom recovery (you need to flash stock recovery back on before taking an OTA or you'll be stuck in a boot loop), deleting bloat (common in the USA where carriers like Verizon install a lot of extra apps and stuff as part of their rom), etc. The OTA performs a validation check before it installs. Modify too much on your phone and you will probably touch something that will cause the validation check to fail, and the OTA wont install.
Xposed gets in the way of OTA updates. You need to disable it or un-install it before taking an OTA.
I have never seen an unlocked bootloader be the cause of bricking a phone, taking an OTA or otherwise.
Attempting to down grade your ROM then later taking an OTA can/will brick your phone. But if you've never tried to downgrade your rom, there is nothing to worry about.
Once you unlock your bootloader, there is no need to re-lock it. It wont get in the way of an OTA. There is a process re-lock your bootloader if you want, but there is no reason to. Also keep in mind there are 3 states of the Moto X bootloader. 1. Locked - as it ships from the factory, 2. Unlocked - after you get your bootloader unlock code and use it, 3. Re-Locked - after you follow the process to relock the bootloader. And Once unlocked, we can only toggle it to RELOCKED. We can't set it back to LOCKED.
There are many ways to get back to "stock" after rooting and modifying your phone. I've outlined a few HERE
I have a locked BL VZW XT1060 on 4.4.2 stock
It was/is rooted.
It has SuperSU installed but without binaries installed.
A little history:
Originally on 4.2.2 then OTA to 4.4.
Downgraded to 4.2.2 and applied SlapMyMoto.
I believe I took OTA to 4.4 with the intention to sit tight there.
I accidentally took OTA to 4.4.2.
This is where it gets weird.
Root was still intact but write protection was temporary, meaning after reboot, I lose it.
This was fine as it allowed me to temporarily disable write protection and enable the native hotspot.
Then, one day I was updating some apps on my phone, I noticed that I completely lost the ability to disable to write protection. I tried uninstalling all to the app updates to no avail.
What are my options to get WiFi tether/Hotspot back?
Sunshine, unlock the bootloader, and have a fully unlocked device. Anything else and you'll likely run into issues similar to what you have now.
Sent from my Moto X
What the guy above me said.
@slingblade01 what you described is exactly what happens.
The vulnerability which MotoWpNoMo exploited to disable write protection was patched in 4.4.2, so if you have a LOCKED Bootloader, and updated from 4.4 you could keep root, but write protection became enabled with no way to disable it again.
If you don't care about upgrading past 4.4.2, you can search for TowelPieRoot, and gain temp root to.
Otherwise, as @imnuts and @nhizzat say, If you are still on 4.4.2, and have its bootloader, then you can use Sunshine to unlock the bootloader, after witch your phone will be just like a Developer Edition, or other edition with the bootloader unlocked.
In other words, once you unlock using Sunshine, you may root by following -> http://forum.xda-developers.com/moto-x/moto-x-qa/instructions-unlocking-rooting-dev-ed-t2649738 Just please be sure to use the latest TWRP fastboot IMG file and Installable ZIP of SuperSU. Once completed, you will have root with write protection disabled.
And it does not matter what Stock ROM or Android version is on your phone (Android 5 has some changes, so stay tuned) , once your bootloader is unlocked, you can always root or re-root it. (You just can't take OTA with custom recovery on there!!).
For Sunshine discussion see -> http://forum.xda-developers.com/moto-x/general/request-help-exploit-moto-x-bl-t2828471
and -> http://forum.xda-developers.com/showthread.php?t=2792487
and most importantly....
http://theroot.ninja/
Sunshine will check if its compatible with your phone first, if it is, it will charge you $25 before proceeding to unlock you. Unlike using the bootloader unlock code from Moto or the middleman, using Sunshine to unlock your bootloader is not destructive.
Once your bootloader is unlocked via Sunshine, do NOT attempt to re-lock it. because if you do relock it, you wont be able to unlock it again!! BTW, there is no need to relock anyway. It doesn't impact taking OTAs, etc.
Thank you and last question.
Thanks, that was the answer I was expecting but wanted professional opinions first.
Before I use Sunshine, do I need to do any prep work first, such as disable/remove root (remove SuperSU)?
Thanks again.
slingblade01 said:
Thanks, that was the answer I was expecting but wanted professional opinions first.
Before I use Sunshine, do I need to do any prep work first, such as disable/remove root (remove SuperSU)?
Thanks again.
Click to expand...
Click to collapse
Because I have a developer edition, I got my bootloader unlock code from moto, and haven't tried Sunshine.
From my brief reading/following of the Sunshine thread, I don't think you have to un-do anything. But I would consider flashing back to stock to remove any traces of SlapMyMoto and the like AFTER you unlock via Sunshine.
Is there a procedure to unlock the bootloader, root, uninstall some of the T-Mobile apps and make a few changes, then unroot, and relock the bootloader?
Everything I've seen so far requires re-flashing everything back to stock, I was hoping to avoid that. (Obviously, the bootloader and recovery would be stock when I'm done, just not the system)
The locked bootloader will not boot a modified system partition. As such revert to stock is required. Question is still open on relocking the bootloader post MM. After MM the unlock is visible on the boot screens where previously it was not. This would be an instant giveaway on any warranty claims.
Thanks, that's what I thought but I wasn't sure.
Is it possible to install Magisk and then relock the bootloader?
This is on OPWS27.1.3 (March update, Android 8.0)
Aka:
1) unlock bootloader
2) flash Magisk boot
3) install Magisk
4) relock bootloader
The general advice is to not lock the bootloader with custom or modded ROMs. If you want to throw caution to the wind, you probably want to have a stable, custom recovery first.
The dangers of locking it is that you will probably get stuck with a soft bricked device.
gee one said:
The general advice is to not lock the bootloader with custom or modded ROMs. If you want to throw caution to the wind, you probably want to have a stable, custom recovery first.
The dangers of locking it is that you will probably get stuck with a soft bricked device.
Click to expand...
Click to collapse
Ah, that's unfortunate. I was hoping to be able to essentially add sudo usable via adb when debugging is enabled leaving everything else intact. Is it possible to gain root privileges without unlocking the bootloader or using a modded ROM?