Related
Hello,
Let me start by saying I have looked a searched through several other threads but cannot seem to find anything that mimics my problem 100%. I had rooted the Kindle Fire HD 7" a few weeks ago and have been going along with no problem. One day (cannot remember what I installed) the KFHD crashed on me and wanted me to Restore the device in a "download mode" type of screen (used the volume buttons to select restore and power to confirm selection.) The device restarted just fine and was working normally. I went through the KFFirstAide root process again, root checker told me it was rooted. Starting using the options in KFFA to diable OTA, install play store, install google apps, installed Holo Launcher.. Some of the programs did not seem to install properly and didn't like the way things were behaving so I went to the Settings/Device/Restore to Factory Defaults...
After that process finished I am not at an Android setup screen. It has a blue Welcome at the top, select Language below that, Start below that, and a green outlined Android guy below that. When I hit start it says Just a sec.... and eventually get the message Setup Wizard has Stopped.. I can no longer see Kindle Fire ADB in the Device Manger.. Nothing seems to work on KFFA.. I have tried using the fastboot command in a command prompt (says waiting for device) and never does anything..
Basically I would like to know, what steps I may have to take to get the device to load properly again, and hopefully root the device again. IIRC the software version I last saw was 7.3.1...
Thank you for your time and assistance and appologize if it has been discussed before, but I just couldn't seem to find it and not sure what this problem is called to be able to properly search for it..
Before. it says "waiting for device", you should have the kindle powered off and disconnected from the computer. Plug it in after it says "waiting for device" and it should boot into fastboot.
Sent from my CyanogenFire HD7
Krsmqn said:
Before. it says "waiting for device", you should have the kindle powered off and disconnected from the computer. Plug it in after it says "waiting for device" and it should boot into fastboot.
Sent from my CyanogenFire HD7
Click to expand...
Click to collapse
Yep, it is powered off and the cable is disconnected. I plug it in after it says waiting for device and it powers up to the Welcome Setup screen.the command prompt on the computer still says < waiting for device >
When I hold one of the volume buttons and press power on it says Safe Mode at the bottom of the screen. Might there be something I can work with in that? Is there another boot method similar to "download" mode on the GalaxySIII?
jhutch825 said:
Yep, it is powered off and the cable is disconnected. I plug it in after it says waiting for device and it powers up to the Welcome Setup screen.the command prompt on the computer still says < waiting for device >
Click to expand...
Click to collapse
Sounds like you just need to get a factory cable and use that to get into fastboot mode. If the device is not recognized by adb using the fastboot cmds will not work on the 7" variant, that only works on the 8.9".
Is there a way to make on or do I have to order it?
Just ordered a factory cable ... what should I do when I get it?
onemeila said:
Sounds like you just need to get a factory cable and use that to get into fastboot mode. If the device is not recognized by adb using the fastboot cmds will not work on the 7" variant, that only works on the 8.9".
Click to expand...
Click to collapse
You can get fast boot on the KFHD7 using the stock cable and adb by issuing the adb commands then running "adb reboot bootloader" I think it was. I did it this afternoon when coming off the stock ROM to cm10.1
Edit: n/m, I though he had adb but it wouldn't boot fastboot on a restart with the cable. Guess it doesn't help his case if adb itself won't show.
-Ken
---------- Post added 30th April 2013 at 12:03 AM ---------- Previous post was 29th April 2013 at 11:41 PM ----------
jhutch825 said:
Just ordered a factory cable ... what should I do when I get it?
Click to expand...
Click to collapse
Since your boot loader is still starting up okay, when powered up with the factory/fastboot cable attached it should jump straight into fastboot. You can then use the fast boot command line tool in the adb kit from Google to push either a backup you made previously, or one from a recovery thread back onto your device. Check in the android development section, there's plenty on info on using fastboot.
-Ken
codepoet82 said:
You can get fast boot on the KFHD7 using the stock cable and adb by issuing the adb commands then running "adb reboot bootloader" I think it was. I did it this afternoon when coming off the stock ROM to cm10.1
Edit: n/m, I though he had adb but it wouldn't boot fastboot on a restart with the cable. Guess it doesn't help his case if adb itself won't show.
-Ken
---------- Post added 30th April 2013 at 12:03 AM ---------- Previous post was 29th April 2013 at 11:41 PM ----------
Since your boot loader is still starting up okay, when powered up with the factory/fastboot cable attached it should jump straight into fastboot. You can then use the fast boot command line tool in the adb kit from Google to push either a backup you made previously, or one from a recovery thread back onto your device. Check in the android development section, there's plenty on info on using fastboot.
-Ken
Click to expand...
Click to collapse
Ok. I will try that forum when it arrives.. To the best of my knowledge, I had not created a backup at any time so I will search out something from the Recovery Thread.
Thank you
-Joe
I am just 100% confused now.. I have searched and searched and everything I am reading is just making me more confused.
The cable will put the device into fast boot and will show up in Device Manager as an ADB Device.. I ran option 3 on KFFA and I don't believe the entire system image downloaded as now I am stuck on a screen with a red triangle asking to reboot or restore the device. Neither option does anything.
I have looked in recovery threads for fresh stock images but only find links and directions to TWRP.. Which, if I understand correctly, needs a 2nd bootloader.. And still will need a fresh stock image from amazon. Also, in KFFA it says to connect the device with a normal cable, not fastboot cable, in ADB mode for TWRP and the second bootloader.. I cannot get into the KF to enable ADB like it asks because I cannot get anything to load..
I have downloaded kfhd7-amazon-os-7.3.1 from goo.im and it comes in a zip file. I am not really sure of what to do..
I looked in the Android Development section of this forum and there are only 18 threads that don't talk about fastboot either. Do I need to go to a general Android Development section, not in the Kindle Fire Forum Sections?
I just want to go back to 100% factory original and start over from there..
Also, the KindleFireFirstAide dropbox seems to be overloaded and suspended, so I cannot get the images from there at the moment through their tool.
jhutch825 said:
Just ordered a factory cable ... what should I do when I get it?
Click to expand...
Click to collapse
You didn't need a fast boot cable. All you needed to do was setup ADB drivers and issue the command "adb reboot bootloader"
Sent from my KFTT using xda app-developers app
-a- said:
You didn't need a fast boot cable. All you needed to do was setup ADB drivers and issue the command "adb reboot bootloader"
Sent from my KFTT using xda app-developers app
Click to expand...
Click to collapse
Even though the device was no longer showing up in the windows device manager as Kindle Fire ADB? The Kindle was being recognized under Mobile Devices.
I don't know if I will be able to do that now that I used Fastboot to reload Factory Reset through KindleFire First Aide (option 3).. I don't think the entire system.img downloaded before it tried to install it and their dropbox server is down now so I can't rerun the command right now.
Solved
Found a link, finally, to onemeila's KFHD System.img Restore tool... Used the fastboot cabled and got it installed and everything seems to be running flawlessly.
Same Story Here...
jhutch825 said:
Even though the device was no longer showing up in the windows device manager as Kindle Fire ADB? The Kindle was being recognized under Mobile Devices.
I don't know if I will be able to do that now that I used Fastboot to reload Factory Reset through KindleFire First Aide (option 3).. I don't think the entire system.img downloaded before it tried to install it and their dropbox server is down now so I can't rerun the command right now.
Click to expand...
Click to collapse
Hello, after looking through many, many threads..I have finally found this one. Same story here..I have not order the factory cable. I have the original cable that came with my kindlehd. Before I go and buy the cable I wanted to see if this question can be addressed?
Dnoob, it's been a while don't remember the solution but I did get a factory cable and worked everything out through fast boot
Sent from my Amazon Kindle Fire HD using Tapatalk now Free
Hello.
After hours of struggling and Googling (and reading mostly from this forum) I managed to root my KFHD 7.4.6 using bin4ry method. I have two questions about where I'm at right now.
Question 1: While struggling to get adb to recognize my KF, I realized that the problem was quite simple: after installing the special adb drivers, I would plug the Kindle back in and Windows would recognize the device and install the Microsoft drivers - completely ignoring the driver I had just installed. The only way I managed to get around this was to quickly interrupt Windows 7's driver installation and tell it to NOT install drivers from Windows Update.
However, I'm sure there must have been a more elegant way of accomplishing this. What would have been the correct way to do this?
Question 2: Now that adb finally recognizes the KF, and the KF shows up as "Android Composite ADB Interface" in device manager, I want to put Android 4.2.2 on the KF - so CM 10.1. I'm doing preparatory research so I can learn about what I need to do. The big concern for me now is that my KF version is 7.4.6. There seems to be relatively little information about this, and I've seen it explicitly indicated in a few places that only versions before 7.3.something have the exploit available. Does this mean I must first downgrade from 7.4.6? I've had trouble pinning resources down that would help me answer this question - so if anyone has any solid tips about this, I'd appreciate it! I'd really rather not brick it :silly:
Thanks! :good:
SpidaFly said:
Question 2: Now that adb finally recognizes the KF, and the KF shows up as "Android Composite ADB Interface" in device manager, I want to put Android 4.2.2 on the KF - so CM 10.1. I'm doing preparatory research so I can learn about what I need to do. The big concern for me now is that my KF version is 7.4.6. There seems to be relatively little information about this, and I've seen it explicitly indicated in a few places that only versions before 7.3.something have the exploit available. Does this mean I must first downgrade from 7.4.6? I've had trouble pinning resources down that would help me answer this question - so if anyone has any solid tips about this, I'd appreciate it! I'd really rather not brick it :silly:
Click to expand...
Click to collapse
I just found this:
http://forum.xda-developers.com/showthread.php?t=2271909
So the answer to my question appears to be "YES", correct? It appears that I need to flash back to 7.2.3?
Question 1 still remains unsolved.
Well you could downgrade it, I don't know if the latest update causes problems, but the thing that needs downgrading isn't the os, its the bootloader. I suggest the fireflash method in seokhuns tutorial, the one you linked. Just make sure to check the first box at the top in fire flash or you will have a red screen brick, which requires a fastboot cable to fix. Also I have never heard of windows update having drivers for the kindle, I mean I usually hit skip anyways, I believe the more elegant solution may have come with kindle fire first aid, not positive though.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Thanks!
I'm having another little inconsistency now.
I disconnect and power off my KF.
I run in cmd: fastboot -i 0x1949 getvar product
It says < waiting for device >
I then plug in my (powered off) KF, and it boots up NORMALLY, and fastboot doesn't return the expected tate-xxx.
Any ideas why?
My ADB is seeing the device. (ie. adb devices is returning one device).
Your fastboot drivers aren't working.
soupmagnet said:
Your fastboot drivers aren't working.
Click to expand...
Click to collapse
Indeed. Can this be solved by wiping existing drivers and reinstalling Amazon's USB drivers from sdk/extras/amazon ?
EDIT: I've attempted reinstall twice with no improvement. ADB works, fastboot won't.
Um I thought that command only worked on a 8.9" kindle to get it into fastboot.try this instead:
Adb shell su -c "reboot bootloader"
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Um I thought that command only worked on a 8.9" kindle to get it into fastboot.try this instead:
Adb shell su -c "reboot bootloader"
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Interesting. I tested that. adb shell su -c "reboot bootloader" does indeed put my device in fastboot mode, and fastboot -i 0x1949 reboot takes it out.
Interesting. Seokhun's tutorial seems to indicate that fastboot -i 0x1949 getvar product should do it as well... so it seems that my fastboot drivers are... kinda half working? Or something?
SpidaFly said:
Interesting. I tested that. adb shell su -c "reboot bootloader" does indeed put my device in fastboot mode, and fastboot -i 0x1949 reboot takes it out.
Interesting. Seokhun's tutorial seems to indicate that fastboot -i 0x1949 getvar product should do it as well... so it seems that my fastboot drivers are... kinda half working? Or something?
Click to expand...
Click to collapse
That option may have been removed in later versions of the bootloader. Some have had success with it while others apparently haven't. If the reboot command works, your drivers should be working properly.
soupmagnet said:
That option may have been removed in later versions of the bootloader. Some have had success with it while others apparently haven't. If the reboot command works, your drivers should be working properly.
Click to expand...
Click to collapse
Sounds good, thanks. I'm following that tutorial even though it's for 7.4.3, and I'm on 7.4.6. I hope that doesn't cause any issues - but 7.4.6 looks like it's pretty new, so I don't see other options.
Ok - I've followed the aforementioned tutorial precisely up to step 4. When I try to boot the kindle up, it shows orange logo, then blue logo, then looks like it's trying to boot normally, then sends me into TWRP.
Is this what is called "boot loop"?
At this point my PC doesn't see the sdcard so I can't get CM/Gapp copied over.
Would it be safe to push CM & Gapp to the sdcard using adb, then resume with TWRP?
EDIT: Still can't boot into the system. Just sideloaded CM 10.1 ROM onto the sdcard. Safe to continue with Step 4, wipe stuff, and install the CM rom?
SpidaFly said:
EDIT: Still can't boot into the system. Just sideloaded CM 10.1 ROM onto the sdcard. Safe to continue with Step 4, wipe stuff, and install the CM rom?
Click to expand...
Click to collapse
This ended up working.
However, now with CM 10.1, my PC isn't recognizing the device for MTP. It still does recognize it as an ADB device, but ADB doesn't see it.
Odd that MTP isn't working, u can always switch to pptp mode if that helps, but everything goes to the dcim folder on the sdcard.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Odd that MTP isn't working, u can always switch to pptp mode if that helps, but everything goes to the dcim folder on the sdcard.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Got it working. Basically just uninstalled the existing drivers and reinstalled standard drivers. Works like a charm. I love CM, this is great! Thanks all, for the help!
I'll worry about getting adb going again later.
Hey,
I recently bought me a Kindle Fire HD, assuming that rooting and custom roms are no problem.
But I can't even root my device. I tried to use this file but the batch just stucks.
When I try to find my device in console via "adb devices" it's not listet. But I have adb drivers installed.
Any suggestions? I'm really clueless.
schwixxer said:
Hey,
I recently bought me a Kindle Fire HD, assuming that rooting and custom roms are no problem.
But I can't even root my device. I tried to use this file but the batch just stucks.
When I try to find my device in console via "adb devices" it's not listet. But I have adb drivers installed.
Any suggestions? I'm really clueless.
Click to expand...
Click to collapse
so it shows up as a adb device in the device manager?
No, it doesn't. I guess thats why the batch won't work. I just dont understand why the adb driver doesn't work.
Gesendet von meinem MK16i mit Tapatalk 2
But you've ADB enabled in System Settings?
BTW - rooting ist the only thin you can do with Fire HD 7 (2013) there are no Customs in Moment.
Regards
Yeah, i read that far already. Rooting is fine for the moment to remove the amazon ads and to install play. Customs will come earlier or later
Adb is activated on my Kindle
Gesendet von meinem MK16i mit Tapatalk 2
schwixxer said:
Yeah, i read that far already. Rooting is fine for the moment to remove the amazon ads and to install play. Customs will come earlier or later
Adb is activated on my Kindle
Gesendet von meinem MK16i mit Tapatalk 2
Click to expand...
Click to collapse
You know that you have to use a Factory Cable? For Rooting 11.3.2.1 you've to Downgrade bootloader (the script is dealing with that automaticaly) but you have to be in fastboot mode, and fastboot mod is only possible with a factory cable (as far as I know)
BTW "adb devices" doesn't show me my device either.
Regards
dvb127 said:
You know that you have to use a Factory Cable? For Rooting 11.3.2.1 you've to Downgrade bootloader (the script is dealing with that automaticaly) but you have to be in fastboot mode, and fastboot mod is only possible with a factory cable (as far as I know)
BTW "adb devices" doesn't show me my device either.
Regards
Click to expand...
Click to collapse
I've read that "factory cable" before, I just thought that it refers to the cable that came with the kindle. Is that wrong? Where do I get a factory cable?
schwixxer said:
I've read that "factory cable" before, I just thought that it refers to the cable that came with the kindle. Is that wrong? Where do I get a factory cable?
Click to expand...
Click to collapse
I built one myself. if you ask Google for a factory cable Motorola then you'll find a very good how to . I don't know where to buy.
regards
Its better to call it a fastboot cable, I think factory cable is misleading unless you look it up.
Sent from my Amazon Kindle Fire HD using Tapatalk
Okay, solderd a Factory cable and now I'm able to access fastboot mode.
But the batch still stucks here:
//Edit1:
Okay, Windows reconized the Kindle as "soho pvt prod 07". Had to update driver manually in order to work.
Now im stuck here: nothing seems to happen anymore. Why?
//Edit2:
Seems to have a brick. Kindle won't boot anymore. I can still access fastboot mode but kindle wont show up in adb devices, so i cant flash the other boot img. Help?
//Edit3:
Okay, was able to flash the new image without having kindle in the adb devices list. This brings me back to Edit1: Why does the batch stop?
schwixxer said:
Okay, solderd a Factory cable and now I'm able to access fastboot mode.
But the batch still stucks here:
//Edit:
Okay, Windows reconized the Kindle as "soho pvt prod 07". Had to update driver manually in order to work.
Now im stuck here: nothing seems to happen anymore. Why?
Click to expand...
Click to collapse
Power Off your Kindle, then connect your "fastboot cable" --> then your Kindle should power on autom. and show a screen like attached, if not you've problem with your cable. If it shows the screen then there is a Problem with fastboot driver.
dvb127 said:
Power Off your Kindle, then connect your "fastboot cable" --> then your Kindle should power on autom. and show a screen like attached, if not you've problem with your cable. If it shows the screen then there is a Problem with fastboot driver.
Click to expand...
Click to collapse
Well, it works to this point. I have the fastboot logo on my kindle. The batch flahes the boot image. And then everything stops.
Edit:
Okay, the Problem seems to be, that after the downgrade the kindle does not show up as adb device anymore. It works fine with the new image though.
Is that a driver related problem? Do I need a different driver for the old boot image?
Edit2:
Just noticed that the Kindle never shows up under "adb devices" when in fastboot mode. It dows work when I boot the Kindle normal though.
So the batch stucks naturally an "adb wait-for-device"
schwixxer said:
Well, it works to this point. I have the fastboot logo on my kindle. The batch flahes the boot image. And then everything stops.
Edit:
Okay, the Problem seems to be, that after the downgrade the kindle does not show up as adb device anymore. It works fine with the new image though.
Is that a driver related problem? Do I need a different driver for the old boot image?
Click to expand...
Click to collapse
How long did you wait? It'll take a few minutes. When your Kindle is powered on do you've an "adb" connection?
dvb127 said:
How long did you wait? It'll take a few minutes. When your Kindle is powered on do you've an "adb" connection?
Click to expand...
Click to collapse
I waited a few minutes. I also tried to do it manually. I typed:
Code:
fastboot -i 0x1949 flash boot old-boot-prod.img
On my kindle then appears "Start downloading", "writing boot.....done"
Code:
fastboot -i 0x1949 continue
I hear now the usb-disconnect and afterwards the connect sound of windows, no change on my kindle
Code:
adb wait-for-device
and then I can wait forever. Nothing happens here. Only thing I can do is ctrl+c.
Ok. I tried again with my notebook (still running WinXp) and... it worked. On the second try.
Device is rooted now, annoying ads are gone. Thank god.
Why this did not work under Win7....I have no idea.
Last quastion: How to get GooglePlay now? And i read that I can't use the Amazon store anymore, will I need it for some Apps?
schwixxer said:
Ok. I tried again with my notebook (still running WinXp) and... it worked. On the second try.
Device is rooted now, annoying ads are gone. Thank god.
Why this did not work under Win7....I have no idea.
Last quastion: How to get GooglePlay now? And i read that I can't use the Amazon store anymore, will I need it for some Apps?
Click to expand...
Click to collapse
In the post you downloaded your root Script you'll find a link in Signature of the Poster to his playstore Script (To Root your KFSOWI and install working Google Play Click Here)
And yes if playstore ist installed Amazon Downloads are not possible anymore, but you can save all files named “DownloadProvider***.apk/odex“ out of /system/apps before using Playstore Script. You'll find such files also in playstore Script. Than you can always change files. Take the files out of org. Firmware to Download from Amazon and reverse to Download Form google.
dvb127 said:
In the post you downloaded your root Script you'll find a link in Signature of the Poster to his playstore Script (To Root your KFSOWI and install working Google Play Click Here)
And yes if playstore ist installed Amazon Downloads are not possible anymore, but you can save all files named “DownloadProvider***.apk/odex“ out of /system/apps before using Playstore Script. You'll find such files also in playstore Script. Than you can always change files. Take the files out of org. Firmware to Download from Amazon and reverse to Download Form google.
Click to expand...
Click to collapse
Are there special app's that I might need the amazon-appstore for later?
Also, is there a way to change the lockout-screen? Im glad that the ad's are gone now, but just black is boring, too.
schwixxer said:
Are there special app's that I might need the amazon-appstore for later?
Also, is there a way to change the lockout-screen? Im glad that the ad's are gone now, but just black is boring, too.
Click to expand...
Click to collapse
Waht I know ist that only need DownloadProvider** Files (*. odex and *.apk). I don't know how to change the lockscreen, but I think you mean that there is no possibitly to set a wallpaper --> than look at here.
schwixxer said:
Okay, solderd a Factory cable and now I'm able to access fastboot mode.
But the batch still stucks here:
//Edit1:
Okay, Windows reconized the Kindle as "soho pvt prod 07". Had to update driver manually in order to work.
Now im stuck here: nothing seems to happen anymore. Why?
//Edit2:
Seems to have a brick. Kindle won't boot anymore. I can still access fastboot mode but kindle wont show up in adb devices, so i cant flash the other boot img. Help?
//Edit3:
Okay, was able to flash the new image without having kindle in the adb devices list. This brings me back to Edit1: Why does the batch stop?
Click to expand...
Click to collapse
Congrats on rooting your Soho! I'm having similar problems that you did initially. The device is recognized in adb. I bought a fastboot cable. The devices comes up in fastboot mode using the fastboot cable but is not recognized in Windows and so 'fastboot devices' comes up empty. You said you fixed that by updating the drivers manually. Can you share exactly what you did please? This has been driving me nuts for over a week. Thanks!
djlman said:
Congrats on rooting your Soho! I'm having similar problems that you did initially. The device is recognized in adb. I bought a fastboot cable. The devices comes up in fastboot mode using the fastboot cable but is not recognized in Windows and so 'fastboot devices' comes up empty. You said you fixed that by updating the drivers manually. Can you share exactly what you did please? This has been driving me nuts for over a week. Thanks!
Click to expand...
Click to collapse
fastboot devices never promted anything for me, either.
I had to go to the Device Manage in Windows, look for the Kindle and manually update the driver to the "android_winusb.inf"
Hey everybody!
This is my first time posting something on XDA. This is really cool.
So I just bricked my fire, hard. Let's start from the top:
- I used the super tools rootjunkysdl.com/?device=Amazon%20Fire%205th%20gen&folder=SuperTool to get the google play store.
- Using the google play store, I got flashfire.
- Using flashfire, I flashed SlimLP onto my tablet successfully and quickly.
- I got a little cocky, and based on the comments on the youtube.com/watch?v=NaCBSuUuhRE video that I used to flash SlimLP I decided to try the flashfire technique with CM since it is my favorite ROM.
- I did everything properly and the same, but... it got stuck here... for about an hour...
imgur.com/QJvmRz3
So I decided to do the smartest thing ever and cancel it myself by turning it off, I wasn't able to do anything else anyway. Either way, my tablet is now stuck in the cyanogen 12 boot load animation, the one of the cute blue head with the radar effect.
I would of fixed this a long time ago, but for some reason I'm not able to adb sideload.
I go into fastboot, I can detect the device, but not adb sideload.
I go into adb sideload mode, I can't detect the device, so definitely not sideload. :/
I've tried updating my drivers, I don't know if I'm doing it right, but while it was in fastboot mode, I changed it to Android Composite ADB Interface, and that didn't change anything.
No matter what I'm doing, whenever I do adb devices, I always get:
List of devices attached
Blank. Nothing. Only when I'm in fastboot mode do I get:
fastboot devices
G0K0H40454261ARU fastboot
Something, but still no ADB. I can't even load TWRP here, tried that, I just install it and it just sits there dumbly saying it's installed.
I'm bricked just like my tablet. Could I please get some help here? I'm very desperate to get this tablet back up and running, and I feel so stupid for not having stuck with Slim and trying to install CM. I really don't want it to stay bricked like this.
Thank you, XDA!
Do you know if you had amazon FireOS version 5.0.1 or 5.1.1?
Just to be clear, you have actually selected the adb sideload option on your Fire when you try to connect with adb on you pc, correct? ADB is not even active until the adb sideload option has been selected.
drillster said:
I can't even load TWRP here, tried that, I just install it and it just sits there dumbly saying it's installed.
Click to expand...
Click to collapse
We can not "install" twrp. The bootloader is locked & won't allow it. We can only temporarily load twrp into memory. Each time we want to use twrp, we must connect usb to a pc, enter fastboot mode & load twrp. But this can only been done on 5.0.1 Fires. It's been blocked on 5.1.1. No way to load twrp at all on 5.1.1.
Just use this method: http://forum.xda-developers.com/ama...howto-how-to-restore-frimware-device-t3238740
hAtE NeVeR dIeS said:
Just use this method: http://forum.xda-developers.com/ama...howto-how-to-restore-frimware-device-t3238740
Click to expand...
Click to collapse
Do not follow the instructions in that thread! It will permanently brick you if you're have the FireOS 5.1.1 bootloader. The OP of that thread finds it too hard to add a note that it's outdated. See the page 4, post #36
blueberry.sky said:
Do not follow the instructions in that thread! It will permanently brick you if you're have the FireOS 5.1.1 bootloader. The OP of that thread finds it too hard to add a note that it's outdated. See the page 4, post #36
Click to expand...
Click to collapse
I have 5.1.1... yeah, thanks.
blueberry.sky said:
Do you know if you had amazon FireOS ve wrsion 5.0.1 or 5.1.1?
Click to expand...
Click to collapse
I have 5.1.1.
blueberry.sky said:
Just to be clear, you have actually selected the adb sideload option on your Fire when you try to connect with adb on you pc, correct? ADB is not even active until the adb sideload option has been selected.
Click to expand...
Click to collapse
Yeah I selected apply update from adb, adb devices was blank, didn't work.
blueberry.sky said:
We can not "install" twrp. The bootloader is locked & won't allow it. We can only temporarily load twrp into memory. Each time we want to use twrp, we must connect usb to a pc, enter fastboot mode & load twrp. But this can only been done on 5.0.1 Fires. It's been blocked on 5.1.1. No way to load twrp at all on 5.1.1.
Click to expand...
Click to collapse
I went into fastboot mode, installed twrp, and nothing happened because yes, its 5.1.1.
I've seen some other people who also have been unable to get adb to work (in custom recovery). I don't recall a solution.
There is an option in fastboot to flash firmware, I haven't seen anyone try that yet..
blueberry.sky said:
I've seen some other people who also have been unable to get adb to work (in custom recovery). I don't recall a solution.
There is an option in fastboot to flash firmware, I haven't seen anyone try that yet..
Click to expand...
Click to collapse
Do you have any ideas on how to do this? I would greatly appreciate it.
Thank you!
Since I haven't read anyone try it before, there would be some risk. I suppose you are already bricked, seemingly without a way to fix it, but you could brick it harder. You might be able to get adb working. I may not have any ideas on how to get adb working for you, but someone else might know. If you try flashing the stock OS via fastboot, there is a chance you could brick it in a different way.
The command would be
Code:
fastboot update <filename-of-stock-firmware.zip>
But we don't have a .zip stock firmware file. In twrp recovery you can just rename the .bin file to .zip & it works. Not sure if that will also work for fastboot. My guess is it won't work & might brick you.
Also be aware, on Fires that self-updated to FireOS 5.1.1 (or came with 5.1.1 new) you must only flash 5.1.1. Attempting to flash 5.0.1 will brick it 100% of the time & it's unrecoverable.
drillster said:
No matter what I'm doing, whenever I do adb devices, I always get:
List of devices attached
. . .
Click to expand...
Click to collapse
Just a shot in the dark here, but have you gone into device manager while in sideload mode and updated drivers for KFFOWI under Other devices? Windows needs drivers for every mode.
I have same issue.
[QUOTE=drillster;64617577]Hey everybody!
This is my first time posting something on XDA. This is really cool.
So I just bricked my fire, hard. Let's start from the top:
- I used the super tools rootjunkysdl.com/?device=Amazon%20Fire%205th%20gen&folder=SuperTool to get the google play store.
- Using the google play store, I got flashfire.
- Using flashfire, I flashed SlimLP onto my tablet successfully and quickly.
- I got a little cocky, and based on the comments on the youtube.com/watch?v=NaCBSuUuhRE video that I used to flash SlimLP I decided to try the flashfire technique with CM since it is my favorite ROM.
- I did everything properly and the same, but... it got stuck here... for about an hour...
imgur.com/QJvmRz3
So I decided to do the smartest thing ever and cancel it myself by turning it off, I wasn't able to do anything else anyway. Either way, my tablet is now stuck in the cyanogen 12 boot load animation, the one of the cute blue head with the radar effect.
I would of fixed this a long time ago, but for some reason I'm not able to adb sideload.
I go into fastboot, I can detect the device, but not adb sideload.
I go into adb sideload mode, I can't detect the device, so definitely not sideload. :/
I've tried updating my drivers, I don't know if I'm doing it right, but while it was in fastboot mode, I changed it to Android Composite ADB Interface, and that didn't change anything.
No matter what I'm doing, whenever I do adb devices, I always get:
List of devices attached
Blank. Nothing. Only when I'm in fastboot mode do I get:
fastboot devices
G0K0H40454261ARU fastboot
Something, but still no ADB. I can't even load TWRP here, tried that, I just install it and it just sits there dumbly saying it's installed.
I'm bricked just like my tablet. Could I please get some help here? I'm very desperate to get this tablet back up and running, and I feel so stupid for not having stuck with Slim and trying to install CM. I really don't want it to stay bricked like this.
Thank you, XDA![/QUOTE]
I did the same thing. Slim worked great, tried to flashfire CM12, ot bricked. Can get fastboot, but nothing else. Afraid to try update from fastboot.
I just want to say thanks to everybody who contributed, I'm really appreciative of the support, especially because I didn't expect it, haha! Listening to blueberry.sky I'm going to try the flashboot update, because it's either that or a bricked device. School just started so I got busy with that.
DoLooper said:
Just a shot in the dark here, but have you gone into device manager while in sideload mode and updated drivers for KFFOWI under Other devices? Windows needs drivers for every mode.
Click to expand...
Click to collapse
So when I have it in adb mode, the fire doesn't seem to show up anywhere in any of my devices, and I can only find it when it's in fastboot mode. So when it's in that mode, I've tried Android ADB Interface, Android ADB Composite Interface, and when I go back to adb sideload, it's just not there in device manager. I don't know what this means, so any speculation? But no matter what mode I'm in or what driver I'm using, I can't seem to get it to show up in adb when in sideload mode.
Again, thanks everybody, and I hope anybody else in the future with this issue can refer to this thread for a lead!
So I just tried to flash update the firmware from Amazon amazon.com/gp/help/customer/display.html?nodeId=201830180 which I renamed from .bin to .zip:
C:\path\to\SuperTool>fastboot update update-kindle-global-37.5.4.1_user_541112720.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
I didn't rename the Slim and this is what I get:
C:\path\to\SuperTool>fastboot update Slim-ford-5.1.1.build.2.2b-20151210.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Is there anyway I can resolve this, so I can do SOMETHING?
Thank you!
drillster said:
So I just tried to flash update the firmware from Amazon amazon.com/gp/help/customer/display.html?nodeId=201830180 which I renamed from .bin to .zip:
Is there anyway I can resolve this, so I can do SOMETHING?
Thank you!
Click to expand...
Click to collapse
To be clear, you were able to, "adb sideload update-kindle-global-37.5.4.1_user_541112720.bin". To restore your Fire OS 5.1.1?
thekrakah said:
To be clear, you were able to, "adb sideload update-kindle-global-37.5.4.1_user_541112720.bin". To restore your Fire OS 5.1.1?
Click to expand...
Click to collapse
No, I did fastboot update in fastboot mode as suggested by blueberry.sky since ADB isn't working for reasons I stated before.
C:\path\to\SuperTool>fastboot update update-kindle-global-37.5.4.1_user_541112720.zip
drillster said:
No, I did fastboot update in fastboot mode as suggested by blueberry.sky since ADB isn't working for reasons I stated before.
C:\path\to\SuperTool>fastboot update update-kindle-global-37.5.4.1_user_541112720.zip
Click to expand...
Click to collapse
So when you say you go into "adb sideload mode. You selected "apply update from adb", and the Fire device is actively waiting for the sideload command, but you got nothing showing up in your device manager at that point?
I'm just clarifying because until the "apply update from adb" is activated, windows doesn't get a communication from the Fire device.
thekrakah said:
So when you say you go into "adb sideload mode. You selected "apply update from adb", and the Fire device is actively waiting for the sideload command, but you got nothing showing up in your device manager at that point?
I'm just clarifying because until the "apply update from adb" is activated, windows doesn't get a communication from the Fire device.
Click to expand...
Click to collapse
On my device, I can get fastboot, but not adb. if I reboot from fastboot, I only get the
CM logo and it sticks there permanently until I power off. When I boot to fastboot, the screen is blank but my Windows PC can see the device and return the SN. I can issue the command to reboot to bootloader, but reboots to fastboot with "fastboot" in small letters at the bottom of the screen. What else can I try? Thanks for all the help offered so far.
What happens when you try to get into recovery mode?
To get into recovery you start with the Fire off. Turn off by holding power button until it goes off (might take awhile). I just tried turning off from fastboot mode. Took only about 14 seconds of holding power.
To enter recovery: hold volume down button + hold power button.
blueberry.sky said:
What happens when you try to get into recovery mode?
To get into recovery you start with the Fire off. Turn off by holding power button until it goes off (might take awhile). I just tried turning off from fastboot mode. Took only about 14 seconds of holding power.
To enter recovery: hold volume down button + hold power button.
Click to expand...
Click to collapse
When I try to get into recovery, it boots with a blank screen. At that point, I can connect to my PC, type fastboot devices, and it will show me device. Then I try to reboot-bootloader, and it reboots to fastboot, but this time it says fastboot on the screen. I can't seem to get to recovery
watch this video to see if it helps.
https://www.youtube.com/watch?v=RQLoH-ahjy4
An app in google play store wasn't installing correctly and I was told a factory reset would fix my issue but now when the Kindle HD reboots it stays on the blue screen teamwin logo and keeps looping. How do I solve this ?
p.s my fastbooy cable is coming tomorrow but not sure what to do with it
did you manage to sort this im in the exact same position. factory reset within a custom rom! in windows its recognised in adb but not authorised and cant get it to recognise whilst in fastboot
KindleFireHD7" said:
did you manage to sort this im in the exact same position. factory reset within a custom rom! in windows its recognised in adb but not authorised and cant get it to recognise whilst in fastboot
Click to expand...
Click to collapse
Yeah I got it up and running again NO help to this site ... anyways
First I bought this Fastboot cable
www.amazon.com
Second install these Drivers:
http://forum.xda-developers.com/attachment.php?attachmentid=1337103&d=1348009415
Third install 2nd set of drivers if you need them/Used this tool to restore the kindle
https://drive.google.com/file/d/0B14UeDuAgQxRSjdzNGFDMzVRcms/view?usp=sharing
option 2 if that one didn't work or if you want to restore with root access
http://androidcowboy.com/2013/07/how-to-recover-bricked-kindle-fire-hd/
meowmix2 said:
Yeah I got it up and running again NO help to this site ... anyways
First I bought this Fastboot cable
www.amazon.com
Second install these Drivers:
http://forum.xda-developers.com/attachment.php?attachmentid=1337103&d=1348009415
Third install 2nd set of drivers/Used this tool to restore the kindle
https://drive.google.com/file/d/0B14UeDuAgQxRSjdzNGFDMzVRcms/view?usp=sharing
option 2 if that one didn't work or if you want to restore with root access
http://androidcowboy.com/2013/07/how-to-recover-bricked-kindle-fire-hd/
Click to expand...
Click to collapse
Will give this a go later on , I have fastboot cable just having serious trouble trying to pc to recognize it whilst in fast boot mode. It recognizes it in adb but it's unauthorized so that's no help. Thanks for reply will let you know how I get on
---------- Post added at 10:50 PM ---------- Previous post was at 10:40 PM ----------
meowmix2 said:
Yeah I got it up and running again NO help to this site ... anyways
First I bought this Fastboot cable
www.amazon.com
Second install these Drivers:
http://forum.xda-developers.com/attachment.php?attachmentid=1337103&d=1348009415
Third install 2nd set of drivers if you need them/Used this tool to restore the kindle
https://drive.google.com/file/d/0B14UeDuAgQxRSjdzNGFDMzVRcms/view?usp=sharing
option 2 if that one didn't work or if you want to restore with root access
http://androidcowboy.com/2013/07/how-to-recover-bricked-kindle-fire-hd/
Click to expand...
Click to collapse
its failing to install the first set of drivers any suggestions?? thanks
KindleFireHD7" said:
Will give this a go later on , I have fastboot cable just having serious trouble trying to pc to recognize it whilst in fast boot mode. It recognizes it in adb but it's unauthorized so that's no help. Thanks for reply will let you know how I get on
---------- Post added at 10:50 PM ---------- Previous post was at 10:40 PM ----------
its failing to install the first set of drivers any suggestions?? thanks
Click to expand...
Click to collapse
continue to second set maybe the first set of drivers is what worked for me maybe you don't need them . I'll try to find the source where i found them maybe you need a different set that was provided
update* ok heres the source of the ADB drives that finally worked for me
http://forum.xda-developers.com/showthread.php?t=1893838
Your goal is for the unbrick tool to detect your device. so find right combination of drives that work for you. some people even go to thier driver manager and uninstall / refresh them from there. If it still not working try uninstalling all previous drives and do a clean install with the two i gave you
Fix...
meowmix2 said:
An app in google play store wasn't installing correctly and I was told a factory reset would fix my issue but now when the Kindle HD reboots it stays on the blue screen teamwin logo and keeps looping. How do I solve this ?
p.s my fastbooy cable is coming tomorrow but not sure what to do with it
Click to expand...
Click to collapse
Hello,
Fortunately, i was in the same position as you and that too, for a whole year and 3 months. But I was a noob at that time. With your fastboot cable to be usable(no drivers needed but just a simple program), you need to get (Minimal ADB and Fastboot. The link is provided for download. Now you need to do some research. For me I found out that the main problem was that it was a TWRP problem and nothing else. So I am guessing you ahve the exact same. You need to go to CyanogenMod Wiki(discountinued so you'll have to wait until Lineage OS gets their Wiki up and then figure it out) and from there find your device and then the installation instructions whihc include the downlaod link for TWRP. From there download the recovery(it will link you to android file host or something like that). Now you can install Minimal Adb and Fastboot(MAF) and install it wherever convenient to you. Now you can place the zip file of recovery in the folder where MAF is installed and rename it to recovery.zip for your convenience. In that folder, open the exe that says "MAFAF" or something to that extent(dont' have it memorized lol). Now connect your fastboot cable to your Kindle and it should turn on with a screen on the kindle that says Fastboot and then Kindle. Now on your MAF, you cna check it's working by typing
Code:
fastboot devices
or
Code:
adb devices
. In theory, you should get something like " recovery (device number[random letters and numbers])". From this you can now type in
Code:
fastboot flash recovery recovery.zip
as done to flash our TWRP recovery. When this finishes(shouldn't take to long), you can detach the fastboot form the computer and device. Next, hodl down power to turn it off. Wait like 5 seconds after shut down and then turn the Kindle back on. This should momentarily boot into TWRP and then it will take off into your ROM or whatever OS you have installed. Now you should have not jsut fixed your problem but got TWRP to work too and from there it is easy to do stuff without the need of a PC. Hope this helps and feel free to quote me with a post if something didn't work or messed up. Sorry for bad grammer and spelling. Thanks!
meowmix2 said:
continue to second set maybe the first set of drivers is what worked for me maybe you don't need them . I'll try to find the source where i found them maybe you need a different set that was provided
update* ok heres the source of the ADB drives that finally worked for me
http://forum.xda-developers.com/showthread.php?t=1893838
Your goal is for the unbrick tool to detect your device. so find right combination of drives that work for you. some people even go to thier driver manager and uninstall / refresh them from there. If it still not working try uninstalling all previous drives and do a clean install with the two i gave you
Click to expand...
Click to collapse
Sorted thank you!