Develop Bugs

[Question] Kindle Fire is possibly dead.

Guys,
Details: Using Windows 7 64 bits, on a notebook.
Here is the full history of my brand new brick... call me stupid.
Second day with my Kindle Fire, I tryed to root my kindle fire.
Downloaded the KFU 0.9.5, instaled the drivers.
But the KFU wasn't workig... I only was getting the ADB offline status and the "waiting for device" message.
When I realized that the drivers I had were from my Motorola Milestone.
Next step: Uninstall the wrong drivers, and reinstall the new ones.
Only with this i could get the device to work with KFU.
Open the Run application at KFU folder.
Choosed option 2: Install Permanent Root with Superuser.
All worked fine until i get the message "with great powers come great responsabilityies" press any key to continue...
[EDIT: Tried to install Gapps extras... I don't remember if Kindle was dead before this or after]
The Kindle rebooted, got to the screen with the "kindle" word, and died.
Since that I'm getting no power on, no led lights, no response when connected to usb... nothing.
What should I do?
Go to Motorola Tech Support (here in my city) and try to use a factory cable?
or
I can only put my hopes on USB Boot Mode?
Guys, thanks in advance and sorry for my english, I certainly made some msitakes.
Or I can try Firekit?

That's strange, installing the wrong device drivers on your computer shouldn't affect your Kindle.
What it really sounds like is your battery died in the process of installing the FFF bootloader. How was your battery before you started? Have you tried holding the power button for 20 seconds for a hard shutdown?
As far as I know, the only thing that will cause power on issues is a broken bootloader. In which case, USB boot with firekit is your only option.

I guess I had at least 50% o battery charge, or more... I can't remember...
If I push the power button now, the Kindle will get warm, as if it was in use. And if I hold for 20s, will shut down...
I don't even started to install de fire fire fire bootloader, I installed the permanent root with super user and then went to install GApps. I guess my kindle was shutdown before Gapps install.
What should I do? Test the factory cable first?
When you say that I have to use Firekit, you are saying that I have to open my Kindle?

Left the Fire charging for at least 12 hours.
Tried to power on, to hold 20s and nothing happened.
I'll gonna try this:
Fix power on problems: If the Fire's screen never seems to turn on, you may have wrecked the bootloaders or the partitioning. Fortunately most of the time this results in the CPU falling into the low level USB boot mode. Use the "usb_fix_parts_and_install_fff_twrp" to rebuild the flash enough to boot TWRP. You don't need to use the USB shorting trick for this one, just power up the Kindle after running the script.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1430038
My question is: I'm running Ubuntu within VMWare tools. Can I boot from usb stick this way?
Gonna try this before I use factory cable or open my Kindle Fire.
EDIT:
Reading the FIREKIT Topic, this post: http://forum.xda-developers.com/showpost.php?p=25814062&postcount=26
My issue is kind of different from his... I'm guessing I'll have to open my Kindle anyway... Started yesterday, but I was messing with the case, gonna find some proper tools

VMs will not work. You have to create a bootable Linux LiveUSB thumb drive.

DuendePaladino said:
Left the Fire charging for at least 12 hours.
Tried to power on, to hold 20s and nothing happened.
I'll gonna try this:
http://forum.xda-developers.com/showthread.php?t=1430038
My question is: I'm running Ubuntu within VMWare tools. Can I boot from usb stick this way?
Gonna try this before I use factory cable or open my Kindle Fire.
Click to expand...
Click to collapse
If you already have a working Ubuntu installation, you don't have to make the USB stick. You can just run the fk binary in your Ubuntu setup.

kinfauns said:
If you already have a working Ubuntu installation, you don't have to make the USB stick. You can just run the fk binary in your Ubuntu setup.
Click to expand...
Click to collapse
I've tried it on a VM and had it confirmed by other users that VMs aren't fast enough to detect the USB in time. From what I've seen, it has always been suggested to either use either a straight Linux install or a bootable LiveUSB.

soupmagnet said:
I've tried it on a VM and had it confirmed by other users that VMs aren't fast enough to detect the USB in time. From what I've seen, it has always been suggested to either use either a straight Linux install or a bootable LiveUSB.
Click to expand...
Click to collapse
I guess it might depend on the VM, but I disagree with the generalization that VMs are too slow and have issues with USB.
The only thing I've seen is that Oracle's VirtualBox USB implementation breaks adb. I've never tried VMWare, but Parallels Desktop for both my Ubuntu and Windows setups work perfectly. Never had an issue.

DuendePaladino said:
What should I do? Test the factory cable first?
Click to expand...
Click to collapse
Anybody who is going to be modifying the basic software of their Kindle, or even just root it and play around, should have a factory cable. Xda member SkOrPn makes good ones at a reasonable price and ships them quickly. See http://forum.xda-developers.com/showpost.php?p=25725396&postcount=338.
(From what you wrote earlier, I presume that you don't yet have convenient access to a factory cable but would have to go out of your way to use one. If you do, in fact, have easy access to one, I can't imagine why you wouldn't try using it instead of putting a lot of effort into looking for alternatives.)

aarons510 said:
Anybody who is going to be modifying the basic software of their Kindle, or even just root it and play around, should have a factory cable. Xda member SkOrPn makes good ones at a reasonable price and ships them quickly. See http://forum.xda-developers.com/showpost.php?p=25725396&postcount=338.
(From what you wrote earlier, I presume that you don't yet have convenient access to a factory cable but would have to go out of your way to use one. If you do, in fact, have easy access to one, I can't imagine why you wouldn't try using it instead of putting a lot of effort into looking for alternatives.)
Click to expand...
Click to collapse
Without a working bootloader, a factory cable is useless.

soupmagnet said:
Without a working bootloader, a factory cable is useless.
Click to expand...
Click to collapse
All the scene leads to this... USB Boot.
About the USB stick, I was making some confusion about it.
But, I´ll gonna make one stick right now.

Guys,
I made the usb stick... just figuring how to open the kindle fire, without ruining the case.
But I guess today I'll made the short trick.
Question: I'll keep the 6.3 stock room that i tried to root? Or I'll have to download another ROM?

Is there any know issues about firekit compatibility with ubuntu 12.04?
Like this here? http://forum.xda-developers.com/showpost.php?p=25918331&postcount=10

I WON!!!!
I'M BEOWULF!!!!
Serious now...
Firekit method, with short trick... keep trying... until you find the right spot for the shor... and will work
EDIT:
THANK YOU GUYS!!!
I wouldnt be that happy without your help and your knowledge... You're the real Beowulf!

[Q] Kindle Fire rooting got ugly

ladies and gentlemen. i start this thread after months of being at my witt's end with my first generation kindle fire.
upon recieving my fire last december as a christmas gift from my father in law i coundn't wait to jump at the chance to root it and see what she can REALLY do. burritoroot at the time was the tool of choice to do it, and so i climbed about the band wagon. When the fire's software updated automatically it locked me out of root access (auto update was not a welcome surprise for an avid jailbreaker) i reluctantly picked myself out of the silicone mudd that the laughing folks at amazon had thrown me in while stealing my lunch money and wiped the sweat from my brow and returned to google to get myself back where i belonged, rooted, and easily enough, burrito root2 had dropped just in time to let me dance about with glee in the wonderful world of roothood once again until of course another update.
my bloodthirst for rooting had begun to wain as the new update left all me favorite tweaks still available even without having to get my hands dirty with root access. (google play and my custom skin with the eye candy of ice cream sandwich remained leaving me satisfied)
a few months went by and a stood mild mannered not willing to delve deeper into system files until the filthy root lust reared its ugly head again. this time flaunting a new shiny toy in front of my keen childlike eyes. Free. In-App. Purchases. I smoothly popped open my laptop in hopes to find burrito root three to give me that hot fix i needed. much to my dismay the rules had changed. doing this job would require a whole new batch of tricks. so i took the bait and downloaded KFU .0.9.6 and grabbed my usb cord in hopes that in a few minutes i'd be back balls deep in the 6.3.1 system files of my kindle fire. but of course this would not be the case. after installing the proper drivers to make device manager say what it is supposed to say, KFU wouldnt even notice my kindle was online on my windows 7 64 bit laptop. running as admin yielded different results, as it said adb was online but when asked to do anything it said it couldnt find the hard drive in question. nor the specified path. whats more it behaved the same way without the kindle even connected.
i went to bed to watch netflix on the device and decided to try again the next day. this time with my windows 7 64 bit desktop computer that i had used to root the item before (as well as a motorola backflip that i used for work at the time, but that is another tale.) i downloaded another copy of KFU .0.9.6, decompressed its files and placed it in drive C like a good boy. plugged the usb cord in and crossed my fingers. without a doubt things were working differently. not necessarily smoothly. but differently. kfu was reading the fire and so i chose option 2. the screen went black.
and i waited. and waited. my impatience got the better of me and i decided to start over thinking that things had frozen and become unresponsive. only to find my kindle would only boot to the unfainting orange and white kindle fire screen. frustrated i read as many forum support pages as my brain would allow. for weeks i did this until i found myself getting to frustrated knowing i'd have to finally resort to the inevitable. buying a factory cable.
so when i had some free cash on paypal i went to ebay and found one fro a chinese seller for 8 bucks shipped. eagerly i waited for a week until final arrival. i plugged it in just waiting for all my troubles to just vanish. nothing. i cant find it doing much of anything different. kfu is of course finding adb offline, and windows device manager is calling the device the same thing but stating the obvious (this device doesnt seem to start up properly) on a whim today i plugged it into my laptop. similar story. for about three minutes or so while it just sat rebooting itself every 10 seconds or so before i did more than plug the thing in. that changed when i hooked it up to a charger though. i'll keep you posted though.
my question though is where exactly am i going wrong? is the factory cable supposed to do something different right away? maybe i shouldve bought a factory cable from here to debunk that theory... i will of course appreciate any help i can get with this. luckily my wife's kindle still works so we arent completely tabletless. but being in maintenance by trade i know that $200 is a little steep for a masonry brick.
any wise guides apreciated.
-HJD

Part of it sounds like a flat battery but I think you caught that. The main problem I think you have on top of the battery thing is a broken shell which is exactly what a factory cable is for. I found a couple small things with the approach to using a factory cable that can help. First start with the device off plug to the device end then the pc side, it should boot static at the logo if it kicks into fastboot then recovery and bootloader can be sent to the device rooting stock is obsolete, simply do a full wipe when in recovery minus external storage/sdcard and flash a rom. About the very worst thing you can do is unplug the kindle in middle of a bootloader flash despite your thorough post I can't tell you if thats the case. The second way that helps get it into fastboot I have found is merely going through the paces shift+right click on the tools folder in kfu, select open command window here execute
Code:
fastboot -i 0x1949 getvar product
then plug the kindle in with your cable if the terminal throws product: kindle your are indeed in fastboot at least its been effective for me at that point you can use kfu to send fff and twrp. Mount your sdcard in twrp, transfer rom.zip and gapps zip, then unmount and unplug, wipe and flash away.
If your having trouble with drivers or the situation is worse like as in a broken bootloader then you will need Soupkit to rescue your device http://forum.xda-developers.com/showthread.php?t=1850038.

If the kindle is still at the orange and white KindleFire screen here's what you can try which has worked for me and a couple others at this point:
Plug in the kindle to the computer via a normal usb and turn it on (it should be at the KindleFire boot screen)
Boot up KFU, it probably won't see the device, but this is FINE!!!
Select the option to install TWRP, it should push it to it.
when the Kindle reboots it should be in recovery mode, if not try using KFU to boot it into Recovery mode.
If you get this far use KFU to download the latest amazon update. Find this update.zip and in recovery mount the kindle and move the update.zip to the root of the sdcard. Then try to install the zip and it should put you back to stock which then you can try rooting it again or you can leave it alone lol. You might run into an issue in recovery flashing the zip, if you do here's what you can do to fix that:
unmount data, system, cache BUT leave sdcard mounted
do a factory restore, wipe dalvik cache and cache
fix the permissions in twrp
then attempted to flash the update.zip
Now if you weren't able to get it into recovery or if TWRP failed instead use KFU to try and install FireFireFire. Again, KFU will most liekly NOT see your device, this is FINE, go ahead and try it. Remember use the normal usb cable for this. If you get FireFireFire installed then you can go ahead and try recovery TWRP at that point which then follow the steps I posted above. Hope this helps!

Do a full wipe before flashing.

looks like we got it guys! thank you so much. as for now it back to factory with the inclusion of fff and twrp. couldnt be happier at this point.:good::good::good:

[Q] Bricked ... tried most things ... need some guidance

Hi,
Some background - I've been tinkering with android roms on phones for a while, and thought i'd give it a go on my Kindle, which I hardly ever use with the stock rom. I have a very low level of understanding regarding rooting, etc., but generally I'm good at following instructions (until now!)
So everything was going along nicely. Because I hardly ever use the device, I decided to do a full wipe before installing the new rom. Then, when I went to flash it, it turns out that I had forgotten to copy the new rom onto the SD card. In a moment of temporary insanity, I turned the device off (don't ask me why, I can't explain it).
On restart, the device now gets stuck on the logo screen. KFU tells me that the device is online, but boot status is unkown, and it can't change the status (although it does reboot the device when I try to put it into fast boot mode- but it doesn't actually 'fastboot').
If I try to reinstall TWRP or anything else, I get the 'exec system\bin\sh failed' error. The Kindle unbrick utility is unable to help.
I did some research and it kept pointing me to a factory cable, which I duly bought off eBay. When I use the factory cable, the only difference is that the boot sequence is slightly different (different levels of backlight) and KFU can't recognise the device at all - it says its offline.
I have no idea if the factory cable I have bought is any good - it might be complete rubbish.
Can any tell me if there is a simple option I have missed? Is trying fixes through Linux the only option? Will I have to open my kindle to fix it? I've already spent a heap of time on it, and I'm just about ready to call it a paperweight. Any help would be greatly appreciated.

I`m a little confused so file me in. Do you have access to recovery? with your type of error "exec system\bin\sh failed" a factory cable is indeed needed to reinstall twrp and the bootloader, unless you can access TWRP and mount your sdcard and transfer a rom. If that is not possible then you have some kind of mounting issue. So I still wonder what happened to your recovery and your bootloader? For me yet not everything is meshing to well. No bootloader, no acces to recovery, kindle just boots to logo and no further. Does the logo flicker and brighten and dim at boot? Yes very likely you will need to run linux on a live usb then run soupkit on it. Still you may still need a real factory cable not one half **s one from ebay you can find that here http://forum.xda-developers.com/showthread.php?t=1392693 from user @SkOrPn no one can beat what he does I`m sorry. As for linux and soupkit the where and how is here http://forum.xda-developers.com/showthread.php?t=1850038 . Unless you get easily confused then try the iso I created with some fairly easy instructions soupkit is ran already simple create boot and use you can find that here http://forum.xda-developers.com/showthread.php?t=1413358 post # 7 make no mistake that this is only for the kindle like the last person I helped with this setup. This is your best route to get your kindle fixed sounds like it could still be a combined effort cable and soupkit .You will know when you hook your kindle up and run some of the features in soupkit if your device is truly online or if a cable is needed. If you run my iso teamviewer is also installed so it provides a nice edition for assistance if you want someone to see what you see. If you choose to run soupkit then the par for instructions differ from those of my iso.

Thepooch said:
I`m a little confused so file me in. Do you have access to recovery? with your type of error "exec system\bin\sh failed" a factory cable is indeed needed to reinstall twrp and the bootloader, unless you can access TWRP and mount your sdcard and transfer a rom. If that is not possible then you have some kind of mounting issue. So I still wonder what happened to your recovery and your bootloader? For me yet not everything is meshing to well. No bootloader, no acces to recovery, kindle just boots to logo and no further. Does the logo flicker and brighten and dim at boot? Yes very likely you will need to run linux on a live usb then run soupkit on it. Still you may still need a real factory cable not one half **s one from ebay you can find that here http://forum.xda-developers.com/showthread.php?t=1392693 from user @SkOrPn no one can beat what he does I`m sorry. As for linux and soupkit the where and how is here http://forum.xda-developers.com/showthread.php?t=1850038 . Unless you get easily confused then try the iso I created with some fairly easy instructions soupkit is ran already simple create boot and use you can find that here http://forum.xda-developers.com/showthread.php?t=1413358 post # 7 make no mistake that this is only for the kindle like the last person I helped with this setup. This is your best route to get your kindle fixed sounds like it could still be a combined effort cable and soupkit .You will know when you hook your kindle up and run some of the features in soupkit if your device is truly online or if a cable is needed. If you run my iso teamviewer is also installed so it provides a nice edition for assistance if you want someone to see what you see. If you choose to run soupkit then the par for instructions differ from those of my iso.
Click to expand...
Click to collapse
No, I can't access recovery at all. When I use the factory cable, there is no flicker, but all other ways (standard cable, no cable) there is a flicker and it brightens. Either way, it just hangs on the logo.
I suspect that the factory cable is not all it should be ... I will probably try the @SkOrPn option first, then work my way through the other options you mention. I had kind of figured from reading other posts that this would be the case ...
Thanks for taking the tiime to help.

There is no flicker because your likely in fastboot the lack of recognition is drivers which can easily be solved using linux and soupkit. Otherwise straighten out your drivers in windows by running the driver bat packaged with kfu. If your on XP it`s a fight to the death to try to sort out unsigned drivers on that os. Sometimes I can get it fast other times it`s pointlessbut a huge hassle nonetheless. Attempt to fix your drivers while using the factory cable you have maybe you will get lucky.

Fixed! Thanks so much!
I used your pre-installed ISO and it was a piece of cake. Initially, I had the device connected over the factory cable and it wasn't recognising it, but when I swapped to a standard cable, suddenly I was able to reboot into recovery straight away. Rom mounted and installed, and I have a new tablet!
Definitely appreciate all your hard work!

That`s great I`m happy you had good success!!

[Q] KF2 Empty and not recognized on windows

So I was trying to change my son's Fire 2 over to the new Kit Kat OS, and as I was downloading the necessary files to my computer, I thought I would wipe everything, since he had managed to pretty much fill it with junk, (he's 8). I have TWRP, (2.3.3.0) installed, and used that to wipe everything, including the internal storage and the format data wipe. I have done this with my Fire 1 with no issues, but this time I ran into a problem. TWRP works fine, but now windows won't recognize the tablet. When I go to mount the usb storage to copy the os files over, windows 7 cant load the device drives, and in my device manager it shows the Amazon Kindle fire 2 with the yellow exclamation mark next to it, saying that the drivers for this device are not installed. I have the SDK installed, and I have gone through and re installed the device drivers several times, and also uninstalled the kindle from the device list in manager. Nothing is working. I have attempted fastboot, but when I do try, it gets stuck at the "press the button menu" for TWRP, and after running the fastboot -i 0x1949 getvar product command, it tells me it sees an Otter2-Prod-04.
Does anybody have any ideas or suggestions on how I can get into the usb storage so I can load the OS info? Thanks for any help.

Dead?
Well, I rebooted from TWRP and it just went black. No light when the cable is plugged in, (factory cable), no twenty second reset working, nothing. IS it safe to assume I now have a pretty paperweight, and I should be looking into getting my son another tablet?

xanthian23 said:
Well, I rebooted from TWRP and it just went black. No light when the cable is plugged in, (factory cable), no twenty second reset working, nothing. IS it safe to assume I now have a pretty paperweight, and I should be looking into getting my son another tablet?
Click to expand...
Click to collapse
Leave it on the charger overnight. Keep trying 20 second reboot. If you can get back into recovery you can adb sideload a rom into the device.
You've never been able to USB Mount this device from recovery.
Good luck. No reason it should be bricked....
How did you try to get into fast boot? You need a fastboot cable. This device is NOTHING LIKE the kf1.
Edit: also need to be sure exactly which kf2 you have.
--》Sent from my mind to your screen

mindmajick said:
Leave it on the charger overnight. Keep trying 20 second reboot. If you can get back into recovery you can adb sideload a rom into the device.
You've never been able to USB Mount this device from recovery.
Good luck. No reason it should be bricked....
How did you try to get into fast boot? You need a fastboot cable. This device is NOTHING LIKE the kf1.
Edit: also need to be sure exactly which kf2 you have.
--》Sent from my mind to your screen
Click to expand...
Click to collapse
I have the standard cheap Kf2, no HD, just the upgrade from the first from last year, (2012), they were selling around Christmas last year. I have tried getting it to start back up, but with no success. I don't even understand why it shut down like that. I hadn't done anything to it other than reboot, which I had done successfully several times before. As for the fastboot, I may be incorrect. I ran the adb command: fastboot -i 0x1949 getvar product in CMD, and then plugged the kindle in and booted up. It showed it was an otter4 or something like that, which I thought meant it was in fastboot. At that time I was using my S4 usb cable. I'm sure I can sort out ho to sideload a rom via adb if I can ever get it started back up again. I had thought about opening it up and unplugging the battery and then re-plugging it back it to try to reset it, but I doubt it will help. Would getting a fastboot cable possibly make it start back up? If anyone has any suggestions on how I can get this thing started up again I would greatly appreciate it. I fell like crap for bricking my kids kindle, he's 8, so it's really important to him. It'll take me several months to save up to buy another one, so if I can get it running again, that would be awesome.

Here's a bit of an oddity, and maybe this spells some hope for me yet. So I plug the KF2 into the computer with the factory cable, hold down the power button for twenty seconds, let go, and then hit the power button again, for about a second, and windows makes the usb device plugged in sound, followed by a usb rejected or not recognized sound. It repeats this over and over for about thirty seconds or so and then stops. So there is something going on with the kindle, and its not flat out dead, or at least it seems. Is this a good sign? Does this help anyone to figure out what I might need to do?

So just to be sure that I was using a fastboot cable, even though I believe that my samsung s4 cable is fastboot capable, and I'm pretty sure I am using the factory cable, (it's not marked so I can't be 100% sure), I built my own fastboot cable, via instructions on how to do so on xda. (found HERE) It's doing the same thing with windows making the usb device inserted / recognized sound, followed by the usb device error sound. I'm guessing that this is a bad thing, am I correct?

One more bit of information to add to the list. I attempted to do the fastboot mode again,and decided to watch my device manager. Whenever windows chimes off that it detects a usb device, something called OMAP 4430 pops up for about a second before disappearing when the error sound comes on. I'm going to try and get a driver for that, just to see what happens. Maybe it'll help. I doubt it, but you never know until you try...

This just keeps getting weirder and weirder. So I installed the omap driver for windows and android, and now windows recognizes the device, but only for about a second. It just keeps cycling through the usb connected sound, recognizing the omap device, and then the usb disconnected sound, as though the device were being plugged in and then unplugged about every second for roughly thirty seconds. I'm starting to think there is something seriously wrong, which bites. If anyone has any suggestions, I'm all ears.

That's a hard brick' we can't use the usboot/aboot utility to fix the device like you can on other omap devices because we need a certain signed file to fix the boot loader. Only amazon has that file and they aren't giving it out. There is a way to recover your device from a hard brick but you need to be good with a soldering iron and have a USB sdcard reader, the kind that kinda is like a flashdrive rather than the multi type readers and some really small wire. Kurohyou wrote a tutorial on how to fix it in the kf2 dev section, not sure if he ever added the part in on how to reflash the boot loader from Linux, but if you take this route and try to fix it I wouldn't mind helping.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
That's a hard brick' we can't use the usboot/aboot utility to fix the device like you can on other omap devices because we need a certain signed file to fix the boot loader. Only amazon has that file and they aren't giving it out. There is a way to recover your device from a hard brick but you need to be good with a soldering iron and have a USB sdcard reader, the kind that kinda is like a flashdrive rather than the multi type readers and some really small wire. Kurohyou wrote a tutorial on how to fix it in the kf2 dev section, not sure if he ever added the part in on how to reflash the boot loader from Linux, but if you take this route and try to fix it I wouldn't mind helping.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
OK, I have both a tf - micro sd card usb card reader, and a full sd card usb card reader. I'll have to go digging for them in the morning, but I think I can find them. I'm also really good with a soldering iron, (used to be a vcr / tv repair technician), It took me roughly two minutes to do the homemade factory cable. So I am game, especially since at this point I really have nothing to loose by trying. Would you mind posting a link to where the tutorial is? I'm going to go looking for it, but just in case I can't find it, a link would help. And thank you so much for this suggestion!

OK, I found the tutorial on how to wire everything up and what's needed. I'll have to go get some small wire and a better tip for my iron, but aside form that, the wiring and soldering seems simple enough. My problem is going to be dealing with linux. I know Windows backwards and forwards, but I have a pretty limited knowledge of linux, aside from a few things we did in school to cover general PC repair. I can get it up an running, which I will do tomorrow, but I may need some help sorting out what to do with it once I have the board lined up and ready to roll, which will have to wait till next week when I get back from a work trip. Do you know if kurohyou offers repairs? If it's not too expensive, I would be willing to pay for the fix.

He might repair it, he just made a solderless repair tool to repair them. But like I said I'm more than willing to help with the Linux side, I'm a PC tech myself and use Linux primarily, you can basically burn an ubuntu live CD or put it on a USB stick and boot into the entire os without having to install it, from there's its as simple as plugging the device into the PC, and seeing what device path it assigned to the kindle's emmc, and running a dd command to flash the boot loader back onto the device.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
... you can basically burn an ubuntu live CD or put it on a USB stick and boot into the entire os without having to install it, from there's its as simple as plugging the device into the PC, and seeing what device path it assigned to the kindle's emmc, and running a dd command to flash the boot loader back onto the device.
Click to expand...
Click to collapse
Yeah, I've ran a live usb version of unbuntu a few times, and in the past I have had the full version on my system, but I rarely ever used it, so I got rid of it. I have an extra 600 gig's of space just sitting around on my laptop, so I will install a full version, and get off my lazy rear and start learning linux. This should be a good first lesson. I can't do any of this until next week though, so I will be pm'ing you once I've gotten everythig hooked up and ready to go. Thanks again for the help.
I had a question about the repair though. I went through the discussion, and I may have just missed it, but did he ever figure out how to get the OS up and running? From what I could tell, he was still working on it, and hadn't managed to get a working rom loaded. I probably just either missed it, or didn't understand one of the post's.

*Solved* FireTV 1 Gen - Rooted/Unlocked BL/Pre-rooted 5.2.7.2_r1, can I downgrade?

Basically I want to downgrade from rbox's pre-rooted version 5.2.7.2_r1 back to 5.2.6.3_r1.
I use ADB via Windows 10 with no problems, I've access to SU, FireTV is rooted and TWRP 3.0.0.7 is installed.
In the past I would just boot into TWRP recovery and select any of rbox' pre-rooted rom and hit install/upgrade and all went well since 2016.
This is the first time trying to downgrade, TWRP recovery went well 5.2.6.3_r1 got installed, but no way to login into my Amazon A/C (kept saying login/password combinations not correct, but they were 100% correct).
One thing interesting is before I could see my bootloader as fully unlocked as "[email protected]", but now I see its only partial unlocked ([email protected])?
Update:
It seems like I do have rooo#bueller? from this picture after typing adb shell and su?
Any help will be much appreciated!

In regards to your original post on the bueller thread - have you tried re-enabling updates? A few other members here found that disabling updates on their sloane (see here) stopped them from using particular apps on 5.2.7.2 until they re-enabled updates, allowed the Fire TV to download updated apk files & then disabled them again
If that doesn't work: I had a Fire TV recently that I thought it was blacklisted by Amazon (wouldn't log in with the correct details), but turns out it was just never registered as a AFTV on their end & was being refused a connection. This obviously won't be your case, but something similar could be happening, so I would suggest you remove the device from your account (here: https://www.amazon.co.uk/hz/mycd/myx#/home/devices/1) & then attempt to log in again - if this doesn't work, maybe talk to Amazon via their live chat, ask them to register your device to your account manually (they'll happily do it) & attempt login again after a hour or two (that worked for me).
edit: I've just seen your latest post about bricking - general rule of thumb (as far as I'm aware) is that anything after 5.2.6.8 shouldn't be rolled back to pre-5.2.6.8 due to changes within the partitions, therefore, if you do so, you essentially brick your device after reboot as the prerooted zip only flashes boot/preloader/LK, then at boot, the rpmb checks to see if all those files match & when they don't, sends the device into a bootloop. If this was a Fire TV 2, you'd be in luck, but unfortunately, there doesn't seem to be any way to unbrick a Fire TV 1 on the latest software yet?
If you're bootloader unlocked, you might be able to get into fastboot & fix it from there, but I'm not clued up on the Fire TV 1 bl unlock unfortunately.

