Hello, i think my phone is completely dead. Here's what happened : i wanted to go back to a stock ROM so i used MiFlash, but it gave me an error really early after a couple seconds (modem flash error i think) and now it doesn't respond. When i connect it to my PC nothing happens (nothing in device manager). The only sign of "life" is that when the battery is low (i think that's the case), the LED starts flashing RED until the phone runs out of juice. Any ideas? I already tried charging the phone all the way up and then discharging it completely(those are the only things that seem to work as they should) but the phone seems completely dead. I had a similar thing happen to me before on my older Xiaomi phone but that time my PC at least managed to detect it in device manager as qdloader 9008 (EDL mode) but that just doesn't seem to work now. Would shorting the test points work to make it go into EDL mode or is it a lost call? The bootloader was unlocked before flashing and i chose the option in MiFlash that doesn't lock it again. Thanks for anything. EDIT: Phone sent to a repair centre.
Related
Hi guys i think my galaxy s4 may be hard bricked. i took my phone out of my pocket today to find it completely dead. The phone is rooted and was running jamals 4.3 ge rom. The only explanation i have is that i bumped it in my pocket and it somehow installed the ota update for the google edition phone. very unlucky i know but i cant think of any other explanation apart from hardware failure. When i try to power the phone now i get a flash of green across the screen and the phone vibrates. i then get a solid blue led in the corner. Ive hooked the phone up to the computer and odin recognises it as com5 and blue. ive checked device manager and windows recognises it under portable devices as jussa sam (my phone) i am unable to get the phone into download mode its completely dead apart from a blue led. Any suggestions? ive ordered a usb jig to see if i can force it into download mode. When plugged into the charger the phone is getting very hot.
If the screen goes on, you can repair it.
Put out battery and put it in again.
vol down+home+power button
That must work with odin.
If not try with kies.
My guess is that you have a hardware failure. It's almost impossible to brick it in the way you descriped. You just got unlucky. Nothing you can do that will fix it.
looks like you killed your bootloader. And so the regulation of charching and booting
try kies. if that not works, deinstall the driver from your phone.
restart computer and plug in your phone.
Look what driver will be installed
The OTA would not install on a rooted phone, it would fail during the process and revert back to normal booting.
Convinced its hardware fault nw. Will put it in to Samsung for warranty hoping they won't be able to tell it's rooted. Pic of screen in link http://i105.photobucket.com/albums/m217/justinneumann01/Mobile Uploads/image_zps619f1980.jpg
So today was time for me to wipe clean and install a factory image like I've always done (bootloader unlocked fyi). I go through the usual fastboot flash procedures. Get into the OS, login, start the play store updates. I let my phone sit and 20 minutes later I try to wake it to check the status... NOTHING. Screen has been black since. I've tried charging it, getting into the bootloader mode. I even tried using XiaoMiFlash and QFIL to get things back on track. I have the "Qualcomm HS-USB QDLoader 9008" in my device manager. I can hear the phone connecting and disconnecting when I hold the power button.
QFIL has been complaining about Sahara failing but when it does gets past that it fails at the Firehose stage where it tries to upload files to the device.
I'm pretty pissed that a legit factory image from Google would cause that. My device has never suffered from any soft or hard bricks before. Never exhibited battery drain issues either. But today after a flash it goes flat out dead.
Has anyone ever had any luck unbricking a 6P through XiaoMiFlash or QFIL?
You may have better luck posting in the dedicated thread for this;
https://forum.xda-developers.com/nexus-6p/general/howtos-debrick-nexus-6p-stuck-edl-9008-t3552838
Good luck!
bought this phone used and I don't think it was rooted but never checked, confirmed. Last night it turned off and will not turn on anymore..
Tried the pwr button for several minutes and no change. Plugged it in with several different cables and no change.
Any other suggestions or options? USB to computer detects something but says it can't install the driver.
Any ideas?
oNe
Can you enter to the bootloader menu? Maybe you can enter recovery and wipe the cache and dalvik
martinfarrell11 said:
Can you enter to the bootloader menu? Maybe you can enter recovery and wipe the cache and dalvik
Click to expand...
Click to collapse
negative, either the phone is totally dead or the screen is dead but NOTHING happens when pwr is pressed
here is what I have tried:
1. Press and hold PWR button for over 3minutes
- Plugged in and unplugged into ac - no change
2. Press and hold volume DOWN + Pwr for over 3minutes
- Plugged in and unplugged into ac - no change
3. Plugged into different a/c power outlets with 2 different chargers - no change
NOT sure what else to try or do?
Funny thing is if ya plug into a computer it does indeed detect "something'
However it says it can't load the USB drivers something about QU_***
Open to any ideas and suggestions.. WHILE I would love to get the phone working whats more high priority for me now is the 20gb's of pics that apparently did NOT back up.
oNe
Sean Price said:
Funny thing is if ya plug into a computer it does indeed detect "something' However it says it can't load the USB drivers something about QU_***
Click to expand...
Click to collapse
Funny thing is- that "something" is the solution to your problem. Capture the error message completely and search the 6P forums for that. Several threads on the "something" issue.
v12xke said:
Funny thing is- that "something" is the solution to your problem. Capture the error message completely and search the 6P forums for that. Several threads on the "something" issue.
Click to expand...
Click to collapse
Several threads with no solution. I went through the same "something" . Can't be fixed
v12xke said:
Funny thing is- that "something" is the solution to your problem. Capture the error message completely and search the 6P forums for that. Several threads on the "something" issue.
Click to expand...
Click to collapse
fixed that issue, aka QHSUSB_BULK is now working properly according to Device Manager.. but Nexus 6P is not detected, and doesn't even show up in Disk Management either.
Any other ideas?
please advise..
oNe
Sean Price said:
fixed that issue, aka QHSUSB_BULK is now working properly according to Device Manager.. but Nexus 6P is not detected, and doesn't even show up in Disk Management either. Any other ideas? please advise.. oNe
Click to expand...
Click to collapse
If you found the right EDL_9008 thread, there is Qualcomm software to download for your PC. If your phone is in the right downloader mode you can use the PC software with a special recovery.img. I don't know anything about it, just read through the threads long ago. It's a mixed bag with some success stories, some not. Keep looking though, I think you are on the right track. The original poster was "Tenfar" if I recall correctly. Good luck.
Try cleaning out the charging port.
Hi there,
I think we are in the same/similar boat. My phone shut off while using it (screen froze, then went black) and seems to have bricked itself. I *am* able to get mine to turn on, but only about once per day after it has been left plugged in for a few hours (although there is no indication it is charging while plugged in - never gets warm, no lights, etc.) I can get into recovery if I am lucky (usually get to the android bot laying on its back, then PWR+VOLUP just causes the phone to shut off instead of actually getting into recovery menu.) I've been able to clear cache/factory wipe from recovery menu with no luck. I never did unlock the bootloader so I am unable to use fastboot to do anything. I tried to flash a few OTA (full and incremental) images using adb when I am able to get into recovery, but they always failed in one way or another.
I've been trying the methods described in the 'tenfar' threads - using the xiaomi flasher and QPST tools. The xiaomi tool always fails for me. I have been able to get the QFIL tool to successfully 'download' about 3 times now, with tenfar's recovery images. However, after the success message, the phone doesn't do anything (I read in other threads it should reboot itself) - and after unplugging, the behavior of the device seems to be the same - just stuck and won't turn on at all.
Right now I think I am stuck in 'EDL' mode where the only evidence that the device isn't completely dead is that it shows up in device manager as 'Qualcomm HS-USB QDLoader 9008 (COM3)', and the factory imager tools do recognize it.
It *seems* like the only way forward is to somehow get one of these factory tools to flash the right set of files onto the device - I've tried a few now with no luck. I even tried extracting the relevant *.img files out of the google factory image download and replacing tenfar's image files with them. I was able to load those onto the device with QFIL. This morning my attempt at turning on the device has me stuck on the white google logo, which is new behavior for me - usually it shows the logo for ~5-10 seconds then the device powers off. I've left it on for a while stuck on the white google image, but I'm not sure if I'm doing anything useful here.
Here are my reference threads:
tenfar's 'debrick' thread
QFIL thread
If anyone has any crazy ideas, I am open to try them. Thank you.
Maybe disable big cores?
apples1678 said:
Hi there,
I think we are in the same/similar boat. My phone shut off while using it (screen froze, then went black) and seems to have bricked itself. I *am* able to get mine to turn on, but only about once per day after it has been left plugged in for a few hours (although there is no indication it is charging while plugged in - never gets warm, no lights, etc.) I can get into recovery if I am lucky (usually get to the android bot laying on its back, then PWR+VOLUP just causes the phone to shut off instead of actually getting into recovery menu.) I've been able to clear cache/factory wipe from recovery menu with no luck. I never did unlock the bootloader so I am unable to use fastboot to do anything. I tried to flash a few OTA (full and incremental) images using adb when I am able to get into recovery, but they always failed in one way or another.
I've been trying the methods described in the 'tenfar' threads - using the xiaomi flasher and QPST tools. The xiaomi tool always fails for me. I have been able to get the QFIL tool to successfully 'download' about 3 times now, with tenfar's recovery images. However, after the success message, the phone doesn't do anything (I read in other threads it should reboot itself) - and after unplugging, the behavior of the device seems to be the same - just stuck and won't turn on at all.
Right now I think I am stuck in 'EDL' mode where the only evidence that the device isn't completely dead is that it shows up in device manager as 'Qualcomm HS-USB QDLoader 9008 (COM3)', and the factory imager tools do recognize it.
It *seems* like the only way forward is to somehow get one of these factory tools to flash the right set of files onto the device - I've tried a few now with no luck. I even tried extracting the relevant *.img files out of the google factory image download and replacing tenfar's image files with them. I was able to load those onto the device with QFIL. This morning my attempt at turning on the device has me stuck on the white google logo, which is new behavior for me - usually it shows the logo for ~5-10 seconds then the device powers off. I've left it on for a while stuck on the white google image, but I'm not sure if I'm doing anything useful here.
Here are my reference threads:
tenfar's 'debrick' thread
QFIL thread
If anyone has any crazy ideas, I am open to try them. Thank you.
Click to expand...
Click to collapse
I have the 100% same issue. Screen froze,then went black and now its stuck in EDL mode. I need my data. Recovery access or anything else would be fine/enough for me. I have had LineageOS and TWRP on the device. With TWRP i can access my data.
How have you got your device on? Mine dont start once a day or so. Its always in EDL mode ( 9008 ).
ncc8uetou5et said:
I have the 100% same issue. Screen froze,then went black and now its stuck in EDL mode. I need my data. Recovery access or anything else would be fine/enough for me. I have had LineageOS and TWRP on the device. With TWRP i can access my data.
How have you got your device on? Mine dont start once a day or so. Its always in EDL mode ( 9008 ).
Click to expand...
Click to collapse
Sorry bud - I never was able to get any further than when I posted this. I eventually gave up, got a full out of warranty refund through my CC after the manufacturer wouldn't help me at all, and upgraded to a Pixel XL. I still do have the device, I should try to boot it up again . I didn't have any data concerns on my device so I was able to give up... good luck!
I don't know what has happened... I took the phone off my charger at about 80%, was playing on it for a little bit and then restarted the phone.... the next moment I look at it, it is just a black screen. It is completely dead, pushing or holding power button does nothing (held for minutes multiple times), holding volume buttons & power button does nothing, plugging in to charger does nothing. It seems to be completely dead.
I have no idea why, it was working fine until I selected restart and was dead a few minutes later. Completely normal usage prior to that.
Anyone have any suggestions for what I can do to get this phone turned back on at all??
Nubia Z17 NX563J
Kind of a pain that these are completely sealed units...
I've just seen some posts about the Nubia Emergency Tool. If I plug my phone into the PC it does show up as "Qualcomm HS-USB QDLoader 9008" device so it looks like the emergency tool might work with it.
But does that mean it will flash my phone and I will lose all data on it?
There was nothing wrong with it just before, is there no other way to recover the data?
bunta126 said:
I've just seen some posts about the Nubia Emergency Tool. If I plug my phone into the PC it does show up as "Qualcomm HS-USB QDLoader 9008" device so it looks like the emergency tool might work with it.
But does that mean it will flash my phone and I will lose all data on it?
There was nothing wrong with it just before, is there no other way to recover the data?
Click to expand...
Click to collapse
How long have you used your phone? Better to replace the battery as one of my phones behaves the same way. Just replace the battery and that's it.
Tims Fong said:
How long have you used your phone? Better to replace the battery as one of my phones behaves the same way. Just replace the battery and that's it.
Click to expand...
Click to collapse
But the battery is not replaceable...?
bunta126 said:
But the battery is not replaceable...?
Click to expand...
Click to collapse
[NX563J][Project Treble][Android 10-11-12-13][GSI][AB]
Whats about magisk it Boot no more gsi after Flash magisk use this:https://github.com/ExpressLuke/phh-magisk-builder/releases/download/08-12-2020/magisk-v21.1-phh.zip
forum.xda-developers.com
bunta126 said:
But the battery is not replaceable...?
Click to expand...
Click to collapse
you need special usb cable i got same problem long time before
for edl mode
Update: I managed to get the bootloader and recovery working using the Nubia Emergency Tool. The system would not boot and even a dirty flash of the same ROM I was using would not make it boot. I could reinstall the ROM however and the phone is now working fine again.
So, I rebuilt my phone with a completely different ROM on Android 13, and today the same thing has happened: I chose to restart my phone and it has gone black and won't turn back on again.
It has been running perfectly fine on the new ROM until today, why would this same problem reoccur? I suppose battery is likeliest issue... although maybe there is something I'm doing to break the system?
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.