Database Users

The strangest issues...

Hey all!
Those of you monitoring the unofficial LineageOS thread may have seen me talking about this already. I've been having issues with Magisk. I'm running their beta versions for 13.0.
So here's the story...
I have wanted to pass SafetyNet since May, when I got this phone and rooted it. I obviously went to Magisk, and when I realized that 11.6 was not passing SafetyNet, I decided to try the 13 betas. These didn't pass either, but since they were more recent than 11.6, I stuck with them. But when I heard of the Universal SafetyNet Fix Module, I immediately tried it.
Bottom line, these are my issues:
1. Magisk will not install the module. I go to Magisk Manager -> Modules -> + and select the ZIP for the module. Magisk gives me a toast saying "Installation error!" (See screenshot).
2. Okay, so now I want to start fresh and see if it works then. I boot into TWRP, flash the lastest Magisk uninstaller (08 June), and boot. Nope! Stuck on the "device unlocked" screen with ID: bad key.
3. Uhh.. maybe the stock boot image will work? I go to TWRP and flash the stock boot.img taken from the stock firmware. Still ID: bad key and I'm stuck again.
And I can boot successfully if I flash a Magisk 13.0 beta.
So, does anybody have any solutions? I think I may just have to reflash stock firmware.. not my top choice. Thank you for any help and reading through my long post :good: :highfive:

Try to install magisk v12, it always worked for me on every rom with safetynet fix ( try also the previous uninstaller )

eskamhl said:
Try to install magisk v12, it always worked for me on every rom with safetynet fix ( try also the previous uninstaller )
Click to expand...
Click to collapse
Will give it a shot and update when I see results.
Edit: Nope. I've a feeling that I'll have to start from scratch by flashing stock firmware.

Try flashing the safetynet fix in trwp.

triggerlord said:
Try flashing the safetynet fix in trwp.
Click to expand...
Click to collapse
Tried already. Still no.

Well, as far as I can see you messed up your installation. Start from scratch:
1. Go to TWRP and wipe system, data, cache and dalvik cache.
2. Install LineageOS, GAPPS, Magisk 12 and the stable version of the safetynet fix
3. Reboot and setup your nice and clean system again.
Bottom-line: don't keep messing with an already messed up system. Start clean again. And really: don't install stock boot.img on LineageOS: that's asking for trouble! To be honest: I'm astonished it even booted!!

smitharro said:
Well, as far as I can see you messed up your installation. Start from scratch:
1. Go to TWRP and wipe system, data, cache and dalvik cache.
2. Install LineageOS, GAPPS, Magisk 12 and the stable version of the safetynet fix
3. Reboot and setup your nice and clean system again.
Bottom-line: don't keep messing with an already messed up system. Start clean again. And really: don't install stock boot.img on LineageOS: that's asking for trouble! To be honest: I'm astonished it even booted!!
Click to expand...
Click to collapse
Lol, was doing this all on the stock ROM. See my original response to triggerlord's post.
Edit: issues fixed with a clean install of the pure Nexus ROM. I'm assuming this would be the case with a clean install of the stock ROM, but I am definitely not switching anytime soon (this ROM is amazing!)

Stuck in Boot Animation

