Database Users

Is there an up to date guide for Rooting A2017G B04?

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!

Unusable A2017G

So i have this A2017G owned by a cousin of mine. He had never tempered with anything except updating OTAs from the settings app. Meaning Stock everything and BL locked. Now, all of a sudden his device lags a lot (after the N-B06 update). When booting the device the boot animation lags like crazy. And it almost never gets past the boot animation (always restarts at Axon 7). The times it does reach past the boot screen, the device hangs after a minute or so and restarts.
Things that i have tried:
# Factory resetting through stock recovery.
# Downloading update.zips from ZTE and trying SD Card update trough stock recovery. Which always fails saying Signature verification failed.
# Booted to factory test mode and tried adb devices on cmd. Nothing comes up as there is no new device on the device manager. Also no sound.
# Booted to EDL mode and flashed N-B06 from this post: https://forum.xda-developers.com/axon-7/how-to/guide-ztea2017v2-0-0b08-t3658636
Nothing helped. Same old lags. And of course, the device is unusable.
What to do? Suggestions?

nsabir said:
So i have this A2017G owned by a cousin of mine. He had never tempered with anything except updating OTAs from the settings app. Meaning Stock everything and BL locked. Now, all of a sudden his device lags a lot (after the N-B06 update). When booting the device the boot animation lags like crazy. And it almost never gets past the boot animation (always restarts at Axon 7). The times it does reach past the boot screen, the device hangs after a minute or so and restarts.
Things that i have tried:
# Factory resetting through stock recovery.
# Downloading update.zips from ZTE and trying SD Card update trough stock recovery. Which always fails saying Signature verification failed.
# Booted to factory test mode and tried adb devices on cmd. Nothing comes up as there is no new device on the device manager. Also no sound.
# Booted to EDL mode and flashed N-B06 from this post: https://forum.xda-developers.com/axon-7/how-to/guide-ztea2017v2-0-0b08-t3658636
Nothing helped. Same old lags. And of course, the device is unusable.
What to do? Suggestions?
Click to expand...
Click to collapse
Get a new phone. Unfortunately I think it's some hardware that is broken. But in case it's not try to flash b05 instead?

