Database Info

What's New(?) procedure to install Custom ROMs coming from OOS 9.0.5?

Hello guys,
I'm having trouble trying to install a Custom ROM (Tresk Mod, but I get it with others too)
So basically some days ago my whole Internal Storage got encrypted so I had to a full wipe.
From there I decided to use Msmtools just in case, so I got back to OOS 5.1.5 from there I updated to OOS 9.0.5 via OTA and unlock the bootloader and install TWRP everything works fine.
But when I tried to install any custom ROM I either cannot boot and just boots to Bootloader (Not even the recovery works) and I get "Failed to load/authenticate boot image: Load Error" which I can fix fastboot flashing all the partitions...
Or I straight get a black screen with the White Notifications LED whenever I try to boot either to system or recovery and from there I can only recover using Msmtools...
So I'm now asking, what are the steps for flashing Custom ROMs now?? Because seems like I'm doing something wrong since I'm ending having a Bricked device...

try to flash rom with bluespark recovery

Nothing changed that I'm aware of, but I found that I'll have the same experience if I try to root before booting the system at least once rootless first. Also, I have issues like that whenever I keep TWRP (even Blu Spark) installed. Now I only use it via sideload every time. I never have issues anymore.

Mdknight said:
Nothing changed that I'm aware of, but I found that I'll have the same experience if I try to root before booting the system at least once rootless first. Also, I have issues like that whenever I keep TWRP (even Blu Spark) installed. Now I only use it via sideload every time. I never have issues anymore.
Click to expand...
Click to collapse
I did the following:
1. Upgraded from 5.1.5 to 9.0.5 (Since I was coming from Msmtools fix)
2. Unlock bootloader
3. Reboot to system and then boot again to bootloader for doing (fastboot boot TWRP.xxx.img)
4. Once in the recovery flash recovery and Magisk (just because) and back to system (where everything was working perfectly)
5. Rebooted to recovery and did the following:
Factory Reset (The one that you slide which should wipe Cache, Dalvik and Data)
Flashed the ROM (HavocOS 2.5) and right after that TWRP
And at this point I tried to reboot back to recovery but black screen and cannot boot to recovery nor system not even via fastboot
Is your order different? Am I missing something?

Asiier said:
I did the following:
1. Upgraded from 5.1.5 to 9.0.5 (Since I was coming from Msmtools fix)
2. Unlock bootloader
3. Reboot to system and then boot again to bootloader for doing (fastboot boot TWRP.xxx.img)
4. Once in the recovery flash recovery and Magisk (just because) and back to system (where everything was working perfectly)
5. Rebooted to recovery and did the following:
Factory Reset (The one that you slide which should wipe Cache, Dalvik and Data)
Flashed the ROM (HavocOS 2.5) and right after that TWRP
And at this point I tried to reboot back to recovery but black screen and cannot boot to recovery nor system not even via fastboot
Is your order different? Am I missing something?
Click to expand...
Click to collapse
You have to install twrp.zip again after havoc, boot Back Into Recovery and then gapps and magisk

Asiier said:
I did the following:
1. Upgraded from 5.1.5 to 9.0.5 (Since I was coming from Msmtools fix)
2. Unlock bootloader
3. Reboot to system and then boot again to bootloader for doing (fastboot boot TWRP.xxx.img)
4. Once in the recovery flash recovery and Magisk (just because) and back to system (where everything was working perfectly)
5. Rebooted to recovery and did the following:
Factory Reset (The one that you slide which should wipe Cache, Dalvik and Data)
Flashed the ROM (HavocOS 2.5) and right after that TWRP
And at this point I tried to reboot back to recovery but black screen and cannot boot to recovery nor system not even via fastboot
Is your order different? Am I missing something?
Click to expand...
Click to collapse
Sconny said:
You have to install twrp.zip again after havoc, boot Back Into Recovery and then gapps and magisk
Click to expand...
Click to collapse
Agreed. Always reboot from recovery to recovery after flashing a new one (TWRP). THEN, go ahead and flash gapps and magisk.

Sconny said:
You have to install twrp.zip again after havoc, boot Back Into Recovery and then gapps and magisk
Click to expand...
Click to collapse
Mdknight said:
Agreed. Always reboot from recovery to recovery after flashing a new one (TWRP). THEN, go ahead and flash gapps and magisk.
Click to expand...
Click to collapse
I finally figured it out
The problem was that as I was updating via OTA OOS 9.0.5 was only installed in one Slot so I need to install it in the other as well.
Did the following process:
1. Boot to Bootloader and do "fastboot boot TWRP.img"
2. From there flash TWRP.zip and Reboot back to it (Recovery)
3. Flash OOS Latest (9.0.5)
4. Flash TWRP
5. Reboot to TWRP
6. Flash OOS Latest (9.0.5)
7. Flash TWRP
8. Reboot to TWRP
9. Wipe data, dalvik cache
10. Flash ROM
11. Flash TWRP
12. Reboot to TWRP
13. Flash gapps + Misc (Magisk, etc)
14. Boot system
Technically just one 1 installation should do as the other slot was already populated but the twice just to be safe.

Lenovo p2 blue led after magisk update

