Kindle fire hd 8 hard brick, I think that's it. - Fire HD 8 and HD 10 Q&A, Help & Troubleshooting

Hi,
I used adb sideload to upgrade my firmware so I could root my Kindle fire HD 8 and stuff, but since I didn't know which version I was on to begin with, I guess I flashed the wrong version. Stayed dead after pressing reboot in recovery. Well, that was stupid, but I never had a brick this bad on any of my numerous android phones.
So, to summarize:
Doesn't turn on.
No lights or anything when charging (Does it even have a notification light?)
Doesn't get recognised on 3 different pcs, not by device manager on windows or dmesg on linux.
Not only doesn't get recognised, but just nothing in device manager or anywhere, absolutely nothing.
Can't get into recovery.
Got a fastboot cable, connected it, no reaction what so ever.
So all in all, that's it isn't it? I destroyed it by installing the wrong firmware? I have done that many times on different phones but was always able to get into recovery or fastboot.
If you guys have any Ideas, I appreciate it.
Thanks in advance, Fritz

derfritz said:
Hi,
I used adb sideload to upgrade my firmware so I could root my Kindle fire HD 8 and stuff, but since I didn't know which version I was on to begin with, I guess I flashed the wrong version. Stayed dead after pressing reboot in recovery. Well, that was stupid, but I never had a brick this bad on any of my numerous android phones.
So, to summarize:
Doesn't turn on.
No lights or anything when charging (Does it even have a notification light?)
Doesn't get recognised on 3 different pcs, not by device manager on windows or dmesg on linux.
Not only doesn't get recognised, but just nothing in device manager or anywhere, absolutely nothing.
Can't get into recovery.
Got a fastboot cable, connected it, no reaction what so ever.
So all in all, that's it isn't it? I destroyed it by installing the wrong firmware? I have done that many times on different phones but was always able to get into recovery or fastboot.
If you guys have any Ideas, I appreciate it.
Thanks in advance, Fritz
Click to expand...
Click to collapse
I'm very sorry for you. But, I'll have to say, that's it.
Amazon has a very strange way of preventing downgrade, they have an exclusive process looking for a version mismatch, and when it detects a version mismatch, it terminates the installation in a special ... way. Effectively bricking the device by failing the signatures and files of every partition, purposefully. I confirmed this myself by looking at the abandoned logs a Fire device produced before it shutted down forever.
If that's the 7th Gen model, please contact an Amazon representative. They should offer you a replacement for your device, but your data is gone.
Good luck!

Supersonic27543 said:
I'm very sorry for you. But, I'll have to say, that's it.
Amazon has a very strange way of preventing downgrade, they have an exclusive process looking for a version mismatch, and when it detects a version mismatch, it terminates the installation in a special ... way. Effectively bricking the device by failing the signatures and files of every partition, purposefully. I confirmed this myself by looking at the abandoned logs a Fire device produced before it shutted down forever.
If that's the 7th Gen model, please contact an Amazon representative. They should offer you a replacement for your device, but your data is gone.
Good luck!
Click to expand...
Click to collapse
Thankfully I had no important data on it. I had a 6th gen so that's no option either. Well, thank you for your help, I think I'll stay away from amazon devices for a while...

Related

[Q] New kind of unfixable Super Brick?

