Database Users

Android SDK issues

Ok, I have had multiple Android devices and have never had a problem with any of them with adb however, my computer had done some weird thing and every time I opened SDK Manager, it would open, but then time out and freeze..
SO.
I uninstalled both java development kit, and sdk manager, but now the manager wont open at all.. It just flashes a command prompt and exits out... So I ran the android.bat batch file in a command window, and i got this error
'xcopy' is not recognized as an internal or external command,
operable program or batch file.
ERROR: SWT folder 'lib\x86_64' does not exist.
Please set ANDROID_SWT to point to the folder containing swt.jar for your platform.
If anyone can help me, I would be much appreciated, I just got two new devices this month. I was able to root my SGS2 before, and now I am trying to root my Kindle, and all this is happening... Any help would me much appreciated...
Oh, and I did check my system32 file, and I do have xcopy in my system files

UntamedDeviance said:
Ok, I have had multiple Android devices and have never had a problem with any of them with adb however, my computer had done some weird thing and every time I opened SDK Manager, it would open, but then time out and freeze..
SO.
I uninstalled both java development kit, and sdk manager, but now the manager wont open at all.. It just flashes a command prompt and exits out... So I ran the android.bat batch file in a command window, and i got this error
'xcopy' is not recognized as an internal or external command,
operable program or batch file.
ERROR: SWT folder 'lib\x86_64' does not exist.
Please set ANDROID_SWT to point to the folder containing swt.jar for your platform.
If anyone can help me, I would be much appreciated, I just got two new devices this month. I was able to root my SGS2 before, and now I am trying to root my Kindle, and all this is happening... Any help would me much appreciated...
Oh, and I did check my system32 file, and I do have xcopy in my system files
Click to expand...
Click to collapse
I'm not sure why you'd be running the android.bat file? It's not really required to get things working. I have no idea why the SDK Manager would be hanging, but if you really want to have that, then I'd do a full uninstall of everything, reboot, and then try again. Did you download the SDK from here?
Technically you don't HAVE to install the SDK to get access to the Kindle Fire. You only really need fastboot.exe, and adb.exe, and the Android drivers. All of these are available in a single download via the following post. You also don't have to use the actual utility if you don't want to, although it is actually quite cool and recommended if you are new to this.

sl0ttedpig said:
I'm not sure why you'd be running the android.bat file? It's not really required to get things working. I have no idea why the SDK Manager would be hanging, but if you really want to have that, then I'd do a full uninstall of everything, reboot, and then try again. Did you download the SDK from here?
Technically you don't HAVE to install the SDK to get access to the Kindle Fire. You only really need fastboot.exe, and adb.exe, and the Android drivers. All of these are available in a single download via the following post. You also don't have to use the actual utility if you don't want to, although it is actually quite cool and recommended if you are new to this.
Click to expand...
Click to collapse
Thanks, I appreciate that... I was only trying to run android.bat because it is what SDK Manager first runs when it first boots and that is why SDK won't boot... I have tried a full uninstall, reboot, install, reboot... But I have done this for a while, so I am really comfortable with adb, so I will just get the files there... Thank you for those links.. I will do it that way, something to make it easier for always helps
EDIT:
I must have messed with something in my system settings somewhere to corrupt a bunch of stuff... I did a system restore to the 18th of December, reinstalled, and everything works perfect now... Oh well! Haha

[HOWTO] Backup and Restore the System Software

