Hi Everyone,
I have a 4 year old Nokia 7.1 that was working fine a week ago with Android 10.
I accidentally let the battery drain out, phone would not turn on - no Android, no download mode, nothing on the screen however I turn it on - power/volume up/down, etc
I have replaced the battery with a brand new one (very carefully).
New to Android flashing but...
On attaching to PC I get HS-USB Diagnostics 9008 device. I have QFIL, QPST, firmware, firehose programmer for SDM636, etc.
I have shorted pins 3,4 internally, rebooted phone, battery in, battery out. Whatever I do it won't enter EDL mode to try reflashing.
QFIL always says - Switch to EDL Fail Failed to Switch to Emergency Download Mode.
Tried Linux with sahara, etc and phone is visable, but again no respose - can't enter EDL mode.
I have a feeling the hardware may be fried anyway
Am I doing something wrong? Any ideas? Do HMD block EDL?
I think its a lost cause...
Thanks.
Related
Hello. I'm new here. and not native speaker.
I'll try my best for English.
My device got soft bricked after I'm trying to install the new ROM.
Actually I had installed the ROM but It didn't appear anything.
Then I'd try to restore my backup to Its place.
It made my phone brick.
I can't boot into recovery mode, ROM and also FTM mode.
I must have an access to adb, If I want to boot into bootloader.
But I don't have any access to it at all!!.
I had read some post and I hope that DFU can help me.
But I don't know how can I boot into that mode.
And I had try hold volume + and - with and without power button but it still the same.
I had read that the DFU mode will display nothing but have the briefly red led.
I had accident plug the USB to device without battery.
And I got it, The briefly red led light with nothing change in the display (still nothing).
My computer recognizes it as a ZTE technology device. But It's in an unspecified device zone.
I had installed the ZTE USB device (My computer is MS Windows 8.1) and I had also installed it with unsigned driver mode too.
What could I do for getting it to work again?
Have I found the correct DFU mode?
My device is ZTE V817.
With MSM8225Q CPU and MSM7627A board platform specified in default.prop.
Hi,
I got my new phone a couple of days back, installed CM13 (officially unlocked, did that with TWRP + install ROM) probably incorrectly because i couldn't get the fingerprint sensor and other stuff to work at all.
Today my phone turned off by itself with around 70% of battery left and it's not responding anymore. Cannot go into Recovery mode, not even to Fastboot. Connected it to the charger and have the red light of the devil blinking... Tried to do everything i found online but i couldn't get into EDL mode (and then Flash through MiFlash), since fastboot is not working at all.
I really don't wanna have to open the back of the phone and. What can i do to save the phone? Is there any proven solution and a comprehensive guide to this (for a total idiot like me)?
Yes there is deep flash cable method search on xda/youtube it works like a charm,😉, this method saved me once
Try this (http://forum.xda-developers.com/redmi-note-3/how-to/guide-how-to-flash-hard-bricked-redmi-t3490055) works 100%
Try to disconnect and reconnect the battery.
This has kicked me into EDL mode once and after flashing it was fine
Both methods are sound, but if you decide to remove the back cover, remember to eject the SIM card tray first
Thanks for the replies, i was hoping i wouldn't have to have to open the back cover and disconnect the battery but it seems to be the only option at this point.
The deep flash cable doesn't seem that difficult tho, why don't you give it a shot? It seems like that's what they use at MI service centres after all.
So i have managed successfully to have the pc recognise the device as Qualcomm Hs USB Qdloader 9008, opened the MiFlash tool and recognised the device, but when i try to flash a stable MIUI rom i get an error: "Write timed out" as many times i tried to do it.
Does anybody have a suggestion?
My device was unlocked officially and i have no recovery no fastboot nothing at all.
alphax_ said:
So i have managed successfully to have the pc recognise the device as Qualcomm Hs USB Qdloader 9008, opened the MiFlash tool and recognised the device,
Click to expand...
Click to collapse
Which method you used - Deep Flash cable or Battery disconnect?
Yeah sorry i did not mention it, disconnected the battery.
i tried the battery removing method but the phone is not responding
now need to try cable method
Ryan Raghendh said:
i tried the battery removing method but the phone is not responding
now need to try cable method
Click to expand...
Click to collapse
Get into EDL
Hello Members,
The device was stuck in boot loop so i tried to flash via EDL mode. First it came to edl mode but while flashing i got some XML error. Now i tried to put the phone again in EDL mode but its not working.
I had removed the battery and and i have connected to 2 jumper pins 1 and 4 and connect the usb but the phone dont seems to come to edl mode. just flashes the MI screen and power off repeatedly.
Now i connect the phone directly with battery on and its coming as charging but surprisingly the phone got detected, the device manager shows the phone as Linux file stor gaget usb device. I tried to flash with mi flash tool and its running indefinitely saying flashing..
Help...
How about good morning friends.
I had a problem recently, I tried to update my LG to Android 10 to the Android 10 version, but at 80% the cable moved and there was a failure in the update, so the phone was left with screen off, which was recognized by the PC in 9008 mode, I looked for a tutorial that said to flash some Laf A and B files, But at the time of doing it, the video asked me to reboot it. But it was one of the biggest mistakes. The PC no longer recognized the phone in 9008 mode, it only felt lukewarm implying that it was charging.
Will there be a solution?
Please help.
Did you flash the laf a and laf b? If so, can you boot to download mode now with vol up + plug in phone?
Hi,
My BLA-L09 (Mate 10 Pro) is bricked due to a bad firmware update. I have a black screen, I cannot enter any mode (recovery, fastboot). But when I plug/unplug the phone, Windows detects it. I've downloaded (and paid some credits) DC-Phoenix. Now the phone is detected as a USB COM 1.0 device since I've installed the driver as explained here https://www.dc-unlocker.com/flash-bricked-huawei-phones-in-huawei-1-mode. With Dc-Phoenix, I can boot into fastboot mode thanks to testpoint mode. But my problem is that everytime I leave fastboot mode, the phone screen turn to black (like if it's shut down).
I guess my board software is broken, so I would lilke to re-install a fresh board software (via testpoint fastboot mode using Dc-Phoenix), but unfortunatelly, I cannot find a place to download board software for BLA-L09.
Anyone knows where we can find board software for BLA-L09?
Is there another way to unbrick my phone? Considering I can go in fastboot mode, I hope there is still a chance!
iBen68 said:
Hi,
My BLA-L09 (Mate 10 Pro) is bricked due to a bad firmware update. I have a black screen, I cannot enter any mode (recovery, fastboot). But when I plug/unplug the phone, Windows detects it. I've downloaded (and paid some credits) DC-Phoenix. Now the phone is detected as a USB COM 1.0 device since I've installed the driver as explained here https://www.dc-unlocker.com/flash-bricked-huawei-phones-in-huawei-1-mode. With Dc-Phoenix, I can boot into fastboot mode thanks to testpoint mode. But my problem is that everytime I leave fastboot mode, the phone screen turn to black (like if it's shut down).
I guess my board software is broken, so I would lilke to re-install a fresh board software (via testpoint fastboot mode using Dc-Phoenix), but unfortunatelly, I cannot find a place to download board software for BLA-L09.
Anyone knows where we can find board software for BLA-L09?
Is there another way to unbrick my phone? Considering I can go in fastboot mode, I hope there is still a chance!
Click to expand...
Click to collapse
Take a look at my GDrive Folder
Btw latest DC provides software testmode and hard brick recovery...