I was given a Fire HD 7th Gen. I cannot get into recovery on it.
The story is that is was on 5.6.2.0 and accidentally downgraded to 5.6.1.0, which in turn never booted.
My diagnosis is...
I plugged it into my pc and I can hear the windows usb connect chime every 10 seconds or so and 2 seconds after a usb disconnect chime.
I cannot do any key combo to get into recovery as i only have a black screen and no more.
Have adb (and am familiar with) installed and the bin downloaded ready to sideload...
any help is appreciated, thanks!!
Did you try holding all the buttons - Volume UP, Volume DOWN and POWER - together for 30 seconds? That may get you back to power on or to recovery.
Did you verify that you can downgrade from 5.6.2.0 to 5.6.1.0 without bricking due to different bootloaders or recoveries? That tablet may now be bricked.
mdvanness said:
I was given a Fire HD 7th Gen. I cannot get into recovery on it.
The story is that is was on 5.6.2.0 and accidentally downgraded to 5.6.1.0, which in turn never booted.
My diagnosis is...
I plugged it into my pc and I can hear the windows usb connect chime every 10 seconds or so and 2 seconds after a usb disconnect chime.
I cannot do any key combo to get into recovery as i only have a black screen and no more.
Have adb (and am familiar with) installed and the bin downloaded ready to sideload...
any help is appreciated, thanks!!
Click to expand...
Click to collapse
donslade said:
Did you try holding all the buttons - Volume UP, Volume DOWN and POWER - together for 30 seconds? That may get you back to power on or to recovery.
Did you verify that you can downgrade from 5.6.2.0 to 5.6.1.0 without bricking due to different bootloaders or recoveries? That tablet may now be bricked.
Click to expand...
Click to collapse
Yes, I have tried that combination to no effect. From what I have read it cannot be downgraded from 5.6.2.0 to anything.
black screen
donslade said:
Did you try holding all the buttons - Volume UP, Volume DOWN and POWER - together for 30 seconds? That may get you back to power on or to recovery.
Did you verify that you can downgrade from 5.6.2.0 to 5.6.1.0 without bricking due to different bootloaders or recoveries? That tablet may now be bricked.
Click to expand...
Click to collapse
my partner was playing a game put it down for a few mins and screen is black. tried power button method nothing. tried with volume and power button and it wont hard reset. hes even taken out the battery ( its 7th gen 10 inch with alexa) any ides what we can do please. i cant contact amazon as i put google play on it. thanks
von1uk said:
my partner was playing a game put it down for a few mins and screen is black. tried power button method nothing. tried with volume and power button and it wont hard reset. hes even taken out the battery ( its 7th gen 10 inch with alexa) any ides what we can do please. i cant contact amazon as i put google play on it. thanks
Click to expand...
Click to collapse
If still under warranty, return it to Amazon for replacement or refund. Otherwise you can try flashing stock firmware back to it. That's assuming you know what version of fire OS it was on.
mdvanness said:
I was given a Fire HD 7th Gen. I cannot get into recovery on it.
The story is that is was on 5.6.2.0 and accidentally downgraded to 5.6.1.0, which in turn never booted.
My diagnosis is...
I plugged it into my pc and I can hear the windows usb connect chime every 10 seconds or so and 2 seconds after a usb disconnect chime.
I cannot do any key combo to get into recovery as i only have a black screen and no more.
Have adb (and am familiar with) installed and the bin downloaded ready to sideload...
any help is appreciated, thanks!!
Click to expand...
Click to collapse
I have the same problem with my amazon fire hd 10 now downgraded it and screen is black same thing with usb sound when plugged into PC tried every possible buttons compilation to enter recovery still nothing happens device not recognized by ADB which I'm very familiar with as well..tried opening the device and unplugged the battery cable from inside then still nothing totally dissembled it and assembled it again same result please let me know if you find a way to bypass this problem..
Mahmud92 said:
I have the same problem with my amazon fire hd 10 now downgraded it and screen is black same thing with usb sound when plugged into PC tried every possible buttons compilation to enter recovery still nothing happens device not recognized by ADB which I'm very familiar with as well..tried opening the device and unplugged the battery cable from inside then still nothing totally dissembled it and assembled it again same result please let me know if you find a way to bypass this problem..
Click to expand...
Click to collapse
You are permanently bricked. However there will hopefully be a fix in a week or two that would allow you to unbrick any Amazon tablet and unlock the bootloader. I have to run a few small tests on my test devices. I have on bricked HD 10 and it just takes a few minutes to complete the test. If successful, it will immediately boot again. After that we have to modify the zip files and scripts for this device.
DragonFire1024 said:
You are permanently bricked. However there will hopefully be a fix in a week or two that would allow you to unbrick any Amazon tablet and unlock the bootloader. I have to run a few small tests on my test devices. I have on bricked HD 10 and it just takes a few minutes to complete the test. If successful, it will immediately boot again. After that we have to modify the zip files and scripts for this device.
Click to expand...
Click to collapse
I do really appreciate the effort, thanks for the fast reply as well will be waiting for the fix.. :fingers-crossed:
Mahmud92 said:
I do really appreciate the effort, thanks for the fast reply as well will be waiting for the fix.. :fingers-crossed:
Click to expand...
Click to collapse
I can't make any promises. We still need to figure out if its possible. I've only glanced at the board of the 10 and it looks like it will work, but I won't know until I can perform the few tests needed. Hopefully tomorrow I will have time.
Sent from my MotoG3 using XDA Labs
Seems I joined to bricked club today (black screen, USB sound wehen plugging in).
Was on newest version (greather than 5.6.2.0, i think 5.6.3.x) and flashed 5.6.2.0.bin (latest you can download from amazon) via adb sideload for a complete reset and a clean device. I thought downgrading would not work if it would lead to problems - hm seems i was wrong
I bought it on 16.01.2018 so the questions is should i try if i get a replacement from amazon or wait if there will be an solution from DragonFire1024 within the next weeks? Not sure if amazon will replace it without trouble
Bierfreund said:
Seems I joined to bricked club today (black screen, USB sound wehen plugging in).
Was on newest version (greather than 5.6.2.0, i think 5.6.3.x) and flashed 5.6.2.0.bin (latest you can download from amazon) via adb sideload for a complete reset and a clean device. I thought downgrading would not work if it would lead to problems - hm seems i was wrong
I bought it on 16.01.2018 so the questions is should i try if i get a replacement from amazon or wait if there will be an solution from DragonFire1024 within the next weeks? Not sure if amazon will replace it without trouble
Click to expand...
Click to collapse
I'm going as fast as I can to try and unlock this thing apparently I always get the crap end of the stick when it comes to things that are easy I always get the hard part. Until I can get out and get a kit to remove the board, we're stuck where we're at. the motherboard needs to be removed and the only way to do that as a special screwdriver and I do not have the tools. But if the weather lets up I will be able to get them.
Bierfreund said:
Seems I joined to bricked club today (black screen, USB sound wehen plugging in).
Was on newest version (greather than 5.6.2.0, i think 5.6.3.x) and flashed 5.6.2.0.bin (latest you can download from amazon) via adb sideload for a complete reset and a clean device. I thought downgrading would not work if it would lead to problems - hm seems i was wrong
I bought it on 16.01.2018 so the questions is should i try if i get a replacement from amazon or wait if there will be an solution from DragonFire1024 within the next weeks? Not sure if amazon will replace it without trouble
Click to expand...
Click to collapse
Try your luck by contacting Amazons Customer Service they seem quite helpful when I wrote to them, explained the situation about downgrading the version and what happened, they simply asked to do some steps like turning of and button compo etc after making sure its bricked they offered to replace it with a new one right away ..but unfortunately I'm not at USA and they can't ship the replacement to Turkey..so my only hope for now is @DragonFire1024 fix
Mahmud92 said:
Try your luck by contacting Amazons Customer Service they seem quite helpful when I wrote to them, explained the situation about downgrading the version and what happened, they simply asked to do some steps like turning of and button compo etc after making sure its bricked they offered to replace it with a new one right away ..but unfortunately I'm not at USA and they can't ship the replacement to Turkey..so my only hope for now is @DragonFire1024 fix
Click to expand...
Click to collapse
We have download mode on the HD 10 which means we can get our bootloader unlocked once we can execute the payload. There won't be such a thing as a bricked tablet. If you can hold off, we just need execution. We have the recovery already. Everything nearly works aside from the script to load and execute the payload. Hopefully we'll get unlocked today.
Bierfreund said:
Seems I joined to bricked club today (black screen, USB sound wehen plugging in).
Was on newest version (greather than 5.6.2.0, i think 5.6.3.x) and flashed 5.6.2.0.bin (latest you can download from amazon) via adb sideload for a complete reset and a clean device. I thought downgrading would not work if it would lead to problems - hm seems i was wrong
I bought it on 16.01.2018 so the questions is should i try if i get a replacement from amazon or wait if there will be an solution from DragonFire1024 within the next weeks? Not sure if amazon will replace it without trouble
Click to expand...
Click to collapse
Although there are (as yet unrealized) prospects of a hardware unlock/rejunivation I would reach out to Amazon. What can it hurt? You might just score a essentially new refurb vs tearing apart your existing 'brick' with the associated risk of damaging it further. You can still pursue that option if Amazon declines to help. Why hold off...keep all options open.
DragonFire1024 said:
We have download mode on the HD 10 which means we can get our bootloader unlocked once we can execute the payload. There won't be such a thing as a bricked tablet. If you can hold off, we just need execution. We have the recovery already. Everything nearly works aside from the script to load and execute the payload. Hopefully we'll get unlocked today.
Click to expand...
Click to collapse
I got the same problem with my Fire HD 10 after flashing rom. Since I don't live in the US, I can not take it back to Amazon. Hope for the fix from you
see this post
https://forum.xda-developers.com/hd...-fire-hd-10-unbricking-anti-rollback-t3896616
i solved this problem with the post
Mine got a black screen today what do i do?
mdvanness said:
I was given a Fire HD 7th Gen. I cannot get into recovery on it.
The story is that is was on 5.6.2.0 and accidentally downgraded to 5.6.1.0, which in turn never booted.
My diagnosis is...
I plugged it into my pc and I can hear the windows usb connect chime every 10 seconds or so and 2 seconds after a usb disconnect chime.
I cannot do any key combo to get into recovery as i only have a black screen and no more.
Have adb (and am familiar with) installed and the bin downloaded ready to sideload...
any help is appreciated, thanks!!
Click to expand...
Click to collapse
This full solution: https://forum.xda-developers.com/hd8-hd10/orig-development/unlock-fire-hd-10-2017-suez-t3913639
Related
so i have a stock rooted a500 i got yesterday new.
have a problem..
10 minutes ago i was setting a wallpaper to a picture of my car. i cropped and set..wallpaper stayed black, so i did it again, still black. so i tried a different picture.
Crash
restarted, now stuck at lock screen, lock button doesnt slide, once you shut screen off, wont turn back on. clock doesnt move either. help?
Snag a paperclip
Hit that reset button.
Failing that, i'm at a loss. Never had anything remotely similar happen.
entropy.of.avarice said:
Hit that reset button.
Failing that, i'm at a loss. Never had anything remotely similar happen.
Click to expand...
Click to collapse
niether have i, i have a custom evo. reset button only restarts it
i didnt flash recovery yet, though i can access the files via usb when its locked at lock screen, so im going to try adb push
Good move
Or you can always toss a full stock ROM image on microSD and flash without custom recovery.
entropy.of.avarice said:
Or you can always toss a full stock ROM image on microSD and flash without custom recovery.
Click to expand...
Click to collapse
ok, adb sees no devices, so ill have to do it that way
where can i find a stock full rom for USA? seems full package links are dead
skullzaflare said:
where can i find a stock full rom for USA? seems full package links are dead
Click to expand...
Click to collapse
Not sure - never done any full package flashes, only update packages. Pretty sure I've seen a bunch of them around these fourms.
Best of luck - hope you don't have a dead tab.
entropy.of.avarice said:
Not sure - never done any full package flashes, only update packages. Pretty sure I've seen a bunch of them around these fourms.
Best of luck - hope you don't have a dead tab.
Click to expand...
Click to collapse
so far it seems i do, tried a update, and still does the same thing
it would be fine if i didnt have a custom boost animation in the system/media
i still have 12 more days warrenty.
is there a way to delete it via computer?
not sure if anyone knew about the hard reset, i contacted acer and played dumb, though i told them what happened.
i was instructed to
Power down the device
hold Vol Up + Power for 3 sec
continue holding Vol up, and keep switch the screen lock back and forth until "erasing cache" comes up on the acer screen
at which point you stop and let it run its course.
said it would take 30 minutes. i fell asleep, 2hrs later i checked it, still same. recontacted acer, another tech said to do the default hard restart with the push pin
worked like a charm
in process of rooting, installing CWM and making backup lol
skullzaflare said:
not sure if anyone knew about the hard reset, i contacted acer and played dumb, though i told them what happened.
i was instructed to
Power down the device
hold Vol Up + Power for 3 sec
continue holding Vol up, and keep switch the screen lock back and forth until "erasing cache" comes up on the acer screen
at which point you stop and let it run its course.
said it would take 30 minutes. i fell asleep, 2hrs later i checked it, still same. recontacted acer, another tech said to do the default hard restart with the push pin
worked like a charm
in process of rooting, installing CWM and making backup lol
Click to expand...
Click to collapse
Hello ,
Did have the same problem and solved it by flashing the update.zip found on this site.
I've put it on the root of the SD card , push start and holding vol down , and then perform the update .
Can you explain me tough what you men by " do the default hard restart with the push pin " .
Thanks
BerreZ said:
Hello ,
Did have the same problem and solved it by flashing the update.zip found on this site.
I've put it on the root of the SD card , push start and holding vol down , and then perform the update .
Can you explain me tough what you men by " do the default hard restart with the push pin " .
Thanks
Click to expand...
Click to collapse
the reboot is for if it stops responding, like a reset button on a computer. its under the usb port
flashing any update zip didnt work for me
skullzaflare said:
flashing any update zip didnt work for me
Click to expand...
Click to collapse
Did you get it from a local retail location? If so, I would just march back there with my receipt and not give too many details - i was working on a picture and it broke and I have no idea what is wrong, etc - they should just give you a new one.
Have you tried clearing the cache? There is a combo with holding power / volume up when booting and using the rotation lock switch, not quite sure how it is done but i think you just hold both and flip the switch like mad - totally sure I have seen the process posted here somewhere.
If you got it via online order, you still should be able to just return it.
Or call acer - they might be able to work some magic.
Best of luck, hope you get it going or at least get a new one. Really sounds like you have a defective unit, I rooted mine the day after I bought it, have had it for nearly two months and multiple rootings/unrootings/rom flashes and have had no issues at all.
Hi, i got a problem with my 10:1 tab. Today i tried to install honeycomb rom using clockworkmod recovery and after the installation and rooting my tab there was a question should flash boot be fixed because the new one will replace other without going back so new flash and root from honeycomb could take it place and i said no to fixing it, second after my tab went off black and it not reacting to anything including trying to power on and get into recovery mode and i tried to push all the buttons and nothing works. Odin doesnt recognize the tab and if i plug it to charger or pc there is no response. The only thing i realized is i heard a plug in usb sound when i connect tab to pc and try to pull the power on button for like 5 seconds i hear plug in and second later plug out usb sound. What can i do to make it works again? I cannot give it to guaranty and all i can do is by myself
Send it to Samsung for a repair.
i cant, i have no guarantee all i can do is by myself, what can i do?
Did you try to hold power button a little longer ? Like 10 or 30sec. This works for some devices
Sent from my GT-P3110 using xda premium
Pull back cover off (use google to figure out how to do so), unplug battery for a few seconds. Plug battery back in. Press and hold power + vol down to try to get into ODIN.
There is no honeycomb rom for these tabs. What did you try to install? Link me.
Holding power button gives nothing, i tried ever combination for a couple minutes and not working. I tried to remove battery yesterday but it was connected via cables and there was no way to remove it without cutting out cables as far as i seen, if anyone can know how i can remove battery then let mw know because i can't find anything ever the internet. I downloaded HoneyVillain_1.2 from here http://forum.xda-developers.com/showthread.php?t=1138115. I tried to plug tab to charger today but after 10 hours it didn't worked at all, still got black screen with no reaction to buttons ;/
Hello
bad news - I killed my P5100 2 months ago and I can't repair it. I have same problem - I can hear plug on / plug off sound in Windows. But i have installed drivers and found that this is OMAP4430 device was connected/disconnected each time. And I can't do anything with my Tab.
I have took my Tab to official Samsung service and I've received answer that it is not repairable - only full replacement of internal board possible, and it costs 300$.
And I have tried to unofficial services and they tells me what my problem. Bootloader was corrupted and device can't start. So it is impossible to repair bootloader because it is protected in Galaxy Tab 2 and they proposed me to replace internal flash memory chip.
So I have dead Tab and wait for ability to programmatically repair my Tab
You can see my thread here http://forum.xda-developers.com/showthread.php?t=1908949, maybe it will be helpful for you
FrostX26 said:
Holding power button gives nothing, i tried ever combination for a couple minutes and not working. I tried to remove battery yesterday but it was connected via cables and there was no way to remove it without cutting out cables as far as i seen, if anyone can know how i can remove battery then let mw know because i can't find anything ever the internet. I downloaded HoneyVillain_1.2 from here http://forum.xda-developers.com/showthread.php?t=1138115. I tried to plug tab to charger today but after 10 hours it didn't worked at all, still got black screen with no reaction to buttons ;/
Click to expand...
Click to collapse
I honestly believe that the Rom you downloaded is for the acer ionica!
See xda has created separate forums for each phone because you can't use one phones rom for another! Yet you flashed that!
There s nothing you can do other than sending your phone for repair!
Sent from my GT-P3100 using Tapatalk 2
Ok so i installed wrong rom for my tab right? Is there something i can do to repair it by myself?
FrostX26 said:
Ok so i installed wrong rom for my tab right? Is there something i can do to repair it by myself?
Click to expand...
Click to collapse
No. Its a paper weight now and you could have prevented this by reading.
If you can't get it into Download Mode, then the only options are to send it to Samsung to fix it, or find some loose papers.
Hey guys, thanks for the answers so far I would like to know if every type of tablet brick can be unbricked? I mean if there is no brick that couldn't be unbricked by using cables and garage methods
FrostX26 said:
Hey guys, thanks for the answers so far I would like to know if every type of tablet brick can be unbricked? I mean if there is no brick that couldn't be unbricked by using cables and garage methods
Click to expand...
Click to collapse
http://www.jtagbox.com/jtag-news/ri...tab-2-101-unbrick-dead-boot-repair-supported/
I don't know how much support you'll get to follow this method but if nothing else will work it's worth a try.
As far as this tablet being unbrickable, that's only true if you don't intentionally flash something that was made for a completely different tablet...
Sent from my GT-P5110 using XDA Premium HD app
Well that's the point, I flashed with rom made for different tablet and it's dead now My question was if any brick could be repaired if i'll give it to someone with all the right tools to resurrect it, or there are certain bricks that can't be repaired no matter what tools and skills the person who attempt it have?
FrostX26 said:
Well that's the point, I flashed with rom made for different tablet and it's dead now My question was if any brick could be repaired if i'll give it to someone with all the right tools to resurrect it, or there are certain bricks that can't be repaired no matter what tools and skills the person who attempt it have?
Click to expand...
Click to collapse
Check my post again for the link as that's the only method that shows up on Google search for this tab.
does odin recognize your tablet?
Is it a tab 2. In your op it just said tab 10:1. Not tab 2. Just making sure as this is the tab 2
sent from MY BAD A$$ ET4G
I might be able to help u
Alright i had the problem recently and heres what i did to fix it If you can get into download mode ur all good from there. To get into download mode hold the power button and up on the volume rocker, if u get a message saying flashing roms is dangerous blah blah blah then press down on the volume rocker to enter download mode. Odin will recognize it if its in download mode, also what model is ur galaxy tab? Also if its a 10 inch model GT5113 i have the stock rom file for it so i could send it to u
Some helpful Info
Maybe you should have said yes? because after all you can't be too carefull , maybe there was something wrong with the rom. If the system asks you if you want to fix ALWAYS say YES. You should have said yes. Why did you say no ?! all right now to the fixing part. PLEASE NOTE I'M NOT AN EXPERT IN ROOTING BUT I'LL GIVE IT A GO. I think that if you can, then power it up and press the VOLUME UP key while holding the power button. From the menu choose recovery and factory reset your device. If it's possible reset rom to default. It should work if not then Post a reply saying not and I'll see what else can be found. Hold on tight for now!There is a Optional thing you can do if the above doesn't work: that is, if possible, you can un-root your tablet with an app from the market. If all of the above is impossible to do, and you cant even power your tab on, it's as useful as a brick, a black screen. Then I'm afraid it's a hard brick fopr you, boyo.
---------- Post added at 03:48 PM ---------- Previous post was at 03:41 PM ----------
FrostX26 said:
Hey guys, thanks for the answers so far I would like to know if every type of tablet brick can be unbricked? I mean if there is no brick that couldn't be unbricked by using cables and garage methods
Click to expand...
Click to collapse
Sorry for my previous post, didn't read the whole forum! Stupid me! ok now there are only two types of brick. Soft brick and hard brick. Soft brick can be fixed, Hard brick - Not quite. And as you said, you flashed a rom for a different tab, maybe thats a compatibility issue. If you want a new os, honeycomb to be exact. You can always upgrade, just search 'honeycomb upgrade'.
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
Hi guys yesterday my nexus freeze in gmail.. so i turn it down by pressing and hold te power button
then the tablet freeze in the Google LOGO
after taht i try to ge into Recovery mode,, it freeze aswell then i just reboot it on bootloader adn i leave it thre for about 1 hour charging
the i try to go to boot loader to fhasl stok rom..
but..!! it wont work.. never turns on..
and it shows in my pc as APX mode
no more than that y tri to start it in bootloader but i just cant with every method i find in internet even i try to charge it by pogo pins and nothing happends
i try to do soetring with nvflash but it said
Unknow devices found and do nothing
pls help me ,!!
radeon9550 said:
Hi guys yesterday my nexus freeze in gmail.. so i turn it down by pressing and hold te power button
then the tablet freeze in the Google LOGO
after taht i try to ge into Recovery mode,, it freeze aswell then i just reboot it on bootloader adn i leave it thre for about 1 hour charging
the i try to go to boot loader to fhasl stok rom..
but..!! it wont work.. never turns on..
and it shows in my pc as APX mode
no more than that y tri to start it in bootloader but i just cant with every method i find in internet even i try to charge it by pogo pins and nothing happends
i try to do soetring with nvflash but it said
Unknow devices found and do nothing
pls help me ,!!
Click to expand...
Click to collapse
Ok as far as I have herd there is no way to rescue a bricked nexus 7 using NVflash if there are no Backed-up Blob files on it. If you just ended up in apx mode without doing anything to its bootloader then it is probably out of charge or needs to have a particular button combo to sort it out
if on the other hand you corrupted the bootloader and after that the device is in a sleep of death then you have hardbricked your nexus 7 'apparently'
good luck
No Custom Bootloader
Hill well i never done something to the bootlaoder no Multibot no Custom bootloader ( factory only )
i try a lot of key combination but nothing happend :/
but my questin is i got a second n7 same specs how can i pull the blob files and,
can i use this files to unbrink the other
if i can pls explainme that
i love my tablet i dont wanna see her die
thnaks..
don't give up
radeon9550 said:
Hill well i never done something to the bootlaoder no Multibot no Custom bootloader ( factory only )
i try a lot of key combination but nothing happend :/
but my questin is i got a second n7 same specs how can i pull the blob files and,
can i use this files to unbrink the other
if i can pls explainme that
i love my tablet i dont wanna see her die
thnaks..
Click to expand...
Click to collapse
Ok if you want to know about how to set up a link between the NVflash tool (on your computer) and your new n7 just use the following proceedure here www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean
As far as your old n7 is concerned if it is definitely hard-bricked and you have not made a backup using NVflash before the brick then there is no known way to save it with only a computer and n7 connected via USB however there is a slim chance your old n7 might just be in a state where it can't access the bootloader because of some power shortage or incorrect button states so do keep trying the key combos and recharging etc because there are a lot of stories of people who escaped using this random strategy. Normally to get into apx mode one would press all three buttons at once so to get out you could do the same so it is worth a try
BTW I have one more trick up my sleeve, if you download WugFresh's toolkit for the n7 (make sure its 2012 edition) then you could try pressing the 'reboot bootloader' option in the advance options menu in the lower left.
good luck
Gloftking said:
Ok if you want to know about how to set up a link between the NVflash tool (on your computer) and your new n7 just use the following proceedure here www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean
As far as your old n7 is concerned if it is definitely hard-bricked and you have not made a backup using NVflash before the brick then there is no known way to save it with only a computer and n7 connected via USB however there is a slim chance your old n7 might just be in a state where it can't access the bootloader because of some power shortage or incorrect button states so do keep trying the key combos and recharging etc because there are a lot of stories of people who escaped using this random strategy. Normally to get into apx mode one would press all three buttons at once so to get out you could do the same so it is worth a try
BTW I have one more trick up my sleeve, if you download WugFresh's toolkit for the n7 (make sure its 2012 edition) then you could try pressing the 'reboot bootloader' option in the advance options menu in the lower left.
good luck
Click to expand...
Click to collapse
Same deal here - and frickin ASUS wanted $165 JUST for the motherboard part. So I said no to the RMA and they sent it back.
NOW my question is - can I order a motherboard and just swap it out? Does that work? http://www.ebay.com/itm/Asus-Nexus-...2GB-ASUS-Google-ME370T-Ship-Fast/121330719361
bshiznit said:
Same deal here - and frickin ASUS wanted $165 JUST for the motherboard part. So I said no to the RMA and they sent it back.
NOW my question is - can I order a motherboard and just swap it out? Does that work? http://www.ebay.com/itm/Asus-Nexus-...2GB-ASUS-Google-ME370T-Ship-Fast/121330719361
Click to expand...
Click to collapse
Haven't done it myself, but understand it does work. https://www.ifixit.com/Guide/Nexus+7+Motherboard+Replacement/9943
PrizmaticSmoke said:
Haven't done it myself, but understand it does work. https://www.ifixit.com/Guide/Nexus+7+Motherboard+Replacement/9943
Click to expand...
Click to collapse
Thanks! Ordered it and will be attempting
Hi,
My brother is having trouble with his Nexus 4 and I was hoping I could get some help here.
The phone won't go past the boot animation, with the 4 floating balls.
It keeps showing that forever (left it for 20 minutes with charger, phone got really hot but did not get past the animation)
- Never rooted or changed firmware. Only updates from Google. (It was on 5.1.1/5.1/5.0.1)
- Sent to a shop, which claimed it can't be fixed (I do not know the reason they gave him).
My brother thinks it is because a weight was accidently dropped on the phone, but the problem only started 3 days after the incident.
No outer damage can be seen on the device, other then a small brake in the back glass.
Thanks in advance to anyone who will try to help
possibly?
Did you just update and it got stuck at the booting up????
opeller said:
Hi,
My brother is having trouble with his Nexus 4 and I was hoping I could get some help here.
The phone won't go past the boot animation, with the 4 floating balls.
It keeps showing that forever (left it for 20 minutes with charger, phone got really hot but did not get past the animation)
- Never rooted or changed firmware. Only updates from Google. (It was on 5.1.1/5.1/5.0.1)
- Sent to a shop, which claimed it can't be fixed (I do not know the reason they gave him).
My brother thinks it is because a weight was accidently dropped on the phone, but the problem only started 3 days after the incident.
No outer damage can be seen on the device, other then a small brake in the back glass.
Thanks in advance to anyone who will try to help
Click to expand...
Click to collapse
Do you have data on it that you want to keep? If you don't you can try booting into the bootloader and unlock it. Then try flashing a factory image. This will wipe all the data on the phone though so that should probably be a last resort.
ChainFires Son said:
Did you just update and it got stuck at the booting up????
Click to expand...
Click to collapse
No, it did not occur after an update.
theminikiller said:
Do you have data on it that you want to keep? If you don't you can try booting into the bootloader and unlock it. Then try flashing a factory image. This will wipe all the data on the phone though so that should probably be a last resort.
Click to expand...
Click to collapse
I have no important data on it.
Which is the safest way to do this? I'd appreciate it if you would be detailed or refer me to a guide, as I want to be careful.
Where should I download the factory image from?
As the name of it states, I wish to get the one from Google, without any changes or addons from users.
Follow this guide http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
You can download factory images from here https://developers.google.com/android/nexus/images
opeller said:
I have no important data on it.
Which is the safest way to do this? I'd appreciate it if you would be detailed or refer me to a guide, as I want to be careful.
Where should I download the factory image from?
As the name of it states, I wish to get the one from Google, without any changes or addons from users.
Click to expand...
Click to collapse
First we should check if you can boot into the bootloader at all. First turn the device off. Then hold down both the volume buttons and then press and hold the power key. Keep holding all the buttons until you see some different colored text. If that happens we should be able to install a factory image, if it still gets stuck on the Google logo I unfortunately don't have any more ideas.
Tried pressing both volume keys and power button. Google logo show for a second, then black for 2 second, thank flashing red notification light every 1/2 second until I let go of the buttons.
When I release the buttons, the phone goes back to charging battery screen.
I see people suggesting that the red light flashing means a battery problem, but the device keeps trying to boot up while it is not plugged to the charger, unlike what happened to them
Any Ideas why this is happening or what the red light means in this case?
You need to press volume down+power button to get into bootloader. Unplug the charger before doing this.
harishmenace said:
You need to press volume down+power button to get into bootloader. Unplug the charger before doing this.
Click to expand...
Click to collapse
Oh it was just volume down, not both. Heh, sorry.
Use the Nexus Root Toolkit (NRT), it's the easiest way to unlock, root, flash and manage your SuperUser needs!
http://www.wugfresh.com/nrt/
Not sure, but maybe?
You can try using the nexus root kit & unlock your bootloader and see if a factory reset can work. If it does you can always relock it again ☺..Flashing a factory image can work too also ...
Tried volume down+ power button while unpluged from charger.
Google logo show up with vibration, then goes away after 2 seconds, like before, but then the screen goes blank. But red led not flashing.
What should I do now? Even just to use the Nexus Root Toolkit I have to allow Developer mode, which I can't as the phone will not boot up.
opeller said:
Tried volume down+ power button while unpluged from charger.
Google logo show up with vibration, then goes away after 2 seconds, like before, but then the screen goes blank. But red led not flashing.
What should I do now? Even just to use the Nexus Root Toolkit I have to allow Developer mode, which I can't as the phone will not boot up.
Click to expand...
Click to collapse
I'm you can't get into the bootloader then I am unfortunately not aware of any way to help you. If you can't even get into the bootloader I think it is a high probability that it is a hardware problem.
I understand. Thank you for your attempt to help me so far, I apriciate it
Anyone else has any Idea what I can try?
opeller said:
I understand. Thank you for your attempt to help me so far, I apriciate it
Anyone else has any Idea what I can try?
Click to expand...
Click to collapse
First you have to ensure "The Situation" of your phone, diagnostic is very important to decide the kind of medicine or treat. Your N4 booting, stuck on google-logo with red blink, then black screen.
To check : Connect your N4 to PC on linux check on terminal command $ lsusb if output
Bus 001 Device 005: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode),
Click to expand...
Click to collapse
on windows (XP/Vista/7)
Qualcomm something QDL Mode or something like this on "device manager"
Click to expand...
Click to collapse
there is a big hope to revive but very long journey. You are lucky since N4 is very popular device.You can obtain required file like MPRG8064.hex and friends
x1123 said:
First you have to ensure "The Situation" of your phone, diagnostic is very important to decide the kind of medicine or treat. Your N4 booting, stuck on google-logo with red blink, then black screen.
To check : Connect your N4 to PC on linux check on terminal command $ lsusb if output
on windows (XP/Vista/7) there is a big hope to revive but very long journey. You are lucky since N4 is very popular device.You can obtain required file like MPRG8064.hex and friends
Click to expand...
Click to collapse
Hi, thank you for your will to help.
When I turn on the Nexus 4 and connect it to my pc, it show the device as Nexus 4 in device manager.
What do you want me to do?
opeller said:
Hi, thank you for your will to help.
When I turn on the Nexus 4 and connect it to my pc, it show the device as Nexus 4 in device manager.
What do you want me to do?
Click to expand...
Click to collapse
detected as Nexus 4 mean your device well alive. any respons from the phone if you check with adb command ? if the phone give respond to adb you can ask phone to turn to recovery $ adb reboot recovery ...
opeller said:
Tried volume down+ power button while unpluged from charger.
Google logo show up with vibration, then goes away after 2 seconds, like before, but then the screen goes blank. But red led not flashing.
What should I do now? Even just to use the Nexus Root Toolkit I have to allow Developer mode, which I can't as the phone will not boot up.
Click to expand...
Click to collapse
That sounds like the battery is completely empty. Put the device on charger over a night and try then to boot into the bootloader.
Once I had these symptoms (red light flashing) on my N4, it was enough to charge the battery for one hour. Then it booted properly. It's worth trying.
x1123 said:
detected as Nexus 4 mean your device well alive. any respons from the phone if you check with adb command ? if the phone give respond to adb you can ask phone to turn to recovery $ adb reboot recovery ...
Click to expand...
Click to collapse
How do I do that?