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.
Related
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.
Help please
When I try to flash the edl rom folder I get a error in miflash "cannot receive hello packet" and "can not read from port com9".
I tried almost all of the different official miflash versions including betas and still the same error.
I've never had this problem with any other edl roms.
Rooted,twrp, and unlocked bootloader.
What am I doing wrong?
Thank you
You can try using the MiFlash and Qualcomm drivers in @jcadduono's EDL thread (pinned at the top of the Development subforum). Just make sure you uninstall MiFlash first, and also uninstall the Qualcomm drivers from Device Management (cant remember what it's called, QUSBBulk or something). Enable the viewing of hidden devices and check all categories, should be under Ports or USB.
To install the drivers, first go into EDL while plugged in. Extract the Qualcomm zip, then right click on the files that end with .inf, then click Install. There are 3.
If you have ever used Zadig, then its' WinUSB drivers must be removed too.
Another thing, power off the phone with cable unplugged from it, then go into EDL with VolUp+VolDown+Power (in that order). When the light at upper left of screen blinks red, you're in EDL. Just to be safe, restart EDL again with the button combo before plugging cable into phone.
I have no plans to flash stock Oreo, but I figured I could help anyway. I personally have never gotten errors with EDL, by doing the above.
AnonVendetta said:
You can try using the MiFlash and Qualcomm drivers in @jcadduono's EDL thread (pinned at the top of the Development subforum). Just make sure you uninstall MiFlash first, and also uninstall the Qualcomm drivers from Device Management (cant remember what it's called, QUSBBulk or something). Enable the viewing of hidden devices and check all categories, should be under Ports or USB.
To install the drivers, first go into EDL while plugged in. Extract the Qualcomm zip, then right click on the files that end with .inf, then click Install. There are 3.
If you have ever used Zadig, then its' WinUSB drivers must be removed too.
Another thing, power off the phone with cable unplugged from it, then go into EDL with VolUp+VolDown+Power (in that order). When the light at upper left of screen blinks red, you're in EDL. Just to be safe, restart EDL again with the button combo before plugging cable into phone.
I have no plans to flash stock Oreo, but I figured I could help anyway. I personally have never gotten errors with EDL, by doing the above.
Click to expand...
Click to collapse
I tried all of that and still getting same error.
Thank you though
I never had this problem
did ya ever get it sorted out? i ask bc i have been in edl hell with two boards, neither of which will accept a full flash. ive tried axon 7 edl tool, and the two most prevalent versions of miflash. the flashes go through, but do not completely flash back to stock. both boards are bl unlocked. one runs hot enough to cook an egg, the other works perfectly in TWRP, but has no touch in booted systems. ive spent two days flashing and resetting both. i say they dont completely flash bc even after wiping and cleaning files that are not system files persist on internal storage. maybe im missing something.
kitcostantino said:
did ya ever get it sorted out? i ask bc i have been in edl hell with two boards, neither of which will accept a full flash. ive tried axon 7 edl tool, and the two most prevalent versions of miflash. the flashes go through, but do not completely flash back to stock. both boards are bl unlocked. one runs hot enough to cook an egg, the other works perfectly in TWRP, but has no touch in booted systems. ive spent two days flashing and resetting both. i say they dont completely flash bc even after wiping and cleaning files that are not system files persist on internal storage. maybe im missing something.
Click to expand...
Click to collapse
well, i guess you didn't try EDL Tool?
Choose an username... said:
well, i guess you didn't try EDL Tool?
Click to expand...
Click to collapse
oh yes, many times. ive given up on all the edl files i have access to. i deleted all of them and am trying to find the ZTE provided ones. i have started redownloading the ones i can find. really, i want to go to a clean, unadulterated stock and start fresh. b32 doesnt work on either. i also am reinstalling axon7edltool and killer off the miflashes (i had two versions). full axon flash setup reset. atm, im trying to figure out how id apply mm b20 full properly from an old (necro'd by me today) thread. b15 and b32 fail. im going to re-evaluate every step of my installs and redownload all of my edls.
edit: after redownloading and installing miflash 2017.4.25 i flashed the initial twrp b29 edl. then, using twrp, i installed the stock recovery image. then, and only then, i was able to flash the b29 marshmallow full edl. good news? it all works. still hot though.
Update: making all my pointless updates in one day. lol.
I hard bricked the hot board experimenting with flashing a2017 edl (although when reflashed, it actually ran at normal temp). i managed to restore the serial of my other spare board, but still could not regain the imei. unless i discover a guide to pull imei from some hidden partition or qfuses or wherever it is stored locally, if such a thing even exists, it is doomed to not have service. im tempted to try to find somewhere or someone that can flash the board fully (like a proper factory reflash beyond what edl is. Qfil files for the axon 7 dont seem to exist. but i'd love to see someone flash one like that. maybe ill find a river of knowledge one day.
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.
hi guys, i have a oneplus 8 pro model phone. I tried to install OTA with a program called Fastboot Enchancer. However, after the installation was complete, my phone did not turn on again. Fastboot mode, and recovery mode won't boot. It doesn't open in edl mode, which is the only one I trust and use often. When I connect it to the computer, it does not respond at all. I have done recovery with edl mod many times with MSM tool, but now I can't. Looking forward to your help and ideas.
If your device no longer ever appears as a USB device and the screen is not helpful and you've tried all the "magic" gestures like holding down 3 buttons and standing on your head, then you'll have to do something different.
This kind of thing happens when something is broken, but it's not broken enough that it realizes that it's broken.
Life is easier when it's totally broken.
Possibilities are:
1) find the EDL test points inside and connect them while reseting.
2) disable data lines or clock to the flash so that it can't read anything and knows that it can only go to EDL.
3) JTAG to fix the problem or else just wipe the SBL so that it goes to EDL.
4) Use a USB UART. Maybe it's getting as far as u-boot and you can stop it and make it go to fastboot.
x_files_X said:
hi guys, i have a oneplus 8 pro model phone. I tried to install OTA with a program called Fastboot Enchancer. However, after the installation was complete, my phone did not turn on again. Fastboot mode, and recovery mode won't boot. It doesn't open in edl mode, which is the only one I trust and use often. When I connect it to the computer, it does not respond at all. I have done recovery with edl mod many times with MSM tool, but now I can't. Looking forward to your help and ideas.
Click to expand...
Click to collapse
Sometimes you have to hold VolUp + VolDown + Power for a long time before anything happen. As far as i know we dont know about any EDL points ant the op8 and we have the button combo anyway.
SInce you post on the op8pro forum you probably have a op8pro (obviously) and since you used fastboot i guess you simly hard bricked you phone beyond repair. Your phone RAM is overvolted and dead. And i dont think JTAG or anything else next to a motherboard swap can help you here.
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com
Renate said:
If your device no longer ever appears as a USB device and the screen is not helpful and you've tried all the "magic" gestures like holding down 3 buttons and standing on your head, then you'll have to do something different.
This kind of thing happens when something is broken, but it's not broken enough that it realizes that it's broken.
Life is easier when it's totally broken.
Possibilities are:
1) find the EDL test points inside and connect them while reseting.
2) disable data lines or clock to the flash so that it can't read anything and knows that it can only go to EDL.
3) JTAG to fix the problem or else just wipe the SBL so that it goes to EDL.
4) Use a USB UART. Maybe it's getting as far as u-boot and you can stop it and make it go to fastboot.
Click to expand...
Click to collapse
Is there any documentation of the OP8pro about the steps you mention? For example we had a discussion about edl points some days ago and the guy could not find them. And we came to the conclusion the wont help because we already have the button combo.
If the ram is overvolted and fried, which is most likely the case because anything else wont keep the phone away from EDL. Nothing can help to repair a dead ram.
I was listing 4 alternatives above.
Why do you think the RAM is dead?
EDL itself doesn't use any external RAM. There's a bit of static RAM on the chip and it uses that.