Hi!
I have a A2107G and unlocked it, coming from B04.
Everything worked so far, but I have messed around with bootstack/modem and now I am struggling.
I flashed a new ROM with TWRP (different versions) and the ROM (doesn't matter which one) is stuck in booting animation.
What can I do to bring it back to life?
Also another question: After switching on, directly after the ZTE logo coming up, a black sceen with some infos coming up and stay there for 5 secs.
Is there a way to get rid of this

Sui77 said:
Hi!
I have a A2107G and unlocked it, coming from B04.
Everything worked so far, but I have messed around with bootstack/modem and now I am struggling.
I flashed a new ROM with TWRP (different versions) and the ROM (doesn't matter which one) is stuck in booting animation.
What can I do to bring it back to life?
Also another question: After switching on, directly after the ZTE logo coming up, a black sceen with some infos coming up and stay there for 5 secs.
Is there a way to get rid of this
Click to expand...
Click to collapse
Do you have twrp? If yes, flash stock rom.

WesTD said:
Do you have twrp? If yes, flash stock rom.
Click to expand...
Click to collapse
Yes, I have TWRP.
So i should flash a stock image and start over from scratch (with rooting, ...)
Is the posted screen normal?

Sui77 said:
Yes, I have TWRP.
So i should flash a stock image and start over from scratch (with rooting, ...)
Is the posted screen normal?
Click to expand...
Click to collapse
Yes it is normal. It means you've unlocked bootloader.
Flash stock rom zip. There are some guides.

WesTD said:
Yes it is normal. It means you've unlocked bootloader.
Flash stock rom zip. There are some guides.
Click to expand...
Click to collapse
THX.
Will do so.
Which ROM do you prefer? CarbonRom? LOS?
How do i get the system partition r/w?
I think I screwed up the phone when i tried to make it writable?

Sui77 said:
THX.
Will do so.
Which ROM do you prefer? CarbonRom? LOS?
How do i get the system partition r/w?
I think I screwed up the phone when i tried to make it writable?
Click to expand...
Click to collapse
I use aosp bases.

Sui77 said:
THX.
Will do so.
Which ROM do you prefer? CarbonRom? LOS?
How do i get the system partition r/w?
I think I screwed up the phone when i tried to make it writable?
Click to expand...
Click to collapse
Heh. I don't know if there are flashable stock zips for the A2017G, the way I know of is flashing the stock recovery and using an official zip. But you shouldn't go back to stock if you want to use custom ROMs. Try this:
-Get an SD card, put
~ a custom ROM (RR, LOS,NucleaROM (i prefer NucleaROM, just sayin)),
~a Magisk 13.3 zip or SuperSU 2.82 zip,
~an OpenGApps zip (I use pico), arm64,
~a TWRP 3.1.1-0.img and
~A2017X Universal Bootloader and A2017G modem.
-Wipe system, data, cache and dalvik
-Install the Universal Bootloader, then the Modem, then the ROM and last the GApps and magisk/SuperSU
-If you had something important on the internal storage put it on the SD with the File manager under Advanced
-Go to Wipe -> Format data -> type Yes. This will get rid of the possible encryption from the stock ROM, but it will wipe your internal storage too.
-Reboot to system
You can use the 5 seconds screen to get to TWRP with the Volume buttons. Pretty handy I guess. There's a zip out there that gets rid of that screen, but you risk black-screening your phone with what seems to be no immediate fix (you'd be looking at an RMA)
So, after you use the phone and open TWRP again, you'll have an old version of it (3.0.1N-0 or sth). So go to Install, choose Install image, and select the TWRP 3.1.1-0.img on your SDcard. Then Reboot -> reboot to recovery and you can do whatever you want.

Choose an username... said:
Heh. I don't know if there are flashable stock zips for the A2017G, the way I know of is flashing the stock recovery and using an official zip. But you shouldn't go back to stock if you want to use custom ROMs. Try this:
-Get an SD card, put
~ a custom ROM (RR, LOS,NucleaROM (i prefer NucleaROM, just sayin)),
~a Magisk 13.3 zip or SuperSU 2.82 zip,
~an OpenGApps zip (I use pico), arm64,
~a TWRP 3.1.1-0.img and
~A2017X Universal Bootloader and A2017G modem.
-Wipe system, data, cache and dalvik
-Install the Universal Bootloader, then the Modem, then the ROM and last the GApps and magisk/SuperSU
-If you had something important on the internal storage put it on the SD with the File manager under Advanced
-Go to Wipe -> Format data -> type Yes. This will get rid of the possible encryption from the stock ROM, but it will wipe your internal storage too.
-Reboot to system
You can use the 5 seconds screen to get to TWRP with the Volume buttons. Pretty handy I guess. There's a zip out there that gets rid of that screen, but you risk black-screening your phone with what seems to be no immediate fix (you'd be looking at an RMA)
So, after you use the phone and open TWRP again, you'll have an old version of it (3.0.1N-0 or sth). So go to Install, choose Install image, and select the TWRP 3.1.1-0.img on your SDcard. Then Reboot -> reboot to recovery and you can do whatever you want.
Click to expand...
Click to collapse
Hi!
Thanks for your help and the time you spent on my problem.
I have tried all that stuff already, but maybe not in exact that order. Will try it this evening.
In case i will be able to bring it back to life, I have 2 questions, pls:
1: You mentioned the 5sec-screen and a zip to get rid of it.
Where could I find it (not seen yet) and how do i get into fastboot, when I skip this screen?
2: When I setted up my Axon with a Custom Rom and SU and everything was working as it should do, I was not able to write to /system (or deleting something in system/apps)
How do I get rid of this restriction? I think I have found an instruction once, but I failed and afterwards my device was stuck in animation.
orry for bothering, but the Axon really drive me nuts. Never had such a hassle with my Nexus

Sui77 said:
Hi!
Thanks for your help and the time you spent on my problem.
I have tried all that stuff already, but maybe not in exact that order. Will try it this evening.
In case i will be able to bring it back to life, I have 2 questions, pls:
1: You mentioned the 5sec-screen and a zip to get rid of it.
Where could I find it (not seen yet) and how do i get into fastboot, when I skip this screen?
2: When I setted up my Axon with a Custom Rom and SU and everything was working as it should do, I was not able to write to /system (or deleting something in system/apps)
How do I get rid of this restriction? I think I have found an instruction once, but I failed and afterwards my device was stuck in animation.
orry for bothering, but the Axon really drive me nuts. Never had such a hassle with my Nexus
Click to expand...
Click to collapse
Which file manager you are using?
I'm using Root Explorer and no problem. Be sure you allow to root permission

WesTD said:
Which file manager you are using?
I'm using Root Explorer and no problem. Be sure you allow to root permission
Click to expand...
Click to collapse
Also Root Explorer, root granted.

Sui77 said:
Also Root Explorer, root granted.
Click to expand...
Click to collapse
Can you just leave the 5 sec screen alone? You can kill your phone, and there doesn't seem to be anything you can do really.
If you're insistent, you can find it under Themes Apps and Mods, called "We remove the inscription that the bootloader is unlocked" made by NFound1.
And about the restriction to modify the system, connect your phone to a PC with ADB, fire up ADB and configure it (USB debugging, ADB over network if you have the option, permit the connection) and issue 'adb reboot disemmcwp' (disable emmc write protection, that is. Write it just like that or your phone will reboot and you will still have the protection active).
The phone has its difficulties and all but it's easy to work with once you get the hang of it. And, you know, your big cores don't just die all of a sudden, which is a good thing!

