Database Users

OP2 Bricked

A few days ago I was running xodus rom and the battery was at about 50% and the phone instantly shut off and I have not been able to get it back on since. I have tried the method of letting it sit for 12 hours and then charging for 6 but that didnt work. I have been trying the unbrick methods on the forums here but I cant get any of those to work. The problem is when I get to the step where I run the recovery tool and press start, nothing happens. I am running it as admin. Ive tried different ports on the computer and even running a vm of a different version of windows but nothing. Any help with this would be much apreciated. I can even teamviewer with someone if theyre willing to take a look at what I mean.
Edit: I am getting this on the recovery tool:
dynamic_nvbk.bin: OK
emmc_appsboot.mbn: OK
gpt_backup0.bin: OK
gpt_main0.bin: OK
userdata.img: FAILED open or read
userdata_64G.img: FAILED open or read
rawprogram0.xml: FAILED
rawprogram0_64G.xml: FAILED
NON-HLOS.bin: OK
rpm.mbn: OK
sbl1.mbn: OK
sdi.mbn: OK
static_nvbk.bin: OK
tz.mbn: OK
boot.img: FAILED open or read
cache.img: FAILED open or read
persist.img: OK
recovery.img: FAILED
system.img: FAILED open or read

ONEPLUS 2 bricked
i am also facing same issue .
stevecaboose said:
A few days ago I was running xodus rom and the battery was at about 50% and the phone instantly shut off and I have not been able to get it back on since. I have tried the method of letting it sit for 12 hours and then charging for 6 but that didnt work. I have been trying the unbrick methods on the forums here but I cant get any of those to work. The problem is when I get to the step where I run the recovery tool and press start, nothing happens. I am running it as admin. Ive tried different ports on the computer and even running a vm of a different version of windows but nothing. Any help with this would be much apreciated. I can even teamviewer with someone if theyre willing to take a look at what I mean.
Edit: I am getting this on the recovery tool:
dynamic_nvbk.bin: OK
emmc_appsboot.mbn: OK
gpt_backup0.bin: OK
gpt_main0.bin: OK
userdata.img: FAILED open or read
userdata_64G.img: FAILED open or read
rawprogram0.xml: FAILED
rawprogram0_64G.xml: FAILED
NON-HLOS.bin: OK
rpm.mbn: OK
sbl1.mbn: OK
sdi.mbn: OK
static_nvbk.bin: OK
tz.mbn: OK
boot.img: FAILED open or read
cache.img: FAILED open or read
persist.img: OK
recovery.img: FAILED
system.img: FAILED open or read
Click to expand...
Click to collapse

Are u referring to the qualcomm recovery tool? I semi bricked mine yesterday and took me a while to figure out how to get into that mode. I even tried on 3 different PCs to get the drivers working as i got it messed with ADB then OnePlus drivers. Into consideration too that 1 of the machine was in windows7, two on 8.1 so need to go to the driver signature disable thingy. Lucky me, i have my screen on as i still have like 70% battery in it. not sure bout yours.
If youre able to charge and boot it to at least fastboot or get the LED blinking to show it has battery to boot, next step is just to play around and get the qualcomm recovery mode working well. Dont give up man. you can do it.

