[FYI: I don't a thing about tech stuff, but I can follow directions well enough if they're spelled out for me.]
I rooted my KF the day I got it using KF Utility. I don't remember what I did, and I certainly didn't understand much of it; I just followed the steps. That was several months ago (in December), and I haven't messed around with anything since. Everything worked fine, no problems. Haven't made any significant changes in months.
Then today, I tried to turn it on; the power light went on and the words "kindle fire" flashed for a second -- and then both disappeared. I connected it to a charger, and the same thing happened -- both, even the power light, disappeared after a second.
Same thing happens when I tried to connect it to my computer -- and my computer won't even recognize that it's there.
[It's now been connected to a wall charge for several hours, but the power light's not even glowing.]
What do I do? Is it "bricked"? And if so, how do I "unbrick" it, especially if my computer can't even recognize it?
Thank you in advance!
KF won't start, charge, or connect to PC
Absurd1 said:
[FYI: I don't a thing about tech stuff, but I can follow directions well enough if they're spelled out for me.]
I rooted my KF the day I got it using KF Utility. I don't remember what I did, and I certainly didn't understand much of it; I just followed the steps. That was several months ago (in December), and I haven't messed around with anything since. Everything worked fine, no problems. Haven't made any significant changes in months.
Then today, I tried to turn it on; the power light went on and the words "kindle fire" flashed for a second -- and then both disappeared. I connected it to a charger, and the same thing happened -- both, even the power light, disappeared after a second.
Same thing happens when I tried to connect it to my computer -- and my computer won't even recognize that it's there.
[It's now been connected to a wall charge for several hours, but the power light's not even glowing.]
What do I do? Is it "bricked"? And if so, how do I "unbrick" it, especially if my computer can't even recognize it?
Thank you in advance!
Click to expand...
Click to collapse
If you have the FIREFIREFIRE logo I hope this will help.
1. Make sure you still have the driver installed for you KF from KindleFireUtitly.
2. Open command prompt
3. change directory
cd C:\KindleADB
4. Check and see if adb services are running
adb devices
It will not come back with any device running and that is ok.
5. Look in the KINDLEFIREUTITLY folder for a bat file named Run.bat
double click and hit run and it will open a red command prompt.
After it has ran just a few short seconds it will give you a few number prompts. Chose number 5. and reboot Kindle and it will reinstall TWRP for you. These steps will also help if you ever get stuck in FIREFIREFIRE logo again.
I really hope this helps.
Thanks,
JohninLex
JohninLex said:
If you have the FIREFIREFIRE logo I hope this will help.
1. Make sure you still have the driver installed for you KF from KindleFireUtitly.
2. Open command prompt
3. change directory
cd C:\KindleADB
4. Check and see if adb services are running
adb devices
It will not come back with any device running and that is ok.
5. Look in the KINDLEFIREUTITLY folder for a bat file named Run.bat
double click and hit run and it will open a red command prompt.
After it has ran just a few short seconds it will give you a few number prompts. Chose number 5. and reboot Kindle and it will reinstall TWRP for you. These steps will also help if you ever get stuck in FIREFIREFIRE logo again.
I really hope this helps.
Thanks,
JohninLex
Click to expand...
Click to collapse
Well, like I said, I don't know much about any of this stuff, but here's what I can tell you:
I don't have FIREFIREFIRE. Not really sure what that is, but it's certainly never been on my Kindle.
What I did try doing was following those steps in Kindle Fire Utility anyway. I can get it to the point where it says:
ADB Status: Online
ADB Rooted: No
Boot Status Unknown
If from there I hit 5 (to "install latets TWRP recovery"), I get a whole bunch of
"The system cannot find the path specified." for each step it goes through, until finally it gets here:
"If we get stuck here a long time, check the ADB drivers in windows.
Fastboot uses a different device than ADB, so make sure it is installed as an
ADB device. If you see "kindle" in device manager, you need to install the
drivers. You can also try running install_drivers.bat in the drivers folder.
Do NOT unplug the kindle if we are stuck here, leave it plugged in and on.
Do NOT touch the kindle at all if we are stuck.
Setting Normal Bootmode.
Please wait..."
To reiterate again -- I don't know what any of this ADB stuff is, where to find it, etc.
We are in the same boat. Was messing around w/ someone's Bare Bones CM7, and as per instructions, clicked wipe SYSTEM, and since then my device has been with screen "on" but black; non response to power button weather plugged on AC adapter or USB. Will have to research the forums tomorrow (cant find search function now) and let you know if I find a fix and please do the same if you find something first.
Sincerely,
-RM
---------- Post added at 08:49 AM ---------- Previous post was at 08:37 AM ----------
Actually --- I've just resolved the issue.
I had it plugged into the computer (still unresponsive), held down the power button for about 25 seconds, heard the computer do the "tuh-rup" sound, prayed, could finally stop seeing the "black screen" while on, it was pure black due to it powering off. After it was off, I powered back up and was able to get back into TWRP. Restored, did not wipe system and presto... hopefully you can get yours fixed.
theartofbone said:
Actually --- I've just resolved the issue.
I had it plugged into the computer (still unresponsive), held down the power button for about 25 seconds, heard the computer do the "tuh-rup" sound, prayed, could finally stop seeing the "black screen" while on, it was pure black due to it powering off. After it was off, I powered back up and was able to get back into TWRP. Restored, did not wipe system and presto... hopefully you can get yours fixed.
Click to expand...
Click to collapse
Nope, that's not doing anything for me. My kindle won't power on. All it does is display "Kindle Fire" for one second, then go dead.
Does anyone have ANY advice?
oundsde good
Try a different charger and plug into the wall for a little while.
_Justin said:
Try a different charger and plug into the wall for a little while.
Click to expand...
Click to collapse
Tried that. No luck.
Do you have a chat program, or google talk? I'll help you out.
_Justin said:
Do you have a chat program, or google talk? I'll help you out.
Click to expand...
Click to collapse
..........
My device has the same issue, it powers down as soon as I connect it to a PC or charger. The interesting thing, that it is charging, but the led is dark. When I take it off the charger the next day, it boots up and fully charged. (when I connect a cable again it shuts down immediately)
If you find out something I would be also interester. (I've also rooted before 6.2, than I've lost root, than after I while I've faced these issues)
Alright, unless any folks have any other advice, I'm gonna go ahead and contact Amazon for a return.
try to charge it with the wall charger for some hours - check the charger - should have ~1.8A - maybe the orange light is showing up after half an hour
try to power it off by holding pwr ~20sec to allow better charging - if you can't let it on the charger - try to power it off later (eg after an hour)
look here about charger spec and contact problems:
http://forum.xda-developers.com/showthread.php?p=23035482#post23035482
some had success with a factory cable:
http://forum.xda-developers.com/showthread.php?p=23034046#post23034046
Related
My kindle fire is rooted and TWRP installed.
All has been fine since this was done, almost a month ago.
Suddenly, the fire keeps rebooting. Further, everytime it reboots, it gets stuck at the yellow triangle with the orange colored button.
I then have to turn it off and on and during the green button phase:
fastboot oem idme bootmode 4000
and then
fastboot reboot
Work fine. The fire reboots and goes to the "Kindle Fire" logo.
But immediately when the lock screen appears, the fire powers down again. To add insult to injury, it always reboots and gets stuck at the triangle.
I can only connect to the fire during the very limitted time it comes up from a hard power down and the light is green. About 10 seconds. Enough time for the fastboot commands above, but little else.
I cannot enter TWRP recovery mode, either. If I push the green button and it turns to orange, trying to go into recovery, it just hangs with the yellow triangle.
I don't think TWRP is responsible for the reboots, however. Nothing has changed with it since I installed it a few weeks ago. I never managed to get it into recovery mode, but I let it be for a while since it was booting into the system. (I was waiting for CM9 to be ready before I tackled it)
This may have been a mistake as now I have no way to interface with the device, but that's the situation.
The only thing I changed recently was intsall Titanium Backup, but I can't imagine how that would case the reboot problem? I did set it to auto backup, could that be it? (not that I can do anything about it if it was)
I also saw around that some people were having problems with constant reboots in Dec. due to WiFi issues, but supposedly update 6.2.1, which I have, fixed the issue.
Anyway, I'm quite ready to chuck stock for CM7 if that will fix it, but I don't know how to get there from here. Any help would be appreciated.
Oh, and I should mention that I am running linux, not windows, so utilities for windows won't help. Has to be a manual solution.
Tom
sound like a battery issue - tried to charge with the wall-charger for an hour or so to get it stable ?
if it will help you there is also a kfu for mac/linux:
http://forum.xda-developers.com/showpost.php?p=21369040&postcount=653
b63 said:
sound like a battery issue - tried to charge with the wall-charger for an hour or so to get it stable ?
Click to expand...
Click to collapse
I thought of that! I did leave it plugged in overnight, last night, but I am not wholly sure the KF will recharge when not turned on.
if it will help you there is also a kfu for mac/linux:
http://forum.xda-developers.com/showpost.php?p=21369040&postcount=653
Click to expand...
Click to collapse
I can't believe I missed that! Thanks so much. Maybe it will help, I'll let you know.
Tom
I cannot explain this, but I reinstalled TWRP with the utility and now all is well.
The battery is, in fact, fully charged, so that wasn't the issue.
Seems to have been connected to my boched instillation of TWRP, thought I can't imagine how or why it would take almost a month ot manifest itself.
Strange, but I'm glad it's working. Thanks for pointing out the KFU for linux!
Tom
glad to help ...
please mark the subject of the topic (edit first post) with [Solved]
Ha! I believe I figured it out.
Amazon pushed out 6.2.2 and that broke root again. Working on the fix...
Damn, I thought I had it set up not to update.
Will fix OP with solved, thanks.
So I'm stuck on the FireFireFire logo (Fire Hazard Symbol) before I get to recovery. The KF will not go past this slash screen into normal boot, nor will it go into recovery when press the power button (light stays Amber and does nothing).
To make matters worse, when I plug it into my computer, the KF shows up then goes away within 10 seconds. It will pop up again in device manager and disappear again within 10 seconds. After that, I will not show as trying to connect and I have to turn the KF and retry.
I cannot use KF Utility because my KF will not stay active on my computer long enough to do it. I have yet to try it on another computer, but I don't think I have too many options left.
Oh, XDA-Developers, you're my only hope.
[Issue Resolved]
I reinstall the recovery by quickly using the KF Utility 9.1. It seems to have reinstalled and working well again. If anyone has similar issues as I had, try reinstalling recovery. Thanks!
Malhou said:
So I'm stuck on the FireFireFire logo (Fire Hazard Symbol) before I get to recovery. The KF will not go past this slash screen into normal boot, nor will it go into recovery when press the power button (light stays Amber and does nothing).
To make matters worse, when I plug it into my computer, the KF shows up then goes away within 10 seconds. It will pop up again in device manager and disappear again within 10 seconds. After that, I will not show as trying to connect and I have to turn the KF and retry.
I cannot use KF Utility because my KF will not stay active on my computer long enough to do it. I have yet to try it on another computer, but I don't think I have too many options left.
Oh, XDA-Developers, you're my only hope.
[Issue Resolved]
I reinstall the recovery by quickly using the KF Utility 9.1. It seems to have reinstalled and working well again. If anyone has similar issues as I had, try reinstalling recovery. Thanks!
Click to expand...
Click to collapse
Hi,
I got a problem very similar to yours. I tried to root my KF (obvioulsy I didn´t know what I was doing) and now I get the KF looping on load screen. It does not not get recognized by the computer and, if not connected to the usb or ac charger it won´t do anything (tried to press for 30 sec and nothing). When it´s connected it will only flashes the KF logo.
I also tried to connect to a different computer. The KF appears for few seconds on device manager and then vanishes again. Do not know what to do. I tried to download the KFU you mentions but that didn´t worked (unless I used the wrong option)
Do you have any suggestion? Thanks
andersonrel said:
Hi,
I got a problem very similar to yours. I tried to root my KF (obvioulsy I didn´t know what I was doing) and now I get the KF looping on load screen. It does not not get recognized by the computer and, if not connected to the usb or ac charger it won´t do anything (tried to press for 30 sec and nothing). When it´s connected it will only flashes the KF logo.
I also tried to connect to a different computer. The KF appears for few seconds on device manager and then vanishes again. Do not know what to do. I tried to download the KFU you mentions but that didn´t worked (unless I used the wrong option)
Do you have any suggestion? Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1623244
I literally just got the 4.3 OTA update. Phone was fully charged... like 98%. I went ahead and let it update. It rebooted, and it got about 75% into updating and then the icon switched to the sideways android with the red caution symbol and said "Error". I let it sit there for awhile hoping it would do something. It didn't, so I held down power to reboot. It rebooted to the same icon, but now says "No command". I did the vol up/power to get into the wipe/reboot options. I went ahead and rebooted. Every single time... I see the Google logo for like a min, then to the sad android logo w/ "No command". Now I can't even get that far, the indicator light flashes red. I've read that indicates a totally drained battery. Not sure how it can go from full charged to fully drained in a matter of minutes. However on the issue of the error and no command, is my device dead? I've never rooted it or used custom roms. I got the N4 for the pure vanilla stock experience, so I never felt rooting was needed. Any advice? Should I just call Google and request replacement?
I would try a few things first before calling Google. Sometimes the battery doesn't show its correct percentage, it's pretty common on my N4 as far as I can tell. Maybe you've just run out of battery. Let it charge for half an hour or so and then try it again.
If you can't boot to system after that, turn off your phone, press and hold volume down and power buttons at the same time for a few seconds until it boots to bootloader. If you can't boot to bootloader after doing this let it charge for more time, an hour or two.
Sometimes, after the battery has run dry completely it is really hard to turn the phone on (I've even seen this behavior on my 7 years old Nokia). One question, does a charging animation shows up when you plug your phone?
Mercado_Negro said:
I would try a few things first before calling Google. Sometimes the battery doesn't show its correct percentage, it's pretty common on my N4 as far as I can tell. Maybe you've just run out of battery. Let it charge for half an hour or so and then try it again.
If you can't boot to system after that, turn off your phone, press and hold volume down and power buttons at the same time for a few seconds until it boots to bootloader. If you can't boot to bootloader after doing this let it charge for more time, an hour or two.
Sometimes, after the battery has run dry completely it is really hard to turn the phone on (I've even seen this behavior on my 7 years old Nokia). One question, does a charging animation shows up when you plug your phone?
Click to expand...
Click to collapse
It's been charging now for a little over an hour. No animation or indication the battery may be drained other than the red indicator light when I try to go to into the boot loader. Still can't do anything. If I power it on, I see Google logo for awhile, then sad Android icon and "no command". If I try to go into bootloader, just red indicator light and black screen. All while plugged in.
I just don't understand how it went from fully charged to drained in minutes. It was plugged in for hours today. In fact I initiated the OTA update only about 20-30 min after taking it off the charger.
Unplug your device, press and hold the power and volume down buttons for a few seconds until it boots to the bootloader. Now plug your phone again and let it charge.
Mercado_Negro said:
Unplug your device, press and hold the power and volume down buttons for a few seconds until it boots to the bootloader. Now plug your phone again and let it charge.
Click to expand...
Click to collapse
Alright, it's now been charging for 3 hours. I did what you just suggested. All that happens is I see a white Google logo for about 10 seconds, then it goes black. I think the device is off at this point. Stupid question I'm sure... I can't dock my phone to my computer to get any of my data at the "no command" screen can I? It needs to be fully booted, right?
Get into recovery, wipe cache, then it "should" boot.
ksilver89 said:
Get into recovery, wipe cache, then it "should" boot.
Click to expand...
Click to collapse
Like I said above, I'm not able to. I hold down power + vol up and it just shows white Google logo then goes black.
Well hmmm. I just did power + vol down for the hell of it, and I have a menu. Selected "recovery mod" and it just went straight to the sad Android icon with "No command".
I'm not sure what to make of all the stuff I see on this menu...
https://dl.dropboxusercontent.com/u/28754710/20130730_100302.jpg
Here is a short video of what I get from that menu when trying to go into recovery...
https://dl.dropboxusercontent.com/u/28754710/20130730_100936.mp4
For the sake of simplicity, learn how to use Fastboot. You should find more than enough information in the General section.
All you need to do is run this command in bootloader mode.
Code:
fastboot format cache
Edit:
Just saw the video, press vol up + power together in the recovery to access the menu.
ksilver89 said:
For the sake of simplicity, learn how to use Fastboot. You should find more than enough information in the General section.
All you need to do is run this command in bootloader mode.
Code:
fastboot format cache
Edit:
Just saw the video, press vol up + power together in the recovery to access the menu.
Click to expand...
Click to collapse
Again... like I said before vol up + power does nothing. I can take a video if you like.
Disregard the above. Got it into recovery. I guess my pushing was off or something. I took the rigid case off and made it easier to press the vol button. Let's see what happens now.
Alright. Got into recovery, did a wipe data/factory reset, still no dice. This time it rebooted several times, Google white logo each time, then finally a sad Android icon with "No command". Guessing next step is to download it and try updating via ADB?... or just say screw it and call Google and initiate a replacement?
Alright, it is screwed. Long guide here: http://forum.xda-developers.com/showthread.php?t=2010312
Short guide:
1. You need basically 3 things, the factory image, fastboot, and nexus 4 drivers
2. Download and setup all of them.
3. Extract the factory image tgz file TWICE until you see a folder.
4. Place "fastboot" into that folder.
5. Unlock your bootloader, shift + right click inside the folder, Open command window here. Run "fastboot oem unlock" and read the agreement (it's screwed anyway), select Yes if agree.
6. Once unlocked, run "flash-all".
7. Go running around your house for 10 mins.
Warning: This operation will wipe everything in your phone, if there's any crucial data, edit flash-all.bat to remove "-w" flag, and remove userdata.img in the occam zip.
Edit:
Or probably you can just get a toolkit...
ksilver89 said:
Alright, it is screwed. Long guide here: http://forum.xda-developers.com/showthread.php?t=2010312
Short guide:
1. You need basically 3 things, the factory image, fastboot, and nexus 4 drivers
2. Download and setup all of them.
3. Extract the factory image tgz file TWICE until you see a folder.
4. Place "fastboot" into that folder.
5. Unlock your bootloader, shift + right click inside the folder, Open command window here. Run "fastboot oem unlock" and read the agreement (it's screwed anyway), select Yes if agree.
6. Once unlocked, run "flash-all".
7. Go running around your house for 10 mins.
Warning: This operation will wipe everything in your phone, if there's any crucial data, edit flash-all.bat to remove "-w" flag, and remove userdata.img in the occam zip.
Edit:
Or probably you can just get a toolkit...
Click to expand...
Click to collapse
Thanks for your help. I appreciate it. I'm probably going to give this a try, couldn't get any worse. I think all data is gone anyhow when I did the factory reset option in the recovery, right? I did just call Google, they said I could get a replacement no problem, but that will probably take a week.
pixelbat said:
Thanks for your help. I appreciate it. I'm probably going to give this a try, couldn't get any worse. I think all data is gone anyhow when I did the factory reset option in the recovery, right? I did just call Google, they said I could get a replacement no problem, but that will probably take a week.
Click to expand...
Click to collapse
Yes, what he suggested should get you up and running again (if not, then yes your phone needs a replacement). I saw the video and the image. I'm pretty sure your system was wiped somehow and that's why you can't boot to it anymore. If what he suggested fails I can walk you through the steps to flash each factory image separately.
What would you do if the nexus 4 drivers wont install?
I have similar problem, I got the 4.3 update ota and it crashed half way through and now it gets stuck on the X logo. I was trying to follow a guide (http://forum.xda-developers.com/showthread.php?t=2010312) to install 4.3 back onto the device but failed at the first hurdle, when plugin the phone in it fails on the driver software installation - mtp usb device failed.
Is there any other way to do it?
pixelbat said:
Thanks for your help. I appreciate it. I'm probably going to give this a try, couldn't get any worse. I think all data is gone anyhow when I did the factory reset option in the recovery, right? I did just call Google, they said I could get a replacement no problem, but that will probably take a week.
Click to expand...
Click to collapse
unplug your phone. reboot into bootloader (vol down + power) but don't plug it in
downloaded the file posted in this topic from the google website.
http://forum.xda-developers.com/showthread.php?p=44088784
once you download it, extract it to a folder
then open up flash_all.bat in notepad, and it will say -w near the end. remove that (leaving it would wipe all of your data) and save the file
then run it, it will say waiting for device. plug your phone in and it will start updating
flipfamous said:
What would you do if the nexus 4 drivers wont install?
I have similar problem, I got the 4.3 update ota and it crashed half way through and now it gets stuck on the X logo. I was trying to follow a guide (http://forum.xda-developers.com/showthread.php?t=2010312) to install 4.3 back onto the device but failed at the first hurdle, when plugin the phone in it fails on the driver software installation - mtp usb device failed.
Is there any other way to do it?
Click to expand...
Click to collapse
Which driver did you try to install? Naked Drivers 0.72? What OS (Win8, Win7, etc)?
Plug your device in, go to control panel, click on Device Manager, scan for hardware changes or select the device with a yellow exclamation mark. Click on "Update driver" and search for the drivers in your PC (where you downloaded them). That should work.
Just Boot from a ubuntu live cd, install fastboot with apt-get and get started
Gesendet von meinem Nexus 4 mit Tapatalk 4 Beta
sa·yo·na·ra
ˌsīəˈnärə/
Thanks a lot for the info !
I bet some dudes will be really happy to get their devices back up and running again
Thanks
In case of lost boot I can not use this way????
vdsno1 said:
In case of lost boot I can not use this way????
Click to expand...
Click to collapse
It is going to depend on why you lost boot. This really only applies to those that forced their device into Fastboot mode, particularly anyone that used a Factory Fastboot cable, when you have a condition where the device will not turn back on. It times out of QHSUSB_BULK mode & then is reset by a long hold power condition.
If you made changes to certain system files without properly applying permissions, this could also possibly help. If you however, completely removed system files, then I have no idea. I have not tested that yet, though it seems that it may as the HDX does appear to hold a good portion of the raw firmware on-board for some reason I have not been able to completely determine yet.
GSLEON3 said:
It is going to depend on why you lost boot. This really only applies to those that forced their device into Fastboot mode, particularly anyone that used a Factory Fastboot cable, when you have a condition where the device will not turn back on. It times out of QHSUSB_BULK mode & then is reset by a long hold power condition.
If you made changes to certain system files without properly applying permissions, this could also possibly help. If you however, completely removed system files, then I have no idea. I have not tested that yet, though it seems that it may as the HDX does appear to hold a good portion of the raw firmware on-board for some reason I have not been able to completely determine yet.
Click to expand...
Click to collapse
Can you give me the link of the software QHSUSB_BULK or not????? I can not find out, and apparently my kindle fire is completely white and 1 computer file no longer anything I'm also trying to recover!
---------- Post added at 04:19 PM ---------- Previous post was at 03:58 PM ----------
I have seen one of the original rom on kindle fire hdx address: http://www.amazon.com/gp/help/customer/display.html/ref=hp_left_v4_sib?ie=UTF8&nodeId=201357190
But the problem here is that I can not be restored with the original rom, I can not connect memory to copy this rom to proceed very difficult recovery method one can not??
GSLEON3 said:
Okay. There is a secondary reset in the Kindle Fire HDX Bootloader.
Those of you that have the previously thought brick that gives you the QHSUSB_BULK device USB install, you are NOT bricked.
you need to let the device sit for a few minutes & then press & hold the power button for several minutes. I have successfully recovered from this state doing this (purposely) numerous times. Be patient. Let your device sit in BULK mode for 5 minutes WITHOUT touching anything. Leave it unplugged & do not press any buttons.
After 5 minutes, press & hold ONLY the power button for approximately 2 minutes. It should boot in approximately 90 second to 2 minutes, after which, immediately release the power button & let the device restart.
This works for me on BOTH HDX 7 & 8.9 devices without fail.
Click to expand...
Click to collapse
I'll try this when I get home, thanks!
vdsno1 said:
Can you give me the link of the software QHSUSB_BULK or not????? I can not find out, and apparently my kindle fire is completely white and 1 computer file no longer anything I'm also trying to recover!
---------- Post added at 04:19 PM ---------- Previous post was at 03:58 PM ----------
I have seen one of the original rom on kindle fire hdx address: http://www.amazon.com/gp/help/customer/display.html/ref=hp_left_v4_sib?ie=UTF8&nodeId=201357190
But the problem here is that I can not be restored with the original rom, I can not connect memory to copy this rom to proceed very difficult recovery method one can not??
Click to expand...
Click to collapse
There is no software. That is a QC diagnostic mode that sits between DLOAD & the bootloader. It may be possible to trigger DLOAD from this mode, however, currently, I do not know if the appropriate driver is available, nor do I know any of the commands that may be used to trigger DLOAD. Likely, since fastboot does not recognize commands, there is a security element that requires a password/key to be sent before, or with any fastboot or DLOAD commands.
I did however reply in YOUR thread & have yet to see any response. I am not sure what you mean by "all white". Are you saying your device powers on, but will not fully boot? If this is the case, you may be able to use ADB to push the system folder, after remounting the partition as R/W, which should restore the files you removed.
GSLEON3 said:
Okay. There is a secondary reset in the Kindle Fire HDX Bootloader.
Those of you that have the previously thought brick that gives you the QHSUSB_BULK device USB install, you are NOT bricked.
you need to let the device sit for a few minutes & then press & hold the power button for several minutes. I have successfully recovered from this state doing this (purposely) numerous times. Be patient. Let your device sit in BULK mode for 5 minutes WITHOUT touching anything. Leave it unplugged & do not press any buttons.
After 5 minutes, press & hold ONLY the power button for approximately 2 minutes. It should boot in approximately 90 second to 2 minutes, after which, immediately release the power button & let the device restart.
This works for me on BOTH HDX 7 & 8.9 devices without fail.
Click to expand...
Click to collapse
I am at this point right now.Could you please tell me more details like what the kindle show at every step?
It just turn on and turn off. Never sit in a bulk mode.
GSLEON3 said:
Okay. There is a secondary reset in the Kindle Fire HDX Bootloader.
Those of you that have the previously thought brick that gives you the QHSUSB_BULK device USB install, you are NOT bricked.
you need to let the device sit for a few minutes & then press & hold the power button for several minutes. I have successfully recovered from this state doing this (purposely) numerous times. Be patient. Let your device sit in BULK mode for 5 minutes WITHOUT touching anything. Leave it unplugged & do not press any buttons.
After 5 minutes, press & hold ONLY the power button for approximately 2 minutes. It should boot in approximately 90 second to 2 minutes, after which, immediately release the power button & let the device restart.
This works for me on BOTH HDX 7 & 8.9 devices without fail.
Click to expand...
Click to collapse
Never sit in a bulk mode. I have been pushing the power bution for ten minutes.It just turn on and turn off cyclely.
Roogephy said:
Never sit in a bulk mode. I have been pushing the power bution for ten minutes.It just turn on and turn off cyclely.
Click to expand...
Click to collapse
This is only for devices that are stuck in QC HSUSB_BULK mode. If your device bootloops, then it is NOT in this mode. What did you do to it? I need info, concise info on what you did, so I can MAYBE tell you how to start going at recovering it. Also, is it 7" or 8.9"?
GSLEON3 said:
This is only for devices that are stuck in QC HSUSB_BULK mode. If your device bootloops, then it is NOT in this mode. What did you do to it? I need info, concise info on what you did, so I can MAYBE tell you how to start going at recovering it. Also, is it 7" or 8.9"?
Click to expand...
Click to collapse
I need help i ersed everything in my kindle.
i used safestrap and i went to WIPE then i clicked ADVANCE And i clicked format all.
I erased my os now its stuck on the kindle logo Grey.
Lupekid said:
I need help i ersed everything in my kindle.
i used safestrap and i went to WIPE then i clicked ADVANCE And i clicked format all.
I erased my os now its stuck on the kindle logo Grey.
Click to expand...
Click to collapse
I did and stuck just the same ways like Lupekid!!!
Any one help me. I've got about 3 days to return it to normal or die (
GSLEON3 said:
sa·yo·na·ra
ˌsīəˈnärə/
Click to expand...
Click to collapse
really? Thank you.
tianlie said:
really? Thank you.
Click to expand...
Click to collapse
perhaps a chance after the unlock bootloader
Kindle recongnized as qhsusb_bulk
qhsusb_bulk
So...
My Kindle Fire HDX is in the same boat... Honestly, not sure what happened. I had rolled back to 3.2.8, installed Saftstrap, SU, thought that I had disabled the OTA update but only by renaming the file. I was rooted and flashed ggow's Nexus mod on the ROM SLOT 1 and left the stock alone. It was working fine, never tried to update anything that night. Was plugged in and connected and booted to the Nexus side. The next morning I was showing someone how I could switch to the Amazon side through Safestrap and still had no issues. I set the Kindle on my desk at work and looked over to see it at the Kindle Fire logo and below it a progress bar saying Installing System Update! What I don't understand is I had not connected to the WiFi at work. The Kindle was wiped out and did not have the WiFi passwords nor did I accept the WiFi policy when connecting.
I had a couple of file on the SD card that I had transferred via the USB cable on the SD portion of the Kindle. The nexus mod .zip file and a copy of the renamed OTA update file that I had changed the name and extension on. Did it somehow recognize the .zip nexus file as an update and try to load it?? I am lost...
I am able to plug it into the computer and was getting the qhsusb_bulk as the device type. I have tried to access that through adb but it doesn't find it.
Amazon was kind enough to offer me a refurbished kindle for $149. I said I can buy a new HD7 for $99!? So... I have just over a year old 64gb HDX staring at me... asking me why I messed with it. Good question...
If anyone has any advice or possible solution, that would be great!
Thanks
How can i do it i can cannot see a guide
Thinh Duong said:
How can i do it i can cannot see a guide
Click to expand...
Click to collapse
This is an old thread. If there was a guide/instructions they have since been removed. I am not aware of any generalized/repeatable solution to this problem.
OP abandoned - Thread closed
So my girlfriend was using her Google Nexus 7 2012 of 32gb only Wi-Fi triying to play the EA game "The Simpsons: Springfield" while the tablet was charging and when the game loaded it was running slowly till it frozen and then she tried to see all apps open with the 3rd button, she could pull down and see the notification drawer, then she push the 3rd button (that one on the right) but the tablet didn´t respond, instead it will just pull back the notification drawer, then the tablet started to show a notification in the middle of the screen that said "the system process is not responding" (We don´t have screenshots from this notification, that´s what she remember's and I am translating into English from the Spanish she saw) with 2 options, "wait" and "close", she pressed "close" and then it showed another notification saying "the user interface is not responding" (We don´t have screenshots from this notification, that´s what she remember's and I am translating into English from the Spanish she saw) with 2 options, "wait" and "close", she pressed "close" and I am pretty d#%n sure that it was in that moment when it got f$#%&d. Then she left it alone for like 10 minuts but it didn´t do anything, so she attempted to restart it by pressing "power + volume down" buttons together for 10 seconds and when she let the buttons go, that´s when she realized it was gone all wrong, what she saw was this "Android Robot with his belly opened with a lot of words on the down - left of the screen which ended up with look state - unlocked, it also had two arrows on the right-top of the screen, one pointing up and one pointing down, there was also on the top of the screen a red arrow with black background and inside that red arrow had written RECOVERY MODE" then she used the arrows on the right to move what was written on the red arrow, there was at least 3 options, she remember´s the first which was "RECOVERY MODE" and the second that was "POWER OFF" she is also pretty sure that it was a 3rd option but so far she doesn't remember. So she chosen power off with the power button and the tablet powered off automatically and she waited to see the tablet charging but it never appeared, later on, she tried to turn it on, it won't happen.
So now the tablet is totally dead and the only sign of life i have seen is that sound when i plug in the tablet into my pc or her laptop and press the power button, that sound that minds that a device has been mounted and the same sound when i unplug it from the pc or laptop. I have no idea of what should I do with her, my best hope is that I found a genius here patient enough to help me out with this peace of technology. :crying:
Connect to Nexus Root Kit and try to flash stock ROM. There is option for non bootable devices
Sent from my Nexus 4 using Tapatalk
Which Nexus Root Kit?
I only found here the Wugs Nexus Root Toolkit, I already installed the Wugs Nexus Root Toolkit v2.1.6 but I couldn't find the proper way to use it for a non bootable device.
Am I using the correct Nexus Root Kit?
If yes, please tell me: where can i find a step by step guide to solve the problem?
If nope, where can i find the correct Nexus Root Kit with a step by step guide?
Thank's so much in advance for your help, I already tried with the Wugs Nexus Root Toolkit v2.1.6 to flash stock ROM but as the tablet is dead, I couldn't boot it to bootloader, obviously I couldn't either turn the tablet on to allow usb debugging, for all matters, the toolkit need's adb connection to work, and I couldn't find the way to start an adb connection.
Make sure the tablet is not stuck in APX mode. To get out of this: connect the tablet for some time (at least for about 1 hour) to the charger then press for about >=20 sec the power button *only*. Release the button. If the tables was stuck in APX mode, now it should have exited that mode. Now you should be able to boot to bootloader / recovery / system. If this does not work, I suppose your tablet is bricked ...
Its correct NRT. First step is to download correct drivers and make sure it passes full driver test and adb and fastboot work. If that's the case then everything can be flashed (bootloader, recovery and ROM). Here is link to a manual process that shows steps but NRT does it automatically. Look at flashall script
http://www.laptopmag.com/articles/how-to-hard-reset-a-bricked-nexus-7-with-your-pc
Also try connecting to charger, keep it charging for 30 min or so and then try power button
Sent from my Nexus 4 using Tapatalk
Thank's!
Thank's to much for your glorious help!
I tried connecting to a charger about an hour and half and then power button, nothing happened, in approximately 24 housr from now I will follow the step by step guide to unbrick the tablet, thank's for the link, I hope it work's, I let you know later on.
If your device is really bricked, there is no change for reviving it, sorry.
Try installing just adb/fastboot (adb-setup-1.4.3.exe) from https://drive.google.com/file/d/0B0MKgCbUM0itNVB1elljU2NPR0k After installing open cmd window as admin, go to c:\adb and see if "fastboot devices" returns anything. If yes, then download recovery TWRP image (twrp-3.0.2-0-grouper.img) to same folder and type "fastboot boot twrp-3.0.2-0-grouper.img". If recovery comes up then you have options to flash some ROM. To permanently install recovery "fastboot flash recovery twrp-3.0.2-0-grouper.img" Boot loader can be flashed in the same cmd window, If it worked then reboot into bootloader with fastboot.
Why is everyone giving him advice on unbricking when he can't even power on the tablet.
Yeah, you can use ADB to fix a tablet that won't power on so the computer can even load a driver for it. LOL
<sarcasm>
Look, the Nexus 7 has random charging issues especially when it gets drained down to zero battery.
I deal with it on mine sometimes.
Not saying this is your problem, but since you can't even power the device on, it's the first thing I'd look at.
Gotta pop the back cover and reseat the battery connector.
Then try charging again for a couple hours.
Ugh, I've got to do it to mine right now too.
For the third time since I've owned it.
---------- Post added at 12:12 PM ---------- Previous post was at 11:56 AM ----------
Yep, reseating the battery cable fixed it once again for me.
https://www.youtube.com/watch?v=x8u8xSnfCOA