Database Users

New to rooting - What is easiest?

Hi everyone,
I'm new to "rooting" android devices, although I have jailbroken all my iPhones and "rooted" my palm pre.
As a newbie, it seems the "root toolkit" is the best way to do this? Is this Windows only, or is there a Mac version?
anything else I should read up on / know before rooting? I basically want to root, initially at least, to get sixaxis support and stickmount working.
Thank you all for your help in advance.

First of all, this is the wrong section. You should post inquiries in the q/a section.
In terms of rooting, I personally find the easiest way is to unlock the bootloader, flash a custom recovery such as cwm/twrp, and then install the supersu zip via recovery. You should be able to unlock the bootloader and install recovery via fastboot. After that the rest is just copying a file to the device, booting into recovery and installing a zip file.
Sent from my Nexus 7

Take a peek at the nexus root toolkit thread in this forum...quick and easy.
Sent from my Nexus 7 using xda app-developers app

The tool kit is windows only, correct?

Any reason to NOT use the tool kit and go with other more manual methods?
An iphone is virtually impossible to "brick" - Is the same true for the N7?

Foxman2k said:
Any reason to NOT use the tool kit and go with other more manual methods?
An iphone is virtually impossible to "brick" - Is the same true for the N7?
Click to expand...
Click to collapse
I would agree with:
evonc said:
In terms of rooting, I personally find the easiest way is to unlock the bootloader, flash a custom recovery such as cwm/twrp, and then install the supersu zip via recovery. You should be able to unlock the bootloader and install recovery via fastboot. After that the rest is just copying a file to the device, booting into recovery and installing a zip file.
Click to expand...
Click to collapse
Then you know what is happening, and how it works... so if you run into troubles later, you know what to do.
Hard to brick this device.

Foxman2k said:
Any reason to NOT use the tool kit and go with other more manual methods?
Click to expand...
Click to collapse
For practice, and maybe the one-click solution is not flexible enough for your means. It's usually dependent on the developer to update it, so do check if it has any limitations.
Also, the ones I've seen are Windows only.
Foxman2k said:
An iphone is virtually impossible to "brick" - Is the same true for the N7?
Click to expand...
Click to collapse
As long as you don't mess up the bootloader, it should be possible to reflash stuff via recovery or fastboot. Bear in mind there have been exceptions (though that came about because of a serious kernel bug, rather than due to user error) so this can't be a guarantee.

I was new to rooting too, using the nexus toolkit helped me learn a lot about rooting and all the android stuff I wasn't used too!
I really recommend it

spdecoste said:
I was new to rooting too, using the nexus toolkit helped me learn a lot about rooting and all the android stuff I wasn't used too!
I really recommend it
Click to expand...
Click to collapse
Another recommendation for WUGS rootkit - literally very easy foolproof step by step menus/instructions - only prob I had were the drivers - just manually pointing to driver directory sorted this out.

I made a guide that could help you. http://exzacklyright.blogspot.com/2012/07/nexus-7-guide-for-adbunlocking-rooting.html There's really only 3 commands. I don't recommend toolkits.

exzacklyright said:
I made a guide that could help you. http://exzacklyright.blogspot.com/2012/07/nexus-7-guide-for-adbunlocking-rooting.html There's really only 3 commands. I don't recommend toolkits.
Click to expand...
Click to collapse
Great, will check that out!
Can someone explain to me, in layman's terms, what "unlocking the bootloader" does?
I'm familiar with what "root" technically means as I've been using Linux since back when it had to be loaded on floppys and manualy configuring X LOL. So basically "root" means you have access to super user privileges.
Why is the bootloader locked in the first place? Once it's unlocked can it be locked again?

exzacklyright said:
I made a guide that could help you. http://exzacklyright.blogspot.com/2012/07/nexus-7-guide-for-adbunlocking-rooting.html There's really only 3 commands. I don't recommend toolkits.
Click to expand...
Click to collapse
This seems to rely on Windows. Any Mac tools available?

