Database Users

A2017U Totally unresponsive - blank screen - unresponsive to any button combination

Has anyone any idea on how to get out of this situation. Device totally unresponsive, screen is black blank and displays nothing irrespective of button press combinations, including EDL. Not that its of any consequence now but this was achieved by my flashing a data file onto and overwriting the "aboot protected partition"
Device cannot be switched "on" and therefore is not recognized by windows device manager. Windows has all drivers installed i.e. ZTE - Qualcomm - Qualcomm EDL, although this is rather a moot point considering the device won't switch on.
The following files are still alive both on my device external SD card and in a windows "C:" folder --- B20 file, B27 file, B29 file, B15 file, plus a TWRP backup. To repeat myself all and every button combination has been used to no effect.
I rather much doubt that I shall get an answer to this question but has anyone any idea as to how I can get in the position where I can flash any of the above files?

Attempt to put it in edl mode I believe there is an unbrick guide somewhere around here. Aboot is related to bootloader so your phone is bricked.

Do you hear any sound from the PC when you connect the phone? This is particularly important because with the "wrong" driver enabled your device may not show in Device Manager, but it most likely, may have booted into EDL mode. Please check this and post back. If there's a sound on connect, there is hope. Nothing ZaDig and the new unbrick guide can't help you fix. I was in a similar hopeless situation a few weeks back but I resolved it with the help of the unbrick guide.

@george241312 ... @KwesiJnr ... I appreciate your answers and thank you for bothering to reply.
george ... Sad to say I was fully aware of what I was doing when I overwrote the "aboot" partition and anticipated ending up in something like my present situation. I have one final line of help to try before giving up all together.
Kwesi ... The only sound my device made was agonizing screams as I totally bricked it.
THANK YOU ALL BUT NO MORE REPLIES IF YOU PLEASE - CONSIDER THIS MATTER CLOSED ..... The device is dead due to my own stupidity and I will just live with that.

Try connecting the phone to another computer or wall charger ?

Non Hacked/Rooted 6p Shut Off And Will Not Turn On

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!

Hardbricked to Qualcomm USB 9008

Really hoping someone can help me out here. I have a Nexus 6P, Non-BLOD. Yesterday, after clean flashing the latest version of EvoX, while setting some things up, device randomly crashed. No Shut down animation or anything. Just black screen. Tried turning it on via Power Button and then Power And Volume Buttons but nothing works. Connected it to PC and see it's Detected as Qualcomm USB Bulk (9008) in Coms and Ports. Did some research and found out I have to flash via QFIL. And this is where I am stuck. I tried several versions, but it doesn't flash/gives Shara error. I tried reinstalling driver. I also read a guide here. But the Firmware link is dead and it says to flash via MiFlash, something I can't even try since the Link in the OP is dead. I tried some different versions of QFIL but all of them give a Sahara Communication error. Now I'm pretty much at a loss on what to do. I'd really like to fix my 6P. And I would appreciate anyone taking the time to point me in the right direction, or help me fix it. Thanks in Advance.

DarthVader said:
Really hoping someone can help me out here. I have a Nexus 6P, Non-BLOD. Yesterday, after clean flashing the latest version of EvoX, while setting some things up, device randomly crashed. No Shut down animation or anything. Just black screen. Tried turning it on via Power Button and then Power And Volume Buttons but nothing works. Connected it to PC and see it's Detected as Qualcomm USB Bulk (9008) in Coms and Ports. Did some research and found out I have to flash via QFIL. And this is where I am stuck. I tried several versions, but it doesn't flash/gives Shara error. I tried reinstalling driver. I also read a guide here. But the Firmware link is dead and it says to flash via MiFlash, something I can't even try since the Link in the OP is dead. I tried some different versions of QFIL but all of them give a Sahara Communication error. Now I'm pretty much at a loss on what to do. I'd really like to fix my 6P. And I would appreciate anyone taking the time to point me in the right direction, or help me fix it. Thanks in Advance.
Click to expand...
Click to collapse
Same thing happened to me in the same ROM (Weird) .. but i managed to flash the qfil successfully .. but still phone doesnt boot up .. here's what you should do ... try to hard reset the phone until you hear the disconnecting sound from pc . Ready all the necessary flash in the qfil and as soon as u hear the device connected hit the download button .. it will flash without the sahara protocol error . Be quick ! tell me if that fixed ur problem . Peace

hk1271 said:
Same thing happened to me in the same ROM (Weird) .. but i managed to flash the qfil successfully .. but still phone doesnt boot up .. here's what you should do ... try to hard reset the phone until you hear the disconnecting sound from pc . Ready all the necessary flash in the qfil and as soon as u hear the device connected hit the download button .. it will flash without the sahara protocol error . Be quick ! tell me if that fixed ur problem . Peace
Click to expand...
Click to collapse
Thanks. Can you share the files you used please? I can't for the life of me, find the correct download files. There was a Nexus6P_Unbrick by TenFar but all the links are down.

DarthVader said:
Thanks. Can you share the files you used please? I can't for the life of me, find the correct download files. There was a Nexus6P_Unbrick by TenFar but all the links are down.
Click to expand...
Click to collapse
I used another qfil firmware
https://drive.google.com/file/d/1PixuumVVzxBKUsQ88X3AJ21Hsi2mV3Zq/view
Here is the link .. you can find the firehose and all files in the firmare folder . Best of Luck

I have a similar situation where I am unable to power on the phone in any way, and I am only able to communicate with the qualcom USB 9008 driver.
I am following your instructions using the firmware files you provided (thank you!) and I can see an attempt is being made to download the files before sahara error occurs.
I don't think I enabled developer options when my Nexus 6P was working and wondered if sahara error is due to that.
I was wondering if you had previously enabled developer options by tapping on the build number several times, once the operating system booted and if that is a critical step in being able to recover the Nexus 6p from this hard bricked state where I am stuck in EDL 9008 mode, and unable to access bootloader, and volume+power keys do not do anything...I feel like I'm screwed (and already moved on) but using time these days to learn about android devices!
thanks!

