and I want to make it a normal Kindle Fire HD. I know I need to root to get rid of the demo software but I want to put the real FireOS on it and have it update normally so how would I go about unrooting it, or do I even have to unroot?
Um if it's a demo unit then it is not rooted, its on it's own demo os, you will need a fastboot cable to get it into fastboot mode so you can flash a normal os onto it. The normal os that get's flashed onto it comes prerooted because in order to make a system image we need root, hence it's got the su binary in the system image. I personally recommend installing a cm based os and 2nd bootloader afterwards if this is a 2012 model(has a camera), the amazon os is kinda limited capability wise.
Sent from my Amazon Kindle Fire HD using Tapatalk
Same Problem
stunts513 said:
Um if it's a demo unit then it is not rooted, its on it's own demo os, you will need a fastboot cable to get it into fastboot mode so you can flash a normal os onto it. The normal os that get's flashed onto it comes prerooted because in order to make a system image we need root, hence it's got the su binary in the system image. I personally recommend installing a cm based os and 2nd bootloader afterwards if this is a 2012 model(has a camera), the amazon os is kinda limited capability wise.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Hi All
I have the same issue brought a cheap Demo unit off eBay, just need to restore / re flash to a normal amazon kindle, Yep a Noob ! so simplest terms please .. have a fastboot cable and the kindle screen shows the fastboot logo, (PC_Windows 7 OS) sees the Kindle in my computer, however no other files can be seen. downloaded KffirstAide64, when I run the software, the following appears 'The system cannot find the path specified'
any ideas or help would be greatly appreciated.
I have ever had to use any of the utilities to restore a kindle though I vaguely remember there being a long list of instructions on kffa's post to do before using it, if you haven't done so then follow the directions, or just try kindle fire system restore tool. http://forum.xda-developers.com/showthread.php?t=1951254
Ignore the part on srt's page about the adb command, that's only for if you don't have a fastboot cable and you have adb access.
Sent from my Amazon Kindle Fire HD using Tapatalk
Still no go
stunts513 said:
I have he er had to use any of the utilities to restore a kindle though I vaguely remember there being a long lost of instructions on kffa's post to do before using it, if you haven't done so then follow the directions, or just try kindle fire system restore tool. http://forum.xda-developers.com/showthread.php?t=1951254
Ignore the part on srt's page about the adb command, that's only for if you don't have a fastboot cable and you have adb access.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Followed the instructions, still not recognising the device in recovery tool ( < waiting for device> ), any suggestions please?
Check the device manager for a device with a yellow triangle next to it, if you find it then download the drivers in my signature and unzip them somewhere, then in the device manager right click the device with yellow triangle, hit update drivers, point it to where my drivers are and you should be set.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
Check the device manager for a device with a yellow triangle next to it, if you find it then download the drivers in my signature and unzip them somewhere, then in the device manager right click the device with yellow triangle, hit update drivers, point it to where my drivers are and you should be set.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
OK, now with a fresh head to look at this, installed the drivers and cleared off the DEMO software, The KFHD boots with the KFHD splash screen then imeadiately goes to boot menu.
now the Recovery software runs but states -' The system cannot find the path specified'
'Fastboot is not recognised as an internal or external command'
The KFHD is in fastboot mode as per screen with the factory cable attached to the PC
The KFHD is not recognised in my computer but there is no triangle showing
Any ideas please?
Your recovery software wasn't extracted completely? That error means the fastboot command wasn't ran because windows couldn't find the file specified. If you were running kffa without extracting it that would explain it.
As for the not showing up part, it should show up as a adb device when it is in fastboot. You can always try switching to a normal cable once it is in fastboot. I would try getting the command working first in case its showing up and you aren't seeing it since the command would.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
Your recovery software wasn't extracted completely? That error means the fastboot command wasn't ran because windows couldn't find the file specified. If you were running kffa without extracting it that would explain it.
As for the not showing up part, it should show up as a adb device when it is in fastboot. You can always try switching to a normal cable once it is in fastboot. I would try getting the command working first in case its showing up and you aren't seeing it since the command would.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
AH HA ! I have the device showing as android ADB interface, now for the silly question, once I have downloaded and extracted kffistaide where should it be located? now it is just in a folder on the desktop, should it be in a specific location? to allow the path to be seen.
You can extract kffa wherever you want.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
You can extract kffa wherever you want.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
OK, but it still quotes unable to find the path specified?
OK just want to verify, you extracted everything from the zip file, not just the batch file that you have to run, right? If that was the case, I also might mention running the script as admin would be a good idea. If this still doesn't work I have another idea of a reason why, had something similar happen to someone I helped and man was the reason weird.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
OK just want to verify, you extracted everything from the zip file, not just the batch file that you have to run, right? If that was the case, I also might mention running the script as admin would be a good idea. If this still doesn't work I have another idea of a reason why, had something similar happen to someone I helped and man was the reason weird.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
yes all 155 file extracted and placed into a folder n the desktop, the run me file is run as admin
OK, shift + right click the folder that everything is extracted to and hit "new command prompt here", or something like that. Downside to what I'm telling Younis I'm not sure if the command promoted will have admin access, but if you know hot to use a command prompt, then feel free to run one as admin and CD into the directory. Anyways type the script name into the command promoted and press enter and try it. I had something like this happen before that didn't make sense but it worked when I did it like this.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
OK, shift + right click the folder that everything is extracted to and hit "new command prompt here", or something like that. Downside to what I'm telling Younis I'm not sure if the command promoted will have admin access, but if you know hot to use a command prompt, then feel free to run one as admin and CD into the directory. Anyways type the script name into the command promoted and press enter and try it. I had something like this happen before that didn't make sense but it worked when I did it like this.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Sadly ....
press any key to continue....
the system cannot find the path specified.
am sure this is an odd one ,,,,,,,,,,,,
The fastboot and adb commands are in the kffa folder right?
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
The fastboot and adb commands are in the kffa folder right?
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Yes,
Fastboot application
Adb application
Adb file
adbWinApi.dll
AdbWinUsbApi.dll
Maybe its time to give SRT a try.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
Maybe its time to give SRT a try.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
OK, downloaded and extracted KFHD_SR_v1.2.3
Extracted to folder
KF in Fastboot mode with Factory cable
Run SR Tool in Admin mode
Selec 4 Check Fastboot status - Product Tate-PVT-08
Select 3 Erase Cache an userdata - completed.
Select 1 Restore su only ..............
target reportd max download size f 1006632960 bytes
error: cannot load 'images/system.img' : no error
A bit further than previously but another wall..
Related
I just purchased a kindle fire and it was automatically updated to 6.21. I would like to download apps from the android market but it does not recognize my kindle as something that I can download to. How do I associate the kindle fire to my google account?
Thanks
You have to install google market
Sent from my Kindle Fire using xda premium
So at the moment I can not associate my fire because the fire can not be rooted so i cant install the market app correct?
chuckado said:
So at the moment I can not associate my fire because the fire can not be rooted so i cant install the market app correct?
Click to expand...
Click to collapse
That is correct. If you have the latest KF update, no root. If you had rooted previously this update breaks root.
Just got a KF for Christmas. I have it rooted, but I can't get the Vending.apk file to transfer to the /system/app directory. I have all the permissions; it just doesn't allow the .apk file to transfer.
I'd post in the appropriate directory, but because I have a new account, it won't let me.
Did you mount the system directory as RW? It's Read Only by default.
Sent from my Kindle Fire using xda premium
Try Kindle Fire Utility, it's [almost] foolproof.
borborpa said:
Did you mount the system directory as RW? It's Read Only by default.
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
I did mount it as RW. When I try to paste the file into the directory, it just disappears. I can never get Vending.apk to actually paste into the directory.
http://www.youtube.com/watch?feature=player_embedded&v=KapnjR89ICA
For all of you who needs a root before the 6.2.1 use this video, is very easy and you will be rooted again! also offers the way to get the market in.
Happy New Year to all
So does anyone know a why I can revert my Kindle Fire to the version just before 6.2.1 was pushed out and installed?
Finally got the android market to load on my kindle fire. It wasn't too bad and I don't know why no other way worked, but this way does.
You have to have your Kindle Fire rooted before you do this step, so search elsewhere to do that. Once you have it rooted, follow this video:
I can't post links yet, so go to youtube and search for this title:
How to Install Android Market - Rooted Kindle Fire (No ADB, V2)
Works like a charm!
A) Before using the Kindle Fire Utility to install TWRP, I DO need to uninstall BurritoRoot on my Kindle, correct?
B) Since I'm going to lose all my apps anyway, should I delete the ones that are not necessary for the process?
C and D) I do actually use my Fire to read PDF books, will Adobe Reader still work as it should? Where do I put the files when I transfer them from my computer to my Kindle?
I've got everything downloaded and ready to roll. I'm going to bed and plan on flashing in the morning, just need these questions answered before I do. Thanks.
A) I rooted before I even knew what TWRP was, so no.
B) You could if you want to.
C) I don't know, but I could test it.
D) The update.zip and gapps? You could put them on the root of your "sdcard," or you could create a folder for them.
UPDATE: I tested Adobe Reader and it seems to work fine.
Sent from my Kindle Fire using XDA Premium.
Another Question or two
il Stalk3r li said:
A) I rooted before I even knew what TWRP was, so no.
B) You could if you want to.
C) I don't know, but I could test it.
D) The update.zip and gapps? You could put them on the root of your "sdcard," or you could create a folder for them.
UPDATE: I tested Adobe Reader and it seems to work fine.
Sent from my Kindle Fire using XDA Premium.
Click to expand...
Click to collapse
I rooted with BurritoRoot, and yes, I found out that I do need to uninstall it before I use the Kindle Utility to install TWRP(v. 0.9).
Is there anything else I need to do before I do this?
Not the gapps, the PDFs I want to read in Adobe reader, where would I place those is transferring from my computer?
Sorry for all the questions I just want to be thorough and make sure I have every single thing right.
Thanks
Did you install the drivers that came with the Kindle Fire Utility? Do you have 0x18D1 at the end of the adb_usb.ini file? Those steps helped me most when my first install of TWRP2 wasn't done correctly. An extra step I took was downloading techerrata.com/file/twrp2/twrp-blaze-2.0.0RC0.img and adding it to the recovery folder of the KFU. Then I renamed it to twrp.img and the other to twrp.img.bak. I don't know if that helped, but after all of that was covered my second install was successful.
You could put your PDFs in a folder on your kindle. It doesn't matter really, as long as it is some place you can find them. Hopefully this helps you and if you have anymore questions I'll be glad to answer them if I can.
- il Stalk3r li
You would place your PDF files on the SD card (the file system you can access from your computer when you connect via USB) either in the root or a folder such as books.
You would then install PDF reader or Kindle reader from the market in order to read the files.
Finally, install a good file manager (or if you are installing an alternate rom such as CM7 it comes with one) such as ES file explorer (free) or Root Explorer (paid). Navigate to your files and click on the one you want to open. A popup may ask you to choose your reader if you have both the above installed. Adobe will keep a list of recently opened files so you will not have to go through the file manager again for any previously accessed docs.
il Stalk3r li said:
Did you install the drivers that came with the Kindle Fire Utility? Do you have 0x18D1 at the end of the adb_usb.ini file? Those steps helped me most when my first install of TWRP2 wasn't done correctly. An extra step I took was downloading techerrata.com/file/twrp2/twrp-blaze-2.0.0RC0.img and adding it to the recovery folder of the KFU. Then I renamed it to twrp.img and the other to twrp.img.bak. I don't know if that helped, but after all of that was covered my second install was successful.
You could put your PDFs in a folder on your kindle. It doesn't matter really, as long as it is some place you can find them. Hopefully this helps you and if you have anymore questions I'll be glad to answer them if I can.
- il Stalk3r li
Click to expand...
Click to collapse
Do I need to install the Kindle Fire Utility drivers while my Kindle is hooked up, or does it matter?
I don't think it matters.
Sent from my Kindle Fire using XDA Premium.
This is for those on ICS only. If you have upgraded to jellybean, this will not work.
There have been other posts, and this one is nothing new, in fact it's a remake of DebugfsRoot so that author gets all credit. I just made a couple of tweaks to help those that might be having a fuss with it. First, this is assuming you are using a windows PC. I don't work on MACs. Next, make sure you have ADB working properly on your PC. To do this:
Go to your start menu and open a command prompt, usually by typing "cmd" in the run blank.
Type adb
If you don't get a whole heap of feedback of how to use adb returned to you, and instead get an error, you don't have it set right. If you're sure you installed the development kit and you have ADB on your PC, do the following:
FIND IT... and add it to your system path variable. adb.exe comes with the root extract, so if you don't have the kit installed, you can use that instead, but seriously, if you want to root and enjoy this hobby to its fullest, install the android kit. The most common location is "C:\Program Files (x86)\Android\android-sdk-windows\platform-tools" - but hey, get this, did you know the asus sync software available from their site also includes it? I just now found that out haha...
To add whichever absolute path to your system path variable, start menu > control panel > system > advanced system settings > environment variables button > In the system variables window, scroll down to path, click it, click EDIT > move your cursor to the very end and add ; again that's (semi-colon) - you'll see other entries there which show you, just follow the pattern. Remember, you only need to do this if your original attempt at typing adb didn't work. Save your settings, return to that command window, and try adb again, you should have better results this time.
Now then, download the root package here:
https://dl.dropbox.com/u/33560221/DebugfsRoot_v1.8.exe
This is the original software with slight enhancements by me...those enhancements are all to the BAT file, and are as follows:
The EXE file is a self-extracting archive which will extract the contents to C:\tabletroot Please don't change this install location. You'll see why in a moment. the RootDebugfs.bat was edited as follows:
Within each push command, I preceeded the file name with C:\tabletroot so it knows exactly where to find what it needs. I found if you just pushed without it, it didn't like it too much.
Last, after each "wait-for-device" command, I added TIMEOUT 120 This forces the batch file to sleep for 2 minutes allowing plenty of time for your tablet to reboot. I found if you didn't do this, it would try to do the next commands way too soon causing failure. This should give enough time for you to get to your desktop before the next command is issued. If you find it's too long and you're ready to go, just press a key and that will kill the clock. If not long enough, edit the batch file with any text editor, and increase the timeout time.
All other files are what was originally found. I didn't update any of the apks or edit any other file than the main batch file. That's it. I used these exact files to root my tf300t on firmware version .30 with no issue of any kind. I hope this helps someone. If you run into trouble, not sure how much help I can be. I'm simply posting exactly what I did. I didn't author anything other than the edits mentioned above. Good luck.
Did the your_path thing and it didn't work.
Could you describe just a bit more which part you're having trouble with and what happened?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
I added ;<your_path> at the end of the path and it did not change anything in the CMD window after imputing adb, when nothing happened before.
I'm sure it's something that I did not do that went wrong.
The your path thing was just a descriptor. You need to replace that with the location of your adb.exe file so it would look like ;c:\program files\ ... and so on. I gave a sample path of where mine is but it could vary between systems.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Well if my previous answer doesn't prove I've never rooted anything...
Where do you DL the adb file from?
Couple Choices
10010110 said:
Well if my previous answer doesn't prove I've never rooted anything...
Where do you DL the adb file from?
Click to expand...
Click to collapse
OK, I will assume you do not have the android development kit installed, so you still have a couple of choices here:
ADB comes with the archive I directed you to download, so if you download it and run the EXE, you'll find ADB inside the newly created folder I mentioned, so using this method, you would add... ;C:\tabletroot
ADB also comes with the ASUS sync software found on the ASUS website. If you have / will download and install this software, the ADB file will be located here: C:\Program Files (x86)\ASUS\ASUS Sync or it might be in C:\Program Files\ASUS\ASUS Sync just depends on the type of system you have. I have a 64-bit OS, so I have a Program Files and a Program Files (x86) folder (the x86 is for 32-bit programs) - in this situation, you would want to add ;C:\Program Files (x86)\ASUS\ASUS Sync or ;C:\Program Files\ASUS\ASUS Sync
Remember if you go with option one, download the archive I provided and run it before you add / test to your path variable, because that's what puts ADB in place. Once you have that all done, just go run the BAT file - after you connect your tablet and can see it on your PC as a media device that is
Clarification
So using this method do we need the blob files or was that just for downgrading, and since we don't need to downgrade using this method, everything that we need is in that self extracting exe file? I'm not interested to unlock bootloader -for now-...just want a few tweaks and to install a few root apps
Sorry, I only have experience rooting a couple HTC devices and they were both 1 touch and rooted.
I hear you, and they are legit questions. This is for rooting only. This procedure doesn't unlock your bootloader, which is why i used it. All you need is in the archive.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Another question, do you have to put the tablet into any special mode in order for the batch file to work? If I remember correctly, the phones just had to be on, plugged in via usb (duh) and the batch files did the rest. The batch file has the 120 second pause, but it seems like it does the first part with -
1. waiting for device to be detected
2. daemon not started
3. daemon started successfully
then it just sits there, and its been longer than 2 minutes...what am I missing?
Only mode i know of is to put it in media mode mentioned above. Also I've read to turn off asus sync found in the sync section of settings.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
HandicapFailure said:
Another question, do you have to put the tablet into any special mode in order for the batch file to work? If I remember correctly, the phones just had to be on, plugged in via usb (duh) and the batch files did the rest. The batch file has the 120 second pause, but it seems like it does the first part with -
1. waiting for device to be detected
2. daemon not started
3. daemon started successfully
then it just sits there, and its been longer than 2 minutes...what am I missing?
Click to expand...
Click to collapse
Either unknown sources, or USB debugging might need to be on.
Ah yes forgot those. I'd do both thankya.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
FYI the batch file does not work with windows xp, I searched and seems timeout is not supported. Sucks having an old OS..
I ran the commands manually and the root worked, so thanks anyway!
rickc3k said:
FYI the batch file does not work with windows xp, I searched and seems timeout is not supported. Sucks having an old OS..
I ran the commands manually and the root worked, so thanks anyway!
Click to expand...
Click to collapse
Wow, I didn't know that. Thanks for the tip.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
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.
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?