The recently posted rooting method for the KFHD has been great for owners to get started on modifying the device to suit their own tastes. However, I've been a little concerned about everybody jumping in without a safety net in place. There are numerous ways that this device can get bricked. Not to put all of you into a panic, but just getting an eventual OTA update from Amazon might put some of these rooted KFHDs in jeopardy. With no custom recovery on the horizon, I think it's important to have some backup/restore plan to get these devices booting again.
Overview
This backup plan involves making raw data clones of all critical storage partitions required to boot the device. These backup archives can then be stored somewhere off the device. In case of some critical failure that prevents the device from booting normally, these archives can be used to get the device booting normally again. The restore procedure requires the use of fastboot to write the backup archives back to their proper partitions. The use of fastboot requires a working bootloader, so the device will need to boot to the bootloader's bootlogo at a minimum. If the device has a broken bootloader, this guide will not be helpful. There's currently no working procedure for repairing a broken bootloader on the 2nd generation Kindle Fire devices.
To be clear, this guide is not a backup/restore plan for your data. This is strictly for backing up the system software while in a bootable state and recovering it if some modification bricks the device. This procedure has been tested on a KFHD with system software version 7.1.1. Although I have not tested it, I'm nearly certain it will work just fine on version 7.1.5. If the KF2 has the same partition layout as the KFHD, there's no reason why it shouldn't work for that device as well. Check the post on KFHD partitions for details.
Warning: Everything below is inherently dangerous and can potentially brick your device if they are not executed properly. I have tested various aspects to the best of my ability, but you assume all responsibility for performing any of these steps.
Backup
Attached is a small shell script written to do the following…
Make a "kindlebackups" directory in /sdcard (if necessary) and make it user read/writeable.
Create gzipped backup archives of partitions 1 through 11. This includes all partitions except /cache and /data.
Make all archive files user read/writeable.
The entire backup (stock) takes up approximately 550 MB, so be sure to have at least that much available in /sdcard. Root privileges are required for the script to run properly. The best time to use this script is after step two of the published rooting procedure. That's after the second reboot of the process when the device boots up in emulation mode and allows root access for the first time. At this point, the system partition is completely stock and has not been exposed to any modifications. Even if you are past this point, the backups will still be useful for any bootable state that allows root privileges.
Download the script, unzip and place it into your current working directory where you still have access to adb, then run the following adb commands to copy the script to the Kindle Fire and prepare it to be executed...
Code:
adb push backup.sh /data/local/backup.sh
adb shell chmod 777 /data/local/backup.sh
If the device is in the process of being rooted and it has just finished rebooting for the second time...
Code:
adb shell /data/local/backup.sh
If the device has already been rooted and the su binary is available on the system...
Code:
adb shell su -c "/data/local/backup.sh"
The entire process should take approximately 5 minutes. Once the script has completed the backup, access the Kindle Fire's storage area from your computer, then copy the contents of the "kindlebackups" folder to it. The "kindlebackups" folder may be deleted after transferring to your computer.
Restore
To begin the restore procedure, the device must be put into fastboot mode. My factory cable did the job for me, so I have not explored the possibility of changing bootmodes. I developed this guide on a borrowed KFHD and I do not intend to risk the device more than necessary. Unless someone comes forward with a procedure to change bootmodes into and out of fastboot mode, I'm going to say that a factory cable is required for the time being. Besides, based on my experience with the original Kindle Fire, a broken system almost always means there is no way to change the bootmode through it. Since this procedure will very likely be used on a device that cannot boot completely or otherwise has a bad system, a factory cable will probably be the only way into fastboot mode. If you plan to root or modify your system software, invest in a factory cable.
Use the factory cable (with the device turned off, plug into the device, then the computer) to get to fastboot mode. If successful, a "fastboot" logo will take the place of the original "kindle fire" logo.
Decompress the gzipped archive to be flashed… Linux users have gunzip, Mac OS X users also have gunzip and a built-in GUI utility, and Windows users can use 7-zip. The archive must be decompressed before flashing. Skipping this step will brick your device.
Flash the image file(s) back to the device. In most cases, the device will just have to get a working system partition flashed back to it, but the others are available if they are needed. To flash the system partition...
Code:
fastboot -i 0x1949 flash system system.img
- Optionally erase the cache and/or userdata partitions if the contents of either interfere with the operation of the system software. The system will rebuild them on reboot…
Code:
fastboot -i 0x1949 erase cache
fastboot -i 0x1949 erase userdata
Once the process is complete, long-press the power button (~20 seconds) until it powers down, unplug the factory cable, and power the device back up.
Good luck.

Thanks kinfauns. I appreciate everything you did for the original kindle fire. This should help a lot of people.
Sent from my Kindle Fire

My kindles /system directory is already screwed. Do you have a system.img file I can use?
Sent from my Galaxy Nexus using xda app-developers app

When i boot my kindle fire hd to fastboot (by factory cable) and connect it to pc, pc can't recognize kindle, it don't have driver for it.

Could anybody post his clean backup here? Screwed my kindle, want go back to stock. Backup is only way.

Copying kindlebackup folder
Thanks for the script - the backup procedure was smooth -
I couldnt find the kindlebackups folder while browsing through my PC and for others like me who wonder how to take these out of your KFHD, here is a simple way - I used a program called Wondershare MObilego (Manage SDcard option under more tools) Backing up was a cakewalk.
I have no affiliation to this tool maker - Just sharing a way that helped a n00b like me. (First rooting experience)

