Hello everyone,
Please help with my situation
My phone is not powering on. Red light (led) is constantly blinking (pretty fast).
I would like to understand why? What is the culprint (soft or hard, etc) of this?
This is what happend (I remember pretty well and exactly):
In the morning I had tried to power up my phone but realized it has discharged completly over night (it happens to me quite often).
So, I put it to charge (connect the cable).
It didn't show the battery logo and charge percent and suprisingly powered ON by itself.
I considered this thing quite odd because it rarely does this. Usually it does this only when it is connected to charging cable (and it if powered off) and the time is arround the time I set an alarm. (but it was passed that time with at least 30minutes)
So I don't know why it powered ON by itself.
It had started booting up normally, showing Android Log, and those loading marbles (points).
I expected to boot properly in a minute or so, as usual.
But it stood there to much time - arround 4,5min (animation was there, so it was not stuck)
So I decided (probably wrongfully) to power it off (pressing the power button 4,5 sec) and restart the phone again.
But after when I tried to power it on or connect to charging, it was only the red led light blinking.
What might have happened? to get the phone in this mode?
Now when I try to connect the phone to computer it is detected as Qualcomm HS-USB QDLoader 9008 (COM3). (QUSB_Bulk, before installing drivers)
Like it were in EDL mode. Is this normal or why is it showing like this?
I have found some info about red blinking of death on internet and found that it usually is a problem with power IC, which needs reballing (reheating)
But is this my case also? Because by connecting the phone to the computer it shows Qualcom HS-USB QDLoader 9008.
I did NOT try to update the OS of the phone.
Could I think that it did this by itself without my consent (xiaomi idiots or hacked phone)? And while it did the update I powered it off ? And this is the result (red blinking of death)
Is this a hard (power ic problem) or soft (an update without my consent somehow)?
Thank you.
Hope I didn't write to much. I tried to be as brief as possible.
Check in device manager , phone is making qloder 9008 port without pressing any key.
If yes then tell me
kuldeepchavda7794 said:
Check in device manager , phone is making qloder 9008 port without pressing any key.
If yes then tell me
Click to expand...
Click to collapse
Phone is detected (in device manager) as
Qualcomm HS-USB QDLoader 9008 (COM3)
when connected to computer, automatically.
No button pressed.
The phone is dead (bricked) any button I press does not start or do anything. Only red led blinking.
clabr2 said:
Phone is detected (in device manager) as
Qualcomm HS-USB QDLoader 9008 (COM3)
when connected to computer, automatically.
No button pressed.
The phone is dead (bricked) any button I press does not start or do anything. Only red led blinking.
Click to expand...
Click to collapse
Do you have any tool for read info from it. if no then is it take flashing from mi flash tool without any error. if you getting any flashing error then reply with screenshot.
Thank you for your answer.
I have tools and know about tools to read and write from it (fastboot, edl mode etc)
I know about Mi Flash Tool and other tools like QPST.
The bootloader of the phone is still locked. I didn't want or try to unlock it.
I have QPST Tool (QFIL flash tool) which I have used in the past.
A few month ago, I put the phone manually in EDL mode, using test points on the motherboard and succesfully backed up the phone.
Ok, so I understand you think this is not a power IC problem like it shows in the youtube video link I have posted ? And that I need to try to reflash.
I don't have much experience with flashing (I did not flash any phone) but I have some knowledge about, as you read above.
I'm gonna try to flash but I need to keep user data . I also think it is advisable to flash the same OS that I had before. (I have to search among saved mobile screenshots to find out exactly what version of MIUI I had)
But I am mostly interested in how the phone got in this situation.
Why over night it switched on while I put it to charge (it was completly discharged) powered on by itself then I powered it off while Android logo was displayed, and then only red blinking led always, no matter what I did.
I mention that I didn't try to update the OS manually because I was well satisfied with the MIUI I had. I know it was an update that the phone notified me since a long time ago. But I did let it or consent to update.
Do you think this problem was because the phone update forced somehow by xioami?
clabr2 said:
Thank you for your answer.
I have tools and know about tools to read and write from it (fastboot, edl mode etc)
I know about Mi Flash Tool and other tools like QPST.
The bootloader of the phone is still locked. I didn't want or try to unlock it.
I have QPST Tool (QFIL flash tool) which I have used in the past.
A few month ago, I put the phone manually in EDL mode, using test points on the motherboard and succesfully backed up the phone.
Ok, so I understand you think this is not a power IC problem like it shows in the youtube video link I have posted ? And that I need to try to reflash.
I don't have much experience with flashing (I did not flash any phone) but I have some knowledge about, as you read above.
I'm gonna try to flash but I need to keep user data . I also think it is advisable to flash the same OS that I had before. (I have to search among saved mobile screenshots to find out exactly what version of MIUI I had)
But I am mostly interested in how the phone got in this situation.
Why over night it switched on while I put it to charge (it was completly discharged) powered on by itself then I powered it off while Android logo was displayed, and then only red blinking led always, no matter what I did.
I mention that I didn't try to update the OS manually because I was well satisfied with the MIUI I had. I know it was an update that the phone notified me since a long time ago. But I did let it or consent to update.
Do you think this problem was because the phone update forced somehow by xioami?
Click to expand...
Click to collapse
this same thing happened to me today! I'm stuck with the red blinking light of Death!
Related
Guys,
I have a Xperia Active and I don't know how but my phone get stucked in qhsusb_DLOAD (Qualcomm HS-USB QDLoader 9008).
Any one know how I can fix it?
Hmmm that is sign of a hard brick, prolly on bootlader....What did you do? Tried to install cwm?
Try repairing using pccompanion or flashing custom rom through flashtools if pc can detedct it otherwise it's off to service i'm afraid
The true is that the phone is not mine, is from a friend (was mine but I sold it to him). He told me that he was using it and suddenly phone goes off and never powered on again. But I think that is a lie and he tried to upgrade it or did something with software.
I don't know how but doing some combo using power, volume buttons, putting battery in - out and connecting USB while I was doing this phone goes on and shown me "Sony Ericcson" on screen. Flashtool program recognized it as MTP and later phone goes off again in qhsusb_DLOAD state.
PC Companion doesnt recognize it in this state and to use Flashtool I need to get in flashmode.
If you can get to the sony ericcson logo can't you get in flashmode? What happens if you connect the phone holding vol button down?
Btw he probably didn't tell the whole truth, it's not a problem that just pops up, something got messed up in the system partition, he might have flashed or disconnected the phone while sw was updating or something similar
the phone has broken trim area, it can be repaired by guy called Alejassindrimo (not sure if I spelled it right)
It will work again, but SIM area when doing something with trim area is KO. so you need to spent 20 USD to get unlock, after this your phone will be good to go!
Hi Guys, greetings from India!
I have a E970 which I unfortunately bricked ( in what seems to be a hard brick) during flashing an updated ROM. The phone screen now does not turn on at all, though when I connect it to my computer the power button led flickers on and off, and the PC responds as if a removable device is getting attached to it and being removed in quick succession.
In Device Manager I can see that the phone gets recognized as QHUSB_DLOAD.
When I tried to run the unbrick process via LGNPST, the phone name flashes along with the COM port name in the software, then disappears, and then comes back again. Moreover, the process errors out at 85% but pressing the power button does nothing.
Since the screen does not turn on, I am not sure whether my phone goes into a download mode or not.
So - is the phone recoverable at all or is it all over? Please help.
Thank you.
Chironx2012 said:
Hi Guys, greetings from India!
I have a E970 which I unfortunately bricked ( in what seems to be a hard brick) during flashing an updated ROM. The phone screen now does not turn on at all, though when I connect it to my computer the power button led flickers on and off, and the PC responds as if a removable device is getting attached to it and being removed in quick succession.
In Device Manager I can see that the phone gets recognized as QHUSB_DLOAD.
When I tried to run the unbrick process via LGNPST, the phone name flashes along with the COM port name in the software, then disappears, and then comes back again. Moreover, the process errors out at 85% but pressing the power button does nothing.
Since the screen does not turn on, I am not sure whether my phone goes into a download mode or not.
So - is the phone recoverable at all or is it all over? Please help.
Thank you.
Click to expand...
Click to collapse
If device mgr is seeing the phone as qhusb, you done did bricked your phone. You need to jtag it to fix it. Your best bet would be to look into this... http://mobiletechvideos.mybigcommerce.com/lg-optimus-g-jtag-brick-repair/
Ok, hi guys... yesterday I misinterpreted some instructions before flashing Rajeev's PureX v4.1 rom... was on Niaboc79's ExistenZ Y v2.6.0... so went on, wiped and factory resetted... then, instead of formatting system/data, I formatted data AND system so obviously now it gets stuck at the Sony logo when booting because it has nothing to boot up and the only way to shut it off is with the small red button on the left side until it vibrates, resets then shuts off...
I then told myself I could simply flash a .FTF back from FlashTool, but alas, not this time... ok, I'm on D6503 Z2 with locked bootloader which is not unlockable... and now, when my phone's off and FlashTool asks to connect phone in flash mode the phone doesn't act as it normally would. when plugging usb cable, instead of the original green led, it quickly shows red, then green then nothing and on flashtool we can now see an error which is shown in the screenshot below.
Drivers are installed and I guess the problem now has to do with the bogus leds as they are the same just trying to connect in flash mode out of FlashTool... I Googled and read a lot about it yesterday on XDA and the only potential answer I could find was telling to flash a .ftf whrough FlashTool which was my first bet anyway but now, I really can't think of anything and would please appreciate your assistance about that... I hate to say this but I must admit what I'm requesting now is some help to get me through my own f*** up, please...
Might be a corrupt .ftf , try downloading another one or build your own with xperifirm+flashtool.
You can also try repairing with sony pc companion app...
Thanks for the quick answer... In fact I tested with 4 different ftfs I know are working... and as I said the problem is with the inability of phone to enter flash mode and its wrong leds when connecting to flash mode; not a software issue... I also tried with PCCompanion but it fails at detecting the phone since it freezes at the Sony logo and doesn't boot anything...
EDIT it also doesn't charge when I plug usb or ac. Instead it quickly toggles leds red, green, none one time and stays off... same way as when I try connecting it to flashmode holding vol-...
I've flashed many sony phones that don't boot / bootloop with flashtool and they always come to life again unless there's hardware problems
You phone is beeing detected in flashtool as beeing in flashmode so it's entering the correct mode. As a last resort i would try flashing on another pc/os , i still think it's pc related... are you using any android emulator on the pc? bluestacks / andy or that kind of stuff?
They cause loader.sin errors too... had that happen once on my work computer, uninstalled bluestacks and flashed fine afterwards.
Sorry i can't think of anything else right now...
I don't have another pc, but I reinstalled a pc backup so it is as when I originally set it up... reinstalled flashtool, reinstalled drivers and launched FlashTool to flash a .FTF. It just did the same as before flashes red, flashes green then nothing but the same errot message in FlashTool... but I noticed one thing, everytime I just plug phone to pc, Flashtool states it's in Flash mode as it is not. it was simply plugged in... and I don't use such as BlueStacks... and anyway the phone's leds react wrongly first then the asked action, flashing, cannot be applied hence the error message in FlashTool... thanx for your help...
I'm really used to flashing stuff and I know my mistake now was to format the system partition. From that time, it became impossible to flash any .ftf and the only info, signal I've got is the led quickly displaying red then green led intead of just green then starting to flash, when cable is plugged in, holding VOL-...
Damn formatting the system partition should not hard-brick your phone bro i've done exactly the same mistake on my also unlockable BL Z2 a long time ago, wiped everything and rebooted the phone without flashing the rom xD phone would only show sony logo (can't remember led status) but it flashed normally and came back to life. maybe you got really really unlucky and your bootloader got messed up somehow :| You already did everything i would have done without success, i'm also out of ideas... but xda is full of great minds, maybe someone else can help you better.
You are absolutely right... I had done the same mistake on my xperia T, a while back, and a simple flash from flashtool had taken care of it... I don'T even come to ask for help, usually... when I mess things up, I have always succeeded in bringing the thing back to life... until now...
thanx a lot for your help.
EDIT: Oh, even worse now... when flashtool is done preparing the FTF to be flashed and asks to plug in phone holding VOL-, I tried just plugging the phone WITHOUT holding any button and it did the exact same error I screenshotted earlier, with same red/green/none scheme... So computer really sonsiders phone to be in flashmode from the moment it's plugged in...
No problem, wish i could help more. It does seem like your phone is stuck on fastboot or flashmode. If you just power on the phone and connect it to pc (no flashtool running) does your pc device manager detect your phone? what device does it detect? If you connect in fastboot mode (vol up + plugin usb cable) what do you see in the device manager? Maybe try completely discharging your phone, leave it powered on for a day or so until the battery dies completely, maybe it'll "reset" to normal mode? Just throwing some ideas now, at least we're keeping the thread alive, maybe someone more expert will look at it too
Why you guys quoting every post? Makes it tedious scrolling on mobile.
@rubiicon59 old habits lol xD i edited my posts and removed the quotes, since no one else is participating in the thread they aren't really needed...
ptmaniac said:
No problem, wish i could help more. It does seem like your phone is stuck on fastboot or flashmode. If you just power on the phone and connect it to pc (no flashtool running) does your pc device manager detect your phone? what device does it detect? If you connect in fastboot mode (vol up + plugin usb cable) what do you see in the device manager? Maybe try completely discharging your phone, leave it powered on for a day or so until the battery dies completely, maybe it'll "reset" to normal mode? Just throwing some ideas now, at least we're keeping the thread alive, maybe someone more expert will look at it too
Click to expand...
Click to collapse
first, sorry for the late answer... ok,,, when I only plug usb cable into phone, it is not detected... However, I can boot into fastboot and then it's detected in device manager as in the screenshot below... But, it does flash red just before turning blue for fastboot... just the same quick red flash as when I plug USB in...
ptmaniac said:
No problem, wish i could help more. It does seem like your phone is stuck on fastboot or flashmode. If you just power on the phone and connect it to pc (no flashtool running) does your pc device manager detect your phone? what device does it detect? If you connect in fastboot mode (vol up + plugin usb cable) what do you see in the device manager? Maybe try completely discharging your phone, leave it powered on for a day or so until the battery dies completely, maybe it'll "reset" to normal mode? Just throwing some ideas now, at least we're keeping the thread alive, maybe someone more expert will look at it too
Click to expand...
Click to collapse
first, sorry for the late answer... ok,,, when I only plug usb cable into phone, it is not detected... However, I can boot into fastboot and then it's detected in device manager as in the screenshot below... But, it does flash red just before turning blue for fastboot... just the same quick red flash as when I plug USB in... it also doesn't charge when plugged in... no orange led... was at about 90% when it stopped working...
Just a quick tip- don't use the red button, it is only for emergency and it is annoying to open the flap everytime. Instead, use the Power + Volup and hold for a few seconds.
WOW! reallly can'T say why it didn't work first time, but I tried reinserting sd card and retake it out, started one last time to flash a .ftf and it worked.... Great, now back on my backup... everything working as it should now....
thanx to @BlAckXpeRia for the reminder tip... Red button should only be used when everything else failed to shut the phone down...
and of course, thanks to @ptmaniac for your help all along these stressful last 2 days... THANKS!!!
oh yeah, SOLVED
Nice!! i really really like this phone, i would be very sad if it died on me like that, good to hear you got your phone back
M having same issue without any SD card, what should I do ? :'(
Hello,
I've bricked my phone after a TRWP recovery. I've tried the solution provided on the forum (wait until the battery dies, unplug the battery....). Nothing worked.
I've tried to connect my phone to the PC and it cannot be detected. I have flashing red light when first connected and after few seconds a constant red light that stay for 30 seconds and flashing red light again.
I've tried to use adb devices command and nothing shows up. On linux, I've did "lsusb" command and the phone didn't show up.
Is that my device definitively broken or there is still option that I didn't explore?
Thanks for your support
Once time this happened to me but with my Z1, after desperately search for a solution and read many tutorials, the only solution was reinstall all drivers and connect device to be repaired with Sony Pc Companion, but is necessary have some of battery, if you drained completely, then charge it at least 50%
This works for me, and maybe works now, as long you device led indicator works and Pc sounds when plug in USB, then there's hope.
As @BalamXDroidhe said, charge your phone, put it off and try the program Pc Companion or Xperia Companion, but DO NOT WAIT for the computer to recognize the phone, why still remains the operating system is not loaded.
Just go to repair the software and i believe that everything will be fine.
yofranch said:
Hello,.............
Thanks for your support
Click to expand...
Click to collapse
Thanks for the reply. I did try Sony companion. Unfortunatly this is not the software that is not recognizing the device, the computer itself don't shows any Z2 on USB port. Furthermore, I went to a repair shop and said that the battery is not charging at all. A mother board problem to his point of view.
I'm afraid that is not much to be done at this stage
If you have any suggestion....
Thanks
first of all you need to charge the battery or swap it with another one if the phone isn't charging it at all. then try to boot the phone in flash mode with flashtools in order to try to flash a new .ftf (use the guide below for flashtools).
http://www.gizmobolt.com/2015/04/09...z3-23-1-a-0-690-ftf-using-flashtool-manually/
This is the first step to do in a such situation.
yofranch said:
I've bricked my phone after a TRWP recovery. I've tried the solution provided on the forum (wait until the battery dies, unplug the battery....). Nothing worked.
Click to expand...
Click to collapse
Never wait until the battery dies, that is not wise at all.
How did you unplug the battery? You completely disassembled the device? That is not wise at all.
You should have simply pressed Vol up plus power for 3 seconds, that would have forced a power disconnect. It is that easy.
The 2 things you did are somewhere close to the worst things to do when your device has a problem.
You could try a charged battery from another device as said but you will likely physically damage the device when you open it. or simply leave on wall charger for a few hours and see if it can charge.
Ensure your USB cable is a "data" USB cable, not a cheapo charge only cable.
Even try another windows computer.
May I ask how did you brick your device? What did you do in recovery?
Sent from my D6503 using XDA-Developers mobile app
Hello,
I've had a problem while updating a custom ROM and I had to restart the rooting process from scratch. All went well (Kit kat install, rooting, TRWP install) until I've used a previous TRWP backup. Since then, only red light
Is there an hardware problem occured at the same time that I flashed the device... Very unlikly. My feeling is that the kernel is corrupted and don't allow the device to start the early stage boot and so no more charging and no connection possible. It's just a feeling.
Thanks for your support
yofranch said:
Hello,
I've bricked my phone after a TRWP recovery. I've tried the solution provided on the forum (wait until the battery dies, unplug the battery....). Nothing worked.
I've tried to connect my phone to the PC and it cannot be detected. I have flashing red light when first connected and after few seconds a constant red light that stay for 30 seconds and flashing red light again.
I've tried to use adb devices command and nothing shows up. On linux, I've did "lsusb" command and the phone didn't show up.
Is that my device definitively broken or there is still option that I didn't explore?
Thanks for your support
Click to expand...
Click to collapse
What do you mean by "after a TWRP recovery"?
Your bootloader is locked or unlocked?
Use a wall charger to charge your phone.
Hello,
"Never wait until the battery dies, that is not wise at all." => I did not at a first, I've tried to flash with flash tool the stock rom with roughly 80% battery. The phone was already not detected by computer ( I tried Linux, Windows 8 and Windows 7 computer).
"How did you unplug the battery? You completely disassembled the device? That is not wise at all.
You should have simply pressed Vol up plus power for 3 seconds, that would have forced a power disconnect. It is that easy. "
=> I couldn't agree more that is not wise to disassemble the device, I've done it after I tried the Vol up+ power technique.
"The 2 things you did are somewhere close to the worst things to do when your device has a problem." => The next time...
"You could try a charged battery from another device as said but you will likely physically damage the device when you open it. or simply leave on wall charger for a few hours and see if it can charge." => No charge at all over night with genuine Sony charger and cable. I brought it to a repair shop and with a magnetic charger, not better.
Thanks for your reply.
"What do you mean by "after a TWRP recovery"?" => I've made a backup before flashing my custom rom, just in case. As I said, the rooting process went well until I launch the backup recovery.
"Your bootloader is locked or unlocked?" I'm afraid that is the step I've missed after flashing KitKat and rooting. Is that possible that locked bootloader can lead to that mess?
"Use a wall charger to charge your phone" => No charge, just blinking red light even with battery level at least 50%.
Thanks for your reply.
Same thing happened to me. My phone got bricked.
Its not androxide flashtool or sony companion
Use this.
Its official sony xperia flashtool.
Its called 'Emma'
http://developer.sonymobile.com/open-devices/flash-tool/
All process shared in link..
Good luck
Hello,
I also tried Emma without any success.
Thanks again
The exact same thing happened to me when i flashed a kernel, what i did, was just open xperia companion, click on repair software, and follow the instructions, connecting in flash mode and that stuff, and boila, brand new. i almost cried when that happened to me tho:crying:
it seems that you are using locked bootloader phone, and flashed custom kernel or twrp image, can you connect in fastbooot mood of in flash mood? (by pressing vol+ and connecting usb or vol- and connecting usb respectively),
Hi everyone i have a xiaomi redmi 3 pro i think because it has 4 gb of ram, and it doesnt on anymore. I was flashing the stock rom with twrp but it block the process, I turned off my phone and now it doesn't on. No fastboot, No recovery, nothing. The screen doesn't on.
I've tried to connect it with the computer, and it shows a "Qualcomm HS-USB QDLoader 9008 (COM 20)" so I've read some guides that made me use the xiaomi flash tool but when I tried to install the global rom but il fails with "cannot receive hello packet"
PLEASE HELP ME I DON'T KNOW HOW TO DO!
leocap33 said:
Hi everyone i have a xiaomi redmi 3 pro i think because it has 4 gb of ram, and it doesnt on anymore. I was flashing the stock rom with twrp but it block the process, I turned off my phone and now it doesn't on. No fastboot, No recovery, nothing. The screen doesn't on.
I've tried to connect it with the computer, and it shows a "Qualcomm HS-USB QDLoader 9008 (COM 20)" so I've read some guides that made me use the xiaomi flash tool but when I tried to install the global rom but il fails with "cannot receive hello packet"
PLEASE HELP ME I DON'T KNOW HOW TO DO!
Click to expand...
Click to collapse
I have very similiar problem with you, i hope someone has a solution
Wikusaurus said:
I have very similiar problem with you, i hope someone has a solution
Click to expand...
Click to collapse
Edit: I've found the solution.
1. go into EDL mode by pressing Power vol+ vol-
2. use miphone 20151028, don't use recent mi flash
3. Flash TWRP
4. Proceed to flash ROM (in my case i use RR Os) via TWRP
Hello, is it possible that I have my phone bricked after a battery replacement?
Heres what happened: I had obviously a battery problem. So I ordered one from ebay and I replaced it. The new battery seem to work, however the phone will not respond to the buttons. Not any buttons. Only if I plug in a cable, mi logo appears for a few seconds and then a big battery bar shows for a few more seconds. Then nothing. (If I put in the old battery and I plug in a cable, the reaction is the same BUT no battery bar appears). The phone does not respond to any buttons like vol +/- holding together with power on, etc. Any help? Thanks, Filip.
Dexaderon said:
Hello, is it possible that I have my phone bricked after a battery replacement?
Heres what happened: I had obviously a battery problem. So I ordered one from ebay and I replaced it. The new battery seem to work, however the phone will not respond to the buttons. Not any buttons. Only if I plug in a cable, mi logo appears for a few seconds and then a big battery bar shows for a few more seconds. Then nothing. (If I put in the old battery and I plug in a cable, the reaction is the same BUT no battery bar appears). The phone does not respond to any buttons like vol +/- holding together with power on, etc. Any help? Thanks, Filip.
Click to expand...
Click to collapse
your battery/connector/header(on mainboard side) seems broken. battery usually does not impact any software. It's better if you open new thread specifically about your problem, so anyone can join to discuss further.