Choose an username... said:
Heh. I don't know if there are flashable stock zips for the A2017G, the way I know of is flashing the stock recovery and using an official zip. But you shouldn't go back to stock if you want to use custom ROMs. Try this:
-Get an SD card, put
~ a custom ROM (RR, LOS,NucleaROM (i prefer NucleaROM, just sayin)),
~a Magisk 13.3 zip or SuperSU 2.82 zip,
~an OpenGApps zip (I use pico), arm64,
~a TWRP 3.1.1-0.img and
~A2017X Universal Bootloader and A2017G modem.
-Wipe system, data, cache and dalvik
-Install the Universal Bootloader, then the Modem, then the ROM and last the GApps and magisk/SuperSU
-If you had something important on the internal storage put it on the SD with the File manager under Advanced
-Go to Wipe -> Format data -> type Yes. This will get rid of the possible encryption from the stock ROM, but it will wipe your internal storage too.
-Reboot to system
You can use the 5 seconds screen to get to TWRP with the Volume buttons. Pretty handy I guess. There's a zip out there that gets rid of that screen, but you risk black-screening your phone with what seems to be no immediate fix (you'd be looking at an RMA)
So, after you use the phone and open TWRP again, you'll have an old version of it (3.0.1N-0 or sth). So go to Install, choose Install image, and select the TWRP 3.1.1-0.img on your SDcard. Then Reboot -> reboot to recovery and you can do whatever you want.
Click to expand...
Click to collapse
Tried exactly the steps you descriped, but no luck ---- still stuck in animation
Will try it tomorrow with Magist.
How can I go back to total stock.
Tried anything I found on xda, but no luck.
When I flash the ZTE B05 zip, I don't even get the boot animation.

Sui77 said:
Tried exactly the steps you descriped, but no luck ---- still stuck in animation
Will try it tomorrow with Magist.
How can I go back to total stock.
Tried anything I found on xda, but no luck.
When I flash the ZTE B05 zip, I don't even get the boot animation.
Click to expand...
Click to collapse
How do you flash the B05 zip? Did you try to flash the official zip?? lol
Follow my guide on the Guides section ("back to stock safely" or sth), it works...

Choose an username... said:
How do you flash the B05 zip? Did you try to flash the official zip?? lol
Follow my guide on the Guides section ("back to stock safely" or sth), it works...
Click to expand...
Click to collapse
I tired to flash a B5 an B5 bootstack with TWRP 3.1.1 -> not able to boot
Then i flashed, according to your guide, the stock recovery and now the device seems to be really bricked.
After the ZTE logo a lying robot appears for half a second and after that, the device is dead.
Can't boot into TWRP, can't use adb, EDL, ...

Ok, managed to get back TWRP.
But I really don't know how so solve my issue of how to come back to stock :crying:
Flashed a B05 stock (zip) and B05 bootstack and Magist....stuck in boot animation (AXON picture collage).
Fu....

Update:
Managed to flash this files:
ZTE_A2017GV1.0.0B09_BootStack_by_tron1.zip
ZTE_A2017GV1.0.0B09_StockSystem_by_tron1.zip
TWRP 3.1.1.0
Phone is up and running with A2017GV1.0.0B09
How can I upgrade to the B05 bootstack and the B05 ROM

Sui77 said:
Update:
Managed to flash this files:
ZTE_A2017GV1.0.0B09_BootStack_by_tron1.zip
ZTE_A2017GV1.0.0B09_StockSystem_by_tron1.zip
TWRP 3.1.1.0
Phone is up and running with A2017GV1.0.0B09
How can I upgrade to the B05 bootstack and the B05 ROM
Click to expand...
Click to collapse
to go back to stock, download the full zip of any version you want, and download stock recvovery from b08, you have flashed it.
from twrp, format data, and try to boot, if you cannot, reflash b09 recovery from twrp, select image and the recovery you download, then go to stock recovery and update from sdcard. it allways work for me, if you stuck in boot animation again, reboot recovery and wipe data.
after you succesfully boot, reboot edl, and reflash twrp, the version you were using before witn axon7tool, thats all

Sui77 said:
Update:
Managed to flash this files:
ZTE_A2017GV1.0.0B09_BootStack_by_tron1.zip
ZTE_A2017GV1.0.0B09_StockSystem_by_tron1.zip
TWRP 3.1.1.0
Phone is up and running with A2017GV1.0.0B09
How can I upgrade to the B05 bootstack and the B05 ROM
Click to expand...
Click to collapse
Just follow my guide for that. If you flash the B04 recovery (the one i provided) you shouldn't have any trouble

Managed to flash the B05 and phone is up and running.
Made a backup by using TWRP 3.1.1.0 and flashed CarbonRom, which also worked nicely.
However, I'm not able to flash LOS by using the B05 bootstack.
I'm too dumb for this phone

Sui77 said:
Managed to flash the B05 and phone is up and running.
Made a backup by using TWRP 3.1.1.0 and flashed CarbonRom, which also worked nicely.
However, I'm not able to flash LOS by using the B05 bootstack.
I'm too dumb for this phone
Click to expand...
Click to collapse
What B05 bootstack? You have to use the universal bootstack and the A2017G modem file...
Both are on the LOS thread. It seems weird that carbonROM would even boot without the universal bootstack though

'The System has been Destroyed' when installing TWRP zip in hotboot TWRP

