[Q] Really Bricked? - Oppo Find 5

I had an Asylum Custom Rom installed.
I also had TWRP as the recovery installed.
I decided to try the new COLOR ROM public beta that I got from the OPPO forums.
I went into TWRP recovery, did a full wipe and then proceeded to install the new COLOR ROM.
When I rebooted, the phone never turned on again.
Now I cannot get to fastboot, recovery, or turn on the phone at all.
I browsed through many forums and tried
1. Charging phone for 5 hours (no led light when plugged in) -> nothing
2. Holding Power button for 30 secs, (5 times to try a hard reset) -> nothing
3. Holding Down button for 10 secs -> nothing
4. Power and up volume -> nothing
5. Power and down volume -> nothing
6. Plugged into computer USB and tried all button combos -> nothing
Is my phone really bricked now?

I hope for your sake it really isn't the case. It does seem like you have tried all the usual ways of getting around the symptoms you are describing. It sounds like you had a bad download and flashed it anyway. I hope someone has some advice for you to fix your device. I am currently on Asylum and was just considering trying out the new Color ROM so i think i'll hold off until i know for sure you can resurrect your device.
when you are hooked up to USB on PC can you try ADB? does it even see the device at all?

killerskincanoe said:
I hope for your sake it really isn't the case. It does seem like you have tried all the usual ways of getting around the symptoms you are describing. It sounds like you had a bad download and flashed it anyway. I hope someone has some advice for you to fix your device. I am currently on Asylum and was just considering trying out the new Color ROM so i think i'll hold off until i know for sure you can resurrect your device.
when you are hooked up to USB on PC can you try ADB? does it even see the device at all?
Click to expand...
Click to collapse
Nothing. no response whatsoever. I've worked with many different phones before starting with the Nexus One and I've always been able to get out of a potentially bad situation because I could at least always get to fastboot or recovery, but in this case, nothing. It really is like working with a brick, hence the term "brick". Now i can really understand the meaning of the term.

such a bummer. it certainly makes me think twice about trying other ROMS now jeez

update
Just an update to this thread... I sent my Find 5 to get repaired to try and figure out what the problem was. It turned out that the battery had failed and they replaced the battery for me. Glad to say that my Find 5 is up and running again.

dtwrain said:
Just an update to this thread... I sent my Find 5 to get repaired to try and figure out what the problem was. It turned out that the battery had failed and they replaced the battery for me. Glad to say that my Find 5 is up and running again.
Click to expand...
Click to collapse
good to hear !!
I couldnt really believe that flashing a rom using recovery affects fastboot let alone button combos/charging...
btw what were the costs of replacing the battery ? or was it free of charge under warranty...

dtwrain said:
Just an update to this thread... I sent my Find 5 to get repaired to try and figure out what the problem was. It turned out that the battery had failed and they replaced the battery for me. Glad to say that my Find 5 is up and running again.
Click to expand...
Click to collapse
Glad to hear it turned out that way. Really strange situation.

Oualcomm HS-USB Diagnostics 9008
1) Can you give me some advices? Smartphone OPPO find 5 x909 is in the Oualcomm HS-USB Diagnostics 9008 port. Completely brick. What we gonna do with it ? Where i may download unbrick files and will see unbrick method? Need just rowprogram0.xml, patch0.xml, 8064_msimage.mbn, MPRG8064.hex for OPPO find5 x909 strongly.
2) How i can place other (working) smartphone in Download mode? What i gonna press?
Sorry for my english, and thank you.

olezhek1975 said:
1) Can you give me some advices? Smartphone OPPO find 5 x909 is in the Oualcomm HS-USB Diagnostics 9008 port. Completely brick. What we gonna do with it ? Where i may download unbrick files and will see unbrick method? Need just rowprogram0.xml, patch0.xml, 8064_msimage.mbn, MPRG8064.hex for OPPO find5 x909 strongly.
2) How i can place other (working) smartphone in Download mode? What i gonna press?
Sorry for my english, and thank you.
Click to expand...
Click to collapse
I suggest you to ask addel in oppo forum, she can help you just pm her and tell your problem, because she has an app like odin in samsung to totally flash new rom inage from pc like odin did. But its not officially released by oppo and its hard to find, so i suggest you to contact her
Sent from my GT-I9205 using XDA Free mobile app

Related

milestone 2 a953 DEAD after DOWNGRADE

