Database Users

A2017G bricked with Lineage OS and Twrp

Hullo,
I succesfully installed Lineage with no problems in the OS, but was unable to access TWRP as it asked for a decryption pattern that didn't seem to match the pattern I set on my phone. I then tried a password in the OS but this also didn't work in TWRP.
After checking the thread again, I found Unjustified had recommended the TWRP found in his bootloader, which I then downloaded and proceeded to install via fastboot. The installation appeared to go smoothly but after that I was unable to turn on my phone.
After pressing the power button I am presented with either the battery icon or the ZTE logo, which disspears after a few seconds followed by three flashing red lights. The last flashing light seems to be cut off part way.
I thought this might be a dead battery but even after charging for an extended period of time the result is the same.
Any help would be very much appreciated!

mvortex3710 said:
Hullo,
I succesfully installed Lineage with no problems in the OS, but was unable to access TWRP as it asked for a decryption pattern that didn't seem to match the pattern I set on my phone. I then tried a password in the OS but this also didn't work in TWRP.
After checking the thread again, I found Unjustified had recommended the TWRP found in his bootloader, which I then downloaded and proceeded to install via fastboot. The installation appeared to go smoothly but after that I was unable to turn on my phone.
After pressing the power button I am presented with either the battery icon or the Axon logo, which disspears after a few seconds followed by three flashing red lights. The last flashing light seems to be cut off part way.
I thought this might be a dead battery but even after charging for an extended period of time the result is the same.
Any help would be very much appreciated!
Click to expand...
Click to collapse
Your phone doesn't seem to be bricked at all.
That was a known issue many G users encountered...
Just boot into TWRP by pressing Power and volume + or choosing it from the bootloader warning screen and reflash the universal B15 N bootloader.
Reboot your phone and from now on it should boot every N rom just fine :fingers-crossed:
Good luck,
Martin

mischa_martin said:
Your phone doesn't seem to be bricked at all.
That was a known issue many G users encountered...
Just boot into TWRP by pressing Power and volume + or choosing it from the bootloader warning screen and reflash the universal B15 N bootloader.
Reboot your phone and from now on it should boot every N rom just fine :fingers-crossed:
Good luck,
Martin
Click to expand...
Click to collapse
I'm glad to hear it is quite common, but I should mention that the three lights persist when I try to load TWRP... I can only get as far as the ZTE logo.
The bootloader warning also hasn't shown since I attempted to flash TWRP as the phone appears to cut off after showing ZTE.
I will try an overnight charge in case the battery is completely empty and somehow slow charging. But any other suggestions are most welcome.
Kind regards,
James

mvortex3710 said:
I'm glad to hear it is quite common, but I should mention that the three lights persist when I try to load TWRP... I can only get as far as the ZTE logo.
The bootloader warning also hasn't shown since I attempted to flash TWRP as the phone appears to cut off after showing ZTE.
I will try an overnight charge in case the battery is completely empty and somehow slow charging. But any other suggestions are most welcome.
Kind regards,
James
Click to expand...
Click to collapse
You should try some button combinations like
Power + volume down
Power + volume down + volume up
And see how the device reacts
It helps connecting the device to a PC to look up in device manager to determine the mode its booted in

mischa_martin said:
You should try some button combinations like
Power + volume down
Power + volume down + volume up
And see how the device reacts
It helps connecting the device to a PC to look up in device manager to determine the mode its booted in
Click to expand...
Click to collapse
Thanks for the continued help.
I was just trying to connect it to the PC and appear to have made some headway, it started off showing up as qusb_bulk, but after repeatedly deleting that driver I returned to Qualcomm HS-USB QDLoader 9008 (COM6).
As I understand axon7root *should be able to write to the device at this point.
Does this device name give any indication as to the problem?
I wonder if miflash could be used on a G model to unbrick it. I'm happy to restart from stock files.

