Ok. Yesterday my daughter was playing with my phone and she kept trying to unlock with the fingerprint reader. She ended up locking me out of my phone. The backup password I thought I created is not working. I never used the password. Always the fingerprint reader. Just to let you know. It's not a stolen phone. If you look at my post history, you'll see that I've had it for a few weeks. Just wanted to post that because people usually think the phone is stolen. Back to the problem at hand. I let the phone die and it's not letting me get to the boot loader to reset the phone. I can't adb into it either as the phone isn't recognized by the PC. Am I screwed or is there any other options to get back in? Thanks.
cellington77 said:
Ok. Yesterday my daughter was playing with my phone and she kept trying to unlock with the fingerprint reader. She ended up locking me out of my phone. The backup password I thought I created is not working. I never used the password. Always the fingerprint reader. Just to let you know. It's not a stolen phone. If you look at my post history, you'll see that I've had it for a few weeks. Just wanted to post that because people usually think the phone is stolen. Back to the problem at hand. I let the phone die and it's not letting me get to the boot loader to reset the phone. I can't adb into it either as the phone isn't recognized by the PC. Am I screwed or is there any other options to get back in? Thanks.
Click to expand...
Click to collapse
If you can plug it into a computer and back up the files. Then factory reset it
Flyhalf205 said:
If you can plug it into a computer and back up the files. Then factory reset it
Click to expand...
Click to collapse
When I plug it in to my PC it says I need to enter password to access my files. When I try to get into the boot loader it's not letting me. It just boots into safe mode.
I got it fixed. Chatted with HTC.
cellington77 said:
I got it fixed. Chatted with HTC.
Click to expand...
Click to collapse
What did they tell you to do? I'm having the exact same problem!
I have had the phone for a year, never once had to type in the password. Were there any restrictions when creating it? I can't imagine why I didn't just use one of my normal passwords. Nothing I try will let me in. I've tried every password I would have ever used to no avail. My password manager is on my phone and I have not backed it up in forever...I'm desperate to avoid a factory reset. Pretty please tell me there is something I can do to get back to the fingerprint scanner ;-(
I spoke with HTC and it seems there is nothing you can do once the fingerprint scanner locks you out. Only option is a hard reset. Turns out I had fat fingered my usual password, so I found it by trying a dozen permutations or my usual password. Everyone that might not entirely remember there password should go change it, before they get caught without it.
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
Purchased a used Nexus 9 on Ebay factory reconditioned.
Unit's arrived with someone's email info associated with it.
Factory reset within Android seems to do not much of anything, I haven't done anything in recovery yet as I read that might require the registered owner's password.
Tried to unlock the bootloader so I could flash a fresh image but getting that permission is denied
What steps do I need to take to remove the other user, make myself the owner, unlock the bootloader, and rid myself of them? I'm about to email the person who's listed as the owner and see if they're willing to help in the event I need them to do something
Thanks!
What happens when you remove their email from Accounts in settings?
Sent from my XT1528
mildlydisturbed said:
Purchased a used Nexus 9 on Ebay factory reconditioned.
Unit's arrived with someone's email info associated with it.
Factory reset within Android seems to do not much of anything, I haven't done anything in recovery yet as I read that might require the registered owner's password.
Tried to unlock the bootloader so I could flash a fresh image but getting that permission is denied
What steps do I need to take to remove the other user, make myself the owner, unlock the bootloader, and rid myself of them? I'm about to email the person who's listed as the owner and see if they're willing to help in the event I need them to do something
Thanks!
Click to expand...
Click to collapse
That's a new security feature in 5.1. You either need to get the former owner's username and password, or return it for a refund.
Ace42 said:
What happens when you remove their email from Accounts in settings?
Click to expand...
Click to collapse
As I recall it didn't let me
cam30era said:
That's a new security feature in 5.1. You either need to get the former owner's username and password, or return it for a refund.
Click to expand...
Click to collapse
It's running 5.0.1
Just talked with Google support - man they're easy to contact as a note. He said since 5.0.x didn't have the feature that locks the username and password in through a HBoot factory reset so to try it there. I'm at minute 9 of waiting for the thing to reboot to see if it worked or if it's going to ask me for a password.
We shall see however
After two hours it didn't boot. Got into recovery, factory reset doesn't seem to work, plenty of errors about trying to delete folders.
Took Google's suggestion and downloaded an image that was still in the 5.0.x range and tried flashing it ... get nothing but errors PU-FAIL
Noticed the hboot version number was for the WiFi, was sold it as an LTE/CDMA... downloaded the correct WiFi-only stuff, flashing fails.
It updates BCM, then PU-FAIL and something else on everything else.
Unit doesn't boot any more.. just sits at the spinning balls screen.
Think I got a lemon...
Managed to get it to mostly flash 5.0.2 - first part flashes fine, second part fails on .sig missing, extracted and flashed everything individually - cache failed a few times, few times it flashed fine, always throws up errors in recovery that it can't write it.
I'm beginning the believe the unit was refurbed and they missed a bad EMMC
mildlydisturbed said:
Managed to get it to mostly flash 5.0.2 - first part flashes fine, second part fails on .sig missing, extracted and flashed everything individually - cache failed a few times, few times it flashed fine, always throws up errors in recovery that it can't write it.
I'm beginning the believe the unit was refurbed and they missed a bad EMMC
Click to expand...
Click to collapse
Return it. Never buy electronics on ebay...there is no official warranty and after 60 days, the buyer protection of paypal terminates so you have no leverage with the seller in case of problems. Also, seller refurbished items are the worst as they repair things with no finesse and dont usually do a very good job of diagnosing the issue or replace with cheap parts. I have a lot of experience in refurbishing as I am a Samsung trained technician that works for a major Canadian retailer that has licensed repair centers across the country. I often try to make money on the side by buying broken Samsung phones and tablets and going through official channels to get replacement parts. Official replacement parts are more expensive but I get them at wholesale cost. What I have learned in my years of dealing with replacement parts is that a lot of those that use chinese replacement parts often end up with more problems than they had...you often see that in screen replacements, some of the quickest and high profit margins, using chinese parts will leave you with problems such as undercalibrated screens, low precision digitizers, backlight bleeding, and such. eBay is the biggest market for those parts and a high percentage of sellers on these channels make a living off those repairs. In any case, bad idea.
Yup, initiated a return. Wasn't what I ordered (ordered LTE/CDMA version, got WiFi), bad EMMC. as far as I can tell - I can flash 5.0.2 but always getting cache errors on clear and never able to do anything.
After a few more flashing experiences I found that I had about a 90% chance of successfully flashing a partition and about a 70% chance of getting into recovery.
These of course should have been 100%.
Thing's boxed up, sitting with a return label on it in the outgoing mailbox at work. Ah well, was interesting being a nexus owner if only for a couple of days
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.
Let me start by saying I am a newbie. I haven't done any modifications or anything of that sort to the device. I have a Fire HDX 7" that is about 18 months old. Things were going great and then my reader started acting up. The device wasn't completely turning pages, and then locked up all together. I plugged it in to charge, powered down and left it to charge overnight. Turned it back on and was greeted by a screen that says:
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.
Volume up/down to move highlight;
power button to select.
Reboot your Kindle
Reset to Factory Defaults
So I chose the Factory Default. It doesn't seem to be completing the erase procedure, it won't boot. I tried customer service and they were less than helpful, offering me a $20 discount on a refurbished unit.
I expected more than 18 months out of this device. Anything I can do?
Did you make any modifications to the system? (i.e. root, Safestrap)
EncryptedCurse said:
Did you make any modifications to the system? (i.e. root, Safestrap)
Click to expand...
Click to collapse
Nope. Didn't do anything to the device.
VilleDJ said:
Let me start by saying I am a newbie. I haven't done any modifications or anything of that sort to the device. I have a Fire HDX 7" that is about 18 months old. Things were going great and then my reader started acting up. The device wasn't completely turning pages, and then locked up all together. I plugged it in to charge, powered down and left it to charge overnight. Turned it back on and was greeted by a screen that says:
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.
Volume up/down to move highlight;
power button to select.
Reboot your Kindle
Reset to Factory Defaults
So I chose the Factory Default. It doesn't seem to be completing the erase procedure, it won't boot. I tried customer service and they were less than helpful, offering me a $20 discount on a refurbished unit.
I expected more than 18 months out of this device. Anything I can do?
Click to expand...
Click to collapse
Unfortunately, if the device is 'stock' little can be done to recover from the situation you are in. Hard to tell what happened; sounds like a hardware failure but can't rule out software or malware. Sorry the news isn't better.
Did your battery die in the tablet before during this time? Might of been a failed ota.