I have a Kindle Fire HD 7" system version 7.4.3 that has the proverbial "Red Triangle" of death.
This unit has not been rooted and I am very much a newbie.
I have rebooted the unit many times. Periodically it will work and then lock up again with the Red Triangle.
90% of the time I no longer have wireless access as this has been disabled with the error.
After reading many of the posts here, I have considered rooting it to a) back up my system files (including email) and b) reloading the software. However, if I am not mistaken, I need to load an ADB file. Since the "Enable ADB" under Security Settings is on OFF and cannot be turned on, is there any way that I can revive this unit?
What I would really like is to back up those hidden system files that include email files, program data, etc. as well as make this work like it used to.
Can any one help me?
Without adb on you can't do much, you could just reflash the system image from fastboot, but you would probably need a fastboot cable since u don't have adb or root access. On the bright side a system reflash only reflashes the system partition, you won't lose any of the data for any of the apps. It also is prerooted, so you don't have to worry about doing that later. There's a tool that does the work for you in the android development section called kindle fire system restore tool. You will still need a fastboot viable to run this tool though. Also I haven't looked into it but I thought the red triangle thing was a kf2 error, but maybe I am mistaken?
Edit: I'm a moron, red triangle is the useless stock recovery on the kindle. Least thats my best guess.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Without adb on you can't do much, you could just reflash the system image from fastboot, but you would probably need a fastboot cable since u don't have adb or root access. On the bright side a system reflash only reflashes the system partition, you won't lose any of the data for any of the apps. It also is prerooted, so you don't have to worry about doing that later. There's a tool that does the work for you in the android development section called kindle fire system restore tool. You will still need a fastboot viable to run this tool though. Also I haven't looked into it but I thought the red triangle thing was a kf2 error, but maybe I am mistaken?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I do have a factory cable (same as fastboot cable?) from SkOrPn, but will have to look through the forum for how to do a system reflash. I am glad to know that I have an option to save all of my data.
Unfortunately the red triangle is not limited to the kf2, but don't I wish it was.
Thank you.
Try this: http://forum.xda-developers.com/showthread.php?t=1951254
If that doesn't work try kffa in the general 7" forum.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Since I am such a newbie, I have a couple of questions:
1) Can I assume that the "KFHD_SRT_v1.3.5- 7.3.0 (separate option for restoring factory recovery)" would be the option that I should use for my KFHD running system version 7.4.3? If I read thru this correctly, it will reset the system back to 7.3.0 and then auto update to 7.4.3 once connected to the internet. Is that correct?
2) If so, step 2 says to enter a command if your device recognizes ADB. Will this work on my device since the ADB option is turned off?
Thank you again for walking me through this process. [And by the way, you are not a moron. ]
Step 2 is misleading, you only need that command if you don't have a fastboot cable. I personally haven't had to use this tool, but from what I know it kinda downgrades the system but it should update on its own which also unroots it. And yes the download you were talking about it should be the right one.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
After downloading the KFHD System Recovery Tool (that took a long while) and installing the driver for my KFHD, I am now running the SRT batch file. I am afraid that I am a bit confused here. The batch file gives you the following 7 choices:
1) Restore-Factory Rooted with SuperSU.apk
2) Restore-Factory Rooted with SuperSU.apk, Apex Launcher, and PlayStore
3) Restore-Factory Recovery
4) Erase cache & userdata
5) Check fastboot status
6) Reboot normally (must have a standard cable connected to work)
0) Exit
According to the instructions, I am to select #4 and Erase cache & userdata. Won't this erase my hidden system data (i.e., program data, email, etc.)?
Please advise before I take the next step.
I would use option 1 or 2, idk y it says to use 4.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
I would use option 1 or 2, idk y it says to use 4.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Okay, my KFHD is in Fastboot mode (or at least that is what is displayed on it's screen).
However, my PC found new hardware - Tate-PVT-08 and needs the driver for it. Do you know where I can find this driver?
The SRT Tool is stuck in "trying to locate device" in the interim.
UGH, I am so close and yet so far away.
Just FYI, I had to go way back to remember CMD line instructions, but I also tried typing in the "fastboot -i 0x1949 flash boot boot.img" command. This generated an error message of "fastboot is not recognized as an internal or external command, operable program or batch file."
pi lady said:
Okay, my KFHD is in Fastboot mode (or at least that is what is displayed on it's screen).
However, my PC found new hardware - Tate-PVT-08 and needs the driver for it. Do you know where I can find this driver?
The SRT Tool is stuck in "trying to locate device" in the interim.
UGH, I am so close and yet so far away.
Just FYI, I had to go way back to remember CMD line instructions, but I also tried typing in the "fastboot -i 0x1949 flash boot boot.img" command. This generated an error message of "fastboot is not recognized as an internal or external command, operable program or batch file."
Click to expand...
Click to collapse
Oops, now I am the moron.
I was in the wrong folder/directory. However, when I moved to the KFHD_SRTv.1.3.5 folder and entered this command, the new error message is "cannot load 'boot.img' - so what gives?
I have no idea, usually if someone gets stuck with this app I recommend using kindle fire first aid, it can do the same thing and probably has a better rep. I just prefer individual apps so I recommended this. http://forum.xda-developers.com/showthread.php?t=2096888
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
I have no idea, usually if someone gets stuck with this app I recommend using kindle fire first aid, it can do the same thing and probably has a better rep. I just prefer individual apps so I recommended this. http://forum.xda-developers.com/showthread.php?t=2096888
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Okay I have my KFHD temporarily back up again. It is more functional than it was, but not all applications are running yet.
I haven't tried the KF First Aid yet, but will. I have downloaded the zip file and extracted the files so that I will be ready. Not sure yet if I have to upgrade my Java (it is SE v7up25, but not the developer version).
However, before I proceed much further, I really want to back up my KFHD.
- My data has been "backed up" by making a copy via a USB cable and Windows Explorer to my flash drive.
- What is left to back up is the hidden section/partition of my KFHD. All the postings I have seen so far discuss backing up the system (OS) of the KFHD, but what about the area where applications store user profiles and/or data. For example, the email program stores all the email data in this hidden area. How can I get that backed up?
Once this is accomplished, I would feel much more comfortable in running the KFFA as well as the replacement of image files.
Any clues?
If u can find the email app's internal name you are using then goto "/data/com.emailappname" and copy that folder, usually that's where a program stores its data, not positive about that on the kindle is though, last time cleared my cache and dalvik cache on that os, I had to reset up my email account so I don't know for sure if that's correct exactly.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Try this dude
https://www.youtube.com/watch?v=k-8lTMLCGfE&feature=youtube_gdata_player
Sent from my SGH-T989 using Tapatalk 2
stunts513 said:
If u can find the email app's internal name you are using then goto "/data/com.emailappname" and copy that folder, usually that's where a program stores its data, not positive about that on the kindle is though, last time cleared my cache and dalvik cache on that os, I had to reset up my email account so I don't know for sure if that's correct exactly.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Okay after multiple manipulations, I have run the KFHD SRT using Option 1) Restore-Factory Rooted with SuperSU.apk (WooHoo!)
Can I assume that my KFHD is rooted? If so, what do I need to do to actually see these hidden files? (The email program is e-mail.apk or so I have been told.)
Of course with the standard USB cable, I still see the usual stuff with Win Explorer.
What is my next step?
:victory:
Related
I guess I'm missing something really simple. I've bricked my KFHD 7 and have a red screen. I'm trying to follow the tutorial here http://forum.xda-developers.com/showthread.php?t=2273638 and it's telling me to enter the command
fastboot -i 0x1949 flash bootloader kfhd7-u-boot-prod-7.2.3.bin
Where exactly do I type this command? I've tried searching the forums, but I must not be using the correct key words to find what I'm looking for.
You type this into a command prompt on windows. If u don't knows where command prompt is its on the start me it's under accessories I think. Anyways if u don't have the android SDK installed, then download one of the utilities on the forum that has fastboot in it like I think kindle fire first aid does. From there you would have to CD into that directory that fastboot is in and put your bin file your flashing in the same directory for convenience. If this was too complicated i can maybe explain it better.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
You type this into a command prompt on windows. If u don't knows where command prompt is its on the start me it's under accessories I think. Anyways if u don't have the android SDK installed, then download one of the utilities on the forum that has fastboot in it like I think kindle fire first aid does. From there you would have to CD into that directory that fastboot is in and put your bin file your flashing in the same directory for convenience. If this was too complicated i can maybe explain it better.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Ok, I follow part of that. I have already installed KF First Aide and I have my device in Fastboot. I also have Andriod SDK installed. Whats I'm losing you on is where to put Fastboot. When you say CD into the directory with Fastboot and put my bin file there what exactly do you mean. Where do I get said bin file?
bora1.8t said:
Ok, I follow part of that. I have already installed KF First Aide and I have my device in Fastboot. I also have Andriod SDK installed. Whats I'm losing you on is where to put Fastboot. When you say CD into the directory with Fastboot and put my bin file there what exactly do you mean. Where do I get said bin file?
Click to expand...
Click to collapse
With all due respect, this may be too far beyond your capabilities at the moment. If you aren't 100% clear in what you are doing, you stand a good chance at permanently bricking your device.
Before you do anything else, you'll need to get very comfortable with the command line interface and be able to navigate it with ease.
http://www.computerhope.com/issues/chusedos.htm
http://www.cs.princeton.edu/courses/archive/spr05/cos126/cmd-prompt.html
Once you have that figured out, then you need to get an idea of what you're dealing with. Modifying the 2nd generation Kindle Fires is not a task to be taken lightly. They are not as forgiving as their 1st generation counterparts and can be permanently bricked very easily. Be sure to read the Frequently Asked Questions thread posted at the top of the Q&A forum to better understand what you should do and what you should avoid. Having said that, tools like the KFFA are nice, but are not to be used as a substitute for "good old fashioned" know how.
You have been warned.
Take your time, learn what you are doing, be careful, and good luck.
Thanks for the warning. I'm willing to take the risk. Worst case I'm out $169 and best case I fix it and start tinkering with it all over again.
OK well that tutorial is vague in the sense I don't see any links to that file it references. If u backed up your kindles boot loader before doing this then I would tell u to run that command with a different file, but I don't know if u made backups. I don't know if kindle fire first aid has then option to fix your bootloader because I haven't used it. If worst comes to worst I can upload my bootloader's backup, if I remember correct,y they should work on all kindles that are 7inch hd's. To make what I'm saying clear that command they were telling you to run means it wants your PC to flash that file at the end to your kindle. Problem is you said you don't have that file, so running the command is pointless. I thought the kindle fire system restore utility might be of help, but it says it flashes the boot partition, not the boot loader partition, and the boot partition is just where the kernel for the os is stored so that isn't of help. Just tell me if u made backups before you tried to install twrp and 2nd bootloader, and I may be able to help you more. Also mention whether u were able to get your kindle into fastboot mode, in your case u would of had to use a fast boot cable to do so. Because before we can even flash it the kindle has to be in fast boot mode.
Edit: while Pershing the forums I found the old boot loader that should be used in the process of flashing twrp from a newer is. If u can get into fast boot you will need this file if you don't have backups, rather than me sending you mine.
http://goo.im/devs/Hashcode/tate/kfhd7-u-boot-prod-7.2.3.bin
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Well my problem its different that the ones I've looked over the forum.
I get the cyanogenmod installed , and then I wait for almost 45 mins, with the cyanogenmod logo.
Then it suddenly comes with the new android unlock screen for like 1 second and then it begins again with the cyanogenmod.
But to resolve it, I just turn off the kindle go to teamwin boot and then just restore.
Then it becomes like factory settings..
But I can't get the cyanogenmod to work no matter what.
What I'm missing...
Did u check the cm 10.1 zip files md5 checksum before flashing it? You should always do this, you can do it in es file explorer by going to a files properties and calculating the md5. Compare it to the md5 from the post where u got it from, if its different then re-download it..
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Well I downloaded everything from this post.
http://forum.xda-developers.com/showthread.php?t=2245335
and followed the instructions...
I don't really know what's the "md5 checksum"
I only rooted and did the 2nd-bootloader + TWRP 2.6.0.0 for the Kindle Fire HD 7
from this tutorial:
http://forum.xda-developers.com/showthread.php?t=2271909
But I don't recall seeing anything related with "md5 checksum"
seekario said:
Well I downloaded everything from this post.
http://forum.xda-developers.com/showthread.php?t=2245335
and followed the instructions...
I don't really know what's the "md5 checksum"
I only rooted and did the 2nd-bootloader + TWRP 2.6.0.0 for the Kindle Fire HD 7
from this tutorial:
http://forum.xda-developers.com/showthread.php?t=2271909
But I don't recall seeing anything related with "md5 checksum"
Click to expand...
Click to collapse
Try downloading again, make sure file size is the same as the website says and md5 is the numbers in the description, just above the file or below, also try (make backup first) wipe cache, dalvik cache, data,system, flash rom , flash gapps, wipe internal, wipe dalvik, then reboot
stolen from my drunk kindle by Tapatalk 4
Well looks like I erased everything and it says I don't have a OS installed, but now the cyanogenmod zip its not in the sd card of the kindle.
So I have nothing to flash with, and it won't go to the locked screen.
But I'm stuck with the Team Win recovery project menu .
So its there anything I could do to copy the zip from my pc to the kindle so I can flash it, or even restore it so I can connect my kindle to my pc?
Thanks!
Your going to have to plug it into your PC and use adb sideload to put the zip file on it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Your going to have to plug it into your PC and use adb sideload to put the zip file on it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Well Im going to look more info about that adb sideload.
Thanks!
stunts513 said:
Your going to have to plug it into your PC and use adb sideload to put the zip file on it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Guys so sorry to bother u guys again , idk why I have such a big problem following instructions today...
I have flash my android phones before, I tho this was gonna be just like it...
But I was following this thread and nothing so far..
http://forum.xda-developers.com/showthread.php?p=37594973
if u guys got anything I could use.
Thanks!
Eh well I was hoping for more specifics, but I will tell you what I can, because I haven't ever had to use adb sideload. First go into twrp and hit advanced, them hit adb sideload and swipe to start. If your device manager doesn't have the drivers installed for your kindle when its in twrp for adb, you will need to install them, if you have installed adb drivers before and are running the latest twrp version for kindle(2.6.0.0 I believe), then it should be pretty much plug and play, but if you are running an older version of twrp you will need to force install the adb driver for that device because it didn't have the same vendor ID as the kindle like the new twrp has. Usually I think u just have hit update driver and tell it to let u browse for the driver manually, then uncheck only show compatible device drivers( it says something relatively similar to this) and look for the adb driver, can't remember if its the adb composite device or a different one. If all goes well and u haven't got driver issues, which I hope you don't because I think my tut was a bit lacking for installing drivers, then u should goto a command prompt and CD into the directory u have adb in, it would be in the android SDK, or a utility like kffa, anything that comes with adb will do. Make sure to put the zip u are side loading in the same directory as adb.exe. after that just type adb.exe sideload zipfilename.zip. that should put it on your kindle.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Well I tried that a few times already the adb sideload.
and i just loads, and does nothing, I even waited for an hour, and wouldn't finish :S
So I just think the adb sideload its not gonna do it :S
Just in case u didn't understand whats my problems.
It won't boot up because it has no OS.
So I can't put anything in the sd or backup because I accidently erased everything... even the zip from my sd(cyanogenmod )
I will have to test out adb sideload on my PC to get a better understanding of whats going on, keep in kind I use Linux and not windows, so I don't have driver issues, though I guess you are past any issues that would occur with drivers. Just to validate while I check, but u did put the file u want to side load in the same folder as the adb.exe and you are sure u ran the command correctly? Just thought I'd mention windows doesn't show file extension by default, so make sure u add the .zip to the filename if you didn't already when u type the command.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
I will have to test out adb sideload on my PC to get a better understanding of whats going on, keep in kind I use Linux and not windows, so I don't have driver issues, though I guess you are past any issues that would occur with drivers. Just to validate while I check, but u did put the file u want to side load in the same folder as the adb.exe and you are sure u ran the command correctly? Just thought I'd mention windows doesn't show file extension by default, so make sure u add the .zip to the filename if you didn't already when u type the command.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Thanks for the fast response
So I'm guessing I'd have to put the" cm 10.1 in the same folder as the adb tools(where are 2 .exe fastboot and adb) just to make sure we are talking about the same thing lol.
But I think I did the command wrong.
because I got to the part of the cmd and running the adb, but then I get nothing when I try to push the file to the sd.
Just to make sure can u put the command again
this its the name of the .zip : cm-10.1-20130725-NIGHTLY-otter2
and this its where its located : C:\Users\seekario\Desktop\ADB-Tools
Thanks so much for your time also!
seekario said:
Thanks for the fast response
So I'm guessing I'd have to put the" cm 10.1 in the same folder as the adb tools(where are 2 .exe fastboot and adb) just to make sure we are talking about the same thing lol.
But I think I did the command wrong.
because I got to the part of the cmd and running the adb, but then I get nothing when I try to push the file to the sd.
Just to make sure can u put the command again
this its the name of the .zip : cm-10.1-20130725-NIGHTLY-otter2
and this its where its located : C:\Users\seekario\Desktop\ADB-Tools
Thanks so much for your time also!
Click to expand...
Click to collapse
OK so type this: adb.exe sideload cm-10.1-20130725-NIGHTLY-otter2.zip
That command should work, just to make sure I'll mention it again, before u run the command, in twrp goto advanced, adb sideload, and swipe the thing to the left, afterwards run this command.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Just download kindle fire first aide and run option to restore into stock 7.2.3 and there should be good as new( fast boot required )
stolen from my drunk kindle by Tapatalk 4
So I put the command and now it says
*cannot read 'sideload' *
any ideas ? thanks!
south956 said:
Just download kindle fire first aide and run option to restore into stock 7.2.3 and there should be good as new( fast boot required )
stolen from my drunk kindle by Tapatalk 4
Click to expand...
Click to collapse
I tried that first, and to reboot into fastboot I have to be in the menu, but I have no OS so I can't load anything, it just stays in the kindle fire logo.
I can only access to the Team Win recovery project menu(TWR v2.6) :S
Thanks anyways!
Do you have fastboot cable?
stolen from my drunk kindle by Tapatalk 4
---------- Post added at 10:39 PM ---------- Previous post was at 10:33 PM ----------
Whoa whoa whoa whoa whoa, our device is under Tate not otter2, otter2 is for original kindle fire and not the HD which explains why your stuck in bootloop, find the cm10.1 in Hash codes forum and download that one
stolen from my drunk kindle by Tapatalk 4
south956 said:
Do you have fastboot cable?
stolen from my drunk kindle by Tapatalk 4
---------- Post added at 10:39 PM ---------- Previous post was at 10:33 PM ----------
Whoa whoa whoa whoa whoa, our device is under Tate not otter2, otter2 is for original kindle fire and not the HD which explains why your stuck in bootloop, find the cm10.1 in Hash codes forum and download that one
stolen from my drunk kindle by Tapatalk 4
Click to expand...
Click to collapse
I wish I had, I only have the original cable from amazon :S
I doubt anything can be done til you have fastboot cable, I heard people try adding certain lines in cmd but most say it doesn't work, so a sure fire way would be to either make or buy fastboot cable.
stolen from my drunk kindle by Tapatalk 4
Hi everyone, today i would like to ask for your help with a pretty big problem i have with my Kindle fire HD, you see, i was updating from my current rom 7.4.4 to CM 10.2. to achieve thi i followed this tutorial http://forum.xda-developers.com/showthread.php?t=2271909 , everything was going fine until i installed 2nd-Bootloader and TWRP recovery. The problem came up here, when i realized that i forgot to move the rom and the files for google play into the SD card, now whenever i try to do this i can't seem to get my PC to recognize the Kindle with TWRP (i can browse my files and such with TWRP directly through the kindle itself) i tried to move the required file with adb and fastboot but i can't get it to work.
The kindle is rooted and running version 7.4.6 from amazon.
i have a backup for the rom and the files but i can't use fastboot.
i have a backup for each of the following files: boot0block, stock-boot, stock-recovery, stock-system
all the adb drivers and sdk are functioning perfectly.
When i connect it to my PC with windows 7 i can see the kindle recognized by the device manager but it has yellow triangle next to the icon.
i also tried using an otg cable but the kindke did not recognize it.
any and all help is appreciated, i don't want my tablet to die Dx
I've never had to do this, but in TWRP, if you go to "Advanced," there's a button labeled "ADB Sideload." Then you should be able to use ADB to sideload files onto your Kindle using the "adb sideload" command.
Example:
Code:
adb sideload name of.zip
Hope this helped
>>Sent from my homebuilt TARDIS running Android 4.3... or maybe it's a rooted Kindle Fire HD running ChameleonOS<<
Ph0enix_216 said:
I've never had to do this, but in TWRP, if you go to "Advanced," there's a button labeled "ADB Sideload." Then you should be able to use ADB to sideload files onto your Kindle using the "adb sideload" command.
Example:
Code:
adb sideload name of.zip
Hope this helped
>>Sent from my homebuilt TARDIS running Android 4.3... or maybe it's a rooted Kindle Fire HD running ChameleonOS<<
Click to expand...
Click to collapse
I tried this but the problem is that the pc not find device , it show me in device manager yellow triangle next to the icon of kindle
When i send a adb command , the adb say "Device not found"
Thanks you anyway!
Try updating the device driver for the device with mark next to it, use these drivers from this post, they should work. http://forum.xda-developers.com/showpost.php?p=44446906&postcount=9
stunts513 said:
Try updating the device driver for the device with mark next to it, use these drivers from this post, they should work. http://forum.xda-developers.com/showpost.php?p=44446906&postcount=9
Click to expand...
Click to collapse
Hi and thanks for your help now i try send the next command adb push file.zip /sdcard
but adb say this menssage:
C:\Users\Cristian>adb push file.zip /sdcard
cannot stat 'file.zip': No such file or directory
I put a rom in C:\adt-bundle-windows-x86_64-20130729\sdk\platform-tools in the same folder that adb.exe
and the name of the rom file is : file
Shur'tugal said:
Hi and thanks for your help now i try send the next command adb push file.zip /sdcard
but adb say this menssage:
C:\Users\Cristian>adb push file.zip /sdcard
cannot stat 'file.zip': No such file or directory
I put a rom in C:\adt-bundle-windows-x86_64-20130729\sdk\platform-tools in the same folder that adb.exe
and the name of the rom file is : file
Click to expand...
Click to collapse
Ok if u want to simply type file.zip u need to be CD's into the directory of where u put the ROM, but as it seems u have the SDK in your paths simply putting the ROM in c:\users\cristian should suffice. Try moving the ROM there and running the command again.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Ok if u want to simply type file.zip u need to be CD's into the directory of where u put the ROM, but as it seems u have the SDK in your paths simply putting the ROM in c:\users\cristian should suffice. Try moving the ROM there and running the command again.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Thanks for your help your save my tablet
Thanks you very much
Finally i exit for this bricked
Enviado desde mi GT-I9300 usando Tapatalk 4
I have a dude im install CM 10.2 perfect , but i dont remember install de google apps as i have to do now?
Thanks
One step further
My apologies for hijacking this thread. I had made the same error as the OP. however, instead of searching here for solution, I panicked and wiped the cache and user data using the SR tool and wiped everything. Now unfortunately my kfhd tells me it can't boot, which my incompetent mind tells me is likely because I have no rom?
I've tried to use first aide to do a system recovery but I get told the files are too large and it can't do anything.... Any suggestions or thoughts from people? Appreciate any help I can get. Been up late the last 3 days trying to sort this out, while I thought I was going to provide m wife with a slick android device!!
That's odd, I wouldn't think wipe your data partition and cache would cause that to happen, then again there are some files stored under data the system uses out side of apk's so I guess that could be why. Did you get your kindle into fastboot? If you did I would suggest trying to use kfhd system restore tool if kffa didn't work.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Yes, can fast boot. Shows up when I plug in the factory cable. When I use the system restore tool, and try and do a basic recovery, it can't copy the images over as it says the files are too big.
deeman77 said:
Yes, can fast boot. Shows up when I plug in the factory cable. When I use the system restore tool, and try and do a basic recovery, it can't copy the images over as it says the files are too big.
Click to expand...
Click to collapse
All the files, or just the system.img?
soupmagnet said:
All the files, or just the system.img?
Click to expand...
Click to collapse
each one of them unfort.
Do you have twrp installed?
hloomsc some
soupmagnet said:
Do you have twrp installed?
Click to expand...
Click to collapse
I did. Not sure i do now post trying to do a wipe. Don't see any blue when I start up, just the original kindle letter coloring, after which I get a message saying it can't boot
any suggestions anyone or is my kfhd pretty much killed? there's got to be a way to load some rom on to it!!
You should be able to load the original images over fastboot, something just isn't working right. I would say its far from hard bricked, it should still be fixable, its just a matter of troubleshooting it. If you have the kindle fire system image I would try manually flashing it but you need to know what you are doing. If you CD into the SRT folder where im assuming the IMG files are in the same folder as fastboot, try running "fastboot -i 0x1949 flash system system.img" think I got the syntax right, haven't had to ever use fastboot myself, anyways if you run that what does it report back? Hopefully not the same error, or it might be something messed up with the image.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
thanks for the advice. ended up re downloading the images again and this time it worked. go figure.
back to starting again to get my custom rom on.
once i have a custom rom, guessing there are no amazon bits left in there that would cause any updates to come through right?
Thank god there isn't, I would scream if there was, just make sure to wipe system, cache, dalvik cache and do a factory reset when coming from amazon to cm based ROMs.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Thank god there isn't, I would scream if there was, just make sure to wipe system, cache, dalvik cache and do a factory reset when coming from amazon to cm based ROMs.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Good afternoon: I bricked a nice 8.9 tablet several weeks ago using ADB sideload...
I used ADB Sideload to install Gapps since I was already in TWRP and was too lazy to reboot and transfer the gapps.zip file to my tablet.
The sideload installed the gapps.zip as I expected it to and I was brought back to the main TWRP screen.
When I clicked on reboot/reboot system, the tablet started flashing the three partitions (boot, recovery and system) as I was watching. TWRP then left me at the booting screen doing nothing. I did not know why the tablet decided to flash the three main partitions but, I opted to push the power button and that was the last time I saw my tablet.....
Apparently ADB sideload is only for ROM's? I had only used it to flash ROMs prior but, I thought ADB Sideload should be able to install any properly zipped file designed to flash with TWRP?
Regards
Hi all,
I'm new here, and I've been trying for the past few hours to root my Kindle Fire HD 7" so I can install a CM10.1 ROM and turn it into a google tablet. I've been searching the web for information, and I kept getting directed here so I decided I might as well join.
Anyway it seems the one method that works is the Bin4ry one, and I started following the instructions given on this site and others. However when I installed the driver, it said the installation was successful but when I clicked "Finish" a window popped up and told me the driver didn't install properly. Then I tried to execute the "Run Me" file, but it gave me this:
"Please connect device with enabled USB-debugging to your computer.
the system cannot find the path specified
doing a backup first, please confirm this on your device
the system cannot find the path specified
Done!"
Nothing happens on the Kindle Fire. But I checked the Device Manager, after I downloaded and installed a driver linked in a thread on this forum, it said the Kindle was USB-enabled interface. Anyone have any idea what the problem is, here? Thanks
Ok did you enable usb-debugging in the kindle's security settings? If you have try opening a command prompt and CD into the directory of the adb command in binary's root tool, run adb devices and see if the kindle is listed.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Ok did you enable usb-debugging in the kindle's security settings? If you have try opening a command prompt and CD into the directory of the adb command in binary's root tool, run adb devices and see if the kindle is listed.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Yep, USB-debugging is enabled. It's the same thing as enabling ADB, right? This is what I've done thus far. I'm running Windows 8, so I've disabled driver signature enforcement, and also installed the drivers. I've checked Device Manager---the system has recognized the Kindle as a Google Android ADB interface, and if I check adb devices in cmd prompt, the serial number of my Kindle is listed. Also created an adb_usb.ini file according to these instructions:
"open adb_usb.ini with notepad
(add on one line each!)
0x1949
0x006
save file."
The problem now is not that nothing happens on the Kindle when I run the root tool, I do get the option to restore data but it prompts me to enter a data encryption password. I researched this and a techleopard article said to enter my Amazon password, which I did but nothing happens. The data restore options (Restore or Do Not Restore) just grey out and the root tool just says "Running" for ever and ever. Tried some other root tools such as Quemp and Kindle Fire Utility, but neither worked and besides the more recent information I've seen have Bin4ry's as the only one that works on 7.4.6 which is the OS I am using.
EDIT: Okay, tried it again and for some reason this time the root tool ran successfully. I did a power reset, and ran a RootChecker, and it says it's rooted but I can't find the SuperUser app (the checker also could not find it). Was the root still successful?
Probably though I am throwing a guess that only the such binary is installed, look in the /system/xbin folder and see if the such binary is there, if you want to to retry the process just delete that file. I was going to mention the encryption password is whatever your lock screen code is set to.
BTW don't ever use kfu to try to root your kindle, it will hard brick it. Its designed only for kf1's.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Probably though I am throwing a guess that only the such binary is installed, look in the /system/xbin folder and see if the such binary is there, if you want to to retry the process just delete that file. I was going to mention the encryption password is whatever your lock screen code is set to.
BTW don't ever use kfu to try to root your kindle, it will hard brick it. Its designed only for kf1's.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Heh, actually after a LOT of messing around, and perusing several articles across the web and on xda, I've got it working. KFU didn't brick anything, just didn't work. My only regret is that I now can't access the HD quality movies I'd bought from Amazon because Amazon only allows downloading to the Kindle and the Kindle only, and my internet isn't fast enough to stream HD.
I've tried a bunch of tutorials on here to fix this, but can't figure it out.
I was on my Kindle HD 8.9" running CyanogenMod 10.1, which it has for a year. Suddenly, I got some popup last night. It said there was a nightly build update in my notifications area, so I just clicked "OK" and let it do its thing. It installed for a little bit, all was okay... but now I cannot access my Android OS.
I went to turn my Kindle on after the update, but it keeps going to TWRP. What will happen exactly is it starts... orange letters... then blue letters... then restarts again to orange letters... then blue letters... then TWRP. Why does it keep going to TWRP? How do I fix this?
My Kindle can't even connect to the PC. I just either get "Unknown Device" or "Kindle" in my Device Manager, and mounting from TWRP does nothing.
Then I try installing the Android SDK to get the ADB on my machine, and I added the "Path" in my environment to the two tools folders, but nothing... same thing happens. Constant loop into TWRP. Driving me nuts.
The update it wanted me to install when I could still get into the Android OS was cm-11-20140420-NIGHTLY-jem. I thought maybe trying to connect my Kindle to my PC in order to open the drive, then pasting the cm-11-20140420-NIGHTLY-jem into a folder and installing again from TWRP would solve my problem, but I can't even get that far.
I'm at a loss. Please help.
GogoplataMMA said:
I've tried a bunch of tutorials on here to fix this, but can't figure it out.
I was on my Kindle HD 8.9" running CyanogenMod 10.1, which it has for a year. Suddenly, I got some popup last night. It said there was a nightly build update in my notifications area, so I just clicked "OK" and let it do its thing. It installed for a little bit, all was okay... but now I cannot access my Android OS.
I went to turn my Kindle on after the update, but it keeps going to TWRP. What will happen exactly is it starts... orange letters... then blue letters... then restarts again to orange letters... then blue letters... then TWRP. Why does it keep going to TWRP? How do I fix this?
My Kindle can't even connect to the PC. I just either get "Unknown Device" or "Kindle" in my Device Manager, and mounting from TWRP does nothing.
Then I try installing the Android SDK to get the ADB on my machine, and I added the "Path" in my environment to the two tools folders, but nothing... same thing happens. Constant loop into TWRP. Driving me nuts.
The update it wanted me to install when I could still get into the Android OS was cm-11-20140420-NIGHTLY-jem. I thought maybe trying to connect my Kindle to my PC in order to open the drive, then pasting the cm-11-20140420-NIGHTLY-jem into a folder and installing again from TWRP would solve my problem, but I can't even get that far.
I'm at a loss. Please help.
Click to expand...
Click to collapse
boot into twrp, check what version of twrp you have. Then you may need to update your twrp to be cm 11 compatible if its not at latest version, current version is like 2.7.0.0(least it is for the 7", havnet check to see if that builds out for 8.9 as well), anyways check the device manager for a device with a yellow triangle next it, if you don't see that and you do have a adb interface showing up but adb doesnt detect it then uninstall the adb device and mtp device and search for devices, if it still doesnt work look for a component device with a vid of 1949 in the properties>details>hardware id's section, if you find it then remove it and scan for device. Windows is a pain in terms of drivers for the kindle in different modes. Once adb is working its as simple as pushing the rom with adb push. You may need to factory reset and/or wipe internal storage so i recommend backing up the data, i would assume the current bootloop has something to do with either no factory reset before going to cm 11 or selinux issues, but that would mean the kernel didnt flash in the ota which would be weird.
stunts513 said:
boot into twrp, check what version of twrp you have. Then you may need to update your twrp to be cm 11 compatible if its not at latest version, current version is like 2.7.0.0(least it is for the 7", havnet check to see if that builds out for 8.9 as well), anyways check the device manager for a device with a yellow triangle next it, if you don't see that and you do have a adb interface showing up but adb doesnt detect it then uninstall the adb device and mtp device and search for devices, if it still doesnt work look for a component device with a vid of 1949 in the properties>details>hardware id's section, if you find it then remove it and scan for device. Windows is a pain in terms of drivers for the kindle in different modes. Once adb is working its as simple as pushing the rom with adb push. You may need to factory reset and/or wipe internal storage so i recommend backing up the data, i would assume the current bootloop has something to do with either no factory reset before going to cm 11 or selinux issues, but that would mean the kernel didnt flash in the ota which would be weird.
Click to expand...
Click to collapse
Now I'm all screwed up. Before I saw this message, I restored my Kindle back to when it was still running the factory default OS with root, then I shut it down to enter TWRP, and it appeared on its own, but it was installing some sort of update... and when the Kindle's factory default OS appeared, my root was gone. Now I am stuck on the factory default Kindle HD 8.9" on System Version 8.4.8. Man, I should have never accepted that update and just left it as it was. Ugh. Well, for right now, there's an entry in my Device Manager that says "Kindle Fire" and when you click the arrow to bring down the submenu, it says "Android ADB Interface." The Kindle is now working when connected through USB. Now... how do I go about rooting this thing and getting TWRP on it again, because it seems the entire thing got erased. Not having my ROM installed on this thing makes it mostly useless to me.
Root with kffa or binary's root, think the newest version has different choices than the tutorial, use the old normal method. Last I checked it worked.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
Root with kffa or binary's root, think the newest version has different choices than the tutorial, use the old normal method. Last I checked it worked.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
I can't find anything. Download links are dead for KFFA. You have a link to get it through another source?
They are up and running when I click em. You were on this thread right?: http://forum.xda-developers.com/showthread.php?t=2096888
If that doesn't work you can always use binary's root.
http://forum.xda-developers.com/showthread.php?t=1886460
Use the old normal method if I remember correctly.
Sent from my Amazon Kindle Fire HD using Tapatalk
Nah, the link is dead here. Says the file was removed. There are other members in the forum asking as well for a new link.
I managed to get ADB working, and in Device Manager, I have "Android Device -> Android Composite ADB Interface."
I open CMD and type "ADB" and it scrolls a bunch of stuff, but when I type "ADB Devices" I get a list with nothing there. It's just blank.
I tried using BIN4RY Revision 33, using Option #1, but it just keeps bringing me to a "Path not Found" error of some sort.
It looks like all I need to manage to do now is get ADB to list my Kindle device before attempting the ROOT, but how can I do that?
I still wanna give KFFA a try, but no downloads anywhere, and I don't trust random 4Share and the likes, not that it's gonna fix my problem.
I'm close... I just need this damn ADB to list my Kindle device and I think I'll be okay.
Also, I want to say thanks for the help you've given me so far. It's greatly appreciated. :highfive:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb kill-server
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
C:\Program Files (x86)\Android\android-sdk\platform-tools>
Click to expand...
Click to collapse
i.imgur.com/gZrrqXm.jpg
No problem, i like helping people fix things.
Try uninstalling the device and letting it search for new hardware. This is more than likely a driver issue.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
No problem, i like helping people fix things.
Try uninstalling the device and letting it search for new hardware. This is more than likely a driver issue.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Oh, believe me. I tried that like 50 times. I think I'm just gonna make a virtual machine of Win7, completely clean install without all my drivers everywhere, and try my luck there.
GogoplataMMA said:
Oh, believe me. I tried that like 50 times. I think I'm just gonna make a virtual machine of Win7, completely clean install without all my drivers everywhere, and try my luck there.
Click to expand...
Click to collapse
From the administrator profile on your PC open a command prompt and type Bcdedit.exe -set TESTSIGNING ON then hit enter. Now restart your computer. This will disable Windows driver security enforcement. Then try to install the drivers in the device manager.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
LinearEquation said:
From the administrator profile on your PC open a command prompt and type Bcdedit.exe -set TESTSIGNING ON then hit enter. Now restart your computer. This will disable Windows driver security enforcement. Then try to install the drivers in the device manager.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Unfortunately, that didn't work. I'm pretty sure one or more of my drivers are interfering with the connection to the Kindle, but this is such an old OS with so many drivers, it's hard to tell.
Right now, I have a Virtual Machine of Windows 7 up. I plugged my Kindle in and I can instantly see it. I can even enter the internal storage! I'm currently installing the Android SDK for the ADB after installing the Java SE x86 version. Once I get ADB on it, I'll see if it lists my device now. Seems promising since the VM sees and allows me to already enter the internal storage, unlike my original Win7 OS.
EDIT #1: Great news! ADB now lists my device! Thing is... Root with Bin4ry Revision 33 does not seem to want to work. This is what I get...
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= Idea for Tablet S from Fi01_IS01 =
= (14.12.2013) v33 =
======================================================================
Device type:
0) Xperia Root by cubeundcube
1) New Standard-Root (thx Ariel Berkman)
2) New Xperia Root by Goroh_kun (Xperia Z, Xperia V [JellyBean] ...)
3) Old
4) Old-Special (for example: Sony Tablet S, Medion Lifetab)
G) Google Glass Mode (thx Saurik for the ab file)
x) Unroot
Make a choice: 1
Please connect Device with enabled USB-Debugging to your Computer
The system cannot find the path specified.
Doing a Backup first, please confirm this on your device!
The system cannot find the path specified.
Done!
Press any key to continue . . .
Click to expand...
Click to collapse
It doesn't give me a chance to do anything. All of that pops up as soon as I press enter. ADB and third party software is enabled on my Kindle. ADB even reads my device as:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
B0C9110232560198 device
Click to expand...
Click to collapse
I'm at a loss now. Any ideas?
EDIT #2: Success! The issue was I was using Root with Bin4ry Revision 33. I should have been using Root with Bin4ry Revision 30. That worked, and I am now ROOT. Mission accomplished. Now the next part of my mission... figuring out how to get TWRP on this thing.
Well, trying to install TWRP is going very wrong. I'm using the tutorial here: http://forum.xda-developers.com/showthread.php?t=2128175
Everything seemed to work until I get to Step 3. I'll enter the commands but it tells me that there is no such directory or something. Something about there not being any "stack." Can't recall. I wanted to ask on the thread there but the site isn't allowing me to post there.
adb push stack /sdcard/ is where the issue occurs. Everything else worked.
I'm at a loss, and the comments don't seem to help on that thread. Please tell me there is an easier method of getting TWRP on this thing.
ERROR:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb push stack /sdcard
/
cannot stat 'stack': No such file or directory
C:\Program Files (x86)\Android\android-sdk\platform-tools>
Click to expand...
Click to collapse
GogoplataMMA said:
Well, trying to install TWRP is going very wrong. I'm using the tutorial here: http://forum.xda-developers.com/showthread.php?t=2128175
ERROR:
Click to expand...
Click to collapse
That tutorial is for the 8.9. You want the tutorial for the 7". http://forum.xda-developers.com/showthread.php?t=2218796
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
LinearEquation said:
That tutorial is for the 8.9. You want the tutorial for the 7". http://forum.xda-developers.com/showthread.php?t=2218796
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
He's on a 8.9", he just posted in the wrong section. Use the fireflash method from seokhuns tutorial, just don't forget to check the box with red text near it or you will get a nice redscreen brick. Lemme grab a link
Edit: link grabbed! http://forum.xda-developers.com/showthread.php?t=2277105
I used FireFlash, followed the instruction... now I cannot get passed the first "Kindle Fire" logo when I turn the Kindle on. It just freezes at "Kindle Fire" as soon as I turn it on. I can't seem to do anything at all, and it won't connect via USB. Any ideas?
You missed a check box somewhere. If it is indeed a 8.9" kindle this should be fairly easy to fix. Open the device manager and plug the kindle in while it is off, it should briefly appear as a jem device. While it briefly shows up you need to right click it and hit update drivers and navigate to where you would have downloaded and extracted the drivers in my signature, once you manage to install them you just need to run a "fastboot -i 0x1949 getvar product" with the kindle unplugged and off, and then plug it in once it says waiting for device. It should then go into fastboot mode where you can restore from kffa or SRT.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
You missed a check box somewhere. If it is indeed a 8.9" kindle this should be fairly easy to fix. Open the device manager and plug the kindle in while it is off, it should briefly appear as a jem device. While it briefly shows up you need to right click it and hit update drivers and navigate to where you would have downloaded and extracted the drivers in my signature, once you manage to install them you just need to run a "fastboot -i 0x1949 getvar product" with the kindle unplugged and off, and then plug it in once it says waiting for device. It should then go into fastboot mode where you can restore from kffa or SRT.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
It's not working... it won't read at all. Device Manager doesn't see the Kindle at all. And yes it is 8.9". I think it may be bricked now. ;'(
And all because of that stupid update... ughhhh. Sucks!
You should try the command from a Ubuntu live CD/USB if is a lot easier to do from there, if it won't work from there then I would be convinced something may be wrong with the bootloader, but I don't see the bootloader as the problem because if anything it would have just been downgraded and I'm more inclined to thinking the bootimg is corrupted. That can cause odd behavior with the bootloader. Are you positive this is the 8.9" model and not the 7" model?
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
You should try the command from a Ubuntu live CD/USB if is a lot easier to do from there, if it won't work from there then I would be convinced something may be wrong with the bootloader, but I don't see the bootloader as the problem because if anything it would have just been downgraded and I'm more inclined to thinking the bootimg is corrupted. That can cause odd behavior with the bootloader. Are you positive this is the 8.9" model and not the 7" model?
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
I switched over to my main Windows 7 OS and did what you said. I connected it and it showed for a brief moment in Device Manager, so I quickly loaded the driver and updated. But wen I type the command you gave me, it says <waiting for device>, so I plug it back in and... nothing. At all. Just sits there at <waiting for device>
I'd try Linux, I have several copies of different OS's, but I'm not very good at working with it or using Terminal... I can try that though, but no clue how I'd get ADB or the Kindle to read on it. :\
And yes, 100% it's the 8.9". The resolution is 1200p.
OK the command has to be run while the device is off and disconnected, once it says waiting for device, plug the kindle in and it should work if the drivers are working. Linux is really easy to use with a kindle, it has the fastboot and adb drivers built in natively, only thing you need is the fastboot command from the Ubuntu repos if you are using Ubuntu, believe they were added to the repo in 13.10.
Sent from my Amazon Kindle Fire HD using Tapatalk