I used the almighty wipe feature of safesortrap and now i have no zips on the device, no way to put them on it, i tried adb push, sideload,etc. i do have a fastboot cable, although when it is plugged in to the fastboot cable, it wont turn on at all. my computer recognizes it as an unknown
device in safestrap, troubleshooting doesnt work. I have the OS I need, I just need a way of getting it onto the device. Any help is greatly appreciated! c: NOTE: 3rd gen kindle fire hdx 7. Also, is it possible when it is unbricked to unlock the bootloader in this situation?
Depends on the Fire OS version you had installed. Only versions below x.3.2.4 are unlockable (i.e. 3.2.3.2 or lower). Note that you can NOT downgrade below 3.2.8 once 3.2.8 or higher have been installed! Attempt would brick the device, thanks to rollback protection by amazon.
Which Safestrap version do you have installed, and what did you wipe?
Cl4ncy said:
Depends on the Fire OS version you had installed. Only versions below x.3.2.4 are unlockable (i.e. 3.2.3.2 or lower). Note that you can NOT downgrade below 3.2.8 once 3.2.8 or higher have been installed! Attempt would brick the device, thanks to rollback protection by amazon.
Which Safestrap version do you have installed, and what did you wipe?
Click to expand...
Click to collapse
I have Safestrap v4.01 and i wiped dalvik,data,cache, and system(im an idiot, i know lol). I had 4.5.2 installed, so no BL unlock.
InfiniteSpace said:
I have Safestrap v4.01 and i wiped dalvik,data,cache, and system(im an idiot, i know lol). I had 4.5.2 installed, so no BL unlock.
Click to expand...
Click to collapse
Don't be so quick, Safestrap v4 has a built-in System-wipe-protection, could've helped here.
Stay away from amazon's stock recovery! Using it with Safestrap installed will brick the device!
Try to get adb access, I think there's a thread somewhere here where a user was able to get access and to revive the HDX. May be the PDA drivers help regarding that. If not, try the original amazon drivers again.
Also try different USB cables, the HDX is surprisingly picky regarding cables. Fastboot cables won't work anyway btw.
You mean the PDANET drivers?
Nvm found it, trying this
I have adb access, i think it was the cable and im a noob, thank you for your time!
Kindle Fire THOR Black Screen wont connect to ADB
Okay so long long story short- my daughter has a kindle fire HD 7 inch version 3rd generation tablet. I did root it a while back and thought I had disabled the updates. However she accidentally so how allowed the updates and duringt the process it went black screen and wont boot or do anything at all. I have read countless forums and tried almost all the un-bricking tools out there as well as the commands in ADB. Currently what I have concluded is that the tools and typical un-bricking methods wont work since the tablet will not power on it wont connect to the computer in ADB mode and I have no idea if its in USB debugging mode at this time.
It will sorta power on (screen still blank- by holding the power button for 20 secs) and the computer "senses" it but at that point it will not be recognized by the PC, and give the error that the "USB device has malfunctioned". I have tried about everything out there- can you guys help me out to get the power back on at least where I can get the ADB to recognize the device? Thanks in advance.
Oh- I did purchase a fastboot cable as well but that did not help matters at all.....
Amazon: "3ft Fastboot Factory Cable For Motorola Unbrick Droid Xoom Fire by Atomic Market"
Athruz
Athruz said:
Okay so long long story short- my daughter has a kindle fire HD 7 inch version 3rd generation tablet. I did root it a while back and thought I had disabled the updates. However she accidentally so how allowed the updates and duringt the process it went black screen and wont boot or do anything at all. I have read countless forums and tried almost all the un-bricking tools out there as well as the commands in ADB. Currently what I have concluded is that the tools and typical un-bricking methods wont work since the tablet will not power on it wont connect to the computer in ADB mode and I have no idea if its in USB debugging mode at this time.
It will sorta power on (screen still blank- by holding the power button for 20 secs) and the computer "senses" it but at that point it will not be recognized by the PC, and give the error that the "USB device has malfunctioned". I have tried about everything out there- can you guys help me out to get the power back on at least where I can get the ADB to recognize the device? Thanks in advance.
Oh- I did purchase a fastboot cable as well but that did not help matters at all.....
Amazon: "3ft Fastboot Factory Cable For Motorola Unbrick Droid Xoom Fire by Atomic Market"
Athruz
Click to expand...
Click to collapse
You mentioned "THOR" in the title later expanding that to "HD 7". They are two distinctly different devices. For the purpose of this post I'll assume you are referincing a 3rd gen HDX 7 device (Thor). Unfortunately nothing can be done short of board replacement which is not cost effective given the current price point of pre-owned devices in good condition. As you probably read fastboot/factory cables are useless on HDX models which is the only way to communicate with an otherwise comatose device. Sorry for your daughter's loss. Poke around action sites like eBay; I have seen supposedly new 16GB HDX 7's going for $50-60 USD. If you daughter is younger a 5th gen 7" fire is a good alternative as it can be rooted and with several quality custom ROMs available you FireOS is not to you/her liking.
Thanks
Davey126 said:
You mentioned "THOR" in the title later expanding that to "HD 7". They are two distinctly different devices. For the purpose of this post I'll assume you are referincing a 3rd gen HDX 7 device (Thor). Unfortunately nothing can be done short of board replacement which is not cost effective given the current price point of pre-owned devices in good condition. As you probably read fastboot/factory cables are useless on HDX models which is the only way to communicate with an otherwise comatose device. Sorry for your daughter's loss. Poke around action sites like eBay; I have seen supposedly new 16GB HDX 7's going for $50-60 USD. If you daughter is younger a 5th gen 7" fire is a good alternative as it can be rooted and with several quality custom ROMs available you FireOS is not to you/her liking.
Click to expand...
Click to collapse
Thank you very much for the info - I was suspecting that unfortunately.
Question
Apologies, to hasty in getting a question onto the forums
Related
I installed twrp on my kindle 8.9, then i installed a couple of roms onto it. It worked just perfect. That until i got bored of the CM and i wanted to get back to the original OS. I followed the instructions on this site : //androidcowboy.com/2013/06/how-to-return-kindle-fire-hd-to-stock// , and then it got stuck to the static white/orange boot screen. I tried several restore softwares like kfhd, kffa, kindle unbrick, utilities and then i got the redscreen. After that i searched the internet and everyone adviced me to use either the kfhd uility or the kffa, and then BOOM, the device won't turn on.
I read that i could do the shorting trick, but nobody tried that. Is my kindle bricked for good, or do I still have any hope?
Have you tried holding the power button down for 30 seconds, releasing, then trying to boot?
Sent from my KFAPWI using xda app-developers app
MoisoiuMihai said:
I installed twrp on my kindle 8.9, then i installed a couple of roms onto it. It worked just perfect. That until i got bored of the CM and i wanted to get back to the original OS. I followed the instructions on this site : //androidcowboy.com/2013/06/how-to-return-kindle-fire-hd-to-stock// , and then it got stuck to the static white/orange boot screen. I tried several restore softwares like kfhd, kffa, kindle unbrick, utilities and then i got the redscreen. After that i searched the internet and everyone adviced me to use either the kfhd uility or the kffa, and then BOOM, the device won't turn on.
I read that i could do the shorting trick, but nobody tried that. Is my kindle bricked for good, or do I still have any hope?
Click to expand...
Click to collapse
First & foremost, you say you did this on a "Kindle Fire HD 8.9". Is this correct? If so, you are in the WRONG forum. This is for the NEW Kindle model, called the HDX.
If you do something for the HDX on the HD you will likely make the situation much worse. If you truly are on the OLDER Kindle Fire HD, then you can ALMOST ALWAYS recover using fastboot, but that will require either buying or making a factory fastboot cable.
GSLEON3 said:
First & foremost, you say you did this on a "Kindle Fire HD 8.9". Is this correct? If so, you are in the WRONG forum. This is for the NEW Kindle model, called the HDX.
If you do something for the HDX on the HD you will likely make the situation much worse. If you truly are on the OLDER Kindle Fire HD, then you can ALMOST ALWAYS recover using fastboot, but that will require either buying or making a factory fastboot cable.
Click to expand...
Click to collapse
Yes, i have the 8.9 hd model not the hdx. I tried holding the power button for 30 sec/ 1min , but it didn't work. And i don't know if any recovery/fastboot cable could help me, the device won't even turn on. Also, im sorry for misplacing this thread, but by any chance, does anyone know what should i start with? Maybe an older thread or anything.
MoisoiuMihai said:
Yes, i have the 8.9 hd model not the hdx. I tried holding the power button for 30 sec/ 1min , but it didn't work. And i don't know if any recovery/fastboot cable could help me, the device won't even turn on. Also, im sorry for misplacing this thread, but by any chance, does anyone know what should i start with? Maybe an older thread or anything.
Click to expand...
Click to collapse
Here is where you should start. http://forum.xda-developers.com/kindle-fire-hd
As I have BOTH the HD 8.9 & the HDX 8.9, I can tell you that a factory fastboot cable would likely work. It allows you to flash over adb, like other normal Android devices. At any rate, there are several threads & tools available in the forums I linked above that should help to get you going again.
Hi everyone,
I bought HDX 7 just 2 months ago. I was on 4.5.2 and last week i requested amazon to downgrade my device and they allowed me to downgrade to 3.2.8. Then I rooted it using Towelroot and used Safestrap bootloader to install Nexus 2.0.3 ( For Kindle Device).After completion of Installation of Nexus ROM (ZIP file) from safestrap, device restarted and just hanged on some NEXUS logo and could not start up. But after some manual force restarts the safestrap was replaced by normal Kindle bootloader and finally NEXUS 2.0.3 was able to load. But i could not use some Google apps therefore In order to install Gapps I tried to flash TWRP 2.3.3.0 with Flashify i bricked the device. The device just hangs on KINDLE FIRE logo and dont show any response to PC and cant be able to move in Fastboot mode or bootloader mode.
Is there any thing i could do at this moment or should i ask amazon for replacement?
Thanks !!!
marshhhh said:
Hi everyone,
I bought HDX 7 just 2 months ago. I was on 4.5.2 and last week i requested amazon to downgrade my device and they allowed me to downgrade to 3.2.8. Then I rooted it using Towelroot and used Safestrap bootloader to install Nexus 2.0.3 ( For Kindle Device).After completion of Installation of Nexus ROM (ZIP file) from safestrap, device restarted and just hanged on some NEXUS logo and could not start up. But after some manual force restarts the safestrap was replaced by normal Kindle bootloader and finally NEXUS 2.0.3 was able to load. But i could not use some Google apps therefore In order to install Gapps I tried to flash TWRP 2.3.3.0 with Flashify i bricked the device. The device just hangs on KINDLE FIRE logo and dont show any response to PC and cant be able to move in Fastboot mode or bootloader mode.
Is there any thing i could do at this moment or should i ask amazon for replacement?
Thanks !!!
Click to expand...
Click to collapse
Yeah, HDX is a finicky device. Looks like you may have skipped a few critical prerequisites (eg: NEXUS 2.0.3 not guaranteed to run w/Safestrap; TWRP is not compatible with 3.2.8) but that's water under the bridge. Flashing stock recovery is your first step IMHO but if you can't see your device via tether then you are pretty much hosed.
Should you seek a replacement Amazon will likely provide a refurbished unit given you are outside the 30-day return window. There have been reports of refurbished units coming with older firmware that that can be exploited (bootloader unlock) which will permit TWRP, Nexus and other ROMs to be installed. You'll need to do some reading to explore your options.
Davey126 said:
Yeah, HDX is a finicky device. Looks like you may have skipped a few critical prerequisites (eg: NEXUS 2.0.3 not guaranteed to run w/Safestrap; TWRP is not compatible with 3.2.8) but that's water under the bridge. Flashing stock recovery is your first step IMHO but if you can't see your device via tether then you are pretty much hosed.
Should you seek a replacement Amazon will likely provide a refurbished unit given you are outside the 30-day return window. There have been reports of refurbished units coming with older firmware that that can be exploited (bootloader unlock) which will permit TWRP, Nexus and other ROMs to be installed. You'll need to do some reading to explore your options.
Click to expand...
Click to collapse
Ja, its true because of more excitation and some laziness i escaped some important things to know. Anyway learned something.
I just called amazon and the conversation was like this.
Me: My device hanged on Kindle fire logo. what shall i do?
Amazon: since when ?
Me: Yesterday
Amazon: is that device rooted?
Me: No
Amazon: But I can see that it was rooted using some apps. and you asked for downgrade 2 days ago.
Me: I tried but i was not able to do so, But i had this problem when i did factory reset. ( It was a lie )
Amazon: Ok. Did you drop the device or was it in water before you had this problem.
Me: No No
Amazon: Ok then it should be defect. so send it to us. Thanks
But I am not sure whether they will replace it.
Amazon (at least in the US) will likely make some type of accommodation to keep you happy; they are good that way. Keep us posted!
marshhhh said:
Ja, its true because of more excitation and some laziness i escaped some important things to know. Anyway learned something.
I just called amazon and the conversation was like this.
Me: My device hanged on Kindle fire logo. what shall i do?
Amazon: since when ?
Me: Yesterday
Amazon: is that device rooted?
Me: No
Amazon: But I can see that it was rooted using some apps. and you asked for downgrade 2 days ago.
Me: I tried but i was not able to do so, But i had this problem when i did factory reset. ( It was a lie )
Amazon: Ok. Did you drop the device or was it in water before you had this problem.
Me: No No
Amazon: Ok then it should be defect. so send it to us. Thanks
But I am not sure whether they will replace it.
Click to expand...
Click to collapse
Davey126 said:
Amazon (at least in the US) will likely make some type of accommodation to keep you happy; they are good that way. Keep us posted!
Click to expand...
Click to collapse
Ya, i just got a mail from amazon and it says that my new device will be in front of my door in 3 days. Actually amazon are willing to have a good relationship with their customers. Impressive...
Good eveing-
I'm not sure where to start. I have a kindle fire HDX 7, and just attempted to root the device yesterday. I was able to roll back to 3.2.8, then upgrade to 4.5.2 and successfully root the device. Everything was good.
I then toyed around with a few methods to install GAPPS. With each method, if I didn't achieve the desired results, I would factory reset, rollback to 3.2.8, upgrade to 4.5.2, root... etc. A process which I went through 3 or 4 times just to try and get access to the google play store. The final method was to use the steps layed out In This Thread, which is where my current problem started.
I was not able to get the play store working correctly. I then attempted to do a factory reset, and **** hit the fan. Upon reboot, I was greeted by the stock android welcome screen, asking me to select a language, and giving me the option to make an emergency call. My best guess is something in the "system" folders/files in the gapps zip doesn't jive with FireOS. From the provided setup screen, I am able to select a language and hit next, and then it takes me through to the FireOS wireless setup screen - and that's where things come to a halt. The process won't advance, the device is somewhat functional.. I can pull down the menu from the top, I can infact authenticate to wireless, I can fully access settings, I made a MAYDAY call... But I cannot get to a home screen. In theory - I believe this to be a "soft brick" as it doesn't do anything.. Though the operating system, is running.
I was toying around in ADB trying to get it to push the 3.2.8 bin image to /storage/emulated/0/, but it wasn't cooperating. After doing some research, I came to the conclusion that the stock USB cable won't work, and I need to order a Fastboot cable? Any truth to this?
I'm just looking for some direction here if anyone has any advice. Amazon said they won't replace it - so I'm kinda stuck at this point.
Any help is much appreciated!
http://forum.xda-developers.com/showpost.php?p=59186495&postcount=9
Hi - thank you for that link. Am I to take one of the Kindle setup bin's and rename it to an apk?
Just a little vague on the instructions.
NM - I'm following it now.. Didn't realize someone else had my problem. Hoping this works - will tune back once confirmed!
You saved my kindle - thank you!
Hi, I need your help PZ.
positivehxcgo said:
You saved my kindle - thank you!
Click to expand...
Click to collapse
I have same problem like you. so Follow OnyXis's thread but not solve the problem.
May i ask you a Q? how did you solve this problem? PZ. show me instruction....
thankyou!! have a nice day~
positivehxcgo said:
[Excerpt] ... I was toying around in ADB trying to get it to push the 3.2.8 bin image to /storage/emulated/0/, but it wasn't cooperating. After doing some research, I came to the conclusion that the stock USB cable won't work, and I need to order a Fastboot cable? Any truth to this?
Click to expand...
Click to collapse
For anyone who stumbles upon this post ...
Cables DO make a difference but a 'fastboot' cable is not necessarily the solution. HDX models do not respond to fastboot cables in the same way most other android devices do; they are effectively useless on this device for recovery purposes. However, a crappy cable can create all sorts of havoc, both with data transfer and charging. Whenever a tether isn't working as expected one of the first troubleshooting steps is to switch cables. Visually it is hard to tell the difference between a good/bad cable so you may have to go through a few. Fastboot cables are generally constructed to higher standards which may fool some HDX users into thinking that was the solution. More likely any high-quality USB cable would have done the trick.
I have solved this problem.
cjdfyd2 said:
I have same problem like you. so Follow OnyXis's thread but not solve the problem.
May i ask you a Q? how did you solve this problem? PZ. show me instruction....
thankyou!! have a nice day~
Click to expand...
Click to collapse
Follow Onyxis´s thread but not skip mark ´ and after rebooting you must skip wifi connect
And then u show start stable welcome display connect wifi. that´s all thankyou onyxis and who interest my problem have a nice day
Hello everyone,
I've been tinkering with my kindle attempting to flash TWRP so I could flash other ROMs on my Kindle Fire HDX 7 (3rd generation) but I have seemed to soft brick the device after using unlock.bat from https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982/post70881555#post70881555
The unlock.bat was supposed to unlock my bootloader, but now the device won't power on. If I plug it into the windows a bunch of partitions appear and windows prompts me if I want to format the various drives. If I plug my kindle into Linux, the 7 (i think) partitions show folders various different system functions.
Someone wrote in a separate forum that it's possible to restore kindle if I using something called eMMC Raw tool, but didn't really give any clear instructions.
If anyone could help me recover my device, that would be greatly appreciated. Thank you.
For some reason I can't upload a picture of the various files in the partition.
Side note: could I theoretically put CM 12 or anything else on one of the partitions instead of the stock ROM?
Praxxer1 said:
Hello everyone,
I've been tinkering with my kindle attempting to flash TWRP so I could flash other ROMs on my Kindle Fire HDX 7 (3rd generation) but I have seemed to soft brick the device after using unlock.bat from https://forum.xda-developers.com/ki...r-firmware-t3463982/post70881555#post70881555
The unlock.bat was supposed to unlock my bootloader, but now the device won't power on. If I plug it into the windows a bunch of partitions appear and windows prompts me if I want to format the various drives. If I plug my kindle into Linux, the 7 (i think) partitions show folders various different system functions.
Someone wrote in a separate forum that it's possible to restore kindle if I using something called eMMC Raw tool, but didn't really give any clear instructions.
If anyone could help me recover my device, that would be greatly appreciated. Thank you.
Click to expand...
Click to collapse
Unlock.bat did not "soft brick" your device as the actions it performs are totally benign. More likely you got sloppy and flashed an incompatible aboot (via dd) or erased aboot and don't know how to recover. Me thinks it is the latter. Keep reading; you'll eventually stumble on posts that describe corrective actions. I will edit this post with a link as time permits.
You do not need "eMMC Raw Tool" whatever that is.
edit: https://forum.xda-developers.com/ki...ing-bootloader-firmware-t3463982/post75284993
Davey126 said:
Unlock.bat did not "soft brick" your device as the actions it performs are totally benign. More likely you got sloppy and flashed an incompatible aboot (via dd) or erased aboot and don't know how to recover. Me thinks it is the latter. Keep reading; you'll eventually stumble on posts that describe corrective actions. I will edit this post with a link as time permits.
You do not need "eMMC Raw Tool" whatever that is.
edit: https://forum.xda-developers.com/ki...ing-bootloader-firmware-t3463982/post75284993
Click to expand...
Click to collapse
Ah. I wish I had seen that thread before I started the process! You may be right about the compatible boot. I couldn't find the original aboot_vuln.mbn file mentioned in the thread I was following, but managed to find aboot.img file and flashed that hoping it was the same. I could have sworn though, that the device stopped working the second after I clicked the unlock.bat file (executed outside the fastboot screen), but could be wrong.
Only problem about the thread you linked, device isn't responding to any ADB or fastboot commands, but still shows that my PC recognizes the device as a fire device.
Thank you for your time, I'll keep reading through the thread you linked.
Praxxer1 said:
Only problem about the thread you linked, device isn't responding to any ADB or fastboot commands, but still shows that my PC recognizes the device as a fire device.
Click to expand...
Click to collapse
Likely a Windows driver issue. Suggest installing Motorola Device Manager here which includes composite USB drivers that work reliably with HDX devices. Need need to run MDM; just install it. After connecting the device you will need update the driver via Windows Device Manager. Bit of hit and miss with a non-functioning device. Cables and USB ports also play a huge role, especially with fussy bootloader/fastboot communications. Avoid external hubs, USB3 ports and add-on expansion cards. Change cables, ports, etc. Good luck.
Davey126 said:
Likely a Windows driver issue. Suggest installing Motorola Device Manager here which includes composite USB drivers that work reliably with HDX devices. Need need to run MDM; just install it. After connecting the device you will need update the driver via Windows Device Manager. Bit of hit and miss with a non-functioning device. Cables and USB ports also play a huge role, especially with fussy bootloader/fastboot communications. Avoid external hubs, USB3 ports and add-on expansion cards. Change cables, ports, etc. Good luck.
Click to expand...
Click to collapse
Thanks Davey, I'll definitely give it a try. Just as a bit more information on my situation, the device manager on windows does read Fire Device "ADB composite driver". I also have it connected to the PC using a Fastboot Cable. I will give all of this a try when I get home from work today.
If I am able to communicate with the device after installing the MDM drivers, should I attempt to restore the device? Or try to unlock and flash the stock ROM?
Praxxer1 said:
Thanks Davey, I'll definitely give it a try. Just as a bit more information on my situation, the device manager on windows does read Fire Device "ADB composite driver". I also have it connected to the PC using a Fastboot Cable. I will give all of this a try when I get home from work today.
If I am able to communicate with the device after installing the MDM drivers, should I attempt to restore the device? Or try to unlock and flash the stock ROM?
Click to expand...
Click to collapse
- dump the fastboot cable (all but useless on a HDX); this isn't a generic Android device
- ADB composite drivers come in many flavors; HDX bootloader only likes a few of them
- if/when you reestablish communication first step is to restore aboot and install TWRP; unlocking and ROM installation come later
- do not attempt to reinstall stock; frustration and heartache consume those who do
- again, this is not a run-of-the-mill Android gizmo; many of the tricks you learned in kindergarden do not apply to Amazon tablets
Davey126 said:
- dump the fastboot cable (all but useless on a HDX); this isn't a generic Android device
- ADB composite drivers come in many flavors; HDX bootloader only likes a few of them
- if/when you reestablish communication first step is to restore aboot and install TWRP; unlocking and ROM installation come later
- do not attempt to reinstall stock; frustration and heartache consume those who do
- again, this is not a run-of-the-mill Android gizmo; many of the tricks you learned in kindergarden do not apply to Amazon tablets
Click to expand...
Click to collapse
Lol I feel like I'm in kindergarten tinkering with this HDX. How do I restore aboot? clearly the image I flashed with was not the correct bootloader. Should I attempt to extract aboot from the stock ROM? Or would you be able to share you tool set/point me to a working link for aboot, TWRP, and ROMs (I've looked at 4 threads so far without working links)?
UPDATE: I managed to install the ADB MOT Composite driver, but still no response to simple ADB and Fastboot commands
Thanks again
Praxxer1 said:
Lol I feel like I'm in kindergarten tinkering with this HDX. How do I restore aboot? clearly the image I flashed with was not the correct bootloader. Should I attempt to extract aboot from the stock ROM? Or would you be able to share you tool set/point me to a working link for aboot, TWRP, and ROMs (I've looked at 4 threads so far without working links)?
UPDATE: I managed to install the ADB MOT Composite driver, but still no response to simple ADB and Fastboot commands
Thanks again
Click to expand...
Click to collapse
Not uncommon. Unfortunately, there is no 'fix script' moving forward as each situation is unique. If aboot is too damaged to support basic communication it's pretty much game over for the average laymen. You will need to comb the threads for information nuggets that may apply to your situation. Or cut your losses and move on. I am not big on trying to unbrick these pups unless one well versed in low level trouble shooting. Lousy ROI; has to be a labor of love including copious time researching, trying and (likely) failing. Good luck.
@draxie - for awareness; read back a few posts for context.
1-Click is your friend
Davey126 said:
Not uncommon. Unfortunately, there is no 'fix script' moving forward as each situation is unique. If aboot is too damaged to support basic communication it's pretty much game over for the average laymen. You will need to comb the threads for information nuggets that may apply to your situation. Or cut your losses and move on. I am not big on trying to unbrick these pups unless one well versed in low level trouble shooting. Lousy ROI; has to be a labor of love including copious time researching, trying and (likely) failing. Good luck.
@draxie - for awareness; read back a few posts for context.
Click to expand...
Click to collapse
Right... the symptoms described are the normal state of affairs
after 'fastboot erase aboot' and 'unlock.bat' does no such thing.
The post linked above and/or my original "Bulk mode" post both
have the necessary instructions to recover. Alternatively, 1-Click
can handle this, assuming access to either MacOS or Linux (for
the time being).
hello,
my hdx 7inch "thor" I believe is stuck and bricked.
It was on an old firmware that was rootable with towelroot, and it was towelrooted with supersu installed. no safestrap, no custom rom, no twrp, no bootloader unlock. I was aware of the issue of this tablet so I never really mess with it. well until I handed this to my relative and she tried to do a factory reset in the settings to set up her own amazon account.
when I connect it to my laptop and tried adb I get either device offline or unathorized.
let me know if it's not unbrickable, so I will accept the loss.
thanks
supaet said:
hello,
my hdx 7inch "thor" I believe is stuck and bricked.
It was on an old firmware that was rootable with towelroot, and it was towelrooted with supersu installed. no safestrap, no custom rom, no twrp, no bootloader unlock. I was aware of the issue of this tablet so I never really mess with it. well until I handed this to my relative and she tried to do a factory reset in the settings to set up her own amazon account.
when I connect it to my laptop and tried adb I get either device offline or unathorized.
let me know if it's not unbrickable, so I will accept the loss.
thanks
Click to expand...
Click to collapse
Should be able to revive it via 1-click. But it will take some work.
https://forum.xda-developers.com/kindle-fire-hdx/general/multi-platform-1-click-bootloader-t3241014