Foxman2k said:
Great, will check that out!
Can someone explain to me, in layman's terms, what "unlocking the bootloader" does?
I'm familiar with what "root" technically means as I've been using Linux since back when it had to be loaded on floppys and manualy configuring X LOL. So basically "root" means you have access to super user privileges.
Why is the bootloader locked in the first place? Once it's unlocked can it be locked again?
Click to expand...
Click to collapse
Unlocking the bootloader allows you to mess with the bootloaders progression at startup, which gives you the ability to install a custom recovery and gives us the method to gain root access. The bootloader can be unlocked by many different methods - some manual and some "one-click". I'd suggest doing it the manual way first, so you understand the process, and are able to fix it manually if anything goes wrong.
To my understanding, it's locked so that people who don't know what they're doing can't mess the device up. It's a safety procedure basically.
To relock the bootloader, you just type (I only know how to do this in windows - Linux and Mac work as well al beit differently)
Code:
fastboot oem lock
and you're all set.

Foxman2k said:
This seems to rely on Windows. Any Mac tools available?
Click to expand...
Click to collapse
The Android SDK and ADB tools are equally available on Linux and Mac. You won't have to do the "Adding to Path" thing. All of the ADB commands will be the same, though.

I didn't know anything about rooting at all too, despite having an android phone for more than 2 years.
I went with the one-click root process.
Download this file, plug your Nexus 7, follow the instructions- which means typing Y, N, Y etc
Done in 5 minutes. There's a youtube video on it too. Go check it out.
I still dont know much about the process.. except I'm unlocked and rooted =)

I have a few naive questions
Do I have to do the OEM unlock to root the device? I would prefer not to wipe it.
Assuming I don't hard brick the device, can I go back to stock for warranty work?
Does rooting the device mean I can't get OTA updates from Google? For now I just want to run the stock kernel/rom and get updates. I just want root to run titanium and certain other apps that require root.
I've seen a thread that suggest that the play store (market) doesn't work on rooted devices. Is that true?

Easy 2 click root: How I got to 4.2.2 Camera Update/Rooted and WP permanently Off

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:

[How To] Downgrade to 4.5.3 so you can root device

Step by step instructional video
Help setting up adb for windows: https://www.youtube.com/watch?v=CyJlmTtLsIg
If you are already running Fire OS 4.5.3 and below, all you need to do is follow this video to root: https://youtu.be/KcQ30qcImJc
Steps:
1. Install the Fire OS 5.0 developer preview. EDIT: Do not do this. If you already have a lollypop ROM installed, use that instead of installing dev preview (You could cause a brick)
2. Enable ADB on your device and set up ADB on your computer
3. Download 4.5.3 firmware: https://kindle-fire-updates.s3.amazonaws.com/update-kindle-20.4.5.3_user_453011120.bin (Mirror coming soon. This download works for the Fire HD7 and HD6)
4. connect device to computer and run "adb reboot recovery"
5. use volume keys and power button to navigate to "Apply update from ADB"
6. from computer type "adb sideload update-kindle-20.4.5.3_user_453011120.bin"
7. from tablet select "wipe data/factory reset"
8. from tablet select "reboot system"
9. Complete setup (do not connect to a wifi network yet)
10. Download KingRoot: http://www.kingroot.net/
11. Download JmzFireHDTool: http://forum.xda-developers.com/fir...ool-jmz-fire-hd-7-tool-gapps-disable-t3113655
12. install both apps. "adb install KingRoot-4.1.0.249-release-nolog-201505211812_105001.apk" and "adb install JmzFireHDTool_v4.apk"
13. Temporarily disable otaverify via adb "adb shell pm block com.amazon.otaverifier" (spelled wrong in video)
14. Connect to wifi so that KingRoot can work
15. Open KingRoot on your device
16. press "try to root"
17. re-enable otaverifier "adb shell pm unblock com.amazon.otaverifier" (spelled wrong in video)
18. Open JMZ Fire Tools and press "Disable OTA's"
Note: If you ever need to upgrade back to lollypop, you should follow these steps so you do not brick device: http://forum.xda-developers.com/fire-hd/general/tools-fire-hd-67-rooting-gapps-t3371242/page4

