[Q] ADB & TWRP Issue. - Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot

[Q] ADB & TWRP Issue. - Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot

Has anyone been successful using adb commands from TWRP recovery? I have been unsuccessful getting it to connect.

What's the problem?
Do you have the yellow exclamation point next to the Samsung_android device in the device manager?
What OS?
---------- Post added at 11:51 AM ---------- Previous post was at 11:29 AM ----------
Went ahead and did a quick write up. This is from memory so wording might not be exact, but if you're familiar with Windows XP, it shouldn't be too hard to follow along.
1) Go the the directory (your android sdk directory)\extras\google\usb_driver
2) Look for the file called "android_winusb.inf"
3) Open it with an editor (i used wordpad).
4) Right under the section labeled [Google.NTx86] I added the following line: %CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001 (I would cut and paste this for syntax accuracy) Look at the other lines in the file to make sure it looks right.
5) save the file.
6) Put your phone in recovery, plug it in to your computer and wait for windows to try and install the driver.
7) Select "Do not search, I will choose the driver" (I'm doing this from memory, so wording might not be exact)
8) Get to where you tell it you have the disk, and point it to the usb_driver directory/file listed above. It should install it now.
This worked for me on my work Windows XP laptop. My home computers are Windows 8, and everything installed just fine on it's own.

fgr said:
What's the problem?
Do you have the yellow exclamation point next to the Samsung_android device in the device manager?
What OS?
---------- Post added at 11:51 AM ---------- Previous post was at 11:29 AM ----------
Went ahead and did a quick write up. This is from memory so wording might not be exact, but if you're familiar with Windows XP, it shouldn't be too hard to follow along.
1) Go the the directory (your android sdk directory)\extras\google\usb_driver
2) Look for the file called "android_winusb.inf"
3) Open it with an editor (i used wordpad).
4) Right under the section labeled [Google.NTx86] I added the following line: %CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001 (I would cut and paste this for syntax accuracy) Look at the other lines in the file to make sure it looks right.
5) save the file.
6) Put your phone in recovery, plug it in to your computer and wait for windows to try and install the driver.
7) Select "Do not search, I will choose the driver" (I'm doing this from memory, so wording might not be exact)
8) Get to where you tell it you have the disk, and point it to the usb_driver directory/file listed above. It should install it now.
This worked for me on my work Windows XP laptop. My home computers are Windows 8, and everything installed just fine on it's own.
Click to expand...
Click to collapse
Running Win8 and driver is installed and was without issue. OS sees device and mounts storage. However, when in TWRP cannot see device in order to start shell. Want to make sure it is not a limitation of the S4 TWRP.

Gotcha,
I'm currently not running TWRP, but I was and don't recall having this problem.

Related

[STICKY][ROM] nvflash FULL restore, using bekit's original image (Instructions)

