Hello,
First off, I've gone through the forums and I have looked up other posts and despite everything I cannot figure out how to get my nexus 7 tablet to be recognized by the computer (I tried and after two days of searching for answers I decided to make a post). I like to include this information so people don't assume that I post without browsing or haven't tried anything yet.
The thing that I am having troubles with is that I have a nexus 7 tablet that is softbricked, I have already gone through a lot of ways to fix that problem (I found the best solution is this:http://forum.xda-developers.com/showthread.php?t=1809195). However, the issue is is that I cannot get my computer to recognize the nexus tablet to flash it and restore it back to factory settings.
I have installed and updated the device drivers on my computer, but still I have had no such luck. I found that ADB doesn't recognize the device whilst in the Bootloader, but still will not recognize the device in recovery mode. If anyone has any tips, or suggestions that might work PLEASE let me know, at this point I'm getting desperate and any/all help would be greatly appreciated!
Thank you!
NecroGi said:
Hello,
First off, I've gone through the forums and I have looked up other posts and despite everything I cannot figure out how to get my nexus 7 tablet to be recognized by the computer (I tried and after two days of searching for answers I decided to make a post). I like to include this information so people don't assume that I post without browsing or haven't tried anything yet.
The thing that I am having troubles with is that I have a nexus 7 tablet that is softbricked, I have already gone through a lot of ways to fix that problem (I found the best solution is this:http://forum.xda-developers.com/showthread.php?t=1809195). However, the issue is is that I cannot get my computer to recognize the nexus tablet to flash it and restore it back to factory settings.
I have installed and updated the device drivers on my computer, but still I have had no such luck. I found that ADB doesn't recognize the device whilst in the Bootloader, but still will not recognize the device in recovery mode. If anyone has any tips, or suggestions that might work PLEASE let me know, at this point I'm getting desperate and any/all help would be greatly appreciated!
Thank you!
Click to expand...
Click to collapse
adb is not designed to be usable in bootloader mode. You need fastboot for that. If you have the fastboot.exe program in the same folder as your adb stuff, try this:
fastboot devices
If it reads, then all you need to do is fastboot flash the various .img files back to the tablet. There are tool kits that do this for you, but I prefer doing it manually as there are less chances of things messing up and if they do, you're more likely to know at what step which could be useful for further troubleshooting if need be. It is important to download the correct img files due to differences between the generations and wifi / data enabled ones. There is a flash-all script that you can find in the download of the factory images, which might make it easier, but you can just manually flash the separate files as sometimes you don't need to bother with them all (like the bootloader) though if the script works, then it'll be fine and might make it easier if you are not familiar with the commands.
If you don't have fastboot at all, just grab it from here: http://forum.xda-developers.com/showthread.php?t=2317790
Nexus img files: https://developers.google.com/android/nexus/images
Hit me up on Hangouts if you need more direction.
NecroGi said:
Hello,
First off, I've gone through the forums and I have looked up other posts and despite everything I cannot figure out how to get my nexus 7 tablet to be recognized by the computer (I tried and after two days of searching for answers I decided to make a post). I like to include this information so people don't assume that I post without browsing or haven't tried anything yet.
The thing that I am having troubles with is that I have a nexus 7 tablet that is softbricked, I have already gone through a lot of ways to fix that problem (I found the best solution is this:http://forum.xda-developers.com/showthread.php?t=1809195). However, the issue is is that I cannot get my computer to recognize the nexus tablet to flash it and restore it back to factory settings.
I have installed and updated the device drivers on my computer, but still I have had no such luck. I found that ADB doesn't recognize the device whilst in the Bootloader, but still will not recognize the device in recovery mode. If anyone has any tips, or suggestions that might work PLEASE let me know, at this point I'm getting desperate and any/all help would be greatly appreciated!
Thank you!
Click to expand...
Click to collapse
You won't get adb in bootloader mode.
You have to use the fastboot command.
Please tell the OS on your computer.
Use the tool in my signature as an environment.
Download 7zip, and install that.
Then go here and download the proper image for your device.
It would either be "Factory Images "nakasi" for Nexus 7 (Wi-Fi)" or "Factory Images "nakasig" for Nexus 7 (Mobile)".
Grab the 4.4.2 version.
Extract the downloaded file with 7zip into the "Work" folder in the tool form my signature.
Then extract that "nakasig-kot49h-factory-83d93b5f.tar" file with 7zip.
Then go into the folder that came out of that, and extract the "image-nakasig-kot49h.zip" into the Work folder.
And enter the following commands while in bootloader.
Code:
fastboot oem unlock
fastboot erase userdata
fastboot erase system
fastboot erase recovery
fastboot erase cache
cd nakasig-kot49h
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
Make SURE you grab the correct image for your device. Wifi or Mobile.
I also assume that you know the .img files should be in the Work folder before you type thse commands into my tool.
Hey guys, first of all thank you for the speedy replies and steps I should follow.
Right now I'm using OSX but for the tablet I'm using a virtual Win7 machine to try and get this damn tablet to be recognized by the computer. The process is being delayed a little bit because my micro USB cords are being temperamental, meaning that the tablet has no juice, and when I mess with it (using the power + volume buttons to boot to bootloader/recover) the cord comes unplugged. I know automatically you guys are going to pinpoint this as the source of the issue (mainly because I would too), but it works fine if just laid flat and stays connected. It just has zero charge so when it disconnects/reconnects I literally have to power it back up, just need to wait for it to have some charge before I tinker with it more.
I will post updates after it charges.
Although I already thanked you guys, thanks again for speedy reply. It's much appreciated.
NecroGi said:
Hey guys, first of all thank you for the speedy replies and steps I should follow.
Right now I'm using OSX but for the tablet I'm using a virtual Win7 machine to try and get this damn tablet to be recognized by the computer. The process is being delayed a little bit because my micro USB cords are being temperamental, meaning that the tablet has no juice, and when I mess with it (using the power + volume buttons to boot to bootloader/recover) the cord comes unplugged. I know automatically you guys are going to pinpoint this as the source of the issue (mainly because I would too), but it works fine if just laid flat and stays connected. It just has zero charge so when it disconnects/reconnects I literally have to power it back up, just need to wait for it to have some charge before I tinker with it more.
I will post updates after it charges.
Although I already thanked you guys, thanks again for speedy reply. It's much appreciated.
Click to expand...
Click to collapse
I suggest to STOP!!!
If you are trying to restore the device and the cable disconnects in the middle of it, it might not be recoverable. That would be one of the few ways to really damage the tablet as they are pretty difficult to hard brick. Don't half ass it with stuff like this. A good cable is not THAT much and will certainly be cheaper than a new tablet or getting it to a point where you might have to send it somewhere for service.
I'm not familiar with Macs, but if you are more so, then this might be better than using a Virtual set up:
https://code.google.com/p/adb-fastboot-install/
es0tericcha0s said:
I suggest to STOP!!!
If you are trying to restore the device and the cable disconnects in the middle of it, it might not be recoverable. That would be one of the few ways to really damage the tablet as they are pretty difficult to hard brick. Don't half ass it with stuff like this. A good cable is not THAT much and will certainly be cheaper than a new tablet or getting it to a point where you might have to send it somewhere for service.
I'm not familiar with Macs, but if you are more so, then this might be better than using a Virtual set up:
Click to expand...
Click to collapse
It's actually working fine now (in the sense that the computer can now read it). The Virtual Machine also works just as good, but for some reason the toolkit I'm using won't properly return the tablet to the stock image using the SkipSoft Android ToolKit, so I'm going to have to try and find another way.
Thanks for your guys' help.
Related
Im faily new to the android world. please forgive me of any stupid questions that i may ask.
I was trying to reinstall a new version of maximus 7 on my htc one .
i had the CM 10 installed and was having wifi issues. read that i should clear data and what not and instead of doing a factory reset....i did a format...
now i have no rom on the phone and cant figure out how to do this.
ill upload a video on what i currently have going on...
when i plug it in to the computer...i head the noise from the computer saying that it connected..but nothing popped up.
please help.
heres the youtube video of whats going on with the phone. take a look and suggest any fixes . thanks.
youtube.com/watch?v=NCSJPpLuQiE
adb sideload. you should search this thread there are many that will help you
i searched what i could. didnt find much because im not familiar with terms much.
andrey64 said:
i searched what i could. didnt find much because im not familiar with terms much.
Click to expand...
Click to collapse
you should download all in one toolkit and use the sideload feature. read the on screen directions as you go through the process and you should have no problems
I also ran into a similar predicament a few days ago. I found adb push to be much easier than sideload. Make sure that your drivers and adb is installed on your PC (I assume Windows). In recovery mode, plug phone into USB and your PC should detect the phone but you won't be able to see phone contents; mine made a connection sound.
Then open a command prompt and type: adb push ROM.zip /data/media/ROM.zip
Rom.zip is the rom file that you want to flash, which should be in the same folder as adb. For the path, I used "/data/media" because the custom recovery defaults to that but you may be able to use "/sdcard" as well.
Then flash the rom using recovery
Hi guys,
Wondering if anyone here has the know how to help.
Im fiddling with some new Kobo arcs, the 7HD and the 10HD and im having some bother with installing a custom recovery img.
For simplicity sake im going to refer to them as the same device as they are both behaving the same way
The device is rooted, and I am able to flash a custom recovery made by Jenkins builder but its not functional, when you boot to the recovery OS it just goes black and the back light flashes on an off (screen remains black it just lightens up)
At this point I can reboot as normal and adb to it and flash the original recovery img and all is well.
As far as I can tell its bootloader is unlocked but there might be a second bootloader im not able to interact with yet, possible called uboot?
From adb I am able to reboot the device in to bootloader and fastboot and both function as id expect, but the problem im having is booting directly to fastboot in case I bugger something up which would allow me to fix it.
I can boot the device in to a "mode" that tries to install an APX device, ive tried using various adb, fastboot, and composite drivers and nothing seems to work, ive downloaded some old NVidia APX tegra 2 drivers ive found but these fail to work with the NVFlash utility that comes with it, it says unknown device found, which would make sense given the utility is at least 3 years old
So firstly,
Does anyone know what might course the customer recovery rom to fail and yet flash like it is doing, if so any suggestions where to start to look for a solution?
Secondly,
Does anyone know much about this APX mode and how to actually put it to good use the driver appears to work and communicate but im needing something desktop wise to talk to it...?
hope you guys can help
edit
ive answered some of question 2 myself, it appears its a pain in the arse by all accounts and not as user friendly as I was hoping, I can send commands to it but it appears that commands may need to be "signed" of sorts as I don't get any response other than acknowledgment of the command sent, ill monitor the USB traffic and see if that sheds some light, it also appears that NVflash (not to be confused with its cousin in the GPU arena) is also hopelessly out of date and once again Linux is needed to get something more updated, if there is ANY help at all id appreciate some input
D
dazza9075 said:
Hi guys,
Wondering if anyone here has the know how to help.
Im fiddling with some new Kobo arcs, the 7HD and the 10HD and im having some bother with installing a custom recovery img.
For simplicity sake im going to refer to them as the same device as they are both behaving the same way
The device is rooted, and I am able to flash a custom recovery made by Jenkins builder but its not functional, when you boot to the recovery OS it just goes black and the back light flashes on an off (screen remains black it just lightens up)
At this point I can reboot as normal and adb to it and flash the original recovery img and all is well.
As far as I can tell its bootloader is unlocked but there might be a second bootloader im not able to interact with yet, possible called uboot?
From adb I am able to reboot the device in to bootloader and fastboot and both function as id expect, but the problem im having is booting directly to fastboot in case I bugger something up which would allow me to fix it.
I can boot the device in to a "mode" that tries to install an APX device, ive tried using various adb, fastboot, and composite drivers and nothing seems to work, ive downloaded some old NVidia APX tegra 2 drivers ive found but these fail to work with the NVFlash utility that comes with it, it says unknown device found, which would make sense given the utility is at least 3 years old
So firstly,
Does anyone know what might course the customer recovery rom to fail and yet flash like it is doing, if so any suggestions where to start to look for a solution?
Secondly,
Does anyone know much about this APX mode and how to actually put it to good use the driver appears to work and communicate but im needing something desktop wise to talk to it...?
hope you guys can help
edit
ive answered some of question 2 myself, it appears its a pain in the arse by all accounts and not as user friendly as I was hoping, I can send commands to it but it appears that commands may need to be "signed" of sorts as I don't get any response other than acknowledgment of the command sent, ill monitor the USB traffic and see if that sheds some light, it also appears that NVflash (not to be confused with its cousin in the GPU arena) is also hopelessly out of date and once again Linux is needed to get something more updated, if there is ANY help at all id appreciate some input
D
Click to expand...
Click to collapse
I know this is old, but how did you flash the original recovery? I think I need to do this so that I can install the update ZIP for the Kobo 10. CWM is failing to install the file.
Recently, actually the day after getting a phone, it broke, somehow, while using king root, and I need to fix it quick as possible. Is it possible to flash a new rom onto a phone using the chromebook I have. I need to know quick before I get in trouble.:crying:
H4ck3rz said:
Recently, actually the day after getting a phone, it broke, somehow, while using king root, and I need to fix it quick as possible. Is it possible to flash a new rom onto a phone using the chromebook I have. I need to know quick before I get in trouble.:crying:
Click to expand...
Click to collapse
Hello H4ck3rz,
I have recently purchased a Samsung Chromebook Plus and I also recently got a Nexus 6. I have been looking into how to use fastboot in order to root and rom my Nexus. I have found some promising info on the subject:
I first found this XDA Article that gives more of an overview on enabling ADB and Fastboot on Chrome OS
https://www.xda-developers.com/guide-to-enable-adb-and-fastboot-on-chromeos/
That article refers to an actual XDA guide (tutorial thread) at the very end:
https://forum.xda-developers.com/showthread.php?p=38232908#post38232908
I've read through them both and they seem pretty straight forward. It helps to have a bit of command line knowledge, but the commands used are clear in the instructions.
There is a section in the tutorial that links back to the Chromium Project site where you'll have to find your specific device to learn how to get into developer mode (assuming you don't already know).
NOTE: I have not tried this yet, but I am 100% sure I am going to at some point soon. Probably some time this weekend. After I go through it, I will post again to let you know how it went, if you want to wait to hear about results before you try it.
Hope this helps.
Rk.
Update: I decided I to work on this last night and from the beginning I had problems. TL;DR - adb and fastboot are already part of the developer mode system on my Chromebook Plus. So the need to follow those guides isn't necessary for me.
I was not, however, able to do anything to my Nexus 6 from my Chromebook. Since the Plus only has USB Type-C ports, I bought a USB Type-C to Micro USB cord, but the Nexus wasn't being recognized properly. adb devices returned "????????????" devices, and I didn't get anything with fastboot. I can only surmise that it is the cord, because on my windows laptop, adb and fastboot work flawlessly while my Nexus 6 was connected with the included sync cable.
I'll post again if have more info to share. Sorry I couldn't be of more help.
Rk
rkwarner2 said:
Hello H4ck3rz,
I have recently purchased a Samsung Chromebook Plus and I also recently got a Nexus 6. I have been looking into how to use fastboot in order to root and rom my Nexus. I have found some promising info on the subject:
I first found this XDA Article that gives more of an overview on enabling ADB and Fastboot on Chrome OS
https://www.xda-developers.com/guide-to-enable-adb-and-fastboot-on-chromeos/
That article refers to an actual XDA guide (tutorial thread) at the very end:
https://forum.xda-developers.com/showthread.php?p=38232908#post38232908
I've read through them both and they seem pretty straight forward. It helps to have a bit of command line knowledge, but the commands used are clear in the instructions.
There is a section in the tutorial that links back to the Chromium Project site where you'll have to find your specific device to learn how to get into developer mode (assuming you don't already know).
NOTE: I have not tried this yet, but I am 100% sure I am going to at some point soon. Probably some time this weekend. After I go through it, I will post again to let you know how it went, if you want to wait to hear about results before you try it.
Hope this helps.
Rk.
Click to expand...
Click to collapse
Thanks for this! I can't find my windows laptop and all I have to use now is a Chromebook that does not have adb or fastboot installed. I followed the links and tutorials you shared and was able to install chroot (linux), install adb and fastboot on that linux, and then finally use it to load my phone into fastboot and flash TWRP on my nexus 5. You saved me so much trouble!
i3uu said:
Thanks for this! I can't find my windows laptop and all I have to use now is a Chromebook that does not have adb or fastboot installed. I followed the links and tutorials you shared and was able to install chroot (linux), install adb and fastboot on that linux, and then finally use it to load my phone into fastboot and flash TWRP on my nexus 5. You saved me so much trouble!
Click to expand...
Click to collapse
can you please help me. when I enter 'sudo adb devices' the device is seen. but it says unauthorized. Can you help me with a a step by step write up. I want to flash Android P on to my Pixel 2 XL.
Thanks
Please help, Kindle HDX 8.9 (3rd Generation).
Kindle is stuck on fastboot
@draxie it seemed like you know a lot about the kindle fire hdx model,
from a completely noobish point of knowing absolutely nothing about adb, sideloading, twrp any of that
I had attempted to use flashify to uh, boot a ubuntu.img
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en
https://dl.xda-developers.com/thumbs/3/7/9/9/0/7/2/3799072.jpg
above image copied from another thread, showing the image that is displayed on my kindle when I try to turn it on now.
I called into Amazon tech support.
But, that didn't work. they suggested leaving the tablet on the charger for a good 1 hour then called me back, still on the same screen.
Before I was going to attempt restore to factory defaults, I wanted check back here to see if I could get some help before I decide to wipe it.
If I could get some step by step instructions on how to fix it I would greatly appreciate it!
Please help, thanks in advance.
Really desperate here.. :/
Whats happens when you connect the tablet on a PC? First of all , you need check if you can get ADB Conectivity, using Minimal ADB and Fastboot, before that, install Kindle Fire Drivers
https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982
After driver installation, download ADB and read how it works (super easy if you pay atention) to check if possible recover your tablet using some comands , read about that and wait for Draxie reponse or Davey126 to get correct instructions.
Here's a case similar to you (stuck in Fastboot) but dont take it as solution, becasue every single brick isnt the same, and you could need other method
https://forum.xda-developers.com/ki...stuck-fastboot-kidnle-hdx-8-9-apollo-t3667492
Yousucks2 said:
Whats happens when you connect the tablet on a PC? First of all , you need check if you can get ADB Conectivity, using Minimal ADB and Fastboot, before that, install Kindle Fire Drivers
https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982
After driver installation, download ADB and read how it works (super easy if you pay atention) to check if possible recover your tablet using some comands , read about that and wait for Draxie reponse or Davey126 to get correct instructions.
Here's a case similar to you (stuck in Fastboot) but dont take it as solution, becasue every single brick isnt the same, and you could need other method
https://forum.xda-developers.com/ki...stuck-fastboot-kidnle-hdx-8-9-apollo-t3667492
Click to expand...
Click to collapse
You are in a world of hurt. It's possible (likely) the device can be recovered but not without considerable effort and (probably) many failed attempts. Such assistance is beyond what can reasonably be provided via the forums. You can browse through HDX threads to get the gist of what needs to happen. If you are a technology/Android noob it will probably be easier to pick up a refurb at an auction site. Good luck.
PM for support is normally ignored
joltpodcast03 said:
Please help, Kindle HDX 8.9 (3rd Generation).
Kindle is stuck on fastboot
@draxie it seemed like you know a lot about the kindle fire hdx model,
from a completely noobish point of knowing absolutely nothing about adb, sideloading, twrp any of that
I had attempted to use flashify to uh, boot a ubuntu.img
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en
https://dl.xda-developers.com/thumbs/3/7/9/9/0/7/2/3799072.jpg
above image copied from another thread, showing the image that is displayed on my kindle when I try to turn it on now.
I called into Amazon tech support.
But, that didn't work. they suggested leaving the tablet on the charger for a good 1 hour then called me back, still on the same screen.
Before I was going to attempt restore to factory defaults, I wanted check back here to see if I could get some help before I decide to wipe it.
If I could get some step by step instructions on how to fix it I would greatly appreciate it!
Please help, thanks in advance.
Click to expand...
Click to collapse
If you have fastboot working, your device should be recoverable.
The steps to take depend largely on your definition of "fix it"...
What host platform (i.e. Windows, MacOS, Linux) and variant
are you using BTW? Can you communicate with the device
using the fastboot command?
draxie said:
If you have fastboot working, your device should be recoverable.
The steps to take depend largely on your definition of "fix it"...
What host platform (i.e. Windows, MacOS, Linux) and variant
are you using BTW? Can you communicate with the device
using the fastboot command?
Click to expand...
Click to collapse
If it's fixable, it's worth fixing for me.
@draxie I have a Mac OS for a computer, I'm able to hook up a virtual machine if I need Linux. (Thanks again for the timely response to).
If I plug my machine into my computer and attempt to access its storage with the android tool that it mentions when you plug it in. I was able to access its storage before this happened, (factory provided cable), (just talking about accessing downloads).
It's bricked!?
How do I use fast boot commands?
And don't I need to make a special cord for it?
I have tons of micro USB to USB cords laying around to.
Do your homework...
joltpodcast03 said:
If it's fixable, it's worth fixing for me.
@draxie I have a Mac OS for a computer, I'm able to hook up a virtual machine if I need Linux. (Thanks again for the timely response to).
If I plug my machine into my computer and attempt to access its storage with the android tool that it mentions when you plug it in. I was able to access its storage before this happened, (factory provided cable), (just talking about accessing downloads).
It's bricked!?
How do I use fast boot commands?
And don't I need to make a special cord for it?
I have tons of micro USB to USB cords laying around to.
Click to expand...
Click to collapse
As I said, if fastboot works, it's fixable (in other words, it's not a brick).
BUT, you'll have to find one of the million guides on how to setup and
use fastboot all by yourself. That's not something I'm willing to spend
time on. Sorry...
As for cables, unless the device is a soft-brick, you don't need a special
cable, but it's preferable to use your factory cable not random junk.
BUT, seeing that you have MacOS, my 1-Click tool _should_ work for you.
Then, all you need to do is click through a web-UI. If you want to do that
instead, you'll have to wait though, because I need to iron out a wrink or
two, and haven't had the time the last week or so...
Do you have the drivers installed ? Its the first step, you need it because ADB program needs recognize a device to work , without that, its useless
Before continue, i reccomend you use windows , the tools provided to get ADB and Unlock bootloader, are simplier for beginners, with linux you need some commands input skills
Second = Install ADB from the link i posted or search it on google "ADB And Minimal Fastboot" dont take more than a seconds
And read please, without your cooperation, i think no one have the time and patience to guide you on a step by step instructions (assuming youre on a tech forum and you need a minimun knowledge before ask/do something)
If you get ADB Connection :aka conect your tablet to your PC using USB Cable ,run ADB (prefer as admin) and this show some device connected (you dont need put some command to get connection)
From my ignorance (Fortunately i do two succesfull bootloader unlocks without brick my devices) i think you screwed the original boot, thats why your tablet starts directly to fastboot mode, if you can get ADB connection, its possible unlock it or reapair, but again, you need know how to input the codes, come back when you post the results about ADB State and read abouthow works ADB before proceed to help you
Yousucks2 said:
Do you have the drivers installed ? Its the first step, you need it because ADB program needs recognize a device to work , without that, its useless
Before continue, i reccomend you use windows , the tools provided to get ADB and Unlock bootloader, are simplier for beginners, with linux you need some commands input skills
Second = Install ADB from the link i posted or search it on google "ADB And Minimal Fastboot" dont take more than a seconds
And read please, without your cooperation, i think no one have the time and patience to guide you on a step by step instructions (assuming youre on a tech forum and you need a minimun knowledge before ask/do something)
If you get ADB Connection :aka conect your tablet to your PC using USB Cable ,run ADB (prefer as admin) and this show some device connected (you dont need put some command to get connection)
From my ignorance (Fortunately i do two succesfull bootloader unlocks without brick my devices) i think you screwed the original boot, thats why your tablet starts directly to fastboot mode, if you can get ADB connection, its possible unlock it or reapair, but again, you need know how to input the codes, come back when you post the results about ADB State and read abouthow works ADB before proceed to help you
Click to expand...
Click to collapse
Technically not ADB if working in fastboot but guidance is still 100% relevant.
fastboot commands?
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).