So I was being stupid and I moved a system file... Which not surprisingly crashed it. When I rebooted, It started to flash the "Kindle Fire" logo for about 30-45 seconds before becoming a red triangle and telling me I should do a system restore, which did nothing.
I searched around and found that I needed to get into fastboot to flash my backed up copy of the partitions back on to undo what I did. So I ordered a cable off ebay, which arrived from china yesterday. Sadly, when I plug my kindle into my computer via this cable it does nothing. When I run any fastboot commands, they hang at "< waiting for device >".
Is there anything that I can do that might help? I plan on soldering my own cable tomorrow to see if that's the problem.
Additional information:
- OS: Windows 7
- Kindle Fire 2
- I changed a file in "/system/framework/framework-res.apk"
- Used Kindle FirstAide to make backups
- adb drivers don't show up in device manager
You didn't see any devices with a yellow triangle next to them when the kindle is in fastboot mode? On wait your kindle never shows the fastboot logo?
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
You didn't see any devices with a yellow triangle next to them when the kindle is in fastboot mode? On wait your kindle never shows the fastboot logo?
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
It never showed fastboot logo despite being plugged in with a factory cable. And no, the triangle was red.
Lemonilla said:
It never showed fastboot logo despite being plugged in with a factory cable. And no, the triangle was red.
Click to expand...
Click to collapse
sounds like a bad fastboot cable. i have heard horror stories of people buying them and then using them and having the usb port fried on the kindle, so i guess yours was the lucky side of a bad fastboot cable. Lately i think people have been going for this nice adapter i think hashcode mentioned in his post by blackhat or something, it goes between the microusb plugs on the kindle and cable. Feel free to make one though, thats usually pretty easy to do.
stunts513 said:
Feel free to make one though, thats usually pretty easy to do.
Click to expand...
Click to collapse
One would think so. I managed to break the connection wire (the little one that goes into the micro_usb). Then while trying to solder to the broken stub, I wedged some molten solder to cross between ping 3 and 5's wires. I think I'll open up the one I bought for a second try. If that doesn't work I'll look into buying one of the adapters.
So I finally found time to try making a new one with the Chinese one that they sent. You were right about it being a bad cable. I took it apart and it was missing pin 5 altogether. Where would you recommend buying one from? I saw a neat little adapter head somewhere, but don't want to buy another one that doesn't work. I've been looking at this one: shop. teamblackhat .info (won't let me post the link )
If that's the one I'm thinking it is, its the same one hashcode mentions in his 2nd bootloader + twrp installation tutorial, I recommend it.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
If that's the one I'm thinking it is, its the same one hashcode mentions in his 2nd bootloader + twrp installation tutorial, I recommend it.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
So it came in the mail, and it works. It flashes everything but system.img, which I believe it says is too large to flash. The problem is that I believe this is the partition that is messed up. Do you know how to bypass this?
Code:
C:\Users\Lemonilla\Documents\System Files\Backups\KindleBackup1>fastboot -i 0x19
49 flash system system.img
target reported max download size of 486539264 bytes
Invalid sparse file format at header magi
sending sparse 'system' (463367 KB)...
OKAY [ 10.661s]
writing 'system'...
FAILED (remote: : Sparsed Write)
finished. total time: 10.716s
I'm guessing the system.img is just corrupt, I see it happen on occasion and it causes this error, try redownloading the system.img using kffa but I think kffa's links are down for its system images. Hopefully this situation isn't the same as a situation I'm having with someone else's kindle that is reporting that issue when it shouldn't be unless I make the actual partition smaller.
Sent from my Amazon Tate using Tapatalk
It worked, now all I have to do is get it to find my router. Thanks a ton!
EDIT: For some reason it is not letting me enable Wi-Fi. Is this common, I can't find anything on it.
Oh boy... Check to see if you can enable bluetooth
Sent from my Amazon Tate using Tapatalk
stunts513 said:
Oh boy... Check to see if you can enable bluetooth
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
I managed to fix it. I re-flashed the system and downloaded the boot and launcher from kffa and flashed those over my backups as well and that seemed to fix it. Thank you so much for your help!
OK glad to hear that that fixed it, I was worried it might be the boot0block, but thankfully it was not.
Sent from my Amazon Tate using Tapatalk
It might have been, that is one of the one's that I flashed with kffa's files.
The boot0block isn't flashed by kffa because its unique to every device, its basically the nvram with your serial number, WiFi mac address, Bluetooth mac address and such in it. You probably saw it flashing the bootimg (kernel + intramfs).
Sent from my Amazon Tate using Tapatalk
Related
Ok im posting in hopes to help someone else and myself.
DEVICE: 1st Gen Kindle Fire (D01400)
PROBLEM: Kindle quickly flashes stock logo then displays red screen.
I created this problem by using the wrong root tool (Qemuroot) [This tool is made for a Kindle Fire HD]
I bought a fastboot cable i hopes to use KFU/KUU to unbrick the device.
However Windows 8 only shows the device driver listed as Otter2-Prod-04 (Unknown Device) I proceeded to install the ADB drivers, even manualy assigned the device driver, and disabled driving signing and reinstalled drivers. (Drivers appear to install correctly however won't show up in connected adb devices.)
At this point im going to use SoupKit. I will post the outcome.
If you have had a similar problem or know of a fix which I have yet to research please let me know.
Thanks
Tested with Ubuntu linux using soupkit & firekit.
Both resulted in <Waiting for Android device> same in windows as well.
So I tried another computer also running windows 8, installed fresh SDK/Java/Drivers.
Once again had to force the driver to replace the unknown device "Otter2-Prod-04" now the device says its working in device manager yet nothing in ADB or fastboot.
I will add when I plug the device in using the fastboot cable it shows a red fastboot text and a stoplight green is flashing.
At this point im stuck and have reached the end of google. Yup thats right the very last page.
More hours put into this. I can issue fastboot commands. So this now turns into a question.
Is it possible to restore my kindle using fastboot?
tmobile-repair said:
More hours put into this. I can issue fastboot commands. So this now turns into a question.
Is it possible to restore my kindle using fastboot?
Click to expand...
Click to collapse
You should be able to if you can push fff and recovery over and flash them via fastboot
Should enable you to have recovery back and work from there
Sent from my YP-G1 using Tapatalk 4 Beta
Well I killed my kindle.
Pushed the FFF via fast boot and now the device no longer powers on, no lights, no sign of life.
fastboot -i 0x1949 flash bootloader <name of firefirefire image here> which was u-boot
guess its time to cash in on my my rapid exchange at Best Buy
Or get a new battery
Sent from my Amazon Kindle Fire using xda app-developers app
joshuabg said:
Or get a new battery
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
New battery ? Can you explain never heard of this before. I was under the impression that I killed the bootloader.
I was just thinking that the battery may have died
Sent from my Amazon Kindle Fire using xda app-developers app
ah that better explains it.
Thanks
Please help me!
I rooted my girlfriend's Kindle a few days ago in order to install the Google Play store. Managed that just fine and installed a few apps. I then decided it would be a good idea to change the launcher and get shot of the carousel. I tried the next Launcher 3D and followed an online guide to install it. On rebooting the Kindle I got a constant pop up advising Next Launcher 3D had stopped working. It popped up continually every 1/2 second or so and I couldn't get rid of it,
Again I had a look online and found a guide to removing it using command prompt script via ADB. I went through the instructions correctly but it kept telling me the app didn't exist. Using the dir command showed the app though. Confused I tried again a couple of times. I then got a pop up on the device telling me another app.....something relating to Swype had stopped working. The Kindle rebooted itself and presented a screen with a red triangle and 'Kindle Fire System Recovery' giving me the options to either reboot or reset to factory defaults. I tried both of these options (perhaps foolishly) and had no success.
I was given some further advice from a very helpful poster on here to get KFFAide v100 and enter some fastboot commands. On entering the command 'fastboot -i 0x1949 getvar product', the script shows 'waiting for device'. Powering on the device at that point does nothing more than booting to the same screen with the red triangle. Windows does not acknowledge that the device is connected at all.
It would seem I was hasty in rooting the device. Having rooted several other Android devices I was clearly overconfident in my ability and now find myself at a loss. Is there any way at all for me to recover the device at this point? Or should I now file this under 'very expensive experience and education'?
Its completely fixable, you just need to install the fastboot driver, if u open the device manager and plug the kindle in when its off, it should briefly show up as a jem device, while it shows up as that tell it to update the drivers and use the ones in my signature and it should install. It might give you problems installing though if it disconnects before the driver can finish installing. Once the driver is installed then power it off and unplug it and run the previous command and then plug it in. Now it should go into fastboot. If you can't get the driver to install, u should try using an Ubuntu live CD, since it doesn't use drivers in the same way windows does, it loads up the driver automatically so you wouldn't have this problem. Once this is in fastboot just reflash the system partition, if u hadn't factory reset it, it would still have all the data and apps, but as is its going to be "fresh out of the box".
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Its completely fixable, you just need to install the fastboot driver, if u open the device manager and plug the kindle in when its off, it should briefly show up as a jem device, while it shows up as that tell it to update the drivers and use the ones in my signature and it should install. It might give you problems installing though if it disconnects before the driver can finish installing. Once the driver is installed then power it off and unplug it and run the previous command and then plug it in. Now it should go into fastboot. If you can't get the driver to install, u should try using an Ubuntu live CD, since it doesn't use drivers in the same way windows does, it loads up the driver automatically so you wouldn't have this problem. Once this is in fastboot just reflash the system partition, if u hadn't factory reset it, it would still have all the data and apps, but as is its going to be "fresh out of the box".
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Hi Stunts513. Thank you for your reply. Have tried what you said above and Windows (8) just doesn't detect that the device has been connected. No pop up from system tray, nothing in file explorer and nothing, not even for a second in device manager.
Am at a loss for the moment. Will have to get hold of an Ubuntu CD and try that way. Am just praying it detects the Kindle. Didn't on my girlfriends laptop nor my PC so am mildly panicked just now.
OK, so I went through Linux Mint and installed the SoupKit and tried it that way. Same result. The device just isn't detected at all. Really starting to fear the worst here. The fact it's still powering on should give me some faith but i've tried all I can think of and everything advised and cannot proceed past this point.
Does anyone have any last gasp possibilities for me? Borderline desperate here now.... will try anything at this point.
In linux did you run "fastboot -i 0x1949 getvar product" with the kindle unplugged, and then after the command says waiting for device, plug the kindle in? Because on Linux, unless you know where to look its not going to really notify you that its plugged in. It probably will in the kernel logs in the f1 virtual terminal. If you can't get the device to respond to that command, hit Ctrl+alt +F1, and plug the kindle in with it off, and see if you notice anything in that terminal about jem, otter, or Tate coming up at the bottom of the terminal.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
In linux did you run "fastboot -i 0x1949 getvar product" with the kindle unplugged, and then after the command says waiting for device, plug the kindle in? Because on Linux, unless you know where to look its not going to really notify you that its plugged in. It probably will in the kernel logs in the f1 virtual terminal. If you can't get the device to respond to that command, hit Ctrl+alt +F1, and plug the kindle in with it off, and see if you notice anything in that terminal about jem, otter, or Tate coming up at the bottom of the terminal.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Did exactly that. Brought up the virtual terminal. Nothing.
Have tried everything now I think. Used different PCs. Different cables. Different OS. Tried bypassing getvar and just trying a manual command "fastboot -i 0x1949 flash recovery recovery.img". Nothing is getting any response from this device other than booting to the recovery screen.
Suspect I may be out of luck.
Are you absolutely positive this was an 8.9” model and not a 7” model, because the method to get it into fastboot without a fastboot cable doesn't always work with 7” models if I remember right, so if its a 7” model you just would need a fastboot cable to get it into fastboot mode, but on the 8.9” models we don't use fastboot cables, hence the command.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Are you absolutely positive this was an 8.9” model and not a 7” model, because the method to get it into fastboot without a fastboot cable doesn't always work with 7” models if I remember right, so if its a 7” model you just would need a fastboot cable to get it into fastboot mode, but on the 8.9” models we don't use fastboot cables, hence the command.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Yeah it is most definitely an 8.9 model. Am not sure what I have done to it but it is not being detected by any OS whatsoever. Have bitten the bullet and bought the Mrs a replacement. Expensive error on my part.
Out of curiosity, was it still under warranty?(not counting the fact you technically voided it) Also what are you going to do with the old one? I can think of a person that needs one to try to make a hard brick fix for the kfhd models, he has a working unhardbricking method right now, but it still is in a complicated soft brick state, anyways he's making these pcb's that attach to the kindles motherboard to directly access the emmc to flash it from Linux. Long story short he has made on for kf2, but doesn't own a 7" or 8.9" model, and if he can get his hands on one it could potentially profit the community greatly.
But yea if it was still under warranty you could probably get a new one for free, I only mention what I did above to either hard bricks or people getting new ones, I don't typically just ask people to do this. Would be kinda rude if I did...
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Out of curiosity, was it still under warranty?(not counting the fact you technically voided it) Also what are you going to do with the old one? I can think of a person that needs one to try to make a hard brick fix for the kfhd models, he has a working unhardbricking method right now, but it still is in a complicated soft brick state, anyways he's making these pcb's that attach to the kindles motherboard to directly access the emmc to flash it from Linux. Long story short he has made on for kf2, but doesn't own a 7" or 8.9" model, and if he can get his hands on one it could potentially profit the community greatly.
But yea if it was still under warranty you could probably get a new one for free, I only mention what I did above to either hard bricks or people getting new ones, I don't typically just ask people to do this. Would be kinda rude if I did...
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Many apologies for the delay. i managed to get the Kindle up and running following your advice coupled with that on another thread. Although it wouldn't detect in either Windows 8 or Ubuntu, it did so on Windows XP. Don't imagine you can begin to explain that one any better than I can as it's entirely illogical......but there you go. From there it detected as a JEM device and I was able to run KFFA and do a complete restore.
I now have it the way I intended to have it in the first place. Changing the launcher was fruitless as I couldn't get the wallpaper fix to work but am fine with that. had a look at customising the icons on the carousel but boy does that look like more trouble than it's worth!! Lol.
I wont pretend I was going to send my Kindle off to you guys. In truth I would have sold it to recoup some of my losses and raise funds towards the replacement. I will however be making a donation to the team very shortly as a token of my appreciation.
Thank you very much for all your help. it is greatly appreciated.
Unluckly i bricked my kindle fire hd 8.9.Now when i press the power button,after the yellow kindle fire logo flash,it will stuck on the red screen.And when i connect it to the PC,i got the red screen again.By the way,when the yellow kindle fire logo shows up, the PC could recognize the tablet but in less than 1 second the red screen will come out and the tablet will be disconnected from the PC as if the USB cable is pulled out.(i could hear the sound of disconnecting USB device.)
I also made a fastboot cable but it truned out to be invalid.Did i hard-brick the tablet? Is there any possibility to unbrick it? (I'm not a native speaker so sorry for my poor English)
z1326 said:
Unluckly i bricked my kindle fire hd 8.9.Now when i press the power button,after the yellow kindle fire logo flash,it will stuck on the red screen.And when i connect it to the PC,i got the red screen again.By the way,when the yellow kindle fire logo shows up, the PC could recognize the tablet but in less than 1 second the red screen will come out and the tablet will be disconnected from the PC as if the USB cable is pulled out.(i could hear the sound of disconnecting USB device.)
I also made a fastboot cable but it truned out to be invalid.Did i hard-brick the tablet? Is there any possibility to unbrick it? (I'm not a native speaker so sorry for my poor English)
Click to expand...
Click to collapse
These don't use fastboot. Use the regular USB and Has codes thread for 8.9" tablet for instructions to factory reset. Red screen on this is lack of bootloader.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
LinearEquation said:
These don't use fastboot. Use the regular USB and Has codes thread for 8.9" tablet for instructions to factory reset. Red screen on this is lack of bootloader.
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
Once the tablet is connected to the computer it will fall into red screen and become invisible to the computer in 1 second so the computer is not able to recognize the tablet.How can i install the necessary drivers?
BTW,you mentioned the instructions to factory reset,could you give me the link of the thread?
I would suggest using a Ubuntu 13.10 live CD in your case since you never installed the fastboot driver previously. Makes things a lot simpler since you won't need to install drivers, only the fastboot command. Should be able to install it from the Ubuntu software center, just search for fastboot.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
I would suggest using a Ubuntu 13.10 live CD in your case since you never installed the fastboot driver previously. Makes things a lot simpler since you won't need to install drivers, only the fastboot command. Should be able to install it from the Ubuntu software center, just search for fastboot.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I have opensuse installed in my PC but that doesn't work either. Connect the tablet with the computer and the red screen shows up then the connection breaks and the tablet become invisible to the PC,just the same situation as it is in windows.
Yes but here's the thing, it's supposed to do that. You basically run in a terminal "fastboot -i 0x1945 getvar product" and after it says waiting for device you plug your kindle in while it's off. That way once its detected for a brief moment it sends the command and goes into full fledged fastboot. Never had an issue with it in Linux before, then again I have never red screened my kindle and mine's a 7" model so a fastboot cable would have worked on mine.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
Yes but here's the thing, it's supposed to do that. You basically run in a terminal "fastboot -i 0x1945 getvar product" and after it says waiting for device you plug your kindle in while it's off. That way once its detected for a brief moment it sends the command and goes into full fledged fastboot. Never had an issue with it in Linux before, then again I have never red screened my kindle and mine's a 7" model so a fastboot cable would have worked on mine.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Thank you for you reply.I'd like to know if I could use this method in opensuse?
Should be able to as long as the kernel supports the device, anything modern should. I had native drivers in 10.04 of Ubuntu so it's safe to bet you have the kernel drivers. If you can't get it to work in suse, just try a live distro like I said, though I don't think there's a need to, but I have never tried suse before, I stick to Debian based distros.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
Should be able to as long as the kernel supports the device, anything modern should. I had native drivers in 10.04 of Ubuntu so it's safe to bet you have the kernel drivers. If you can't get it to work in suse, just try a live distro like I said, though I don't think there's a need to, but I have never tried suse before, I stick to Debian based distros.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
I tried thay in suse but it didn't work.I think when the yellow kindle fire logo shows up the tablet is in fastboot mode but I'm just wondering why the tablet can't stay in fastboot after the screen truned into red.
Because it's not supposed to... The 8.9" models don't work with a fastboot cable so instead they made it so it will briefly appear as a fastboot device when the boot loader initializes, and if a command gets passed to it while its briefly like this it gets told to go into full on fastboot mode. That red screen you're seeing is not it trying to go into fastboot, its just a messed up bootloader, but it should still be intact enough to reflash the bootloader to fix this. Weird to suggest this at this point but maybe try using an Ubuntu live CD and see what happens... I don't know why suse wouldn't work but maybe give it a shot.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
Because it's not supposed to... The 8.9" models don't work with a fastboot cable so instead they made it so it will briefly appear as a fastboot device when the boot loader initializes, and if a command gets passed to it while its briefly like this it gets told to go into full on fastboot mode. That red screen you're seeing is not it trying to go into fastboot, its just a messed up bootloader, but it should still be intact enough to reflash the bootloader to fix this. Weird to suggest this at this point but maybe try using an Ubuntu live CD and see what happens... I don't know why suse wouldn't work but maybe give it a shot.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
So your suggestion would be
step1，Download a Ubuntu live CD image file，write the image into a usb disk，and reboot into the live CD.
step2，Open a terminal，input the fastboot command，then connect the tablet to the PC when the terminal says"waiting for device"
step3，Then the tablet should stay in fastboot and it is now possible to fix the bootloader and system with fastboot command.
Did I understand that correctly？
stunts513 said:
Because it's not supposed to... The 8.9" models don't work with a fastboot cable so instead they made it so it will briefly appear as a fastboot device when the boot loader initializes, and if a command gets passed to it while its briefly like this it gets told to go into full on fastboot mode. That red screen you're seeing is not it trying to go into fastboot, its just a messed up bootloader, but it should still be intact enough to reflash the bootloader to fix this. Weird to suggest this at this point but maybe try using an Ubuntu live CD and see what happens... I don't know why suse wouldn't work but maybe give it a shot.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
And since my tablet is dead now， is it possible to install the fastboot driver in windows without the tablet？
It would be very difficult' unless you can get the driver into the driver cache but I haven't looked up how to do that, also on Ubuntu you will have to install the fastboot command, it should be in the Ubuntu software center, I'd give u the terminal command but I don't know the package name offhand.
Sent from my Amazon Kindle Fire HD using Tapatalk
Just out of curiosity have you tried KFFirstAide?
Sent from my KFTHWI using xda app-developers app
OK so i have searched everywhere for days. Tried tons of kindle unlock/unbrick tools. I rooted my Kindle fire HD7 (no sd card slot) using kingroot and twrp. at some point i used a utility that also put SuperSU on it. Everything seemed successful and i rebooted several times tweaking other settings, when i was almost finished tweaking i tried to remove kingsroot and rebooted which put me into some kind of boot loot. I only see the white/grey AMAZON (arrow under the word AMAZON) logo it only stays up for about 20 secs then goes black and starts over. All the unbrick tools i have tried either say can't find device and fail or say <waiting for device> and are never able to find it. I have installed new signed kindle device drives successfully. Windows device manager does show an Other device (with accompanying ding dong sound) > MTX65xx Preloader for about 5 secs then it disappears, the kindle never shows up as a drive thou. from what i read i think i may be stuck in fastboot? I don't know. I ordered and am using a Fastboot cable that i ordered from amazon which seems to have no effect. Ive tried using it in usb 2.0 slot as well as 3.0 (which they say won't work) The cable is from Atomic Market (3ft Motorola Factory Cable unbrick Droid Xoom Fire).
I also tried loading Ubunto via USB and running all unbrick tools i could find always the same .. it can't find device or waiting for device.
Windows 7 and Windows 10 same problem
Does anyone know how to help me? every article or guide i find talks about the kindle Fire logo that is orange and white with an animation or without. or a triangle... i have not read one article that talks about the white/grey amazon logo.
I believe i have a 2014 Kindle Fire HD 7 (no SD slot) was the cheaper version on sale this last year.
Thank you,
Mnfire
mnfire said:
OK so i have searched everywhere for days. Tried tons of kindle unlock/unbrick tools. I rooted my Kindle fire HD7 (no sd card slot) using kingroot and twrp. at some point i used a utility that also put SuperSU on it. Everything seemed successful and i rebooted several times tweaking other settings, when i was almost finished tweaking i tried to remove kingsroot and rebooted which put me into some kind of boot loot. I only see the white/grey AMAZON (arrow under the word AMAZON) logo it only stays up for about 20 secs then goes black and starts over. All the unbrick tools i have tried either say can't find device and fail or say <waiting for device> and are never able to find it. I have installed new signed kindle device drives successfully. Windows device manager does show an Other device > MTX65xx Preloader for about 5 secs then it disappears, the kindle never shows up as a drive even for a second. from what i read i think i may be stuck in fastboot? I don't know. I ordered and am using a Fastboot cable that i ordered from amazon which seems to have no effect. Ive tried using it in usb 2.0 slot as well as 3.0 (which they say won't work) The cable is from Atomic Market (3ft Motorola Factory Cable unbrick Droid Xoom Fire).
Does anyone know how to help me? every article or guide i find talks about the kindle Fire logo that is orange and white with an animation or without. or a triangle... i have not read one article that talks about the white/grey amazon logo.
Thank you,
Mnfire
Click to expand...
Click to collapse
Fire Index: Which Amazon (Kindle) Fire Do I have?
Sent from my KFFOWI using Tapatalk
sd_shadow said:
Fire Index: Which Amazon (Kindle) Fire Do I have?
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
I have a Kindle Fire HD 7 i believe it is 2014 model with no SD card slot
mnfire said:
I have a Kindle Fire HD 7 i believe it is 2014 model with no SD card slot
Click to expand...
Click to collapse
ok, please post in that forum.
Sent from my KFFOWI using Tapatalk
sd_shadow said:
ok, please post in that forum.
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
Done
http://forum.xda-developers.com/kindle-fire-hd/7-inch-help/kindle-fire-hd7-rooted-stuck-boot-loop-t3297856
A couple of months back I tried to flash something (If I recall correctly, I flashed an otter mod on twrp) and failed miserably. System was not able to be mounted anymore, kindle fire was not readable by adb, it had no operating system. Fast forward a couple of months I am stuck with FireFireFire menu (v1.4a) and there is no recovery either, just normal boot which boot loops the amazon kindle logo.
I do not have a fastboot nor factory cable.
Complete noob.
1st generation Kindle Fire.
P.S : When I try flashing twrp with KFU it says it succeeds but once I try a recovery menu it does not boot into recovery menu, just the firefirefire menu and from there the only working option is to normal boot into the kindle fire bootloop.
Help? Please?
thethrowaway2001 said:
A couple of months back I tried to flash something (If I recall correctly, I flashed an otter mod on twrp) and failed miserably. System was not able to be mounted anymore, kindle fire was not readable by adb, it had no operating system. Fast forward a couple of months I am stuck with FireFireFire menu (v1.4a) and there is no recovery either, just normal boot which boot loops the amazon kindle logo.
I do not have a fastboot nor factory cable.
Complete noob.
1st generation Kindle Fire.
P.S : When I try flashing twrp with KFU it says it succeeds but once I try a recovery menu it does not boot into recovery menu, just the firefirefire menu and from there the only working option is to normal boot into the kindle fire bootloop.
Help? Please?
Click to expand...
Click to collapse
First the only thing KFU is good for is installing the drivers.
You likely need a fastboot cable
$10 on Amazon or eBay
See my
[6.3.4] Flashing FFF and TWRP without Fastboot Cable
Sent from my ali using XDA Labs
sd_shadow said:
First the only thing KFU is good for is installing the drivers.
You likely need a fastboot cable
$10 on Amazon or eBay
See my
[6.3.4] Flashing FFF and TWRP without Fastboot Cable
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
Thank you for replying! I have tried that tutorial, however, I am always prompted with "error : device not found" even if the kindle is plugged in
thethrowaway2001 said:
Thank you for replying! I have tried that tutorial, however, I am always prompted with "error : device not found" even if the kindle is plugged in
Click to expand...
Click to collapse
Sounds like a driver issue
Sent from my Moto E (4) using Tapatalk
---------- Post added at 08:54 AM ---------- Previous post was at 08:51 AM ----------
See
https://forum.xda-developers.com/showpost.php?p=54123148&postcount=1
Sent from my Moto E (4) using Tapatalk
sd_shadow said:
Sounds like a driver issue
Sent from my Moto E (4) using Tapatalk
---------- Post added at 08:54 AM ---------- Previous post was at 08:51 AM ----------
See
https://forum.xda-developers.com/showpost.php?p=54123148&postcount=1
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
Ok through some trial and error I managed to install twrp on it using firekit on ubuntu, so now I at least have that. However, I cannot seem to be able to mount sd card. Tried soupkit to fix it, says it is fixed and I am given the same mounting error in twrp terminal. When I try to mount anything else other than that, the pc just does not see it. Driver issue? I remember installing the drivers just fine, what should I do next? Change its driver somehow?
P.S : In device manager it seems to be listed as "Android ADB Interface". Is that correct?
thethrowaway2001 said:
Ok through some trial and error I managed to install twrp on it using firekit on ubuntu, so now I at least have that. However, I cannot seem to be able to mount sd card. Tried soupkit to fix it, says it is fixed and I am given the same mounting error in twrp terminal. When I try to mount anything else other than that, the pc just does not see it. Driver issue? I remember installing the drivers just fine, what should I do next? Change its driver somehow?
P.S : In device manager it seems to be listed as "Android ADB Interface". Is that correct?
Click to expand...
Click to collapse
Which TWRP version?
Sent from my Moto E (4) using Tapatalk
sd_shadow said:
Which TWRP version?
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
Version 2.0.0.0
thethrowaway2001 said:
Version 2.0.0.0
Click to expand...
Click to collapse
Flash 2.2.2.1
Sent from my ali using XDA Labs
sd_shadow said:
Flash 2.2.2.1
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
How? The pc does not recognize the kindle, nor can I mount any files on it. Firekit only flashes 2.0.0.0, soupkit and kfu are not of much help either.
thethrowaway2001 said:
How? The pc does not recognize the kindle, nor can I mount any files on it. Firekit only flashes 2.0.0.0, soupkit and kfu are not of much help either.
Click to expand...
Click to collapse
Have you checked device manager?
Sent from my ocean using XDA Labs
sd_shadow said:
Have you checked device manager?
Sent from my ocean using XDA Labs
Click to expand...
Click to collapse
Mentioned previously it shows up as Android ADB Device. When I change the driver to usb composite it does show up as kindle and shows up as USB Drive F. I can store stuff on there, but there are no partitions and when I look for the files on TWRP they do not show up anywhere.
sd_shadow said:
First the only thing KFU is good for is installing the drivers.
You likely need a fastboot cable
$10 on Amazon or eBay
See my
[6.3.4] Flashing FFF and TWRP without Fastboot Cable
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
Is it possible for you to link a fastboot cable that would work from Amazon?
t3chwizard said:
Is it possible for you to link a fastboot cable that would work from Amazon?
Click to expand...
Click to collapse
Not many options anymore but this should work.
Factory Fastboot Cable by N2A (R) - Fix/Repair Kindle Fire, Kindle Fire HD, Kindle Fire HDX, Motorola Xoom & Phones https://www.amazon.com/dp/B0099E59SG/ref=cm_sw_r_u_apa_fabc_0.JbGbVDERHAA
Well gang it was a good run but I think mine is dead. It will only turn on for a split second when holding the power button and show the otterx bootlogo then shuts off completely (can't even select the recovery menu option) and this will repeat every time I try until it occasionally will go into the battery charging screen when holding the power button to turn it on (while the device is not charging, but then it shuts off after a second or 2 on that screen). I have tried a factory cable (the one @sd_shadow recommended above - which unfortunately seemed to not work). I also tried the pin short usbboot method which didn't work either. The battery does appear to be charging though, as it went from 75% to 83% after a bit of charging.
The odd thing is that I cannot get the power light to turn on when I have usb plugged into it (it only turns on without USB connected). So any of those occurrences above only happen when USB is not connected. I am not sure why this is, but I am very confused at this point.
If anyone has any ideas I would appreciate it, but I am assuming it's a lost cause at this point... not sure what else I can try beyond an entire motherboard swap
I am going to post a video of the shutting off so you guys can see what I am talking about, maybe that might help idk
EDIT: it's now at 86% so I am gonna see if I can charge it fully then try again
My thoughts are that either the battery is acting up, or the charging/USB port is, it has to be one or the other if I cannot get it into usbboot, but I am going to keep trying I guess. Will post those videos I said I would above soon