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:.
Related
Hi all,
Thinking about this phone, what is bootloader like, unlockable? Can fastboot be accessed?
Looked all over for info, most Chinese forums are bashing the phone, but the reason is not clear to me (seems mostly joking that it is just a knock off of the Nexus they produced). Chinese is not my first language, that is probably most of the problem.
I am interested in getting some development going on here, but I need to know if it is worth the trouble even trying. Huawei does release source, but it is really not easy to find. Also, source for this phone seems to not be released yet. If you google "huawei open source" you get some sources, but not for this device. If anyone can point me in a better direction I would appreciate it.
I followed step 1 of this guide: http://forum.xda-developers.com/showthread.php?p=68280798 to get my bootloader unlock code.
I haven't been able to find a version of TWRP for this phone yet and KingoRoot hasn't been able to achieve root either ?
Sent from my HUAWEI MLA-L03 using Tapatalk
You might try this for root: http://www.huaweishuaji.com/112.html
Supports many other Huawei devices, but I cannot guarantee as I have never used it, so use at your own risk. There are also some Chinese guides for unbricking out there. It involves putting the stock image onto the external SD card and running a flash from the phone. Seems it would be fairly easy to build TWRP for the the device if there was a little more info about it, such as partitions. Unfortunately, I do not have the device and need to upgrade my PC before I can start building anything again.
Bored today, so been digging. Seems it would be fairly easy to port the zenfone 3 twrp over, as the specs are similar.
I can't try to build as I need to upgrade, and don't have the phone to test anyway.
Here is the git, looks like only a few changes to make: https://github.com/shakalaca/android_device_asus_ze520kl
Here is a link with how to flash the zenfone: http://www.asus-zenfone.com/2016/10/how-to-root-asus-zenfone-3-ze520kl-and.html
If it was me I would give it a go booting the z017d one, but make sure you "fastboot boot filename.img" and not flash. I would take the risk, but not saying anyone else should.
Not going to have anything to build with until around Christmas, so hopefully someone can give it a go building for the phone. I might get the phone around Christmas too, lets see how development goes.
can anyone try to load the twrp from p9 lite? The hardware specs are just as much the same
"fastboot boot recovery recovery_twrp.img"
maybe it works...
It's a no go booting either of those recoveries. Each flash while successful, ends in a boot loop.
I also don't have the time right now to dedicate to build TWRP from source.
Sent from my HUAWEI MLA-L03 using Tapatalk
thisizM1 said:
I followed step 1 of this guide: http://forum.xda-developers.com/showthread.php?p=68280798 to get my bootloader unlock code.
I haven't been able to find a version of TWRP for this phone yet and KingoRoot hasn't been able to achieve root either
Sent from my HUAWEI MLA-L03 using Tapatalk
Click to expand...
Click to collapse
Mine was bricked after trying the KingoRoot. Any chance I can unbrick it somehow?
P/S: Yes I am an idjit because I didn't make any kind of backup. :crying::crying:
Seems the Huawei unlock code generator is down. I entered my phones data, but the unlock code never appears. I only get an error message when I enter wrong data (i.e., CAN-L11 instead of HUAWEI CAN-L11), so seems the data is validated. When did you create your code, @wangdaning?
Regards,
sebastian
Don't have the phone, I think an earlier poster did get an unlock. I was speculating about what might be possible.
wangdaning said:
Don't have the phone, I think an earlier poster did get an unlock. I was speculating about what might be possible.
Click to expand...
Click to collapse
Sorry, my fault. thisisMZ1 was the lucky guy with the unlock code.
@thisisMZ1: did you try to boot the image without flashing it first? Don´t know if that makes a difference, but one never knows.
For the unlock code, I got an unhelpful reply from the support team ("please use the form provided on..."). My replies on this haven´t been answered yet, so I´m waiting... Will keep you updated.
Regards,
Sebastian
Hi again,
I managed to unlock the bootloader: I created the Huawei ID on the wron (Asian) website. I created a new ID via the German website and was able to use the website for unlocking code with the new ID.
Regards,
Sebastian
sebixvi said:
Sorry, my fault. thisisMZ1 was the lucky guy with the unlock code.
@thisisMZ1: did you try to boot the image without flashing it first? Don´t know if that makes a difference, but one never knows.
For the unlock code, I got an unhelpful reply from the support team ("please use the form provided on..."). My replies on this haven´t been answered yet, so I´m waiting... Will keep you updated.
Regards,
Sebastian
Click to expand...
Click to collapse
I tried both, booting and flashing, neither worked.
Sent from my Nexus 6P using Tapatalk
sebixvi said:
Hi again,
I managed to unlock the bootloader: I created the Huawei ID on the wron (Asian) website. I created a new ID via the German website and was able to use the website for unlocking code with the new ID.
Regards,
Sebastian
Click to expand...
Click to collapse
Hi,
could you leave us the links to the websites you used? Thank.
TWRP has been released in Chinese http://www.netded.com/a/jingpinshouji/2016/1108/32373.html
m00h said:
Hi,
could you leave us the links to the websites you used? Thank.
Click to expand...
Click to collapse
https://uniportal.huawei.com/accounts/register.do?method=toRegister®siterMethod=byPhone ist the page I used to create my ID.
Regards,
Sebastian
wangdaning said:
TWRP has been released in Chinese http://www.netded.com/a/jingpinshouji/2016/1108/32373.html
Click to expand...
Click to collapse
i installed this on my Nova Plus and then changed the language to english
works, however when trying to backup the files it says invalid argument. no matter what it tries to mount
soliditalstud said:
i installed this on my Nova Plus and then changed the language to english
works, however when trying to backup the files it says invalid argument. no matter what it tries to mount
Click to expand...
Click to collapse
Wonder if it is only for the nova and not the nova plus. I did not make it and have neither phone to test, just passing it along. Unfortunately, they seem to have not used github.
Does anyone have a link to the factory recovery.img?
I flashed the Recovery to the Nova (not the plus) and I got exactly the same error. If I try to flash the superSU, I got a error that it couldnt Mount data and after a Reboot the root doesnt work.
I guess their could be several variants of the phone, which does not bod well for hopes of development.
Something new?
The chinese recovery boots but has problems to mount the partitions.... Its for the CAN-L01 and on my CAN-L11 is a different fstab. I have not the skills to compile a working one.
I am having trouble finding a root method for this phone
, Or even just some news about development. Anyone point the way?
i have the same question. Anyone have any information?
It's kinda like a bum deal right now. I got two ZTE devices no root. Upset I can't disable all these google apps
Sent from my Z971 using Tapatalk
Same. Waiting for ZTE 971 root.
What is needed to get the process started to Root the ZTE Blade Spark z971
CharmedWhovian said:
What is needed to get the process started to Root the ZTE Blade Spark z971
Click to expand...
Click to collapse
Nobody knows yet
Sent from my ZTE Z971 using XDA Labs
Anybody has ROM or smth else for this phone?
Frp for blade spark?
I have had now about 4 or 5 newer ZTE phones. What I have come across is that none were able to be rooted. I posted a few requests, no one here took on the task. I don't know if it is that they can't be rooted or its just to hard for someone to do. Either way I have gotten away from buying ZTE phones for this reason.
Did anyone try to unlock the bootloader?
Code:
adb reboot bootloader
fastboot oem unlock
AT&T shows that there have been multiple OTA updates for this phone, and the last one early Jan 2018 was over 500mb. It should not be hard to port TWRP if we have an unlocked bootloader.
https://www.att.com/devicehowto/tutorial.html#!/stepbystep/id/stepbystep_KM1217955?make=ZTE&model=ZTEZ971
sparkie420 said:
I am having trouble finding a root method for this phone
, Or even just some news about development. Anyone point the way?
Click to expand...
Click to collapse
Nope, fastboot is removed on ZTE Nougat devices
It looks like they figured out ways around this for the Axon7, using EDL mode, but I tried a few things (including axon7tool, and the flashable zip to enable fastboot) without any luck.
I'll keep digging but it doesn't look too promising.
ZTE has our kernel sources at http://opensource.ztedevice.com [ZTE Z971 Nougat(7.1.1) Kernel(3.18.31)]
Won't do us much good without an unlocked bootloader though..
Anyone know if you can use MiFlash to flash in EDL mode without an unlocked bootloader?
aslezak said:
Did anyone try to unlock the bootloader?
Code:
adb reboot bootloader
fastboot oem unlock
AT&T shows that there have been multiple OTA updates for this phone, and the last one early Jan 2018 was over 500mb. It should not be hard to port TWRP if we have an unlocked bootloader.
https://www.att.com/devicehowto/tutorial.html#!/stepbystep/id/stepbystep_KM1217955?make=ZTE&model=ZTEZ971
Click to expand...
Click to collapse
TWRP for ZTE 791
Here is a Z971 TWRP I compiled for our device.
Any brave soul want to flash it using QPST or using one of the other methods in this post? Unbrick All Qualcomm
You'll need to rename it to recovery.img first. If you have to choose a firehose, choose prog_emmc_firehose_8917_ddr.mbn
Supposedly you can flash even with a locked bootloader :good:
aslezak said:
Here is a Z971 TWRP I compiled for our device.
Any brave soul want to flash it using QPST or using one of the other methods in this post? Unbrick All Qualcomm
You'll need to rename it to recovery.img first. If you have to choose a firehose, choose prog_emmc_firehose_8917_ddr.mbn
Supposedly you can flash even with a locked bootloader :good:
Click to expand...
Click to collapse
I'll do it man just message me details on how to
I was going to try & backup all the partitions using QPST, but it seems you need to get the phone into 9006 mode. We can only get into 9008 mode [Qualcomm HS-USB QDLoader 9008] with "adb reboot edl" (emergency download mode). Holding down Vol+/Vol-/Power from EDL will get you into yet another mode, ZTE Handset Diagnostic (DFU) mode, but I couldn't figure out how to do anything from here with QPST.
The only way to get the phone into 9006 mode is to brick the bootloader, which I'm not willing to do at the moment. Supposedly you can use the "axon7tool -d" and it will try to write to your bootloader & boot, but it just crashed when I tried to do it.
The other way to get into 9006 mode is to flash an mbn and another file, but I believe those are device specific, and we don't have those..
Anyway, does anyone have a phone that wasn't updated to the latest Z971V1.0.0B20 firmware? It would be nice if we could get that from the /update folder so if we brick, we have something we might be able to flash to recover.
JonnyGrench said:
I'll do it man just message me details on how to
Click to expand...
Click to collapse
I figured out if you put the AT&T SIM card in, then Settings / AT&T Software Update, you will see the Z971V2.0 update & it will download.
I wasn't able to see the update until I put the AT&T SIM card in.
Unfortunately, I was unable to grab the OTA update.
If someone hasn't already updated to the latest software version, if you could "adb logcat -d -f /sdcard/Download/ota.txt" once the download starts, we can probably get the url of the OTA update, then work from there on building a flashable firmware... :good:
aslezak said:
I was going to try & backup all the partitions using QPST, but it seems you need to get the phone into 9006 mode. We can only get into 9008 mode [Qualcomm HS-USB QDLoader 9008] with "adb reboot edl" (emergency download mode). Holding down Vol+/Vol-/Power from EDL will get you into yet another mode, ZTE Handset Diagnostic (DFU) mode, but I couldn't figure out how to do anything from here with QPST.
The only way to get the phone into 9006 mode is to brick the bootloader, which I'm not willing to do at the moment. Supposedly you can use the "axon7tool -d" and it will try to write to your bootloader & boot, but it just crashed when I tried to do it.
The other way to get into 9006 mode is to flash an mbn and another file, but I believe those are device specific, and we don't have those..
Anyway, does anyone have a phone that wasn't updated to the latest Z971V1.0.0B20 firmware? It would be nice if we could get that from the /update folder so if we brick, we have something we might be able to flash to recover.
Click to expand...
Click to collapse
Greetings, i have ZTE blade spark too, as i see, this thread looks like it died very quick. well, i am not a developer but i'll try contacting some developers to check if we can do something. Maybe since they know a lot about it, they can help us to unlock bootloader, etc. I JUST HOPE that this thread doesnt die like the Huawei Ascend XT forums did and the phone couldnt have any custom ROM. The best thing is we have source code (the XT didnt had a good source code or no source code at all) and we can start from that. But we need a good dev to help us, try to contact as many devs as possible too.
Not to discourage you, but the fastboot is "disabled" on all ZTE U.S. devices. You would need to flash using QPST which requires having the correct vendor signed firehose programmer (which isn't available). You could try modifying the ota zip update, if you received one on your phone. You would need to download this OTA update manually before rebooting the phone (to have it installed), otherwise the link will be rolled off the logcat logs.
Good luck.
ensol52 said:
Greetings, i have ZTE blade spark too, as i see, this thread looks like it died very quick. well, i am not a developer but i'll try contacting some developers to check if we can do something. Maybe since they know a lot about it, they can help us to unlock bootloader, etc. I JUST HOPE that this thread doesnt die like the Huawei Ascend XT forums did and the phone couldnt have any custom ROM. The best thing is we have source code (the XT didnt had a good source code or no source code at all) and we can start from that. But we need a good dev to help us, try to contact as many devs as possible too.
Click to expand...
Click to collapse
So I just got this phone and wanted to root and all that like I did my S4. Came here for some help because I am most definitely not educated enough for this. I did have a question though. I see a lot about a locked bootloader but under the developer settings I see "OEM Unlocking Allow the bootloader to be unlocked." The default is off, and I have left it so. Is this anything or am I missing something?
aslezak said:
I figured out if you put the AT&T SIM card in, then Settings / AT&T Software Update, you will see the Z971V2.0 update & it will download.
I wasn't able to see the update until I put the AT&T SIM card in.
Unfortunately, I was unable to grab the OTA update.
If someone hasn't already updated to the latest software version, if you could "adb logcat -d -f /sdcard/Download/ota.txt" once the download starts, we can probably get the url of the OTA update, then work from there on building a flashable firmware... :good:
Click to expand...
Click to collapse
Just got the phone, going to do this. Edit: Total skid here btw. Is it safe to post that file here?
Foggofed said:
Just got the phone, going to do this. Edit: Total skid here btw. Is it safe to post that file here?
Click to expand...
Click to collapse
Hello ? Lol, yeah! Upload it to a good site like Android dev, I'm a lil behind the loop but I'm sure sharing your findings are what's going to lead us into a possibility of getting some Dev love...
Sent from my Z971 using Tapatalk
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.
I'm not seeming to find coherent instructions to get back to stock 11.0.2.2IN11AA
I have the 8 Pro, rooted, newest magisk and I installed a magisk module that is now causing System UI crash at startup. I have tried a couple things: 1) tried the "adb wait-for-device shell magisk --remove-modules" --> nothing happens when starting back up except System UI error. 2) I've flashed back to stock boot.img (hoping to get to safe mode to disable magisk)...all I get is System UI error again.
So...what I want to do is start all over and end up with 11.0.2.2IN11AA rooted. Once I'm back to "factory" I'm pretty sure I can get back to magisk and root.
Can anyone help me with some decent instructions please?
Thanks
I can. So last week I managed go back from a rooted situation to stock rom with LOCKED bootloader. This means that you're phone will be as you bought it and you're gonna lose everything of course.
This video on YT helped me.
***REMEMBER TO CHOOSE YOUR FIRMWARE BECAUSE I THINK THIS VIDEO IS FOR ASIA, IF IT IS THE SAME FOR YOU THEN YOU SHOULD FOLLOW THIS VIDEO***
I provide you a link with a thread on xda where I found the version for my oneplus 8 pro (EU)
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS | XDA Developers Forums (xda-developers.com)
Thanks I'll check it out and report back
glhelinski said:
Thanks I'll check it out and report back
Click to expand...
Click to collapse
Let me know
glhelinski said:
I'm not seeming to find coherent instructions to get back to stock 11.0.2.2IN11AA
I have the 8 Pro, rooted, newest magisk and I installed a magisk module that is now causing System UI crash at startup. I have tried a couple things: 1) tried the "adb wait-for-device shell magisk --remove-modules" --> nothing happens when starting back up except System UI error. 2) I've flashed back to stock boot.img (hoping to get to safe mode to disable magisk)...all I get is System UI error again.
So...what I want to do is start all over and end up with 11.0.2.2IN11AA rooted. Once I'm back to "factory" I'm pretty sure I can get back to magisk and root.
Can anyone help me with some decent instructions please?
Thanks
Click to expand...
Click to collapse
Visit the MSM thread, that's it
Sneakdovi said:
Let me know
Click to expand...
Click to collapse
Good site and instructions. They sure don't make it clear that msmtool is packaged inside the image download file
glhelinski said:
Good site and instructions. They sure don't make it clear that msmtool is packaged inside the image download file
Click to expand...
Click to collapse
I only donwloaded the EU verision (because i'm in Italy), went to qualcom recovery, and started the process
Sneakdovi said:
I only donwloaded the EU verision (because i'm in Italy), went to qualcom recovery, and started the process
Click to expand...
Click to collapse
Please help me, i'm bricked my new device. I want that ****** monocrome filter and make to many bull**** ! :-( I need my phone.
The MSM-Tool is give me always "Sahara" errors. Make the same misstake then you! I locked the bootloader!
Please.
chr_rocke808 said:
Please help me, i'm bricked my new device. I want that ****** monocrome filter and make to many bull**** ! :-( I need my phone.
The MSM-Tool is give me always "Sahara" errors. Make the same misstake then you! I locked the bootloader!
Please.
Click to expand...
Click to collapse
First off, you may want to edit your language in here, no need to swear. Secondly you should check out the thread regarding the MSM tool.
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Post #2 above has a video and also links to the same place that freshlybaked420 referenced... Should be enough to get you back on track
FreshlyBaked 420 said:
First off, you may want to edit your language in here, no need to swear. Secondly you should check out the thread regarding the MSM tool.
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Click to expand...
Click to collapse
Yes, it's all true. Sorry for that i have now working for many days on this. Not sleeping enought. One more question that could bring me a step foward...
I was on IN11.0.2.2 before i locked the bootloader and bricked the device.
Now i downladed the Decrypted OxygenOS 11.0.0 IN21BA Version. I have now the error: Param Preload Device not match image. Question: Must i habe the Decrypted OxygenOS 11.0..2.2 IN21BA Version that it goes to work?
I can't the use the link for the right version, it is password protected.!
Thanks
The password is listed in the OP
glhelinski said:
The password is listed in the OP
Click to expand...
Click to collapse
Thank you, but I didn't find it.
One point I have forgotten to tell. Before the hard brick happened, I used Magistik and Patch a new boot.img then I flashed this with fastboot command. My failure was to make this 2. times. with different patches. The horrible thing is now that I must delete these files on my Laptop to get more space. When this the Problem of the MSMTOOL error is I had not really a chance to unbrick my device. Have anyone Downgrade with MSMTOOL the Stock Rom?
Thx for your help. I download now from OP the latest ROM. I will try it. I feel really scared. Maybe my device is not unbricked anymore.
The other Tool that I have (last chance) is the original Qualcomm flashing Tool QPST.
described here:
Download QPST Flash Tool & How to Use it to Flash Firmware on Qualcomm Android Devices
Download all versions of QPST Flash tool and learn how to use the QFIL and Software Download programs to flash firmware files on Qualcomm Android devices.
www.thecustomdroid.com
-- > But I found nothing here, that this tool was used. There is no special Rom here to found.
chr_rocke808 said:
Thank, but i didn't find it.
One point i forgotten to tell. Before the hard brick happend, i used Magistik and Patch a new boot.img then i flashed this with fastboot comand. My failure was to make this 2. times. with diffred pachtes. The horrible thing is now that i must delete this files on my Laptop to get more space. When this the Problem of the MSMTOOL error is i had not realy a chance to unbrick my device. Habe anyone Donwgrade with MSMTOOL the Stock Rom?
Thx for your help. I download now from OP the latest ROM. I will try. i feel realy scared. Mabye my device is not unbricked anymore.
The other Tool that i have (last chance) is the orginal Qulacomm flashing Tool QPST.
described here:
Download QPST Flash Tool & How to Use it to Flash Firmware on Qualcomm Android Devices
Download all versions of QPST Flash tool and learn how to use the QFIL and Software Download programs to flash firmware files on Qualcomm Android devices.
www.thecustomdroid.com
-- > But i found nothing here, that this tool was used. There is noch spezial Rom here to found.
Click to expand...
Click to collapse
None of that matters.
1st identify your device!
What region is it?
If you have BA then don't flash AA you'll mess things up.
2nd visit the MSM thread!
Download the tool 'for your device!'
3rd boot to EDL (I responded to you in the romaur thread how to do this)
4th as soon as it's connected to your pc in edl, flash the device
5th MSM will relock your bootloader.
6th don't do something if you're not sure, just ask.
Oh and lol chill on the swearing also on posting everywhere, just make 1 thread and stick with it, people will help
Hey, my Phone is working like a charm. Thx for the great work !!!. I'm so happy !!!
It is better to come here to real developers, I had to get bad download links and bad Software! This was the only problem. For many years I have the first Samsung Galaxy and I'm knowing that I can get all the problems for not booting devices back. But I was scared that many Devices like Huwai bring their bootloaders with cryptographic methods in a safe trunk.
Best wishes to you, and the people that I'm working for the android project!
regardless,
chr_rocke808
chr_rocke808 said:
Hey, my Phone is working like a charm. Thx for the great work !!!. I'm so happy !!!
It is better to come here to real developers, I had to get bad download links and bad Software! This was the only problem. For many years I have the first Samsung Galaxy and I'm knowing that I can get all the problems for not booting devices back. But I was scared that many Devices like Huwai bring their bootloaders with cryptographic methods in a safe trunk.
Best wishes to you, and the people that I'm working for the android project!
regardless,
chr_rocke808
Click to expand...
Click to collapse
Lol no worries pal, but trust me, always make a thread unless one exists, it'll work out.
Glad you're sorted.
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.