Database Develop

Softbricked Phone Battery Too Low for RSD Lite, Won't Charge

I have searched around for a couple days, but there doesn't seem to be anyone who has posted about this issue with a Droid 4. So here is what I have.
I rooted my Droid 4 using the RazrBlade method without incident. Afterwards I wanted to flash Cyanogenmod onto it, but did not have a custom recovery like ClockworkMod or TWRP set up yet. So, looking around led me to download the latest safestrap .apk so I would have a recovery capable of flashing Cyanogenmod. The latest version of safestrap would not work for me because of a parsing error, I looked around and found that some people were having the same issue and fixed it by downloading an earlier version of safestrap to their Droid 4. So, I found a safestrap 2.x.x version, downloaded that and followed the directions accordingly. I now had a functional (to my knowledge) recovery that would allow me to flash CyanogenMod. So I downloaded the .zip file from the CyanogenMod website for Droid 4, and attempted to flash it using the recovery that safestrap 2.x.x set up.
Everything looked okay for the install, no errors were reported, phone was at least at 80% battery, but once the phone rebooted, after the Motorola spash screen, there was a blank screen. The phone is on, evidenced by the backlight being visibly seen, but otherwise there is no evidence that it is trying to boot up any ROM. There is no loop whatsoever, just a blank screen.
First, I thought it was a bad install, afterall, it wouldn't be the first time. But when I turned it off (only possible via PWR&Vol.- button combo) it did not give the option to go into the safestrap recovery mode upon booting back up.
But I am not without a working knowledge of how to pull a phone out of a softbrick state, so I quickly connected my phone to a computer set up to take adb commands and tried to reboot my phone into the recovery mode. I connected my phone to my PC, left it on the blank screen mode and typed the adb command [adb devices] to confirm that it was acknowledged by my computer, it was, and attempted to reboot it into the recovery mode with the command [fastboot reboot-recovery]. It responded by rebooting, but led back to the backlit blank screen. I thought that this might be an issue with the wires or drivers or something to that effect, so I reattempted with a usb cord that was supplied by Motorola, and reinstalled all the appropriate drivers. Nothing worked, so I moved everything to a new computer freshly set up to take adb commands. I connected my phone and it was immediately recognized by the new computer, but it still would not respond to any adb commands. Attempting to reboot into recovery yields a blank screen still.
By this point I do not care if my phone is rooted or if I have to restore it to factory settings. So I look up solutions that flash it back to the stock 4.1.2 ROM. I find one that does this, but it requires that I am in AP Fastboot Flash Mode. I put it in the aforementioned mode, but it is not recognized by the adb terminal. It is listed as an adb device if it is in "blank screen mode" but not while in AP Fastboot Flash Mode. Shortly after this the battery is too low to program anyway, so I turn it off and set it to charge. But instead of a "battery charging" screen, I am greeted with the Motorola splash screen for as long as the phone is connected to the charger. Every time the phone is removed from the charger it, immediately and without pause, loses power and cannot be powered on until placed back on a charger.
Looking around some more, because I am increasingly desperate to solve this problem, I find something called RSD Lite, which will reflash the stock firmware to the phone and it will behave as if it was reset to factory settings. I plug the phone up to the computer, it powers on, I boot it up to the AP Fastboot Flash Mode and RSD Lite sees the phone as a fastboot device, and is ready and willing to fix it, but the battery is too low to program.
The battery is incapable of being charged by a wall outlet by any means that I have tried (will list below), BUT... If I connect my phone to a computer, and after the phone is connected, turn the phone off, a little green LED light appears at the top left and stays for at least 15 minutes until the Motorola splash logo appears and my phone connects to the computer. The phone recieves power in this mode evidenced by the fact that it does not instantly power down after it is disconnected from the power source. But at this point in time, the battery does not charge enough to cause a change in the AP Fastboot Flash Mode to allow it to be OK to Program.
Here is some misc info that might be needed:
Modes that I have access to
1.) Motorola Splash Screen + "Blank Screen Mode": This mode connects to the computer and is registered by the device number XT894. After the Moto Splash Screen there is a backlit blank screen I call "Blank Screen Mode". This mode is recognized by adb commands but not by RSD Lite. Any time an adb command is used apart from rebooting, command prompt says <waiting for device> and the device does not respond.
2.) Motorola Splash Screen Only: This mode is only accessible by connecting the phone to a wall outlet. This mode does not charge the phone and if the phone does not have any power otherwise, will power down without warning upon being disconnected from the power source.
3.) Boot Mode Selection Menu: This mode provides various options that appear to do nothing. The "Recovery" option that is supposed to bring me to the default android recovery mode instead brings me to the Motorola Boot Logo and then to a green android laying down with a red triangle over it (with an exclamation point). I am able to access AP Fastboot Flash Mode from here.
4.) AP Fastboot Flash Mode: In this mode, the device is recognized by the computer as an adb fastboot device (not as an XT894 device). It does not respond to adb commands, and the adb terminal does not acknowledge the phone in this mode. RSD Lite does acknowledge the phone in this mode, but trying to begin the process to reflash the stock firmware causes the "Low Battery/ No Program" text on the phone to flicker and result in a failure in the RSD Lite program. It lists the reason as: Phone return(ed) Fail.
5.) Computer Charging Mode: When connected to a computer, and immidiately powered off, a green LED light turns on. After leaving the phone for some time, the phone can be disconnected and stands on it's own power without needing to be connected to a power source to remain on. In this mode, the screen is not on, and the phone is not recognized by the computer at all.
Methods I Have Attempted to Use to Charge Phone
1.) Plugging Moto Stock USB charging cable to computer and leaving it: This causes the 1st mode listed above to occur, and no charge is held. After 10 minutes of "charging" upon disconnecting cable, phone shuts off abruptly, and without any warning.
2.) Plugging Moto Stock USB into USB to Wall Outlet Plug: This causes 2nd Mode listed with similar results to above.
3.) Plugging Motorola Wall Outlet Charging Cable to Phone: See above
4.) ALL Above Methods + Boot Mode Selection Menu BD Tools Mode: I read that if you were to connect your phone to a wall outlet after booting it up into the Boot Mode Selection Menu, and selecting BD Tools, the phone would boot up to the Motorola Boot Logo screen, then show a battery charging similarly to how one does if you charge your phone after it shuts down from having 0% Battery. This was not the result I received. Similar results to #1
I apologize if there is some blatant simple answer here, but I have looked everywhere to find a solution to no avail. I included everything that occured between then and now so as to facilitate this process, and hope that I am not stepping on any toes with the wall of text I just posted.
Thanks in advance, if more info is needed (or if the post needs to be formatted in an easier to read way) just say so.

