well, im not a noob but i feel like one atm. my axon 7 is brieked and EDL and MiFlash cannot seem to resurrect it. i have tried the axon7 Flash tool and all of the edl files within to no avail. the phone shows the splash screen then reverts to edl mode. bootloader was/is unlocked. but i literally cannot get it working again. its a a2017u. i actually have two axon 7, so i could swap boards and have a working phone. i imagine ZTE wouldn't honor warranty in this scenario. (purchased second hand, had for about a week.)
kitcostantino said:
well, im not a noob but i feel like one atm. my axon 7 is brieked and EDL and MiFlash cannot seem to resurrect it. i have tried the axon7 Flash tool and all of the edl files within to no avail. the phone shows the splash screen then reverts to edl mode. bootloader was/is unlocked. but i literally cannot get it working again. its a a2017u. i actually have two axon 7, so i could swap boards and have a working phone. i imagine ZTE wouldn't honor warranty in this scenario. (purchased second hand, had for about a week.)
Click to expand...
Click to collapse
Are you sure you're not on DFU mode? DFU looks kinda like EDL but you basically can't do anything there. There are a couple of ways that seem to work, the surefire one is taking the phone apart and shorting a test contact, then turning the phone on or whatever (4th category brick repair guide, check it out). If you do that you might as well change the board and be done with it
The other one is not taking it apart, let the phone discharge, then hold volume down + power (I don't know if you have to plug it, but if you have to, I guess you should connect it to the PC) and you MIGHT get to FTM mode. You should have ADB there, so you just issue 'adb reboot edl' and you can use MiFlash with one of the files the Russians have (check the 4th categ brick repair guide. Click on 'MiFlash and drivers' and it will redirect you to 4pda. You don't need to translate the page, just open the spoilers until you find a file called A2017U-FULL-EDL or something like that (has to say FULL EDL and be for the U of course)
I have used the first method on an A2017G. don't know about the FTM way
Well, I bit the bullet and swapped the back housings. I now have a functional grey a2017u.
Update: I'm fairly sure its in DFU mode. Prior to that brick,, the screen had stopped responding across a band in the middle. Prior to flashing carbon ROM, it worked fine. After, that. The two are likely unrelated. Eventually, I will buy a third axon 7 for parts, but right now, I'm $550 in to these two. Including my dumb idea to duracoat it. Still, Axon 7 is the best device I have owned. Sure there are better socs, but if this was the only phone I'd have for the next year, I'd be totally okay with it. Thank you for the assist in making the choice to Frankenstein. ;/
Also, for posterity, the ois on the camera freaked out when the band of non responsiveness occurred
Well this is late but I just unbrick an axon 7 that I couldn't get past dfu mode or fastboot. Here is a clue get edl for axon, fastboot flash system system.img, fastboot flash boot boot.img... oh yes you don't need miflash you can flash from fastboot individually. There is a flashall function in fastboot but don't know the code.
Maxemus_04 said:
Well this is late but I just unbrick an axon 7 that I couldn't get past dfu mode or fastboot. Here is a clue get edl for axon, fastboot flash system system.img, fastboot flash boot boot.img... oh yes you don't need miflash you can flash from fastboot individually. There is a flashall function in fastboot but don't know the code.
Click to expand...
Click to collapse
lol if you are DFU bricked you don't have anything but DFU mode, that's the whole point of a DFU brick. you don't have fastboot or recovery mode and certainly not edl
@kitcostantino
If you 100% sure that this is a dfu brick then this thread guide will save your device
https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898
Good luck!
You don't need the 4th category repair guide. You can just do this:
Hold down power and volume down until you boot into factory test mode.
It should then be recognized as an adb device and you can do "adb reboot edl" to boot into edl mode, where you can use miflash to unbrick.
I will pull it out and see here in a few. Thank you both for the advice. ZTE told me for $80 they will replace it, but i like the idea of resurrecting it before I send it in.
The camera was doing the OIS freakout thing, so it may have been that phones destiny anyway. the screen was only half displaying as well, which I doubt is from incompatible edl flash (which is how I arrived at dfu), but hey, anything is possible.
bkores said:
You don't need the 4th category repair guide. You can just do this:
Hold down power and volume down until you boot into factory test mode.
It should then be recognized as an adb device and you can do "adb reboot edl" to boot into edl mode, where you can use miflash to unbrick.
Click to expand...
Click to collapse
It's not that easy, I suspect that there's another factor at play there because some people can enter FTM when they're bricked and some cannot. Out of 10 people that I told to try that, only 1 could enter FTM after draining the battery and all
Choose an username... said:
lol if you are DFU bricked you don't have anything but DFU mode, that's the whole point of a DFU brick. you don't have fastboot or recovery mode and certainly not edl
Click to expand...
Click to collapse
I had fastboot. I lost edl some how. I wou I'd like to get edl back tho. I think I lost it flashing a2017g.
well, here i go necro-ing an old thread. i actually didnt end up doing the unbrick properly. i did manage to get mi flash to see the phone. i attempted all of the a2017u EDL files i had to no avail. somehow, the oreo beta edl file worked like a month or so ago. found out my flex cable for buttons is damaged, and also that my vol buttons and power buttons are toast. fortunately, all of those parts are on ali express, so if i cant grab a broken a2017 on ebay (working on that now although someone outbid me) for $45, i can have it up and running again fully. but gold....again. lol.
Edit: something i had forgotten, my screen is not responding correctly to touch. the bottom half cannot sense where i am touching it. @Choose an username... is it possible that this is just from mis-matched firmware, or is it possible that with no physical damage or stimuli that my screen is broken/borked? thank you, man.
kitcostantino said:
well, here i go necro-ing an old thread. i actually didnt end up doing the unbrick properly. i did manage to get mi flash to see the phone. i attempted all of the a2017u EDL files i had to no avail. somehow, the oreo beta edl file worked like a month or so ago. found out my flex cable for buttons is damaged, and also that my vol buttons and power buttons are toast. fortunately, all of those parts are on ali express, so if i cant grab a broken a2017 on ebay (working on that now although someone outbid me) for $45, i can have it up and running again fully. but gold....again. lol.
Edit: something i had forgotten, my screen is not responding correctly to touch. the bottom half cannot sense where i am touching it. @Choose an username... is it possible that this is just from mis-matched firmware, or is it possible that with no physical damage or stimuli that my screen is broken/borked? thank you, man.
Click to expand...
Click to collapse
well, i don't know, but it is possible. I recall that OrdenKrieger put A2017U touchscreen files on NucleaROM to try something, and it ended up borking touch for everyone that was using it until he issued a fix.
Try installing TWRP and booting into it. if the screen works there then it's fine.
Also check the connector, it might be badly seated
thank you, man. its still factory installed as i havent taken it apart fully, but ill check it anyway. im thinking something doesnt translate from model to model and the beta i flashed was definitely for the a2017 but modded for a2017u. however, the last firmware i flashed prior (that stuck my phone in dfu mode) was for the a2017, so that part still makes sense. really, just knowing its possible for the firmware to do that in any instance gives me enough hope to justify throwing $40-50 at it. lol.
EDIT:
So ive tried to flash from the leaked stock 8.0 build to anything else and realized two things.
First, my axon 7 is definitely flashed as an a2017 and not an a2017u.
Second, my axon 7 cannot load the hello file or any firehose files in the various toolkits. the edl axon toolkit sounded promising, but so far, no dice with the edl for a2017u b15 and b19. is there like a type o negative EDL file for the axon 7 ?
kitcostantino said:
thank you, man. its still factory installed as i havent taken it apart fully, but ill check it anyway. im thinking something doesnt translate from model to model and the beta i flashed was definitely for the a2017 but modded for a2017u. however, the last firmware i flashed prior (that stuck my phone in dfu mode) was for the a2017, so that part still makes sense. really, just knowing its possible for the firmware to do that in any instance gives me enough hope to justify throwing $40-50 at it. lol.
EDIT:
So ive tried to flash from the leaked stock 8.0 build to anything else and realized two things.
First, my axon 7 is definitely flashed as an a2017 and not an a2017u.
Second, my axon 7 cannot load the hello file or any firehose files in the various toolkits. the edl axon toolkit sounded promising, but so far, no dice with the edl for a2017u b15 and b19. is there like a type o negative EDL file for the axon 7 ?
Click to expand...
Click to collapse
Try the EDL tool (bat by djkuz). that one is much better than miflash and will give you more verbose errors too
Choose an username... said:
Try the EDL tool (bat by djkuz). that one is much better than miflash and will give you more verbose errors too
Click to expand...
Click to collapse
i actually did. spent an hour and a half trying to flash using the edl tool saturday it errors trying to load the firehose programmer file. i unpacked (unzipped) the tool to
C/axon EDL TOOL/ .. i tried b15 nougat after b19 nougat failed multiple times. the issue is the phone legitimately thinks it is an a2017 , not an a2017u and its on the 8.0 beta, and im trying to go back to a2017u firmware, in either case, i will have one workinh, unbroken axon 7 by the end of the day if all goes well when i get home from work today as my board in my dd, unlike my housing and my screen, is still good. lol
kitcostantino said:
i actually did. spent an hour and a half trying to flash using the edl tool saturday it errors trying to load the firehose programmer file. i unpacked (unzipped) the tool to
C/axon EDL TOOL/ .. i tried b15 nougat after b19 nougat failed multiple times. the issue is the phone legitimately thinks it is an a2017 , not an a2017u and its on the 8.0 beta, and im trying to go back to a2017u firmware, in either case, i will have one workinh, unbroken axon 7 by the end of the day if all goes well when i get home from work today as my board in my dd, unlike my housing and my screen, is still good. lol
Click to expand...
Click to collapse
So, you can't enter other modes? If you could get into Fastboot you should be able to flash TWRP and install stock
well, now i have successfully swapped my good board onto my 'good' screen, but touch is not working correctly. i dont know which component controls the touch itself. booted into the OS, the screen responds to no touch at all. booting into TWRP yields many vibrations, but touch works. the screen is possibly bad. i cant find any connection that i could have missed in teardown vids that control touch response. im seriously confused.
After all is said and done, I have not one but two axon 7 paperweights. Touchscreen is non-functional on the not broken one. At this point, I'm fairly confident it's a hardware issue with my spare, formerly bricked, axon 7 screen wise. if there is a specific point on the phone that is critical aside from the screen cable and screen itself that could affect touch response, I'm all ears. For now, I'm phoneless-ish. Still have a Droid turbo and an s4, neither of which work well with tmob. gonna give up for today.
kitcostantino said:
After all is said and done, I have not one but two axon 7 paperweights. Touchscreen is non-functional on the not broken one. At this point, I'm fairly confident it's a hardware issue with my spare, formerly bricked, axon 7 screen wise. if there is a specific point on the phone that is critical aside from the screen cable and screen itself that could affect touch response, I'm all ears. For now, I'm phoneless-ish. Still have a Droid turbo and an s4, neither of which work well with tmob. gonna give up for today.
Click to expand...
Click to collapse
Damn what a mess. If I was selling my Axon 7 I wouldn't give it to you... The poor thing ??
I guess you should just take it apart and connect it again, i don't know. maybe check the connectors, see if any contacts are broken.
Choose an username... said:
Damn what a mess. If I was selling my Axon 7 I wouldn't give it to you... The poor thing ??
I guess you should just take it apart and connect it again, i don't know. maybe check the connectors, see if any contacts are broken.
Click to expand...
Click to collapse
the funny thing is the bent broken screen still worked fine with touch and display. just the outer glass was tweaked. the screen cable is under the battery. i pulled the battery to look at it on the borked one. and pulled apart the 'good one, checked connections, and confirmed they were all tight. the screen cable isnt swappable. i disassembled the displayf from the midframe to confirm. what i learned: if anyone ever has to do a screen only repair, there is a thin tape that holds the screen to the midframe. a blade run alongside that edge of the midframe frees the display from the mid frame.
Hey Folks, i just bricked My Axon 7 some Days ago. It started randomly a reboot which i can't abort anymore. Everytime the Device get's a Charge does it start again. I can't enter TWRP or Fastboot (Reboots after a few Seconds). Same for the Flash Mode. It is now completely discharged and i don't know how to recover it. Any Ideas?
Think i can't fix this, but asking here don't hurts... :angel:
4th grade unbrick guide here in the Forums. That helped me after i cannot access any Mode. No Flash Mode, No EDL, No USB, No Qualcomm Loader. Axon 7 too.
https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898
HighSierra1014 said:
4th grade unbrick guide here in the Forums. That helped me after i cannot access any Mode. No Flash Mode, No EDL, No USB, No Qualcomm Loader. Axon 7 too.
https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898
Click to expand...
Click to collapse
Lol. I made a guide based on that one but updated, called DFU unbrick, because everybody had to read my comments there anyways to be able to do it. Not sure why everyone still uses the old one ?
@Miustone: If you want, you can try an EDL cable first. A lot of people say that they could get out of DFU that way. (assuming that you can get into EDL/DFU that is). Google my guide, it's called "DFU unbrick", if the EDL cable doesn't work
Thanks Guys! I will take a look on the DFU unbrick and the EDL Cable. At least a blink of Hope for this great Device... Still good as new, would be sad to use it just as a golden Sculpture lol
Miustone said:
Hey Folks, i just bricked My Axon 7 some Days ago. It started randomly a reboot which i can't abort anymore. Everytime the Device get's a Charge does it start again. I can't enter TWRP or Fastboot (Reboots after a few Seconds). Same for the Flash Mode. It is now completely discharged and i don't know how to recover it. Any Ideas?
Think i can't fix this, but asking here don't hurts... :angel:
Click to expand...
Click to collapse
Hey, sorry for asking but how did you brick it? I am thinking about installing a custom ROM, rooting etc and I would just like to know if it was something in specific so I can stay away from it. Cheers.
i own a zte blade z max z982 model and i am stuck in a hard brick, the phone ONLY goes into DFU mode and none of the currently available fixes do anything, the dfu to edl tool shows "disconnected" when its listed under the device, the EDL tool is able to flash recovery or boot but then goes back into DFU afterwards, i can't find stock firmware online to save my life, and i don't have the cash atm to get another phone, i desperately need a fix, any help would be masssively appreciated.
Jpen91 said:
i own a zte blade z max z982 model and i am stuck in a hard brick, the phone ONLY goes into DFU mode and none of the currently available fixes do anything, the dfu to edl tool shows "disconnected" when its listed under the device, the EDL tool is able to flash recovery or boot but then goes back into DFU afterwards, i can't find stock firmware online to save my life, and i don't have the cash atm to get another phone, i desperately need a fix, any help would be masssively appreciated.
Click to expand...
Click to collapse
did you ever find a fix for this?
The official way to unlock the bootloader has been unavailable for just over a year, since LG ended their developer program as of 01/01/2022 and you now can't apply for an unlock file anymore.
Searching for a work-around I found this: https://drfone.wondershare.com/unlock/lg-bootloader-unlock-how-to.html
I have tried as best I can to follow these instructions and fail because I can't get my device to enter Qualcomm EDL 9008 mode by any keypress combination, or ADB or fastboot command from OS (Windows and Linux tested). I suspect my edition of the phone doesn't have EDL, or the method of accessing it is not correct in all instructions I've seen. I can get in to fastboot, and LG download mode (which shows in device manager as LGE AndroidNet USB Serial Port), but not Qualcomm ADL 9008 mode which should show in device manager as Qualcomm HS-USB QDLoader 9008.
I'd rather not brick my device, but it is a spare, and I thought I'd try and soup it up with a newer AOSP-Extended before maybe gifting to my partner.
AND!! I'm suspicious of the instructions in the first place! At the bottom, it advertises a piece of software to something related. As a Windows technician in my day job, I see this too often, can't solve bluescreen error 0x123abc45 just download this trialware to fix your PC!!
Try "adb reboot edl" from adb, anyway yes that site is not good
Hey, thanks for coming back to me.
I have tried that, but have just repeated right now to remind myself the outcome, which is, phone reboots as normal. Does not enter EDL mode. Windows and Linux.
Cheers
Anne-d'Royd said:
I suspect my edition of the phone doesn't have EDL, or the method of accessing it is not correct in all instructions I've seen
Click to expand...
Click to collapse
Isn't the method to access EDL on the G6 through shorting two pins on the mobo?
LG G6 TestPoints for EDL Mode (9008)
Simple af. Just short them. For incase that doesn't work;
forum.xda-developers.com
Also, that guide is just a re-worded one for the LG G7 One, not the G6, which use different processors. An engineering bootloader for the LG G6 has not leaked yet, and likely will not leak since it's been 6 years.
LG G7 One Bootloader Unlock [How-to]
Disclaimer: Do this at your own risk, blah blah blah. Brick your phone its on you.. Just a quick tutorial on bootloader unlocking the G7 One. Lots of the info in here can be found in other areas of XDA. *****Read full post before...
forum.xda-developers.com
Hey thanks for the input!
I'm reluctant to go in since the glass is splintered on the back of the unit, that's the main reason I changed my phone nearly 2 years ago.
There are enough varying instructions of there to suggest that EDL on that phone can be accessed by I think five methods.Two methods involve commands from PC, one method is button press combinations whilst connected to PC, another is a special EDL cable and then lastly, the test points.
The guides I've seen explaining the keypress routine says it works for a range of LG phones with qualcomm chips, including the G6 but I have they're wrong. Example:
Dont bother with dr phone. I previously used it to backup my phone. It wanted me to pay to restore but all it did was create a zip of my internal storage.
I think it is highly unlikely that they have a secret way of unlocking one of the hardest to unlock bootloaders on a phone.