Hello, i have a big problem with my motorola milestone 2 A953, I apologize for my english
pleased help me my milestone 2 a953 completely dead after trying to downgrade it with rsd lite from 2.3.6 to 2.2.1
pleeeeeeeeeased help
jakkokko said:
Hello, i have a big problem with my motorola milestone 2 A953, I apologize for my english
pleased help me my milestone 2 a953 completely dead after trying to downgrade it with rsd lite from 2.3.6 to 2.2.1
pleeeeeeeeeased help
Click to expand...
Click to collapse
You can't downgrade, search for the SBF here: http://and-developers.com/sbf:milestone2 and download it from here: http://sbf.droid-developers.org/umts_milestone2/list.php
Then, read this: http://forum.xda-developers.com/showthread.php?t=1497263
lean946 said:
you can't downgrade, search for the sbf here: http://and-developers.com/sbf:milestone2 and download it from here: http://sbf.droid-developers.org/umts_milestone2/list.php
then, read this: http://forum.xda-developers.com/showthread.php?t=1497263
Click to expand...
Click to collapse
i know that i did a big mistake there is any solution pleased
jakkokko said:
i know that i did a big mistake there is any solution pleased
Click to expand...
Click to collapse
Search for the rom you had before on the link I gave you (2.3.6 retail brazil, retail latam, personal argentina, vivo brazil, etc), copy the MD5, and search it on the other site to download it.
Then flash it with RSD.
Lean946 said:
Search for the rom you had before on the link I gave you (2.3.6 retail brazil, retail latam, personal argentina, vivo brazil, etc), copy the MD5, and search it on the other site to download it.
Then flash it with RSD.
Click to expand...
Click to collapse
sorry but i sad that i can no more get my milstone boot to flash it with rsd or with memory card i sad it is completely dad and i have exactly the rom witch i was in it and the other one witch i flash the phone with it then it become dead
pleased try to understand me an my problem and help that i think my phone need a jtag to be flashed and unbricked
Did you follow this procedure to put it in bootloader mode? http://forum.xda-developers.com/showthread.php?t=1032372
If your battery is discharged, try this: http://forum.xda-developers.com/showthread.php?p=10163846
If everything else fails, take it to Moto.
Good Luck
Lean946 said:
Did you follow this procedure to put it in bootloader mode? http://forum.xda-developers.com/showthread.php?t=1032372
If your battery is discharged, try this: http://forum.xda-developers.com/showthread.php?p=10163846
If everything else fails, take it to Moto.
Good Luck
Click to expand...
Click to collapse
first of all thank you very much for quick replay
the phone is no more able to be putted in bootloader mode
the battry is ok then the led of charg light on when lug it to usb
then there is no possibility to take it to moto for me
so there is an other method to force it (my phone) to get bootloader mode by hardware like gtag in samsung
If your phone shows a black screen right after turning it on, then it means you're on bootloader mode...
Next time pay more attention to the warnings...
Sent from my A953 using xda app-developers app
jakkokko said:
first of all thank you very much for quick replay
the phone is no more able to be putted in bootloader mode
the battry is ok then the led of charg light on when lug it to usb
then there is no possibility to take it to moto for me
so there is an other method to force it (my phone) to get bootloader mode by hardware like gtag in samsung
Click to expand...
Click to collapse
Try entering bootloader mode (vol up + camera + power). Even though the screen will stay black (but with backlight turned on), the phone will be in bootloader mode. You can see it by connecting USB cable - the white charging led will light up. At this stage you can simply start flashing latest stock gingerbread firmware via RSD lite. After several minutes the phone screen will display some info about flashing and you just have to wait a little bit longer.
You might be at a bit bigger trouble if your battery is empty. If so, you can try to recharge it with +5V current i.e. from USB port as described in this forum. Or you can find somebody with MS2, just to recharge the battery.
I also simply downgraded my MS2 to Froyo, and had problems like you. I was scared I bricked my phone, but luckily it's not so easy to be damaged!
rabinhood said:
Try entering bootloader mode (vol up + camera + power). Even though the screen will stay black (but with backlight turned on), the phone will be in bootloader mode. You can see it by connecting USB cable - the white charging led will light up. At this stage you can simply start flashing latest stock gingerbread firmware via RSD lite. After several minutes the phone screen will display some info about flashing and you just have to wait a little bit longer.
You might be at a bit bigger trouble if your battery is empty. If so, you can try to recharge it with +5V current i.e. from USB port as described in this forum. Or you can find somebody with MS2, just to recharge the battery.
I also simply downgraded my MS2 to Froyo, and had problems like you. I was scared I bricked my phone, but luckily it's not so easy to be damaged!
Click to expand...
Click to collapse
thank you for understanding my problem
i fully charge my battery with external charger then i clean it very well to be sure from the connection then i try to put the phone into bootloader mod ( volume up + camera+ power) screen still black then i plug the phone to pc the white charging led light up but the pc and RSD lite don't detect any think it is really confusing cause when i plug the phone without pressing (vol up + camera + power) the white charging dont led light up
but when i do it lghit up but nothing detected
any solution for that pleased
thank you every body i finally resolve the problem by downing this http://forum.xda-developers.com/showthread.php?p=10163846
then put the phone in bootloader mod with black screen and the RSD Lite detect it and i flash it with the good sbf and every think is ok
jakkokko said:
thank you for understanding my problem
i fully charge my battery with external charger then i clean it very well to be sure from the connection then i try to put the phone into bootloader mod ( volume up + camera+ power) screen still black then i plug the phone to pc the white charging led light up but the pc and RSD lite don't detect any think it is really confusing cause when i plug the phone without pressing (vol up + camera + power) the white charging dont led light up
but when i do it lghit up but nothing detected
any solution for that pleased
Click to expand...
Click to collapse
I'm having the exact same problem, and if someone know how to fix this I would be very grateful.
But before I log out I have a question about this? If the phone's ROM was bricked, what procedure Motorola should take to resolve the issue?
I heard that they make a direct installation on the ROM's cellphone, but just don't know how they do that. If someone knows how to, could tell us to reproduce the same strategy in our home's. I believe this knowledge could fix the problem we have.
:good:
Anyone?
alexpsad said:
I'm having the exact same problem, and if someone know how to fix this I would be very grateful.
But before I log out I have a question about this? If the phone's ROM was bricked, what procedure Motorola should take to resolve the issue?
I heard that they make a direct installation on the ROM's cellphone, but just don't know how they do that. If someone knows how to, could tell us to reproduce the same strategy in our home's. I believe this knowledge could fix the problem we have.
:good:
Anyone?
Click to expand...
Click to collapse
1. Install Moto's USB drivers.
2. Install RSD Lite
3. Download an SBF depending on the software you had before.
4. Reboot into downloader mode, and flash that.
If it still doesn´t work, google it. Use the defy forums, the MS2 has the exact same hardware.
If it STILL doesn't work, google again.
If it STILL WON'T WORK, google once again.
And if it still won't show signs of life, take it to moto's service center. Use your social skills and play dumb and maybe you get a cheap repair.
99% of problems happen when users don't read before flashing. It's explicitly written in huge bloody red letters to NOT downgrade from GB.
Lean946 said:
1. Install Moto's USB drivers.
2. Install RSD Lite
3. Download an SBF depending on the software you had before.
4. Reboot into downloader mode, and flash that.
If it still doesn´t work, google it. Use the defy forums, the MS2 has the exact same hardware.
If it STILL doesn't work, google again.
If it STILL WON'T WORK, google once again.
And if it still won't show signs of life, take it to moto's service center. Use your social skills and play dumb and maybe you get a cheap repair.
99% of problems happen when users don't read before flashing. It's explicitly written in huge bloody red letters to NOT downgrade from GB.
Click to expand...
Click to collapse
I've tried to flash the phone using sbf_flash at Linux. In older days I used RSD Lite and windows stuffs, now just Linux. But considering the behavior of the phone, it'll not meter what kind of tool I use, the problem will not be resolved. How you've said: "NOT downgrade from GB"
I've done this, and now the phone looks to be over! My mistake!! And now I would like to know if someone have the knowledge to bring the phone back from this situation, without physically change the ROM. What Motorola's service center people do to recover the phone in cases like that? If not involve hardware stuffs, just software, I believe it's possible to fix it for ourselves. And THAT was my question.
I know the things about downgrade, and the loss and bricks that this procedure could make, once I read it. I'm not worried about what was made, but about what could I do from now on, to repair the phone.
What was done there's no coming back!
But thanks anyway. If you know the "how to" to fix bricked phones, I'll be glad!
alexpsad said:
I've tried to flash the phone using sbf_flash at Linux. In older days I used RSD Lite and windows stuffs, now just Linux. But considering the behavior of the phone, it'll not meter what kind of tool I use, the problem will not be resolved. How you've said: "NOT downgrade from GB"
I've done this, and now the phone looks to be over! My mistake!! And now I would like to know if someone have the knowledge to bring the phone back from this situation, without physically change the ROM. What Motorola's service center people do to recover the phone in cases like that? If not involve hardware stuffs, just software, I believe it's possible to fix it for ourselves. And THAT was my question.
I know the things about downgrade, and the loss and bricks that this procedure could make, once I read it. I'm not worried about what was made, but about what could I do from now on, to repair the phone.
What was done there's no coming back!
But thanks anyway. If you know the "how to" to fix bricked phones, I'll be glad!
Click to expand...
Click to collapse
They use JTAGs, but even if you get your hands in a JTAG box, I don't think we have any way to flash anything with it.