Thanks for the efforts!
BTW, will a backup from a clean device work for other devices instead of the same one which the backup was created from? Just wondering if people who have already fiddled around their root devices can get a fresh start.

vuhai6 said:
When i boot my kindle fire hd to fastboot (by factory cable) and connect it to pc, pc can't recognize kindle, it don't have driver for it.
Click to expand...
Click to collapse
I don't know if anybody has packaged the device drivers set up for this device. If nothing else, you can get the device driver installer in the "Kindle Fire Utility" for the original KF and use that. You just have to change the PID from 0006 to 0007 before installing it and should work. Refer to this post if you still have problems...
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
for device driver information. Again, written for the original KF, but the process for installing device drivers is the same. Only the PID is slightly different and that should get edited in the INF before installation.
ceebu said:
Thanks for the script - the backup procedure was smooth -
I couldnt find the kindlebackups folder while browsing through my PC and for others like me who wonder how to take these out of your KFHD, here is a simple way - I used a program called Wondershare MObilego (Manage SDcard option under more tools) Backing up was a cakewalk.
I have no affiliation to this tool maker - Just sharing a way that helped a n00b like me. (First rooting experience)
Click to expand...
Click to collapse
Glad to hear it worked out for you. I am not familiar with that program, but the KFHD should connect automatically to a Windows device as external storage... does it not?
dreamcryer said:
Thanks for the efforts!
BTW, will a backup from a clean device work for other devices instead of the same one which the backup was created from? Just wondering if people who have already fiddled around their root devices can get a fresh start.
Click to expand...
Click to collapse
I have not tested this and don't have a way to do so. I have some concerns about it, but I'm sure someone desperate enough will jump in and try it out. I know it's too late for some, but my suggestion is for everybody to make a backup if you can and not rely on someone else to give you archives after the fact. It's better to have your own backups.

Not recognized
My kindle is also not recognized when plugged in

kinfauns said:
I don't know if anybody has packaged the device drivers set up for this device. If nothing else, you can get the device driver installer in the "Kindle Fire Utility" for the original KF and use that. You just have to change the PID from 0006 to 0007 before installing it and should work. Refer to this post if you still have problems...
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
Click to expand...
Click to collapse
But pc don't recognize as Kindle, it as Tate-PVT-08 (sorry, i use mac cho screenshot, but windows too)

vuhai6 said:
But pc don't recognize as Kindle, it as Tate-PVT-08 (sorry, i use mac cho screenshot, but windows too)
Click to expand...
Click to collapse
I know that the vendor id is correct.
Sent from my Kindle Fire

kinfauns said:
Glad to hear it worked out for you. I am not familiar with that program, but the KFHD should connect automatically to a Windows device as external storage... does it not?
Click to expand...
Click to collapse
I was only able to see the contents of /sdcard using windows...
Sent from my GT-I9100 using xda app-developers app

cesdev89 said:
My kindle is also not recognized when plugged in
Click to expand...
Click to collapse
Then you're first going to have problems getting root privileges. You need to get adb working before you attempt any part of rooting or backing up with this procedure.
vuhai6 said:
But pc don't recognize as Kindle, it as Tate-PVT-08 (sorry, i use mac cho screenshot, but windows too)
Click to expand...
Click to collapse
This is the correct "product" reported by the KFHD. This and the product ID (0007) are the only differences between the KFHD and the original when it comes to installing the device drivers on Windows.
ceebu said:
I was only able to see the contents of /sdcard using windows...
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
/data/media and /sdcard are essentially the same thing (see the second post in this thread for an explanation of why this is the case). You should have seen kindlebackups in that directory.

kinfauns said:
You should have seen kindlebackups in that directory.
Click to expand...
Click to collapse
For some reason I didn't see it there, on hindsight I guess I panicked a bit (n00b) and fell back to the solution I already had.. (been using mobilego to manage my sgs2)..
Sent from my GT-I9100 using xda premium

