Related
Hi everyone, today i would like to ask for your help with a pretty big problem i have with my Kindle fire HD, you see, i was updating from my current rom 7.4.4 to CM 10.2. to achieve thi i followed this tutorial http://forum.xda-developers.com/showthread.php?t=2271909 , everything was going fine until i installed 2nd-Bootloader and TWRP recovery. The problem came up here, when i realized that i forgot to move the rom and the files for google play into the SD card, now whenever i try to do this i can't seem to get my PC to recognize the Kindle with TWRP (i can browse my files and such with TWRP directly through the kindle itself) i tried to move the required file with adb and fastboot but i can't get it to work.
The kindle is rooted and running version 7.4.6 from amazon.
i have a backup for the rom and the files but i can't use fastboot.
i have a backup for each of the following files: boot0block, stock-boot, stock-recovery, stock-system
all the adb drivers and sdk are functioning perfectly.
When i connect it to my PC with windows 7 i can see the kindle recognized by the device manager but it has yellow triangle next to the icon.
i also tried using an otg cable but the kindke did not recognize it.
any and all help is appreciated, i don't want my tablet to die Dx
I've never had to do this, but in TWRP, if you go to "Advanced," there's a button labeled "ADB Sideload." Then you should be able to use ADB to sideload files onto your Kindle using the "adb sideload" command.
Example:
Code:
adb sideload name of.zip
Hope this helped
>>Sent from my homebuilt TARDIS running Android 4.3... or maybe it's a rooted Kindle Fire HD running ChameleonOS<<
Ph0enix_216 said:
I've never had to do this, but in TWRP, if you go to "Advanced," there's a button labeled "ADB Sideload." Then you should be able to use ADB to sideload files onto your Kindle using the "adb sideload" command.
Example:
Code:
adb sideload name of.zip
Hope this helped
>>Sent from my homebuilt TARDIS running Android 4.3... or maybe it's a rooted Kindle Fire HD running ChameleonOS<<
Click to expand...
Click to collapse
I tried this but the problem is that the pc not find device , it show me in device manager yellow triangle next to the icon of kindle
When i send a adb command , the adb say "Device not found"
Thanks you anyway!
Try updating the device driver for the device with mark next to it, use these drivers from this post, they should work. http://forum.xda-developers.com/showpost.php?p=44446906&postcount=9
stunts513 said:
Try updating the device driver for the device with mark next to it, use these drivers from this post, they should work. http://forum.xda-developers.com/showpost.php?p=44446906&postcount=9
Click to expand...
Click to collapse
Hi and thanks for your help now i try send the next command adb push file.zip /sdcard
but adb say this menssage:
C:\Users\Cristian>adb push file.zip /sdcard
cannot stat 'file.zip': No such file or directory
I put a rom in C:\adt-bundle-windows-x86_64-20130729\sdk\platform-tools in the same folder that adb.exe
and the name of the rom file is : file
Shur'tugal said:
Hi and thanks for your help now i try send the next command adb push file.zip /sdcard
but adb say this menssage:
C:\Users\Cristian>adb push file.zip /sdcard
cannot stat 'file.zip': No such file or directory
I put a rom in C:\adt-bundle-windows-x86_64-20130729\sdk\platform-tools in the same folder that adb.exe
and the name of the rom file is : file
Click to expand...
Click to collapse
Ok if u want to simply type file.zip u need to be CD's into the directory of where u put the ROM, but as it seems u have the SDK in your paths simply putting the ROM in c:\users\cristian should suffice. Try moving the ROM there and running the command again.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Ok if u want to simply type file.zip u need to be CD's into the directory of where u put the ROM, but as it seems u have the SDK in your paths simply putting the ROM in c:\users\cristian should suffice. Try moving the ROM there and running the command again.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Thanks for your help your save my tablet
Thanks you very much
Finally i exit for this bricked
Enviado desde mi GT-I9300 usando Tapatalk 4
I have a dude im install CM 10.2 perfect , but i dont remember install de google apps as i have to do now?
Thanks
One step further
My apologies for hijacking this thread. I had made the same error as the OP. however, instead of searching here for solution, I panicked and wiped the cache and user data using the SR tool and wiped everything. Now unfortunately my kfhd tells me it can't boot, which my incompetent mind tells me is likely because I have no rom?
I've tried to use first aide to do a system recovery but I get told the files are too large and it can't do anything.... Any suggestions or thoughts from people? Appreciate any help I can get. Been up late the last 3 days trying to sort this out, while I thought I was going to provide m wife with a slick android device!!
That's odd, I wouldn't think wipe your data partition and cache would cause that to happen, then again there are some files stored under data the system uses out side of apk's so I guess that could be why. Did you get your kindle into fastboot? If you did I would suggest trying to use kfhd system restore tool if kffa didn't work.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Yes, can fast boot. Shows up when I plug in the factory cable. When I use the system restore tool, and try and do a basic recovery, it can't copy the images over as it says the files are too big.
deeman77 said:
Yes, can fast boot. Shows up when I plug in the factory cable. When I use the system restore tool, and try and do a basic recovery, it can't copy the images over as it says the files are too big.
Click to expand...
Click to collapse
All the files, or just the system.img?
soupmagnet said:
All the files, or just the system.img?
Click to expand...
Click to collapse
each one of them unfort.
Do you have twrp installed?
hloomsc some
soupmagnet said:
Do you have twrp installed?
Click to expand...
Click to collapse
I did. Not sure i do now post trying to do a wipe. Don't see any blue when I start up, just the original kindle letter coloring, after which I get a message saying it can't boot
any suggestions anyone or is my kfhd pretty much killed? there's got to be a way to load some rom on to it!!
You should be able to load the original images over fastboot, something just isn't working right. I would say its far from hard bricked, it should still be fixable, its just a matter of troubleshooting it. If you have the kindle fire system image I would try manually flashing it but you need to know what you are doing. If you CD into the SRT folder where im assuming the IMG files are in the same folder as fastboot, try running "fastboot -i 0x1949 flash system system.img" think I got the syntax right, haven't had to ever use fastboot myself, anyways if you run that what does it report back? Hopefully not the same error, or it might be something messed up with the image.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
thanks for the advice. ended up re downloading the images again and this time it worked. go figure.
back to starting again to get my custom rom on.
once i have a custom rom, guessing there are no amazon bits left in there that would cause any updates to come through right?
Thank god there isn't, I would scream if there was, just make sure to wipe system, cache, dalvik cache and do a factory reset when coming from amazon to cm based ROMs.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Thank god there isn't, I would scream if there was, just make sure to wipe system, cache, dalvik cache and do a factory reset when coming from amazon to cm based ROMs.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Good afternoon: I bricked a nice 8.9 tablet several weeks ago using ADB sideload...
I used ADB Sideload to install Gapps since I was already in TWRP and was too lazy to reboot and transfer the gapps.zip file to my tablet.
The sideload installed the gapps.zip as I expected it to and I was brought back to the main TWRP screen.
When I clicked on reboot/reboot system, the tablet started flashing the three partitions (boot, recovery and system) as I was watching. TWRP then left me at the booting screen doing nothing. I did not know why the tablet decided to flash the three main partitions but, I opted to push the power button and that was the last time I saw my tablet.....
Apparently ADB sideload is only for ROM's? I had only used it to flash ROMs prior but, I thought ADB Sideload should be able to install any properly zipped file designed to flash with TWRP?
Regards
Hey, I looked on other threads but I did't find my problem or the description was too difficult for my ( I'm from Germany, my english is good but not perfect).
I installed TWRP but I also deleted my system, now I only can use the TWRP Menu...
But I think that I can use adb, when I type:
Code:
adb devices
then there comes:
Code:
List of devices attached
0123456789ABCDEF recovery
I used this Tutorial: http://forum.xda-developers.com/showthread.php?t=2271909
And I found this thread with a similar problem: http://forum.xda-developers.com/showthread.php?t=2412932
The answer ther is:
stunts513 said:
You shouldn't nessasrily need fastboot to fix this, I'm assuming the drivers you don't have installed for twrp is the adb device, so try updating Ur drivers with this version of the drivers: http://forum.xda-developers.com/show...php?p=44446906
Once the adb driver work you should be able to go I to twrp, hit advanced, then hit side load, and swipe to start side load, and with it plugged I to your PC put either a cm ROM or the stock rooted amazon ROM from android development into the same folder as your adb command, and run a line with this syntax in a command prompt: adb sideload myrom.zip
If that doesn't work you might be able to use adb push when not in side load mode but I haven't tinkered to much with twrp. If you must resort to using fastboot you shouldn't even need a factory cable in this case, as u can just go into twrp and hit reboot and tap bootloader, that should put you in fastboot. Hope this helps.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
There I don't understand the part with sideloading a rooted stock or custom rom.
I hope that you can help me and thet you understand my question
EDIT: I have a factory cable mybe it's good to know for you.
Basically you put the file you want to flash in the same folder as adb unless your have adb in your system paths, and type "adb sideload filetoflash.zip". You still have to go into twrp before this and hit advanced, then hit sideload, then swipe the thing. Sorry if this seems repetitive, I'm not sure how to make it much simpler. If you can't figure out the side load just do what I would do, boot your kindle into twrp, and plug into your PC. Now with the file you want to flash to the kindle in the same folder as adb run "adb push filename.zip /sdcard/filename.zip". That should put the file onto the kindles sdcard, from there you can use the install button in twrp and choose the file.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Basically you put the file you want to flash in the same folder as adb unless your have adb in your system paths, and type "adb sideload filetoflash.zip". You still have to go into twrp before this and hit advanced, then hit sideload, then swipe the thing. Sorry if this seems repetitive, I'm not sure how to make it much simpler. If you can't figure out the side load just do what I would do, boot your kindle into twrp, and plug into your PC. Now with the file you want to flash to the kindle in the same folder as adb run "adb push filename.zip /sdcard/filename.zip". That should put the file onto the kindles sdcard, from there you can use the install button in twrp and choose the file.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
So I have the zip file of the custopm rom and the md5 file on the sd card, after I moved them from an other directionary to the sd.
Now it' said that the md5 file is missing... but I can't put them into one zip file, idk, do you now what I do wrong?
What do you need an md5 file for?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Basically you put the file you want to flash in the same folder as adb unless your have adb in your system paths, and type "adb sideload filetoflash.zip". You still have to go into twrp before this and hit advanced, then hit sideload, then swipe the thing. Sorry if this seems repetitive, I'm not sure how to make it much simpler. If you can't figure out the side load just do what I would do, boot your kindle into twrp, and plug into your PC. Now with the file you want to flash to the kindle in the same folder as adb run "adb push filename.zip /sdcard/filename.zip". That should put the file onto the kindles sdcard, from there you can use the install button in twrp and choose the file.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2388341 for this, I have the md5 file but I think it must be in the rom.zip
Edit: Thanks stunts513, I tried it with CM10.1 Tablet UI, succses.
Hello all.
Was tinkering around with my KF- And accidentally wiped everything from my internal storage and system. When it boots up I get the blue KF logo and it stays stuck there- Can't boot into recovery.
ADB doesnt recognize it.
Have a fastboot cable.
How do I atleast push files to it /boot into recovery??
Many thanks.
To boot into recovery, after you power on the kindle, immediately let go of power and instead hold volume down usually only until you see the blue kindle logo. You can hold it longer if it makes ya feel better, it should then show the twrp logo and from there you can use adb to push the ROM of your choosing onto the device, here's a tutorial for that assuming you get into recovery. http://forum.xda-developers.com/showthread.php?t=2459498
I think I know how to get it into recovery from fastboot as well but if that doesn't work you'd just have to reflash Amazon's os with kindle fire first aid.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
To boot into recovery, after you power on the kindle, immediately let go of power and instead hold volume down usually only until you see the blue kindle logo. You can hold it longer if it makes ya feel better, it should then show the twrp logo and from there you can use adb to push the ROM of your choosing onto the device, here's a tutorial for that assuming you get into recovery. http://forum.xda-developers.com/showthread.php?t=2459498
I think I know how to get it into recovery from fastboot as well but if that doesn't work you'd just have to reflash Amazon's os with kindle fire first aid.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I tried all of this- Yes, I got it into recovery, It was recognized once by ADB and when I attempted to push the files from a flash drive it stopped working. Did the flash drive effect it or? It's also not showing up in device manager at all anymore after updating the drivers to ADB.
SilverRoxas said:
I tried all of this- Yes, I got it into recovery, It was recognized once by ADB and when I attempted to push the files from a flash drive it stopped working. Did the flash drive effect it or? It's also not showing up in device manager at all anymore after updating the drivers to ADB.
Click to expand...
Click to collapse
You cannot use a flash drive with the Kindle Fire HD as it's unsupported. You have to push it via command prompts on your computer. Follow the tutorial posted. try adb sidelad rather than adb push as the command.
LinearEquation said:
You cannot use a flash drive with the Kindle Fire HD as it's unsupported. You have to push it via command prompts on your computer. Follow the tutorial posted. try adb sidelad rather than adb push as the command.
Click to expand...
Click to collapse
I don't believe I made myself clear. I attempted to push a file from a flash drive connected from my computer and after it was attempted ADB couldn't find my device. Unless I am misunderstanding you, this is what I did. I have attempted cmd prompts and none are moving to my avail.
My apologizes if I am misunderstanding you, sir.
SilverRoxas said:
I don't believe I made myself clear. I attempted to push a file from a flash drive connected from my computer and after it was attempted ADB couldn't find my device. Unless I am misunderstanding you, this is what I did. I have attempted cmd prompts and none are moving to my avail.
My apologizes if I am misunderstanding you, sir.
Click to expand...
Click to collapse
Ah gotcha, I was thinking you were trying to use OTG with a flashdrive. So, I wonder if the problem was that you were trying to flash from a flashdrive or maybe you are missing the adb.exe file. The folder you put the ADB drivers in should have a file marked adb.exe as well. This is what will execute the pushing of the files. Make sure you point the drivers after it is in the folder you will CD from. If you don't have this then download the sdk package and in one of the tool folders you will have adb.exe. Just throw your drivers and ROM in that folder and that will be the folder you CD from.
So try this:
a. Make sure the ROM, ADB drivers and adb.exe are in the same folder.
b. Now go into device driver and manually (choose from your files) update the adb drivers and install them.
c. Once the adb is again recognised go into the folder with all the files and find a white area and hold shift and right click on the mouse and choose open a command window here.
d. Now enter the commands adb sideload name-of-rom-or-file-here-make-sure-to-add (.zip) - at - the-end /sdcard/
e. Give a minute for the process to show in the command window. You should start seeing some percentages as the file is pushed.
LinearEquation said:
Ah gotcha, I was thinking you were trying to use OTG with a flashdrive. So, I wonder if the problem was that you were trying to flash from a flashdrive or maybe you are missing the adb.exe file. The folder you put the ADB drivers in should have a file marked adb.exe as well. This is what will execute the pushing of the files. Make sure you point the drivers after it is in the folder you will CD from. If you don't have this then download the sdk package and in one of the tool folders you will have adb.exe. Just throw your drivers and ROM in that folder and that will be the folder you CD from.
So try this:
a. Make sure the ROM, ADB drivers and adb.exe are in the same folder.
b. Now go into device driver and manually (choose from your files) update the adb drivers and install them.
c. Once the adb is again recognised go into the folder with all the files and find a white area and hold shift and right click on the mouse and choose open a command window here.
d. Now enter the commands adb sideload name-of-rom-or-file-here-make-sure-to-add (.zip) - at - the-end /sdcard/
e. Give a minute for the process to show in the command window. You should start seeing some percentages as the file is pushed.
Click to expand...
Click to collapse
I attempted your method shown here and I get stuck at ADB drivers. There is no Kindle Fire device in my device manager and no bubble shows up when my kindle is attached to my pc. Could the cord be the issue? (I'm also running Windows XP, if that makes a difference.)
Also, I have drivers installed, but I'm unsure they're the correct ones. Where can I find them?
SilverRoxas said:
I attempted your method shown here and I get stuck at ADB drivers. There is no Kindle Fire device in my device manager and no bubble shows up when my kindle is attached to my pc. Could the cord be the issue? (I'm also running Windows XP, if that makes a difference.)
Also, I have drivers installed, but I'm unsure they're the correct ones. Where can I find them?
Click to expand...
Click to collapse
You won't have a pop up when your tablet is plug in at this point. In your device manage do you see a yellow triangle? There should be some android device in your device manager of some sort the pops up when plugged in. To test abd being recognized type adb devices in the command window and you should see your device show in the command window within 30 seconds.
LinearEquation said:
You won't have a pop up when your tablet is plug in at this point. In your device manage do you see a yellow triangle? There should be some android device in your device manager of some sort the pops up when plugged in. To test abd being recognized type adb devices in the command window and you should see your device show in the command window within 30 seconds.
Click to expand...
Click to collapse
After another day of messing with it, yes, finally, it's recognized in ADB. I can push anything but the .zip files for Gapps and Roms. When I try to, it just gives me a list of all the commands you can use with ADB. I've tried ADB sideload and push. Neither work.
SilverRoxas said:
After another day of messing with it, yes, finally, it's recognized in ADB. I can push anything but the .zip files for Gapps and Roms. When I try to, it just gives me a list of all the commands you can use with ADB. I've tried ADB sideload and push. Neither work.
Click to expand...
Click to collapse
Check the md5sum for corruption. Make sure to have those zips in the same folder you're CDing from.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
LinearEquation said:
Check the md5sum for corruption. Make sure to have those zips in the same folder you're CDing from.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Okay, so now no file is pushing/sideloading to my Kindle. I have them in the same folder I'm CDing from and it's still just running through what commands ADB can do. I'm unsure why it's doing this? It pushed once and now it won't anymore (similar to how it detected my kindle before then didnt).
SilverRoxas said:
Okay, so now no file is pushing/sideloading to my Kindle. I have them in the same folder I'm CDing from and it's still just running through what commands ADB can do. I'm unsure why it's doing this? It pushed once and now it won't anymore (similar to how it detected my kindle before then didnt).
Click to expand...
Click to collapse
Is adb still recognized in you device drivers?
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
LinearEquation said:
Is adb still recognized in you device drivers?
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes, my Kindle is still recognized.
i dont os on my kindle fire hd 7
I am having a mare with my kindle fire hd 7
It all starrted when anything google related kept crashing.
I tried to find solutions to the problem but no joy.
I then tried to install a different update to cyanogenmod nightly software but i then had a major problem with not being able to turn on my wifi.
I went into Twrp and tried to restore to my previous software but when my kindle re-booted i got stuck with a flashing teamwin logo
After trawling for days i managed to get out of that but im now in a situation where i dont have any OS on my kindle.
I have followed instructions on how to push files onto my kindle but despiote finding some files on my sdcard i am unable to reboot past the blue and white Kindlefire logo.
I have tried using the kindle un-brick java option but no joy either
I would really appreciate some help solving this proble as it is really driving me crazy.
I can still access twrp and i can access bootloader to get the orange and white fastboot logo.
If someone can help guide me through how i can get my kindle working again id really appreciate it
cheers
JJ
Might be able to help.
I had the exact same problem as you and watched this video and i fixed it youtube(dot)com/watch?v=NaK5OxUeDKM
sorry im not allowed to post links because im a new user.
Hey Danny101
Danny101 said:
I had the exact same problem as you and watched this video and i fixed it youtube(dot)com/watch?v=NaK5OxUeDKM
sorry im not allowed to post links because im a new user.
Click to expand...
Click to collapse
Thanx for your response.
Sorry its taken me a while to reply but have had loads going one recently.
Shortly after making my post i did find that exact same youtube vid tutorial and was able to solve my problem.
I just wanted to say thanx for taking time to respond even so.
All the best.
JJ
So my kindle fire is stuck on twrp mode everytime i boot it. it first go to kindle with the "orange logo" then the "blue logo" i can hold the volume down to go to twrp recovery options and i can go to fastboot by going to "reboot" and "bootloader". How did this happen your wondering? Well i accidentally deleted my backup and the rom after i was done installing a rom, when i mount it i dont see it on my desktop, I click on the script while its mounting and it says "E:Unable to locate volume information for usb storage mode". it wont show the device on my windows 7 on "my computer" i downloaded the adb driver it detects the kindle and w/e but it wont show on my desktop so that i can transfer a rom into it and install it. If your curious of knowing what usb im using , its a galaxy s3 usb charger. It fits on the rear side of the kindle fire 7 hd and chargers...could it be that thats stoping my kindle fire hd from mounting? if it is then what other usb am i suppose to use to mount it or where can i find or buy one online or store? :crying:
Marckiscool said:
So my kindle fire is stuck on twrp mode everytime i boot it. it first go to kindle with the orange logo then the blue logo (twrp) i can hold the volume down to go to twrp recovery options but i accidentally deleted my backup and the rom when i mount it i dont see it, i click on the script while its mounting and i see "E:Unable to locate volume information for usb storage mode". it wont show the device on my windows 7 on "my computer" i downloaded the adb driver it detects the kindle and w/e but it wont show on my desktop so i can transfer a rom in it and install it. Of your curious of knowing what usb im using its a galaxy s3 it fits on the rear side of the kindle fire 7 hd and chargers could it be that? if it is then what other usb am i suppose to use to mount it or where can i find or buy one online or store? :crying:
Click to expand...
Click to collapse
Here is the tutorial to push onto TWRP. http://forum.xda-developers.com/showthread.php?t=2459498 Follow it and you will be back up in a short time.
Hey Thanks for the reply tho but The cmd doesnt seem to find the rom and its not working i tried to download his adb but my kindle wont install it
Marckiscool said:
Hey Thanks for the reply tho but The cmd doesnt seem to find the rom and its not working i tried to download his adb but my kindle wont install it
Click to expand...
Click to collapse
To CD into the directory you go into the folder where you put your extracted adb zip folder and ROM hold shift and right click on the mouse. Now left click on "open a command window here." Or you can CD from the directory directly. Use adb sideload rather than adb push. You want to copy the ROM into the same folder as the extracted adb folder because adb.exe is already in there and that's what you need for this procedure to work.
Here is a video that I think will help you a bit too. Short but very well done and very informative https://www.youtube.com/watch?v=CivvxcM1PCY He refers to the SDK tool folder. When he refers to that, you will refer to the extracted ABD folder. It takes a few seconds but soon you will see the flashing process in the form of a percentage.
Edit: When he refers to the USB drivers, thats what you use to get your device recognized. In command type adb devices. If you get waiting for device, you need to square that around first.
same thing wid nexus s
same thing happened to my nexus s. but when i type sideload or push it, it shows device not found. And when i type adb devices command it shows no devices please help, no os is there. i think there is any virus or any thing there which is stops it to connect. Kindly tel me if there is any file tht i can delete frm system and i can connect. Please guyx help me
Ok I've been at this for hours trying to get adb to recognize the tablet in recovery mode and to no avail. I've tried every trick and random driver i can find on here and still am unable to get adb to recognize the tablet while waiting for a sideload .bin file. While in normal mode while up and running adb devices command find sit np but once it goes into recovery it's gone.
I type adb devices and it comes back null. I've tried killing and restarting the daemon server and that isn't it. I've tried uninstalling and reinstalling the drivers. There is even an ADB composite driver listed in the device manager and yet once the tablet is in recovery mode it seems to disappear.
I tried doing a factory reset and wiping the cache. i'm drawing a blank on this. I've also tried changing usb ports and cables on the computer. It's just not working.
Any ideas?
You may need to disable driver signature enforcement
then install drivers.
After that you may still need to follow this guide
http://forum.xda-developers.com/showpost.php?p=62561874&postcount=2
This was written for a different FIRE so yours will be KFFOWI instead of KFARWI in the guide.
I did this and in worked for me..
There are two options to restore stock at the bottom of this link, it all depends what version you have. See if it helps...
http://forum.xda-developers.com/showpost.php?p=62986666&postcount=4
or you could also try this to get into Amazon Custom recovery:
adb reboot recovery
Yeah, most likely a driver issue. Try different drivers until you find one that actually works!
Well I just thought of this when I woke up, could it be that I'm using minimal ADB and fastboot or should that not make a difference?
As long as your device is listed when doing a "adb devices" or "fastboot devices" should make no difference. But yes, minimal should be fine.
But it is usually a good idea to have the latest version.
I think your issue is with getting to Amazon recovery. If in recovery, there should be a menu. See that menu here in post #3:
http://forum.xda-developers.com/amazon-fire/general/amazon-fire-2015-tips-tricks-t3214544
Tuvan03 said:
Ok I've been at this for hours trying to get adb to recognize the tablet in recovery mode and to no avail. I've tried every trick and random driver i can find on here and still am unable to get adb to recognize the tablet while waiting for a sideload .bin file. While in normal mode while up and running adb devices command find sit np but once it goes into recovery it's gone.
Click to expand...
Click to collapse
You're talking 2 different modes here: (1) Recovery mode: You see menu options on tablet. Windows can't ever recognize device while in recovery mode; no driver appears in Win Device Manager. (2) Sideload mode: After you select "apply update from ADB" and press power button and you see yellow text on tablet saying to sideload the file. Fire appears in Device Manager. If no driver installed (or messed up), it's under "Other" with the name KFFOWI as @gray-beard said. That's what you need to install drivers for in order for sideload to work. I doubt Minimal adb is the problem. You're probably just not all the way into sideload mode. If problems persist, open the console window from the folder containing adb.exe.
gray-beard said:
You may need to disable driver signature enforcement
then install drivers.
After that you may still need to follow this guide
http://forum.xda-developers.com/showpost.php?p=62561874&postcount=2
This was written for a different FIRE so yours will be KFFOWI instead of KFARWI in the guide.
I did this and in worked for me..
Click to expand...
Click to collapse
Many Thanks Gray Beard, it's reloading the stock firmware now. I was just trying to go through the pick your device drivers thing too quickly and needed to do the see all devices to be able to see the adb drivers to get them loaded.
A pint of the finest dwarven ale to you (with a name like gray beard i couldn't resist)
EDIT: I did all this just to try to restore OTA updates, yet i hit the update button now that it's restored with the factory firmware and it's saying no updates found. hmm