I am creating this post to help p2 community who is stuck on blue led after magisk update on custom rom
I have encountered this issue twice on my phone after a magisk update.
This happens when you patch the update directly from magisk manager.
The first time I was stuck with this issue on custom pie rom, I searched on other threads and got to know that device needs to reset to stock rom by flashing fast boot stock files on download mode, just search it, you will get link with details
However, this was a very complex task , also I lost my data in the process after flashing the data partition. From there , I went on to flash custom rom ,then installed apps , the process took the whole day
The second time when I again stuck with blue led , I was on another pie rom, This time I recovered my device without having to go over flashing all things again.
Please find the detailed step below , as I think it may help someone in such critical issues
1) Go to download mode, flash treble supported twrp for treble supported pie roms, by using command - fastboot flash recovery name.img
2) Temporary boot into same twrp , command is -
fastboot boot name.img
3) Once in twrp, go to reboot, reboot to recovery
4) Once in recovery , copy following files into internal storage - magisk.zip, magiskunistaller.zip, twrprecovery.img ( one used in step 1 ), boot.img ( extract it from existing rom package.zip)
5) Flash magisk uninstaller first
6) Go to install, install image
flash boot.img by selecting boot partition
if it get stuck , again go in twrp using step 3 and try again, it will work
flash twrprecovery.img by selecting recovery partition
7) Flash magisk zip now
8) If all goes well , you phone will boot into existing rom
Please like the post if you had same issue and are able to recover it from mentioned steps

I got into this trouble too, when direct installing magisk from v19.2 to v19.3. The magisk manager shows that it's finished installing v19.3 and reboot. Then the phone shows the white Lenovo screen, then turns dark, and vibrate for a few seconds with blue led lighting up, and finally just freeze. No bootloop, just a dark screen with blue notification led.
What I did was going to twrp (the one recommended in LOS 16.0 thread) by pressing vol up + down + power button until the white Lenovo screen come up, then release. I just reflash my current ROM (RR-P-v7.0.2-20190604-kuntao-Official.zip) using adb sideload. It finished flashing, click reboot, and finally managed to boot into system. No data loss, magisk v19.3 worked, and no magisk uninstaller required.
During the flashing process, I noticed that Magisk v19.3 was being auto flashed, so the magisk manager direct install probably somehow mess up with the boot.img after installing v19.3.

I was not able to go in twrp by any means , so I mentioned steps via download mode
Regarding your way to sideload and dirty flash whole rom , it didnt worked with me previously, so I cannot say about that, it was going back to blue led after reflashing
Regarding magisk installing and removing steps, anyone can ignore this steps and try if it works for them.

Just uninstall the magisk and reinstall it.
I have also faced same error previously and reinstalled magisk and it worked.

Someone please make a video of this and post it here
Rakxx said:
1) Go to download mode, flash treble supported twrp for treble supported pie roms, by using command - fastboot flash recovery name.img
2) Temporary boot into same twrp , command is -
fastboot boot name.img
3) Once in twrp, go to reboot, reboot to recovery
4) Once in recovery , copy following files into internal storage - magisk.zip, magiskunistaller.zip, twrprecovery.img ( one used in step 1 ), boot.img ( extract it from existing rom package.zip)
5) Flash magisk uninstaller first
6) Go to install, install image
flash boot.img by selecting boot partition
if it get stuck , again go in twrp using step 3 and try again, it will work
flash twrprecovery.img by selecting recovery partition
7) Flash magisk zip now
8) If all goes well , you phone will boot into existing rom
I have this issue but I don't know how to do these steps please make a YouTube video and post a link here (I'm new to this)
Click to expand...
Click to collapse

Can't install LineageOS

Hi
I have problems to install LineageOS on my new OnePlus6. I tried to install LineageOS with the guide on https://wiki.lineageos.org/devices/enchilada/install. If I follow the guide exactly step by step no OS is starting and I can't boot into recovery because (I think) twrp isn't installed (just black screen with blue led). But also if I first boot twrp with fastboot boot 'twrp.img' and after install the twrp.zip, no OS is starting after sideload or flash the 'lineageos.zip'. I think, the install doesn't finish correct. In the terminal on my debian I can see, that the installprocess ends at 47%. But I'm not really shure if this is the problem and if it is, how I can solve it. Probably in this thread the same problem is described: https://forum.xda-developers.com/oneplus-6/help/lineage-doesnt-boot-black-screen-light-t3958351 Unfortunately no solution is available in the thread.
Now I flashed the stockrom (https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665) and have done all updates but don't know how I can install twrp and after LineageOS. I hope somebody can help me. Thanks

Do you have the latest ADB version? Instead of sideloading you can try just transferring the zip files (with e.g. "adb push lineageos.zip /sdcard/") and then installing directly from TWRP.
Make sure you do all the wipes / formats mentioned in the guide. Transfer and flash the lineageos.zip. Then directly after you should flash the twrp.zip Then reboot back into recovery and flash Magisk / Gapps etc if needed. Then finally reboot to system.
Also read this guide if you haven't already as it explains a lot about how flashing ROMs on OnePlus 6 is different to many other older phones.