kinfauns said:
I don't know if anybody has packaged the device drivers set up for this device. If nothing else, you can get the device driver installer in the "Kindle Fire Utility" for the original KF and use that. You just have to change the PID from 0006 to 0007 before installing it and should work. Refer to this post if you still have problems...
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
for device driver information. Again, written for the original KF, but the process for installing device drivers is the same. Only the PID is slightly different and that should get edited in the INF before installation.
Glad to hear it worked out for you. I am not familiar with that program, but the KFHD should connect automatically to a Windows device as external storage... does it not?
I have not tested this and don't have a way to do so. I have some concerns about it, but I'm sure someone desperate enough will jump in and try it out. I know it's too late for some, but my suggestion is for everybody to make a backup if you can and not rely on someone else to give you archives after the fact. It's better to have your own backups.
Click to expand...
Click to collapse
I'm ready to try

Didn't show at first
Kindlebackups showed up in root browser right away, but didn't show on PC until I rebooted KF2. So now should
I decompress and put in folder containing ADB?

Yuretz said:
Could anybody post his clean backup here? Screwed my kindle, want go back to stock. Backup is only way.
Click to expand...
Click to collapse
I got the same situation, could anyone kindly help to provide a backup?

Same here ... just need the system image ... Please

I'd appreciate it if everybody would refrain from making this a "beg for a system image" thread.
strat6 said:
Kindlebackups showed up in root browser right away, but didn't show on PC until I rebooted KF2. So now should
I decompress and put in folder containing ADB?
Click to expand...
Click to collapse
You can put the the images wherever you want, but you'll need to specify the path to the file. For example, if you are using Windows and put the kindlebackups directory on C:, you just need to modify the command to...
Code:
fastboot -i 0x1949 flash system C:\kindlebackups\system.img

Thank you for posting how to do this. It opens a lot of doors with at least a little security.
I made a backup earlier without a problem, then went ahead and made myself a factory cable(easy to do and worked great- old asus usb cable, 1k resistor, soldering iron, shrink tape and voila!). I feel much better about doing any mods to this device now knowing I can just flash my backup.

Kindle Fire HD - USB Drivers (ADB) Windows 7

If you have trouble with the QuemuRoot-Script (nothing happens, after starting demon), uninstall your old Kindle USB Driver and install this one.
https://dl.dropbox.com/s/vprplelu9zx7s2o/kindle_fire_usb_driver.rar?dl=1

adb_usb.ini file
Also, These instructions helped me get over the hurdle of not seeing my device when typing adb devices. Not sure if I didn't have the folder and file to begin with or if it was hidden. Either way, when I attempted to create the .android folder it appeared with the said file in it and the correct 0x1949 line in it. After that it worked great! saved me hours of frustration i'm sure
4. Hold down the Windows key and press R to bring up the run dialog and type %USERPROFILE% then click OK.
5. Open the .android folder.
6. Open the adb_usb.ini using Notepad or Wordpad.
7. Type 0x1949 at the end of the file, then save and close adb_usb.ini. (Note, some people are saying the ‘X’ has to be upper-case in order to work. See comments.)

ADB Communication Issues
Thank you for the post, just FYI if you use our download links, our utilities use the latest ADB daemon and API's
so these steps can be ignored.
If you have an old version of the utility and need the update in Zip form, here is another link: https://dl.dropbox.com/u/54456659/ADB%20Update.zip
The key is that the API's and daemon has the following stamp
adb.exe 12/28/2012 4:52 PM 796 KB
AdbWinApi.dll 12/28/2012 4:52 PM 94 KB
AdbWinUsbApi.dll 12/28/2012 4:52 PM 60 KB
Anything older need to be replaced.
The exact location of the files is
Root_with_Restore_by_Bin4ry_v17 move the files to the Stuff Folder
Qemu move the files to the root of the Qemu folder
Note: We apologize to the XDA Community for anyone who experienced trouble downloading from Dropbox.
We were unaware that the Dropbox free service is VERY limited in the amount of download traffic allowed
so we decided to upgrade our Dropbox account to the Team Premium version (ouch $795 Year) which allows
unlimited traffic. We upgraded our account yesterday, you should no longer experience 404 Errors
when using our download links. We thank everyone who is involved with the XDA Community.

It's great to know dropbox has been updated. Great addition for the community. Hopefully it allows potential for it to grow.
Sent from my KFTT using xda app-developers app

