Kindle Fire HD 7.2.3 - 7" Kindle Fire HD General

Hi,
I just received Update 7.2.3 I am wondering what could have changed. There is now changelog so far on amazon.com

dang this is a real cat n mouse game going on with amazon. i've been trying to catch up on how i can root my brand new kfhd7 and another update pops up before i even finish reading everything within 24 hours of owning it. is there no way to flash a custom recovery with a fastboot cable?

Thanks for the update. I disabled some files. Let's see if it prevents 7.2.3 from unrooting my device.
Sent from my SPH-L710 using xda premium

have u lost ur root after received the updates?

Yeah i lost my root - but i got it back after rooting it again
just use "Root_with_Restore_by_Bin4ry_v17" and take option 1.
still wondering if there's something new about the update..

Already up?
Already updated?
That to fix what is wrong, what? Or, in order to increase store sales Guernsey
First by a firewall blocking the update, but it can feel a little slow.
7.2.3 and re-routing, just one worry.
Backup routing state does not know, then here too bulletins see I'll have to.
All Merry Christmas

viro18 said:
Yeah i lost my root - but i got it back after rooting it again
just use "Root_with_Restore_by_Bin4ry_v17" and take option 1.
still wondering if there's something new about the update..
Click to expand...
Click to collapse
I have my Kindle Fire HD 7.2.2 and I tried the root and I get so far until
adb shell
echo 'ro.kernel.qemu=1' > /data/local.prop "Permission Denied" Does the Root_with_Restore_by_Bin4ry_v17 work?
Because I get this too
Device type:
1) Normal
2) Special (for example: Sony Tablet S, Medion Lifetab)
x) Unroot
Make a choice: 1
Checking if i should run in Normal Mode or special Sony Mode
Please connect your device with USB-Debugging enabled now
remote object '/system/app/Backup-Restore.apk' does not exist
remote object '/system/bin/ric' does not exist
.
.
Normal Mode enabled!
.
Pushing busybox....
failed to copy 'stuff/busybox' to '/data/local/tmp/./busybox': Permission denied
Pushing su binary ....
failed to copy 'stuff/su' to '/data/local/tmp/./su': Permission denied
Pushing Superuser app
failed to copy 'stuff/Superuser.apk' to '/data/local/tmp/./Superuser.apk': Permi
ssion denied
Making busybox runable ...
Unable to chmod /data/local/tmp/busybox: No such file or directory
.
Please look at your device and click RESTORE!
If all is successful i will tell you, if not this shell will run forever.
Running ...
Even after this it asks to reset data on my Kindle I let it reboot and it fails

Khasar2012 said:
I have my Kindle Fire HD 7.2.2 and I tried the root and I get so far until
adb shell
echo 'ro.kernel.qemu=1' > /data/local.prop "Permission Denied" Does the Root_with_Restore_by_Bin4ry_v17 work?
Because I get this too
Device type:
1) Normal
2) Special (for example: Sony Tablet S, Medion Lifetab)
x) Unroot
Make a choice: 1
Checking if i should run in Normal Mode or special Sony Mode
Please connect your device with USB-Debugging enabled now
remote object '/system/app/Backup-Restore.apk' does not exist
remote object '/system/bin/ric' does not exist
.
.
Normal Mode enabled!
.
Pushing busybox....
failed to copy 'stuff/busybox' to '/data/local/tmp/./busybox': Permission denied
Pushing su binary ....
failed to copy 'stuff/su' to '/data/local/tmp/./su': Permission denied
Pushing Superuser app
failed to copy 'stuff/Superuser.apk' to '/data/local/tmp/./Superuser.apk': Permi
ssion denied
Making busybox runable ...
Unable to chmod /data/local/tmp/busybox: No such file or directory
.
Please look at your device and click RESTORE!
If all is successful i will tell you, if not this shell will run forever.
Running ...
Even after this it asks to reset data on my Kindle I let it reboot and it fails
Click to expand...
Click to collapse
i did not even install andoird sdk just "Kindle Fire ADB drivers.exe" and killed "adb.exe" process in tasmanager before rooting my device^^

Khasar2012 said:
I have my Kindle Fire HD 7.2.2 and I tried the root and I get so far until
adb shell
echo 'ro.kernel.qemu=1' > /data/local.prop "Permission Denied" Does the Root_with_Restore_by_Bin4ry_v17 work?
Click to expand...
Click to collapse
Yup, that is as far as I get too. No one has been able to help me get past this.

Ravynmagi said:
Yup, that is as far as I get too. No one has been able to help me get past this.
Click to expand...
Click to collapse
You guys are using the wrong root method, that one doesn't work anymore. use this one: http://forum.xda-developers.com/showthread.php?t=1886460
choose option 1.