Onn Surf 8 Pro (100003561) Bricked

Is there anyway to unbrick my onn surf 8? It shows the boot logo then turns off. I tried fastboot and SP Flash tool. Nothing works please help. Please provide me a rom supported with the model number 100003561

joshilita said:
Is there anyway to unbrick my onn surf 8? It shows the boot logo then turns off. I tried fastboot and SP Flash tool. Nothing works please help. Please provide me a rom supported with the model number 100003561
Click to expand...
Click to collapse
Deadman posted a few images for that device:
https://forum.xda-developers.com/showthread.php?p=82619259#post82619259
Given what you describe, it sounds like your battery may be almost dead. You may still be able to get away with that in sp tools but it would be better if you could make sure you have at least a %30 charge. SP tools takes some getting used to, if you need help let me know. I'll try to keep an eye open for updates on this thread.

will160628 said:
Deadman posted a few images for that device:
https://forum.xda-developers.com/showthread.php?p=82619259#post82619259
Given what you describe, it sounds like your battery may be almost dead. You may still be able to get away with that in sp tools but it would be better if you could make sure you have at least a %30 charge. SP tools takes some getting used to, if you need help let me know. I'll try to keep an eye open for updates on this thread.
Click to expand...
Click to collapse
I don't think it works. I charged my tablet all night and i tried to use the SP flash tool again. I used the firmware started the download before connecting USB. I hear the tablet disconnecting and reconnecting constantly and SP flash tool doesnt find the device because the constant reconnecting.

I got somewhere with the fastboot. It showes the Orange State warning. It never showed that before. But it reboots back to the loading after 5 seconds I cant make it stop.

fixed
Okay, update. I dont know what I did but i think i unbricked the tablet. Is there any TWRP file for 100003561?

Major help needed

OP 8 Pro (Global-US) is horribly MUCKED UP!
I am in need of some high-level assistance, hoping someone here is able to help me.
Here’s what I know: My phone got messed up when I was attempting to install Magisk to android 12 C33. (Not really sure why) I tried you using various tools and methods to fix it. Each time I hit one roadblock or another. Biggest issue was I was never able to boot to EDL mode.
At this stage, no matter what key combo I use, the phone only boots to fastboot mode. Selecting any of the other options has no effect, it simply boots back to fastboot. At the time, that this happened, the bootloader was unlocked and developer options with USB debugging WAS active.
I have tried multiple times to install OnePlus_8_Pro_Global_OxygenOS_11.0.4.4.zip via fastboot, but it always fails with several 'Flashing is not allowed for Critical Partitions” and partition not found, etc
At this stage, I don’t know what to do. I am hoping one of you can help me restore my phone back to factory.
PS - would OnePlus reset/restore it for a fee?

SteveHebe said:
OP 8 Pro (Global-US) is horribly MUCKED UP!
I am in need of some high-level assistance, hoping someone here is able to help me.
Here’s what I know: My phone got messed up when I was attempting to install Magisk to android 12 C33. (Not really sure why) I tried you using various tools and methods to fix it. Each time I hit one roadblock or another. Biggest issue was I was never able to boot to EDL mode.
At this stage, no matter what key combo I use, the phone only boots to fastboot mode. Selecting any of the other options has no effect, it simply boots back to fastboot. At the time, that this happened, the bootloader was unlocked and developer options with USB debugging WAS active.
I have tried multiple times to install OnePlus_8_Pro_Global_OxygenOS_11.0.4.4.zip via fastboot, but it always fails with several 'Flashing is not allowed for Critical Partitions” and partition not found, etc
At this stage, I don’t know what to do. I am hoping one of you can help me restore my phone back to factory.
PS - would OnePlus reset/restore it for a fee?
Click to expand...
Click to collapse
Try firing up MSM and click the start button before connecting your phone. You should have at least 1 COM port listed with a N/A status. Now plug your phone in to the computer and let it boot to fastboot. Now hold down VUP,VDO & Power all at the same time until MSM starts the install. You should be good to go, if you get a good MSM install.

I tried what you suggested with no success. I am using the instantnoodlep_15_O.34_210201 MSM. Any thoughts?

HolyHog said:
Try firing up MSM and click the start button before connecting your phone. You should have at least 1 COM port listed with a N/A status. Now plug your phone in to the computer and let it boot to fastboot. Now hold down VUP,VDO & Power all at the same time until MSM starts the install. You should be good to go, if you get a good MSM install.
Click to expand...
Click to collapse
I tried what you suggested with no success. I am using the instantnoodlep_15_O.34_210201 MSM. Any thoughts?

SteveHebe said:
I tried what you suggested with no success. I am using the instantnoodlep_15_O.34_210201 MSM. Any thoughts?
Click to expand...
Click to collapse
DId you install all the drivers correctly? DId you try another cable? Did you try another usb port?
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com

xtcislove said:
DId you install all the drivers correctly? DId you try another cable? Did you try another usb port?
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Click to expand...
Click to collapse
I have current drivers, tried different machines, different ports and different cables.

SteveHebe said:
I have current drivers, tried different machines, different ports and different cables.
Click to expand...
Click to collapse
Is your phone regognized in device manager?

No, it is not

SteveHebe said:
No, it is not
Click to expand...
Click to collapse
Your phone boots ot fastboot and your pc does not regonize it? You need to make sure to install the drivers correctly imo.
Please read this sections carefully https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4084953/