DanielF50 said:
I've just seen your latest post about bricking - general rule of thumb (as far as I'm aware) is that anything after 5.2.6.8 shouldn't be rolled back to pre-5.2.6.8
Click to expand...
Click to collapse
Completely right for the second gen fireTV :good:
But the first gen fireTV isn't a MTK SOC device, the SOC is from broadcom with different booting stages. In case of a rooted box, you can up- & downgrade to any fireOS 5 version if you like.
DanielF50 said:
there doesn't seem to be any way to unbrick a Fire TV 1 on the latest software yet?
Click to expand...
Click to collapse
There is a way, but it requires hardware (low voltage emmc adapter, a special sdcard reader, small soldering iron) and at least some soldering skills.
DanielF50 said:
If you're bootloader unlocked, you might be able to get into fastboot & fix it from there, but I'm not clued up on the Fire TV 1 bl unlock unfortunately.[/B]
Click to expand...
Click to collapse
Some guys have tried it, it's all in the bueller prerooted rom thread.

Hi Daniel, thanks for taking the time to write.
Yes my bootloader is fully unlocked, and my unit is rooted with TWRP installed.
Hi Sus_i, where are you at? If you can try the "hardware (low voltage emmc adapter, a special sdcard reader, small soldering iron)" thing on my FireTV, I will compensate you for your time and ship the unit to you (I'm near the border, so US/CAN addresses are fine with me).
Ok, this is what happened in my case:
My FireTV 1 background - bought directly from Amazon, rooted back in 2015/2016, bootloader fully unlocked and TWRP installed in 2017.
1) Was running on rbox's pre-rooted 5.2.6.3_r1
2) Updated to rbox's 5.2.7.2_r1 and discovered that upon resuming/waking up from sleep the unit always return to the Home page instead of whatever page/Tab you left it as in 5.2.6.3_r1, also Alexa and few other APPS were automatically installed in 5.2.7.2_r1.
I only use 4 APPS on my FireTV, an APK from my IPTV (90 %), VLC to watch videos from my own local Network (5%), CX_File Explorer to move/transfer files (3%) and NewPipe (alternative to YouTube) (2%).
rbox’s pre-rooted 5.2.6.3_r1 is perfect for my needs above, as I NEVER need to see the Amazon Home screen or any ads. Only the 1st time after a power off/on that I would ever see the Home page and from there on I would navigate to the “Settings” Tab – “Applications” Tab – “Manage Applications” and I only see a few pre-installed APPS from Amazon and my 4 APPS above and going to sleep mode and waking up sleep mode always stays in the “Manage Applications” Tab and NOT Amazon Home page as in 5.2.7.2_r1.
3) Flashing back from 5.2.7.2_r1 to 5.2.6.3_r1/5.2.7.0_r1/5.2.6.9_r1 to no avail because I would always get an error stating Login ID/password combinations were in errors (Login ID/password were 100% dead correct), also the Developer Options would also no longer showing under My Device/My FireTV Tab. Amazon FireTV support would be quick to add the FireTV under my profile (because they could see I bought it directly from them back in 2014 and they also could see my serial numbers and all along I was the only one registered for this unit), but still no go, so I tried to de-register/re-register again during all the testing and Amazon must had added the FireTV to my profile at least 10 times and in the end it escalated to the point they credited my account $25.00 (this is usually the price of the FireTV Stick 4K during sales/promotions) and also at the same time sent out a FireTV Stick 4K to me FOC.
I’m not a FireTV expert, but just an ordinary user with some sys/programming backgrounds during my early years. I reckon Amazon must had implemented some sort of hard coded checks either on their side (registration) or in the firmware since 5.2.6.3_r1.
4) So now my unit is flashed with 5.2.6.3_r1 and couldn’t get passed the registration screen, what do I do? I re-flash it to 5.2.7.2_r1 and bingo, everything is back to normal again and don’t even need to register the unit. (For testing purposes, I removed my A/C from the unit and re-register again and this time Login ID/password got no errors).
5) Thinking that back from Windows 98SE/2000/XP Pro/W7 Pro and now Windows 10 Pro, no matter what kind of messed I created, I would just format the drive/write zeros and re-image (Ghost image Back-ups) and everything would be normal again. My fireTV is rooted, bootloader is fully unlocked and TWRP installed, I told myself what’s there to afraid of , so I tried to re-flash 5.2.7.2_r1 to 5.2.6.3_r1/5.2.7.0_r1 and it would always back to the registration error and now double icons under settings, lol.
6) I suspect during one of the re-flash I made a mistake of after clearing/wipe Cache/Dalvik, instead of the default reboot, I ESC back out and redo the install/re-flash thinking that might get rids of all the leftovers that cause the double icons under Settings.
7) Now I’m left with the white Amazon logo on my TV screen and white pulsing light on the unit itself. I like to think that the motherboard or the power unit are still alive, just that the software part of it got messed up by ME big time!

