Develop Bugs

My Kindle Is Maybe Gone Forever!!!

My Kindle Fire is now maybe gone, forever!
It was a smooth and easy life for me and my Kindle Fire, we've been through root, recovery, bootloader and everthing. She was running fine, until the recent day.
I installed the 1.4 FFF from Hashcode, it was good, I loved the blue Kindle Fire logo. But then the next day I saw an update of 1.4a, so I booted into TWRP recovery and uses ADB (since I'm using Kernel 3.0 without ADB) and does the command:
adb push <filename> /sdcard
Sdcard: Read-Only File System
That was really weird, we all know sdcard is never a read-only, so I thought something was wrong here, I copy the FFF.bin file from my PC to my Sdcard using Mount USB (Still Working)
I tried the second command to install the FFF 1.4a:
adb shell
dd if=\......
And it says I/O error.
I thought I would reboot and live with 1.4 then, but when I reboot system in TWRP, the Kindle never came on again.
It was at 73% battery so there's no chance of a battery drain, but know when I press the power button, NOTHING, no green light, no backlight, it does NOTHING! When I was holding it, it was very very hot at the area around the power button, everywhere else it's cool. I hold it for 20 seconds, left it there and in the evening that area is cool again!
SO I doubt a hardware error, that separate the power button with the CPU,RAM,ROM to power it on or what--so--ever. But the Kindle was smooth until I tried to flash the 1.4a, and what was the problem with the "Read-Only SDCARD", even I can still Mount it to PC and Copy it over. What should I do, should I bring it to the Hardware Fixing Store? Or throw away my Kindle Fire!!!

Try wiping everything
Inviato dal mio Kindle Fire con Tapatalk 2

Recinded

Thepooch said:
http://forum.xda-developers.com/showthread.php?t=1550999
Click to expand...
Click to collapse
That's a factory cable isn't it? The problem is my Kindle won't power on, I'm doubting is hardware, will plugging in the factory cable turn on my device, now it's like a REAL BRICK, NOTHING!!!

Recinded

Thepooch said:
Yes that's a factory cable or try this http://forum.xda-developers.com/showthread.php?t=1430038
A factory cable will force your kindle to power on. http://forum.xda-developers.com/showthread.php?t=1392693
Click to expand...
Click to collapse
I hate to bother you like this, but even with no power button working and no backlight? I do think my case is rare, I mean it has to power on to do the commands right?I mean the Kindle is still hot while plug in and charge so I'm guessing it's energy problem? No offense so don't misunderstand this, but if the charger fails in powering on the Kindle Fire, why should the factory cable be a success? (Sorry my English is bad so it sounds offensive)

No offense taken but the factory cable acts as a short and puts your kindle in a state where you can fix the problem so keep reading on how to use this cable. you can also issue fast boot in kfu then power your device on after.

Thepooch said:
No offense taken but the factory cable acts as a short and puts your kindle in a state where you can fix the problem so keep reading on how to use this cable. you can also issue fast boot in kfu then power your device on after.
Click to expand...
Click to collapse
I see now, I guess I will order the cable now! Anyway I was browsing the forum and I see a guy who has the similar problem to mine (which also helped by you!) here: http://forum.xda-developers.com/showthread.php?t=1636107
So there is a problem of the Kindle leaving it can't power on and I'm not the only one that have it! What seems to be the cause and how to prevent this in the future for me and everyone else!

read my thread: bricked after installing fff1.4
Sent from my Amazon Kindle Fire using xda premium

lovejoy777 said:
read my thread: bricked after installing fff1.4
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
There were so many replies in that thread that blurry me, can you tell me how did you unbrick it??
PLEASE HELP!!!

Its not something you can explain in a few short sentences. You have to research it.

Make a usb stick that loads ubuntu, put fk at the root of it.
Take the back of your kindle off, short a certain point on the motherboard, plug your kindle into the computer and run the last command in the list for firekit.

tombombman said:
Make a usb stick that loads ubuntu, put fk at the root of it.
Take the back of your kindle off, short a certain point on the motherboard, plug your kindle into the computer and run the last command in the list for firekit.
Click to expand...
Click to collapse
You make it sound SO easy. Where were you when Lovejoy777 needed help?
(BTW that's a joke, so don't get bent out of shape)

it turned out it was my pc that caused most of my upset. im still sorting it now. iv'e had to wipe my hard drive and start again. just updating ubuntu 11.10 (not upgrading to 12.04 as i think thats when the fun & games started)
next is sdk/adb/fastboot etc :-(
my only tip is read the top link from the first page from tom (and i mean read it) then follow it to the t (no short cuts) and your kindle will boot i'm sure
if you get stuck at a certain bit post back with some detail of where you are at in the process etc. and people will help
Sent from my Amazon Kindle Fire using xda premium

Kindle Fire Failed Factory Reset

I had Jandycane installed and wanted to go back to the stock rom and I guess I didn't wipe everything I should have. The Kindle now boots into what appears to be a stock rom and then I get several popup errors and then it reboots. I have tried to quickly get into the factory reset but it reboots while trying to reset. The final says that "billing is not supported on this version of android market" If I ignore the error or if I don't swipe to log in it reboots anyway after about 10-15 seconds.
I have the Kindle fire utility installed but I don't see how I could mount if the unit won't stay on.
I don't see anyway to get into TWRP. The unit goes right into the kindle fire startup, so option for bootloader.
Anything I can try?

From the command prompt, with device turned off, enter:
Code:
adb wait-for-device shell idme bootmode 4002
…then turn the device on. That should put you back in fastboot, assuming the shell still works.

soupmagnet said:
From the command prompt, with device turned off, enter:
Code:
adb wait-for-device shell idme bootmode 4002
…then turn the device on. That should put you back in fastboot, assuming the shell still works.
Click to expand...
Click to collapse
It just boots to the Kindle Fire rom and reboots.

That's all? No messages in the command window? No errors or confirmations of any sort?

soupmagnet said:
That's all? No messages in the command window? No errors or confirmations of any sort?
Click to expand...
Click to collapse
Nothing. I tried the cable in a different port and the command window doesn't change. The Kindle Fire will say a USB cable is connected after I swipe into the Fire OS. It reboots after 10 or so seconds. One of the error in the Fire OS has to do with Calender and the other with android.process.acore.

You can try the Linux approach, but I doubt it would help in your situation.
You'll probably need to get a factory cable to get the device in fastboot before you can fix anything.

All fixed.
soupmagnet said:
You can try the Linux approach, but I doubt it would help in your situation.
You'll probably need to get a factory cable to get the device in fastboot before you can fix anything.
Click to expand...
Click to collapse
Cable bought, cable received, read the forums, got into TWRP again, wiped everything, installed clean ROM, ALL BETTER.
Thanks for your help and thanks to SkOrPn for the cable.

[Q] Need help with rooted(?) possibly bricked kindle fire

Back story: I purchased a used Kindle Fire on Ebay about a week ago, not knowing that it had been rooted. I was looking for a standard Kindle fire for my son so he would stop using my tablet (lol) and the parental controls are better and more books and so on... none the less when I got it I noticed that it booted differently (I had a kindle fire prior) and it booted into Android. I have had problems with trying to be able to get my computer to recognize it. It looks for missing drivers and I have been all frustrated, but figured that we would just have to download off of it, well, we went on a trip this past weekend (11 hours) and my son wanted to watch a movie, turned it on and it wont boot past the yellow triangle now. I have tried a hard reboot, I have tried to turn it on and hold it and watch for the orange light to no avail. The light is either green or its powered off.
I don know what to do at this point? I cant hook it to my computer (wont even recognize as an F drive or mass media) and I cant boot past the orange triangle. Yes, I am a newb (apologies) but a very frustrated one if that counts?
Sadly I think the thing is bricked and I will take a $150 hit (ugh)

No worries, your Kindle isn't bricked, it's just stuck in the wrong bootmode, which is easy to fix if you know what you are doing.
I could give you links to various guides and tutorials but it seems that it would be a lot to handle all at once for someone who knows nothing about Android and probably has no intention to.
Changing bootmodes is very easy, but getting everything set up to change bootmodes can be tricky, especially on Windows. It seems to me that you want the device back to stock (not rooted, stock bootloader, etc.), which may be a little less troublesome for you in the long run.
Hold the power button for 10-15 seconds to ensure it is completely powered off, then turn it on again.
When you see the yellow triangle, hold the power button until it turns orange and release. That should get you into the custom recovery that has been installed. When it boots into that recovery, describe what you see (i.e. recovery version, color scheme, etc.)

Yes, you would be correct in that I just want it stock, sure Android is great but my son is 4 and he just needs the basics for his books and angry birds lol. So, I attempted what you said, powered off all of the way and turned back on, as soon as I see the yellow triangle I hold the button and it wont turn orange, it will just power back off. I used to be able to touch the screen when the yellow triangle came up and it would take me into some menu (TWRP?) but it wont do that anymore either, its just remains either off or on the yellow triangle.
soupmagnet said:
No worries, your Kindle isn't bricked, it's just stuck in the wrong bootmode, which is easy to fix if you know what you are doing.
I could give you links to various guides and tutorials but it seems that it would be a lot to handle all at once for someone who knows nothing about Android and probably has no intention to.
Changing bootmodes is very easy, but getting everything set up to change bootmodes can be tricky, especially on Windows. It seems to me that you want the device back to stock (not rooted, stock bootloader, etc.), which may be a little less troublesome for you in the long run.
Hold the power button for 10-15 seconds to ensure it is completely powered off, then turn it on again.
When you see the yellow triangle, hold the power button until it turns orange and release. That should get you into the custom recovery that has been installed. When it boots into that recovery, describe what you see (i.e. recovery version, color scheme, etc.)
Click to expand...
Click to collapse

Well you're going to need a few things first.
The Kindle Fire Software Update
The Kindle Fire Utility
And you need to get a custom recovery. TWRP is kind of on the fritz right now so getting it from the TWRP website is probably not your best option. You can still find a working one with the smirkit but you'll have to extract it yourself. It will be titled "recovery_twrp_2.x.img". COTR will work just as well but be sure you get the .img
Extract the KFU and run the install_drivers.bat
Place your custom recovery.img in the Kindle Fire Utilitiy's " tools" folder
Shift + Right-click on the Kindle Fire Utilitiy's "tools" and select "Open command window here". In the window that opens up enter the following commands:
Code:
fastboot flash recovery name_of_recovery.img
fastboot oem idme bootmode 5001
fastboot reboot
I'll leave it at that until you can confirm you have recovery installed and you're booted into it.

I would if I could... lol... I can not get my computer to recognize the Kindle as either a kindle or a mass media drive... when I plug it in it will say that I need kindle drivers (which I am told there is no such thing as) and it does not show up as a drive either. I am to the point that I am about ready to throw it on craigslist for 50 bucks, take the 100 plus loss and start all over with a brand new one... damn you ebay! Lol
soupmagnet said:
Well you're going to need a few things first.
The Kindle Fire Software Update
The Kindle Fire Utility
And you need to get a custom recovery. TWRP is kind of on the fritz right now so getting it from the TWRP website is probably not your best option. You can still find a working one with the smirkit but you'll have to extract it yourself. It will be titled "recovery_twrp_2.x.img". COTR will work just as well but be sure you get the .img
Extract the KFU and run the install_drivers.bat
Place your custom recovery.img in the Kindle Fire Utilitiy's " tools" folder
Shift + Right-click on the Kindle Fire Utilitiy's "tools" and select "Open command window here". In the window that opens up enter the following commands:
Code:
fastboot flash recovery name_of_recovery.img
fastboot oem idme bootmode 5001
fastboot reboot
I'll leave it at that until you can confirm you have recovery installed and you're booted into it.
Click to expand...
Click to collapse

Save yourself the trouble mail it to me I will fix it then you reimburse me the return postage or better yet I can show you how to fix it without even mailing it . 150 for a first gen kindle is pretty high you kinda already got taken.

[email protected] said:
I would if I could... lol... I can not get my computer to recognize the Kindle as either a kindle or a mass media drive... when I plug it in it will say that I need kindle drivers (which I am told there is no such thing as) and it does not show up as a drive either. I am to the point that I am about ready to throw it on craigslist for 50 bucks, take the 100 plus loss and start all over with a brand new one... damn you ebay! Lol
Click to expand...
Click to collapse
Pay attention to what I said previously...
soupmagnet said:
Extract the KFU and run the install_drivers.bat
Click to expand...
Click to collapse
Clearly, there are drivers for the Kindle Fire and they are needed to fix your device.

I think I am officially over this thing... I downloaded the drivers and went to plug in the kindle fire to the computer and now its just looping the triangle... it turns on for a second and then off and on and off and so on... UGHHHHHH....
soupmagnet said:
Pay attention to what I said previously...
Clearly, there are drivers for the Kindle Fire and they are needed to fix your device.
Click to expand...
Click to collapse

You let the battery die. I won't go into how it happened but to get it to charge, you need to...
With the device turned off, Plug the device into USB and hold the power button until it shuts off again. If you can get it to stay off, leave it plugged in for about half a day and turn it on again.

Bricked Kindle HD.

After countless hours of trying to root it, I sort of finally did it right using this tutorial http://www.youtube.com/watch?v=CYDBoTtdvcE . After which of course it wasn't done correctly because I didn't have "Mount as R/W" available to copy market etc etc. Then because I'm a total twat I used http://forum.xda-developers.com/showthread.php?t=1638452 that to "UNROOT" it so I can try again. After I used adb shell su -c 'idme bootmode 5001' and rebooted, the device was bricked. It turned off and I assume it's a bootloop. The computer recognizes, then miliseconds after disconnects.
When I try to power it on, it goes through the Kindle Fire menu, then it goes to that orange "fastboot" thing where it dies, just after it produces a random vertical line on the screen.
Anything I can do?
EDIT: And nope I do not have TWRP installed.

The hd forum can be found here http://forum.xda-developers.com/forumdisplay.php?f=1782 The methods here are for the first gen. kindle only including the restore stock which very likely permanently bricked your kindle sorry to be the bearer of bad news.

Oddly bricked Fire TV Gen 1

Picked up a super cheap Gen 1 FireTV from a yard sale but I think someone was tinkering with it and messed something up.
Plugging it into to HDMI it gets stuck at the white Amazon logo (with black background), will not go further. Remote control and keyboard commands to reboot or go to recovery do nothing, but CTRL-ALT-DELETE on keyboard will reboot it and return to white logo. I had to connect to device via A-to-A USB cable. I believe the bootloader is fully unlocked as I can connect via fastboot and send / boot into CWM-based Recovery v6.0.5.1.4a.
ADB commands seem to work and I have followed this guide (http://www.aftvnews.com/how-to-unbrick-and-prevent-bricking-an-amazon-fire-tv/#toc3) but after installing the ROM it get stuck back at the white logo.
adb shell gives me this, which seems odd:
C:\Android>adb shell
~ # su
/sbin/sh: su: not found
~ # cat /proc/cmdline
androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 maxcpus=2 androidboot.emmc=true androidboot.serialno=<censored> androidboot.baseband=apq
~ #
I'm not sure what direction I should go now. I have tried to install the AFTV full unlock (https://forum.xda-developers.com/fire-tv/orig-development/firetv-bootloader-unlock-t3031867) but since su is not found, I am kind of stuck.
Any help would be greatly appreciated!

bump in case anyone has ever seen this kind of issue happen

dekkon said:
bump in case anyone has ever seen this kind of issue happen
Click to expand...
Click to collapse
By the "#" looks like you're already in a root shell.
Can you post the output of "id"?
Regards!

I don't know what I did but it seems to be fixed.
I'd put it away in a drawer after I didn't get a response for a week. Pulled it out last night to try your suggestion and it booted up to the main screen. In the process of upgrading to rbox's latest version.
Thank you mighty internet wizard