My kindle is bricked and I have tried everything.
This is what i did: I rooted it, installed CM7, it worked fine. I then wanted to go back to the stock rom (due to countless FCs and freezing in CM) so i flashed the stock rom through TWRP. When i re-booted, the TWRP recovery screen no longer shows and it has the stock kindle fire logo on screen.
It does not show up in device manager in windows, I have re-installed the usb drivers multiple times. Any recovery methods using ADB simply result in "waiting for device" forever.
I have tried:
hard reset
fastboot commands
booting to linux live cd with firekit
kindle fire unbrick utility
None of these work because it does connect via usb
Anyone else have this problem>?
EDIT: Im fed up, ive tried every method on XDA and youtube, nothing works. I convinced amazon to replace it. Thanks anyways.
Hi Try This http://forum.xda-developers.com/showthread.php?t=1398728
lovejoy777 said:
Hi Try This http://forum.xda-developers.com/showthread.php?t=1398728
Click to expand...
Click to collapse
If you notice, that uses ADB shell. All of these commands result in "waiting for device" as it it not detected as a USB device
Sorry forgot to attach
Ok dont worry ive gotten my self into the same issue and lots of other ones lol
I just kept on trying different things.
it will be a driver issue Ill try to find the thread that got me out of it
---------- Post added at 11:11 PM ---------- Previous post was at 11:03 PM ----------
Found it Try this.http://forum.xda-developers.com/showthread.php?t=1399889
I bricked mine last night and kept getting stuck at "waiting for device" and figured out Windows ceases to recognize it as something it has a driver for.
Windows Device Manager showed the Kindle with a yellow sign next to it. I right clicked and updated the driver but rather than detecting it at all I manually picked a device.
Don't have Windows in front of me right now but it was something like "Android Phone" for the device type and then the device was the first one listed "ADB Interface" or something starting with ADB anyway.
Once that driver was loaded I could issue ADB commands again and got it fixed.
Sent from my Kindle Fire using Tapatalk
Please do the KF rooting community a favor when you get your new kindle and stay away from rooting it. You obviosuly cant take the time to fix your own problems and would rather give amazon another reason to hate root users.
googlelover said:
Please do the KF rooting community a favor when you get your new kindle and stay away from rooting it. You obviosuly cant take the time to fix your own problems and would rather give amazon another reason to hate root users.
Click to expand...
Click to collapse
not very nice - I had same problem - stuck at boot logo.
instead of telling someone where to go maybe a fix would be better.
bg4 said:
not very nice - I had same problem - stuck at boot logo.
instead of telling someone where to go maybe a fix would be better.
Click to expand...
Click to collapse
Well considering he already convinced amazon to send him a new one its a little too late, and others have already weighed in to help, its not very nice but its the truth. If he would have just waited more than an hour for people to try and help him he would probably have been able to fix it.
Jus a quick servh would give you the answers you're looking for. It's not bricked. So relax
HaroldBawls said:
Rooting it inst the issue, trying to put a phone OS on a tablet is the issue.
Click to expand...
Click to collapse
?
Tell that to all the Nook Color users running CM7 or to Samsung, HTC and others that shipped tablets with Android 2.2 and 2.3
googlelover said:
Please do the KF rooting community a favor when you get your new kindle and stay away from rooting it. You obviosuly cant take the time to fix your own problems and would rather give amazon another reason to hate root users.
Click to expand...
Click to collapse
Troll found. Anti-Hate taser activate.
Sent from my Kindle Fire using Tapatalk
Hey, quick question. I'm having similar issues and want to just call it a day.
When you convinced Amazon to replace it, did you tell them it was rooted/modified? Also, are they shipping you a new one just like that? Or do you have to send yours back first. Thanks! A response would be very much appreciated.
i had an issue last night and spent seven hours between dos and reading forums and couldn't find the answer, but at 630 this morning i got it and retested it today again by rebricking it and fixing it and it has to be the easiest thing that i've ever done.
unplug your kindle
turn your computer off
turn off your kindle with a hard reset
turn the computer back on and plug the kindle in
turn the kindle back on
in kindle utilities hit 1 and press enter
then hit 1 and press enter
it should go to reset your kindle and say it's done and to press any button to continue but don't press anything until your kindle is back on the splash menu
it worked for me when i couldn't find anything else to do and is way to simple to not try, so i hope it helps someone else
zbhest said:
Hey, quick question. I'm having similar issues and want to just call it a day.
When you convinced Amazon to replace it, did you tell them it was rooted/modified? Also, are they shipping you a new one just like that? Or do you have to send yours back first. Thanks! A response would be very much appreciated.
Click to expand...
Click to collapse
I was on skype with him. He said he was "playing angry birds, it restarted and is stuck at the 'kindle fire logo' " they didn't ask if it was rooted, no questions asked.
Sent from my Kindle Fire using Tapatalk
mattlgroff said:
I was on skype with him. He said he was "playing angry birds, it restarted and is stuck at the 'kindle fire logo' " they didn't ask if it was rooted, no questions asked.
Sent from my Kindle Fire using Tapatalk
Click to expand...
Click to collapse
This is exactly what happened. Because it didn't have the TWRP recovery screen or anything, any average tech support person wouldnt be able to tell it had been rooted. The failure actually happened after installing the stock rom so im pretty sure if they even take the time to inspect it, they wil see an unused, unrooted stock rom on the devoce
punkboyarde said:
i had an issue last night and spent seven hours between dos and reading forums and couldn't find the answer, but at 630 this morning i got it and retested it today again by rebricking it and fixing it and it has to be the easiest thing that i've ever done.
unplug your kindle
turn your computer off
turn off your kindle with a hard reset
turn the computer back on and plug the kindle in
turn the kindle back on
in kindle utilities hit 1 and press enter
then hit 1 and press enter
it should go to reset your kindle and say it's done and to press any button to continue but don't press anything until your kindle is back on the splash menu
it worked for me when i couldn't find anything else to do and is way to simple to not try, so i hope it helps someone else
Click to expand...
Click to collapse
Thanks, but this only works if it connects over usb. Doing this results in "waiting for device" as mentioned before

[Q] Acer A500 bricked. Is it fixable?