jmandawg said:
You guys are using the wrong root method, that one doesn't work anymore. use this one: http://forum.xda-developers.com/showthread.php?t=1886460
choose option 1.
Click to expand...
Click to collapse
The other thread recommended that as the first step, and then the older qemu method as the second step. So I tried both. And both run into permission denied errors.

First I wanna say when I first got my kindle fire HD 7" I rooted it having 7.2.1 on it.. Amazon pushed the 7.2.2 update, and I lost root so I use Root_with_Restore_by_Bin4ry_v17, and used the normal option as he stated. Once that was done, the kindle was very slow and the screen was flickering and then I used qemuroot v1.0 as instructed and did option 1. It went thru its process and I regained root. I just now checked the kindle and saw 7.2.3 on there now. I went to Root_with_Restore_by_Bin4ry_v17 and chose normal option, and went thru the process and have regained root only by using Root_with_Restore_by_Bin4ry_v17. This was my scenario and excactly what I did each time.

I'm also getting permission denied errors no matter what guide I follow.

djr4x4 said:
First I wanna say when I first got my kindle fire HD 7" I rooted it having 7.2.1 on it.. Amazon pushed the 7.2.2 update, and I lost root so I use Root_with_Restore_by_Bin4ry_v17, and used the normal option as he stated. Once that was done, the kindle was very slow and the screen was flickering and then I used qemuroot v1.0 as instructed and did option 1. It went thru its process and I regained root. I just now checked the kindle and saw 7.2.3 on there now. I went to Root_with_Restore_by_Bin4ry_v17 and chose normal option, and went thru the process and have regained root only by using Root_with_Restore_by_Bin4ry_v17. This was my scenario and excactly what I did each time.
Click to expand...
Click to collapse
Re-rooting is the easy part. Rooting a new 7.2.2 or 7.2.3 seems to be the PITA.

Ravynmagi said:
Re-rooting is the easy part. Rooting a new 7.2.2 or 7.2.3 seems to be the PITA.
Click to expand...
Click to collapse
It would be interesting to see if those who are having difficulty rooting 7.2.2 received their KFHD with 7.2.2 preloaded. I bought my KFHD 7" the first day of availability, never rooted it before, but was able to cleanly root it after it updated to 7.2.2.
I believe that it is possible that Amazon slipstreamed in a minor hardware change (that required the 7.2.2 firmware) that affects how the existing rooting methods operate.

Ravynmagi said:
The other thread recommended that as the first step, and then the older qemu method as the second step. So I tried both. And both run into permission denied errors.
Click to expand...
Click to collapse
Make sure you have the adb "composite" driver listed under the Kindle device in device manager. Otherwise you have the wrong adb driver and this won't work.

Xyth said:
Make sure you have the adb "composite" driver listed under the Kindle device in device manager. Otherwise you have the wrong adb driver and this won't work.
Click to expand...
Click to collapse
I just double checked, says Kindle Fire, then Android Composite ADB Interface, right below it. It always shows up just fine in adb devices.
I just did a factory reset, will start over and give it a few more tries tonight.
---------- Post added at 10:27 PM ---------- Previous post was at 10:13 PM ----------
Well what do you know. It decided to work today. Don't think I did anything different (other than not trying a factory restore earlier).

Try running the first stage twice if you're getting permission errors. was able to root 7.2.3 by running option 1 twice back to back, no Qemu needed.

Anyone know of a temp root method for this?

Root and Google Play for Amazon 7" Kindle Fire HD Software Version 7.2.3
demoncamber said:
Anyone know of a temp root method for this?
Click to expand...
Click to collapse
What exactly do you mean by "temp root method"?
You can Unroot after Root if that is what you want to do. What are you trying to accomplish?

Related

[Q] sdcard permission denied

