Database Info

Bootloop into TWRP no matter how many attempts to clean flash OOS 9.0.2

I was running lineage-16.0-20181203_184022-UNOFFICIAL-enchilada just fine with open gapps nano and Magisk 17.1.
I attempted to upgrade to lineage-16.0-20181208_183559-UNOFFICIAL-enchilada, but I ran into issues with gapps force closing.
I attempted to restore my TWRP nandroid backups, but the attempts at restoring them just put me in a bootloop into TWRP.
Therefore, I am attempting to get back to OOS 9.0.2, OnePlus6Oxygen_22_OTA_027_all_1810260000_d46787d2c9, with a clean flash, following the process:
Fastboot into TWRP with fastboot boot twrp-3.2.3-x_blu_spark_v9.86_op6.img
Wipe -> Advanced Wipe -> Cache, System, Data, Internal Storage
adb push OnePlus6Oxygen_22_OTA_027_all_1810260000_d46787d2c9.zip and twrp-3.2.3-x_blu_spark_v9.86_op6.zip
Install -> OOS 9.0.2 and then TWRP
Reboot into System
No matter how many times I try this, the first boot fails with a vibration from the phone and it reboots into the blu_spark TWRP.
I have also tried the above process from inside the installed TWRP instead of from a fastbooted TWRP. I have also tried the above process with lineage-16.0-20181203_184022-UNOFFICIAL-enchilada.zip instead of OOS.
What could possibly be wrong? Isn't this a completely clean install?

MaxRabbit said:
I was running lineage-16.0-20181203_184022-UNOFFICIAL-enchilada just fine with open gapps nano and Magisk 17.1.
I attempted to upgrade to lineage-16.0-20181208_183559-UNOFFICIAL-enchilada, but I ran into issues with gapps force closing.
I attempted to restore my TWRP nandroid backups, but the attempts at restoring them just put me in a bootloop into TWRP.
Therefore, I am attempting to get back to OOS 9.0.2, OnePlus6Oxygen_22_OTA_027_all_1810260000_d46787d2c9, with a clean flash, following the process:
Fastboot into TWRP with fastboot boot twrp-3.2.3-x_blu_spark_v9.86_op6.img
Wipe -> Advanced Wipe -> Cache, System, Data, Internal Storage
adb push OnePlus6Oxygen_22_OTA_027_all_1810260000_d46787d2c9.zip and twrp-3.2.3-x_blu_spark_v9.86_op6.zip
Install -> OOS 9.0.2 and then TWRP
Reboot into System
No matter how many times I try this, the first boot fails with a vibration from the phone and it reboots into the blu_spark TWRP.
I have also tried the above process from inside the installed TWRP instead of from a fastbooted TWRP. I have also tried the above process with lineage-16.0-20181203_184022-UNOFFICIAL-enchilada.zip instead of OOS.
What could possibly be wrong? Isn't this a completely clean install?
Click to expand...
Click to collapse
Try installing magisk too.

mikex8593 said:
Try installing magisk too.
Click to expand...
Click to collapse
Thanks for the suggestion. Tried installing magisk in between OOS and the TWRP, and then also tried installing OOS, TWRP, rebooting, and installing magisk. No luck either way.

Well, this was a nightmare. Finally fixed it by:
fastbooting into twrp
wiping everything in twrp
flashing oos 9.0.2
NOT installing twrp
bootlooping into oneplus recovery
clearing ALL data through oneplus recovery (after backing up via ADB)
reboot
phone booted up just fine
Wow. Never seen those particular steps mentioned.
After that, I was able to flash OOS 9.0.2 again, then flash lineage-16.0-20181203_184022-UNOFFICIAL-enchilada & TWRP, boot LOS, reboot into TWRP, wipe everything, flash lineage-16.0-20181203_184022-UNOFFICIAL-enchilada again, boot into LOS, reboot into TWRP, restore my system, data, and boot backups from TWRP, and I'm finally back up and running with a fully working backup.

