Related
XOOM2/Xyboard Everything root and more!
From 26/03/2014, I will no longer be updating this post as I no longer have the device and Motorola won't be upgrading the device further. Please instead of sending me PMs, go to the Q&A board or post your comment on this thread.
Note: This method will not work on Windows 8. Only Windows XP, Vista, 7, Linux and Mac OS X is supported.
Root Method - Honeycomb
1. Download the Windows version here, or the Linux/OSX version here.
2. Your Computer must have Motorola Drivers installed before rooting and connect your device with debugging on to your computer via USB. (Mac Users don't need drivers)
3. Extract the zip file from the download link, and run “run.bat” (on Windows) or “run.sh” from a terminal (on Linux/OSX)
4. Your device should reboot a few times during the process, don't worry.
5. Then you should see a finished message on the Root Method Window. At this point your device is safe to be removed from the computer.
7. As you are running Honeycomb if you are reading this then you should be receiving the ICS OTA soon. So lets backup your root so you can restore everything root after the upgrade (saves time). Download OTA Rootkeeper and backup root.
6. Well Done! You have root. Enjoy root and be safe.
Blog Post: Here
Root Method - Ice Cream Sandwich
1. Connect your Xoom2/Xyboard via USB to your Windows PC. Install Motorola Drivers from here.
2. Under Settings > Developer Options > Hit the "Enable USB Debugging" selection.
3. Download the Root Installer from here. (Says for Droid RAZR but also works on Xyboard and Xoom 2]
4. Unzip the download.
Bootstrap/Safestrap[Custom Recovery]
Waring: DO NOT proceed if you are inexperienced. bootstrap is messy and is only needed once we have ROMs cooking. All questions about the recovery ask in the developer thread.
1. Install the Bootstrap APK file.
2. Allow Superuser Powers.
3. Read the instructions which is displayed on the user interface.
5. You will now see a splashscreen after you reboot (before boot animation), here you can decide if you want to enter recovery or continue with boot.
-Method Under Constuction-
Unroot or temporary unroot
Temp Unroot - If you need to unroot for any reason and come back at any time, then install OTA Rootkeeper and then select the option "temp unroot). This will remove root without restarting and you can restore by a touch of a button.
Full remove of Root - If you want to complety remove root all together, if you need to send in your device for repair or trading your device. Install Ginger Unroot and continue with the onscreen instructions. This application has confirmed to work on the Xoom2/Xyboard.
Doing it right now
Linux version has a wrong link or not uploaded yet
mdcykkk9 said:
Linux version has a wrong link or not uploaded yet
Click to expand...
Click to collapse
Should be working now.
Thx is working now . i just made a donation to his paypal account. i hope for future support for the tablet .
Thanks, is good news. Now we just need that we have updates to fix bugs, and if it can be ics ...
This is worth a donation to continue the work.
édit : error, sorry, it's ok
Working well ! Thank you.
I rooted my Xoom 2 ME bought in France.
But I cannot update to 3.2.2 ???
My build 1.6.0_218.3-MZ607 ,current version 3.2
Would this work for Xoom 1 wi-fi version ?
ouatitw said:
Would this work for Xoom 1 wi-fi version ?
Click to expand...
Click to collapse
This root method should work on all Motorola Devices running honeycomb or gingerbread. Try it out and see if it does
Sent from my Motorola Xoom 2
I did the US ICS update on My UK Xoom so im on 4.03 at the moment - i believe Motorola added some file which prevents me so far from rooting with the current one click programs ? so would it be safe to try this ?
ouatitw said:
I did the US ICS update on My UK Xoom so im on 4.03 at the moment - i believe Motorola added some file which prevents me so far from rooting with the current one click programs ? so would it be safe to try this ?
Click to expand...
Click to collapse
The method is safe to try but Email Dan if you have any issues when rooting.
Thanks a lot Dan Rosenberg,
Suppose i root my device and if i need to use my warranty at later point of time.
Is there is anyway that i can hide Motorola that i have rooted my device.
luke.arran said:
The method is safe to try but Email Dan if you have any issues when rooting.
Click to expand...
Click to collapse
I wouldn't email Dan, I'd post it here... Dan probably has more than enough things going on than to answer all rooting questions on here...
This root method very well may work on the Xoom with ICS, never hurts to try it. I don't see how you can't root with an existing method though, with the Xoom being fully unlockable and all...
Elysian893 said:
I don't see how you can't root with an existing method though, with the Xoom being fully unlockable and all...
Click to expand...
Click to collapse
the thing is that maybe you can, but you might not want to Unlocking wipes all your data, apps, etc and also permanently sets a variable stating that your warranty is gone.
It might, for example, be desireable to create a backup of all your apps and data using titanium backup, which requires root, before unlocking your xoom.
Does this mean that more knowledgeable folks can create custom ROMs now, or does that still require an unlocked bootloader?
Trackz said:
Does this mean that more knowledgeable folks can create custom ROMs now, or does that still require an unlocked bootloader?
Click to expand...
Click to collapse
No, we need to figure out a bootstrap for custom roms. No custom kernels.
Also, the method to fix adb remount is reset every other boot by the kernel, init.rc rebuilds local.prop on reboot as a failsafe and can't be changed without a custom kernel...
Response to luke.arran
luke.arran said:
This root method should work on all Motorola Devices running honeycomb or gingerbread. Try it out and see if it does
Click to expand...
Click to collapse
Just to let you know this does not work on all Xoom models like you say. Here is my thread with my specs in it. I have tried it three times following the directions to a T and it never gets past;
"[*] Initiating Phase 1...
[*] This may take a few minutes, don't mind the buzzing."
I have now let it run for over an hour each time and it never goes any further and my Xoom is still not rooted. It did not even ever reboot on its own. Does anyone have any suggestions? If not I'll just use some threads 1 & 2, I got from a friend.
Thanks, InfiniteImmortal
llama-power said:
Unlocking wipes all your data, apps, etc
Click to expand...
Click to collapse
Not this method. It is supposed to unlock and root motorola devices in 10 minutes without deleting any files. When I read about this on android police I was very excited as I never rooted because I only needed Superuser for my Xoom (never was interested in ROMs) and could never justify scraping everything just for this.
I tested the files here on a windows 7 machine... if I run from command at step 2. I get su permission denied. If I run the batch file I get "failed backup" loop after the device has been detected
tried the portable one click .exe found in "Motofail: Universal Motorola Android Root Tool (Portable)" works perfect on my bionic
obviously fails to remount as it does not include local.prop from step 5. so it's not working on xoom
This is the most awesome root utility I ever came along. It took something like 6 mins to root my phone without losing any files, if I can get it to run on my Xoom this will be just a dream come true!
Update: This root method does not support the Original Xoom. Confirmed by Dan.
Noob for tablets. Got the nexus 10 for the family for christmas. Want to get it all setup before I turn it over to the wolves.
I love using TBpro on my Droid Bionic. I thought it would be good to have a solid backup program on the tablet, and since I have it on my smartphone I thought I would hang with what I've sorta know already.
Dont really understand what unlocked/locked means for a bootloader, and why the N10 needs that why many smartphone can be rooted without being unlocked.
I would love to hear some views on the purposes of apps like ClockWorkMod and TWRP and what they do and provide. Seems like they do perform backups and more. Why TBpro is likely just a backup app. What functions do these recovery apps have the make them "must have".
thanks for the time answering the tablet noob
TBPro requires Root access and to acquire root access you have to be able to modify the operating system. You can't do that until the bootloader is unlocked. Once unlocked, you then need to flash Custom Recovery (either CMW or TWRP) in order to to flash/install the the files required to install the root binaries. Other uses of recovery include making NAND/System Backups and installing custom roms. They are essential if you are into modding your device. I have an LG G2x that is rooted and has a custom rom (CM7.2) and a Custom Kernel (Faux123 v54), as well as Beats Audio for Gingerbread. I installed all of those via ClockworkMod. I followed ZedoMax's instructions to root my Nexus 10 and had only the initial bootloop issue after unlocking the bootloader. That was easy to fix but I couldn't get ClockWorkMod to stay installed so I flashed TWRP instead. Works great. Just follow this thread and watch the vids. Hope I helped some.
http://forum.xda-developers.com/showthread.php?t=1997227
bg1906 said:
TBPro requires Root access and to acquire root access you have to be able to modify the operating system. You can't do that until the bootloader is unlocked. Once unlocked, you then need to flash Custom Recovery (either CMW or TWRP) in order to to flash/install the the files required to install the root binaries. Other uses of recovery include making NAND/System Backups and installing custom roms. They are essential if you are into modding your device. I have an LG G2x that is rooted and has a custom rom (CM7.2) and a Custom Kernel (Faux123 v54), as well as Beats Audio for Gingerbread. I installed all of those via ClockworkMod. I followed ZedoMax's instructions to root my Nexus 10 and had only the initial bootloop issue after unlocking the bootloader. That was easy to fix but I couldn't get ClockWorkMod to stay installed so I flashed TWRP instead. Works great. Just follow this thread and watch the vids. Hope I helped some.
http://forum.xda-developers.com/showthread.php?t=1997227
Click to expand...
Click to collapse
Thanks!
After unlocking, and using CMW or TWRP. I can then "root" my device. ok. After rooting, I can use TBpro.
At this point, do I need to remain "unlocked" Does it matter? For the N10 will I receive OTA after being unlocked/rooted,
or do I need to be in another state?
jetguat said:
Thanks!
After unlocking, and using CMW or TWRP. I can then "root" my device. ok. After rooting, I can use TBpro.
At this point, do I need to remain "unlocked" Does it matter? For the N10 will I receive OTA after being unlocked/rooted,
or do I need to be in another state?
Click to expand...
Click to collapse
Yes to all. Another option for you if you are not comfortable typing in the various commands is to use the Wufresh method. Watch the video by qbking777 here: http://forum.xda-developers.com/showthread.php?t=2015467
bg1906 said:
Yes to all. Another option for you if you are not comfortable typing in the various commands is to use the Wufresh method. Watch the video by qbking777 here: http://forum.xda-developers.com/showthread.php?t=2015467
Click to expand...
Click to collapse
Thanks again. I did stumble across that site and was trying to compare that to the mskip Nexus root tool kit. That was had so many options and I didnt (yet) find the cliff note's version on what they all do and why you'd need to.
The GUI for Wufresh is simple. Do you use it? I read a little about the root and the root+custom recovery choices. Not entirely clear which is preferred, at least for me needs. And I've not got a warm fuzzy feeling about what state the N10 should be in, such that OTA updates still happen. Can they happen when unlocked+rooted+custom recovery but still stock ROM (without system mods)
The wugfresh version automates what the zedomax version does by hand. I did mine via the zedomax way.
Sent from my Nexus 10 using xda app-developers app
jetguat said:
Thanks again. I did stumble across that site and was trying to compare that to the mskip Nexus root tool kit. That was had so many options and I didnt (yet) find the cliff note's version on what they all do and why you'd need to.
The GUI for Wufresh is simple. Do you use it? I read a little about the root and the root+custom recovery choices. Not entirely clear which is preferred, at least for me needs. And I've not got a warm fuzzy feeling about what state the N10 should be in, such that OTA updates still happen. Can they happen when unlocked+rooted+custom recovery but still stock ROM (without system mods)
Click to expand...
Click to collapse
I would suggest using the Wugfresh method, definitely the simplest to use. And a great recovery is TWRP, it is very clear and easy to understand what it is that each menu contains.
Also with the OTA updates, it really depends on the size and type of update. If it is a fairly major one, like JB 4.1 to JB 4.2 then you will have to use the option in Wugfresh toolkit to 'unroot', then update. After the update you can simply reuse the toolkit to root again. Sometimes if the OTA is small it will simply install over the rooted device, but I wouldn't count on it. It definitely shouldn't discourage you from rooting though, its relatively simple to fix
Hello, I have had a few people ask about how I reverted back to stock and managed to root without having reboots so here is an outline including links.
First you will need to use ODIN to go back to the original stock firmware.
Stock Odin for P907A can found here: http://forum.xda-developers.com/galaxy-note-pro-12/general/sm-p907a-att-version-news-t2850564/page1
Stock ODIN for the P900 can be found here: http://forum.xda-developers.com/showthread.php?t=2724895
For those who don't know how to use ODIN, here is a nce guide for you: http://androidcentral.us/2014/02/how-to-flash-firmware-using-odin-samsung-devices/
Now the next thing you need to do is root using TowelRoot, but DO NOT install SuperSU yet! After rooting use the debloat script in this thread (You run it from your device using terminal, I used the terminal function in ROM Toolbox): http://forum.xda-developers.com/showthread.php?t=2797540
I only used the option to disable KNOX and the updater along with the option to disable the startup sound.
Once you have successfully done those things, you may now install SuperSU. It will no longer ask you about KNOX, because it is properly disabled and will not cause you any reboots. My Note Pro has been rock solid stable and lightning fast after doing this.
NOTE: You will not be able to update to new firmwares after this.
Thanks to:
najoor
torreon91
Please make sure you hit thanks in these guys' threads for their hard work!
EDIT: If Jellybean comes out for our tablet I would not update unless the trade off was worth it to you. Or obviously if an exploit for the jellybean update were found then you would want to. If you did want to update, you could re-enable the updater by using the enbloat script that was with the debloat script.
Thank you for your help. Now I will be able to use my tablet more frequently
dragunbayne said:
Hello, I have had a few people ask about how I reverted back to stock and managed to root without having reboots so here is an outline including links.
First you will need to use ODIN to go back to the original stock firmware.
Odin for P907A can found here: http://forum.xda-developers.com/galaxy-note-pro-12/general/sm-p907a-att-version-news-t2850564/page1
For those who don't know how to use ODIN, here is a nce guide for you: http://androidcentral.us/2014/02/how-to-flash-firmware-using-odin-samsung-devices/
Now the next thing you need to do is root using TowelRoot, but DO NOT install SuperSU yet! After rooting use the debloat script in this thread (You run it from your device using terminal, I used the terminal function in ROM Toolbox): http://forum.xda-developers.com/showthread.php?t=2797540
I only used the option to disable KNOX and the updater along with the option to disable the startup sound.
Once you have successfully done those things, you may now install SuperSU. It will no longer ask you about KNOX, because it is properly disabled and will not cause you any reboots. My Note Pro has been rock solid stable and lightning fast after doing this.
NOTE: You will not be able to update to new firmwares after this.
Thanks to:
najoor
torreon91
Please make sure you hit thanks in these guys' threads for their hard work!
Click to expand...
Click to collapse
EDIT: If Jellybean comes out for our tablet I would not update unless the trade off was worth it to you. Or obviously if an exploit for the jellybean update were found then you would want to. If you did want to update, you could re-enable the updater by using the enbloat script that was with the debloat script.
dragunbayne said:
Hello, I have had a few people ask about how I reverted back to stock and managed to root without having reboots so here is an outline including links.
First you will need to use ODIN to go back to the original stock firmware.
Odin for P907A can found here: http://forum.xda-developers.com/galaxy-note-pro-12/general/sm-p907a-att-version-news-t2850564/page1
For those who don't know how to use ODIN, here is a nce guide for you: http://androidcentral.us/2014/02/how-to-flash-firmware-using-odin-samsung-devices/
Now the next thing you need to do is root using TowelRoot, but DO NOT install SuperSU yet! After rooting use the debloat script in this thread (You run it from your device using terminal, I used the terminal function in ROM Toolbox): http://forum.xda-developers.com/showthread.php?t=2797540
I only used the option to disable KNOX and the updater along with the option to disable the startup sound.
Once you have successfully done those things, you may now install SuperSU. It will no longer ask you about KNOX, because it is properly disabled and will not cause you any reboots. My Note Pro has been rock solid stable and lightning fast after doing this.
NOTE: You will not be able to update to new firmwares after this.
Thanks to:
najoor
torreon91
Please make sure you hit thanks in these guys' threads for their hard work!
EDIT: If Jellybean comes out for our tablet I would not update unless the trade off was worth it to you. Or obviously if an exploit for the jellybean update were found then you would want to. If you did want to update, you could re-enable the updater by using the enbloat script that was with the debloat script.
Click to expand...
Click to collapse
Is there a way to do this, but for the SMP-900 version the first link with the odin files state that they are only for the SM-P907 version? I have reverted back to stock but my tablet reboots qute often and with school starting it would be great to avoid that while taking notes. Thanks!
acaldrn2 said:
Is there a way to do this, but for the SMP-900 version the first link with the odin files state that they are only for the SM-P907 version? I have reverted back to stock but my tablet reboots qute often and with school starting it would be great to avoid that while taking notes. Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2724895
I will add it to the main post also.
Good day, all.
My son has recently got a Verizon s5 and took the lollipop update. He now decided he wants root and all the fun that comes with it - and doesn't need to be lollipop; kitkat was fine.
Here's the problem. I am a Moto guy. I've always been moto and recently have turbo. I have NO clue what the build numbers mean, exactly how to start to get to where he wants to be. I've read these threads a dozen times and I think I'm ready to try. Any guidance would be greatly appreciated.
1. I believe I need Odin. And the drivers. No problem.
2. I believe I need to get back to kitkat, then root. with towel root.
3. He wants native tether capability to go along with his UDP, adaware, etc. Not sure I've found the kitkat app to do that.
4. I believe I can stop the lollipop update by freezing apps with TIbu, and I found the thread which says which apps to freeze.
5. He is not interested in custom ROMS yet so I don't think I'll be using safestrap ( I used that during my Droid Razr Maxx days so I am familiar with that).
So, if you can direct me to THE exact thread, that would be helpful. And the build / version of what I need to install. This is all like a foreign language at this point as the naming appears to me to be very different than my moto experience.
Thank you!
newskate9 said:
Good day, all.
My son has recently got a Verizon s5 and took the lollipop update. He now decided he wants root and all the fun that comes with it - and doesn't need to be lollipop; kitkat was fine.
Here's the problem. I am a Moto guy. I've always been moto and recently have turbo. I have NO clue what the build numbers mean, exactly how to start to get to where he wants to be. I've read these threads a dozen times and I think I'm ready to try. Any guidance would be greatly appreciated.
1. I believe I need Odin. And the drivers. No problem.
2. I believe I need to get back to kitkat, then root. with towel root.
3. He wants native tether capability to go along with his UDP, adaware, etc. Not sure I've found the kitkat app to do that.
4. I believe I can stop the lollipop update by freezing apps with TIbu, and I found the thread which says which apps to freeze.
5. He is not interested in custom ROMS yet so I don't think I'll be using safestrap ( I used that during my Droid Razr Maxx days so I am familiar with that).
So, if you can direct me to THE exact thread, that would be helpful. And the build / version of what I need to install. This is all like a foreign language at this point as the naming appears to me to be very different than my moto experience.
Thank you!
Click to expand...
Click to collapse
There is only one firmware that can be rooted. That is NGC. Odin the full stock tar file that is in the notes #4 of this post. Root with towelroot, download SuperSU from play store, update the binaries, reboot phone. You will be rooted on 4.4.2
There are several firmwares that are 4.4.4. NI2 or NK2 would probably be best but that is up to you. Get rooted first. Then decide where you want to be.
newskate9 said:
Good day, all.
My son has recently got a Verizon s5 and took the lollipop update. He now decided he wants root and all the fun that comes with it - and doesn't need to be lollipop; kitkat was fine.
Here's the problem. I am a Moto guy. I've always been moto and recently have turbo. I have NO clue what the build numbers mean, exactly how to start to get to where he wants to be. I've read these threads a dozen times and I think I'm ready to try. Any guidance would be greatly appreciated.
1. I believe I need Odin. And the drivers. No problem.
2. I believe I need to get back to kitkat, then root. with towel root.
3. He wants native tether capability to go along with his UDP, adaware, etc. Not sure I've found the kitkat app to do that.
4. I believe I can stop the lollipop update by freezing apps with TIbu, and I found the thread which says which apps to freeze.
5. He is not interested in custom ROMS yet so I don't think I'll be using safestrap ( I used that during my Droid Razr Maxx days so I am familiar with that).
So, if you can direct me to THE exact thread, that would be helpful. And the build / version of what I need to install. This is all like a foreign language at this point as the naming appears to me to be very different than my moto experience.
Thank you!
Click to expand...
Click to collapse
I will help you out with a full guide. I have nothing better to do right now. This will wipe the device.
Step 1: Download Odin, the Samsung USB Drivers, and the NCG Firmware. I have packaged them into a ZIP file for you here:
https://dl.dropboxusercontent.com/u/82986368/Revert_And_Root_4-4-2-G900V.zip
Step 2: Extact the ZIP file.
Step 3: Install the Samsung USB Driver. Do not plug in the phone while the drivers are installing.
Step 4: Turn off the device. Now, hold down Home + Power + Volume Down. Once the Download mode screen comes up, press the Volume Up key.
Step 5: Open the Odin EXE file, in the Odin-3.09 folder.
Step 6: Click the "AP" button, and select the NCG Firmware (the .tar.md5 file with the very long name).
Step 7: Click "Start." This will flash the full stock KitKat firmware.
Step 8: Once rebooted, skip through the setup process.
Step 9: On the device, go to towelroot.com and click the weird symbol. This will download Towelroot. Install the APK now.
Step 10: Open TR, and click Make it Rain. You are now rooted on KitKat.
Step 11: Install SuperSU from the play store, open it up, and install the binaries.
Freezing the app "SDM" in Titanium Backup will indeed disable the Lollipop update notification.
FoxFi is the tethering app you're looking for.
You can stop here, but if you want to get a custom recovery, follow these steps: (UPDATE: You said you don't need one. I'm just pointing you there in case).
Install "Busybox Free" from the Play Store.
Open it and click "Install."
Download this APK and install it: http://forum.xda-developers.com/devdb/project/dl/?id=7144&task=get
Open it, click "Agree," and then click Install Recovery.
You now have a custom recovery! Rebooting will ask you to boot into recovery or into normal mode.
That's it! Let me know of any problems. I will be active here today
Nandr0idC0nsumer said:
I will help you out with a full guide. I have nothing better to do right now. This will wipe the device.
Step 1: Download Odin, the Samsung USB Drivers, and the NCG Firmware. I have packaged them into a ZIP file for you here:
https://dl.dropboxusercontent.com/u/82986368/Revert_And_Root_4-4-2-G900V.zip
Step 2: Extact the ZIP file.
Step 3: Install the Samsung USB Driver. Do not plug in the phone while the drivers are installing.
Step 4: Turn off the device. Now, hold down Home + Power + Volume Down. Once the Download mode screen comes up, press the Volume Up key.
Step 5: Open the Odin EXE file, in the Odin-3.09 folder.
Step 6: Click the "AP" button, and select the NCG Firmware (the .tar.md5 file with the very long name).
Step 7: Click "Start." This will flash the full stock KitKat firmware.
Step 8: Once rebooted, skip through the setup process.
Step 9: On the device, go to towelroot.com and click the weird symbol. This will download Towelroot. Install the APK now.
Step 10: Open TR, and click Make it Rain. You are now rooted on KitKat.
Freezing the app "SDM" in Titanium Backup will indeed disable the Lollipop update notification.
FoxFi is the tethering app you're looking for.
You can stop here, but if you want to get a custom recovery, follow these steps: (UPDATE: You said you don't need one. I'm just pointing you there in case).
Install "Busybox Free" from the Play Store.
Open it and click "Install."
Download this APK and install it: http://forum.xda-developers.com/devdb/project/dl/?id=7144&task=get
Open it, click "Agree," and then click Install Recovery.
You now have a custom recovery! Rebooting will ask you to boot into recovery or into normal mode.
That's it! Let me know of any problems. I will be active here today
Click to expand...
Click to collapse
y
You forgot one step. After making it rain, you download SuperSU from the play store, update the binaries, and reboot.
Tulsadiver said:
y
You forgot one step. After making it rain, you download SuperSU from the play store, update the binaries, and reboot.
Click to expand...
Click to collapse
Woops! Just added it back in.
Gentlemen - success!
Wow. I was telling my son this would be "hard" and he laughed at how easy it was. Thank you, guys. Sitting at 4.4.2 for now, and we'll let him play with this a bit then go from there.
Sincerely, thank you for your help and guidance.
A contributor is reporting success rooting 5.3.2.1 with Kingroot. No immediate confirmation...simply reposting for visability and comment. Report your results here for community benefit.
https://forum.xda-developers.com/am...-5th-gen-supertool-root-t3272695/post70784402
Reminder: Do not attempt to rollback FireOS 5.3.2.1; you will likely be rewarded with a brick.
No success for me. I have assumed "Gave both king root and purify full access via setting" as enabling these apps in accessibility under services?
I have tried KR 4.9.2, 4.9.6, 4.9.7, 5.0.0 and 5.0.3 numerous times. Also done a factory reset and followed the steps stated to no avail.
Maybe I am just unlucky.
stonedpsycho said:
No success for me. I have assumed "Gave both king root and purify full access via setting" as enabling these apps in accessibility under services?
I have tried KR 4.9.2, 4.9.6, 4.9.7, 5.0.0 and 5.0.3 numerous times. Also done a factory reset and followed the steps stated to no avail.
Maybe I am just unlucky.
Click to expand...
Click to collapse
Not having any luck with it either.
This is just a quick overview for testing purposes. As always, there is an extreme chance of the undesired "Bricked Device". You are warned...
1. Make sure adb and fastboot drivers are enabled and working to the 5th gen Fire. Extremely important.
2. Once connection is working follow the "Super Tool" setup directions.
3. Disable ota, disable ads and install GPlay. Somethings can only be done after root.
4. Once you have Gplay setup, use Super Tool to install KingRoot.
5. When you first run KingRoot, it will advertise "Purify Battery Saver" install it.
6. Afterwards run KingRoot. It will reboot 3-5 times before applying root. This process of rooting consumed over an hour and may need to be restarted if KingRoot fails.
7. Please keep in mind it is just an overview in order to determine the steps correctly.
If necessary I will start from square one and document all my steps. After rooting, I downgraded to 5.3.1 and verified 2 roms worked (Fire Nexus and CM Fire.)
My apologies for not providing more accurate details, its just an overview.
TechDad378 said:
This is just a quick overview for testing purposes. As always, there is an extreme chance of the undesired "Bricked Device". You are warned...
1. Make sure adb and fastboot drivers are enabled and working to the 5th gen Fire. Extremely important.
2. Once connection is working follow the "Super Tool" setup directions.
3. Disable ota, disable ads and install GPlay. Somethings can only be done after root.
4. Once you have Gplay setup, use Super Tool to install KingRoot.
5. When you first run KingRoot, it will advertise "Purify Battery Saver" install it.
6. Afterwards run KingRoot. It will reboot 3-5 times before applying root. This process of rooting consumed over an hour and may need to be restarted if KingRoot fails.
7. Please keep in mind it is just an overview in order to determine the steps correctly.
If necessary I will start from square one and document all my steps. After rooting, I downgraded to 5.3.1 and verified 2 roms worked (Fire Nexus and CM Fire.)
My apologies for not providing more accurate details, its just an overview.
Click to expand...
Click to collapse
Are you sure it was 5.3.2.1 you where on ? I only ask because downgrading to 5.3.1 from 5.3.2.1 should result in a brick as the boot loader used in 5.3.1 and 5.3.2 changed from on 5.3.2.1 and the anti-roll back measure amazon have should have kicked in to give you a brick.
How did you roll back ? Through ADB or placing the update file in the internal SD ?
Correct it was 5.3.2.1. While playing around with it I hit a black screen while booting. Upon reading some posts, I thought there was no return because of the version. Since the device responded via usb on pc, adb sideload worked causing downgrade to work.
Don't get me wrong this may have been just pure random luck. But hopefully my results my lead to "Fire Lineage OS".
No luck with this method. Will keep trying.
Zero Luck yet as well. Will try again. Hopefully something more reliable will come about soon.
Sorry to hear you have had no success. Will revert everything back and document each step. Once the method has been identified as successful, the information will be provided.
You still need to provide us with one of the most important tips, what version of kingroot you are using.
Thank you
TechDad378 said:
... But hopefully my results my lead to "Fire Lineage OS".
Click to expand...
Click to collapse
Quick side note: No LineageOS for this pup while the bootloader remains locked. LineageOS begins with Android 6 (Marshmallow); the current suite of Android 5 (Lollipop) ROMs is all we'll see due to FireOS 5 kernel restrictions. Unless Amazon releases and back ports FireOS 6 to older devices. Highly unlikely IMHO ... economics don't square.
If someone succeeds, could they try to post the kmPlugins.zip from their downloads folder? If we can get that from a successful root, then we could probably skip all the repeated failures and just get KingRoot to use that method immediately.
What ever happened to the guy that had rooted it? I knew he was bs.
Geek Surfer said:
What ever happened to the guy that had rooted it? I knew he was bs.
Click to expand...
Click to collapse
Hmm...
Interesting response.
With a full time job and a family, this is a hobby I do for fun in my spare time. Most mods are done with patience and diligence.
Recommending following command,
C:/yourself/ adb sideload patience.zip
---------- Post added at 03:20 AM ---------- Previous post was at 03:09 AM ----------
Davey126 said:
Quick side note: No LineageOS for this pup while the bootloader remains locked. LineageOS begins with Android 6 (Marshmallow); the current suite of Android 5 (Lollipop) ROMs is all we'll see due to FireOS 5 kernel restrictions. Unless Amazon releases and back ports FireOS 6 to older devices. Highly unlikely IMHO ... economics don't square.
Click to expand...
Click to collapse
Point taken. Just hoping LineageOS will be as widespread.
As for the root, I reverted back to original. Trying to recreate the environment which allowed success.
Geek Surfer said:
What ever happened to the guy that had rooted it? I knew he was bs.
Click to expand...
Click to collapse
Nice. If you bothered to read his post history you might think differently. Well presented/documented with all the appropriate caveats.
Geek Surfer said:
What ever happened to the guy that had rooted it? I knew he was bs.
Click to expand...
Click to collapse
What a shame that people can't be considerate online anymore.
@TechDad378 Could you verify what supertool version you are using . I'm trying to figure what version of gapps got installed, and can you recall if you installed any apps from playstore like chrome ?
I don't have a tablet with 5.3.2.1 but it occoured to me that kingroot may have found a backdoor to root in playstore or another installed app. I've tested on a tablet with previously unrootable 5.1.4 and the difference in root behaviour pre/post play store installion is very noticable. The tablet reboots several time during root with playstore installed , it only rebooted once without it installed.
Ive not managed to root it yet but kingroot now stuck on verifing root status, it previouly detected it as unrooted, something has changed
My router is blocking OTA so going keep playing with this
5.1.4 Rooted !!!!!
Mr McBoatface said:
@TechDad378 Could you verify what supertool version you are using . I'm trying to figure what version of gapps got installed, and can you recall if you installed any apps from playstore like chrome ?
I don't have a tablet with 5.3.2.1 but it occoured to me that kingroot may have found a backdoor to root in playstore or another installed app. I've tested on a tablet with previously unrootable 5.1.4 and the difference in root behaviour pre/post play store installion is very noticable. The tablet reboots several time during root with playstore installed , it only rebooted once without it installed.
Ive not managed to root it yet but kingroot now stuck on verifing root status, it previouly detected it as unrooted, something has changed
My router is blocking OTA so going keep playing with this
Click to expand...
Click to collapse
Well it may not be the news most visiting this thread are looking for but I've rooted the previously unrootable 5.1.4 !!!!
I played around with various play store installations as suggested in my post above looking for a back door to root. 3 hours and got no where. Decided to downgrade to 5.1.2 and use supertools to root it the tablet. For the life of my I couldn't root this rootable OS..... six attempts failed each with multipul reboots. Then I read up a bit more and use kingroot 4.8.2 as suggested in this thread - https://forum.xda-developers.com/amazon-fire/general/flashing-kindle-5-1-2-using-kingroot-t3346300. This time 5.1.2 Rooted first time one reboot using Kingroot. I had always thought the Kingroot edition used didn't really matter that the files it used came from the online database. This result put that assumption into doubt.
Decided to go back to 5.1.4 and retry using the kingroot as above....... Didn't work. Not being someone who gives up easy i tried the impressively long-named "NewKingrootV5.0.1_C165_B377_xda_release_protected_2016_12_22_20161222120332_105243_signed.apk" from here https://forum.xda-developers.com/devdb/project/?id=9793#downloads
Rooted first time !!! It did reboot a few times, I had to manually restart the root process each time it rebooted but it picked off at the % point where it rebooted.
Moral of the story never give up and try some kingroot versions from the xda links above
Going to reset the device and confirm it's repeatable.
Mr McBoatface said:
Well it may not be the news most visiting this thread are looking for but I've rooted the previously unrootable 5.1.4 !!!!
I played around with various play store installations as suggested in my post above looking for a back door to root. 3 hours and got no where. Decided to downgrade to 5.1.2 and use supertools to root it the tablet. For the life of my I couldn't root this rootable OS..... six attempts failed each with multipul reboots. Then I read up a bit more and use kingroot 4.8.2 as suggested in this thread - https://forum.xda-developers.com/amazon-fire/general/flashing-kindle-5-1-2-using-kingroot-t3346300. This time 5.1.2 Rooted first time one reboot using Kingroot. I had always thought the Kingroot edition used didn't really matter that the files it used came from the online database. This result put that assumption into doubt.
Decided to go back to 5.1.4 and retry using the kingroot as above....... Didn't work. Not being someone who gives up easy i tried the impressively long-named "NewKingrootV5.0.1_C165_B377_xda_release_protected_2016_12_22_20161222120332_105243_signed.apk" from here https://forum.xda-developers.com/devdb/project/?id=9793#downloads
Rooted first time !!! It did reboot a few times, I had to manually restart the root process each time it rebooted but it picked off at the % point where it rebooted.
Moral of the story never give up and try some kingroot versions from the xda links above
Going to reset the device and confirm it's repeatable.
Click to expand...
Click to collapse
Nice! While you can downgrade 5.1.4, this mean it may be possible to root without using a PC to downgrade first. I'm going to try on 5.3.2.1, and see how it works.
Sent from my Amazon Fire using XDA Labs
Repeated root on 5.1.4, replace the kingroot in supertools with the "NewKingrootV5.0.1_C165_B377_xda_release_protected _2016_12_22_20161222120332_105243_signed.apk" version and ran the script.
It needed 2 attempts this time but it rooted. The supertools script removed it and replaced with supersu.
See attached video in zip to confirm