Follow Up - Feedback
bbanghyung said:
It's great to know dropbox has been updated. Great addition for the community. Hopefully it allows potential for it to grow.
Sent from my KFTT using xda app-developers app
Click to expand...
Click to collapse
bbanghyung,
We hope so as well. Thank you for the feedback, we work hard to improve the Kindle each day.
Hopefully our passion helps others, even if we do not make money. So far we are several tens
of thousands in the hole but this is OK. We will work hard each day hoping the word is passed
to others. In the end, if we do not make money, we can say we loved what we were doing and
at the moment, we are having lots of fun helping people like yourself.

THANK YOU
bbanghyung said:
Also, These instructions helped me get over the hurdle of not seeing my device when typing adb devices. Not sure if I didn't have the folder and file to begin with or if it was hidden. Either way, when I attempted to create the .android folder it appeared with the said file in it and the correct 0x1949 line in it. After that it worked great! saved me hours of frustration i'm sure
4. Hold down the Windows key and press R to bring up the run dialog and type %USERPROFILE% then click OK.
5. Open the .android folder.
6. Open the adb_usb.ini using Notepad or Wordpad.
7. Type 0x1949 at the end of the file, then save and close adb_usb.ini. (Note, some people are saying the ‘X’ has to be upper-case in order to work. See comments.)
Click to expand...
Click to collapse
I HAVE BEEN LOOKING FOR THAT LINK FOR SO LONG,
I finally rooted my device thanks to you!

I can't believe I'm having such a hard f***** time doing this.
For the first, after I install the ADB drivers it brings up the same error message on 3 different computers "drivers not installed properly".
But when I plug in my Kindle, I go to the device management and there under Kindle it says "Android Composite ADB driver".
So when I try either the KF First Aid or QemuRoot the bring up the same darn error message "Unable to find ADB"!
This is driving me crazy! I followed the guide step for step, Enabled ADB on the device, no freaking luck.
Also there is no ".android" folder, I can only assume that's part of this mistery.
All help will be greatly appreciated.

Stuck on logo/windows7 not recogonizing
I was given a Kindle Fire 7" HD the other day. Turns on then there is a bit of a flash/interruption then the "Kindle Fire" logo appears and proceeds to slightly animate. That is all it does. I have tried the hard resets many times but to no use. Upon connecting the USB cable to my windows7 pc there is no response other than the Kindle turning on when I do so.
I need to know step by step how to start the process of correcting this from the very beginning.
I look forward to donating!
Thanks in advance.

[Q]How to extract CPUID from bricked A500

My partner has a bricked A500. It will NOT boot so any utilities utilising adb/dmesg fail. I can boot into fastboot mode (v0.03.11-ICS) but fastboot returns USB write errors stating invalid partition format "." So, I assume I have to use nvFlash to re-write the partition table but this still requires the SBK that I can not generate as I do not know what my CPUID is.
I have read so many threads all offering tweaked variations of the same process but I haven't found as yet a definitive how-to on re-creating your CPUID/SBK on a bricked device as they all assume you either know your CPUID or the tablet stills boots so you can retrieve it easily.
Does anyone have any links to resources to assist? I currently can boot into fastboot and APXmode. Attempts to factory reset seem to kick off OK but then fail with errors erasing data/cache etc... I have both windows/linux and the tablet is recognized in APX/fastboot mode on both OS's.
Thanks

1- download the attached file
2- go to linux
3- install GCC , lsUSB , Libusb-1.0.x , libusb-1.0-dev (from “Ubuntu software center” )
4- drag and drop the APX.c file in your desktop
5- connect your tablet to the computer (through mini USB) and put it in APX mode
6- Now on computer fire up “Terminal” and type this code
Code:
cd Desktop
sudo su
gcc apx.c -o apx -lusb-1.0
7- a new file should appear in your desktop
8- keep typing :
Code:
./apx
it will return to you the UID (AKA: CPUID)
DONE

Error: Failed to open device
Dr.GM said:
1- download the attached file
2- go to linux
3- install GCC , lsUSB , Libusb-1.0.x , libusb-1.0-dev (from “Ubuntu software center” )
4- drag and drop the APX.c file in your desktop
5- connect your tablet to the computer (through mini USB) and put it in APX mode
6- Now on computer fire up “Terminal” and type this code
Code:
cd Desktop
sudo su
gcc apx.c -o apx -lusb-1.0
7- a new file should appear in your desktop
8- keep typing :
Code:
./apx
it will return to you the UID (AKA: CPUID)
DONE
Click to expand...
Click to collapse
Many thanks for the walkthrough.. n sorry for being such a noob!
My A500 is bricked, and not flashing through update.zip method.. dint have my cpuid so decided to follow your guide.. installed Ubuntu on my windows pc, installed all the additional packages you just mentioned, but after the last command of ./apx it returns with Error: Failed to open device !!!
Now What? can there be ANY way or ANYTHING i can do to get over with this LLAAAST step? pretty pretty please!?
Thanks in Advance!