MaxRabbit said:
Well, this was a nightmare. Finally fixed it by:
fastbooting into twrp
wiping everything in twrp
flashing oos 9.0.2
NOT installing twrp
bootlooping into oneplus recovery
clearing ALL data through oneplus recovery (after backing up via ADB)
reboot
phone booted up just fine
Wow. Never seen those particular steps mentioned.
After that, I was able to flash OOS 9.0.2 again, then flash lineage-16.0-20181203_184022-UNOFFICIAL-enchilada & TWRP, boot LOS, reboot into TWRP, wipe everything, flash lineage-16.0-20181203_184022-UNOFFICIAL-enchilada again, boot into LOS, reboot into TWRP, restore my system, data, and boot backups from TWRP, and I'm finally back up and running with a fully working backup.
Click to expand...
Click to collapse
this could have been done in twrp. all you had to do was format data
the correct way is this.
fastbooting into twrp
flashing oos 9.0.2
flashing twrp, to keep twrp.
format data.
install any mod you want, like root.
reboot
this is require only when going from aosp to oos again.

MrSteelX said:
this could have been done in twrp. all you had to do was format data
the correct way is this.
fastbooting into twrp
flashing oos 9.0.2
flashing twrp, to keep twrp.
format data.
install any mod you want, like root.
reboot
this is require only when going from aosp to oos again.
Click to expand...
Click to collapse
How come that would have worked, but wiping system and data and then installing OOS 9.0.2 doesn't? Shouldn't you end up at the same point either way, with a clean OOS 9.0.2 in system and wiped data?

Format is the answer.

MaxRabbit said:
How come that would have worked, but wiping system and data and then installing OOS 9.0.2 doesn't? Shouldn't you end up at the same point either way, with a clean OOS 9.0.2 in system and wiped data?
Click to expand...
Click to collapse
just simply flash oss9.0.2 two time using twrp then get hold of 9.0.2 boot img go back to twrp and the select flash image flash the image and let it boot.
if it works toss a thanks.

MaxRabbit said:
Well, this was a nightmare. Finally fixed it by:
fastbooting into twrp
wiping everything in twrp
flashing oos 9.0.2
NOT installing twrp
bootlooping into oneplus recovery
clearing ALL data through oneplus recovery (after backing up via ADB)
reboot
phone booted up just fine
Wow. Never seen those particular steps mentioned.
After that, I was able to flash OOS 9.0.2 again, then flash lineage-16.0-20181203_184022-UNOFFICIAL-enchilada & TWRP, boot LOS, reboot into TWRP, wipe everything, flash lineage-16.0-20181203_184022-UNOFFICIAL-enchilada again, boot into LOS, reboot into TWRP, restore my system, data, and boot backups from TWRP, and I'm finally back up and running with a fully working backup.
Click to expand...
Click to collapse
Thank you for this. I was trying to dirty flash 9.0.2 to fix a notification issue and ended up in the same situation as you. Format ended up fixing it. Only crappy part is I lost about all my text messages with my SO. Google said it has a 2mb backup for SMS so I'm hoping it got all 30k+ of it
MrSteelX said:
this could have been done in twrp. all you had to do was format data
the correct way is this.
fastbooting into twrp
flashing oos 9.0.2
flashing twrp, to keep twrp.
format data.
install any mod you want, like root.
reboot
this is require only when going from aosp to oos again.
Click to expand...
Click to collapse
Tried this and it ended up causing the exact same problem. The folks installing the new OB8/9 seems to be having similar issues. Not sure what's going on.

its because of security patch. 9.0.2 has nov sec patch, lineage you flashed has dec sec patch. i have experienced this in pixel rom. just flash lineage Nov build, then wipe data and system and flash OOS 9.0.2 and twrp.
do a clean flash

MaxRabbit said:
I was running lineage-16.0-20181203_184022-UNOFFICIAL-enchilada just fine with open gapps nano and Magisk 17.1.
I attempted to upgrade to lineage-16.0-20181208_183559-UNOFFICIAL-enchilada, but I ran into issues with gapps force closing.
I attempted to restore my TWRP nandroid backups, but the attempts at restoring them just put me in a bootloop into TWRP.
Therefore, I am attempting to get back to OOS 9.0.2, OnePlus6Oxygen_22_OTA_027_all_1810260000_d46787d2c9, with a clean flash, following the process:
Fastboot into TWRP with fastboot boot twrp-3.2.3-x_blu_spark_v9.86_op6.img
Wipe -> Advanced Wipe -> Cache, System, Data, Internal Storage
adb push OnePlus6Oxygen_22_OTA_027_all_1810260000_d46787d2c9.zip and twrp-3.2.3-x_blu_spark_v9.86_op6.zip
Install -> OOS 9.0.2 and then TWRP
Reboot into System
No matter how many times I try this, the first boot fails with a vibration from the phone and it reboots into the blu_spark TWRP.
I have also tried the above process from inside the installed TWRP instead of from a fastbooted TWRP. I have also tried the above process with lineage-16.0-20181203_184022-UNOFFICIAL-enchilada.zip instead of OOS.
What could possibly be wrong? Isn't this a completely clean install?
Click to expand...
Click to collapse
You know if all else fails you could always download the Qualcomm MSM tool and boot into Qualcomm mode (with the phone off hold vol down button for about 10-15 seconds and plug into computer), you won't see anything on the screen, load up the tool and it shall put u back to full stock. This will solve all and any sort of bricking which if you flash alot you will by default probably learn how to use