I have rooted my OG MyTouch 3g, so I am familiar with the process, and now I am trying to root my MyTouch 4g.
I am trying to:
Code:
adb push su /sdcard/su
and every time i try it says:
Code:
failed to copy 'su' to '/sdcard/su': Permission denied
Any suggestions?
rbmako69 said:
I have rooted my OG MyTouch 3g, so I am familiar with the process, and now I am trying to root my MyTouch 4g.
I am trying to:
Code:
adb push su /sdcard/su
and every time i try it says:
Code:
failed to copy 'su' to '/sdcard/su': Permission denied
Any suggestions?
Click to expand...
Click to collapse
Okay what Rooting process are you trying to follow? And in what step are you.
The main reason you are getting that error is the file "su" doesn't exist.... but if you answer the question above we can help you more.
I am trying the Cyanogen Mod: TMobile_myTouch_4G:_Full_Update_Guide
rbmako69 said:
I am trying the Cyanogen Mod: TMobile_myTouch_4G:_Full_Update_Guide
Click to expand...
Click to collapse
Make sure you have ADB Debugging turned on
- Settings > applications > development
Make sure you have the SD Card mounted to the computer
Make sure you changed your ADB target folder to the one store that rooting package.
Those would be the three places i'd start if i were you.
However alot of people will contest that this method is simpler with a high percentage of "" when you are done with the rooting process.
neidlinger said:
Make sure you have ADB Debugging turned on
- Settings > applications > development
Click to expand...
Click to collapse
Yes, I did that.
neidlinger said:
Make sure you have the SD Card mounted to the computer
Click to expand...
Click to collapse
I have access to all the files on the SDCARD on my mac
neidlinger said:
Make sure you changed your ADB target folder to the one store that rooting package.
Click to expand...
Click to collapse
Not sure what you mean by this.
Those would be the three places i'd start if i were you.
However alot of people will contest that this method is simpler with a high percentage of "" when you are done with the rooting process.[/QUOTE]
I'm going to try the method that you linked.
rbmako69 said:
I have access to all the files on the SDCARD on my mac
Click to expand...
Click to collapse
Being that you are using a Mac you might run into some problems along the road. I've see quite a few "problematic" threads pop up regarding Mac and Android's ADB not working correctly.
you could also try This Method < it doesn't require the use of a PC @ all.
I did that other method and it seems to have worked.
Now do I continue with the walkthrough of installing cyanogen now that the phone is rooted?
rbmako69 said:
I did that other method and it seems to have worked.
Now do I continue with the walkthrough of installing cyanogen now that the phone is rooted?
Click to expand...
Click to collapse
Do you have a Super User icon on your screen?
If you do
-Downloaded Terminal Emulator from the market.
- go to it and type "su" you should get a window asking you to approve the Super User request.
If the dollar sign ($) changes to a pound (#) sign then you are rooted.
next turn off the phone and hold the volume down rocker and the power button that will boot into engineering scree (HBoot) look on the top line and see if you have "s=off"...
If the s=off then you are perma rooted w/o the security check. temp root with VISIONary one last time, then install Clockwork ROM Manager and change the Recovery Image to 3.0.0.06 (Here or Here) From their you can do what you want to do regarding Cyanogen(mod).
*The reason i recommend flashing 3.0.0.6 prior to flashing it ROMs is it handles 2.2 (ext3) and 2.3 (ext4) style roms. Where every other version is either or, not both.
I sucessfully installed cyanogen, and everything seems to be working correctly, but i must not have installed the google apps, and i do have the market place to download them again.
Where can i get those from?
EDIT: I found them.
rbmako69 said:
I sucessfully installed cyanogen, and everything seems to be working correctly, but i must not have installed the google apps, and i do have the market place to download them again.
Where can i get those from?
Click to expand...
Click to collapse
http://android.d3xt3r01.tk/cyanogen/gapps/gapps-gb-20110120-signed.zip
wipe (factory reset) before flashing the g/apps via the recovery image.
I had found them before, but the market wasn't working, and I was trying to sync my contacts back to the phone from my gmail account. I didn't do a factory reset through, so I'm trying again. Hopefully it works this time.
I'm guessing the market isn't working because I haven't signed in with my gmail account.
Any idea on how to set that back up?
rbmako69 said:
I'm guessing the market isn't working because I haven't signed in with my gmail account.
Any idea on how to set that back up?
Click to expand...
Click to collapse
Settings > accounts & Sync > menu button > add account.

Unable to Re-Root Droid 2 after Gingerbread OTA

Here's my problem,
I had the Droid 2 with stock ROM rooted and all was well. My phone installed the Gingerbread ROM (4.5.601) when Verizon pushed it out a few days ago. Thankfully, this did not totally jack up my phone. However, I no longer have root access.
I have tried three different 1 click root methods for the Gingerbread ROM but none of them worked. I tried un-rooting and re-rooting with one clicks and that's not working. I tried manually removing the Superuser app and rooting, no joy.
The one clicks are connecting with the phone but the phone does not seem to want to allow access to change files.
Before anyone asks, YES I have the drivers installed and the connection with the PC is good. I have attempted to run the 1 click roots in "charge only" AND "PC Mode". Debugging is on and I am set to allow non-market applications.
Suggestions?
Thanks,
Tracker
Update: in trying to manually remove old superuser file with adb shell, I just can't seem to get the # prompt to execute the commands even after running Pete Souza's exploits.
suggestions?
Hope somebody comes up with an answer - same thing happened to me.
did you use the d3 root method? thats the only one that works 100% on gingerbread.
Yes. I used the "Pete's Motorola Root Tools.exe" program on Win7:
psouza4.com/droid3/#root
I also followed the "Droid X Notes" section at the bottom even though I have the D2 and I'm not able to get the "adb shell" ending with #.
SOS!!
Thank you for such a clear, concise post! I am in the same boat with no luck. I used the one click root for D3 which says it will work for a number of Android phones, including the D2 Global, but is NOT working with my D2. I have run the application two times and both times it went through the entire process, rebooted my phone three times and said success but...no success... I am sooo bummed as the only way I get internet at home is via Wireless Tether which I can no longer use because I do not have Root access!
Desperate in Cool (the name of the town I live in), I need help!!
Thanks in advance,
Jeni
Yeah, still no joy here. I've retried everything that I mentioned in the OP and still can't get the # so I can execute an un-root and/or re-root as described on Pete's website.
I've tried it on both a Win XP and a Win 7 machine.
Anyone have any suggestions? It appears the D2 Gingerbread firmware doesn't want to allow permissions to modify certain portions that were allowed before.
Success
I didn't so much fix the problem as hit it with a bat until it shattered, then rebuilt it.
My fix was to SFB the phone back to Froyo with factory defaults, activate it with Verizon (at this point I have no software added or accounts set up on it so obviously no root), apply the OTA update to GB, perform the 1-click Root which worked this time, then setup my google accounts and install Titanium Backup which I had previously used, and restored all my data from it.
At this point I'm getting some force-close errors which I'm sure are related to the Titanium restore but I was able to ADB Shell in and SU so I know I have rooted it properly and at the very least I will do another clean wipe and restore individual applications one at a time so I know which aren't working right and go from there.
Good luck everyone!
My fix was to SFB the phone back to Froyo with factory defaults, activate it with Verizon (at this point I have no software added or accounts set up on it so obviously no root), apply the OTA update to GB, perform the 1-click Root which worked this time, then setup my google accounts and install Titanium Backup which I had previously used, and restored all my data from it.
Click to expand...
Click to collapse
I kinda figured that this would work. I'm trying to avoid a full nuke of the phone, but so far it appears that this is the only work around.
Anyone else got a plan?
Only option I was going to provide was SBF to 2.3.2 with RSDlite and re-flash the OTA, then run the Droid3 exploit.
I have a D2G and I had the exact same problem. I did an OTA upgrade without un-rooting (I was earlier rooted using z4root). I had a long discussion with Pete Souza, the guy who created 1-Click root. And he agreed to help me out. He did a remote to my computer and rooted my D2G. I am going to try to reproduce all the steps here.
Situation: Was rooted using z4root. Had Superuser and su binary both on my phone but root was not recognized by titanium Backup, SetCPU, etc.
Resolution:
Run Psouza's 1-cick root http://www.psouza4.com/droid3 (ensure u have motorola drivers)
First try the Root, and if that does not work only then continue with the following steps. I got an error after step 3 which said the phone cannot be rooted (or something like that). The first two steps were a success.
Now that the root is not working, run the Temp ADB Root from the same app. In my case even that failed - but Pete said that ignore the failure message.
Now, I need to delete the su and busybox which are leftovers from the earlier root.
Open a command prompt in the support_files folder where adb is located.
Get into the shell by typing: "adb shell"
type "/system/xbin/su"
This will pop-up a prompt on your phone to allow Superuser access - just click Okay.
The $ sign will change to #
Now type "busybox mount -o remount,rw /dev/block/mtdblock3 /system"
now type "cd /system/bin" This is where your su and busybox are.
Type "rm su"
Type "rm busybox"
After this just exit out of everything and run the 1-click root again. It should work now.
======================
All credits to psouza www.psouza4.com
======================
drumster said:
I have a D2G and I had the exact same problem. I did an OTA upgrade without un-rooting (I was earlier rooted using z4root). I had a long discussion with Pete Souza, the guy who created 1-Click root. And he agreed to help me out. He did a remote to my computer and rooted my D2G. I am going to try to reproduce all the steps here.
Situation: Was rooted using z4root. Had Superuser and su binary both on my phone but root was not recognized by titanium Backup, SetCPU, etc.
Resolution:
Run Psouza's 1-cick root http://www.psouza4.com/droid3 (ensure u have motorola drivers)
First try the Root, and if that does not work only then continue with the following steps. I got an error after step 3 which said the phone cannot be rooted (or something like that). The first two steps were a success.
Now that the root is not working, run the Temp ADB Root from the same app. In my case even that failed - but Pete said that ignore the failure message.
Now, I need to delete the su and busybox which are leftovers from the earlier root.
Open a command prompt in the support_files folder where adb is located.
Get into the shell by typing: "adb shell"
type "/system/xbin/su"
This will pop-up a prompt on your phone to allow Superuser access - just click Okay.
The $ sign will change to #
Now type "busybox mount -o remount,rw /dev/block/mtdblock3 /system"
now type "cd /system/bin" This is where your su and busybox are.
Type "rm su"
Type "rm busybox"
After this just exit out of everything and run the 1-click root again. It should work now.
======================
All credits to psouza www.psouza4.com
======================
Click to expand...
Click to collapse
IMO this instruction should be stickied.
This worked perfectly on my wife's D2G. Rooted Gingerbread = a good start to the day!
Awesome! Thanks!
Just wanted to say I think i love you...this worked for me after two tries on my Droid 2.
First time I was able to remove su and busybox...then when I applied the one click root again, it said there were a bunch of errors but still succeeded. After the reboot I didn't get superuser access yet so I went through deleting su and busybox again (but busybox wasn't found)
The second time i decided to restart my phone before running the script again and when attempting to verify if su was still installed by going into adb shell...it said my phone was already rooted.
Thanks!!
Awesome!
Thanks! This worked for me as well! (after additional reboot)
Good Info but one problem for me
Since I did the OTA Gingerbread, I cannot get into debugging mode. I have uninstalled the Moto drivers & reinstalled using my administrator profile on Windows 7. I have also sbf my phone. Wipe cache. Factory reset. Activate service (NOT download or sync w/ google). OTA Gingerbread. This is on a regualr D2. Anyone have any ideas on how I can get into debugging mode. Otherwise I can't do anything.
Thank you!
I am so glad I found this post and the directions posted by drumster. I had previously used z4root and had not unrooted before allowing the Gingerbread upgrade. Pete's application fixed my Droid 2 on the first attempt; no other steps were needed.
Thanks again,
Andrew
awesome
psouzas 1 click worked for me. Droid 2. previously had rooted with deroot method until it updated by itself to gingerbread which broke root.
enabled usb debugging
in pc mode, clicked on souza's link and followed instructions
i have win 7 64 bit computer
It works
I just got it to work. I was on rooted froyo. Sbf'd back to stock froyo. Downloaded and installed OTA G bread. Then I had to run the D3 one click root method twice but the 2nd time it worked fine.