Matt_7 said:
Now I’m left with the white Amazon logo on my TV screen and white pulsing light on the unit itself
Click to expand...
Click to collapse
Like DanielF50 said, as a first step you may try to connect with fastboot, use an usb a-to-a cable and run: fastboot devices

Sus_i said:
Completely right for the second gen fireTV :good:
But the first gen fireTV isn't a MTK SOC device, the SOC is from broadcom with different booting stages. In case of a rooted box, you can up- & downgrade to any fireOS 5 version if you like.
There is a way, but it requires hardware (low voltage emmc adapter, a special sdcard reader, small soldering iron) and at least some soldering skills.
Some guys have tried it, it's all in the bueller prerooted rom thread.
Click to expand...
Click to collapse
Good information to know, thanks Sus_i :good:
Reading Matt's response, it looks hopeful that he should be able to fastboot into the device to recover it then.

Sus_i said:
Like DanielF50 said, as a first step you may try to connect with fastboot, use an usb a-to-a cable and run: fastboot devices
Click to expand...
Click to collapse
OK, I'll get the USB A to A cable, how does one run the fastboot?
Once I connect the FireTV to my PC using the USB A- A cable, what will happen? do I need to install anything on my Windows 10 to run fastboot?
Update:
OK, dfound out I already have fastboot in my platform-tools folder,
From AFTNews:
Enter the command:
fastboot devices
If your computer has correctly detected your Fire TV, you will see a series of numbers followed by the word “fastboot” after entering the above command.
Download the latest version of ClockworkMod custom recovery from AFTVnews.com/recovery
Rename the file you just downloaded to “recovery.img”
Enter the command:
fastboot flash recovery recovery.img
(Be sure to replacerecovery.img with the full path to the file you just renamed)
Enter the command:
fastboot boot recovery.img
(Be sure to replacerecovery.img with the full path to the file you just renamed)
Your Fire TV should now boot into ClockworkMod recovery. Proceed to follow the steps in the next section below labeled “Resetting with Recovery Mode”.
Resetting with Recovery Mode
If you can successfully enter ClockworkMod recovery, then follow the below steps to reset your Fire TV, regardless of what state it is in and what has been done to it. You can also follow these steps if, for example, you want to update your ROM but aren’t sure if you’ve unlocked your bootloader or aren’t sure if you’ve installed the boot menu.
[OPTIONAL] From within ClockworkMod, select the option to “wipe data/factory reset”. This will delete all of your settings and user data. It is an optional step, but is recommended.
From within ClockworkMod, select the option to “wipe cache partition”.
Follow my guide to install pre-rooted Stock ROM version 51.1.4.0_514006420 updated. Note, you are NOT installing the latest pre-rooted ROM on purpose. Do NOT skip ahead and install the latest pre-rooted ROM.
Restart your Fire TV. You should be able to boot normally.
Follow my guide to install BusyBox.
Follow my guide to unlock your bootloader.
Follow my guide to install the boot menu.
Follow my guide to install the latest pre-rooted ROM.
Do I need to redo all these? I already have TWRP. If I'm to do the above I would end up with both TWRP recovery and ClockworkMod custom recovery, right?
Once done, do I actually install the 51.1.4.0_514006420 updated or 5.2.6.3_r1?
Pardon my ignorance!