mvortex3710 said:
Thanks for the continued help.
I was just trying to connect it to the PC and appear to have made some headway, it started off showing up as qusb_bulk, but after repeatedly deleting that driver I returned to Qualcomm HS-USB QDLoader 9008 (COM6).
As I understand axon7root *should be able to write to the device at this point.
Does this device name give any indication as to the problem?
I wonder if miflash could be used on a G model to unbrick it. I'm happy to restart from stock files.
Click to expand...
Click to collapse
As you are in EDL now you have some options.
First I would try to flash a recovery and boot image that is proven to be working fine e.g official twrp https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715 or some A2017G stock boot.img
If that doesn't help you could get in contact with @jcadduono to be a tester for that miflash method. (As your device is already pretty badly bricked)
I don't exactly know how EDL flashing works if it depends on a exact GPT table or not.
But I can say that I flashed every single part of the A2017U bootloader except for NON-HLOS (modem) on my A2017G for each B29 and B15 and it worked just fine. So maybe we just have to exchange the modem file in the EDL package :silly:
If you don't want to take that risk you also could try sending it back to ZTE and hope they don't check the bootloader :fingers-crossed:
(Just a thought: Maybe if the EDL package won't work on your device it will be so heavily damaged ZTE can't check for bootloader unlock and accept it as a warranty case, but don't take that too seriously )
Regards,
Martin

mvortex3710 said:
Thanks for the continued help.
I was just trying to connect it to the PC and appear to have made some headway, it started off showing up as qusb_bulk, but after repeatedly deleting that driver I returned to Qualcomm HS-USB QDLoader 9008 (COM6).
As I understand axon7root *should be able to write to the device at this point.
Does this device name give any indication as to the problem?
I wonder if miflash could be used on a G model to unbrick it. I'm happy to restart from stock files.
Click to expand...
Click to collapse
If you are not afraid then try to use my package for A2017G with MiFlash: https://mega.nz/#!88BjXKhA!TnVSobBw5PkmShSqZ-Ni8MCCbnhJP2SWRNvvXqYHSjc

I really appreciate all this advice!
Looks like the MiFlash is promising. I was able to load the phone into MiFlash from the [EDL] thread. I have just tried the A2017G package provided by djkuz and will report back with any updates.
Just got to the mifavor screen, charging the battery from empty, although quickcharge appears to be functional again.
The charging battery logo is different from before so appears that this bootstack has done the trick.
The flashing red light has gone now, appears to be loading Lineage as before! I'm so grateful for all this help
However, now the unlock pattern is coming up as 'wrong pattern'. Is there anything that can be done? My settings appear to be saved as before (wallpaper and quick settings are the same).
I will attempt to reinstall twrp recovery and fix the lockscreen over adb. Thanks very much for the help. The brick has gone!!

A2017G Hard Brick - no recovery, only DFU

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

Can't flash EDL rom MiFavor UI 5.2 BETA please help. EDL errors!

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.

Hard Bricked OnePlus 6t Tmobile Version

I have a Tmobile OnePlus 6T, hard bricked.
Mine gives the usb device malfunctioned error. I have installed, uninstalled and reinstalled the qualcomm usb drivers. It recognizes the phone in the device manager as USB DEVICE DESCRIPTION FAILED. The MSM tool wont recognize it, and my phone wont boot in any other mode except EDL. It will not boot to bootloader or anything. Funny thing is, all I was trying to do was convert the T-Mobile version to international which I've done before. During that process, it hung at "recording downloading time". I let it go for 20 minutes, according to the guide it is supposed to take 5. I canceled the process, (I had done this one other time before, and it booted just fine) and now nothing works. I am not a noob at this. I can restore through fastboot if I could get it to boot into fastboot. I could restore through recovery via sideload if I could get it to boot into recovery. Please help.
*Moderators, I have searched high and low through the forums and I cannot find a thread with this problem that has any steps to solve it. I found one thread with a similar description but it is a year old, has no replies and the author managed to fix his phone on his own, with no description of how he did so.*

Txdude35 said:
I have a Tmobile OnePlus 6T, hard bricked.
Mine gives the usb device malfunctioned error. I have installed, uninstalled and reinstalled the qualcomm usb drivers. It recognizes the phone in the device manager as USB DEVICE DESCRIPTION FAILED. The MSM tool wont recognize it, and my phone wont boot in any other mode except EDL. It will not boot to bootloader or anything. Funny thing is, all I was trying to do was convert the T-Mobile version to international which I've done before. During that process, it hung at "recording downloading time". I let it go for 20 minutes, according to the guide it is supposed to take 5. I canceled the process, (I had done this one other time before, and it booted just fine) and now nothing works. I am not a noob at this. I can restore through fastboot if I could get it to boot into fastboot. I could restore through recovery via sideload if I could get it to boot into recovery. Please help.
*Moderators, I have searched high and low through the forums and I cannot find a thread with this problem that has any steps to solve it. I found one thread with a similar description but it is a year old, has no replies and the author managed to fix his phone on his own, with no description of how he did so.*
Click to expand...
Click to collapse
The other of the previous post probably figured out how to get the device recognized by the computer. I would say see if you can use another computer/cable and see if it still has the same issue, if it does i'd probably be concerned about the device health. If the issue is gone on the other PC though then you likely have something wrong with either drivers or usb hardware on your PC. I would assume you've already tried using a different USB cable and port with your current PC.

Just another victim of the android 12 update, hoping for a revival

So im gonna start off by saying that im just some dumb 18 year old and have never actually posted to ask for help, only reading other peoples situations to try to figure out my own.
but introductions aside im just gonna jump in to everything wrong with my oneplus 8 pro (global)
I was on the OOS 12 beta for a while, ive been way too lazy to change it back since ive been occupied by other stuff.
I was using magisk and decided to do some fun shenanigans with it.
I get into bootloop after flying to close to the sun with modules - a common occurrence.
so I try to switch to a custom rom since I was gonna reset anyway.
I download CR droid's recovery and main rom, went into fastboot and flashed the recovery.
I notced that whenever my phone was plugged into the computer, the options would rapidly switch on fastboot's end
when I tried to boot to recovery after flashing, it would only return to fastboot
confused I thought that maybe the recovery was bad and try another rom, no dice
i submit defeat and go to msm tool to fix the issues
I get that "Sahara communication failed" error so I hold down the volume up + power for 13 seconds before trying again.
it flashed smoothly
after getting sad at all the bloatware that was on oxygen OS after a full reset, I get the motivation to try using a custom rom again, this time using a different rom.
same weird fastboot behavior
I was unable to go into recovery
I then tried downloading stock firmware to flash it manually
fixed nothing
I delete the boot and recovery partitions and flash them again, still no dice
I even make a partion called fart, before remembering that I do not know the partition structure of android so i Ctrl+C out before it makes the partition
I go back to msm tool again in shame
"Unknown Target Device"
I reinstalled drivers
switched computers and cables
changed the source of my drivers
nothing fixed this error
and every time I would try to do anything it would go directly back to fastboot.
I try reflashing partitions in this broken fastboot mode and it would only flash if I unplugged, selected reboot bootloader, and plugged it back in
I would then try to fastboot boot into TWRP or other recoveries i downloaded
they would shut off the phone
I remember a/b partitions exist so I switch over between them and try to flash stock OOS again
after more fiddling and nothing working, I noticed some more weird traits of fastboot
twrp did boot directly after switching my main slot, not specific which one just if the slot was changed.
the "this device has an unlooked bootloader" message did not appear
only on slot a would the oneplus logo show up on boot
again every option I would click would take me right back to fastboot.
I wait a day for the phone to die so I could use EDL that way, at this point the twrp method randomly stopped working so I couldn't go into edl that way.
"Unknown Target Device Param Preload"
and like I know Param Preload is a common error but nowhere could I find information on the unknown target device part.
the phone still vibrates if I hold the power and vol+
it just vibrates in a loop as if it keeps rebooting, probably fastboot just selecting the start key over and over when I hold it down.
vol- and power do nothing, and did nothing for the entirety of this story.
is there any chance of saving my poor instantnoodle professional?
## edit for people googling this
the problem I was having was that I didn't set the "target" button on the MSM tool correctly, so make sure its set to O2 or your appropriate reigon

1. Stop fastboot flashing with A12 or if you are on A12.
2. Read this: https://forum.xda-developers.com/t/...ro-8t-9r-with-oxygenos-12-coloros-12.4426167/
3. Rescue your phone using this: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4084953/
4. Stay on OOS11 (Most custom roms INCLUDING A12 custom roms require OOS11 anyway.)
5. There is not much bloat on a OOS11 rom IMO but you can always use a debloater.

xtcislove said:
1. Stop fastboot flashing with A12 or if you are on A12.
2. Read this: https://forum.xda-developers.com/t/...ro-8t-9r-with-oxygenos-12-coloros-12.4426167/
3. Rescue your phone using this: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4084953/
4. Stay on OOS11 (Most custom roms INCLUDING A12 custom roms require OOS11 anyway.)
5. There is not much bloat on a OOS11 rom IMO but you can always use a debloater.
Click to expand...
Click to collapse
Maybe I should clear on what i have tried. since I have read both articles before I made this post (i scanned through them again once you sent them tho)
Ive tried...
The unbricking Msm qualcomm 9008 tool
ive used it a ton in the past
ive switched copmputers, cables, and the qualcomm driver, as well as reset the phone several times
also yeah im not touching oos12 after this with a 9 foot pole, but is there a way of knowing wether I can save it or if its too late and the motherboard has been fried.

NatunaSushi said:
Maybe I should clear on what i have tried. since I have read both articles before I made this post (i scanned through them again once you sent them tho)
Ive tried...
The unbricking Msm qualcomm 9008 tool
ive used it a ton in the past
ive switched copmputers, cables, and the qualcomm driver, as well as reset the phone several times
also yeah im not touching oos12 after this with a 9 foot pole, but is there a way of knowing wether I can save it or if its too late and the motherboard has been fried.
Click to expand...
Click to collapse
Okay i guess this is another situation here. You are not bricked like the other peoplke as far as i can see because there devices are completly bricked. No connection to pc or vibrating at all.
Since you used MSM tool before it should work IMO. Does your pc regonize the phone? Did you tried to switch usb ports? Did you tried other versions of msm tool(eu, older verions, etc)?
Please make sure to follow all MSM instructions closely.

xtcislove said:
Okay i guess this is another situation here. You are not bricked like the other peoplke as far as i can see because there devices are completly bricked. No connection to pc or vibrating at all.
Since you used MSM tool before it should work IMO. Does your pc regonize the phone? Did you tried to switch usb ports? Did you tried other versions of msm tool(eu, older verions, etc)?
Please make sure to follow all MSM instructions closely.
Click to expand...
Click to collapse
after a week of fiddling I DID figure out the issue
unsupported Target unknown was refering to the fact that I had the MSM tool set to Target mode, which I assume tries to set the region according to what the current device has. After selecting that to O2 for the global models, the flash worked fine. I ended up coming across some C stock of a google pixel 3a and will try messing with that so I dont have to go a while without calls or texts. Glad to know I learned some bit of responsibility from this excursion.