So, my neighbor bought an Acer A500 a few months back. He ended up not liking it so I bought it off of him. My tablet and I got really close and I fell in love. I started neglecting my girlfriend and all that. We had a beautiful relationship; my tablet and me. But, a couple days ago I was playing N.O.V.A 3 and it froze. I thought nothing of it and just powered it down. To my dismay, it froze at the Acer screen. I restarted it again and got the same thing. My life was over. My heart felt like it was ripped from my chest... I shed a manly tear.
I've tried vol- and power, vol+ and power, the reset button, D/Ling several different update.zip files and copying them to my SD. I've spent the last couple days reading and trying everything. All I get is the Droid guy with the blue thing swirling in his chest and then him laying on the ground with a red triangle and an exclamation point.
I'm told it's most likely not a hardware issue as things things are almost bullet-proof. But, I am pretty good at breaking things
Am I screwed or does someone have a miracle they can share. My gaming life depends on it.
-Dennis.
DennisPimps said:
So, my neighbor bought an Acer A500 a few months back. He ended up not liking it so I bought it off of him. My tablet and I got really close and I fell in love. I started neglecting my girlfriend and all that. We had a beautiful relationship; my tablet and me. But, a couple days ago I was playing N.O.V.A 3 and it froze. I thought nothing of it and just powered it down. To my dismay, it froze at the Acer screen. I restarted it again and got the same thing. My life was over. My heart felt like it was ripped from my chest... I shed a manly tear.
I've tried vol- and power, vol+ and power, the reset button, D/Ling several different update.zip files and copying them to my SD. I've spent the last couple days reading and trying everything. All I get is the Droid guy with the blue thing swirling in his chest and then him laying on the ground with a red triangle and an exclamation point.
I'm told it's most likely not a hardware issue as things things are almost bullet-proof. But, I am pretty good at breaking things
Am I screwed or does someone have a miracle they can share. My gaming life depends on it.
-Dennis.
Click to expand...
Click to collapse
Do you know what you were running on this thing? Was it stock Honeycomb, scock ICS, or was it running a custom ROM? (If so which one?)
Was it ever hooked up to your PC? (This would help with retrieving CPUID, if it was.) Do you know your CPUID? (Or SBK?)
You should at the least know the answers to these questions before you attempt any type of repair, as it is almost certainly salvageable, but you will almost certainly need your CPUID.
Danny2 said:
Do you know what you were running on this thing? Was it stock Honeycomb, scock ICS, or was it running a custom ROM? (If so which one?)
Was it ever hooked up to your PC? (This would help with retrieving CPUID, if it was.) Do you know your CPUID? (Or SBK?)
You should at the least know the answers to these questions before you attempt any type of repair, as it is almost certainly salvageable, but you will almost certainly need your CPUID.
Click to expand...
Click to collapse
I was running 4.0.1 ICS. I do have my cpuid and SBK. I tried flashing a new rom using blackthund3rs flash tool but it got to about 25% and stopped. I keep losing sync with my PCs, though.
DennisPimps said:
I was running 4.0.1 ICS. I do have my cpuid and SBK. I tried flashing a new rom using blackthund3rs flash tool but it got to about 25% and stopped. I keep losing sync with my PCs, though.
Click to expand...
Click to collapse
So, do you want to go back to stock, or to a custom ROM? If you wanna go stock, the easiest way would be load a 3.01 EUU, & upgrade on the play market to 4.03. That will prove it isn't a hardware issue. Alternatively, you could root, load a recovery, a bootloader, & flash a new ROM.
Danny2 said:
So, do you want to go back to stock, or to a custom ROM? If you wanna go stock, the easiest way would be load a 3.01 EUU, & upgrade on the play market to 4.03. That will prove it isn't a hardware issue. Alternatively, you could root, load a recovery, a bootloader, & flash a new ROM.
Click to expand...
Click to collapse
To be honest, I really don't care as long as I can getting it working again. But I would rather root it.
I think I can get it to work but neither one of my computers will recognize it. It shows up in APX and says something about recovery driver mode when I plug it into the laptop with Vista automatically downloads a driver and installs it again. I've tried turning off automatic driver install but that doesn't work for some reason. The one with XP Pro just shows up APX device but the APX Flash Tool by blackthund3r says it can't find it. I've downloaded the Acer Iconia 500 drivers and installed them but that doesn't work either. I'm at a loss.
Any tips would be great. I think I have a better chance using my laptop with XP, though. I also need to let you know that I truly do appreciate you trying to help. If you're ever in Columbus Ohio, let me know and I'll buy you a beer. lol
DennisPimps said:
To be honest, I really don't care as long as I can getting it working again. But I would rather root it.
I think I can get it to work but neither one of my computers will recognize it. It shows up in APX and says something about recovery driver mode when I plug it into the laptop with Vista automatically downloads a driver and installs it again. I've tried turning off automatic driver install but that doesn't work for some reason. The one with XP Pro just shows up APX device but the APX Flash Tool by blackthund3r says it can't find it. I've downloaded the Acer Iconia 500 drivers and installed them but that doesn't work either. I'm at a loss.
Any tips would be great. I think I have a better chance using my laptop with XP, though. I also need to let you know that I truly do appreciate you trying to help. If you're ever in Columbus Ohio, let me know and I'll buy you a beer. lol
Click to expand...
Click to collapse
Sorry,I thought I responded to this yesterday, but just now noticed I didn't.
Fire it up in APX mode, and install the 3.01 EUU from the development section, (Stock ROM listing) then simply follow the upgrade path to 4.03, then root. If you drivers are installed correctly, everything will work fine, if not, nothing will happen. If it does start to load the stock ROM, then fails with a write error after it attempts to write the bootsector, you may need to run Badsector, or babsector, depending where you look. Search the recent posts on this, you will find lots of stuff.
Danny2 said:
Sorry,I thought I responded to this yesterday, but just now noticed I didn't.
Fire it up in APX mode, and install the 3.01 EUU from the development section, (Stock ROM listing) then simply follow the upgrade path to 4.03, then root. If you drivers are installed correctly, everything will work fine, if not, nothing will happen. If it does start to load the stock ROM, then fails with a write error after it attempts to write the bootsector, you may need to run Badsector, or babsector, depending where you look. Search the recent posts on this, you will find lots of stuff.
Click to expand...
Click to collapse
How would I go about installing the EUU? I have nvflash and blackthund3r's flashing tools. But I can't seem to get my PC and tablet to connect. When I plug it into my PC without being in APX mode, it just says MTP Device. When I plug it in while in APX mode it does say something about Picasso Recovery Driver.
If you could explain things to me like I'm aN idiot, I'd really appreciate it.
Thanks,
Dennis
DennisPimps said:
How would I go about installing the EUU? I have nvflash and blackthund3r's flashing tools. But I can't seem to get my PC and tablet to connect. When I plug it into my PC without being in APX mode, it just says MTP Device. When I plug it in while in APX mode it does say something about Picasso Recovery Driver.
If you could explain things to me like I'm aN idiot, I'd really appreciate it.
Thanks,
Dennis
Click to expand...
Click to collapse
Sorry for late response, I watched for reply from yourself, but you didn't answer for 10 days, I lost track. Still need help?
Danny2 said:
Sorry for late response, I watched for reply from yourself, but you didn't answer for 10 days, I lost track. Still need help?
Click to expand...
Click to collapse
Yea, it's still bricked. I did finally get the flash tool to recognize it but it kept hanging up. I also tried Timmy Dean's EUU tool and that hangs up too. I did a little more research and found that I may have a faulty emmc. I ran babsector and got 'fatal error code 9 cannot format partition BCT.' I found a thread here that discusses how to write around the bad sectors using Linux. I'm going to give that a go... I've always wanted to learn Linux. Hey, I can't screw it up anymore than it already is, right? Again, thanks for your time and effort in trying to help.
Cheers,
Dennis
Hey, before you try that, try different USB cables and ports (if u haven't already)
I had a similar problem with my phone not maintaining stable USB link to PC... after 4 days I tried a diff USB cable and boom, snap, working.
Just a thought.....
Sent from my A500 using xda app-developers app
ericpeacock79 said:
Hey, before you try that, try different USB cables and ports (if u haven't already)
I had a similar problem with my phone not maintaining stable USB link to PC... after 4 days I tried a diff USB cable and boom, snap, working.
Just a thought.....
Sent from my A500 using xda app-developers app
Click to expand...
Click to collapse
I'll give that a go, m8.
Thanks!
-Dennis
DennisPimps said:
I'll give that a go, m8.
Thanks!
-Dennis
Click to expand...
Click to collapse
Just wondering if you ever figured out the errors you were getting during flashing? Currently having the same issues when using babsector.

Need help... cannot figure rooting out

Hi all,
Long story short, I accidentally bought a Kindle Fire HD 7. I was hoping to root it but I've had nothing but difficulty. Can anyone help me with the things below? ** Please don't reply if you can't - the disorder and unmoderation of this forum is part of the confusion problem **
- The apps that are given on this site mostly don't work for 7.2.3. Is this an issue with the version?
- I kept getting permission denied errors. Nothing that pushes over, pushes successfully - yet it says it does
- When I finally got something "rooted", my status bar and home bar (at the bottom) are all gone. I can pretty much do nothing with it
- I can't figure out how to restore. I can get into FastBoot mode fairly easily, but when I try to do anything I get "waiting on device" errors. Any ideas?
- I'm a Mac guy, but running Windows 7 to do this. I've tried various versions of drivers posted on the board, but W7 is just a PITA to work with. When it goes into Fastboot, it comes up as an "unrecognized device" in Device Manager. Would this be part of the problem? I've tried to associate drivers with the unknown device, but it keeps saying the driver it has is the best (even though I've removed it).
And while I admit, an emotional rant after spending way too long having to do the above..:
- This forum is a complete mess.. can people with KF HD 8.9's get out of the forum and quit replying or giving advice on the wrong device? Mods, please shut down or move KFHD 8.9 posts. For people trying to find out info, it's seriously a mess.
lordmuggins said:
Hi all,
Long story short, I accidentally bought a Kindle Fire HD 7. I was hoping to root it but I've had nothing but difficulty. Can anyone help me with the things below? ** Please don't reply if you can't - the disorder and unmoderation of this forum is part of the confusion problem **
- The apps that are given on this site mostly don't work for 7.2.3. Is this an issue with the version?
- I kept getting permission denied errors. Nothing that pushes over, pushes successfully - yet it says it does
- When I finally got something "rooted", my status bar and home bar (at the bottom) are all gone. I can pretty much do nothing with it
- I can't figure out how to restore. I can get into FastBoot mode fairly easily, but when I try to do anything I get "waiting on device" errors. Any ideas?
- I'm a Mac guy, but running Windows 7 to do this. I've tried various versions of drivers posted on the board, but W7 is just a PITA to work with. When it goes into Fastboot, it comes up as an "unrecognized device" in Device Manager. Would this be part of the problem? I've tried to associate drivers with the unknown device, but it keeps saying the driver it has is the best (even though I've removed it).
And while I admit, an emotional rant after spending way too long having to do the above..:
- This forum is a complete mess.. can people with KF HD 8.9's get out of the forum and quit replying or giving advice on the wrong device? Mods, please shut down or move KFHD 8.9 posts. For people trying to find out info, it's seriously a mess.
Click to expand...
Click to collapse
Ok what is the state of your KFHD? 7"? I would try to use this toolhttp://forum.xda-developers.com/showthread.php?t=1951254 to restore your kindle and getting back to a working state. If you have any questions post them in here or that forum and I will try to guide you through anything. You should not try to use an automated root tool if it isn't for your specified version(7" 7.2.3) and using a automated tool, I think personally, is just not good in general. What does the device manager specifically say when you are in fastboot? It shoulde look like this:
Thanks for getting back to me. I have indeed also tried that, but I encounter the Fastboot problem mentioned above. I can get it into FB mode fine, but when I go to do anything, it gets stuck at "waiting for device". I'm wondering what I'm doing wrong?
I'm using Windows 7 (gah)... just for the purpose of this. Believe me, it reminds me why I've left Windows looonngg ago
PS All automated tools were specific to my model and version #.. i wouldn't do otherwise.
And I forgot to say, it shows the yellow triangle warning signs.
I have however installed all the right drivers that I got on various places on the forums. Any ideas why it's doing that? (USB debugging/ADB is enabled of course)
lordmuggins said:
And I forgot to say, it shows the yellow triangle warning signs.
I have however installed all the right drivers that I got on various places on the forums. Any ideas why it's doing that? (USB debugging/ADB is enabled of course)
Click to expand...
Click to collapse
Try to reinstall the appropriate drivers.. first uninstall the ones you have now then reinstall.. if you have the yellow triangle in device manager the drivers are not installed correctly
I've tried that.. not sure what I need to do now. (I hate Windows)
The drivers appear fine when not in Fastboot (ie regular ADB) just not when in Fastboot
lordmuggins said:
I've tried that.. not sure what I need to do now. (I hate Windows)
The drivers appear fine when not in Fastboot (ie regular ADB) just not when in Fastboot
Click to expand...
Click to collapse
You do know that ADB and Fastboot are different.. Correct? They are two different cmd lines to execite comds to your kindle..does your kindle boot? What is its state? what are you seeing or does it even run at all>
I thought I made this clear in other posts, sorry
My Kindle boots fine normally, but in my attempts to root it, it's screwed something up (my menubar doesn't appear). I wished to restore it using the tool above.
I can get it into Fastboot, but I can't actually perform any actions due to it saying "waiting for device". Most ADB functionality works fine, i.e. to push apps. But I also can't get it rooted.
My issue is that when it is in Fastboot...not when it's not. That is what I'm trying to figure out.
lordmuggins said:
I thought I made this clear in other posts, sorry
My Kindle boots fine normally, but in my attempts to root it, it's screwed something up (my menubar doesn't appear). I wished to restore it using the tool above.
I can get it into Fastboot, but I can't actually perform any actions due to it saying "waiting for device". Most ADB functionality works fine, i.e. to push apps. But I also can't get it rooted.
My issue is that when it is in Fastboot...not when it's not. That is what I'm trying to figure out.
Click to expand...
Click to collapse
Have you tried Kindle Fire First Aide tool and the restore option of you version?
Yes, I have.
And my issue remains - when in Fastboot mode, it also gets stuck on "waiting for device".
When normal boot, ADB functions are fine. It communicates.. things happen
When in fastboot (I have a WordArt looking 'fastboot' logo on the screen) then nothing appears to communicate, and my Device Manager claims it has an "Unknown Device" that it wont let me manually install drivers for.
Windows 7 is x64 if that makes a difference
lordmuggins said:
Yes, I have.
And my issue remains - when in Fastboot mode, it also gets stuck on "waiting for device".
When normal boot, ADB functions are fine. It communicates.. things happen
When in fastboot (I have a WordArt looking 'fastboot' logo on the screen) then nothing appears to communicate, and my Device Manager claims it has an "Unknown Device" that it wont let me manually install drivers for.
Windows 7 is x64 if that makes a difference
Click to expand...
Click to collapse
Try a factory reset on the device and if that doesn't work go to Chris's thread, KFFirstAide and post your problems that you having with the software. He will help you figure out if something is wrong with your device or its the software. I would think its user related, in the nicest way possible. A lot of times we get are selves all worked up over this stuff and forget to specific steps, I am guilty as well. Maybe take a step back for a few hours and then give it another shot.. Sorry I couldnt help more but I currently don't have my KFHD bc I just got a new one shipped to me and still waiting for it to arrive.. If i had my device in front of me I would probably be able to find you a solution.. Its been three weeks since I have seen a Kindle and my memory is vanishing
How do you propose I do a factory reset?
lordmuggins said:
How do you propose I do a factory reset?
Click to expand...
Click to collapse
right.. menubar is gone.. how the F did that happen.. I don't get all these people having so much problem with rooting their devices and $hit disappearing.. Can you download soft keys? I don't remember if you need to be rooted or not too..
If I knew the answer to that question, I wouldn't be here. I do not see how I can download soft keys.. unless they're in the Amazon store?
lordmuggins said:
If I knew the answer to that question, I wouldn't be here. I do not see how I can download soft keys.. unless they're in the Amazon store?
Click to expand...
Click to collapse
Hey man just trying to help you.. I'm not the one with the problem, although I am making my problem bc I am trying to help. Go over to either thread KFFirstAide or KFHD system.img resotre tool and post your problem.. good luck
So I got it restored; I had to execute the app open in adb to get into Settings. Still can't figure out how to get the Win 7 to recognize it in Fastboot mode.. I just get "waiting for device"
lordmuggins said:
So I got it restored; I had to execute the app open in adb to get into Settings. Still can't figure out how to get the Win 7 to recognize it in Fastboot mode.. I just get "waiting for device"
Click to expand...
Click to collapse
Do you mean you get that when you select the option to reboot into fastboot mode, or that you are already on the fastboot screen but nothing is happening?
I had the exact same issue with missing status bar and softkeys, cazy annoying. So hopefully I can remember exactly what I did, depending on your answer to my question though
In regular mode, I had missing status bar and softkeys. I restored factory settings (by using adb to get into the settings screen). They are now back.
Now, I have it rooted (well, I have Superuser loaded at least and it appears to be working)... but that is all. It still feels half-done to me.
With the FirstAide tool I'm getting into Fastboot and then I was going to use it to restore it using the Restore Tool here: http://forum.xda-developers.com/showthread.php?t=1951254
But it doesn't work.. I can load into the Fastboot screen (wordart logo) but it doesn't connect to the device... I just get "waiting for device" and that's where it stops. The WIndows 7 PC I'm using just says that an unknown device has connected and leaves it there.
Ideally, I wish to load Google Play etc, but I can't do that using the First Aide tool. It throws a lot of permission denied errors at me.. reboots several times, says it has been successful but none of the apps are there.
Ideas? I feel like I'm getting closer... perhaps..!
Have you tried running a app that needs root and seeing if the "grant permission" window pops up when you run it. There is a root checker app that you could install from the Noobs Guide to rooting, which should do the trick. SUChecker.apk http://forum.xda-developers.com/showthread.php?t=2069117
If you have managed to get the UI bars back, how come you want to use the restore tool to reset the whole kindle?
If you root is working fine, and you want to install google play then follow the Alternative Manual Install from here http://forum.xda-developers.com/showthread.php?t=2069329 instead of using the first aide tool, which seems to be giving a few issues at the moment.
Another random solution is make sure you are using a usb2 port instead of a usb3 port(if you have one)

