Related
All,
Has anyone on Verizon done the OTA update and kept root? From what I've been reading, sounds like if you rooted with MotoRoot then you're okay, but not if you used PwnMyMoto.
As far as people getting a bootloop, that does make some sense because the recovery partition is really just the boot image... So I can flash the stock recovery to the recovery partition before running the update, and that should theoretically prevent a bootloop. However, if this is going to erase my root, then I don't want to do the update.
So, has anyone on verizon done the OTA and kept their root? How did you do it?
First item, this is a question so it should belong in the question and answer threads! Secondly look here http://forum.xda-developers.com/showthread.php?t=2466191
Sent on my Moto X
Sorry, and thanks! I'll probably give this a shot, make that camera work a little better...
You can always install the SafeStrap ROM here. That's what I did.
http://forum.xda-developers.com/showthread.php?t=2484908
[Rom] [VZW] SafeStrap 139.12.57
Sent from my Moto X
The way that everyone (including myself) have been updating and keeping root on Verizon is as followed:
1. RSD back to stock (instructions here: http://forum.xda-developers.com/showthread.php?t=2446515)
2. Install PwnMyMoto and DO NOT RUN IT
3. Download and install OTA
4. When the install completes, your phone will reboot a few times. This is just PwnMyMoto doing its magic.
5. Profit.
dymmeh said:
The way that everyone (including myself) have been updating and keeping root on Verizon is as followed:
1. RSD back to stock (instructions here: http://forum.xda-developers.com/showthread.php?t=2446515)
2. Install PwnMyMoto and DO NOT RUN IT
3. Download and install OTA
4. When the install completes, your phone will reboot a few times. This is just PwnMyMoto doing its magic.
5. Profit.
Click to expand...
Click to collapse
This method makes it so SafeStrap is no longer available though, right? If that's not the case then... Don't know what I've been waiting for!
Sent from my Moto X
mercado79 said:
This method makes it so SafeStrap is no longer available though, right? If that's not the case then... Don't know what I've been waiting for!
Sent from my Moto X
Click to expand...
Click to collapse
I searched around and can't really find an answer to that. I don't use SafeStrap so I have no idea. I'd assume you can try the method I posted and try using SafeStrap after. If that doesn't work then just RSD back to pre-update and hang on to SafeStrap until it's figured out. No guarantees if it'd work / break stuff, though. You'd be the guinea pig for that one.
dymmeh said:
I searched around and can't really find an answer to that. I don't use SafeStrap so I have no idea. I'd assume you can try the method I posted and try using SafeStrap after. If that doesn't work then just RSD back to pre-update and hang on to SafeStrap until it's figured out. No guarantees if it'd work / break stuff, though. You'd be the guinea pig for that one.
Click to expand...
Click to collapse
@jcase Any chance you can answer this for us? Just cause someone was able to keep root (the one shot kind you mentioned), does that mean that using RSD is still on the table?
Sent from my Moto X
mercado79 said:
@jcase Any chance you can answer this for us? Just cause someone was able to keep root (the one shot kind you mentioned), does that mean that using RSD is still on the table?
Sent from my Moto X
Click to expand...
Click to collapse
If you take the OTA you dont have wY to revert to old stock Motorola block the reverts already and @jcase already said that he will be back for root in this device till 4.3 is out
Sent from my XT1060 using Tapatalk
juancaperez2000 said:
If you take the OTA you dont have wY to revert to old stock Motorola block the reverts already and @jcase already said that he will be back for root in this device till 4.3 is out
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
That's what I thought too. Thanks.
MikeyNick said:
All,
Has anyone on Verizon done the OTA update and kept root? From what I've been reading, sounds like if you rooted with MotoRoot then you're okay, but not if you used PwnMyMoto.
As far as people getting a bootloop, that does make some sense because the recovery partition is really just the boot image... So I can flash the stock recovery to the recovery partition before running the update, and that should theoretically prevent a bootloop. However, if this is going to erase my root, then I don't want to do the update.
So, has anyone on verizon done the OTA and kept their root? How did you do it?
Click to expand...
Click to collapse
For sure have I just updated my Moto X the other day on VZW and kept root. Here is a link to the process on how to do it
http://forum.xda-developers.com/showthread.php?t=2466191
will2live said:
For sure have I just updated my Moto X the other day on VZW and kept root. Here is a link to the process on how to do it
http://forum.xda-developers.com/showthread.php?t=2466191
Click to expand...
Click to collapse
I think that's not up for debate. The issue is that even though you kept root, you're now blocked from using safestrap or ever gaining root again in the future (once another ota comes through). The update has now patched root going forward and it sounds like you won't be able to keep it after this update.
MikeyNick said:
All,
Has anyone on Verizon done the OTA update and kept root? From what I've been reading, sounds like if you rooted with MotoRoot then you're okay, but not if you used PwnMyMoto.
As far as people getting a bootloop, that does make some sense because the recovery partition is really just the boot image... So I can flash the stock recovery to the recovery partition before running the update, and that should theoretically prevent a bootloop. However, if this is going to erase my root, then I don't want to do the update.
So, has anyone on verizon done the OTA and kept their root? How did you do it?
Click to expand...
Click to collapse
mercado79 said:
I think that's not up for debate. The issue is that even though you kept root, you're now blocked from using safestrap or ever gaining root again in the future (once another ota comes through). The update has now patched root going forward and it sounds like you won't be able to keep it after this update.
Click to expand...
Click to collapse
Safestrap i know about and dont care about as i dont use it. As for moving forward with root I'll be surprised if that is the case but I wont disagree either. It is very possible they patch something to actually block root down the road. From my understanding tho currently the patch is blocking ppl to root the update not keeping root if the process is followed correctly. My guess is odds are it will be the same on the next OTA just like we had to do on the original Razr line to keep root until the bootloader was unlocked. However if the next OTA is 4.3 tha tcould all change for sure as anything is possible. Even so when that time comes I'll just unlock mine. I do have a Dev edition i just haven't unlocked with it being brand new and not wanting to void warranty yet to make sure hardware is cool but i do want root so i went the long route for now is all.
dymmeh said:
The way that everyone (including myself) have been updating and keeping root on Verizon is as followed:
1. RSD back to stock (instructions here: http://forum.xda-developers.com/showthread.php?t=2446515)
2. Install PwnMyMoto and DO NOT RUN IT
3. Download and install OTA
4. When the install completes, your phone will reboot a few times. This is just PwnMyMoto doing its magic.
5. Profit.
Click to expand...
Click to collapse
So I installed PwnMyMoto, SuperSU and OTA Root Keeper, then decided not to root. I installed the Verizon update and boom, I'm rooted. Is that what you're saying is needed? I was surprised that root apps all work fine for me, I really didn't do anything but install those apks before I installed the camera update!
boardrx182 said:
So I installed PwnMyMoto, SuperSU and OTA Root Keeper, then decided not to root. I installed the Verizon update and boom, I'm rooted. Is that what you're saying is needed? I was surprised that root apps all work fine for me, I really didn't do anything but install those apks before I installed the camera update!
Click to expand...
Click to collapse
As long as you had PwnMyMoto and never ran it / not rooted you were good to go. SuperSU could be installed before or after. I dont think OTA Root Keeper was needed at all. PwnMyMoto runs after a reboot so once you installed the OTA and rebooted it did its rooting magic automatically for you. Glad it all worked out for you
dymmeh said:
The way that everyone (including myself) have been updating and keeping root on Verizon is as followed:
1. RSD back to stock (instructions here: http://forum.xda-developers.com/showthread.php?t=2446515)
2. Install PwnMyMoto and DO NOT RUN IT
3. Download and install OTA
4. When the install completes, your phone will reboot a few times. This is just PwnMyMoto doing its magic.
5. Profit.
Click to expand...
Click to collapse
dymmeh said:
As long as you had PwnMyMoto and never ran it / not rooted you were good to go. SuperSU could be installed before or after. I dont think OTA Root Keeper was needed at all. PwnMyMoto runs after a reboot so once you installed the OTA and rebooted it did its rooting magic automatically for you. Glad it all worked out for you
Click to expand...
Click to collapse
That's awesome, didn't realize that would happen automatically. I completely expected that I'd have to complete the entire root process steps that were outlined in an earlier post if I wanted root. Thanks for the reply.
will2live said:
Safestrap i know about and dont care about as i dont use it. As for moving forward with root I'll be surprised if that is the case but I wont disagree either. It is very possible they patch something to actually block root down the road. From my understanding tho currently the patch is blocking ppl to root the update not keeping root if the process is followed correctly. My guess is odds are it will be the same on the next OTA just like we had to do on the original Razr line to keep root until the bootloader was unlocked. However if the next OTA is 4.3 tha tcould all change for sure as anything is possible. Even so when that time comes I'll just unlock mine. I do have a Dev edition i just haven't unlocked with it being brand new and not wanting to void warranty yet to make sure hardware is cool but i do want root so i went the long route for now is all.
Click to expand...
Click to collapse
people who have moto employee friends say they are moving to 4.3 next. Also, there may be a work around for you to keep root with the next release, but because people who aren't on dev phones that must be sure they can retain root would not have used this method (as it is a one chance type of method). so it is more likely that any new workarounds that people come up with will be for those that still have the ability to downgrade to original stock firmware. Also, SS is nice because it gives you the ability to run the phone just like you normally would but you can create complete backups of the device so you don't have to set everything up all over again if you screw something up with your phone. Even if you don't use SS for flashing roms it is still useful for back ups.
jayboyyyy said:
people who have moto employee friends say they are moving to 4.3 next. Also, there may be a work around for you to keep root with the next release, but because people who aren't on dev phones that must be sure they can retain root would not have used this method (as it is a one chance type of method). so it is more likely that any new workarounds that people come up with will be for those that still have the ability to downgrade to original stock firmware. Also, SS is nice because it gives you the ability to run the phone just like you normally would but you can create complete backups of the device so you don't have to set everything up all over again if you screw something up with your phone. Even if you don't use SS for flashing roms it is still useful for back ups.
Click to expand...
Click to collapse
I have my Moto contacts and yes they are moving to 4.3 next last i was told when I asked. As for downgrading stock software that isn't going to happen once updated as you can't go backwards. Moto devices have been that way going back to the original Droid Razr. Its few and far between where you could actually go backwards after an OTA. So unless you mean stock of the current build installed then ppl will have issues for sure. That said if ppl OTA and have root now but for whatever reason need to use the new fastboot file that was just posted they will in fact be SOL for gaining root. This is exactly why I refuse to buy consumer units from the carrier besides a few other reason I wont go into. My theory is simple we want to mess with device buy an unlockable one or be ready to suffer/wait for an exploit after an OTA hits.
As far as root moving forward what process you talking about tho? There is 2 ways to do it. The one posted right above your post in this thread, or the link I posted above. If the info in this thread was used yes there may be an issue because of the patch. However I will be very surprised to see ppl not be able to keep root if they updated using the process in the link I posted above. Besides having to fastboot the boot.img to recovery in that process its the same way original Droid Razr owners had to update to be able to keep root if there was no root process for the OTA being pushed. Moving forward my guess is there will be an issue once 4.3 hits tho. I'm not sure you will be able to use the old kernel from 4.2.2 to overwrite recovery and boot the 4.3 /system so you can restore root and pull the actual 4.3 boot.img so that can be used for the recovery highjack. Bottom line is only time will tell at this point as you never know what Moto/Google will do with the next update.
Agreed on SS for backups even if not flashing ROMs, but personally i just dont mess with my device enough to worry about a full back i guess. For apps/settings I just use MyBackup PRO. I've also have an app a buddy made that creates a full XML if i wanted to use it. In the old days I use to make alot of backups for ROM flashing when I used SS. Guess in my old age I've just got lazy and dont worry about it that much anymore. I really hose the device I'll just swap to one of my others til i get back to fixing the messed up one.
will2live said:
I have my Moto contacts and yes they are moving to 4.3 next last i was told when I asked. As for downgrading stock software that isn't going to happen once updated as you can't go backwards. Moto devices have been that way going back to the original Droid Razr. Its few and far between where you could actually go backwards after an OTA. So unless you mean stock of the current build installed then ppl will have issues for sure. That said if ppl OTA and have root now but for whatever reason need to use the new fastboot file that was just posted they will in fact be SOL for gaining root. This is exactly why I refuse to buy consumer units from the carrier besides a few other reason I wont go into. My theory is simple we want to mess with device buy an unlockable one or be ready to suffer/wait for an exploit after an OTA hits.
As far as root moving forward what process you talking about tho? There is 2 ways to do it. The one posted right above your post in this thread, or the link I posted above. If the info in this thread was used yes there may be an issue because of the patch. However I will be very surprised to see ppl not be able to keep root if they updated using the process in the link I posted above. Besides having to fastboot the boot.img to recovery in that process its the same way original Droid Razr owners had to update to be able to keep root if there was no root process for the OTA being pushed. Moving forward my guess is there will be an issue once 4.3 hits tho. I'm not sure you will be able to use the old kernel from 4.2.2 to overwrite recovery and boot the 4.3 /system so you can restore root and pull the actual 4.3 boot.img so that can be used for the recovery highjack. Bottom line is only time will tell at this point as you never know what Moto/Google will do with the next update.
Agreed on SS for backups even if not flashing ROMs, but personally i just dont mess with my device enough to worry about a full back i guess. For apps/settings I just use MyBackup PRO. I've also have an app a buddy made that creates a full XML if i wanted to use it. In the old days I use to make alot of backups for ROM flashing when I used SS. Guess in my old age I've just got lazy and dont worry about it that much anymore. I really hose the device I'll just swap to one of my others til i get back to fixing the messed up one.
Click to expand...
Click to collapse
3 ways to maintain root are the one in the thread, SS, and the one you posted. The one you posted actually allows you to flash the original stock firmware on the phone because the BL was never touched thus the security (keeping you from downgrading) was never installed. That was what I was referring to when I said those that must make sure they will retain root in the future would not have done the install pwnmymmoto without running then take ota then run pwnmymoto. As you said those people will be screwed if the next root requires you to flash back to original stock or use part of the pwnmymoto exploit that will only be accessible to those that got the OTA with SS or the link you posted. I don't toy with my phone as much as I used to especially this one, but bypasing exchange security is pretty essential for me. I don't want an encrypted device with mandatory pin. I never lose my phone and I would know within minutes of losing it if i ever did so I could shut it down remotely.
And I'm not sure about the new kernel situation either. This is why I wanted to make sure I could go back to original firmware as I see that being our best bet to retain root through 4.3, assuming jcase doesn't release another exploit for it to get some cash.
jayboyyyy said:
3 ways to maintain root are the one in the thread, SS, and the one you posted. The one you posted actually allows you to flash the original stock firmware on the phone because the BL was never touched thus the security (keeping you from downgrading) was never installed. That was what I was referring to when I said those that must make sure they will retain root in the future would not have done the install pwnmymmoto without running then take ota then run pwnmymoto. As you said those people will be screwed if the next root requires you to flash back to original stock or use part of the pwnmymoto exploit that will only be accessible to those that got the OTA with SS or the link you posted. I don't toy with my phone as much as I used to especially this one, but bypasing exchange security is pretty essential for me. I don't want an encrypted device with mandatory pin. I never lose my phone and I would know within minutes of losing it if i ever did so I could shut it down remotely.
And I'm not sure about the new kernel situation either. This is why I wanted to make sure I could go back to original firmware as I see that being our best bet to retain root through 4.3, assuming jcase doesn't release another exploit for it to get some cash.
Click to expand...
Click to collapse
Gotchya, makes total sense now what you are saying. I think there is just confusion at times when talking about root & OTA because of different ways to do it in a case like this device. Being a Moto guy for so long tho i'm use to all the BS they throw at us.....lol. That said that is why i posted the link I did. Imho it's a bad plan to update using the other method of installing pwnmymoto and not running it first before taking the OTA. Doing the process to protect root before updating is a much safer bet atm imo. Sure its a little more work but at the end of the day you dont have to be worried as much moving forward. Only concern I have still for doing it the longer way is if that process will work when they push out 4.3. It had alot of changes in it so lord only knows what will be up for keeping root. And really in my case its no concern but for all the folks with consumer version it is still a concern i think for the time being
Ive uploaded a fully working root method of kingoroot that roots the nexus 5 on 5.1.1 LMY48B firmware
I have used it myself with uk stock nexus 5 and all works just thought i would upload so other people can benefit from this instead of using a pc enjoy
anyone tested this yet? i am to scared to try xD
thankyoumr said:
anyone tested this yet? i am to scared to try xD
Click to expand...
Click to collapse
working fine.. tested by me
Yes, this can also root from COMPLETE stock without the need of a computer of any kind. May want to add that to thread title if possible to let others know it can be used to root LMY48B(At Least) without the need of a computer to unlock bootloader first and without the need of a custom recovery first. Just install Kingroot then use KingUser(I Believe That Is The Super User App It Installs, Do NOT Install Another SuperUser App Yet Until After Custom Recovery Installed) and use KingUser to allow custom recovery App permissions to install recovery then use that recovery to install SuperUser binaries properly.
Sent from my Nexus 5 using Tapatalk
Why? It's a Nexus.
fastboot oem unlock
flash supersu zip file.
GldRush98 said:
Why? It's a Nexus.
fastboot oem unlock
flash supersu zip file.
Click to expand...
Click to collapse
He just said why on the first post...lol
So you dont need a pc
Its just an easier method if you ask me and for unlocking bootloader you just need to download the nexus 5 unlock bootloader app from google play to unlock bootloader then just install twrp manager from google play and theres your root bootloader unlock and custom recovery but thats upto the user as other people do it there way
It's remarkable what I'm willing to download and install from XDA sometimes.
Anyway, it certainly rooted my device without needing to hook it up to a PC. Threw two "this is bypassing android security" messages. Hope it didn't do anything else :/
---------- Post added at 09:57 PM ---------- Previous post was at 09:37 PM ----------
This also leaves you with an app called Kinguser, which is used to grant root permission to other apps, which can't be removed.
I think I'll feel better if I wipe and start over...
---------- Post added at 09:57 PM ---------- Previous post was at 09:57 PM ----------
This also leaves you with an app called Kinguser, which is used to grant root permission to other apps, which can't be removed.
I think I'll feel better if I wipe and start over...
All you do is use KingUser to grant permission to TWRP Manager to install TWRP and then use SuperSU to install SU through recovery THEN you can easily use SuperSU to grant permissions to any app that'll allow you to remove KingUser. That way you always have an app that can grant SU at all times without going ANY time at all without a SuoerUser app
EPayne123 said:
All you do is use KingUser to grant permission to TWRP Manager to install TWRP and then use SuperSU to install SU through recovery THEN you can easily use SuperSU to grant permissions to any app that'll allow you to remove KingUser. That way you always have an app that can grant SU at all times without going ANY time at all without a SuoerUser app
Click to expand...
Click to collapse
Tried that but SuperSU kept failing to install. Ended up just wiping and going from scratch. The whole Kingroot sending data home to a server just didn't sit well with me. I know they've addressed that they do it to keep track of success rates and don't collect any personal data.
rbrenart said:
Tried that but SuperSU kept failing to install. Ended up just wiping and going from scratch. The whole Kingroot sending data home to a server just didn't sit well with me. I know they've addressed that they do it to keep track of success rates and don't collect any personal data.
Click to expand...
Click to collapse
Failed to install returning SuperSU?
Will this wipe all data the way unlocking the bootloader does?
Sent from my Nexus 5 using Tapatalk 2
ddimple4 said:
Will this wipe all data the way unlocking the bootloader does?
Sent from my Nexus 5 using Tapatalk 2
Click to expand...
Click to collapse
No, wiping data only happens when you unlock bootloader through the bootloader. . . not through the OS. I believe only of you use the Farnborough method instead of manually doing so inside of OS
Sent from my Nexus 5
My friend has nexus 5 tmobile. Will this work? If so any additional steps?
Hi. I'm a newbie in root matter. My nexus 5 is already in LMY48b 5.1.1. Hong Kong stock ROM. So far there's only one reason I want to root it, it is to let some call recorder apps to record incoming voice clearly. So at this stage I don't need to flash any custom ROM. I dug for a certain time of course I can find many teaching how to root, but most of them look like it involves many procedures, many terms or apps, unlock bootloader, android SDK, twrp, custom recovery, etc... it makes me so scared even to give it a try. Until I saw this thread and I think the kingroot app probably the simplest one for my case! In fact I can get it done with a Chinese root way, it's also very simple but I also heard that most likely there's spyware inside so I leave it.
So what I want to make sure is my thought above is it correct? I try not to annoy you guys, any answer simply either yes or no is appreciated. Of course if you guys want to tell me more it is most welcome.
我從使用 Tapatalk 的 SM-T700 發送
lookgod88 said:
Hi. I'm a newbie in root matter. My nexus 5 is already in LMY48b 5.1.1. Hong Kong stock ROM. So far there's only one reason I want to root it, it is to let some call recorder apps to record incoming voice clearly. So at this stage I don't need to flash any custom ROM. I dug for a certain time of course I can find many teaching how to root, but most of them look like it involves many procedures, many terms or apps, unlock bootloader, android SDK, twrp, custom recovery, etc... it makes me so scared even to give it a try. Until I saw this thread and I think the kingroot app probably the simplest one for my case! In fact I can get it done with a Chinese root way, it's also very simple but I also heard that most likely there's spyware inside so I leave it.
So what I want to make sure is my thought above is it correct? I try not to annoy you guys, any answer simply either yes or no is appreciated. Of course if you guys want to tell me more it is most welcome.
我從使用 Tapatalk 的 SM-T700 發送
Click to expand...
Click to collapse
may be you can try the nexus toolkit, http://www.wugfresh.com/nrt/
beware that when unlock the bootloader all data will lost (factory reset), you can use something like helium to make a backup first (for back app data)
DummyPLUG said:
may be you can try the nexus toolkit, http://www.wugfresh.com/nrt/
beware that when unlock the bootloader all data will lost (factory reset), you can use something like helium to make a backup first (for back app data)
Click to expand...
Click to collapse
Hi dummyplug, thank you for your reply and your referring. But I actually don't need to flash ROM, that's why I thought that I don't need to unlock the bootloader either. Do I?
lookgod88 said:
Hi dummyplug, thank you for your reply and your referring. But I actually don't need to flash ROM, that's why I thought that I don't need to unlock the bootloader either. Do I?
Click to expand...
Click to collapse
The reason to unlock the bootloader is because if it is locked you can't run custom recovery (not flash, just a temp boot up with custom recovery), which is need for the root process, in short, you need to unlock the boot loader before you can do anything.
something like kingroot can bypass the need of an unlocked bootloader, so you actually can use kingroot to root your nexus first, then use those bootloader unlocker from play store to unlock the bootloader, but I will stay away from those tools because I don't trust them.
the toolkit can help you to unlock the bootloader and root, and do something else.
p.s. that means you need an unlocked bootloader to root, meanwhile can keep all other things (recovery, firmware) as stock.
DummyPLUG said:
The reason to unlock the bootloader is because if it is locked you can't run custom recovery (not flash, just a temp boot up with custom recovery), which is need for the root process, in short, you need to unlock the boot loader before you can do anything.
something like kingroot can bypass the need of an unlocked bootloader, so you actually can use kingroot to root your nexus first, then use those bootloader unlocker from play store to unlock the bootloader, but I will stay away from those tools because I don't trust them.
the toolkit can help you to unlock the bootloader and root, and do something else.
Click to expand...
Click to collapse
Oh I see. Now I understand! Thank you very much. I got what I want to know.
I used this method after I unlocked with sunshine to remove king-root and replace it with SuperSU. It worked great for me. Kingroot is gone and i have a permanent root and SuperSU installed. I was wondering if there is someone else who has unlocked their boot-loader and not yet installed TWRP who can give it a shot to see if my expereince was a fluke or the norm. It would be a nice addition for people who want root but don't want TWRP installed for one reason or another.
I used the second link in his post.
Replace_Kinguser_with_SuperSU-v2.4.zip
http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html
Thank you
HT123 said:
I used this method after I unlocked with sunshine to remove king-root and replace it with SuperSU. It worked great for me. Kingroot is gone and i have a permanent root and SuperSU installed. I was wondering if there is someone else who has unlocked their boot-loader and not yet installed TWRP who can give it a shot to see if my expereince was a fluke or the norm. It would be a nice addition for people who want root but don't want TWRP installed for one reason or another.
I used the second link in his post.
Replace_Kinguser_with_SuperSU-v2.4.zip
http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html
Thank you
Click to expand...
Click to collapse
I previously used the above method you posted to permanent root an LG Transpyre on 5.1.1 that did not have the bootloader unlocked. Glad to see someone else knows about it. :good:
Maybe it will work on a locked bootloader Turbo for those who don't want to unlock their phones but just want root.
classic757 said:
I previously used the above method you posted to permanent root an LG Transpyre on 5.1.1 that did not have the bootloader unlocked. Glad to see someone else knows about it. :good:
Maybe it will work on a locked bootloader Turbo for those who don't want to unlock their phones but just want root.
Click to expand...
Click to collapse
Can not unlock booloader root? I do not have a visa. $ 25 is a huge amount to me
Thành67890 said:
Can not unlock booloader root? I do not have a visa. $ 25 is a huge amount to me
Click to expand...
Click to collapse
I don't think that is the case.
What I said was you don't need to install a custom recovery.
Give it a shot report back though. Worst that can happen is it does not work.
HT123 said:
I don't think that is the case.
What I said was you don't need to install a custom recovery.
Give it a shot report back though. Worst that can happen is it does not work.
Click to expand...
Click to collapse
Agreed. I was just pointing out that I was able to use kingroot and wolfdroid's method to permanent root a phone (albeit an lg phone) that had a locked bootloader. Other people also had success doing that as well on other brands of phones. Will it work on a Turbo with a locked bootloader? IDK. However I would not be surprised if it does. I had a Turbo with a locked bootloader but sold mine else I would try it myself.
classic757 said:
Agreed. I was just pointing out that I was able to use kingroot and wolfdroid's method to permanent root a phone (albeit an lg phone) that had a locked bootloader. Other people also had success doing that as well on other brands of phones. Will it work on a Turbo with a locked bootloader? IDK. However I would not be surprised if it does. I had a Turbo with a locked bootloader but sold mine else I would try it myself.
Click to expand...
Click to collapse
I agree, i apologize if it it came off otherwise. I think the question is if the sunshine process removes the protection and allow writing to the system partition. I unlocked prior to making my root permanent so i cant test again but am very interested to see if it works with a locked boot loader
HT123 said:
I agree, i apologize if it it came off otherwise. I think the question is if the sunshine process removes the protection and allow writing to the system partition. I unlocked prior to making my root permanent so i cant test again but am very interested to see if it works with a locked boot loader
Click to expand...
Click to collapse
My thinking it that it probably will work because temp root can be obtained on a locked bootloader Turbo with kingroot. It's just that kingroot is unstable and often times does not survive reboot. However, wolfdroid's method is similar to using SuperSu Me(or SuperSume). It removes kingroot and replaces it with SuperSu, which of course is more stable and survives reboot.
classic757 said:
My thinking it that it probably will work because temp root can be obtained on a locked bootloader Turbo with kingroot. It's just that kingroot is unstable and often times does not survive reboot. However, wolfdroid's method is similar to using SuperSu Me(or SuperSume). It removes kingroot and replaces it with SuperSu, which of course is more stable and survives reboot.
Click to expand...
Click to collapse
If security is disabled and the system can write to the system partition it will work, if not, then I assume Sunshine disables it in the process of unlocking the boot-loader. Hopefully someone with a stock Turbo who was going to unlock anyway can verify.
Not sure why you wouldn't want a custom recovery. With custom recovery you can make backups of your entire phone image in case you screw something up. Many times in the past I've flashed something that didn't work as I expected. And with ROOT, if you flash something you can screw up something system-related. Very easy to boot back into TWRP recovery and restore the previous day's backup I had made. Like a time machine to erase your mistake.
And it's FREE. Doesn't cost anything.
Yes, with Titanium Backup (a powerful app) you can restore previous versions of an another app. (I choose to save 3 days worth of apps in Titanium Backup.) But with a TWRP custom recovery backup (also called a "nandroid"), you can save and restore the ENTIRE phone, including all system apps, all settings, everything. Very powerful, useful tool.
I wouldn't have a rooted phone without custom recovery. That's one of the main reasons I always buy phones where I can unlock the bootloader -- to install custom recovery (like TWRP or CW) and root.
If you screw something up and come asking for help, the first thing someone is going to ask is, "Did you make a backup?" And they are talking about a custom recovery backup.
ChazzMatt said:
Not sure why you wouldn't want a custom recovery. With custom recovery you can make backups of your entire phone image in case you screw something up. Many times in the past I've flashed something that didn't work as I expected. And with ROOT, if you flash something you can screw up something system-related. Very easy to boot back into TWRP recovery and restore the previous day's backup I had made. Like a time machine to erase your mistake.
And it's FREE. Doesn't cost anything.
Yes, with Titanium Backup (a powerful app) you can restore previous versions of an another app. (I choose to save 3 days worth of apps in Titanium Backup.) But with a TWRP custom recovery backup (also called a "nandroid"), you can save and restore the ENTIRE phone, including all system apps, all settings, everything. Very powerful, useful tool.
I wouldn't have a rooted phone without custom recovery. That's one of the main reasons I always buy phones where I can unlock the bootloader -- to install custom recovery (like TWRP or CW) and root.
If you screw something up and come asking for help, the first thing someone is going to ask is, "Did you make a backup?" And they are talking about a custom recovery backup.
Click to expand...
Click to collapse
As far as why... some people like chocolate... some people like vanilla. The question is not the merits of a custom recovery, it is if one is required to have persistent root on the phone.
I personally don't care about a custom recovery. I prefer the stock rom at this point because without fail most custom roms have some minor bug that inevitably annoys the sh*t out of me. I want root because i want an ad blocker. I want an ad blocker because I use my phone as a proxy for web traffic on a computer with network monitoring software and i would prefer my internet traffic not be visible to my employer. There is zero reason for a custom recovery to do what i want to do.
Ok so i watch the youtube video on this and read though some of the Kingroot and Sunshine threads.
now i saw on Sunshine site (verizon3.2 for droid turbos) that Kingroot wasnt needed anymore to gain temproot. And this is only my sec droid that ive tried to root so forgive me for any mess ups. Aways i download sunshine. It ran its test on my phone, it said that everything was good it will work buy or code bla. So i buy it 25bones. It does what it does and works rebooted my phone says it unlocked(score) now doing a root test with Easy Root Checker say the a dont have root and that superuser: Unidentified Superuser. should i of done King Root before? What should i do now?
Being rooted is different from being unlocked.
Unlocking the bootloader allows changes to to be made to your device's operating system files that the manufacturer/carrier has blocked access to.
Root, meanwhile, is traditionally the username in Linux who has the highest level permission settings possible (ie. Superuser permissions).
Sunshine unlocks the bootloader; and Kingroot can also be used to gain permanent superuser level access your Droid Turbo. When you unlocked your phone, it only /temporarily/ rooted as part of the unlock process. Now what you need to do is go to kingroot.net and permanently root your phone.
Many people seem to like SuperSU better than Kingroot though. So after you get Kingroot to root your phone, go to the Play Store and get Super-Sume Pro. It automatically removes Kingroot and installs SuperSU. Oddly enough, though Super-Sume Pro does cost money to purchase from the Play Store initially, the Play Store's automatic refund policy kicks in if you uninstall it within 2 hours of purchase, and there's no reason to keep it after you've successfully run it once.
Sent from my XT1254 using Tapatalk
If your bootloader is unlocked, then install TWRP custom recovery and from there flash SuperSu. You will have a FREE solution and have both custom recovery and full root -- the best of both worlds.
Custom recovery lets you make image backups so you can restore your phone to an earlier point in time when everything was OK, if you screw up. Also lets you flash stuff like custom kernels and custom ROMs. But just the image backups is enough to have it.
When you install TWRP, if you try to exit without root it will ask if you want to flash SuperSu. It's included in TWRP. Or you can download SuperSu and flash it manually in TWRP. Your choice.
What chazzmatt said. Here are some basic links and instructions.
http://forum.xda-developers.com/showthread.php?p=64033988
Hello all. First time posting on the forum. I've looked up on how to root the Moto x 2nd gen, but most I find is for the xt1095. I've read some information on how to unlock the bootloader for the xt1097 (I'm on AT&T). But it all just seems so confusing. I can't seem to find a source that has all the information I need all in one. I've found info from different sources but I don't wanna mess anything up by miss connecting the dots. If anyone has had success or knowledge on how to root this type of phone, I'd be very grateful! Thank you!
USA1791 said:
Hello all. First time posting on the forum. I've looked up on how to root the Moto x 2nd gen, but most I find is for the xt1095. I've read some information on how to unlock the bootloader for the xt1097 (I'm on AT&T). But it all just seems so confusing. I can't seem to find a source that has all the information I need all in one. I've found info from different sources but I don't wanna mess anything up by miss connecting the dots. If anyone has had success or knowledge on how to root this type of phone, I'd be very grateful! Thank you!
Click to expand...
Click to collapse
Hey, welcome to our forum.
You can use Kingroot (a one click root app) to root your at&t xt1097.
Then, if you want to unlock the bootloader, you can do it ONLY with sunshine app (an app that unlocks the bootloader, simple either), but in order to use sunshine app you need to pay for license or something like that, about 20-25$.
Sunshine works only if you have root, so you have to use kingroot.
Kingroot will not always work, but it should. Use it until it works, many reported it took them more than once.
That happens because you don't have offical bootloader unlock.
Have fun
OrenGazala said:
Hey, welcome to our forum.
You can use Kingroot (a one click root app) to root your at&t xt1097.
Then, if you want to unlock the bootloader, you can do it ONLY with sunshine app (an app that unlocks the bootloader, simple either), but in order to use sunshine app you need to pay for license or something like that, about 20-25$.
Sunshine works only if you have root, so you have to use kingroot.
Kingroot will not always work, but it should. Use it until it works, many reported it took them more than once.
That happens because you don't have offical bootloader unlock.
Have fun
Click to expand...
Click to collapse
Hey thank you for the information!! On the kingroot it said my phone was rooted, but then once I tried to do sunshine app, it said my phone was not rooted so I couldn't do that. Any idea why that is? Also, is kingroot and sunshine app the only thing I have to do? Or is after the bootloader unlocked there's other steps I must take to root the phone?
Was finally able to get kingroot to work and sunshine to unlock the bootloader after I did a factory reset. Now I'm confused as whats next. I read something about twrp and flashing logo?
I'm not trying to unlock the bootloader, only root the phone. KingRoot says "root successful," I download supersu, and it says my root binary (or something) isn't installed. However, SuperSu isn't able to install the binary for me.
An even worse problem: after KingRoot says "root successful" I check RootChecker, and it tells me I am NOT rooted. Also, every time I reboot, KingRoot claims I am not rooted. This makes me think that KingRoot incorrectly thinks it's rooted my phone. Because no other app seems to think I'm rooted, and when I reboot not even KingRoot thinks I'm rooted.
Finally, many of the KingRoot tutorials (as well as the app itself) say that KingRoot will likely reboot your phone a few times before it roots, and that after it roots it your phone will reboot. However, KingRoot has never rebooted my phone ONCE. This also adds evidence to my hypothesis that KingRoot incorrectly thinks it's rooting me. When I run KingRoot, it tells me not to be afraid if my phone reboots; well I am afraid because my phone is NOT rebooting.
Vegerot said:
I'm not trying to unlock the bootloader, only root the phone. KingRoot says "root successful," I download supersu, and it says my root binary (or something) isn't installed. However, SuperSu isn't able to install the binary for me.
An even worse problem: after KingRoot says "root successful" I check RootChecker, and it tells me I am NOT rooted. Also, every time I reboot, KingRoot claims I am not rooted. This makes me think that KingRoot incorrectly thinks it's rooted my phone. Because no other app seems to think I'm rooted, and when I reboot not even KingRoot thinks I'm rooted.
Finally, many of the KingRoot tutorials (as well as the app itself) say that KingRoot will likely reboot your phone a few times before it roots, and that after it roots it your phone will reboot. However, KingRoot has never rebooted my phone ONCE. This also adds evidence to my hypothesis that KingRoot incorrectly thinks it's rooting me. When I run KingRoot, it tells me not to be afraid if my phone reboots; well I am afraid because my phone is NOT rebooting.
Click to expand...
Click to collapse
Vegerot,
KingRoot accomplishes what's called a temp root (temporary root). After you reboot your phone, the temp root files will be deleted and you will not have root anymore. Also, installing a SuperSu binary will not work with a temp root. If you want to perm root your phone (permanent root), you will need to use KingRoot to root your phone (may take a couple of tries) and then you will need to use Sunshine to unlock your bootloader. After it is unlocked, you can flash a custom recovery and install the SuperSu binary.
Secondly, I've had that problem before. I would recommend using the PC version first, (which is in Chinese, but is easy to figure out) which will attempt the root, and if that doesn't work, use the phone version right after using the computer one. As I mentioned before, KingRoot is a temporary root that goes away after a reboot.
Lastly, usually reboots are not a measure of success. When I rooted, I did not reboot that often, so you should not be worried. If you think that something is not working, again, use the PC version; it seems to have a better success rate.
Contact me if you need any help.
R55770 said:
Vegerot,
KingRoot accomplishes what's called a temp root (temporary root). After you reboot your phone, the temp root files will be deleted and you will not have root anymore. Also, installing a SuperSu binary will not work with a temp root. If you want to perm root your phone (permanent root), you will need to use KingRoot to root your phone (may take a couple of tries) and then you will need to use Sunshine to unlock your bootloader. After it is unlocked, you can flash a custom recovery and install the SuperSu binary.
Secondly, I've had that problem before. I would recommend using the PC version first, (which is in Chinese, but is easy to figure out) which will attempt the root, and if that doesn't work, use the phone version right after using the computer one. As I mentioned before, KingRoot is a temporary root that goes away after a reboot.
Lastly, usually reboots are not a measure of success. When I rooted, I did not reboot that often, so you should not be worried. If you think that something is not working, again, use the PC version; it seems to have a better success rate.
Contact me if you need any help.
Click to expand...
Click to collapse
Thank you! Is it possible to use the TempRoot to remove bloatware?
Vegerot said:
Thank you! Is it possible to use the TempRoot to remove bloatware?
Click to expand...
Click to collapse
Yep. In the KingRoot app, after you have successfully rooted, you can uninstall the bloat apps.
---------- Post added at 07:47 PM ---------- Previous post was at 07:44 PM ----------
USA1791 said:
Was finally able to get kingroot to work and sunshine to unlock the bootloader after I did a factory reset. Now I'm confused as whats next. I read something about twrp and flashing logo?
Click to expand...
Click to collapse
After I unlocked my bootloader, I first flashed TWRP through the bootloader. I then did a full backup and installed a ROM. Flashing a LOGO is optional as it only changes the logos before the actual boot animation.
Contact me if you need any help with flashing or anything else.
After unlocking the bootloader, I'm having trouble installing Marshmallow. I tried following this tutorial but it hasn't helped either. This is my problem with that tutorial:
"When I run "fastboot flash system..." I'm stuck on "waiting for devices." Also, "fastboot devices" returns nothing. However, adb devices returns my phone.
Also, instead of system.img, the download link you provided gave me boot.img (along with a META-INF and system folder).
When entering TWRP, why must we go through that bootloader interface? I just do "adb reboot recovery" and that also opens TWRP.
Since fastboot isn't working, is there a way to do it through the TWRP GUI? Such as copying the file to my phone and then doing something with that?
Something strange happened. I decided to download the Marshmallow .zip on my phone, then booted into recovery and went to Install, and selected that file. I thought I would get an error (I'm trying to flash my phone from a file stored on my phone (therefor deleting itself)), but I didn't. I rebooted and all my apps were still there from before and my background, but the settings app says I'm running Android 6.0. What exactly happened?
There are some unexpected things happening though. For examples, I cannot swipe down with 2 fingers to access my quick settings In addition, the home button will not take me back to my app launcher (I have to tap the multitasking button THEN tap the home button to return to the launcher). When I look at my notifications, it still says "AT&T" at the bottom. Is that supposed to happen? This doesn't feel right and I would like to use the method you recommended in the article, but for now this is the only thing that will work.
"
????
Kingroot not works on my moto x 2nd gen xt1097 at&t ... How it works??
Como ser root
Ver contraseñas