Market wont work on rooted kindle

Not sure what is going on. I rooted the fire, install vendor.app and framework. I open market it has a difficult time with my gmail.account but after a few tries it authenticates successfully. At this point it tries opening the market and fails. I've tried reinstalling, revolting.
I will say that I have not tried root explorer as I cannot understand how to install it (amazon denies my purchasing it since it is not compatible with my device)
Could it be a rights issue? If I need root explorer how can I get it?
Sent from my Kindle Fire using Tapatalk
sideload dat ****
Maybe you should try another version of vending.apk and sideload the root explorer into your fire rather than getting it from amazon.
Then i guess you might need to use the root explorer to modify the permission of vending.apk to rw-r--r--
Easiest fix for this is downloading the Kindle Fire Utilities:
http://forum.xda-developers.com/showthread.php?t=1399889
And once in, go to extras and install google hulabaloo.
http://forum.xda-developers.com/showpost.php?p=20240542&postcount=8
I had so much trouble with the market and other versions of Vendor.apk myself on the stock KF rom and no matter what I did, I ended up with similar issues. Setting permissions isn't really hard at all (most require a chmod 644, which is user/owner read + write, all others just read), and I actually did get it to work just once before having to restore a backup because I screwed something completely unrelated up . If you keep at it, there's a good chance you'll get it right eventually, but I just installed CM7 and couldn't be happier.
I also had trouble at first but I found this videos method to work flawlessly and easily.
http://www.youtube.com/watch?v=rTkegVrnAvA
I got it to work. Hopefully this works for you as it was frustrating for me to have so many problems.
http://forum.xda-developers.com/showthread.php?t=1450232
You are all awesome in my book!!! Thank you. I will keep at it and not give up.
Sent from my Kindle Fire using Tapatalk
success!!! thanks again

