###YOUTUBE VIDEO WILL BE UP SHORTLY###
###ALSO THE GUIDE WILL GET MORE DETAILS AND INFORMATION IN A SHORT PERIOD OF TIME###
###Before you ask, i use Quote instead of Code to NOT cut of the Code###
Requirement:
- Fire Tab 6" or 7" 4th Generation
- be patient
- be Aware - things can go wrong, if ANYthing is unclear, please ask first!
- Around 30~ to 60~ Minutes
depending how fast you get ADB and everything else required to get to the initial Root.
IF you already using ADB with your Fire, Check Step 3, THEN go to Step 7
Hi there,
In this Tutorial you will learn how you can root your Amazon Fire HD 6" or 7" Tablet.
First we are going to root it using Kingroot, after thet we Sideload SuperSU Root.
Please note this Tutorial requires the 4th(!) Generation of Fire Tabs.
Error-Solutions are at the BOTTOM of this Document!
NOTE: This Tutorial includes:
-Install ADB using Android Studio (also Windows 8, 10)
-Disable Fire Tab Ads
-Connect to Google
-Install Google GAPPS
-Install Custom Launcher
-Replace Default FireLauncher with Custom Launcher
-Root Device
-Sideload superSU, replace Root
-Install Google Store
-Implement Google Service as System-Apps
-Block Google-Phone-Home, AutoUpdates
Step 1:
Download the required Files (~180 MB)
Link: https://drive.google.com/file/d/0B5zOo5KIf0WdSVZKUllhQm85alk/view
Step 2:
Get Android Studio (FULL Install ~800MB)
Check the Android Studio Dir this ZIP contains and execute "Get AndroidStudio.lnk"
Step 2.1:
- After installing Android Studio launch it, click "Configuration" and Select the SDK (first Option)
- Select "Tools" at the Top and click "Manage Add-on Sites"
- Click the "User Defined Sites" Tab and click on "New..."
- Paste this URL:
http://kindle-sdk.s3.amazonaws.com/addon.xml
Click to expand...
Click to collapse
- confirm with "OK"
- Close this Window after and go back to the Mainwindow "Android SDK Manager"
Step 2.2:
- Scroll down until you see the "Extras" Folder, select "Kindle Fire USB Driver"
TIP: Click "Deselect All" first and reselect "Kindle USB Driver" so you don't have to install the Whole Package.
- Click "Install x packages..." after and wait until it's installed. After it's done you can close the SDK Manager Process.
Step 3:
- Open the Android SDK Main Dir wich is located for ex:
C:\Users\<USERNAME>\AppData\Local\Android\
Click to expand...
Click to collapse
- Enter "android-sdk\platform-tools"
- Copy the Content from "APT" Dir to this Folder, for ex:
C:\Users\<USERNAME>\AppData\Local\Android\android-sdk\platform-tools
Click to expand...
Click to collapse
- Go back to the Mainfolder and enter "sdk\extras\amazon\kindle_fire_usb_driver"
Step 4:
- Open your Devicemanager (Controlpanel > Devices > Devicemanager) and connect your Fire Tab to the Computer
- Open the Internal Storage of your Fire Tab and go to "Download" Dir at, copy & paste the whole Content from APK Dir to Fire Tab's Download folder.
Step 5:
- Open "Settings" at your Fire Tab Device and select "Applications"-Tab, enable Third Party Application.
- Go back to Settings and go to your Device Propertys, now tap the "Serialnumber" Field until you enable the Dev-Mode.
- Enter Developersettings and enable "ADB" at the "Debugging"-Tab.
Step 6:
- Now (you are still at the Devicemanager) select the "Fire", it should be displayed as a protable device.
- Rightclick it and select "Uninstall".
If there is any other Kind of "Fire" you should install them, too.
Do NOT close the Devicemanager now.
###
---If you use Windows 8 or 10 - go to the Bottom now to see what you have to do instead of the following---
###
- Unplug your Device now and Run (As Admin) the "KindleDriver.exe" at your Amazon Folder located at AndroidSDK
- Install it (should give you a green tick if everything was correct)
- After you installed it - connect the Fire Tab again.
- If your Fire Tab Fire is not marked as "ADB Device" repeat
Step 7:
- Now ADB and your Fire Tab are ready to get tested.
- Your Fire should already be connected to your device, if not, do so.
- Run a Command Prompt (Win+R and type "cmd" without ")
- now first go to your Android AD Location wich should be by default:
C:\Users\<USERNAME>\AppData\Local\Android\android-sdk\platform-tools
Click to expand...
Click to collapse
- After you found the correct dir, copy the Path, go to your Command Prompt, paste it with "cd " in Front of it.
cd C:\Users\<USERNAME>\AppData\Local\Android\android-sdk\platform-tools
Click to expand...
Click to collapse
###NOTE: All ADB-Commands are single-lined Commands.
Even if there are empty lines between them, it's just for better orientation.
Each command has to be added, one by one!
Step 8:
- Now you should be at the correct Dir, write
adb kill-server
Click to expand...
Click to collapse
Then
adb start-server
Click to expand...
Click to collapse
- The Server should start now, after it's online write
adb devices
Click to expand...
Click to collapse
- Your Device should now be displayed at the Prompt, if it says "Unauthorized", check your Tab, accept the Message and type again
adb devices
Click to expand...
Click to collapse
- It should now be displayed as "device"
Step 9:
- Enter
adb shell
Click to expand...
Click to collapse
at your Command Prompt
- Now let's make connection with Google.
- Enter the following command and accept with Enter of course
pm grant com.google.android.gms android.permission.INTERACT_ACROSS_USERS
Click to expand...
Click to collapse
---Optional: to Block Ads from the Lockscreen menu type this:
pm block com.amazon.kindle.kso
Click to expand...
Click to collapse
Step 10:
- Go to your device and run Amazon Appstore look for "ES File Explorer" and install it.
- After that, we are starting to Install GAPPS.
NOTE: After each App, REBOOT your device and install the next one!
- Open ES File Explorer and go your "Download" Folder.
- Install the Apk's in this Order, don't forget to reboot:
Google Account Manager
Google Service Framework
Google Play Services
Google Play Store
Click to expand...
Click to collapse
- Now you can Create your Account and Log-In if you like
- After this Step, you do not need to reboot after the next APKs.
Google Play Games (also Create Acc/Login if you like)
Aptoide
VireLauncherPro
RootChecker
KindleReader (The default one may not work anymore)
Click to expand...
Click to collapse
Step 11:
- Back to adb Shell Prompt, we are going to Block our Amazon Default Launcher, type
pm block com.amazon.kindle.otter
Click to expand...
Click to collapse
- Now just Launch VireLauncher and mark it as default if it asks for.
- Now we got what we need to proceed for our root.
-----------IMPORTANT: In order to make sure all Amazonapps are Still working after the initial Root
-----------It is recommend to run all Amazon Apps you are going to use even once (MOST important after factory Reset)
Step 12:
- UNPLUG your Fire Tab (IMPORTANT)
- Open your ES File Explorer at the Download Tab and install
KingRoot-4.0.0.233-release-201505071219_105001
Click to expand...
Click to collapse
- Run KingRoot and tab the blue button at the bottom
- Now KingRoot is going to root your device, the device restarts during this Process.
- After the Device restarted.
- Click the Check Button (Top right Corner) and scroll up, it should say rooted, if NOT - restart KingRoot again and Root again.
Step 13:
- Go back to our Commandprompt (if you are still in ADB Shell, type "exit" first) and now excecute those Commands
adb push su /data/local/tmp
adb push busybox /data/local/tmp
adb shell
Click to expand...
Click to collapse
- Now simply type
su
Click to expand...
Click to collapse
- now the following commands one after another, remember each command is a single line!
mount -o remount,rw /system
cat /data/local/tmp/su >/system/xbin/daemonsu && chmod 0755 /system/xbin/daemonsu
cat /data/local/tmp/busybox >/system/xbin/busybox && chmod 0755 /system/xbin/busybox
daemonsu -d &
Click to expand...
Click to collapse
Leave the ADB Terminal for now and go back to your Device, open the KingUser App
Click at the Top Right Corner on the Screen, click the Root authorization Settings and Remove Root Permission.
go to Settings > Application > All Applications/Third Party and uninstall the other King Applications (KingRoot and a Chinese one)
Go back to ADB now and enter the following commands one after another:
cat /data/local/tmp/su >/system/xbin/su && chmod 0755 /system/xbin/su
busybox chattr -ia /system/xbin/ku.sud
busybox chattr -ia /system/xbin/supolicy
rm /system/xbin/ku.sud
rm /system/xbin/supolicy
rm /system/bin/rt.sh
rm /system/bin/install-recovery.sh
rm /system/bin/shipclean
rm /system/bin/start-ssh
busybox chattr -ia /system/etc/install-recovery.sh
busybox chattr -ia /system/etc/install-recovery.sh-ku.bak
rm /system/etc/install-recovery.sh
rm /system/etc/install-recovery.sh-ku.bak
rm /system/etc/install_recovery.sh
rm /system/usr/icu/icusuflag.conf
busybox chattr -ia /system/usr/iku/isu
rm -rf /system/usr/iku
rm /system/kroot_*
rm /sdcard/kr-stock-conf
rm -rf /sdcard/Kingroot
Click to expand...
Click to collapse
Step 14:
- leave the ADB Terminal again and open your ES File Explorer
- Install superSU now, then run it and let it update after that reboot your Device
- Leave the Device for around 5 Minutes after Reboot.
- Now run your RootChecker and click the Checkbutton at the Top right, and scroll up again, it should say "rooted".
Step 15:
- Go back to ES File Explorer but leave ADB open as always, Install
SysAppConverter
Click to expand...
Click to collapse
- Open the SysAppConverter after and add the following things to your "System-Apps"
Google Play Store (com.android.vending)
Google Services Framework (com.google.android.gsf)
Google Play Services (com.android.google.gms)
Click to expand...
Click to collapse
Step 16:
- After you have done this, go back to ADB Shell and stop them from Phoneing home
pm block com.amazon.otaverifier
pm block com.amazon.dcp
Click to expand...
Click to collapse
Also enter the Playstore, top right corner -> uncheck autoupdate
Swipe to the right, click Settings and also disable autoupdates.
Finally, you are ready and your Device is rooted including Access to Google Playstore
IMPORTANT: If Apps or Playstore should not work because of reasons, there is a simple trick just reset your Google Frame Services.
Open SystemAppConverter
Browser for "Google Play-Services" (The Puzzle Piece) and hit the "System" button to the right.
Now select "Remove Updates". Now wait around a minute. Try if it works, if not - restart the Device.
Sometimes the Screen can Flash or the Tab will just shut down.
-------------------------------------------------------------------------
WINDOWS 8
Go to the Windows 8 folder, There is a tutorial how to install ADB on Win 8, then back to Step 7
WINDOWS 10
Click this Link: http://pdanet.co/a/
Download PdaNet+ "Version 4.18 installer for Windows" for ex.
If you haven't done yet, unplug your Fire Tab and install PdaNet.
After you installed it completly ADB should be ready now.
Go to Step 7
-------------------------------------------------------------------------
###VIRE SETTINGS###
#Launcher Settings#
Enable reflections - y
Lock Home screen - n
Themes - Stock
Home transition style - Crystal
Advanced Features - include Wallpaper - y
" - Full Screen Transitions - y
" - Enable Frame
" - Enable HD Shaders - y
" - Enable infinite Scroll - y
" - Homescreen - iconlabelsize - large
Icon
Show icon Shadow - y
Icon Style - none
Icon pack Settings - None
Homescreen - Add App - Vire App - Clock
Click to expand...
Click to collapse
thanks for this- tried to download the link in Step 1 but the google drive link is protected. I requested access- email has "ben" in it, just hoping to try this out on my hd7.
I'd REALLY like to be able to follow your guide here, but...
Unfortunately I can't advance past the first couple steps because the google drive link posted in STEP ONE containing all the necessary files requires permission from you before I can download it.
Once you fix this, this guide will really help everyone.
Hell i'm sorry i updated the Link! Going to edit soon, there are a lot of parts pretty undetailed.
thank you, it's downloading for me now
Great, thanks for the Reply about that, just updated the "Tutorial" a bit, so it's maybe a bit more easy to read, my english is so rusted - i didn't even noticed before i wrote it.
As said, i'm going to add much more details, if ANYTHING is unclear, please reply i'm going to detail it more, so no mistakes will happen.
Step 7 CMD window - suggestion for noobs
vismxownz said:
Great, thanks for the Reply about that, just updated the "Tutorial" a bit, so it's maybe a bit more easy to read, my english is so rusted - i didn't even noticed before i wrote it.
As said, i'm going to add much more details, if ANYTHING is unclear, please reply i'm going to detail it more, so no mistakes will happen.
Click to expand...
Click to collapse
Wow! Thank you SO much. Step 7 might be a little unclear. Not sure "first copy the Android ADB Location" -- copy from where?-- and then "write to your Commandprompt" cd (ADB location)" -- do you mean write "cd" (no ") and paste what you copied? Just a thought . . .
Think it would be simpler to just open CMD window from adb.exe folder::
1. Open the folder containing adb.exe. (Should be C:\Users\<USERNAME>\AppData\Local\Android\android-sdk\platform-tools)
2. Hold down the shift key and right-click a white space in the folder. Choose "open command window here."
also for step 2.1 i wasn't able to get the fire SDK listed in the android SDK manager until i added the following URL
https://s3.amazonaws.com/android-sdk-manager/redist/addon.xml
I have to say that I am pretty underwhelmed by the instructions, since all they do is expand what others have tried for GAPPS with only limited success ...
Btw, the easiest way to get adb drivers is to follow this post, there is much less to download :
http://forum.xda-developers.com/showpost.php?p=58822885&postcount=6
And for the rest, follow the earlier guide to rooted Fire with non-working GAPPS:
http://forum.xda-developers.com/fire-hd/general/playstore-t3110773
Unfortunately, the GAPPS fail to work reliably using similar instructions, and there is no consistent fix yet.
Awaiting more useful instructions now ...
bibikalka said:
I have to say that I am pretty underwhelmed by the instructions, since all they do is expand what others have tried for GAPPS with only limited success ...
Btw, the easiest way to get adb drivers is to follow this post, there is much less to download :
http://forum.xda-developers.com/showpost.php?p=58822885&postcount=6
And for the rest, follow the earlier guide to rooted Fire with non-working GAPPS:
http://forum.xda-developers.com/fire-hd/general/playstore-t3110773
Unfortunately, the GAPPS fail to work reliably using similar instructions, and there is no consistent fix yet.
Awaiting more useful instructions now ...
Click to expand...
Click to collapse
First I want to say thank you for the instructions this is a more detailed version of the steps I was taking. I had full intention to clean up my guide once we solved the problems we are currently having. I'm pretty sure these steps above are the basic steps of getting the Playstore but we are still not without issues. I'd be interested to see how many people this is working.
After all that, i still dunno why People got still issues - in first place with PlayStore.
It's the 6th (and 5th Day) for both HD 7" - still everything is working - PlayStore, also downloads and Cache Cleaning like a charm.
Also the Tablet seems to work faster now, cause of disabled Amazon Startup-Apps.
Also bibikalka is right, there are less big downloads, also you can evade downloading the whole SDK if you do not like, to. But you safed it for Future uses and instructions.
Also my first DL is above 100MB because it also includes the GAPPS, they are working as said and still working after nearly a week of usage on 2 Fire Tabs.
Just wanted to help, not that pro in writing instructions as you may already know.
But after all this, is Play Store application working?
devicer said:
But after all this, is Play Store application working?
Click to expand...
Click to collapse
As said before, nearly a week without any problems. Applications updating fine (for sure execluding Google Apps, don't updating anymore) - they should work until there is a update wich REQUIRES a newer Version of any GAPPS. But as said they work.
Thanks for the tutorial!!!
I got supersu and playstore installed and worked. This is what I did.
First I used playsevice 6.5.99_(xxxxxxxxxx-034) the last 3 number (-034) suppose to be the correct one for HD6. It work only the first time then update itself to 7.3.29 so no good.
So I changed to playservice 6.1.88_(xxxxxxxxxx-032). This one so far working very good after a few reboots. It won't update itself. Maybe because its not the correct one? But since it work so who care.
Now I can download apps, games no problem at all. So anybody got problem, maybe try playservice 6.1.88_(xxxxxxxxxx-032). I think thats a reason.
droidnext said:
Thanks for the tutorial!!!
I got supersu and playstore installed and worked. This is what I did.
First I used playsevice 6.5.99_(xxxxxxxxxx-034) the last 3 number (-034) suppose to be the correct one for HD6. It work only the first time then update itself to 7.3.29 so no good.
So I changed to playservice 6.1.88_(xxxxxxxxxx-032). This one so far working very good after a few reboots. It won't update itself. Maybe because its not the correct one? But since it work so who care.
Now I can download apps, games no problem at all. So anybody got problem, maybe try playservice 6.1.88_(xxxxxxxxxx-032). I think thats a reason.
Click to expand...
Click to collapse
Yes the GoogleCode got Patchday and 034 got patched. BUT to evade you also can go to your SysCustomizer and Reset the Google Play-Service to "Systemdefault" so it resets back to the first installed version. Until this gets a problem you can do it over and over again, so it would take just like 1 minute to fix the issue. Also there is no error or fail in using an "outdated" Version. Thanks for your Sharing i updated my uploadings
Everything is working now, and does not self update, see here :
http://forum.xda-developers.com/fire-hd/general/root-play-store-short-disabled-self-t3113975
Anyone else have problems setting up supersu?
Sent from my LG-V480 using Tapatalk
I'm waiting for the tuto video
thanks for the work btw !!!
Wich Problems?
greetings
So if we want the Google play store, we won't be able to use the default launcher anymore ? damn it ...
is it an obligation ?
Related
Hi,
I rooted my Nook 1.2 with ManualNooter 4.5.6 and have it running at 1.1GHz. Have some issues and was wondering if I can get some help.
How do I install non-market apps? I went to the amazon page and was able to download the Amazon_Appstore-release.apk. When I click on it, I get a choice of App Installer and Package Installer, neither of which works. I've tried unchecking and checking "Allow Non-Market Apps" in Nook Tools, but it still didn't work. It notes that the apk must be copied to /system/app...how do I do that?
I've installed SetCPU (full version) from the market and set max to 1100. SetCPU seems like it can do so much more, but I'm hesitant to mess anything up. Anyone willing to share their settings?
When looking through the Battery Use stats, I noticed that Cell Standby is using up 49% battery, and Phone Idle another 2%. Is there some way to set airplane mode or something to disable those?
Thanks,
kftgr
Easy solutions (although they take some steps). I've done both of these.
Amazon App Store:
* Download to your PC
http://amzn.to/getamazonappstore
* Put the apk onto your sdcard.
* Use a File Manager that will give you Read/Write access. I use SUFBS, so I'll give instructions for that.
Open SUFBS, rotate your nook on it's side and click the S and the D in the upper left hand corner. For whatever reason, at least on my Nook, it must be in landscape to be able to click the S.
* Navigate to the Amazon App Store apk. In my case, it was /sdcard/Amazon_Appstore-release.apk
* Click on it, click "Install", click "Package installer".
It should install, and ask you to log in.
DONE!
For the Cell Standby issue, you need to rename two apk's, you can do this in ADB, but since we're in SUFBS anyway:
* Navigate to /system/app
* Long Press "Phone.apk" until a menu pops up
* Select "Rename", rename it to "Phone.OLD"
Next, still in /system/app
* Long Press "TelephonyProvider.apk" until the menu pops up
* Select "Rename", rename it to "TelephonyProvider.OLD"
REBOOT
DONE!
If you ever want to turn those two back on, just replace .OLD with .apk and reboot again. It will make a difference in your battery life. Let me know if you have any questions. Good luck.
I downloaded the Amazon App store apk and have tried to install it, but whenever I do I get a Parse Error, "There is a problem parsing the package"
Edit: This happens whenever I try to use the Application Installer first, then the Package Installer. I've rebooted the machine and tried just using the Package Installer and I get a error saying my phone has been set to only allow applications from the market to be installed. I've verified that in the Nook Tools the "allow non-market apps" checkbox is checked. I even unchecked it and rebooted and it was checked when I went back into the Tools.
KWKSLVR said:
Easy solutions (although they take some steps). I've done both of these.
Amazon App Store:
* Download to your PC
http://amzn.to/getamazonappstore
* Put the apk onto your sdcard.
* Use a File Manager that will give you Read/Write access. I use SUFBS, so I'll give instructions for that.
Open SUFBS, rotate your nook on it's side and click the S and the D in the upper left hand corner. For whatever reason, at least on my Nook, it must be in landscape to be able to click the S.
* Navigate to the Amazon App Store apk. In my case, it was /sdcard/Amazon_Appstore-release.apk
* Click on it, click "Install", click "Package installer".
It should install, and ask you to log in.
DONE!
Click to expand...
Click to collapse
I couldn't find SUFBS in the market, so used Ghost Commander and was able to install the apks with your instructions. Thanks!
KWKSLVR said:
For the Cell Standby issue, you need to rename two apk's, you can do this in ADB, but since we're in SUFBS anyway:
* Navigate to /system/app
* Long Press "Phone.apk" until a menu pops up
* Select "Rename", rename it to "Phone.OLD"
Next, still in /system/app
* Long Press "TelephonyProvider.apk" until the menu pops up
* Select "Rename", rename it to "TelephonyProvider.OLD"
REBOOT
DONE!
If you ever want to turn those two back on, just replace .OLD with .apk and reboot again. It will make a difference in your battery life. Let me know if you have any questions. Good luck.
Click to expand...
Click to collapse
Could you provide the adb instructions? I already have the sdk installed.
I tried the renaming steps in Ghost Commander, but the new name doesn't stick, even though it's been given root.
@r0n1n69:
Just use the steps that KWKSLVR provided. Basically: get a file manager that provides read/write access, navigate to the apk, then install with "package installer."
kftgr said:
Could you provide the adb instructions? I already have the sdk installed. I tried the renaming steps in Ghost Commander, but the new name doesn't stick, even though it's been given root.
Click to expand...
Click to collapse
Try:
Code:
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
adb shell mv /system/app/Phone.apk /system/app/Phone.OLD
adb shell mv /system/app/TelephonyProvider.apk /system/app/TelephonyProvider.OLD
adb reboot
I've installed FileExpert and given it root permission, but I still get the "can only install from market" error whenever I try to install a package from my sdcard. In this case I'm trying to install mobo player, if that makes a difference.
KWKSLVR said:
Try:
Code:
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
adb shell mv /system/app/Phone.apk /system/app/Phone.OLD
adb shell mv /system/app/TelephonyProvider.apk /system/app/TelephonyProvider.OLD
adb reboot
Click to expand...
Click to collapse
Thanks much. Pretty much doubled my battery life
kftgr said:
Thanks much. Pretty much doubled my battery life
Click to expand...
Click to collapse
So what? I enter in that string of text in where? and it doubles battery?
These are my notes and guide for rooting the Kindle with 6.2.1 firmware. If I left something out, or something is not working, please leave a comment and I'll try to update.
Credit goes to JCase for the root. Please consider making a donation to him here:
https://market.android.com/details?id=net.andirc.jcasedonate
Original procedure is here:
http://www.androidpolice.com/2011/1...on-kindle-regardless-of-its-software-version/
ADB INSTALL AND TEST - Method 1 (skip to the ROOT INSTALL section if you already have a working ADB)
NOTE: ADB = Android Debug Bridge. It is a command line interface to the android device. A working ADB is required before you can root your Kindle. ADB is installed on a PC and accesses the Kindle via USB cable.
Install Java SE Development Kit 7 on PC
The Android SDK Manager requires Java SDK
http://www.oracle.com/technetwork/java/javase/downloads/jdk-7u1-download-513651.html
Install Android SDK Manager on PC
The Android SDK has the drivers and ADB needed to perform the root procedure
http://developer.android.com/sdk/index.html
Uncheck Android 4.0
Check 2.33
Ensure Google USB Driver is checked
Install to c:\android to make typing easier later on
NOTE: The install can take a long time!
Manually update files so drivers will properly install
Open c:\users\your account name\.android\adb_usb.ini (or c:\documents and settings... if you have XP) and add the following
Code:
0x1949
Open c:\android\extras\google\usb_driver\android_winusb.inf and make additions as shown:
Code:
[Google.NTx86]
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
....
[Google.NTamd64]
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
Install drivers
Find the Kindle device in device manager and update drivers. Point to the location with android_winusb .inf
Verify ADB works
Open a command prompt
CD to c:\android\platform-tools
Code:
adb kill-server
adb devices
If it's working, ADB will return a large number, like this:
Code:
312342134231342 device
ADB INSTALL AND TEST - Method 2
NOTE: I have not tried this, but Vashypooh's app can apparently handle the driver install, and run ADB without installing the above software. If all of this works, then his app would be the best way IMO.
NOTE 2: I've seen a lot of comments suggesting the driver install in Vashypooh's app doesn't work at this point.
http://forum.xda-developers.com/showthread.php?t=1399889
ROOT INSTALL - Method 1
Install JCase's kindleroot_androidpolice.apk
JCase's app gives ADB root access. Once this is done, you still need to install the superuser app
Download kindleroot_androidpolice.apk to PC
http://www.multiupload.com/VNZ6Y41EQF
Ensure the Kindle is connected via USB, and copy file to Kindle sdcard
Using ES File Explorer on Kindle, navigate to the kindleroot_androidpolice.apk and launch
Follow prompts and click root
Install superuser app
Download superuser-2 to PC
http://www.multiupload.com/M2CX14W7Y0
Unzip to c:\download\sufiles
Use ADB to install SU app
Code:
adb root
adb remount
adb push c:\download\sufiles\su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb install c:\download\sufiles\Superuser.apk
adb reboot
ROOT INSTALL - Method 2
NOTE: I have not tried this, but Vashypooh's app can apparently handle the root process.
BurritoRoot (Temporary)
Install Permanent Root with Superuser
http://forum.xda-developers.com/showthread.php?t=1399889
A+ instructions, wish I could write my own that good lol.
jcase said:
A+ instructions, wish I could write my own that good lol.
Click to expand...
Click to collapse
Thanks to you for the root. I hope the guide will help those trying to root!
Thanks for the clear and easy steps.
Great guide Ectoplasmic!
One thing I would add though, in step 5 "Verify ADB Works", before you use the "adb devices" command, you need to type "adb kill-server". If you don't type in "adb kill-server" first, the device won't show up when you use the "adb devices" command. Or at least it didn't for me.
Otherwise, everything worked FLAWLESSLY. I verified I was rooted using Root Checker. Thank you!
zopzop25 said:
Great guide Ectoplasmic!
One thing I would add though, in step 5 "Verify ADB Works", before you use the "adb devices" command, you need to type "adb kill-server". If you don't type in "adb kill-server" first, the device won't show up when you use the "adb devices" command. Or at least it didn't for me.
Otherwise, everything worked FLAWLESSLY. I verified I was rooted using Root Checker. Thank you!
Click to expand...
Click to collapse
Thanks, I added this to the guide.
Hi I use JCase method to root my 6.2.1 KF, then I need to unroot it so my kids can still enjoy the prime video, but I cannot. I try rootkeeper but failed. I also try the "kindleroot_androidpolice.apk" and click the unroot button, but it still cannot unroot. Pls help!
Get help in irc from jcase and vashypool theyll probably be able to help u
tkcctkcc said:
Hi I use JCase method to root my 6.2.1 KF, then I need to unroot it so my kids can still enjoy the prime video, but I cannot. I try rootkeeper but failed. I also try the "kindleroot_androidpolice.apk" and click the unroot button, but it still cannot unroot. Pls help!
Click to expand...
Click to collapse
Unroot in my app (BurritoRoot) does not remove su, it just turns off adb root (which is what my app turns on) sorry for the confusion.
Will add in the future when I release burritomod
Here's the equivalent instructions for Mac
I am pretty new myself, but I'm happy to share what I've come up with so far. I am on a Mac OS X 10.6.8
Download the Android SDK for Mac (dl.google.com/android/android-sdk_r16-macosx.zip), the easiest place to put it is at the top of your user directory, from the browser download window chose your username from places on the left side, then name the zip "Android"
Next from Finder, navigate to the place where you downloaded the SDK, and double-click on it which should unzip it and create a folder of the same name e.g "Android". Open that and inside it will be a folder "tools", and inside that there will be a file "android". Double-click that to run it and the "Android SDK Manager" program window will pop up, you will also see a Terminal window in the background, don't worry about that. Uncheck all the boxes, then check "Android SDK Platform-tools" which should be the third from the top, and click install. This gets you the actual "dab" program.
Once adb is setup, to get it to recognize your kindle fire on your mac, you may need to make an entry in a config file if you haven't already.
Start Terminal Applications > Utilities > Terminal or if you are used to using spotlight, simply type in "Terminal". (here's an intro to using Terminal guides.macrumors.com/Terminal) and navigate to the directory where you have adb, e.g. if you placed it at the top of your user directory that would be
Code:
cd Android
or if you left it in the default downloads directory it would be
Code:
cd Downloads/android-sdk-macosx/
then enter the following commands
Code:
mkdir ~/.android
You may get the following error
Code:
mkdir: /Users/<username>/.android: File exists
If so, that is fine, continue to the next step
Code:
touch ~/.android/adb_usb.ini
open -e ~/.android/adb_usb.ini
TextEdit will open with that file open, you should have an entry in it on a single line that says
Code:
0x1949
if not, copy that in, then save and close it, then
Code:
./adb kill-server
Connect your kindle to the mac if it isn't already, then
Code:
./adb devices
You should see a message like
Code:
List of devices attached
2ED6000600000001 device
On your kindle, make sure you have a file navigation app, the example above ES FileExplorer is excellent and is the one I use from Amazon app store
Download Burrito Root from Android Police ( androidpolice.com/2011/12/23/exclusive-how-to-easily-root-the-amazon-kindle-regardless-of-its-software-version/)
Also download the Superuser.zip from the same page (multiupload.com/ONH28CB1GU) and unzip, then make sure you move the contents "su" and "Superuser.apk" into the same directory as adb
Through Finder copy the "kindleroot_androidpolice.apk" file you downloaded earlier to your kindle, some place like "download" so you can find it easily later
Now on the Kindle, tap disconnect on your KIndle so you can get back to the apps screen, launch the file explorer you installed earlier, navigate to folder you copied it to, e.g. "download" then install the "kindleroot_androidpolice.apk", open it, and go through the steps to launch click "Root"
Back on the Mac, in the terminal window where you had adb going, enter the commands
Code:
./adb root
./adb remount
./adb push su /system/xbin/su
./adb shell chown 0.0 /system/xbin/su
./adb shell chmod 06755 /system/xbin/su
./adb install Superuser.apk
./adb reboot
You should be rooted now, then you can follow the other instructions out there for getting Android market, etc working
TIP
here's a tip if you don't want to have to type in the period and slash ahead of adb every time. from your terminal window enter the
Code:
cd ~
touch .profile
open -e .profile
That will open text editor, and paste in the following line,
Code:
PATH=${PATH}:/Users/<username>/<sdk-directory>/platform-tools
replacing both our user name and the path to where you have sdk e.g. in my case
Code:
PATH=${PATH}:/Users/kbiz/Android/platform-tools
Then close the terminal window and reopen a new one and you should be good to go, now you'll only need to type in "adb".
Let me know if I missed something, trying to give back since this forum has been super helpful.
---------- Post added at 01:04 AM ---------- Previous post was at 12:58 AM ----------
tkcctkcc said:
Hi I use JCase method to root my 6.2.1 KF, then I need to unroot it so my kids can still enjoy the prime video, but I cannot. I try rootkeeper but failed. I also try the "kindleroot_androidpolice.apk" and click the unroot button, but it still cannot unroot. Pls help!
Click to expand...
Click to collapse
OTA Rootkeeper should work but since its not, try this (courtesy rootkindlefire.com/kindle-fire-unroot/how-to-unroot-kindle-fire/)
Code:
adb shell
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
rm /system/app/Superuser.apk
rm /system/xbin/su
reboot
after your Kindle restarts you won't have root and Amazon Video should work just fine.
Hello,
I have successfully rooted my device with the above instructions. While installing the Android market I was abusing of my root privileges and I've successfully "burned" my device. That is, the Kindle won't start up anymore (it stays forever in the initial phase showing the kindleFire logo).
I don't know where else to turn for help so I'm writing about this here. If anyone has hints of how I could recover my kindle from the void, please let me know
Cheers
http://forum.xda-developers.com/showthread.php?t=1356257
Yesssssssssss
Yesssssssssssssssssss. So nice to have root again. My Titanium Backup and SUFBS works again
I had ADB and SDK working when I had my Glacier, but since I have gotten my SGS2, and my Kindle, Android SDK Manager will not open... It just opens a command prompt, and then closes.. I have reinstalled both the SDK Manager and the Java Kit... Any ideas?
EDIT:
I must have messed with something in my system settings somewhere to corrupt a bunch of stuff... I did a system restore to the 18th of December, reinstalled, and everything works perfect now... Oh well! Haha
Hey, I used a combo of the link JCase gave me when I had questions, this guide, and the links off the rootzwiki guide and managed to get it first try. It was actually easier than I thought it was going to be. I've never rooted anything before, I didn't even have ADB or the SDK until tonight. The process (while using both guides and video tut) went smoothly without a hitch. I just finished installing the Android Market but have to wait til morning to access it, as I have no WiFi at home, and its too late for me to be driving to a hotspot. Thank you very much. You(JCase) and your comrades who put this all together f**king rule.
a really clear and easy guide ! - congratulations - you shoud try to let it pin on top !
Ectoplasmic said:
NOTE 2: I've seen a lot of comments suggesting the driver install in Vashypooh's app doesn't work at this point.
Click to expand...
Click to collapse
the reason people have problems with vashipooh's driver installation seems to be the old drivers - they don't manage to clean up the old drivers:
disconnect KF
Open an (elevated for win7) command prompt:
set devmgr_show_nonpresent_devices=1
devmgmt.msc
device manager opens - click "view" - click "show hidden devices"
now you see all devices ever connected/installed
uninstall all devices regarding "kindle" and "android (composite) adb device"
connect KF - will startup by itself
select the most recent driver (that you have installed before by install_driver.bat from KFU) manually (check date/time)
now you should be set up with a good driver installation
btw. i'm on xp - it's working for xp and 7, 32 and 64 bit
just tried this from a cm7 thread on the stock rom (6.2.1)
http://forum.xda-developers.com/showpost.php?p=20495152&postcount=290
edit the file /system/lib/egl/egl.cfg (open it on text editor)
original is this:
0 0 android
0 1 POWERVR_SGX540_120
So just remove the first line, that it looks like :
0 1 POWERVR_SGX540_120
made a backup copy first, just to be shure
validated with "quadrant standard" - the scene with the planet and the moon
fps from 10 to 54 - and now without artefacts
tested some apps - no issues so far
perhaps it helps some gamers ...
added benchmark on request:
b63 said:
just tried this from a cm7 thread on the stock rom (6.2.1)
http://forum.xda-developers.com/showpost.php?p=20495152&postcount=290
validated with "quadrant standard" - the scene with the planet and the moon
fps from 10 to 54 - and now without artefacts
tested some apps - no issues so far
perhaps it helps some gamers ...
Click to expand...
Click to collapse
hmm. interesting
could you post some benchmark results ?
The same thing happens to me. When using the stock Rom you get around 10 fps. But when using another Rom its anywhere from 50-60 on that quadrant standard test.
mine says
0 0 android
0 1 POWERVR_SGX540_120
So just remove 0 0 android and change it to
0 0 POWERVR_SGX540_120
?
original is this:
0 0 android
0 1 POWERVR_SGX540_120
So just remove the first line, that it looks like :
0 1 POWERVR_SGX540_120
made a backup copy first, just to be shure
still working - no issues
yea i did it, no issues so far either. maybe a few times i feel like its actually faster in some games
Pretty simple change.
I did this on a stock 6.2.1 rooted KF...
Before the change, there were wierd artifacts on the moon as it went around the world in that test. After the change, that was not there and everything seemed smoother.
Both test results are below:
Before Change:
After:
Guys, where is this file located (directory wise)? I can't find it.
Thats funny, it was in one of the posting above.. seems someone updated their post and removed it.
Code:
/system/lib/egl/egl.cfg
Actually it is in the first post.
krelvinaz said:
Thats funny, it was in one of the posting above.. seems someone updated their post and removed it.
Code:
/system/lib/egl/egl.cfg
Actually it is in the first post.
Click to expand...
Click to collapse
Thank you!
EDIT -
Oh man, just tried this and it messed up my Kindle Fire. I'm on 6.2.1 and I just get a black screen now. The only thing visible is the top part of the UI (the part where it says "My Kindle, the Time, Options/Wifi/Battery).
you've messed up your egl.cfg - correct or use the backup you've made (hopefully) with adb.
in case you don't have:
@b63
Thanks for the file but I backed up my egl.cfg file (renamed egl.cfg.bak) before I did anything (one backup is on my desktop PC, the other is on the Kindle itself in the /sdcard/download folder).
The question is how do I replace the one I messed up in /system/lib/egl with the backup?
This is how I came to be in this predicament : I downloaded the original egl.cfg file to my desktop pc, edited it, saved it, and reuploaded to my Kindle and placed it in the /system/lib/egl folder, then I restarted my Kindle. When it booted up, there's nothing on screen except the [My Kindle Time Options/Wifi/] up top.
to copy to computer and edit/write back ist is very likely that you make a failure in editing or with the permissions.
it's better to use "es file explorer" or "root explorer" on the KF
gimme some information that i know which options you have available
your rooted - assume yes, since you coldn't do the change
do you have adb available on your computer and the right drivers installed ?
if not:
download the newest KFU (.9.1) and run install_drivers.bat
http://forum.xda-developers.com/showthread.php?t=1399889
turn off usb mass storage mode: tap on the kf screen disconnect - but let it plugged
open a command prompt and cd to the tools folder (Kindle Fire Utility\tools)
there you should have the adb command availabe - you can test it with "adb devices" - you should get a device id back
then do the following commands:
adb shell
cp /sdcard/download/egl.cfg.bak /system/lib/egl/egl.cfg
chmod 0666 /system/lib/egl/egl.cfg
b63 said:
to copy to computer and edit/write back ist is very likely that you make a failure in editing or with the permissions.
it's better to use "es file explorer" or "root explorer" on the KF
Click to expand...
Click to collapse
Yeah, I didn't edit the permissions when I copied it back from the PC. I think that's what can be causing this.
your rooted - assume yes, since you coldn't do the change
Click to expand...
Click to collapse
Yes, it was rooted using JCase method, http://forum.xda-developers.com/showthread.php?t=1409078. I was running 6.2.1 and root was confirmed using Root Checker (I even installed Android Market on it).
do you have adb available on your computer and the right drivers installed ?
Click to expand...
Click to collapse
Yes, before I updated to 6.2.1, I used Superoneclick method : http://forum.xda-developers.com/showthread.php?t=1348830 , to root my 6.2 Kindle Fire.
turn off usb mass storage mode: tap on the kf screen disconnect - but let it plugged
open a command prompt and cd to the tools folder (Kindle Fire Utility\tools)
there you should have the adb command availabe - you can test it with "adb devices" - you should get a device id back
then do the following commands:
adb shell
cp /sdcard/download/egl.cfg.bak /system/lib/egl/egl.cfg
chmod 0666 /system/lib/egl/egl.cfg
Click to expand...
Click to collapse
I get an error message saying I'm unable to do this because directory is read-only.
I ve heard that messing with egl.cfg might cause video playback problems for example youtube application
Can anyone confirm that ?
zirooo said:
I ve heard that messing with egl.cfg might cause video playback problems for example youtube application
Can anyone confirm that ?
Click to expand...
Click to collapse
no - youtube and all other stuff is working fine
the patch only affects 3d gl graphics
zirooo said:
I ve heard that messing with egl.cfg might cause video playback problems for example youtube application
Can anyone confirm that ?
Click to expand...
Click to collapse
Video playback seems good to me.
zopzop25 said:
I get an error message saying I'm unable to do this because directory is read-only.
Click to expand...
Click to collapse
do you get an device from "adb devices" ?
if yes:
type adb shell - your adb prompt is $ - type su and enter - does the prompt change to # ?
if yes:
do the rest of the commands
b63 said:
do you get an device from "adb devices" ?
if yes:
Click to expand...
Click to collapse
Yes :
List of devices attached
4332000600000001 device
type adb shell - your adb prompt is $ - type su and enter - does the prompt change to # ?
Click to expand...
Click to collapse
Yes, it changes from $ to #
if yes:
do the rest of the commands
Click to expand...
Click to collapse
Same message, that it's Read-Only.
ok - your on the # prompt
if you issue:
cp /sdcard/download/egl.cfg.bak /system/lib/egl/egl.cfg
then you get that it's read only ?
lets test something:
at the # prompt try to cd to /system/lib/egl/
and make a ls -l to see the permissions on your egl.cfg
they should be "-rw-rw-rw-" -> ok yours are not otherwise you would have not a black screen
but what are yours ?
does "chown root:root /system/lib/egl/egl.cfg" say the same ?
Hey Guys,
i hope my english is ok and you can unterstand all what i mean.
I have a Kindle Fire HD Software version 7.2.3
i try to root my Kindle, fot the root i use this Method:
http://forum.xda-developers.com/showthread.php?t=1886460
Root_with_Restore_by_Bin4ry_v17 in the cmd.exe i got and error "permission denied"
then i use QemuRoot.bat and step 2 the same error "permission denied"
Driver installed and work correctly.
Kindel settings are correct.
maybe their have an idea.
I uploaded some pictures of the error in a few minutes.
CMD returned error "permission denied"
HarldOOOandSon said:
Hey Guys,
i hope my english is ok and you can unterstand all what i mean.
I have a Kindle Fire HD Software version 7.2.3
i try to root my Kindle, fot the root i use this Method:
http://forum.xda-developers.com/showthread.php?t=1886460
Root_with_Restore_by_Bin4ry_v17 in the cmd.exe i got and error "permission denied"
then i use QemuRoot.bat and step 2 the same error "permission denied"
Driver installed and work correctly.
Kindel settings are correct.
maybe their have an idea.
I uploaded some pictures of the error in a few minutes.
Click to expand...
Click to collapse
If I understand correctly, you try to execute the batch files to Root the Kindle Fire 7" HD: RunMe.bat (Step 1) or QemuRoot.bat (Step 2), Microsoft Windows returns an error Permission Denied or Access Denied. I suspect you are using Windows 7, correct? Try to Right Hand Mouse Click on then CMD.EXE Shortcut and choose "Run As Administrator".
prokennexusa said:
If I understand correctly, you try to execute the batch files to Root the Kindle Fire 7" HD: RunMe.bat (Step 1) or QemuRoot.bat (Step 2), Microsoft Windows returns an error Permission Denied or Access Denied. I suspect you are using Windows 7, correct? Try to Right Hand Mouse Click on then CMD.EXE Shortcut and choose "Run As Administrator".
Click to expand...
Click to collapse
I try it and choose Run As Administrator but the same error.
Here the Line i file in:
echo 'ro.kernel.qemu=1' > /data/local.prop then the error "permission denied"
"[email protected]:/ $ rm -r /data/local/tmp
rm -r /data/local/tmp
rm failed for /data/local/tmp, Permission denied"
Mhhh anybody a Idea?
Driver correct install, install Android SDK Packages (SDK Tools + Plattorm Tools installed, and google Driver), and Java too.
HarldOOOandSon said:
I try it and choose Run As Administrator but the same error.
Here the Line i file in:
echo 'ro.kernel.qemu=1' > /data/local.prop then the error "permission denied"
"[email protected]:/ $ rm -r /data/local/tmp
rm -r /data/local/tmp
rm failed for /data/local/tmp, Permission denied"
Mhhh anybody a Idea?
Driver correct install, install Android SDK Packages (SDK Tools + Plattorm Tools installed, and google Driver), and Java too.
Click to expand...
Click to collapse
I have the same exactly issue and I do run the .exe as administrator.... i don´t know whats going on....
HarldOOOandSon said:
I try it and choose Run As Administrator but the same error.
Here the Line i file in:
echo 'ro.kernel.qemu=1' > /data/local.prop then the error "permission denied"
"[email protected]:/ $ rm -r /data/local/tmp
rm -r /data/local/tmp
rm failed for /data/local/tmp, Permission denied"
Mhhh anybody a Idea?
Driver correct install, install Android SDK Packages (SDK Tools + Plattorm Tools installed, and google Driver), and Java too.
Click to expand...
Click to collapse
Had the same problem. DL my package and see if you have any better luck:
http://www.mediafire.com/?t570mx55pqw5ezw
Or here are my instructions anyways:
Instructions:
1. Install/update Java from "chromeinstall-7u10.exe"
2. Install Kindle Fire ADB Drivers with "Kindle Fire ADB drivers.exe"
3. Place your Kindle fire in ADB mode (Settings->Security->Enable ADB->On) and connect your device by USB.
4. In the "Root_with_Restore_by_Bin4ry_v18" folder run "RunMe.bat"
5. Use Option one and follow the on-screen instructions
6. In the "QemuRoot_v1.0" folder, run "RootQemu.bat"
7. Follow the onscreen instructions.
8. You should be greeted with a success prompt.
*NOTE*
This method has gotten me farther and actually installs Superuser.apk, which I can open using ES File Explorer.
HOWEVER, Root still apparently doesn't work for me.
bigtimer5 said:
Had the same problem. DL my package and see if you have any better luck:
Or here are my instructions anyways:
Instructions:
1. Install/update Java from "chromeinstall-7u10.exe"
2. Install Kindle Fire ADB Drivers with "Kindle Fire ADB drivers.exe"
3. Place your Kindle fire in ADB mode (Settings->Security->Enable ADB->On) and connect your device by USB.
4. In the "Root_with_Restore_by_Bin4ry_v18" folder run "RunMe.bat"
5. Use Option one and follow the on-screen instructions
6. In the "QemuRoot_v1.0" folder, run "RootQemu.bat"
7. Follow the onscreen instructions.
8. You should be greeted with a success prompt.
*NOTE*
This method has gotten me farther and actually installs Superuser.apk, which I can open using ES File Explorer.
HOWEVER, Root still apparently doesn't work for me.
Click to expand...
Click to collapse
Still doesn´t work for me, the RunMe.Bat did finish the process but, the RooQuemu.Bat keeps teelling that in the 2nd step the prompting the access in denied
jose87413 said:
Still doesn´t work for me, the RunMe.Bat did finish the process but, the RooQuemu.Bat keeps teelling that in the 2nd step the prompting the access in denied
Click to expand...
Click to collapse
Same thing here. Doesnt matter which tutorial I follow. I get a permission or operation denied on anything that I want to do on the Kindle Fire.
echo 'ro.kernel.qemu=1' > /data/local.prop then the error "permission denied"
HarldOOOandSon said:
I try it and choose Run As Administrator but the same error.
Here the Line i file in:
echo 'ro.kernel.qemu=1' > /data/local.prop then the error "permission denied"
"[email protected]:/ $ rm -r /data/local/tmp
rm -r /data/local/tmp
rm failed for /data/local/tmp, Permission denied"
Mhhh anybody a Idea?
Driver correct install, install Android SDK Packages (SDK Tools + Plattorm Tools installed, and google Driver), and Java too.
Click to expand...
Click to collapse
Run everything again, first updating these utilities to the latest versions - these links have an updated ADB Server and API's:
https://dl.dropbox.com/u/54456659/Qmenu.zip
https://dl.dropbox.com/u/54456659/Ro...Bin4ry_v17.zip
Then follow these instructions again (Ignoring the links below):
Root Step 1: Run Root MANY ANDROID! http://forum.xda-developers.com/show....php?t=1886460. Run Normal Method and ignore errors. Pay attention, you will need to answer "Restore" a dialogue box on the Kindle. When the Kindle asks to be Restored, CLICK on it (this installs the binary files).
Root Step 2: The Kindle will reboot and react VERY slowly, this is normal - leave it alone. Proceed to Step 3.
Root Step 3: Run Qemu automated root http://forum.xda-developers.com/show....php?t=1893838. Let this utility complete to the end.
Root Step 4: Click on Superuser.apk under the Apps tab.
You now have Root.
prokennexusa said:
Run everything again, first updating these utilities to the latest versions - these links have an updated ADB Server and API's:
https://dl.dropbox.com/u/54456659/Qmenu.zip
https://dl.dropbox.com/u/54456659/Ro...Bin4ry_v17.zip
Then follow these instructions again (Ignoring the links below):
Root Step 1: Run Root MANY ANDROID! http://forum.xda-developers.com/show....php?t=1886460. Run Normal Method and ignore errors. Pay attention, you will need to answer "Restore" a dialogue box on the Kindle. When the Kindle asks to be Restored, CLICK on it (this installs the binary files).
Root Step 2: The Kindle will reboot and react VERY slowly, this is normal - leave it alone. Proceed to Step 3.
Root Step 3: Run Qemu automated root http://forum.xda-developers.com/show....php?t=1893838. Let this utility complete to the end.
Root Step 4: Click on Superuser.apk under the Apps tab.
You now have Root.
Click to expand...
Click to collapse
Thanks for the info (i'm having the same problem)
The 2nd download link does work (
Broken Link
Wilson157 said:
Thanks for the info (i'm having the same problem)
The 2nd download link does work (
Click to expand...
Click to collapse
2nd Download Link: Root_with_Restore_by_Bin4ry_v17.zip
thanks but no cigar
Thanks for the link.
I restored the kindle back to factory settings, followed your steps but i still get access denied on step 2 (exploiting) [local.prop]
(
Any help would be really really appreciated.
Step 1
Wilson157 said:
Thanks for the link.
I restored the kindle back to factory settings, followed your steps but i still get access denied on step 2 (exploiting) [local.prop]
(
Any help would be really really appreciated.
Click to expand...
Click to collapse
When you did Step 1, did you see Restore on the Kindle? Did you click on the Restore dialog and let the program reboot the Kindle? When the Kindle rebooted, was it running slow?
prokennexusa said:
When you did Step 1, did you see Restore on the Kindle? Did you click on the Restore dialog and let the program reboot the Kindle? When the Kindle rebooted, was it running slow?
Click to expand...
Click to collapse
Yes i saw the restore window. i did the restore, the kindle rebooted and the 1st root programe (by bin4ry) seemed to work fine, it told me i had root. When i ran the Qemu root kit it failed on step 2.
No the kindle didnt seem to run slow. it did the very 1st time i tried to root it after the 7.3.2 update, but since doing a factory reset, the kindle didnt run slow after rooting attempts.
if you get me rooted i will post you a very sexy picture of my ankle!
---------- Post added at 10:09 PM ---------- Previous post was at 10:01 PM ----------
Wilson157 said:
Yes i saw the restore window. i did the restore, the kindle rebooted and the 1st root programe (by bin4ry) seemed to work fine, it told me i had root. When i ran the Qemu root kit it failed on step 2.
No the kindle didnt seem to run slow. it did the very 1st time i tried to root it after the 7.3.2 update, but since doing a factory reset, the kindle didnt run slow after rooting attempts.
if you get me rooted i will post you a very sexy picture of my ankle!
Click to expand...
Click to collapse
actually i've tried running the 1st step...and the kindle DOES run really slow. sorry for the confusion
Wilson157 said:
Yes i saw the restore window. i did the restore, the kindle rebooted and the 1st root programe (by bin4ry) seemed to work fine, it told me i had root. When i ran the Qemu root kit it failed on step 2.
No the kindle didnt seem to run slow. it did the very 1st time i tried to root it after the 7.3.2 update, but since doing a factory reset, the kindle didnt run slow after rooting attempts.
if you get me rooted i will post you a very sexy picture of my ankle!
---------- Post added at 10:09 PM ---------- Previous post was at 10:01 PM ----------
actually i've tried running the 1st step...and the kindle DOES run really slow. sorry for the confusion
Click to expand...
Click to collapse
yea, just tried. no go. any other ideas?
Qemu ADB Update
Wilson157 said:
Yes i saw the restore window. i did the restore, the kindle rebooted and the 1st root programe (by bin4ry) seemed to work fine, it told me i had root. When i ran the Qemu root kit it failed on step 2.
No the kindle didnt seem to run slow. it did the very 1st time i tried to root it after the 7.3.2 update, but since doing a factory reset, the kindle didnt run slow after rooting attempts.
if you get me rooted i will post you a very sexy picture of my ankle!
---------- Post added at 10:09 PM ---------- Previous post was at 10:01 PM ----------
actually i've tried running the 1st step...and the kindle DOES run really slow. sorry for the confusion
Click to expand...
Click to collapse
After the first step, do not do anything to the Kindle, leave it alone after the reboot and proceed using the following updated Qemu program.
You may download the updated version here: https://dl.dropbox.com/u/54456659/Qmenu.zip
Extract to your desktop and run the RootQemu.bat file. Choose Option 1.
littleengin said:
yea, just tried. no go. any other ideas?
Click to expand...
Click to collapse
in the words of alan partridge....A HAAAA!
Solved the issue.....Instead of running the batch file as admin, i opened up 'CMD' as admin, then navigated (using command prompt) to the folder containing the root files and ran them.....it worked!!! it passed through step 2.
However....when i run es file explorer. i cannot access root
Initialize Superuser.apk
Wilson157 said:
in the words of alan partridge....A HAAAA!
Solved the issue.....Instead of running the batch file as admin, i opened up 'CMD' as admin, then navigated (using command prompt) to the folder containing the root files and ran them.....it worked!!! it passed through step 2.
However....when i run es file explorer. i cannot access root
Click to expand...
Click to collapse
Ahhh, almost there. This is a bug in Superuser.apk - go into your Apps folder, you will see Superuser, click on it. It will open, now go to File Explorer, see if you can run as Root. I prefer Root Explorer.
Wilson157 said:
in the words of alan partridge....A HAAAA!
Solved the issue.....Instead of running the batch file as admin, i opened up 'CMD' as admin, then navigated (using command prompt) to the folder containing the root files and ran them.....it worked!!! it passed through step 2.
However....when i run es file explorer. i cannot access root
Click to expand...
Click to collapse
sorry my bad! Es file explorer was set to access root. Now i can access it. Thank you thank you thank you
I would post a picture of my ankle but the mods might class it as porn
Root and Google Play for Amazon 7" Kindle Fire HD Software Version 7.2.3
Since this thread had seen a lot of changes over the last couple of weeks, I decided it was time to consolidate everything again, so here it is the consolidated and updated link version as of 12/23/2012:
The problem "Device not Found" is usually driver related or ADB Security issue. I assume you have ADB enabled under Security - Enable ADB? Also enable "Allow Installation of Applications" under the Device tab - this will allow installation of Google Play applications. If all OK, move onto the next step.
Next, as per the Qemu thread noted here http://forum.xda-developers.com/show....php?t=1893838 you will find a driver package named "Kindle_Fire_HD_ADB_Drivers.zip", be sure to install the ADB driver package. Reboot the PC and next the Kindle.
As you noted, if you want to use Google Play, you must Root the device. Just to keep everything consolidated, I will give you a brief Rooting instructions which works for Software 7.2.2 and 7.2.3.
Download Root MANY ANDROID! to your desktop. Extract to your desktop.
Download Qemu automated root to your desktop. Extract to your desktop.
NOTE WINDOWS 7 USERS: You need to open a command prompt "as Administrator" when running the batch files RunMe.bat and RootQemu.bat - otherwise Windows will respond with "Permission Denied".
Root Step 1: Run RunMe.bat from Root MANY ANDROID! http://forum.xda-developers.com/show....php?t=1886460. Choose option 1 Run Normal Method and ignore errors. Pay attention, you will need to answer "Restore" a dialogue box on the Kindle. Click on Restore. When the program has completed, the Kindle will Reboot.
Root Step 2: When the Kindle reboots it will react VERY slowly, this is normal - leave it alone. Proceed to Step 3.
Root Step 3: Run RootQemu.bat from Qemu automated root http://forum.xda-developers.com/show....php?t=1893838. Follow the instructions Step-by-Step allowing Windows to re-detect the Kindle between reboots (about 2 minutes). Let this utility complete to the end.
Root Step 4: Click on Superuser.apk under the Apps tab.
You should now have root AND if this is true your ADB communication is also functional. Finally to Google Play.
Play Step 1 Move GoogleServicesFramework.apk, AccountAndSyncSettings.apk and GoogleLoginService.apk to /system/app. Using Root explorer app on the Fire (be sure it has Superuser Permissions). Change permissions on both to Owner: Read-Write, Group: Read and Others: Read. Install GoogleServicesFramework.apk, AccountAndSyncSettings.apk and GoogleLoginService.apk
Play Step 2 Reboot the Kindle
Play Step 3 Download Vending.apk
Play Step 4 Using Root explorer app on the Fire (be sure it has Superuser Permissions). Move Vending.apk to /system/app with permissions set to Owner: Read-Write, Group: Read and Others: Read.
Play Step 5 Install Vending.apk
Play Step 6 Google Play should show up in your Kindle Fire HD Apps. Tap on it and follow the steps.
Play Step 7 Download and install the Gplay3.8.17.apk to upgrade the the android market to the current Google Play market.
Play Step 8 Download google_apps - unzip to /sdcard/download
Play Step 9 Install Google Apps as needed. There is no need to move any of the apps to /system/app, just perform a normal apk install by using Root Explorer to install these apps.
I have also attached copies of these noted files to this thread.
Also, I have organized a few Google Apps & Services then zipped them into a folder you may download here: Google Apps. I have used all these Apps on my Kindle 7" HD successfully.
If you would like to disable the Amazon OTA Updates, delete or move /system/ect/security/otacerts.zip to /sdcard/download - Reboot the Kindle.
Finally, to eliminate Amazon from intercepting any Market requests, thus allowing Google Play to be the default Market move /system/app/MarketIntentProxy.apk to /sdcard/download - Reboot the Kindle
I'm also trying to do what previous users have been doing in this thread: running Rootqemu.bat but I still get permission denied on the second step. I've tried navigating to the folder using an administrator command prompt and running it through cmd, still fails on the second step with permission denied:
/system/bin/sh: cannot create /data/local.prop: Permission denied.
Have no idea where to go from here any help would be appreciated.
THANKS TO JORDAN011 FOR SOME OF THIS INFO. i tried the origional post but got confused with some of the bits esspeciaolly as i didnt find mention of installing Java which was a big stumbling block so i did more tial and error and research and Rooted my Kindle - heres what i did with links: hope it helps (sorry pics didnt come out and niether did the highlighted instructions but short of time and have to popout -- follow it word for word and it will definately work
1. Turn your Kindle Fire on and swipe down the top bar and tap on More+
2. Goto device and turn on the “allow installation of applications” button (ontop of the reset factory defaults)
3. Go back and then goto Security and turn on the “enable ADB” button
4. On your PC Figure out if you have 32 bit or 64 bit windows running and download the correct versions of java and android sdk below:
5. Download and install Java se7u11 the JDK file. From http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html. This is needed for the android SDK to work (otherwise ADB wont work). You may have to register and reboot
6. Download android SDK then extract the folder to your desktop and install the (green icon). download from https://developer.android.com/sdk/index.html
7. If you have installed java and the android sdk – you should get the following screen:
8. If SDK manager asks you to install any missing packages (button on bottom right corner) then install them/accept and install
9. Download then extract to desktop and install the Kindle fire ADB Drivers (don’t worry if there’s an error message – Just install Anyway as its an unsigned file. Download from http://forum.xda-developers.com/showthread.php?t=1893838
10. Open up device manager ie start/control panel/hardware and sound/devices and printers/device manager
11. Turn on your kindle and plug it into the PC
12. Your kindle should be recognised in device manager as Andriod composite adb interface.
13. Download Bin4rysroot from here http://uploaded.net/file/0fpyh5c5
14. download Quemu root from here http://forum.xda-developers.com/showthread.php?t=1893838
15. Extract both the above files to your C Drive into two new folders and rename the folders Qemu (for quemuroot contents) and Root (forbin4ryroot contents)
16. THE ROOTING PART NOW!!
17. On the Pc goto Start and type in CMD then right click on the CMD icon at the top of the window and select “Run as Administrator” and hit yes if the User Account Control window pops up and a dos window will appear
18. Copy and past (or type this into the window) cd ..\..\Root then hit enter
19. Copy and past (or type this into the window) runme.bat then hit enter
20. When the screen shows an interface, type 1 then hit enter, A lot of errors will show up but that's fine
21. When your kindle shows a "Restore" screen hit restore my data your kindle will restore and reboot (may take some time be patient!)
22. After it finishes out you should get a command line on the pc saying “press any key to continue” when you do that you will see C:|\Root>
23. Copy and past (or type this into the window) cd ..\Qemu then hit enter
24. Copy and past (or type this into the window) rootqemu.bat then hit enter
25. When you get another interface type 1, then hit enter, press enter twice until it starts the steps.
26. It'll restart your kindle a couple times make sure you don't press enter until it has booted up again whenever it prompts you to (ie wait 3 mins before pressing enter) your Now rooted – you don’t have to press any key on the pc now.
27. If you want proof, you can download Es File explorer and in the apps settings goto root settings grant it Root permissions in the settings by ticking root explorer boxe and clicking yes and grant for both
:good: thank for sharing..wil try root my kindle fire...cheerzz
Thought this was great, could finally get my mum's Kindle rooted and put Play Store on it....... Then found that it says I've reached my download limit and that I need to register and pay...
Back to the drawing board.
patel989 said:
THANKS TO JORDAN011 FOR SOME OF THIS INFO. i tried the origional post but got confused with some of the bits esspeciaolly as i didnt find mention of installing Java which was a big stumbling block so i did more tial and error and research and Rooted my Kindle - heres what i did with links: hope it helps (sorry pics didnt come out and niether did the highlighted instructions but short of time and have to popout -- follow it word for word and it will definately work
1. Turn your Kindle Fire on and swipe down the top bar and tap on More+
2. Goto device and turn on the “allow installation of applications” button (ontop of the reset factory defaults)
3. Go back and then goto Security and turn on the “enable ADB” button
4. On your PC Figure out if you have 32 bit or 64 bit windows running and download the correct versions of java and android sdk below:
5. Download and install Java se7u11 the JDK file. From http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html. This is needed for the android SDK to work (otherwise ADB wont work). You may have to register and reboot
6. Download android SDK then extract the folder to your desktop and install the (green icon). download from https://developer.android.com/sdk/index.html
7. If you have installed java and the android sdk – you should get the following screen:
8. If SDK manager asks you to install any missing packages (button on bottom right corner) then install them/accept and install
9. Download then extract to desktop and install the Kindle fire ADB Drivers (don’t worry if there’s an error message – Just install Anyway as its an unsigned file. Download from http://forum.xda-developers.com/showthread.php?t=1893838
10. Open up device manager ie start/control panel/hardware and sound/devices and printers/device manager
11. Turn on your kindle and plug it into the PC
12. Your kindle should be recognised in device manager as Andriod composite adb interface.
13. Download Bin4rysroot from here http://uploaded.net/file/0fpyh5c5
14. download Quemu root from here http://forum.xda-developers.com/showthread.php?t=1893838
15. Extract both the above files to your C Drive into two new folders and rename the folders Qemu (for quemuroot contents) and Root (forbin4ryroot contents)
16. THE ROOTING PART NOW!!
17. On the Pc goto Start and type in CMD then right click on the CMD icon at the top of the window and select “Run as Administrator” and hit yes if the User Account Control window pops up and a dos window will appear
18. Copy and past (or type this into the window) cd ..\..\Root then hit enter
19. Copy and past (or type this into the window) runme.bat then hit enter
20. When the screen shows an interface, type 1 then hit enter, A lot of errors will show up but that's fine
21. When your kindle shows a "Restore" screen hit restore my data your kindle will restore and reboot (may take some time be patient!)
22. After it finishes out you should get a command line on the pc saying “press any key to continue” when you do that you will see C:|\Root>
23. Copy and past (or type this into the window) cd ..\Qemu then hit enter
24. Copy and past (or type this into the window) rootqemu.bat then hit enter
25. When you get another interface type 1, then hit enter, press enter twice until it starts the steps.
26. It'll restart your kindle a couple times make sure you don't press enter until it has booted up again whenever it prompts you to (ie wait 3 mins before pressing enter) your Now rooted – you don’t have to press any key on the pc now.
27. If you want proof, you can download Es File explorer and in the apps settings goto root settings grant it Root permissions in the settings by ticking root explorer boxe and clicking yes and grant for both
Click to expand...
Click to collapse
I get to step #2 in the script
Step 2 - Exploiting...
/system/bin/sh: cannot create /data/local.prop: Permission denied
My kindle is 10.2.6_user_2630020
What else can be done?
Thank you.
snoopdujour said:
I get to step #2 in the script
Step 2 - Exploiting...
/system/bin/sh: cannot create /data/local.prop: Permission denied
My kindle is 10.2.6_user_2630020
What else can be done?
Thank you.
Click to expand...
Click to collapse
This happened to me. And I googled extensively about the problem. Honestly.. the only thing to do is keep running the script.. worked for me after about 20 tries. Sorry I couldn't be of more help.
snoopdujour said:
I get to step #2 in the script
Step 2 - Exploiting...
/system/bin/sh: cannot create /data/local.prop: Permission denied
My kindle is 10.2.6_user_2630020
What else can be done?
Thank you.
Click to expand...
Click to collapse
Nothing. It's normal and doesn't mean anything. Root still works even with the error
--
Sent from my Kindle Fire 2, CM 10.1
Rooting Kindle Fire 10.2.6
I was able to get my Kindle Fire .v2 rooted. I ran through the process again. This time going back to the beginning.
I wasn't able to get it to run, so I refreshed the files, and ran it again. It took 2 attempts to get the first script to run. I thought it didn't run, so I was searching for a reason why. Then I looked up, and the script had finished. Then it took 3 times for the second part of the script to complete.
After getting the the launcher I wanted installed (APEX failed, so did Novo and a few others) AWD worked, but I was unable to get it to be the default launcher. (the kindle launchers 'default' settings were grayed out.
I then went into /system/app and renamed Launcher.apk to Launcher Default.apk and the com.awd.launcher-1.apk to Launcher.apk.
the system didn't respond when I pressed the home key, so I took a chance and rebooted my kindle.
When it rebooted, I was asked which launcher I wanted to use, so I clicked set as default, and clicked on AWD.
All is good now. Thanks
help
i keep getting a runme.bat is not recognized as a internal or external command , operable program or batch file
when i select 1 and hit enter i'm not getting the restore screen on the kindle it just says that it couldnt' push busybox and superuser and then it asks me wich superuser i want too install 1 or 2 and when i select one it just goes back too prompt. any ideas drivers are all good adb good cant figure it out
hey did u ever get help with that
blythefam5 said:
i keep getting a runme.bat is not recognized as a internal or external command , operable program or batch file
Click to expand...
Click to collapse
hey did u ever get help with that
Work for 10.4.6?!?
Does this work on 10.4.6 at all? My kindle is running this software atm
Thanks
Lewiswatson99 said:
Does this work on 10.4.6 at all? My kindle is running this software atm
Thanks
Click to expand...
Click to collapse
Use step 1 http://forum.xda-developers.com/showthread.php?t=2075959
Hello everyone, need help
I've got Amazon Kindle Fire HD, the version is 10.2.6. Want to unlock it. I follow this instructions step by step, then i stumbled on the 18 step.
It says "Copy and past (or type this into the window) cd ..\..\Root then hit enter" I type everything as written and system says that it is not able to find the reqested path..( What should I do? Maybe I should type same exact address instead of ..\.. ? Thank you for your response in advance.:angel:
Vitaliy7 said:
I've got Amazon Kindle Fire HD, the version is 10.2.6. Want to unlock it. I follow this instructions step by step, then i stumbled on the 18 step.
It says "Copy and past (or type this into the window) cd ..\..\Root then hit enter" I type everything as written and system says that it is not able to find the reqested path..( What should I do? Maybe I should type same exact address instead of ..\.. ? Thank you for your response in advance.:angel:
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2075959