Hi and thank you makeyourself
I tried the following steps:
1. starting fastboot
2. fastboot boot twrp-3.3.1-2-enchilada.img -> twrp starting up
3. adb push twrp-installer-3.3.1-2-enchilada.zip /sdcard/ -> transfer ok
4. adb push lineage-16.0-20190922-nightly-enchilada-signed.zip /sdcard/ -> transfer ok
5. in twrp Wipe -> Format Data
6. in twrp Advanced Wipe -> System
7. in twrp install lineage-16.0-20190922-nightly-enchilada-signed.zip
8. in twrp install twrp-installer-3.3.1-2-enchilada.zip
9. reboot to recovery
After this steps I got the same problem as before. Before the reboot to recovery, twrp showed the message "no OS installed". So I think, the zip weren't installed correctly. Now, I have the black screen with the blue led. Can you find out what I did wrong?
Edit: Now, I can't also boot twrp. Also if I do a fastboot boot twrp-3.3.1-2-enchilada.img nothing happens.

Fastboot to twrp (newest blu spark should be fine, or black twrp)
Flash twrp zip
Reboot to twrp
Wipe data, cache.
Flash recommended oos
Flash twrp
Reboot to twrp
Flash recommended twrp (yes...... Again)
Flash twrp (yes... Again, recovery is lost after rom Flash ALWAYS)
Reboot to twrp
Flash LOS or any other custom rom
Flash twrp (rom Flash, so twrp is lost like I said)
Reboot to twrp
Flash magisk (IF ypu want magisk)
Flash gapps (IF ypu want gapps)
Flash kernel (IF I like to run another custom kernel)
Boot
Enjoy

Thank you whizeguy, I'll try this. But just one question about "Flash recommended oos". Which OxygenOS can I flash (this full OTA? https://www.xda-developers.com/oneplus-6-oneplus-6t-oxygenos-9014-906/) and why I have to do this? Sorry if it is a bad question.

You Flash The oxygen OS version that is recommended in Los thread, simple as that.
You have an a/b device, vendor partition (could be other files needed aswell, not 100 % sure) is needed to Flash custom, IF you did Amy research you'd finns some good info. Also for faster answers in The future: post your issue in the thread for LOS, that way you would get help from People Who uses it, knows The exact version you should use and what not

Hey whizeguy, thank you very much. Everything works perfect now. But why for heaven's sake do I have to flash oos and why the guide on the LineageOS site don't tell me this way?

Wow idk what happened here. Mistakenly replied to this thread. Apologies.

Installing Recovery Ramdisk issues

To be brief, here's a summary of my issue: I had previously installed twrp, magisk, and a bunch of other garbage and decided to move to LineageOS. I tried to install it, opengapps, and magisk and I got some out of space errors, and I ended up infinite booting. I did manage to flash my custom rom and that does work. However, now i'm back to square one where I need to reinstall twrp, and in order to do that, I need to install a recovery ramdisk because moto g7 powers dont come with a recovery partition because Motorola big brain. Well, upon running
Code:
adb reboot bootloader
and running
Code:
fastboot boot <mytwrpimg>.img
, twrp doesnt ask me to decrypt my partition, and Advanced -> Install Recovery Ramdisk just isn't there. I only see a Reload Theme option, Partition SD Card, and Fix Contexts or something to that effect. What is the issue I am having? I appreciate any help.

I am not an expert, by far, but what version of twrp do you have? I used TWRP-ocean-3.3.1-Syber-v2.2_11-02. Should get the .img and .zip.
Once you fastboot boot twrpxxx.img, use it to install TWRPxxx.zip. You should have a working recovery.

Do you want to install TWRP? It's as easy as flashing TWRP's installer zip.

phone stuck in bootloop

i don't know how else to describe this, i was flashing a custom ROM, then flashed magisk and now my phone is stuck in bootloop unable to go to recovery or system, the phone boots then black screen, etc etc, the same goes for recovery except it is faster (i reflashed recovery and it still happens) unable to do basically anything other than stay in fastboot mode.
what should i do?
edit 1: i can reboot to recovery and only be able to access shell.

Enter fastboot and flash recovery again. Brigudav's TWRP is the most used one. Gringo80's TWRP is new but seems to be working as others have written. (Both are unofficial and a take or leave, we don't have their source code, unfortunately.)
Right after flashing reboot to RECOVERY (not system). Can do with fastboot command or by holding button as usual. Alternative: reboot to recovery image file itself.
Once in recovery, format data (the option that has to type "yes" ). Reboot to RECOVERY again. Wipe cache, dalvik.
Reboot to system. Probably will work if your custom ROM was flashed properly.
Otherwise you can do everything again and also reflash ROM.
EDIT: I missed the Magisk part. So, while in recovery, dirty flash same custom ROM again. Or alternative: rename the Magisk file to uninstall.zip and flash it....this will restore your original boot and completely clean Magisk.
After you properly booting to system, then you can again try install Magisk.

why does flashing TWRP and booting to it directly work? i don't know! but it worked!
it seems that the custom ROM i installed is probably corrupt and flashed anyway ( i reflashed dirty/clean to make sure ) thanks for your help.