Matt_7 said:
OK, I'll get the USB A to A cable, how does one run the fastboot?
Once I connect the FireTV to my PC using the USB A- A cable, what will happen? do I need to install anything on my Windows 10 to run fastboot?
Click to expand...
Click to collapse
Yep, bundled with android-sdk so runs just like you'd use adb, but obviously has a different purpose/commands - I should think there would be info on the full bootloader unlock thread on how to use it to recover from a bootloop using fastboot?

Matt_7 said:
Do I need to redo all these? I already have TWRP. If I'm to do the above I would end up with both TWRP recovery and ClockworkMod custom recovery, right?
Once done, do I actually install the 51.1.4.0_514006420 updated or 5.2.6.3_r1?
Pardon my ignorance!
Click to expand...
Click to collapse
You can try to boot the recovery.img (boot... not flash!)
This means, grab the latest prerooted, extract the recovery.img into the fastboot/adb folder. Check/connect with fastboot devices and run: fastboot boot recovery.img
In case this fails, you may carefully follow the guide you've posted above.

Sus_i said:
You can try to boot the recovery.img (boot... not flash!)
This means, grab the latest prerooted, extract the recovery.img into the fastboot/adb folder. Check/connect with fastboot devices and run: fastboot boot recovery.img
In case this fails, you may carefully follow the guide you've posted above.
Click to expand...
Click to collapse
OK, will try and report back.
I actually made a copy of "bueller-twrp_3.0.0-7.img", "bootmenu.img" and "recovery.img" which I copied from the FireTV before flashing, I reckon I can use the "recovery.img"?

