BRICKED Amazon Fire HD 10 (2019) Tablet - HELP? =) - Fire HD 8 and HD 10 Q&A, Help & Troubleshooting

I have used TWRP and recovered a few tablets before so i'm familiar with the process. However my friend gave me this Fire HD 10 tablet and the amazon splash screen just cycles through a 10 second reboot loop. Holding down Volume UP and the Power button does nothing, i am unable to access TWRP or even the original recovery tool. I then held the Volume button DOWN with the power button and the adb recovery does not appear. The device just keep rebooting no matter the combo of buttons i hold down.
Anyway to recover this device?

You need to open the device, and short the pins to get into preloader. Use the TWRP Thread and download gptfix and run it, after that short again and do bootrom-step.sh then continue the process to reinstall TWRP from there.
Hope this helps! From my own experience. This happened to me when messing with the partition table!

I appreciate your reply, however is there an instruction guide to show how to do this? i have a heat gun but not the best or most patient when it comes to opening these devices, my track record is sub par at best =)

Related

Stuck on Google logo boot screen -- Bricked??

I unlocked the bootloader and flashed a custom recovery. I then rebooted the device. Now it is stuck at the bootloader (white Google logo on black background) and I can't get it to do anything else. I've rebooted it a bunch of times including with the vol + and vol - buttons held down to no avail. I've also let the battery run out and then tried to boot it up again and the same thing happens. adb nor fastboot see the device and it doesn't show up in the logs on my machine (Mint 13) as coming online at any time.
Most of the times I reboot it with the power switch it reboots to the Google logo even without me letting go of the power button. Sometimes I can get it to fully power off but I haven't figured out what combination of vol keys and reboot does that.
Anyone have any ideas what could be wrong? Any help would be much appreciated!
You are not bricked if you can still get into the bootloader.
Download the factory image from here, and flash it with fastboot. If you don't know how to do that, read this thread.
I wish I could get fastboot to see it then I could definitively flash that img.
I can't get into the bootloader and can't get fastboot or adb to see it. It's stuck at the Google logo now and when i hold the power key it reboots back to the Google logo with the unlock logo at the bottom.
Thanks for the help
You've tried holding volume down+power for 10+ seconds? That should power off the device, then hold both vol up+down down and power up
Ya I've tried to hold vol + and power for 10+ seconds and it reboots back to the Google logo even if I don't off the power key. Same happens with all the other combinations of keys being held with the power button. I can't get it to turn off now unless I let the battery die
Press and hold power till screen goes black. Then quickly press power+volume down and HOLD.
Sent from my Nexus 7
Tried that and still stuck at the Google logo. I have to go to work for a couple hours and then will hack on it when I'm back. Hope I don't have to deal with Googles rma process seeing how disorganized the rest of that company is
Sent from my HTC one s
No luck with any button combos but the vol + and power actually turned it off. All out of ideas over here. I'm thinking it really is bricked
I'm in the same spot. I can get it into recovery occasionally but once there it locks up after trying to flash or clear the cache.
I'm wondering if a contributing issue is CMR v6.0.0.6? I updated it from 6.0.0.4 that was running fine. But no fastboot or adb so that is doubtful.
This is frustrating and not a great start with this N7.
thank you
giveen said:
Press and hold power till screen goes black. Then quickly press power+volume down and HOLD.
Sent from my Nexus 7
Click to expand...
Click to collapse
this worked. you have to be fast. as soon as screen goes black release power button then quickly, very quickly repress along with vol up and down.
You will still be able to get into the bootloader! Force kill the tablet by holding the power button for ages. Then hold volume up and volume down and the power button together, which will boot to fastboot.
It looks like a CWM bug as I feared. Anyone in the same boat try here - http://forum.xda-developers.com/showthread.php?t=1782932
Nothing has worked and I've literally tried everything that those three buttons can do. Thanks again for all the help guys. Had a great time trying to resurrect it but guess it's time for it to go back home
Just as I suspected. Google puts out buggy junk once again.
I just wanted to report a similarly event. I have a rooted, unlocked Nexus 7, with TWRP recovery. I have previously rebooted without issue. Tonight I booted into bootloader mode to check something and the hit power button to choose start. I got stuck on the boot logo. After finding this thread, I started with the simplest combination and held power button until screen went dark, then added volume down and once again in bootloader. This time choosing start led to a regular system boot. It's as if the device froze and needed a hard reboot.
Sent from my SCH-I535 using Tapatalk 2
I was attempting to boot into recovery and kept getting the 'Google' logo (I am unlocked/rooted with twrp recovery). I wasn't aware that one had to be plugged in via usb in order to *not* hang....
Any way around this?
Once I plugged it in and attempted to boot into recovery it worked fine.
I had a similar issue after using the Nexus Root Toolkit to flash to nakasi 4.2 with CWM recovery - just got stuck on the nexus boot screen, flashing in a loop for over 15 minutes.
I ended up powering down the device, holding power for about 5-10 seconds - then QUICKLY holding both the power and volume up+down keys, it then went into the fastboot screen.
After it was there, plugged it into my PC.
Now, this should work for you - assuming you have all the fastboot/usb driver stuff installed.
I extracted the contents of nakasi-jop40c-factory-6aabb391.tgz into the same directory as the fastboot.exe provided by WugFresh with his Nexus Root Toolkit (google search or xda search for this if you dont have it, i dont think i can post links due to my low postcount) - typical filepath: C:\Program Files (x86)\WugFresh Development\data
By the files in there, I mean drilling down inside the tgz to where the image files were inside so that files like bootloader-grouper-4.13.img, image-nakasi-jop40c.zip etc were extracted into the directory and sitting alongside the fastboot.exe - NOT in a subfolder.
Once its all here, running flash-all.bat (this is provided by google in the nakasi-jop40c-factory-6aabb391.tgz) from the command line or by double clicking on it from explorer should kick off the process. After about 2-3 minutes, it was complete, and my Nexus then booted up within about 3 minutes after that.
Also worth noting, device remained unlocked, but I lost root/root binary