UPDATE - Did not manage to find a way to get TWRP installed permanently but did manage to install Lineage OS 16 (which was my end goal) via hotboot of their recovery IMG, so happy with that at least! Appreciate any help given!
Not sure what I am doing wrong. have never come across this before!
I just completely reset my phone to stock via MiFlash
I then boot into TWRP recovery from Fastboot
I then install the TWRP installer in TWRP
I then reboot to recovery but get 'The System has been Destroyed'
I can still boot into the stock ROM
I can still boot into Fastboot
I just can't seem to get TWRP to install, I can only access it in hotboot
Any help would be amazing!

It's a known issue with Stock Pie and permanent TWRP.
A solution is to install magisk before booting to system

Tepig said:
It's a known issue with Stock Pie and permanent TWRP.
A solution is to install magisk before booting to system
Click to expand...
Click to collapse
Oh well damn, I will give that a shot thank you!

Tepig said:
It's a known issue with Stock Pie and permanent TWRP.
A solution is to install magisk before booting to system
Click to expand...
Click to collapse
Unfortunately did not do the trick for me
I installed TWRP then magisk, then rebooted to system
I then rebooted back to recovery but still get 'The system has been destroyed' message

MoonCakeHug said:
Unfortunately did not do the trick for me
I installed TWRP then magisk, then rebooted to system
I then rebooted back to recovery but still get 'The system has been destroyed' message
Click to expand...
Click to collapse
Never install twrp on stock pie. You'll get the same message. Hotboot it only.

MoonCakeHug said:
Unfortunately did not do the trick for me
I installed TWRP then magisk, then rebooted to system
I then rebooted back to recovery but still get 'The system has been destroyed' message
Click to expand...
Click to collapse
From what I have tried it seems that it is a bug with stock pie, custom roms with pie and stock oreo don't have this problem.
Anyway, you can basically get the same functionality by hotbooting but it's less convenient.

I have TWRP installed and resurrection remix. Maybe their TWRP works for you, just check the instructions and give it a try.

I think you should install TWRP in both slot A and B for it to work.

MoonCakeHug said:
Unfortunately did not do the trick for me
I installed TWRP then magisk, then rebooted to system
I then rebooted back to recovery but still get 'The system has been destroyed' message
Click to expand...
Click to collapse
Weird, it used to work for me when I was on stock pie.
I'm on a custom rom right now so I cannot test if it still works.
Sorry

I also have the same problem but now I'm on a custom rom and the TWRP without magisk works, but I would like to try an sGSI, on a custom rom does the procedure work?

Try another twrp

I'm here also had the same problem on mi A2 lite
But Rom run smooth and stable for a long time that I even forgot I have no twrp. Instead I backed up with titanium bk just in case. So ,Hotbooted with adb.... less convinient but u get to where u wanna flash though

Always boot in recovery mode after an update

Hi,
I was updating my OP6T to the new version (Magisk + Xxx NoLimits), but after the reboot post-update the device started to reboot to recovery after it booted. So I've tried to delete Magisk but the problem was still present, so I've decided to download the latest Oxygen ROM from the OnePlus and flash it from TWRP, but after flashing, the device started to always boot to recovery (before the OnePlus boot animation).
At least i tried to restore a nandroid backup of 1 month ago (System, Boot and Data), but still the device after the restore still boot to recovery before the boot animation.
I've only tried the system reboot (I've not tried to force boot another slot).
Do you have a solution to try before formatting the internal storage?
Thanks
Edit: After unistalling magisk and reflashing it again, now the device boots again, but immediately after (when the lock screen appear) the device reboot automatically to recovery again

Try this:
- in twrp , dirty flash the rom you are using (Oxygen os)
- factory reset
- flash twrp (the latest the better)
- flash Magisk 19.1
Reboot to system.
If this not working, Format data will work.

null0seven said:
Try this:
- in twrp , dirty flash the rom you are using (Oxygen os)
- factory reset
- flash twrp (the latest the better)
- flash Magisk 19.1
Reboot to system.
If this not working, Format data will work.
Click to expand...
Click to collapse
Factory reset from TWRP?

yes

null0seven said:
yes
Click to expand...
Click to collapse
So, do you mean the classic Wipe data, cache and dalvik?

https://forum.xda-developers.com/oneplus-6t/how-to/official-oxygenos-9-0-4-ota-oneplus-6t-t3860953
TWRP Users
1. Boot into TWRP and Flash the Latest Magisk Uninstaller
2. Flash the latest Full Oxygen OS Zip
3. Flash the TWRP installer Zip
4. Reboot to RECOVERY to make sure TWRP stays and continue to root.
5. Flash the Latest Magisk to maintain root
6. Reboot System and Enjoy the latest firmware without any data loss
Click to expand...
Click to collapse
I am guessing you skipped the first step...
Try this:
Flash the OTA zip
Reboot (you will be unrooted and with stock recovery)
Boot to TWRP through ADB
Flash magisk unistaller
Reboot
Boot to TWRP through ADB
Flash OTA zip
Flash TWRP
Reboot to TWRP
Flash magisk