Sounds like you will need a motorola factory cable. I think that's what they are called. It provides power directly to the phone allowing you to fastboot. I know you can find them on ebay. I believe team black hat also sells an adapter to turn your regular OEM cable into a factory cable.
Your other alternative would be to sacrafice a usb cable and attach to the battery terminals directly to charge the battery. If you google it you should be able to find directions for how to do this. I believe someone posted a how to on youtube for the razr which should give you a good idea of what you would be getting into.
Good luck!
Droid 4 - Avatar

Fixed It
Thanks for the help.
I didn't feel like paying $12 dollars and waiting several days to purchase one of those special factory cables, so I ended up taking a non-USB charger, spicing it, and hooking it directly to the battery terminals like you said. After I did that, it automatically said that it was "OK to Program".
The only problem I had was that RSD Lite wasn't able to fix it, I had to download some other app that ran things through command prompt while the device was in AP Fastboot mode. But the end result was the same.
I found out that the problem that caused all this was me not flashing the CyanogenMod firmware into ROM Slot-1 while in the safestrap recovery mode. I flashed it to the "Stock" ROM Slot instead.
Thanks again for the help, I learned a lot, and I am glad I didn't have to shell out money for a new phone. :laugh:

Cannot Access Android Recovery Mode - Xperia Z1

I have two Xperia Z's , Z1(a) - Display is jet black and sim port broken but phone and touch still function as normal. Bought another broken screen Z1(b) - recovered motherboard to replace Z1a. That worked but now Z1b stuck on pattern screenlock and ebay seller does not want to give me password. I have the old screen with fingerprint smudges and everyday I attempt to crack the pattern lock and phone not blocked as i put sim in and able to call phone and answer..
I have tried connecting Z1b to PC to use Sony Update Service software to restore phone back to factory setting but phone is not recognised or charging by PC (does charge through wall socket and Mac USB port). Run SUS>Press Vol Down Button while connecting USB and LED indicates GREEN then RED but software cannot find phone.
{{Run SUS>Press Vol Up Button while connecting USB and LED indicates solid BLUE LED - not sure what this feature is???}}
So I exchange Z1b motherboard with Z1a and when connected to PC, phone indicates charging and installs a driver to PC. Do a dummy SUS test and phone is found by software allowing option to do a factory reset. Re-exchange back Z1b and still nothing - no charge, not recognised by PC or software - so assume Z1b usb port is faulty.
So read about Android recovery mode but i cannot access recovery mode on either of them - Is recovery mode only available for rooted android phones??? I can only enter safe mode (Power+VolDown) and tried the following options but got no response:
1. Holding Power + VolUp
2. Pressing Vol Up continuously after pressing power button
3. Pressing Vol Down continuously after pressing power button
4. Press all Buttons together.
NEXT STEPS:
1.Connect Z1b to a MacOS 10.6 or later and try SUS and PC companion (i have old Mac 10.4)
Any other help or suggestion??? - many thanks in advance.

