Database Users

[request] effective method to prevent OTA updates

Since every method proposed in the thread over in the General forum to prevent updates doesn't work, even having custom TWRP recovery, i'm reaching out to the developers to ask for help on this. I suspect ADCP is involved myself but have no way to trace it.
What if I set /cache to read only? That apparently is where the .bin gets written to by whatever process downloads it, and from there it's read by recovery. Is /cache used by anything else on a typical Android system?
Not everyone wants to use CM7 but that appears to be the ONLY thing that "breaks" OTA updates. I'm sure there's some link in the chain we could interrupt to stop this creeping menace. I'm sure i'm not the only person with 6.2 rooted sitting here with wifi off!

Just a suggestion, but if you set the folder kindleupdates on the sdcard to read-only (it's where updates are downloaded to), would that break OTA updates?

jb0ne said:
Since every method proposed in the thread over in the General forum to prevent updates doesn't work, even having custom TWRP recovery, i'm reaching out to the developers to ask for help on this. I suspect ADCP is involved myself but have no way to trace it.
What if I set /cache to read only? That apparently is where the .bin gets written to by whatever process downloads it, and from there it's read by recovery. Is /cache used by anything else on a typical Android system?
Not everyone wants to use CM7 but that appears to be the ONLY thing that "breaks" OTA updates. I'm sure there's some link in the chain we could interrupt to stop this creeping menace. I'm sure i'm not the only person with 6.2 rooted sitting here with wifi off!
Click to expand...
Click to collapse
Unregistered fires will not get OTA updates. Renaming com.amazon.dcp.apk to com.amazon.dcp.apk.bak will unregister your fire but you will be able to sign into and use all of the amazon services individually.

neilrl79 said:
Unregistered fires will not get OTA updates. Renaming com.amazon.dcp.apk to com.amazon.dcp.apk.bak will unregister your fire but you will be able to sign into and use all of the amazon services individually.
Click to expand...
Click to collapse
Somone just posted that their unregistered Kindle has been updated! There is no escape

Somebody on 6.2 delete /system/etc/otacerts.zip and see if it still updates
Sent from my Galaxy Nexus using XDA App

JackpotClavin said:
Somebody on 6.2 delete /system/etc/otacerts.zip and see if it still updates
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
I just went to do that in File Expert, and I don't have a /system/etc/otacerts.zip.
Any other possible locations for that file? I'll try it.
Edit: Found it in /system/etc/security. It has a 1.6kb file called releasekey.x509.pem in it. Renamed to otacerts.bak
Edit2: Just to be safe, moved the file to my sdcard and deleted it from /system/etc/security. Rebooted ok, temp unrooted, Amazon Videos works, my books work, everything seems ok. Note that I am also one of those who disabled OTASilentInstall as well though that doesn't seem to have mattered for some.

bus_ter said:
Somone just posted that their unregistered Kindle has been updated! There is no escape
Click to expand...
Click to collapse
Interesting, I wonder if they recently unregistered it,after the update had already downloaded and was just waiting to install. My fire has never been registered and has never seen an OTA, in fact a couple of amazon techs told me that it was unable to be updated while unregistered. Although now that i think about it, I can't imagine amazon techs know anymore than anyone else

Wrong forum... Rename /system/etc/otacerts.zip does help.

this would be great. at least then we could edit the binarys before updating to include FFF and TWRP.

Mine is still on 6.2 with these methods.
How to disable auto software update OTA on Kindle Fire?

JayceOoi said:
Mine is still on 6.2 with these methods.
How to disable auto software update OTA on Kindle Fire?
Click to expand...
Click to collapse
Yes, Jayce, but there are people reporting use those methods and still getting the update.

I added another layer of protection, the program Droidwall. I allowed Amazon Apps and Amazon Videos plus a bunch of others but did not allow ADCP. Now if I browse to Amazon App Store, buy an app, it no longer pushes to my Kindle, despite the web page saying just go to the Amazon App store App on my kindle and it would download automagically. I had to manually initiate a download of the app. So either otacerts.zip or firewalling off ADCP disabled remote push of apps -- and hopefully disabled remote push of updates, that part remains to be seen.

new method
new method (not confirmed yet i think)
Kindle Fire 6.2.1 breaks root and you cannot re-root. To prevent this, simply install DroidWall. If you are afraid of downloading the update and want to keep wifi disabled, just do a google search for Droidwall.apk and sideload.
Once installed, launch Droidwall. Make sure the mode says "Mode: White list (allow selected). You will have to manually select which apps to give Wifi access to (I selected Email, Browser, Netflix, and Amazon Video on Demand). You should only select the apps you REALLY want to give access to. Then hit Menu and Apply Rules. Enable Wi-fi, and you should be good.
I tested while running Wireshark and watched the bandwidth according to my Tomato router - no more huge files being downloaded.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DroidWall : https://market.android.com/details?id=com.googlecode.droidwall.free
or : http://code.google.com/p/droidwall/
source : http://gizmodo.com/5870339/how-to-keep-your-kindle-fire-rooted-and-update+free

Has your log of the app shown you anything?

Where does it log to?

This works if you rename OTASilentInstall.apk to OTASilentInstall.apk.bak and apply the rooted 6.2.1 update. NOTE when you apply the update you have to rename the apk again.
Sent from my still rooted Kindle Fire using xda premium

jb0ne said:
Where does it log to?
Click to expand...
Click to collapse
the app has a log file you can turn on. You view it via the app under more in settings of the app.
http://i.imgur.com/sRDb6.jpg

zirooo said:
new method (not confirmed yet i think)
Kindle Fire 6.2.1 breaks root and you cannot re-root. To prevent this, simply install DroidWall. If you are afraid of downloading the update and want to keep wifi disabled, just do a google search for Droidwall.apk and sideload.
Once installed, launch Droidwall. Make sure the mode says "Mode: White list (allow selected). You will have to manually select which apps to give Wifi access to (I selected Email, Browser, Netflix, and Amazon Video on Demand). You should only select the apps you REALLY want to give access to. Then hit Menu and Apply Rules. Enable Wi-fi, and you should be good.
I tested while running Wireshark and watched the bandwidth according to my Tomato router - no more huge files being downloaded.
DroidWall : https://market.android.com/details?id=com.googlecode.droidwall.free
or : http://code.google.com/p/droidwall/
source : http://gizmodo.com/5870339/how-to-keep-your-kindle-fire-rooted-and-update+free
Click to expand...
Click to collapse
Hi, but just wanted to confirm will this work or will it still update??
Has anyone tried this?

icebuck said:
Hi, but just wanted to confirm will this work or will it still update??
Has anyone tried this?
Click to expand...
Click to collapse
I was using the Droidwall method all day yesterday and today only allowing Netflix, Youtube, Pandora, Spotify, Onlive, Dolphin HD and Market Place wifi access and Just a few minutes ago my kindle was attempting to download and install the update while I was pushing a few apps and I did adb reboot and before it could finish and I'm still at 6.2 but now I've just disabled all wifi access which sucks.

dev/null/ said:
I was using the Droidwall method all day yesterday and today only allowing Netflix, Youtube, Pandora, Spotify, Onlive, Dolphin HD and Market Place wifi access and Just a few minutes ago my kindle was attempting to download and install the update while I was pushing a few apps and I did adb reboot and before it could finish and I'm still at 6.2 but now I've just disabled all wifi access which sucks.
Click to expand...
Click to collapse
Same err...My WiFi is off.
Until some solid solution is found to stop these forced updates.

Rooting Kindle Fire HD - continually fails

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.

[ROOT] [How To] Root Amazon 7" Kindle Fire HD Version 7.4.7

I'll Show You How To Root Your Amazon 7" Kindle Fire HD In Version 7.4.7 (This Also Works For Older Versions) With The Bin4ry Method.
Step By Step Instructions:
- Step 1: Download The View attachment Root_with_Restore_by_Bin4ry_v33.zip.
- Step 2: Extract The File.
- Step 3: This Step Is Very Important. Uninstall Any Drivers You Have For The Kindle Fire HD. Connect Your Kindle To The PC Via USB. Press The Windows Start Button And Search "Device Manager" Go to >Portable Devices. "Right Click" On Kindle And Choose "Properties". Go to "Driver" and Click "Uninstall". Then Unplug the Kindle From the PC.
- Step 4: Now Download And Install Kindle Fire ADB Drivers. (Dropox Link) (Google Drive Link)
- Step 5: Now On your Kindle Fire HD Go To "Settings" Then >Security. Mark "Enable ADB" - ON.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- Step 6: Connect The Kindle Fire HD To The PC Via USB. Wait Till Automatic Installation Completes And Kindle is Recognized.
- Step 7: Navigate To The Folder Where You Extracted The Bin4ry Method And "Double Click" the "RunMe.bat" File And Choose Option 1.
View attachment 2118382
- Step 8: On The Kindle Fire HD Select The Option "Backup My Data" And Wait Till The Backup Completes (When The Backup Completes, On The Computer Press Any Key). Then Select The Option "Restore My Data" (This Will Not Erase Any Data Or Files) And Wait Till The Restore Completes (When The Restore Completes, On The Computer Press Any Key).
- Step 9: Your Device Will Reboot. When The Kindle Boot The First Time (It Will Be Sluggish), Unlock It And Wait The Other Reboot.
- Step 10: When Your Device Boot Select Select The Option "Restore My Data" Once Again (This Will Not Erase Any Data Or Files) And Wait Till The Restore Completes (When The Restore Completes, On The Computer Press Any Key). Your Device Will Reboot Once Again.
- Step 11: When Your Device Boot, Unlock Your Device And Go To "Apps Drawer", You Should See The "Superuser" App.
You're Done!
Now Your Amazon Kindle Fire HD Has Root Access.

I had a rooted 7.4.2 having used Bin4ry the first time. I was sure I had disabled OTA updates. Anyway I now have 7.4.3 unrooted.
Is it safe to use this method in the above scenario or is it for vanilla unrooted 7.4.3 machines that weren't prior rooted ?
thanks in advance

It's Safe
Yeah It's Safe. Use The Las Version Of The Bin4ry Method

Keep getting the same error message
I keep getting this message while running Bin4ry "RunMe"
"could not find C:\User\Home\Download\Root_with_Restore_by_Bin4ry_v31\ric"
Anyone know what this error message means? I am trying to root a kindle Fire HD with 7.4.3. All other steps go as described until It resets and I unlock it the first time. Then the error message comes onto the cmd.exe
Any help would be appreciated.

avmann11011 said:
I keep getting this message while running Bin4ry "RunMe"
"could not find C:\User\Home\Download\Root_with_Restore_by_Bin4ry_v31\ric"
Anyone know what this error message means? I am trying to root a kindle Fire HD with 7.4.3. All other steps go as described until It resets and I unlock it the first time. Then the error message comes onto the cmd.exe
Any help would be appreciated.
Click to expand...
Click to collapse
I've used this on a Kindle Fire HD 7* with 7.4.3 as well. I assume you chose option #1, New Standard root?
It looks like it gets stuck when it tries to delete the non-existent ric file (towards the end of the batch file under the "newstandard" section). It should just continue onwards though. Does the batch file kick you back out into the command prompt directly?
Another thing to try - I don't think this is necessary, but it's easy enough to try - run the batch file as Windows administrator.

once i root my 7.4.3 kindle, i can flash any rom? also do i need to do the Bootloader + TWRP things?

BenCf said:
once i root my 7.4.3 kindle, i can flash any rom? also do i need to do the Bootloader + TWRP things?
Click to expand...
Click to collapse
Once you root your Kindle, you can install things like the Google Apps framework and the Google Play store, which gives you access to a large number of other applications.
However, you'd still need to separately flash the bootloader and TWRP if you wish to install secondary ROMs. For those steps, please see the individual threads. Make sure you've made backups of your existing factory ROMs (system.img, boot.img, and recovery.img) and pick up a factory cable (aka fastboot)...

I can't make it work
Hey,
I cannot make it work. I tried from two different computers and I keep getting this error message, please help it's a Kindle Fire HD 7" firmware 7.4.3
RCamacho50 said:
You Can Root Your Amazon 7" Kindle Fire HD In Version 7.4.3 With The Bin4ry Method.
Step By Step Instructions:
- Step 1: Download The View attachment 2092604.
- Step 2: Extract The File.
- Step 3: This Step Is Very Important. Uninstall Any Drivers You Have For The Kindle Fire HD. Connect Your Kindle To The PC Via USB. Press The Windows Start Button And Search "Device Manager" Go to >Portable Devices. "Right Click" On Kindle And Choose "Properties". Go to "Driver" and Click "Uninstall". Then Unplug the Kindle From the PC.
- Step 4: Now Download And Install Kindle Fire ADB Drivers. (Dropox Link) (Google Drive Link)
- Step 5: Now On your Kindle Fire HD Go To "Settings" Then >Security. Mark "Enable ADB" - ON.
View attachment 2095941
- Step 6: Connect The Kindle Fire HD To The PC Via USB. Wait Till Automatic Installation Completes And Kindle is Recognized.
- Step 7: Navigate To The Folder Where You Extracted The Bin4ry Method And "Double Click" the "RunMe.bat" File And Choose Option 1.
View attachment 2118382
- Step 8: On The Kindle Fire HD Select The Option "Backup My Data" And Wait Till The Backup Completes (When The Backup Completes, On The Computer Press Any Key). Then Select The Option "Restore My Data" (This Will Not Erase Any Data Or Files) And Wait Till The Restore Completes (When The Restore Completes, On The Computer Press Any Key).
View attachment 2095943 View attachment 2095944
- Step 9: Your Device Will Reboot 2 Times.
- Step 10: When Your Device Boot Select Select The Option "Restore My Data" Once Again (This Will Not Erase Any Data Or Files) And Wait Till The Restore Completes (When The Restore Completes, On The Computer Press Any Key). Your Device Will Reboot Once Again.
View attachment 2095944
- Step 11: When Your Device Boot, Unlock Your Device And Go To "Apps Drawer", You Should See The "Superuser" App.
View attachment 2095946
You're Done!
Now Your Amazon Kindle Fire HD Has Root Access.
Click to expand...
Click to collapse

nice, thanks for the guide!

Thanks a lot it worked without any issue.
Cheers Fidi

#su here!
Thanks it worked like a charm...Next Step!!

Root with restore ( Bin4ry) works with the new 7.4.6 update.

Flawless root on windows 7 box of kindle fire hd 7".
I ordered one last night on amazon, was here this morning. Was on 7.3.1 when I got it, as soon as the battery hit full it updated itself to 7.4.6
I confirm root prompt in adb shell from that windows 7 box and superuser in the app drawer on 7.4.6
Thanks!

7.4.6
This method worked perfectly with the latest Amazon OS 7.4.6. Going to try to install 2nd bootloader and CM10.1...we'll see how that goes.

mpkothari said:
This method worked perfectly with the latest Amazon OS 7.4.6. Going to try to install 2nd bootloader and CM10.1...we'll see how that goes.
Click to expand...
Click to collapse
Let me know if it worked! I am hesitating to try without downgrading the Kindle os.

awesome
rooted in less than 3 minutes. thanks RCamacho50 for the full informative guidelines .

Questions
1. My kindle hd 7" is rooted using kkfa for 7.4.3. Can I still use this method to re-root?
2. If OTA has been turned off thru kkfa, is there a way to install the new update? Will installing the new update cancel out all my apps or mess up anything that was done with the kkfa root in 7.4.3?
Sent from my BNTV600 using Tapatalk 2

Thank you for the great guide! I was able to root my kindle and install the Google Play store without any issues, but now my Kindle app won't work. I found another thread that advised to go to the Kindle app in the Play store and choose uninstall to role back to the previous version, but I don't have this option. It just has Open, no Uninstall.
Any suggestions?

Piece of cake.
Root is in the house!

cant install
I keep getting error cannot copy. After backup I hit any key and kindle restarts without letting me restore. If i restore after restart I get error and program quits? Need some help. Device manager only says kindle not adb. I have uninstalled and reinstalled drivers same issue.
---------- Post added at 01:44 PM ---------- Previous post was at 01:14 PM ----------
ok ran setup on another pc and worked! I was running mac with vm win7.

[SOLVED] Win7/8 ADB Driver - VZW G2

FYI this is solved.
1. Install drivers can be found here: http://d-h.st/fBw or when you first plug your phone into PC, within the virtual drive: \tools\LG VZW_United_WHQL_v2.11.1.msi file
2. Next make sure to switch to Internet connection --- ethernet within PC Connection settings
3. command prompt and type adb devices, you should see your Serial Number and online.
4 Now that we know ADB is working the process is the same, download this: http://www.mgyun.com/vroot
5. Yes it is in chinese, install it, then run it while your phone is plugged into your USB port on your PC.
6, The program will do some checks once its finished it will pop a screen that has the model number of the phone LG-D800 and a check mark. Notice the button on the bottom right, it says ROOT with some chinese lettering.
7. Click it and wait, the phone will reboot after a couple minutes. Once it reboots you will be rooted. Also it will install a Chinese language Root Manager. This is temporary.
8. Now we will replace the Chinese binary with an English one. Download superuser by clockworkmod from the play store. Open it and grant root permission (right button when the window pops up in Chinese). Superuser will ask to update the binary, hit install. Now exit by swiping superuser out of recents.
9. Now open titanium backup, install from play store if you don't have it. Find the Chinese root manager app and either uninstall it or freeze it.
10. Next open superuser again and once again install the superuser binary when asked. Reboot. You should now be rooted in English.
11. Optionally you can install Busybox with Busybox installer like I did.
Initially this did not work for me....i had to take the below steps to get it to work.
After rooting with app and installing CWM superuser
-open CWM SU
-allow root
-update binaries
-go to settings -> app manager -> select cwm su and force close it (do not just swipe it away in recents)
-open titanium bu and freeze the chinese version
-open cwm su again and update binaries again
-reboot
-open titanium and uninstall the chinese version
Original Question:
Does anyone have adb properly detecting their VZW G2 on Windows 8? Windows 8 is using a driver that is built into Win8, and I haven't found a way to get ADB working because of it. It shows up and works fine as an MTP device, and in device manager (as seen below). If anyone gets this working please let me know what you did.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Have you tried the ones on LG's site?
http://algmcdn.lgmobile.com/dn/downloader.dev?fileKey=UW00120120425

Huskehn said:
Have you tried the ones on LG's site?
http://algmcdn.lgmobile.com/dn/downloader.dev?fileKey=UW00120120425
Click to expand...
Click to collapse
I can't even get it to see my device on windows 7...not sure you're going to get far at the moment.

Yea i've tried the drivers from LG's site and the drivers that come on the phone itself. Definitely no luck so far.

Darkestred said:
I can't even get it to see my device on windows 7...not sure you're going to get far at the moment.
Click to expand...
Click to collapse
Same here. With Dev. Options and ADB enabled, nothing shows on Windows 7 (I'm assuming all versions of Windows). It would seem to me that there is a software issue and VZW needs to give us an update ASAP. This is total bull. I'm a developer and I want to use my phone to develop, that is one of the key points of Android.

drkow19 said:
Same here. With Dev. Options and ADB enabled, nothing shows on Windows 7 (I'm assuming all versions of Windows). It would seem to me that there is a software issue and VZW needs to give us an update ASAP. This is total bull. I'm a developer and I want to use my phone to develop, that is one of the key points of Android.
Click to expand...
Click to collapse
Software update would probably break current root method though sadly.

bose301s said:
Software update would probably break current root method though sadly.
Click to expand...
Click to collapse
ADB > root! ADB is usually essential to achieve root anyway.

It turns out this seems to be an issue with the Verizon G2 not actually enabling USB Debugging mode when it's checked. Refer to the thread below.
http://forum.xda-developers.com/showthread.php?p=45556319

emplox said:
It turns out this seems to be an issue with the Verizon G2 not actually enabling USB Debugging mode when it's checked. Refer to the thread below.
http://forum.xda-developers.com/showthread.php?p=45556319
Click to expand...
Click to collapse
This sucks, now we wait for a software update... without the ability to use ADB or any way to fix it. Oh well, worse things have happened.

I just got off the phone with LG. They specifically told me that there are no drivers that currently work on the VZW G2 and they should have the released 'in less than a week' and it should solve all ADB issues. Not sure I believe it...but I guess we'll see.

emplox said:
Does anyone have adb properly detecting their VZW G2 on Windows 8? Windows 8 is using a driver that is built into Win8, and I haven't found a way to get ADB working because of it. It shows up and works fine as an MTP device, and in device manager (as seen below). If anyone gets this working please let me know what you did.
Click to expand...
Click to collapse
Can you right click the device in Device Manager, then click Properties.
I think the answer is in the Details tab, if you drop down the Property list and choose Hardware IDs.
I have a feeling the ID in there (for the VZW variant) is NOT in the driver installation file from LG (yet, anyway)

chrisexv6 said:
Can you right click the device in Device Manager, then click Properties.
I think the answer is in the Details tab, if you drop down the Property list and choose Hardware IDs.
I have a feeling the ID in there (for the VZW variant) is NOT in the driver installation file from LG (yet, anyway)
Click to expand...
Click to collapse
FYI this is solved.
1. Install drivers can be found here: http://d-h.st/fBw or when you first plug your phone into PC, within the virtual drive: \tools\LG VZW_United_WHQL_v2.11.1.msi file
2. Next make sure to switch to Internet connection --- ethernet within PC Connection settings
3. command prompt and type adb devices, you should see your Serial Number and online.
4 Now that we know ADB is working the process is the same, download this: http://www.mgyun.com/vroot
5. Yes it is in chinese, install it, then run it while your phone is plugged into your USB port on your PC.
6, The program will do some checks once its finished it will pop a screen that has the model number of the phone LG-D800 and a check mark. Notice the button on the bottom right, it says ROOT with some chinese lettering.
7. Click it and wait, the phone will reboot after a couple minutes. Once it reboots you will be rooted. Also it will install a Chinese language Root Manager. This is temporary.
8. Now we will replace the Chinese binary with an English one. Download superuser by clockworkmod from the play store. Open it and grant root permission (right button when the window pops up in Chinese). Superuser will ask to update the binary, hit install. Now exit by swiping superuser out of recents.
9. Now open titanium backup, install from play store if you don't have it. Find the Chinese root manager app and either uninstall it or freeze it.
10. Next open superuser again and once again install the superuser binary when asked. Reboot. You should now be rooted in English.
11. Optionally you can install Busybox with Busybox installer like I did.
Initially this did not work for me....i had to take the below steps to get it to work.
After rooting with app and installing CWM superuser
-open CWM SU
-allow root
-update binaries
-go to settings -> app manager -> select cwm su and force close it (do not just swipe it away in recents)
-open titanium bu and freeze the chinese version
-open cwm su again and update binaries again
-reboot
-open titanium and uninstall the chinese version

ok i'm having issues with getting adb to find my device and this is an old thread and the chinese root wasn't working right. anyway to get the phone to list in adb yet, not using the chinese method?
Edit: could drivers from my previous phone have anything to do with this?
Edit2: Still could use an answer just in case, but i just realized that i haven't had to use adb on a device since before 4.2.2 so i possibly need to update my abd from pdanet, so i'll give that a go later tonight. but any other help would be appreciated. thanks in advance

drkow19 said:
Same here. With Dev. Options and ADB enabled, nothing shows on Windows 7 (I'm assuming all versions of Windows). It would seem to me that there is a software issue and VZW needs to give us an update ASAP. This is total bull. I'm a developer and I want to use my phone to develop, that is one of the key points of Android.
Click to expand...
Click to collapse
I have the T-Mobile G2 and have the same issue, my PC won't recognize the device. Wth?!?
Sent from my LG-D801 using xda app-developers app

bigox said:
I have the T-Mobile G2 and have the same issue, my PC won't recognize the device. Wth?!?
Sent from my LG-D801 using xda app-developers app
Click to expand...
Click to collapse
We figured out how to enable ADB a while ago. You need to plug in your phone to PC, select Internet then Ethernet (or something similar) instead of Media Sync or Charge Only. Also ADB must be enabled in Settings. Then, it should show in PC devices, you can install the Google ADB driver, and use ADB. First time using it, your phone should pop up with an RSA key window to allow ADB.

1. Install drivers can be found here: http://d-h.st/fBw
downloaded this file but i dont see how to install it. no .exe or anything
how do i install drivers? http://i.imgur.com/J5dax87.png
thanks
emplox said:
FYI this is solved.
1. Install drivers can be found here: http://d-h.st/fBw or when you first plug your phone into PC, within the virtual drive: \tools\LG VZW_United_WHQL_v2.11.1.msi file
2. Next make sure to switch to Internet connection --- ethernet within PC Connection settings
3. command prompt and type adb devices, you should see your Serial Number and online.
4 Now that we know ADB is working the process is the same, download this: http://www.mgyun.com/vroot
5. Yes it is in chinese, install it, then run it while your phone is plugged into your USB port on your PC.
6, The program will do some checks once its finished it will pop a screen that has the model number of the phone LG-D800 and a check mark. Notice the button on the bottom right, it says ROOT with some chinese lettering.
7. Click it and wait, the phone will reboot after a couple minutes. Once it reboots you will be rooted. Also it will install a Chinese language Root Manager. This is temporary.
8. Now we will replace the Chinese binary with an English one. Download superuser by clockworkmod from the play store. Open it and grant root permission (right button when the window pops up in Chinese). Superuser will ask to update the binary, hit install. Now exit by swiping superuser out of recents.
9. Now open titanium backup, install from play store if you don't have it. Find the Chinese root manager app and either uninstall it or freeze it.
10. Next open superuser again and once again install the superuser binary when asked. Reboot. You should now be rooted in English.
11. Optionally you can install Busybox with Busybox installer like I did.
Initially this did not work for me....i had to take the below steps to get it to work.
After rooting with app and installing CWM superuser
-open CWM SU
-allow root
-update binaries
-go to settings -> app manager -> select cwm su and force close it (do not just swipe it away in recents)
-open titanium bu and freeze the chinese version
-open cwm su again and update binaries again
-reboot
-open titanium and uninstall the chinese version
Click to expand...
Click to collapse

Having the same problem
I have the Verizon phone and tried using the 3.1.1 driver on Windows 7 (latest driver linked on the rooting post). When I went to the LG website and downloaded the 2.11.1 driver there, everything worked perfectly and I can see the phone on the PC using ADB devices command.

question:
emplox said:
FYI this is solved.
1. Install drivers can be found here: http://d-h.st/fBw or when you first plug your phone into PC, within the virtual drive: \tools\LG VZW_United_WHQL_v2.11.1.msi file
2. Next make sure to switch to Internet connection --- ethernet within PC Connection settings
3. command prompt and type adb devices, you should see your Serial Number and online.
4 Now that we know ADB is working the process is the same, download this: http://www.mgyun.com/vroot
5. Yes it is in chinese, install it, then run it while your phone is plugged into your USB port on your PC.
6, The program will do some checks once its finished it will pop a screen that has the model number of the phone LG-D800 and a check mark. Notice the button on the bottom right, it says ROOT with some chinese lettering.
7. Click it and wait, the phone will reboot after a couple minutes. Once it reboots you will be rooted. Also it will install a Chinese language Root Manager. This is temporary.
8. Now we will replace the Chinese binary with an English one. Download superuser by clockworkmod from the play store. Open it and grant root permission (right button when the window pops up in Chinese). Superuser will ask to update the binary, hit install. Now exit by swiping superuser out of recents.
9. Now open titanium backup, install from play store if you don't have it. Find the Chinese root manager app and either uninstall it or freeze it.
10. Next open superuser again and once again install the superuser binary when asked. Reboot. You should now be rooted in English.
11. Optionally you can install Busybox with Busybox installer like I did.
Initially this did not work for me....i had to take the below steps to get it to work.
After rooting with app and installing CWM superuser
-open CWM SU
-allow root
-update binaries
-go to settings -> app manager -> select cwm su and force close it (do not just swipe it away in recents)
-open titanium bu and freeze the chinese version
-open cwm su again and update binaries again
-reboot
-open titanium and uninstall the chinese version
Original Question:
Does anyone have adb properly detecting their VZW G2 on Windows 8? Windows 8 is using a driver that is built into Win8, and I haven't found a way to get ADB working because of it. It shows up and works fine as an MTP device, and in device manager (as seen below). If anyone gets this working please let me know what you did.
Click to expand...
Click to collapse
will this work for d800 d80010o?

does this ( VZW LG G2 Drivers) work for at&t g2 also?

It will works for Sprint LS980?

Root method likely possible via modified Binary method...

sa·yo·na·ra
ˌsīəˈnärə/

GSLEON3 said:
ABSOLUTELY DO NOT, DO NOT TRY THIS IS WILL LIKELY BRICK YOUR DEVICE!!!
Ok, so I have been able to confirm that using a modified Sony Xperia script, the Binary Root Mothod is able to initiate a desktop restore. HOWEVER, I am woefully unfamiliar with Kindle devices & I have not had time to study the partition structure, so I went no further than initiating the Desktop Full Data Restore mode on the HDX 8.9.
Based on what I have seen thus far, I do believe that root will be possible using existing Binary methods once a HDX desktop backup can be properly modified for these devices. The standard Kindle restore leaves the accept or cancel buttons grayed out. However, as you can see in the attached picture, using a modified version based on a Sony script, allows for the restore selection to be made.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Once I have some time, I will see what I can learn about the method Binary uses & see what files are currently included in previous Binary method backup files. In all likelihood, the root process will remain the same for the Kindle line as previous versions. At this time however, unless you know what you are doing, leave well enough alone & lets see what @Hashcode thinks.
Click to expand...
Click to collapse
Just wanted to say thanks for helping the cause.

GSLEON3 said:
ABSOLUTELY DO NOT, DO NOT TRY THIS IS WILL LIKELY BRICK YOUR DEVICE!!!
Ok, so I have been able to confirm that using a modified Sony Xperia script, the Binary Root Mothod is able to initiate a desktop restore. HOWEVER, I am woefully unfamiliar with Kindle devices & I have not had time to study the partition structure, so I went no further than initiating the Desktop Full Data Restore mode on the HDX 8.9.
Based on what I have seen thus far, I do believe that root will be possible using existing Binary methods once a HDX desktop backup can be properly modified for these devices. The standard Kindle restore leaves the accept or cancel buttons grayed out. However, as you can see in the attached picture, using a modified version based on a Sony script, allows for the restore selection to be made.
Once I have some time, I will see what I can learn about the method Binary uses & see what files are currently included in previous Binary method backup files. In all likelihood, the root process will remain the same for the Kindle line as previous versions. At this time however, unless you know what you are doing, leave well enough alone & lets see what @Hashcode thinks.
Click to expand...
Click to collapse
Well at least things are moving here. It's been so sad seeing no development on this thread. I have the KF HDX 7" and willing to offer mine for testing. I've been itching to see at a least root. I also did run the Bin4ry method and the restore reboots but doesn't do anything else.

Really? Unless that's new with the hdx, any backup/restore should work fine. Even if its files are corrupt.
Sent from my KFTT using xda app-developers app

Are you SURE? You know EXACTLY what is pushed in the desktop restore?
I am not familiar with KF Binary or First Aide backup/restore methods, but unless Binary is solely adding the necessary files for root, that could be disastrous. I find it hard to believe that is the case, considering how badly display & performance are affected during the previous HD versions desktop restore methods.
Sent from my Nexus 7 using XDA Premium HD app

GSLEON3 said:
Are you SURE? You know EXACTLY what is pushed in the desktop restore?
I am not familiar with KF Binary or First Aide backup/restore methods, but unless Binary is solely adding the necessary files for root, that could be disastrous. I find it hard to believe that is the case, considering how badly display & performance are affected during the previous HD versions desktop restore methods.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I have manually corrupted files and was able to send them to the device just fine. The restore option was not grayed out, but when you hit that button, it does nothing and just does not restore the data.
Sent from my KFTT using xda app-developers app

r3pwn said:
I have manually corrupted files and was able to send them to the device just fine. The restore option was not grayed out, but when you hit that button, it does nothing and just does not restore the data.
Sent from my KFTT using xda app-developers app
Click to expand...
Click to collapse
Be careful. I can tell you that I was at one point able to get the SU binary into a temp folder & copied into xbin, however, when I tried to get bb over as well, the device rebooted & I have not been able to get any ADB connection since. I have reset & removed devices, used different pc's & even factory reset the HDX. After four hours I cannot get any ADB access period.

You try using a terminal on the kindle and manually restarting the adbd service? I'm not aware of if you need root access to do so but maybe you can get some debugging output or just get it working in general by tinkering with this. For reference try something like
Code:
stop adbd
start adbd
Edit: also at this point you technically are rooted, I'm not sure if u have to have an apk to interface with the su binary, but after trying to help my friend root his Alcatel phone (don't get me started), the thing is rooted but while trying to get it switched from using supersu to superuser I believed superuser isn't functioning but we still have root access, and I don't believed superuser is in the/system/app directory, so point being, if u can sideload superuser and es file explorer you might be able to fix the situation if busy box caused the problems.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

good to hear this, hope the rooting method coming out soon!

stunts513 said:
You try using a terminal on the kindle and manually restarting the adbd service? I'm not aware of if you need root access to do so but maybe you can get some debugging output or just get it working in general by tinkering with this. For reference try something like
Code:
stop adbd
start adbd
Edit: also at this point you technically are rooted, I'm not sure if u have to have an apk to interface with the su binary, but after trying to help my friend root his Alcatel phone (don't get me started), the thing is rooted but while trying to get it switched from using supersu to superuser I believed superuser isn't functioning but we still have root access, and I don't believed superuser is in the/system/app directory, so point being, if u can sideload superuser and es file explorer you might be able to fix the situation if busy box caused the problems.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Yeah, I've tried just about everything I've ever seen or done to resolve abd issues since 2007. Still a no go. Going to give usb otg a try. Otherwise it's RMA & start over. While the SU binary is in place, I still cannot access it. Calls to SU or trying to open the SU app cause an instantaneous FC & reboot.
I'll tell you though, I really like the tablet. Awesome display & the SD800 w/Adreno 330 flat out rocks. This is totally what the Nexus 10 should have been.
I've also been able to determine that Motorola is the OEM. There are Motorola backup files native to the device at least. I am also going to run this weekend & pick up a 1k transistor, to make a Motorola factory fastboot cable, since I gave mine away with an Xperia tablet. With the factory cable, I should be able to issue fastboot commands. That may enable me to devise a BL unlock.

GSLEON3 said:
Be careful. I can tell you that I was at one point able to get the SU binary into a temp folder & copied into xbin, however, when I tried to get bb over as well, the device rebooted & I have not been able to get any ADB connection since. I have reset & removed devices, used different pc's & even factory reset the HDX. After four hours I cannot get any ADB access period.
Click to expand...
Click to collapse
How are you sure that you got it into xbin?
Sent from my iPod touch using Tapatalk