[ROOT]Kindle Fire HD 8.9

Ok, I had no other place to put this post, but figured this was the best for right now. I was unable to achieve root with the HD 7 method, so I went searching. I am happy to report success!
All thanks go to Bin4ry, as I did nothing to contribute to this method, only tried his auto root program.
The files and steps are located here:
http://forum.xda-developers.com/showthread.php?t=1886460
Follow the steps for the Sony tablet. This is achieved using the 2nd option.
Video for steps are here:
http://forum.xda-developers.com/showthread.php?p=33470626#post33470626
Again follow all the steps in the video for the tablet, which is the second item rooted.
I also tried the 7 root method and it did not work. Thanks for this, it worked. It was a little tricky and some of the commands didn't appear to be working but in the end I have superuser installed. So far so good...
Maybe someone can shed some light on exactly what this method is doing and verify it is safe.
Thanks, just got an 8.9 myself. Going to try your root method tomorrow
No go here. Can't get adb to recognize the device, and I don't know where to find the device ID for fixing the ADB_USB file in .android directory
After rooting using this method and installing go launcher and es file explorer. I found a few odd applications that are installed. I'm trying to figure out if these were already on the device or if they were installed by this root method.
WanPeek
AT&T AllAccess
Are these one your device?
Update: looks like the AT&T apk is indeed a Kindle app. I'll assume WanPeek was also already here.
jmoak said:
After rooting using this method and installing go launcher and es file explorer. I found a few odd applications that are installed. I'm trying to figure out if these were already on the device or if they were installed by this root method.
WanPeek
AT&T AllAccess
Are these one your device?
Update: looks like the AT&T apk is indeed a Kindle app. I'll assume WanPeek was also already here.
Click to expand...
Click to collapse
Yes, they were already on all three I rooted. My guess is they are there to support the AT&T 4G version of the 8.9.
Thanks for the confirmation
Sent from my KFJWI using Tapatalk 2
mdblaze said:
Ok, I had no other place to put this post, but figured this was the best for right now. I was unable to achieve root with the HD 7 method, so I went searching. I am happy to report success!
All thanks go to Bin4ry, as I did nothing to contribute to this method, only tried his auto root program.
The files and steps are located here:
http://forum.xda-developers.com/showthread.php?t=1886460
Follow the steps for the Sony tablet. This is achieved using the 2nd option.
Video for steps are here:
http://forum.xda-developers.com/show...6#post33470626
Again follow all the steps in the video for the tablet, which is the second item rooted.
Click to expand...
Click to collapse
I can confirm as well that this method works. As the post said before it appears the process is not working, but sure enough when it finished there was superuser apk and su access. Thanks for being the guinea pig mdblaze, good find!
Confirmed Root + Play Store
mdblaze said:
Ok, I had no other place to put this post, but figured this was the best for right now. I was unable to achieve root with the HD 7 method, so I went searching. I am happy to report success!
All thanks go to Bin4ry, as I did nothing to contribute to this method, only tried his auto root program.
The files and steps are located here:
http://forum.xda-developers.com/showthread.php?t=1886460
Follow the steps for the Sony tablet. This is achieved using the 2nd option.
Video for steps are here:
http://forum.xda-developers.com/show...6#post33470626
Again follow all the steps in the video for the tablet, which is the second item rooted.
Click to expand...
Click to collapse
I can confirm this works as well, and also that Kindle Fire HD 7 method for installing Play Store works as well too (did not auto-update with old vending.apk, but works just as fine with actual Google Play APK) Hands-down the 8.9 flies faster than the 7!
It worked! Thanks OP!
Anything we can do about apps that don't work? ie google maps, tasks apps, google currents, etc?
Are you guys using a different launcher now, like ADW launcher or NovaLauncher?
Not working for me either. Seems like it can't detect my tablet (have ADB mode enabled). Did ya'll have to install some drivers? I Googled some Fire HD 7.0 ADB drivers, but those wouldn't install for me.
If someone can provide a bit more details, I'd appreciate it. Thanks.
Ravynmagi said:
Not working for me either. Seems like it can't detect my tablet (have ADB mode enabled). Did ya'll have to install some drivers? I Googled some Fire HD 7.0 ADB drivers, but those wouldn't install for me.
If someone can provide a bit more details, I'd appreciate it. Thanks.
Click to expand...
Click to collapse
These are the directions I used to install ADB drivers on my 8.9. Good Luck
https://developer.amazon.com/sdk/fire/connect-adb.html
somdave2005 said:
These are the directions I used to install ADB drivers on my 8.9. Good Luck
https://developer.amazon.com/sdk/fire/connect-adb.html
Click to expand...
Click to collapse
If I run "adb devices" from the Android SDK, it shows the Kindle Fire.
However if I run "adb devices" from the batch file link above, it never finds it.
---------- Post added at 11:42 PM ---------- Previous post was at 11:41 PM ----------
Well I had to install the Android SDK. Then copy the Platform-Tools folder into this script's "\stuff" folder.
Now ADB finds my Kindle Fire HD.
I tried option 1, it seemed to complete fine, but no Super User in apps. So I tried option 2, again no Super User. Which method are people using with success?
Ravynmagi said:
If I run "adb devices" from the Android SDK, it shows the Kindle Fire.
However if I run "adb devices" from the batch file link above, it never finds it.
---------- Post added at 11:42 PM ---------- Previous post was at 11:41 PM ----------
Well I had to install the Android SDK. Then copy the Platform-Tools folder into this script's "\stuff" folder.
Now ADB finds my Kindle Fire HD.
I tried option 1, it seemed to complete fine, but no Super User in apps. So I tried option 2, again no Super User. Which method are people using with success?
Click to expand...
Click to collapse
Option 2, I followed along with the video. Entering every command even if they didn't appear to work.
---------- Post added at 12:51 AM ---------- Previous post was at 12:50 AM ----------
somdave2005 said:
It worked! Thanks OP!
Anything we can do about apps that don't work? ie google maps, tasks apps, google currents, etc?
Are you guys using a different launcher now, like ADW launcher or NovaLauncher?
Click to expand...
Click to collapse
I tried both Go Launcher HD and Apex Launcher. I like Apex better so far.
jmoak said:
Option 2, I followed along with the video. Entering every command even if they didn't appear to work.
---------- Post added at 12:51 AM ---------- Previous post was at 12:50 AM ----------
I tried both Go Launcher HD and Apex Launcher. I like Apex better so far.
Click to expand...
Click to collapse
Are you getting permission denied errors with the first two commands?
Ravynmagi said:
Are you getting permission denied errors with the first two commands?
Click to expand...
Click to collapse
I believe so but I do not fully remember. I do know I was getting errors but just kept pushing on. It even mentions you will get errors in the video. I do remember getting errors on the last two commands thinking something was wrong but he also gets the same error in the video.
Start watching the video at about the 7 minute mark. That is when he roots a tablet.
jmoak said:
I believe so but I do not fully remember. I do know I was getting errors but just kept pushing on. It even mentions you will get errors in the video. I do remember getting errors on the last two commands thinking something was wrong but he also gets the same error in the video.
Start watching the video at about the 7 minute mark. That is when he roots a tablet.
Click to expand...
Click to collapse
I decided to just a factory restore and start over.
Unfortunately it's still not working. No Super User, no root access. No idea why this isn't working for me.
---------- Post added at 12:59 AM ---------- Previous post was at 12:25 AM ----------
Have no clue what I was doing wrong or what went wrong the half a dozen previous tries. But now Super SU is installed and root access is confirmed.
Got Google apps installed, but can't sign in with YouTube though. It crashes when trying to sign in.
Edit: Got the YouTube issue resolved as well. Was missing the GoogleLoginService.apk. It's all finally coming together nicely.
Is this surviving reboot? Also has anyone attempted to do a factory reset to see if it clears it? I've had this thing 3 days I really want Google Play on it so I can access my apps but don't really want to nuke the warranty just yet. :/
Technogen said:
Is this surviving reboot? Also has anyone attempted to do a factory reset to see if it clears it? I've had this thing 3 days I really want Google Play on it so I can access my apps but don't really want to nuke the warranty just yet. :/
Click to expand...
Click to collapse
Yes it does work, but no a factory reset will not clear it. If you what to get rid of root you have to move superuser.apk from /system/app folder,to /data/app folder, install it in that location. Then delete the su binary from /system/xbin/. After all that the factory reset will restore to original.
Somethings I ran into that may help other people.
If you do all the steps and still can't see the kindle in ADB run a driver update on the kindle, ADB showed up for me after that.
After the kindle rebooted it was not seeing the device as being back up after a 2 minute wait. I unpluged and reconnected the USB cable and this correct it.