Have you installed a recovery?
If not then you cant access something that your phone does not have
You will have to root and install one, just follow the link in my signature to get root on latest KK firmware
PS, wrong section, but I have asked the mods to move it for you

Thanks for your reply.
I thought this was a built in feature on android devices - guess am wrong. I will not be able to install anything if i cannot access phone OS.
Looks like i will have to see if i can reset Z1b through Mac Sony bridge SUS, cough up for USB repair OR by chance crack code.

or just read some "how to" / "Tutorial" / "guides" threads to install recovery. Its very easy.

xiaomi mi3 hard brick cold dead?

Lately I was flashing mi3 trough fastboot on w7ulti64bit when something went wrong and now its cold dead.
I have been looking for solution everywhere and as usual xda is my last resort for help with phones, usually I found here what I was looking for but this time it is first time when I have to post new threat.
So basically I found that battery controller had some cold soldier on chip, whole module gives 0v while cell itself 2,8v so I think I fixed it since now whole battery module shows 3.3v and cell itself 3.8v after charging.
But im unable to wake up phone in to fastboot or any other way to reflash it.
When connected to 2000mAh charger there is solid red light, when connected to PC it lit for a second then goes off and PC recognizes mi3 as USB input device and HID compliant device.
I have tried to update drivers for those devises so miflash would recognize it and allow to flash it but without any success.
Any idea what else I could do with it, or how to force flash to flash at least boot sector?

Shamoth said:
Lately I was flashing mi3 trough fastboot on w7ulti64bit when something went wrong and now its cold dead.
I have been looking for solution everywhere and as usual xda is my last resort for help with phones, usually I found here what I was looking for but this time it is first time when I have to post new threat.
So basically I found that battery controller had some cold soldier on chip, whole module gives 0v while cell itself 2,8v so I think I fixed it since now whole battery module shows 3.3v and cell itself 3.8v after charging.
But im unable to wake up phone in to fastboot or any other way to reflash it.
When connected to 2000mAh charger there is solid red light, when connected to PC it lit for a second then goes off and PC recognizes mi3 as USB input device and HID compliant device.
I have tried to update drivers for those devises so miflash would recognize it and allow to flash it but without any success.
Any idea what else I could do with it, or how to force flash to flash at least boot sector?
Click to expand...
Click to collapse
Try mi flash tool

Main problem is that I have tried all 3 miflash I could found 2.11.6 20131108 20140509 and none of them recognizes device and I can't even initiate flashing process ;/

it sounds like a driver issue. just download all the drivers you can find for your phone.

Shamoth said:
Lately I was flashing mi3 trough fastboot on w7ulti64bit when something went wrong and now its cold dead.
I have been looking for solution everywhere and as usual xda is my last resort for help with phones, usually I found here what I was looking for but this time it is first time when I have to post new threat.
So basically I found that battery controller had some cold soldier on chip, whole module gives 0v while cell itself 2,8v so I think I fixed it since now whole battery module shows 3.3v and cell itself 3.8v after charging.
But im unable to wake up phone in to fastboot or any other way to reflash it.
When connected to 2000mAh charger there is solid red light, when connected to PC it lit for a second then goes off and PC recognizes mi3 as USB input device and HID compliant device.
I have tried to update drivers for those devises so miflash would recognize it and allow to flash it but without any success.
Any idea what else I could do with it, or how to force flash to flash at least boot sector?
Click to expand...
Click to collapse
Same problem here, waiting for someone give the solution

if the device is not getting detected in any of the mi flash tools,i feel its a clear sign of driver issues ,