Galeanatur said:
https://forum.xda-developers.com/oneplus-6t/how-to/official-oxygenos-9-0-4-ota-oneplus-6t-t3860953
I am guessing you skipped the first step...
Try this:
Flash the OTA zip
Reboot (you will be unrooted and with stock recovery)
Boot to TWRP through ADB
Flash magisk unistaller
Reboot
Boot to TWRP through ADB
Flash OTA zip
Flash TWRP
Reboot to TWRP
Flash magisk
Click to expand...
Click to collapse
I don't have the OTA but the full rom, isn't simplier to update with the full ROM?
I think I'm going to try the null0seven's solution

null0seven said:
Try this:
- in twrp , dirty flash the rom you are using (Oxygen os)
- factory reset
- flash twrp (the latest the better)
- flash Magisk 19.1
Reboot to system.
If this not working, Format data will work.
Click to expand...
Click to collapse
Ok, I've done this and actually is even worse, the device started to boot in recovery again and TWRP doesn't recognize that the internal storage is crypted, so i can't even access the internal storage (it shows only strange folders), so, now I can't flash the nandroid backup anymore.

I also mean FULL rom .zip.
Format data in twrp or in Fastboot. Or use MSM tool .
https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
all of them will wipe ALL in youre phone, but it will work.

null0seven said:
I also mean FULL rom .zip.
Format data in twrp or in Fastboot. Or use MSM tool .
https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
all of them will wipe ALL in youre phone, but it will work.
Click to expand...
Click to collapse
So I've to Full wipe and then adb sideload the ROM? Because at the current state I can't even boot the device, it always starts in TWRP
Edit: I've also tried the blue_spark's version but nothing changed, TWRP can't recognize the encrypted storage

you can try this first.
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516

fuji97 said:
Hi,
I was updating my OP6T to the new version (Magisk + Xxx NoLimits), but after the reboot post-update the device started to reboot to recovery after it booted. So I've tried to delete Magisk but the problem was still present, so I've decided to download the latest Oxygen ROM from the OnePlus and flash it from TWRP, but after flashing, the device started to always boot to recovery (before the OnePlus boot animation).
At least i tried to restore a nandroid backup of 1 month ago (System, Boot and Data), but still the device after the restore still boot to recovery before the boot animation.
I've only tried the system reboot (I've not tried to force boot another slot).
Do you have a solution to try before formatting the internal storage?
Thanks
Edit: After unistalling magisk and reflashing it again, now the device boots again, but immediately after (when the lock screen appear) the device reboot automatically to recovery again
Click to expand...
Click to collapse
When you're saying you're flashing the full ROM after wiping, are you meaning the xxx no limit? If so this isn't an os rom it's just a magisk module rom that's an add on to oxygen os. You need to wipe and flash the latest oxygen os rom, stable or beta which ever you're using, then flash TWRP, flash your os again on the other slot, flash TWRP, flash magisk, if your system boots fine then flash the xxx no limits rom in twrp.

ebproject said:
When you're saying you're flashing the full ROM after wiping, are you meaning the xxx no limit? If so this isn't an os rom it's just a magisk module rom that's an add on to oxygen os. You need to wipe and flash the latest oxygen os rom, stable or beta which ever you're using, then flash TWRP, flash your os again on the other slot, flash TWRP, flash magisk, if your system boots fine then flash the xxx no limits rom in twrp.
Click to expand...
Click to collapse
No, I flashed the full ROM downloaded from the OnePlus server

Have you tried formatting data?

Cablespider said:
Format data.
Click to expand...
Click to collapse
So, full format data and flash rom + TWRP + Magisk?

fuji97 said:
No, I flashed the full ROM downloaded from the OnePlus server
Click to expand...
Click to collapse
You're best bet is to use the MSM tool
https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448

Ok, I've decided to use MSM to recover the device, I've lost the internal storage, but at least the device is working again.
Thank you to everyone who helped me in this thread

fuji97 said:
Ok, I've decided to use MSM to recover the device, I've lost the internal storage, but at least the device is working again.
Thank you to everyone who helped me in this thread
Click to expand...
Click to collapse
Maybe it was a Magisk module that caused it. I removed pixel module from Magisk and it done the same to me.

Flash custom ROM

From 6T (purchased from oneplus.com), any time I follow the instructions for how to flash one of the custom ROMs, I get stuck at the bootloader with no working rom.
I was able to use the MSMTool to restore to 9.0.13. I upgraded a few times flashing OnePlus6TOxygen_34_OTA_024_all_1909112343_9fd6e0057b8747dc, which works, but when I try to flash a custom ROM, I cannot get past the bootloader. I say a few times because I've tried this for a few days now with no success.
Most recently, I used the Flash-all.bat inside 10.3.0-OnePlus6TOxygen_34_OTA_042_all_1912142031_d9ef3-FASTBOOT
I am currently on 10.3.0, with twrp-3.3.1-31-fajita-Q-mauronofrio installed using the fastboot flash boot_a twrp-3.3.1-31-fajita-Q-mauronofrio.img then fastboot boottwrp-3.3.1-31-fajita-Q-mauronofrio.img commands from fastboot.
I can then install Magisk 19.4 or 20.3, however again when I try to flash a custom ROM, I cannot get past the bootloader.
What am I doing wrong?

When you 'fastboot boot' twrp, you can't flash twrp as .img file after that..... (There is no recovery partition on our phone, only a boot one)
If you flash a twrp img it will overwrite boot partition with only twrp and no kernel... Basic knowledge. Once temporarily booted in twrp by 'fastboot boot' command you must flash the installer, meaning the .zip file.
Then reboot your phone in twrp and flash whatever you want
Always latest versions of Magisk, why flashing a deprecated 19.4?