fastboot into twrp
Flash TWRP within twrp
Format all data.
Reboot recovery
transfer OOS
Flash OOS
Flash TWRP
Reboot recovery
Flash OOS
Flash TWRP
Reboot recovery
Flash kernel/magisk/etc
Reboot system.

I just want to tell you that I love you. The format data finally fixed this for me.
MrSteelX said:
this could have been done in twrp. all you had to do was format data
the correct way is this.
fastbooting into twrp
flashing oos 9.0.2
flashing twrp, to keep twrp.
format data.
install any mod you want, like root.
reboot
this is require only when going from aosp to oos again.
Click to expand...
Click to collapse

Bootlooping to recovery after flashing Custom rom

I unlocked my phone yesterday and installed orangefox recovery in it. However after flashing custom rom, it keeps rebooting back to recovery. Have no idea how to solve this. Any solutions?

hackmonker said:
I unlocked my phone yesterday and installed orangefox recovery in it. However after flashing custom rom, it keeps rebooting back to recovery. Have no idea how to solve this. Any solutions?
Click to expand...
Click to collapse
Try wiping data once and reboot to system

Nutya said:
Try wiping data once and reboot to system
Click to expand...
Click to collapse
Tried that. not working. Also if its relevent system, vendoe, etc are not mounted. only data, cache, and microsd is mounted. Have no idea why.

Me too faced this kind of issue, peter's TWRP worked for me, follow instructions from here

Ok It worked. No need to flash the dm Verity for orange recovery. What I did was simple.
1. Factory reset (Did this step before also)
2. Format Data (Also Did this step)
3. Flash rom (Of course did this too)
4. Then reboot to RECOVERY again, not to system. (did not do this step before). Go to reboot part and click reboot to recovery, not to system.
5. After that reboot to system and it should work. Mine did.

Solved
I to had same problem but mine worked after installing custom ROM install FCrypt disabler.zip from recovery then reboot and enjoy.
Download FCrypt disabler.zip for Redmi note 7 Pro from Google.

Flash any zip which disables dm verity things. Suggestion: flash lazyflasher zip.

NO OS Found IN ONEPLUS 6

Hi Team,
Today i was flashing custom os in oneplus 6 via one youtuber videos
He has selected TWRP wipe menu
Advance -> system , data , Davic/ cache
i did same then he installed the os i also did the same and flash twrp
After doing roboot the system TWRP given me error no os was installed i ignored that message and proceed to next
After system was rebooted im only getting fastboot mode and no other options also im unable to install now any TWRP in my system
can some one help me please

Maybe try format data.
Go to wipe then advance wipe and format data.
If it doesnt work then use msmtool to go back to stock rom and start again.

Don't trust every YT videos you see, NEVER wipe system on op6 or you get this result.
Now you can reinstall TWRP from fastboot and reflash stock OOS twice, if it did not work try to flash stock fastboot firmware

here is a simple solution..
Reboot Recovery
Wipe Data, System, Cache
Flash OOS & TWRP
Reboot into recovery (Ignore No OS Installed Warning)
Flash OOS & TWRP Again
Reboot
Done
if you want to Flash Custom ROM, Here is guide
Reboot Recovery
Wipe Data, System, Cache
Flash OOS & TWRP
Reboot into recovery (Ignore No OS Installed Warning)
Flash OOS & TWRP Again
Reboot into Recovery
Flash Custom ROM & TWRP
Reboot into Recovery
Flash Gapps, Magisk Latest & No-Varity zip is had data decrypted
Reboot
Done

