Related
I've looked everywhere for an answer to my question and have yet to find an answer. Probably because my Kindle Fire is truly bricked for good. But here is the series of events that lead to my current predicament.
1. I used Kindle Fire Utility 0.9.1 to root and install TWRP.
2. I was ignorant of the uses of TWRP so when I wanted to restore the Kindle to factory settings I did it within the kindle.
3. I ended up in TWRP so I looked up how to force the amazon update to the kindle. I cleared both caches and factory restore and then installed update.zip.
4. When I rebooted I am now stuck on the boot up screen with no access to TWRP. My computer still recognizes the kindle fire, but I can't access the directory of the kindle.
5. I've tried to use fastboot, Kindle Fire Utility, and anything else to knock it out of the boot logo, but I always am stopped by the error: exec "system/bin/sh": No such file or directory
i think you should try to reinstall twrp eighter with kfu or manually
kfu is the easier way - if you will try it manually this would be a good point to start: http://forum.xda-developers.com/showthread.php?t=1414832
then flash one of the prerooted stock images or cm7
b63 said:
i think you should try to reinstall twrp eighter with kfu or manually
kfu is the easier way - if you will try it manually this would be a good point to start: http://forum.xda-developers.com/showthread.php?t=1414832
then flash one of the prerooted stock images or cm7
Click to expand...
Click to collapse
I´m in the same situation. We can´t use kfu because everyrthing it does needs adb shell, wich isn´t working.
I´d love to be wrong, but the only solution we have is getting a factory cable.
adb is'nt working in fastboot - could you give this a try?
fastboot -i 0x1949 getvar product
it should return "kindle"
btw. twrp installation of kfu don't use adb - it works with fastboot
b63 said:
adb is'nt working in fastboot - could you give this a try?
fastboot -i 0x1949 getvar product
it should return "kindle"
btw. twrp installation of kfu don't use adb - it works with fastboot
Click to expand...
Click to collapse
The problem is we are not in fastboot mode. We have normal boot enabled.
your in normal boot and don't have adb available ?
sounds bad - maybe your only solution is really the factory cable !
would you try my last idea ?
do
fastboot -i 0x1949 getvar product
should say <waiting for device>
and power off (hold ~20sec) and power back on before the command times out (~1min)
if we are lucky we should get a response
try it more than one times
b63 said:
your in normal boot and don't have adb available ?
sounds bad - maybe your only solution is really the factory cable !
would you try my last idea ?
do
fastboot -i 0x1949 getvar product
should say <waiting for device>
and power off (hold ~20sec) and power back on before the command times out (~1min)
if we are lucky we should get a response
try it more than one times
Click to expand...
Click to collapse
Thanks, but it doesn´t work. Factory cable is the last hope.
Its not bricked, only missing the .sh in the bin directory. Try these commands from the bootloop screen.
./ adb devices
If device is listed
./ adb reboot recovery
qv775219 said:
Its not bricked, only missing the .sh in the bin directory. Try these commands from the bootloop screen.
./ adb devices
If device is listed
./ adb reboot recovery
Click to expand...
Click to collapse
It reboots the device but not to recovery.
---------- Post added at 05:21 PM ---------- Previous post was at 05:18 PM ----------
osozraz said:
It reboots the device but not to recovery.
Click to expand...
Click to collapse
It looks like flashing the stock rom erases FireFireFire and recovery
osozraz said:
It reboots the device but not to recovery.
---------- Post added at 05:21 PM ---------- Previous post was at 05:18 PM ----------
It looks like flashing the stock rom erases FireFireFire and recovery
Click to expand...
Click to collapse
OK, what you need is a recovery .img file. Once you have the .Ingram file type these commands.
From bootloop screen
./adb reboot bootloader
From bootloader screen
./fastboot flash recovery recovery.img
(Recovery image needs to be named recovery.img)
After flash is done
./fastboot reboot recovery
If have issues from fastboot, reboot the device and from bootloop screen
./adb reboot recovery
qv775219 said:
OK, what you need is a recovery .img file. Once you have the .Ingram file type these commands.
From bootloop screen
./adb reboot bootloader
From bootloader screen
./fastboot flash recovery recovery.img
Click to expand...
Click to collapse
First of all, thank you very much for your help.
I type
adb reboot bootloader
and the device reboots, but
fastboot flash recovery recovery.img
gives the same result as before
< waiting for device >
just a suggestion:
fastboot -i 0x1949 flash recovery recovery.img
or
fastboot -i 0x18d1 flash recovery recovery.img
b63 said:
just a suggestion:
fastboot -i 0x1949 flash recovery recovery.img
or
fastboot -i 0x18d1 flash recovery recovery.img
Click to expand...
Click to collapse
If I am not mistaken, to execute fastboot you have to boot in fastboot mode. My fire is always booting in Normal mode so all fastboot commands i execute have the same result:
< waiting for device >
the adb command suceeded
maybe this helps to get to fastboot:http://forum.xda-developers.com/showthread.php?t=1414832
allthrough i doubt
edit: i saw - we have allready tried - but adb was'nt working before - now it's working ?
edit2: just for info: kfu uses this to switch to fastboot:
adb shell "idme bootmode 4002"
adb shell "reboot"
don't think that this works
b63 said:
the adb command suceeded
maybe this helps to get to fastboot:http://forum.xda-developers.com/showthread.php?t=1414832
allthrough i doubt
edit: i saw - we have allready tried - but adb was'nt working before - now it's working ?
Click to expand...
Click to collapse
Adb works. If I type adb devices it shows my Kindle is connected. BUT when executing adb shell or commands that use the sh like adb logcat it fails with the message from the topic title.
If adb shell were working i could use pokey9000´s program to boot in fastboot.
would need a command like "adb reboot bootloader" but never saw such one
could be creative and try "adb reboot fastboot" but it's a shot in the blue ...
sorry
I think we have the same problem
I think we have the same problem @osozraz. I'll share my experience and add more information that I feel is relevant.
1. I also used Kindle Fire Utility to root my Kindle and install TWRP 2.0.
2. I tried installing CM7, it worked, but figured I'd like to get back to stock firmware.
3. In TWRP, I too cleared both caches, factory restored and then proceeded to install update.zip.
4. When the Kindle rebooted it was stuck on the Kindle Fire boot screen.
Now, I researched and tried a couple of unbricking/debricking methods and failed. Here is what I've observed:
a. My device drivers are fine. If I do 'adb devices' it's recognized by the PC. However if I try 'fastboot devices' it returns nothing at all. I assume
b. I also tried the Kindle Fire Utility. Any command I try to do gets stuck on <waiting for device>. I figured that while KFU commands work on the PC's end, it doesn't work on the Kindle Fire. It's basically as if the Kindle is not connected to the computer (try running some of the commands in KFU with the Kindle disconnected, such as changing the bootmode. It'll still say <waiting for device>).
c. I can't to 'adb root' as it will say I don't have permission. Same with adb 'remount' or even 'adb shell', which from what I've gathered is crucial to this process. I can do 'adb reboot' though. I haven't tried rebooting into restore mode but I will try when I get a new MicroUSB B cable.
d. I can't change the bootmode, it gets stuck on <waiting for device> as I've said in point b. Is there a way to actually know what bootmode your device is in? I'm just assuming it's in normal bootmode because I can get fastboot.exe to detect it on the PC. In addition, KFU returns 'unknown'.
Factory Cable
Of course, there's the method of using a factory cable. I'm trying to create one and from what I've gathered there are two ways to do so: 1) use a breakout board (this one I think is the safest way to go) or 2) hack together one using your existing cable: http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html. I'm also still scouring the forums for additional information that may help debrick/unbrick my device without the use of the cable. I'm afraid that I might end up damaging my PC or Kindle if I create the cable incorrectly. I've been following this thread though http://forum.xda-developers.com/showthread.php?t=1392693 because I'm thinking of actually just buying one.
Hopes these all help.
You are probably out of luck and need a factory cable at the moment.
You wiped /system/ or killed its permissions, and thus it is unable to load shell.
@osozraz and @jkspn looks like we all have the same problem. Thanks for all the suggestions. I've tried everything. Looks like the only option left is the factory wire. Only problem is that I have 0 skills with smoldering. I guess I could buy one but the site doesn't look like it will be restocking anytime soon. I'll see if I can't return it to Best Buy.
shop.teamblackhat.info/Factory-style-programming-cable-for-Motorola-FactCable.htm
When it says waiting for device, what happens when you unplug and plug in the device?
Alright, so my Kindle Fire is bricked, and was stuck at the boot screen (the default Kindle Fire loading screen) after attempting to root it with an outdated tutorial (didn't know this at the time, but the program is called SuperOneClick) then I made another foolish attempt to install TWRP (I THINK I did it to restore the Kindle back to the factory software/defaults but I'm not sure exactly what I was thinking as it was probably 2 weeks ago)... After doing a little more research, I made my way back here because the forums have been resourceful in the past concerning my Evo 4G... After that I found a very similar thread and decided to try my luck once again, had extreme problems trying to get my computer to recognize the Kindle (on both Windows 7 and Ubuntu), all of my settings were correct and are now correct to the best of my knowledge (adb/udev files included)... To this day I still have no luck getting my computer to recognize it, after reading through numerous tutorials/threads I've resorted to buying a "factory cable" because the battery died (while plugged in the wall/usb both it just flashed on and off) and I was told by another member here that it is the only way to bypass the dead battery... Yesterday I've received the "factory cable", but the Kindle still flashes on and off while it is plugged in via usb, and still doesn't show up in device manager, or in command prompt/terminal via adb devices/lsusb commands even after multiple restarts and adb kill-server, adb start-server have been applied... Can anybody help guide me through this??? My faith is running extremely dry at this point, and I'm willing to try just about anything to get this thing right, and learn a few things in the process!!!
Thanks in Advance,
CJ
Firekit http://forum.xda-developers.com/showthread.php?t=1430038
I will help you
And you have done sooo much!!! I've spent a total of at least 12 hours trying to figure this thing out, and getting the terminal to recognize it CORRECTLY is the furthest I've seen so far, even if it was for only one command, for a few seconds... My charging attempt has yet again failed miserably, BUT I have however bypassed the boot loop for about 30 seconds, still staying at the default Kindle Fire screen (tried a random tutorial to trick the Kindle into charging, it MIGHT have worked because it was only plugged in via usb for about 1 minute after this trick but instead of the orange light coming on the Kindle just stayed in the power off looking state)... Even with the boot loop bypassed though, fk did not seem to recognize the device so I'm even more lost than I was originally lol...
EDIT: I am positive the Kindle is receiving a charge, the charge light isn't on BUT it is charging!!! Regardless of the power state no command is working to recognize the device, including "adb devices", "lsusb", and "fastboot getvar product"... I guess that it's possible that one of my files have gone corrupt so I'll check them out again but other than that I'm stumped...
After many trial and error's, and with the amazing guidance of "Thepooch", we have finally unbricked the KF!!! Thank you for your time and patience, if it wasn't for you I would've probably given up by now
Great Job Pooch! You da' man. Glad you got it working!
Was an adventure your welcome though
Sent from my Amazon Kindle Fire using Tapatalk 2
An adventure is an understatement, for me at least but in the end you came through once again and it is up and running like a champ!!!
Sent from my GT-P3113 using Tapatalk 2
Bricked Kindle Fire
I was having trouble using KFU. I wanted to install JellyBean 4.1 and after finding a post to perform some command lines the KFU finally found my KF. I installed the permanent root (i thought) and it rebooted the KF into fastboot it stated. Now it loads to a logo and stops. If I hold the power button (5-10 secs) it shuts off and that is the only thing I can do. It does not show up in my device manager so I feel I killed it. I know you guys have the answer and I apologize in advanced for being a newbie but I am desperate. It looked so easy in the YouTube videos but as always that is the famous last words...
gtc954 said:
I was having trouble using KFU. I wanted to install JellyBean 4.1 and after finding a post to perform some command lines the KFU finally found my KF. I installed the permanent root (i thought) and it rebooted the KF into fastboot it stated. Now it loads to a logo and stops. If I hold the power button (5-10 secs) it shuts off and that is the only thing I can do. It does not show up in my device manager so I feel I killed it. I know you guys have the answer and I apologize in advanced for being a newbie but I am desperate. It looked so easy in the YouTube videos but as always that is the famous last words...
Click to expand...
Click to collapse
Likely your stuck in fastboot shift+ right click on the tools folder in kfu select open command window here power your device off completely leave it unplugged type fastboot -i 0x1949 getvar product when it says waiting for device plug in your powered off kindle it should then power on in fastboot mode if you get the response product: kindle then type fastboot -i 0x1949 oem idme bootmode 4000 it will say okay hopefully the type fastboot -i 0x1949 reboot it should then reboot in normal mode
Thepooch said:
Likely your stuck in fastboot shift+ right click on the tools folder in kfu select open command window here power your device off completely leave it unplugged type fastboot -i 0x1949 getvar product when it says waiting for device plug in your powered off kindle it should then power on in fastboot mode if you get the response product: kindle then type fastboot -i 0x1949 oem idme bootmode 4000 it will say okay hopefully the type fastboot -i 0x1949 reboot it should then reboot in normal mode
Click to expand...
Click to collapse
You are amazing!!!!
GameGuru41 said:
You are amazing!!!!
Click to expand...
Click to collapse
Naww lol don't forget to hit the than button lol
Thank you!!
Thepooch said:
Likely your stuck in fastboot shift+ right click on the tools folder in kfu select open command window here power your device off completely leave it unplugged type fastboot -i 0x1949 getvar product when it says waiting for device plug in your powered off kindle it should then power on in fastboot mode if you get the response product: kindle then type fastboot -i 0x1949 oem idme bootmode 4000 it will say okay hopefully the type fastboot -i 0x1949 reboot it should then reboot in normal mode
Click to expand...
Click to collapse
Pooch thank you buddy very much!! I thought I owned a black brick. Now with that newbie mess out of the way could you help with what went wrong using KFU? It would not find my KF and only when I found something about typing in some command lines (similar to your fix) did KFU finally state the KF was online. I then chose option 2 used the permanent root function and viola a brick. I of course followed all the previous directions about loading drivers and making sure the ADB composite was in the device manager. Can you point me in the right direction?
Thanks again...
gtc954 said:
Pooch thank you buddy very much!! I thought I owned a black brick. Now with that newbie mess out of the way could you help with what went wrong using KFU? It would not find my KF and only when I found something about typing in some command lines (similar to your fix) did KFU finally state the KF was online. I then chose option 2 used the permanent root function and viola a brick. I of course followed all the previous directions about loading drivers and making sure the ADB composite was in the device manager. Can you point me in the right direction?
Thanks again...
Click to expand...
Click to collapse
If your main intent is to flash a ROM no need to root simply just allow installation from unknown sources under device in your kindle settings when you plug it it disconnect the USB transfer app. Then select option for twrp it should reboot then swipe open and stop USB app again this time send fff. Then use the boot loader to enter recovery when there select backup make a backup that you will later name noroot631 without spaces after you have created a backup reboot to os then use the USB app to place a ROM zip and a gapp zip on your SD card but do not place it inside of a folder this is considered the root of your sdcard then boot back into recovery . Go to install make sure you can locate the files you intend to flash then use the back button or home button in upper right to return to twrp main screen. At this point you have a safety net and a backup and you are getting familiar with the functions and learning how to navigate in twrp. Now for a flash if you are gonna flash modaco for the stock like adventure its not required to perform any wipes just simply flash and reboot. No gapps required either now you are rooted If you intend to flash a different flavor like cm7 cm9 or jelly bean it gets a bit more technical . After placing ROM and appropriate gapps on your SD card this time your gonna wipe and its very important you do so!!! First go and wipe factory reset then wipe cache then wipe dalvik here's the scary part wipe system do not reboot you have no system!! There is no need to wipe sdcard or external storage as it is called in the new twrp if you did you would have nothing to flash then hit the home button above right taking you back to the twrp main screen this time select install tap on the ROM zip swipe to install then home again install again this time select gapps swipe to install select reboot and system if prompted. It will reboot initial boot takes time I would say 5-8 mins longer and then you need to be a little alarmed If your greeted by an android for account setup your good congrats your rooted. If boot takes longer than 10 mins hold power button return to recovery restore your backup after the wipes I mentioned above try again later with new ROM and new gapps. Good luck as for kfu awhhh so many things broken for so many people near impossble to say why so many fail to root frankly operator error accounts for at least 80% of failures could be more like 90% . Common mistakes thinking you need to root to flash a ROM, bad drivers windows is terrrrrible,wrong cable,using a 3.0 USB port instead of 2.0, and general miscommunication between the device your computer and the utility. Whewwww all that said install twrp install fff if you can 100% verify that you have both and you know how to use both and move files to your SD card and have made a backup every time before you flash. Then flash Awaaaayyy!!! Hope I didnt miss anything oh and the usual disclaimer know what your doing or you shoot your eye out lol and of course I'm not responsible if you brick your kindle!! Good luck
---------- Post added at 10:57 PM ---------- Previous post was at 10:55 PM ----------
Ohh and if you can't read that I'm sorry for the novel punctuation and such costs more
---------- Post added at 11:11 PM ---------- Previous post was at 10:57 PM ----------
PS as well after creating the huge safety net I explained above go ahead after your backup and select permanent root with superuser you have a backup and a bootloder that resets your boot mode have it but IMO that function is broken for too many people these days I don't recommend it because if our gonna flash a ROM all ROMs are rooted so what's the point?
Thepooch said:
Sent from my GT-P3113 using Tapatalk 2
Click to expand...
Click to collapse
Thepooch said:
Common mistakes thinking you need to root to flash a ROM, bad drivers windows is terrrrrible,wrong cable,using a 3.0 USB port instead of 2.0, and general miscommunication between the device your computer and the utility.
Click to expand...
Click to collapse
So that's probably why I bricked my kindle was due to using a 3.0 port. I don't see how that would affect it though. Either way, I'm trying to charge up the battery on my kindle some since it drained itself to dead over night when I gave up in frustration and went to sleep. Then I'm going to try to unbrick using your methods mentions above and on the first page. If none work you'll be hearing from me again. lol
Well switching to the USB 2 and those commands through dos worked perfectly. Now if only it would download the twrp file. Just can't get a break with this stupid thing.
http://forum.xda-developers.com/showthread.php?t=1836005 twrp problem
where are the simple, easy to follow directions...
to root my Kindle..
All this stuff is overwhemingly confusing for a non-computer speaking person..
I tried to follow the directions listed here:
http://forum.xda-developers.com/showthread.php?t=1638452
but got really confused.
So I read through this thread: http://forum.xda-developers.com/showthread.php?t=1399889 and got even more confused.
I've rooted my Samsung Galaxy SII, but that used a simple one-click process. Trying to decipher the procedures for rooting a kindle fire is confusing to say the least.
Im begining to think that my stock Kindle is ok...
I'd just assume ship my KF off to someone to root it and install a custom ROM.. i've been reading these threads and forums for 3 days now and I just keep spinning myself in circles...
Thepooch said:
Likely your stuck in fastboot shift+ right click on the tools folder in kfu select open command window here power your device off completely leave it unplugged type fastboot -i 0x1949 getvar product when it says waiting for device plug in your powered off kindle it should then power on in fastboot mode if you get the response product: kindle then type fastboot -i 0x1949 oem idme bootmode 4000 it will say okay hopefully the type fastboot -i 0x1949 reboot it should then reboot in normal mode
Click to expand...
Click to collapse
Don't worked here. The triangles keep spinnig and the cmd keeps on <waiting for device>.
Reinaque said:
Don't worked here. The triangles keep spinnig and the cmd keeps on <waiting for device>.
Click to expand...
Click to collapse
Start a new thread and explain your problem in detail.
i wanted to reset my device back to default rom. so i downloaded the zip file via KFU. then i flashed it. however, i forgot to wipe everything. now when i turn on my device and unlock it, it says that all these apps cannot open and i have to force close them. then after like 30 seconds, it closes and i see the kindle fire logo. then it boots up and the same thing happens again. I then tried to reinstall twrp and FFF but it cant because the location where evry thing recquired for fastboot doesnt exist. it could be because of a different reason so any help will be appreciated! :crying::crying::crying:
Why would you be confused you know what you did wrong here's the trick you need to be really fast ... get to factory reset and reset it try from a powered off position maybe you will get the few extra seconds it takes to get it done...
---------- Post added at 11:36 PM ---------- Previous post was at 11:27 PM ----------
Otherwise you need to somehow get into fastboot and fastboot flash twrp.img and fff.bin note that I did say .bin if you cannot the best way is to get a factory cable...
Thepooch said:
Why would you be confused you know what you did wrong here's the trick you need to be really fast ... get to factory reset and reset it try from a powered off position maybe you will get the few extra seconds it takes to get it done...
---------- Post added at 11:36 PM ---------- Previous post was at 11:27 PM ----------
Otherwise you need to somehow get into fastboot and fastboot flash twrp.img and fff.bin note that I did say .bin if you cannot the best way is to get a factory cable...
Click to expand...
Click to collapse
im sorry, what do you mean by try it from a "powered off position"?
I mean turn it off then power it on and race to reach factory reset in the settings
---------- Post added 11th August 2012 at 12:00 AM ---------- Previous post was 10th August 2012 at 11:56 PM ----------
Anything you can do to shave time
reboot into fastboot and open kfu. then install superuser and others
i have got the same trouble.
I'm sure he would if he knew how to achieve fastboot :
Shift+ right click on the tools folder in kfu ... select open command window here.. power your kindle off.. type fastboot -i 0x1949 getvar product ... plug your kindle in it will power on in fastboot and return product: kindle open kfu and commit send of twrp after reboot commit send of fff .... power off power back on select recovery in recovery factory reset , wipe cache, wipe dalvik select reboot then system if prompted. In theory it should work if fastboot can be initiated...
Edit: no need to root twrp and fff is all you need
Sounds like you have enough time to set the bootmode to fastboot before your KF reboots.
So what you need to do is download the fbmode binary (may be include in KFU, otherwise search the development forum), adb.exe, fastboot.exe, and the TWRP 2.2.0 fastboot image. All of which should be placed in a single folder.
I'm assuming your on Windows, and therefore you must open a command prompt in your working directory. You will need to run the following commands...
Code:
adb wait-for-device
adb push fbmode /data/local/tmp
adb shell chmod 755 /data/local/tmp/fbmode
adb shell /data/local/tmp/fbmode
adb reboot
It may be easier to make a batch file so you don't have to type all the commands.
Then you could boot TWRP without flashing it by issuing this command...
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 boot openrecovery-twrp-2.2.0-blaze.img
From there, you should be able to delete the dalvik-cache, userdata, and cache.
Note: You must have the adb drivers installed and working properly. On the stock KF rom, adb is enabled by default so there's no reason this shouldn't work.
Edit: Actually, there's a possibility that this won't work if you disabled USB Debugging before switching back to the stock KF rom.
Thepooch said:
I'm sure he would if he knew how to achieve fastboot :
Shift+ right click on the tools folder in kfu ... select open command window here.. power your kindle off.. type fastboot -i 0x1949 getvar product ... plug your kindle in it will power on in fastboot and return product: kindle open kfu and commit send of twrp after reboot commit send of fff .... power off power back on select recovery in recovery factory reset , wipe cache, wipe dalvik select reboot then system if prompted. In theory it should work if fastboot can be initiated...
Edit: no need to root twrp and fff is all you need
Click to expand...
Click to collapse
thx! am going to try soon.... not at home atm....
lmntone said:
Sounds like you have enough time to set the bootmode to fastboot before your KF reboots.
So what you need to do is download the fbmode binary (may be include in KFU, otherwise search the development forum), adb.exe, fastboot.exe, and the TWRP 2.2.0 fastboot image. All of which should be placed in a single folder.
I'm assuming your on Windows, and therefore you must open a command prompt in your working directory. You will need to run the following commands...
Code:
adb wait-for-device
adb push fbmode /data/local/tmp
adb shell chmod 755 /data/local/tmp/fbmode
adb shell /data/local/tmp/fbmode
adb reboot
It may be easier to make a batch file so you don't have to type all the commands.
Then you could boot TWRP without flashing it by issuing this command...
Code:
fastboot oem idme bootmode 4000
fastboot boot openrecovery-twrp-2.2.0-blaze.img
From there, you should be able to delete the dalvik-cache, userdata, and cache.
Note: You must have the adb drivers installed and working properly. On the stock KF rom, adb is enabled by default so there's no reason this shouldn't work.
Edit: Actually, there's a possibility that this won't work if you disabled USB Debugging before switching back to the stock KF rom.
Click to expand...
Click to collapse
for some reason, i cant get the adb to work..... i hav the correct driver (i already did this before) but adb cannot find the device.
Then here is your best bet http://forum.xda-developers.com/showthread.php?t=1392693&highlight=info+factory+cable unless you can reach factory reset in time to do it
n00byn00bface said:
for some reason, i cant get the adb to work..... i hav the correct driver (i already did this before) but adb cannot find the device.
Click to expand...
Click to collapse
If you had adb disabled in the old rom, the settings could have been carried over to the stock rom.
Using a factory cable seems to be the only solution.
Thepooch said:
Then here is your best bet http://forum.xda-developers.com/showthread.php?t=1392693&highlight=info+factory+cable unless you can reach factory reset in time to do it
Click to expand...
Click to collapse
i was going to try to buy one from skorpn..... anyway, factory reset does nothing.
lmntone said:
If you had adb disabled in the old rom, the settings could have been carried over to the stock rom.
Using a factory cable seems to be the only solution.
Click to expand...
Click to collapse
i got it into fastboot mode, but now the command is stuck on fastboot oem idme bootmode 4000 <waiting for device>
also, its stuck on the kindle fire logo screen (that means its in fastboot right?)
thx everyone! i managed to fix my device! i followed imntones instructions and they worked.... sort of.... i used the first codes to get into fastboot, then i used twrp to install..... the last two codes dont work. thank you thank you thanmk you..... :highfive:
n00byn00bface said:
thx everyone! i managed to fix my device! i followed imntones instructions and they worked.... sort of.... i used the first codes to get into fastboot, then i used twrp to install..... the last two codes dont work. thank you thank you thanmk you..... :highfive:
Click to expand...
Click to collapse
I think that you just needed to specify the vendor id for fastboot. As in...
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 boot openrecovery-twrp-2.2.0-blaze.img
Anyway, glad to see you got your device working.
I think I flashed the wrong recovery (otter). Prior to doing so I had wiped /system. Now I'm stuck at the kindle fire logo with no apparent way to boot to anything functional.
On both linux and windows 'adb devices' shows the device is offline and the serial is 01234567890ABCDEF.
On both linux and windows 'fastboot devices' show no device.
I've tried using Kindle Fire Utility v.0.9.9 but since neither adb nor fastboot work it doesn't help
I've tried using Kindle Unbrick Utility v1.1 but it too fails to help in this case.
Is there any hope of recovering this device?
Thanks,
xdadevelopers-user
xdadevelopers-user said:
I think I flashed the wrong recovery (otter). Prior to doing so I had wiped /system. Now I'm stuck at the kindle fire logo with no apparent way to boot to anything functional.
On both linux and windows 'adb devices' shows the device is offline and the serial is 01234567890ABCDEF.
On both linux and windows 'fastboot devices' show no device.
I've tried using Kindle Fire Utility v.0.9.9 but since neither adb nor fastboot work it doesn't help
I've tried using Kindle Unbrick Utility v1.1 but it too fails to help in this case.
Is there any hope of recovering this device?
Thanks,
xdadevelopers-user
Click to expand...
Click to collapse
Hey shoot me any email here [email protected]
We can see if there is a solution and if we find one we can post our
findings back hereto help others..
Thx Josh
lj50036 said:
Hey shoot me any email here [email protected]
We can see if there is a solution and if we find one we can post our
findings back hereto help others..
Thx Josh
Click to expand...
Click to collapse
Thank you very much for the offer Josh. I was able to recover using a fastboot cable.
Initially I thought it did not work since I saw no difference on the screen and the command
Code:
fastboot devices
did not show any device. But I tried running
Code:
fastboot -i 0x1949 devices
and there it was. From there I booted into TWRP
Code:
fastboot -i 0x1949 boot openrecovery-twrp-2.7.0.1-blaze.img'
and installed CM11 M5.
Thanks again,
-xdadevelopers-user
So i been trying to find the answer to my issue everywhere. everything i try fails.
So basically my Kindle fire hd 8.9 is in a constant boot loop. it goes from orange w/animation, then blue w/animation... then after a period of time it says that it cant boot gives me option to factory restore (which does nothing).
when i have it hooked up to a computer, it connects for 1 second, then quickly disconnects. In device manager it comes up as "jem-pvt-prod-04" with the yellow "!". i even tried to use the amazon drivers from another post on xda, in that split second it would appear in device manager, i would update device and point it to the driver. then i will get an error saying it encountered an error installing Android ADB interface. problem encountered while trying to add driver.
Does anyone have any tips for me. im kinda stuck here and desperate with a very expensive paperweight. very upsetting!
I never tried to root, or mod this kindle fire. this problem happened on its own. or possibly after an update of some sort.
thanks guys.
piffdaddy420 said:
So i been trying to find the answer to my issue everywhere. everything i try fails.
So basically my Kindle fire hd 8.9 is in a constant boot loop. it goes from orange w/animation, then blue w/animation... then after a period of time it says that it cant boot gives me option to factory restore (which does nothing).
when i have it hooked up to a computer, it connects for 1 second, then quickly disconnects. In device manager it comes up as "jem-pvt-prod-04" with the yellow "!". i even tried to use the amazon drivers from another post on xda, in that split second it would appear in device manager, i would update device and point it to the driver. then i will get an error saying it encountered an error installing Android ADB interface. problem encountered while trying to add driver.
Does anyone have any tips for me. im kinda stuck here and desperate with a very expensive paperweight. very upsetting!
I never tried to root, or mod this kindle fire. this problem happened on its own. or possibly after an update of some sort.
thanks guys.
Click to expand...
Click to collapse
You're not hopelessly bricked if your Kindle still boots to the orange logo.
Might I ask what Windows version you're using? Newer versions enforce driver signatures, and that enforcement will cause failed installations in Windows 8+ unless you disable the enforcement before installing the drivers. I would also suggest installing ADB and fastboot if you haven't already done so. (Use the 15 second ADB installer - it's on XDA, and it works wonders!)
Sent from my Amazon Jem using XDA Labs
monster1612 said:
You're not hopelessly bricked if your Kindle still boots to the orange logo.
Might I ask what Windows version you're using? Newer versions enforce driver signatures, and that enforcement will cause failed installations in Windows 8+ unless you disable the enforcement before installing the drivers. I would also suggest installing ADB and fastboot if you haven't already done so. (Use the 15 second ADB installer - it's on XDA, and it works wonders!)
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Yes, actually i am using windows 10. My thinkpad has windows 7, so i will try to do this using windows 7. i will post back with results. its funny, out of everywhere i looked nobody mentioned windows 8+ having to disable enforcement. actually it will probably just be easier just to disable the enforcement. ill give it a try and report back.
still no luck. i was able to install the driver. but it still does the same thing. only connects for 1 second when i first turn it on. idk where to go from here? any suggestions?
piffdaddy420 said:
still no luck. i was able to install the driver. but it still does the same thing. only connects for 1 second when i first turn it on. idk where to go from here? any suggestions?
Click to expand...
Click to collapse
Completely turn off the kindle and unplug it from your PC if it's connected. Open Command Prompt and type fastboot -i 0x1949 getvar product. Plug in the kindle when you see <waiting for device> outputted. The kindle should now boot into fastboot mode, from which point you can reflash the bootloader, TWRP, and the freedom-boot image in Hashcode's thread.
Sent from my Amazon Jem using XDA Labs
monster1612 said:
Completely turn off the kindle and unplug it from your PC if it's connected. Open Command Prompt and type fastboot -i 0x1949 getvar product. Plug in the kindle when you see <waiting for device> outputted. The kindle should now boot into fastboot mode, from which point you can reflash the bootloader, TWRP, and the freedom-boot image in Hashcode's thread.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
ok so im in fastboot mode now. i checked out that thread that you sent. but i have another problem, how am i supposed to get cm and gapps onto the kindle? is there a command i can use to put the files on the internal sd card? and i cant do the adb commands to push the stack, and do the other commands adb since i couldnt get it loaded to begin with, i am not able to enable developer mode. it would be nice if i could do those commands in fastboot mode. there has to be a way to do this....
maybe if someone can send me the stock partitions that they backed up stock boot partititons when they did it. maybe if i flashed them onto my kindle it will allow me to get it to atleast boot up so i can get into adb.
right now this is completely bricked.
can anyone help me? i just need the original boot loader, boot, recovery... basically whatever was backed up before you flashed it.
i aam looking for the original because i know mine was corrupt to begin with. my theory is if i load the original boot loaders and everything then maybe i can get into the kindle just so i can run the abd commands and then put cyanogenmod on it. unless someone has a suggestion on how i can get my device to be detected by adb ? the furthest i can get into is fastboot.
piffdaddy420 said:
can anyone help me? i just need the original boot loader, boot, recovery... basically whatever was backed up before you flashed it.
i aam looking for the original because i know mine was corrupt to begin with. my theory is if i load the original boot loaders and everything then maybe i can get into the kindle just so i can run the abd commands and then put cyanogenmod on it. unless someone has a suggestion on how i can get my device to be detected by adb ? the furthest i can get into is fastboot.
Click to expand...
Click to collapse
Once you're in fastboot, you should run these fastboot commands (most of which I ripped from Hashcode's thread) to flash the bootloader, etc.:
fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.4.6.img
fastboot -i 0x1949 flash recovery kfhd8-twrp-2.8.7.0-recovery.img
fastboot -i 0x1949 oem recovery
after that, you should be in TWRP, from which point you can use ADB sideload (enable in TWRP through Advanced -> ADB sideload) to flash CM. After running ADB sideload, you need to re-enable it in TWRP for each subsequent zip you want to flash.
Sent from my Amazon Jem using XDA Labs
monster1612 said:
Once you're in fastboot, you should run these fastboot commands (most of which I ripped from Hashcode's thread) to flash the bootloader, etc.:
fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.4.6.img
fastboot -i 0x1949 flash recovery kfhd8-twrp-2.8.7.0-recovery.img
fastboot -i 0x1949 oem recovery
after that, you should be in TWRP, from which point you can use ADB sideload (enable in TWRP through Advanced -> ADB sideload) to flash CM. After running ADB sideload, you need to re-enable it in TWRP for each subsequent zip you want to flash.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Yes, i did all of those steps, however i never did the final step the oem recovery one...
everytime i try it now the screen turns completely red and stays there.
piffdaddy420 said:
Yes, i did all of those steps, however i never did the final step the oem recovery one...
everytime i try it now the screen turns completely red and stays there.
Click to expand...
Click to collapse
That's going to be a problem... hold down the Kindle till it completely powers off. Then open command prompt, type fastboot -i 0x1949 getvar product , and plug in the Kindle when you see <waiting for device>. Does this get you into fastboot mode?
Sent from my Amazon Jem using XDA Labs
monster1612 said:
That's going to be a problem... hold down the Kindle till it completely powers off. Then open command prompt, type fastboot -i 0x1949 getvar product , and plug in the Kindle when you see <waiting for device>. Does this get you into fastboot mode?
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
yes it does
piffdaddy420 said:
yes it does
Click to expand...
Click to collapse
It sounds like you've got a newer bootloader that's been patched. Go ahead and download the files from Hashcode's thread, and type in all of the commands exactly as given in step 5. Those should fix the red screen issue and allow you to boot normally (or into TWRP, from which point you can ADB sideload CM).
Sent from my Amazon Jem using XDA Labs
monster1612 said:
It sounds like you've got a newer bootloader that's been patched. Go ahead and download the files from Hashcode's thread, and type in all of the commands exactly as given in step 5. Those should fix the red screen issue and allow you to boot normally (or into TWRP, from which point you can ADB sideload CM).
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
i followed that exact, i tried it a couple times before you even mentioned it. but i did it again, i redownloaded everything and did it again. just to be sure. but it still continues to do the same thing with the red screen. it goes from kindlefire for 2 seconds then red screen comes across it and stays red. idk what to do. i am so upset.
piffdaddy420 said:
i followed that exact, i tried it a couple times before you even mentioned it. but i did it again, i redownloaded everything and did it again. just to be sure. but it still continues to do the same thing with the red screen. it goes from kindlefire for 2 seconds then red screen comes across it and stays red. idk what to do. i am so upset.
Click to expand...
Click to collapse
Do you happen to have any stock OS backups? If you do, you should remain able to flash those over fastboot.
Sent from my Amazon Jem using XDA Labs
monster1612 said:
Do you happen to have any stock OS backups? If you do, you should remain able to flash those over fastboot.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
no, i wish i did. the whole reason i started trying this was because the kindle was in a bootloop without even trying to flash it. it would go from kindlefire (orange) then blue, then it will ask me to do factory reset. and nomatter what i did i would keep going in the same bootloop.
so i turned to here for help, and following instructions now i am in this situation.
unfortunatley since i wasnt able to get into the kindle, i was never able to do any abd backups. so i just took my chances with it.
i was actually originally asking if anyone had the original files they can send me so i can try to flash those. atleast i can get it up and running because i really have a feeling this isnt working because i need to push the stack file over thru abd first.
piffdaddy420 said:
no, i wish i did. the whole reason i started trying this was because the kindle was in a bootloop without even trying to flash it. it would go from kindlefire (orange) then blue, then it will ask me to do factory reset. and nomatter what i did i would keep going in the same bootloop.
so i turned to here for help, and following instructions now i am in this situation.
unfortunatley since i wasnt able to get into the kindle, i was never able to do any abd backups. so i just took my chances with it.
i was actually originally asking if anyone had the original files they can send me so i can try to flash those. atleast i can get it up and running because i really have a feeling this isnt working because i need to push the stack file over thru abd first.
Click to expand...
Click to collapse
You should be able to separately flash the system.img, boot, and recovery from this tool via fastboot. It's stock OS 8.1.4, but it should work.
monster1612 said:
You should be able to separately flash the system.img, boot, and recovery from this tool via fastboot. It's stock OS 8.1.4, but it should work.
Click to expand...
Click to collapse
ok, it provided me with all the files except the bootloader. i did it step by step... but it only gave me original recovery, and original boot.img but it didnt give me the bootloader (and yes it is still turning red)
piffdaddy420 said:
ok, it provided me with all the files except the bootloader. i did it step by step... but it only gave me original recovery, and original boot.img but it didnt give me the bootloader (and yes it is still turning red)
Click to expand...
Click to collapse
anyone have any suggestions or can help me with my situation?? i am wondering if maybe someone could just send me the original backed up bootloader, boot, and recovery. i tried the original ones that were posted with that srt file. but it included everything but the bootloader. which is what i need. i know that in original thread they recommended to back up your original files (i was unable to do so because my kindle woulnt boot so i couldnt use adb to back up these files).
so if someone on here can send me the original files so i can try to get my kindle booted back up. that so far is my only theory because i tried everything else. i know people with advance knowledge would be able to help me in a heartbeat. any devs out there wanna help me out? i would greatly appreciate it!
anyone?