Matt_7 said:
OK, will try and report back.
I actually made a copy of "bueller-twrp_3.0.0-7.img", "bootmenu.img" and "recovery.img" which I copied from the FireTV before flashing, I reckon I can use the "recovery.img"?
Click to expand...
Click to collapse
I would try to boot bueller-twrp_3.0.0-7.img and recovery.img

Update 3:
Gosh, I got it to the point of checking for updates and unplugged the internet cable hoping to issue via adb to block OTA, and the FireTV detected no internet connection and asked to unplug the power for a few minutes and I did that, but now no whatsoever light on the FIreTV itself, don't tell me its now dead not because I bricked it the other day, but because of the power unit?
Tested the power adapter with a multimeter, got 6.18V (6.25 is printed on the power adapter), since 6.18V is close to 6.25V, its not the power adapter right?
Update 2:
OK, figured out I could remove the USB A to A cable and use the USB port on the FireTV to connect my Logitech K400 ! (see, I'm not a very smart person!)
- I deleted "Data"
- Tried to wipe cache and got a message "No OS installed"
- No choice but to select install option and install 5.2.7.2_r1
- Now at least I'm seeing the Colourful Amazon logo again, and now its doing the "Optimizing system storage and applications...", wish me luck!
Update 1:
Just received my USB A to A Male to Male (LOL) cable today.
Don't know to jump for joy or cry!
- When I typed "fastbbot devices", I got exactly from "AFTNews - If your computer has correctly detected your Fire TV, you will see a series of numbers followed by the word “fastboot” after entering the above command.", I got the screen showing me my device/serial number and the word fastboot, so I think its working!
- I then typed "fastboot boot bueller-twrp_3.0.0-7.img" and the white Amazon logo was gone I was back in TWRP screen, but I couldn't do anything, the USB port is already used by the USB A to A cable (USB splitter couldn't work either), I see the mouse pointer, but how to move it to reboot/wipe/install/advance etc?
Mayday, help!