Lost root after OTA update yesterday! [email protected]@rds

I JUST spent a week trying to get voice-dictation working in my email app, which meant needing a keyboard that had voice as an option - I used Swype. IMMEDIATELY after all my hard work, on my rooted Kindle Fire HD 7" - actually, in the middle of still doing work on replacing fuzzy icons with shiny new ones - Amazon decided to do an OTA update and completely undo everything, and now I can't re-do it until someone figures out how to root this thing again. My guess is it won't be so easy this time around.
Goodbye cool keyboard and goodbye dictation and goodbye root and goodbye Voice Searching. And Hello ADS on the lockscreen again. I had gotten rid of them. Dammit.
I also have the special offers version and I also lost my root, but the ads didn't appear again. damn I'm really lucky
Sent from my KFTT using XDA Premium HD app
cdictio said:
I also have the special offers version and I also lost my root, but the ads didn't appear again. damn I'm really lucky
Sent from my KFTT using XDA Premium HD app
Click to expand...
Click to collapse
Same with me - root lost , ads also lost
bryanchapman9999 said:
Same with me - root lost , ads also lost
Click to expand...
Click to collapse
X2 my kindle fire HD is locked, i lost SU access.. any solution? i have 7.2.2 firmware...
Maybe try the 8.9 method? Maybe the 7 got the same fix the 8.9 has always had. I couldn't root my 8.9 using the 7 method. Maybe the 7 is just now getting the updates that the 8.9 has.
Just a thought
Sent from my KFJWI using Tapatalk 2
jmoak said:
Maybe try the 8.9 method? Maybe the 7 got the same fix the 8.9 has always had. I couldn't root my 8.9 using the 7 method. Maybe the 7 is just now getting the updates that the 8.9 has.
Just a thought
Sent from my KFJWI using Tapatalk 2
Click to expand...
Click to collapse
I see complaints about the OTA under the 8.9 thread that is stickied to the top of this forum as well?
Yeah, I noticed those too. The 8.9 got a 8.1.3 update that wiped root but the root method still works. So you just need to reroot. I don't see anyone mentioning using the 8.9 method on the 7 but I do see complaints about the 7.2.2 update.
So it's exactly clear....
Sent from my KFJWI using Tapatalk 2
I'd dig a little, but need to finish a ton of stuff. What happens when trying to reroot? I thought there was a way to lock out the OTAs as well, will be sure to do that this time around. Losing the work is a bummer to be sure; I just wanted to clarify what is going on for my own sanity and that of others who have to hit and run.
Cheers
Krept said:
I'd dig a little, but need to finish a ton of stuff. What happens when trying to reroot? I thought there was a way to lock out the OTAs as well, will be sure to do that this time around. Losing the work is a bummer to be sure; I just wanted to clarify what is going on for my own sanity and that of others who have to hit and run.
Cheers
Click to expand...
Click to collapse
Code:
[email protected]:/ $ echo 'ro.kernel.qemu=1' > /data/local.prop
echo 'ro.kernel.qemu=1' > /data/local.prop
/system/bin/sh: cannot create /data/local.prop: Permission denied
I went ahead and tried the 8.9 method on my HD 7 with 7.2.2
It did not work.
I have used this method with success on my 8.9 so I'm pretty sure I did it right. The terminal app never launches on the device.
Arcymag, thanks. I got that as well now that I had a little time.
Also, here is some info on the methods used to block OTA updates for future reference. http://forum.xda-developers.com/showthread.php?t=1893838&page=11
I apologize if this is seen as duplication, I'm trying to err on the side of tying up little loose ends if anyone had a similar recollection.
cheers
jmoak said:
I went ahead and tried the 8.9 method on my HD 7 with 7.2.2
It did not work.
I have used this method with success on my 8.9 so I'm pretty sure I did it right. The terminal app never launches on the device.
Click to expand...
Click to collapse
Good to know. I was going to try this tonight.. but no need now. Thanks!
lost root
lost root and my launcher gone but playstore istill works and gmail
Root for Amazon 7" Kindle Fire HD Software Version 7.2.2
Thanks to natorus87!
Step 1 Use "Root MANY ANDROID!" http://forum.xda-developers.com/show....php?t=1886460 and use the Normal Method. Pay attention, at some point you will have to respond to a "Restore" dialog box on the Kindle itself. Ignore any errors. The Kindle will reboot and now responds Slowly.
Step 2 Use "Qemu automated root" http://forum.xda-developers.com/show....php?t=1893838 and allow the process to complete.
Step 3 Launch Apps-Superuser to initialize Superuser.apk
That was all you now have Root.
DssTrainer said:
Good to know. I was going to try this tonight.. but no need now. Thanks!
Click to expand...
Click to collapse
Looks like I should have tried option 1 of the root tool. Apparently it works even though we use option 2 for the 8.9.
Sent from my SGH-T769 using Tapatalk 2
worked, great, thank you
This is awesome. I I'm rooted again. Thank you all..
Sent from my KFTT using Tapatalk 2
Thanks, Prok.; that worked for my KFTT which was unrooted by the 7.2.2 update.
No idea what the included exploit bug-fix is but I notice that I now have a SuperSU app in addition to the prior SU.
OTA 7.2.3 lost root
Lost root after update to 7.2.3.
Tried this on a once rooted KFHD didn't work. Factory reset the device and it still shows 7.2.3.
When in RunMe.bat, everything that gets pushed results in access denied.
Busybox, su and superuser apk. "the system cannot find the path specified"
With the RootQemu.bat it's there is no /data/local.prop
[email protected]:/ $ echo 'ro.kernel.qemu=1' > /data/local.prop
echo 'ro.kernel.qemu=1' > /data/local.prop
/system/bin/sh: cannot create /data/local.prop: Permission denied
I have the latest drivers and even tried the latest adb.exe. I can see my device in cmd. (adb devices) ... Java is up to date.
Any ideas?
Root and Google Play for Amazon 7" Kindle Fire HD Software Version 7.2.3
Krsmqn said:
Lost root after update to 7.2.3.
Tried this on a once rooted KFHD didn't work. Factory reset the device and it still shows 7.2.3.
When in RunMe.bat, everything that gets pushed results in access denied.
Busybox, su and superuser apk. "the system cannot find the path specified"
With the RootQemu.bat it's there is no /data/local.prop
[email protected]:/ $ echo 'ro.kernel.qemu=1' > /data/local.prop
echo 'ro.kernel.qemu=1' > /data/local.prop
/system/bin/sh: cannot create /data/local.prop: Permission denied
I have the latest drivers and even tried the latest adb.exe. I can see my device in cmd. (adb devices) ... Java is up to date.
Any ideas?
Click to expand...
Click to collapse
Krsmqn,
You are Rooted per http://forum.xda-developers.com/showthread.php?t=2050553&page=3, correct? Just want to make sure you are not waiting for an answer.

Categories

Resources