Striatum_bdr said:
When you 'fastboot boot' twrp, you can't flash twrp as .img file after that..... (There is no recovery partition on our phone, only a boot one)
If you flash a twrp img it will overwrite boot partition with only twrp and no kernel... Basic knowledge. Once temporarily booted in twrp by 'fastboot boot' command you must flash the installer, meaning the .zip file.
Then reboot your phone in twrp and flash whatever you want
Always latest versions of Magisk, why flashing a deprecated 19.4?
Click to expand...
Click to collapse
I was having an issue with the boot command in 10.3.0, which is how I found the flash command, and using both of those seemed to work (at least get me into twrp).
Now I am able to just run fastboot boot twrp-3.3.1-31-fajita-Q-mauronofrio.img and it works.
I was using 19.4 because somewhere in here someone mention twrp not working with magisk 20.3.
I've had no issues with 20.3 and twrp, so I will continue to use 20.3
The steps I use to flash a custom ROM (after twrp is installed)
1. remove the lock screen security from the existing ROM
2. boot straight into recovery from the existing ROM
3. wipe Data, Cache, and Dalvik by swiping right to factory reset from the wipe menu
4. flash the ROM from internal storage using the Install button
at this point I've tried a couple of approaches including a reboot here to see if the ROM flashed, and also installing twrp right after flashing ROM so that I will have a working twrp install.
Either way, I can never get past the bootloader.
Am I performing these steps correctly?

s7itch3s said:
I was having an issue with the boot command in 10.3.0, which is how I found the flash command, and using both of those seemed to work (at least get me into twrp).
Now I am able to just run fastboot boot twrp-3.3.1-31-fajita-Q-mauronofrio.img and it works.
I was using 19.4 because somewhere in here someone mention twrp not working with magisk 20.3.
I've had no issues with 20.3 and twrp, so I will continue to use 20.3
The steps I use to flash a custom ROM (after twrp is installed)
1. remove the lock screen security from the existing ROM
2. boot straight into recovery from the existing ROM
3. wipe Data, Cache, and Dalvik by swiping right to factory reset from the wipe menu
4. flash the ROM from internal storage using the Install button
at this point I've tried a couple of approaches including a reboot here to see if the ROM flashed, and also installing twrp right after flashing ROM so that I will have a working twrp install.
Either way, I can never get past the bootloader.
Am I performing these steps correctly?
Click to expand...
Click to collapse
I don't know I don't flash custom ROMs anymore, too old for that stuff and need my time for me.
There are specific instructions for each custom ROM it's better to ask in dedicated threads, some of them need to have OOS in both slots before, some of them need to be fleshed in both slots. Normally you eventually wipe things, flash the ROM and twrp to keep it, then reboot to twrp (necessary to boot on the slot where the ROM is actually fleshed, which is always the non active slot, which become the new active slot) and flash Gapps and Magisk ( because Gapps and Magisk can be flashed only in active slot) then reboot system

s7itch3s said:
Am I performing these steps correctly?
Click to expand...
Click to collapse
I've updated these instructions here, they are the same, just added to them really.
This is how I install Lineage 17. (If you are doing 16, replace 10.3.0 with 9.0.17, and the Q image of TWRP with the Pie image)
- Install 10.3.0 fastboot ROM again to start over, boot it once. Just to make sure everything is good.
- Reboot to fastboot.
- Boot the Q image of TWRP.
- Run the TWRP installer, reboot to recovery
- You backed everything up right?
- Factory reset (This is the slider at the bottom in the wipe menu).
- Format data. (This is the button that says Format data in the wipe menu)
- Do NOT wipe cache, do not Wipe system, do NOT Wipe Dalvik / ART, do not add anything else, Just Factory Reset and Format Data. After doing those two Reboot to Recovery one more time. You must do this after formatting data.
- Now transfer Lineage and TWRP to your phone, Windows / Linux should see TWRP fine as a media device when plugged in.
- Install Lineage
- Run the TWRP Installer.
- Reboot to Recovery.
- Install Lineage (You need Lineage on both slots, so yes run it again)
- Run the TWRP Installer (yes again).
- Reboot to Recovery.
- Install Gapps if you want them.
- Install Magisk 20.3 if you use Magisk. I used 20.3 it works fine. (20.4 also fine) Do not install modules or other add ons at this point. Boot once and go through the setup and everything, then install your add-ons.
- Be aware the phone will restart once, then Lineage will start up and all will be good.
From that point on updating should just be like normal :
- Reboot to recovery
- Flash Lineage.
- Flash TWRP Installer
- Reboot to Recovery
- Flash Gapps. (Assuming you use them, if you installed them once you must continue to install them or do a clean install)
- Flash Magisk. (If you use it)
- Reboot to system.
- No loss of data, or anything.
- No need to flash anything twice etc.
I've posted similar instructions here. It was just for LOS 16, same thing essentially though.