Matt_7 said:
Update 1:
Click to expand...
Click to collapse
:good:
Matt_7 said:
Update 2:
Click to expand...
Click to collapse
:good:
Matt_7 said:
Update 3:
Click to expand...
Click to collapse
Pull all the plugs from the box + tv and try again...
6.xx v seems ok. Any voltage drops if you connect a device, light bulb or anything like that?

Sus_i said:
: Any voltage drops if you connect a device, light bulb or anything like that?
Click to expand...
Click to collapse
Thanks Sus_i.
How to connect the light bulb to test, and connect from where to where?
I couldn't believe what a stupid move I did by pulling the internet cable and now I want to beat myself so bad...
I've a few power adapters from router/modem etc lying around, will I damage the Fire TV if I'm to try them out?

Matt_7 said:
Thanks Sus_i.
How to connect the light bulb to test, and connect from where to where?
Click to expand...
Click to collapse
Have you tried to pull all plugs, reconnect only the power supply... what does the LED?
There is an ifixit guide on how to disassemble the fireTV. In case you open the box, measure the voltage IN inside the fireTV at power on. You can measure VDD 3.3v and VDDQ 1.8v too, next to the emmc, see the picture here.
Matt_7 said:
I couldn't believe what a stupid move I did by pulling the internet cable and now I want to beat myself so bad...
Click to expand...
Click to collapse
That shouldn'd harm anything. In case of a failure, the fireTv should blink yellow.
Matt_7 said:
I've a few power adapters from router/modem etc lying around, will I damage the Fire TV if I'm to try them out?
Click to expand...
Click to collapse
You can test other adapters, someone on this forum said that he used an 5v usb supply, but for a 'stable use' you need a big one... regards the amps...
I think a power supply between 7v to 5v works fine, probably no damages at all.

