Related
I am about ready to give up. I tried the "root-android.org" oneclick and it continually fails. The technical support for the rooting software from root-android.org is not helping. I'm not sure that the oneclick method has ever worked on a Kindle Fire HD 7.2.3. I have downloaded SDK and the ADB as directed and kindle does show up on my devices (32 bit with Vista running) but various methods can't seem to connect to the Kindle from the PC. I really want to be able to do more with the Kindle and with some help I believe that it can be done. Any help from anyone would be greatly appreciated. I do have a Macbook Pro, but everything I have read indicates that you need to use a pc and not a mac.
http://forum.xda-developers.com/showthread.php?t=2069117
something got lost
Krsmqn said:
http://forum.xda-developers.com/showthread.php?t=2069117
Click to expand...
Click to collapse
When I first went to the thread I started to read about the rooting procedure. I went to eat dinner and afterwards the same informationa thread isn't there. The first one stated that with vista I should load some corrective software. It also talked about entering some CMD commands and then rebooting.
After dinner I don't get the same steps when I log on???????
Found an issue with browsers
chetek said:
When I first went to the thread I started to read about the rooting procedure. I went to eat dinner and afterwards the same informationa thread isn't there. The first one stated that with vista I should load some corrective software. It also talked about entering some CMD commands and then rebooting.
After dinner I don't get the same steps when I log on???????
Click to expand...
Click to collapse
When I am on the Mac I use Firefox and come up with one page for "http://forum.xda-developers.com/showthread.php?t=2069117" that shows on top the rating results and the process. When I am on the PC and go to "http://forum.xda-developers.com/showthread.php?t=2069117" I am using IE and I get a page that doesn't have the results for rating the process but rather its a page that let's you rate the process and has an entirely differnent bunch of discussions. Go figure...
say waaa?
chetek said:
When I first went to the thread I started to read about the rooting procedure. I went to eat dinner and afterwards the same informationa thread isn't there. The first one stated that with vista I should load some corrective software. It also talked about entering some CMD commands and then rebooting.
After dinner I don't get the same steps when I log on???????
Click to expand...
Click to collapse
I have no idea what you mean. The link I provided goes to the same thread every time.
It worked - rooted my Kindle Fire HD 7.2.3
Thank you so much for the assistance in completing the rooting of my Kindle Fire HD 7.2.3. I have so much admiration for all the developers that take the time to help newbie like myself when it comes to modifying these devices. So you know, the procedure was VERY easy to follow for this 67 year old man. Krsmgn, I am so grateful especially to you for getting me on the right track.:laugh::good:
The only issue I have now is getting Google play to work. I completed all the steps except the last one to keep Amazon from interfering when I want to go to the Google Play store. I still don't see anything in my apps for Google Play and wonder if I did something wrong along the way. I was able to use my phone Google Play store login and password when installing the software.
I also have a proble with ES File Explorer in that I can't get to the area called for in step 16 of the proceedure for getting the Amazon apk file moved to the download file.
chetek said:
Thank you so much for the assistance in completing the rooting of my Kindle Fire HD 7.2.3. I have so much admiration for all the developers that take the time to help newbie like myself when it comes to modifying these devices. So you know, the procedure was VERY easy to follow for this 67 year old man. Krsmgn, I am so grateful especially to you for getting me on the right track.:laugh::good:
The only issue I have now is getting Google play to work. I completed all the steps except the last one to keep Amazon from interfering when I want to go to the Google Play store. I still don't see anything in my apps for Google Play and wonder if I did something wrong along the way. I was able to use my phone Google Play store login and password when installing the software.
I also have a proble with ES File Explorer in that I can't get to the area called for in step 16 of the proceedure for getting the Amazon apk file moved to the download file.
Click to expand...
Click to collapse
Sir do you have an app anywhere called terminal emulator? If so go in there and type su and tell me what it says? (Verifying that you have root) after that I may be able to help walk you through the process
Or....
Open ES File Explorer, open settings and choose root settings (down near the bottom) make sure all the boxes are checked. Then you should be able to access /system/.
As for Google Play, go here.
Krsmqn said:
Open ES File Explorer, open settings and choose root settings (down near the bottom) make sure all the boxes are checked. Then you should be able to access /system/.
As for Google Play, go here.
Click to expand...
Click to collapse
Haha probably a lot simpler to do his method. Also if you have a super user app open it and set it to auto grant permissions. Had an issue myself where it wouldn't show the prompt
Market stops
Fianlly see Google Play in the apps. I rechecked all the steps and found that I cannot move Vending.apk to /System/app. The failure indicates that the file cannot be moved from /sdcard/Download to /System/app.
I also can't figure out how to "ES File Explorer or Root Explorer, change permissions set to Owner: Read-Write, Group: Read and Others: Read". Is the procedure talking about tyhe Vending.apk file?
STOP - I was able to move the file (Vending.apk), rebooted the Kindle and now I can go to Google Play where it shows my already purchased apps for my mobile phone. It indicates that two of the phone apps are starting to download but that's it. Seems like it can't really download. The files are continually stating that they are "starting download".
chetek said:
Fianlly see Google Play in the apps. I rechecked all the steps and found that I cannot move Vending.apk to /System/app. The failure indicates that the file cannot be moved from /sdcard/Download to /System/app.
I also can't figure out how to "ES File Explorer or Root Explorer, change permissions set to Owner: Read-Write, Group: Read and Others: Read". Is the procedure talking about tyhe Vending.apk file?
STOP - I was able to move the file (Vending.apk), rebooted the Kindle and now I can go to Google Play where it shows my already purchased apps for my mobile phone. It indicates that two of the phone apps are starting to download but that's it. Seems like it can't really download. The files are continually stating that they are "starting download".
Click to expand...
Click to collapse
Look in the settings menu (pull down status bar and click more+), find Applications, click, find Installed Applications, click, look for "Appstore" and force stop, clear data. Reinstall vending apk. Reboot.
Google play icon keeps disappearing from apps
Krsmqn said:
Look in the settings menu (pull down status bar and click more+), find Applications, click, find Installed Applications, click, look for "Appstore" and force stop, clear data. Reinstall vending apk. Reboot.
Click to expand...
Click to collapse
Seems like I am there but not quite there. In apps I lose the Google Play icon yet I keep the market icon. I tried downloading a live wallpaper that I have on my phone but it stops. Wallpapers can't be set. Am I missing something?
Refresh
chetek said:
Seems like I am there but not quite there. In apps I lose the Google Play icon yet I keep the market icon. I tried downloading a live wallpaper that I have on my phone but it stops. Wallpapers can't be set. Am I missing something?
Click to expand...
Click to collapse
Seems like you got yourself in a weird spot. Rather then trying to find the needle in the haystack, it's sometimes easier to simply start over from scratch. What I mean is to remove all google stuff and reinstall. I mean everything "google" that wasn't on your kindle when you got it.
Then... Start over here.
Give it a try. I have been right where you are and this has worked for me. Nobody said it was going to be easy to make something do what it wasn't intended to do.
All is well that ends well
Thanks so very much for your patience and assistance. I have everything working on my Kindle and I owe it all to you. I even have the living wallpapers, seeing all the online videos I couldn't before, using ES file explorer I can look at everything from root down.
Many thanks to you and all the developers at XDA.:victory:
[ROOT] How To: Root the Kindle Fire 7" HD or 2 with Linux/MAC - Noob (Simple) Versio
chetek said:
I am about ready to give up. I tried the "root-android.org" oneclick and it continually fails. The technical support for the rooting software from root-android.org is not helping. I'm not sure that the oneclick method has ever worked on a Kindle Fire HD 7.2.3. I have downloaded SDK and the ADB as directed and kindle does show up on my devices (32 bit with Vista running) but various methods can't seem to connect to the Kindle from the PC. I really want to be able to do more with the Kindle and with some help I believe that it can be done. Any help from anyone would be greatly appreciated. I do have a Macbook Pro, but everything I have read indicates that you need to use a pc and not a mac.
Click to expand...
Click to collapse
chetek,
I am sorry to hear you are having trouble. The One-click Method does work on the Kindle Fire HD and 2 it is not preferred since there are many known Bugs with SuperOneClick. The first problem is the SDK, if you install the SDK and setup the environment variable correctly you will trigger Root MANY ANDROID and Qemu Root to fail since they already have a build in adb tool.
The problem with installing the SDK is several fold:
1. The SDK is over 500MB - The SDK is designed for Developers NOT End Users
2. There are only 2 programs used by the normal End User: adb.exe and fastboot.exe - they total less than 200KB
3. Qemu has its own adb.exe
4. SuperOneClick has its own adb.exe
5. Root MANY ANDROID! has its own adb.exe
So what happens is when SuperOneClick calls to it's internal adb.exe, this triggers the SDK adb.exe to start. They both use the same port so the are unable to communicate to the Kindle due to this port conflict. If adb.exe is lucky, it attempts to pull from it's own Root directory in an attempt to Push su ans Superuser.apk. Guess what? These files are not in the SDK directory so in the end, the utilities completely fail.
The solution? Remove the SDK, you will be able to Root the device in less than 5 minutes. Next you asked about Rooting the Kindle with a Mac, yes this can be done and is preferred over Windows since the Kindle driver is built into Mac OS X, here is a link to the steps:
[ROOT] How To: Root the Kindle Fire 7" HD or 2 with Linux/MAC - Noob (Simple) Version
Finally, since you have Vista, please be sure to apply this fix prior to Rooting the Kindle:
[Bug Report] Attention Windows 7 and Vista Users - Noob (Simple) Version
So the final conclusions are:
1. Remove the SDK
2. Remove the SDK Path Statement if Inserted into PATH
3. Verify Driver is functioning
4. Apply the Fix
5. Use the Mac if Windows continues to fail
I also have problems rooting my kindle fire hd its running 7.2.3
I have tryed Mac os x and windows 7 no luck can someone help me out thanks
kindle fire hd
[ROOT][HOW TO] Root the Kindle Fire 7" HD and 2 with Windows - Noob (Simple) Version
Raymond199483 said:
I also have problems rooting my kindle fire hd its running 7.2.3
I have tryed Mac os x and windows 7 no luck can someone help me out thanks
kindle fire hd
Click to expand...
Click to collapse
Raymond199483,
First let's get you in a thread which we monitor closely - click on the link below:
[ROOT][HOW TO] Root the Kindle Fire 7" HD and 2 with Windows - Noob (Simple) Version
Please begin the operation per the instructions. Check the driver per the tutorial, then post us what you see in the Windows Device Manager. If everything appears OK, then proceed to the Rooting steps, please let us know what happens with the first two steps - do you see error? If yes, what do they say?
Once you give us additional information we will be able to get you Rooted.
Hey guys in this tutorial i will show you how to root the Samsung Galaxy Exhibit from Metro PCS, model SGH-T599N.
The phone comes Stock with Android Jelly Bean 4.1 Jelly Bean. This will also work on 4.1.2 Jelly Bean.
So lets get started.
There is a tutorial video at the bottom of the page
WARNING:
THIS WILL MOST LIKELY VOID YOUR WARRANTY.
YOU DO THIS AT YOUR OWN RISK, THERE IS A CHANCE YOU COULD BRICK YOUR PHONE.
What you will need:
1) A Samsung Galaxy Exhibit SGH-T599N
(To check your model number, go to Settings / About Device / Model Number)
2) A PC running Windows (XP, Vista, 7, 8 or 8.1)
3) A Usb Cable
4) Rooting program called VROOT
Step 1:
You need to download the VROOT rooting program.
https://www.dropbox.com/s/f85okpyc1u33zgt/Galaxy_Exhibit_Root.zip
Once the link is downloaded, extract the zip. You will get a .exe file called VRoot_1.7.3.4863_english_cid1005_7337ba1e_89.exe
Run the VRoot_1.7.3.4863_english_cid1005_7337ba1e_89.exe You will be greeted with the VROOT Setup Screen.
Click the Next button. You will be taken to the screen where you can chose where the installer, installs the program. You can chose a directory or use the default. Use the default.
Click the Next button. The next screen will ask you if you want the program to be put in your Start Menu, this is up to you.
Click the Next Button. The next the screen will ask if you want to place a Shortcut on your desktop, again this is up to you.
Click the Next Button. The program will now install it self. It should only take a couple of seconds. once the installer is done you will see the Setup Complete screen. Make sure the Launch VROOT box has a check in it and click the Finish Button.
The VROOT program will open. You will see a screen saying Device is connecting. After a moment the program will install daemon.
Step: 2
For the program to recognize you phone, you will need to turn on Usb Debugging on, on your phone. To do this on your phone go to Settings / Developers Options
Scroll down to the Debugging Section. Look for USB debugging and click on it.
A warning will pop up saying Allow USB debugging, select OK
After you turn on Usb Debugging a second warning should pop up on your phone asking if you wanna allow Usb debugging between your computer and phone. Check the always allow and then OK. Checking Always makes it so you do not have see that warning everything. Your computer and phone will allow debugging connect every time you connect in that mode.
Step 3
Now back on your PC you should see VROOT trying to connect to your phone. Once it connects you should see your phones model number on the screen. T599N
VROOT will now check to see if your phone already has root permission. VROOT will tell you, you do not have root.
The green root button in the bottom right corner should now be available. Press the Root button.
You will see the Rooting now screen. This should only take a moment to complete.
When VROOT is done, you will see a screen saying Success, your T599N is rooted. Rebooting.
You can now click complete, you are done with the VROOT program.
Step 4
You Exhibit will now reboot back into the Android OS
Once you are back at your home screen, open the app drawer in the bottom right hand corner to show all your phone apps. Scroll all the way to the right. You should now have two new apps installed on your phone. Superuser and one that is in Chinese. The one in Chinese was installed when VROOT told you it was installing daemon. You will no longer need that app.
The Superuser app is the one we want. This app regulates which app you grant root permission to. Just open the app. Make sure it does no tell you, you do not have root permission.
Now my suggestion here is to get a different app to do the same thing. The one you should use is SuperSU by Chainfire from the Play Store. Go to the Play Store and in the search look for SuperSU. There are 2 verions, a free one and a paid one. The free on works just fine.
Install this version. You will now have a app that looks like a Superman symbol with a # inside of it. Open the app. Make sure SuperSU does not tell you, you do not have root.
Now anytime a app requests root, a warning will pop up from SuperSU asking if you want to allow that app root access.
You have the option to Deny or Grant that app root. You can also check the Ask again box. If you check this box and Grant a app root, after some time SuperSU will pop up again asking the same thing. If you chose to Grant a app root without checking the box, that app will have full root access anytime you use it.
If you Deny it then the app will not have root access and not work the way it was ment to.
And that's it guys. You now have root access on your Metro PCS Samsung Galaxy Exhibit SGH-T599N
Video Tutorial
https://www.youtube.com/watch?v=SzUpbP55k30
Checkout my blogger page for these instructions with lots of pictures.
Checkout my Youtube page also
If this helped in any way please leave a comment of say thanks.
Can anybody here confirm that this method works? My mothers phone is in need of rooting and I want to make sure this won't brick her phone.
Same question
any verification this will work? Thanks in advance.
dadlovsyall said:
any verification this will work? Thanks in advance.
Click to expand...
Click to collapse
I can verify that this rooting method works. 100%. It's simple and easy to do. I'd recommend it.
Rooted my wifes t599n , metro pcs, stock rom. Worked perfect exept now i can't remove he chinese superuser app, i can disable, but new superuser will not install over it.
Never mind, got it.
sent from my lgms323 towelrooted waiting on cstom rom
brentwago said:
Rooted my wifes t599n , metro pcs, stock rom. Worked perfect exept now i can't remove he chinese superuser app, i can disable, but new superuser will not install over it.
Never mind, got it.
sent from my lgms323 towelrooted waiting on cstom rom
Click to expand...
Click to collapse
How did you get it?
jeankeeRD said:
How did you get it?
Click to expand...
Click to collapse
Found it in one of the cleaner apps on there, don't remember which one tho, sorry I went through like 6 of them that day.
sent from my lgms323 towelrooted waiting on custom rom
brentwago said:
Found it in one of the cleaner apps on there, don't remember which one tho, sorry I went through like 6 of them that day.
sent from my lgms323 towelrooted waiting on custom rom
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2843809
still working, EXE auto-updated, then i followed simple instructions, and the device rebooted with root.
vroot does install its own Super User Permission Management app, and a System Cleaner app (which are both actually useful), and some other junk (i uninstalled this). all their apps seem to have links to their other apps/appstore, but as long as you ignore them the apps themselves seem to be harmless enough.
Download the latest tools from the AFH link near end of post. It includes the changes in the attached "jobs" zip. You only need "jobs" if you downloaded the tools before May 11
EDIT May 29: Playstore is currently unreliable. Until updated, use the workaround here.
UPDATE May 17: Install Other Launcher and Install Kingroot tools may not complete if Windows username has spaces. I'll fix in next update. Until then, if your username has spaces, use this fix.
Here are tools for the 2014 Fire HD 6 and 7. A little late, I know, but some of you who still troll the forums may find them handy. Download the tools from AFH link, extract and run RUNME.bat.
IF YOU PLAN TO ROOT, TURN OFF WIFI NOW!
Tested working on OS 5.1.2.1 and below, except:
- Current Kingroot can't root 5.1.2.1. You need to downgrade. See "ROOT OS 5.1.2", below.
- OS 4: Only OTA blocking is implemented in the Block/Unblock jobs. [5/13/16 UPDATE: Also, Play Store isn't working on OS 4.
.. I probably won't fix it unless there's some demand. Try the video guide here. OS 4 users, also see post #11 for useful info about custom launchers.]
THE TOOLS
Install Play Store
Install Nova Launcher to /priv-app [root]
Install Other Launcher to /priv-app [root]
Uninstall priv-app Launchers [root]
Install Apps
Block/Unblock: OTA, ADS, AMAZON LAUNCHER, APPSTORE, AMAZON SEARCH [root]
Root Checker
Device Info
Root Tools
Install Kingroot ~ Root ~ Block OTA
Replace Kingroot with SuperSU [root]
DESCRIPTIONS
Before running a job, look here for any tips and instructions. This info is also in the readme.txt in the zip
INSTALL PLAY STORE - Like it says. Works on both rooted and unrooted OS 5. Not for OS 4. EDIT May 29: Playstore is currently unreliable. Until updated, use the workaround here.
INSTALL NOVA LAUNCHER - Installs Nova to /system/priv-app so widgets work. If you just rooted, make this your first custom launcher. You can replace it or add a different one later.
INSTALL OTHER LAUNCHER Installs the launcher app in user_launcher folder to priv-app. Get the apk for the launcher you want (from apkmirror.com for example) and put it into the folder and run the job. EDIT 5/16/2016: Filenames must end with ".apk" No spaces allowed; replace with "_". (The tool will find spaces and pause while while you fix.)
HOW TO INSTALL GOOGLE NOW (also in Readme.txt):
It's much easier to install Google Now if Amazon is blocked, and you need a custom launcher to do that.
1. If you don't have a custom launcher installed, use Install Nova tool (installs Nova and blocks Amazon)
If you have a custom launcher, block Amazon so your custom launcher is running.
2. Get Google Now (small) from apkmirror.com, e.g., put into user_launcher folder and run Install Other Launcher job.
You'll boot to your "other" launcher
3. Run Google Now in app drawer and:
If prompted to Update Google App (Get it from Google Play), do it.
If prompted that other launcher is default, tap link to go to Amazon Settings. In Apps & Games>Manage all Applications: Swipe to All, scroll to your other launcher, tap it and see if "Launch by Default" is on. If yes, Clear Defaults. If no, go to your launcher settings and see if you can turn off default there.
Some launchers don't give up their default easily. If pressing home key doesn't show "Select Home App" after doing the above, run Block/Unblock tool and switch to Amazon. Then block Amazon again. After restart, press home key and you'll get "Select Home App" and be able to choose Google Now.
UNINSTALL LAUNCHERS - Uninstalls and deletes everything associated with a launcher installed to /priv-app. If multiple, prompts you to choose the one to uninstall.
INSTALL APPS - Installs all the apps in the user_apps folder. Put the apks into the folder and run the job. Filenames must end with ".apk" No spaces allowed; replace with "_". (The tool will find spaces and pause while while you fix.) Don't install a launcher with this; use one of the launcher tools.
BLOCK/UNBLOCK - OTA, ADS, AMAZON LAUNCHER, APPSTORE, AMAZON SEARCH
Except for OTA, these work only on rooted OS 5. OTA does a soft block on unrooted OS 4, hard block on rooted.
OTA: Disables update packages and renames DeviceSoftwareOTA.apk for a "hard" block. Unblock reverses it.
ADS: Blocks/unblocks the lockscreen ads.
AMAZON LAUNCHER: Block disables the stock launcher (Amazon UI) and the Appstore, which forces the home key to use your custom launcher. Unblock switches you to Amazon. Checks for custom launcher before disabling Amazon. Black screen with multiple custom launchers: If you haven't set a default launcher, disabling Amazon will boot to black screen. (System doesn't know which launcher to use.) Press home key (circle at bottom) for launcher choices. TIP: To easily switch between your launcher and Amazon, use @bibikalka's guide here to set up "one-tap switching" from launcher home screen.
APPSTORE: Blocks the appstore so in-app links take you to the Play Store (instead of throwing that stupid Appstore prompt). Amazon complains bitterly if you run this from Amazon UI, so use it at your custom launcher or just use the Amazon launcher block.
AMAZON SEARCH: If you have Google Search installed, blocking Amazon Search makes your launcher search bar use Google instead of Amazon shopping.
DEVICE INFO - Just some specs that I find interesting. Lazy man's way to find out which tablet is plugged in, OS it's running, whether rooted . . .
INSTALL KINGROOT, ROOT, BLOCK OTA - Installs Kingroot, prompts you through rooting and blocks OTA updates.
- Installs kingroot v.4.8.5 by default.
- You can skip installation if Kingroot already installed
- You can install a later version if available: Check for new versions here: http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
ROOTING AND UPDATES: An update file can download while you're rooting. The Kingroot tool prevents it from installing as soon as you press Enter to tell the tool you're rooted. Then it looks for any downloaded file and if it finds one it tells you where it is and prompts you to delete.
Amazon says that updates install when the the device is not being used, but be aware that on OS 5 there's some risk. To minimize the risk, never leave the tablet idle while rooting. Just keep running Kingroot until root is successful and then press Enter to block installation of any download. (These instructions are in the tool.) To eliminate all risk, you can downgrade and root OS 4.5.3. On OS 4 the tool blocks update installation before rooting. (There's no way to do this on OS 5.) From OS 4.5.3, you upgrade with root in TWRP per bibikalka's root Tut.
True story: Kingroot once rebooted 5 times and told me "Root Failed" 3 times before finally succeeding. An update had downloaded to /cache, but the kingroot tool successfully blocked installation and found the file, which I deleted. So, although it's possible you could get upgraded, as long as you keep the tablet busy trying to root and then press Enter as soon as you're rooted, it's very unlikely.
REPLACE KINGROOT WITH SUPERSU - Installs W0lfDroid's sh script and prompts you through using it to replace Kingroot.
I reviewed and tested the script and it does (only) what it says: Removes all Kingroot (except Purify app, which tool uninstalls) and installs SuperSU. The tool uses SuperSU v. 2.4.6 for OS 5 (known working on OS 5.1.2) and SuperSU v. 2.4.9 for OS 4 (because 2.4.6 didn't seem to work).
FULL DISCLOSURE: I lost root one time after running this on OS 4. I think the problem was SuperSU 2.4.6 and that's why I changed it. I've tested many times and this only happened once, but you should know it happened. AFAIK W0lfDroid script is still the best free tool for the job.
ERRORS: Script was written to remove Kingroot from multiple android versions, so it tries to remove Kingroot files that don't exist on Lollipop. THIS PRODUCES LOTS OF ERRORS. THAT'S OK. I left in all commands so it will work on OS 4, too.
USE THIS SOON AFTER ROOTING. W0lfDroid's script should work fine even with root apps installed, but all I know for sure is it runs quick and easy on a "fresh" system.
ADB Sideload
There's an adb-sideload job in the jobs folder. I didn't put it on the menu because it uses commands that may not run on some systems. Also, if you know what you're doing, it's probably faster to manually sideload an update. If someone wants to try it, put the update bin file into adb_sideload folder and run sideload.bat.WINDOWS TESTING: Script was tested on English-language versions of Win 7 Pro and Home. Some testing on Win 10. (Thanks @SpaceBananas!) There's nothing that can hurt your tablet, but there may be kinks to work out based on Windows version. Hope a tester will work with me to help make the tools accessible to everyone. Thanks!
ADB DRIVERS REQUIRED: Try the guide in first link below. If problems, try the second.
Guide: http://forum.xda-developers.com/fir...ivers-fire-t3189000/post62561840#post62561840
Other options: http://forum.xda-developers.com/showpost.php?p=63072252&postcount=2
ROOT OS 5.1.2
IF YOU PLAN TO ROOT, TURN OFF WIFI NOW!
ROOT GUIDE: Follow this guide to use Kingroot and the root tools to set up your tablet.
At this time, Kingroot can only root OS 5.1.2 (February 2016) and below.
You can downgrade OS 5.1.2.1 (March 2016) to 5.1.2 and root, as explained in Root Guide, but this is an exception!
In general, never downgrade in order to use Kingroot. It's the fastest way to a brick!
You may be able to safely downgrade a higher OS to OS 4.5.3, root, and then upgrade in TWRP per @bibikalka's root Tut. Before trying this on an OS later than 5.1.2.1, make sure the tutorial says it's safe.
DOWNLOAD THE TOOLS FROM AFH ➔ . FireHD_TOOLS v 1.2
Update as of 5/11/16
➔ If you got the tools before the update, just replace the jobs folder in FIREHD_TOOLS with the one in attached "jobs_v1.x.zip"
Change Log
5/11/2016 - v1.2: Updated sideload.bat. (Missed the Find/Findstr fixes.)
5/10/2016 - v1.1: Fixed "No such file or directory" and "Permission denied" errors for users with *nix Find command installed
.
Nice Work!
@DoLooper - Magnum Opus, no less !
Why version 0.1 ??? The first release - solid 1.0 !!!
Updated. See OP.
Guys, I could use some feedback. Tools are getting downloaded a lot. Anybody using them? Are they helpful? Problems? Wishes? Anything? Thanks!
.
Updated again <sigh>. Sideload tool didn't get updated in v1.1. Apologies to those who downloaded the jobs zip.
DoLooper said:
Updated. See OP.
Guys, I could use some feedback. Tools are getting downloaded a lot. Anybody using them? Are they helpful? Problems? Wishes? Anything? Thanks!
.
Click to expand...
Click to collapse
Thanks DoLooper.
I tried these tools on my Fire HD 7 running 4.5.5.1 rooted with KingRoot.
I was able to use the script to successfully switch from KingRoot to SuperSU as well as to install Nova Launcher.
However, I had issues with the script elsewhere.
The play store seemed to install okay and it let me put in my google account info. After that, things went down hill. I was able to open the Play Store app without it crashing, but I just kept getting the "Error retrieving information from server. [RH-01]" message . I tried numerous things to correct this, but nothing seemed to work. In the end, I downgraded to 4.5.5, wiped data, cache and dalvik, and then flashed gapps via TWRP. This worked out, so all is good now.
I also had trouble with blocking the default launcher. Nova seemed to install okay, but the default launcher still worked and was a constant nag with each press of the home button. I fixed this by freezing the default launcher via Titanium Backup.
I don't know if these issues are particular to 4.5.5.1, or if I'm just unlucky. Regardless, I still appreciate your effort for putting this together. :good:
I'm currently trying to get wallpapers and widgets to work on the Nova launcher with no success. I tried the fixes intended for earlier Kindle models and (not surprisingly), they didn't work. Specifically, I tried Stunt's Wallpaper Fix and Kindlefree from the app store.
Any ideas where I should look for guidance on making Wallpapers and Widgets work?
Thanks again!
notorious.dds said:
Thanks DoLooper.
I tried these tools on my Fire HD 7 running 4.5.5.1 rooted with KingRoot.
I was able to use the script to successfully switch from KingRoot to SuperSU as well as to install Nova Launcher.
However, I had issues with the script elsewhere.
The play store seemed to install okay and it let me put in my google account info. After that, things went down hill. I was able to open the Play Store app without it crashing, but I just kept getting the "Error retrieving information from server. [RH-01]" message . I tried numerous things to correct this, but nothing seemed to work. In the end, I downgraded to 4.5.5, wiped data, cache and dalvik, and then flashed gapps via TWRP. This worked out, so all is good now.
I also had trouble with blocking the default launcher. Nova seemed to install okay, but the default launcher still worked and was a constant nag with each press of the home button. I fixed this by freezing the default launcher via Titanium Backup.
I don't know if these issues are particular to 4.5.5.1, or if I'm just unlucky. Regardless, I still appreciate your effort for putting this together. :good:
I'm currently trying to get wallpapers and widgets to work on the Nova launcher with no success. I tried the fixes intended for earlier Kindle models and (not surprisingly), they didn't work. Specifically, I tried Stunt's Wallpaper Fix and Kindlefree from the app store.
Any ideas where I should look for guidance on making Wallpapers and Widgets work?
Click to expand...
Click to collapse
Thanks for feedback. Tools apparently need work for OS 4.5.5.1. I tested pretty well on 4.5.3 and 4.5.5, but not 4.5.5.1. There may be some peculiarity there.
- The play store error has been reported on some 2015 Fires (using a different tool, but same method to install). It's unclear why it happens on some devices and not others, and they haven't found a fix, but it may be an OS 4 issue on the Fire HDs. I'll look into it.
- Nova & stock launchers: The block on stock launcher didn't work because it isn't implemented for OS 4. As mentioned at top of OP, only OTA block is available for OS 4. I'll need to add it in an update. Hadn't thought about need for it when using the Nova tool.
Would you please look in /system/priv-app folder and see if com.teslacoil.launcher.apk is at the bottom of directory? If so, are perms set to rw- r-- r--? Let me know and we'll proceed from there to get you widgets. Thanks.
DoLooper said:
Thanks for feedback. Tools apparently need work for OS 4.5.5.1. I tested pretty well on 4.5.3 and 4.5.5, but not 4.5.5.1. There may be some peculiarity there.
- The play store error has been reported on some 2015 Fires (using a different tool, but same method to install). It's unclear why it happens on some devices and not others, and they haven't found a fix, but it may be an OS 4 issue on the Fire HDs. I'll look into it.
- Nova & stock launchers: The block on stock launcher didn't work because it isn't implemented for OS 4. As mentioned at top of OP, only OTA block is available for OS 4. I'll need to add it in an update. Hadn't thought about need for it when using the Nova tool.
Would you please look in /system/priv-app folder and see if com.teslacoil.launcher.apk is at the bottom of directory? If so, are perms set to rw- r-- r--? Let me know and we'll proceed from there to get you widgets. Thanks.
Click to expand...
Click to collapse
Thanks for the help!
I found the com.teslacoilsw.launcher-1.apk file, but it's in my /data/app folder... and it is chmod'ed to 644.
Also, I did successfully install the AppWidgetPicker.apk and LiveWallpapersPicker.apk files to /system/app using the "kindlefree" app, but I think that about all the app did. These files are also chmod'ed to 644.
notorious.dds said:
Thanks for the help!
I found the com.teslacoilsw.launcher-1.apk file, but it's in my /data/app folder... and it is chmod'ed to 644.
Also, I did successfully install the AppWidgetPicker.apk and LiveWallpapersPicker.apk files to /system/app using the "kindlefree" app, but I think that about all the app did. These files are also chmod'ed to 644.
Click to expand...
Click to collapse
I've been using OS 5 for too long! Forgot you can't get wallpaper on OS 4 without fussing. It's unclear from your post: Did the pickers get wallpaper to work? This is the way we did it back when we always booted twrp and installed xposed: http://forum.xda-developers.com/fire-hd/general/how-to-wallpaper-custom-launcher-t3123009
As to widgets: What I meant is, you should have /system/priv-app/com.teslacoil.launcher_4.2.2.apk. Do you? I just retested this on 4.5.3. Nova (com.teslacoil.launcher_4.2.2.apk) got copied there and chmod'ed to 644 as it should and widgets are working fine.
No wallpaper is a bad problem, though, and no tool can fix it--unless that LiveWallpapersPicker DID work. Let me know. And let me know about /system/priv-app/com.teslacoil.launcher_4.2.2.apk.
BTW, how come you want to stay on OS 4?
DoLooper said:
I've been using OS 5 for too long! Forgot you can't get wallpaper on OS 4 without fussing. It's unclear from your post: Did the pickers get wallpaper to work?
Click to expand...
Click to collapse
Nope.
DoLooper said:
This is the way we did it back when we always booted twrp and installed xposed: http://forum.xda-developers.com/fire-hd/general/how-to-wallpaper-custom-launcher-t3123009
Click to expand...
Click to collapse
I think I tried that to no avail, but I can't remember exactly which module I used.
DoLooper said:
As to widgets: What I meant is, you should have /system/priv-app/com.teslacoil.launcher_4.2.2.apk. Do you? I just retested this on 4.5.3. Nova (com.teslacoil.launcher_4.2.2.apk) got copied there and chmod'ed to 644 as it should and widgets are working fine.
Click to expand...
Click to collapse
I think I ended up installing Nova via the app store so that's why it wasn't on the system partition. However, my widgets seemed to work when I checked again. I have no idea why they wouldn't work when I first tried them. I did end up creating two simple scripts via the "Scripter" app that would enable and disable the stock launcher. I put them as widgets on the nova desktop allowing for single click toggling of the stock launcher.
DoLooper said:
No wallpaper is a bad problem, though, and no tool can fix it--unless that LiveWallpapersPicker DID work. Let me know. And let me know about /system/priv-app/com.teslacoil.launcher_4.2.2.apk.
Click to expand...
Click to collapse
No, nothing seemed to fix the wallpaper... always black. Am understanding this correctly that the wallpaper works on this thing if I load Lollipop?
DoLooper said:
BTW, how come you want to stay on OS 4?
Click to expand...
Click to collapse
I didn't want to fiddle around with change the bootloaders every time I wanted into TWRP. At this point, it doesn't matter anyway... I hard bricked the device by flashing the 5.2.0 stock recovery last night
The post about using this to revert to stock should be edited or removed. It's bad.
The only reason I was trying to revert to stock was that I ended up getting into a situation where the stock launcher would continue looping back to the Welcome/select language screen. I wiped cache, data, and dalvik and reflashed the 4.5.5 rom which didn't fix it. I even tried that same approach including a wipe of system... same result. I was quite surprised to see the problem continue even after wiping everything. At that point I figured I go back to full stock and start over... BAD IDEA.
Anyway, I ordered a new one and it should be here tomorrow. I'm now curious if it's possible to recover the bricked device via the UART port on the motherboard. We'll see.:fingers-crossed::fingers-crossed:
notorious.dds said:
. . .
I think I ended up installing Nova via the app store so that's why it wasn't on the system partition. However, my widgets seemed to work when I checked again. I have no idea why they wouldn't work when I first tried them. I did end up creating two simple scripts via the "Scripter" app that would enable and disable the stock launcher. I put them as widgets on the nova desktop allowing for single click toggling of the stock launcher.
No, nothing seemed to fix the wallpaper... always black. Am understanding this correctly that the wallpaper works on this thing if I load Lollipop?
I didn't want to fiddle around with change the bootloaders every time I wanted into TWRP. At this point, it doesn't matter anyway... I hard bricked the device by flashing the 5.2.0 stock recovery last night
The post about using this to revert to stock should be edited or removed. It's bad.
The only reason I was trying to revert to stock was that I ended up getting into a situation where the stock launcher would continue looping back to the Welcome/select language screen. I wiped cache, data, and dalvik and reflashed the 4.5.5 rom which didn't fix it. I even tried that same approach including a wipe of system... same result. I was quite surprised to see the problem continue even after wiping everything. At that point I figured I go back to full stock and start over... BAD IDEA.
Anyway, I ordered a new one and it should be here tomorrow. I'm now curious if it's possible to recover the bricked device via the UART port on the motherboard. We'll see.:fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
Sorry to hear about the brick. Good thing Amazon is patient with us.
Yes, wallpaper works fine on OS 5. [For others who read this, on OS 4 the only way to get wallpaper is with Xposed (installed in TWRP) and the kindleBG module in the link I posted above. And BTW, although the tools don't block OS 4 Amazon launcher ATM, it can be done manually. Commands are here.]
Thanks for your input. Play store didn't work for me either this time, despite earlier success. Everything else except the launcher block (and other non-OTA blocks) does work, so for now I'm just going to edit post and see if there's any other interest in play store on OS 4. (I trust you'll get OS 5 on replacement or will want to update to it.)
As to TWRP: Once tablet is set up, booting TWRP isn't needed much except for upgrading. and bibikalka gives us lots of options for doing it.
Let us know if anything comes of UART port tests. You'd be the hero of the community!
Workaround for Windows username with spaces
The Install Other Launcher and Install Kingroot jobs may not complete if your Windows username has spaces in it. I'll fix this in next update. Meanwhile here's the workaround:
1. Right-click RUNME.bat and choose Edit. [file opens in Notepad]
2. Add a blank line under :: Set paths and run menu.
3. Type: SET "username=abc"
4. Make sure this section of RUNME looks like below and then save and close Notepad
Code:
:: Set paths and run menu.
SET "username=abc"
SET "main=%CD%\"
SET "jobsdir=%main%jobs\"
[remaining code]
This changes the username only for the tools. The rest of Windows continues to use the real username.
I'm getting ready to update. Please let me know if you found any problems.
Used the tool on my Fire HD 6 (4th Gen) running a Rooted OS 5.1.2.1 to install a new launcher and block OTA's, ads, fire launcher, appstore, and Amazon search. Everything worked without issue! Thanks for the awesome and simple to use tool! Tablet is now almost pure Android. Great work!!!
Sidenote: Used bibikalka's TUT (http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950) on my Fire HD 6 that was currently running Fire OS 4.5.3 with TWRP Recovery to obtain a Rooted Fire OS 5.1.2.1..
I adb'd the 5.1.2 upgrade to my slab this way.
$ adb push update-kindle-20.5.4.2_user_542168620.bin /sdcard/
3047 KB/s (663908627 bytes in 212.722s)
My OS is FIRE OS 5.1.2 Build Date March 31, 2016 1:37 AM.
I tried and got an error to the effect, "cannot upgrade because the upgrade you are trying is older than the one you have".
So I'm probably running an even later version of 5.1.2 where they blocked that loophole.
I'm just going to by a cheap Chinese slab and root that.
wallywallywally said:
I adb'd the 5.1.2 upgrade to my slab this way.
$ adb push update-kindle-20.5.4.2_user_542168620.bin /sdcard/
3047 KB/s (663908627 bytes in 212.722s)
My OS is FIRE OS 5.1.2 Build Date March 31, 2016 1:37 AM.
I tried and got an error to the effect, "cannot upgrade because the upgrade you are trying is older than the one you have".
So I'm probably running an even later version of 5.1.2 where they blocked that loophole.
I'm just going to by a cheap Chinese slab and root that.
Click to expand...
Click to collapse
use adb sideload in Stock recovery
Sent from my KFFOWI using XDA Labs
sd_shadow said:
use adb sideload in Stock recovery
Sent from my KFFOWI using XDA Labs
Click to expand...
Click to collapse
Yuh, I used sideload AND IT WORKED!!
I also have a fire 5th generation. Does the same procedure work for that, assuming I use the proper 5.1.2 for that device: https://kindle-fire-updates.s3.amaz...ate-kindle-global-37.5.4.2_user_542168620.bin
wallywallywally said:
Yuh, I used sideload AND IT WORKED!!
I also have a fire 5th generation. Does the same procedure work for that, assuming I use the proper 5.1.2 for that device: https://kindle-fire-updates.s3.amaz...ate-kindle-global-37.5.4.2_user_542168620.bin
Click to expand...
Click to collapse
yes
Sent from my KFFOWI using XDA Labs
Confirmed, this procedure worked for Fire (5th generation), however the amazon update file is different (see a few posts back)
I just got a fire HD 6 (4th Gen) with the 4.5.2 OS.
Everything I see talks about 4.5.3 and later. I have not turned on wifi, so basically in a holding pattern for now. I want to root/twrp and maybe a custom rom.
Can some give me advice on the best path to take? Should I upgrade then root? Or root then upgrade? Any advice is appreciated.
So I successfully followed this guide for rooting my V20:
http://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
I now have SuperSU and TWRP on my phone. However, nothing actually works whenever I do anything root related. I can't uninstall any system apps with "System app remover", deleting anything in /system/app with "Root Browser" doesn't work, and even changing some buildprop settings with "BuildProp Editor" gives me an error that I don't have root. The SuperSU pop-up to grant access showed up for each of them, and I granted access for each of them, yet they still work as if I have no root. Although, checking my root with "Root Checker" or "Root Check" both say that I have root.
If it helps any, my software version is exactly "H91810d".
I'm not really a root wiz, so I'm not sure what to do now. Any help from here is greatly appreciated!
Fixed it
I have finally fixed it! Apparently I need to install BusyBox first to actually be able to do anything. I thought I already have it installed from the App Store; however, I apparently also need to install it by going to the BusyBox app, going to Installer, then installing it there to /su/xbin. For anyone with a similar problem, hopefully this will solve it. Cheers, and Merry Christmas!
Hello, just received my Fire HD 8 (2017), with Fire OS 5.3.3.0.
I am aware no root exists for that firmware at the minute. I was wondering if there was a way to stop OTA updates, so that if root comes out for that version I'm not stuck on the latest. Thanks.
I just received one as well and came here looking for similar info. Short of keeping the device turned off, I don't think there is a way to stop it from trying to update without root. However, you should be able to block the requests by using a no-root firewall app like NetGuard or NoRoot Data Firewall. See the following for some info:
https://forum.xda-developers.com/hd8-hd10/help/block-ota-updates-root-t3496861
(Note: one user there mentions the OP method no longer works on 5.3.3)
I received mine today as well, but unwittingly entered wifi details during the setup and, of course, the bloody thing updated straightaway. So now its on 5.4.
Just one thing. I have developer options and install from unknown sources enabled, but when I try to install any apk's copied from my phone using myappshare, the install button doesn't work. Is this because they were downloaded from the Google app store originally? None of the copied apps are available on the Amazon app store.
mickrick said:
I received mine today as well, but unwittingly entered wifi details during the setup and, of course, the bloody thing updated straightaway. So now its on 5.4.
Just one thing. I have developer options and install from unknown sources enabled, but when I try to install any apk's copied from my phone using myappshare, the install button doesn't work. Is this because they were downloaded from the Google app store originally? None of the copied apps are available on the Amazon app store.
Click to expand...
Click to collapse
someone on a different thread mentioned that a reboot is needed after enabling the "install from unknown sources" for the install button to work.
ravipkumar said:
someone on a different thread mentioned that a reboot is needed after enabling the "install from unknown sources" for the install button to work.
Click to expand...
Click to collapse
Of course it does . Working fine now.