OhioYJ said:
I've updated these instructions here, they are the same, just added to them really.
This is how I install Lineage 17. (If you are doing 16, replace 10.3.0 with 9.0.17, and the Q image of TWRP with the Pie image)
- Install 10.3.0 fastboot ROM again to start over, boot it once. Just to make sure everything is good.
- Reboot to fastboot.
- Boot the Q image of TWRP.
- Run the TWRP installer, reboot to recovery
- You backed everything up right?
- Factory reset (This is the slider at the bottom in the wipe menu).
- Format data. (This is the button that says Format data in the wipe menu)
- Do NOT wipe cache, do not Wipe system, do NOT Wipe Dalvik / ART, do not add anything else, Just Factory Reset and Format Data. After doing those two Reboot to Recovery one more time. You must do this after formatting data.
- Now transfer Lineage and TWRP to your phone, Windows / Linux should see TWRP fine as a media device when plugged in.
- Install Lineage
- Run the TWRP Installer.
- Reboot to Recovery.
- Install Lineage (You need Lineage on both slots, so yes run it again)
- Run the TWRP Installer (yes again).
- Reboot to Recovery.
- Install Gapps if you want them.
- Install Magisk 20.3 if you use Magisk. I used 20.3 it works fine. (20.4 also fine) Do not install modules or other add ons at this point. Boot once and go through the setup and everything, then install your add-ons.
- Be aware the phone will restart once, then Lineage will start up and all will be good.
From that point on updating should just be like normal :
- Reboot to recovery
- Flash Lineage.
- Flash TWRP Installer
- Reboot to Recovery
- Flash Gapps. (Assuming you use them, if you installed them once you must continue to install them or do a clean install)
- Flash Magisk. (If you use it)
- Reboot to system.
- No loss of data, or anything.
- No need to flash anything twice etc.
I've posted similar instructions here. It was just for LOS 16, same thing essentially though.
Click to expand...
Click to collapse
Sir, apology for being an old noob, I am on OOS 10.3.2 TWRP 3.3.1-32 can I follow the above guide? If Yes,
Why aren't we using the "Lineage Recovery" provided in "Lineage OS Downloads" page?? If we use it, will the above instructions change ? What are the cons of using it?
Sorry again for asking!! Can you please share me the Link to Open Gapps which Will be suitable in my scenario ?

Advised Sloth said:
Sir, apology for being an old noob, I am on OOS 10.3.2 TWRP 3.3.1-32 can I follow the above guide? If Yes,
Why aren't we using the "Lineage Recovery" provided in "Lineage OS Downloads" page?? If we use it, will the above instructions change ? What are the cons of using it?
Sorry again for asking!! Can you please share me the Link to Open Gapps which Will be suitable in my scenario ?
Click to expand...
Click to collapse
Historically Lineage / CM recovery was hit or miss, or TWRP or other recoverys worked better. To be fair I haven't even tried the Lineage recovery. So maybe that is no longer true? Right now, I know TWRP works. The updated instructions link up there has links in it, FYI, link OpenGapps. OpenGapps can be found here. You will be using Arm64, Android 10 obviously.
Since you are already on 10.3.2 (I assume you were on 10.3.1 before) you should be good to skip the step about fastboot ROM or install OOS, and you already have TWRP., so you should be able to go right on to backing everything up, wiping everything, and installing Lineage. (So you can skip the first few steps)
Anymore questions feel free to ask.

OhioYJ said:
Historically Lineage / CM recovery was hit or miss, or TWRP or other recoverys worked better. To be fair I haven't even tried the Lineage recovery. So maybe that is no longer true? Right now, I know TWRP works. The updated instructions link up there has links in it, FYI, link OpenGapps. OpenGapps can be found here. You will be using Arm64, Android 10 obviously.
Since you are already on 10.3.2 (I assume you were on 10.3.1 before) you should be good to skip the step about fastboot ROM or install OOS, and you already have TWRP., so you should be able to go right on to backing everything up, wiping everything, and installing Lineage. (So you can skip the first few steps)
Anymore questions feel free to ask.
Click to expand...
Click to collapse
First of all, thank you very much for your time and explanation.
Sir, so i will proceed as follows:
* Boot into TWRP Recovery
* Perform "swipe to factory reset" & "swipe to wipe data"
* Reboot to TWRP recovery again
* Flash LOS 17.1 on slot A
* Reboot to TWRP recovery again
* Flash LOS 17.1 on slot B
* Reboot to system
Sir, please check are my steps correct? If not,
From which step( steps mentioned in your guide) should i start?
Last query is, which GApps zip will be best for me, micro/nano/pico/tv stock, If i want max coverage of google?
Very sorry for knocking you repeatedly!!!

Advised Sloth said:
First of all, thank you very much for your time and explanation.
Last query is, which GApps zip will be best for me, micro/nano/pico/tv stock, If i want max coverage of google?
Click to expand...
Click to collapse
Your starting point is correct. However make sure you don't miss the re-install TWRP after flashing Lineage each time, and the second time you need to flash Gapps before you reboot to system.
Personally I always do Nano. Anything else you need (that would be included in Micro) can be installed from the Play store. Nano at least includes all the things that can't be installed from the play store.
Pico has the least in it. TV is for TV devices. On OpenGapps there is a box next to each package you can click and it will tell you exactly what is in each package.

