Database Users

2017g DFU mode investigation

This thread is for users who have a 2017g model that is stuck in DFU mode.
If you would like to assist in the investigation, please reply here. I'll be sending links to test programs to try to diagnose and repair devices.
With any luck, we can get the devices back to normal within a few days.

Reserved

I had this problem, but luckily I could send it back and get a new one on warranty. I was very careful when unlocking the new one ?
Skickat från min ZTE A2017G via Tapatalk

Can more people who are stuck in DFU mode PLEASE contact tennear? I worked with him before and he really knows what he is doing. He's the only one who I think could be able to help you restore your device to working state.
Please help him, so A2017g users like me know they have a trick up their sleeve in the case the BL unlock goes awfully wrong
Thank you.

@tennear keep us updated. I'm planning to give up root in order to get this week's B08 update and i'm not sure if flashing the system with twrp will go smoothly.
Thank you for you work and dedication to help other people.

I have two people that are able to help now. But more is always better. If you have a G model and you can access DFU (regardless if you are bricked or not), you can help test. Linux is my preferred OS, but I can also build for Win64 if needed.

razorsbk said:
@tennear keep us updated. I'm planning to give up root in order to get this week's B08 update and i'm not sure if flashing the system with twrp will go smoothly.
Thank you for you work and dedication to help other people.
Click to expand...
Click to collapse
If you are Lock bootloader and have TWRP you CAN flash B08 , just need to mod. The updater_script in other for the B08 to be install, but YOU WON'T BE ABLE TO ROOT unless you unlock bootloader and I'll be posting something about that later today or coming days.

DrakenFX said:
If you are Lock bootloader and have TWRP you CAN flash B08 , just need to mod. The updater_script in other for the B08 to be install, but YOU WON'T BE ABLE TO ROOT unless you unlock bootloader and I'll be posting something about that later today or coming days.
Click to expand...
Click to collapse
I'm rooted without unlocking bootloader (tenfar's method).
So you are saying I can flash the upcoming update safely from TWRP by editing updater script and removing getprop & assertprop lines from it?
I also have system modifications.
Sent from my ZTE A2017G using Tapatalk

razorsbk said:
I'm rooted without unlocking bootloader (tenfar's method).
So you are saying I can flash the upcoming update safely from TWRP by editing updater script and removing getprop & assertprop lines from it?
I also have system modifications.
Sent from my ZTE A2017G using Tapatalk
Click to expand...
Click to collapse
Ok, I don't want to go off topic here, but YES you'll need to edit updater_script and look and bookmark if possible my thread about Updates ,I'll be posting B08 as soon the full update hits ZTE site. If you want to talk about Updates post there , so we can keep this thread on topic.

I agree. See you there.
Sent from my ZTE A2017G using Tapatalk

tennear said:
I have two people that are able to help now. But more is always better. If you have a G model and you can access DFU (regardless if you are bricked or not), you can help test. Linux is my preferred OS, but I can also build for Win64 if needed.
Click to expand...
Click to collapse
I have a G model and I am using Linux (based on ArchLinux). I can use Windows 10 if needed, so OS should not be a problem.
So if you need some testing, I can help

Hi, I would love to help,
I have a G model and I have TWRP and unlocked bootloader but u can access DFU mode
I am using windows

I'm afraid that I have not been successful getting out of DFU mode. I have tried several things, but the device refuses to switch into EDL mode.
According to the user who has a bricked device, he got bricked by running "axon7backup -d" without any image files present. The tool wrote something to both boot and recovery partitions. I don't know what that something is -- zeros, random data, ... who knows.
So it seems that if you are careful and only flash recovery properly, the device should not brick. But I cannot test -- someone else will need to confirm.
Now that this investigation is concluded, I will be posting my own tool shortly.
Always remember: to avoid bricking your device, never flash both boot and recovery at the same time.

^^Is there even a reason to flash the boot/kernel? The main reason why most of us would use the axonbackup tool is to flash twrp.

gpz1100 said:
^^Is there even a reason to flash the boot/kernel? The main reason why most of us would use the axonbackup tool is to flash twrp.
Click to expand...
Click to collapse
The only reason why tenfar had the tool to Flash boot is because he had the boot sign and pre-rooted for Lock bootloader units.

^^Got it. I thought about keeping the BL locked, but decided unlocking it would cause fewer headaches and be less restrictive.

That is correct, there is no real reason to flash your boot partition now that the images provided by tenfar are not compatible with the latest updates from ZTE.
However, the real danger remains: if you run "axon7backup -d" with no files to write, it is reported to write bad data over both boot and recovery and brick your device.
I highly recommend using my tool instead. I can guarantee that it will never write both boot and recovery in the same session.

tennear said:
That is correct, there is no real reason to flash your boot partition now that the images provided by tenfar are not compatible with the latest updates from ZTE.
However, the real danger remains: if you run "axon7backup -d" with no files to write, it is reported to write bad data over both boot and recovery and brick your device.
I highly recommend using my tool instead. I can guarantee that it will never write both boot and recovery in the same session.
Click to expand...
Click to collapse
The command help indicates -d is to dump only. My understanding is nothing is written to the phone when reading from it? Are you saying that's not the case?