Sus_i said:
Have you tried to pull all plugs, reconnect only the power supply... what does the LED?
There is an ifixit guide on how to disassemble the fireTV. In case you open the box, measure the voltage IN inside the fireTV at power on. You can measure VDD 3.3v and VDDQ 1.8v too, next to the emmc, see the picture here.
That shouldn'd harm anything. In case of a failure, the fireTv should blink yellow.
You can test other adapters, someone on this forum said that he used an 5v usb supply, but for a 'stable use' you need a big one... regards the amps...
I think a power supply between 7v to 5v works fine, probably no damages at all.
Click to expand...
Click to collapse
OK, will try to open up the FireTV.
No light/LED when plugging only the power adapter to the FIreTV, already tried different power outlets throughout the house
Come to the worst, will this https://forum.xda-developers.com/showpost.php?p=66961740&postcount=676 help?
Thanks again.

Matt_7 said:
Come to the worst, will this https://forum.xda-developers.com/showpost.php?p=66961740&postcount=676 help?
Click to expand...
Click to collapse
Worst case is a broken fireTV.
Don't follow this guide, you lose your unlock... apart from that, the download link from the guide is dead

Sus_i said:
Worst case is a broken fireTV.
Don't follow this guide, you lose your unlock... apart from that, the download link from the guide is dead
Click to expand...
Click to collapse
OK, will forget about that!
Once I got the FireTV opened, will take some pixs and report back!

OK, here are the pixs.
Now that I look at the Multimeter, I'm not sure I'm using it correctly. Bought this few years ago (just in case I need to test my car's battery).
AT the bottom of the multimeter, there are 3 holes, one red on each side and black hole in the center, which two am I supposed to use?
I tested the power adapter again with multimeter using the center black and red on the right, and I'm reading 4.2V?

Sus_i said:
Worst case is a broken fireTV.
Click to expand...
Click to collapse
Would it be possible just by looking at the board if its kaput?