Database Users

Having problem rooting my Axon 7 A2017U

Hey guys, first of all sorry about my english, im french.
So my problem is: I tried rooting my Axon 7 A2017U many times, with different guides. I always end up with a softbricked phone, having to restore to stock using MiFlash.
My bootloader is unlocked, i have stock recovery and stock rom for now.
Whenever i flash TWRP, either the signed one (from @tenfar) or unsigned (and up to date) ones, i can't go past the menu saying something like "your phone cant be checked for corruption, please lock your phone [...]" it just freeze. i did read somewhere that i should flash chainfire's root or a special .zip that, i guess, disabled some check that could prevent booting a phone with unsigned stuff/edited system (after flashing TWRP, so it could boot) that didn't work out. i think i found that information in some LineageOS thread here on XDA.
My ultimate goal would be to get a rooted stock nougat 7.1.1, up to date TWRP recovery and to be able to switch to LineageOS to try it out soon.
For what it is worth, i rooted many phones over the years, so while i'm no expert, i should be able to follow most of the steps you give me.
Thanks alot!

What version of TWRP did you flash first?

I have the same root problem i can not install in twrp install in twrp ok but su application displays no root cause i have latest twrp

KwesiJnr said:
What version of TWRP did you flash first?
Click to expand...
Click to collapse
this
https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715
And @tenfar's signed one

KwesiJnr said:
What version of TWRP did you flash first?
Click to expand...
Click to collapse
this
https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715
And @tenfar's signed one

Okay. Download and flash this one alone via fastboot and see what happens. This is one the I personally use. It is required for any of the newer versions to work properly.
twrp-3.0.2-2-a2017u.img
You can choose to rename it to just recovery.img, then:
1. fastboot flash recovery recovery.img
or
2.
if you choose to work with the same filename:
fastboot flash recovery twrp-3.0.2-2-a2017u.img
Select reboot to recovery from the bootloader menu now and try again.
Either way, should work fine. I know you mentioned you knew the basics, but just want to be sure.
Also forgot to mention. If TWRP works but you still can't get your phone to boot, you need to follow this guide here
You can start from the part that says:
-----------------------------------------------------
UPDATING FROM B20_Boot / B20 / B27 / B29 / B15(N)
-----------------------------------------------------
Again, that's the ROM I personally use if I want to go back to stock, not the one from the ZTE site.

Gonna try it and give feedback. thanks for taking time to help!
edit: im downloading the rom from the link you shared.
like you said, i can get TWRP to boot but not the phone.
So if i use full stock from ZTE, it can't boot with modified recovery?
edit 2: i don't know what worked, i think it might be the bootstack. or the rom by DrakenFX. now i can boot to the rom with a TWRP recovery installed. It worked, but i soft bricked again trying to flash SuperSU. So now i'm retrying with an updated TWRP.

I haven't tried that yet, but I really suspect that's the reason you're having problems. I rarely use pure stock ROMs. Like you, I'm not an expert in Android Development so I can't tell you why. Just been a flashaholic for years so made a few observations.

Which supersu are you installing? If you're swiping to the right in twrp, you need to install the dm-verity zip or supersu 2.79. There's some issues with newer builds.

Everything is working like a charm! Now im going to finally give lineageOS a try
I used Chainfire's SuperSU 2.79 stable.
Edit : Everything is working flawlessly! I'm running the lastest LineageOS nightly with root (Chainfire's 2.79). Followed their instruction and installation was smooth as butter. I should also point out i flashed the lastest official TWRP which seems more stable than the one @KwesiJnr suggested. The one he suggested was giving me some "can't read X partition" in red text everywhere in the log section, which the official one doesn't do. It was doing his job properly anyway though.
I can't thank @KwesiJnr enough, it helped me find the single mistake i was making.

lololo2 said:
Everything is working like a charm! Now im going to finally give lineageOS a try
I used Chainfire's SuperSU 2.79 stable
Click to expand...
Click to collapse
Glad you're up and running root. :good:

lololo2 said:
Everything is working like a charm! Now im going to finally give lineageOS a try
I used Chainfire's SuperSU 2.79 stable.
Edit : Everything is working flawlessly! I'm running the lastest LineageOS nightly with root (Chainfire's 2.79). Followed their instruction and installation was smooth as butter. I should also point out i flashed the lastest official TWRP which seems more stable than the one @KwesiJnr suggested. The one he suggested was giving me some "can't read X partition" in red text everywhere in the log section, which the official one doesn't do. It was doing his job properly anyway though.
I can't thank @KwesiJnr enough, it helped me find the single mistake i was making.
Click to expand...
Click to collapse
Yeah, like I mentioned before that was the base TWRP you needed to flash first, before any of the newer ones. You weren't intended to use it indefinitely.
There's a lot of Dev love for our device now and support is growing ... exciting new ROMs cropping up. Don't hesitate to try them out.

Won't boot into system or fastboot

Hello,
Just got it and already bricked it, hooray.
I did the Nougat update and allowed modifications (the swipe in TWRP). I'm dumb
So here's everything I did :
First I used the Axon 7 Toolkit by BKORES to unlock bootloader and flash TWRP.
At step 9), It failed to boot TWRP even tho I could access it with power+volume.
It eventually would get stuck at the ZTE logo when I wanted to boot system.
I flashed SuperSU with an SD card in recovery.
So : Fastboot and system won't work. Recovery would, and so does bootloader from this.
What should I do ?

CiT42 said:
Hello,
Just got it and already bricked it, hooray.
I did the Nougat update and allowed modifications (the swipe in TWRP). I'm dumb
So here's everything I did :
First I used the Axon 7 Toolkit by BKORES to unlock bootloader and flash TWRP.
At step 9), It failed to boot TWRP even tho I could access it with power+volume.
It eventually would get stuck at the ZTE logo when I wanted to boot system.
I flashed SuperSU with an SD card in recovery.
So : Fastboot and system won't work. Recovery would, and so does bootloader from this.
What should I do ?
Click to expand...
Click to collapse
Nah this is a soft brick, nothing to worry about
Maybe your SuperSU did some bad stuff on the rom. For exampls if you flash SuperSU 2.79 or higher on Android 6 (at least in the stock rom) it won't boot. Maybe try flashing Magisk B13? I think it gets rid of SuperSU
There's a no-verity-opt-encrypt file too, somewhere in this forum, maybe in Kernels, ROMs thread. Maybe give it a shot
Another way is going back to the stock recovery and flash an official package. I have made an easy guide for the A2017G, not sure if it works on the U or chinese. you can find it over at Guides, should be pretty close to the top
If you have an A2017U you can get the DrakenFX system files and install them, maybe you can fix the stuff
Or take the easy way, and install a custom ROM. Not the best choice unless you're willing to withstand some small bugs and stuff. The way to install them is get the A2017X_Universal_Bootstack and corresponding modem for your model, plus the ROM and OpenGApps 7.1.2 arm64 (Or beansgapps if the rom specifies), and of course the ROM itself. You wipe system, data, caches (not necessarily internal) then flash the Universal Bootstack and tbe modem, then the ROM, then GApps if you want to have them, then Magisk or SuperSU if you want root (some roms come with self-installing Magisk in the same package, too).
Or use MiFlash and flash a complete stock image of your phone's system. That one works like a charm

Choose an username... said:
Nah this is a soft brick, nothing to worry about
Maybe your SuperSU did some bad stuff on the rom. For exampls if you flash SuperSU 2.79 or higher on Android 6 (at least in the stock rom) it won't boot. Maybe try flashing Magisk B13? I think it gets rid of SuperSU
There's a no-verity-opt-encrypt file too, somewhere in this forum, maybe in Kernels, ROMs thread. Maybe give it a shot
Another way is going back to the stock recovery and flash an official package. I have made an easy guide for the A2017G, not sure if it works on the U or chinese. you can find it over at Guides, should be pretty close to the top
If you have an A2017U you can get the DrakenFX system files and install them, maybe you can fix the stuff
Or take the easy way, and install a custom ROM. Not the best choice unless you're willing to withstand some small bugs and stuff. The way to install them is get the A2017X_Universal_Bootstack and corresponding modem for your model, plus the ROM and OpenGApps 7.1.2 arm64 (Or beansgapps if the rom specifies), and of course the ROM itself. You wipe system, data, caches (not necessarily internal) then flash the Universal Bootstack and tbe modem, then the ROM, then GApps if you want to have them, then Magisk or SuperSU if you want root (some roms come with self-installing Magisk in the same package, too).
Or use MiFlash and flash a complete stock image of your phone's system. That one works like a charm
Click to expand...
Click to collapse
I flashed DrakenFX's B29 stock rom. Didn't thought it would work with recovery but anyway ! Thank you.
Do you recommend some ROMs, kernels, etc ?