Hitman478™ said:
Don't trust every YT videos you see, NEVER wipe system on op6 or you get this result.
Now you can reinstall TWRP from fastboot and reflash stock OOS twice, if it did not work try to flash stock fastboot firmware
Click to expand...
Click to collapse
Any reason why we shouldn't delete system partition in op6?
Sent from my ONEPLUS A6000 using XDA Labs

Bintang Krisna said:
Any reason why we shouldn't delete system partition in op6?
Sent from my ONEPLUS A6000 using XDA Labs
Click to expand...
Click to collapse
The system also holds the recovery....i made that mistake once and i had to use MSM tool to restore my phone. Big waste of my time to a dumb mistake.

[Solved] Help to flash custom ROMs

Hello everybody,
I bought a Oneplus 7 Pro a few days ago and I'm preparing it for my daily usage. It's my fourth Android smartphone, and the third Oneplus. So far, I managed to flash everyone of them, with no major issues.
And then, the Oneplus 7 Pro suddenly appeared
I used this tutorial to unlock the bootloader and flash the custom recovery.
From my understanding, the custom recovery is flashed in the Recovery Ramdisk and available for both A & B slots.
For now, I have A and B slots with stock OSS, unlocked bootloader, custom recovery and Magisk. All of this is working.
There began my problems. I want to flash a custom ROM without Gapps and I fail to do it. All instructions around ROM threads seems different to me, I don't get the thing about A & B slots, when I flash one rom, it boots as usual on the stock ROM, if I flash both slots, It causes bootloops and if I manage to launch the recovery, my internal storage isn't detected and I can't restore any backup.
I already used MSMDownload to restore the phone completely once.
Can somebody explain to my dumb person how to do it proprely ? Thanks in advance ! :fingers-crossed:
TL;DR : I fail to flash a custom ROM and make it work.

Yes I had same issues when rooted, it means you lost root. You can try tool all in one to flash recovery and magesik via fastboot. If that doesn't restore your access, on twrp you will have to type in format, then mount, then add rom to storage(this method wipes everything beware)

djhulk2 said:
Yes I had same issues when rooted, it means you lost root. You can try tool all in one to flash recovery and magesik via fastboot. If that doesn't restore your access, on twrp you will have to type in format, then mount, then add rom to storage(this method wipes everything beware)
Click to expand...
Click to collapse
For now, my phone is working nicely. But that's the process of flashing a new ROM that fails. Recovery and Magisk are already and working.

Factory reset
Flash rom
Flash twrp installer
Reboot recovery
Format data
Reboot system
i boot all roms with these steps

WesTD said:
Factory reset
Flash rom
Flash twrp installer
Reboot recovery
Format data
Reboot system
i boot all roms with these steps
Click to expand...
Click to collapse
Thanks, I will try.
When you flash the ROM, does TWRP tell you that if you want to continue you need to reboot recovery ? If so, do you ? Do you reboot recovery on the same slot, or do you flash both ?

draentor said:
Thanks, I will try.
When you flash the ROM, does TWRP tell you that if you want to continue you need to reboot recovery ? If so, do you ? Do you reboot recovery on the same slot, or do you flash both ?
Click to expand...
Click to collapse
Nope, it doesnt tell you anything. Just reboot recovery from reboot menu. Don't touch the slot options

Thanks for your advices.
I'm trying right now, here's my steps :
- Wipe Data, Cache, Dalvik Cache (the standard Factory Reset)
- Install ROM : TWRP logs show that he's flashing on inactive slot A, then B. After that logs said " To flash additional zips, please reboot recovery to switch to the updated slot ". I'm going back on the menu
- Install TWRP Installer like previously
- Reboot Recovery : TWRP ask me if I want to install the TWRP App, I dismiss. After reboot of the recovery, it asks if I want to keep System Read Only, I swipe to allow modifications
- Wipe Data : Can't do it because TWRP is unable to mount storage. And after further investigations, I'm now on slot A, not B as before.
- Reboot recovery to slot B
- Wipe Data on slot B
- Reboot system
And It still booting on the stock Oxygen OS Rom, not the custom one installed before. I'm lost