MANY THANKS TO REV FOR RE-WRITING THIS FOR ME!
(Post was updated on 3/23/2011)
=======================================
This post is to provide a template for using NVFlash to restore/recover your G-Tablet after suffering some kind of malfunction. Specifically, this document tries to provide ALL the information you need to use the NVFlash tool to recover the bekit 1105 software version, which has been found to be safe as a starting point for rebuilding your tablet after having a problem. This post does not include other methods of setting up NVFlash (such as installing the SDK, etc.) because this method is proven and can be easily supported.
I use Ubuntu Linux and know that the Linux instructions below are correct. Others have written Windows instructions and those too have been checked carefully and have been used before successfully.
A WARNING IN ADVANCE: NVFlash makes changes to the partition structure of your device. You should tread carefully and understand the risks. (MOD EDIT Note: It also has been noted a bunch of times that even NVFlashing your G-Tablet will not completely overwrite everything on it.)
The NVFlash setup process begins with a visit to:
http://db.tt/Wm25t7U
(Note: Sometime this DropBox is cranky. If you have trouble with it, check back later.)
Linux users: You want to get "nvflash_linux_2010110500.tar.gz" and "nvflash_gtablet_2010110500.zip "
Windows users: You want to get "nvflash_windows_20100500.zip" and ""nvflash_gtablet_2010110500.zip"
Note: The above "nvflash_gtablet_2010110500" is commonly referred to as bekit version 1105 in many posts relating to nvflashing (especially my posts).
-------------------------------------------
Installation
First, create a folder named "NVFlash" on your PC to put the needed files into and to work from. (Note: You can call it something else if you want to; we're just using "NVFlash" to keep all of us on the same page.)
Next, extract the files you downloaded from the DropBox above into the "NVFlash" directory. The files with linux and windows in the middle of then are the files for setting up NVFlash. (The are taken from the SDK and do not install the whole SDK -- just a simple, operable NVFlash for us to use here.) The files with gTablet in the middle contains the .img files with the software to go on your G-Tablet.
Third, for Windows users, you'll need to have an APX-specific USB driver for the next steps. (The Windows package bekit supplied has an .inf file in it, but the actual drivers are not there). For Linux users, you don't need an extra driver.
One source for the Windows drivers is at
http://www.myadventvega.co.uk/
Find the "Downloads" tab in the middle of the page and click on "USB System Driver" to get the files. Extract them and go down two levels to the "USB" folder -- and move that into your "NVFlash" directory. The USB folder has the .inf file for installation in it along with two other directories with drivers for the various operating systems. (Note: These drivers, which are the same as the drivers in the SDK, are proven to work with Win 7 64-bit and have the setup include to load into other versions of Windows.) Follow this narrative for actual installation of the drivers.
CHECKPOINT: At this point, you should have the nvflash files, .img files, and USB directory (and files) in you "NVFlash" directory and are ready to begin the recovery process.
Now, you will need to boot into G-Tablet APX mode: hold down the power and volume - button simultaneousl until your G-Tab comes up and the goes back to a black screen. The black screen means it is in APX mode and it is waiting to display the flashing process. In Linux, type "lsusb" in a terminal and you should see this "0955:7820 NVidia Corp.". 7820 means the device is in APX mode.
Connect your G-Tablet to your PC using your miniUSB to USB cable that came with your tablet.
Linux users: At this point, open up a command window to the folder you created, and run this script:
./nvflash_gtablet.sh
This will wipe the device back to bekit's original TnT stock image, except for user data which is retained. Should take about a minute to run and the device will reboot itself automatically. If the script does not work, make sure that the shell script and nvflash binary are set as executables.
Windows users: When you connect to the PC, the PC immediately tries to load a driver -- but since it doesn't know where the USB driver files are it will fail. Click through Start/Control Panel/Device Manager and find "APX" listed in the devices with a yellow "!" (exclamation point) on the icon. Select the APX item and find the "Update Driver" button and click it. When it asks where to search, choose the local computer manual selection choice and tell it to Browse.
Point the Browse (and the USB install) at the "USB" directory under the "NVFlash" folder. When pointed at the "USB" directory, the driver installed and I was ready to nvflash. If you go back to Device Manager after the Windows install has completed, it will show the nVidia USB drivers near the top of the USB device list.
Again, for Windows: Run this script which is in the "NVFlash" folder:
nvflash_gtablet.bat
This will wipe the device back to bekit's original TnT stock image except for user data, which is retained. Should take about a minute to run and the device will reboot itself automatically all the way to the main screen.
POST NVFlash:
When your G-Tablet has booted back to the main screen, you will have to check and make sure everything is set up. Particularly, get the wifi on and connected to the Internet. Almost immediately, you should get a notice about an OTA (over the air) update. This is the OTA Update to software version 3588. If it does, go ahead and have it do the update. From there, you can begin using your "stock 3588" G-Tablet.
If you don't get an automatic OTA notification, you can go the to manual "Update" icon on your tablet and have it check for updates -- and hopefully it will find OTA 3588.
Or, if neither of the above happen, you can download 3588 at the following link and install it manually:
http://tapntap.http.internapcdn.net/tapntap/viewsonic/update-smb_a1002-3588-user.zip
Note: Following is a STICKY from General Forum on the stock recovery process:
http://forum.xda-developers.com/showthread.php?t=892090
NOTICE: There are many threads out there with tell how to do this process. Others tell individuals' problem solving experiences. A few of them may not be right! The above process is not the only way to do this -- but it is fairly straightforward and it is proven. It is recommended for anyone who does not have experience with nvflashing.
***************************************************
Further references (since I'm not a Windows user): http://forum.xda-developers.com/show...0&postcount=28
and http://forum.tegratab.com/viewtopic....bbde76184e550a and http://wiki.tegratab.com/index.php/Nvflash_FAQ
An additional suggestion if you also want to tack on bekit's clockworkmod recovery versus standard recovery: http://forum.xda-developers.com/show...3&postcount=17
Hope this helps!
03/2011 update -- I've been told that this tool has been useful to erase ALL partitions, including user data. I believe you need to re-flash with the bekit 1105 above, AFTER you use this: http://forum.xda-developers.com/showthread.php?t=974422
04/22/2011 update -- I've built out both 1.1-3588-based and 1.2-4349-based versions that have effectively replaced bekit's 1105 image ("nvflash_gtablet_2010110500.zip"), at least on my own device - I'm also addding a clockworkmod recovery option. It is being hosted in the same location as my 1.2-based mods - I will be making updates there, from this point on (as I might update them from time to time).
(you'd still need bekit's Windows or Linux tools, keep in mind) I've been able to bring back my device back from a soft-brick several times, so I feel they are usable.
05/09/2011 update -- A reminder that these images are not being updated, here. I have a newer nvflash post over in the same site where I have my 1.2-based mods. The 1105 bekit image mentioned here is still relevant for 1.1-based ROM users, or you can use my 3588 ot 4349 solution at the other site.
05/10/2011 update -- I have PM'd the moderator to either unsticky this post and / or assign it to someone else, as I do not plan on updating it, here. I believe that there is a 3588 image in the TegraTab IRC that someone created, for example.

Looks good Roebeet. I wrote a little how to a while back on tegratab. I know you are aware but for the benefit of others I wanted to add the following.
One little thing is sometimes when you are done you will get a boot loop. I think it only may happen once as I never saw it again. The fix is to go into Clockwork and partition the internal sd card again. The old settings said 512 for memory, and 256 swap. Bekit updated Clockwork and now you can format all the way to 4gb if you like, and swap should be 0 as it is not used.
Edit: New wisdom says not to partition the internal sdcard to anything but 2048. Folks have had issues with memory errors in the market with anything bigger. 0 for a swap is also the recommendation as Android apparently does not make use of the swap.

roebeet said:
Wanted to expand on what was already here, since there seems to be a lot of questions that pop up. I use Ubuntu so I know that the Linux instructions are correct.
A warning in advance: nvflash makes changes to the partition structure of your device. You should tread carefully and understand the risks.
Pre-req: http://db.tt/Wm25t7U
Linux users: You want to get "nvflash_linux_2010110500.tar.gz" and "nvflash_gtablet_2010110500.zip "
Windows users: You want to get "nvflash_windows_20100500.zip" and ""nvflash_gtablet_2010110500.zip"
Other references (since I'm not a Windows user): http://forum.xda-developers.com/showpost.php?p=9564270&postcount=28
and http://forum.tegratab.com/viewtopic.php?f=6&t=8&sid=4e6bd75cda9e24e04fbbde76184e550a
http://wiki.tegratab.com/index.php/Nvflash_FAQ
-------------------------------------------
Installation
Create a folder on your PC which you use as your restore base, and then extract the platform-specific ZIP into that location.
Then, download the "nvflash_gtablet_2010110500.zip" package and unzip the /nvflash_gtablet/ folder inside into the same folder as where you dropped nvflash.
For Windows users, you'll need to have an APX-specific USB driver for the next steps (I believe that the Windows package bekit supplied has that .inf file, but again I don't know for sure). For Linux users, you don't need an extra driver.
Once ready, boot the device into APX mode (power up and volume down, at the same time - you'll see the boot screen pop up, and then go blank.). In Linux, type "lsusb" in a terminal and you should see this "0955:7820 NVidia Corp.". 7820 means the device is in APX mode.
Linux users: At this point, open up a command window to the folder you created, and run this script:
nvflash_gtablet.sh
This will wipe the device back to bekit's original TnT stock image, except for user data which is retained. Should take about a minute to run and the device will reboot itself automatically.
Windows users: (again, I did not test this myself). Run this script, in the folder you created:
nvflash_gtablet.bat
Hope this helps!
Click to expand...
Click to collapse
I need help. I finally got Windows 7 to recognize the device in APX mode but how do I flash from this point. It only shows up in my Device list with all the subfolders in it.

What is this for? Restoring to factory Rom?
Thanks,
Scott

cscotty said:
What is this for? Restoring to factory Rom?
Thanks,
Scott
Click to expand...
Click to collapse
Yes, you can use it for exactly that. I believe bekit added Launcher Pro and superuser, but other than that it's a way to completely wipe the device. Moreso than a standard recovery would do.

The pre-req link doesnt work. Can you update the link?
Thanks
roebeet said:
Wanted to expand on what was already here, since there seems to be a lot of questions that pop up. I use Ubuntu so I know that the Linux instructions are correct.
A warning in advance: nvflash makes changes to the partition structure of your device. You should tread carefully and understand the risks.
Pre-req: http://db.tt/Wm25t7U
Linux users: You want to get "nvflash_linux_2010110500.tar.gz" and "nvflash_gtablet_2010110500.zip "
Windows users: You want to get "nvflash_windows_20100500.zip" and ""nvflash_gtablet_2010110500.zip"
Other references (since I'm not a Windows user): http://forum.xda-developers.com/showpost.php?p=9564270&postcount=28
and http://forum.tegratab.com/viewtopic.php?f=6&t=8&sid=4e6bd75cda9e24e04fbbde76184e550a
http://wiki.tegratab.com/index.php/Nvflash_FAQ
-------------------------------------------
Installation
Create a folder on your PC which you use as your restore base, and then extract the platform-specific ZIP into that location.
Then, download the "nvflash_gtablet_2010110500.zip" package and unzip the /nvflash_gtablet/ folder inside into the same folder as where you dropped nvflash.
For Windows users, you'll need to have an APX-specific USB driver for the next steps (I believe that the Windows package bekit supplied has that .inf file, but again I don't know for sure). For Linux users, you don't need an extra driver.
Once ready, boot the device into APX mode (power up and volume down, at the same time - you'll see the boot screen pop up, and then go blank.). In Linux, type "lsusb" in a terminal and you should see this "0955:7820 NVidia Corp.". 7820 means the device is in APX mode.
Linux users: At this point, open up a command window to the folder you created, and run this script:
nvflash_gtablet.sh
This will wipe the device back to bekit's original TnT stock image, except for user data which is retained. Should take about a minute to run and the device will reboot itself automatically.
Windows users: (again, I did not test this myself). Run this script, in the folder you created:
nvflash_gtablet.bat
Hope this helps!
Click to expand...
Click to collapse

stanglx said:
The pre-req link doesnt work. Can you update the link?
Thanks
Click to expand...
Click to collapse
It seems to go up and down (it's bekit's dropbox). Try this:
https://www.dropbox.com/s/wrcd87u1iy31u4e

roebeet said:
Wanted to expand on what was already here, since there seems to be a lot of questions that pop up. I use Ubuntu so I know that the Linux instructions are correct.
A warning in advance: nvflash makes changes to the partition structure of your device. You should tread carefully and understand the risks.
Pre-req: http://db.tt/Wm25t7U
Linux users: You want to get "nvflash_linux_2010110500.tar.gz" and "nvflash_gtablet_2010110500.zip "
Windows users: You want to get "nvflash_windows_20100500.zip" and ""nvflash_gtablet_2010110500.zip"
Other references (since I'm not a Windows user): http://forum.xda-developers.com/showpost.php?p=9564270&postcount=28
and http://forum.tegratab.com/viewtopic.php?f=6&t=8&sid=4e6bd75cda9e24e04fbbde76184e550a
http://wiki.tegratab.com/index.php/Nvflash_FAQ
-------------------------------------------
Installation
Create a folder on your PC which you use as your restore base, and then extract the platform-specific ZIP into that location.
Then, download the "nvflash_gtablet_2010110500.zip" package and unzip the /nvflash_gtablet/ folder inside into the same folder as where you dropped nvflash.
For Windows users, you'll need to have an APX-specific USB driver for the next steps (I believe that the Windows package bekit supplied has that .inf file, but again I don't know for sure). For Linux users, you don't need an extra driver.
Once ready, boot the device into APX mode (power up and volume down, at the same time - you'll see the boot screen pop up, and then go blank.). In Linux, type "lsusb" in a terminal and you should see this "0955:7820 NVidia Corp.". 7820 means the device is in APX mode.
Linux users: At this point, open up a command window to the folder you created, and run this script:
nvflash_gtablet.sh
This will wipe the device back to bekit's original TnT stock image, except for user data which is retained. Should take about a minute to run and the device will reboot itself automatically.
Windows users: (again, I did not test this myself). Run this script, in the folder you created:
nvflash_gtablet.bat
Hope this helps!
Click to expand...
Click to collapse
Roebeet sorry but I just noticed for noobs that the linux command needs to be
. nvflash_gtablet.sh
Also if you unzip those files into a premade directory such as "gtablet" when you unzip them each have their own directories and if you ls you can see that the bash script isn't executable from there. So you need to copy either the gtablet files into the platform folders or copy all the files inside both into your "gtablet" folder. Then you can run the ". nvflash_gtablet.sh" command and voila. Sorry I am on Ubuntu and don't know if it is different, but that is the way I run them.

No worries - all replies are welcome! the more info we have, the better.

This should be stickied. Nvflash has saved my gtab many times and I think its the reason why my gtab doesn't really encounter too many Force closes. Its the perfect method to ensure your gtab is clean.

I tried this tonight to try to get my gTablet back to stock so that I could show people how to install CWM on a video but I could get neither of my Windows 7 64-bit computers to recognize the APX .inf that was included in the pack.
I have a linux machine around here somewhere I may have to use...

ehunyadi said:
I tried this tonight to try to get my gTablet back to stock so that I could show people how to install CWM on a video but I could get neither of my Windows 7 64-bit computers to recognize the APX .inf that was included in the pack.
I have a linux machine around here somewhere I may have to use...
Click to expand...
Click to collapse
My limited experience with 64-bit Win7 -- the drivers have to be signed, or else they won't work. There's a way to disable that on boot, but you can't permanently disable it. I'm wondering if the APX USB driver is signed?

Open a command prompt as an admin and type
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
This is the only way.. dont worry if the test watermark shows up.. it wont affect anything.
Also... They have a x64 driver - read this
http://tegradeveloper.nvidia.com/tegra/forum/adb-usb-driver

Hi there,
I exchanged for a new Gtab yesterday from sears (as it had some power issues).
Today, I tried TnT 2.2 on my rooted tab (Z4 for rooting). Also have ClockworkMod .8.
I partitioned my internal SDCard. But after vanilla restore, I could find my tab space reduced to 4 gigs. What should I do to restore to full 16 gigs(14+ gigs actually).
============================================================================================================================
2. I followed your instrction and partitioned again in clockworkMod and did 4 gigs and 0 in the second one. Now it shows 11 gigs for data and 4 gigs for system.
Now I inserted an external micro SD card (16 gigs) but my storage is not seeing it. What should i do? Ignore my first part please.

Your gonna have problems later if you don't repartition to 2048 and 0

satishraman said:
Hi there,
I exchanged for a new Gtab yesterday from sears (as it had some power issues).
Today, I tried TnT 2.2 on my rooted tab (Z4 for rooting). Also have ClockworkMod .8.
I partitioned my internal SDCard. But after vanilla restore, I could find my tab space reduced to 4 gigs. What should I do to restore to full 16 gigs(14+ gigs actually).
============================================================================================================================
2. I followed your instrction and partitioned again in clockworkMod and did 4 gigs and 0 in the second one. Now it shows 11 gigs for data and 4 gigs for system.
Now I inserted an external micro SD card (16 gigs) but my storage is not seeing it. What should i do? Ignore my first part please.
Click to expand...
Click to collapse
You only have 16gb to start. Partitioning you internal to 4gb uses part of that. I would go back and only use 2gb, and 0 for swap. There are things, like the new market that break with anything but 2gb.
If you mean the settings menu is not showing your external sd card that's normal. Look in a file explorer program in the / directory. Look for SDcard2. That is your external. Same deal, look for usbdisk if you plug in a usb drive.

Roebeet
also this could be helpful to Ubuntu/linux users.
in the same directory where your flash script is there is a file that is called "gtablet.cfg" if you download the clockwork.img recovery and put it in this directory you can open up the "gtablet.cfg" with a text editor
scroll down to where you see "filename=part9.img" and replace "part9" with "clockwork" and it should now read "filename=clockwork.img" this will flash clockwork and save you a step. To change it back so you flash complete stock just edit the file again and reverse it.

romanrish said:
Roebeet
also this could be helpful to Ubuntu/linux users.
in the same directory where your flash script is there is a file that is called "gtablet.cfg" if you download the clockwork.img recovery and put it in this directory you can open up the "gtablet.cfg" with a text editor
scroll down to where you see "filename=part9.img" and replace "part9" with "clockwork" and it should now read "filename=clockwork.img" this will flash clockwork and save you a step. To change it back so you flash complete stock just edit the file again and reverse it.
Click to expand...
Click to collapse
You don't even have to do that - you can just rename part9.img to something else, and clockworkmod.img to "part9.img". That's actually what I do.

roebeet said:
You don't even have to do that - you can just rename part9.img to something else, and clockworkmod.img to "part9.img". That's actually what I do.
Click to expand...
Click to collapse
Yeah I thought about that, but figured some people might get confused and forget which one was which. Either way works as well just as long as you keep both files. You should edit your original post and add that in as an option to do at the end. It will keep some from having to look through and creating a new post cause they can't find it, and keep our forums clean.

This should definitely be stickied. Mods please?
P.S. I cannot believe how awesome this forum is(Viewsonic G Tablet). I have gone to other forums and the other devs and users are not as friendly and awesome as the ones we have here. Almost brings a tear to my eye. Great job Roebeet, this should help us noobs out a lot. LOL!

[GUIDE][Update][Android CM Alpha 3] How to Install CM Alpha on Touchpad

NOTE: I don't have a TP anymore, but i am pretty sure the installation instructions will be the same moving forward. If you are new follow the full guide, if you are already on one of the CM versions, skip to step 7 and replace the file with the current file.
Note: If you are already on CM Alpha 1/2.1 skip to step 7, if not you can follow the instructions below to install CM Alpha 3 from WebOS.
Alright, here is a step by step instruction on how to install CM Alpha 3 on Touchpad. I did notice there is a video guide but a text step by step might be useful for some. I have this installed and for Alpha release this is fantastic.
Pretty straightforward installation, but as always you follow this guide and flash at your own risk. Main thread for the CM port is here. Read whats working and whats not working there. If you have any questions, post it there. but read the known issues first, don't post know issues. This is just a guide.
Required:
1) PC ( windows, mac or linux) with working Internet
2) HP Touchpad ( obviously) and the usb cable that came with it.
3) Good Reading skills ( I am serious).
4) Read this guide twice if you have to.
Step 0:
Get your pre flash jitters out and think twice. This will root your device and hence your warranty will be void after the flash. If you still want to flash, back up your current HP touchpad. figure out which way is your volume up button ( you will need for step 4) and proceed to step 1
Step 1:
Make sure you have atleast 2GB of free space in your touchpad. Download the following files from here
1)Moboot bootloader for multi boot
2)CM Alpha 3
3)Clockwork Mod Recovery
Once done, go to step 2 below;
Step 2:
1)Acme Installer from here
2) HP WebOS SDK for windows, mac or linux
3) Follow the links above to install the full SDK or just the Novacom driver which is all that is required. If you are not sure, install the full sdk.
on to step 3 now.
Step 3:
1) Connect Touchpad to PC with the usb cable that came with it and select Usb Drive option.
2) Once the Touchpad pops up on your screen, create a folder called cminstall and put the files you downloaded in Step 1 there.
3) Eject/Safely remove touchpad from the pc, remove the USB cable from pc and shutdown touchpad, then go to step 4.
Step 4:
1) Do you know which way is your volume up button? if you are not sure then you are not paying attention to this guide. To figure out which way, boot to webOS, figure it out and shutdown.
2)Hold the volume up button and press power button simultaneously. You should see a white USB symbol.
3)Connect the USB cable back to pc and if the Novacom drivers were properly installed, the driver will be automatically detected and installed.
Step 5:
Almost there, time to install now.
Extract the Acme Installer you downloaded in Step 2 to your desktop or wherever you want. Open up cmd ( in windows) or terminal ( in linux or mac). cd to the directory where you just extracted your Acme Installer.zip and go to step 6 for install.
Step 6:
Now type this in the command prompt after you have done cd
novacom boot mem:// < ACMEInstaller
NOTE: windows users might have to manually move the novacom.exe and/or AcmeInstaller into c:\programfiles\palm folder and run the above command from there.
and wait for it to install and boot into CyanogenMod. If your clockwork mod didn't get installed, go here for a fix.
Step 7:
Update from CM Alpha 1/ 2.1
1) Download CM Alpha 3 from here
2) Plug in your touchpad to PC, select copy usb files option
3) Transfer CM Alpha 3 zip file into the "sd card" of your touchpad when it pops up and disconnect.
4) Long press power button and select reboot, then recovery option.
5) Recommended but Optional ( I didn't): In CWM recovery, go to backup and storage, do a nandroid backup before updating, back to main cwm recovery, wipe cache and in advanced wipe dalvik cache.
6) In the CWM recovery meny, use your volume buttons and select install zip file from sd card, select zip file and select cm alpha 3 zip, then scroll down and say yes.
7) Reboot. To check if you are on alpha 3, go to settings, about tablet and mod version should be alpha3.
To install google market and google apps, go here
Have Fun. Thanks to the awesome CM team, we have android on touchpad.
NOTE: If you want to uninstall CM for whatever reason, download ACME uninstaller from here and run it like you did with ACME installer. This should work ( i haven't tried it though).
SOD( Sleep of Death): This is when touchpad goes to sleep and wouldn't wake up, don't panic. Doesn't happen often and I have never seen it since installing Alpha 2.1. Press and hold power and home button for 10 - 20 secs and your TP will reboot. One fix for this is to use no-frills cpu control or set cpu and set min cpu to 384Mhz.

sticky this!

Good effort but you're going to get warned/banned by the mods for cross linking. They have to protect their domain you know.

techspecs said:
Good effort but you're going to get warned/banned by the mods for cross linking. They have to protect their domain you know.
Click to expand...
Click to collapse
Cross linking? I linked directly to the other websites which host the files. Thats not allowed? If so, mods can delete this thread. Only trying to help. I don't see another thread for a guide here in this section unless i am blind .

I've followed all the steps exactly and I'm getting this:
The ACME files were extracted to my users folder.

RavenSEAL said:
I've followed all the steps exactly and I'm getting this:
The ACME files were extracted to my users folder.
Click to expand...
Click to collapse
Looks like novacom wasn't installed properly. I don't have windows, so hopefully somebody else can chime in. try reinstalling novacom or the entire sdk.
Sent from my HP Touchpad using xda premium

reinstall and a quick reboot on my PC did the trick , running CM7 now

RavenSEAL said:
reinstall and a quick reboot on my PC did the trick , running CM7 now
Click to expand...
Click to collapse
Glad you got it sorted out. Enjoy cm
Sent from my HP Touchpad using xda premium

Android is unable to establish a reliable data connection to verify your google account :|

I am getting the same error:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Damian>cd c:\Users\Damian\desktop
c:\Users\Damian\Desktop>novacom boot mem:// < ACMEInstaller
'novacom' is not recognized as an internal or external command,
operable program or batch file.
c:\Users\Damian\Desktop> novacom boot mem:// < ACMEInstaller
'novacom' is not recognized as an internal or external command,
operable program or batch file.
c:\Users\Damian\Desktop>Acmeinstaller
'Acmeinstaller' is not recognized as an internal or external command,
operable program or batch file.
c:\Users\Damian\Desktop>novacom boot mem:// < ACMEInstaller
'novacom' is not recognized as an internal or external command,
operable program or batch file.
c:\Users\Damian\Desktop>novacom boot mem:// < ACMEInstaller
'novacom' is not recognized as an internal or external command,
operable program or batch file.
c:\Users\Damian\Desktop>
I reinstalled Novacom and in device manager it's there and installed correctly.

Breakthecycle2 said:
I am getting the same error:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Damian>cd c:\Users\Damian\desktop
c:\Users\Damian\Desktop>novacom boot mem:// < ACMEInstaller
'novacom' is not recognized as an internal or external command,
operable program or batch file.
c:\Users\Damian\Desktop> novacom boot mem:// < ACMEInstaller
'novacom' is not recognized as an internal or external command,
operable program or batch file.
c:\Users\Damian\Desktop>Acmeinstaller
'Acmeinstaller' is not recognized as an internal or external command,
operable program or batch file.
c:\Users\Damian\Desktop>novacom boot mem:// < ACMEInstaller
'novacom' is not recognized as an internal or external command,
operable program or batch file.
c:\Users\Damian\Desktop>novacom boot mem:// < ACMEInstaller
'novacom' is not recognized as an internal or external command,
operable program or batch file.
c:\Users\Damian\Desktop>
I reinstalled Novacom and in device manager it's there and installed correctly.
Click to expand...
Click to collapse
Sorry, are you saying when you reinstalled novacom everything worked? if not try moving ACME installer to the novacom directory and try from there.

Any idea where they would be? I can't find them.
---------- Post added at 04:48 PM ---------- Previous post was at 04:39 PM ----------
That didnt work either.

Breakthecycle2 said:
Any idea where they would be? I can't find them.
---------- Post added at 04:48 PM ---------- Previous post was at 04:39 PM ----------
That didnt work either.
Click to expand...
Click to collapse
try running cmd prompt as an admin. I don't have a windows machine, so i am not sure whats happening with yours. you have xp or windows 7 or vista?

Breakthecycle2 said:
Any idea where they would be? I can't find them.
---------- Post added at 04:48 PM ---------- Previous post was at 04:39 PM ----------
That didnt work either.
Click to expand...
Click to collapse
I had problems running it from desktop as well. got the same message you did. tried running it as admin and from c:\ to no avail. put acme in C:\Program Files\Palm, Inc\ directory and it worked finally

I got it! Thanks!

Breakthecycle2 said:
I got it! Thanks!
Click to expand...
Click to collapse
it worked for you by putting it in the palm folder like the poster above yours said? if not please post your soln for other windows users benefit. thanks

im having problems within cmd, i get access denied anytime i run the novacom command, i also ran under an admin account and as administrator n have the same problem, i tried under safe mode and it couldnt connect to server so what do i do?

I am using a laptop using ubuntu 11.04 lts. I follow all of the steps 100% and yet when i do the novacom prompt in terminal it boots my touchpad yet never goes to the penguin screens or installs anything. It just stays on the HP logo untill i do the manual reboot by holding home and power. Any ideas?

rizdog23 said:
I am using a laptop using ubuntu 11.04 lts. I follow all of the steps 100% and yet when i do the novacom prompt in terminal it boots my touchpad yet never goes to the penguin screens or installs anything. It just stays on the HP logo untill i do the manual reboot by holding home and power. Any ideas?
Click to expand...
Click to collapse
did you install the sdk and the novacom driver like the linux link suggested? i have ubuntu 11.04 and the steps i described worked no problems. reinstall novacom drivers

i installed the driver but not the full sdk cuz i was told i did not need to. Can you maybe give me a break down of how things will look like on ubuntu strictly? Sorry if i seem like a noob or it is bothersome for you to have to reply. I greatly appreciate your help

[ANDROID] Mac Guide to put some cm goodness on your touchpad

alright guys so the procedure is kinda complicated compared to Windows but not really lol Welp here it goes
TUTORIAL
1st: Download all the files needed to install (ACMEInstaller, CM7, Clockworkmod recovery, and Moboot) from rootzwiki
2nd: Once downloaded place all of those zips EXCEPT for ACMEInstaller into a folder on your touchpad called "cminstall"
3rd: Have the novacom drivers installed (google universal novacom installer, should be a .jar file)
4th: once that is done find the novacom drivers by searching in the finder (search novacom )
5th: unzip ACMEInstaller.zip and place the one that isn't the readme in with novacom
6th: drag novacom over to a terminal window followed by "boot mem:// <" then without a space drag the ACMEInstaller file over to the end of that string. (The result should look something like this Garrett-Witts-MacBook-Pro-2:~ garrett_witt$ /opt/nova/bin/novacom boot mem:// </opt/nova/bin/ACMEInstaller)
7th: Behold! You have installed cm7 using mac!

thank you very much!

You are very welcome man, just giving back to the community, was it easy to follow? It was my first guide lol

I would've put:
1st: Download all the .ZIP files needed to install (ACMEInstaller, CM7, Clockworkmod recovery, and Moboot) from rootzwiki via the forum link HERE
2nd: Once downloaded place all of those zips EXCEPT for ACMEInstaller into a folder on your touchpad (via USB mount) called "cminstall". Optionally you can also download the latest CM7 Google Apps package from http://goo-inside.me/gapps/ and put that in there as well - this is required if you want access to the Android market.
3rd: Download Novacom from HERE & install it.
4th: Unzip ACME Installer onto your desktop
5th: Power off your TouchPad, then turn it on again, holding down the Volume-Up button until a large USB logo appears on the screen.
5th: Open a terminal window (click on spotlight, type terminal and select it) and type the following into the terminal window:
novacom boot mem:// <~/Desktop/ACMEInstaller
The installer will now proceed. It'll adjust partition sizes, install ClockWorkMod, CM7 itself, the Moboot bootmenu and optionally the Google Apps package. WebOS will remain the default OS.

I got the install on my touchpad running. It got quite far and then stopped with the following lines ending it.
"Looking for the install images...
Initial install files not found.
Please download it from touchpad.linuxhacker.ru
and put in sminstall folder on media partition
the name should start with update-cm and end with .zip"
Any ideas?

liemydude said:
I got the install on my touchpad running. It got quite far and then stopped with the following lines ending it.
"Looking for the install images...
Initial install files not found.
Please download it from touchpad.linuxhacker.ru
and put in sminstall folder on media partition
the name should start with update-cm and end with .zip"
Any ideas?
Click to expand...
Click to collapse
Did you create the folder titled "cminstall" on the touchpad through webos?
and place in that folder the files "update-cyanogenmod...", "update-clockworkmod...", "update-gapps..." ?

thanks for the feedback knight, I will rewrite when I get the chance.

I can not get the Novatel package to install on 10.7.2 (Lion). It errors on the final step. Anyone else get it to install?

Boutwell, I think you may have the same problem I had. If you downloaded the SDK for the Novacom drivers from the link in the original README file you may have the version known to be in compatible with OS X Lion. Don't have the links to hand, but you can get the latest version of the SDK installer from the HP/WebOS site.
EDIT - found the link here: https://developer.palm.com/content/resources/develop/sdk_pdk_download.html#c23352
Download the Mac version of the SDK and install, no need to bother with the VMWare section and during the installer's option selection, clear the tick boxes for the Emulator and PDK as they are not needed.

Is this confirmed working / updated? I don't want to get out of bed to fire up my PC. Haha.

yes this works. i've done it on my macbook and my sister was able to do this on her macbook

Does Wifi work?

6th: drag novacom over to a terminal window followed by "boot mem:// <" then without a space drag the ACMEInstaller file over to the end of that string. (The result should look something like this Garrett-Witts-MacBook-Pro-2:~ garrett_witt$ /opt/nova/bin/novacom boot mem:// </opt/nova/bin/ACMEInstaller)
Click to expand...
Click to collapse
I get here and nothing. I followed the instructions perfectly. Touchpad is on the USB screen and Terminal is sitting there...
---------- Post added at 08:23 PM ---------- Previous post was at 07:46 PM ----------
chrischoi said:
I get here and nothing. I followed the instructions perfectly. Touchpad is on the USB screen and Terminal is sitting there...
Click to expand...
Click to collapse
I ended up having to redo the novacom drivers. Downloading them from the SDK pack is the way to go.

These ^last instructions worked best for me. Something about where my novacom and acme files were located had me messed up.

chrischoi said:
I get here and nothing. I followed the instructions perfectly. Touchpad is on the USB screen and Terminal is sitting there...
---------- Post added at 08:23 PM ---------- Previous post was at 07:46 PM ----------
I ended up having to redo the novacom drivers. Downloading them from the SDK pack is the way to go.
Click to expand...
Click to collapse
Just the Novacom drivers were giving me a install error. I also found that it's more consistent with changing director, then running the commands.

hey thanks for the write up very helpful
ps digging the A.B.R

Yo Garrett I gotta say thank you man. I been struggling with that terminal command for 2 hours. My damn eyes hurt. Every site was just giving windows info. Thank you much man. I owe you a drink

Thanks for this tutorial, mate. For those(lazy bastards) who don't like reading instructions, here's a video guide :
How to Install Android on the HP TouchPad (Mac Version)

if anyone else is having issues with mac try running the commands in su mode.

Thanks... very easy to follow compared to the original. The original had nothing about putting the files onto the device. Go figure...

Windows 8 can't install recovery mode ADB Drivers

If this isnt in the right spot please move it there, but I ran across this issue and figured I'd share the fix.
I kept getting Device Not Found in ADB while booted into Recovery so I followed the steps here:
http://blog.dantup.com/2012/10/fixing-adb-device-not-found-with-nexus-7-in-recovery-mode
Problem is, if you're on Windows 8 editing that file will cause a hash mismatch not allowing you to install the driver.
To go around that, follow these steps here:
http://www.windows7hacker.com/index.php/2012/09/3-ways-to-fire-up-windows-8-advanced-boot-options/
Once inside the Advanced Startup menu, click Troubleshoot, then Advanced Options, then Windows Startup Settings. Hit Restart Now and when it reboots into those settings hit the number 7 to Disable Driver Signature Enforcment. Once you reboot try installing the modified driver again. Should work.

all of that is not needed. Just install the windows 8 drivers:
http://dlcdnet.asus.com/pub/ASUS/EeePAD/Nexus7/usb_driver_r06_windows.zip
Unzip the file to a folder on your computer
When you connect your nexus to your computer you will have to go into the device manager. You will see the Nexus listed there with a "!" (assuming you had the previous drivers installed)
Right click, select update driver and point it to the folder you unzipped the file above into. After that adb and fastboot work fine with win 8. No need to jump through all the hoops.

Oh good to know.
Thanks! Feel free to delete this thread then.

graffixnyc said:
all of that is not needed. Just install the windows 8 drivers:
http://dlcdnet.asus.com/pub/ASUS/EeePAD/Nexus7/usb_driver_r06_windows.zip
Unzip the file to a folder on your computer
When you connect your nexus to your computer you will have to go into the device manager. You will see the Nexus listed there with a "!" (assuming you had the previous drivers installed)
Right click, select update driver and point it to the folder you unzipped the file above into. After that adb and fastboot work fine with win 8. No need to jump through all the hoops.
Click to expand...
Click to collapse
Not for me I had to use the ASUS files for ADB in Windows (yeah, 8 and 64bit), although I had the Univ. Naked Drivers installed already. But in fastboot Windows didnt want to recognize the device and it didnt let me install the ASUS r6, the Google original ones or the Univ. Naked (The last ones because of the hash), so I had to go into advanced startup and do the steps mentioned in the OP. (Damn Win 8 )

For fastboot/adb in fastboot mode you need to disable driver signing, this is an other way to do that :
Command Prompt (as admin!)
Disable driver signing :
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
Reboot
(on your desktop you see the watermark : 'Test mode' This is permanent, even after every reboot till :
Enable driver signing :
bcdedit -set loadoptions ENABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING OFF
Reboot

xXfuzzXx said:
Not for me I had to use the ASUS files for ADB in Windows (yeah, 8 and 64bit), although I had the Univ. Naked Drivers installed already. But in fastboot Windows didnt want to recognize the device and it didnt let me install the ASUS r6, the Google original ones or the Univ. Naked (The last ones because of the hash), so I had to go into advanced startup and do the steps mentioned in the OP. (Damn Win 8 )
Click to expand...
Click to collapse
hmm that's odd. I was having the issue with the normal driver (win 8 64bit) and the normal driver would fail to reinstall(as many reported). I downloaded the one I linked to and updated the driver in device manager and adb and fastboot worked without doing anything else.

graffixnyc said:
all of that is not needed. Just install the windows 8 drivers:
http://dlcdnet.asus.com/pub/ASUS/EeePAD/Nexus7/usb_driver_r06_windows.zip
Unzip the file to a folder on your computer
When you connect your nexus to your computer you will have to go into the device manager. You will see the Nexus listed there with a "!" (assuming you had the previous drivers installed)
Right click, select update driver and point it to the folder you unzipped the file above into. After that adb and fastboot work fine with win 8. No need to jump through all the hoops.
Click to expand...
Click to collapse
That driver worked perfectly, thanks! :good:

graffixnyc said:
all of that is not needed. Just install the windows 8 drivers:
http://dlcdnet.asus.com/pub/ASUS/EeePAD/Nexus7/usb_driver_r06_windows.zip
Unzip the file to a folder on your computer
When you connect your nexus to your computer you will have to go into the device manager. You will see the Nexus listed there with a "!" (assuming you had the previous drivers installed)
Right click, select update driver and point it to the folder you unzipped the file above into. After that adb and fastboot work fine with win 8. No need to jump through all the hoops.
Click to expand...
Click to collapse
Dude, thank you so much for that download link. I have been going out of my mind trying to get this device recognized in adb/fastboot on windows 8. Your tips/download worked perfectly. Thank you

I can choose only the MTB USB device when I try to update Nexus 7 driver
graffixnyc said:
hmm that's odd. I was having the issue with the normal driver (win 8 64bit) and the normal driver would fail to reinstall(as many reported). I downloaded the one I linked to and updated the driver in device manager and adb and fastboot worked without doing anything else.
Click to expand...
Click to collapse
I wanted to root my Nexus 7 device on the basis of a tutorial (links not allowwed yet )
Downloaded the Asus driver.
I choose the "Update Device Driver Software"option from Device Manager on Nexus 7, pointed to the installation folder on my computer ".. \android-sdk-windows\extras\google\usb\android_winusb.info" file, but the model window shows only the MTP USB Device, instead of the list of Android ADB Interface, Android Bootloader Interface and Android Composite ADB Interface.
The winusb.info file contains info for these drivers. If I point to this file, get an error message:
"The folder, You specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."
The host computer able to connect to the device, and I can list the folders, but the fastboot doesn't work.
Does anybody has a solution?
Thanks in advance
Gabor

graffixnyc said:
all of that is not needed. Just install the windows 8 drivers:
http://dlcdnet.asus.com/pub/ASUS/EeePAD/Nexus7/usb_driver_r06_windows.zip
Unzip the file to a folder on your computer
When you connect your nexus to your computer you will have to go into the device manager. You will see the Nexus listed there with a "!" (assuming you had the previous drivers installed)
Right click, select update driver and point it to the folder you unzipped the file above into. After that adb and fastboot work fine with win 8. No need to jump through all the hoops.
Click to expand...
Click to collapse
BRAVO... :good:
II solved it in 1 second ...
thanks

[HOWTO] Root the Kindle Fire 2 (non HD)

Device = Kindle Fire 2 and Windows 8 64bit
Although I have tagged this as a howto, its more of a compilation of what others have done - many thanks to them. This is the first howto post I've done so please thank the guys that made this happen - not me.
There are many, many posts showing how to root the kindle fire (HD and normal) but it took me a while to piece together all the information I needed to root (re-root actually!) mine.
As I've just re done mine and its fresh in my head, here it is.
Download the Android SDK and unzip it and copy the 'adt-bundle-windows' folder to your documents folder
Navigate to Documents/adt-bundle-windows/sdk/tools and run the android app - this opens the android SDK manager.
Go to tools - Manage-addon-sites and select the User defined Sites tab. Click new and add the following url
http://kindle-sdk.s3.amazonaws.com/addon.xml
Hit OK and close
Now scroll to the bottom on the SDK manager and under extras will be 2 kindle fire options 'kindle fire device definitions' and 'kindle fire USB driver' select both and install.
Now close the SDK manager.
If you have previously used your kindle on your PC, plug it in and go to device manager and un-install the drivers for it - now unplug it.
Navigate to \Documents\adt-bundle-windows\sdk\extras\amazon\kindle_fire_usb_driver and install the kindle USB drivers
Now add the location of the ADB.exe file to your path
You should now be able to plug in your kindle and execute adb devices and see your kindle - that means your good to go.
Download this tool made by Bin4ry - http://forum.xda-developers.com/showthread.php?t=1886460
Unzip the file you download.
Now goto the platform-tools folder of the SDK and copy all the files in here into the 'stuff' folder of the file you just unzipped.
Now simply run the 'RunMe' batch file.
Now, you mileage may vary of course but this is what worked for me.
Some threads that I used for reference;
http://forum.xda-developers.com/showthread.php?t=2035334
http://forum.xda-developers.com/showthread.php?t=1886460
http://forum.xda-developers.com/showthread.php?t=1893838
https://developer.amazon.com/sdk/fire/connect-adb.html#Prerequisites

Path question
delete

Thanks a lot for this tutorial, i was searching for a way to root my kindle 2 (non HD) for the past 1 week and i almost felt like throwing it out of the window. Finally this helped me, installed SU successfully. Cheers!

Re-Rooted Kindle Fire 2 on Windows 7 X4-Bit
Finally, I'm going to bed!
Anyway, THIS is what I did.

BookCase said:
Finally, I'm going to bed!
Anyway, THIS is what I did.
Click to expand...
Click to collapse
Noobie question what do you actually type in when you add it to the path? Thanks

bryanchapman9999 said:
Device = Kindle Fire 2 and Windows 8 64bit
Although I have tagged this as a howto, its more of a compilation of what others have done - many thanks to them. This is the first howto post I've done so please thank the guys that made this happen - not me.
There are many, many posts showing how to root the kindle fire (HD and normal) but it took me a while to piece together all the information I needed to root (re-root actually!) mine.
As I've just re done mine and its fresh in my head, here it is.
Download the Android SDK and unzip it and copy the 'adt-bundle-windows' folder to your documents folder
Navigate to Documents/adt-bundle-windows/sdk/tools and run the android app - this opens the android SDK manager.
Go to tools - Manage-addon-sites and select the User defined Sites tab. Click new and add the following url
http://kindle-sdk.s3.amazonaws.com/addon.xml
Hit OK and close
Now scroll to the bottom on the SDK manager and under extras will be 2 kindle fire options 'kindle fire device definitions' and 'kindle fire USB driver' select both and install.
Now close the SDK manager.
If you have previously used your kindle on your PC, plug it in and go to device manager and un-install the drivers for it - now unplug it.
Navigate to \Documents\adt-bundle-windows\sdk\extras\amazon\kindle_fire_usb_driver and install the kindle USB drivers
Now add the location of the ADB.exe file to your path
You should now be able to plug in your kindle and execute adb devices and see your kindle - that means your good to go.
Download this tool made by Bin4ry - http://forum.xda-developers.com/showthread.php?t=1886460
Unzip the file you download.
Now goto the platform-tools folder of the SDK and copy all the files in here into the 'stuff' folder of the file you just unzipped.
Now simply run the 'RunMe' batch file.
Now, you mileage may vary of course but this is what worked for me.
Some threads that I used for reference;
http://forum.xda-developers.com/showthread.php?t=2035334
http://forum.xda-developers.com/showthread.php?t=1886460
http://forum.xda-developers.com/showthread.php?t=1893838
https://developer.amazon.com/sdk/fire/connect-adb.html#Prerequisites
Click to expand...
Click to collapse
does this guide work to install a rom in Kindle Fire 2nd gen?

adisagio said:
does this guide work to install a rom in Kindle Fire 2nd gen?
Click to expand...
Click to collapse
No. It is a quick guide on how to root a 2nd gen

Recovery
Do we have KF2 recovery until now?

Follow Up - Feedback
bryanchapman9999 said:
Device = Kindle Fire 2 and Windows 8 64bit
Although I have tagged this as a howto, its more of a compilation of what others have done - many thanks to them. This is the first howto post I've done so please thank the guys that made this happen - not me.
There are many, many posts showing how to root the kindle fire (HD and normal) but it took me a while to piece together all the information I needed to root (re-root actually!) mine.
As I've just re done mine and its fresh in my head, here it is.
Download the Android SDK and unzip it and copy the 'adt-bundle-windows' folder to your documents folder
Navigate to Documents/adt-bundle-windows/sdk/tools and run the android app - this opens the android SDK manager.
Go to tools - Manage-addon-sites and select the User defined Sites tab. Click new and add the following url
http://kindle-sdk.s3.amazonaws.com/addon.xml
Hit OK and close
Now scroll to the bottom on the SDK manager and under extras will be 2 kindle fire options 'kindle fire device definitions' and 'kindle fire USB driver' select both and install.
Now close the SDK manager.
If you have previously used your kindle on your PC, plug it in and go to device manager and un-install the drivers for it - now unplug it.
Navigate to \Documents\adt-bundle-windows\sdk\extras\amazon\kindle_fire_usb_driver and install the kindle USB drivers
Now add the location of the ADB.exe file to your path
You should now be able to plug in your kindle and execute adb devices and see your kindle - that means your good to go.
Download this tool made by Bin4ry - http://forum.xda-developers.com/showthread.php?t=1886460
Unzip the file you download.
Now goto the platform-tools folder of the SDK and copy all the files in here into the 'stuff' folder of the file you just unzipped.
Now simply run the 'RunMe' batch file.
Now, you mileage may vary of course but this is what worked for me.
Some threads that I used for reference;
http://forum.xda-developers.com/showthread.php?t=2035334
http://forum.xda-developers.com/showthread.php?t=1886460
http://forum.xda-developers.com/showthread.php?t=1893838
https://developer.amazon.com/sdk/fire/connect-adb.html#Prerequisites
Click to expand...
Click to collapse
bryanchapman9999,
Nice work bryanchapman9999, very solid How to.

when am trying to open the SDK manager nothing is happening. Can any1 help me ?

Open as admin ?
Sent from my Amazon Kindle Fire2 using xda app-developers app

Thanks it worked!!
bryanchapman9999 said:
Device = Kindle Fire 2 and Windows 8 64bit
Although I have tagged this as a howto, its more of a compilation of what others have done - many thanks to them. This is the first howto post I've done so please thank the guys that made this happen - not me.
There are many, many posts showing how to root the kindle fire (HD and normal) but it took me a while to piece together all the information I needed to root (re-root actually!) mine.
As I've just re done mine and its fresh in my head, here it is.
Download the Android SDK and unzip it and copy the 'adt-bundle-windows' folder to your documents folder
Navigate to Documents/adt-bundle-windows/sdk/tools and run the android app - this opens the android SDK manager.
Go to tools - Manage-addon-sites and select the User defined Sites tab. Click new and add the following url
http://kindle-sdk.s3.amazonaws.com/addon.xml
Hit OK and close
Now scroll to the bottom on the SDK manager and under extras will be 2 kindle fire options 'kindle fire device definitions' and 'kindle fire USB driver' select both and install.
Now close the SDK manager.
If you have previously used your kindle on your PC, plug it in and go to device manager and un-install the drivers for it - now unplug it.
Navigate to \Documents\adt-bundle-windows\sdk\extras\amazon\kindle_fire_usb_driver and install the kindle USB drivers
Now add the location of the ADB.exe file to your path
You should now be able to plug in your kindle and execute adb devices and see your kindle - that means your good to go.
Download this tool made by Bin4ry - http://forum.xda-developers.com/showthread.php?t=1886460
Unzip the file you download.
Now goto the platform-tools folder of the SDK and copy all the files in here into the 'stuff' folder of the file you just unzipped.
Now simply run the 'RunMe' batch file.
Now, you mileage may vary of course but this is what worked for me.
Some threads that I used for reference;
http://forum.xda-developers.com/showthread.php?t=2035334
http://forum.xda-developers.com/showthread.php?t=1886460
http://forum.xda-developers.com/showthread.php?t=1893838
https://developer.amazon.com/sdk/fire/connect-adb.html#Prerequisites
Click to expand...
Click to collapse
Im a complete noob and was kind of lost through the process. Finally it took me around 40 minutes to complete the whole process. Thanks a lot!
Some things to consider for noobs like me:
1. You MUST have Java SDK installed in order to open the "Android" App (SDK Manager) (I didnt have it)
2. It is important to delete the drivers of the kindle fire at Device manager (while is connected) if you have used (connected) it before. After deleting the drivers disconnect the kindle fire and install the drivers again.
3. adb.exe is located at \adt-bundle-windows-x86_64\sdk\platform-tools\ (sorry I didnt know where it was located)
4. When referring to "execute adb devices" it means you should type in a command prompt "adb devices" (I was looking for an .exe or a .bat file named "adb devices"!) LOL
5. After running "adb devices" you should be able to "see" your kindle device as a large alphanumeric sequence. Now, this was the tricky part for me... I tried several times and couldnt "see" my kindle listed! So I figured out that maybe there was a different kind of connection I could configure and indeed there was! I had to set my Kindle Fire to be in ADB Debug Mode. This is achieved by going to Settings->Security->Enable ADB And after that it was a piece of cake! I downloaded the file made by Bin4ry and followed the rest of the instructions.
Excellent tutorial bryanchapman9999!! I really appreciate your time and effort to gather up this information!
Regards.

Root the Kindle Fire 2 (non HD)
Divanus said:
Im a complete noob and was kind of lost through the process. Finally it took me around 40 minutes to complete the whole process. Thanks a lot!
Some things to consider for noobs like me:
1. You MUST have Java SDK installed in order to open the "Android" App (SDK Manager) (I didnt have it)
2. It is important to delete the drivers of the kindle fire at Device manager (while is connected) if you have used (connected) it before. After deleting the drivers disconnect the kindle fire and install the drivers again.
3. adb.exe is located at \adt-bundle-windows-x86_64\sdk\platform-tools\ (sorry I didnt know where it was located)
4. When referring to "execute adb devices" it means you should type in a command prompt "adb devices" (I was looking for an .exe or a .bat file named "adb devices"!) LOL
5. After running "adb devices" you should be able to "see" your kindle device as a large alphanumeric sequence. Now, this was the tricky part for me... I tried several times and couldnt "see" my kindle listed! So I figured out that maybe there was a different kind of connection I could configure and indeed there was! I had to set my Kindle Fire to be in ADB Debug Mode. This is achieved by going to Settings->Security->Enable ADB And after that it was a piece of cake! I downloaded the file made by Bin4ry and followed the rest of the instructions.
Excellent tutorial bryanchapman9999!! I really appreciate your time and effort to gather up this information!
Regards.
Click to expand...
Click to collapse
Divanus,
First, the Android SDK is completely independent of other services and is only required for developers. The package includes Eclipse which is a Programming platform that people like us use to develop software for Android. The software used in Root MANY ANDROID includes the adb.exe utility needed to Root the Kindle.
You only need four things to Root the Kindle:
1. Root MANY ANDROID: http://ubuntuone.com/6LfERbIVoLRh822wHFicgR
2. Android ADB Driver: http://ubuntuone.com/4UaHeEJBrh9PT87RFzYR19
3. Windows PC
4. Kindle Fire 2
Step 1: Install the ADB Driver while the Kindle is Unplugged from USB, then Reboot your PC.
Step 2: Plug the Kindle into USB, wait 2 minutes for the driver to initialize
Step 3: Unzip Root_with_Restore_by_Bin4ry_v18.5.1.zip as Root_with_Restore_by_Bin4ry_v17 to your desktop
Step 4: If you installed the SDK, you need to disable it, otherwise Root Many Android will fail. You can disable it by changing the platform-tools folder to platform-tools-temp. This can usually be found C:\Program Files\Android\sdk\platform-tools
Step 5: Run Root Many Android RunMe.bat
Step 6: You now have Root!

I cant do it
I am running a windows 7 32 OS and i cant install the driver I uninstall the default and try to install the other one manualy but my kindle
isnt under other devices its under portable devices and when i select the driver it says its not supported and to check if the driver is used
on 32 bit systems
Some please respond or make a video tutorial please i want root for chain fire 3d driver graphics if you have anything email me at
"[email protected]"

I'm having problems
Now add the location of the ADB.exe file to your path
I don't get this part can someone please help me plus i'm having a lot of problems i'm running windows 7 32 bit so can some please do like
a video tutorial with windows 32 please I want my root.

Kindle Fire HD and 2 First Aide - 4.1.43-Beta - Dated 02/19/2013 at 22:15
Kusakus said:
I am running a windows 7 32 OS and i cant install the driver I uninstall the default and try to install the other one manualy but my kindle
isnt under other devices its under portable devices and when i select the driver it says its not supported and to check if the driver is used
on 32 bit systems
Some please respond or make a video tutorial please i want root for chain fire 3d driver graphics if you have anything email me at
"[email protected]"
Click to expand...
Click to collapse
Kusakus,
First let me apologize for the delay we have been working hard to improve our software. Please follow these steps to solve your problem:
Step 1: Remove Kindle driver by plugging the Kindle into USB, then Go to the Windows Device Manager and select the Kindle > Android ADB Interface - choose Remove and be sure to check the Box to remove the driver from the driver database.
Step 2: Remove the second driver found under Portable Devices > Kindle - choose Remove and be sure to check the Box to remove the driver from the driver database.
Step 3: Next you need to remove "phantom devices" in the Windows Device Manager. Go to Control Panel and double click on System. You can also right-click "Computer" on the Start menu (or on the desktop if it's shown there) and choose Properties. Note: A faster way for opening up the System applet is to press the Windows logo key on your keyboard and then press Pause/Break at the same time.
Step 4: Click on "Advance System Settings" link, and then click on the "Environment Variables" button.
Step 5: In the System Variables section click on the "New" button.
In the New System Variable dialog box, under the Variable Name value enter devmgr_show_nonpresent_devices (just copy the value from here and paste it there) and give it a variable value of 1. Click OK.
Step 6: In the Environment Variables window notice how the new variable appeared in the System Variables section. Click OK.
Step 7: In the System Properties window click OK.
Step 8: Reboot the PC.
Step 9: Open Device Manager (Control Panel > System > Hardware > Device Manager).
Step 10: From the View menu click Show Hidden Devices and notice the change. Now remove EVERY instance of Kindle, Portable Devices, Android ADB Interface and Android ADB Composite Interface. Be sure to check the box to remove the driver from the PC.
Step 11: When you are done reboot the PC. Wait 3 minutes once you see the desktop for Windows to stabilize. Plug the Kindle into USB, wait 60 seconds and open the Windows Device Manager, you should now see two Yellow Triangles:
MTP
Unknown Device
Step 12: If you see two Yellow Triangles you have successfully removed all the Kindle Drivers! Unplug the Kindle from USB.
Step 13: Check Add/Remove Programs do you see Android SDK? If yes, please Remove it and reboot the PC.
Step 14: Please download and install Kindle Fire First Aide per this thread: http://forum.xda-developers.com/showthread.php?t=2096888
Step 15: Use Kindle Fire First Aide to install the Kindle Fire USB Driver - Option 12. Wait for the Install to complete. Once you see a successful driver install then go to the Kindle. Make sure "Allow installation of programs" is ON under the Kindle Status Bar - More + > Device. Also make sure ADB is ON under the Kindle Status Bar More + Security Enable ADB is ON.
Step 16: Plug the Kindle into your PC USB, wait 2 minutes, maybe 3 minutes for the driver to successfully install. When done go back to the Windows Device Manager, do you now see the following:
Kindle > Android ADB Interface
Portable Devices > Kindle
Step 17: If yes, then SUCCESS! Great work! Let's proceed, if NO post what you see in the Device Manger in the Kindle Fire First Aide thread here: http://forum.xda-developers.com/showthread.php?t=2096888
Step 18: Let's finally Root your Kindle Fire 2. Try Option 20 first if that root method fails, reboot the PC and Kindle then try Option 21. Pay close attention to the Kindle when using Option 21, the Kindle should ask to be "Restored" do not worry it is a fake restore that is only used to exploit the Kindle. When you restore the Kindle, the process will wrap up and you will have Root!
Step 19: You may use our software to install Google Play Store and Google Apps.
Kindle Fire First Aide Software Version 4.1.43-Beta The RunMe is Dated 02/19/2013 at 22:15:
Microsoft Windows Kindle Fire First Aide Universal Version 4.1.43-Beta: KFFirstAide.zip
Microsoft Windows Kindle Fire First Aide 32-bit Version 4.1.43-Beta: KFFirstAide32.zip
Microsoft Windows Kindle Fire First Aide 64-bit Version 4.1.43-Beta: KFFirstAide64.zip
Please unzip the above packages to C:\KFFirstAide make sure the RunMe.bat is Dated 02/19/2013 at 22:15. Before running the software, make sure you do not have another folder inside C:\KFFirstAide named KFFirstAide32, KFFirstAide64 or KFFirstAide. After you Unzip the software you should only have one folder named C:\KFFirstAide, this is critical to proper operation.
Make sure you have a Environment Variable in the Microsoft Windows PATH Statement of C:\KFFirstAide otherwise you will see many 'unable to find ???package???.apk' messages. Also, if you see an ADB message alerting the following "adb server is out of date. killing.." then make sure you do not have another version of ADB or the Android SDK on your computer.
Finally, make sure you are running the latests version of Java SE Development Kit 7u13
Thank you to EVERYONE for working as a team to make this software a better product. We will never forget the people who have made this product successful.
---------- Post added at 01:20 AM ---------- Previous post was at 12:57 AM ----------
Kusakus said:
Now add the location of the ADB.exe file to your path
I don't get this part can someone please help me plus i'm having a lot of problems i'm running windows 7 32 bit so can some please do like
a video tutorial with windows 32 please I want my root.
Click to expand...
Click to collapse
Kusakus,
We are sorry this is more difficult than is has to be. To make you life easy, please download Kindle Fire First Aide from here, if you do not know if you have a 32-bit or 64-bit version of Windows use the Universal package:
Microsoft Windows Kindle Fire First Aide Universal Version 4.1.43-Beta: KFFirstAide.zip
Microsoft Windows Kindle Fire First Aide 32-bit Version 4.1.43-Beta: KFFirstAide32.zip
Microsoft Windows Kindle Fire First Aide 64-bit Version 4.1.43-Beta: KFFirstAide64.zip
Step 1: Unzip Kindle Fire First Aide to C:\KFFirstAide - make sure there is no number on the end of the C:\KFFirstAide and make sure there is not a second folder named KFFirstAide inside the folder C:\KFFirstAide
Step 2: Use Windows Explorer to navigate to C:\KFFirstAide, find the RunMe.bat, Right Hand Mose Click on RunMe.bat and select 'Send to', select Desktop (Create Shortcut). Now press the Left Hand Mouse button to create the Shortcut named RunMe.bat.
Step 3: 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.
Step 4: 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.
Step 5: Double Mouse Click the new Icon named KF First Aide. You may be presented with a security window, just click Yes.
Step 6: 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
Step 7: That is it! The software is ready. Next we get the Kindle ready to Root! Grab the Kindle, pull down the upper Status Bar and select More + then select Device. Is "Allow Installation of Programs" ON? Good, next go to More + then select Security is Enable ADB ON? Good! Proceed.
Step 8: Plug the Kindle into USB. Wait 2 minutes for the Windows Device Manager to initialize. The open the Windows Device Manager by selecting the Keyboard "Windows Key" plus "Pause/Break", this will display the Windows System Properties. Click on the Device Manager tab do you see the following in the Device Manager?
Kindle > Android ADB Interface
Portable Devices
Step 9: If you do not see the above and you see two yellow triangles then remove the Kindle from USB and launch our software, select Option 12 to install the Kindle ADB Driver, wait for the driver install to complete, then plug the Kindle into USB, wait 2 to 3 minutes for everything to install, then inspect the Windows Device Manager again, do you see the two devices now? Good proceed!
Step 10: You are ready to Root, please elect Option 20 if that method of Rooting the Kindle fails do not worry we have more up our sleeve! Reboot the Kindle and the Computer.
Step 11: Please open Kindle Fire First Aide and this time use Option 21 to Root the Kindle. Please pay close attention to the Kindle, at one point the Kindle will ask to be Restored, click on RESTORE and let the software finish the process. In the end you will have Root!
Step 12: You may use our software to install Google Play Store Option 18 and Google Apps Option 23.
If you have any questions, please post them in our thread Kindle Fire First Aide: http://forum.xda-developers.com/showthread.php?t=2096888

Not trying to revive an old thread and I have been reading what I could find on the kindle fire 2. Recently got my daughter one and I'm not happy with the amazon store, etc. I would like to root and be able to use the playstore. Is this the best method? Is this what I need to do to accomplish this? She and her mother both like the stock ui and all, especially the carousel, so I have no intention of installing a different rom or launcher. So is it possible to simply root and get access to the google playstore? Thanks!

I used this thread recently and it worked fine
http://forum.xda-developers.com/showthread.php?p=36122126
Sent from my GT-P3110 using xda app-developers app

Hey It's me again
prokennexusa said:
Kusakus,
First let me apologize for the delay we have been working hard to improve our software. Please follow these steps to solve your problem:
Step 1: Remove Kindle driver by plugging the Kindle into USB, then Go to the Windows Device Manager and select the Kindle > Android ADB Interface - choose Remove and be sure to check the Box to remove the driver from the driver database.
Step 2: Remove the second driver found under Portable Devices > Kindle - choose Remove and be sure to check the Box to remove the driver from the driver database.
Step 3: Next you need to remove "phantom devices" in the Windows Device Manager. Go to Control Panel and double click on System. You can also right-click "Computer" on the Start menu (or on the desktop if it's shown there) and choose Properties. Note: A faster way for opening up the System applet is to press the Windows logo key on your keyboard and then press Pause/Break at the same time.
Step 4: Click on "Advance System Settings" link, and then click on the "Environment Variables" button.
Step 5: In the System Variables section click on the "New" button.
In the New System Variable dialog box, under the Variable Name value enter devmgr_show_nonpresent_devices (just copy the value from here and paste it there) and give it a variable value of 1. Click OK.
Step 6: In the Environment Variables window notice how the new variable appeared in the System Variables section. Click OK.
Step 7: In the System Properties window click OK.
Step 8: Reboot the PC.
Step 9: Open Device Manager (Control Panel > System > Hardware > Device Manager).
Step 10: From the View menu click Show Hidden Devices and notice the change. Now remove EVERY instance of Kindle, Portable Devices, Android ADB Interface and Android ADB Composite Interface. Be sure to check the box to remove the driver from the PC.
Step 11: When you are done reboot the PC. Wait 3 minutes once you see the desktop for Windows to stabilize. Plug the Kindle into USB, wait 60 seconds and open the Windows Device Manager, you should now see two Yellow Triangles:
MTP
Unknown Device
Step 12: If you see two Yellow Triangles you have successfully removed all the Kindle Drivers! Unplug the Kindle from USB.
Step 13: Check Add/Remove Programs do you see Android SDK? If yes, please Remove it and reboot the PC.
Step 14: Please download and install Kindle Fire First Aide per this thread: http://forum.xda-developers.com/showthread.php?t=2096888
Step 15: Use Kindle Fire First Aide to install the Kindle Fire USB Driver - Option 12. Wait for the Install to complete. Once you see a successful driver install then go to the Kindle. Make sure "Allow installation of programs" is ON under the Kindle Status Bar - More + > Device. Also make sure ADB is ON under the Kindle Status Bar More + Security Enable ADB is ON.
Step 16: Plug the Kindle into your PC USB, wait 2 minutes, maybe 3 minutes for the driver to successfully install. When done go back to the Windows Device Manager, do you now see the following:
Kindle > Android ADB Interface
Portable Devices > Kindle
Step 17: If yes, then SUCCESS! Great work! Let's proceed, if NO post what you see in the Device Manger in the Kindle Fire First Aide thread here: http://forum.xda-developers.com/showthread.php?t=2096888
Step 18: Let's finally Root your Kindle Fire 2. Try Option 20 first if that root method fails, reboot the PC and Kindle then try Option 21. Pay close attention to the Kindle when using Option 21, the Kindle should ask to be "Restored" do not worry it is a fake restore that is only used to exploit the Kindle. When you restore the Kindle, the process will wrap up and you will have Root!
Step 19: You may use our software to install Google Play Store and Google Apps.
Kindle Fire First Aide Software Version 4.1.43-Beta The RunMe is Dated 02/19/2013 at 22:15:
Microsoft Windows Kindle Fire First Aide Universal Version 4.1.43-Beta: KFFirstAide.zip
Microsoft Windows Kindle Fire First Aide 32-bit Version 4.1.43-Beta: KFFirstAide32.zip
Microsoft Windows Kindle Fire First Aide 64-bit Version 4.1.43-Beta: KFFirstAide64.zip
Please unzip the above packages to C:\KFFirstAide make sure the RunMe.bat is Dated 02/19/2013 at 22:15. Before running the software, make sure you do not have another folder inside C:\KFFirstAide named KFFirstAide32, KFFirstAide64 or KFFirstAide. After you Unzip the software you should only have one folder named C:\KFFirstAide, this is critical to proper operation.
Make sure you have a Environment Variable in the Microsoft Windows PATH Statement of C:\KFFirstAide otherwise you will see many 'unable to find ???package???.apk' messages. Also, if you see an ADB message alerting the following "adb server is out of date. killing.." then make sure you do not have another version of ADB or the Android SDK on your computer.
Finally, make sure you are running the latests version of Java SE Development Kit 7u13
Thank you to EVERYONE for working as a team to make this software a better product. We will never forget the people who have made this product successful.
---------- Post added at 01:20 AM ---------- Previous post was at 12:57 AM ----------
Kusakus,
We are sorry this is more difficult than is has to be. To make you life easy, please download Kindle Fire First Aide from here, if you do not know if you have a 32-bit or 64-bit version of Windows use the Universal package:
Microsoft Windows Kindle Fire First Aide Universal Version 4.1.43-Beta: KFFirstAide.zip
Microsoft Windows Kindle Fire First Aide 32-bit Version 4.1.43-Beta: KFFirstAide32.zip
Microsoft Windows Kindle Fire First Aide 64-bit Version 4.1.43-Beta: KFFirstAide64.zip
Step 1: Unzip Kindle Fire First Aide to C:\KFFirstAide - make sure there is no number on the end of the C:\KFFirstAide and make sure there is not a second folder named KFFirstAide inside the folder C:\KFFirstAide
Step 2: Use Windows Explorer to navigate to C:\KFFirstAide, find the RunMe.bat, Right Hand Mose Click on RunMe.bat and select 'Send to', select Desktop (Create Shortcut). Now press the Left Hand Mouse button to create the Shortcut named RunMe.bat.
Step 3: 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.
Step 4: 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.
Step 5: Double Mouse Click the new Icon named KF First Aide. You may be presented with a security window, just click Yes.
Step 6: 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
Step 7: That is it! The software is ready. Next we get the Kindle ready to Root! Grab the Kindle, pull down the upper Status Bar and select More + then select Device. Is "Allow Installation of Programs" ON? Good, next go to More + then select Security is Enable ADB ON? Good! Proceed.
Step 8: Plug the Kindle into USB. Wait 2 minutes for the Windows Device Manager to initialize. The open the Windows Device Manager by selecting the Keyboard "Windows Key" plus "Pause/Break", this will display the Windows System Properties. Click on the Device Manager tab do you see the following in the Device Manager?
Kindle > Android ADB Interface
Portable Devices
Step 9: If you do not see the above and you see two yellow triangles then remove the Kindle from USB and launch our software, select Option 12 to install the Kindle ADB Driver, wait for the driver install to complete, then plug the Kindle into USB, wait 2 to 3 minutes for everything to install, then inspect the Windows Device Manager again, do you see the two devices now? Good proceed!
Step 10: You are ready to Root, please elect Option 20 if that method of Rooting the Kindle fails do not worry we have more up our sleeve! Reboot the Kindle and the Computer.
Step 11: Please open Kindle Fire First Aide and this time use Option 21 to Root the Kindle. Please pay close attention to the Kindle, at one point the Kindle will ask to be Restored, click on RESTORE and let the software finish the process. In the end you will have Root!
Step 12: You may use our software to install Google Play Store Option 18 and Google Apps Option 23.
If you have any questions, please post them in our thread Kindle Fire First Aide: http://forum.xda-developers.com/showthread.php?t=2096888
Click to expand...
Click to collapse
Ummm Well I used your software and i got it rooted (at least the software says it is) but now I cant even use the kindle it is really buggy and i press somthing and a minute later it does it plz help

If you got it rooted, try to put on the recovery and flash a custom one (slimkat is pretty awesome). The amazon OS is terrible IMO.
Kusakus said:
Ummm Well I used your software and i got it rooted (at least the software says it is) but now I cant even use the kindle it is really buggy and i press somthing and a minute later it does it plz help
Click to expand...
Click to collapse

Database Users

welcome