gpz1100 said:
The command help indicates -d is to dump only. My understanding is nothing is written to the phone when reading from it? Are you saying that's not the case?
Click to expand...
Click to collapse
Yes, that is what I am saying. According to a PM that I received, the user ran "axon7backup -d" without any other files in the directory. The tool flashed something to both boot and recovery partitions. No idea what it flashed. But then the device was bricked. And because 2017g cannot enter EDL mode directly, there is no way to unbrick.

hi i have china version of axon 7 A2017 and have the same problem with my device (stuck in dfu mode after Flashing SuperSU).Will there ever be a way to fix this problem? I am depered :crying:.

Total idiot here needs help rooting.

Hey everyone, I'm currently on B29, non-rooted and locked bootloader.
I would like to root and make my up to stock 7.1.1. The issue I'm having, is that there is an absolute ton of conflicting info and ways to do things that I'm just not sure at all how to proceed.
What I've tried so far was starting with this guide: https://forum.xda-developers.com/axon-7/how-to/newbies-guide-to-unlocking-rooting-axon-t3496234. But the tool from step three wouldn't download and the hosting site threw a ton of popups and redirects at me (yes, I have uBlock).
Then continuing through that same thread I found this tool https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254 that is apparently safer, but I have no idea how to use it.
Then I started hearing about this EDL mode stuff https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514 which I attempted to do when I tried the Axon7Toolkit yesterday, but my phone just wouldn't go into EDL mode (or I just had no idea how to tell if it was or not) and the MiFlash thing didn't do anything.
So my real questions are:
1: Which version of TWRP and SuperSU do I need?
2: How do I unlock the bootloader?
3: What steps should I take so that I eventually end up rooted on stock 7.1.1 (currently still on B29)?
Thanks!

umm shouldn't this go on questions and answers?
Just one thing: You mostly can't tell if your phone is in EDL mode. Some axons will turn the notif light red, some will not do s**t, like mine. Just do whatever the guide says. On A2017G you use "adb reboot edl" and the phone just goes into EDL mode. After that you have to use axon7tool but I'm not sure if it works for nougat...
If the phone is not on EDL mode then the worst thing that can happen is that you get an error. Axon7tool doesn't do anything unless the phone is on EDL, so you pretty much can't mess up

Choose an username... said:
umm shouldn't this go on questions and answers?
Just one thing: You mostly can't tell if your phone is in EDL mode. Some axons will turn the notif light red, some will not do s**t, like mine. Just do whatever the guide says. On A2017G you use "adb reboot edl" and the phone just goes into EDL mode. After that you have to use axon7tool but I'm not sure if it works for nougat...
If the phone is not on EDL mode then the worst thing that can happen is that you get an error. Axon7tool doesn't do anything unless the phone is on EDL, so you pretty much can't mess up
Click to expand...
Click to collapse
Sorry, I thought it would go here because it was a question about the guides. I'm not sure if a mod would move this but I don't think I should repost the same question in another section?
But yeah, about the EDL, I have the U and I ran "adb reboot edl" but MiFlash didn't see anything and it wasn't showing up when I did "adb devices" so I wasn't sure what was going on. Do you have any guides or anything you'd recommend?

CookedBooks said:
Sorry, I thought it would go here because it was a question about the guides. I'm not sure if a mod would move this but I don't think I should repost the same question in another section?
But yeah, about the EDL, I have the U and I ran "adb reboot edl" but MiFlash didn't see anything and it wasn't showing up when I did "adb devices" so I wasn't sure what was going on. Do you have any guides or anything you'd recommend?
Click to expand...
Click to collapse
No access with adb or fastboot in edl mode. It' strictly for use with low level tools like miflash. Your environment will make the difference. I couldn't get miflash on my main pc (win8/x64) to see the device. Likely an issue of drivers even through the proper driver is installed, and phone is showing up properly in device mgr. I used a spare pc with a relatively fresh win10/x64 install. Miflash saw the phone right away.
Also, for edl mode, my u model will just flash the led once then go blank.
To achieve your goal, easiest to probably just unlock the bootloader with the B29, then mess around with updating to latest.

gpz1100 said:
To achieve your goal, easiest to probably just unlock the bootloader with the B29, then mess around with updating to latest.
Click to expand...
Click to collapse
Okay thanks, I'll give it a go again. Would you be able to clarify which version of TWRP I should use? I'm thinking 3.0.2-0 but I've seen other guides mention different versions and other people say the wrong version is going to be a massive headache.

For the initial unlocking, you'll have to use the signed twrp. I don't recall the exact version, but whatever is included in the unlock thread. Once unlocked, then you can flash the latest 3.1.something.

