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...
Related
Hello guys,
A few minutes ago I bricked my Nexus 4 by inserting an incorrect terminal command found in this thread from another device. http://forum.xda-developers.com/showthread.php?t=1333782
My Nexus 4 did not turn on anymore after I rebooted and whenever I try to power it on by holding on the PWR button when plugged in (via charger or computer) it shows a red LED of death for 4 seconds and goes away, while the screen stays black. I do not know what to do, can anyone please help? I have tried reading other threads but to no avail.
EDIT1: My PC displays the QHSUSB_DLOAD message when plugged
EDIT2: I got it to display Qualcomm HS-USB QDLoader 9008 (COM4). [I assume it has to do with the Qualcomm High Speed USB Driver]
you wanted to get into recovery? with a terminal emulator? su(press enter) reboot recovery(press enter) didnt work?
simms22 said:
you wanted to get into recovery? with a terminal emulator? su(press enter) reboot recovery(press enter) didnt work?
Click to expand...
Click to collapse
I was being naive and I blindly followed the command. Very foolish of me.
can you get into your recovery? can you get into the bootloader? i see you were messing with partitions, which differ on every device. if you can get into your bootloader, you can try to flash the whole system image.
simms22 said:
can you get into your recovery? can you get into the bootloader? i see you were messing with partitions, which differ on every device. if you can get into your bootloader, you can try to flash the whole system image.
Click to expand...
Click to collapse
Nope, I can't even get into recovery OR bootloader. Power button does nothing except show a red light LED for a few seconds, then goes away while screen stays black.
fakudolan said:
Nope, I can't even get into recovery OR bootloader. Power button does nothing except show a red light LED for a few seconds, then goes away while screen stays black.
Click to expand...
Click to collapse
oh, that's not good.
id look look for any tool that lg provides for flashing, if they provide something. or, id start the rma process. you can always try the fixes posted for tbe red light of death, but only the tiniest chance that it would help.
simms22 said:
oh, that's not good.
id look look for any tool that lg provides for flashing, if they provide something. or, id start the rma process. you can always try the fixes posted for tbe red light of death, but only the tiniest chance that it would help.
Click to expand...
Click to collapse
Why RMA? This isn't Google or LG's fault. Pure user error.
Sent from my iPad 4
mitchdickson said:
Why RMA? This isn't Google or LG's fault. Pure user error.
Sent from my iPad 4
Click to expand...
Click to collapse
truth.
mmcblk0p3 on the N4 is SBL2, ie one of the bootloader pieces.
Are you sure you cant get into fastboot? If you actually were able to you could reflash the bootloader and that would restore SBL2, if you cant then you're SOL.
You might still be able to fix it with QPST or something as that sounds like the mode it's booting into, though I dont actually know anything about QPST.
I agree that its a user fault, but everyone RMAs devices like this. Plus its not that hard for Google to flash stock images on them
Sent from my Nexus 4 using xda app-developers app
TheManii said:
mmcblk0p3 on the N4 is SBL2, ie one of the bootloader pieces.
Are you sure you cant get into fastboot? If you actually were able to you could reflash the bootloader and that would restore SBL2, if you cant then you're SOL.
You might still be able to fix it with QPST or something as that sounds like the mode it's booting into, though I dont actually know anything about QPST.
Click to expand...
Click to collapse
I probably could, but I have no idea what or how to use QPST.
I think I found out how to use QPST, it says COM4 Phone is in Download mode, and it asks for a Phone Image and Boot image.
Can anyone tell me what is a Phone Image?
EDIT: Nevermind, QPST is asking for .hex files...
There exists an 8960_msimage.mbn file which is what QPST is asking for under the Factory Image tab in QPST Software Download. Should I use that?
Status
Hey, can you report back whether you could fix your phone or not? I'm in the very same situation as you are right now.
Thanks
darkware said:
Hey, can you report back whether you could fix your phone or not? I'm in the very same situation as you are right now.
Thanks
Click to expand...
Click to collapse
Have you tried Gigadroid's unbrick method at http://forum.xda-developers.com/showthread.php?t=2347060?
fakudolan said:
My Nexus 4 did not turn on anymore after I rebooted and whenever I try to power it on by holding on the PWR button when plugged in (via charger or computer) it shows a red LED of death for 4 seconds and goes away, while the screen stays black. I do not know what to do, can anyone please help? I have tried reading other threads but to no avail.
EDIT1: My PC displays the QHSUSB_DLOAD message when plugged
EDIT2: I got it to display Qualcomm HS-USB QDLoader 9008 (COM4). [I assume it has to do with the Qualcomm High Speed USB Driver]
Click to expand...
Click to collapse
This happened to my first N4 without me doing anything.
Also had QHSUSB_DLOAD couldn't find any method to recover it I'm afraid.
It's under a year old so try for an RMA, I probably wouldn't suggest that you mention how it happened
aanonymoushuman said:
I agree that its a user fault, but everyone RMAs devices like this. Plus its not that hard for Google to flash stock images on them
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
People like you are the reason cell phone prices go up. A huge problem with today's society....no one takes responsibility for their own mistakes. Can't pay your mortgage? Have government refinance your house. Don't like to work? Just collect welfare and stay home. Brick your nexus for doing something stupid? Just make Google pay for it. I swear you people make me sick.
Sent from my Nexus 4 using Tapatalk 4 Beta
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
I need some serious help guys. Phone is stuck at boot logo and wont turn on. IT wont enter recovery mode. it wont hard reset. It wont enter download mode.
The phone was completely stock originally. So i rooted using towelroot and ran the 'AutoREC' program. That did its thing and restarted and got stuck in fastboot mode. couldnt get out of it. Eventually managed to reflash all the original stock ROM partitions and it started to boot again... only to get stuck at the LG logo. I need some serious help.
PC wont detect the phone at all and its as if there is no OS on the phone. I have the D802 variant 32gb.
which kdz variant did you flash.
v.konvict said:
which kdz variant did you flash.
Click to expand...
Click to collapse
D80220C_00
got it from "lg-firmware-rom" after entering my imei
spookyleaf said:
D80220C_00
got it from "lg-firmware-rom" after entering my imei
Click to expand...
Click to collapse
same thing happened to a d802 of a friend of mine. but he flashed the d802h variant. will keep you posted if i find a way out.
I am in the same position. Except I tried to flashify stock recovery on d800 at&t variant. I wanted to install the stock update because I was still stock. Just root with twrp before...I had the sprint variant before the ls980 and it never screwed me over like this. I'll post if I figure anything out... I got to get ahold of shellnutt... He's the g2's god.
Dam. Leme me know what happens
Sent from my Nexus 5 using XDA Free mobile app
spookyleaf said:
Dam. Leme me know what happens
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Have you tried both ways to enter recovery?
Push PWR + Vol Down till you see the LG Logo then release and press both again
Push PWR + Vol Down till you see the LG logo then release and press and hold the volume up and volume down buttons until reset screen appears.
If you can see the LG logo I think you are not Hard Bricked
I haven't tried that exactly. I'll give it a shot when I get a chance
Sent from my Nexus 5 using XDA Free mobile app
You may want to check your internal hardware to be sure it's marked as a D802. Typically the feint white stamp in the lower center/left of the phone with rear cover removed is the true model number. It's also stamped on the board and on the ribbon cables going up eithe side. Your device is showing the signs of a false d802 which has become sadly common in recent months.
If it's legit d802 then flash aboot, boot, laf and power it off.
Then hold voume up and connect to pc while still holding volume up.
Make sure you have the drivers installed, fire up lg mobile support tool or the lg flash tool 2014 (you need your kdz file now - find it using your imei and lg-firmware site)
Okay so I found this: http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404 to get it to come up as a device in Windows and Linux. And this: http://forum.xda-developers.com/showthread.php?t=2582142 I'm sure you read this but you need to do it after following the first guide. I already have a Linux installed and I'm going to try today. I'll update with a guide for you only if you need it and if I succeed. I just need to remind you. You CANNOT mess up on the second guide... Well as far I can tell. But if the first guides label is actually true then maybe I'm wrong.
ok so ive ordered some tools to open up the phone and check the internals. Hopefully its a legit G2. Meanwhile every single possible combination of the power and volume keys does absolutely nothing. If all else fails ill try shorting the capacitors as ive seen on a guide from here and hopefully that will be the end of it. Thanks for all the input guys. Ill keep you posted!
darkpower_4 said:
Okay so I found this: http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404 to get it to come up as a device in Windows and Linux. And this: http://forum.xda-developers.com/showthread.php?t=2582142 I'm sure you read this but you need to do it after following the first guide. I already have a Linux installed and I'm going to try today. I'll update with a guide for you only if you need it and if I succeed. I just need to remind you. You CANNOT mess up on the second guide... Well as far I can tell. But if the first guides label is actually true then maybe I'm wrong.
Click to expand...
Click to collapse
thanks i appreciate that very much. Keep me informed on how it goes. Fingers crossed!
spookyleaf said:
ok so ive ordered some tools to open up the phone and check the internals. Hopefully its a legit G2. Meanwhile every single possible combination of the power and volume keys does absolutely nothing. If all else fails ill try shorting the capacitors as ive seen on a guide from here and hopefully that will be the end of it. Thanks for all the input guys. Ill keep you posted!
Click to expand...
Click to collapse
Plug it into a windows machine, open device manager and look for Qualcomm qhsusb_bulk. If you get that, you're already in bulk and don't need to worry about shorting capacitors. If it's not being recognized in any way, you may be forced into that as a last resort.
spookyleaf said:
ok so ive ordered some tools to open up the phone and check the internals. Hopefully its a legit G2. Meanwhile every single possible combination of the power and volume keys does absolutely nothing. If all else fails ill try shorting the capacitors as ive seen on a guide from here and hopefully that will be the end of it. Thanks for all the input guys. Ill keep you posted!
Click to expand...
Click to collapse
All you really need to open it up is a guitar pick. It pries apart make sure you take the sim card out. After that it's going to take a little swipe around the edge and it'll pop open no problem.
iowabowtech said:
Plug it into a windows machine, open device manager and look for Qualcomm qhsusb_bulk. If you get that, you're already in bulk and don't need to worry about shorting capacitors. If it's not being recognized in any way, you may be forced into that as a last resort.
Click to expand...
Click to collapse
I checked that already. Not going into bulk mode. Seems like the capacitors are my last resort
so ive poped the phone open and guess what... its not a D802.. its a D800.. the at&t version... wtf.. no wonder i bricked it. gonna see if i can use the unbrickable method
did you checked the IMEI?
nope its says on the speaker grille after you remove the back cover. "D800"
how is that possible? did phone information apps showed your device as 802 aswell? did kernel info and phone info in system settings lied too?
So guys, i have tried to downgrade my phone from android 7.1.1 to 6.0 which ended in a softbrick, after that i tried 2 flash a stock rom but that completely bricked it and now my phone wont dont anything anymore except for some kind of mode that my computer can detect in device it sees the qualcomm port 9008 device but there a thing it just wont work miflash doesnt recognize it and i cant find any sollutions online please help
tnhx
Daan_K said:
So guys, i have tried to downgrade my phone from android 7.1.1 to 6.0 which ended in a softbrick, after that i tried 2 flash a stock rom but that completely bricked it and now my phone wont dont anything anymore except for some kind of mode that my computer can detect in device it sees the qualcomm port 9008 device but there a thing it just wont work miflash doesnt recognize it and i cant find any sollutions online please help
tnhx
Click to expand...
Click to collapse
I wonder:
-Which is your phone model, as stated on the back of the phone?
-Which is the file that you used to downgrade?
-Which stock rom did you try to flash?
The fix is pretty simple but seeing how you borked three simple procedures I'd like to know everything and lay it out for you precisely. You have to have done something horribly wrong to softbrick a phone with the stock updater system...
Choose an username... said:
I wonder:
-Which is your phone model, as stated on the back of the phone?
-Which is the file that you used to downgrade?
-Which stock rom did you try to flash?
The fix is pretty simple but seeing how you borked three simple procedures I'd like to know everything and lay it out for you precisely. You have to have done something horribly wrong to softbrick a phone with the stock updater system...
Click to expand...
Click to collapse
Okay at first my phone model on the back of my device is, as i mentioned before, "zte a2017g" thats the european version of this phone, chinese is "a2017" and the us version is "2017u".
The file i used 2 downgrade was the stock rom from the official website of zte
it was the full edl file buildnumber b10.
and again i once sofbricked it, i know how 2 fix that, but now it hard bricked, well i think so at least, i cant get it to boot into bootloader, recovery or anything, when i hold the power button it shakes the device, and it shows the zte logo for about 2 seconds then it disappears, and nothing happens but my computer does recognize it as a connected device but i cant use miflash of something else because those programs dont see it.
Daan_K said:
Okay at first my phone model on the back of my device is, as i mentioned before, "zte a2017g" thats the european version of this phone, chinese is "a2017" and the us version is "2017u".
The file i used 2 downgrade was the stock rom from the official website of zte
it was the full edl file buildnumber b10.
and again i once sofbricked it, i know how 2 fix that, but now it hard bricked, well i think so at least, i cant get it to boot into bootloader, recovery or anything, when i hold the power button it shakes the device, and it shows the zte logo for about 2 seconds then it disappears, and nothing happens but my computer does recognize it as a connected device but i cant use miflash of something else because those programs dont see it.
Click to expand...
Click to collapse
all right. it's still freaking weird. Use my DFU unbrick guide but only do step 4 and 5 (but use the files on the top anyways)(you just have to hold Vol+ and Vol - and insert the cable instead of taking the phone apart and shorting pins). After that check the driver, if it is still Qualcomm HS-USB QDLoader 9008 then flash with MiFlash, if not, tell me what appears
Choose an username... said:
all right. it's still freaking weird. Use my DFU unbrick guide but only do step 4 and 5 (but use the files on the top anyways)(you just have to hold Vol+ and Vol - and insert the cable instead of taking the phone apart and shorting pins). After that check the driver, if it is still Qualcomm HS-USB QDLoader 9008 then flash with MiFlash, if not, tell me what appears
Click to expand...
Click to collapse
allright allready thanks loads for your support but could you maybe send the right file to flash because i have no idea, and please, the files for a2017g not a2017 or a2017u thankyou so much
Daan_K said:
allright allready thanks loads for your support but could you maybe send the right file to flash because i have no idea, and please, the files for a2017g not a2017 or a2017u thankyou so much
Click to expand...
Click to collapse
they are in the guide. at the top, there's a link to WesTD's EDL flashable files. Get one for A2017G, for example B09
Choose an username... said:
they are in the guide. at the top, there's a link to WesTD's EDL flashable files. Get one for A2017G, for example B09
Click to expand...
Click to collapse
Allright, thankyou so much my dude
Choose an username... said:
all right. it's still freaking weird. Use my DFU unbrick guide but only do step 4 and 5 (but use the files on the top anyways)(you just have to hold Vol+ and Vol - and insert the cable instead of taking the phone apart and shorting pins). After that check the driver, if it is still Qualcomm HS-USB QDLoader 9008 then flash with MiFlash, if not, tell me what appears
Click to expand...
Click to collapse
aight, as i thought this didnt work, i tired it but miflash basicly just gave me an error notification.
also when i go into device manager i can see that my device is connected but i show the name with a yellow triangle with a ! in it i have no clue what this means can u please help me with this. i rlly want my phone back
Daan_K said:
aight, as i thought this didnt work, i tired it but miflash basicly just gave me an error notification.
also when i go into device manager i can see that my device is connected but i show the name with a yellow triangle with a ! in it i have no clue what this means can u please help me with this. i rlly want my phone back
Click to expand...
Click to collapse
First of all, if you get an error TELL ME what it says!
Send me a screenshot of the device manager, i can do very little with "yellow triangle"
Don't bother? That guy is using XDA as a free emergency support without looking for one second.
He probably would like you to do a teamviewer while he's watching football with a beer and not even say thank you.
I'm horrified.
RedWave31 said:
Don't bother? That guy is using XDA as a free emergency support without looking for one second.
He probably would like you to do a teamviewer while he's watching football with a beer and not even say thank you.
I'm horrified.
Click to expand...
Click to collapse
rlly m8. im just a guy who needs help with his phone the guy "choose a username..." i helping me with it, ive been unable 2 fix my phone with any of the other threads i just need some help and i have said thanks alot, dont call me that
Daan_K said:
rlly m8. im just a guy who needs help with his phone the guy "choose a username..." i helping me with it, ive been unable 2 fix my phone with any of the other threads i just need some help and i have said thanks alot, dont call me that
Click to expand...
Click to collapse
Sorry, I don't believe you for one second. Like litterally THOUSANDS of people here and here opening "bricked plz hlp" threads, you didn't even have the BASIC, LOWEST courtesy of writing more than 10 words of gibberish whining about your situation, without a single usefull element of context.
Proof of that in the NUMEROUS questions asked about ELEMENTARY elements about your situation. You're litterally the kind of person that would go to a car mechanic, drop the keys on the counter saying "my car is broken, fix it" and just leave without a single word added. That's RUDE and, yeah, I'm tired AF of people like you who can't READ THE DAMN XDA RULES and got NOT education whatsoever.
Nd writng frm a phone in T9 mde dsnt rlly bring nythng mre on the tble either.
Too bad you found somebody to help, as it's only encouraging that kind of behaviour.
//Rant off//
@Daan_K this EDL Tool can help https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759
Choose an username... said:
First of all, if you get an error TELL ME what it says!
Send me a screenshot of the device manager, i can do very little with "yellow triangle"
Click to expand...
Click to collapse
this is a screenshot of my device manager, and what I meant with yellow triangle, also it doesn't work with the edl-tool nor the axon7tool
Daan_K said:
this is a screenshot of my device manager, and what I meant with yellow triangle, also it doesn't work with the edl-tool nor the axon7tool
Click to expand...
Click to collapse
Okay, let's try two things:
First right click on it and uninstall the device, also delete driver software for the device (it will be a checkbix asking for that after you hit 'uninstall device'). After that, hold Volume up, Volume down, and Power until the Device manager refreshes. After that the driver should reinstall itself. If it still shows with the yellow triangle, right click it, click on Properties, and send me a screenshot (or translate me what it says on the status part)
https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898
if you can only get to dfu mode and nothing else, use thise guide, you'll have to dismantle your phone. Had to unbrick mine with this from a hardbrick, worked flawlessly
IvI97 said:
https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898
if you can only get to dfu mode and nothing else, use thise guide, you'll have to dismantle your phone. Had to unbrick mine with this from a hardbrick, worked flawlessly
Click to expand...
Click to collapse
Hey, a couple of things: one, i've updated the guide, it's around, much simpler to use. just saying. Two, this guy has the right driver. Don't confuse him with DFU while at least for now it is not.
Choose an username... said:
Okay, let's try two things:
First right click on it and uninstall the device, also delete driver software for the device (it will be a checkbix asking for that after you hit 'uninstall device'). After that, hold Volume up, Volume down, and Power until the Device manager refreshes. After that the driver should reinstall itself. If it still shows with the yellow triangle, right click it, click on Properties, and send me a screenshot (or translate me what it says on the status part)
Click to expand...
Click to collapse
omg the triangle is gone, thankyousomuch, but what can I use now 2 fix it further?? is that in your guide maybe?
choose an username... said:
hey, a couple of things: One, i've updated the guide, it's around, much simpler to use. Just saying. Two, this guy has the right driver. Don't confuse him with dfu while at least for now it is not.
Click to expand...
Click to collapse
omygod it ****ing working, choose an username man, i can't thank you enough, seriously ur the best man lots of love for doing this
Hey guys,
Guess today it was my turn ****ing up.
I apparently have completely bricked my Axon 7 after trying to go from LOS 15.1 to stock oreo beta. The only thing I seem to be able to boot to is DFU mode and for some reason, if I press the Power button + Vol Down I will get stuck on the ZTE Logo and my PC will detect my phone through the ADB interface but every time I try doing something it says my device is unauthorized. Is there any way I can authorize the device whilst being completely bricked?
The only other thing I get is the unlocked bootloader warning screen. If I don't press anything the phone will be stuck there, if I select recovery the phone will simply shut down and anything else will result in a reboot. I have also tried a deep flash cable that that only results on the phone being stuck at the unlocked bootloader screen.
I cannot access the bootloader,
I cannot access EDL mode
I can access ADB, but device shows as unauthorized.
I can access DFU mode.
Any suggestions would be appreciated. I have looked at the Hard brick guide that involves taking the phone apart but that's not something I really want to do.
Thanks in advance.
Edit: My phone gets detected by MiFlash but every time I try flashing I get a cannot receive hello packet and object reference not set to an instance of an object.
ZTE axon 7 EDL tool detects it in ADB mode but says ERROR! NO ANSWER FROM PHONE!. Possibly since its not authorized with ADB.
Ouh....DFU? I think this thing is totally bricked.
I can access my phone in ADB. If only I could make it reboot to edl or something like that through ADB even though my device shows as unauthorized. That is the only problem why this thing is completely messed up.. ADB works but I can't do anything with it because my phone shows unauthorized. Does anyone know if there's a workround or a bypass for that?
Victor13f said:
I can access my phone in ADB. If only I could make it reboot to edl or something like that through ADB even though my device shows as unauthorized. That is the only problem why this thing is completely messed up.. ADB works but I can't do anything with it because my phone shows unauthorized. Does anyone know if there's a workround or a bypass for that?
Click to expand...
Click to collapse
Hi Victor !
Like we discussed before there is nothing much left as to use the DFU unbrick-disassemble guide or buy something like this to be sure you tried everything.
Good Luck mate !
raystef66 said:
Hi Victor !
Like we discussed before there is nothing much left as to use the DFU unbrick-disassemble guide or buy something like this to be sure you tried everything.
Good Luck mate !
Click to expand...
Click to collapse
Thank you for your help . It's a risk you take when flashing phones.
Can you get custom recovery in it some recovery allow you to get in to EDM from there you can flash stock rom with Mi flash tool.......try to push both volume buttons at the same time don't touch the power button this might get you in to EDM.
stinka318 said:
Can you get custom recovery in it some recovery allow you to get in to EDM from there you can flash stock rom with Mi flash tool.......try to push both volume buttons at the same time don't touch the power button this might get you in to EDM.
Click to expand...
Click to collapse
Hi. I cant get anywhere near recovery. When I press both buttons without the power button nothing happens. Thanks though!
Victor13f said:
Hi. I cant get anywhere near recovery. When I press both buttons without the power button nothing happens. Thanks though!
Click to expand...
Click to collapse
The screen will be blank untill you plug in USB cable to flash on mi flash tool then you refresh button on the computer screen....
stinka318 said:
The screen will be blank untill you plug in USB cable to flash on mi flash tool then you refresh button on the computer screen....
Click to expand...
Click to collapse
The moment I plug in any cable the screen turns on automatically. I've tried everything at the phone won't go into EDL. Thanks though!
Victor13f said:
The moment I plug in any cable the screen turns on automatically. I've tried everything at the phone won't go into EDL. Thanks though!
Click to expand...
Click to collapse
Nothing, you'll have to use my guide for that (the one that raystef linked). Otherwise try entering FTM mode (Power and Vol-) but it's surely not gonna work. If it does, you'll see a screen with a square that says "FTM", and you'll be able to do " adb reboot edl" and flash stuff from there.
Unbricking by disassembing the phone is the most reliable method; an EDL cable just might save you the hassle but it's not guaranteed to work; some phones won't accept it for some reason. In this case just follow the guide unless you want to try your luck with an EDL cable
Choose an username... said:
Nothing, you'll have to use my guide for that (the one that raystef linked). Otherwise try entering FTM mode (Power and Vol-) but it's surely not gonna work. If it does, you'll see a screen with a square that says "FTM", and you'll be able to do " adb reboot edl" and flash stuff from there.
Unbricking by disassembing the phone is the most reliable method; an EDL cable just might save you the hassle but it's not guaranteed to work; some phones won't accept it for some reason. In this case just follow the guide unless you want to try your luck with an EDL cable
Click to expand...
Click to collapse
Hello. Thank you for your advices, it is as I feared.
I have however already bought another Axon 7 which I'm using at the moment, and I have plans for mine since it was only bought new about 8 months ago and I believe I could get a replacement for a fee even if its bricked to fault of my own. So I will try that since I'm not in a rush.
This thread can be closed.
Cheers!
Victor13f said:
Hello. Thank you for your advices, it is as I feared.
I have however already bought another Axon 7 which I'm using at the moment, and I have plans for mine since it was only bought new about 8 months ago and I believe I could get a replacement for a fee even if its bricked to fault of my own. So I will try that since I'm not in a rush.
This thread can be closed.
Cheers!
Click to expand...
Click to collapse
In that case you can just pretend that the phone got in that state by itself, it's not too morally correct but some people here pulled it off...
twice now i have gotten an axon 7 into this state. while mine have been a2017u models, i dont know that they are different than yours in that regard.
What worked for me the first time was letting the phone completely die. Being unable to boot into anything, it was somewhat a task to actually make it die, so i kept powering it on (which merely made the red led indicator come on). i did this over and over again over the course of a day at work whenever i noticed it had powered off.
eventually, the phone had no response at all. then, i plugged it up to my laptop, and left it, convinced i had killed it. a dialogue popped up after a minute or two on the phone screen saying to charge the phone by plugging it up. i had no access to fastboot or EDL mode prior. once i got that 'plug in to charge' screen, i switched it to the wall charger, and left it to charge a bit (50-60%) from that state, then, i unplugged it again, and somehow, i managed to get edl mode to work by unplugging it and pressing all three buttons and holding them (typical edl boot).
once there, i reflashed via MiFlash an earlier build. i rolled back using MiFlash as far back as i could. in the process, i lost my imei and serial, which i have yet to successfully recover, but i did get out of DFU pergatory. the imei thing seems to be caused by going back to MM which i did on both of my IMEI-less a2017u boards, but im only guessing. my dd axon 7 is the only one of the three boards with imei and serial, so maybe MM is a bad idea. lol.
The first time i recovered from DFU, i did it inadvertently by letting the phone die and then flashing in EDL mode as well. (i left it for a few weeks as i had given up on it.) after it died completely, and i plugged ut up to the computer and had the same experience, I flashed the beta oreo build for a2017 using miflash. the screen had stopped responding. and i ended up doing a RMA. I now know the screen response thing was bc of a faulty EDL file of B15. (happened again to another of my axon, so i retraced my steps and realized it was when i flashed b15 that it died) . the fix if your screen ever stops responding, but isnt physically damaged? re-flash via EDL a different file. it may take a few tries, but eventually a build will work. for me, it was Marshmallow. I still do not know for certain, but that possibly is what killed my IMEI. but hey, it boots and the screen works.
I genuinely hope posting my idiocy in toying with axon 7s has helped someone out there.