[Q] Is it dead?

So I apologize in advance, I am a n00b to rooting android devices.
Long story short, I think I hard bricked my TF300T.
I had followed some rooting guides (from other sites ) and yup, I'm stuck at the Asus logo with the "unlock" message in the corner.
I can't get into fastboot or anything else by holding Volume Down + Power, all I can get is my computer to recognize it as an APX device.
At one point previously, it almost bricked and froze at the same spot, but I somehow played with different reset combinations and it came alive again. Is there any reset combinations that worked for anyone?
Also, I remember doing a system backup within the device. Is there any way to access that, or is it gone?
In other words, do I need to buy a new motherboard? Or is there a remote possibility I can fix it?
One last layman question: why is it I can't just read and write to the device's internal memory, regardless of its status?
-Cannon Fodder
Cannon Fodder said:
So I apologize in advance, I am a n00b to rooting android devices.
Long story short, I think I hard bricked my TF300T.
I had followed some rooting guides (from other sites ) and yup, I'm stuck at the Asus logo with the "unlock" message in the corner.
I can't get into fastboot or anything else by holding Volume Down + Power, all I can get is my computer to recognize it as an APX device.
At one point previously, it almost bricked and froze at the same spot, but I somehow played with different reset combinations and it came alive again. Is there any reset combinations that worked for anyone?
Also, I remember doing a system backup within the device. Is there any way to access that, or is it gone?
In other words, do I need to buy a new motherboard? Or is there a remote possibility I can fix it?
One last layman question: why is it I can't just read and write to the device's internal memory, regardless of its status?
-Cannon Fodder
Click to expand...
Click to collapse
Looks like you will need to replace the mb, if you have not already generated nvflash binaries. You can't read/ write to internal memory because when connected to a pc this is done using the mtp protocol which os loaded by android, and hasn't in your case.
JoinTheRealms said:
Looks like you will need to replace the mb, if you have not already generated nvflash binaries. You can't read/ write to internal memory because when connected to a pc this is done using the mtp protocol which os loaded by android, and hasn't in your case.
Click to expand...
Click to collapse
Ok another n00b question...
Why can't I download someone else's binaries from the same type of product?
Forgive me, I'm used to working with Windows and I'm thinking in terms of an install disc...
Cannon Fodder said:
Ok another n00b question...
Why can't I download someone else's binaries from the same type of product?
Forgive me, I'm used to working with Windows and I'm thinking in terms of an install disc...
Click to expand...
Click to collapse
NvFlash blobs are specific to each device they are generated on.
Its like trying to infuse with a different blood type, where each tf300 has a different blood type. Wheelie will reject it and your tablet will reject it.
Cannon Fodder said:
So I apologize in advance, I am a n00b to rooting android devices.
Long story short, I think I hard bricked my TF300T.
I had followed some rooting guides (from other sites ) and yup, I'm stuck at the Asus logo with the "unlock" message in the corner.
I can't get into fastboot or anything else by holding Volume Down + Power, all I can get is my computer to recognize it as an APX device.
At one point previously, it almost bricked and froze at the same spot, but I somehow played with different reset combinations and it came alive again. Is there any reset combinations that worked for anyone?
Also, I remember doing a system backup within the device. Is there any way to access that, or is it gone?
In other words, do I need to buy a new motherboard? Or is there a remote possibility I can fix it?
One last layman question: why is it I can't just read and write to the device's internal memory, regardless of its status?
-Cannon Fodder
Click to expand...
Click to collapse
Here is a link to my guide to enter the bootloader.* Try these each several times as this tablet morphs as you progress.
Provide us a little more info.
What happened to create this problem? *Details please.
Did you have a custom recovery, rom, etc? *If so which ones?
Can you fix it; maybe. *We'll have a better idea once we know your details.
cmendonc2 said:
NvFlash blobs are specific to each device they are generated on.
Its like trying to infuse with a different blood type, where each tf300 has a different blood type. Wheelie will reject it and your tablet will reject it.
Click to expand...
Click to collapse
Thank you for that illustration. It did help me understand.
One last thought of desperation: Is the internal storage an actual SD Card? Or is it just called that on the device menu for some odd reason?
tobdaryl said:
Here is a link to my guide to enter the bootloader.* Try these each several times as this tablet morphs as you progress.
Provide us a little more info.
What happened to create this problem? *Details please.
Did you have a custom recovery, rom, etc? *If so which ones?
Can you fix it; maybe. *We'll have a better idea once we know your details.
Click to expand...
Click to collapse
I was installing a custom ROM, when I went to "RCK"(?), it hung up when it said it was booting kernal. It didn't do anything for quite a while, so I held down the power buttong and reset it. And now it is stuck in the boot loop.
cmendonc2 said:
NvFlash blobs are specific to each device they are generated on.
Its like trying to infuse with a different blood type, where each tf300 has a different blood type. Wheelie will reject it and your tablet will reject it.
Click to expand...
Click to collapse
off topic but that is a pretty good analogy :highfive:
One question tearing me long enought: did someone tryed to hack nvflash binaries? As far as I know there is only one unique file and may be not all of it's content is specific for certain device. Did someone dig in that direction?
Graiden05 said:
One question tearing me long enought: did someone tryed to hack nvflash binaries? As far as I know there is only one unique file and may be not all of it's content is specific for certain device. Did someone dig in that direction?
Click to expand...
Click to collapse
that would be really useful.
And although I understood the analogy, I still don't get the technical aspects of why you can have 1,000 devices that are all the same but they each need a different file. I'm used to building Windows computers, and you can use the same image repeatedly for multiple copies of the same type of computer.
I'm also wondering: why can't anything be installed straight from the SD card or even USB when a device is bricked? How does Asus do it when they fix people's motherboards?
Cannon Fodder said:
that would be really useful.
And although I understood the analogy, I still don't get the technical aspects of why you can have 1,000 devices that are all the same but they each need a different file. I'm used to building Windows computers, and you can use the same image repeatedly for multiple copies of the same type of computer.
I'm also wondering: why can't anything be installed straight from the SD card or even USB when a device is bricked? How does Asus do it when they fix people's motherboards?
Click to expand...
Click to collapse
Think of it like a cryptographic key. Each tablet's NVFlash blobs has a certain signature. To compare it to the Windows situation, assume that you have a legal, non-volume licence key for Windows, only that when you installed it the first time, the key was permanently bound to the motherboard.
Assume that it is a string of lower-case letters (good chance that it has numbers, capital letters, and all sorts of fun stuff). A two-character signature has a space of 26*26, which is already over 625 keys. That number scales hella fast when you add more characters.
Asus will fix your tablet by either replacing your motherboard completely (more likely), or they may have the NVFlash keys for your device by its serial number. However, since your bootloader is unlocked, and they will have your serial number on file as "unlocked", they may just refuse to repair it outright. Surely, they will refuse it for a warranty repair, though I don't know if they will even repair your device for money.