gpz1100 said:
For the initial unlocking, you'll have to use the signed twrp. I don't recall the exact version, but whatever is included in the unlock thread. Once unlocked, then you can flash the latest 3.1.something.
Click to expand...
Click to collapse
Okay thanks. As for the rest, am I correct in my understanding that I need to:
First: Use Axon7tool to flash TWRP https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254
Second: Unlock bootloader
Third: flash the official 7.1.1

Hmm you could use a7tool to flash TWRP, then install the twrp app and upgrade to 3.1 or whatever, and then get to nougat after some backups. I'm not sure but I think tenfar's twrp FUBAR'd some partitions when you tried to backup

Okay thanks. I think I'll give it a rest for today, I've been scouring threads since yesterday trying to get a clear picture of what to do. I think I'll spend the week researching further and give it a go next weekend.
I just miss having AdAway and CF Lumen installed on my phone. And I really want to give Substratum a try.
Thanks for all the tips and info!

Hang in there. You are on the right track. The edl thing can take a few attempts to get recognized.

Did you try the toolkit? Same as using miflash but he has direct downloads to all the necessary drivers and tools along with instructions.

lafester said:
Did you try the toolkit? Same as using miflash but he has direct downloads to all the necessary drivers and tools along with instructions.
Click to expand...
Click to collapse
There are people who are reporting that the drivers that I provide in the toolkit do not work and therefore MiFlash fails to flash packages. I am going to use new drivers in the next version(the drivers that come with the stock ROM) and then the OP should test it.

If you have to use axon7tool then you might find this useful
https://forum.xda-developers.com/showpost.php?p=71206394
But I think that the US version has a different way to root and stuff, so i wouldn't be able to help...

bkores said:
There are people who are reporting that the drivers that I provide in the toolkit do not work and therefore MiFlash fails to flash packages. I am going to use new drivers in the next version(the drivers that come with the stock ROM) and then the OP should test it.
Click to expand...
Click to collapse
Okay I think this may be my issue, this is where I get roadblocked. Thanks for the response, I'll try the new version as soon as it's available.

CookedBooks said:
Okay I think this may be my issue, this is where I get roadblocked. Thanks for the response, I'll try the new version as soon as it's available.
Click to expand...
Click to collapse
Can you try these drivers: http://drivers.softpedia.com/get/MOBILES/Others/ZTE-Handset-USB-Driver-52066111.shtml
Then test the option again and see if MiFlash will detect your device? Thank you.
Just make sure after you install them you go to C:\Windows and delete adb.exe and AdbWinApi.dll otherwise there will be two conflicting adb versions which will cause the toolkit to indefinitely hang when checking adb connectivity.

bkores said:
Can you try these drivers: http://drivers.softpedia.com/get/MOBILES/Others/ZTE-Handset-USB-Driver-52066111.shtml
Then test the option again and see if MiFlash will detect your device? Thank you.
Just make sure after you install them you go to C:\Windows and delete adb.exe and AdbWinApi.dll otherwise there will be two conflicting adb versions which will cause the toolkit to indefinitely hang when checking adb connectivity.
Click to expand...
Click to collapse
Okay, I just walked into work though. When I get home and settled this evening I'll give it a whirl and let you know what happens.

@CookedBooks I have great news for you: Thanks to one of my testers I have fixed the MiFlash issue. The problem was not with the drivers, but with MiFlash itself. So the solution was an EARLIER VERSION of MiFlash!! The next version of the toolkit will utilize the earlier version so I should no longer have to deal with this issue! Huzzahh!

bkores said:
@CookedBooks I have great news for you: Thanks to one of my testers I have fixed the MiFlash issue. The problem was not with the drivers, but with MiFlash itself. So the solution was an EARLIER VERSION of MiFlash!! The next version of the toolkit will utilize the earlier version so I should no longer have to deal with this issue! Huzzahh!
Click to expand...
Click to collapse
Did they just release a new version? The one I'm using has been ok.
If you could post which one is bad that would be great.

lafester said:
Did they just release a new version? The one I'm using has been ok.
If you could post which one is bad that would be great.
Click to expand...
Click to collapse
The one that is bad is the one in the toolkit right now. Its the EARLIER version of MiFlash that works correctly.

bkores said:
The one that is bad is the one in the toolkit right now. Its the EARLIER version of MiFlash that works correctly.
Click to expand...
Click to collapse
I used the toolkit to flash b15 full with miflash and it worked fine, however I already had miflash installed.

Need IMG file for SM-950U

Can someone please connect their rooted S8 via adb and run the following commands:
adb shell
su
dd if=/dev/block/mmcblk0 of=/storage/sdcard1/unbrick.img bs=512 count=30535646
Make sure you have an empty 16+ GB sd card inserted into your phone.
unbrick.img should be in your SD card.
Please zip the file and share it with me so I can unbrick my S8.
Thank you so much!!
I will make a guide once the device is successfully unbricked.

