hi guys im getting anoyed with my pc and phone now ive followed so meany tutorial etc on how to install adb but still not getting any where so far i have done
1. downloaded sdk from code.google.com
2. extracted to c:/android-sdk-windows
3.installed htc wildfire drivers
4.created a path on enviromentable variuble
5.ive loaded the skd.exe
6. ran cmd and ran adb and adb devices but my pc will not reconise this command any adice please thanks
ps ive also tryed using qtaADB it connect to the phone but dnt show any thing frustrated now lol thanks daddyspud
First download adb for windows from " http://developer.android.com/sdk/ ".
then u will get a file named " android-sdk_r08-windows ".rename it as "Android SDK" after extracting.
download proper driver for your phone and install them .now move "Android SDK" to root of hard drive that is to c\Android SDK...
now update the adb using SDK manager that is inside Android SDK.all packeges even usb drivers.
connect the phone via usb and windows should recognize it as android phone .
now take "cmd".command prompt and type the following code .
cd\
cd Android SDK\tools\
adb devices
Now Adb is set if it shows your phone code ..
Sorry about my english .
I had a hardtime making my computer recognize my wildfire, I had to manipulate the driver to make it find it. just google it and you shall find .. if thats the problem ..
thanks worked a dream cheers buddie
They changed the location of the adb.exe file with the new SDK release using the example given would be :-
cd\
cd Android SDK\platform-tools\
easier in my opinion to add to path in windows
c:\android sdk\platform-tools\adb.exe
make sure u add java.exe to path aswell
Hope this helps
ok i got that and it worked, ie picked up my device, then what do i do?
magpie22 said:
ok i got that and it worked, ie picked up my device, then what do i do?
Click to expand...
Click to collapse
Well what do you want to do with adb?
run the sdk but i get errors when i start it "error 2" cant find file.
Failed to get the adb version.
Edit - Never mind i have sorted it.
I've seen a few posts mentioned how easy using adbWireless app, instead of using USB. However, I've tried and never work. I don't now why people saying it's easy or simple to use, based on different of definition of "easy"
On the NC side, it asked to "adb connect 192.168.xx.yyyy:5555"
I typed that on the Command Prompt on PC running W7, always get "adb is not recognized as an internal or external command, operable program or patch file."
Am I missing something here?
Thought I must need to get the SDK installed, I follow this link:
http://www.androidcentral.com/sdk-driver-root-oh-my
In that instructions of Step 1, the author said "Unzip the download with your favorite archiving tool and drag the folder you extracted into your Workspace. Don't open the folder, just drag the whole thing over. That's it. The Android SDK is now installed."
Is that true? That's it? no need to run any executable file? just drag the folder over and SDK suddenly get installed somehow? Really?
Any input is welcomed.
Ended up installing both SDK and usb driver.
Using adbWireless, cannot connect to it then suddenly it does, don't even know why or what I have done.
I'm start thinking the culprit is my laptop.
"adb devices" always returns with no devices regardless using adbWireless or USB cable.
Gotta tried on different computer.
Sounds like you need to CD to your tools folder in the sdk.
Sent from my LG Optimus V using Tapatalk
You bet.
I CD'ed to the "platform-tools" directory where the adb.exe resided.
Still nothing, even though trying on a different PC.
I guess I've followed the incorrect instructions or at least, an out-dated one.
votinh said:
You bet.
I CD'ed to the "platform-tools" directory where the adb.exe resided.
Still nothing, even though trying on a different PC.
I guess I've followed the incorrect instructions or at least, an out-dated one.
Click to expand...
Click to collapse
If you use adb connect ###.###.###.### (you only need ": port" if you change from default of 5555) then issue adb devices it should list the nook with its ip address as the device id after it is connected.
One thing to be aware of with adb wireless... if the nook is rebooted with it enabled... you will have to cycle adb wireless for it to work.
I actually tried to connect both with and without xx:5555
Hello everyone
Have you ever been bored in a borrowed pc and wanting to try out a new library/idea on your android but dont have admin privileges to install all the needed android tools? I was in this exact same situation, so i decided to engineer a solution (After all, i AM an engineering student ) to this boring problem. This solution works almost entirely like a standard Android SDK install (Only downside: Eclipse won't run your application) and has only been tested on Ubuntu Linux so you are on your own on other platforms, but the principle is the same, it might work after all.
Whenever prompted for a platform choose x86 , x64 needs ia32-libs which you cant install due to not having admin privileges
1. Create a directory for all the files and folders (I'll name mine "Development")
2. Download the JDK tar.bz file from http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1637583.html (You'd better search for an updated link when you read this tho) and extract it into Development
3. Download eclipse from http://eclipse.org/downloads/ (I used the Eclipse IDE for Java Developers) and extract it into the Development folder
4. Download the Android SDK from http://developer.android.com/sdk/index.html (If you are on windows, choose the zip!. Again, i've only tested on Linux so you are on your own) and extract it into the Development folder
5. Open the tools/android (It's a shell script) file with gedit/any other editor and edit the line containing java_cmd=".." to read java_cmd="/home/xxx/Development/jdk1.7.0_06/bin/java" (This is my case, make sure this line actually points to the place where you extracted the jdk zip, else this will fail)
6. Open a terminal, cd to the location where you extracted the android sdk, then type "./tools/android" and press enter (Without the quotation marks) to start the sdk manager, install the platform-tools package, the Jellybean (4.1) SDK, and any other SDK you may want, then close the SDK manager.
7. cd to the Development folder and run this "./eclipse/eclipse -vm jdk1.7.0_06/bin" (Assuming you kept the stock folder names from the zips) to run eclipse, then install the ADT as described here http://developer.android.com/sdk/installing/installing-adt.html.
8. When eclipse restarts, it will ask you for the android sdk, just point it to the location where you extracted it.
That's it, your eclipse installation is ready for you to write code.
Now, to debug you'll need to do so manually as eclipse won't somehow recognize this workaround to the usb priviliges (Linux won't allow adb to communicate with the phone unless it's ran as root [Which you can't, that's why you are here] or a configuration file [Again, written as root] is present) system so you need to do this to make adb work:
1. Disconnect your phone from 3G (Optional)
2. Connect your phone to your pc via usb
3. Enable usb tethering on your phone
4. Enable ADB over Network on Application settings
5. On the terminal emulator, run "ip addr show" and look for the usb section
6. On your computer, open a terminal and cd to the tools directory fo the android sdk, then type "./adb connect xxx.xxx.xxx.xxx" (Replace the x's with the IP of your phone, as it appears on the output of the previous command. Remember to use the one on the USB section)
7. Verify adb picked up your device by runing "./adb devices", if it lists an IP as a device, you are ready
Each time you want to test your app, export a signed apk from your project (I may write a small guide for that later, google will help you if you dont know how to do it) and run "./adb install xxx.apk" (Obviously, replace xxx with the path to your exported apk). The icon(s) for your main activity(ies) will promptly appear on your launcher. Again, Eclipse won't run nor debug your app using this method. (Maybe it's an SDK bug?)
I know it's not exactly streamlined but it's something for when you are on the go.
Hope you find this guide useful someday. Until next time.
This is a simple Step-by-Step guide on How To: How To: Root the Kindle Fire 7" HD, Kindle Fire HD 8.9" and Kindle Fire 2 with Windows - Noob (Simple) Version. The main group steps are outlined with A, B, C while the sub-group steps are outlined with 1, 2, 3. We attempt to keep this tutorial updated regularly - adding information from the end users experience. We have recently upgraded the storage servers to increase uptime, you now have two options for the downloads both are ad free. Option one is a Dropbox Storage Server and Option two is a Ubuntu One Storage Server, if one is under maintenance you may use the other download link. When you are done with the tutorial, please take the time to post feedback, this is very important to us - without your feedback, we have no way of knowing if we are doing our job. Finally, if you feel we did a decent job, please think about donating to us using the "Donate to Me" button - this is how we make a living, without your kind donations we would no longer be able to do this for a living.
Prerequisites:
1. Software: Windows XP, 7 or 8 Workstation 32bit or 64bit
2. Hardware: Free USB 2.0 or Greater Port
3. Kindle Fire HD 7", Kindle Fire HD 8.9" or Kindle Fire 2 7"
Note: Windows 7 and Vista users, please perform this fix before Rooting: http://forum.xda-developers.com/showthread.php?p=36373627
It is important that you use our Utilities since we have modified the ADB daemons plus we did little tweaks in some of the batch files. PLEASE USE OUR UTILITIES, WE ARE RECEIVING A NUMBER OF FAILURES CAUSED BY USING ANOTHER PARTIES UTILITIES. IF YOU FOLLOW THE STEPS BELOW, EXACTLY, YOU HAVE A 99% CHANCE OF SUCCESS.
Unplug the Kindle from USB.
A) Although the processes do not use Java directly, the software does call to some Java API's so we need to make sure Java is updated to the latest version. Please go to Oracle's site here: Java SE Development Kit 7u13 download and install Java SDK 32-bit or 64-bit. Reboot your computer after installing the Java update.
B) The first step is to get the ADB Driver installed. If you already performed this step and verified communication to the Kindle, move on to Main Step C
Note: Please remove any old or outdated drivers by following the instructions in Post #361 here: http://forum.xda-developers.com/showpost.php?p=37733595&postcount=361
The following ADB Driver was provided by Amazon and should install on most platforms (Windows XP, Vista, 7, and 8): Kindle Fire ADB drivers(Dropbox) or Kindle Fire ADB Drivers(Ubuntu One)
Note: Due to intermittent issues with the USB Drivers, we offer two versions. First try Kindle Fire ADB drivers.exe if this
does not open ADB Communication try the new updated KindleDrivers.exe
Please open an Administrative CMD Prompt and enter:
Code:
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
Reboot the Computer to apply the above command.
Extract the Kindle Fire ADB drivers.zip to your desktop.
1. Unzip Kindle Fire ADB drivers.zip to Kindle Fire ADB drivers on your desktop.
2. Click windows start button.
3. Next choose Search, in the "Search programs and files" box type "cmd" (don't hit enter or search).
4. The program "cmd.exe" should be listed at the top. Right click that and select "Run As Administrator".
5. Navigate to the Kindle Fire ADB drivers.exe or KindleDrivers.exe using the DOS Command cd.
6. Next, the install will begin, allow the install to complete.
7. While the driver is installing. Go to the Kindle unlock if locked.
8. Pull down the upper bar. Select "More".
9. Now Select the "Security" Tab.
10. In Security is an option to: Enable ADB
11. Select "On" to Enable ADB on the Kindle
If not, We have an alternative driver here: usb_driver(Dropbox) or usb_driver(Ubuntu One)
Extract the alternative driver to your desktop and follow the install instructions at the bottom of this response
The alternative driver originates from the Android SDK and is universal for just about any Android device.
The alternative driver instructions are for Windows XP but can be used with Windows 7 and Vista.
Once we get ADB installed then let's plugin the Kindle to your computer USB to see if it initializes properly.
Once this driver has been properly installed you will see "Android Composite ADB Interface" under "Kindle Fire" in the Windows Device Manager which is located by Right Hand Mouse Click Computer, Choose Properties, then Devices or Device Manager. Expand the tree. Expand Kindle. This is where you will see "Android Composite ADB Interface".
Amazon Notes regarding this ADB Driver can be found here: Amazon ADB Notes
ALTERNATIVE DRIVER INSTALL (Vista/XP/Windows7):
Windows XP
To install the Android USB driver on Windows XP for the first time:
1. Connect your Android-powered device to your computer's USB port. Windows will detect the device and launch the Hardware Update Wizard.
2. Select Install from a list or specific location and click Next.
3. Select Search for the best driver in these locations; un-check Search removable media; and check Include this location in the search.
4. Click Browse and locate the USB driver folder. (The Google USB Driver is located on your desktop \usb_driver\.)
5. Click Next to install the driver.
Or, to upgrade an existing Android USB driver on Windows XP with the new driver:
1. Connect your Android-powered device to your computer's USB port.
2. Right-click on My Computer from your desktop or Windows Explorer, and select Manage.
3. Select Device Manager in the left pane.
4. Locate and expand Android Phone in the right pane.
5. Right-click Android Composite ADB Interface and select Update Driver. This will launch the Hardware Update Wizard.
6. Select Install from a list or specific location and click Next.
7.Select Search for the best driver in these locations; un-check Search removable media; and check Include this location in the search.
8. Click Browse and locate the USB driver folder. (The Google USB Driver is located on your desktop \usb_driver\.)
9.Click Next to upgrade the driver.
C-1) The next steps are used to Root the Kindle - Preferred Method (Automated Version)
The problem "Device not Found" is usually driver related or ADB Security issue. Let's make sure ADB is enabled on the Kindle under Security - Enable ADB?
Open the Windows Task Manager. Review the Processes. "End Process" on any adb.exe running. If you installed the Android SDK, there is probably a PATH Statement pointing to the platform-tools folder. To avoid adb.exe start-up conflicts, temporarily rename the SDK platform-tools folder to platform-tools-temp.
Plug the Kindle back into USB if it is not already plugged into USB.
Root Step 1: Download Kindle Fire First Aide: Windows 32-bit Version Or Windows 64-bit Version
Root Step 2: Using either 7-Zip or Microsoft Zip, unzip the KFFirstAide.zip to your C:\ Drive as C:\KFFirstAide
Root Step 3: With your mouse, open the C:\KFFirstAide contents by double mouse clicking the C:\KFFirstAide folder
Root Step 4: Find the RunMe.bat file. Right Hand Mouse click on RunMe.bat, select 'Send to', select Desktop (Create Shortcut). Now press the Left Hand Mouse button to create the Shortcut named RunMe.bat.
Root Step 5: Find the RunMe Shortcut on your desktop, select it by left mouse click over the icon, then while on the icon choose Right Hand mouse click, select Properties.
Root Step 6: This will display the RunMe properties. Select the General Tab, change the top name to KF First Aide. Then click on the Shortcut tab, click on Advanced. Check 'Run as Administrator', click OK, then click Apply, then click OK. All windows should be closed.
Root Step 7: Double Mouse Click the new Icon named KF First Aide. You may be presented with a security window, just click Yes.
Root Step 8: Please click on the Windows Key plus Pause/Break, this will display the Windows System Properties. Next Click on the Advanced Tab and find "Environment Variables". Please click on Environment Variables and find the Path Statement. Carefully add at the end of the Path Statement:
Code:
;C:\KFFirstAide
Note: Do Not forget the semi-colen before the C:\KFFirstAide
Root Step 9: That is it! The software is ready. Next we get the Kindle ready to Root.
Root Step 10: Please check the Kindle under More + > Security - make sure ADB is ON. Leave it disconnected from USB.
Root Step 11: Launch Kindle Fire First Aide, if the ADB Driver is not installed, use Option 12 to Install the ADB Driver
Root Step 12: Make sure the Kindle is turned ON, plugged into the Computer USB and ready. Select Option 15 to Root the Kindle. If Option 15 fails to Root the Kindle, use Option 16.
Root Step 13: That is it! The Kindle now has Root, you may close the software.
You may view the Kindle Fire First Aide Forum Notes here: http://forum.xda-developers.com/show....php?t=2096888
C-2) The next steps are used to Root the Kindle - Alternative Method (Manual Version):
The problem "Device not Found" is usually driver related or ADB Security issue. Let's make sure ADB is enabled on the Kindle under Security - Enable ADB?
Open the Windows Task Manager. Review the Processes. "End Process" on any adb.exe running. If you installed the Android SDK, there is probably a PATH Statement pointing to the platform-tools folder. To avoid adb.exe start-up conflicts, temporarily rename the SDK platform-tools folder to platform-tools-temp.
Plug the Kindle back into USB if it is not already plugged into USB.
1. Download Root MANY ANDROID 32-bit!(Dropbox) or Root MANY ANDROID! 64-bit(Dropbox) to your desktop. Extract to your desktop. This package includes updated adb daemons.
NOTE WINDOWS 7 USERS: You need to open a command prompt "as Administrator" when running the above utility batch files RunMe.bat and RootQemu.bat - otherwise Windows will respond with "Permission Denied".
Make sure the Kindle is still plugged into USB.
Root Step 1: Run RunMe.bat from Root MANY ANDROID! through a command window as noted:
Double Mouse Click and Open the Win32 or Win64 folder.
Next Single Left Mouse Click on the Win32 or Win64 folder tool-bar.
This highlights the Win32 or Win64 folder.
Note: Make sure none of the files within the Win32 or Win64 are highlighted in blue.
Next Press the SHIFT Key, next Right Hand Mouse Click
Choose "Open command window here"
A Command window will open, finally type
Code:
RunMe.bat
Choose option 1, Run Normal Method and ignore errors. Pay attention, you will need to answer "Restore" a dialogue box on the Kindle. If you are asked for an 'encryption password', enter the password you use to sign onto Amazon. Click on Restore. When the program has completed, the Kindle will Reboot.
Root Step 2: When the Kindle reboots it may react VERY slow, this is normal - leave it alone. Immediately proceed to Step 1 again. If the Kindle reboot normally and appears normal, then proceed to Step 3 you are almost done.
Root Step 3: Download suchecker.apk from here: Root Checker Basic(Dropbox)
Root Step 4: Using Windows Explorer, move suchecker from the desktop to /Kindle/Internal Drive/Download
Root Step 5: Now go to the Kindle. Using ES File Explorer or Root Explorer, go to /sdcard/Download/suchecker.apk choose Install
Root Step 6: When the install has finished, go to your Apps. Launch Root Checker. When you check Root you will be presented with a "Allow" dialog box, be sure to Allow Root Checker. You should now see that Superuser.apk is working.
You should now have root AND if this is true your ADB communication is also functional.
D) Finally, let's disable the Amazon OTA (Over The Air) Updates so your hard work is not destroyed.
OTA Step 1: Open Kindle Fire First Aide - Select Option 14 to Disable OTA.
Note: You may still install the updates manually after you have read the install notes and know what to expect. The updates and manual install instructions can be found on Amazon Support here: http://www.amazon.com/gp/help/customer/display.html/ref=hp_left_sib?ie=UTF8&nodeId=201016350
E) Finally drop to an Administrative CMD and enter:
Code:
bcdedit -set loadoptions ENABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING OFF
Reboot the computer to apply the above command.
When you run Root Checker, the output should be similar to:
{
"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"
}
Next, move onto our How to: Install Google Play Step-by-Step Thread
:good::good::good::good::good:
how long is it suppose to stay at *daemon started successfully* ?
ADB Communication Issues
urbannerdmaeio said:
how long is it suppose to stay at *daemon started successfully* ?
Click to expand...
Click to collapse
Once you plug in the Kindle, it takes up to 2 minutes for Windows to detect it. So having said this *daemon started successfully*
Should not be displayed for longer than 2 minutes.
Where did you download the Utilities? From us or the developers? Our utilities use new updated adb.exe daemons
dated 11/05/2012 11:06AM
If the adb.exe has the correct date stamp, then make sure you are following our instructions on how to open a command
prompt. If you are following the instructions exactly then....
You must have Windows 7 which requires you to open an Administrative Prompt by choosing Run as: Administrator when
opening the CMD Shortcut.
Still nothing...
I downloaded the files from this thread, minus the ADB drivers because my computer already reads it under the device manager.
I go to the start menu, search for "cmd", run it as administrator and launch RunMe.bat from it
and it reads this to me
http[semi-colon]//s9.postimage.org/bpzs9w8u7/Untitled_1[dot]jpg
and nothing happens to the kindle, no message to restore and if i press any key on the command prompt it doesnt do anything either.
ADB Communication Issues
urbannerdmaeio said:
I downloaded the files from this thread, minus the ADB drivers because my computer already reads it under the device manager.
I go to the start menu, search for "cmd", run it as administrator and launch RunMe.bat from it
and it reads this to me
http[semi-colon]//s9.postimage.org/bpzs9w8u7/Untitled_1[dot]jpg
and nothing happens to the kindle, no message to restore and if i press any key on the command prompt it doesnt do anything either.
Click to expand...
Click to collapse
Please verify the date of the adb.exe daemons. Reply back with the date if the daemon in Root_with_Restore_by_Bin4ry_v17Root_with_Restore_by_Bin4ry_v17 Stuff folder.
Next download this mini-test utility: https://dl.dropbox.com/u/54456659/ADB%20Update.zip to your desktop
Unzip ADB Update.zip to your desktop
Open the ADB Update folder on your desktop
Make sure the Kindle is still plugged into USB.
Double Mouse Click and Open the ADB Update folder.
Next Single Left Mouse Click on the ADB Update folder toolbar.
This highlights the ADB Update folder.
Note: Make sure none of the files within the ADB Update are highlighted in blue.
Next Press the SHIFT Key, next Right Hand Mouse Click
Choose "Open command window here"
A Command window will open, finally type
Code:
adb kill-server
adb start-server
adb devices
Respond with the results.
Never mind
results...
http[semi-colon]//s7.postimage.org/md0uwbkij/Untitled_2[dot]jpg
and the date for the adb file matches the date you said it should be
urbannerdmaeio said:
http[semi-colon]//s7.postimage.org/md0uwbkij/Untitled_2[dot]jpg
and the date for the adb file matches the date you said it should be
Click to expand...
Click to collapse
I was getting the same results as you earlier. The mistake i made was that i believed my drivers were good too because my PC was reading the device under device manager. This ended up being a bad assumption. I deleted the drivers and installed the drivers that are found in the Qemu Zip folder. The drivers there worked perfectly.
I am rooted w/Play & thats what made the difference.
fiddystorms said:
I was getting the same results as you earlier. The mistake i made was that i believed my drivers were good too because my PC was reading the device under device manager. This ended up being a bad assumption. I deleted the drivers and installed the drivers that are found in the Qemu Zip folder. The drivers there worked perfectly.
I am rooted w/Play & thats what made the difference.
Click to expand...
Click to collapse
I've tried this several times, I keep getting the exact same problem regardless of where I get the drivers from, or what computer I use. I'm ready to pull out my hair...
ADB Communication Issues
urbannerdmaeio said:
http[semi-colon]//s7.postimage.org/md0uwbkij/Untitled_2[dot]jpg
and the date for the adb file matches the date you said it should be
Click to expand...
Click to collapse
There is a problem with ADB Communicating to the Kindle.
What platform are you using? Windows 7?
Are you sure ADB is enabled on the Kindle itself?
When you go into Windows device manager, do you see any Yellow Triangles over the devices?
In the device manager, do you see "Android Composite ADB Interface" or ?
ive already uninstalled and deleted the drivers, then installed the ones from the Quem folder and it gives me the same "drivers were not installed blah blah" message everyone else gets, and so i unplug then plug back in the kindle and my pc reinstalls the adb drivers....
try to root again, and nope, nothing.
heres a screen shot of my device manager (WINDOWS 7 x64)
http[semi-colon]//s14.postimage.org/6t9oytl5d/Untitled_3[dot]jpg
& yes im 100% positive ADB is on
Woop, finally got it rooted! Thanks for the noob guide and your patience.
One more question tho, I can't find where this path is: /system/ect/security/otacerts.zip
I'd rather not have amazon get rid of my rooting and wipe all my google play apps once I get that up and running.
ADB Communication Issues
urbannerdmaeio said:
ive already uninstalled and deleted the drivers, then installed the ones from the Quem folder and it gives me the same "drivers were not installed blah blah" message everyone else gets, and so i unplug then plug back in the kindle and my pc reinstalls the adb drivers....
try to root again, and nope, nothing.
heres a screen shot of my device manager (WINDOWS 7 x64)
http[semi-colon]//s14.postimage.org/6t9oytl5d/Untitled_3[dot]jpg
& yes im 100% positive ADB is on
Click to expand...
Click to collapse
OK, everything looks good with ADB. Looks like we have a pesky Windows 7 issue. Windows 7 Command prompt is only User level by default and will cause these utilities to fail.
If you go into Programs > Accessories or Programs > Accessories > System Tools do you see the Command Prompt? Now Right Hand Mouse click over the prompt and choose Run As Administrator
Once the Command Prompt is opened navigate to each utility using the "cd" "cd.." "cd c:\" etc command.
Once you navigate to the Root_with_Restore_by_Bin4ry_v17 folder, you will be able to successfully run the batch file through the Administrative prompt.
Thank you
Wow thank you for taking all of this time to put together a easy to follow guide in rooting the Kindle Fire HD. I plan to do this soon, just waiting on my scorpi0n cord, just incase I make a mistake. I am a total noob to android so I am looking forward to seeing some of the options with root. Again thank you
Follow Up
Jayj0ka said:
Wow thank you for taking all of this time to put together a easy to follow guide in rooting the Kindle Fire HD. I plan to do this soon, just waiting on my scorpi0n cord, just incase I make a mistake. I am a total noob to android so I am looking forward to seeing some of the options with root. Again thank you
Click to expand...
Click to collapse
Thank you for the feedback. We are here to support you.
We monitor the Threads closely from about 10AM PST to 10PM PST USA GMT -8 so if you get stuck we'll be here for you.
prokennexusa said:
This is a simple Step-by-Step guide on How To: Root the Kindle Fire 7" HD. The main group steps are outlined with A, B, C while the sub-group steps are outlined with 1, 2, 3.
Click to expand...
Click to collapse
Your guides are amazing can I request a how to backup and restore possibly, you offer so much information and support that really helps to break down and simplify the process for me.
Again thank you
Backup and Restore
Jayj0ka said:
Your guides are amazing can I request a how to backup and restore possibly, you offer so much information and support that really helps to break down and simplify the process for me.
Again thank you
Click to expand...
Click to collapse
Thank you for the feedback.
We are in the process of creating a How to: Backup and Restore the Kindle System Image
Give me 48 hours for this series. We are working on How to: How to: Install ICS Google Applications and Google Voice Noob (Easy) Version at the moment.
Hi, Excellent guide!
Will this work on Kindle Fire 2nd Gen (10.2.4)
Big thanks, all these How-To guides are great, bookmarked them all