Awesome find !!! Here is a direct link to the 5.2.0 update file:
http://forum.xda-developers.com/fire-hd/general/lolipop-ota-capture-t3141810
After the downgrade, install TWRP, and upgrade to 4.5.4 but this time with root and fully working GAPPS:
http://forum.xda-developers.com/fire-hd/general/root-v2-0-fireos-4-5-4-gapps-t3150613
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-4-5-4-twrp-root-t3141648
This way one goes directly to SuperSu, and a clean device with no traces of KingRoot.

bibikalka said:
Awesome find !!! Now, can you install TWRP, and try to upgrade to 4.5.4 while keeping root as per this post:
http://forum.xda-developers.com/showpost.php?p=61329063&postcount=4
This way one goes directly to SuperSu, and a clean device with no traces of KingRoot.
Click to expand...
Click to collapse
ah yes good idea. I'm hoping someone with ROM development knowledge will start a build. We've got just about everything setup so that a custom ROM can run
Sent from my LG-V480 using Tapatalk

powerpoint45 said:
ah yes good idea. I'm hoping someone with ROM development knowledge will start a build. We've got just about everything setup so that a custom ROM can run
Click to expand...
Click to collapse
The tricky part is that the unlocked bootloader still needs a signed kernel. Which is pretty constraining. It'd be interesting to replace the boot preloader, but the risks are high.
Upon boot (if connected to PC), the system flashes MT65xx pre-loader. Which seems to indicate that one could start looking into programs such as "Smart Phone Flash Tool" and "MTK Droid Tools" for MTK chipsets.
Another hope is that the 5.0 version would be sufficiently buggy, such that the bootloader can be made to boot unsigned kernels.

bibikalka said:
The tricky part is that the unlocked bootloader still needs a signed kernel. Which is pretty constraining. It'd be interesting to replace the boot preloader, but the risks are high.
Upon boot (if connected to PC), the system flashes MT65xx pre-loader. Which seems to indicate that one could start looking into programs such as "Smart Phone Flash Tool" and "MTK Droid Tools" for MTK chipsets.
Another hope is that the 5.0 version would be sufficiently buggy, such that the bootloader can be made to boot unsigned kernels.
Click to expand...
Click to collapse
Hashcode has gotten around this issue multiple times with something called a bootstrap but I'm not too sure how it works
Sent from my LG-V480 using Tapatalk

Btw, any chance you could post the direct link to 5.0 preview (for non-developers), since it's probably behind some registration page or something ...

i just signed in with my amazon account, you will need to unroot your fire and reset it as 5.0 is a OTA.

bibikalka said:
Btw, any chance you could post the direct link to 5.0 preview (for non-developers), since it's probably behind some registration page or something ...
Click to expand...
Click to collapse
I wish I could find that bin file link... I looked for it but could not find a link to the actual bin file.. If ota's download to the sdcard then It could still be accessed but I don't know where it downloads to. If it downloads to the data dir of the app it would be inaccesable since you need to be on the latest update in order to download the 5.0 version and on the latest version we have no root which means no access to data dir
Sent from my LG-V480 using Tapatalk

this is a great find. but stupid me only have a macbook pro and i cant set up adb. sucks..

edgar.vrgs said:
this is a great find. but stupid me only have a macbook pro and i cant set up adb. sucks..
Click to expand...
Click to collapse
you can set it up on a mac. Just do a little searching. I know it's plausible
Sent from my LG-V480 using Tapatalk

powerpoint45 said:
you can set it up on a mac. Just do a little searching. I know it's plausible
Sent from my LG-V480 using Tapatalk
Click to expand...
Click to collapse
i have tried but i cant figure it out

It worked perfectly. Thanks

Despite really wanting root and the possibility of using my already paid for apps from the Play store, I really like the lollipop version of fire os. I do think it's a bit ridiculous they haven't retained the old kindle skin because it's exactly how every real android tablet looks but at this point they should be forced by law to let people use the Play store as they wish. Sort of like how Verizon was once forced to allow tethering without a subscription.

devicer said:
It worked perfectly. Thanks
Click to expand...
Click to collapse
great to hear it!
Sent from my LG-V480 using Tapatalk