thehaXor said:
Can someone please connect their rooted S8 via adb and run the following commands:
adb shell
su
dd if=/dev/block/mmcblk0 of=/storage/sdcard1/unbrick.img bs=512 count=30535646
Make sure you have an empty 16+ GB sd card inserted into your phone.
unbrick.img should be in your SD card.
Please zip the file and share it with me so I can unbrick my S8.
Thank you so much!!
I will make a guide once the device is successfully unbricked.
Click to expand...
Click to collapse
1) that comand is wrong. This would back up their entire ssd which would give you all their files. Don't do this.
2) there are plenty of root methods on this vs very site. If you could apply to kind of image your can use one of them

Partcyborg I had your rom installed on my s8, but I hardbricked it by running xposed. Now all I see is "qualcomm hs-usb qdloader 9008" when I plug in my s8 but the phone is unresponsive no download mode and no recovery. I read on another posting on
https://forum.xda-developers.com/yureka/help/question-qualcomm-download-mode-k-t3068040
That if someone provides me with a img I can use it to revive my phone.
Please help me.

thehaXor said:
Partcyborg I had your rom installed on my s8, but I hardbricked it by running xposed. Now all I see is "qualcomm hs-usb qdloader 9008" when I plug in my s8 but the phone is unresponsive no download mode and no recovery. I read on another posting on
https://forum.xda-developers.com/yureka/help/question-qualcomm-download-mode-k-t3068040
That if someone provides me with a img I can use it to revive my phone.
Please help me.
Click to expand...
Click to collapse
Hello
I can make you a backup of my device.
Yes true some of the files from my device could be bad for you to have.
Like the EFS partition that contains the IMEI number Serial number ect.
Im not too worried about that but if you have a dump of your efs partition that would be very helpful.
Now the thread you linked too is a way of unbricking some of the devices that arent so heavily secured.
Unless you have the Samsung Signed Firehose i dont think it will work.
Good news is that there is a way to make a debrick image that you burn to a sd card.
Then putting the sd card in the device gets it booted into download mode.
The bad news is I dont know exactly how to create the unbrick.img.
Currtently i am trying to do this for my Galaxy Tab E.
If someone knows how to make the debrick.img I have all the files needed.
Someone out here please help us make a debrick.img

This all seems really complicated its not really. U want that partition? Download es file explorer and follow me... Thumbnails below. Your device must be rooted.
BigCountry907 said:
Hello
I can make you a backup of my device.
Yes true some of the files from my device could be bad for you to have.
Like the EFS partition that contains the IMEI number Serial number ect.
Im not too worried about that but if you have a dump of your efs partition that would be very helpful.
Now the thread you linked too is a way of unbricking some of the devices that arent so heavily secured.
Unless you have the Samsung Signed Firehose i dont think it will work.
Good news is that there is a way to make a debrick image that you burn to a sd card.
Then putting the sd card in the device gets it booted into download mode.
The bad news is I dont know exactly how to create the unbrick.img.
Currtently i am trying to do this for my Galaxy Tab E.
If someone knows how to make the debrick.img I have all the files needed.
Someone out here please help us make a debrick.img
Click to expand...
Click to collapse

thehaXor said:
Partcyborg I had your rom installed on my s8, but I hardbricked it by running xposed. Now all I see is "qualcomm hs-usb qdloader 9008" when I plug in my s8 but the phone is unresponsive no download mode and no recovery. I read on another posting on
https://forum.xda-developers.com/yureka/help/question-qualcomm-download-mode-k-t3068040
That if someone provides me with a img I can use it to revive my phone.
Please help me.
Click to expand...
Click to collapse
There is no way you hardbricked running xposed. If you Google there is a recovery img that is out there for 9008 u2 bootloader

thehaXor said:
Partcyborg I had your rom installed on my s8, but I hardbricked it by running xposed. Now all I see is "qualcomm hs-usb qdloader 9008" when I plug in my s8 but the phone is unresponsive no download mode and no recovery. I read on another posting on
https://forum.xda-developers.com/yureka/help/question-qualcomm-download-mode-k-t3068040
That if someone provides me with a img I can use it to revive my phone.
Please help me.
Click to expand...
Click to collapse
Ok a few things:
1) this did not happen because of "Xposed". This is literally impossible. Xposed only modifies things in /system, this can not cause you to be stuck in 9008. Only bad modifications to bootloader files can do this, which again, Xposed doesn't touch.
2) you don't need someones system image, in fact system images aren't what you need all. You need to flash a working set of bootloaders using the firehose programmer. If you were on my rom then you're in luck, the v2 programmer is out there so doing this is possible.
All you need is a copy of the stock rom, and the firehose programmer with xmls. I think they were shared around here before, if not I can post them for you. Just make sure the stock bl files you upload are for 950u v2 ONLY, or you might not be able to root anymore, or it won't fix it

Depending on what rev bootloader you are on I have the EDL Files.
The official samsung edl files to unbrick your s8.
The sd card trick don't work on the newer samsungs.
You need to use the edl files and flash in edl mode.
Let me know what bootloader you are on.