[Q] Possible Brick?

Hey all, requesting some assistance...
I had used the nexus 7 toolkit to unlock the bootloader and root my tablet.
Earlier this afternoon, I decided to cave and flash cm10 on my tablet. Before doing so, instructions stated to wipe. In my ignorance, I wiped one too many things and also wiped the internal memory.
As a result, I am unable to get my tablet to fastboot and when I searched for the .zip to flash, I was presented with an ominously empty file directory to my sdcard's root. I have tried various things with the nexus 7 toolkit and have been unsuccessful in my endeavors, as many of those functions require the tablet to be in fastboot mode before any of them will work.
The device is stuck on the Google screen, and if I push the volume buttons with the power button, it will flicker and eventually return to this screen.
I do have a nandroid backup stored on my machine, but I am unable to use it as I am unable to even boot to the recovery (because I can't get to fastboot)... Any suggestions? I really hope I didn't brick this...
I believe you can get to fastboot mode with the v4.13 bootloader from any other mode so long as the battery is not dead and the screen is working.
When the battery has a good charge, hold the power button down until the google logo appears (could be up to 15-18 seconds). At that very moment that the black-and-white google logo image appears, press the Vol-down button.
Voila. Fastboot.
You do need to see that screen appear though; maybe that's the rub. Note that the timing is important - you only get one second or two to do this immediately after the image first appears.
As a bonus, glance at the bottom of that image. Shows an unlocked padlock for an unlocked bootloader, nothing if locked.
It worked! Thanks a bunch!
qwertyx7 said:
It worked! Thanks a bunch!
Click to expand...
Click to collapse
No worries. Glad it worked. Actually, I only stumbled across a reference to that button sequence a couple days ago.
If you see someone else reporting that they "can't get to fastboot", let them know - you can get there from ANY MODE.
[REF] Nexus 7 Button Combinations
Don't be this guy...

N7 (tilapia) stuck at logo - no fastboot access ...

Hello everybody,
I hope somebody can help me to save my N7 (2012).
I installed TWRP without problems and after that I tried to flash a custom rom - which, for some reasons, didn't work.
After reboot my Nexus is stuck at Google logo with an opened lock at bottom...
I can't get to fastboot because when I power on while pushing VOL - button it just get stuck at the same logo screen.
If I keep power button pressed for about 10s, it shuts down but after a few seconds it boots again just to get stuck again at the logo screen...
The only way to shut it down completely is to keep VOL+ button pressed while pressing the power button.
My Windows 7 computer won't recognize the N7 at all anymore, but when I shut it down completely (Power & VOL+), windows says "Unknown device".
Is my Nexus still to be saved or I can throw it away?
Thank you in advance for each advice.
Conrad
Conrad-007 said:
Hello everybody,
I hope somebody can help me to save my N7 (2012).
I installed TWRP without problems and after that I tried to flash a custom rom - which, for some reasons, didn't work.
After reboot my Nexus is stuck at Google logo with an opened lock at bottom...
I can't get to fastboot because when I power on while pushing VOL - button it just get stuck at the same logo screen.
If I keep power button pressed for about 10s, it shuts down but after a few seconds it boots again just to get stuck again at the logo screen...
The only way to shut it down completely is to keep VOL+ button pressed while pressing the power button.
My Windows 7 computer won't recognize the N7 at all anymore, but when I shut it down completely (Power & VOL+), windows says "Unknown device".
Is my Nexus still to be saved or I can throw it away?
Thank you in advance for each advice.
Conrad
Click to expand...
Click to collapse
Hi, Conrad-007...
This is very strange - your Nexus 7 is clearly 'bootable' (sort of), with a functioning bootloader, ie., it's not hardbricked... or you wouldn't be seeing the Google logo.
In the distant past, back when I used to experiment with custom kernels on my Nexus 7, it sometimes required the POWER BUTTON+VOL DOWN buttons be pressed and held down for a good 30 seconds or more, to generate the necessary 'interrupt', and force the device into the bootloader.
My first instinct, is to suggest you may possibly have a problem with your VOL DOWN button, and maybe it's stuck somehow or not making contact.
It also occurred to me, that you might be able to access the bootloader with...
Code:
adb reboot bootloader
...or possibly...
Code:
adb reboot fastboot
...and even...
Code:
adb reboot recovery
But unfortunately, I'm pretty sure you need to be running fully booted Android or booted into a custom recovery (eg., TWRP) before you can issue ADB commands. I haven't tinkered around in this area of Android for a couple of years now, so my memory of the specifics is a little hazy.
Anyhow, here's a fairly comprehensive listing of Nexus 7 button presses/interrupts, which maybe of some use...
https://forum.xda-developers.com/showthread.php?p=37606945#post37606945
--------------------------------
Anyway, just some thoughts that might give you some clues/ideas, that may resolve your problem.
Good luck, and I hope you find something that works.
Rgrds,
Ged.
Thanks Ged for the detailed answer.
Unfortunately it seems that my Nexus is not booting complete (not finishing the booting sequence due to corrupted bootloader?) and so I cannot send to it any adb or fastboot command...
I read in the meantime that holding the VOL up button while powering up the Nexus, it will bring it in the APX mode (whatever this mean) and indeed, my computer recognize it as "APX" device.
I hope at least that this is a good sign and a first step to bring my Nexus back to life... but I have no idea what is the APX mode and what can I do in this mode to attempt to save my device...
Do you (or somebody else) have (has) an advice or tutorial for me concerning this?
Regards,
Conrad
Hi Conrad.
I'm in exactly the same situation (I've mistakenly posted a duplicate thread here https://forum.xda-developers.com/nexus-7/general/bricked-tilapia-t4005149). Let's continue here. So:
1. I spent 4 hours trying all possible button press combinations, including VERY long presses. I didn't notice any APX device or Uknown device connected to Windows. I might have missed it, you gave me hope. I will check again.
2. APX mode enables low level access to the chipset via nVidia tool nvflash. You probably came accross these threads here on xda:
https://forum.xda-developers.com/nexus-7/general/tutorial-how-to-unbrick-nexus-7-using-t3342364
https://forum.xda-developers.com/showthread.php?t=2564615
https://forum.xda-developers.com/showthread.php?t=2455927
https://forum.xda-developers.com/showthread.php?t=2340237
I haven't so far, as I was not aware of the visibilty of the tablet in Windows. I will check again.
Well, I must have been blind not to have seen all the posts here on xda and everywhere else. I went through the threads and now I know:
1. I can see the tablet in APX mode in Windows. Possibly I could correctly set up the driver.
2. This would be totally useless, since I hadn't backed up necessary blob.
I have a new paperweight

New Fire HD 10 2019 no recovery mode?

Is it just me or does the new Fire HD 10 2019 not have a recovery mode? I have owned a ton of android devices and know how to get into recovery (hold power down and volume up or down depending on model). Anyways when I try to hardware go into recover or go into recover via the toolbox, all I get is a black screen with the white triangle and exclamation mark for a minute then reboots. There is no recovery mode? Is this correct or do I have a defective unit?
Thanks
hotstocks said:
Is it just me or does the new Fire HD 10 2019 not have a recovery mode? I have owned a ton of android devices and know how to get into recovery (hold power down and volume up or down depending on model). Anyways when I try to hardware go into recover or go into recover via the toolbox, all I get is a black screen with the white triangle and exclamation mark for a minute then reboots. There is no recovery mode? Is this correct or do I have a defective unit?
Thanks
Click to expand...
Click to collapse
Interesting - my sample behaves the same way. Not sure I'm going to keep it so unwilling to tinker further. I suspect recovery is there somewhere, just not accessible via traditional means.
Edit - answered here: https://forum.xda-developers.com/hd...d-10-2019-recovery-mode-t4017503/post81158755
hotstocks said:
Is it just me or does the new Fire HD 10 2019 not have a recovery mode? I have owned a ton of android devices and know how to get into recovery (hold power down and volume up or down depending on model). Anyways when I try to hardware go into recover or go into recover via the toolbox, all I get is a black screen with the white triangle and exclamation mark for a minute then reboots. There is no recovery mode? Is this correct or do I have a defective unit?
Thanks
Click to expand...
Click to collapse
Can install TWRP custom recovery (needs to unlock/crack bootloader)
Hold down power button and volume down or try ADB
Code:
adb reboot recovery
AmznUser444 Dev said:
Can install TWRP custom recovery (needs to unlock/crack bootloader)
Hold down power button and volume down or try ADB
Code:
adb reboot recovery
Click to expand...
Click to collapse
There is no Bootloader hack, therefore TWRP can't exist for new hd10, what are you trying to do is to reboot device into bootloader (fastboot mode), which won't give any results. If neither toolbox or hardware methods are working, there's a chance that it's hidden, or just uses different combinations, like connecting a usb c to tablet and then pressing buttons, or any other thing, there are many possibilities, i guess we just have to wait
https://forum.xda-developers.com/showpost.php?p=81024051&postcount=88
Can you explain EXACTLY how and when to press each button after the triangle? And when to let go of each button. I just can't get it to go into recovery or get past that first triangle.
hold the power button and tap volume up from that screen with the triangle and exclamation point to access the menu.... very limited menu though...
I am trying these methods and its working fine
https://hardreset.one/how-to-hard-reset-amazon-fire-hd-10-2019/

Rooting Fire HD 8 (kamak) 6.3.1.2 - Bricked

Hi together,
thanks especially to xyz` and k4y0z for your effort and your contributions! This is amazing!
I have an Amazon Fire HD 8 (karnak) with FireOS 6.3.1.2 which I want to root, unlock and install LineageOS on.
With 6.3.0.0 on another tablet, I already performed this procedure successfully.
As k4y0z writes in https://forum.xda-developers.com/hd...nlock-fire-hd-8-2018-karnak-amonet-3-t3963496 that a hardware-change in combination with the soft-brick method could lead to a real brick rendering the device unusable, I went for the hardware method.
What I did:
1. Disconnect tablet
2. Run "bootrom-step.sh"
3. Shorten CLK to GND and at the same time connect the tablet to USB
4. I get the message to remove the short and confirm with ENTER
--> flashing occurs and I find myself in fastboot mode (the tablet also shows up when I do a "fastboot devices")
5. Run "fastboot-step.sh"
--> flashing of recovery and misc occurs, followed by a reboot
Then I see the "Amazon" logo flashing shortly and then the screen stays black. I tried pressing power and the volume-keys shortly, twice, for a long time, ... nothing happens.
If I disconnect and reconnect USB I see the "Amazon" logo flashing again. The device is not in fastboot mode, ("fastboot devices" shows no device) nor is it in adb mode ("adb devices" also shows no device).
Luckily the steps below can be performed again and the flash procedure happens again so I can always get into fastboot mode but then I'm stuck flashing the TWRP with the fastboot-step.sh...
I tried the files from karnak-3.0, karnak-3.0.1 as well as the original amonet-v2, all with the same issue.
Can anybody please shed some light here? What am I doing wrong? Is there anything else I can try or is the tablet unusable now (which I cannot believe as there is fastboot access).
I am in fact running Debian 10 on a VirtualBox on my MacBook with USB forwarding to the Virtual Machine but I'm not sure if that can be the issue as all the flashes are working just fine.
Thanks for your support!
How old is the tablet? Anything bought January or newer is potential unlock-blocked....
Thanks for your answer, Michajin.
The tablet was bought in February 2020. Does that mean I'm out of luck getting LineageOS to run on this tablet?
Would the error I am seeing fit the unlock-block? I had the feeling that all the installing went through just fine, just TWRP is not loaded correctly, right?
Thanks!
Michajin said:
How old is the tablet? Anything bought January or newer is potential unlock-blocked....
Click to expand...
Click to collapse
freddy40 said:
Thanks for your answer, Michajin.
The tablet was bought in February 2020. Does that mean I'm out of luck getting LineageOS to run on this tablet?
Would the error I am seeing fit the unlock-block? I had the feeling that all the installing went through just fine, just TWRP is not loaded correctly, right?
Thanks!
Click to expand...
Click to collapse
If the fastboot-step finishes as success you have TWRP (fastboot step is just the flashing of twrp replacing stock recovery). You should be able to hold the volume down and press the power button, this will boot the device into recovery.
Thanks, Michaejin! That did the trick. Pressing those buttons yesterday didn't help as the tablet was somehow turned on, now I disconnected and reconnected the battery and pressed VolDown + Power and got into TWRP!
Great! Thanks again!
Michajin said:
If the fastboot-step finishes as success you have TWRP (fastboot step is just the flashing of twrp replacing stock recovery). You should be able to hold the volume down and press the power button, this will boot the device into recovery.
Click to expand...
Click to collapse
freddy40 said:
Thanks, Michaejin! That did the trick. Pressing those buttons yesterday didn't help as the tablet was somehow turned on, now I disconnected and reconnected the battery and pressed VolDown + Power and got into TWRP!
Great! Thanks again!
Click to expand...
Click to collapse
You can also hold the power button for about 10 seconds to force a power down, so you should have to pull the cover off in case something goes wrong. Likely the device was stuck in preloader or bootrom.

Categories

Resources