bpeery84 said:
Despite really wanting root and the possibility of using my already paid for apps from the Play store, I really like the lollipop version of fire os. I do think it's a bit ridiculous they haven't retained the old kindle skin because it's exactly how every real android tablet looks but at this point they should be forced by law to let people use the Play store as they wish. Sort of like how Verizon was once forced to allow tethering without a subscription.
Click to expand...
Click to collapse
I hear ya
Sent from my LG-V480 using Tapatalk

so i finally got adb on my mac to work, but now when i am on the last command to install 4.5.3 terminal says it can't read update-kindle-20.4.5.3_user_453011120.bin
has anybody done this on a mac and would like to guide me on what i am doing wrong?

edgar.vrgs said:
so i finally got adb on my mac to work, but now when i am on the last command to install 4.5.3 terminal says it can't read update-kindle-20.4.5.3_user_453011120.bin
has anybody done this on a mac and would like to guide me on what i am doing wrong?
Click to expand...
Click to collapse
does adb devices list your device. Maybe try re-downloading the update in case of corruption
Sent from my LG-V480 using Tapatalk

Perfect timing! Lost root last week and hoped for a way to get back. You the man

I wonder if there is a way to stop the update once it's downloaded, in order to grab the 5.0 update bin from /cache.
This would help to re-pack the update in a way that does not re-write key partitions, then one can have TWRP and root on 5.0
It does sound like 5.0 is a nice update, since it provides stock Android. That's what custom ROMs are usually for, but Amazon will give it away !

bibikalka said:
I wonder if there is a way to stop the update once it's downloaded, in order to grab the 5.0 update bin from /cache.
Click to expand...
Click to collapse
I was wondering the same. Seems like you could rename the otaverifier apk back to (plain) .apk and get the download but by keeping com...otaverifier blocked it wouldn't install. I'm just not sure these developer updates are handled like any other.

Root Xperia Z2 Tablet (All Models/Regions) on 5.1.1 build 23.4.B.0.319 in 3 Steps