BigCountry907 said:
Depending on what rev bootloader you are on I have the EDL Files.
The official samsung edl files to unbrick your s8.
The sd card trick don't work on the newer samsungs.
You need to use the edl files and flash in edl mode.
Let me know what bootloader you are on.
Click to expand...
Click to collapse
Probably the ones I shared In my groups....
I have a whole automated script to fix it But I still want to know what this guy was really doing

TheMadScientist said:
Probably the ones I shared In my groups....
I have a whole automated script to fix it But I still want to know what this guy was really doing
Click to expand...
Click to collapse
There is the possibility that the files I have may have originated by you.
But they did not come from XDA they came from a very different source.
I do agree with you that the only way to truly brick the device is to mess with the bootloaders.
Even mixing bootloaders can cause the brick.
I believe the bat file your referring to was released along with the EDL bootloaders.
But you could have easily wrote it it's not very complicated.
I'm just grateful that these files got leaked no matter where they came from.
At one point they were made by samsung at samsung factory without any doubt.
Either a samsung employee or an authorized samsung repair center that had them Leaked the files.
Unless you have samsungs private Key. Actually 3 of them considering the bootloaders are signed using 3 different certs.
If you have that then we should all be running unlocked devices. Please share.
I have been working on unlocking the bootloader for the N950U. Or at least finding a way to load a custom kernel. I believe the EDL bootloaders may have more ability than the stock or combination bootloaders.
We would need to pull the signatures from all the bootloaders and first determine if there using a 2 cert or 3 cert signing scheme. Then by looking at how certain bits of the device serial and other data in the signature we can determine if the debug level is set higher. Like Jtag access and what not.
I do have a copy of the msm8998 Source Code that was leaked. Its a very recent version. There are some things we can use it for but ultimately it would be nice to have the KEY. I'd be happy just to have the private key for signing the boot.img.

BigCountry907 said:
There is the possibility that the files I have may have originated by you.
But they did not come from XDA they came from a very different source.
I do agree with you that the only way to truly brick the device is to mess with the bootloaders.
Even mixing bootloaders can cause the brick.
I believe the bat file your referring to was released along with the EDL bootloaders.
But you could have easily wrote it it's not very complicated.
I'm just grateful that these files got leaked no matter where they came from.
At one point they were made by samsung at samsung factory without any doubt.
Either a samsung employee or an authorized samsung repair center that had them Leaked the files.
Unless you have samsungs private Key. Actually 3 of them considering the bootloaders are signed using 3 different certs.
If you have that then we should all be running unlocked devices. Please share.
I have been working on unlocking the bootloader for the N950U. Or at least finding a way to load a custom kernel. I believe the EDL bootloaders may have more ability than the stock or combination bootloaders.
We would need to pull the signatures from all the bootloaders and first determine if there using a 2 cert or 3 cert signing scheme. Then by looking at how certain bits of the device serial and other data in the signature we can determine if the debug level is set higher. Like Jtag access and what not.
I do have a copy of the msm8998 Source Code that was leaked. Its a very recent version. There are some things we can use it for but ultimately it would be nice to have the KEY. I'd be happy just to have the private key for signing the boot.img.
Click to expand...
Click to collapse
Actually a friend wrote the bat lol Pm me I have a telegram group not much activity but several s8 devs
including some well known fellars in it
Im pretty sure they use 3 keys But Several of us have looked into it quite extensively....
You are more than welcome to join the group and shoot the crap

brick axon 7 A2017G (android 7.1.1.)

Good evening owner of the axon 7 I decided to finally get into the unlocking of my phone in order to root. I followed the first step. Install the twrp on the phone. I had the Nexus 4 and the LG G3 I managed to do it without problem.
There I am the steps I had problems with drivers that I had to reinstall. When then I made the invitation to order I had trouble to have the "QUSB__BULK".
When I managed it with XDA's Axon7_EDL_Tool software (compatible with my French axon in 7.1.1) I managed to install twrp except that ... behind bootloop I get stuck on the zte logo !!! I press volume up the twrp is displayed. I decided to use my update on my SD. I realize that my phone reference US (A2017U) !!! I do not understand how I did to find myself with that !!! However, I used the tutorial link [GUIDE] [A2017G] Install TWRP, Unlock BL, Flash Custom ROM. Is it because of Axon EDL tool? Yet I read and read it is compatible with the euro version A2017G! I do not understand and I panic !!! So I tried to use my backup Update (the last update of ZTE performed in August) and I find myself without the twrp! And I still have the bootloop ... How to remove this brick please ???? Thank you very much for your help !!!:crying::crying::crying:

angelmika91 said:
Good evening owner of the axon 7 I decided to finally get into the unlocking of my phone in order to root. I followed the first step. Install the twrp on the phone. I had the Nexus 4 and the LG G3 I managed to do it without problem.
There I am the steps I had problems with drivers that I had to reinstall. When then I made the invitation to order I had trouble to have the "QUSB__BULK".
When I managed it with XDA's Axon7_EDL_Tool software (compatible with my French axon in 7.1.1) I managed to install twrp except that ... behind bootloop I get stuck on the zte logo !!! I press volume up the twrp is displayed. I decided to use my update on my SD. I realize that my phone reference US (A2017U) !!! I do not understand how I did to find myself with that !!! However, I used the tutorial link [GUIDE] [A2017G] Install TWRP, Unlock BL, Flash Custom ROM. Is it because of Axon EDL tool? Yet I read and read it is compatible with the euro version A2017G! I do not understand and I panic !!! So I tried to use my backup Update (the last update of ZTE performed in August) and I find myself without the twrp! And I still have the bootloop ... How to remove this brick please ???? Thank you very much for your help !!!:crying::crying::crying:
Click to expand...
Click to collapse
that is not very understandable to be honest. Just know that any misstep can put you into a hard brick.
If your phone is an A2017G then you have to install A2017G stuff, NO MATTER WHAT. The name will change to A2017U after installing a ROM, but that's normal since most ROMs are based in U firmware. Your phone is still a G.
You cannot install an official SD card update from zte if you are on TWRP, it will fail. Those can only be installed through the stock recovery
To unbrick your phone, first enter EDL mode (vol+ vol- and insert the cable). Tell me what driver appears on the Device manager (QUSB_BULK, Qualcomm HS-USB, ZTE diagnostics)
If it is Qualcomm HS-USB QDLoader 9008, you'll need a stock EDL file (download one FOR THE A2017G, from the EDL Tool thread). Then install it using EDL Tool

Reading your post I didn't see you unlock the bootloader first?
That can cause major problems.
The best app to use to reinstall your firmware is the Miflash app.
Ive used the Edl tool and the Axon 7 toolkit and both are good for certain flashing and unlocking.
If you have a A2017G make sure all software is related to that device to be sure.

Syberclone said:
Reading your post I didn't see you unlock the bootloader first?
That can cause major problems.
The best app to use to reinstall your firmware is the Miflash app.
Ive used the Edl tool and the Axon 7 toolkit and both are good for certain flashing and unlocking.
If you have a A2017G make sure all software is related to that device to be sure.
Click to expand...
Click to collapse
don't mislead. if you're using Controllerboy's guide you have to install a signed TWRP prior to unlocking the bootloader.

Choose an username... said:
don't mislead. if you're using Controllerboy's guide you have to install a signed TWRP prior to unlocking the bootloader.
Click to expand...
Click to collapse
I'm not using anyone's guide, (I always read several guides not just one BTW)
Show me where Twrp is installed on a locked bootloader, I think that info is misleading.
The twrp site instructions require an unlocked bootloader.
Cyanogen Mod also states and unlocked bootloader is required.

Syberclone said:
I'm not using anyone's guide, (I always read several guides not just one BTW)
Show me where Twrp is installed on a locked bootloader, I think that info is misleading.
The twrp site instructions require an unlocked bootloader.
Cyanogen Mod also states and unlocked bootloader is required.
Click to expand...
Click to collapse
The twrp site has nothing to do with specific per-device unlocking. The point of signed TWRP is being able to install it on a locked phone without wreaking havoc.
I don't have to show you. He said which guide he used, go check it up. But don't mess it up more than it is.

Choose an username... said:
The twrp site has nothing to do with specific per-device unlocking. The point of signed TWRP is being able to install it on a locked phone without wreaking havoc.
I don't have to show you. He said which guide he used, go check it up. But don't mess it up more than it is.
Click to expand...
Click to collapse
I do know the difference between "signed" and "unsigned" software.
I'll let you help this guy out if you think my info is misleading, good luck

Hello,
We can close the subject, I managed to do it again my phone thanks to the update file (the last update ZTE) I still had in the micro SD card.
The latter by putting it in my samsung tablet I saw that my content was not finally erased. So I put the sd in my tel and suddenly the content was finally visible in the part apply update from sdcard. I could make a flash with the update and everything is fine it works! ouffff
Anyway all my apologies I had misread the tutorial.
I did not see that it was compatible only with Marshmallow and not Nougat. I was in 7.1.1 ... I focused too much on the models (A2017x) and the updates of ZTE (B4 / B5 / B6 ...). Then my english is bad. I had to use google translation but no apology is my fault. I should have been careful. I am a bit rusty since Nexus 4 (or it was super easy and there was a huge community) and even the LG G3. I find the ZTE Axon 7 more boring to root, to unlock ...
In short again thank you and sorry for this post !!!

Syberclone said:
Reading your post I didn't see you unlock the bootloader first?
That can cause major problems.
The best app to use to reinstall your firmware is the Miflash app.
Ive used the Edl tool and the Axon 7 toolkit and both are good for certain flashing and unlocking.
If you have a A2017G make sure all software is related to that device to be sure.
Click to expand...
Click to collapse
for information I also based on a second site in French where it was explained that it was necessary to first put the TWRP and after and only after unlocked the bootloader. In short, I lacked vigilance and concentration. Even on the French tutorial it was marked in red that it was incompatible Nougat. I read diagonally and made a mix with the other XDA tutorial. That's it I did not care. Do not fight lol The phone works is essential. Now I would like to know why I have a driver problem on my PC it seems to me but that's another subject! Thank you all anyway !!!