OhioYJ said:
I've updated these instructions here, they are the same, just added to them really.
This is how I install Lineage 17. (If you are doing 16, replace 10.3.0 with 9.0.17, and the Q image of TWRP with the Pie image)
- Install 10.3.0 fastboot ROM again to start over, boot it once. Just to make sure everything is good.
- Reboot to fastboot.
- Boot the Q image of TWRP.
- Run the TWRP installer, reboot to recovery
- You backed everything up right?
- Factory reset (This is the slider at the bottom in the wipe menu).
- Format data. (This is the button that says Format data in the wipe menu)
- Do NOT wipe cache, do not Wipe system, do NOT Wipe Dalvik / ART, do not add anything else, Just Factory Reset and Format Data. After doing those two Reboot to Recovery one more time. You must do this after formatting data.
- Now transfer Lineage and TWRP to your phone, Windows / Linux should see TWRP fine as a media device when plugged in.
- Install Lineage
- Run the TWRP Installer.
- Reboot to Recovery.
- Install Lineage (You need Lineage on both slots, so yes run it again)
- Run the TWRP Installer (yes again).
- Reboot to Recovery.
- Install Gapps if you want them.
- Install Magisk 20.3 if you use Magisk. I used 20.3 it works fine. (20.4 also fine) Do not install modules or other add ons at this point. Boot once and go through the setup and everything, then install your add-ons.
- Be aware the phone will restart once, then Lineage will start up and all will be good.
From that point on updating should just be like normal :
- Reboot to recovery
- Flash Lineage.
- Flash TWRP Installer
- Reboot to Recovery
- Flash Gapps. (Assuming you use them, if you installed them once you must continue to install them or do a clean install)
- Flash Magisk. (If you use it)
- Reboot to system.
- No loss of data, or anything.
- No need to flash anything twice etc.
I've posted similar instructions here. It was just for LOS 16, same thing essentially though.
Click to expand...
Click to collapse
Sorry for the necropost, but this also works for TWRP 3.6 and Lineage 18.1. I initially had a problem with the default TWRP for my 6t. During the initial TWRP fastboot the version on their site caused a firmware error which I could just barely get out of, but it screwed up the system boot process in some subtle way that even the fixed version of TWRP (found on this site) couldn't solve.
After trying your instructions above, it didn't work the first time because of the screwed up system boot. It just kept trying to boot to recovery. I suspected a firmware error and was almost going to do an mcmdownload soft-brick rescue. I tried one last thing, using the TWRP on the system to sideload the stock ROM. That worked and patched up the system boot process. Once I booted and ran through some basic initialization to make sure developer options were properly set I followed the above instructions and it worked nearly flawlessly.
One strange thing. After I installed Lineage 18.1 and TWRP to both partitions (as well as Gapps / magisk), it rebooted to system and almost booted without incident -- except a large circular logo popped up that said 100% and stopped. I figured that that meant someting completed properly, so I powered off, waited 10 seconds, powered on and then the Lineage green system initialization spinner came up for a few minutes and it went through the user initialization sequence.
Thanks. I almost gave up and bought a new phone.

OhioYJ said:
I've updated these instructions here, they are the same, just added to them really.
This is how I install Lineage 17. (If you are doing 16, replace 10.3.0 with 9.0.17, and the Q image of TWRP with the Pie image)
- Install 10.3.0 fastboot ROM again to start over, boot it once. Just to make sure everything is good.
- Reboot to fastboot.
- Boot the Q image of TWRP.
- Run the TWRP installer, reboot to recovery
- You backed everything up right?
- Factory reset (This is the slider at the bottom in the wipe menu).
- Format data. (This is the button that says Format data in the wipe menu)
- Do NOT wipe cache, do not Wipe system, do NOT Wipe Dalvik / ART, do not add anything else, Just Factory Reset and Format Data. After doing those two Reboot to Recovery one more time. You must do this after formatting data.
- Now transfer Lineage and TWRP to your phone, Windows / Linux should see TWRP fine as a media device when plugged in.
- Install Lineage
- Run the TWRP Installer.
- Reboot to Recovery.
- Install Lineage (You need Lineage on both slots, so yes run it again)
- Run the TWRP Installer (yes again).
- Reboot to Recovery.
- Install Gapps if you want them.
- Install Magisk 20.3 if you use Magisk. I used 20.3 it works fine. (20.4 also fine) Do not install modules or other add ons at this point. Boot once and go through the setup and everything, then install your add-ons.
- Be aware the phone will restart once, then Lineage will start up and all will be good.
From that point on updating should just be like normal :
- Reboot to recovery
- Flash Lineage.
- Flash TWRP Installer
- Reboot to Recovery
- Flash Gapps. (Assuming you use them, if you installed them once you must continue to install them or do a clean install)
- Flash Magisk. (If you use it)
- Reboot to system.
- No loss of data, or anything.
- No need to flash anything twice etc.
I've posted similar instructions here. It was just for LOS 16, same thing essentially though.
Click to expand...
Click to collapse
OhioYJ, these are great instructions but it initially left me with questions about how that procedures would create duplicate installs on slot A and B. The answer is of course that the Lineage installer for the 6t knows about the dual slot setup and always writes to the inactive slot. Booting into recovery activates the inactive slot so that installing again after that installs to the other slot and now you have Lineage on both slots. The installer for TWRP always installs to both slots and is needed because Lineage always installs its recovery handler and you don't want that so you overwrite.
PS: TWRP has an option for installing itself after installing the requested package. Would that be just as good as installing the TWRP zip?
PPS: I had to do an 'adb push' of the Lineage and TWRP zips to sdcard for the installs. Unfortunately installing and slot switching makes the sdcard unavailable so you have to push the zips again. Is there somewhere I can write them to that I don't lose access to after a boot to recovery?