CiT42 said:
Do you recommend some ROMs, kernels, etc ?
Click to expand...
Click to collapse
Nah, they are all mostly bad. The best of the bunch seems to be NucleaRom, it has an okay kernel (Radioactive, not too good battery-wise but I've never seen so little UI lag, like, ever) and okay features (like 1/3 of what ResurrectionRemix has), an awesome maintainer (OrdenKrieger) and boots in like 15 seconds
But the stock ROM is currently the best of them all, not battery wise (you can get some obscenely high SOT numbers on LineageOS with Substratum black themes) but it's fluid and stuff runs well on it. The status bar is hideous though, and MiFavor is white themed, on an AMOLED screen, what the crap ZTE?
Don't try PureNexus, permanent hard brick from the looks of it.
LineageOS works okay but it has some compatibility problems with some apps I use, dunno
I think you could try the dual-boot patcher, that way you can test the roms and keep a working stock rom to use it as your daily driver without losing data. i never used the dual boot patcher though, so good luck if you will use it

I've bad experiences with Dual boot on my old 1+.

Clarify ZIP kernel flashing in A/B partitions

Hi,
Why can I not successfully flash a zip kernel such as Elemental X or the Rey kernel? The .img file from the Neutrino kernel via fastboot works great. But with zips I get stuck on boot animation regardless of how long it sits. I've flashed in twrp or sideloaded in both twrp or stock recovery. In most cases I'm rooted and on custom ROM, and i especially liked B2 Android P (but no fling navigation and it didn't want to allow root for some reason?) Here's my understanding of the way it goes. As I'm just a novice, please correct my understanding of any concept or feel free to share any extra tips. I feel confident in getting from BTS to rooted custom rom and .img kernel. So my problems are probably in the way it works flashing zips in twrp. My questions are:
Say I'm on partition A running AICP rooted with Magisk and I want to install the ElementalX kernel. So I reboot to boatloader, fastboot flash boot twrp , staying on the same partition (side A) (switch sides here?).... i generally dont. Here is where the confusion comes. I know TWRP will flash a rom to the oppsite partition, so if I flash under this current scenario where i booted into TWRP on side A it will flash a ROM to side B. Additionally: Do I first need to flash the stock boot image here? It seems yes and no people include this as a step. Assuming i should, flashing an image file will stay on the same side, right?So I have flashed the stock boot image and now am installing the kernel zip. Do I flash the zip kernel to the same side (side A) it will be used on, or does it flash to the opposite side like a ROM will? Do all non-ROM zips flash in the same manner? If sideloading, does it have the same result as flashing within twrp?[/I]
To my knowledge I've never gotten past this and, "essentially" lol, have to use a kernel that is installed with fastboot, otherwise I get either bootlooped or stuck on the boot animation. I can get it booted by flashing a kernel via fastboot, but not a zip in twrp. thanks for the read. bonus question is below.
thanks
BONUS- it KILLS me not having a built in option on any ROM to reboot into the other partition to use twrp. Why is there not a mod for this? And i've seen with the Pixel phone and others they have gotten twrp to stick, but that involved using a flashable zip lol if feel ilike

KingBeefy said:
Hi,
Why can I not successfully flash a zip kernel such as Elemental X or the Rey kernel? The .img file from the Neutrino kernel via fastboot works great. But with zips I get stuck on boot animation regardless of how long it sits. I've flashed in twrp or sideloaded in both twrp or stock recovery. In most cases I'm rooted and on custom ROM, and i especially liked B2 Android P (but no fling navigation and it didn't want to allow root for some reason?) Here's my understanding of the way it goes. As I'm just a novice, please correct my understanding of any concept or feel free to share any extra tips. I feel confident in getting from BTS to rooted custom rom and .img kernel. So my problems are probably in the way it works flashing zips in twrp. My questions are:
Say I'm on partition A running AICP rooted with Magisk and I want to install the ElementalX kernel. So I reboot to boatloader, fastboot flash boot twrp , staying on the same partition (side A) (switch sides here?).... i generally dont. Here is where the confusion comes. I know TWRP will flash a rom to the oppsite partition, so if I flash under this current scenario where i booted into TWRP on side A it will flash a ROM to side B. Additionally: Do I first need to flash the stock boot image here? It seems yes and no people include this as a step. Assuming i should, flashing an image file will stay on the same side, right?So I have flashed the stock boot image and now am installing the kernel zip. Do I flash the zip kernel to the same side (side A) it will be used on, or does it flash to the opposite side like a ROM will? Do all non-ROM zips flash in the same manner? If sideloading, does it have the same result as flashing within twrp?[/I]
To my knowledge I've never gotten past this and, "essentially" lol, have to use a kernel that is installed with fastboot, otherwise I get either bootlooped or stuck on the boot animation. I can get it booted by flashing a kernel via fastboot, but not a zip in twrp. thanks for the read. bonus question is below.
thanks
BONUS- it KILLS me not having a built in option on any ROM to reboot into the other partition to use twrp. Why is there not a mod for this? And i've seen with the Pixel phone and others they have gotten twrp to stick, but that involved using a flashable zip lol if feel ilike
Click to expand...
Click to collapse
Sup guy:
A: sides won't switch, if you flash twrp on a, you will stay on A, just make sure you have disabled all locks, pins, swipes, and fingerprint s in room prior...which leads me to B
B: you must flash a stock boot.img (just ex doesn't help, due to system as root), then flash EX, then magisk, in that order, every time.
So.... Flash twrp-->get into twrp recovery-->FLASH STOCKBOOT.IMG VERY IMPORTANT-->flash custom kernel (this is obviously optional)--->magisk--->reboot

Additionally, I recall having issues getting kernels to flash if I didn't swipe all modifications in twrp. I would have the same issues as the OP when I didn't.

Milly7 said:
Additionally, I recall having issues getting kernels to flash if I didn't swipe all modifications in twrp. I would have the same issues as the OP when I didn't.
Click to expand...
Click to collapse
I promise the way above works

aer0zer0 said:
Sup guy:
A: sides won't switch, if you flash twrp on a, you will stay on A, just make sure you have disabled all locks, pins, swipes, and fingerprint s in room prior...which leads me to B
B: you must flash a stock boot.img (just ex doesn't help, due to system as root), then flash EX, then magisk, in that order, every time.
So.... Flash twrp-->get into twrp recovery-->FLASH STOCKBOOT.IMG VERY IMPORTANT-->flash custom kernel (this is obviously optional)--->magisk--->reboot
Click to expand...
Click to collapse
with roms that have built in updates, do i lose root and have to repeat this procedure every time a weekly update happens? the lack of a permanent twrp recovery is so inconvenient

envizion58 said:
with roms that have built in updates, do i lose root and have to repeat this procedure every time a weekly update happens? the lack of a permanent twrp recovery is so inconvenient
Click to expand...
Click to collapse
Like LOS and whatever, yeah, but it takes like 2 minutes. Stock won't flash, since magisk is there anyways

aer0zer0 said:
Sup guy:
A: sides won't switch, if you flash twrp on a, you will stay on A, just make sure you have disabled all locks, pins, swipes, and fingerprint s in room prior...which leads me to B
B: you must flash a stock boot.img (just ex doesn't help, due to system as root), then flash EX, then magisk, in that order, every time.
So.... Flash twrp-->get into twrp recovery-->FLASH STOCKBOOT.IMG VERY IMPORTANT-->flash custom kernel (this is obviously optional)--->magisk--->reboot
Click to expand...
Click to collapse
Thanks! the instruction you gave worked splendidly. I'm only a few months into modding and there are things that become so clear when someone tells you something that answers multiple questions. Thanks in specific for the "whatever side you boot into twrp with is the side you will flash on" . The rebooting sides in twrp doesnt function like an actual reboot.. no one has said that. so , one question down.
staying on topic with twrp, why can someone not write a script or something to reboot to the other side. I've been attempting to install it permanently to that partition like other a/b devices but the hangup for that is they all start with booting twrp using fastboot boot .file instead of flashboot flash boot command. is there an alternative way ti biit without flashing as the ph-1 bootloader doesnt recognize that command? the rest seems easy. but needing to have a computer any time something goes awry is really an inconvenience and if a patch exists I havent found it. you opened the door for this question by giving me the Thomas Edison moment in the first answer. Can't wait for a repeat cuz I'm dying to know this answer. Thanks again bud

Milly7 said:
Additionally, I recall having issues getting kernels to flash if I didn't swipe all modifications in twrp. I would have the same issues as the OP when I didn't.
Click to expand...
Click to collapse
Hopefully I'm reading this correctly, but if you are referring to swiping as opposed to sideloading I've noticed that too. i do still sideload the ROMs but I swipe all mods and kernels. commonly I would get an error regarding /system not remounting after some flashes but that stopped a while back. @topjohnwu commented in a magisk thread to mount system before flashing as a fix. Its worked great.
Thanks for the response and if i read your question wrong fire it back at me for a second attempt lol

KingBeefy said:
Thanks! the instruction you gave worked splendidly. I'm only a few months into modding and there are things that become so clear when someone tells you something that answers multiple questions. Thanks in specific for the "whatever side you boot into twrp with is the side you will flash on" . The rebooting sides in twrp doesnt function like an actual reboot.. no one has said that. so , one question down.
staying on topic with twrp, why can someone not write a script or something to reboot to the other side. I've been attempting to install it permanently to that partition like other a/b devices but the hangup for that is they all start with booting twrp using fastboot boot .file instead of flashboot flash boot command. is there an alternative way ti biit without flashing as the ph-1 bootloader doesnt recognize that command? the rest seems easy. but needing to have a computer any time something goes awry is really an inconvenience and if a patch exists I havent found it. you opened the door for this question by giving me the Thomas Edison moment in the first answer. Can't wait for a repeat cuz I'm dying to know this answer. Thanks again bud
Click to expand...
Click to collapse
with our TWRP being janky as it is, trust me, you dont want living in the other slot.

Spent 6+ Hours Trying To Get Rooted Android 10

I tried rooting my OP6T on Android 10, and was up half the night. Recovered from a hard brick twice, using the Qualcomm serial flash tool thing. I was trying to flash Majisk, and read that it had to be done via a custom recovery like TWRP. All the guides said that it to boot TWRP, then basically flash TWRP using itself so that it says. Fastboot kept saying "Remote Unknown Command" when using "fastboot boot" like all the guides said. Then someone told me to run "fastboot flash boot twrp.img". This caused the first hard brick. I guess because I wrote the recovery over the boot partition. I then found a post somewhere where someone said that Oneplus Devs removed the boot command from Fastboot for some reason. No idea why!! But no one else in the OP6T TWRP thread reported issues. Maybe they were all installing TWRP on an Android 9.x build that diden't have this issue? Eventually after recovering and flashing several layers on OTA updates through the local upgrade option, I was back on A10 OB2. But I still wanted root and hadn't got TWRP working yet. Then I found a random post buried in a random thread somewhere saying that custom recoveries on A10 are useless at this point period because TWRP can't flash the system partition, as it's read only. Not sure if this only applies to OP devices?
I am now back to where I started. I would still like twrp for backups, but since it's not cooperating, I try the alternative option for Masisk, involving the patched boot.img file. I download the patched the patched boot file in this thread. Flashed it with "fastboot flash boot boot.img", and got my 2nd hard brick. It would get stuck at the bootloader warning screen and no fastboot.
Now i've lost my data, 6+ hour of time, and no closer than I was before.
I am going to take a break now, cause I need an operational phone this week. Word of advice: If you're not a developer that knows exactly what they are doing, don't even attempt to get root on an Android 10 build!

You can install Magisk,manager,extract the boot img from the OOS zip file using payload_dumper,copy that boot img. to your phone,patch the image with magisk,copy to your PC then fastboot the patched image to your phone .And yes,you cannot have twrp yet.

I'm on the open beta 2 of Android 10 and I have root and TWRP. It's possible.

It's not that hard, you don't even need twrp to install magisk. in android 10.
download open beta 2 Android 10. Extract payload.bin from it. Use payload_dumper to extract boot
install magisk apk, and patch boot.
go to fastboot use the
"Fastboot flash boot_a patched_boot.img "
and you are done.

Sh4d0wk1ng said:
It's not that hard, you don't even need twrp to install magisk. in android 10.
download open beta 2 Android 10. Extract payload.bin from it. Use payload_dumper to extract boot
install magisk apk, and patch boot.
go to fastboot use the
"Fastboot flash boot_a patched_boot.img "
and you are done.
Click to expand...
Click to collapse
I think I see what I did! I need to use "fastboot flash boot_a" (or b), and not just "fastboot flash boot". Not sure how you know whether to use a or b without a custom recovery though? Because AFAIK, the fastboot command for that is broken.
Not sure what payload dumper is, but I should be able to use the the same patched boot image that everyone else used since it's for that same ROM, now that I known exactly where to flash it to (besides A or B).
When I flashed to "boot" before, I must have overwritten some kind of low-level pre-bootloader, lol.
Thank you
Bhamilton0347 said:
I'm on the open beta 2 of Android 10 and I have root and TWRP. It's possible.
Click to expand...
Click to collapse
How did you achieve this? Do you have to start with A9 with TWRP, and then somehow upgrade to A10 without overwriting it with stock recovery?
I found this guide, but step 2 does not make sense to me. How could you flash TWRP inside of the Masisk Manager app?
I imagine you still can't flash system with TWRP, but everything else works?
Thank you
roman gabriel said:
You can install Magisk,manager,extract the boot img from the OOS zip file using payload_dumper,copy that boot img. to your phone,patch the image with magisk,copy to your PC then fastboot the patched image to your phone .And yes,you cannot have twrp yet.
Click to expand...
Click to collapse
I think the issue was that I flashed to the wrong place. See above. Thank you.

I'm feeling extremely lazy rn and I don't feel like explaining all of the trouble I went through to get it working, but you should be able to just fastboot flash these images to their respective partitions and you should have both TWRP and Magisk. It's got Magisk 20.1, the modified one so that EdXposed will work. But they're functionally the same.
https://drive.google.com/file/d/149TqVLqKr7Rc8xygMDoUyY_SLoATQrRq/view?usp=drivesdk
Let me know if it works.
Note: this is the boot.img for the second open beta of Android 10 for the OnePlus 6T. This may also work on the stable and first beta release as well as even on the 6, but I do not know. Also, your SIM card may not be showing up, but this problem disappeared for me a minute or two after boot.

Bhamilton0347 said:
I'm feeling extremely lazy rn and I don't feel like explaining all of the trouble I went through to get it working, but you should be able to just fastboot flash these images to their respective partitions and you should have both TWRP and Magisk. It's got Magisk 20.1, the modified one so that EdXposed will work. But they're functionally the same.
https://drive.google.com/file/d/149TqVLqKr7Rc8xygMDoUyY_SLoATQrRq/view?usp=drivesdk
Let me know if it works.
Note: this is the boot.img for the second open beta of Android 10 for the OnePlus 6T. This may also work on the stable and first beta release as well as even on the 6, but I do not know. Also, your SIM card may not be showing up, but this problem disappeared for me a minute or two after boot.
Click to expand...
Click to collapse
Thank you. I can't risk it right now. But i'll try sometime. Anyone wanna be the guinea pig?
If it works well, it should be very useful to the community.
I am brand new to Majisk by the way. It's been a couple years since I was rooted.

flyoffacliff said:
Thank you. I can't risk it right now. But i'll try sometime. Anyone wanna be the guinea pig?
If it works well, it should be very useful to the community.
I am brand new to Majisk by the way. It's been a couple years since I was rooted.
Click to expand...
Click to collapse
It's 100% safe and I can guarantee it'll boot as long as you're on an international OP6T on the Android 10 open beta 2. I reuploaded and included the stock boot.img as well so just in case you do have any problems, you can just fastboot flash it and you'll be able to boot right up (no hard brick or anything)

Bhamilton0347 said:
It's 100% safe and I can guarantee it'll boot as long as you're on an international OP6T on the Android 10 open beta 2. I reuploaded and included the stock boot.img as well so just in case you do have any problems, you can just fastboot flash it and you'll be able to boot right up (no hard brick or anything)
Click to expand...
Click to collapse
Great. Thank you. I might wait for the next stable build though. It just came out on H2OS, so shouldn't be too long now.

Man it just worked smooth for me. I was already on OB2 and I followed this below link. Half way down, I realised it was for OP6 and not 6T. However I had proper twrp and I just followed the procedure.
https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213
EDIT: I faced problems with wifi connectivity. So I had rebooted to TWRP and reflashed OB2, TWRP and Magisk again to get it working. An issue with
"fastboot flash boot" command I guess.

flyoffacliff said:
I think I see what I did! I need to use "fastboot flash boot_a" (or b), and not just "fastboot flash boot". Not sure how you know whether to use a or b without a custom recovery though? Because AFAIK, the fastboot command for that is broken.
Not sure what payload dumper is, but I should be able to use the the same patched boot image that everyone else used since it's for that same ROM, now that I known exactly where to flash it to (besides A or B).
When I flashed to "boot" before, I must have overwritten some kind of low-level pre-bootloader, lol.
Thank you
I wasn't sure either but I know that the boot on the oneplus 6t android 10 it has two partitions. I just flashed it on boot_a and it works. I could attempt to install twrp on the other partition but I don't really needed it. good luck and let us know how it went.
Click to expand...
Click to collapse

I had a bit more luck with the adventure this time! Successfully flashed TWRP and Magisk, but then Emojis were completely broken at the OS level. Apparently this is caused by a partition issue, but not sure how this happened. I tried a script to fix it that someone posted and it did not work. So I took this as an opportunity to flash the latest ROM to fix it.
I went into TWRP, ran the full update ZIP, then the TWRP installer, then the Magisk installer (all without rebooting). Apparently it does not switch slots automatically when you run it from recovery instead of the "local update" option? TWRP was fine after the update, but Masisk was not, despite me flashing the ZIP. No idea why! But I switched back to the other slot that was still rooted, used Magisk Manager to flash it to inactive slot, and switched slot back to one with new OS. Success! Funny how different methods work/fail with different people. Thanks for the help everyone. I just noticed 10.3.1 is no longer posted on the OnePlus website download page, hope it didn't get pulled again!
EDIT: Does each slot just have its own system and cache partition? Everything else is like data and modem is combined, right?

https://forum.xda-developers.com/oneplus-6t/how-to/root-oneplus-6t-loosing-data-android-10-t4041865
follow this guide.. work 100%. Tested.

[HELP] Cannot update TWRP

I have an LG V20 H910 dirty unlocked, rooted, and currently using LOS 16
I bought this phone 8 months ago for the sake of me tweaking with it, but unfortunately it didn't go well
The first thing i noticed was the screen ghosting, then the phone is very slow on stock ROM (H910PR 10f i think), so i rooted the phone and installed TWRP
I did installed the Stock Oreo ROM but i still decided to clean flash LOS 15.1 then dirty flashed LOS 16, and here i am still my current ROM is LOS 16.
I need to install the latest TWRP for me to theoretically install Gamma kernel (cuz mine just goes stuck to fastboot after, i dunno why)
So i thought maybe my TWRP is outdated, so i want to update it, but i can't, it is stuck on fastboot after, just like the kernel
I'm currently on @Phoenix591 TWRP 3.2.3-1 and this is literally as far as i can go, because anything later than that (like the lastest 3.3.1-1 or even just 3.2.3-4) bricks my phone to fastboot.
Can anyone help me with this, please?

Download the newest version from the TWRP thread, and then in your TWRP, hit "install" and then select to install by .img and not .zip and you should be able to flash that way. Otherwise do it through fastboot which I can help you with if you need to. Let me know.

iTzFeRReTTi said:
Download the newest version from the TWRP thread, and then in your TWRP, hit "install" and then select to install by .img and not .zip and you should be able to flash that way. Otherwise do it through fastboot which I can help you with if you need to. Let me know.
Click to expand...
Click to collapse
Already tried, still nothing, installing through TWRP or adb bricks the phone

MEMO#22 said:
Already tried, still nothing, installing through TWRP or adb bricks the phone
Click to expand...
Click to collapse
just for kicks (it won't hurt anything, but chances arn't great it'll help... but its something), does the us996 variant of twrp do the same thing?
There's basically no difference besides what the device calls itself (and some minor kernel options) for the purposes of checking what roms should be allowed to flash.
Also just to cover our bases, have you double checked the md5sum of the downloaded ATT twrp image and ensured it matched what android file host shows for it? (if the download was corrupted in such a way as to prevent it from booting properly it might end up going into fastboot from THAT)

Phoenix591 said:
just for kicks (it won't hurt anything, but chances arn't great it'll help... but its something), does the us996 variant of twrp do the same thing?
There's basically no difference besides what the device calls itself (and some minor kernel options) for the purposes of checking what roms should be allowed to flash.
Also just to cover our bases, have you double checked the md5sum of the downloaded ATT twrp image and ensured it matched what android file host shows for it? (if the download was corrupted in such a way as to prevent it from booting properly it might end up going into fastboot from THAT)
Click to expand...
Click to collapse
Yeah i did, still no luck
I downloaded both my current version and the latest one twice, md5 also matches but still nothing