angelmika91 said:
for information I also based on a second site in French where it was explained that it was necessary to first put the TWRP and after and only after unlocked the bootloader. In short, I lacked vigilance and concentration. Even on the French tutorial it was marked in red that it was incompatible Nougat. I read diagonally and made a mix with the other XDA tutorial. That's it I did not care. Do not fight lol The phone works is essential. Now I would like to know why I have a driver problem on my PC it seems to me but that's another subject! Thank you all anyway !!!
Click to expand...
Click to collapse
Glad you got your phone running again

angelmika91 said:
for information I also based on a second site in French where it was explained that it was necessary to first put the TWRP and after and only after unlocked the bootloader. In short, I lacked vigilance and concentration. Even on the French tutorial it was marked in red that it was incompatible Nougat. I read diagonally and made a mix with the other XDA tutorial. That's it I did not care. Do not fight lol The phone works is essential. Now I would like to know why I have a driver problem on my PC it seems to me but that's another subject! Thank you all anyway !!!
Click to expand...
Click to collapse
what kind of driver problem? EDL or mtp?
Honestly MTP works when it wants to work, so I can't help you if your PC doesn't recognize it. EDL is another matter though, pretty easy.

OnePlus 6T - Can't unlock bootloader nor get into Android

My OP6T had Ubuntu Touch (equivalent to Android 9) installed on it. When it broke, I tried to flash TWRP (version 3.3.1) to clear and reinstall Ubuntu Touch. For some reason it wouldn't boot, so I foolishly decided to flash TWRP onto every single partition. This only succeeded in breaking recovery mode. Following some advice I used the 6T MsmDownloadTool v4.0.58 (OOS v9.0.11), which fixed recovery mode, but not Android - it just showed the booting animation in a infinite loop (bootloop).
I've attached an image I found online showing the screen: bootloop
The issue is that I cannot flash in fastboot mode as the bootloader was relocked by MsmDownloadTool, *and* I cannot get into Android to enable OEM mode/USB debugging. I seem to have encountered a paradox where fastboot mode requires the permissions to be enabled in Android, but I can't boot to Android to enable those permissions, nor can I flash anything else to fix Android.
Is this possible to solve?

AOnePlus6TDestroyer said:
My OP6T had Ubuntu Touch (equivalent to Android 9) installed on it. When it broke, I tried to flash TWRP (version 3.3.1) to clear and reinstall Ubuntu Touch. For some reason it wouldn't boot, so I foolishly decided to flash TWRP onto every single partition. This only succeeded in breaking recovery mode. Following some advice I used the 6T MsmDownloadTool v4.0.58 (OOS v9.0.11), which fixed recovery mode, but not Android - it just showed the booting animation in a infinite loop (bootloop).
I've attached an image I found online showing the screen: bootloop
The issue is that I cannot flash in fastboot mode as the bootloader was relocked by MsmDownloadTool, *and* I cannot get into Android to enable OEM mode/USB debugging. I seem to have encountered a paradox where fastboot mode requires the permissions to be enabled in Android, but I can't boot to Android to enable those permissions, nor can I flash anything else to fix Android.
Is this possible to solve?
Click to expand...
Click to collapse

You can try booting with the twrp.img. "fastboot boot name.img" using that ADB command. If that does not work the only other option is to completely retore your phone using msmdownload tool. This method will also depend on whether you have the international version or the T-Mobile version as there are different approaches depending on the type of phone. Read and study carefully how to proceed. If the msm tool does not work I'm pretty damn sure there are no other options.

rogerrulez said:
You can try booting with the twrp.img. "fastboot boot name.img" using that ADB command. If that does not work the only other option is to completely retore your phone using msmdownload tool. This method will also depend on whether you have the international version or the T-Mobile version as there are different approaches depending on the type of phone. Read and study carefully how to proceed. If the msm tool does not work I'm pretty damn sure there are no other options.
Click to expand...
Click to collapse
He can't boot into anything with bootloader locked. This is why msm tool sucks and people should stop recommending it for any little problem.

Only option now is to use msm tool again and hopefully get something working

Even with the bootloader locked you still should be able to boot the recocery image.

I have the 6T and 7T Pro. When I messed up my 6T my only hope was the msmdownloadtool. But make sure it's the right one.

When I had to use the msm download tool it did lock the bootloader. But I was able to unloack it again from the ADB command prompt at the bootloader screen by typing fastboot oem unlock. But this can only be done if it is set in developer options.
I spent alot of time trying to figure it out but later found outthat I was using the wrong msm tool.
Good luck. I hope you get it and running again because the 6T is still a very good phone.