[STOP] FireOS 5.1.1 & attempted downgrade - the fastest Fire brick!

OK, just got the Fire today. The OS says 5.0.1 from Nov 17th, and says update is available, version 541112720. I block OTAVerifier only, thinking by blocking the verification I can intercept the update file in /cache. then I turn on airplane mode, play a bit and boot into TWRP via fastboot, install SuperSu. All is good.
Then I decide to see what the update is all about, and let it download. To my surprise, it starts installing. After the installation, I see FireOS 5.1.1 Now, I try to go into TWRP via fastboot, and it does not reboot and just hangs. A couple more tries - and still nothing.
I go back to stock recovery, and start sideloading update-kindle-37.5.2.2_user_522054520.bin . It sideloads OK, and upon reboot i get dark screen. Nothing works. This sounds very similar to the 4th gen issues where downgrades were bricking Fires :
http://forum.xda-developers.com/fire-hd/general/stop-upgrade-to-lollipop-via-twrp-t3216817
It'll be simple to install 5.1.1 via TWRP once the update file is captured, such that the older bootloaders can be kept.
But beware of the update - without TWRP there likely won't be root!
Dang, sucks about the brick! Hopefully getting TWRP to work again won't take a herculean effort. Right now I'm loving SlimLP but anyone getting one for xmas would likely get that Fire OS 5.1.1 pushed to them right away upon booting up and logging in and I would hate to see them stuck on that!
Damn!
What if an open wifi network is within range? Will the Fire OS ask before connecting?
My friend has a new fire in the box & has an open wifi network within range of their place.
The 5.1.1 update should find it's way to amazon's Software Updates page in time. It's not there yet. http://www.amazon.com/gp/help/customer/display.html?nodeId=201830180
blueberry.sky said:
What if an open wifi network is within range? Will the Fire OS ask before connecting?
My friend has a new fire in the box & has an open wifi network within range of their place.
Click to expand...
Click to collapse
afaik they don't ship with wifi on, and you have to agree to connect if wifi is detected.
Still, anyone who might want to root needs to keep wifi off until this is sorted--or until they're rooted and can rename DeviceSoftwareOTA.apk . And everyone on rooted stock should confirm /system/priv-app/DeviceSoftwareOTA/DeviceSoftwareOTA.apk is renamed to .apkOFF (or whatever), which should prevent a download. Don't know how the roms handle OTA.
I do believe that you should have to agree to connect to wifi. But I'd like to be 100% sure. Don't want to take the slightest chance.
I would appreciate confirmation from anyone with a brand new Fire & an open wifi network within range, that it will not auto-connect.
bibikalka said:
It'll be simple to install 5.1.1 via TWRP once the update file is captured, such that the older bootloaders can be kept.
But beware of the update - without TWRP there likely won't be root!
Click to expand...
Click to collapse
So, 5.1.1 can't boot TWRP and downgrading produces bricks. Lovely!
Wonder if there's any chance the CM recovery will boot?
I assume some of the "old-timers" here will capture the update soon enough. If not, I'm glad to give it a go.
tried the downgrade as well, same result. I think the reason we can't get back into recovery\fastboot is because the device is just endlessly rebooting (you can see in device manager). it wont let you power it off to try the volume down+power combo and just holding them does nothing. im going to let mine die overnight hopefully and maybe getting the volume down+power from off will let us back into recovery?
---------- Post added at 01:14 AM ---------- Previous post was at 12:46 AM ----------
DoLooper said:
So, 5.1.1 can't boot TWRP and downgrading produces bricks. Lovely!
Wonder if there's any chance the CM recovery will boot?
I assume some of the "old-timers" here will capture the update soon enough. If not, I'm glad to give it a go.
Click to expand...
Click to collapse
Well 5.0.1 is available on the Amazon website here: https://www.amazon.com/gp/help/customer/display.html?nodeId=201830180 so I contacted Amazon for the 5.1.1 file and this was what I got:
Jyothirmayi: In this case, I'll personally follow up your contact and email you the link for the update because we currently don't have the manual link for the update in our website.
I will post here if\when I hear back
dmesg on linux machine when plug usb, open mediatek preloader com port.
Have this on bricked fire ?
usb 1-2.4: Product: MT65xx Preloader
usb 1-2.4: Manufacturer: MediaTek
cdc_acm 1-2.4:1.1: ttyACM0: USB ACM device
adb
usb 1-2.4: New USB device found, idVendor=1949, idProduct=0222
usb 1-2.4: New USB device strings: Mfr=2, Product=3, SerialNumber=4
usb 1-2.4: Product: Fire
usb 1-2.4: Manufacturer: Amazon
usb 1-2.4: SerialNumber: xxxxxxxxxxxxxxxxxxx
fastboot
usb 1-2.4: New USB device found, idVendor=0bb4, idProduct=0c01
usb 1-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-2.4: Product: Android
usb 1-2.4: Manufacturer: MediaTek
usb 1-2.4: SerialNumber: xxxxxxxxxxxxxx
If you have TWRP, why didn't you just use the file manager to copy and paste the OTA from your /cache to your sd card? If you can boot to TWRP, see if it's still there.
You can also dump your cache via adb shell from within TWRP and get the OTA by extracting the cache.img that dumps. There are several ways, as long as TWRP and fastboot are still booting.
Also, you can use adb shell within twrp to dd a system.img dumped from another fire tab, and restore your device that way if all else fails.
hp420 said:
If you have TWRP, why didn't you just use the file manager to copy and paste the OTA from your /cache to your sd card? If you can boot to TWRP, see if it's still there.
You can also dump your cache via adb shell from within TWRP and get the OTA by extracting the cache.img that dumps. There are several ways, as long as TWRP and fastboot are still booting.
Also, you can use adb shell within twrp to dd a system.img dumped from another fire tab, and restore your device that way if all else fails.
Click to expand...
Click to collapse
I think in the OP, he mentioned that he is no longer able to get into TWRP after 5.1.1 update...
So I bricked my device last night trying to downgrade before anyone had posted about it. Oops.
I did some Googling and theoretically these tools here should help us unbrick, but I believe we don't have the Amazon firmware in the right format.
HOWEVER, this tool, if I understand it right, should be able to pull the firmware from a working device in the right format for us to try flashing to a bricked device. Anyone want to give it a shot?
87racer said:
Jyothirmayi: In this case, I'll personally follow up your contact and email you the link for the update because we currently don't have the manual link for the update in our website.
I will post here if/when I hear back
Click to expand...
Click to collapse
mmoogle said:
So I bricked my device last night trying to downgrade before anyone had posted about it. Oops.
I did some Googling and theoretically these tools here should help us unbrick, but I believe we don't have the Amazon firmware in the right format.
HOWEVER, this tool, if I understand it right, should be able to pull the firmware from a working device in the right format for us to try flashing to a bricked device. Anyone want to give it a shot?
Click to expand...
Click to collapse
When we get the official file from Amazon, we can format it to the way the MTK Droid Tool wants it, and then that would theoretically work.
mmoogle said:
So I bricked my device last night trying to downgrade before anyone had posted about it. Oops.
I did some Googling and theoretically these tools here should help us unbrick, but I believe we don't have the Amazon firmware in the right format.
HOWEVER, this tool, if I understand it right, should be able to pull the firmware from a working device in the right format for us to try flashing to a bricked device. Anyone want to give it a shot?
Click to expand...
Click to collapse
Vlasp said:
When we get the official file from Amazon, we can format it to the way the MTK Droid Tool wants it, and then that would theoretically work.
Click to expand...
Click to collapse
Well, I've been there before with the 4th gen Fire HD :
http://forum.xda-developers.com/fire-hd/help/mtk-tools-people-hopeless-bricks-t3139784
In a nutshell, MTK Droid tools don't even talk to the working Fire properly, so it's unlikely they'd help with a bricked one ...
87racer said:
tried the downgrade as well, same result. I think the reason we can't get back into recovery\fastboot is because the device is just endlessly rebooting (you can see in device manager). it wont let you power it off to try the volume down+power combo and just holding them does nothing. im going to let mine die overnight hopefully and maybe getting the volume down+power from off will let us back into recovery?
Click to expand...
Click to collapse
Just pull your battery. The back cover is very easy to get off. Use a knife just to widen the seam so you can get your fingernail in at the corner. Keep one fingernail at the corner & side a 2nd nail down along the edge.
Then the battery connector lifts out upwards.
http://forum.xda-developers.com/ama...o-photo-amazon-fire-2015-motherboard-t3227808
bibikalka said:
Well, I've been there before with the 4th gen Fire HD :
http://forum.xda-developers.com/fire-hd/help/mtk-tools-people-hopeless-bricks-t3139784
In a nutshell, MTK Droid tools don't even talk to the working Fire properly, so it's unlikely they'd help with a bricked one ...
Click to expand...
Click to collapse
We might be in luck. I happen to have 3 of them One bricked, one mostly untouched on 5.1.1 and another with OTA blocked on 5.0.1. I will fiddle with the tools you posted and see if I can come up with something.
blueberry.sky said:
Just pull your battery. The back cover is very easy to get off. Use a knife just to widen the seam so you can get your fingernail in at the corner. Keep one fingernail at the corner & side a 2nd nail down along the edge.
Then the battery connector lifts out upwards.
http://forum.xda-developers.com/ama...o-photo-amazon-fire-2015-motherboard-t3227808
Click to expand...
Click to collapse
Good to know, even over night, it still isn't dead so I might give this a shot.

			
				
