Related
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 think I fucced up pretty badly this time...
I was on LOS, wanted to get back to stock, for some reason wiped and rebooted...
Infamous DFU mode. I can't get to FTM (tried power + vol down and it only turns on, scrolls a little and turns off), and I wasn't able to use axon7tool using zadig. No recovery at all, no fastboot, nothing...
I've installed QDLoader 9008 drivers and MiFlash actually recognizes the... thing. Can anyone tell me if this is worth trying/what I have to do? Thanks
P.S I have no way of returning it to ZTE
Edit: The miflash thing didn't work as expected, can't find programmer file
Look like you kill yourseft this time.
You have to enter EDL with any cost, or at less FTM - let batttery drain up and try again.
Otherwise, people say somethings about a DIY EDL cable, but I not really sure
tamahouse02 said:
Look like you kill yourseft this time.
You have to enter EDL with any cost, or at less FTM - let batttery drain up and try again.
Otherwise, people say somethings about a DIY EDL cable, but I not really sure
Click to expand...
Click to collapse
I've found this QPST thing from Qualcomm, also heard that the only thing missing is the programmer which is not released. It detects my device, reports it is a Sahara Memory Dump, and that's pretty much that. I hope that people is actually looking into this
Also I noticd that in the first seconds when it is seemingly installing, it says it is a Sahara Download. Does that help?
I also wanted to know, is there a main thread for this sort of thing? I've seen @tenfar 's thread but there is nothing to do on A2017G's
https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898
I know you're already active in this thread, but I don't know if you understand it in depth. You must open your device to enter into edl mode. In edl you can flash twrp and are back in business. So your only way to enter edl is to open your brick as described.
Thank you, however i wanna be extra cautious here. When I have to connect the test point to ground, do I connect it with the SIM slot? What is valid as ground?
If MiFlash recognizes it you should be able to flash a stock Rom. The I have the A2017U so I could be wrong
supergear said:
If MiFlash recognizes it you should be able to flash a stock Rom. The I have the A2017U so I could be wrong
Click to expand...
Click to collapse
It's all done, thank you though. I disassembled the whole thing and did the short to ground thing, and after literally 30 tries it flashed the damn thing
Hi everyone
I tried to updade my huawei nova CAN-L11C530B130 to CAN-L11C432B340
I think the copy/paste of the UPDATE.APP ****ed up beacause the transfer time was very short...Anyway the phone accepted the update but turned off after that.
Now I can't boot, no recovery, no download mode, not even a charging led light.
Please tell me there is a way besides RMA
Thank you very much :good:
Well, either there is no charge (try keeping it on charger for a few hours) or it is totally bricked based on what you said. If it is completely unresponsive there is really nothing you can do.
Boot loader doesnt start as well?
Thanks for your help
I tried an all night charching but It did not help, no boot loader either.
What about the version I had : CAN-L11C530, I don't find any results about it on the internet, strange right ?
When I plug the phone to my computer I get "Qualcomm HS-USB QDLoader 9008 (COM3)"
You could try contacting Huawei support, their is a qualcomm flash tool. You need the tool and the rom to use it. I know it worked on the Nexus 5, but have seen nothing like it for us. I would try going to a shop and asking, but I do not know how viable that is for you.
Thank you wangdaning, it's very kind of you
I'm gonna leave the phone to the carrier who will send it to huawei.
I'm just surprised how easy it was to brick, I have a honor 8 and a mate 8 and it never happened.
I wonder if it comes down to it being a defective device. I have run circles of flashing on mine and it does not brick. I am running Lineage and even the build is not for my device. I have manually flashed partitions, wiped and reflashed partitions (in fastboot). I have made it unusable at times, but never bricked. It works fine now. Seems it might just be an unlucky bad unit you got. Hopefully you had all your stuff backed up and hopefully you get a unit that works well next time.
Hello everybody,
First off, I hate people who don't search on google before making a post, I have been searching for 4 days and I feel that it's appropriate to ask now.
I will make 2 parts to this thread, one will be a very fast explanation of what I did and the second part will be the same but a very thorough with a step by step process of what I messed up...
TL;DR: I was tired, late in the evening I flashed for some reason a Partition table of a Mi Note 3 on my Mi A1... I am now bricked and cannot access anything, fastboot, ADB, recovery nothing! I guess my phone is in EDL mode cause when I plug it in it flashes its led. "Qualcomm HS-USB QDLoader 9008" Is what I see in my device manager.
What do? oh, I forgot! I cannot access anything through any combination of buttons. I am stuck here, where I am!
The full thorough explanation for people who are bothered to read fully. (Includes my excuses for making noob mistakes, might be fun to read idk.)
Young me on a Sunday evening decides to reinstall magisk but this time with twrp cause I did it without twrp (yeah yeah I know). I was left without OTA's and after uninstalling anything that had something to do with Xposed or magisk I trashed it all. and stupid me thought that maybe? maybe? just maybe deleting Dalvik Cache would help me get my OTA's back after injecting my original ROM. This is where the fun begins.
I was not wanting to go through reinstalling magisk and all that to wipe the Dalvik Cache, I thought that that was my mission now, so I decided to search for methods that don't require root or being in the system, so some kind of fastboot or ADB command or something idk. I tried installing twrp and without my understanding that failed miserably and then I read some post where someone said that they flashed a mi note 3 partition table on their phone and something worked. Being the naïve little boii that I am, let's do that hey? Bam! bricked! I read somewhere I can open the phone and remove the battery and not having the tools is a mess, having to ask friends for some and voiding my warranty for something that probably won't work and after reading I understood that I'm in "EDL 9008 recovery" or something like that. I cannot boot into anything, I only have EDL 9008 to work with. I tried using Xiaomi's flasher tool and it would never respond to the initial hello packet (duuhh! I can't use ADB nor fastboot).
I know that this was stupid, I know! I learnt my lesson. If there is nothing we can do can I at least somehow get my internal storage data back? I deleted the backups from google drive for a short amount of time but randomly 5hrs prior to this sad story. All I have safe are now my contacts.
I hope you guys have some ideas! I feel like I'm fked but maybe with EDL 9008, there is a little glimmer of light?
P.S. If you guys somehow get me into fastboot I can flash a correct partition table back. My PC has all drivers so I can do this!
Sincerely, Micheal.
There is a way although i did tried it yet.
First of all sorry for my English.
Download latest MiFlash tool and qualcomm driver, this package contain both but not latest MiFlash so you should download lastest version from official site.
https://www.fshare.vn/file/H3R8M6OMRP2R
Download lastest stock rom.
You will need a good USB type C cable, dont use the one come with phone because you dont want to cut it in half.
Yes, that exactly what i said. Cut it in half, there are 4 small wire (or maybe 5 with type C?), remove it outer plastic and reconnect them.
Join the green and black cable, like you short circuit them, then plug your phone into PC with that cable without release green and black, wait for 5 sec then seperate them, the green and black.
Check device manager on your PC, you should hear device connect sound and qualcomm HS-USB QDLoader show up under Ports.
Open MiFlash and try to flash it.
You may want to check this video, although it in Vietnamese but you should understand the usb cable part.
https://www.youtube.com/watch?v=d5-1I9rWTiw
Hi, interesting situation. What about following this guide: http://en.miui.com/thread-235865-1-1.html ?
Its for some other phone, but try instaliing some drivers and you may get some signal of life.
Very interesting
I have thought about doing this as I had an old type-c lying around that came with the phone (I use a beautiful cable I bought off amazon) and saw this method to flash but never tried it..
I'll give it a go thanks.
btw. Your English is good I understood everything
The second comment from TrueMS:
I already have all drivers installed and in the long post I said that I have a flashing led that indicates that i'm in EDL 9008, the phone isn't dead but it won't turn on with any driver
m1shka said:
Very interesting
I have thought about doing this as I had an old type-c lying around that came with the phone (I use a beautiful cable I bought off amazon) and saw this method to flash but never tried it..
I'll give it a go thanks.
btw. Your English is good I understood everything
The second comment from TrueMS:
I already have all drivers installed and in the long post I said that I have a flashing led that indicates that i'm in EDL 9008, the phone isn't dead but it won't turn on with any driver
Click to expand...
Click to collapse
Yes, thats what I meant. Well, I dont know how to help you, wish you luck. I remember how I flashed wrong ROM for my S3 Mini and it was completly trashed, I'm glad that Xiaomi gives us at least some signs of life and hope.
And btw. I would rather charge the phone somehow - I hope it charges even in EDL mode, because if your phone dies while flashing with MiFlash, things can be even worse.
EDIT: I also found this guide, you can try it out: https://forum.xda-developers.com/g4/general/guide-unbrick-via-external-sdcard-qfil-t3748946
Okay so now a major reply!
I have stated in the OP that I am already in EDL, there is no need for cutting the cable or installing any driver, I am in EDL 9008 I don't need to "try to get there" as i'm already there.
These guides failed miserably as I have already tried them, my phone "doesn't receive a hello packet" from my phone, as I can't use adb or fastboot, or recovery.
I'll download linux and give that usb method a go then
m1shka said:
Okay so now a major reply!
I have stated in the OP that I am already in EDL, there is no need for cutting the cable or installing any driver, I am in EDL 9008 I don't need to "try to get there" as i'm already there.
These guides failed miserably as I have already tried them, my phone "doesn't receive a hello packet" from my phone, as I can't use adb or fastboot, or recovery.
I'll download linux and give that usb method a go then
Click to expand...
Click to collapse
Wish you luck:
Something that is never mentioned is to disable driver enforcement, this time hello packet was successfully recieved and flashed... Hold your happiness, cause now EDL no longer works so I can't see it in any com port and i'm certainly still in edl cause of the flashing led. Only difference I see is that now the led flashes when I hold the power button??? hmmmmmmm
To clarify:
Can't boot
Device was flashed successfully
Com port on pc can no longer see phone even after reboot
adb still don't work (proves again i'm in edl)
I'm in an even stickier situation now, can't access with my pc hmmmm..
m1shka said:
Something that is never mentioned is to disable driver enforcement, this time hello packet was successfully recieved and flashed... Hold your happiness, cause now EDL no longer works so I can't see it in any com port and i'm certainly still in edl cause of the flashing led. Only difference I see is that now the led flashes when I hold the power button??? hmmmmmmm
To clarify:
Can't boot
Device was flashed successfully
Com port on pc can no longer see phone even after reboot
adb still don't work (proves again i'm in edl)
I'm in an even stickier situation now, can't access with my pc hmmmm..
Click to expand...
Click to collapse
did you try to hold more than 30 second ? and also , do you have flash log ?
m1shka said:
Something that is never mentioned is to disable driver enforcement, this time hello packet was successfully recieved and flashed... Hold your happiness, cause now EDL no longer works so I can't see it in any com port and i'm certainly still in edl cause of the flashing led. Only difference I see is that now the led flashes when I hold the power button??? hmmmmmmm
To clarify:
Can't boot
Device was flashed successfully
Com port on pc can no longer see phone even after reboot
adb still don't work (proves again i'm in edl)
I'm in an even stickier situation now, can't access with my pc hmmmm..
Click to expand...
Click to collapse
So did you flash official stock ROM? Because I dont understand why doesnt it work... btw. when you flashed the ROM, did you lock bootloader?
Cant be battery dead?
If you are on "Qualcomm HS-USB QDLoader 9008" you will be able to flash stock fastboot firmware. Flash it using MiflashTool. Normally Miflashtool will recognized it as COMXX, where XX is the number of the port.
It's the official rom for the march ota.
The phone works, apparently it was encrypting everything... and now as I interrupted it, the encrypting failed and I lost all my data.....
Phone works but could have been better.
Before I reset the phone to factory, as i cannot use it yet, is there any way to get anything personal back? or is it gone gone and just factory reset?
What I see after boot, the phone resets every minute
https://drive.google.com/file/d/13sARZzlf3vJZK6Mx4hil6lsXRUl7-r-K/view?usp=sharing
The button that is hard to see says factory reset
m1shka said:
It's the official rom for the march ota.
The phone works, apparently it was encrypting everything... and now as I interrupted it, the encrypting failed and I lost all my data.....
Phone works but could have been better.
Before I reset the phone to factory, as i cannot use it yet, is there any way to get anything personal back? or is it gone gone and just factory reset?
What I see after boot, the phone resets every minute
https://drive.google.com/file/d/13sARZzlf3vJZK6Mx4hil6lsXRUl7-r-K/view?usp=sharing
The button that is hard to see says factory reset
Click to expand...
Click to collapse
Good job mate, so that SD card method worked with Linux? Be happy that your phone is alive.
EDIT: Maybe consider locking bootloader? Try it if youre on official stock.
EDIT 2: By flashing that ROM I guess you lost all data, but you can try to boot in TWRP without installing it and browse in file manager to see, if there is any data.
TrueMS said:
Good job mate, so that SD card method worked with Linux? Be happy that your phone is alive.
Click to expand...
Click to collapse
No... I was going to do that tomorrow but I decided to disable driver signature enforcement which worked. This should be written everywhere if it's this important..
Is there still a way to get my internal data back? Question as well, in recovery "mounting" the data partition will that let me get everything back "mounting" the drive to the pc? or do i not understand what mounting is.
m1shka said:
No... I was going to do that tomorrow but I decided to disable driver signature enforcement which worked. This should be written everywhere if it's this important..
Is there still a way to get my internal data back? Question as well, in recovery "mounting" the data partition will that let me get everything back "mounting" the drive to the pc? or do i not understand what mounting is.
Click to expand...
Click to collapse
As I said, you can try it, but when I flashed my Nougat stock ROM, i lost all the data. Or you can boot into TWRP and connect with USB to your computer to see the data in phone.
Good that your phone is working now, as for the data, i once forgot to remove encrypt before flash custom rom, but when enter TWRP it will ask for old password to decrypt. Just enter your old pass then connect to PC, or use TWRP file explorer to copy your data to sdcard
GVN.Gallus said:
Good that your phone is working now, as for the data, i once forgot to remove encrypt before flash custom rom, but when enter TWRP it will ask for old password to decrypt. Just enter your old pass then connect to PC, or use TWRP file explorer to copy your data to sdcard
Click to expand...
Click to collapse
None of the passwords I used worked.. I just factory reset it, thanks alot everybody. And now I will be more careful, don't flash anything weird. And backup!
I understood why I can't get the data back, if android fails at the encryption it jsut deletes everything!
My fone also in 9008 please can you guide me
I did the same what you have and it's on 9008 my flashing is successful but still my fone is not opening help me
m1shka said:
It's the official rom for the march ota.
The phone works, apparently it was encrypting everything... and now as I interrupted it, the encrypting failed and I lost all my data.....
Phone works but could have been better.
Before I reset the phone to factory, as i cannot use it yet, is there any way to get anything personal back? or is it gone gone and just factory reset?
What I see after boot, the phone resets every minute
https://drive.google.com/file/d/13sARZzlf3vJZK6Mx4hil6lsXRUl7-r-K/view?usp=sharing
The button that is hard to see says factory reset
Click to expand...
Click to collapse
How did you fixed i'm stuck in EDL?
SevenSlevin said:
If you are on "Qualcomm HS-USB QDLoader 9008" you will be able to flash stock fastboot firmware. Flash it using MiflashTool. Normally Miflashtool will recognized it as COMXX, where XX is the number of the port.
Click to expand...
Click to collapse
i am in Qualcomm HS-USB QDLoader 9008 but i can't flash, it doesn't matter if the phone is on fastboot mode or turned off (i can't even turn it on)
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.