Hello everyone,
I've noticed that there hasn't been any threads about rooting the Xperia Z2 Tablet on lollipop. Most threads have discussed how to root the device on 4.4.4 and to create an update image to maintain your root whilst updating to 5.0+.
I've scoured the interwebs and found nothing so I'll make it easy for those whom don't know how to achieve root or don't want to do much work without creating images and such.
First off I'm not responsible for any inconvenience that may come with rooting your device and losing your warranty. I can and will be willing to help out in restoring or answering questions that you may have.
This method uses Kingroot... For those who have a problem with kingroot, it is only used to achieve root and this guide will also be showing you how to remove kingroot and install Supersu with ease. Using the link below download the necessary files: Kingroot V4, Supersume, XZDualRecovery 2.8.26. Place all these files on the root of your devices internal storage/SD card excluding Xdualrecovery as that needs a PC. (If you want to Xposed working I will also supply the files needed for that as well). https://www.mediafire.com/download/wrsajbgw2jr6czt
*Make sure you have unknown sources enabled under Settings>Security>Device administrators as well as Developer Options available and USB debugging enabled. (To enable Developer Options go to Settings>About Tablet>Build Number and click it 10 times).
1. Install NewKingroot.apk and run the application. It will notify you that a root method was found and to try it. It may take up to 2 minutes to achieve root. (If all you wanted was root and are content with kinguser then you're done! :good: if you want Supersu and/or a custom recovery then continue on to step 2!
2. Connect your Tablet to your PC via microUSB. On your PC open and extract the contents of TabZ-lockeddualrecovery2.8.26-RELEASE.combined.zip to your desktop. Now double click install.bat a screen will pop up providing you with options to install xdualrecovery. Choose option 2. Installation on ROM rooted with SuperUser by pressing 2 and enter. The script will run its course and tell you to grant permission on your tablet. Open up your tablet and a kinguser prompt will show asking you to grant or deny permission to ADB (Grant it!!!) afterwards your tablet will reboot on it's own to TWRP. (I advise you to either make a backup of the tablet now or after you install Supersu as insurance in case of any mishaps). Click reboot System.
3.Install Supersume, open the application and run it. It will of course ask to grant it permission (Grant it!!!) it will check the environment (making sure that there isn't any Pokemon nearby that you don't need... Sorry Pokemon Go reference) and it will begin removing kingroot and install Supersu. If you didn't have Supersu installed already great! It'll open up Supersu automatically. Supersu may ask you to update binaries (DO NOT click TWRP as it will reboot and you have to start the process over from step one!!! :crying: Just click Normal and once it says successful you're done! :victory: The next step is optional if you Want Xposed.
*Optional 4. Install XposedInstaller_3.0_alpha4.apk. Open your app drawer and open NDR Utils. It will ask for permission (Grant it!!!) now here you may choose your preferred recovery... Philz Touch Recovery,TWRP or Clockwork Mod Recovery. Click Reboot to Primary Recovery (fourth option) once it's rebooted you want to click install>SD>xposed-v85.1-sdk22-arm-by-romracer-20160620.zip and swipe to install. You should get a success when it's finished. Now simply reboot and your apps will be upgrading. Congratulations you now have root with SuperSU and xposed! :victory:
**if you wish to uninstall Xposed simply reboot to recovery and click install>SD>xposed-uninstaller-20151218-arm.zip uninstall the application once it's rebooted and you're good to go!
***if you have a problem with Supersume not working, reinstall Newkingroot.apk and run it again to get root. Then run supersume again (Grant permission!!!) and let it run its magic.
If anyone has issues, has questions or needs help PM and I will do my best to help and answer all your questions. Please don't be discouraged because I'm new here! I will be soon adding a link to a video tutorial on how all these steps can be done!

I have the Verizon 561, will this allow rom upgrade to marshmallow?

chin_bone said:
I have the Verizon 561, will this allow rom upgrade to marshmallow?
Click to expand...
Click to collapse
Hi there, I also have SGP561 as well for Verizon. Verizon didn't release Marshmallowfor the device yet unfortunately. ???? still waiting and more then willing to confirm when it does

Just ran on my 5.1.1 z2 and work first time. Great stuff thanks!

creepingcreep said:
Just ran on my 5.1.1 z2 and work first time. Great stuff thanks!
Click to expand...
Click to collapse
Glad it worked for you. Just wanted to help people out as I had invested time trying to figure out my own. I didn't like flashing files constantly so tried making easy.

Never had luck with kingoapp and today isnt any different

Thanks so much. I am away for another week but I can not wait to try this. I got a verizon z2 tablet since it seemed to be the cheapest 10 inch tablet. You have breathed new life in to it.
Sent from my SM-G930V using XDA-Developers mobile app

Am i correct that you don't provide the kingroot.apk?
Which version are you using?

How do you boot into custom recovery from device off? Everytime I try it takes me to the stock recovery
Sent from my SGP561 using XDA-Developers mobile app

ToneLa said:
Never had luck with kingoapp and today isnt any different
Click to expand...
Click to collapse
Sorry to hear what version are you using? Use the provided KingRoot in the download link provided

Daimonion1980 said:
Am i correct that you don't provide the kingroot.apk?
Which version are you using?
Click to expand...
Click to collapse
No, in the link provided all necessary apps and folders/zips are included. Including KingRoot apk

Cammy253 said:
How do you boot into custom recovery from device off? Everytime I try it takes me to the stock recovery
Click to expand...
Click to collapse
Power off device. While device is booting up at the Sony logo hold power and volume down/up (depends on customer recovery) until led flashes green and device vibrates then let go

JediDru said:
Thanks so much. I am away for another week but I can not wait to try this. I got a verizon z2 tablet since it seemed to be the cheapest 10 inch tablet. You have breathed new life in to it.
Click to expand...
Click to collapse
That's great news to hear! I picked one up and wanted to root and I did on KitKat but when I upgraded to lollipop I lost root and rooted it the long way... Needed something simpler and couldn't find anything on here. So I wanted to make sure a guide was available to all. Enjoy and let me know how it went

reymund602 said:
Power off device. While device is booting up at the Sony logo hold power and volume down/up (depends on customer recovery) until led flashes green and device vibrates then let go
Click to expand...
Click to collapse
Thank you working great
Sent from my SGP561 using XDA-Developers mobile app

If you're talking about your google drive, there is no kingoapp.apk in there
All there is:
- supersume.apk
- tabz-lockeddualrecovery
- xposed uninstaller
- xposed v85.1
- xposed installer

I downloaded the most recent kingroot, which worked on my Verizon sgp561, and then I used your superuser file to change over to su. Seems to work just fine.. I'm on 5.1.1.

I tried the most recent kingroot and it fails.
An old version gave me an error code of 0x162982

ToneLa said:
If you're talking about your google drive, there is no kingoapp.apk in there
All there is:
- supersume.apk
- tabz-lockeddualrecovery
- xposed uninstaller
- xposed v85.1
- xposed installer
Click to expand...
Click to collapse
Let me double check and if anything I'll post a link to the apk
Sorry that you're having issues though

bilestoad said:
I downloaded the most recent kingroot, which worked on my Verizon sgp561, and then I used your superuser file to change over to su. Seems to work just fine.. I'm on 5.1.1.
Click to expand...
Click to collapse
Thanks for confirming! If you didn't see the KingRoot apk in drive I'll upload the current version!

ToneLa said:
I tried the most recent kingroot and it fails.
An old version gave me an error code of 0x162982
Click to expand...
Click to collapse
What is the software version you are having problems with?

5.3.1 ROOT! :)

Kingroot now roots 5.3.1!
If you are having trouble installng cm 12.1, try the supertool or @wtfjajaja's instructions.
wtfjajaja said:
try it a few times, i encountered the same problems as well
here's what i did
1. factory reset through recovery
2. root with kingroot, (it worked for me after 2 to 3 tries)
3. installed supersu-me 6.7
4. update su binary
it's important here! don't restart yet, my device bricked few times here
5. install flashfire 0.53
6. follow the steps to install cm12.1 under flashfire from here
7. enjoy
Click to expand...
Click to collapse
Supertool: http://forum.xda-developers.com/amazon-fire/development/amazon-fire-5th-gen-supertool-root-t3272695
Bricked?: http://forum.xda-developers.com/amazon-fire/general/unbrick-amazon-fire-7in-2015-5th-gen-t3285294

Fingers crossed! I can't wait to start flashing roms!

If you're root then maybe you can use flashfire to flash a rom just like 5.1.2

tonibm19 said:
If you're root then maybe you can use flashfire to flash a rom just like 5.1.2
Click to expand...
Click to collapse
Flashfire needs supersu
or Cmsu to work.

hooks024 said:
Flashfire needs supersu
or Cmsu to work.
Click to expand...
Click to collapse
Try rootjunky's supertool after rooting to see if it can install it.

.
tonibm19 said:
Try rootjunky's supertool after rooting to see if it can install it.
Click to expand...
Click to collapse
I just installed coverted kingroot into supersu using supersume. I then used flashfire to install CM12.1

DoctorDark_ said:
I just installed coverted kingroot into supersu using supersume. I then used flashfire to install CM12.1
Click to expand...
Click to collapse
So you installed cm12.1 coming from fireos 5.3.1?
That's awesome!
You should create a tutorial so others can do that to.

marvelous news!!!

DoctorDark_ said:
Kingroot now roots 5.3.1! Hopefully someone can quickly push out a toolkit.
Click to expand...
Click to collapse
Would you add the 5.3.1 version in the title ???

tonibm19 said:
So you installed cm12.1 coming from fireos 5.3.1?
That's awesome!
You should create a tutorial so others can do that to.
Click to expand...
Click to collapse
Same procedure as if coming from FireOS 5.1.2; a new tutorial is not required.

Nice I will try it out.

Good chance the latest versions of Kingroot (always evolving) will also work for those on FireOS 5.1.2.1-5.1.4. Worth a try before attempting a rollback to 5.1.2.

I couldn't get super sume to work.

not working here only upto around 17% restarted a dozen times still not work (Fire 7 2015 5.3.1)

ttcontributor said:
not working here only upto around 17% restarted a dozen times still not work (Fire 7 2015 5.3.1)
Click to expand...
Click to collapse
Not good - earlier builds of Kingroot froze around 29% before crapping out. Make sure you have the latest Kingroot app. Also try a factory reset (warning: you will loose personal apps/data) and do not register with Amazon during subsequent device initialization. This proved effective for some in the past. Recognize the community is still learning; expect some failures along the way.

Davey126 said:
Same procedure as if coming from FireOS 5.1.2; a new tutorial is not required.
Click to expand...
Click to collapse
Which same procedure?
I found a thread but I am not sure if it'll work for new KingRoot, should I pay for Super Sume?
Also what about anti-rollback. What happens when I flash with FlashFire and say I somehow bricked the device?
Can I still adb sideload 5.3.1 back?
We really need a new guide or toolkit because all of these makes me confused.
For those who cannot root.
Tablet shuts down, you go back in Kingroot click root it starts somewhere from 20%s and then reports failed,
You click root again then it roots.

-Yami- said:
Which same procedure?
I found a thread but I am not sure if it'll work for new KingRoot, should I pay for Super Sume?
Also what about anti-rollback. What happens when I flash with FlashFire and say I somehow bricked the device?
Can I still adb sideload 5.3.1 back?
We really need a new guide or toolkit because all of these makes me confused.
For those who cannot root.
Tablet shuts down, you go back in Kingroot click root it starts somewhere from 20%s and then reports failed,
You click root again then it roots.
Click to expand...
Click to collapse
Take a deep breath and start researching what has already been posted (forum index). We don't need a "need a new guide or toolkit" because you are new to the game and haven't done your homework. Everything that was written for 5.1.2 should be applicable to 5.3.1 until proven otherwise.

Davey126 said:
Take a deep breath and start researching what has already been posted (forum index). We don't need a "need a new guide or toolkit" because you are new to the game and haven't done your homework. Everything that was written for 5.1.2 should be applicable to 5.3.1 until proven otherwise.
Click to expand...
Click to collapse
Come check my browser, I've read every single thread on the forums man, the thing is 5.1.2 is not same as 5.3.1 and device has locked bootloader and anti-rollback.
So it is not like my Motorola with unlocked bootloader, I am not sure if I always can save the device and also I cannot send it back to amazon if something goes wrong. (I think I can adb sideload 5.3.1 if I hard brick? see I am not sure).
So I had to make it clear everything works for 5.1.2 also will work for 5.3.1
Now I have to convert kingroot to supersu somehow (can't find the option under supertool like you mentioned.)
Your approach was a little bit harsh on me m8
It doesn't say "What can be done on 5.1.2 also can be done on 5.3.1" anywhere, it says the opposite everywhere.
So someone had to clear it out. Thank you for your help, It really helped me a lot.

-Yami- said:
Come check my browser, I've read every single thread on the forums man...
Click to expand...
Click to collapse
...wow, could make a fortune teaching others to speed read. Installing FlashFire from the SuperTool will take care of the necessary prerequisites around KingUser->SuperSU migration. To be honest I'm not sure it's still necessary with more recent FlashFire builds
-Yami- said:
I cannot send it back to amazon if something goes wrong. (I think I can adb sideload 5.3.1 if I hard brick? see I am not sure).
Click to expand...
Click to collapse
- if the device is within the warranty period for your region Amazon will exchange it no questions asked (many data points)
- if you 'hard brick' the device nothing can recover it short of board replacement
- a soft brick can be recovered by side loading FireOS 5.3.1 via the stock recovery menu

Davey126 said:
...wow, could make a fortune teaching others to speed read. Installing FlashFire from the SuperTool will take care of the necessary prerequisites around KingUser->SuperSU migration. To be honest I'm not sure it's still necessary with more recent FlashFire builds
- if the device is within the warranty period for your region Amazon will exchange it no questions asked (many data points)
- if you 'hard brick' the device nothing can recover it short of board replacement
- a soft brick can be recovered by side loading FireOS 5.3.1 via the stock recovery menu
Click to expand...
Click to collapse
The reason that I cannot return device to amazon is, shipment will cost more than the actual device from here to amazon, and I got it as a gift.
and Thanks so I missed out the part that Supertool automates the conversion when I click install Flashfire, thank you.
Now after this post everybody jumping right onto 5.3.1 root gonna know it, and the guy on first page have used Super Sume, so he probably would use
Supertool if he knew.