Related
I was getting "Failed to boot 2 starting RSD mode" error and when my Atrix tried to reboot to install the OTA update. The only way I could get to boot again was to remove the battery and put it back, and after that, it boots normally to the home screen, and after the SD card gets mounted it shuts down to try to install the OTA update and you get the same error again.
I got it working again by following the suggestions from Atrixforums.com. What I did was to flash my phone with RDS lite v5.6 using the file 1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011 and that fixed my phone and it’s been working normally.
If you can get your phone to the home screen without rebooting or you get a different type of error, you could try the Automated Update (PC Users Only) from Motorola website (I need confirmation if this would work with a unlocked bootloader)
Details:
My phone was using the stock rom version 2.3.4
Rooted (I did not remove the root access before applying OTA 4.5.141 and this is reason why I got in this problem)
Locked bootloader (I am not sure if this would work with unlocked bootloader)
Unlocked sim card
I hope it helps,
Already posted in Dev section:
Warning 1
Warning 2
Search before posting :>
Alaq said:
Already posted in Dev section:
Warning 1
Warning 2
Search before posting :>
Click to expand...
Click to collapse
Those threads reference problems with unlocked phones. The OP has a rooted phone that is not unlocked. So, not a dupe per se.
That said, I upgraded my rooted-only phone with no issues. I rather suspect the OP may have unlocked his bootloader and forgotten about it.
You can OTA 141 with a locked and rooted phone. Just be sure to unroot (you need to do this manually if you ever used the fastboot preinstall method) and make sure everything is back to stock. If you used oneclick or any other root method that has an unroot, manually verify it really removed everything (su, superuser.apk, etc).
gnahc79 said:
You can OTA 141 with a locked and rooted phone. Just be sure to unroot (you need to do this manually if you ever used the fastboot preinstall method) and make sure everything is back to stock. If you used oneclick or any other root method that has an unroot, manually verify it really removed everything (su, superuser.apk, etc).
Click to expand...
Click to collapse
I have used the one click easy method only and nothing else. And I agree with you, it seems that not unrooting your phone before the OTA update creates this problem. I’ll be more careful the next time when the ICS it’s available.
I just want people like me that it’s not been in the android scene for long, do not get in to this kind of problems.
It would probably be a good idea to post a check list every time a new update comes up, reminding us of the precautions that we must have. Because even if you know what you are doing If you forget just one little change you made it could lead to some problems.
Greetings,
btw, here is what I did to unroot prior to the 141 update. I rooted 2.3.4 with the fastboot preinstall method...no idea if this unroot method cleans up the one click method.
link
1. Open Android Terminal Emulator
2. Type in the following commands, hitting ENTER after each line of code: (after typing 'su' below, look for the Superuser request and approve it, you can only continue if you get the # prompt.
Code:
su
mount -o rw,remount /dev/block/mmcblk0p12 /system
mount -o rw,remount /dev/block/mmcblk0p17 /preinstall
rm /system/bin/su
rm /preinstall/sqlite3
rm /preinstall/dosu
rm /preinstall/Superuser.apk
rm /preinstall/su
reboot
3. Let the phone reboot fully and then go into Settings > Applications > Manage Applications > find Superuser and uninstall it just like any other app.
Click to expand...
Click to collapse
I am was also facing the same issue with OTA. I finally managed to update my rooted, locked phone via USB method using Motorola Software Updater.
Root is lost after the update.
I did the OTA on my atrix which was locked and rooted. Updated fine without any problems, but I did lose root. Can't figure out which method is safe to use to re-root.
http://www.android-advice.com/2012/root-the-motorola-atrix-4g-running-4-5-141/
k00ey said:
I did the OTA on my atrix which was locked and rooted. Updated fine without any problems, but I did lose root. Can't figure out which method is safe to use to re-root.
Click to expand...
Click to collapse
live4nyy said:
http://www.android-advice.com/2012/root-the-motorola-atrix-4g-running-4-5-141/
Click to expand...
Click to collapse
I used this method and it worked fine. It did give an error message that superuser was already installed but it rooted the phone anyway.
Sent from my MB860 using Tapatalk
live4nyy said:
http://www.android-advice.com/2012/root-the-motorola-atrix-4g-running-4-5-141/
Click to expand...
Click to collapse
Thank you! Worked great.
charlyee said:
I used this method and it worked fine. It did give an error message that superuser was already installed but it rooted the phone
Click to expand...
Click to collapse
Charlyee, did you unroot your 4G with the preinstall method prior to following these instructions? Please confirm. Thanks!
badnokia said:
Charlyee, did you unroot your 4G with the preinstall method prior to following these instructions? Please confirm. Thanks!
Click to expand...
Click to collapse
I did the root saver method but I had all kinds of problems doing the OTA, so I ended up by downloading the software from the Moto website via USB.
At that point my Atrix was unrooted, but I don't know if it was the root saver method or download of the software.
I tried Motofail to root as well but that didn't work.
Hope that helps.
Sorry, didn't mean to write a thesis in answer to a simple question.
Sent from my MB860 using Tapatalk
Is it safe to use the aRoot unroot method if my Atrix is rooted and unlocked in order to update to 4.5.191?
Confirmed Success: Unroot, OTA Update, Root
Sorry if this info is redundant, but I'm super paranoid about the OTA updates & wanted to confirm what I did worked for my rooted, but locked Atrix 4G:
1) Unrooted with the directions on this page: http://www.atrixforums.com/forum/mo...ons-including-stock-locked-2-3-4-2-3-6-a.html
2) Ran OTA update
3) Rooted again with the following instructions: http://www.android-advice.com/2012/root-the-motorola-atrix-4g-running-4-5-141/
I just did sucessful update on my unlocked and rooted Motorola Atrix 4G (MB860) from 2.3.4 to 2.3.6 via RSDLite 5.6, and 1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf SBF file.
Windows 7 64-bit Ultimate. Everything passes O.K.
I had this happen on my atrix rooted no unlocked bootloader I reflashed with the above method nd success. I unrooted my wife's atrix first and installed the ota with no problems. So unroooting first seemed to work.
Sent from my MB860 using XDA App
I did not have a problem at all updating to 4.5.141 with a rooted phone minus the fact I lost root until I saw the link live4nyy posted.
Just an FYI for others like me that have been waiting to pull the trigger on the update.
I was rooted with the /preinstall (briefmobile) method (had never unlocked the bootloader). I read conflicting reports on whether OTA would work, and for some reason I couldn't get the Motoroloa update program to see my phone. Rather than figuring out why it wasn't seeing my phone, I did the "unroot" steps listed by gnahc79 in this thread and then let the phone update OTA and then rooted again using the /preinstall method.
The whole process took about 30 minutes, most of that was the OTA download and install.
Did you guys have to re-hack mobile hotspot after the OTA update?
Sent from my Motorola 2-way pager
Are the root methods too complicated/risky for you? This is a simple solution.
Start with: original droid maxx software (12.7.7 i believe) on Verizon
1. Install motoroot 1.0 (JCase's first root method from original development section), run it, and click root (that's click #1). Make sure everything's working, reboot a few times, use rootchecker to make sure you've got root. (note you won't have write protection off and there'll be a 10-15 sec delay after booting up before you have root). But hey, it's 1 click.
2. Take 1st Verizon OTA to the 4.2.2 with camera update (12.15.15 i believe). Root should survive. Check that it did with root checker.
3. Install the write protection no more from the moto x original development section on your computer. download android-sdk and make sure adb is working, make sure fastboot is working. connect your phone to your computer and run the "write protectoin no more" app on your computer (that's click #2).
That's it. Now I have write protection permanently off, and I have root. I didn't have to use cydia impactor and mess with a tricky update to 4.4 which if it doesn't work I couldn't go back to a rooted phone. I never had to fxz anything or restore anything to stock, or lose any of my data. I didn't have to pay a dime or give someone on ebay all my phone info.
Sure I'd like to have 4.4, but pretty happy with where I am and how easily I got here. And I've read a lot of people say "the root methods are too complicated" --- well this is pretty easy cause you're just using 2 packaged apps.
I've gotten a lot from this forum, and just thought I'd share. Please don't flame. I feel like this is the best compromise of features:effort for me.
It was really easy to put an unlock code into adb.
Sent from my XT1080 using Tapatalk
Piaband said:
It was really easy to put an unlock code into adb.
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
if i could unlock it when i had gotten it in august, sure. but it's too much effort to start over at this point. i have everything set up perfectly. never had to start over. also didn't want to pay for it and send my info to some stranger on the internet. anyway, moot point. good for you, but that option's not available for most people.
So does this work when your already updated to 4.4?
Sent from my XT1080 using XDA Premium 4 mobile app
No nothing roots 4.4 at this point.
vegasdgk said:
So does this work when your already updated to 4.4?
Sent from my XT1080 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No he basically just rewrote the instructions of how to root the original firmware.
akellar said:
No he basically just rewrote the instructions of how to root the original firmware.
Click to expand...
Click to collapse
I didn't rewrite it. No where are there instructions for getting root AND write protection off on the 4.2.2 camera update without 1 using command line commands AND 2 that network based program (called Cydia compactor I think). There's none of those complications here. Most people don't even realize 1 click root survives the camera update.
But you are right as to kit kat. I thought my title was clear that this is for jellybean though.
mistermojorizin said:
Are the root methods too complicated/risky for you? This is a simple solution.
Start with: original droid maxx software (12.7.7 i believe) on Verizon
1. Install motoroot 1.0 (JCase's first root method from original development section), run it, and click root (that's click #1). Make sure everything's working, reboot a few times, use rootchecker to make sure you've got root. (note you won't have write protection off and there'll be a 10-15 sec delay after booting up before you have root). But hey, it's 1 click.
2. Take 1st Verizon OTA to the 4.2.2 with camera update (12.15.15 i believe). Root should survive. Check that it did with root checker.
3. Install the write protection no more from the moto x original development section on your computer. download android-sdk and make sure adb is working, make sure fastboot is working. connect your phone to your computer and run the "write protectoin no more" app on your computer (that's click #2).
That's it. Now I have write protection permanently off, and I have root. I didn't have to use cydia impactor and mess with a tricky update to 4.4 which if it doesn't work I couldn't go back to a rooted phone. I never had to fxz anything or restore anything to stock, or lose any of my data. I didn't have to pay a dime or give someone on ebay all my phone info.
Sure I'd like to have 4.4, but pretty happy with where I am and how easily I got here. And I've read a lot of people say "the root methods are too complicated" --- well this is pretty easy cause you're just using 2 packaged apps.
I've gotten a lot from this forum, and just thought I'd share. Please don't flame. I feel like this is the best compromise of features:effort for me.
Click to expand...
Click to collapse
Hello,
I have rooted my phone when i am in 12.7.7, then i took the OTA update 12.15.15, now my device is in a boot loop, it boots normally and after a few seconds it will reboot and it goes over and over again.
any thoughts on this and should I use RSDLite to flash it to either 12.7.7 / 12.15.15???
-Zeta- said:
Hello,
I have rooted my phone when i am in 12.7.7, then i took the OTA update 12.15.15, now my device is in a boot loop, it boots normally and after a few seconds it will reboot and it goes over and over again.
any thoughts on this and should I use RSDLite to flash it to either 12.7.7 / 12.15.15???
Click to expand...
Click to collapse
which method did you use to root it? what system stuff did you change after rooting it?
a lot of people had bootloops after taking an OTA because they did the root method that had replaced their stock recovery with a write protect off mode. so in effect, they were having bootloops because they didn't have the recovery, not because they had root. it their case, there was an easy solution of just flashing a recovery. unfortunately i don't know the details of how to do that off the top of my head.'
in any case, rsd'ing to either of those software versions will likely fix all problems.
i rooted as i described with motoroot 1.0, which didn't affect my recovery and was easy to OTA without problems.
good luck
mistermojorizin said:
which method did you use to root it? what system stuff did you change after rooting it?
a lot of people had bootloops after taking an OTA because they did the root method that had replaced their stock recovery with a write protect off mode. so in effect, they were having bootloops because they didn't have the recovery, not because they had root. it their case, there was an easy solution of just flashing a recovery. unfortunately i don't know the details of how to do that off the top of my head.'
in any case, rsd'ing to either of those software versions will likely fix all problems.
i rooted as i described with motoroot 1.0, which didn't affect my recovery and was easy to OTA without problems.
good luck
Click to expand...
Click to collapse
Thanks for the quick reply,
I used the PwnMyMoto here to root, i forgot that this method will replace / remove the stock recovery.
With a minute of panic and some google search, I'd managed to use RSD lite to flash the 12.15.15 FXZ and now my phone is back in business but kinda lost root.
Right now I am looking into the RockMyMoto method here and see if it can help me to gain root.
-Zeta- said:
Thanks for the quick reply,
I used the PwnMyMoto here to root, i forgot that this method will replace / remove the stock recovery.
With a minute of panic and some google search, I'd managed to use RSD lite to flash the 12.15.15 FXZ and now my phone is back in business but kinda lost root.
Right now I am looking into the RockMyMoto method here and see if it can help me to gain root.
Click to expand...
Click to collapse
glad you got your phone back in order, might want to check out slapmymoto (which is the path to rooted kit kat and involves running rockmymoto on the way) while you're at it
mistermojorizin said:
glad you got your phone back in order, might want to check out slapmymoto (which is the path to rooted kit kat and involves running rockmymoto on the way) while you're at it
Click to expand...
Click to collapse
Not sure about the battery life on kitkat of the MAXX right now, so i will stick with 4.2.2 first and do a little research.
Anyway, thanks for the reply and I've gained root on 4.2.2 (12.15.15) using RockMyMoto:laugh:
I've just read about this method by Geohot
http://towelroot.com/
The kernal exploit will allow root for almost all android phones. This includes Moto G, Nexus 5, and Samsung S5.
basestamp said:
I've just read about this method by Geohot
http://towelroot.com/
The kernal exploit will allow root for almost all android phones. This includes Moto G, Nexus 5, and Samsung S5.
Click to expand...
Click to collapse
I think you missed the part that it doesn't work with Moto X/Ultra/Maxx due to Moto's /system write-protection. In it's current state it doesn't help.
Yep, I couldn't get it to work on an unrooted Droid Mini. It just sits there at the screen that says you'll have root in 15-seconds, but it didn't reboot even after half an hour.
I even tried it on a rooted Droid Mini and it did the same thing. Reason for trying on a rooted phone, is on a few other Moto devices like my RAZR M, it opened up a long-ago closed vulnerability where bootloader could be unlocked with Motopocalypse. Too bad it didn't work. I don't really want to drop $45 for a BL unlock which likely wouldn't work on my phone anyway since it was manufactured 9/2013.
It didn't reboot on my maxx either I just rebooted manually then opened SuperSU and installed binaries and it rooted. I can't speak to write protection since I'm unlocked. But it will definitely root the phone.
Sent from my XT1080 using XDA Premium 4 mobile app
I tried that, but SuperSU said, "There is no SU binary installed, and SuperSU cannot install it. This is a problem." Rootchecker also said, "This device does not have proper root access."
Just to make sure, I just tried it again and got the same thing. Not sure what I did wrong. Are you on 19.5.3 or 19.6.3? I tried it on the latter.
6.3
Sent from my XT1080 using XDA Premium 4 mobile app
GnatGoSplat said:
I tried that, but SuperSU said, "There is no SU binary installed, and SuperSU cannot install it. This is a problem." Rootchecker also said, "This device does not have proper root access."
Just to make sure, I just tried it again and got the same thing. Not sure what I did wrong. Are you on 19.5.3 or 19.6.3? I tried it on the latter.
Click to expand...
Click to collapse
He has an unlocked bootloader, meaning /system write-protect is off as well.
MOD EDIT @gregbradley
Also, users should be aware that Kingo root sends your IMEI to an unknown IP address in china during the root process, you have been warned. For more information read the whole OP here
Getting ROOT rights to Android 5.0 Lollipop (KingRoot) It is not my work. Taken from a russian forum.
1.Download and install latest version of Kingroot to phone.
2.Run the application and get the Root. Important - do not restart the device, because it can lead to failure in obtaining Root.
3.Enable "USB debugging" and "unknown sources".
4.Install the latest version from the PC XZDualRecovery to get full access to reading and writing to the section System (connect your phone to a PC via a cable, run the install.bat to select a number " 1 "on the screen to confirm a request for superuser)
5.Phone will reboot automatically to recovery. Install supersu.
6.Boot
Files to root.
https://mega.co.nz/#!eUgAiSDZ!R1bU-_hIxa2GW11Pjd8ikc-AzfbbJsoAXWkh7DG8j1A
isaekrem said:
Getting ROOT rights to Android 5.0 Lollipop (KingRoot) It is not my work. Taken from a russian forum.
1
Click to expand...
Click to collapse
I've been waiting for a one click root, but everything I'm reading says this is really sketchy and no one is quite sure what it is doing.
Can anyone confirm working on Z3?
For which phone? T-Mobile?
se1zure31 said:
For which phone? T-Mobile?
Click to expand...
Click to collapse
Tested by owner z3c.
And I tested on my phone D6603.
Is everything working good ???
Also, users should be aware that Kingo root sends your IMEI to an unknown IP address in china during the root process, you have been warned.
gregbradley said:
Also, users should be aware that Kingo root sends your IMEI to an unknown IP address in china during the root process, you have been warned.
Click to expand...
Click to collapse
Thanks.........for the information.
gregbradley said:
Also, users should be aware that Kingo root sends your IMEI to an unknown IP address in china during the root process, you have been warned.
Click to expand...
Click to collapse
Correct me if I'm wrong, but Kingo root is not the same as this, which is King Root?
haste75 said:
Correct me if I'm wrong, but Kingo root is not the same as this, which is King Root?
Click to expand...
Click to collapse
AFAIK they are the same
haste75 said:
Correct me if I'm wrong, but Kingo root is not the same as this, which is King Root?
Click to expand...
Click to collapse
Yes they are the same ...
Well, I couldnt resist. I've now got a working root with SuperSU, and have removed all I can find of the KingRoot app.
So far, seems to be working well.
Someone else tried it?
haste75 said:
Well, I couldnt resist. I've now got a working root with SuperSU, and have removed all I can find of the KingRoot app.
So far, seems to be working well.
Click to expand...
Click to collapse
Were you able to remove KingUser and install SuperUser?
scoder said:
Were you able to remove KingUser and install SuperUser?
Click to expand...
Click to collapse
Yes I believe so. I have the Kinguser icon in my app draw, but It wont open. I deleted all files associated with King via ES Root Explorer, and cannot find anything.
I still wouldn't recommend anyone else doing this, god knows what information was sent to China upon installing it, but I really wanted root.
haste75 said:
I still wouldn't recommend anyone else doing this, god knows what information was sent to China upon installing it,
Click to expand...
Click to collapse
But if try to isolate PC and phone from the internet during installing?
artlov said:
But if try to isolate PC and phone from the internet during installing?
Click to expand...
Click to collapse
I tried that, it needs internet connectivity. However, the reason I allowed this was I understand that this root is based on a Ping exploit, which would need internet connecivity to work.
I figured the risk werent THAT high for me. I dont re-use passwords and no bank details stored on my phone.
Can confirm this method works.
You might want to try going in Airplane mode if you're paranoid for the Chinese. In any case, Kingroot + XZDR + SuperSU 2.49 works perfectly.
It works for me I can confirm now.I have root on lollipop locked bootloader so nice haha ? thanks
E66666666 said:
Can confirm this method works.
You might want to try going in Airplane mode if you're paranoid for the Chinese. In any case, Kingroot + XZDR + SuperSU 2.49 works perfectly.
Click to expand...
Click to collapse
did you flash the recovery?
krugu said:
did you flash the recovery?
Click to expand...
Click to collapse
Not yet will do tomorrow, now I accidentally cleared the data of kinguser and now any app can't recognize root on my devices although it's installed, it says root denied, but şu binaries are installed, I will try tomorrow the recovery after school, if it really works I will release my ultimate sound mod I'm working since months and ofc I can test it myself and don't need any testers hope the pc cam.recognize the root on my.device and install the .bat files
Hello everyone,
Today I was able to root the VZW Moto E 2015 with the Kingroot app on 5.1. The Kingroot app said there was a method available and I decided to try it.
Simply install the app on your phone here: http://forum.xda-developers.com/devdb/project/dl/?id=16614
The root sticked for me upon reboot!
**I later found it was a hobbed root. You can't make changes to the system partition but you do have SU capabilities. (like you can run hidden apps and menus or block system apps, not remove them)
I still got root failed
Sent from my SM-G900P using Tapatalk
lvpre said:
I still got root failed
Sent from my SM-G900P using Tapatalk
Click to expand...
Click to collapse
You downloaded the latest one right? Keep trying rebooting the device. That is what I had to do.
After 3rd try it worked !!! thanks OP!
Edit: root lost after reboot
...but is it full root, with full /system read-write access? Some people have been able to get hobbled root via Kingroot on 5.0.2, but /system remained read-only.
slinson said:
After 3rd try it worked !!! thanks OP!
Edit: root lost after reboot
Click to expand...
Click to collapse
Keep trying make sure you have latest Kingroot, keep rebooting
xtermmin said:
...but is it full root, with full /system read-write access? Some people have been able to get hobbled root via Kingroot on 5.0.2, but /system remained read-only.
Click to expand...
Click to collapse
I don't know, root checker works. How do I test?
andrewwm said:
I don't know, root checker works. How do I test?
Click to expand...
Click to collapse
Choose a bloatware app that you don't mind losing, such as NFL Mobile. If you "Disabled" it in Settings > Apps, re-enable it.
Install a file manager that has the ability to browse/edit the full filesystem, such as Amaze (https://f-droid.org/repository/browse/?fdid=com.amaze.filemanager) or Root Explorer (in Play Store).
Open up the app and go into /system/app or /system/priv-app and look for the folder related to NFL Mobile (you'll know it's the right folder if the apk inside of it has the NFL Mobile logo). Delete it. If it deletes, that's a good sign. Reboot and see if the NFL Mobile icon is still in the app drawer, and open up the file manager again and verify that the files you've deleted have stayed deleted.
Get hype boiz
xtermmin said:
Choose a bloatware app that you don't mind losing, such as NFL Mobile. If you "Disabled" it in Settings > Apps, re-enable it.
Install a file manager that has the ability to browse/edit the full filesystem, such as Amaze (https://f-droid.org/repository/browse/?fdid=com.amaze.filemanager) or Root Explorer (in Play Store).
Open up the app and go into /system/app or /system/priv-app and look for the folder related to NFL Mobile (you'll know it's the right folder if the apk inside of it has the NFL Mobile logo). Delete it. If it deletes, that's a good sign. Reboot and see if the NFL Mobile icon is still in the app drawer, and open up the file manager again and verify that the files you've deleted have stayed deleted.
Click to expand...
Click to collapse
Wow. Everything fails. Kingroot says I got root and stays upon reboot. Titanium Backup acts like it woks but resets after reboot. Very weird.
andrewwm said:
Wow. Everything fails. Kingroot says I got root and stays upon reboot. Titanium Backup acts like it woks but resets after reboot. Very weird.
Click to expand...
Click to collapse
Yeah, looks like you have hobbled root. While the su binary is installed, the system partition is still in read-only mode. While you'll be able to use apps that only need root privileges to read files/settings, you won't be able to edit the system itself.
Has anybody got it working? What are some signs of it working (i.e. 2 reboots, no reboot, etc.)?
andrewwm said:
Keep trying make sure you have latest Kingroot, keep rebooting
Click to expand...
Click to collapse
It is indeed the latest Kingroot
Also tried for 50+ times maybe, sometimes got root sometimes failed---even if got root, always lost root after reboot
andrewwm said:
Hello everyone,
Today I was able to root the VZW Moto E 2015 with the Kingroot app on 5.1. The Kingroot app said there was a method available and I decided to try it.
Simply install the app on your phone here: http://forum.xda-developers.com/devdb/project/dl/?id=16614
The root sticked for me upon reboot!
**I later found it was a hobbed root. You can't make changes to the system partition but you do have SU capabilities. (like you can run hidden apps and menus or block system apps, not remove them)
Click to expand...
Click to collapse
If someone gets root again, try to run Sunshine (bootloader unlock). You don't have to pay to see if it'll work.
As a heads up, sunshine fails with an error telling you to contact the sunshine support with your IP address if it continues.
Also, was able to back up the existing boot and recovery using flashify. I flashed the typical recovery used for other surnia devices, but when I tried to boot into recovery, it failed.
It got hung up in fastboot and gave check errors.
It did not keep me from booting back into the rom, so I was able to reflash the original recovery after re-rooting.
Yes, is only temporary root for me on 5.1.
I purchased supersume earlier today with the hopes of ridding myself of kingroot, but it immediately force closes. I trust the kr app about as much as I trust esfile explorer now...
Moto e root ,marshamalllow
Hi,I don't know that andriod 5.1 can be rooted by kingo root,so I upgraded to andriod 6.0,after update I tried to root ,the rooting process stops at 70percent,,, so any one help me ,how to root moto e 2015 marshmallow,,,any body have idea
Arunsunny009 said:
Hi,I don't know that andriod 5.1 can be rooted by kingo root,so I upgraded to andriod 6.0,after update I tried to root ,the rooting process stops at 70percent,,, so any one help me ,how to root moto e 2015 marshmallow,,,any body have idea
Click to expand...
Click to collapse
If you have Android 6.0, you do not have the XT1528.
Your device (XT1521 or similar) can be bootloader unlocked and you can install a custom recovery and can flash root.
The device being discussed in this topic (XT1528) cannot be bootloader unlocked.
Hi, I want only simple root I should not want to unlock boot loader and twrp recovery,,, because I don't have pc,, I want to root with phone,,,can you help me regarding this,,,thank you for you response
Arunsunny009 said:
Hi, I want only simple root I should not want to unlock boot loader and twrp recovery,,, because I don't have pc,, I want to root with phone,,,can you help me regarding this,,,thank you for you response
Click to expand...
Click to collapse
Not possible. The only known way to have permanent full root is to unlock the bootloader. Unlocking the bootloader is necessary to make /system mount as read-write.
Yes, I understand.can you please send me the procedure to unlock the bootloader.so no body have mentioned correctly in websites and YouTube... So send me the steps to unlock bootloader and root the andriod