ZenR2 said:
if the device is not getting detected in any of the mi flash tools,i feel its a clear sign of driver issues ,
Click to expand...
Click to collapse
r u following correct procedure for using MI flash tool ?
is ur Phone able to boot to FLash mode ( turn phone off > Press volume + Key then Press Power on - it will show flash mode )
Now Open MI Flash tool > Press Refesh > it will show phone now ( a number will b shown instead of name Xiamo Mi3)
Now Extract Fastboot rom to C Drive ( it should look like this C:\ROM (Location should not cointain space)
Now click Browse > advance > select C:\ROM\Folder\ select bat file

Its not drivers issue since its get detected as QUALCOMM HS-USB QDLoader 9008 or QUALCOMM HS-USB Diagnostic 9006 depending of its state.
In QDLoader it is recognized by miflash as COM20 device and I can upload by miflash or qpst boot image, then it switches to diagnostic that is recognized by some sort of string and I can upload/proceed with rest of rom flashing that includes creating partitions and writing data to them.
Main problem is that when its successfully flashed it is still cold dark, while PC can see it and all partitions like 28 of them...
And I think its related to the fact that qpst reports phone as in download mode.
Any idea how to exit that mode, like in Mi2 that was forced to enter "service" by shortening some pins to put it download mode to flash cold dead ones?

agdag said:
magdag from en.miui.com forum seems to be able to hekp ..or try [email protected] , jason provide paid service
Click to expand...
Click to collapse
You were already looking at it
Kinda wasted a lot of Mine and Yours time and some of my money
If You got any other ideas since that time how to resurrect it just let me know.

Any solution?
Is there any solution to this problem? My phone has been cold brick for 3 days now. Doesnt boot up or charge up. Detected on connecting to PC with a sound, but Shows as Com 10 or 20 on Miflash and thus cannot be flashed.
Cannot boot into fastboot as well.
Anyone anything?

androidy88 said:
Is there any solution to this problem? My phone has been cold brick for 3 days now. Doesnt boot up or charge up. Detected on connecting to PC with a sound, but Shows as Com 10 or 20 on Miflash and thus cannot be flashed.
Cannot boot into fastboot as well.
Anyone anything?
Click to expand...
Click to collapse
You can check the steps I took for recovering from a similar problem here: http://en.miui.com/forum.php?mod=viewthread&tid=22811
If you have any other questions, tag me on your reply and i'll try my best to help.

bricked device, sol?

I've tried both normal & recovery booting and it doesn't turn on. Doesn't show the flashing logo either so I think I might be SOL unless there's a way for me to save it .

BAMvsGAME said:
I've tried both normal & recovery booting and it doesn't turn on. Doesn't show the flashing logo either so I think I might be SOL unless there's a way for me to save it .
Click to expand...
Click to collapse
If there is no sign of life, no known fix
send back to Amazon for a one time exchange if still under warranty
Sent from my sailfish using XDA Labs

Same thing just happened to me. I have a blank screen will not go into recovery mode or even pull up the screen.(black Screen) I just tried to downgrade to root. get nothing now. Take that back, my pc keeps beeping to leave me know a usb connectes, but then disconnects. tried different cables, one gives me a message USB Device not Recognized The last USB device you connected to this computer malfunctioned, and Windows does not recognize it. Another Cable in Device manager pops up MediaTek PreLoasder USB VCOM (Android). then disappears like every 15 seconds.

ivancunningham said:
Same thing just happened to me. I have a blank screen will not go into recovery mode or even pull up the screen.(black Screen) I just tried to downgrade to root. get nothing now. Take that back, my pc keeps beeping to leave me know a usb connectes, but then disconnects. tried different cables, one gives me a message USB Device not Recognized The last USB device you connected to this computer malfunctioned, and Windows does not recognize it. Another Cable in Device manager pops up MediaTek PreLoasder USB VCOM (Android). then disappears like every 15 seconds.
Click to expand...
Click to collapse
The following downgrades will permanently brick device:
- 5.3.2.1 to any lower version (no rollbacks possible)
- 5.3.2.0 to any version below 5.3.1.0
- 5.3.1.0 to any lower version
- 5.1.4/5.1.3 to any version below 5.1.2
- 5.1.2/5.1.1 to any lower version
This information is clearly spelled out in forum index. Contact Amazon for an exchange if within warranty.

Hard bricked device detected by computer as QComm HS-USB Diag 9091

My redmi 4x, running the official build of AOSP Extended, suddenly shutdown during normal usage.
The device is now unresponsive to all button presses, and all keypress combinations do not work.
When connected to the original charger, the device heats up, just as per normal charging, although the display remains dark and the LED does not light up.
However, when plugged into my computer, the device is detected as 'Qualcomm HS-USB Diagnostics 9091 (COM3)'. All my searches have returned solutions that work for other 90__ codes, but none for 9091.
Does anyone have a possible solution to this? Thanks in advance for your assistance!
Some other information that may be of assistance:
The device was running the AOSP Extended 20180510 official build.
TWRP is installed and the device is rooted.
The device does not boot AT ALL. Not to system, not to recovery, and not to fastboot.