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.
Related
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:.
***UPDATE***
Thanks to reply, I have now successfully done everything I set out to do, and created follow-up guide!
You can find it HERE
Original Post below:
Hello Everyone!
I'd like to start off saying I used to have a Nexus 4, with TWRP and Lollipop-based CyanogenMod. I was able to install this all by myself, and keep both TWRP and the ROM updated. I also flashed custom radio to unlock the LTE capability on that phone. My tool of choice to help customize the phone was Nexus Root toolkit.
I was able to follow guides posted long ago on these forums, to do what I wanted with the Nexus 4 back in 2013/2014, but it seems I'm not so capable these days. I've hit such a roadblock with lack of root and constant stutters/slowdowns with everyday use on my current device, the Axon 7, that I must get away from the stock software. I heard it was not so easy with other devices, and while a few devs have posted wonderful guides for users, it's just not enough for a true beginner like me. From skimming guides posted, it seems like devs already expect you to have installed custom recovery, or unlocked bootloader. Then when I try to do these things, so I can move onto custom ROM, it seems the guides are out of date or just not step-by-step enough for me to use, and I don't want to take a risk and brick my device trying things that I'm not sure about. I'm a power user through and through, but not so up-to-date or knowledgeable enough to be able to follow the guides already on the forums. Consider me 1 out of 5 on tech level for Android software.
Here's the model/software already on my device: Stock everything, from bootloader and recovery, to ROM.
Model: A2017U, Nougat 7.0 on B15 ROM
What I still need clarification on:
with my device already running on nougat, do I need to install the nougat universal bootloader/radio I saw in earlier guides?
will LineageOS have any downgrades in regard to audio quality, on either the headphone output or speakers?
will my ROM of choice have Daydream VR support? if not what would be needed?
this is not a big deal, but do I need a special app or entire custom ROM if I'm interested in a temporary unroot to use apps like Android Pay?
Here's what I want on my device: TWRP, LineageOS with root.
If anyone, expert users and devs alike, could reply with current known-good info about the following, I and a lot of other users would be eternally grateful:
unlocking the bootloader, installing TWRP, and LineageOS, in a stupidly long but simple step-by-step process.
Quick follow-up info:
What I can do so far: download current LineageOS nightly, correct version of root .zip, and TWRP from official websites
NO, I'm not good with using ADB on Windows to get things done. I had to ask a friend to help me install it on windows, the guide he sent was much easier than the one i was using, and he still had to walk me through how to use it once installed to help me unlock bootloader/root on another device, Zenphone Zoom if anyone is interested.
PLEASE, don't link me to other guides for any part of this process, if the steps are thorough and relevant, please copy here, of course with all due credit given to original poster.
Feel free to let me know if more info about my knowledge level or device is needed to help you work on my request.
Thanks for reading, here's to several years more of everyone enjoying this wonderful device!
ok there is three real steps, but it can be aheadache, mainly because you didn't unlock before going to nougat.
Step 1. Downgrade to B29 Marshmallow - go here https://www.zteusa.com/axon-7/ and on the support tab in software updates is a full B29 software package. Download it, unzip it once, then put the update.zip file on your SD card.
- on the phone, in developers options, turn on OEM unlocking (it is needed to flash from sd card)
- boot phone to recovery, choose update from sd card, pick the update.zip from the sdcard, the phone will flash the B29 software. It is a bit slow, let it do what it needs to do.
Step 2. Unlock phone and install TWRP - go here https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514 download the miflash program, fastboot unlock program, and twrp for B29.
- instructions are all there, just do what it says.
Step 3, Install LineageOS - https://forum.xda-developers.com/axon-7/development/unofficial-lineageos-14-1-zte-axon-7-t3545679 very straight forward. Don't forget to install first the bootloader, then the rom, then gapps.
What makes this so hard is not being easily able to unlock in nougat. Most of us here unlocked way before marshmallow
No need to downgrade to b29.
lafester said:
No need to downgrade to b29.
Click to expand...
Click to collapse
I was thinking this too. Should be as simple as the steps below
1) Flash signed twrp using axonroot tool - this pry's open the door
2) Using twrp, flash fastboot (b20_fbop or something?) - opens door wider
3) Enable usb debugging and oem unlocking in developer options
4) reboot to fastboot/bootloader mode
5) fastboot oem unlock - door is now wide open
Done.
gpz1100 said:
I was thinking this too. Should be as simple as the steps below
1) Flash signed twrp using axonroot tool - this pry's open the door
2) Using twrp, flash fastboot (b20_fbop or something?) - opens door wider
3) Enable usb debugging and oem unlocking in developer options
4) reboot to fastboot/bootloader mode
5) fastboot oem unlock - door is now wide open
Done.
Click to expand...
Click to collapse
Is that a "should work" or "does work" because I'm trying to root and install LOS also on stock non rooted nougat Axon 7 and so far I've gotten nowhere and no one seems to be able to give me a list that says Yes this works
Help needed
I followed the instructions and is apparently in a boot loop. Initially it was working but now it is not. I can't even wipe the device to start from scratch. Is there another ROM available to try?
kingoftheafro said:
Is that a "should work" or "does work" because I'm trying to root and install LOS also on stock non rooted nougat Axon 7 and so far I've gotten nowhere and no one seems to be able to give me a list that says Yes this works
Click to expand...
Click to collapse
This is exactly the reason I made my post, I need concrete answers not guesses. Glad to see someone else needs the same answers
kaiso said:
I followed the instructions and is apparently in a boot loop. Initially it was working but now it is not. I can't even wipe the device to start from scratch. Is there another ROM available to try?
Click to expand...
Click to collapse
Did you downgrade to Marshmallow B29 first or skip this step?
[email protected] said:
This is exactly the reason I made my post, I need concrete answers not guesses. Glad to see someone else needs the same answers
Click to expand...
Click to collapse
I'm praying that someone will compile the information spread about into 3 guides that are model specific so people like us won't rack our heads trying to figure out what on earth to do.
[email protected] said:
Hello Everyone!
Model: A2017U, Nougat 7.0 on B15 ROM
What I still need clarification on:
1with my device already running on nougat, do I need to install the nougat universal bootloader/radio I saw in earlier guides?
2will LineageOS have any downgrades in regard to audio quality, on either the headphone output or speakers?
3will my ROM of choice have Daydream VR support? if not what would be needed?
4this is not a big deal, but do I need a special app or entire custom ROM if I'm interested in a temporary unroot to use apps like Android Pay?
Here's what I want on my device: TWRP, LineageOS with root.
If anyone, expert users and devs alike, could reply with current known-good info about the following, I and a lot of other users would be eternally grateful:
unlocking the bootloader, installing TWRP, and LineageOS, in a stupidly long but simple step-by-step process.
Quick follow-up info:
What I can do so far: download current LineageOS nightly, correct version of root .zip, and TWRP from official websites
5NO, I'm not good with using ADB on Windows to get things done. I had to ask a friend to help me install it on windows, the guide he sent was much easier than the one i was using, and he still had to walk me through
Click to expand...
Click to collapse
Ok, I've edited your post to clear some of the clutter and numbered everything so I can answer everything.
1. No, bootloader updates are only for users who haven't updated to B15 (through official means)
2. Only audio issues are with the front facing speakers. The way they sound is if you turn them up to 100% and then push it even higher to like 140%. So if you keep it at about 71% they sound normal. Check this guide here to get even better quality on overall sound (headphones, speakers)
3.B15 and LOS both work with Daydream. I currently use LOS with my Daydream headset currently.
4.Magisk with this kernel here. Currently have fully functioning Android Pay with LOS.
5. This is a big problem. If you're not comfortable with ADB you should maybe rethink messing with this phone. EDL mode (which is how I flash TWRP and subsequently the B20 bootloader to unlock) is very similar to ADB and the tools needed to flash in EDL can brick your device. Learning how to use ADB isn't bad but it's good as a fallback so you're not relying on strangers to help you out in a pinch (which most will, I just like having the ability to do things mostly myself).
---------- Post added at 10:05 AM ---------- Previous post was at 09:55 AM ----------
nolimit78 said:
I'll keep on saying this as much as I need to, I get where you're coming from. There's a lot of data about the correct way of doing things. Best thing to do is read and search. When I got my phone B29 was the new hotness and there was a bunch of older data floating around that I had to sift through. But I did it, I sifted and found my own way and combined two different methods to get my phone rooted and flashed with LOS. Honestly, the trial and error, the searching, the sifting is totally worthwhile because while this device is /DIFFERENT/ compared to methods for HTC and Samsung products, it's not harder. It's better to get yourself properly antiquated to the device you plan on flashing/hacking/rooting because there is /always/ a chance for bricking. Then another thread will be created asking for help to unbrick. Take the time, read now, read everything, understand your device, then push forward.
Click to expand...
Click to collapse
I quoted this because this thread is like the third I've seen in the last couple days. But to offer some help, this is the guide that I've followed with two phones one running B29 stock and one running B15 Stock. It remains the same because of the use of EDL. It's also good in case you want to go back to complete stock (which at the time was speculated would brick your device) but I read between the lines and discovered that it's just not a big deal. Once you get TWRP installed, make sure your Data partition is EXT4, flash LOS, flash GApps and you're good to go.
The hardest part of the process, is getting your drivers to be recognized properly for the EDL flashing tool to work. Anti-Virus softwares tend to throw false positives with tools like the EDL Flashing tool. I installed a fresh copy of Windows 7 JUST to have a flashing station ready JIC. Once I did that, smooth sailing.
nolimit78 said:
Ok, I've edited your post to clear some of the clutter and numbered everything so I can answer everything.
1. No, bootloader updates are only for users who haven't updated to B15 (through official means)
2. Only audio issues are with the front facing speakers. The way they sound is if you turn them up to 100% and then push it even higher to like 140%. So if you keep it at about 71% they sound normal. Check this guide here to get even better quality on overall sound (headphones, speakers)
3.B15 and LOS both work with Daydream. I currently use LOS with my Daydream headset currently.
4.Magisk with this kernel here. Currently have fully functioning Android Pay with LOS.
5. This is a big problem. If you're not comfortable with ADB you should maybe rethink messing with this phone. EDL mode (which is how I flash TWRP and subsequently the B20 bootloader to unlock) is very similar to ADB and the tools needed to flash in EDL can brick your device. Learning how to use ADB isn't bad but it's good as a fallback so you're not relying on strangers to help you out in a pinch (which most will, I just like having the ability to do things mostly myself).
---------- Post added at 10:05 AM ---------- Previous post was at 09:55 AM ----------
I quoted this because this thread is like the third I've seen in the last couple days. But to offer some help, this is the guide that I've followed with two phones one running B29 stock and one running B15 Stock. It remains the same because of the use of EDL. It's also good in case you want to go back to complete stock (which at the time was speculated would brick your device) but I read between the lines and discovered that it's just not a big deal. Once you get TWRP installed, make sure your Data partition is EXT4, flash LOS, flash GApps and you're good to go.
The hardest part of the process, is getting your drivers to be recognized properly for the EDL flashing tool to work. Anti-Virus softwares tend to throw false positives with tools like the EDL Flashing tool. I installed a fresh copy of Windows 7 JUST to have a flashing station ready JIC. Once I did that, smooth sailing.
Click to expand...
Click to collapse
I've already used EDL mode from that page to put a fresh copy of stock nougat to, among other things, reduce the potential issues upgrading causes. So all I should have to do is flash B15-NEW_TWRP (Nougat) from that page and then fastboot unlock?
from there reset data/cache, flash custom ROM.
flash gapps
reboot, install apps.
?????
KyJelly69 said:
I've already used EDL mode from that page to put a fresh copy of stock nougat to, among other things, reduce the potential issues upgrading causes. So all I should have to do is flash B15-NEW_TWRP (Nougat) from that page and then fastboot unlock?
from there reset data/cache, flash custom ROM.
flash gapps
reboot, install apps.
?????
Click to expand...
Click to collapse
Yup.
kingoftheafro said:
Is that a "should work" or "does work" because I'm trying to root and install LOS also on stock non rooted nougat Axon 7 and so far I've gotten nowhere and no one seems to be able to give me a list that says Yes this works
Click to expand...
Click to collapse
In case you still need all this, I made a new guide after successfully doing everything:
https://forum.xda-developers.com/axon-7/how-to/complete-guide-to-unlocking-installing-t3561128
[email protected] said:
In case you still need all this, I made a new guide after successfully doing everything:
https://forum.xda-developers.com/axon-7/how-to/complete-guide-to-unlocking-installing-t3561128
Click to expand...
Click to collapse
Thank you for the guide, but I managed to get everything done without having to downagrade from Nougat. I was having issues with my Windows variant recognizing my phone after drivers were installed so I used Linux Mint 18.1 and everything went smooth as a whistle. I think the mods should pin your thread post.
I followed the rootjunkie YouTube videos, worked perfectly and the files were all available.
Sent from my ZTE A2017U using Tapatalk
I normally lurk around to get the information I need to root most of my devices and get root only applications. I recently got the Axon 7 (A2017U B29 Android 6.0.1) and I've perused many of the guides for rooting, TWRP, and bootloading unlocking. I have been unable to get even a single method to work at all.
https://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
This thread flatly did not work and I found out it was because the B29 model does not unlock out of the box.
https://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
I have not been able to get the axon7root.exe to work at all. I keep getting a message saying failed to say hello to the device. (the only one I could get was the zip file in the thread, the links do not work as many go to a host where the file size and download are not the same and the actual thing downloaded seems to be a random exe installer that isn't the actual file. If anyone actually has these files, I would appreciate it). I installed the qualcomm drivers, but I can't figure out which port number is correct. I see this in my device manager: QUSB_BULK with this in the properties: Port_#0001.Hub_#0003 and it isn't what is shown in those pictures. I was able to get the axon7tool to work with edl previously but I cannot get this to work no matter what I put in. It always fails to connect.
https://forum.xda-developers.com/axon-7/how-to/complete-guide-to-unlocking-installing-t3561128
Tried this as well but MiFlash could not see my phone in EDL mode.
There was another thread that used axon7tool and tried to use it to flash the recovery, but that last step never worked no matter which recovery image I attempted to use.
At this point, I am at a loss for what is actually the issue and what needs to be done. Even driver reinstalls have not changed anything (Windows 8.1 if that's relevant).
You could try the tool kit.
lafester said:
You could try the tool kit.
Click to expand...
Click to collapse
Edit: NVM, I found it. I will try this out next.
ruser453 said:
Edit: NVM, I found it. I will try this out next.
Click to expand...
Click to collapse
No, the tool kit in dev released today.
Also you need to flash signed twrp per the guide in order to unlock using your method.
lafester said:
No, the tool kit in dev released today.
Also you need to flash signed twrp per the guide in order to unlock using your method.
Click to expand...
Click to collapse
The toolkit found is exactly that one in that case. The unlock procedure from the getgo is not working as MiFlash still isn't recognizing my device and the Qualcomm drivers refuse to show up as the COM 9008 drivers like the guides are saying. The TWRP flash option on that one also explicitly says an unlocked bootloader is required. I can't see this toolkit helping much if the main tools outright refuse to work. I also DID see one of the guides mention a signed TWRP, but the link for it has been taken down and I've not seen a signed image anywhere else. I can try this on another computer I own some other time, but I can't put my finger on what isn't working.
ruser453 said:
The toolkit found is exactly that one in that case. The unlock procedure from the getgo is not working as MiFlash still isn't recognizing my device and the Qualcomm drivers refuse to show up as the COM 9008 drivers like the guides are saying. The TWRP flash option on that one also explicitly says an unlocked bootloader is required. I can't see this toolkit helping much if the main tools outright refuse to work. I also DID see one of the guides mention a signed TWRP, but the link for it has been taken down and I've not seen a signed image anywhere else. I can try this on another computer I own some other time, but I can't put my finger on what isn't working.
Click to expand...
Click to collapse
https://mega.nz/#F!kYtRAJjJ!5tD1zPpo0nw2tJwhANA9pQ!dVMjmayY
---------- Post added at 04:36 AM ---------- Previous post was at 04:34 AM ----------
You installed tenear driver so you would need to switch it back to use miflash.
Do not use that signed TWRP if you find it somewhere.
If you read the thread to the end, those users found serious problems with their IMEI restoring with that.
Most interested in the results of this thread. Is NOT clear, neither well documented (at least for me, sorry for my clumsiness)
1.- If it is necessary or not to unlock bootloader to let a normal TWRP for Axon 7 install
2.- EDL, fastboot, adb, axon7tool, axon7root.... Which method is best to flash the "good" Twrp. Why flasing TWRP in recovery requires so many operations?
3.- Are those methods (and zips, and other) equally usable for any model? and for any running firmware version?
Regards (and thank you in any case. This is not a lame claim. I do appreciate a lot all the effort that people doing tools and methods devote to help others. A lot.
lafester said:
https://mega.nz/#F!kYtRAJjJ!5tD1zPpo0nw2tJwhANA9pQ!dVMjmayY
---------- Post added at 04:36 AM ---------- Previous post was at 04:34 AM ----------
You installed tenear driver so you would need to switch it back to use miflash.
Click to expand...
Click to collapse
Thank you so much for the links. I didn't notice your post on the signed TWRP sadly. I have removed it. I did not get to peruse those threads in that much detail sadly and I did not notice the warning.
ruser, pls...
document your achievements...
And install other TWRP now you have installed the signed TWRP. At least, read that thread and do not restore a backup done with tht TWRP.
Regards
He used tenear method.
jrotaetxe said:
ruser, pls...
document your achievements...
And install other TWRP now you have installed the signed TWRP. At least, read that thread!!!
Regards
Click to expand...
Click to collapse
I will get to it when there is more time. I've already removed the signed one and installer TWRP proper. I've rooted successfully and backed things up. Xposed and moving my stuff over is all that remains. Nothing out of the ordinary so far, but I won't be using this for calls for a few days at least.
Makes sense. EDL method seems to be easy to do...
Wonder which TWRP he flashed. When receiving mine, I will try to put one "guide for lef-handed and chinese model" to stay in Marshmallow and root...
Thank you
I am looking unlock and root my European Axon 7 running Android 7.1, and all of the guides seem to be for The US version and for Android marshmallow, do I need to revert my phone to an older version (if so how would I go around doing so?). Is there any up to date guides for rooting my version of the phone?
King Norman said:
I am looking unlock and root my European Axon 7 running Android 7.1, and all of the guides seem to be for The US version and for Android marshmallow, do I need to revert my phone to an older version (if so how would I go around doing so?). Is there any up to date guides for rooting my version of the phone?
Click to expand...
Click to collapse
https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
I used this guide 2 weeks ago to unlock my wife's german axon 7, her phone was on 7.1 stock too, but no issue, you don't have to be on marshmallow. Only advice I can give you is to read the guide 2 times or more and take your time.
Btw after you done everything use the b05 modem, my wife has no call issues with this version. I flashed the dark rom to her phone, works nearly perfect.
King Norman said:
I am looking unlock and root my European Axon 7 running Android 7.1, and all of the guides seem to be for The US version and for Android marshmallow, do I need to revert my phone to an older version (if so how would I go around doing so?). Is there any up to date guides for rooting my version of the phone?
Click to expand...
Click to collapse
coremania said:
https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
I used this guide 2 weeks ago to unlock my wife's german axon 7, her phone was on 7.1 stock too, but no issue, you don't have to be on marshmallow. Only advice I can give you is to read the guide 2 times or more and take your time.
Btw after you done everything use the b05 modem, my wife has no call issues with this version. I flashed the dark rom to her phone, works nearly perfect.
Click to expand...
Click to collapse
Why though? I also used that one, but you should try axon7toolkit. It seemingly does everything automatically and with an ok CMD interface
Choose an username... said:
Why though? I also used that one, but you should try axon7toolkit. It seemingly does everything automatically and with an ok CMD interface
Click to expand...
Click to collapse
Yes that's a nice option too, but reading, understanding and knowing what you're doing always works. I'm not a fan of Kit's.
personal choice I think. But you're right.
coremania said:
Yes that's a nice option too, but reading, understanding and knowing what you're doing always works. I'm not a fan of Kit's.
personal choice I think. But you're right.
Click to expand...
Click to collapse
It seems like very few people actually use the kit. Kinda defeats the purpose.
But yeah, that guide was how I learnt how to install TWRP via axon7tool whenever I needed it.
coremania said:
https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
I used this guide 2 weeks ago to unlock my wife's german axon 7, her phone was on 7.1 stock too, but no issue, you don't have to be on marshmallow. Only advice I can give you is to read the guide 2 times or more and take your time.
Btw after you done everything use the b05 modem, my wife has no call issues with this version. I flashed the dark rom to her phone, works nearly perfect.
Click to expand...
Click to collapse
Thanks for the help! Unfortunately I must have done something wrong and I think I've soft bricked my phone! :'(
King Norman said:
Thanks for the help! Unfortunately I must have done something wrong and I think I've soft bricked my phone! :'(
Click to expand...
Click to collapse
Toolkit or step by step with the guide ? just start from scratch again, or try with the kit.
coremania said:
Toolkit or step by step with the guide ? just start from scratch again, or try with the kit.
Click to expand...
Click to collapse
Step by Step, I managed to unlock it and flash the bootstack, but I hit an error when trying to flash LOS and so decided to reboot the system and try again, however when rebooting the system I got the error "Your device software can't be checked for corruption, Please lock the bootloader". And I cant seem to access TWRP anymore, just the stock recovery.
Im just wondering if I can just flash stock because I cant use my phone at all atm
King Norman said:
Step by Step, I managed to unlock it and flash the bootstack, but I hit an error when trying to flash LOS and so decided to reboot the system and try again, however when rebooting the system I got the error "Your device software can't be checked for corruption, Please lock the bootloader". And I cant seem to access TWRP anymore, just the stock recovery.
Im just wondering if I can just flash stock because I cant use my phone at all atm
Click to expand...
Click to collapse
Then flash twrp again, if your on stock recovery. You need twrp. Something must replaced twrp with the stock recovery.
After you flashed twrp use the files from the official Los thread
Bootloader and modem.
coremania said:
Then flash twrp again, if your on stock recovery. You need twrp. Something must replaced twrp with the stock recovery.
After you flashed twrp use the files from the official Los thread
Bootloader and modem.
Click to expand...
Click to collapse
Unfortunately I cant seem to view the phone as an adb device, unless i select the "Apply update from adb" option in the stock recovery, however this only lets me sideload and i cant reboot it to edl mode or anything like that to install TWRP.
What happens if you are on stock recovery and type adb reboot edl. Another way to get to edl mode can be to shut down the phone and press both volume keys while connecting the USB cable, I read that somewhere here, may need some trys.
Btw,
"Your device software can't be checked for corruption" this is normal if your unlocked.
coremania said:
What happens if you are on stock recovery and type adb reboot edl. Another way to get to edl mode can be to shut down the phone and press both volume keys while connecting the USB cable, I read that somewhere here, may need some trys.
Btw,
"Your device software can't be checked for corruption" this is normal if your unlocked.
Click to expand...
Click to collapse
I tried the volume button thing and it must have worked because i redid the scripts and managed to get TWRP back up!
now I just need to do the universal bootstack, the N_Modem thing, and then LOS Right?
Thanks so much for your help
King Norman said:
I tried the volume button thing and it must have worked because i redid the scripts and managed to get TWRP back up!
now I just need to do the universal bootstack, the N_Modem thing, and then LOS Right?
Thanks so much for your help
Click to expand...
Click to collapse
Good, you did it. Yes, after you flashed the latest official twrp,
flash the bootloader zip and modem zip which are linked at the first page of the Los thread, then your prefered rom with gapps and root if you like.
DON'T relock your bootloader !!!
Have fun!
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.