Database Users

Can't unbrick phone becuase of low battery // CAN'T CHARGE phone becuase it's bricked

I'm in a real pickle here...
My phone is bricked and I found all the resources for that already.
However, when I go to flash the firmware on the phone to bring it back to stock it's not allowing me to do it because the battery is at 4%.
I go to charge the phone a it forces itself into bootloops and doesn't charge.
I can get into recovery (CWM--which bricked the phone...likely my fault) but phone doesn't charge there.
I can get into download mode but it doesn't charge there.
WTF is going on!?!?
How can I charge my phone at this point...unfortunately, the battery isn't removable.

Can you flash a custom rom through adb sideload?

datechnerd said:
Can you flash a custom rom through adb sideload?
Click to expand...
Click to collapse
Edit: No, I'm unable to establish an ADB connection in Recovery to do this. I'd actually tried this already with a stock rom. Thanks though.
Flashing the Cyanogen ROM is what bricked the phone. I'm not able to establish an ADB Connection from Recovery (ClockworksMod) so I'm not able to flash anything in Sideload.
Here's the "Boot-Loop":
Power on (vibrate)
LG logo
"Source Booting Unsuccessful"
"Cause: (blank)"
And it just loops like that any time it's plugged in and not in Recovery/Download modes (which also don't charge).
I've tried a factory reset but that didn't change anything. I also tried restoring my original backup image but that doesn't work either.
Currently I'm trying this:
http://forum.xda-developers.com/showthread.php?p=48874488&posted=1#post48874488
This is where I get the failure to flash because of 4% battery.
Only other option I haven't tried yet is to boot into Ubuntu and restore files there and I'm avoiding that for now because I'm at my parents house and don't have burnable DVDs so it's going to be a pain in the ass.

for ubuntu couldn't you do a virtual machine, or live boot from a flashdrive?

datechnerd said:
for ubuntu couldn't you do a virtual machine, or live boot from a flashdrive?
Click to expand...
Click to collapse
I'd do a live CD/USB but they don't have the equipment so I need to go out and buy it (DVD-R is still cheap and so are USB drives) but they're not located very close to any stores

Same issue
Hey man i had the same issue as you and i just plugged it into the wall charger it will charge the phone it will just boot loop a bunch just leave it plugged in for about 30 minutes and try again that worked for me

tim45244 said:
Hey man i had the same issue as you and i just plugged it into the wall charger it will charge the phone it will just boot loop a bunch just leave it plugged in for about 30 minutes and try again that worked for me
Click to expand...
Click to collapse
Thanks a lot. I'll give that a try.

This happened to me too and i dont know what to do if you fixed it help me!

Just an idea. Download an Alternative recovery with charge function. Flash it via ur working recovery from usb otg drive if u have one and reboot to it. Then charge ur phone back to life

Just a thought but maybe you can use an external charger for the battery

had same issue,got bootlopp and baterry dead,can run to download mode but battery dead.everytime gi charge the battery it won't charge just bootloop again.help me too pleaseeee

it wont work for me.i charge it more than an hour but still readed "B0" in download mode thats mean i have 0 battery percent so i can't continueing to flash the phone,please help how to i charge the phone when everythime i charge it on the wall or pc,it will start bootloop again n again without charging the phone.my battery is now at 0% can't do anything

If you can go in cwm, flash twrp from usb and charge your phone in recovery.

Dear friends, anybody has found a solution? I'm on the same situation. If I disassemble my phone, will I be able to charge somehow?

Hi everyone, I know it's been many years but do we have any updates on this? Thank you

Nexus 4 Problem: Wont boot into system or recovery, but fastboot and able to flash?!!