[Q] Did I brick the Nexus 4?

Hey guys!
Yesterday I made a big mistake in the afternoon. I hate myself and don't know what to do now.
I was tired and without concentration so i flashed the nexus 7 franco kernel r38 on my nexus 4 :'(
Now my nexus 4 won't boot up. It's completely shutdown and without AC charging nothing happens.
With plugged in AC power supply module after pressing volume down and power on for 11 sec the red led lights up once for a short time.
If the nexus 4 is connected to the computer with usb the device manager shows me a unknown device 'QHSUSB_DLOAD'.
I have no possibility to go to fastboot mode or recovery. There is only a BlackScreen!
Is there a possibility to make my mistake undo?
If read a lot of threads for now and found solutions (UnBrickableResurrector) for the Galaxy Nexus S but there is nothing for the nexus 4.
Thank you for you help!
chris_te said:
Hey guys!
Yesterday I made a big mistake in the afternoon. I hate myself and don't know what to do now.
I was tired and without concentration so i flashed the nexus 7 franco kernel r38 on my nexus 4 :'(
Now my nexus 4 won't boot up. It's completely shutdown and without AC charging nothing happens.
With plugged in AC power supply module after pressing volume down and power on for 11 sec the red led lights up once for a short time.
If the nexus 4 is connected to the computer with usb the device manager shows me a unknown device 'QHSUSB_DLOAD'.
I have no possibility to go to fastboot mode or recovery. There is only a BlackScreen!
Is there a possibility to make my mistake undo?
If read a lot of threads for now and found solutions (UnBrickableResurrector) for the Galaxy Nexus S but there is nothing for the nexus 4.
Thank you for you help!
Click to expand...
Click to collapse
Can you boot into fastboot? recovery?
Edit: Sorry, saw that you wrote you can't...
I added the information afterwards. Sry
Basically, there are two ways to fix this:
1) I don't know how, but through QHSUSB_DLOAD you probably can flash something...
2) JTAG Repair.
1) Sounds interessting. I thought at something like this: UnBrickable Resurrector
But is there a chance to get this solution to our nexus 4?
2) Nexus 4 - JTAG Brick Repair Service is also interessting but i don't know how much time it take vom germany to usa to germany back.
I thought the nexus 4 is unbrickable
If you got it into Download mode, then you should be able to get into recovery. (Assuming you didn't do a bad flash of that)
Unplug it
Hold volume down and power
Plug it into WALL CHARGER (not a computer) while still holding the buttons
Someone also flashed a Nexus 7 kernel (also Franco) to his Nexus 4. Didn't look good because the Nexus 7 kernel overwrites a partition from the bootloader, if I remember correctly. Here is it explained better. The last post from the guy who flashed it didn't look too good also. Sorry to hear man.
Maybe you can RMA it. I don't recommend it because it's your own fault, but everyone makes a mistake sometime sooner or later.
I am another one who did the same mistake - accidently flashed the franco Nexus 7 Kernel. ::crying:
Even the Qualcomm flash tool which I tried couldn't get acces to the device. So I'm waiting for my replacement device now and hope LG can fix the problem.
chris_te said:
Hey guys!
Yesterday I made a big mistake in the afternoon. I hate myself and don't know what to do now.
I was tired and without concentration so i flashed the nexus 7 franco kernel r38 on my nexus 4 :'(
Now my nexus 4 won't boot up. It's completely shutdown and without AC charging nothing happens.
With plugged in AC power supply module after pressing volume down and power on for 11 sec the red led lights up once for a short time.
If the nexus 4 is connected to the computer with usb the device manager shows me a unknown device 'QHSUSB_DLOAD'.
I have no possibility to go to fastboot mode or recovery. There is only a BlackScreen!
Is there a possibility to make my mistake undo?
If read a lot of threads for now and found solutions (UnBrickableResurrector) for the Galaxy Nexus S but there is nothing for the nexus 4.
Thank you for you help!
Click to expand...
Click to collapse
Sorry to hear your bootloader has been obliterated. Try to RMA via Google or contact LG and find out how much they will charge to flash the device.
On a side note, I'm curious if you're able to put the phone in to download mode (not fasboot or recovery).
1. Make sure it is off
2. Hold volume up + volume down and plug in USB.
Even if you can get to download mode I don't think we have what we need to get the device working (LG drivers, KDZ image, etc) but this would indicate some promise for the future.
Until the Qualcomm USB Dowland mode is figured out, you're boned. Gonna have to send it away.
comminus said:
On a side note, I'm curious if you're able to put the phone in to download mode (not fasboot or recovery).
1. Make sure it is off
2. Hold volume up + volume down and plug in USB.
Click to expand...
Click to collapse
Hi,
I tried your suggestion and it did't work
The phone tried to boot into download mode but didn't get it. Screen was always black. After 10 second the phone vibrated and tried it once more.
Do you think the people of MobileTechVideos can help me?
I'm still waiting for a response from Josh.
Here is a link to a Nexus 4 - JTAG Brick Repair Service video: http://www.youtube.com/watch?v=gYtNWt1h66E
And if all this does not work, i have to send it to the google RMA.
If it were me, I'd pay LG to fix it. Either contact Google for RMA or contact LG and ask them what they would charge to flash the device.
Sent from my Nexus 4
chris_te said:
Hi,
I tried your suggestion and it did't work
The phone tried to boot into download mode but didn't get it. Screen was always black. After 10 second the phone vibrated and tried it once more.
Do you think the people of MobileTechVideos can help me?
I'm still waiting for a response from Josh.
Here is a link to a Nexus 4 - JTAG Brick Repair Service video: http://www.youtube.com/watch?v=gYtNWt1h66E
And if all this does not work, i have to send it to the google RMA.
Click to expand...
Click to collapse
Just press VOL - key and plug into USB connected to PC, ARE YOU IN FASTBOOT MODE ?!
IF YES, flash stock firmwares... and let the device rest for 15 min.
then plug into AC charger and let it charge for min. 1 hour...
If nothing happens, you possibly damaged your battery !
I had the same issue... I sent it for RMA.. Although by this method, many have recovered, if there is no battery issue as such !
Give it a try !
And dont use toolkit... Use FASTBOOT COMMANDS ! MANUALLY !
You have to reach fastboot mode:
1) Turn the phone off!! Not so easy (for me when never done before)!! Unplug it and try to press power, it often needs a little time/serveral tries.
When off :good:- very important:
2) Hold volume - and power simultaniosly - and plug it into WALL CHARGER (not a computer) while still holding the buttons.
3) Fastboot Mode!!!? --> :laugh:
4) Plug it to PC and flash stock rom
Good luck!
torsin said:
You have to reach fastboot mode:
1) Turn the phone off!! Not so easy (for me when never done before)!! Unplug it and try to press power, it often needs a little time/serveral tries.
When off :good:- very important:
2) Hold volume - and power simultaniosly - and plug it into WALL CHARGER (not a computer) while still holding the buttons.
3) Fastboot Mode!!!? --> :laugh:
4) Plug it to PC and flash stock rom
Good luck!
Click to expand...
Click to collapse
The people who said the bootloader was overwritten are most likely right. Its done. This phone has the same processor as the s3 and on the s3 QHSUSB_DLOAD is the kiss of death.
QHSUSB_DLOAD=Qualcomm High Speed USB Download
Its basically a piece of hardware waiting for firmware to be loaded at a factory level. You need JTAG
billard412 said:
The people who said the bootloader was overwritten are most likely right. Its done. This phone has the same processor as the s3
Click to expand...
Click to collapse
btw: s3 is arm not qualcomm, but not important here.
Was referring to the us variants that also use the qualcomm snapdragon s4 processor like the n4 does
Ah, okay - sorry I don´t know!
And for the record, Qualcomm chips are ARM cores.
Also for the record, my JTAG solution for this model will recover a device that is hardbricked via bad software flash. In this case you have flashed a Tegra kernel into the device and likely also into the incorrect partition as well. I have a complete backup of all necessary zones required for boot (sbl's, aboot, boot, rpm, tz and a few others). If you've damaged your Nexus 4's bootable zones and the device is hard bricked due to it, I can repair it for you.

Qualcomm hs-usb qdloader 9008 nexus 6P (HELP!)

Hi there, I've been browsing through the threads related to unbricking of the Nexus 6P stuck in qualcomm hs-usb qdloader 9008 mode, really desperate to get my device working again if even possible however I've tried for about four days now different ways and files and I've had no luck.
My bootloader is locked and no ADB etc managed to get my device showing as the 9008 port so I think it's stuck in EDL.
Following guides, this is the furthest I've yet to get (In screenshot)
Could anyone shed some light and some assistance please? what am I doing wrong!?
attempted to apply for heat some to the device then re flash ?
blackcell1 said:
attempted to apply for heat to the device then re flash ?
Click to expand...
Click to collapse
Sorry, I don't quite understand what you mean?
Clarkeofcurtis said:
Sorry, I don't quite understand what you mean?
Click to expand...
Click to collapse
Use a hairdryer to warm up the back of the phone.
Are you pulling my leg? Warm it up then reflash?
nah im not trying to make you destroy your phone, being rather serious with this method. i use it on a daily basis to solve phones that fail during restoring factory images. i wouldn't know how long to give it with a hair dryer as i have access to a heat gun/heat mats .
just think of it as a cheap mans re balling method
blackcell1 said:
nah im not trying to make you destroy your phone, being rather serious with this method. i use it on a daily basis to solve phones that fail during restoring factory images. i wouldn't know how long to give it with a hair dryer as i have access to a heat gun/heat mats .
just think of it as a cheap mans re balling method
Click to expand...
Click to collapse
Sorry haha, I'm a noob with most of this android stuff bar rooting and flashing a few devices prior! I shall give it a go now and get back to you - thank you for the advice
Clarkeofcurtis said:
Sorry haha, I'm a noob with most of this android stuff bar rooting and flashing a few devices prior! I shall give it a go now and get back to you - thank you for the advice
Click to expand...
Click to collapse
good luck, id give it a good couple of minutes on the highest setting, just so its a little hot to the touch. and attempt the flashing of the files when its still hot/warm.
blackcell1 said:
good luck, id give it a good couple of minutes on the highest setting, just so its a little hot to the touch. and attempt the flashing of the files when its still hot/warm.
Click to expand...
Click to collapse
thank you so much that worked, it has said flash successful, first time I got a google logo but now nothing, what would be my next step please?
if the bootloader is unlocked then you can directly flash the firmware. but if its not google "nexus ota" and then on your phone jump into the recovery and check the firmware model number and download the same ota and adb sideload it.
im not 100% sure on the next step as I've never had a nexus 6p with a dead bootloader. but thats what id do.
---------- Post added at 04:50 PM ---------- Previous post was at 04:49 PM ----------
but from my personal experience with having to heat a phone up to restore factory images, it kinda means the phone is nearing the end of its life and id start thinking about buying your next phone before it sh*ts the bed.
blackcell1 said:
if the bootloader is unlocked then you can directly flash the firmware. but if its not google "nexus ota" and then on your phone jump into the recovery and check the firmware model number and download the same ota and adb sideload it.
im not 100% sure on the next step as I've never had a nexus 6p with a dead bootloader. but thats what id do.
Click to expand...
Click to collapse
Thank you for the reply and continuing to help, after seeing the google logo just once I'm getting nothing again - I'm even more determined now though as It's been dead for 2 months so this is the furthest I've gotten - the application of heat is what did it for me and fixed the error I was getting, can't get into recovery now though holding power + down etc
Clarkeofcurtis said:
Thank you for the reply and continuing to help, after seeing the google logo just once I'm getting nothing again - I'm even more determined now though as It's been dead for 2 months so this is the furthest I've gotten - the application of heat is what did it for me and fixed the error I was getting, can't get into recovery now though holding power + down etc
Click to expand...
Click to collapse
yeah can you access the bootloader at all ? does it say that the bootloader is locked ? from trying to restore LG's it sometimes has to be re heated a few times, but yeah if you need to re heat it to get further into the phone then its pretty much a lost cause. the only reason i do it is to remove the data so we can resell the device.
blackcell1 said:
yeah can you access the bootloader at all ? does it say that the bootloader is locked ? from trying to restore LG's it sometimes has to be re heated a few times, but yeah if you need to re heat it to get further into the phone then its pretty much a lost cause. the only reason i do it is to remove the data so we can resell the device.
Click to expand...
Click to collapse
I can get into the andriod screen where you can select recovery and such, with the BL, Baseband product variation and such, where should I go from here?
Oh right, so even once restored to firmware, will it be useless do you think if I can even manage to?
Clarkeofcurtis said:
I can get into the andriod screen where you can select recovery and such, with the BL, Baseband product variation and such, where should I go from here?
Oh right, so even once restored to firmware, will it be useless do you think if I can even manage to?
Click to expand...
Click to collapse
Sorry if you can't access the recovery from the bootloader and its in locked state then your a member of the lovely group of BLOD (bootloader of death) if you hit recovery does it show a little android logo and sit there?
Sorry for the late reply
blackcell1 said:
Sorry if you can't access the recovery from the bootloader and its in locked state then your a member of the lovely group of BLOD (bootloader of death) if you hit recovery does it show a little android logo and sit there?
Sorry for the late reply
Click to expand...
Click to collapse
I believe so, I can just about get into the bootloader at the best of times and when I do I can select options but once proceeding to start said mode phone freezes so can't get into recovery mode :/
Thank you for your continuous help, only way i can get it into bootloader is by heating it up so does that mean for the device to ever work It'll need heat every time? looking like a spares and repairs listing on ebay
Clarkeofcurtis said:
I believe so, I can just about get into the bootloader at the best of times and when I do I can select options but once proceeding to start said mode phone freezes so can't get into recovery mode :/
Thank you for your continuous help, only way i can get it into bootloader is by heating it up so does that mean for the device to ever work It'll need heat every time? looking like a spares and repairs listing on ebay
Click to expand...
Click to collapse
Hello....
How did you manage to get in to EDL mode..? I'm really curious. With stock bootloader? Since you can't access recovery
Also what is exactly displayed in Windows device manager?
You are using an outdated QFil version... It is from 2014 àr 2015.
Do a google search with: QPST_2.7.453.0 . This version seem to be from 2016.
Use the first link from the result. I analysed the files with virustotal, those seem clean or malware...
Also when plugging your usb cord to your PC, does your phone vibrate? Or does the LED blink in red?
You may have to press power button when plugging the usb cord or press power button for a certain amount of time before you plug the usb cord. I'm not completly sure, but your phone may not be in the "proper" EDL state to accept the QFil flash.
Good luck... :good:
Is it possible to send me the guide you used? Thanks.
Clarkeofcurtis said:
Hi there, I've been browsing through the threads related to unbricking of the Nexus 6P stuck in qualcomm hs-usb qdloader 9008 mode, really desperate to get my device working again if even possible however I've tried for about four days now different ways and files and I've had no luck.
My bootloader is locked and no ADB etc managed to get my device showing as the 9008 port so I think it's stuck in EDL.
Following guides, this is the furthest I've yet to get (In screenshot)
Could anyone shed some light and some assistance please? what am I doing wrong!?
Click to expand...
Click to collapse
Hey there sorry for slow replies, will be back on my desktop in an hour I'll send you links for what I followed and such, I think the only reason my device was in EDL mode was due to a hardware fault? As my device is faulty indefinitely as I had to use a hairdryer to warm it up while flashing this then allowed it to enter firehose state which a lot of people seem to error with - after all my attempts and research I'm to velieve there's a fault with the phone itself the only way I could get it to even power up was applying heat to it after removing the back panel
As blackcell said deballing or something? Worked a treat!
Furthest I've managed to get now is into my boot loader however everything is locked - when I press enter recovery my handset just freezes ?
5.1 said:
Hello....
How did you manage to get in to EDL mode..? I'm really curious. With stock bootloader? Since you can't access recovery
Also what is exactly displayed in Windows device manager?
You are using an outdated QFil version... It is from 2014 àr 2015.
Do a google search with: QPST_2.7.453.0 . This version seem to be from 2016.
Use the first link from the result. I analysed the files with virustotal, those seem clean or malware...
Also when plugging your usb cord to your PC, does your phone vibrate? Or does the LED blink in red?
You may have to press power button when plugging the usb cord or press power button for a certain amount of time before you plug the usb cord. I'm not completly sure, but your phone may not be in the "proper" EDL state to accept the QFil flash.
Good luck... :good:
Click to expand...
Click to collapse
Thanks pal if you check last post I wrote about my EDL mode forgot to tag you my apologies, as for my LED I've never seen that light up since I bricked it, even when google logo came up etc and while in the boot loader
Clarkeofcurtis said:
Thanks pal if you check last post I wrote about my EDL mode forgot to tag you my apologies, as for my LED I've never seen that light up since I bricked it, even when google logo came up etc and while in the boot loader
Click to expand...
Click to collapse
Light usually a red LED blink while in proper EDL state as far as I know. Could be something else on the N6P. Well, it looks like you are SOL. Sorry, I don't know what else to say, since you exhausted all possibilities...
Good luck...

I'm trying to unbrick my x720 by QFIL but my pc won't recognize Qualcomm 9008 port

My problem is that I can't even try to do the procedure in the other threads that i've read because my pc simples dont recognize anything when i install the qualcomm drivers. Any tips? Thank you in advance. I want to try this thread [GUIDE][QFIL MODE]Unbrick your Le Pro3, tested and working. But simply the qualcomm port doesnt appear in the device manager.
Bad cable or need to reinstall drivers...
marik1 said:
Bad cable or need to reinstall drivers...
Click to expand...
Click to collapse
I tried with two different cables and reinstalled the drivers a few times now. No port in the device manager. Just the Android ADB Interface tha showed when I installed the leeco adb drivers. On the ports just appear the standard Comunication port and printer port. I tried everything, the volume bottons power, etc. The Flash One dont recognize the phone for QFIL.
Say sth more about your phone state and history...
marik1 said:
Say sth more about your phone state and history...
Click to expand...
Click to collapse
I dont have hardware problems. I flashed the Pixel Experience rom in february with sucess but I didnt like it. It had too much battery drain. Then I wanned to try some other rom like AICP. But in the process of flashing something went wrong. I wasnt able to flash it, always gave me the error 7. Then it simply died. I was rebooting TWRP mode and it went dead. Now just vibrates when I try to turn on. I tried the QFIL process (both volumes + power) but I dont even know. How can we know that it in qfil mode? My pc wont recognize anything. Not in Flash One, Not in QPST, nothing. Am I doing something wrong? The phone vibrates so its charged. I installed the Qualcomm drivers properly, I thing, eventhow it doesnt appear the qualcomm 9008 port in the device manager. Its suppose to appear before the phone is pluged right? Thank you for the reply.
I've no idea how to help you... Sorry.
gradim said:
I dont have hardware problems. I flashed the Pixel Experience rom in february with sucess but I didnt like it. It had too much battery drain. Then I wanned to try some other rom like AICP. But in the process of flashing something went wrong. I wasnt able to flash it, always gave me the error 7. Then it simply died. I was rebooting TWRP mode and it went dead. Now just vibrates when I try to turn on. I tried the QFIL process (both volumes + power) but I dont even know. How can we know that it in qfil mode? My pc wont recognize anything. Not in Flash One, Not in QPST, nothing. Am I doing something wrong? The phone vibrates so its charged. I installed the Qualcomm drivers properly, I thing, eventhow it doesnt appear the qualcomm 9008 port in the device manager. Its suppose to appear before the phone is pluged right? Thank you for the reply.
Click to expand...
Click to collapse
Instead of creating a new post why not just read the enormous unbrick forums that exists and have proven steps. Many, Many phones have been debricked using those steps.
Hint, read the last pages for updated links to the software tools needed.
Next, I just found this cable which will help immensely with unbricking your device: https://www.amazon.com/GPG-EDL-Cabl...r1&keywords=edl+cable+for+wall+qualcomm+usb+c
tsongming said:
Instead of creating a new post why not just read the enormous unbrick forums that exists and have proven steps. Many, Many phones have been debricked using those steps.
Hint, read the last pages for updated links to the software tools needed.
Next, I just found this cable which will help immensely with unbricking your device: https://www.amazon.com/GPG-EDL-Cabl...r1&keywords=edl+cable+for+wall+qualcomm+usb+c
Click to expand...
Click to collapse
I've tried four different cables now and nothing. Thank you for minding but I think there isn't a solution for my leeco. Its dead and no one can help him.
Is yours 722?
Sent from my SM-A730F using xda premium
mchlbenner said:
Is yours 722?
Sent from my SM-A730F using xda premium
Click to expand...
Click to collapse
No, x720 6gb ram 64 rom.
gradim said:
No, x720 6gb ram 64 rom.
Click to expand...
Click to collapse
Is your phone completely Dead or do you have fashboot or anything working.
Do have a red flashing light?
Sent from my SM-A730F using xda premium
mchlbenner said:
Is your phone completely Dead or do you have fashboot or anything working.
Do have a red flashing light?
Sent from my SM-A730F using xda premium
Click to expand...
Click to collapse
Completely dead, just vibrates when I press power and yes, I sometimes have the red light, sometimes flashing, sometimes stable.
gradim said:
I dont have hardware problems. I flashed the Pixel Experience rom in february with sucess but I didnt like it. It had too much battery drain. Then I wanned to try some other rom like AICP. But in the process of flashing something went wrong. I wasnt able to flash it, always gave me the error 7. Then it simply died. I was rebooting TWRP mode and it went dead. Now just vibrates when I try to turn on. I tried the QFIL process (both volumes + power) but I dont even know. How can we know that it in qfil mode? My pc wont recognize anything. Not in Flash One, Not in QPST, nothing. Am I doing something wrong? The phone vibrates so its charged. I installed the Qualcomm drivers properly, I thing, eventhow it doesnt appear the qualcomm 9008 port in the device manager. Its suppose to appear before the phone is pluged right? Thank you for the reply.
Click to expand...
Click to collapse
Your phone is probably fixable.
Based on what you stated above, it seems that you downloaded and attempted to install the wrong version of TWRP and now your phone has no recovery at all.
Here is partial instructions I posted in the unbricking forum : https://forum.xda-developers.com/showpost.php?p=76100899&postcount=121
Use those instructions along with is mentioned below. I have personally helped so many people unbrick their phone that I have lost track and this is the reason why the posts are so long and extensive. Because sometimes what works for one person does not work for the next. So I have essentially have taken everyone's great advice and updated the links, made the instructions steps a little more concise and easier to read, fixed some incorrect steps or added the needed skipped steps. Plus added my own research into what I believe is now a definitive guide for unbricking the Leeco variants X720 and X727. The point of not reposting the information here is to keep everything from becoming more fragmented.
Yes, it's possible that you have a hardware issue. But, its also possible that it can be fixed!
Remember that you will not see the port unless you are in EDL mode
Just press volume △ (+) and volume ▽ (–) buttons together while powering the phone on.
It should now be EDL mode. If you cannot get into EDO mode, you cannot do anything else.
If you get an error, press and hold the power button while at the same time hold vol up + and down simultaneously plug the usb cord into the back of the computer while holding the buttons.
Yes, It's a pain and this is why the deep flash cable is handy....it's a special cable ( so your extra cables will do nothing to help you) The deep flash cable will automatically put your phone into EDL mode and allow you to use Flash on.
Install the Qualcomm QDLoader 9008 driver: https://goo.gl/9E3bKq or the from links provided in the unbrick forum.
There are multiple versions or Qfil, some have issues. I posted the correct one that works.
FOR anything else go to that forum read my and everyone else's posts. Again, I keep all of my linked files are up to date, and many are located on my own drives.
You can make one of these cables. Here's a video that shows you how:
https://www.youtube.com/watch v=kSiGsYK66gM&lc=z220yhtqvwyyct21pacdp432sh2xjecek10dae1jen5w03c010c.1524884617336803
it will not be a quick fix.
There are 4 or 5 different unbricking options and it requires persistence and patience.
The good news is that your phone has a solution that may work.
So when your where flashing a rom you got error 7 and your phone went dead.
I had gotten that same error.
Error could mean two things 1) update recovery or update firmware.
My point is sounds nice like hardware issue.
These phones are known for just dieing.
Also getting into that mode you have to push power+volume+volume- at the same time.
Sent from my SM-A730F using xda premium