Brettroth said:
He can't boot into anything with bootloader locked. This is why msm tool sucks and people should stop recommending it for any little problem.
Click to expand...
Click to collapse
Are there more suitable tools for fixing a broken recovery mode? It did successfully do that.

rogerrulez said:
Even with the bootloader locked you still should be able to boot the recocery image.
Click to expand...
Click to collapse
How?
rogerrulez said:
When I had to use the msm download tool it did lock the bootloader. But I was able to unloack it again from the ADB command prompt at the bootloader screen by typing fastboot oem unlock. But this can only be done if it is set in developer options.
I spent alot of time trying to figure it out but later found outthat I was using the wrong msm tool.
Good luck. I hope you get it and running again because the 6T is still a very good phone.
Click to expand...
Click to collapse
Thank you! And yes, I tried that command but it is probably unset in the developer options (which I cannot reach, as Android isn't working anymore). I guess I'm using the incorrect version - how do you identify the correct one? I think I've used both the T-Mobile one and the other. I don't think the phone is T-Mobile, but I'm not sure how to identify whether it is or not.

It is very easy to convert a t-mobile variant to the international version. If you bought the phone used you would not know. One tell tale sign could be if you sim card holder supports either one or 2 sims. But that's not a sure way either because you can buy a replacement sim card holder. The fastet was would be to look up the IMEI # and see what variant of the 6 you have.
As for the msm tool you would needd a modified version of that tool. You first use it to downgrade to Android 9. Then you have to upgrade that verion of android 9 to a slightly higher version before you are able to fully upgrade feely to 10 than 11 if you wanted.
If you have the international version pretty much and version of the msm tool would work but a modified version would be best.
However, the first step is to find out which variant you have.
When you used the msmdownload tool which version did you use, and did it finish the job ?

If you have the t-mobile vesion there is a thread on here that gives you step by step instructions to convert from t-mobile to international along with the links to download the software. And even the modified version will know what variant you have simply by not working.

If you are able to get into the bootloader than you have a great chance of fixing your phone. Your phone is bootlooping so that tells me you can access the bootloader screen.

When I bricked mine I thought it was gone forever, I spent several days working on it but I was able to restore it. But I would never use the ubuntu rom on any phone that I care for.

When you are at this level it is very important you proceed with caution and don't just start flashing anything you can find. It will nake matters much worse.

rogerrulez said:
Even with the bootloader locked you still should be able to boot the recocery image.
Click to expand...
Click to collapse
Wasn't sure about that. If that's the case, can you also flash from twrp then?

Brettroth said:
Wasn't sure about that. If that's the case, can you also flash from twrp then?
Click to expand...
Click to collapse
No. Not without an unlocked bootloader. But booting into twrp would give you the ability to flash a ROM tho.

rogerrulez said:
No. Not without an unlocked bootloader. But booting into twrp would give you the ability to flash a ROM tho.
Click to expand...
Click to collapse
That's what I meant. Flash a ROM from twrp. Ok so if that works this guy can fix everything from there. Gonna be a hassle tho. Instead of rebooting to recovery I think you would have to shut off phone and fastboot boot back into twrp to change slots right?

Somehow I feel like that won't work but I'm not locking my bootloader to test it

rogerrulez said:
The fastet was would be to look up the IMEI # and see what variant of the 6 you have.
Click to expand...
Click to collapse
I'm afraid I can't' find it... It is dual-sim though.
rogerrulez said:
When you used the msmdownload tool which version did you use, and did it finish the job ?
Click to expand...
Click to collapse
I used a few - both T-Mobile and not. They all succeeded with (seemingly) no error, but didn't fix the bootloop.
rogerrulez said:
If you have the t-mobile vesion there is a thread on here that gives you step by step instructions to convert from t-mobile to international along with the links to download the software. And even the modified version will know what variant you have simply by not working.
Click to expand...
Click to collapse
I see, but won't that need me to be in Android to be able to run the software?
rogerrulez said:
If you are able to get into the bootloader than you have a great chance of fixing your phone. Your phone is bootlooping so that tells me you can access the bootloader screen.
Click to expand...
Click to collapse
Yup, fastboot and recovery mode work fine. The bootloader is locked though, else installing TWRP, etc. would be easy.
rogerrulez said:
When you are at this level it is very important you proceed with caution and don't just start flashing anything you can find. It will nake matters much worse.
Click to expand...
Click to collapse
Yeah...
rogerrulez said:
Even with the bootloader locked you still should be able to boot the recocery image.
Click to expand...
Click to collapse
It doesn't do it automatically. Is there another way to boot it?
Brettroth said:
Somehow I feel like that won't work but I'm not locking my bootloader to test it
Click to expand...
Click to collapse
As far as I can tell there's no way to flash TWRP without unlocking the bootloader. And there doesn't seem to be any way to do that without getting into Android. And I can't get into Android...
Someone else suggested using this tool (https://github.com/bkerler/edl) as a last-ditch attempt. I'm going to give it a try and hope for the best!
Thank you both for your suggestions.