Very weird behaviour:
1. Phone does not boot up at all - neither system nor recovery (tried 5.1 and 4.4.4 factory images and 2.8.3.0 TWRP as recovery).
2. Can start in fastboot mode and flash factory image but after flashing modem the device is "stuck" in QHSUSB_DLOAD mode.. when I restart into fastboot it continues to flash and finishes the flashing process apparently.
3. When the device is off and plugged in its recognized as "unkown device" or QHSUSB_DLOAD again - no signs of charging at all.
Phone got to me in "bricked" state - would not boot and was only showing red light when plugging in - after loading it for a while (it showed the battery with a lighning inside on screen during charge attempt, but no percentages at all) i flashed latest factory image but that did not help it seems.. =(
Tried "fastboot erase cache" as well...
Any ideas?

zroice said:
Very weird behaviour:
1. Phone does not boot up at all - neither system nor recovery (tried 5.1 and 4.4.4 factory images and 2.8.3.0 TWRP as recovery).
2. Can start in fastboot mode and flash factory image but after flashing modem the device is "stuck" in QHSUSB_DLOAD mode.. when I restart into fastboot it continues to flash and finishes the flashing process apparently.
3. When the device is off and plugged in its recognized as "unkown device" or QHSUSB_DLOAD again - no signs of charging at all.
Phone got to me in "bricked" state - would not boot and was only showing red light when plugging in - after loading it for a while (it showed the battery with a lighning inside on screen during charge attempt, but no percentages at all) i flashed latest factory image but that did not help it seems.. =(
Tried "fastboot erase cache" as well...
Any ideas?
Click to expand...
Click to collapse
u flashed stock doing fastboot -w update?

C4SCA said:
u flashed stock doing fastboot -w update?
Click to expand...
Click to collapse
downloaded the stock factory images (tried 4.4.4 and 5.1 so far) from google and used the "flash-all.bat". Should I do it manually instead?
What you mean "-w update" is that a parameter for the fastboot flash command?

zroice said:
downloaded the stock factory images (tried 4.4.4 and 5.1 so far) from google and used the "flash-all.bat". Should I do it manually instead?
What you mean "-w update" is that a parameter for the fastboot flash command?
Click to expand...
Click to collapse
He is asking if you wiped the device after flashing. You flashed the image using the flash-all.bat, which wipes the device. And you even erased the cache. So from the flashing point of view, it seems you did everything right. Do you have the wall charger to load the battery (for some hours)? I would try this. Besides, here is another thread, which seems to be related: http://forum.xda-developers.com/nexus-4/help/qhsusbdload-problem-t2253874
cheers

Had it charging for hours before flashing, so battery cant be the problem..
But when I now put the device on PC (or Charger) nothing seems to happen - not showing the charging symbols and PC recognizes the device as QHSUSB_DLOAD.
Fastboot mode is working, Boot to system and recovery show the google logo but thats it, not even a boot animation.

now its gettin recognized only as "unknown device" not even QHSUSB_DLOAD anymore.. weird

zroice said:
Had it charging for hours before flashing, so battery cant be the problem..
But when I now put the device on PC (or Charger) nothing seems to happen - not showing the charging symbols and PC recognizes the device as QHSUSB_DLOAD.
Fastboot mode is working, Boot to system and recovery show the google logo but thats it, not even a boot animation.
Click to expand...
Click to collapse
dont do fastboot erase cache. Do fastboot format cache.
reinstall the correct google usb drivers manually (http://forum.xda-developers.com/nexus-s/general/tutorial-n00bs-install-drivers-windows-t1901617)
try to flash 4.2.2 and see if it boots up using the flash all bat.
that QHSUSB_DLOAD mode i think its teh qualcomm recovery mode or something like that, there is a thread on xda about it.

Yea good idea gonna try and flash older firmware - although there was 5.0 or 5.1 on it when the phone got to me..
Starting to believe its a hardware issue or the bootloader is fked up somehow - the thing wasnt even rooted when it wouldnt start anymore ...
Are there any ready to use packages to flash bootloader again with qpst? Dont have much time for this thing anymore - so I cant assemble my own files - unless thats a quick process.. but from what ive seen its a bit difficult, right?

zroice said:
Yea good idea gonna try and flash older firmware - although there was 5.0 or 5.1 on it when the phone got to me..
Starting to believe its a hardware issue or the bootloader is fked up somehow - the thing wasnt even rooted when it wouldnt start anymore ...
Are there any ready to use packages to flash bootloader again with qpst? Dont have much time for this thing anymore - so I cant assemble my own files - unless thats a quick process.. but from what ive seen its a bit difficult, right?
Click to expand...
Click to collapse
no luck with 4.2.2 either - same behaviour.. flash is alright but then it wont boot or go into recovery.. argh

I had the same issue and this worked for me
https://productforums.google.com/forum/#!searchin/nexus/QHSUSB_DLOAD$20nexus$204/nexus/4Z5Sntc7u2c/HIyGuAVz8EQJ

halloga said:
I had the same issue and this worked for me
https://productforums.google.com/forum/#!searchin/nexus/QHSUSB_DLOAD$20nexus$204/nexus/4Z5Sntc7u2c/HIyGuAVz8EQJ
Click to expand...
Click to collapse
thanks man, tried that but no help. Phone isnt really stuck in the qhsusb_dload mode but it just won't boot neither the normal kernel nor the recovery system. All I can get this thing to boot is the fastboot mode and sometimes after flashing and rebooting from there the phone will be recognized as QHSUSB_DLOAD. When I plug it in while its off (either PC or wall charger) the Google Logo comes up, just as if its trying to boot, but no charging symbols.
In this state (google logo stuck) the pc does not recognize it at ALL - after a while the pc says "unknown device" has been attached but it has no hardware id or anything.
So the booting process is broken most likely. Question is if that is fixable with QPST or something else? Don't wanna invest any more time if its not likely to suceed though.. Already spent hours on this damn thing.. =)

zroice said:
thanks man, tried that but no help. Phone isnt really stuck in the qhsusb_dload mode but it just won't boot neither the normal kernel nor the recovery system. All I can get this thing to boot is the fastboot mode and sometimes after flashing and rebooting from there the phone will be recognized as QHSUSB_DLOAD. When I plug it in while its off (either PC or wall charger) the Google Logo comes up, just as if its trying to boot, but no charging symbols.
In this state (google logo stuck) the pc does not recognize it at ALL - after a while the pc says "unknown device" has been attached but it has no hardware id or anything.
So the booting process is broken most likely. Question is if that is fixable with QPST or something else? Don't wanna invest any more time if its not likely to suceed though.. Already spent hours on this damn thing.. =)
Click to expand...
Click to collapse
I know this situation man, I spent many hours too and finally solution came out that simple Hope you solve it soon

well i tried that - but i only get a "red" light when holding volume down and power while on wall charger.
This resets the QHSUSB_DLOAD mode, but still wont make the phone boot for me. Tried that combo several times - only "red" light no orange or smth.
When i do that combo when the phone is plugged in to the pc and its in qhsusb_dload mode the red light will flash instead of beeing on all the time.
So I think ill give up unless someone can point me to a good QPST guide to rewrite bootloader for the nexus 4...
Must be bootloader or hardware issue im quite sure..

Stuck at Fastboot & Rescue Mode, tried multiple things; Always 100% Original Software

Stuck at Fastboot & Rescue Mode, tried multiple things; Always 100% Original Software
Hi reader,
First some background:
A month ago I changed my SIM Card in my 2.5 year old Huawei P9 Lite with original Android 7.0. I never flashed or rooted this phone. Developer options are on (not sure though). Since then, I saw a major battery drain. After charging fully, it drained fast to 51% and got stuck on 51%. The phone turned off. After trying to turn it on, the red LED flashes. Charging it for 2 days, the green led turns up. However, turning the phone one, the screen stays black and red light flashes. Charging for 5-10 minutes, the green light turns on but this loop of green and red lights continues.
What I want:
Get my contacts and notes back
What I tried:
- Volume down + power and connecting to pc -> Fastboot. Message:
* Please connect usb cable to your computer and open HiSuite -> done, but HiSuite does not recognize phone. Windows does, as Android Sooner Single ADB Interface. The cmd code: ''fastboot'' does not give the wanted result (not found). As windows does not recognize the correct phone, I tried to install a new Huawei USB driver. The problem is, that Windows says the Android Sooner driver is already the best driver available.
* Android reboot reason: AP_S_COLDBOOT NA. Volumekey_down_press_process_func
* Green android puppet
* PHONE Locked. FRP Lock. -> I tried to unlock via Universal Fastboot & ADB Tool. This program recognices device as ''FUH4C16518004949 fastboot'' and reboot button in the program phone works (but again the red light). I also tried to unlock bootloader but I cannot find the correct key via the Huawei website (thus could not try oem relock *Here Huawei Code*). I tried to flash EliteTWRP-3.2.1-0_2018-01-19.img, but that is not possible due to the lock.
What can I do next in order to get a backup of my contacts and notes?
Phone will go on charger again.

No one?

So you said you didn't do any root and/or unlocks? This seems like a battery/motherboard failure. To fix it, go to HUAWEI's official service center

The Restless Soul said:
So you said you didn't do any root and/or unlocks? This seems like a battery/motherboard failure. To fix it, go to HUAWEI's official service center
Click to expand...
Click to collapse
Thank you for your answer. That is correct, no root and no unlocks.
Huawei Service Centres are not nearby and warranty is over. That is the reason I wanted to try a few things.
Are there things I could still try?

richh008 said:
Thank you for your answer. That is correct, no root and no unlocks.
Huawei Service Centres are not nearby and warranty is over. That is the reason I wanted to try a few things.
Are there things I could still try?
Click to expand...
Click to collapse
Get the spare parts and fix it by yourself? The battery replacement is very hard and you can damage the display cords. So i recomment a third party service then.

Moto E4 MediaTek hard bricked?

Well, I never thought I would have to do this but now, I have to. I have a Motorola Moto E(4) woods, mediatek and not plus. So I tried to install TWRP into it and did it successfully - or so I thought. It wouldn't turn on. It would boot to TWRP but not to the normal system. When I tried to boot to normal system, it would get stuck in the Motorola logo. So dumbass me, I downloaded stock firmware to flash with SP Flash Tool. I did flash it but what I didn't know until it completed was the fact that it wasn't Moto E4 woods firmware, it was instead Moto E4 Plus firmware
So, now what? Once I try to boot it, the display doesnt do anything. The only signs of life are the led charging light on the front of the phone which comes on than turns off when I connect it to charger. The other one is the LED flash next to the camera which turns on after the charging light goes off. And lastly it randomly vibrates while charging and that's it. When I connect it to PC, it behaves like normal charging except the connect-disconnect sounds my PC makes, than the phone vibrates and that's it. One time I connected it to PC , my PC made the connect sound but not the disconnect sound. adb devices would not show it but the SP flash tool would. Then I accidentally disconnected it and... Done.
So, is there any hope for this phone? Can unbrick it at home with my PC the phone itself? I am waiting for your answers.
Thank you for your time.

Redmi 7A Dead, No display, no fastboot, no recovery

I have some previous threads on my Redmi 7A dead... but no one responded, some did but said I can't fix it, buy a new phone. I am not in a financial condition to buy a new phone. All I can do is fix this phone and continue using it till I get a new phone. But since 3 weeks I am not able to use my Redmi 7A. I was hopeless that this phone could be repaired or could be used again but I went through a few videos on YouTube and saw a ray of hope but still I was helpless I tried booting it into EDL mode using the test point method but nothing worked out. Please I NEED HELP to fix this phone. I have a brief description below of the timeline about how it
crashed, how it was in the service center, what happened after it.
Alright so,
At March 13, It was on AOD (I know it is not supported keep reading), running nusantra os latest version for (Mi-439 aka Redmi 7A, 8) which was last updated on Dec 4, 2022. So when It was on AOD I tried to unlock the phone and it froze. So I rebooted it abnormally. After it was booting it stuck on the Redmi logo but it wasn't going ahead, not showing the boot animation. So I tried to boot it in recovery mode, when it was booting in recovery mode the phone was just shutting down and trying to reboot itself again but it couldn't. So I tried to wipe everything using fastboot commands and the command which I used was -w. So after that instead of waiting at the redmi logo it was stuck in a bootloop, in fact booting in the bootloader (fastboot mode). So after that I lost hope and gave it to the nearby service center. Please note that the phone was turning on before giving it to the service center. After like one day I went there to check if it was done, they say that it's a hardware problem, they are not able to fix it, When I came home the phone didn't boot neither in the fastboot mode nor It was turning on. So I thought it's not charged so I charged it for 1.5 hours but still there was no sign of life. I asked them about the phone not turning on they told me that it's a hardware issue and hung up the phone, said I am in a hurry I will call you later. Till this day I received no call. So Now I am posting this because I see some hope of EDL mode. I even tried to boot it in the EDL mode but still it was neither booting in the EDL mode nor my computer is detecting my phone (I have all the drivers installed). Please help ASAP.

Gibbron1 said:
there was no sign of life
Click to expand...
Click to collapse
1. does the led light up when you charge it?
2. what does you pc device manager show when you plug it in? (do you hear the windows sound?)
try every button combination that is possible. i mean two buttons at the same time, three buttons, all buttons... and for about even up to 1 minute (because this brought my 7A back from just led light when charging to pc detected a usb device)
i can't reproduce your brick but i managed to debrick via edl mode once on a "complete dead" (only led lights up when charging) so i think you can do that too.
also as long as you work with the EDL Tool, deactivate your Firewall (and don't forget to activate it again) just so be sure.
3. are you trying to enter edl mode via adb terminal? i would say you have to open the back cover and enter edl mode via hardware bridge from edl point to ground.
and as far as i can remember you have to be really quick between "starting" (booting) edl mode on the phone and make the phone "accept" edl mode. i think i first made the hardware bridge and then pluged the usb in.
i will dig deeper again in the next few days so i can give you better info's

mYXiao said:
1. does the led light up when you charge it?
2. what does you pc device manager show when you plug it in? (do you hear the windows sound?)
try every button combination that is possible. i mean two buttons at the same time, three buttons, all buttons... and for about even up to 1 minute (because this brought my 7A back from just led light when charging to pc detected a usb device)
i can't reproduce your brick but i managed to debrick via edl mode once on a "complete dead" (only led lights up when charging) so i think you can do that too.
also as long as you work with the EDL Tool, deactivate your Firewall (and don't forget to activate it again) just so be sure.
3. are you trying to enter edl mode via adb terminal? i would say you have to open the back cover and enter edl mode via hardware bridge from edl point to ground.
and as far as i can remember you have to be really quick between "starting" (booting) edl mode on the phone and make the phone "accept" edl mode. i think i first made the hardware bridge and then pluged the usb in.
i will dig deeper again in the next few days so i can give you better info's
Click to expand...
Click to collapse
I bought another phone, but thanks for the reply and help you gave me. My new Phone is Mi A1.