A week ago, my 2 year old daughter was using my HDX7 under her profile. It was set up using Amazon protocol and she did not have administrator access. When my wife looked a few minutes later, she saw a gray Kindle Fire logo and the word 'erasing'. It was stuck in that mode for about 2.5-3 hours. Finally, my wife called Amazon 'tech support' who gave her a bunch of instructions about holding down the power button and volume button. She followed their instructions, and a gray logo appeared with the word '[fastboot]' on the screen. It has been like that ever since. Upon numerous calls to Amazon, they have accused us of rooting the Kindle. It has never been rooted before. No one in our family knows how to do this. Also, this just happened 35 days after the warranty. There seems to be nothing Amazon can do. Apparently, I can't even send it in to Amazon for them to repair. They claim they don't fix them (even though they sell refurbished ones).
I have tried following numerous forums with failure. ADB gives me a 'device not found' error and any other attempts have said, 'flashing not allowed on hw." I would be happy just to have it working again. If anyone knows how to fix this, it would be greatly appreciated.
Oh snap. Since ADB doesn't work and Amazon won't help you, I am not sure what you can do. Try using fastboot on Android SDK, make sure the device is on the [fastboot] screen, or try holding done the power button in till the device turns black, then wait a minute then hold down the power button or press it and it should show the kindle fire screen, then wait for it to load. Hope this helps!
Sent from my KFTHWI using XDA Free mobile app
Related
All,
I've been following posts on XDA since my original droid incredible days. I've rooted and maintained two phones, never have any issues.
Recently I purchased a T-Mobile Springboard (got a crazy promotion price through my company) which ran stock TMo Honeycomb. Eager to get ICS and eager to get rid of the power-on tmobile jingle, I installed the latest S7-302u firmware update from Huawei's website. I am aware that my device is technically S7-303u, but the update worked fine and I had little-to-no bugs. I am very pleased with this tablet.
Now here where I get stupid.
A coworker of mine then tells me that he has a S7-303u update.zip file that he can give me, which I don't object to. I give him my micro SD, he places the file in the 'dload' folder with 'unlmt.cfg'. I then reconsider my predicament, and decide that I'm happy with my current firmware, even if it's not made specifically for my tablet hardware version. If it ain't broke, don't fix it.
By the evening, I forget that the update file is on my SD card.
Before going to bed, I extinguish the battery and let it power down. I then plug it in the the wall and fall asleep.
Around 3 am (3 hours later) I was woken up to my springboard rebooting. Confused, I pick it up and see that it's in some kind of boot-loop. The screen turns on, but stays black, and then immediately powers down, and restarts. This process repeats indefinitely. I hold the power button down, trying to do a hard-reboot, but it doesn't seem t work. Then, after about 5 "holding the power button down for 10 seconds", the device reboots and I am graced with the gracious Huawei MediaPad logo.
The device automatically goes into recovery mode and installs the forgotten update.zip....
Now I'm pissed, specifically because I've lost my high scores in Trainyard Express and just because I now how to re-install all my apps. It's annoying, but it's not the end of the world. Or so I thought.
I use my tablet 75% of the time for reading through the kindle app, and on this version of ICS the kindle app doesn't work! So immediately I decide to revert back to the old S7-302u update that I originally had installed, following the same steps I did to manually update the device previously.
I now cannot, for the life of me, get this thing to boot into recovery mode. The only thing I can get this device to do is get to the "Enter into fastboot mode" screen by holding the power button and the volume+ key (the one closest to the power button).
A few other symptoms:
1. The device is set to quickstart mode by default and I don't see any option to deactivate it. The only way to get the device to actually "turn off" is to choose restart to hold the power button down for a hard reboot.
2. If I hold down the power button for ten seconds, I expect the device to power down and stay down. This is not the case. It always reboots immediately. I have no way of actually fully powering this device down (not counting the quick-start power-down).
3. No charging indication. I'm not sure if this is a hardware or software issue. My device will charge, but it does not give any indication on the screen or the battery icon.
Now I'm stuck wondering what to do. Did I ruin this device? I wanted to avoid rooting it because of the loss of 4G data, but now I'm afraid that I might need root-permissions to fix whatever I messed up.
Thanks in advance for your help.
Daniel
PS. Just so you all know my experience, I've rooted and maintained a droid incredible and currently, my galaxy nexus. I however, have no programming experience what-so-ever. I'm just good at following directions (usually).
What happens if you pull the micro sd card out? It should stop the boot loop (in theory). If the install didn't go through it should boot up normally to the previous version. In settings you can turn off FastBoot.
You might have to look at the sd card on a computer and either get rid of the unlmt.cfg from the dload folder and it shouldn't try to boot to the dload folder.
eurobass said:
All,
I've been following posts on XDA since my original droid incredible days. I've rooted and maintained two phones, never have any issues.
Recently I purchased a T-Mobile Springboard (got a crazy promotion price through my company) which ran stock TMo Honeycomb. Eager to get ICS and eager to get rid of the power-on tmobile jingle, I installed the latest S7-302u firmware update from Huawei's website. I am aware that my device is technically S7-303u, but the update worked fine and I had little-to-no bugs. I am very pleased with this tablet.
Now here where I get stupid.
A coworker of mine then tells me that he has a S7-303u update.zip file that he can give me, which I don't object to. I give him my micro SD, he places the file in the 'dload' folder with 'unlmt.cfg'. I then reconsider my predicament, and decide that I'm happy with my current firmware, even if it's not made specifically for my tablet hardware version. If it ain't broke, don't fix it.
By the evening, I forget that the update file is on my SD card.
Before going to bed, I extinguish the battery and let it power down. I then plug it in the the wall and fall asleep.
Around 3 am (3 hours later) I was woken up to my springboard rebooting. Confused, I pick it up and see that it's in some kind of boot-loop. The screen turns on, but stays black, and then immediately powers down, and restarts. This process repeats indefinitely. I hold the power button down, trying to do a hard-reboot, but it doesn't seem t work. Then, after about 5 "holding the power button down for 10 seconds", the device reboots and I am graced with the gracious Huawei MediaPad logo.
The device automatically goes into recovery mode and installs the forgotten update.zip....
Now I'm pissed, specifically because I've lost my high scores in Trainyard Express and just because I now how to re-install all my apps. It's annoying, but it's not the end of the world. Or so I thought.
I use my tablet 75% of the time for reading through the kindle app, and on this version of ICS the kindle app doesn't work! So immediately I decide to revert back to the old S7-302u update that I originally had installed, following the same steps I did to manually update the device previously.
I now cannot, for the life of me, get this thing to boot into recovery mode. The only thing I can get this device to do is get to the "Enter into fastboot mode" screen by holding the power button and the volume+ key (the one closest to the power button).
A few other symptoms:
1. The device is set to quickstart mode by default and I don't see any option to deactivate it. The only way to get the device to actually "turn off" is to choose restart to hold the power button down for a hard reboot.
2. If I hold down the power button for ten seconds, I expect the device to power down and stay down. This is not the case. It always reboots immediately. I have no way of actually fully powering this device down (not counting the quick-start power-down).
3. No charging indication. I'm not sure if this is a hardware or software issue. My device will charge, but it does not give any indication on the screen or the battery icon.
Now I'm stuck wondering what to do. Did I ruin this device? I wanted to avoid rooting it because of the loss of 4G data, but now I'm afraid that I might need root-permissions to fix whatever I messed up.
Thanks in advance for your help.
Daniel
PS. Just so you all know my experience, I've rooted and maintained a droid incredible and currently, my galaxy nexus. I however, have no programming experience what-so-ever. I'm just good at following directions (usually).
Click to expand...
Click to collapse
Thanks
What is the firmware version of S7-302u are you installed in your S7-303u?
Hey, I have the springboard and did the exact thing you did, somehow the stock recovery was all messed up, best bet is to install twrp using fastbood and cm10. just follow after_silences instructions here,
http://forum.xda-developers.com/showthread.php?t=2045808
[Edit]once you change tmo stock firmware you'll lose your 4g option(there my be a fix for this now)but you will be able to text and make calls over 2g, edge2 and 3g"no need for WiFi or side app"[Edit]
Hello all, My daughter bought a razr off of Ebay and made the mistake of purchasing from a seller that does not accept returns. Anyway when she first got it the screen would rotate constantly and it kept saying the HDMI port was being used. I did some reading and found out you actually could do a reboot on the droid (Sorry cant remember what its officially called) by holding the volume up down etc. buttons. That fixed the other two issues but now the keyboard does not function properly, sometimes when you press a letter it types that letter several times or the phone freezes up. I told her to try and download another keyboard and that doesnt work because if she trys to go to the market she gets a message an update is needed and it loops.
I have rooted a few phones no expert by any means, but if someone could point me in the right direction I would appreciate it.
durtydawg said:
Hello all, My daughter bought a razr off of Ebay and made the mistake of purchasing from a seller that does not accept returns. Anyway when she first got it the screen would rotate constantly and it kept saying the HDMI port was being used. I did some reading and found out you actually could do a reboot on the droid (Sorry cant remember what its officially called) by holding the volume up down etc. buttons. That fixed the other two issues but now the keyboard does not function properly, sometimes when you press a letter it types that letter several times or the phone freezes up. I told her to try and download another keyboard and that doesnt work because if she trys to go to the market she gets a message an update is needed and it loops.
I have rooted a few phones no expert by any means, but if someone could point me in the right direction I would appreciate it.
Click to expand...
Click to collapse
Have you tried factory resetting it? Do you know if it has anything custom installed?
Sent from my SAMSUNG-SGH-I777 using xda app-developers app
At that point i would just reflash the .SBF file with the batman utility 1.8
I have the D-800 AT&T LG G2, It was rooted with KitKat 4.4.2. After I rooted my phone, I tried several different ways to install TWRP onto it. I tried FreeGee, adb shell, and straight from TWRP App, nothing worked, because when I tried to boot into TWRP it would just come up with the LG Logo and "Secure Boot Error" and "Certification Error" or something like that, then be a blank screen. I then just held the power button to turn it off, and it would turn back on and run fine, no problem. I figured it never installed right, and so I left TWRP alone. I know you are not supposed to take an OTA after install TWRP, but thinking TWRP never installed on the phone, I took the OTA, and now it will do the "Error" messages and blank screen, but my power off, power on trick doesn't work anymore. I can boot into Recovery Mode, but when I do a Factory Reset, the screen just goes blank. I have tried to put it into Download Mode by pressing Volume Up + Power when hooked up to a PC, but nothing happens. I feel as though its a tough brick. Please Help!
Dirk1616 said:
I have the D-800 AT&T LG G2, It was rooted with KitKat 4.4.2. After I rooted my phone, I tried several different ways to install TWRP onto it. I tried FreeGee, adb shell, and straight from TWRP App, nothing worked, because when I tried to boot into TWRP it would just come up with the LG Logo and "Secure Boot Error" and "Certification Error" or something like that, then be a blank screen. I then just held the power button to turn it off, and it would turn back on and run fine, no problem. I figured it never installed right, and so I left TWRP alone. I know you are not supposed to take an OTA after install TWRP, but thinking TWRP never installed on the phone, I took the OTA, and now it will do the "Error" messages and blank screen, but my power off, power on trick doesn't work anymore. I can boot into Recovery Mode, but when I do a Factory Reset, the screen just goes blank. I have tried to put it into Download Mode by pressing Volume Up + Power when hooked up to a PC, but nothing happens. I feel as though its a tough brick. Please Help!
Click to expand...
Click to collapse
Bump Please. Same Exact Problem With Me, Rooted, Couldnt Get A Recovery Installed (Even Though I've Literally Been Doing Custom ROMs Since The G1 Released) And As Of The Other Day, AT&T Kept Bugging Me To Update To 4.4.2, Even Though I Was Already At 4.4.2. I Kept Declining, But Today My Battery Died, And When It Turned On, It Automatically Installed It, And I'm Getting The Same Errors And Everything.
Send It In
dotjsx said:
Bump Please. Same Exact Problem With Me, Rooted, Couldnt Get A Recovery Installed (Even Though I've Literally Been Doing Custom ROMs Since The G1 Released) And As Of The Other Day, AT&T Kept Bugging Me To Update To 4.4.2, Even Though I Was Already At 4.4.2. I Kept Declining, But Today My Battery Died, And When It Turned On, It Automatically Installed It, And I'm Getting The Same Errors And Everything.
Click to expand...
Click to collapse
I could not find a fix for this problem. Instead, I sent it back saying that it updated automatically and then it didn't work. They can not tell that you have rooted it, because it is so messed up, SO DONT TELL THEM THAT YOU DID! It'll take about 2-3 weeks foe it to be sent back. It'll be free as long as you are under warranty. Just talk to a customer service person on LGs Online Customer Service people. I hope this helps you out!
Dirk1616 said:
I could not find a fix for this problem. Instead, I sent it back saying that it updated automatically and then it didn't work. They can not tell that you have rooted it, because it is so messed up, SO DONT TELL THEM THAT YOU DID! It'll take about 2-3 weeks foe it to be sent back. It'll be free as long as you are under warranty. Just talk to a customer service person on LGs Online Customer Service people. I hope this helps you out!
Click to expand...
Click to collapse
Thanks For The Suggestion. Ironically, I Was Just At The AT&T Store Because They Were Selling Otterbox Defenders For 25 Bucks, And I Told The Guy That My Phone Was Rooted. I'll Have To Go To Another Store. I'm Working On The Linux Fix As We Speak, So Hopefully I Wont Have To Send It In.
dotjsx said:
Thanks For The Suggestion. Ironically, I Was Just At The AT&T Store Because They Were Selling Otterbox Defenders For 25 Bucks, And I Told The Guy That My Phone Was Rooted. I'll Have To Go To Another Store. I'm Working On The Linux Fix As We Speak, So Hopefully I Wont Have To Send It In.
Click to expand...
Click to collapse
I have tried the Linux fix, that didn't work for me, hope it works out for you. Talk to LG, they are the ones who will fix it. You will have to send it to them. I used United States Postal Service, it costed me like 9 dollars, which isn't bad. Good Luck!
Forgive me for posting something that by most accounts on the forum would be considered redundant, but I have looked around over the past several weeks on XDA and have failed to solve my problem. I foolishly deleted my entire OS and here is just how far I have come since trying to bring the device back to stock:
The RUU’s I have seen posted haven’t worked for me. I’ve gone through the process several times with different RUU’s and I always get stuck with Error 155. Yesterday however, I thought I hit pay dirt when I did “adb push Sprint_One_Stock_Rooted_Deodexed_4.06.651.4.zip. /sdcard/”. Once the push completed, I ran it in TWRP and it reported successful. When I reboot the device, I get as far as the home screen (where you swipe up to unlock) and then it just reboots. After swiping/rebooting several times, it eventually comes to the first screen you would expect to see when performing a factory reset where you choose a language. From there, I can get to the screen to input the password to my wifi connection but the device either reboots or reports “com.htc.htcdialer is not responding”
I feel as if I am close, so perhaps there is a step I am leaving out. I should also note that I am no longer on Sprint, but the device was bought from them and I’d like to properly restock the phone for trade or resale.
Any advice you guys can offer is awesome:fingers-crossed:
HELP!
1st gen Nexus 7. Came home today and found it in the google 4 color boot loop swishing the balls around and around. I don't remember rebooting it or installing any updates, so I just let it run.
20 minutes later- still there.
I powered it off, press the down+power, get to the restore- only to get 'system command not recognized' (unfortunately I didn't write it down, but it showed a flat android with a red ! over the open chest).
Kids started screaming about some trauma... came back... tablet was black. Tried rebooting- nogo. Tried powering up/down- nogo. Hold power for 2 minutes, all buttons, no buttons, down, up, etc- nothing.
Plugged it into the PC- get a 'APX mode', but still no screen and no power charging logo.
I've had the damn thing for not even 3 weeks. Can't even tell you what the last update was but it wasn't lollipop as I hadn't seen that yet when my nexus 4 got updated 2 weeks ago.
No, I didn't do wheelie or any backups because I hadn't made any changes to the system. I've got nothing.
32gb model. Don't know what else I can get off of this brick.
Yes, I've read all the threads I can find on APX mode- installed android toolkit, tried to find the dropbox files to get the windows restore- nogo.
I'll take any suggestions or ideas. And no, I really wasn't f-ing around with it either- it's for the 6 year old kid who needs work on sight words and math... I don't need to be running crazy stuff on it... (Feel free to move to appropriate forum as I only saw Nexus 7 2013)
Anyone? Bueller ?
Did I post in the wrong forum? Or am I really just SOL?