Related
I am rooted but I took all the precautions before the update such as unfreezing. I can't get into boot loader. No matter what kind of reset I'm stuck at the splash screen. Others have this issue and are completely stock. Any guidance is appreciated!
Have same problem coming from stock .28. Actually did a factory reset before update and it looked like update worked fine. Haven't been successfully able to boot into jelly bean. Can't even power off
same problem
me too stuck in to boot screen (asus logo on center nvidia logo in right bottom corner)
after jell bean update !
I'm there too - used Protato's method to the letter (I thought) - it looks like a brick, doesn't it.
OMG asus replied me
Dear Sir/Madam,
Thank you for contacting ASUS Technical Service.
Hi, I'm very glad to help you. For the problem, please try to hold the power button down for 10-15 seconds to reboot the device.
If stills, I suggest you follow the instructions below to perform “Wipe Data” to restore the unit back to the factory default condition.
Warning: Wiping data will erase all user data. The data is irrecoverable after the wipe.
1. Press and hold down “power button” until the system shuts down.
2. Remove the SD card from Eee Pad.
3. Press and hold down “Volume down” button first, and then press and hold down the “Power” button until the below words appear on the screen:
“Checking for RCK..press key in 5 sec to enter RCK”
4. Do not press any button until there is a line “Press to execute, to cancel wiping data.” Press Volume Up button to execute the “Wipe Data”.
5. After the “Wipe Data” process is done, it will reboot automatically. Then Eee Pad should be able to enter the system successfully.
Click to expand...
Click to collapse
problem is device not closing with power button. only restarts itself. volume up + power button closes screen but device still active because apx driver appears in my pc with universal naked drivers.
I have the same problem.
Tried rebooting by holding the power button.
Booting in recovery won't work either.
I can boot in APX, but from there i can' t do anything.
ADB wont recognise my prime...
Contacted Asus about my isue, but knowing asus it will mean waiting for few days, sending in my prime (rooted) and probably having to wait a month to get it back... (3rth RMA in 10 months...)
Selhati said:
I have the same problem.
Tried rebooting by holding the power button.
Booting in recovery won't work either.
I can boot in APX, but from there i can' t do anything.
ADB wont recognise my prime...
Contacted Asus about my isue, but knowing asus it will mean waiting for few days, sending in my prime (rooted) and probably having to wait a month to get it back... (3rth RMA in 10 months...)
Click to expand...
Click to collapse
Do you think they will care if its rooted at this point? I want to RMA mine now this is just the cherry on top. I opened up my prime before but didn't tweak it at all. Hopefully I won't get a 300$ bill after this.
Has anyone figured out how to get pass this issue?
Has anyone figured out how to get pass this issue?
Stuck on splashscreen
I am also experiencing the same issue with my Prime. My tablet had flashed Jelly Bean without a flaw while rooted with a deodexed file I found from one of the developers. It worked great throughout the day and it remained rooted but when I decided to reboot my tablet, it got stuck in the splash screen. Now it will not boot up at all. It is just stuck on the Asus splashscreen. I hope someone figures out how to fix this issue.
Jeez guys, we're all in the same boat, and so far i'm feeling we're F#CKED,
Stuck on asus logo, cant get to the bootloader by pressing volume down and power, can only get to APX mode, and nothing is fixing it, I contacted Asus also, but my bootloader is unlocked, so all im expecting is "Were sorry, your device is out of warranty because it's unlocked" fml.
Brandonxcore said:
Jeez guys, we're all in the same boat, and so far i'm feeling we're F#CKED,
Stuck on asus logo, cant get to the bootloader by pressing volume down and power, can only get to APX mode, and nothing is fixing it, I contacted Asus also, but my bootloader is unlocked, so all im expecting is "Were sorry, your device is out of warranty because it's unlocked" fml.
Click to expand...
Click to collapse
I have tried all the steps listed to fix my prime and nothing seems to work. I feel that were screwed but hopefully someone can prove me wrong. I'm tempted to buy a Nexus 7 now or tf700. If we don't fix our tablets I will have no choice but to get one of them.
Brandonxcore said:
Jeez guys, we're all in the same boat, and so far i'm feeling we're F#CKED,
Stuck on asus logo, cant get to the bootloader by pressing volume down and power, can only get to APX mode, and nothing is fixing it, I contacted Asus also, but my bootloader is unlocked, so all im expecting is "Were sorry, your device is out of warranty because it's unlocked" fml.
Click to expand...
Click to collapse
they'll RMA it for free even if you're rooted/unlocked. they have no way of telling.
EZPIMP69 said:
I have tried all the steps listed to fix my prime and nothing seems to work. I feel that were screwed but hopefully someone can prove me wrong. I'm tempted to buy a Nexus 7 now or tf700. If we don't fix our tablets I will have no choice but to get one of them.
Click to expand...
Click to collapse
I think if everything goes to crap, I'll get a Nexus 7. It's really going to hurt not having a keyboard dock since I use my Prime as a laptop. Reason why I don't really want to get an infinity is because Asus still hasn't ironed out all the issues with the Transformer line. Plus if I hork out another $500 and get burned by a new product come Christmas, I am not going to be happy. Hoping that my Prime will be ok but ya, the worst usually happens to me.
I found this post. I am going to try and see if it works for me. Others are saying that these steps fixed their prime. I'll let you know how it goes for me.
http://forum.xda-developers.com/showthread.php?t=1773280
Any new ideas on how to get this fixed? Stuck on the Asus splash screen alo.
EZPIMP69 said:
I found this post. I am going to try and see if it works for me. Others are saying that these steps fixed their prime. I'll let you know how it goes for me.
http://forum.xda-developers.com/showthread.php?t=1773280
Click to expand...
Click to collapse
Well I tried the steps in the link provided but had no luck since it requires fastboot. My tablet won't turn off or go into fastboot. The only way I think we can repair this is with NVflash but Asus needs to provide the files needed to complete a factory flash. This **** sucks.
EZPIMP69 said:
I found this post. I am going to try and see if it works for me. Others are saying that these steps fixed their prime. I'll let you know how it goes for me.
http://forum.xda-developers.com/showthread.php?t=1773280
Click to expand...
Click to collapse
So what was the result?
Count me in
Just another report of this happening to me. Stuck in the Asus "perfection" logo.
The only thing I have found is that I can turn off the screen following this steps:
Connect it to the power
With a pin press and hold the reset button
Keeping pressed the reset button disconnect the power connector,
Connect the power bak again (always pressing the reset button) and wait about ten seconds before finally release the reset button.
At least now I don't see that dreadful screen reminding me that I have an useless glowing brick in my desk.
Hopefully someone finds a way to unbrick it because I will be costly having to RMA the prime back to the US where I bought it.
T-HO6969 said:
So what was the result?
Click to expand...
Click to collapse
It did not work since I can't boot into fastboot to begin the process.
Let's collect info about the problem.
Let's try to find a common issue of why we got bricked answering some simple questions and hoping someone with better knowledge can use this information to help us. Here are some questions, you can add any information that you consider relevant.
How did you upgrade to JellyBean: I used this method
Unlocked? NO
Rooted"? YES. Because it was necesary in order to update to JB using the procedure linked above
Additional relevant info: My prime have the famous "unknown serial" problem that was never resolved by ASUS. Because of this, it has never received OTA and always have been updated with the firmwares from the ASUS website. This time instead of waiting for ASUS to publish JB in the support website I used the procedure above. Appart from this I have always keep it "stock".
I have the possibility of buying a hdx on Craigslist for cheap that is listed as broken. But the error they get on booting the device is that it wants him to type in a password to decrypt storage. I have seen this issue searching Google but everyone says to factory reset, can you do that without being able to boot into android by holding various button combos like other Android phones? Or I think I can root it to fix it? From reading if the device at least powers on this is likely possible.
The owner has given up on it it seems and I can score it cheap but wanted your input if this is a known issue that can't be fixed, like if he failed to root it and is now trying to pawn it off.
arsenic0 said:
I have the possibility of buying a hdx on Craigslist for cheap that is listed as broken. But the error they get on booting the device is that it wants him to type in a password to decrypt storage. I have seen this issue searching Google but everyone says to factory reset, can you do that without being able to boot into android by holding various button combos like other Android phones? Or I think I can root it to fix it? From reading if the device at least powers on this is likely possible.
The owner has given up on it it seems and I can score it cheap but wanted your input if this is a known issue that can't be fixed, like if he failed to root it and is now trying to pawn it off.
Click to expand...
Click to collapse
power + vol up to boot to recovery
if you can get one for cheap there a pretty good tablet, and if you can get one with lower firmware the better.
i have same issue with you. my kindle ask password to decrypt the device. i already tried to recover by holds uppower button + volume up but didn;t change anything. i don't know what to do
almost the same problem
I have the same boot encryption problem but i am the original owner of my HD 6
I've managed to enter safe mode on my device but this doesn't bypass boot encyption.
I'm waiting for a reply from amazon.
I'll post back when i do
---------- Post added at 06:45 PM ---------- Previous post was at 06:15 PM ----------
amazon tech support helped with the problem.
you can factory reset by turning the device off and pressing on and volume up(booting to recovery mode)(only hold for 4 seconds)
the controls in recovery mode are as follows:
up/down = vol up/vol down
enter = power button(tap once)
this will wipe the device and send you back to first setup.
apparently any further info about this is to be sent directly to tech support on +44 203 356 6212 or to call using amazon.co.uk/clicktocall and request amazon tech support
I am getting a boot password prompt every time I boot the device, I did factory reset twice, and it still does not help, still getting a big lock on the screen and request for a boot password
Any help will be appreciated
[email protected] said:
I am getting a boot password prompt every time I boot the device, I did factory reset twice, and it still does not help, still getting a big lock on the screen and request for a boot password
Any help will be appreciated
Click to expand...
Click to collapse
There is no recovery from this type of block if you don't know or have forgotten the password. You can reach out to Amazon to see if they have a code that will reset the device (unlikely).
Davey126 said:
There is no recovery from this type of block if you don't know or have forgotten the password. You can reach out to Amazon to see if they have a code that will reset the device (unlikely).
Click to expand...
Click to collapse
Thanks for the suggestion, I already reached out to Amazon 3 times. They have no idea, keep telling me Kindles do not have boot passwords
I never set it, and as I mentioned previously I did factory reset on the kindle. At this point this reset was performed 3 times, when the device boots I keep getting this boot password request
[email protected] said:
Thanks for the suggestion, I already reached out to Amazon 3 times. They have no idea, keep telling me Kindles do not have boot passwords
I never set it, and as I mentioned previously I did factory reset on the kindle. At this point this reset was performed 3 times, when the device boots I keep getting this boot password request
Click to expand...
Click to collapse
Like most Android devices Kindles (FireOS) can encrypt the data partition which presents a password prompt upon power-up. According to Amazon a factory reset should wipe the device and thus remove the password. Either that is not working for you or the device has been 'locked' by some other app or potentially malware. You may want to post a picture of the screen you are receiving. Someone may recognize it and be able to provide further guidance.
Davey126 said:
There is no recovery from this type of block if you don't know or have forgotten the password. You can reach out to Amazon to see if they have a code that will reset the device (unlikely).
Click to expand...
Click to collapse
Amazon are telling me now my Kindle was rooted, even though I explain that it was never connected to any network, and no apps were installed on it, just copied some book files from my PC using a USB cable. That's it. Isn't there some kind of re-format, other than reset to factory settings?
[email protected] said:
Amazon are telling me now my Kindle was rooted, even though I explain that it was never connected to any network, and no apps were installed on it, just copied some book files from my PC using a USB cable. That's it. Isn't there some kind of re-format, other than reset to factory settings?
Click to expand...
Click to collapse
If 'reset to factory' did not work then I'm afraid you are out of luck unless you can convince Amazon to offer an exchange. The device may have been rooted if purchased from a 3rd party. That does not explain why it suddenly 'locked' nor what tool/app is throwing up the password prompt.
Davey126 said:
If 'reset to factory' did not work then I'm afraid you are out of luck unless you can convince Amazon to offer an exchange. The device may have been rooted if purchased from a 3rd party. That does not explain why it suddenly 'locked' nor what tool/app is throwing up the password prompt.
Click to expand...
Click to collapse
The device was bought from Amazon, not a 3rd party, and it was working fine until my mom let it sit for several months without charging. Which should not have been a problem, but facts sho otherwise
[email protected] said:
The device was bought from Amazon, not a 3rd party, and it was working fine until my mom let it sit for several months without charging. Which should not have been a problem, but facts sho otherwise
Click to expand...
Click to collapse
You should pound on Amazon for a replacement - especially since they falsely accused you of having a rooted device (how do they know that?). I'm guessing the device may have received an 'over-the-air' upgrade while it was sitting idle but perhaps lacked sufficient charge to complete the update. Or the upgrade just went bad; rare but it happens.
Sorry this happened to your mom. Also regret there is not a (reasonable) way to recover the device and/or its contents.
Davey126 said:
You should pound on Amazon for a replacement - especially since they falsely accused you of having a rooted device (how do they know that?). I'm guessing the device may have received an 'over-the-air' upgrade while it was sitting idle but perhaps lacked sufficient charge to complete the update. Or the upgrade just went bad; rare but it happens.
Sorry this happened to your mom. Also regret there is not a (reasonable) way to recover the device and/or its contents.
Click to expand...
Click to collapse
Thanks for trying
I think it will be cheaper to buy a new kindle, new warranty, new features, etc.
Just a background:
This is not my device
This is a stock OS/nonrooted device
I have done some development on Android, so am somewhat experienced
I am helping a friend who just wants it to work again
Kindle Fire HDX 7" model # C9R6QM
What's going on:
Device is stuck on light gray "kindle fire" boot logo.
Device is not showing in device manager on Windows 7 PRO
Device is not showing in adb "adb devices command"
Device seems charged, has been left with cord in for longer than several hours
Tried several different cords to rule out faulty equipment
Tried multiple USB ports including 2.0, 3.0, front and rear ports, even a powered USB hub
Tried hard reset multiple times using power button
Tried power and vol up to go into a recovery, nothing happens.
"fastboot devices" command shows only "waiting for devices"
Help! I just need to get this thing up and running again, no matter the cost to data. Only thing I haven't tried is the bootloop utilities yet, as I am on a work pc and do not have access to download them atm. Will try these later if I need to.
Thanks in advance, and ask any questions if you need more info.
-Tripp
UPDATE 1: Upon further playing with device, I have finally gained access to the "Fire System Recovery" page seen here.
Well I guess since I am a new user still I cannot post the photo, but it is kindlefire recover page with a bunch of E: failed and E:cant mount stuff underneath. If I need to spell it all out I will.
Unfortunatly, neither "reboot your kindle" or "reset to factory defaults" does any good for me. Rebooting just causes it to bootlogo screen again, and Reset to FD fails, getting some weird oldschool tv effect on the screen until it reboots again into recovery and gives me the same two options.
ADB, windows, and fastboot still do not detect the device while in recovery.
Any ideas?
Doesn't sound like you have many options. Only other thing I can think of would be to try booting into Linux (i.e. Ubuntu) and see if you can get anything to work from there.
Anyways — since you claim this is a stock device — have you tried contacting Amazon for a replacement?
EncryptedCurse said:
Doesn't sound like you have many options. Only other thing I can think of would be to try booting into Linux (i.e. Ubuntu) and see if you can get anything to work from there.
Anyways — since you claim this is a stock device — have you tried contacting Amazon for a replacement?
Click to expand...
Click to collapse
I wish it was that easy. Device is way out of warranty. Was purchased just after it came out in 2013. I have not tried booting into linux, but can run a USB boot when I get home on my machine to attempt it. Will report back after. Thanks.
trippvail said:
I wish it was that easy. Device is way out of warranty. Was purchased just after it came out in 2013. I have not tried booting into linux, but can run a USB boot when I get home on my machine to attempt it. Will report back after. Thanks.
Click to expand...
Click to collapse
No surprise about ADB and not showing in Windows as the former was probably never enabled and the boot never gets far enough for the latter. Curious if you seen anything in device manager.
Unfortunately, you don't have a lot of options given the device is stock and fastboot is next to useless on a HDX with a locked bootloader (special cables don't work). If the previous poster's suggestion yields no progress I would reach out to Amazon. Even though the device is well out of warranty they may offer a deal given it failed spontaneously. Yeah, it likely be a refurb with some coin added in but a working unit is better than a brick if the price is right.
Davey126 said:
No surprise about ADB and not showing in Windows as the former was probably never enabled and the boot never gets far enough for the latter. Curious if you seen anything in device manager.
Unfortunately, you don't have a lot of options given the device is stock and fastboot is next to useless on a HDX with a locked bootloader (special cables don't work). If the previous poster's suggestion yields no progress I would reach out to Amazon. Even though the device is well out of warranty they may offer a deal given it failed spontaneously. Yeah, it likely be a refurb with some coin added in but a working unit is better than a brick if the price is right.
Click to expand...
Click to collapse
Damn was hoping there was a fix. I am sure that adb was never enabled as they are not tech savvy. Nothing shows in device manager when it is plugged in, ever. No changes.
Update 2:
So I popped in my Ubuntu drive and booted up. After installing adb and fastboot just in case, I tried accessing the kindle in both boot logo and recovery modes. No luck.
Ubuntu doesn't even see it there...
I know I'm not going crazy but it seems like I'm missing something somewhere. I have been through multiple brickings of our developer phones and brought them back to life but they always had adb enabled. Seems like there has to be a work around.
Quick question, would I be able to use a factory cable, or a homemade one at least, to force it into fastboot mode while it's stuck on boot like this?
And if I could get it into fastboot, would I be able to do anything to fix my situation?
trippvail said:
Quick question, would I be able to use a factory cable, or a homemade one at least, to force it into fastboot mode while it's stuck on boot like this?
And if I could get it into fastboot, would I be able to do anything to fix my situation?
Click to expand...
Click to collapse
Don't waste your time; traditional fastboot cables are useless on an HDX. One reason this generation of Kindle is exceptionally difficult to recover. The only time your really have control is with an unlocked bootloader. Otherwise the fastboot environment is crippled. Obviously Amazon has a hardware recovery method but no one has discovered it in the nearly 2 years since initial release.
Sorry to be the barer of bad news. It would be much more satisfying communicating a potential solution ...
Davey126 said:
Don't waste your time; traditional fastboot cables are useless on an HDX. One reason this generation of Kindle is exceptionally difficult to recover. The only time your really have control is with an unlocked bootloader. Otherwise the fastboot environment is crippled. Obviously Amazon has a hardware recovery method but no one has discovered it in the nearly 2 years since initial release.
Sorry to be the barer of bad news. It would be much more satisfying communicating a potential solution ...
Click to expand...
Click to collapse
lol thanks anyways. I just can't believe there is nothing I can do. Seems like if taken one step at a time, however lenghty the process may be, I would be able to get it fixed. Like if I can get into fastboot, even if crippled, I could repair the bootloader, or install a new recovery, or even wipe every partition and start over, or something. And then from there just add on little by little till it works again. I guess locking this device up like Amazon has will allow them to be the only ones to fully work on them. What a shame.
trippvail said:
lol thanks anyways. I just can't believe there is nothing I can do. Seems like if taken one step at a time, however lenghty the process may be, I would be able to get it fixed. Like if I can get into fastboot, even if crippled, I could repair the bootloader, or install a new recovery, or even wipe every partition and start over, or something. And then from there just add on little by little till it works again. I guess locking this device up like Amazon has will allow them to be the only ones to fully work on them. What a shame.
Click to expand...
Click to collapse
Yup - in a phrase it sucks. You can enter fastboot via power + vol- (volume down) but no useful commands can be issued unless the bootloader is unlocked. To do that you first need to install a vulnerable bootloader (typically accomplished via a Fire OS rollback), build an unlock code from your serial and manfID (obtained via ADB), sign the code string using a 'special' program and then attempt to unlock from fastboot. You can't even get to the first step no less securing the various details needed to complete the magic.
From a stickily business perspective Amazon is doing the right thing as a 'hacked' Kindle likely won't be used in the manner intended which involves full immersion into the Amazon ecosystem. Yeah, it ticks off a community of Android die-hards who vow never to purchase another Amazon device but in reality we represent a minute fraction of total sales. Apple nerds have been rattling the boycott saber for years. Has worked well - Apple just reported $58B USD sales for 1Q15. Apple probably could have made another 12 cents if they allowed all their devices to be unlocked and loaded with non iOS components (not adjusting for lost revenue from uncaptive app/media sales).
Davey126 said:
Yup - in a phrase it sucks. You can enter fastboot via power + vol- (volume down) but no useful commands can be issued unless the bootloader is unlocked. To do that you first need to install a vulnerable bootloader (typically accomplished via a Fire OS rollback), build an unlock code from your serial and manfID (obtained via ADB), sign the code string using a 'special' program and then attempt to unlock from fastboot. You can't even get to the first step no less securing the various details needed to complete the magic.
From a stickily business perspective Amazon is doing the right thing as a 'hacked' Kindle likely won't be used in the manner intended which involves full immersion into the Amazon ecosystem. Yeah, it ticks off a community of Android die-hards who vow never to purchase another Amazon device but in reality we represent a minute fraction of total sales. Apple nerds have been rattling the boycott saber for years. Has worked well - Apple just reported $58B USD sales for 1Q15. Apple probably could have made another 12 cents if they allowed all their devices to be unlocked and loaded with non iOS components (not adjusting for lost revenue from uncaptive app/media sales).
Click to expand...
Click to collapse
Ya I can understand that. I'm actually using an iPhone right now, jailbroken of course lol. But I understand why Amazon did it. Too bad a tablet has to die because of it though. I love the open Android systems but I like apples hardware better. Haven't found an android phone I like better yet. To each his own, right?
You may have said this before (I didn't read too carefully),
but I'm wondering if you had tried the HW buttons to get
into fastboot mode (power off, hold both volume buttons
while powering on). I have a theory that 'fastboot update'
actually works, but never had the need (or the extra time)
to test this.
Do you know what version of FireOS was installed?
draxie said:
You may have said this before (I didn't read too carefully),
but I'm wondering if you had tried the HW buttons to get
into fastboot mode (power off, hold both volume buttons
while powering on). I have a theory that 'fastboot update'
actually works, but never had the need (or the extra time)
to test this.
Do you know what version of FireOS was installed?
Click to expand...
Click to collapse
I don't and neither does the owner. I would assume the latest if it auto updates, although that may be what bricked it if it didn't have the power to complete the update. Can't confirm any of that though.
I will try both volume buttons in a bit when I get off work. I did the vol up with power to get into recovery, but that did nothing for me as recovery failed every time and rebooting just takes me back to the gray kf logo.
Ok so I tried the vol up and down while powering it on and it just took me to recovery. Same E:failed to mount and E:can't mount/can't open messages below the recovery options in yellow. So I guess I'm screwed then.
Hmm... This sounds kind of weird _to me_ considering that fastboot is the interface
to the bootloader, which loads either the boot or the recovery image. Since you do
seem to be able to boot to recovery (albeit with errors), I'd sort of expect aboot (i.e.
thebootloader) to be reasonably intact. And, in that case, you should be able to get
to fastboot; at least, in my book...
I suppose you must have tried this more than once, but I'd still recommend to give it
another chance. Power off the Kindle. Hold both volume buttons firmly. Push the power
button. And, keep holding all three until the fastboot prompt slides in. (The grey logo
should show up first, even in this case; quickly followed by the [fastboot] text.)
If this just doesn't seem to work, you could also try holding just the power button *really*
long (something like 40 seconds, I believe), which is supposed to trigger some form of low
level reset (possibly the same as factory reset; so, if data on the device matters, you should
think twice before going down this road). Then, see if this helped with getting into fastboot...
Other than that, I'm not quite sure what else to do than pray the thing apart and look for
debug pins.... :crying:
draxie said:
Hmm... This sounds kind of weird _to me_ considering that fastboot is the interface
to the bootloader, which loads either the boot or the recovery image. Since you do
seem to be able to boot to recovery (albeit with errors), I'd sort of expect aboot (i.e.
thebootloader) to be reasonably intact. And, in that case, you should be able to get
to fastboot; at least, in my book...
I suppose you must have tried this more than once, but I'd still recommend to give it
another chance. Power off the Kindle. Hold both volume buttons firmly. Push the power
button. And, keep holding all three until the fastboot prompt slides in. (The grey logo
should show up first, even in this case; quickly followed by the [fastboot] text.)
If this just doesn't seem to work, you could also try holding just the power button *really*
long (something like 40 seconds, I believe), which is supposed to trigger some form of low
level reset (possibly the same as factory reset; so, if data on the device matters, you should
think twice before going down this road). Then, see if this helped with getting into fastboot...
Other than that, I'm not quite sure what else to do than pray the thing apart and look for
debug pins.... :crying:
Click to expand...
Click to collapse
I will be trying your methods draxie when I get home and back with the device today if what I am doing now doesn't work. I was following another dev's advice to let the device die and charge it from there to perform a reset as well. It is not dead yet and has been on boot screen all night. Not sure what it is going to do but I am new to these Kindle Fire related things so I am not going to ask questions.
At this point recovering anything from the device is nothing to me, or the owner, as there was nothing important on it. I was hoping to not take the hardware route, but I have the tools, the time, and the hands to do it if necessary. All I need is the knowledge from someone as to what the hell I'm looking for in there.
Just to confirm, after the gray logo of KindleFire comes up, should I be seeing anything else come up while holding buttons for fastboot? <<Just re-read your post and realized it answered this question>>These things are so much easier to use when rooted and TWRP or CWM recoveries are installed. Android makers all over should take note and use the knowledge of the open source community to improve their own devices.
Below is a photo of the recovery screen I see now that I can finally post photos.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
trippvail said:
I was following another dev's advice to let the device die and charge it from there to perform a reset as well. It is not dead yet and has been on boot screen all night. Not sure what it is going to do but I am new to these Kindle Fire related things so I am not going to ask questions.
Click to expand...
Click to collapse
That sounds like a more surefire way to get any "stuck bits" cleared.
This would be similar to how some laptop manufacturers instruct you
to disconnect power, remove batteries, and let the thing sit for 5-10
minutes as a last resort, e.g. with boot failures. Which reminds me,
it may be a good idea to let the Kindle sit there dead for a while
before connecting a charger...
I was hoping that holding the power button "long enough" might get
you there faster; but that may just be wishful thinking based on a post
I read somewhere in these forums.
draxie said:
That sounds like a more surefire way to get any "stuck bits" cleared.
This would be similar to how some laptop manufacturers instruct you
to disconnect power, remove batteries, and let the thing sit for 5-10
minutes as a last resort, e.g. with boot failures. Which reminds me,
it may be a good idea to let the Kindle sit there dead for a while
before connecting a charger...
I was hoping that holding the power button "long enough" might get
you there faster; but that may just be wishful thinking based on a post
I read somewhere in these forums.
Click to expand...
Click to collapse
Lol thanks. I am sure it will be dead for awhile before I get home, if it's not dead already. But if for some reason it's still alive I will make sure to let it sit for an extra 30 minutes after it goes down.
My kindle unit is in the same boat as that unit above, no fastboot, no ADB, I had TWRP but i formatted it thinking it would only format the OS image.
The only thing I can get is a QHSUSB_BULK driver that doesn't completely install. Am I in a position where I can get fastboot or ADB access?
jwcdis said:
My kindle unit is in the same boat as that unit above, no fastboot, no ADB, I had TWRP but i formatted it thinking it would only format the OS image.
The only thing I can get is a QHSUSB_BULK driver that doesn't completely install. Am I in a position where I can get fastboot or ADB access?
Click to expand...
Click to collapse
If the bootloader remains locked with no access via tether (or wireless ADB) you are pretty much done. You can attempt the cold start remedy suggested in earlier posts. Long shot at best. Note the device should sit idle for several days after appearing to be depleted as internal circuitry prevents the battery from going completely dead. Even then some charge will remain which is necessary to respond to the power button and protect the battery from permanent damage. Removable primary and backup batteries are the only surefire way to insure a true cold start.
Hello guys!
I think i turned my Fire HDX 7" into a fancy cutting board.
I just hope there is still... well... hope.
About 2 month ago I stumbled across an app that "can boot your device in one click". Didn't work out, thought it did nothing but i think it's the root of my problem.
On the weekend i wanted to rest to factory settings. After that i'm stuck in a bootloop.
Kindle logo followed by "Fire is updating.. please wait" aaand reboot
Pressing the power button and volume up gives me the "reset/reboot" menu.
I soldered together a factory cable but it didn't enter fastboot. Showed up as "QHSUSB_BULK". and a "bricked" feeling (no reactions, blackscreen). Pressing power for a long time returned it to the bootloop.
Any help is appreciated and if things work out you just might earn a beer if you ever visite Germany/Munich.
Greeting
Don Karnage said:
Hello guys!
I think i turned my Fire HDX 7" into a fancy cutting board.
I just hope there is still... well... hope.
About 2 month ago I stumbled across an app that "can boot your device in one click". Didn't work out, thought it did nothing but i think it's the root of my problem.
On the weekend i wanted to rest to factory settings. After that i'm stuck in a bootloop.
Kindle logo followed by "Fire is updating.. please wait" aaand reboot
Pressing the power button and volume up gives me the "reset/reboot" menu.
I soldered together a factory cable but it didn't enter fastboot. Showed up as "QHSUSB_BULK". and a "bricked" feeling (no reactions, blackscreen). Pressing power for a long time returned it to the bootloop.
Any help is appreciated and if things work out you just might earn a beer if you ever visite Germany/Munich.
Greeting
Click to expand...
Click to collapse
Sorry for your troubles. Fastboot (aka factory) cables are useless on an HDX. If you can't 'see' your device via a standard usb cable or it shows up as "QHSUSB_BULK" then you're done. If the device was purchased within the past 12 months there is a good chance Amazon will exchange it for a refurb. Just say it died during an update (apparently true). No need to mention the prior root attempt which may or may not be related. Call and be nice to the rep; ultimately it's their decision.
Well, this explains a lot.
First of all thank you!
With a normal usb-cable iz shows up as "Anroid" and "MTB-USB-Device"
Contacting amazon will be the next thing for me i guess.
Don Karnage said:
Well, this explains a lot.
First of all thank you!
With a normal usb-cable iz shows up as "Anroid" and "MTB-USB-Device"
Contacting amazon will be the next thing for me i guess.
Click to expand...
Click to collapse
Those are encouraging signs. Do you recall enabling adb? If so there may be a way to revive your device via tether but the the commands/techniques are a little beyond me (others can probably help). Most require root access which you likely don't have. Best guess is the root exploit you tried was partially successful and may have altered some files needed to process ota updates. A factory reset emulates portions of that process likely resulting in the boot loop. If the offending 'update' file(s) can be renamed you might be able to boot successfully.
Don have you ever used ADB? If so this might possibly save you
http://forum.xda-developers.com/kindle-fire-hdx/general/unbrick-solutions-t3059733
So, I've had my Kindle Fire HDX 7' for a while now, and it's been running great. But amazon updated it from 4.5.3 to 4.5.4 and then it wouldn't boot. It would say: Fire is Upgrading, please wait... Then it would prompt me to choose the default kindle launcher, nova launcher, or the setup wizard. Which ever one I chose, it would close the window, but then come back to the same place. I contacted amazon support, and they said to boot into recovery (power+volume up) and factory reset, which I did. And now what happens is it says Fire is Upgrading please wait... then says that it is starting applications. But it stays there, and nothing happens. Anybody know a way I can fix this?
A very long shot, but try holding down the power button for 2 minutes.
lekofraggle said:
A very long shot, but try holding down the power button for 2 minutes.
Click to expand...
Click to collapse
Nope, that just force rebooted it a bunch of times
ftf841 said:
So, I've had my Kindle Fire HDX 7' for a while now, and it's been running great. But amazon updated it from 4.5.3 to 4.5.4 and then it wouldn't boot. It would say: Fire is Upgrading, please wait... Then it would prompt me to choose the default kindle launcher, nova launcher, or the setup wizard. Which ever one I chose, it would close the window, but then come back to the same place. I contacted amazon support, and they said to boot into recovery (power+volume up) and factory reset, which I did. And now what happens is it says Fire is Upgrading please wait... then says that it is starting applications. But it stays there, and nothing happens. Anybody know a way I can fix this?
Click to expand...
Click to collapse
You mentioned Nova which suggests device was rooted. Once rooted you have to block OTA. Not a lot of options unless root was retained through the update (unlikely) and you have adb enabled. I would work with Amazon given the 4.5.4 update hosed your device. Might get a discount on a replacement. Probably best not to mention root, Nova or any other customizations.
Davey126 said:
You mentioned Nova which suggests device was rooted. Once rooted you have to block OTA. Not a lot of options unless root was retained through the update (unlikely) and you have adb enabled. I would work with Amazon given the 4.5.4 update hosed your device. Might get a discount on a replacement. Probably best not to mention root, Nova or any other customizations.
Click to expand...
Click to collapse
When I contacted them, I didn't mention anything about those. However, it had been past a year, and so the warranty was out, and they said they couldn't do anything about it. I get a 20 dollar discount though
ftf841 said:
When I contacted them, I didn't mention anything about those. However, it had been past a year, and so the warranty was out, and they said they couldn't do anything about it. I get a 20 dollar discount though
Click to expand...
Click to collapse
If I were to guess is your Kindle is trying to start the native launcher but is encountering a conflict with Nova. On most devices this would be fairly easy to fix. Recent Kindles are locked down by Amazon. A next-to-use useless recovery environment compounds the problem. So far no one has figured out how to crack this nut on an unrooted device running Fire v4.
Press your case with Amazon. If you are regular customer a supervisor may be willing to make an exception or offer a larger discount. Your argument is based on an unwanted/unrequested/unnecessary amazon update that went bad. Just minding your own business and blamo ... an OTA out of the blue turned your world upside down. Or something like that ....
Davey126 said:
If I were to guess is your Kindle is trying to start the native launcher but is encountering a conflict with Nova. On most devices this would be fairly easy to fix. Recent Kindles are locked down by Amazon. A next-to-use useless recovery environment compounds the problem. So far no one has figured out how to crack this nut on an unrooted device running Fire v4.
Press your case with Amazon. If you are regular customer a supervisor may be willing to make an exception or offer a larger discount. Your argument is based on an unwanted/unrequested/unnecessary amazon update that went bad. Just minding your own business and blamo ... an OTA out of the blue turned your world upside down. Or something like that ....
Click to expand...
Click to collapse
If Nova was conflicting, the factory reset should've fixed it. Something I forgot to mention, is if I shut it down after it prompts me which launcher to choose, it goes through the same process all over again, with the updating, leading me to believe it's something deeper than just the launchers conflicting.
ftf841 said:
If Nova was conflicting, the factory reset should've fixed it. Something I forgot to mention, is if I shut it down after it prompts me which launcher to choose, it goes through the same process all over again, with the updating, leading me to believe it's something deeper than just the launchers conflicting.
Click to expand...
Click to collapse
A factory reset on a Kindle isn't what you think. It restores some files but does not perform a comprehensive refresh. A reasonable (albeit imperfect) comparison is system restore in Windows. Addresses some issues but is by no means comprehensive. Unlike Windows you don't have access to low level files without root and usually can't fix a start-up problem even if you know the source. What you really want is a true 'reset' or 'restore'; those options aren't available in the stock recovery.
I'm not saying it's 100% unresolvable. But few users exit the dreaded 'setup loop' w/o root access. Don't mean to be negative but also do not want to raise false hopes. There are a few clever (and very talented!) individuals who monitors these forums. Let this post sit for awhile and see who chimes in.
Davey126 said:
A factory reset on a Kindle isn't what you think. It restores some files but does not perform a comprehensive refresh. A reasonable (albeit imperfect) comparison is system restore in Windows. Addresses some issues but is by no means comprehensive. Unlike Windows you don't have access to low level files without root and usually can't fix a start-up problem even if you know the source. What you really want is a true 'reset' or 'restore'; those options aren't available in the stock recovery.
I'm not saying it's 100% unresolvable. But few users exit the dreaded 'setup loop' w/o root access. Don't mean to be negative but also do not want to raise false hopes. There are a few clever (and very talented!) individuals who monitors these forums. Let this post sit for awhile and see who chimes in.
Click to expand...
Click to collapse
Well, thanks anyways
Holding the power button is a way of clearing the cache. It seems like it is just rebooting, but if you do not have a true recovery (which you don't, it is a long shot which has worked for many. If you gave up after a few rounds, stick to it). If that does not work, try pressing poker once and Now, instead of choosing your launcher, enforcing the Kindle to give you the notification bar. Try holding power for just a second and clicking cancel and swiping down from the top. If youngest into settings, you may be able to try the update again. That may reset whatever broke, but Davey is correct, if you indeed were rooted, this is looking bad. If you were not, and you just downloaded nova, there is still a bit of hope.
lekofraggle said:
Holding the power button is a way of clearing the cache. It seems like it is just rebooting, but if you do not have a true recovery (which you don't, it is a long shot which has worked for many. If you gave up after a few rounds, stick to it). If that does not work, try pressing poker once and Now, instead of choosing your launcher, enforcing the Kindle to give you the notification bar. Try holding power for just a second and clicking cancel and swiping down from the top. If youngest into settings, you may be able to try the update again. That may reset whatever broke, but Davey is correct, if you indeed were rooted, this is looking bad. If you were not, and you just downloaded nova, there is still a bit of hope.
Click to expand...
Click to collapse
Well, Amazon told me to boot to recovery and factory reset and that may have screwed me over, because now it doesn't show the nova or kindle launcher, in place of that it says, starting applications, but nothing happens after that. I'll try holding the power button, because I did give up after 3 reboots.
The factory reset could have been a mistake, but I would assume they would have taken you through the power button piece first. Hmm. But, you did try their advice, and it got worse, so perhaps they will hand you a shiny referb. in return. If they do, check it for structural damage. I needed a return, because one of their updates messed my original one up (the kindle app and clipboard would not load), and they sent one with an old boot loader, but it had a cracked bezel. I did eventually get one that worked well, but it took a few rounds. They all had software or hardware issues. Through it all, tech support was stellar.
ftf841 said:
Well, Amazon told me to boot to recovery and factory reset and that may have screwed me over, because now it doesn't show the nova or kindle launcher, in place of that it says, starting applications, but nothing happens after that. I'll try holding the power button, because I did give up after 3 reboots.
Click to expand...
Click to collapse
lekofraggle said:
The factory reset could have been a mistake, but I would assume they would have taken you through the power button piece first. Hmm. But, you did try their advice, and it got worse, so perhaps they will hand you a shiny referb. in return. If they do, check it for structural damage. I needed a return, because one of their updates messed my original one up (the kindle app and clipboard would not load), and they sent one with an old boot loader, but it had a cracked bezel. I did eventually get one that worked well, but it took a few rounds. They all had software or hardware issues. Through it all, tech support was stellar.
Click to expand...
Click to collapse
I think you have a pretty good argument for your next Amazon engagement given the advise given actually made things worse. Obviously demeanor is important; treat everyone with respect and (gently) ask to speak with a supervisor if things grind to a halt. Reputation and customer satisfaction are important to Amazon but you have to be persistent.
Btw - lekofraggle is one of those clever/talented individuals I referenced earlier. Thought s/he might stop by. As always, great to hear multiple perspectives! Good luck.
You must have been in Warranty Leo. I tried so many times. The most helpful tech managed to get me a hundred bucks off, but this was several hours on the phone... He said that a few other people had the same hard brick that I had(never mentioned root) but... no warranty. @op good luck trying to fix this. Amazon is worse than Verizon imo because there is practically no way to fix this damned thing.
I was under warranty. That is too bad because not only is there no way to fix this, there was no way (that they know or want you to be privy to) to prevent it. That is wrong imo.
I'm having the same situation. My kindle was working fine before the night, and the Amazon auto upgrade bricked my Kindle. I contacted Amazon for help. During the conversation they changed 5 agents including one who claimed himself "one of the leaders". Most of them didn't seem to know what happened and how to fix it. Two of them mentioned that I need to factory reset my tablet, but none of them show me how to get into the recovery mode. After 4 hours of conversation they told me my kindle cannot be fixed and the only choice I have is to replace my kindle. And then they said since I've own my kindle for more than one year, the warranty is expired, as a result they cannot replace the kindle for me but they can offer me a discount if I buy another one from them. I was annoyed because what broke my Kindle is Amazon's update, not me. To me, they literally sold me a kindle and broke it after the warranty expired, and then try to sell me another one. They ended up giving me a $50 gift card for whatever sold and shipped by Amazon.
After the conversation I found the way to get into the recovery mode. And I hit the factory reset button. After the reset progress is complete my kindle is still stuck at "starting application", sometimes it passes "starting application" and the screen start flashing... as if the tablet is going to explode....I doubt maybe it is the factory reset file's problem, but it is too late for me to get into the storage using ADB since I don't have debugging mode activated after factory reset.
You may still have adv after factory reset. It only resets some settings. And deletes portions of the /data partition. It does not delete anything from the sd card or much from the /system partitions (which is why it does not help too much if there was a botched install or you messed something up with root powers.
That said, it does remove root, so adb is limited.
Brad D said:
I'm having the same situation. My kindle was working fine before the night, and the Amazon auto upgrade bricked my Kindle. I contacted Amazon for help. During the conversation they changed 5 agents including one who claimed himself "one of the leaders". Most of them didn't seem to know what happened and how to fix it. Two of them mentioned that I need to factory reset my tablet, but none of them show me how to get into the recovery mode. After 4 hours of conversation they told me my kindle cannot be fixed and the only choice I have is to replace my kindle. And then they said since I've own my kindle for more than one year, the warranty is expired, as a result they cannot replace the kindle for me but they can offer me a discount if I buy another one from them. I was annoyed because what broke my Kindle is Amazon's update, not me. To me, they literally sold me a kindle and broke it after the warranty expired, and then try to sell me another one. They ended up giving me a $50 gift card for whatever sold and shipped by Amazon.
After the conversation I found the way to get into the recovery mode. And I hit the factory reset button. After the reset progress is complete my kindle is still stuck at "starting application", sometimes it passes "starting application" and the screen start flashing... as if the tablet is going to explode....I doubt maybe it is the factory reset file's problem, but it is too late for me to get into the storage using ADB since I don't have debugging mode activated after factory reset.
Click to expand...
Click to collapse
If you rooted your Kindle then over-the-air (OTA) updates must also be blocked. That's the case for many devices as the update package expects a device is in a specific condition which may no longer be true after rooting. If the device has never been rooted or otherwise modified an an 'unsupported' manner (including side loading applications; read the disclaimer) then I agree you have a strong case against Amazon and should reengage with the understanding that you will take stronger action if they do not provide a better resolution. Worth a shot unless you are satisfied with the $50 or have something to 'hide'.
Davey126 said:
If you rooted your Kindle then over-the-air (OTA) updates must also be blocked. That's the case for many devices as the update package expects a device is in a specific condition which may no longer be true after rooting. If the device has never been rooted or otherwise modified an an 'unsupported' manner (including side loading applications; read the disclaimer) then I agree you have a strong case against Amazon and should reengage with the understanding that you will take stronger action if they do not provide a better resolution. Worth a shot unless you are satisfied with the $50 or have something to 'hide'.
Click to expand...
Click to collapse
I didn't have my kindle rooted, while I did install some applications from 1 mobile market. I even asked them to take my kindle back for further inspection, while they simply refused my suggestion and insisted their solution, which is either I return the kindle for the discount for a new purchase, or the $50 gift card. I figured that it may cost me more to take further action as I'm just one foreign customer and I don't see many who met the same situation in here.