The problem is that you are not performing factory reset.
Wipe data is not enough,you gotta go to wipe-format data-enter yes and swipe.
That is why you are getting bootloops and twrp unable to mount storage problem.
A/B is pretty simple.
You got two slots for many partitions like system vendor boot and all,but a single data partition.
Flash a rom from one slot,it always gets flashed to the other slot no matter what.So next time you reboot to recovery or system it's gonna be on the other slot.So here is the problem..one rom cannot decrypt data which was initially encrypted by another rom..so you gotta perform a data format instead of wipe.Thats it.

draentor said:
Thanks for your advices.
I'm trying right now, here's my steps :
- Wipe Data, Cache, Dalvik Cache (the standard Factory Reset)
- Install ROM : TWRP logs show that he's flashing on inactive slot A, then B. After that logs said " To flash additional zips, please reboot recovery to switch to the updated slot ". I'm going back on the menu
- Install TWRP Installer like previously
- Reboot Recovery : TWRP ask me if I want to install the TWRP App, I dismiss. After reboot of the recovery, it asks if I want to keep System Read Only, I swipe to allow modifications
- Wipe Data : Can't do it because TWRP is unable to mount storage. And after further investigations, I'm now on slot A, not B as before.
- Reboot recovery to slot B
- Wipe Data on slot B
- Reboot system
And It still booting on the stock Oxygen OS Rom, not the custom one installed before. I'm lost
Click to expand...
Click to collapse
lol i wrote all steps but you didn't do all of them. Use swipe to wipe for factory reset and you didn't format data

Joker123## said:
The problem is that you are not performing factory reset.
Wipe data is not enough,you gotta go to wipe-format data-enter yes and swipe.
That is why you are getting bootloops and twrp unable to mount storage problem.
A/B is pretty simple.
You got two slots for many partitions like system vendor boot and all,but a single data partition.
Flash a rom from one slot,it always gets flashed to the other slot no matter what.So next time you reboot to recovery or system it's gonna be on the other slot.So here is the problem..one rom cannot decrypt data which was initially encrypted by another rom..so you gotta perform a data format instead of wipe.Thats it.
Click to expand...
Click to collapse
Thanks for the explanation !
WesTD said:
lol i wrote all steps but you didn't do all of them. Use swipe to wipe for factory reset and you didn't format data
Click to expand...
Click to collapse
Well yes, I didn't understood the difference between Wipe and Format Data.
So let's resume :
Unlock Bootloader
Advanced -> Install Recovery Ramdisk : Install TWRP
Install -> Flash TWRP Installer
Install -> Flash Magisk
Reboot -> System : Reboot on stock OxygenOS Rooted
Then
Wipe -> Factory Reset : Wipe Data, Cache and Dalvik Cache, that means you just have to swipe on TWRP.
Install -> Flash ROM : Use the install function and install the ROM
Install -> Flash TWRP Installer : Don't reboot, go back and install as the previous step
Reboot -> Recovery : Reboot TWRP and it automatically load the other slot
Wipe -> Format Data : Click and type yes
Reboot -> System : Just reboot and it should load the installed ROM

is wiping internal storage compulsory?

aaryan45 said:
is wiping internal storage compulsory?
Click to expand...
Click to collapse
How would you do it ? This is an open discussion, I can't find one and only way of doing it

aaryan45 said:
is wiping internal storage compulsory?
Click to expand...
Click to collapse
Not wiping.. formatting..that is compulsory if your current data is encrypted

After multiple tries to verify the process :
Wipe -> Factory Reset + : Wipe Data, System, Cache and Dalvik Cache
Install -> Flash ROM : Use the install function and install the ROM
Install -> Flash TWRP Installer : Don't reboot, go back and install as the previous step
Reboot -> Recovery : Reboot TWRP and it automatically load the other slot
Wipe -> Format Data : Click and type yes
Reboot -> System : Just reboot and it should load the installed ROM
Install -> Magisk
Reboot -> System
Install -> Whathever you want
Reboot -> System
It worked !

Correct Procedure

Hey guys
Just need to know correct Procedure. Im currently on Syberia Rom (Android 12)
I want to go down to a Rom (Android 11)
Do i have the procedure right
Boot into Twrp
Wipe Cache, Data, Davlik
Flash OOS (latest build)
Boot to TWRP
Flash New Rom
Boot to TWRP
Flash Gapps
Flash Magisk
Wipe Data
Reboot system
Would that be the correct process?
Thanks

I wouldn't bother with TWRP. I'd use the MSM tool. Sorry, I'm a bit busy, maybe others can chime in here.