So, if i previously installed the google framework and blocked ota like most people did, this won't block the ota really ?
87racer said:
We might be in luck. I happen to have 3 of them One bricked, one mostly untouched on 5.1.1 and another with OTA blocked on 5.0.1. I will fiddle with the tools you posted and see if I can come up with something.
Click to expand...
Click to collapse
The best deal is of course to capture the 5.1.1 update file. I am eager to try it, provided I get root with requires installing via TWRP.
bibikalka said:
Well, I've been there before with the 4th gen Fire HD :
http://forum.xda-developers.com/fire-hd/help/mtk-tools-people-hopeless-bricks-t3139784
In a nutshell, MTK Droid tools don't even talk to the working Fire properly, so it's unlikely they'd help with a bricked one ...
Click to expand...
Click to collapse
So MTK tools does talk but from what I gather it is looking for /proc/dumchar_info which contains the partition structure. This is used to create the scatter file that would allow us to push the firmware back. This file is non-existent. I tried to find some alternate way to build a scatter file but am coming up short and without it we can't really do anything using SP Flash...
Also tried looking into /proc/mtd for info but that file is basically blank. Not sure if Amazon is storing the partition information somewhere else or maybe its hard coded into a chip?
If anybody has any ideas, I have the working devices and can try pulling stuff but I am stumped atm
---------- Post added at 12:28 PM ---------- Previous post was at 12:24 PM ----------
bibikalka said:
The best deal is of course to capture the 5.1.1 update file. I am eager to try it, provided I get root with requires installing via TWRP.
Click to expand...
Click to collapse
We were replying at the same time. I don't think a 5.1.1 file is going to help us on the bricked devices. Once bricked, the preloader seems to just endlessly loop so we would have no way to get the firmware on the device without using something like SP Flash and a scatter file (which eludes me atm)
Theoretically if we have the scatter file I think we should be able to use our 5.0.1 file and restore, then upgrade to 5.1.1 (or stay for root and fastboot boot support)
nEUTRon666 said:
So, if i previously installed the google framework and blocked ota like most people did, this won't block the ota really ?
Click to expand...
Click to collapse
What makes you say that? No one who did that has reported it updating.

Categories

Resources