Related
Hi there,
I juste got a cheapo Azpen A729 tablet. I succesfully rooted it with Kingo Root and it was also recognized by ADB. I then tried to boot into bootloader through ADB, but it never when past the Azpen logo screen and since then the tablet is stuck at the that screen whenever I try to restart it. So I'm afraid that I bricked it... On the Azpen website there are firmwares for several of their devices, but not for the A729. Does anyone have experience with this device and maybe some advice? Thanks!
maksmtl said:
Hi there,
I juste got a cheapo Azpen A729 tablet. I succesfully rooted it with Kingo Root and it was also recognized by ADB. I then tried to boot into bootloader through ADB, but it never when past the Azpen logo screen and since then the tablet is stuck at the that screen whenever I try to restart it. So I'm afraid that I bricked it... On the Azpen website there are firmwares for several of their devices, but not for the A729. Does anyone have experience with this device and maybe some advice? Thanks!
Click to expand...
Click to collapse
yes you bricked your device.
you rooted that device, but not unlock dootloader.
Hi,
I just tried to boot into bootloader, not to unlock it or anything else. I simply rooted the device, I didn't try to install any custom recovery (not that there would be one anyway, AFAIK) or anything like that. If I'm missing something here, would you mind to explain? Thanks.
Paget96 said:
yes you bricked your device.
you rooted that device, but not unlock dootloader.
Click to expand...
Click to collapse
maksmtl said:
Hi,
I just tried to boot into bootloader, not to unlock it or anything else. I simply rooted the device, I didn't try to install any custom recovery (not that there would be one anyway, AFAIK) or anything like that. If I'm missing something here, would you mind to explain? Thanks.
Click to expand...
Click to collapse
Ok, I understand
This device have stock recovery???
Yes, everything is stock, the only thing I did was rooting it with Kingo Root, like so: http://forum.xda-developers.com/android/help/root-azpen-a729-t3003908
Unfortunately there isn't much information out there yet for the A729, it seems to be fairly recent. Treecheetahdolo here managed to unbrick his A727, but unfortunately there is no firmware (yet?) available for the A729 on azpens site to try this...
Paget96 said:
Ok, I understand
This device have stock recovery???
Click to expand...
Click to collapse
maksmtl said:
Yes, everything is stock, the only thing I did was rooting it with Kingo Root, like so: http://forum.xda-developers.com/android/help/root-azpen-a729-t3003908
Unfortunately there isn't much information out there yet for the A729, it seems to be fairly recent. Treecheetahdolo here managed to unbrick his A727, but unfortunately there is no firmware (yet?) available for the A729 on azpens site to try this...
Click to expand...
Click to collapse
Go to recovery and wipe data and cache.
I'd like to, but I'm not able to go into recovery unfortunately... It's supposed to be vol-down + power button (http://www.azpenpc.com/service/detail.php/id-9.html), at least for the earlier devices, but this doesn't seem to work here, it always gets to the Azpen logo screen and gets stuck there... I tried every other key combination I could think of, but to no avail. Either the device is seriously bricked, or there's a secret key combination here to go into recovery that azpen didn't communicate...
Paget96 said:
Go to recovery and wipe data and cache.
Click to expand...
Click to collapse
maksmtl said:
I'd like to, but I'm not able to go into recovery unfortunately... It's supposed to be vol-down + power button (http://www.azpenpc.com/service/detail.php/id-9.html), at least for the earlier devices, but this doesn't seem to work here, it always gets to the Azpen logo screen and gets stuck there... I tried every other key combination I could think of, but to no avail. Either the device is seriously bricked, or there's a secret key combination here to go into recovery that azpen didn't communicate...
Click to expand...
Click to collapse
The [Vol- ] [POWER] combo works, but you have to hold them until the unit powers on, (like forever). If it won't go past the Azpen LOGO, I would recommend contacting your local supplier.
Ok, so if, when you boot into recovery, it still passes through the Azpen logo, then there might definitely be a problem... :-/ Mrdownboy, you have a A729, right? Did you already boot into the bootloader at some point? This thing does have a bootloader, right? I contacted Azpen to see if they have a firmware image that I could try to flash, before trying to going through a RMA procedure with my rooted tablet... We'll see. Anyway, thanks!
mrdownboy said:
The [Vol- ] [POWER] combo works, but you have to hold them until the unit powers on, (like forever). If it won't go past the Azpen LOGO, I would recommend contacting your local supplier.
Click to expand...
Click to collapse
maksmtl said:
Ok, so if, when you boot into recovery, it still passes through the Azpen logo, then there might definitely be a problem... :-/ Mrdownboy, you have a A729, right? Did you already boot into the bootloader at some point? This thing does have a bootloader, right? I contacted Azpen to see if they have a firmware image that I could try to flash, before trying to going through a RMA procedure with my rooted tablet... We'll see. Anyway, thanks!
Click to expand...
Click to collapse
Hey maksmtl,
I haven't tried accesing the bootloader yet, I'm still on the process of acquiring another brand new A729 for dumping the ROM and then start from there. I'll call Azpen tomorrow and ask them about a stock fw, but I wouldn't hold my breath. Once I have a stock ROM, I'll start looking into a custom recovery. Baby steps...
---------- Post added at 01:27 PM ---------- Previous post was at 01:22 PM ----------
maksmtl said:
Ok, so if, when you boot into recovery, it still passes through the Azpen logo, then there might definitely be a problem... :-/
Click to expand...
Click to collapse
I don't quite understand what you are saying here... You have to hold [Vol-] [POWER] until the unit powers on, (forever...). Then just sit back and relax. If after 15 mins you're not on recovery, and it's boot-looping, it might need a STOCK ROM re-flash.
Hi mrdownboy,
what I meant is that, I thought that, as with e.g. a Nexus device, when you boot into recovery it directly goes there, without going through the google logo screen first as it would in a normal boot. So I thought/was hoping, that on the Azpen it would do the same thing, not going through the logo screen when booting into recovery. That's why I thought that I didn't have the right key combination, because it would always boot into the azpen logo screen, where it then gets stuck. From what you said, I understood that the azpen still goes through the logo screen first, before going into the recovery menu, or did I misunderstand you here? When I press and hold [Vol-] + [POWER], the device boots directly into the azpen logo screen after 8 seconds or so, after that nothing happens anymore. I also tried to keep holding the buttons after the logo appears, but that doesn't seem to change anything neither, unless you really have to do that for an insanely long time...?
mrdownboy said:
I don't quite understand what you are saying here... You have to hold [Vol-] [POWER] until the unit powers on, (forever...). Then just sit back and relax. If after 15 mins you're not on recovery, and it's boot-looping, it might need a STOCK ROM re-flash.
Click to expand...
Click to collapse
Did you get into recovery?
mrdownboy said:
Did you get into recovery?
Click to expand...
Click to collapse
Nope... But again, just to be sure, since I'm still a bit confused here: when you go into recovery it DOES go through the Azpen logo screen first, right?
I wrote to Azpen as well about a firmware for the A729, since they have firmwares for other models, but I didn't get a response yet. But then again, if if I had a firmware, I'm not even sure if I could flash it with PhoenixUSBPro tool, if the device can't go into recovery, I doubt it can go into download mode... Btw, be careful in your development if you don't want the same thing happening to you when booting into the bootloader... It would be definitely cool to have a custom recovery and eventually cutom ROMS however!
If I can't recover my device I don't even know if I'll try going through a RMA though, since it might be too expensive sending the tablet in, considering its initial cost...
maksmtl said:
Nope... But again, just to be sure, since I'm still a bit confused here: when you go into recovery it DOES go through the Azpen logo screen first, right?
I wrote to Azpen as well about a firmware for the A729, since they have firmwares for other models, but I didn't get a response yet. But then again, if if I had a firmware, I'm not even sure if I could flash it with PhoenixUSBPro tool, if the device can't go into recovery, I doubt it can go into download mode... Btw, be careful in your development if you don't want the same thing happening to you when booting into the bootloader... It would be definitely cool to have a custom recovery and eventually cutom ROMS however!
If I can't recover my device I don't even know if I'll try going through a RMA though, since it might be too expensive sending the tablet in, considering its initial cost...
Click to expand...
Click to collapse
If you call them right now, you'll be surprised how good they are at personal customer service. They WILL offer options, but they don't have the firmware available for public release yet. Is your model the A729BT or the A729 Non-BT? I really want to do a ROM dump, but it's proven way more difficult than I initially thought. If there is a way to dump a ROM w/o rooting it would be excellent.
Also, I don't think they have a bootloader installed.
mrdownboy said:
The [Vol- ] [POWER] combo works, but you have to hold them until the unit powers on, (like forever). If it won't go past the Azpen LOGO, I would recommend contacting your local supplier.
Click to expand...
Click to collapse
That's what they show on their website, but it has not worked for me at all. I've tried repeatedly with vol+ & power, vol- & power, vol+ & vol- & power... nothing has worked, it always boots fully up.
Is yours the A729 with bluetooth from TigerDirect? (their website lists that only the TigerDirect version has Bluetooth)
Were you actually able to get into the stock recovery menu?
---------- Post added at 09:26 PM ---------- Previous post was at 08:42 PM ----------
mrdownboy said:
If you call them right now, you'll be surprised how good they are at personal customer service. They WILL offer options, but they don't have the firmware available for public release yet. Is your model the A729BT or the A729 Non-BT? I really want to do a ROM dump, but it's proven way more difficult than I initially thought. If there is a way to dump a ROM w/o rooting it would be excellent.
Also, I don't think they have a bootloader installed.
Click to expand...
Click to collapse
I called them and I definitely did not find them customer-friendly.
I politely pointed out that the Users menu was missing and as I understand it, it's only an entry in a config file to enable it and asked if it would be possible to get a patch as I bought this for my son and didn't want to have to root it and the guy on the phone cut me off mid-sentence and scolded me for even mentioning rooting the device and told me it'd void my warranty. I asked about the firmware image and he was very dismissive about it. I asked if I could submit a bug report about the fact that a valuable feature of JB 4.2+ was missing (and the fact that this was a tablet that appeared to have a phone build of Android, more below). I'm not even sure how to describe his response "you want to submit a BUG REPORT?!"... yes, I do. He gruffly agreed to take down my request and proceeded to ask me for full contact info (full name, address, email, phone number, etc.). When I asked for the case number, he was confused... they apparently have no bug or complaint tracking system whatsoever. He explained to me that there was no way the developers were going to provide a patch, that Android is open source and it's up to the developers to decide how to configure the builds, etc. After some back and forth, I finally asked him how big the company was. He was obviously taken aback, so I explained that he seemed to know an awful lot about what the developers would be willing to do... he took this as a compliment and explained that I had "called corporate" (I called the support number on their website).
This screams "tiny operation" to me... either this guy was one of the developers (answering the customer support line), one of the main people in the company, or they're simply an importer and order the devices in bulk and resell them with nothing more than a custom logo.
Alibaba lists this unit for "US $1 - 45"... minimum qty 100 units.
More on the build: This device appears to have a default config for a phone, as not only is the Users menu missing, but it has a "Mobile network settings" menu which is entirely non-applicable to a device like this (menu items include "Data roaming", "Preferred network type" (2G/3G), "Network operators", etc.).
I sure hope I caught him on a bad day, and others have better luck.
Oh - and the reason I was reluctant to root it right away was I'm a bit gunshy and wanted to make sure I could return it if I needed to. I recently had a horrid experience with a d2 tablet that bricked itself (black-screen before splash-screen) after a few hours of use on Christmas morning (nearly every review on newegg for the device, all posted after I bought it, had the exact same problem). I'm lucky I was able to send that one back for a refund. Thankfully, this one appears to be a *lot* more reliable a unit (my son has played many, many hours of games on it for the past month).
I talked to the Azpen support, and they told me to push the volume button in the middle (I guess that comes down to the same as pressing vol- and vol+) and the power button. In my case that didn't work, but my tablet seems to be definitely bricked... I have the BT model from TigerDirect.
glabifrons said:
That's what they show on their website, but it has not worked for me at all. I've tried repeatedly with vol+ & power, vol- & power, vol+ & vol- & power... nothing has worked, it always boots fully up.
Is yours the A729 with bluetooth from TigerDirect? (their website lists that only the TigerDirect version has Bluetooth)
Were you actually able to get into the stock recovery menu?
Click to expand...
Click to collapse
maksmtl said:
I talked to the Azpen support, and they told me to push the volume button in the middle (I guess that comes down to the same as pressing vol- and vol+) and the power button. In my case that didn't work, but my tablet seems to be definitely bricked... I have the BT model from TigerDirect.
Click to expand...
Click to collapse
I just tried it again by pressing in the middle (in case there was a 3rd switch) and could feel both the up and down button click, and it booted all the way up (the logo came and went 3 times as it was booting up). I held all three (incl power) buttons down until it had the full Android display up (with the lock slider).
So... sounds like the guy was wrong - even on a fully functional unit, that won't bring up the menu.
It does have a recessed reset button (you can only hit it with a paper-clip or similar). I've seen some devices where you have to hold that down for ridiculous periods of time. I'm surprised the guy didn't mention that.
maksmtl said:
Hi mrdownboy,
what I meant is that, I thought that, as with e.g. a Nexus device, when you boot into recovery it directly goes there, without going through the google logo screen first as it would in a normal boot. So I thought/was hoping, that on the Azpen it would do the same thing, not going through the logo screen when booting into recovery. That's why I thought that I didn't have the right key combination, because it would always boot into the azpen logo screen, where it then gets stuck. From what you said, I understood that the azpen still goes through the logo screen first, before going into the recovery menu, or did I misunderstand you here? When I press and hold [Vol-] + [POWER], the device boots directly into the azpen logo screen after 8 seconds or so, after that nothing happens anymore. I also tried to keep holding the buttons after the logo appears, but that doesn't seem to change anything neither, unless you really have to do that for an insanely long time...?
Click to expand...
Click to collapse
Please don't panic. I've found myself in the same situation with my A729 where key press sequences and back panel reset were to no avail. As a matter of fact, just last night I found myself where you are now. After booting into the bootloader through ADB, my Azpen had that same zomie stare that your's is experiencing.
Here's what I did. I turned it over screen down and walked away. Simply let the battery deplete over night. When you attempt to turn it on tomorrow it will complain of insufficient power. Plug it into your charger for about a half-hour, press and hold down the Volume "UP" button and then press the power button (You've heard this drill before, but THIS time you've given the instrument time to "forget" the last instruction given to it.) Let me know if this time (finally) your Azpen A729 boots into the recovery screen.
Most importantly, don't panic. Let the battery deplete firstly and then attempt the recovery mode.
- PoFolk
Hi PoFolk,
that sounds very promising! My Azpen is draining its battery right now. I actually had a suspicion that the tablet wasn't completely shut off, since every time I plugged in the charger, it would boot into the Azpen screen right away... But I didn't think about letting the battery die to give it a fresh start. Crossing fingers right now...
Oh, and I'm not panicking actually, I was almost expecting some problems with such a cheap tablet. I would probably be panicking more if this was my Nexus 7, which I just gave a new youth through F2FS.
Anyway, I'll let you know how it went tomorrow, thanks! Btw, are you sure about Volume "UP"? That would be new.
PoFolk said:
Please don't panic. I've found myself in the same situation with my A729 where key press sequences and back panel reset were to no avail. As a matter of fact, just last night I found myself where you are now. After booting into the bootloader through ADB, my Azpen had that same zomie stare that your's is experiencing.
Here's what I did. I turned it over screen down and walked away. Simply let the battery deplete over night. When you attempt to turn it on tomorrow it will complain of insufficient power. Plug it into your charger for about a half-hour, press and hold down the Volume "UP" button and then press the power button (You've heard this drill before, but THIS time you've given the instrument time to "forget" the last instruction given to it.) Let me know if this time (finally) your Azpen A729 boots into the recovery screen.
Most importantly, don't panic. Let the battery deplete firstly and then attempt the recovery mode.
- PoFolk
Click to expand...
Click to collapse
Works for me:
1) Depress "UP" volume button throughout this procedure.
2) Depress power button and release when Azpen bootloader logo appears.
3) Sing or hum a tune whilst the Azpen logo stares at you, all whilst you're depressing the volume "UP" button. (yes, it seems like an eternity)
4) Android system recovery screen pops up.
5) Don't try anything fancy just yet. Select "reboot system now".
6) Light up a cigar or draw a beer. Your Azpen should be restored.
Hi. My sons HDX is stuck in fastboot mode. Amazon support only offered him a discount to replace it. I thought maybe I could do something to wake it up or reflash it but from what I'm reading this is a difficult device. I have been able to get it to respond to the fastboot reboot command in linux but nothing else. This device has never been rooted/flashed/modded and I don't know how it got this way. Is there anything I can do at this point besides throw it away?
Thanks.
when you are at the fastboot screen...
press the power button for 10-20 sec. and it will shut down...
than try to power it on again.... (try it with unplugged usb)
maybe this helps...
If possible, I would unlock the bootloader and then try this guide: http://forum.xda-developers.com/showpost.php?p=22077057&postcount=11
This device has never been rooted/flashed/modded and I don't know how it got this way.
Click to expand...
Click to collapse
Just thought this means the HDX is on 4.5.2(3)
thanks for the responses. I have tried rebooting the device many times with or without usb plugged in. I've held the power button for 25 seconds until it starts rebooting again. It always boots to a gray kindle fire logo and says fastboot. I've tried the fastboot -i 0x1949 oem idme bootmode 4000 command but it says the hw is locked. From what Ive read, the bootloader cant be unlocked right?
ianedward said:
From what Ive read, the bootloader cant be unlocked right?
Click to expand...
Click to collapse
Do you recall the firmware level (eg: 3.2.6; 4.5.2)?
Edit: After shutting down (completely off) have you tried power+volume up to access Amazon's crippled recovery? From there you might be able to initiate a factory reset.
i have tried to power it on with different button combinations. I can only get to the same fastboot screen.
oh and I have no idea what firmware it was on.
ianedward said:
i have tried to power it on with different button combinations. I can only get to the same fastboot screen.
oh and I have no idea what firmware it was on.
Click to expand...
Click to collapse
Yeah, it was a long shot. At this point you may be hosed unless someone knows of a way to recover in fastboot given the state of your device (locked, unrooted, version unknown). Might want to try Amazon again. A different rep may be more accommodating. Sorry, mate.
I've been a lurker of this forum for years. I just joined and I've always done my research before posting anything. But I'm at a loss right now and I do not know what to do.
I have a Kindle Fire HDX 7" (Thor), yesterday I was trying to flash an Android ROM on it. I got up to the point where I was in TWRP, and I accidentally factory reset the Kindle thru TWRP. When the Kindle rebooted, it showed a screen that said something like...
"Kindle Fire System Recovery; Your Kindle doesn't seem to be able to boot. Resetting your device to Factory defaults may help you to fix this issue."
The choices it gave me were, "Reboot your Kindle" and "Reset to Factory Defaults"
I rebooted my Kindle as a first choice, and it booted back to the same screen. So then I reset to factory defaults. Nothing worked and it kept bringing me back to that screen. I'm guessing there is no bootloader or anything on the Kindle.
I left the Kindle on for hours as I was trying to find my fastboot cable knowing that I would probably need it to fix this problem. I then turned off the Kindle hours later (press and hold until screen shut off). I did have a full battery prior to trying to put an Android ROM on the Kindle.
This morning I found my fastboot cable, but when I pressed the power button on the Kindle, it will not turn on. No response from it at all. Did I drain the battery?
When I plug my Kindle to my computer using the fastboot cable, it was showing me "QHSUSB_BULK" in the USB device list. I tried ADB, but it says "error: device not found".
When I plug my Kindle to charge, it doesn't show the low battery/charging indicator like it used to.
What should I do next? Is my Kindle permanently bricked?
I need mad help right now!
Try to boot into twrp, but you may bricked your device permanently because you did a factory reset with the default kindle recovery
Sent from my KFTHWI using XDA Free mobile app
MinerBoy004 said:
Try to boot into twrp, but you may bricked your device permanently because you did a factory reset with the default kindle recovery
Sent from my KFTHWI using XDA Free mobile app
Click to expand...
Click to collapse
Okay, one question, how would I boot into TWRP? I ask only because the Kindle is not starting up, and when I plug the fastboot cable, the computer is not recognizing it.
Junava said:
I've been a lurker of this forum for years. I just joined and I've always done my research before posting anything. But I'm at a loss right now and I do not know what to do.
I have a Kindle Fire HDX 7" (Thor), yesterday I was trying to flash an Android ROM on it. I got up to the point where I was in TWRP, and I accidentally factory reset the Kindle thru TWRP. When the Kindle rebooted, it showed a screen that said something like...
"Kindle Fire System Recovery; Your Kindle doesn't seem to be able to boot. Resetting your device to Factory defaults may help you to fix this issue."
The choices it gave me were, "Reboot your Kindle" and "Reset to Factory Defaults"
I rebooted my Kindle as a first choice, and it booted back to the same screen. So then I reset to factory defaults. Nothing worked and it kept bringing me back to that screen. I'm guessing there is no bootloader or anything on the Kindle.
I left the Kindle on for hours as I was trying to find my fastboot cable knowing that I would probably need it to fix this problem. I then turned off the Kindle hours later (press and hold until screen shut off). I did have a full battery prior to trying to put an Android ROM on the Kindle.
This morning I found my fastboot cable, but when I pressed the power button on the Kindle, it will not turn on. No response from it at all. Did I drain the battery?
When I plug my Kindle to my computer using the fastboot cable, it was showing me "QHSUSB_BULK" in the USB device list. I tried ADB, but it says "error: device not found".
When I plug my Kindle to charge, it doesn't show the low battery/charging indicator like it used to.
What should I do next? Is my Kindle permanently bricked?
I need mad help right now!
Click to expand...
Click to collapse
By TWRP you mean safestrap recovery? If you flashed through safestrap other ROM than Nexus for Safestrap 1.0.1 (which one BTW? Did you flash by accident ROM for Hdx 8.9?) that could be the first reason for bricking your kindle... Safestrap is not TWRP, is only TWRP based and works differently than TWRP 2.8.5.0, also safestrap is located on system partition, but TWRP 2.8.5.0 when installed is flashed to recovery partition...
Doing factory reset through safestrap should be relatively safe unless you mess with advanced wipe and delete/wipe system partition - this effectively erase content of /system including safestrap recovery, this could be the second reason for bricking your kindle.
If you had installed real cuber signed TWRP 2.8.x.x, then the only thing I can think of is that you tried to flash one of amazon update bins with TWRP, these bins when installed replace content of the recovery partition with Amazon FireOS recovery, successfully deleting real TWRP in the process, but this should end with booting to FireOS...
Junava said:
Okay, one question, how would I boot into TWRP? I ask only because the Kindle is not starting up, and when I plug the fastboot cable, the computer is not recognizing it.
Click to expand...
Click to collapse
Just hold the volume up button (+) when it's booting.
However, I'm not really sure of your situation, because TWRP should've replaced the stock recovery.
I finally got it to turn on somehow. And this is the screen that it's giving me (see attachment). I tried both of the options given and it'll bring me back to the same screen.
Also, before I was able to power on the Kindle, it'll say QHSUSB BULK in the connected usb devices when I use my fast-food cable on it. But when I have the Kindle powered on it says Unknown Device.
If I can get the Kindle to respond to adb I can probably work from there. But my computer is not recognizing it.
What version of fireos you had? maybe is possible to unlock bootloader.. but you should know mmc manfid and serial. We don't know yet how to get emmc serial from bootloader only.
dpeddi said:
What version of fireos you had? maybe is possible to unlock bootloader.. but you should know mmc manfid and serial. We don't know yet how to get emmc serial from bootloader only.
Click to expand...
Click to collapse
I had to rollback as I was following the guide on the post in the developmental forum on here. Will the manufacturer id be on the box? I still have the original box for the Kindle.
Sent from my VS980 4G using XDA Free mobile app
Actually you can get it from adb without root
My Kindle is not communicating with adb. I've been trying all week and doing a lot of researching. I either get an "Unknown Device" or "QHSUSB BULK" in the connected usb list.
Sent from my VS980 4G using XDA Free mobile app
Dies it go in fastboot mode with vol+ vol- power?
Junava said:
I finally got it to turn on somehow. And this is the screen that it's giving me (see attachment). I tried both of the options given and it'll bring me back to the same screen.
Also, before I was able to power on the Kindle, it'll say QHSUSB BULK in the connected usb devices when I use my fast-food cable on it. But when I have the Kindle powered on it says Unknown Device.
If I can get the Kindle to respond to adb I can probably work from there. But my computer is not recognizing it.
Click to expand...
Click to collapse
How did you get to that screen? do you remember what you pressed?
dpeddi said:
Dies it go in fastboot mode with vol+ vol- power?
Click to expand...
Click to collapse
Nope.
Silverclaw280 said:
How did you get to that screen? do you remember what you pressed?
Click to expand...
Click to collapse
I held the power button for maybe a good 30 seconds and it powered on and took me to that screen. I'd usually have to keep trying to get the Kindle to power on, and when I do, that screen is all it'll do.
Turn kindle off.. then press and keep pressed vol+ and vol- and keep them pressed. Turn on kindle while pressing both volume. You should enter into fastboot. If we found a relation between emmc serial and kindle serial number you should be able to fix it. (I think your boot.img is corrupted)
Silverclaw280 said:
How did you get to that screen? do you remember what you pressed?
Click to expand...
Click to collapse
I was able to get back to that screen by following the steps in this quoted post.
My Kindle gets the same status. It was safestraped, locked on 3.2.8. Tried to update it with OTA to 4.1.1, it downloaded firmware, checked and rebooted, after that device won't boot up and on connect to pc detects as QHSUSB_BULK. The only way i found is to ask replacement at support
modi said:
My Kindle gets the same status. It was safestraped, locked on 3.2.8. Tried to update it with OTA to 4.1.1, it downloaded firmware, checked and rebooted, after that device won't boot up and on connect to pc detects as QHSUSB_BULK. The only way i found is to ask replacement at support
Click to expand...
Click to collapse
(reposting as a warning to those who may stumble across this thread)
This seems to be the recent fate for many who have rolled back to 3.2.8 and not blocked OTA using HDX Toolkit or an equivalent blocker (renaming otacerts is not reliable). It appears Amazon attempts to push an update that ultimately corrupts the boot partition. Not much you can do to fix it with current techniques/exploits.
If the device is still under warranty Amazon will likely replace it. Just say it died during an update.
Help! I have a newer HDX 7 that is stuck trying to reboot. The device powers up to the gray kindle fire screen but sits there for a minute or so and then the screen flashes and it starts all over. The device does not recognize the power button. I've tried the hold the button for 40 seconds to reset but it just keeps going through this loop while holding the power button. When I connected it to my PC (Win7), it does not see the device. If I connect another Andriod device, it sees it imeadiately.
I'm a complete noob with this but I'm actually in IT, just not in this area. This is my sons device so I'm not sure exactly what he was doing at the time it started this but my guess would be playing MineCraft. Amazon's wonderful support says it just needs to be replaced but it's out of warranty. My son and I were just about to start an online coding course so I'd like to get this back up and running so we can start that. Any help would be appreciated. After searching the web, you guys seem to be the only ones able to root or fix any software/os issues with these devices.
Thanks,
Doug
Leav320 said:
Help! I have a newer HDX 7 that is stuck trying to reboot. The device powers up to the gray kindle fire screen but sits there for a minute or so and then the screen flashes and it starts all over. The device does not recognize the power button. I've tried the hold the button for 40 seconds to reset but it just keeps going through this loop while holding the power button. When I connected it to my PC (Win7), it does not see the device. If I connect another Andriod device, it sees it imeadiately.
I'm a complete noob with this but I'm actually in IT, just not in this area. This is my sons device so I'm not sure exactly what he was doing at the time it started this but my guess would be playing MineCraft. Amazon''s wonderful support says it just needs to be replaced but it's out of warranty. My son and I were just about to start an online coding course so I'd like to get this back up and running so we can start that. Any help would be appreciated. After searching the web, you guys seem to be the only ones able to root or fix any software/os issues with these devices.
Thanks,
Doug
Click to expand...
Click to collapse
Your options are limited given the device is largely invisible via tether (even then there would be little recourse as adb is probably disabled). Did you try a factory reset? Amazon's crippled recovery environment can be accessed via power + vol-up from a cold start. Release the power button after the gray Kindle logo appears. If the recovery menu comes up the only option is 'factory reset'. I realize you may not be able to access recovery given the non-responsive power button.
Any chance you son is old/savvy enough to trying rooting the device? The symptoms suggest either a failed automatic update (rare but it does happen) or botched attempt to root via the wrong method. Obviously a spontaneous hardware failure is also possible albeit unlikely.
Do you know what version of Fire OS was running just prior to the boot loop?
There is still a small chance adb may help even if the device is not recognized by Windows explorer. However, if as Davey said, it is disabled, things are limited.
Again, do you know what version is you were running?
Have you installed adb?
Have you tried recovery?
Sent from my KFTHWI using Tapatalk
Davey126 said:
Your options are limited given the device is largely invisible via tether (even then there would be little recourse as adb is probably disabled). Did you try a factory reset? Amazon's crippled recovery environment can be accessed via power + vol-up from a cold start. Release the power button after the gray Kindle logo appears. If the recovery menu comes up the only option is 'factory reset'. I realize you may not be able to access recovery given the non-responsive power button.
Any chance you son is old/savvy enough to trying rooting the device? The symptoms suggest either a failed automatic update (rare but it does happen) or botched attempt to root via the wrong method. Obviously a spontaneous hardware failure is also possible albeit unlikely.
Do you know what version of Fire OS was running just prior to the boot loop?
Click to expand...
Click to collapse
No, Unless it updated automatically, it was the same version that was on there when it was delivered around 4/14.
No, My son would not have tried rooting this on his own.
I was incorrect when I stated that the system wasn't recognizing the power button. When I try the hold the power button for 40 secs or the Power button + Vol up button to restart, the boot loop gets shorter.
lekofraggle said:
There is still a small chance adb may help even if the device is not recognized by Windows explorer. However, if as Davey said, it is disabled, things are limited.
Again, do you know what version is you were running?
Have you installed adb?
Have you tried recovery?
Sent from my KFTHWI using Tapatalk
Click to expand...
Click to collapse
I have installed ADB on my PC but it doesn't see the device (although I'm not sure I'm using it correctly). What command should I be issuing to see if the device is connected. If I use "adb devices" I get the response in the attached screen shot.
If by recovery, you mean the recovery on the device, the power+volume up button doesn't work.
I appreciate all of the help!
Leav320 said:
No, Unless it updated automatically, it was the same version that was on there when it was delivered around 4/14.
No, My son would not have tried rooting this on his own.
I was incorrect when I stated that the system wasn't recognizing the power button. When I try the hold the power button for 40 secs or the Power button + Vol up button to restart, the boot loop gets shorter.
I have installed ADB on my PC but it doesn't see the device (although I'm not sure I'm using it correctly). What command should I be issuing to see if the device is connected. If I use "adb devices" I get the response in the attached screen shot.
If by recovery, you mean the recovery on the device, the power+volume up button doesn't work.
I appreciate all of the help!
Click to expand...
Click to collapse
Given the delivery date and age of device I STRONGLY recommend you reach out to Amazon for a replacement vs trying to resolve on your own. A new version of Fire OS is currently rolling out which MAY have triggered the behavior you are seeing. Bit of a bummer given your son's course plans but a worthwhile delay IMHO.
I agree with Davey.
Sent from my KFTHWI using Tapatalk
I know this has probably been covered to death in various posts here but I have tried a lot of what is written here and haven't been able to fix my hdx. I am currently stuck in a fastboot loop. Though sometimes it boots into bulk mode, which is strange, but I can get it back into fastboot eventually. Anyone out there able to walk me through steps to figure out what I did and get it back to working, preferably with TWRP and Lineage OS installed. I will just take getting back in to Fire OS atm sine this is giving me a headache. Anyway, I am using a win 10 machine and have fastboot ready on the KF right now. I am going to leave it this way for the time being. I originally used this https://forum.xda-developers.com/kindle-fire-hdx/general/thor-4-5-5-2-easy-to-root-unlock-t3571240 to go about getting this to where I could install a custom ROM but missed the adb composite drivers before I ran the unlock.bat. I have since gotten that straightened out and even ran the unlock.bat and it succeeded. I have reflashed recovery.img and a boot.img though it isn't the right one. (I was desperate and tried some dumb stuff and flashed the boot.img from my lineage os zip via fastboot)(yeah I know, stupid, but like I said, desperate)
Enough rambling for now. Anyway think they can help me with this issue? @draxie maybe? or @Davey126.
Please and thank you!
FumundaSaq said:
I know this has probably been covered to death in various posts here but I have tried a lot of what is written here and haven't been able to fix my hdx. I am currently stuck in a fastboot loop. Though sometimes it boots into bulk mode, which is strange, but I can get it back into fastboot eventually. Anyone out there able to walk me through steps to figure out what I did and get it back to working, preferably with TWRP and Lineage OS installed. I will just take getting back in to Fire OS atm sine this is giving me a headache. Anyway, I am using a win 10 machine and have fastboot ready on the KF right now. I am going to leave it this way for the time being. I originally used this https://forum.xda-developers.com/kindle-fire-hdx/general/thor-4-5-5-2-easy-to-root-unlock-t3571240 to go about getting this to where I could install a custom ROM but missed the adb composite drivers before I ran the unlock.bat. I have since gotten that straightened out and even ran the unlock.bat and it succeeded. I have reflashed recovery.img and a boot.img though it isn't the right one. (I was desperate and tried some dumb stuff and flashed the boot.img from my lineage os zip via fastboot)(yeah I know, stupid, but like I said, desperate)
Enough rambling for now. Anyway think they can help me with this issue? @draxie maybe? or @Davey126.
Please and thank you!
Click to expand...
Click to collapse
Above my pay-grade upon learning you flashed the LineageOS boot.img. Most likely will need to fix this (if repairable) from bulk mode. I believe @draxie is the only one with sufficient knowledge to take this on; also know he's usually quite busy.
Davey126 said:
Above my pay-grade upon learning you flashed the LineageOS boot.img. Most likely will need to fix this (if repairable) from bulk mode. I believe @draxie is the only one with sufficient knowledge to take this on; also know he's usually quite busy.
Click to expand...
Click to collapse
Thanks anyway. I know i screwed it up pretty badly but hoping since i can still get into fastboot and bulk mode that maybe it's still salvageable. Not holding my breath at this point. Thanks again
You should be fine
FumundaSaq said:
Thanks anyway. I know i screwed it up pretty badly but hoping since i can still get into fastboot and bulk mode that maybe it's still salvageable. Not holding my breath at this point. Thanks again
Click to expand...
Click to collapse
As long as your HDX responds to fastboot commands as expected,
your desired outcome should be achievable. Now, since you got
desperate and did a bunch of random stuff, let's start with checking
if that HDX is unlocked. (I suspect it isn't, otherwise that boot.img
from Lineage should just work.)
Code:
fastboot -i 0x1949 oem idme \?
Next, if it were still locked, do you have the unlock code?
If so, try to unlock, and if that works, see if that fixes booting.
Code:
fastboot -i 0x1949 flash unlock unlock.code
If the unlock fails or you're still having problems after a successful
unlock, I'd need to get some clarity regarding that bulk mode you
mention. Since it's -apperently- entered spontaneously (is it?) and
appears to be recoverable without too much effort(correct?), I'd
expect this to be the Sahara-style serial communication bulk mode,
and not the one that exposes all partitions to the host OS (you'd know,
since the latter generates a ton of dialogs asking to format those).
What cable (or cables) are you using? That serial bulk mode can be
consistently entered with a fastboot cable, but I find the kind of
intermittent triggering you describe rather strange...
Ok. First of, thanks @draxie for helping. Second i am including the pic i took of the txt on hdx screen after input of both commands. I honestly don't know what i am looking for so i will let you see it and tell me.
As for the bulk mode, it is the mode that produces the 8 or 9 drives in Windows(and Linux). The intermittent part is that sometimes it isn't recognized correctly by Windows. Sometimes it is recognized as the qloader 9008 like it should be. Sometimes Windows says it is an unrecognized usb device.
Hopefully that makes sense.
FumundaSaq said:
Ok. First of, thanks @draxie for helping. Second i am including the pic i took of the txt on hdx screen after input of both commands. I honestly don't know what i am looking for so i will let you see it and tell me.
As for the bulk mode, it is the mode that produces the 8 or 9 drives in Windows(and Linux). The intermittent part is that sometimes it isn't recognized correctly by Windows. Sometimes it is recognized as the qloader 9008 like it should be. Sometimes Windows says it is an unrecognized usb device.
Hopefully that makes sense.
Click to expand...
Click to collapse
Well, that makes only partial sense to me,
since getting into that bulk mode normally
requires active effort, which does not quite
match my interpretation of what you wrote
(i.e. "sometimes boots into", which sounds
unprovoked/spontaneous to me).
BUT, that's the better scenario; so, let's
just celebrate briefly and move on.
The image indicates that the bootloader is
now unlocked. I think it may have already
been unlocked before, but I'm not sure.
And, frankly, it doesn't really matter now.
What I gather from your original post,
you end up back in fastboot when you
reboot. Is that still the case?
What happens if you hold Volume-Up
and Power to reboot? No TWRP?
draxie said:
Well, that makes only partial sense to me,
since getting into that bulk mode normally
requires active effort, which does not quite
match my interpretation of what you wrote
(i.e. "sometimes boots into", which sounds
unprovoked/spontaneous to me).
BUT, that's the better scenario; so, let's
just celebrate briefly and move on.
The image indicates that the bootloader is
now unlocked. I think it may have already
been unlocked before, but I'm not sure.
And, frankly, it doesn't really matter now.
What I gather from your original post,
you end up back in fastboot when you
reboot. Is that still the case?
What happens if you hold Volume-Up
and Power to reboot? No TWRP?
Click to expand...
Click to collapse
@draxie - keep in mind he can boot a suitable twrp image from fastboot if the bootloader is unlocked. Might provide an expedited path to a bootable system partition.
draxie said:
Well, that makes only partial sense to me,
since getting into that bulk mode normally
requires active effort, which does not quite
match my interpretation of what you wrote
(i.e. "sometimes boots into", which sounds
unprovoked/spontaneous to me).
BUT, that's the better scenario; so, let's
just celebrate briefly and move on.
The image indicates that the bootloader is
now unlocked. I think it may have already
been unlocked before, but I'm not sure.
And, frankly, it doesn't really matter now.
What I gather from your original post,
you end up back in fastboot when you
reboot. Is that still the case?
What happens if you hold Volume-Up
and Power to reboot? No TWRP?
Click to expand...
Click to collapse
Holding volume up and power just gets me back into fastboot. As for the sometimes boots into bulk mode, i didn't really mean spontaneous just that there are times when i tried to force it into bulk mode that Windows sar it only as unrecognized usb device and other times Windows sees it correctly. It only attempted bulk mode when i tried to put it there. Sorry for the misunderstanding. I'm new to this bulk mode thing.
If i remember, i put it into bulk mode using the commands
Fastboot -i 0x1949 erase aboot
Fastboot -i 0x1949 reboot
I probably messed up something doing that so feel free to berate me for that
I will follow whatever instructions you have. I really appreciate the help.
@draxie Just tested the volume up + power again and booted into twrp! Not sure why it never did before. Maybe I am just an idiot or didn't wait long enough. I did reboot with vol up and power but got a grey kindle logo and then nothing. Connected it to my pc and tried adb devices and there was one. The SN was strange, it read 0123456789abcd which obviously isn't correct. But I sent the command adb reboot recovery and then let it shut off, held the vol up and power and now I'm in twrp!
I sideloaded Lineage os and gapps now. It is working! Thanks for the help!!! Not sure what I was doing wrong before but I appreciate your guidance. Thanks to both @draxie and @Davey126 for bearing with me. You guys have the patience of Saints!
FumundaSaq said:
I sideloaded Lineage os and gapps now. It is working! Thanks for the help!!! Not sure what I was doing wrong before but I appreciate your guidance. Thanks to both @draxie and @Davey126 for bearing with me. You guys have the patience of Saints!
Click to expand...
Click to collapse
I'm still confused by your story, but I'm glad it worked in the end.
draxie said:
I'm still confused by your story, but I'm glad it worked in the end.
Click to expand...
Click to collapse
I realize that you probably are. For all I know it would have worked to begin with. I don't know what happened. I'm just strange that way.
If you have a specific question I would be glad to try to answer it.
FumundaSaq said:
Holding volume up and power just gets me back into fastboot. As for the sometimes boots into bulk mode, i didn't really mean spontaneous just that there are times when i tried to force it into bulk mode that Windows sar it only as unrecognized usb device and other times Windows sees it correctly. It only attempted bulk mode when i tried to put it there. Sorry for the misunderstanding. I'm new to this bulk mode thing.
If i remember, i put it into bulk mode using the commands
Fastboot -i 0x1949 erase aboot
Fastboot -i 0x1949 reboot
I probably messed up something doing that so feel free to berate me for that
I will follow whatever instructions you have. I really appreciate the help.
@draxie Just tested the volume up + power again and booted into twrp! Not sure why it never did before. Maybe I am just an idiot or didn't wait long enough. I did reboot with vol up and power but got a grey kindle logo and then nothing. Connected it to my pc and tried adb devices and there was one. The SN was strange, it read 0123456789abcd which obviously isn't correct. But I sent the command adb reboot recovery and then let it shut off, held the vol up and power and now I'm in twrp!
Click to expand...
Click to collapse
I, too, am stuck in fastboot mode after I seemingly flashed TWRP and aboot. Could you elaborate what you did to fix the issue? I held power button + Vol UP and no TWRP mode, just goes back to fastboot...I think my issue is I forgot to run get_code.bat before erasing aboot, and now I can't unlock nor boot into the stock ROM. Is there anyway to unlock through just fastboot or even restore the stock ROM? I don't mind reloading and going through the process all over again.
This was the thread I was following: https://forum.xda-developers.com/ki...loader-firmware-t3463982/page106#post76073370
Praxxer1 said:
I, too, am stuck in fastboot mode after I seemingly flashed TWRP and aboot. Could you elaborate what you did to fix the issue? I held power button + Vol UP and no TWRP mode, just goes back to fastboot...I think my issue is I forgot to run get_code.bat before erasing aboot, and now I can't unlock nor boot into the stock ROM. Is there anyway to unlock through just fastboot or even restore the stock ROM? I don't mind reloading and going through the process all over again.
This was the thread I was following: https://forum.xda-developers.com/ki...loader-firmware-t3463982/page106#post76073370
Click to expand...
Click to collapse
Cross post - answered in other thread.