Related
And now I'm boot looping won't go past n color startup animation wth
Sent from my Cyanogen Mod EVO using Tapatalk
I had that problem on my NC when it was rooted. Luckily I had another problem that let me get out by the 8 times reset manual method. Mine would occasionally update itself back to version 1.0.0. When it did that I managed to reset it & now a new NC is on its way to replace this one.
This probably won't help solve the issue but at least it lets you know you're not alone.
Mine boot looped and I did the full 8X reboot thing and then the 3 button data reset. All of that puts you back to "out-of-the-box" stock. You can then redo the autonooter rooting procedure.
Can't get out
I am stuck in a boot loop and cant get out.
First it was stuck on the droid boot animation from the auto config. After I put the autonooter card back in it started looping the rooted boot animation.
Did the 3 button thing and that forced an update but went back to bootlooping the rooted animation.
Then did the 8X reboots manually and that also forced the down arrow update, but then it still bootloops.
I tried getting in from PuTTy (as admin) but it never connects. Do I just use port 22? (to 192.168.2.2 with Data and username as root?)
adb doesn't work... going to bed now and will try again tomorrow after work.
What i had to do to resolve my issue was that was to do the 8x reset to trigger the factory reset of the OS and then do the 3 button reset of the user data. In my case it was a self tweaked issue with an app permisson. If I remember right the key combo is Power+VolUp+"n" key. Try this and let us know.
Sent from my NookColor using XDA App
Bigger Issues.... First Brick?
Nate731 said:
What i had to do to resolve my issue was that was to do the 8x reset to trigger the factory reset of the OS and then do the 3 button reset of the user data. In my case it was a self tweaked issue with an app permisson. If I remember right the key combo is Power+VolUp+"n" key. Try this and let us know.
Sent from my NookColor using XDA App
Click to expand...
Click to collapse
So ... I left my Nook in what I thought was an "OFF" state last night, only to bring it to work and find it says "Battery too low to Power on" "Please wait 15 minutes and try again"
I think... no worries... plug it in and let 'er sit for an hour.... an hour passes and I'm still getting the same screen.
Is this better or worse? let me see...
1) if it stays like this, I can return/exchange it at B&N and they won't be able to verify that it was rooted due to non-bootiness
2) If it eventually boots, I will have to try to get it out of bootloop.
3) If it comes to life and I can't get it out of bootloop, I will drain the battery again and go back to #1.
Any thoughts besides this current train?
sort of working?
OK....
so after charging on USB port (all I have at work today as I forgot the base to the charger), it will bootloop again... yay!
problem is... the bootloops take too much juice and won't allow me to fail 8 reboots. I can't even charge it up enough since I'm on USB charging and it keeps trying to turn itself on.
2 Options i see:
1) Go home and charge it on the wall and see if that helps
2) Discharge it to death and return within my 30 days (X-mas gift)
Doubt this will work, but have you tried putting in an autonooter sdcard and then plug it into the usb? If it tries to boot maybe it will boot from that sdcard?
Boot from the Froyo SD card, then fix /rom/devconf/BootCnt from ADB.
Cal you never mentioned if you cleared the user data... Did you?
Nate731 said:
Cal you never mentioned if you cleared the user data... Did you?
Click to expand...
Click to collapse
If you mean the 3 button reset? Yes.
If not... I did not because I'm not aware of it. (couldn't through the UI of course)
cal3thousand said:
If you mean the 3 button reset? Yes.
If not... I did not because I'm not aware of it. (couldn't through the UI of course)
Click to expand...
Click to collapse
Try Geezer's tip but do this:
Do three button reset WITH the autonooter card in there.
Got it working
Finally got it working after creating a Nookie Froyo card and booting off of that.
Then I reinstalled ADB on my work computer and reset the BootCnt file to 8...
that successfully restored /system and then the 3 finger trick actually gave an option to wipe.
Now to start over.
New Question: How likely is this hardware related and should I be looking to replace it before my 30 days is up>?
I ran into the same problem, trying the same solution - any luck the second time?
JasonBunting said:
I ran into the same problem, trying the same solution - any luck the second time?
Click to expand...
Click to collapse
My Nook has been great since the fix. But I also needed to use a program to turn off Wifi when I turn the display off.
I did it all from my Nookie...
confused?!
I was wondering how you fixed this..i have read everywhere, but nothing...im stuck in the nook co screen. This happened right after i plugged my nook to charge after my battery was drained...thnks
Hello guys,
I have recently bought my first android phone, the Samsung Galaxy Nexus.
On the second day I decided to root it since I needed market enabler, as my local market (UAE) has literally no apps.
I rooted using the SDK tools, fastboot and superboot. Everything worked fine for 1 day.
However, the next day, the phone just died on me, and would not boot at all. It kept getting stuck on the "Google" image at startup. At that point, I could still go into the bootloader. I tried locking/unlocking the bootloader again, since that basically wipes all the date on the phone, but it still refused to load, it would get stuck at the startup animation.
After a few more attempts, it kept spam restarting every time I tried to switch it on.
At that point, I was downloading the default OEM ROM so I could reflash that onto the phone. However, I thought I could try using the superboot bat file again, and maybe that would fix the problem. BIG MISTAKE.
As soon as I ran that file, the phone COMPLETELY died. It will not start at ALL, it will not go into Bootloader, not go into Recovery mode, and not even go into Download (odin) mode.
The ONLY possible response you can get from it, is when you plug it into the PC. My PC seems to play that "detection" sound, same sound as when you plug in a USB, but it would just play that sound over and over again, as if im plugging/unplugging a device really quickly. It seems like the phone is continously restarting itself. When I connect the phone to the PC and that disconnect/reconnect sound comes up, I went into my device manager and I could see the following:
An item under "Other Devices" called "OMAP4440" keeps appearing and dissapearing all the time, with the little "!" mark next to it indicating that there is a driver error. The drivers for this phone are fully installed on this same PC, and it use to work fine before it went dead.
Now the problem is since I cant get into any mode whatsoever, its a bit hard to diagnose the phone. I know there is a "recovery" slot at the bottom of the phone that is accessible with a small pin, but I dont for the life of me know how that works or what it does. Does anybody know how to work that or what it actually does?
Any help would be appreciated! Thanks fellas.
wrong forum mate...if you go to this link, they might be able to help you there
http://forum.xda-developers.com/forumdisplay.php?f=1431
hi, i have same problam with my galaxy nexus. i just want to ask how to fix my phone, thanks
IamPoison said:
Hello guys,
I have recently bought my first android phone, the Samsung Galaxy Nexus.
On the second day I decided to root it since I needed market enabler, as my local market (UAE) has literally no apps.
I rooted using the SDK tools, fastboot and superboot. Everything worked fine for 1 day.
However, the next day, the phone just died on me, and would not boot at all. It kept getting stuck on the "Google" image at startup. At that point, I could still go into the bootloader. I tried locking/unlocking the bootloader again, since that basically wipes all the date on the phone, but it still refused to load, it would get stuck at the startup animation.
After a few more attempts, it kept spam restarting every time I tried to switch it on.
At that point, I was downloading the default OEM ROM so I could reflash that onto the phone. However, I thought I could try using the superboot bat file again, and maybe that would fix the problem. BIG MISTAKE.
As soon as I ran that file, the phone COMPLETELY died. It will not start at ALL, it will not go into Bootloader, not go into Recovery mode, and not even go into Download (odin) mode.
The ONLY possible response you can get from it, is when you plug it into the PC. My PC seems to play that "detection" sound, same sound as when you plug in a USB, but it would just play that sound over and over again, as if im plugging/unplugging a device really quickly. It seems like the phone is continously restarting itself. When I connect the phone to the PC and that disconnect/reconnect sound comes up, I went into my device manager and I could see the following:
An item under "Other Devices" called "OMAP4440" keeps appearing and dissapearing all the time, with the little "!" mark next to it indicating that there is a driver error. The drivers for this phone are fully installed on this same PC, and it use to work fine before it went dead.
Now the problem is since I cant get into any mode whatsoever, its a bit hard to diagnose the phone. I know there is a "recovery" slot at the bottom of the phone that is accessible with a small pin, but I dont for the life of me know how that works or what it does. Does anybody know how to work that or what it actually does?
Any help would be appreciated! Thanks fellas.
Click to expand...
Click to collapse
onlinemoon said:
hi, i have same problam with my galaxy nexus. i just want to ask how to fix my phone, thanks
Click to expand...
Click to collapse
i have same problem. can you fix it now?
---------- Post added at 08:21 PM ---------- Previous post was at 08:20 PM ----------
IamPoison said:
Hello guys,
I have recently bought my first android phone, the Samsung Galaxy Nexus.
On the second day I decided to root it since I needed market enabler, as my local market (UAE) has literally no apps.
I rooted using the SDK tools, fastboot and superboot. Everything worked fine for 1 day.
However, the next day, the phone just died on me, and would not boot at all. It kept getting stuck on the "Google" image at startup. At that point, I could still go into the bootloader. I tried locking/unlocking the bootloader again, since that basically wipes all the date on the phone, but it still refused to load, it would get stuck at the startup animation.
After a few more attempts, it kept spam restarting every time I tried to switch it on.
At that point, I was downloading the default OEM ROM so I could reflash that onto the phone. However, I thought I could try using the superboot bat file again, and maybe that would fix the problem. BIG MISTAKE.
As soon as I ran that file, the phone COMPLETELY died. It will not start at ALL, it will not go into Bootloader, not go into Recovery mode, and not even go into Download (odin) mode.
The ONLY possible response you can get from it, is when you plug it into the PC. My PC seems to play that "detection" sound, same sound as when you plug in a USB, but it would just play that sound over and over again, as if im plugging/unplugging a device really quickly. It seems like the phone is continously restarting itself. When I connect the phone to the PC and that disconnect/reconnect sound comes up, I went into my device manager and I could see the following:
An item under "Other Devices" called "OMAP4440" keeps appearing and dissapearing all the time, with the little "!" mark next to it indicating that there is a driver error. The drivers for this phone are fully installed on this same PC, and it use to work fine before it went dead.
Now the problem is since I cant get into any mode whatsoever, its a bit hard to diagnose the phone. I know there is a "recovery" slot at the bottom of the phone that is accessible with a small pin, but I dont for the life of me know how that works or what it does. Does anybody know how to work that or what it actually does?
Any help would be appreciated! Thanks fellas.
Click to expand...
Click to collapse
i have same problem. can you fix it now?
adesos said:
i have same problem. can you fix it now?
---------- Post added at 08:21 PM ---------- Previous post was at 08:20 PM ----------
i have same problem. can you fix it now?
Click to expand...
Click to collapse
Well done for not reading the thread and realising you were asking the question in the *wrong forum*!
Hey man I have the same problem and my phone is also from UAE. Did you figure it out??
Sorry posting here.
WTF are these guys for real? This thread should have been deleted the day it was started!!
This is posted in wrong section.
**Reported**
Thread Closed
This forum is for the galaxy note, please post in the correct forum
So after reading about a dozen or so threads, all of the FAQ's, asking in the wrong forum, and 3 other sites, I have come to a roadblock. Here is my situation in its entirety...
Got a brand new Kindle Fire HD 7" for Christmas, obviously couldn't leave it alone. I have rooted about a dozen models of Android phone, and jailbroken multiple iPhones, so I know the trials and tribulations of this process...
So I attempt to root my KF using the Bin4ry and Qemu method. I have a AWFUL time getting the drivers to properly recognise my KF. I end up finding another person's issue such as mine, and go through the LONG way of downloading the adt bundle, and installing all of the google software and drivers that way. EUREKA! Drivers work, KF recognised by my machine. First shot with Bin4ry after the driver mishap, works fine. Takes 2 attempts with the second step with the Qemu method, but again, I get there. after the first time booting up, I factory reset the Kindle. Still have SU on the apps list. Cool! Now what?
I boot the machine and shut it down about 5 times just to check stability, and hard shutdown (power button for 20+ seconds) twice. Every time all is ok, and SU is still there.
Now time to play. I again go through reading a couple threads on changing the launcher, and decide to go with the Nova launcher for now. I download it from the Play store, yet can't seem to find it on my KF. I for some god awful reason decide "well I saw it a couple threads ago, that someone had an issue with the launcher change the name of launcher.apk to launcher.apk1 and then it worked" so obviously I go and do that. Enter the final time I would boot my KF.
Upon reboot, I get the stock/standard "kindle fire" screen with no animation at full brightness. It then goes black for a split second, and comes back with the "kindle fire" screen, but now with the animated "shiny streak" that goes across the logo. I left it there multiple times for a half hour +, no change.
So I don't freak out yet, cause it turned on, and I find it can't be all that bad. So I check for it in device manager...nothing. Check My Computer just to see if its recognised for memory storage...nothing. I run the Bin4ry script again, just to see...nothing. Run Qemu just to be thorough...nothing. Restart my computer, repeat ALL above steps...nothing. Still never see's the KF, also never makes a tone at me when I plug the kindle into the cable. Change USB ports, repeat all, nothing. Back all of the drivers out, and reinstall all of them. Restart. Nothing. Download kindle unbrick utility, that still doesn't see the KF. No adb shell commands ever let me even see that it is seen somehow my my computer.
So now I am stuck. It still seems to me to be a driver issue, but I seriously cannot see how that is possible. I guess while waiting for a response from one of the guru's here, I will repeat my process of backing all of the previous drivers out and reinstalling them. There is NO other software on the kindle except for the Nova launcher and whatever the Bin4ry and Qemu methods install on it.
Sorry for the long post, but I figured it would be better than leaving you guys to ask more questions, though I'm sure you will anyways. My KF is running 7.2.3 before all of this happened...
Thanks for any help, sorry to be that guy!
Jordan
skeeter7424 said:
So after reading about a dozen or so threads, all of the FAQ's, asking in the wrong forum, and 3 other sites, I have come to a roadblock. Here is my situation in its entirety...
Thanks for any help, sorry to be that guy!
Jordan
Click to expand...
Click to collapse
Well the good news is you don't have a driver issue, Its seems you are just stuck in a boot loop and at that point in the boot process adb is not recognized. Check out this thread on how to restore it: http://forum.xda-developers.com/showthread.php?t=1951254
By the way you will need a factory cable. There is a link in the above thread for where to purchase(someone told me they've gotten them on amzon as well). Don't worry they are cheap, about $10-15.
So I see it listed all over the place, but I take it the factory cable is not the one that was supplied in the box?
edit: now i have found what everyone is talking about and have found the writeup on the cable. I am currently sitting at my desk making myself this cable now...we'll see how this goes!
So I got the factory cable made correctly, plugged it in, boom, computer recognizes it. I reload software from the kindle unbrick utility. Now it goes into straight bootloop, KF home screen, blank, KF home screen, blank. Tried with both the factory cable and the stock cable. No changes. Am letting it completely die today to attempt to plug into computer and let it recognize. Should I do this part with the stock cable or the factory modded cable?
skeeter7424 said:
I reload software from the kindle unbrick utility.
Click to expand...
Click to collapse
What are you referring as "the kindle unbrick utility"? Did you try to use KFHD System.img Restore Tool ?
Yes I am. The issue is that the KF boots to the "Kindle" opening screen, then switches to a screen that says "Fastboot" with "amazon kindle" below it. I then get a tone from my computer that is recognized, then about a quarter second later, the KF blacks out, and I get a tone from my comp that says disconnect. It then tones back and forth between connected and not. This happens with both the factory cable and the stock cable.
skeeter7424 said:
Yes I am. The issue is that the KF boots to the "Kindle" opening screen, then switches to a screen that says "Fastboot" with "amazon kindle" below it. I then get a tone from my computer that is recognized, then about a quarter second later, the KF blacks out, and I get a tone from my comp that says disconnect. It then tones back and forth between connected and not. This happens with both the factory cable and the stock cable.
Click to expand...
Click to collapse
What happens when you just turn it on with no cable hooked up. Also did you use the tool that corresponds with the system version your device was running before the problem tat started it. If you used the wrong backup then you will need to use the method to downgrade at the bottom of the restore tool post
Sent from my KFJWI using xda premium
onemeila said:
What happens when you just turn it on with no cable hooked up. Also did you use the tool that corresponds with the system version your device was running before the problem tat started it. If you used the wrong backup then you will need to use the method to downgrade at the bottom of the restore tool post
Sent from my KFJWI using xda premium
Click to expand...
Click to collapse
The same thing happens when trying to boot with no cable. Kindle fire screen, quick to Fastboot/Kindle Fire screen, black.
Also, now with a little more research, I should explain how the computer actually tones when this happens. Right when the KF boots, I get an "unplugged" tone, then right after that I get 3 tones, which after looking at different hardware forums, means that the device is not recognized. It will then go back and forth between the unplugged tone, and the 3 beeps, now with the KF being blacked out. If I then long hold the power button it gives me one "final" unplugged tone.
I used the backup for 7.2.3 which was what was on my KF before I started. Again, that tool will not recognize my KF. All I get with the KFHD_SRT tool is "waiting for device"
Thanks again guys for the help with this!
skeeter7424 said:
The same thing happens when trying to boot with no cable. Kindle fire screen, quick to Fastboot/Kindle Fire screen, black.
Also, now with a little more research, I should explain how the computer actually tones when this happens. Right when the KF boots, I get an "unplugged" tone, then right after that I get 3 tones, which after looking at different hardware forums, means that the device is not recognized. It will then go back and forth between the unplugged tone, and the 3 beeps, now with the KF being blacked out. If I then long hold the power button it gives me one "final" unplugged tone.
I used the backup for 7.2.3 which was what was on my KF before I started. Again, that tool will not recognize my KF. All I get with the KFHD_SRT tool is "waiting for device"
Thanks again guys for the help with this!
Click to expand...
Click to collapse
You made your own factory cable right? Did you use a resistor and if so what size? Sounds like you could have shorted something out, cause I've never heard of this problem but I know you can do a lot of damage to both device and pc if a factory cable is not made correctly with at least a 1k resistor(if I remember correctly).
Do you get the fastboot screen. And also I did not use resistor when I made my cable and it works just fine. Only thing weird Is That once I have fastboot screen I have to unplug my fastboot cable and use original cable in order to flash anything but I have had no other issues. Hope this helps.
Sent from my KFTT using XDA Premium HD app
Need a bandaid?
Try this.
I currently have a bricked kindle 7 hd and wanted to see if anyone could help me out with their expertise. A week ago I accidentally bricked my kindle and purchased the factory cable on ebay to try to fix.
At this point when I connect the cable, screen stays black.
If i press kindle power button, Kindle logo will briefly appear, followed by fastboot logo for split second and then goes black again.
There are so many posts on the website on how to fix a bricked kindle, but I'm unsure which one is the right solution in this case.
Also, my driver on the Device Manager connects and disconnects continuously. And for some reason, I'm showing OMAP4440 when I connect my kindle, which I assume is not correct.
What is my next step, or what do I download?
Please, if someone can help, I'd be very grateful. I've been without my kindle for over a week. Thank you.
That kindle is hard bricked, there's a slight chance of fixing if it is flashing fastboot mode for a few seconds, but I give it a 10% chance of fixing. We can't fix omap4440 bricks because while we have the means to interface with that device, we need a signed xloader for the kindle to let us flash the other partitions. We can't get the signed xloader (believe its called xloader, might be called something else) unless someone at amazon or TI were nice enough to leak it and probably get fired in the process.
On another note is that android adb composite device staying there the entire time the kindle is plugged in? If it does then you may be able to fix the kindle, I haven't heard of omap4440 and the adb composite being there at the same before. I would guess that adb is the fastboot interface but usually it says Tate when drivers aren't installed and in this case it doesn't but still has an exclamation. I'm curious....
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Well, @stunts513, it also shows that a kindle fire is plugged in with adb enabled. So he might not be 100% out of hope.
It sounds like the bootloader does indeed work, but there is a small problem. I am not sure what that problem is, but if the fastboot logo even shows at all, there is a small chance you could get it up and running again. Download the kfhd7 bootloader provided by @Hashcode and see if you can "fastboot flash" it before the screen goes black. Type in the command and the second you see the orange kindle fire logo, hit enter. Keep in mind that it might work. I am not responsible if it ruins your device further. It shouldn't, though.
Sent from my Amazon Kindle Fire HD using xda app-developers app
Well, I wouldn't say 100% out of hope...
http://forum.xda-developers.com/showthread.php?t=2391047
Or you could try using "fastboot boot" to boot the bootloader. This takes barely less time so if the fastboot flash fails, try this.
Sent from my Amazon Kindle Fire HD using xda app-developers app
Same exact problem, did anyone find a fix?
lizvx said:
I currently have a bricked kindle 7 hd and wanted to see if anyone could help me out with their expertise. A week ago I accidentally bricked my kindle and purchased the factory cable on ebay to try to fix.
At this point when I connect the cable, screen stays black.
If i press kindle power button, Kindle logo will briefly appear, followed by fastboot logo for split second and then goes black again.
There are so many posts on the website on how to fix a bricked kindle, but I'm unsure which one is the right solution in this case.
Also, my driver on the Device Manager connects and disconnects continuously. And for some reason, I'm showing OMAP4440 when I connect my kindle, which I assume is not correct.
What is my next step, or what do I download?
Please, if someone can help, I'd be very grateful. I've been without my kindle for over a week. Thank you.
Click to expand...
Click to collapse
I have the same problem Word for Word just a few extra details: I did have TW RP installed and I had just recently installed Kinology which was working but I went Back into TW RP again to try to Flash CM and didnt have all the files I needed But went ahead and removed my OS somehow leaving me stuck in TWRP Trying to figure out away to get the files over to it. At some point it ended up in Fastboot mode and I fell asleep so it was running with just the Fastboot logo for several hours and I woke up and saw that it was turned back off at which point I attempted to reboot back into recovery (TWRP) but discovered it would only show Kindle Fire for <1 second then Fastboot <1.5 seconds and back to a black screen. If it's connected to the computer it will make a sound as if the device was recognized but then a strange sound I have not heard I guess meaning the device was not installed correctly; Then this is repeated not stop until a reset on the device is done just the correct amount of time where it doesn't turn back on but the sound stops on the computer and the KFHD screen stays off. I'm new to Android and rooting, etc. but in the last 45+days since I got this KFHD7 used, I have used XDA countless times for a variety of reasons and I intend to be a contributing member from this day forward, even if only in a very limited capacity. I have grown to respect the incredible work of Hashcode among others on XDA and being a noob to Android customization as well as these forums, I have been reflecting on my years being tied down by iOS devices; can't help but feel like I wasted so much time and money, trying to so the things that Android was already capable of doing. I think I may need to f-around and jailbreak my iPhone 4S pretty soon when I'm able to scoop up a real nice Android phone and leave ios behind for good like I should have done when I switched from the very first iPhone on Cingular Wireless!! But yeah sorry, um... Little long-winded on my first ever reply on XDA. I'll try not to make a habit of that. I was just wondering if anyone made any progress on this issue, and thought my 2¢ could potentially be helpful, disregarding all the ios b.s. My Kindle Fire is Hard Bricked and I'm keeping my fingers crossed that I can squeeze something out of that "10% chance for recovery." Thanks a billi.
Steveohookem said:
I have the same problem Word for Word just a few extra details: I did have TW RP installed and I had just recently installed Kinology which was working but I went Back into TW RP again to try to Flash CM and didnt have all the files I needed But went ahead and removed my OS somehow leaving me stuck in TWRP Trying to figure out away to get the files over to it. At some point it ended up in Fastboot mode and I fell asleep so it was running with just the Fastboot logo for several hours and I woke up and saw that it was turned back off at which point I attempted to reboot back into recovery (TWRP) but discovered it would only show Kindle Fire for <1 second then Fastboot <1.5 seconds and back to a black screen. If it's connected to the computer it will make a sound as if the device was recognized but then a strange sound I have not heard I guess meaning the device was not installed correctly; Then this is repeated not stop until a reset on the device is done just the correct amount of time where it doesn't turn back on but the sound stops on the computer and the KFHD screen stays off. I'm new to Android and rooting, etc. but in the last 45+days since I got this KFHD7 used, I have used XDA countless times for a variety of reasons and I intend to be a contributing member from this day forward, even if only in a very limited capacity. I have grown to respect the incredible work of Hashcode among others on XDA and being a noob to Android customization as well as these forums, I have been reflecting on my years being tied down by iOS devices; can't help but feel like I wasted so much time and money, trying to so the things that Android was already capable of doing. I think I may need to f-around and jailbreak my iPhone 4S pretty soon when I'm able to scoop up a real nice Android phone and leave ios behind for good like I should have done when I switched from the very first iPhone on Cingular Wireless!! But yeah sorry, um... Little long-winded on my first ever reply on XDA. I'll try not to make a habit of that. I was just wondering if anyone made any progress on this issue, and thought my 2¢ could potentially be helpful, disregarding all the ios b.s. My Kindle Fire is Hard Bricked and I'm keeping my fingers crossed that I can squeeze something out of that "10% chance for recovery." Thanks a billi.
Click to expand...
Click to collapse
When you remove your OS off any device without one to install, its like giving someone a car with no steering wheel. You now need to push a ROM thru TWRP using ADB. Try using the solution that helped me, which I provided to another user in this thread:
http://forum.xda-developers.com/showthread.php?p=45188927#post45188927
Sent from my Amazon Kindle Fire HD using xda app-developers app
---------- Post added at 06:10 AM ---------- Previous post was at 05:56 AM ----------
lizvx said:
I currently have a bricked kindle 7 hd and wanted to see if anyone could help me out with their expertise. A week ago I accidentally bricked my kindle and purchased the factory cable on ebay to try to fix.
At this point when I connect the cable, screen stays black.
If i press kindle power button, Kindle logo will briefly appear, followed by fastboot logo for split second and then goes black again.
There are so many posts on the website on how to fix a bricked kindle, but I'm unsure which one is the right solution in this case.
Also, my driver on the Device Manager connects and disconnects continuously. And for some reason, I'm showing OMAP4440 when I connect my kindle, which I assume is not correct.
What is my next step, or what do I download?
Please, if someone can help, I'd be very grateful. I've been without my kindle for over a week. Thank you.
Click to expand...
Click to collapse
Creepy never seen that happen on either of my two KFHD7s. Have you tried uninstalling that driver completely? Or uninstalling those drivers thru "Device Manager" AND all others installed for /example the ones provided by Hashcode, then reinstalling them WITH the device still connected? Many times I've realized that these Kindle Fires love to have drivers juggled around. The fastboot cable I made at home using a Samsung USB does FBmode instantly. Try holding the power button for about 20 seconds while unplugged, make sure when you let go it doesn't power back on. If alls well, have the fastboot cable plugged in already to your computer, then attach it to the KF. See if that helps. If not, then believe it or not it might be a hardware failure if the screen goes black as you mentioned...
Sent from my Amazon Kindle Fire HD using xda app-developers app
r3pwn said:
Well, @stunts513, it also shows that a kindle fire is plugged in with adb enabled. So he might not be 100% out of hope.
It sounds like the bootloader does indeed work, but there is a small problem. I am not sure what that problem is, but if the fastboot logo even shows at all, there is a small chance you could get it up and running again. Download the kfhd7 bootloader provided by @Hashcode and see if you can "fastboot flash" it before the screen goes black. Type in the command and the second you see the orange kindle fire logo, hit enter. Keep in mind that it might work. I am not responsible if it ruins your device further. It shouldn't, though.
Sent from my Amazon Kindle Fire HD using xda app-developers app
Click to expand...
Click to collapse
My bad the picture must have not loaded up last time, or I wouldn't have said that much. But more than likely he has a hard brick. Slim chance of fixing it though.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
lizvx said:
I currently have a bricked kindle 7 hd and wanted to see if anyone could help me out with their expertise. A week ago I accidentally bricked my kindle and purchased the factory cable on ebay to try to fix.
At this point when I connect the cable, screen stays black.
If i press kindle power button, Kindle logo will briefly appear, followed by fastboot logo for split second and then goes black again.
There are so many posts on the website on how to fix a bricked kindle, but I'm unsure which one is the right solution in this case.
Also, my driver on the Device Manager connects and disconnects continuously. And for some reason, I'm showing OMAP4440 when I connect my kindle, which I assume is not correct.
What is my next step, or what do I download?
Please, if someone can help, I'd be very grateful. I've been without my kindle for over a week. Thank you.
Click to expand...
Click to collapse
hi guys from Italy, i have the same very problem...now is the end of Settember....any good news about?????????
Not very much, unless you wanna try hooking up your emmc to a USB card reader like kurohyou did and trying to flash the stock partitions from Linux, no there really isn't any new news. That's basically the only way we have to recover from a hard brick, and it still isntna perfected process, he got his kf2 to a soft brick state after un-hardbricking it, but he couldn't un-softbrick it yet, so he is currently working on that part last I heard.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Hello, I have the exact same problem with my KFHD7 and I was reading this thread with the hope that someone would have find a solution.
Is there a solution out there for this problem yet?
Juls69 said:
Hello, I have the exact same problem with my KFHD7 and I was reading this thread with the hope that someone would have find a solution.
Is there a solution out there for this problem yet?
Click to expand...
Click to collapse
i think someone finished mapping the rest of the points out on the motherboard but i'm not positive, I'll have to find the thread but the only fix is to solder the kindles motherboard contact point for the emmc to a sdcard reader and hook it up to a pc running linux and flash the bootloader partition with the dd command. Keep in mind I'm referring to the hd 7 2012 model, i don't believe anyone has mapped the points for the 2013 model yet.
edit: foudn the thread: http://forum.xda-developers.com/showthread.php?t=2674737&page=3
use the tutorial for the kf2 or kfhd8.9" but use the contact points mentioned there, might take some researching to know what each of those corresponds to on the sdcard reader. Not everybody is up to soldering on their kindle to fix a hard brick.
Hello,
i found these Thread, because i have the same problems.During the boot the kindle shows the kindle logo then the fastboot logo and the screen goes black. But if use a fastboot-code at the right time, the kindle stay in the fastboot-mode. So i tried to flash the Bootloader and so from Hashwell. The output of fastboot says everythings ok, no errors, but my kindle doesn't leave the bootloop. What i done wrong? I read about the Kindle Fire First Aide-Kit, but i cant find an downloadlink, that still work.
Maybe someone of you can help with this problem.
Hello,
I had a KFHD 7" 2012 a while back. I reverted it from CM11 to Fire OS. That red screen came up (was about 3 years ago so don't remember exactly what it said).
I got a fastboot cable and it booted to fastboot, and I reflashed the bootloader.
One problem: the wrong bootloader. I flashed the bootloader for the original Kindle Fire.
Hard Bricked. No response from ANYTHING. Nothing. I can open the back cover, but don't know what to do when inside. Any USB Boot thing I need to do?
Not even plugging it to my PC comes up with ANYTHING in device manager.
It was my sister's tablet, she got a Galaxy Tab Pro and I still have my Tab S, but I'm kinda curious if theres still hope for it. Who knows? Maybe I'll donate it if it gets fixed.
Thanks in advance
-Ryan
Wow. This seems like a HUGE problem. If the Kindle doesn't respond, then this is really bad.
Are you sure the Kindle Fire isn't responding? Have you tried forcefully turning it off (press power button for up to 20 seconds), and then plugging it into the fastboot cable? If it can get to the Fastboot logo then I think you can unbrick it.
I just need to remember the link to the Ultimate Unbrick Tool. If the device isn't showing up in the device manager (starts with tate) in any of the dropdown menus, there is most likely NO fix for this.
DarknesGaming said:
Wow. This seems like a HUGE problem. If the Kindle doesn't respond, then this is really bad.
Are you sure the Kindle Fire isn't responding? Have you tried forcefully turning it off (press power button for up to 20 seconds), and then plugging it into the fastboot cable? If it can get to the Fastboot logo then I think you can unbrick it.
I just need to remember the link to the Ultimate Unbrick Tool. If the device isn't showing up in the device manager (starts with tate) in any of the dropdown menus, there is most likely NO fix for this.
Click to expand...
Click to collapse
Ok I've shorted the USB_BOOT pin and it's coming up in Device Manager as "OMAP44xx USB DEVICE."
No display on the screen no matter what I do.
I've tried compiling USBBoot from source and running it on a Linux machine, and it recognizes the device, and gets stuck at "Unknown Error: -7"
There is not much documentation on this tool so I wonder if anyone knows.
(Actually, if anyone knows, it's probably @Hashcode, but I really doubt I can get a hold of him)
Nandr0idC0nsumer said:
Ok I've shorted the USB_BOOT pin and it's coming up in Device Manager as "OMAP44xx USB DEVICE."
No display on the screen no matter what I do.
I've tried compiling USBBoot from source and running it on a Linux machine, and it recognizes the device, and gets stuck at "Unknown Error: -7"
There is not much documentation on this tool so I wonder if anyone knows.
(Actually, if anyone knows, it's probably @Hashcode, but I really doubt I can get a hold of him)
Click to expand...
Click to collapse
I'm going to take a wild guess and say that a udev rule might need to be added into Linux. I'm not sure though, as I don't think this has been done before with a kindle in this state. I'm going to do research on it before replying any further.
Sent from my Amazon Jem using XDA Labs
monster1612 said:
I'm going to take a wild guess and say that a udev rule might need to be added into Linux. I'm not sure though, as I don't think this has been done before with a kindle in this state. I'm going to do research on it before replying any further.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Thank you for the reply - you actually may be right. I'll try that when I get home but I haven't a clue how to udev so... yeah some research will be done on my end too.
Thanks!