Hello everyone!
I know some of you are still roaming around here and there trying to root your phone; others wanting to root the phone without knowing what rooting is...
Wandering if it's illegal or not; and why should they be Rooting their Devices.
Well that's why i've done this tutorial with a lot of help from different sources.
It has been almost 2 days reading; reading; reading; and writing this tutorial to simplify and compact information scattered around this forum and the web.
Knowing the Basics
In order to explain everyone (specially noobs / starters); please follow this link.
(I advise you to open it in a "new Tab" or "Window"; so you don't loose yourself)
One thing before starting:
I found out that it is important to reboot the device and the PC after installing and Updating the following apps: "Super one Click" and SDK with your firmware version API's.
Some errors that occur during the Rooting with the "Super One Click" happen due to some kind of need to reboot of the machine and device.
As mentioned in Step #9
[...]
Now that you understand what rooting is; let's ROOT your Android.
P.S - As you already know; you are responsible for doing this process; or for anything that goes wrong.
“Rooting Your Android Phone”
Requirements:
Download: "android-sdk_r15" or Later Version.
After Downloading and Installing SDK; download the API's according to your Firmware Version.
(Check Step #1 and #12 of the Easy Rooting Method)
Download: "Super One Click Program"
(Link Goes to XDA Developers "Super one Click Program" Thread)
Download: "Java SE Development Kit 7" (or later)
I. (Easy Method - Using “One Click Rooting Program”)
Note: This method works for almost every Android phone.
1) Take a note of you brand model and android Firmware/ROM installed on you device.
(You need to know the version of your O.S to download your SDK API's later)
i.e:
“Model: Acer C4 Liquid Mini (E310)”
“O.S: Android Froyo v2.2”
2) Download/Install your Android Drivers. (PC)
3) Download/Install your Android SDK/ADB. (PC)
4) Open SDK (as Administrator) and mark the following things to download:
- “Tools” (Select the entire Folder)
- “Your Firmware/ROM Version Installed” (i.e: “Android 2.2 API”) (Select the entire Folder)
5) Now press “Install Packages” (The download will start; follow the next step after it’s completed)
6) Download / Install the Latest version of the rooting program (Super One Click Rooting Program); unzip it and install it on your computer.
7) Make sure that your phone has the "USB Debugging Mode" ON.
NOTE: To turn it on go to your device and press: “Menu” > “Settings” (Icon) > “Applications” > “Debug / Development” > “USB Debug”
8) Make sure you turn Off your Device and Remove the SD Card. It must be done without the SD Card.
9) Safely disconnect your Phone from the PC; and restart. (PC and Device)
10) When your Phone and Windows are ready; connect your phone to the PC.
Note: Just plug the cable. Do NOT select any option in the Phone.
Also you will notice that a small Android Icon will appear at the top left of the screen.
That means that you phone is prepared for debugging Mode.
11) Once again make sure that your phone has the "USB Debugging Mode" ON.
12) Run SDK/ADB as Administrator.
(Windows XP Users just double click to open)
13) Right Click the “Super One Click Rooting Program” and open it as Administrator.
(Or just double click; if you are using Windows XP)
14) Press "Update Check"; just to make sure you have the latest files. (Don't worry with the app version error; if it happens means you just downloaded it/you have the latest version)
14) Click the "Root" button and wait it to finish. (There should be no errors)
15) Once done; you should see “Superuser” permission in your phone’s apps.
Note: If so; your Device is Rooted. Congratulations!
II. (Advanced Method - Manually Rooting)
Pre-requisites
There are a few things that you need to have before you start rooting.
Obviously, you will need an Android device with Android 1.5 or higher and a USB cable to connect it to your computer.
You will also need to have some files for this:
SuperOneClick.zip and the Android SDK/ADB up and running on your computer.
(Run as Administrator if not using Windows XP)
If you are unfamiliar with ADB, GoodAndEvo site has an awesome ADB tutorial that should get you up to speed.
(Note that the tutorial in the Good and Evo Page is for HTC Devices)
First, we need to move some files around to make running commands a bit easier.
Unzip the SuperOneClick.zip and copy the following files: su-v3, busybox, Superuser.apk, psneuter, and GingerBreak; to the Android “ADB Platform-Tools folder”; which is contained in the Android SDK folder on your computer.
i.e: C:\Program Files\Android\Android-SDK\Platform-Tools\
These files can be found in the following SuperOneClickv2.1.1-ShortFuse folders:
- “Busybox” -> “Dependencies” folder
- “psneuter” -> “Exploit” folder
- “GingerBreak” -> “Exploits” folder
- “SuperUser.apk” -> “Root” folder
- “SU-V3” -> “Root” folder
Once copied rename “su-v3” to “su”.
If you are on Windows, you will also need to have proper drivers for your phone installed.
These can usually be found by going either to the manufacturer website or searching for the name of your phone and the word "Drivers."
Once you find drivers, download and install them like any other application.
Rooting your device
Now that you have ADB setup and the proper exploit files, you are finally ready to Root.
Before you start running commands, you need to put your phone in "USB Debugging" mode.
(Menu > Settings > Applications > Development > Enable USB Debugging) and connect the device to your computer.
Note: Just plug the cable and do not select any option in you device.
Now, open command prompt to run some commands.
Windows Vista/7 Users:
(Press "Windows Key" > Type: "CMD" > Right Click on "CMD" and Run it as Administrator)
In Linux, open whichever terminal emulator suits you. Once you have a command prompt, you need to enter your platform-tools folder, also called a directory.
You can use the "CD" or Change Directory command to accomplish this.
If your SDK folder is called "android-sdk" the command should look like this: cd android-sdk_r11-windows/platform-tools.
This command will leave you with a shell prompt in the platform-tools directory.
From here, you can run the commands that will actually root your phone.
Be sure to run these commands exactly as they are written.
The commands with an "$" or "#" will only run after the "adb shell" command.
First, here are the commands that run the” psneuter” exploit and gain a root shell.
Type them in the following order.
…Yes after the ADB and the “$” there is a “Space”.
• adb devices
• adb push psneuter /data/local/tmp
• adb shell
• $ cd /data/local/tmp
• $ chmod 777 psneuter
• $ ./psneuter
At this point, the exploit will run and close the shell.
You will need to run these commands to restart the ADB server.
• adb kill-server
• adb devices
Now comes the moment of truth.
Type:
• adb shell
...command to open a shell.
If you see a "#" sign, you have root access, so go ahead and continue to the next part of this tutorial.
If not, you can go back and try the previous steps again, or ask for help in the comments.
We now need to make this root permanent.
From the root shell you just opened, type the following commands.
• # mount -o remount,rw -t rfs /dev/block/st19 /system
• # exit
• adb push busybox /system/bin
• adb push su /system/bin
• adb install Superuser.apk
• adb shell
• # chmod 4755 /system/bin/busybox
• # chmod 4755 /system/bin/su
• # mount -o remount,ro -t rfs /dev/block/st19 /system
• # exit
• adb reboot
At this point, your device should reboot.
You can check for the Superuser icon in the app drawer, and then try a root only app like Titanium Backup.
If that app works, congratulations!
You have successfully rooted your Android device.
Prepare to enjoy all the benefits of root.
If you are having trouble with this tutorial or want to offer others a tip, please leave a comment.
Me or every XDA developer/user shall gladly help you out clarifying any error message or issue. (at least if i know how i will help)
Just make sure you did exactly as described; and only then post your question / expose your issue(s).
P.S
- Use “Code” Tags to report Logs.
- Remember to "Thank" if this tutorial helped you or if you find it usefull.
Special thanks to:
XDA Developers (Users & Staff)
Pocketables.net (Aaron Orquia)
CLShortFuse (For bringing such Great App)
I can´t do this with method #1 (freeze on step #6)
In method #2 ....
$ cd /data/local/tmp
cd /data/local/tmp
$ chmod 777 psneuter
chmod 777 psneuter
$ ./psneuter
./psneuter
Failed to set prot mask (Inappropriate ioctl for device)
$
Some help?
Regards
niki40 said:
I can´t do this with method #1 (freeze on step #6)
In method #2 ....
$ cd /data/local/tmp
cd /data/local/tmp
$ chmod 777 psneuter
chmod 777 psneuter
$ ./psneuter
./psneuter
Failed to set prot mask (Inappropriate ioctl for device)
$
Some help?
Regards
Click to expand...
Click to collapse
Greetings;
What's your device Make and Model?
Try/Check the following:
- Download the "Super One Click Program" Again. Since there is a new Fix for it.
Follow this Link to download and get more detailled info:
http://forum.xda-developers.com/showthread.php?t=803682
- Check that you have the USB Debug Turned ON (in your device)
---> List > Settings > Applicatons > Development > USB Debugging
- Check what version do you have in your device; and verify that SDK Manager has downloaded your Version API's; and Tools folder. (Look at status tab; it should say installed)
- Did you Restart the machine after the install of Super One Click and SDK Manager? (Only then Root the Device)
- In a Last case there's a small percentage that your phone isn't compatible with "Super One Click".
Thanx a lot bro
You Can Add This To The OP If You Want .
Press Thank If I Help .
For Sony Ericsson Xperia Only .
I Use A Sony Ericsson Xperia X10 And It Work Well .
The File Name Is Call Flash Tool .
The Fuction It Has Is ( Latest 4.2 )
Root
Flash Kernel
Flash Rom
One Click Unlocked Bootloader .
Click to expand...
Click to collapse
Thing You Need To Do Is :
Download The Two File .
Install In The Same Place .
Open The File .
Open Driver Folder .
Install The Driver .
And Open Flash Tool exe .
See If The Computer Detect Your Phone .
USB Debugging Must On .
Click to expand...
Click to collapse
Thing Your Need ( For Rooting Only ) :
https://github.com/Androxyde/Flashtool/downloads
==================================================
Unlocked Bootloader Try At Your Own Risk . Sony Ericsson Xperia X10 Success ) :
Only For Sony Ericsson Xperia Phone .
Download Generic version 2.3.3 build 3.0.1.G.0.75 ( http://www.multiupload.com/564T6TLUD8 )
Download DoomLoard Boot Manager . ( http://doomlord.sylvester20007.com/...tmanager/X10_2.3.3_Stock-BootManager-v1.3.ftf )
Put This Two File In Flash Tool Frimware Folder .
Open Flash Tool .
Press Flash .
Select All The File Inside .
Reboot Your Phone .
Root Your Phone .
And Install DoomLoard Boot Manager .
You Can Now Install Unlocked Bootloader Rom .
Click to expand...
Click to collapse
If Anyone Know Anything And Notice I Say Wrong Here Please Private Message Me Or Comment Here To Tell Me
Special Thank To :
Every One That Teach Me Last Time .
Androxyde For Flash Tool . http://forum.xda-developers.com/showthread.php?t=920746
DooMLoRD For DoomLoard Kernel And Boot Manager . http://forum.xda-developers.com/showthread.php?t=1278318
Every Body Who Click Thank .
Every Body Who Read .
Click to expand...
Click to collapse
==================================================
Do It At Your Own Risk . Press Thank If I Help
And Yes It Work For New Xperia ( 2011 Lines )
nice share...but i already rooted my xperia
Can any one plz root this tablet...... M so depressed coz it doesn't include google play if it can be rooted....i could buy dis.....
successfully rooted HCL ME U1 Tablet
jeevan92ultimate said:
Can any one plz root this tablet...... M so depressed coz it doesn't include google play if it can be rooted....i could buy dis.....
Click to expand...
Click to collapse
This guide is successfully tested by me.
1. You need a 32 bit OS. (I have used 7 Pro x86).
2. Turn USB debugging ‘ON’ in settings of the tablet.
3. Download Superuser. Then extract the zip file to desktop :\ & you will see 2 folders as “System” and “Meta-INF”.
4. Download the drivers from here. Then connect the tablet & install the drivers using device manager.
5. Download SuperOneClick!. Extract the archive, go to the folder named ADB. Open an elevated command prompt there using this.
6. Continue with the following commands:
Code:
>adb root (you will see a message “adb is already running as a root”)
>adb devices (you should see your device number)
>adb shell (adb shell will run and daemon tool will also run) 7. Now restart the tablet & wait till the home screen appears. Now continue with the following commands:
Code:
>adb shell getprop ro.secure (output should be 0)
>adb shell mount -oremount,rw /dev/block/system /system
>adb push d:\system/bin/su /system/bin/
>adb push d:\system/bin/su /system/_install/bin/
>adb shell chmod 4777 /system/bin/su
>adb shell mount -oremount,ro /dev/block/system /system 8. Exit adb, disconnect the tab, restart it again.
9. Open the new Superuser app just once.
10. Download apks of BusyBox, Google Play & Titanium Backup (Google is your friend!!).
11. Install BusyBox first, then check the rooting status with Titanium Backup. After that, install Google Play.
Move your discussion into device forum.
If it doesn't have it, move it to Android Hacking and Development
Trolls, trolls everywhere
ppero196 said:
Move your discussion into device forum.
If it doesn't have it, move it to Android Hacking and Development
Trolls, trolls everywhere
Click to expand...
Click to collapse
Sorry, ppero196. OK
Hi there XDA. Long time lurker, first time poster. Many general thanks to everyone over the years.
So my screen completely gave out a couple of days, but the phone still works. I can still make voice commands etc. I recently lost my other computer where i did most of my ADBing from, so when i hook it up to my temporary laptop, adb is returning "unauthorized." Basically what I want to do is try something like: http://forum.xda-developers.com/showthread.php?t=2786395 but none of the tools i've found is allowing me to modify any of the kernel boot.img i've found. Unpacking works, but repacking is failing somewhere. It is making a .img file but when attempting to reunpack it just errors out. The new boot.img is also about 2K smaller than original which shoiuldn't be the case as I added 3 lines of text to the build.prop file.
So, I ask, does anyone know of a preexisting adb debug enabled and open (no auth required) kernel that I can fastboot? If not, does anyone know of any tools that can properly unpack/repack a boot.img for the S5. Finally, any other potential options of gaining control over my phone for the next week or so while awaiting a replacement? I can also install apps from the google play store, idk if any have services that will start automatically after rebooting that would basically give me VNC type access?
Thanks in advance for your time!
Much easier than that actually
Update:
So to get into an android phone it's actually quite easy.
To solve unauthorized device from adb:
Step 1: Reboot into recovery mode.
Step 2: Run "adb shell" from the ADK.
Step 3: backup /data/misc/adb/adb_keys [optional] by entering command "cp /data/misc/adb/adb_keys /data/misc/adb/adb_keys.bak"
Step 4: Type "exit" to leave shell.
Step 5: Using adb, push adbkey.pub (In .android of your home directory) to /data/misc/adb/adb_keys
Step 6: Reboot phone.
If you didn't already have USB debugging enabled for some reason:
Step 1: Reboot into recovery
Step 2: Run "adb shell" from the ADK.
Step 3: In the shell enter commands:
mkdir /realsystem
mount /dev/block/platform/15570000.ufs/by-name/SYSTEM /realsystem #Note: This will vary by device but should be very close to actual command.
echo "persist.service.adb.enable=1" >>/realsystem/build.prop
echo "persist.service.debuggable=1" >>/realsystem/build.prop
echo "persist.sys.usb.config=mass_storage,adb" >>/realsystem/build.prop"
reboot #Or follow above steps if both need to be done, they can be done at once.
FOR FIRE HD 10 (7th GEN, 2017) ON 5.6.0.0 ONLY
Seems like this is a tradition so I will put this on here.
Update 4: 2018/1/14, Offline rooting method by retyre (If no new method comes out, this will be the final update)
Update 3: 2018/1/1, Minor text fix
Update 2: 2017/12/31, New rooting method by bibikalka.
Update 1: 2017/12/28, Added more content
Code:
###Disclaimer###
I am not responsible for the potential damage that will be done to your tablet, such as boot looping and bricking.
Your warranty might be void by doing the following steps.
YOU are choosing to make these modification.
Looks like these methods doesn't work for Fire HD 8 (7th GEN, 2017)
Reason to start this thread
The topic was started by ztrund in this thread and we ended up with a pretty messy thread, which makes people really hard to locate the exact tutorial post. So I think it should be a good idea to start a new thread.
Note: This thread doesn't work for HD 10 (7th Gen) anymore because root access is temporary and it can't survive after a reboot. As a result, don't follow the exact steps on that thread.
Special thanks to strund, DragonFire1024, Blaiser47, mistermojorizin, UROMEGAX, retyre, bibikalka and countless people who helped, discussed and contributed in the original thread.
By the way, please correct me if there is any problem or mistake.
Some useful posts
1. The first detailed tutorial is located in #221 in the original thread. mistermojorizin provided the method and adb shell history.
2. #233 in the original thread. UROMEGAX provided a detailed guide of the method.
3. #304 in the original thread. I provided a more coherent step by step guide.
4. #248 in the original thread. retyre provided a different way to root the tablet. (Blaiser47 wrote that it's easier for him)
5. Easier Way to Root Fire HD 10 used a different approach by bibikalka. (Looks like new method is easier to do) (For legacy method go to post #2)
6. Offline Rooting Method by retyre
After getting root access
1. Xposed & FlashFire posted by retyre
2. tweaks/apps/modules/hacks/optimizations started by razers7t8
New method
Easier Way to Root Fire HD 10 by bibikalka.
Offline Rooting Method by retyre
Legacy way
You need the following things in order to proceed:
1) adb (Available Here)
2) Kingoroot PC version (Available Here)
3) Kingo.to.SuperSU.zip (can be found here in the attachment of the post)
Preparation work:
1. Turn on USB debug mode and "allow third party app to install" on fire HD 10
2. Update Kingoroot to the latest version
Note: There will be a small grey box on the update pop up page. It is up to you whether to uncheck that box or not. I don't think that will affect the following process.
3. Connect your fire HD 10 with your PC.
4. Unzip "Kingo.to.SuperSU.zip". Copy the folder to your internal storage on tablet.
Note: In root explorer the directory is /storage/emulated/0
Let's start:
1.- Install supersu (ver 2.82) on the fire and root file explorer.
2.- Use Kingoroot to root
3.- Open the adb shell and start to type "su" while Kingoroot is rooting (You can also wait until it's done, then type su to proceed)
Code:
[email protected]:/ $ su
Note: Do not type "adb shell su" because you won't be able to type any command once the # appear. The correct way is to type "adb shell" first then start typing "su"
4.- once the # appear i did # mount -w -o remount /system
5.-Uninstall the Kingo super user app normally (Do not choose to unroot in Kingo super user app)
6.- # cd /data/media/0/Kingo.to.SuperSU
7.- # cp ./su /system/xbin/daemonsu (no error was given in my situation)
8.-# chmod 0755 /system/xbin/daemonsu
9.-# daemonsu -d &
10.-# cp ./su /system/xbin/su
11.-# chmod 0755 /system/xbin/su
12.-# rm /system/xbin/supolicy
13.-# rm /system/bin/install-recovery.sh
14.-# rm -rf /system/usr/iku
15.-# rm -rf /sdcard/Kingroot
16.-Open Supersu (and get the Su occupied error)
17.-setting > reinstall (It is not rebooted)
18.-Install Supersu (ver 2.79) and open it
19.-Supersu ask the user to update binary (I tried to update the binary but failed, nothing happened, didn't reboot)
20.-setting > set supersu as a system app (Mine rebooted immediately after doing this step)
21.-Go to google play to launch Supersu (Don't know why the Supersu icon is not shown in the Fire Launcher so this is an alternative way to open Supersu)
22.-setting > set grant as default access
23.-Then (not sure if a reboot is required here) I received a notification from Supersu and it ask me to update binary
24.-Click the notification to update binary and it should work.
Not sure whether it will work or not if SuperSU (ver 2.79) is used in the beginning of the guide.
Personally the method posted here seems simpler and makes more sense to me.
https://forum.xda-developers.com/hd...re-hd-10-7th-generation-t3718629/post74940137
No need to mess with two versions of supersu. After you have root you can just update supersu and binaries to the latest.
I also do not think there is any need to start adb while kingoroot is rooting. It is fine, and maybe better to prevent errors, to just wait until it is done.
I would recommend one always go back to a clean system by sideloading the official Amazon 5.6.0.0 .bin and do not fully set up or connect to the internet until you have rooted. To skip Amazon set up, just select a wifi and enter the wrong password. Then hit back and it will let you skip. May need to do it a few times.
Make sure to say in the op to copy the kingo folder with the files to your SD card storage and clarify that this is the emulated SD. Implied but for newbies just saying you need to have it and not saying where could be confusing.
After you root, if you want the latest updates, at least as of a day or so ago you can still update officially via device options, system updates. But be careful as at some point doing this may remove root if Amazon pushes more updates. To this point I strongly encourage everyone who roots to keep a copy of the current 5.6.0.0 .bin in case you need to recover. If Amazon updates their website with a new updated os, this version may be gone.
Another note, if you are using the fire launcher (default) and new apps are not showing up, just go to manage apps and find the system app called Home Pages. Force stop it and see if that fixes it. If not, go back and force stop and clear data. That should make it work.
I'll add more as I think of things and as this thread evolves.
why do I have problems with the :
... cd /data/media/0/Kingo.to.SuperSU command
and the ... cd /sdcard/Kingo.to.SuperSU command
Obviously , others like me, have problems with it, so the question becomes why do some Fire 10 devices not recognize the commands, when people are transferring the folder to tablet, HOW EXACTLY are they doing it. I open PC and just copy the files to the base directory of Storage Device of Fire. If you got it to work, where did you place the folder and how?
Thank you so much for working to consolidate the root method for the 10. I've been trying to follow these instructions, but they don't clearly explain what you need to do to the Kingoroot app while it's rooting the device and you're in the ADB shell. Do these instructions imply that I need uninstall Kingoroot and not let it finish it's process? Or do I need to wait until Kingoroot is complete with it's task?
Also, did I need to install the "recommended" app which Kingoroot had checked off before starting the 'One Click Root'? Is that recommended app the 'Kingo Superuser' app that's been mentioned which needs to be removed? More importantly, did I need to run Kingoroot as the APK or did I need to install the Windows version in order to do the rooting process? And what does it mean to copy the 'Kingoroot' folder to the SD card? Is there a compressed package somewhere which I need to extract and put into internal storage? Explaining how to use Kingoroot might help in this thread as well.
Right now Kingoroot is 90% done and has been stuck at the number for 15 minutes.
C:\ADB>adb shell
[email protected]:/ $ su
[email protected]:/ # mount -w -o remount /system
[email protected]:/ # cd /sdcard/Kingo.to.SuperSU
[email protected]:/sdcard/Kingo.to.SuperSU # cp ./su /system/xbin/daemonsu
cp: /system/xbin/daemonsu: Text file busy
1|[email protected]:/sdcard/Kingo.to.SuperSU # cp ./su /system/xbin/daemonsu
cp: /system/xbin/daemonsu: Text file busy
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
bakshi said:
Thank you so much for working to consolidate the root method for the 10. I've been trying to follow these instructions, but they don't clearly explain what you need to do to the Kingoroot app while it's rooting the device and you're in the ADB shell. Do these instructions imply that I need uninstall Kingoroot and not let it finish it's process? Or do I need to wait until Kingoroot is complete with it's task?
Also, did I need to install the "recommended" app which Kingoroot had checked off before starting the 'One Click Root'? Is that recommended app the 'Kingo Superuser' app that's been mentioned which needs to be removed? More importantly, did I need to run Kingoroot as the APK or did I need to install the Windows version in order to do the rooting process? And what does it mean to copy the 'Kingoroot' folder to the SD card? Is there a compressed package somewhere which I need to extract and put into internal storage? Explaining how to use Kingoroot might help in this thread as well.
Right now Kingoroot is 90% done and has been stuck at the number for 15 minutes.
Click to expand...
Click to collapse
I'll try to answer as much as possible.
First, use kingoroot pc, not the apk. This is likely to lead to a soft brick where on next boot you get stuck at fire screen forever. If this happens, you will need to recover by sodeloading the official bin. I posted how to do this in the other HD 10 rooting thread so just search there.
Next, I would recommend letting kingoroot pc fully root. Do not stop it or do any adb until it is done. You will have root so can adb and su at any point afterwards as long as you do not reboot as then root is lost. As for the recommended apps tick, I would un check it if you remember. It will still install what it needs to root (kingo supersu) but just less junk for you to have to uninstall later.
For the kingo.to.supersu folder, you need to download the zip the op points to and unzip it to a location on your fire. The directions in the op assumes you do this to your SD card (main storage) but do it where ever and just adjust the commands as necessary. Since there appear to be some issues with doing it to SD, maybe try the downloads folder?
---------- Post added at 09:53 PM ---------- Previous post was at 09:50 PM ----------
davidinfoman said:
why do I have problems with the :
... cd /data/media/0/Kingo.to.SuperSU command
and the ... cd /sdcard/Kingo.to.SuperSU command
Obviously , others like me, have problems with it, so the question becomes why do some Fire 10 devices not recognize the commands, when people are transferring the folder to tablet, HOW EXACTLY are they doing it. I open PC and just copy the files to the base directory of Storage Device of Fire. If you got it to work, where did you place the folder and how?
Click to expand...
Click to collapse
Use adb and explore your devices directories. CD to get to a directory, ls to list things in the directory. It shouldn't matter how you get it onto your fire, but it needs to be unzipped. It also doesn't matter where you put it as long as you adjust the commands accordingly. Maybe try the downloads folder?
Thanks for your quick reply, I'll do this now!
UPDATE: Your advice worked! Thanks for clarifying that we should do this with a factory reset and should use Kingoroot on the PC.
Blaiser47 said:
I'll try to answer as much as possible.
First, use kingoroot pc, not the apk. This is likely to lead to a soft brick where on next boot you get stuck at fire screen forever. If this happens, you will need to recover by sodeloading the official bin. I posted how to do this in the other HD 10 rooting thread so just search there.
Next, I would recommend letting kingoroot pc fully root. Do not stop it or do any adb until it is done. You will have root so can adb and su at any point afterwards as long as you do not reboot as then root is lost. As for the recommended apps tick, I would un check it if you remember. It will still install what it needs to root (kingo supersu) but just less junk for you to have to uninstall later.
For the kingo.to.supersu folder, you need to download the zip the op points to and unzip it to a location on your fire. The directions in the op assumes you do this to your SD card (main storage) but do it where ever and just adjust the commands as necessary. Since there appear to be some issues with doing it to SD, maybe try the downloads folder?
Click to expand...
Click to collapse
Part of my problem was seeing written many times ... put files on SD card, and I thought we had to have an external SD card put in the tablet. ( I have been running with that "false IDEA" for a couple of days until an hour ago.
No! SD card just refers to location that is on Fire Tablet itself. The ls command helped me a lot. Others should be aware of this.
I thank Blaiser47 for pointing that out. I am getting much further so far, following the advice in this thread.
Thank you oscarcx for starting this thread. Hopefully you can watch over it, and help correct our errors and giving helpful pointers.
Thanks everybody. I feel better now because the roadblock I hit, has been overcome, now for the other steps in the process.
Too many of these instructions get it completely wrong. There is no using KingRoot to unroot necessary or running the rm commands in the original guides. These instructions were taken from this post by retyre and combined with this post. It's all that would work for me after many many attempts.
Root using KingoRoot as usual; start cmd.exe as administrator. Run the following:
Code:
adb shell
su
3. Do not unroot. Do the non-rm steps in the guide (w.r.t. su and daemonsu). Leave this root shell open.
Code:
mount -w -o remount /system
cd /sdcard/Kingo.to.SuperSU
cp ./su /system/xbin/daemonsu
chmod 0755 /system/xbin/daemonsu
daemonsu -d &
cp ./su /system/xbin/su
chmod 0755 /system/xbin/su
4. Uninstall all the Kingo apps on your tablet (SuperUser, Power Cleaner [if installed], Kinglink) from the Apps page on your Fire's Settings.
5. Copy SuperSU 2.82.apk (2.79 also confirmed working) to your tablet and install.
6. Open SuperSU and update as normal if possible. If "SU is occupied" message appears, go to settings and select "clean for reinstall". DO NOT REBOOT. Force stop SuperSu in Settings > Apps.
7. Open SuperSU. Update binary as Normal when asked if possible. It should complete in a minute or two, but report "Installation failed." No worries. Click to reboot. (If it doesn't report an outcome ("failed") in a couple of minutes, go to the Fire's Apps and force-stop SuperSU and retry.)
8. Upon reboot, SuperSU should be functional. Choose "Grant" as the default access.
manaox2 said:
Too many of these instructions get it completely wrong. There is no using KingRoot to unroot necessary or running the rm commands in the original guides. These instructions were taken from this post by retyre and combined with this post. It's all that would work for me after many many attempts.
Root using KingoRoot as usual; start cmd.exe as administrator. Run the following:
Code:
adb shell
su
3. Do not unroot. Do the non-rm steps in the guide (w.r.t. su and daemonsu). Leave this root shell open.
Code:
mount -w -o remount /system
cd /sdcard/Kingo.to.SuperSU
cp ./su /system/xbin/daemonsu
chmod 0755 /system/xbin/daemonsu
daemonsu -d &
cp ./su /system/xbin/su
chmod 0755 /system/xbin/su
4. Uninstall all the Kingo apps on your tablet (SuperUser, Power Cleaner [if installed], Kinglink) from the Apps page on your Fire's Settings.
5. Copy SuperSU 2.82.apk (2.79 also confirmed working) to your tablet and install.
6. Open SuperSU and update as normal if possible. If "SU is occupied" message appears, go to settings and select "clean for reinstall". DO NOT REBOOT. Force stop SuperSu in Settings > Apps.
7. Open SuperSU. Update binary as Normal when asked if possible. It should complete in a minute or two, but report "Installation failed." No worries. Click to reboot. (If it doesn't report an outcome ("failed") in a couple of minutes, go to the Fire's Apps and force-stop SuperSU and retry.)
8. Upon reboot, SuperSU should be functional. Choose "Grant" as the default access.
Click to expand...
Click to collapse
manaox2
Thank You! Thank You! Thank You!
You are the man!
Only those of us that have been frustrated with this process can appreciate your KEEP IT SIMPLE approach to this!
Not sure why the other BIG thread on this couldn't do a step by step like you just did!
You listed the steps that were screwing around with me the last couple of days.
Finally it is ROOTED! Yeah!
Ok i know this is a silly question but how do you install the apk for Super SU or if I need to reload 5.6 APK? Where do I place them when its connected to the PC and how do i actually launch the install process on the tablet in ES file manager ( for SU) and also for if it gets bricked and I need to sideload the official amazon 5.6?
Has anyone tried this method with HD 8 2017 ?
dusty23007 said:
Ok i know this is a silly question but how do you install the apk for Super SU or if I need to reload 5.6 APK? Where do I place them when its connected to the PC and how do i actually launch the install process on the tablet in ES file manager ( for SU) and also for if it gets bricked and I need to sideload the official amazon 5.6?
Click to expand...
Click to collapse
1. You can get it from Google Play or get it from any liable third party app store.
2. If you get it from any liable third party app store, place it directly in the internal storage so you can install it in es file manager.
3. I remember seeing a post about how to save the bricked device in this forum. You can try to follow that post if your tablet got bricked.
YEAH!!!
rooted baby!!!! now can i get rid of the home tabs?
never mind... i disabled fire launcher
Silly question perhaps, Do I need to reset the device before attempting this?
Guys, how about HD8 2017 ?
wikke said:
Silly question perhaps, Do I need to reset the device before attempting this?
Click to expand...
Click to collapse
It is recommended but may not be required
hacker-on said:
Guys, how about HD8 2017 ?
Click to expand...
Click to collapse
As reported in the original long thread, it doesn't work on Fire 7 or Fire HD8.
my .02, i like these instruction by @retyre. Easy peasy when I had to re-root. mostly just posting here for my own reference, hope it's ok.
retyre said:
I have done this with success multiple times over the last day, so try this and report:
1. Start with a pristine /system (adb sideload update .bin if you can).
2. Root using KingoRoot as usual; confirm su usage in adb shell.
Code:
adb shell
su
3. Do not unroot. Do the non-rm steps in the guide (w.r.t. su and daemonsu). Leave this root shell open.
Code:
mount -w -o remount /system
cd /sdcard/Kingo.to.SuperSU
cp ./su /system/xbin/daemonsu
chmod 0755 /system/xbin/daemonsu
daemonsu -d &
cp ./su /system/xbin/su
chmod 0755 /system/xbin/su
4. Uninstall all the Kingo apps (incl. SuperUser) from the Apps page on your Fire's Settings.
5. Confirm su and daemonsu are in /system/xbin/:
Code:
cd /system/xbin
ls -al
If not, copy them to /system/xbin/ as in step 3.
6. Copy SuperSU 2.79 .apk (other versions might work, but this is the one I have tried) to your tablet and install.
7. Open SuperSU and update binary as Normal. It should complete in a minute or two, but report "Installation failed." No worries. Click to reboot. (If it doesn't report an outcome ("failed") in a couple of minutes, go to the Fire's Apps and force-stop SuperSU and retry.)
8. Upon reboot, SuperSU should be functional. Choose "Grant" as the default access.
Click to expand...
Click to collapse
oscarcx said:
3. #304 in the original thread. I provided a more coherent step by step guide.[/SIZE]
Click to expand...
Click to collapse
When I use KingoRoot it gets stuck at 90%, nevertheless su binary exists and is working.
The folder /data/media/0/Kingo.to.SuperSU however does not exists.
So I skip steps 7-11.
The folders /system/usr/iku and /sdcard/Kingroot do not exists, so I skip 14 & 15 as well
SuperSU does not show "ocupied", but the update binary pop-up (as in step 19) which seems to be successfull (non-recovery install).
I move SuperSU to /system (SuperSU config) and reboot manually.
afterwards the boot is stuck at the "fire" Logo, a soft brick. I tried this two times using adb sideload to reset the system.