I don't see anything else you could do since adb doesn't seems to work. I'd just RMA it with the warranty still being in effect. And if it was purchased trough amazon you'll probably just get a new one ! (that's what happened to me last time).

nsabir said:
So i have this A2017G owned by a cousin of mine. He had never tempered with anything except updating OTAs from the settings app. Meaning Stock everything and BL locked. Now, all of a sudden his device lags a lot (after the N-B06 update). When booting the device the boot animation lags like crazy. And it almost never gets past the boot animation (always restarts at Axon 7). The times it does reach past the boot screen, the device hangs after a minute or so and restarts.
Things that i have tried:
# Factory resetting through stock recovery.
# Downloading update.zips from ZTE and trying SD Card update trough stock recovery. Which always fails saying Signature verification failed.
# Booted to factory test mode and tried adb devices on cmd. Nothing comes up as there is no new device on the device manager. Also no sound.
# Booted to EDL mode and flashed N-B06 from this post: https://forum.xda-developers.com/axon-7/how-to/guide-ztea2017v2-0-0b08-t3658636
Nothing helped. Same old lags. And of course, the device is unusable.
What to do? Suggestions?
Click to expand...
Click to collapse
Did you try downgrading through EDL? I'll post the link to MM B10 for you to install through EDL, see if that helps. I seriously doubt that it's a hardware issue since it would not even boot if that was the case (take the Nexus 6P and 5X as an example: big cores busted and the phones wouldn't get past the boot logo).
Don't unlock the bootloader if you can't fix it, it'd make matters worse if LOS-based ROMs didn't work.
Edit: Here are a couple of links for B10 from 4pda. should be the same file:
https://drive.google.com/file/d/0Bynn_Z9_tfeOZWZmN1o2U09pWVU/view
https://mega.nz/#!ZhwR1BAD!PuIWa5Vivk3DxZ1Dgk-wAoITxiKmBiR-j1U8wZZidTw

Choose an username... said:
Did you try downgrading through EDL? I'll post the link to MM B10 for you to install through EDL, see if that helps. I seriously doubt that it's a hardware issue since it would not even boot if that was the case (take the Nexus 6P and 5X as an example: big cores busted and the phones wouldn't get past the boot logo).
Don't unlock the bootloader if you can't fix it, it'd make matters worse if LOS-based ROMs didn't work.
Edit: Here are a couple of links for B10 from 4pda. should be the same file:
https://drive.google.com/file/d/0Bynn_Z9_tfeOZWZmN1o2U09pWVU/view
https://mega.nz/#!ZhwR1BAD!PuIWa5Vivk3DxZ1Dgk-wAoITxiKmBiR-j1U8wZZidTw
Click to expand...
Click to collapse
I have tried this EDL package as well. Most of the time it says can not found programmer file. Only once it said can not find hello packet, reset status. That also ended up in error.
The N-B06 EDL package flashes fine. But the problem still persists.
I have also tried replacing N-B06 recovery.img with TWRP recovery.img and flashed it. But that just bricks the recovery.
Currently the 2 EDL packages i know are these two. N-B06 and MM-B10 for the G. The N one works fine while the MM one doesn't. Do u have any other EDL packages?
I too think it's a software problem since he has never dropped the phone and only used it for 2 months.

nsabir said:
I have tried this EDL package as well. Most of the time it says can not found programmer file. Only once it said can not find hello packet, reset status. That also ended up in error.
The N-B06 EDL package flashes fine. But the problem still persists.
I have also tried replacing N-B06 recovery.img with TWRP recovery.img and flashed it. But that just bricks the recovery.
Currently the 2 EDL packages i know are these two. N-B06 and MM-B10 for the G. The N one works fine while the MM one doesn't. Do u have any other EDL packages?
I too think it's a software problem since he has never dropped the phone and only used it for 2 months.
Click to expand...
Click to collapse
I think something is wrong with the hardware. I had a similar problem as u with my last phone a honor 8, it frozed up and it was nothing I couldnt do other than go back to the store with it. I got a new one.

nsabir said:
I have tried this EDL package as well. Most of the time it says can not found programmer file. Only once it said can not find hello packet, reset status. That also ended up in error.
The N-B06 EDL package flashes fine. But the problem still persists.
I have also tried replacing N-B06 recovery.img with TWRP recovery.img and flashed it. But that just bricks the recovery.
Currently the 2 EDL packages i know are these two. N-B06 and MM-B10 for the G. The N one works fine while the MM one doesn't. Do u have any other EDL packages?
I too think it's a software problem since he has never dropped the phone and only used it for 2 months.
Click to expand...
Click to collapse
I got that package from 4pda. if you go to the 4th category brick repair manual, then enter the link that says "Qualcomm drivers and MiFlash" it will redirect you to 4pda. no need to translate: just open the spoilers (I think it's the 2nd) and you'll find all of the images. You obviously have to use the A2017G ones. there's B10, i think B11, B05, B06 and maybe another N package too
The thing is that it'd be best if you could downgrade to Marshmallow, as that would probably do some other stuff that N packages don't do.

Do you have an external SD card plugged in? Try to use without external sd, i already had lags because of a defective sd card (that couldnt be rescued nor reformatted )

Perru said:
Do you have an external SD card plugged in? Try to use without external sd, i already had lags because of a defective sd card (that couldnt be rescued nor reformatted )
Click to expand...
Click to collapse
I was gonna suggest that, but a read-only SD card wouldn't provoke that. I had one that got read-only after using it as swap for a long time, and you would only notice in twrp (booted in ~2 minutes). If he was able to try to install a system update through the recovery, he was able to write to the SD card --> it's not dead

Perru said:
Do you have an external SD card plugged in? Try to use without external sd, i already had lags because of a defective sd card (that couldnt be rescued nor reformatted )
Click to expand...
Click to collapse
It lags the same. Regardless a sd card is inserted or not.

Choose an username... said:
I got that package from 4pda. if you go to the 4th category brick repair manual, then enter the link that says "Qualcomm drivers and MiFlash" it will redirect you to 4pda. no need to translate: just open the spoilers (I think it's the 2nd) and you'll find all of the images. You obviously have to use the A2017G ones. there's B10, i think B11, B05, B06 and maybe another N package too
The thing is that it'd be best if you could downgrade to Marshmallow, as that would probably do some other stuff that N packages don't do.
Click to expand...
Click to collapse
Thank you for mentioning there is EDL packages in 4pda. I just tried the packages that are available for the G variant on 4pda. But the problem still persists.
I was thinking that too. Trying to downgrade through EDL. But so far i've found only one MM so far, B10. But that ends up in error during flashing process.
Is there any way to install TWRP through EDL without unlocking bootloader? Also, is there any way to unlock BL without adb? If i could at least unlock the BL, i could flash twrp through EDL. There are EDL packages available for flashing TWRP.
Thanks.

nsabir said:
Thank you for mentioning there is EDL packages in 4pda. I just tried the packages that are available for the G variant on 4pda. But the problem still persists.
I was thinking that too. Trying to downgrade through EDL. But so far i've found only one MM so far, B10. But that ends up in error during flashing process.
Is there any way to install TWRP through EDL without unlocking bootloader? Also, is there any way to unlock BL without adb? If i could at least unlock the BL, i could flash twrp through EDL. There are EDL packages available for flashing TWRP.
Thanks.
Click to expand...
Click to collapse
Why don't u just go back to the store with it and get a new one? Its clearly something that can't be fixed by yourself unfortunately.

jw1985 said:
Why don't u just go back to the store with it and get a new one? Its clearly something that can't be fixed by yourself unfortunately.
Click to expand...
Click to collapse
Not all that clear, but yeah the last thing I'd do is unlock the bootloader.

Choose an username... said:
Not all that clear, but yeah the last thing I'd do is unlock the bootloader.
Click to expand...
Click to collapse
Mabey but I think as in my case that something has happened with the hardware. I think it is a hardware's fault that has come up to the surface when he updated the phone like it did 2 me. But hey, it's just my theory.

jw1985 said:
Why don't u just go back to the store with it and get a new one? Its clearly something that can't be fixed by yourself unfortunately.
Click to expand...
Click to collapse
Choose an username... said:
Not all that clear, but yeah the last thing I'd do is unlock the bootloader.
Click to expand...
Click to collapse
jw1985 said:
Mabey but I think as in my case that something has happened with the hardware. I think it is a hardware's fault that has come up to the surface when he updated the phone like it did 2 me. But hey, it's just my theory.
Click to expand...
Click to collapse
The problem is axon 7 is not available in our country. If he has to rma it then he has to send it to a relative in Sweden. Then the relative can do that for him. That's why he asked me to do what i can to revive the phone. RMA is the last resort for him.
Now, i guess i will give up and tell him i did everything i could.
Anyways, thank you all for helping.

Screen Not Responsive After Flash ..... +

Hey,
I've been on quite a journey since I attempted to flash the Treble rom for newbies. My phone eventually ended up as DFU'd but, I brought it back to life after a following the DFU Unbrick - Disassembly guide. After doing this, the screen was not responsive to touch at all at the Welcome screen of the EDU ROM. So, my adventure continued as I took the phone apart several times again to make certain things were connected, not damaged, etc..
After flashing TWRP I concluded the screen itself must be fine because I could use TWRP using the screen/touch. I have since tried flashing several different roms, tried many combos of unlocking the bootloader (again, because I assume it was already unlocked due to the bootloader warning screen of can not check for corruption message), tried flashing bootstack and the stock rom from DrakenFX. Used MiFlash, EDM Tool to flash various items.
Each time and currently, when it boots to the Welcome screen it does not respond to touch.
Can anyone please help me with this?
Thank you!

I remember this happened to me some years ago with a different phone, and it was a bad flash.
I resolved it by flashing the stock firmware again.
What did you flash with MiFlash? Stock firmware untouched? You must do this, try with B35 untouched. Don't flash stuff with TWRP.

Untouched? Is there anything on here like that?

https://androidfilehost.com/?fid=962187416754472312 B35 A2017U
https://androidfilehost.com/?fid=746010030569960045 B10 A2017G
https://www.androidfilehost.com/?fid=818070582850490196 B14 A2017CN
Those are "untouched" system images. Replace recovery.img with a proper TWRP version before flashing:
https://androidfilehost.com/?fid=673956719939822011

bornlivedie said:
https://androidfilehost.com/?fid=962187416754472312 B35 A2017U
https://androidfilehost.com/?fid=746010030569960045 B10 A2017G
https://www.androidfilehost.com/?fid=818070582850490196 B14 A2017CN
Those are "untouched" system images. Replace recovery.img with a proper TWRP version before flashing:
https://androidfilehost.com/?fid=673956719939822011
Click to expand...
Click to collapse
Yeah, unfortunately the very first link (since I am in the USA and have a U version) is the very stock EDL version I used with MiFlash rightg after I was successful getting the phone out of DFU. I have tried flashing it twice after and still nothing.
Thank you for helping!!!

djprez said:
Yeah, unfortunately the very first link (since I am in the USA and have a U version) is the very stock EDL version I used with MiFlash rightg after I was successful getting the phone out of DFU. I have tried flashing it twice after and still nothing.
Thank you for helping!!!
Click to expand...
Click to collapse
Sad to hear that... Maybe you can try again? Who knows, with a little bit of luck...
Or try another version, like this one:
https://www.androidfilehost.com/?fid=890129502657579386
btw, did you try every single spot in your screen while in TWRP? Maybe some pins in the connector are broken and some parts work and others doesn't?
And for the sake of it, you could try discharging your battery completely.
Last thing I can think of... is to restore the stock recovery and apply the official update via sdcard:
https://www.dropbox.com/s/xy7nd252f3rcm5y/338450B3220A2017UV1.1.0B35(SD card software).zip?dl=0
It was taken from here:
https://www.zteusa.com/axon-7#support

bornlivedie said:
Sad to hear that... Maybe you can try again? Who knows, with a little bit of luck...
Or try another version, like this one:
https://www.androidfilehost.com/?fid=890129502657579386
btw, did you try every single spot in your screen while in TWRP? Maybe some pins in the connector are broken and some parts work and others doesn't?
And for the sake of it, you could try discharging your battery completely.
Last thing I can think of... is to restore the stock recovery and apply the official update via sdcard:
https://www.dropbox.com/s/xy7nd252f3rcm5y/338450B3220A2017UV1.1.0B35(SD card software).zip?dl=0
It was taken from here:
https://www.zteusa.com/axon-7#support
Click to expand...
Click to collapse
Yeah, the entire screen works perfectly in TWRP. I disassembled it several times before when I thought I may have put it back together wrong or damaged something so, the battery was removed those several times therefore, no power.
I'll try the stock above. I'm actually trying another stock rom atm --- flashing from sdcard

djprez said:
Yeah, the entire screen works perfectly in TWRP. I disassembled it several times before when I thought I may have put it back together wrong or damaged something so, the battery was removed those several times therefore, no power.
I'll try the stock above. I'm actually trying another stock rom atm --- flashing from sdcard
Click to expand...
Click to collapse
Well, EUREKA! I found I had saved the first files you were supposed to load when the Axon was first unlocked ( file name STEP_1_3-B20_FULL_OTA). Flashed it and the screen works fine. Now, I have to remember how to update it...lol I've unlocked the bootloader in Developer mode and I should be on my way..... fingers crossed.

djprez said:
Well, EUREKA! I found I had saved the first files you were supposed to load when the Axon was first unlocked ( file name STEP_1_3-B20_FULL_OTA). Flashed it and the screen works fine. Now, I have to remember how to update it...lol I've unlocked the bootloader in Developer mode and I should be on my way..... fingers crossed.
Click to expand...
Click to collapse
Strange.
Nevertheless, congratulations. Happy for you.

Well, it's great that I now know the screen/hardware is fine but, I am unable to get any further than version B20. OTA doesn't work, the other files to flash (STEP_4-B20_to_B27 and STEP_5-B27_to_B29) won't flash and get aborted due to it expecting a certain version. I've tried DrakenFX Bootstack and then Stock System and it boots to the Welcome screen but the screen is no longer responsive again.
I have been at this all day again and it's shaping up another all night too. I am so baffled!

Restore to stock firmware your phone came shipped with.After that update trough ota or sd card package and maybe dont flash Treble again,its broken

djprez said:
Well, it's great that I now know the screen/hardware is fine but, I am unable to get any further than version B20. OTA doesn't work, the other files to flash (STEP_4-B20_to_B27 and STEP_5-B27_to_B29) won't flash and get aborted due to it expecting a certain version. I've tried DrakenFX Bootstack and then Stock System and it boots to the Welcome screen but the screen is no longer responsive again.
I have been at this all day again and it's shaping up another all night too. I am so baffled!
Click to expand...
Click to collapse
i wish i had seen this sooner, because i have this same exact problem on one of my boards. it will update perfectly to any of the MM sd card update files (see rootjunkys bl unlock video, thanks @Tomsgt) but the board/phone will not retain touch functionality on anything higher than mm b29. i had lost my imei on that board, and actually swapped to another one despite eventually regaining it simply bc i wanted to be on Oreo ROMs. if you find a fix, id love to know about it. i flashed and reflashed every update, sd card versions, edl versions, and OTA updates to no avail. Nougat or above, touchscreen didnt work... mine was a gold a2017u. good luck, man. im glad im not crazy.

Sorry to bump an old(er) thread I started. I wanted to ask if anyone has found a solution to this issue yet?
I have since tried updating using OTA to Nougat and the screen doesn't respond so, I had to flash back to Marshmallow B29. Thank you to anyone who might have an idea!

After Pie: Bootloader unlocked & TWRP install didn't work

Hi,
I was really unhappy with Pie and tried to prepare my device for Oreo downgrade.
What I did was
- unlock bootloader
- tried to install TWRP
- mixed something up in that processs
- realized TWRP cannot be installed apparently on Pie right now
- MiFlash seems to be not working as well when trying to install stock rom (says flashing but nothing happens)
Well Pie is running right now, but when trying to lock the bootloader again for future updates, the phones is only showing a black screen.
After that I am trying to unlock bootloader again (fastboot oem unlock) and everything works again, except when I try to boot into recovery ("the system is destroyed" or something like that).
Trying to "hotboot" into TWRP currently is also not working, "unable to mount..." and after that automatically reboots into the system itself.
Any idea how I can either put a standard Pie installation with working recovery and locked bootloader on?
Or how I can maybe install Oreo instead? As I said, the MiFlash tool doesn't do anything (tells me "flashing" but actually doesn't do anything).
Thanks for your help!

cyrrel said:
Hi,
I was really unhappy with Pie and tried to prepare my device for Oreo downgrade.
What I did was
- unlock bootloader
- tried to install TWRP
- mixed something up in that processs
- realized TWRP cannot be installed apparently on Pie right now
- MiFlash seems to be not working as well when trying to install stock rom (says flashing but nothing happens)
Well Pie is running right now, but when trying to lock the bootloader again for future updates, the phones is only showing a black screen.
After that I am trying to unlock bootloader again (fastboot oem unlock) and everything works again, except when I try to boot into recovery ("the system is destroyed" or something like that).
Trying to "hotboot" into TWRP currently is also not working, "unable to mount..." and after that automatically reboots into the system itself.
Any idea how I can either put a standard Pie installation with working recovery and locked bootloader on?
Or how I can maybe install Oreo instead? As I said, the MiFlash tool doesn't do anything (tells me "flashing" but actually doesn't do anything).
Thanks for your help!
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-a1/development/treble-twrp-installer-treble-manager-t3793637

Hi,
I somehow managed to put 8.1 on and everything is back to normal.
Thanks

cyrrel said:
Hi,
I somehow managed to put 8.1 on and everything is back to normal.
Thanks
Click to expand...
Click to collapse
can you explain us the procedures that you have followed to downgrade. It would be really helpful. i have tried this
method but it didn't work for me. i am facing IMEI 0/no signal issues using this method.
Thanks

well I have done a lot of stuff that made my phone not working anymore because using a wrong .img file and didn'T understand the tutorial (same link you have provided) fully.
But at the end it was quite close to the link you have sent, the MiFlash tool I needed for example to try like 10 times per step until it worked, maybe a bad cable - I don't know.
But finally it was working, after March update without network signal, but with /boot & /efs partitions and Nov fastboot image, it was working.
If you need any more detail for a specific step, you can of course ask and I can check if there was anything special I can remember

cyrrel said:
well I have done a lot of stuff that made my phone not working anymore because using a wrong .img file and didn'T understand the tutorial (same link you have provided) fully.
But at the end it was quite close to the link you have sent, the MiFlash tool I needed for example to try like 10 times per step until it worked, maybe a bad cable - I don't know.
But finally it was working, after March update without network signal, but with /boot & /efs partitions and Nov fastboot image, it was working.
If you need any more detail for a specific step, you can of course ask and I can check if there was anything special I can remember
Click to expand...
Click to collapse
Are your imei & mac same as original? won't the imei/mac get affected by restoring someone else efs?

I don't know about mac, but imei is ok

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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