http://forum.xda-developers.com/showpost.php?p=62440352&postcount=21
try this. This is slightly modified version. This worked for me after trying it for three times.
(Also flash H2OS, because O2OS doesn't install when you get up to recovery.)

Turns out that my phone shut off and was not able to recover with the qualcomm tool because of hardware damage.

LG L Fino (D295 no download )

Good day all,
I've had my LG for a year almost working perfectly on stock OS. suddenly one morning it was battery drained and ever since wouldn't start up.
my LG boots and gets stuck on
ERROR : boot certification verify
[1040] ---------------------------------------
[1050]
[1050] secure booting Error!
[1050] cause : boot certification verify
[1050]
[1050]----------------------------------------
then it turns off alone...
i have tried getting it into download mode it gives me same error, have also tried a full hard reset(vol- power lg logo vol- power) it goes and starts with the android robot and loading then just goes off.
However i download the LG drivers and after i try turning on the phone normally it goes off all i did was keep holding the volume up button then plugged into PC(win7) i get a removable disk of 63.9mb with two folders init(image and verinfo), in device manager it is COM15 LGE AndroidNet USB Serial Port. please keep in mind the screen is blank off when all this shows on PC.
I'm basically out of options idk what to do, please help me i have searched all over the web and cant find anything valid .
Any help would be appreciated.

Anyone help me (
anhtuan1992s said:
Good day all,
I've had my LG for a year almost working perfectly on stock OS. suddenly one morning it was battery drained and ever since wouldn't start up.
my LG boots and gets stuck on
ERROR : boot certification verify
[1040] ---------------------------------------
[1050]
[1050] secure booting Error!
[1050] cause : boot certification verify
[1050]
[1050]----------------------------------------
then it turns off alone...
i have tried getting it into download mode it gives me same error, have also tried a full hard reset(vol- power lg logo vol- power) it goes and starts with the android robot and loading then just goes off.
However i download the LG drivers and after i try turning on the phone normally it goes off all i did was keep holding the volume up button then plugged into PC(win7) i get a removable disk of 63.9mb with two folders init(image and verinfo), in device manager it is COM15 LGE AndroidNet USB Serial Port. please keep in mind the screen is blank off when all this shows on PC.
I'm basically out of options idk what to do, please help me i have searched all over the web and cant find anything valid .
Any help would be appreciated.
Click to expand...
Click to collapse
Pls help me

Hi guy,
I had a similar problem on weekend. I tried lot of methods and I fixed my phone. I don't have download mode yet, but i did my phone boot to system properly.
I don't know exactly what I did, my on forums of LG G3 a man posted 2 lines of comand that you can write on ADB. I think that these commands fixed my problem. But I tried lot of methods, so i can't say with conviction.
I will look on my historic on browser and put here all links that I researched.

Ben Flanders said:
Hi guy,
I had a similar problem on weekend. I tried lot of methods and I fixed my phone. I don't have download mode yet, but i did my phone boot to system properly.
I don't know exactly what I did, my on forums of LG G3 a man posted 2 lines of comand that you can write on ADB. I think that these commands fixed my problem. But I tried lot of methods, so i can't say with conviction.
I will look on my historic on browser and put here all links that I researched.
Click to expand...
Click to collapse
would you like to send my the link (

Sorry for delay
http://forum.xda-developers.com/showthread.php?t=2451696&page=47

thks a lot

Ben Flanders said:
Sorry for delay
http://forum.xda-developers.com/showthread.php?t=2451696&page=47
Click to expand...
Click to collapse
hi man i have the same problem but i have D290N
My phone is connected to comuter and detecting as "qualcomm mmc storage usb device"
with 63,9mb storage
(like a friend that started this thread)
My problem is that when i type adb shell
in adb
it says "error: no devices/emulators found"
any ideas :crying:

atiPL said:
hi man i have the same problem but i have D290N
My phone is connected to comuter and detecting as "qualcomm mmc storage usb device"
with 63,9mb storage
(like a friend that started this thread)
My problem is that when i type adb shell
in adb
it says "error: no devices/emulators found"
any ideas :crying:
Click to expand...
Click to collapse
Hi guy, in my researches I saw a thread about a problem that when cellphone is connected in the computer, computer recognizes only as qualcomm.
I don't remember exactly how to fix it, but take a look in the forums, i'm sure that you'll find a solution
sorry for don't help you

Help!
phone (lg295) is not included.
connecting see it as qualcomm 9800.
It does not respond to anything. I tried to restore it from the next topic - but there is only a way for the 290 ....
what to do...?

Any help (

anhtuan1992s said:
Any help (
Click to expand...
Click to collapse
See what i wrote above. There is a thread about this issue.

[Hard Brick] Nexus 6P 7.1.2 Beta 2 [Solved]

Hey guys I just installed the full image of 7.1.2 beta 2 over top of beta 1 using Flashfire without the bootloader and modem selected and all went fine until I decided to use Flashfire to upgrade the bootloader and modem forgetting that we must use Fastboot as I am new to Flashfire and I was reading all through the beta thread before I did it and didn't understand we still must use Fastboot so anyways I am stuck in a hard brick now with the phone not powering on at all and can't do anything to restore it as my Windows 10 now detects the phone as unknown device (device descriptor request failed) is there anything I can do at this point as I just bought this phone used.
The error that I got in Flashfire was that the device storage is full when updating the bootloader as the modem went fine.

@rmorris003
You said the phone won't even power on. You mean no Google? Hold the power button down for a couple of minutes and see if it will reboot. If not put it on a charger, and after fully charging try the long press power button again. If you can get it to start, try to put it in fastboot mode. (ie. power+vol dn). If you can get to bootloader you can send fastboot commands and fix it. If you can get to this point, there are instructions here.

rmorris003 said:
Hey guys I just installed the full image of 7.1.2 beta 2 over top of beta 1 using Flashfire without the bootloader and modem selected and all went fine until I decided to use Flashfire to upgrade the bootloader and modem forgetting that we must use Fastboot as I am new to Flashfire and I was reading all through the beta thread before I did it and didn't understand we still must use Fastboot so anyways I am stuck in a hard brick now with the phone not powering on at all and can't do anything to restore it as my Windows 10 now detects the phone as unknown device (device descriptor request failed) is there anything I can do at this point as I just bought this phone used.
The error that I got in Flashfire was that the device storage is full when updating the bootloader as the modem went fine.
Click to expand...
Click to collapse
Hello... Well if your device is recognized as unknown, you could try to give this a shot:
https://forum.xda-developers.com/nexus-6p/general/howtos-debrick-nexus-6p-stuck-edl-9008-t3552838
Try to install Qualcomm driver first check the device manager. If you see your phone recognized as:
HS-USB QDLOADER 9008
You may be lucky!
Good luck...

5.1 said:
Hello... Well if your device is recognized as unknown, you could try to give this a shot:
https://forum.xda-developers.com/nexus-6p/general/howtos-debrick-nexus-6p-stuck-edl-9008-t3552838
Try to install Qualcomm driver first check the device manager. If you see your phone recognized as:
HS-USB QDLOADER 9008
You may be lucky!
Good luck...
Click to expand...
Click to collapse
I will try this when I get back from work, I just cant get my pc to see it as anything other than unknown device as it says this is the best driver for it.

rmorris003 said:
I will try this when I get back from work, I just cant get my pc to see it as anything other than unknown device as it says this is the best driver for it.
Click to expand...
Click to collapse
I see... There's a txt file in the driver folder. Follow its instructions.
Good luck...

5.1 said:
I see... There's a txt file in the driver folder. Follow its instructions.
Good luck...
Click to expand...
Click to collapse
I am stumped, I have disabled driver enforcement and can't get any drivers to see my phone so I am not sure what to do.

rmorris003 said:
I am stumped, I have disabled driver enforcement and can't get any drivers to see my phone so I am not sure what to do.
Click to expand...
Click to collapse
You disabled driver signature and rebooted your computer? Then installed Qualcomm drivers from the thread I linked you to? I think you have to reboot your computer once more...
Good luck...

I held the power and vol down and now it shows up under com ports so this is a good sign.

Ok got bootloader back and now put twrp on, I had to use qfil with nexus6p_fix_bricked but it got stuck at writing system.img but atleast the phone is on now.
Flashed the 7.1.2 beta 2 full image using the fastboot method included and all is back to normal.
Thanks so much for the help.

rmorris003 said:
Ok got bootloader back and now put twrp on, I had to use qfil with nexus6p_fix_bricked but it got stuck at writing system.img but atleast the phone is on now.
Flashed the 7.1.2 beta 2 full image using the fastboot method included and all is back to normal.
Thanks so much for the help.
Click to expand...
Click to collapse
Wow glad it worked for you... You might push the thanks button in the OP of the thread where you found the debrick tools and thanks @tenfar since he offered the solution. He already saved a few N6P devices. I only linked you to his thread which you could have found yourself anyway...
Cheers...

5.1 said:
Wow glad it worked for you... You might push the thanks button in the OP of the thread where you found the debrick tools and thanks @tenfar since he offered the solution. He already saved a few N6P devices. I only linked you to his thread which you could have found yourself anyway...
Cheers...
Click to expand...
Click to collapse
I'm pretty sure I was reading it before but I had to do some extensive reading on how to get the driver to read properly. I work night shift so I was kinda tired yesterday.

rmorris003 said:
I'm pretty sure I was reading it before but I had to do some extensive reading on how to get the driver to read properly. I work night shift so I was kinda tired yesterday.
Click to expand...
Click to collapse
You could report your experience in the other thread. Maybe it could help other users who faced the issue you had. :good:
Cheers...

rmorris003 said:
I'm pretty sure I was reading it before but I had to do some extensive reading on how to get the driver to read properly. I work night shift so I was kinda tired yesterday.
Click to expand...
Click to collapse
Hi there, I'm extremely new to Forums and the whole android scene please could you help?
I have the same issue with my Nexus 6P Hard bricked, only detected as a 9008 Port, no vibrations no power nothing!
I've tried to follow so many guides for the past three days however I've managed nothing. I've tried to do as you mentioned in the first posts, used the nexus6p_unbrick in Qfil but Sahara download fails.
Please Please Help, No Warranty just a Brick!

Clarkeofcurtis said:
Hi there, I'm extremely new to Forums and the whole android scene please could you help?
I have the same issue with my Nexus 6P Hard bricked, only detected as a 9008 Port, no vibrations no power nothing!
I've tried to follow so many guides for the past three days however I've managed nothing. I've tried to do as you mentioned in the first posts, used the nexus6p_unbrick in Qfil but Sahara download fails.
Please Please Help, No Warranty just a Brick!
Click to expand...
Click to collapse
I have the same exact problem, everytime i try to flash with qfil it says it can't connect to my COMPORT

Clarkeofcurtis said:
Hi there, I'm extremely new to Forums and the whole android scene please could you help?
I have the same issue with my Nexus 6P Hard bricked, only detected as a 9008 Port, no vibrations no power nothing!
I've tried to follow so many guides for the past three days however I've managed nothing. I've tried to do as you mentioned in the first posts, used the nexus6p_unbrick in Qfil but Sahara download fails.
Please Please Help, No Warranty just a Brick!
Click to expand...
Click to collapse
Falitheman said:
I have the same exact problem, everytime i try to flash with qfil it says it can't connect to my COMPORT
Click to expand...
Click to collapse
Hello,
Someone mentioned this in another post:
Hold volume up and plug the USB cord to.your computer and start qfil flash. Keep holding volume up until the flash ends...
Good luck...

5.1 said:
Hello,
Someone mentioned this in another post:
Hold volume up and plug the USB cord to.your computer and start qfil flash. Keep holding volume up until the flash ends...
Good luck...
Click to expand...
Click to collapse
So i have some good news...it connects now. it says start sending programmer but then it says download failed: unable to download flash programmer using sahara protocol and then it fails. Any help?:crying:

Falitheman said:
So i have some good news...it connects now. it says start sending programmer but then it says download failed: unable to download flash programmer using sahara protocol and then it fails. Any help?:crying:
Click to expand...
Click to collapse
Hey,
What version of qpst did you install?
Good luck...

5.1 said:
Hey,
What version of qpst did you install?
Good luck...
Click to expand...
Click to collapse
I am using 2.7.441
Update: It seemed to be working for a second but then it says download failed: qsahara server fail: process fail. Any idea what that means? I really need my phone back

Falitheman said:
I am using 2.7.441
Update: It seemed to be working for a second but then it says download failed: qsahara server fail: process fail. Any idea what that means? I really need my phone back
Click to expand...
Click to collapse
Hey,
Google qpst 2.7.453
It's easy to find. Scan the files on virustotal.com though.
Maybe the older versions are incompatible...
Good luck...

5.1 said:
Hey,
Google qpst 2.7.453
It's easy to find. Scan the files on virustotal.com though.
Maybe the older versions are incompatible...
Good luck...
Click to expand...
Click to collapse
I tried with the version you suggested and i got the same error i just had. Can you send me your version so i can see if that works?

P9 Lite Fully Bricked ! HELP PLEASE !

Hello guys , i have a very very big problem here .
So lets start from the beggining :
- i was going to flash RR v5.8.2 through twrp 3.0.2-0 , i backed up boot and data from my stock , and then flashed .
- everything was ok , phone booted into RR , i was customising my android for 1 hour and then decided to restore that backup i made .
- i booted into recovery , restored the backup , and BOOOOM THE PHONE GOT BOOTLOOP
From here i tried dload method .
- put c900b300 or whatever .. UPDATE.APP file on my dload folder from sd card ( with my old phone )
- boot into 3 buttons method .
- flashed , and THEN AGAIN BOOTLOOP , BUT THIS TIME IN "your device has been unlocked and can't be trusted."
I have unlocked bootloader , frp unlocked ... no usb debugging enabled .
And can't get to erecovery , can't get to 3 buttons method . Its just stuck on "Your device is booting now..."
Please help me guys , i have this phone for 5 days only and I already broke it...

This what happens when you don't follow the instructions.
Buy a new motherboard.

Johnny TDN said:
This what happens when you don't follow the instructions.
Buy a new motherboard.
Click to expand...
Click to collapse
Sorry but that's bull****!
No need to buy a new mobo. Just use one of the many downgrade guides and be on your merry way.
A full,. hard brick is pretty hard to get. You'll be ok, OP.

Johnny TDN said:
This what happens when you don't follow the instructions.
Buy a new motherboard.
Click to expand...
Click to collapse
I solved it .

hexxr said:
I solved it .
Click to expand...
Click to collapse
Since you aren't writing HOW you solved it, i will leave here my solution for other ppl
had this problem yesterday & solved it by myself.
u will need fastboot for this
1. Boot phone into fastboot (shut down completely, plug phone in to your pc while you're holding down the "VOL -" Button
2. now download this TWRP Recovery (https://forum.xda-developers.com/huawei-p9lite/development/recovery-twrp-huawei-p9-lite-t3491847)
3. put the img file in the same folder as the "fastboot.exe"
4 go to the folder where your files are. hold shift and do a right click into your folder. Choose "Open Command Prompt here"
5. type in "fastboot devices" -- if your device is showing up then you can continue
6. type in "fastboot flash recovery FILENAME.img" (Change filename to the name of the recovery image)
7 If everything worked, shut down your phone.
8. Hold "Vol +" and the power button
The "untrusted device" screen will come. just pass it.
If everything worked and you're in the recovery then you can install every rom zip you want till ur phone works again
If something doesn't work or something is not clear then don't be afraid to ask
.... i hope i wrote everything right xD

zgomot said:
Sorry but that's bull****!
No need to buy a new mobo. Just use one of the many downgrade guides and be on your merry way.
A full,. hard brick is pretty hard to get. You'll be ok, OP.
Click to expand...
Click to collapse
if he couldn';t even boot in fastboot,,,then a new motherboard was required.

Johnny TDN said:
if he couldn';t even boot in fastboot,,,then a new motherboard was required.
Click to expand...
Click to collapse
You see, he eventually managed to boot into fastboot, so your rash comment about getting a new motherboard was, well... kind of rash.

zgomot said:
You see, he eventually managed to boot into fastboot, so your rash comment about getting a new motherboard was, well... kind of rash.
Click to expand...
Click to collapse
most of the times, Fastboot may save you or not (50/50) when you have a hard brick

hexxr said:
I solved it .
Click to expand...
Click to collapse
HOW? there's plenty of people which hasn't been able to solve it... please share...

islandman75 said:
HOW? there's plenty of people which hasn't been able to solve it... please share...
Click to expand...
Click to collapse
I can't remeber , now I have iPhone 5S , so yea..

kennyweed said:
Since you aren't writing HOW you solved it, i will leave here my solution for other ppl
had this problem yesterday & solved it by myself.
u will need fastboot for this
1. Boot phone into fastboot (shut down completely, plug phone in to your pc while you're holding down the "VOL -" Button
2. now download this TWRP Recovery (https://forum.xda-developers.com/huawei-p9lite/development/recovery-twrp-huawei-p9-lite-t3491847)
3. put the img file in the same folder as the "fastboot.exe"
4 go to the folder where your files are. hold shift and do a right click into your folder. Choose "Open Command Prompt here"
5. type in "fastboot devices" -- if your device is showing up then you can continue
6. type in "fastboot flash recovery FILENAME.img" (Change filename to the name of the recovery image)
7 If everything worked, shut down your phone.
8. Hold "Vol +" and the power button
The "untrusted device" screen will come. just pass it.
If everything worked and you're in the recovery then you can install every rom zip you want till ur phone works again
If something doesn't work or something is not clear then don't be afraid to ask
.... i hope i wrote everything right xD
Click to expand...
Click to collapse
I bricked my phone when trying to downgrade from 7.0. I have bootloader unlocked and can get into fastboot screen but when I flash the recovery i get "FAILED (remote: Command not allowed)".
They say that P9 Lite drivers should be installed (usually installs when Hisuite detects the phone). Unfortunately, I'm using a new PC. Or correct me if I'm wrong.
---------- Post added at 07:24 AM ---------- Previous post was at 06:47 AM ----------
Ok just figured it out thanks to this post: https://forum.xda-developers.com/huawei-p9lite/help/flash-recovery-failed-remote-command-t3555563
it looks like a bug that says bootloader is unlocked even if it isn't. So just perform another bootloader unlock and go back to fastboot screen. You should be able to flash images now.

I have the same problem:
"FAILED (remote: Command not allowed)"
Any solution for this problem? I Cant boot into OS (boot loop). Fastboot and recovery are possible.
bonnerable said:
I bricked my phone when trying to downgrade from 7.0. I have bootloader unlocked and can get into fastboot screen but when I flash the recovery i get "FAILED (remote: Command not allowed)".
They say that P9 Lite drivers should be installed (usually installs when Hisuite detects the phone). Unfortunately, I'm using a new PC. Or correct me if I'm wrong.
---------- Post added at 07:24 AM ---------- Previous post was at 06:47 AM ----------
Ok just figured it out thanks to this post: https://forum.xda-developers.com/huawei-p9lite/help/flash-recovery-failed-remote-command-t3555563
it looks like a bug that says bootloader is unlocked even if it isn't. So just perform another bootloader unlock and go back to fastboot screen. You should be able to flash images now.
Click to expand...
Click to collapse

Nokia 5 Stuck in bootloop and failed to find device for partition system

please, my nokia 5 TA 1024 got stuck in a bootloop after a system update. i tried resetting from the recovery mode, but it keeps saying "failed to find device for partition system". i tried flashing with a rom i found online but an error keeps poping up at a point in the flashing process.(i used OST for flashing). i looked into that and i found out that i have to unlock the bootloader. but since the phone cant actually boot, i dont know how to unlock it. please help.:crying:

havardgyasi said:
please, my nokia 5 TA 1024 got stuck in a bootloop after a system update. i tried resetting from the recovery mode, but it keeps saying "failed to find device for partition system". i tried flashing with a rom i found online but an error keeps poping up at a point in the flashing process.(i used OST for flashing). i looked into that and i found out that i have to unlock the bootloader. but since the phone cant actually boot, i dont know how to unlock it. please help.:crying:
Click to expand...
Click to collapse
Got the same problem months ago by an upgrade from oreo to pie. Nothing worked except "fastboot reboot bootloader" from terminal followed by pluged in the phone.
It was not possible for me to do more things. Could not solve the problem until I get an EDL-cable. Then found out that the upgrade had damaged the bootloader. Could then flash it with the latest OST, the EDL-cable and the 7.1 Rom.

Spartan42 said:
Got the same problem months ago by an upgrade from oreo to pie. Nothing worked except "fastboot reboot bootloader" from terminal followed by pluged in the phone.
It was not possible for me to do more things. Could not solve the problem until I get an EDL-cable. Then found out that the upgrade had damaged the bootloader. Could then flash it with the latest OST, the EDL-cable and the 7.1 Rom.
Click to expand...
Click to collapse
ohk. i managed to get the cable. can you please walk me through the process of getting into EDL mode?

havardgyasi said:
ohk. i managed to get the cable. can you please walk me through the process of getting into EDL mode?
Click to expand...
Click to collapse
There are a bunch of instructions how to use the Cable in the right order.
It is important that the driver in Windows is the right one. Most of the time (in mine device) the EDL-mode was detected incorrectly and the driver has to be changed manually.
It's been a while, so I do not remember all the steps. I'm sorry. I've searched the Nokia 5 and 6 Forums. That should answer most of the questions. The rest was try and error.
Good Luck
---------- Post added at 01:37 AM ---------- Previous post was at 01:33 AM ----------
https://forum.xda-developers.com/no...p-unbricking-ny-nokia-6-t3947148/post79889899
https://forum.xda-developers.com/no...p-unbricking-ny-nokia-6-t3947148/post79889899
Try this one for the drivers.