SM-950F Hard bricked, JTAG?

Hey
So I was flashing android 7.0 to an S8 and it completely died, this is how completely:
- No screen/LED/vibration motor
- No safety/recovery/download mode (and don't ask about button combos, I've tried them all)
- No USB recognition from device manager (not even as exynos in other devices, just nothing)
- USB jig does nothing
- It is however recognised by wireless chargers (but I doubt that has any real significance)
At this point my question is would a JTAG even work on it? Or is my only hope a complete motherboard replacement?
S8 Hard bricked
A_Bad_Marksman said:
Hey
So I was flashing android 7.0 to an S8 and it completely died, this is how completely:
- No screen/LED/vibration motor
- No safety/recovery/download mode (and don't ask about button combos, I've tried them all)
- No USB recognition from device manager (not even as exynos in other devices, just nothing)
- USB jig does nothing
- It is however recognised by wireless chargers (but I doubt that has any real significance)
At this point my question is would a JTAG even work on it? Or is my only hope a complete motherboard replacement?
Click to expand...
Click to collapse
hello!
same happened to me ......dont worry i will help u....
i think u flashed aosp rom
phone is not hard bricked its still not turned off believe me........
do the following:
donot charge phone for atlesat 24 hours .......
after 24 hours try to boot into download mode press button for like a minute it will work in multiple tries,,
immediately flash twrp and when flashed successfully suddenly press vol down + bixby + power it will boot into recovery
charge for 1 -2 hours , clear system and every thing if you have backup thats good other wise flash firmware......donot turn in till flashing the system and data in recovery mood......boot into download mood from recovery and there you go....if still a problem inbox me
Thanks, I'll give it a shot
ok let me know then
Jtag dead phone to life and rewrite IMEI
I had the same thing, sent it to Fonefunshop in England, they said they could fix it, the didn't even open it as discovered by the guys who fixed it and is necessary to use jtag.
Fonefunshop said eMMC chip was bad, which is not true, but that led me to search for someone to replace the chip. I found A2Z cellular in Ottawa, Canada. They got the phone to boot up, but IMMEI was null( I did this trying to flash back to stock after TWRP screwed up). They rewrote original IMEI , now phone works like new. These guys are amazing.
http://a2zcellular.com/
Thank you all for the advice.
But I have now managed to unbrick and reflash the firmware. khawarjaved's advice turned out to be what fixed it in the end.
That was close, nearly lost £30
A_Bad_Marksman said:
Thank you all for the advice.
But I have now managed to unbrick and reflash the firmware. khawarjaved's advice turned out to be what fixed it in the end.
That was close, nearly lost £30
Click to expand...
Click to collapse
I have been through that situation man.... So always ready to help, ??
Hi pros
I'm in kind of a similar situation....I think I flashed MY 950U PIE with wrong BL
This phone is dead....Doesn't boot...no download mode....No recovery mode....
When connected to pc....device manager Recognises device as QUALCOMM HS USB 9008
Any way to brig it back to life...?
Your phone is connected in edl download mod. It will accept special files which will allow it to boot to download mode and let you flash stock firmware
The tool used for this is emmcdl.exe
It has to come with phone specific files
No idea where to get it. Ask people here, those who root phones. They know.

Categories

Resources