dishoom said:
Many thanks for the walkthrough.. n sorry for being such a noob!
My A500 is bricked, and not flashing through update.zip method.. dint have my cpuid so decided to follow your guide.. installed Ubuntu on my windows pc, installed all the additional packages you just mentioned, but after the last command of ./apx it returns with Error: Failed to open device !!!
Now What? can there be ANY way or ANYTHING i can do to get over with this LLAAAST step? pretty pretty please!?
Thanks in Advance!
Click to expand...
Click to collapse
Put your device in APX mode, manually. Then get it.
Sometimes, if you leave it in what you think is APX mode, for a certain amount of time, you may not be able to connect to it. So do it fresh.

Moscow Desire said:
Put your device in APX mode, manually. Then get it.
Sometimes, if you leave it in what you think is APX mode, for a certain amount of time, you may not be able to connect to it. So do it fresh.[/QUOTE
Hmm thanks.. Meanwhile I did the code tweak as digested here: http://forum.xda-developers.com/showthread.php?t=2331151
And got my cpuid as 0x00000042dfd497
Hope this is what I needed? Although the characters are 14 if I exclude 0x?
Thanks again mate!
Click to expand...
Click to collapse

dishoom said:
Moscow Desire said:
Put your device in APX mode, manually. Then get it.
Sometimes, if you leave it in what you think is APX mode, for a certain amount of time, you may not be able to connect to it. So do it fresh.[/QUOTE
Hmm thanks.. Meanwhile I did the code tweak as digested here: http://forum.xda-developers.com/showthread.php?t=2331151
And got my cpuid as 0x00000042dfd497
Hope this is what I needed? Although the characters are 14 if I exclude 0x?
Thanks again mate!
Click to expand...
Click to collapse
Well, if I'm not mistaken, it should be 16. You can try it either way.
Click to expand...
Click to collapse

SUCCESS!!
I finally managed to unbrick my tab, SPECIAL thanks to @Moscow Desire, @eppeP, @civato and @srbeen.. here's what i did, thought it might help someone else like me!
Booted my PC in Ubuntu, to extract the CPUID, as i didnt have it saved. for that i used instructions from this post: http://forum.xda-developers.com/showthread.php?t=1751978
Nevertheless, i couldnt completely follow it till unbricking, as somehow things didnt quite work out as expected. Expecially, the UID i recovered was as i quoted above, filled with many zeroes.. i got the correct one after tweaking with apx.c file as advised here: http://forum.xda-developers.com/showthread.php?t=2331151 because i later realized i was using a 32-bit system.
After recovering my UID, downloaded the "V8-UNL-ICS-HC-bootloader-MULTI-cwm.zip" thing, given here: http://forum.xda-developers.com/showthread.php?t=1622425 .. its a simplified form of nvflash, and is easier to operate for less techno ppl like me. Booted to windows, downloaded and extracted it, and edited the v8.bat file to remove any cls commands and see what this thing does. Then, opened the command prompt with Administrative rights, and run the V8.bat file... Once my tab was unbricked, i could easily flash any update.zip package i wanted!!
Sounds easy! but believe me, its easier said than done! took me over a week to complete the whole process as i tried almost EVERYTHING as anyone suggested in ANY post to unbrick my tab! but nevertheless, got the result finally and thats what matters!
Guys, the devs at xda, You ROCK!! :good::good:

dishoom said:
I finally managed to unbrick my tab, SPECIAL thanks to @Moscow Desire, @eppeP, @civato and @srbeen.. here's what i did, thought it might help someone else like me!
Booted my PC in Ubuntu, to extract the CPUID, as i didnt have it saved. for that i used instructions from this post: http://forum.xda-developers.com/showthread.php?t=1751978
Nevertheless, i couldnt completely follow it till unbricking, as somehow things didnt quite work out as expected. Expecially, the UID i recovered was as i quoted above, filled with many zeroes.. i got the correct one after tweaking with apx.c file as advised here: http://forum.xda-developers.com/showthread.php?t=2331151 because i later realized i was using a 32-bit system.
After recovering my UID, downloaded the "V8-UNL-ICS-HC-bootloader-MULTI-cwm.zip" thing, given here: http://forum.xda-developers.com/showthread.php?t=1622425 .. its a simplified form of nvflash, and is easier to operate for less techno ppl like me. Booted to windows, downloaded and extracted it, and edited the v8.bat file to remove any cls commands and see what this thing does. Then, opened the command prompt with Administrative rights, and run the V8.bat file... Once my tab was unbricked, i could easily flash any update.zip package i wanted!!
Sounds easy! but believe me, its easier said than done! took me over a week to complete the whole process as i tried almost EVERYTHING as anyone suggested in ANY post to unbrick my tab! but nevertheless, got the result finally and thats what matters!
Guys, the devs at xda, You ROCK!! :good::good:
Click to expand...
Click to collapse
Speaking for the rest of the mentions, you are most welcome.

[How To]Fix Recovery Bootloop after installing twrp and 2nd bootloader

First and foremost I AM NOT RESPONSIBLE FOR ANY HARD BRICKS,etc ,etc(Really hard to hard brick a kindle doing this unless you flash a weird rom package)
Now that thats cleared up, I have been seeing too many recovery bootloop bricks lately because I think the main tutorials people use haven't been updated(to mention you need to put a rom on the kindle beforehand now), so I thought why not write a tutorial that explains how to fix this problem since there are so many posts, that way we can just put a link to the tutorial in the peoples threads. So here we go!
Things you need to do this:
a micro-usb cable
patience
minimal command prompt experience
Instructions:
Boot your kindle into twrp (it should do this on its own at this point)
Make sure you have the adb drivers installed(they will need to be installed again if you flashed an older version of twrp), if not, update your drivers in the device manager with the ones in my signature.(See below if you don't know how to update your drivers)
Download the attached file and extract it somewhere
Put the rom and gapps in the folder you extracted the files to
Open a command prompt with admin privileges(start>all programs>accessories right click command prompt, hit run as admin)
CD into the directory where the extracted files are
Type this into the command prompt: adb push rom-or-gapps-name-goes-here.zip /sdcard/
As I said in the filename put either the rom or the gapps, but send both in two commands
At this point once the transfer is done unplug your kindle
If you are going from amazon to a cm based rom, at this point you should wipe system, cache, dalvik cache, and do a factory reset. If not just goto step 11.
Hit install, browse to the /sdcard folder and choose the rom and gapps files and flash them
Reboot and profit!
For people with driver issues that don't know how to install my driver:
Open the device manager
Find the device with a triangle next to it
Right click it and hit update driver
Choose the option that lets you search a folder for drivers by browsing
Choose the folder you extracted my drivers to
Let it search and install the drivers
Profit!
Note: If adb isn't picking up the kindle in recovery, try uninstalling the current kindle devices it detects first and then updating the drivers

It's about time someone posted a tutorial for how to fix this. Great job! This should be a sticky.

thanks
I had the same problem... the looping thing... you're tutorial saved me! thanks a lot.

rom and gapps
sry for my ignorance, but what do you mean with "rom and gapps"?
i explain what i've done:
i did everything in the guide to install twrp and 2nd bootloader.
i can acces in the twrp, but if i enter the reboot menu, if i push the botton "System", i had the boot loop problem (Kindle logo became orange and then blue forever)
Now the question is: where i find the rom and the gapps you're talking about?

You choose a ROM from the android development section for your model kindle, usually it tells what version of gapps(google apps) you need to flash with it. If it doesn't tell what gapps you need its pretty easy to tell, goo.im has the gapps posted for all versions of android, and have a chart telling which version goes with what os.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

*cannot read
When I go to push the file to the kindle I get a message in the command prompt saying *cannot stat 'rom.zip': no such file or directory.
I have the zip in the same folder as the adb file
Any suggestions?

Check the ROM name to make sure its not a typo? It should work. Make sure you didn't rename the ROM and add .zip because windows by default doesn't show extensions, so the filename might actually be ROM.zip.zip now if you did that.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

Sigh, I was hoping my first post on XDA wouldn't be a help request, but here I am..
I agonized for hours over the directions in this tutorial, checked all the right boxes, but I ended up in the bootloop as described in the OP. I can get to TWRP fine, but nothing else. My ADB drivers along with the Android SDK package were installed and previously working fine. Now, of course, the device no longer has a driver in Windows. I followed the instructions here, carefully selecting the extracted folder containing the ADB files, and Device Manager tells me—
"Windows was unable to install your Kindle. If you know the manufacturer of your device, you can visit its website and check the support section for driver software."
Click to expand...
Click to collapse
I tried a number of times to reboot both systems, uninstall the Kindle, try to pick it up again, etc., to no avail.
My device is a Kindle Fire HD 7" originally version 7.4.6. I made backups before I started as per the directions in the linked thread and I have my desired ROM and Gapp .zips all ready to go, I just can't get anything to the device. I'd prefer to avoid needing to get a factory cable, if possible.
Thanks for any help!
Edit: I've managed to get my .zip files to the /sdcard/ directory. For anyone stuck on the same problem I was, the instructions in this thread got my ADB drivers up and running again. The rest of the steps here worked fine at that point.

Oh good, someone finally made a tutorial for this.

Help please
hello i am in need of some help, at step 6 can you explain what CD is. Also in Cmd i keep on getting this message below, please could you help me i also have just installed android ADB driver interface driver.
C:\Windows\system32>adb push cm-10.1-20130726-UNOFFICIAL-tate.zip /sdcard/
'adb' is not recognized as an internal or external command,
operable program or batch file.

CD means change directory, it does what it says, right now you are in your system32 folder so when you CD into the directory you extracted the zip file to you won't get that error. You should Google some command prompt basics.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

Thanks
Thank you for this guide, googled some basic CMD knowledge and now i have cyanogen. Cheers

gallowayj3 said:
hello i am in need of some help, at step 6 can you explain what CD is. Also in Cmd i keep on getting this message below, please could you help me i also have just installed android ADB driver interface driver.
C:\Windows\system32>adb push cm-10.1-20130726-UNOFFICIAL-tate.zip /sdcard/
'adb' is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
Click to collapse
Extract the file in the first post to somewhere on your C drive. (I put it in the C drive directly so it was just c:\adb\.)
Check this: ht tp://coweb.cc.gatec h.edu/ice-gt/339 - remove the spaces.
That should help.
Do
cd..
until you have just c:/. Then type cd:/adb and it should put you in the right place. Then you can do adb push.
I just figured this out actually and did it.

HELP
everything worked until i am flashing the rom, i get this error
updating partition details...
installing ' /sdcard/rom.zip'...
checking for MD5 file...
skipping MD5 check: no file found
assert failed: getprop("ro.product.device")=="blaze_tablet" || getprop(ro.build.product") == "blaze_tablet" || getprop("ro.product.device") == "tate" || getprop("ro.build.product") == "tate"
E:Error executing updater binary in zip ' /sdcard/rom.zip'
Error flashing zip ' /sdcard/rom.zip'
error flashing zip ' /sdcard/rom.zip'
epdating partition details...
PLEASE HELP

Sounds like an old twrp version I think, try downloading the latest twrp from android development for your device, It should have a flashable zip, just push it to your device and flash that, then reboot into recovery again and try flashing the ROM again.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stuck
Hi guys .., when i typed adb push cm-10.1-20130812-UNOFFICIAL-jem.zip /sdcard , it says
error: device not found.
i thing my pc didn't recognize my kindle. In device manager there ain't any devices not installed .
someone pls Help

Find the android adb device in the service manager and uni stall it and let it install my drivers and see if it works, I'm guessing its a simple driver issue.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

Sorry for my stupid question. ) what is service manager?
stunts513 said:
Find the android adb device in the service manager and uni stall it and let it install my drivers and see if it works, I'm guessing its a simple driver issue.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse

My bad I think my kindle autocorrected a word incorrectly. It was supposed to say device manager.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

i'm kind of newbie on rooting and installing ROMs.
http://www.youtube.com/watch?v=hUW6KARo8Y4
i tried this youtube instruction and after step 20 My kindle fire wouldn't start. Not even the kindle fire with blue color.
and also pc didn't recognize my kindle , maybe because of it won't power on.
/this instruction is for kindle fire HD 8.9 , i don't know my kindle is 7 inch/
In device manager can't find adb devices .. what should i do?