Develop Bugs

Rooting went fine Flashing rom almost bricked me due to directions??

I instslled magisk apk and then booted twrp .img in fastboot as directed and flashed magisk zip from twrp as said too . I Rebooted and was rooted fine . Downloaded Resurrection rom and the guide said to only wipe in twrp flash rom then flash twrp zip again and reboot/profit . The rom splash screen just sat there spitting out little purple pink splatters and never booted so I rebooted into twrp and flashed the twrp zip to make twrp permanent and ended up losing my stock backup from the boot.img twrp and my internal storage . Had taken all night to find the right tool kit to flash firmware back .
What went wrong ? How do you flash rom on this phone I'm no noob but I'm not risking it again .
After you boot twrp and flash magisk are you supposed to flash twrp.zip then make your backups and flash roms? I wasn't sure if it was a long bootup or not gonna boot ever
Sent from my [device_name] using XDA-Developers Legacy app

androidddaaron said:
I instslled magisk apk and then booted twrp .img in fastboot as directed and flashed magisk zip from twrp as said too . I Rebooted and was rooted fine . Downloaded Resurrection rom and the guide said to only wipe in twrp flash rom then flash twrp zip again and reboot/profit . The rom splash screen just sat there spitting out little purple pink splatters and never booted so I rebooted into twrp and flashed the twrp zip to make twrp permanent and ended up losing my stock backup from the boot.img twrp and my internal storage . Had taken all night to find the right tool kit to flash firmware back .
What went wrong ? How do you flash rom on this phone I'm no noob but I'm not risking it again .
After you boot twrp and flash magisk are you supposed to flash twrp.zip then make your backups and flash roms? I wasn't sure if it was a long bootup or not gonna boot ever
Click to expand...
Click to collapse
I see a couple possible problems with your steps. The biggest is not being prepared. Not a shot at you but a fact that comes with a new device. The easiest route at this point would be to list out what exactly you want to have as a finished project. I'm assuming rooted RR with installed TWRP? I ask because if you want to have TWRP installed you should also use a condom kernel that has the touch drivers. I'm not sure if RR had them by default it not. Anyway, confirm what you want and I'm sure one of us will get you pointed in the right direction. You won't find most of us using a tool kit, so you will learn the "right" way... Lol

CyberpodS2 said:
I see a couple possible problems with your steps. The biggest is not being prepared. Not a shot at you but a fact that comes with a new device. The easiest route at this point would be to list our what exactly you want to have as a finished project. I'm assuming rooted RR with installed TWRP? I ask because if you want to have TWRP installed you should also use a condom kernel that has the touch drivers. I'm not sure if RR had them by default it not. Anyway, confirm what you want and I'm sure one of us will get you pointed in the right direction. You won't find most of us using a tool kit, so you will learn the "right" way... Lol
Click to expand...
Click to collapse
I know it's a typo but condom kernel cracked me up. Does it automatically boot you to safe mode?
Sent from my Pixel 2 XL using XDA Labs

androidddaaron said:
I instslled magisk apk and then booted twrp .img in fastboot as directed and flashed magisk zip from twrp as said too . I Rebooted and was rooted fine . Downloaded Resurrection rom and the guide said to only wipe in twrp flash rom then flash twrp zip again and reboot/profit . The rom splash screen just sat there spitting out little purple pink splatters and never booted so I rebooted into twrp and flashed the twrp zip to make twrp permanent and ended up losing my stock backup from the boot.img twrp and my internal storage . Had taken all night to find the right tool kit to flash firmware back .
What went wrong ? How do you flash rom on this phone I'm no noob but I'm not risking it again .
After you boot twrp and flash magisk are you supposed to flash twrp.zip then make your backups and flash roms? I wasn't sure if it was a long bootup or not gonna boot ever
Click to expand...
Click to collapse
What?
I never flashed a custom ROM on this device, but it should be fairly easy. Turn off security settings on stock ROM, flash permanent twrp. Wipe system, dalvik/ cache and data and install RR. Boot and wait a few minutes, it sometimes takes some time. I don't know how the gapps situation is, so you might need to flash gapps. Also make sure to make a backup since you will wipe all data. Should be fairly easy of you followed the steps correctly

Vinnipinni said:
What?
I never flashed a custom ROM on this device, but it should be fairly easy. Turn off security settings on stock ROM, flash permanent twrp. Wipe system, dalvik/ cache and data and install RR. Boot and wait a few minutes, it sometimes takes some time. I don't know how the gapps situation is, so you might need to flash gapps. Also make sure to make a backup since you will wipe all data. Should be fairly easy of you followed the steps correctly
Click to expand...
Click to collapse
What I' did to flash the rom was separate from rooting procedures . The phone been unlocked for months.
I did both separate times
I fastboot booted twrp.img then I installed magisk zip. I did not permanent flash twrp zip after . I only flashed the perm twrp zip after I wiped and flsahed the RR Rom . So another words I was on twrp temp boot only when I flashed the rom then I flashed twrp zip per the rom Dev instructions . But I can't make sense why you have to flash twrp after you flash a rom install .
I'm assuming it goes like this
Install latest magisk apk.
Fastboot boot twrp .img
Then perm flash twrp .zip
Then flash magisk .zip
Reboot into the O.S and check for root
Reboot into (permanent Twrp) swipe to allow modifications .
wipe stock rom with the swipe only method??
Install Rom of choice and reboot !
Or is it install Rom /flash twrp.zip for a second time then reboot
Sent from my [device_name] using XDA-Developers Legacy app

CyberpodS2 said:
I see a couple possible problems with your steps. The biggest is not being prepared. Not a shot at you but a fact that comes with a new device. The easiest route at this point would be to list our what exactly you want to have as a finished project. I'm assuming rooted RR with installed TWRP? I ask because if you want to have TWRP installed you should also use a condom kernel that has the touch drivers. I'm not sure if RR had them by default it not. Anyway, confirm what you want and I'm sure one of us will get you pointed in the right direction. You won't find most of us using a tool kit, so you will learn the "right" way... Lol
Click to expand...
Click to collapse
I want to flash a rom but I'm not understanding how the pixel 2 xl works with twrp vs other devices .
If I reboot without first flashing a kernel then maybe that's the dilemma?
I just don't get why you need to flash permanent twrp .zip after you install Rom If you already had twrp permanent installed to begin with .
I' went over what I did in this thread and what I'm guessing I did wrong. So do I need special kernel for each and every rom listed . I never had to flash a kernel to get a rom to boot on any device and I've been flashing for years with T-Mobile phones on Galaxy devices and unlocked Google based phones.
Sent from my [device_name] using XDA-Developers Legacy app

I don't get why you would need to flash magisk before.
0. Make Backups and turn off security settings. Also make sure you're on the newest OTA
1. Boot into TWRP
2. Do a factory reset in Wipe settings.
3. Flash ROM
4. Flash TWRP of you want, not required but recommended
5. Reboot and set it up
6. Install magisk Manager and reboot to TWRP
7. Flash magisk and reboot
That's it.

CyberpodS2 said:
I see a couple possible problems with your steps. The biggest is not being prepared. Not a shot at you but a fact that comes with a new device. The easiest route at this point would be to list our what exactly you want to have as a finished project. I'm assuming rooted RR with installed TWRP? I ask because if you want to have TWRP installed you should also use a condom kernel that has the touch drivers. I'm not sure if RR had them by default it not. Anyway, confirm what you want and I'm sure one of us will get you pointed in the right direction. You won't find most of us using a tool kit, so you will learn the "right" way... Lol
Click to expand...
Click to collapse
Hey let me ask you something, I just got the Pixel 2 XL but I always do a lot of research. Something I wasn't prepared for is the touch issue in TWRP. It works fine when initially installed, works fine sometimes after a reboot, but always ends up not working because touch isnt working. You're saying I can install a custom kernel and that should be fixed? I've always rocked Elemental or Franco's but am on rooted stock and since I've never stayed stock before I'm not even sure if I can flash another kernel without changing ROMs. If I can, or even if I have to change ROMs, you're saying that most custom kernels have the touch in TWRP working?

nein7three said:
Hey let me ask you something, I just got the Pixel 2 XL but I always do a lot of research. Something I wasn't prepared for is the touch issue in TWRP. It works fine when initially installed, works fine sometimes after a reboot, but always ends up not working because touch isnt working. You're saying I can install a custom kernel and that should be fixed? I've always rocked Elemental or Franco's but am on rooted stock and since I've never stayed stock before I'm not even sure if I can flash another kernel without changing ROMs. If I can, or even if I have to change ROMs, you're saying that most custom kernels have the touch in TWRP working?
Click to expand...
Click to collapse
All the custom kernels fix the twrp touch issue. You can flash them anytime you want on stock rom via twrp. Just disable screen lock(just initially for safety) boot into twrp, flash your kernel then magisk, reboot and done

Badger50 said:
All the custom kernels fix the twrp touch issue. You can flash them anytime you want on stock rom via twrp. Just disable screen lock(just initially for safety) boot into twrp, flash your kernel then magisk, reboot and done
Click to expand...
Click to collapse
Thanks a lot. Does changing kernels remove magisk?

nein7three said:
Thanks a lot. Does changing kernels remove magisk?
Click to expand...
Click to collapse
Some do, some don't. That's why you flash magisk after the kernel. But that's changing as well :good:

Questions about upgrading 5T from 5.1.1 to 5.1.3

Hey. I have a rooted with TWRP installed OnePlus 5T on OOS v5.1.1
I've been receiving the 5.1.3 upgrade for a while now and have decided to update. Can i dirty flash the package or do i need to wipe system and data? I'm guessing the root will not be retained and i will have to root again but will the TWRP recovery stay intact? Thanks for your answers

I guess you would be able dirty flash.
You have to flash the twrp and magisk root again. If you are going to flash latest Open Beta 11, you have to flash Beta 10 before to retain data.

XeniX_Force said:
Hey. I have a rooted with TWRP installed OnePlus 5T on OOS v5.1.1
I've been receiving the 5.1.3 upgrade for a while now and have decided to update. Can i dirty flash the package or do i need to wipe system and data? I'm guessing the root will not be retained and i will have to root again but will the TWRP recovery stay intact? Thanks for your answers
Click to expand...
Click to collapse
I have switched from 5.1.3 to beta11 like;
1- download the rom you want to install from oneplus site.
2- also download the stock recovery image from oneplus site.
3- put both files into the phone.
4- flash the stock recovery you downloaded.
5- boot into stock recovery and install the downloaded rom without wiping or formating anything.
6- enjoy your new rom with all your apps and data.
After the above steps you can install custom recovery and magisk again.
I also highly recommend to take a full backup of your phone .
Sent from my OnePlus 5T using XDA Labs

llvllaster said:
I have switched from 5.1.3 to beta11 like;
1- download the rom you want to install from oneplus site.
2- also download the stock recovery image from oneplus site.
3- put both files into the phone.
4- flash the stock recovery you downloaded.
5- boot into stock recovery and install the downloaded rom without wiping or formating anything.
6- enjoy your new rom with all your apps and data.
After the above steps you can install custom recovery and magisk again.
I also highly recommend to take a full backup of your phone .
Click to expand...
Click to collapse
Why was stock recovery flashed? Can the Rom not be installed using TWRP?

XeniX_Force said:
Why was stock recovery flashed? Can the Rom not be installed using TWRP?
Click to expand...
Click to collapse
Well, i always got an error with twrp. No OS installed or something like that. Tried also a dirty flash with twrp and phone was not able to boot. So i found the way with stock recovery.
Sent from my OnePlus 5T using XDA Labs

llvllaster said:
Well, i always got an error with twrp. No OS installed or something like that. Tried also a dirty flash with twrp and phone was not able to boot. So i found the way with stock recovery.
Sent from my OnePlus 5T using XDA Labs
Click to expand...
Click to collapse
Rom can be flashed with Blu Spark treble TWRP V8.78not normal TWRP. And after you flash reboot to recovery then flash magisk 15.3 and no verity V2 or version 3 if your not encrypted either work, I used V2 just fine.
If you try to flash magisk right after rom it will probably give you an error. Reboot only to recovery BEFORE letting the rom boot or you loose recovery, then magisk will flash, 15.3 is the least grievous version after a successful boot upgrading to 16.4 is easy.
16.6 has been giving people grief also.

Some ROMs are'nt flashing

Okay, lemme get this clear that I'm not a pro in all this stuff. Infact, I'm a total idiot.
I have tried to flash a lot of ROMs on my Moto G5 (cedric) but only 3 of them have worked, namely:
1) Pixel Expirience 7.1.2
2) Ressurection Remix 7.1.2
3) Viper OS 7.1.2
I don't know whats the problem and whether it is with my phone or the ROMs. Also, even after i used these ROMs, the apps which need root access weren't working and yes i did select the Root Access setting to ADB only(cause thats was the only option other than Off). Plz help me guys.....

Astitva_ said:
Okay, lemme get this clear that I'm not a pro in all this stuff. Infact, I'm a total idiot.
I have tried to flash a lot of ROMs on my Moto G5 (cedric) but only 3 of them have worked, namely:
1) Pixel Expirience 7.1.2
2) Ressurection Remix 7.1.2
3) Viper OS 7.1.2
I don't know whats the problem and whether it is with my phone or the ROMs. Also, even after i used these ROMs, the apps which need root access weren't working and yes i did select the Root Access setting to ADB only(cause thats was the only option other than Off). Plz help me guys.....
Click to expand...
Click to collapse
First you need to say how you have done the flashing of roms and which rom didn't flash, or what error you got while installing the rom. And second is you need to install magisk manager to gain root access with twrp, by enabling the root access in developer option won't give you root access you need to install it via twrp.

riyan65 said:
First you need to say how you have done the flashing of roms and which rom didn't flash, or what error you got while installing the rom. And second is you need to install magisk manager to gain root access with twrp, by enabling the root access in developer option won't give you root access you need to install it via twrp.
Click to expand...
Click to collapse
I tried flashing them through TWRP. They all were based on Oreo 8.1. I tried Lineage, Invicta, Viper, RR and pixel expirience. As for the error, i don't really know what error it was but Lineage and RR were stuck on the boot loader and the rest just didnt flash.....

Astitva_ said:
I tried flashing them through TWRP. They all were based on Oreo 8.1. I tried Lineage, Invicta, Viper, RR and pixel expirience. As for the error, i don't really know what error it was but Lineage and RR were stuck on the boot loader and the rest just didnt flash.....
Click to expand...
Click to collapse
Chance are you are using the wrong twrp
64bit roms require you to use the 64bit twrp
See the first post of the lineageos thread for the 64bit twrp
Or you can test out the 64bit twrp that uses my encryption edits
https://forum.xda-developers.com/g5/help/help-testing-build-twrp-arm64-t3874472
If you want to root flash the latest version of Magisk and then install the magisk manager app manually if it's not installed

TheFixItMan said:
Chance are you are using the wrong twrp
64bit roms require you to use the 64bit twrp
See the first post of the lineageos thread for the 64bit twrp
Or you can test out the 64bit twrp that uses my encryption edits
https://forum.xda-developers.com/g5/help/help-testing-build-twrp-arm64-t3874472
If you want to root flash the latest version of Magisk and then install the magisk manager app manually if it's not installed
Click to expand...
Click to collapse
I'm sorry but i didn't get what you said. I'm really sorry but I'm really a noob. I would like it if you helped me out a bit....

Astitva_ said:
I'm sorry but i didn't get what you said. I'm really sorry but I'm really a noob. I would like it if you helped me out a bit....
Click to expand...
Click to collapse
All custom oero roms for this device are 64 bit
You need to flash them with a twrp that has been compiled for 64bit twrp use
My official twrp is for 32bit roms only and will not flash 64bit roms - you will get error 7 or I think error 256 or something like that
Flash the 64bit twrp if you want to flash 64bit custom roms - process is the same as if flashing the official twrp via fastboot but you obviously use the 64bit twrp image instead
As mentioned link to 64bit twrp is on the lineageos 15.1 thread first page or try the version in the link I posted in previous post

TheFixItMan said:
All custom oero roms for this device are 64 bit
You need to flash them with a twrp that has been compiled for 64bit twrp use
My official twrp is for 32bit roms only and will not flash 64bit roms - you will get error 7 or I think error 256 or something like that
Flash the 64bit twrp if you want to flash 64bit custom roms - process is the same as if flashing the official twrp via fastboot but you obviously use the 64bit twrp image instead
As mentioned link to 64bit twrp is on the lineageos 15.1 thread first page or try the version in the link I posted in previous post
Click to expand...
Click to collapse
So, I can directly flash the new twrp like i flash the roms right?? Also, what can i do for project treble in my phone...i mean, i cant find redwolf for moto g5(cedric)

Astitva_ said:
So, I can directly flash the new twrp like i flash the roms right?? Also, what can i do for project treble in my phone...i mean, i cant find redwolf for moto g5(cedric)
Click to expand...
Click to collapse
You flash twrp via fastboot commands
fastboot flash recovery recovery.img
Although it is technically possible to flash twrp via twrp if you select image flash & select recovery as the image you are flashing but I'd stick with the fastboot method
I don't own this device anymore so no idea about files that are no longer available

TheFixItMan said:
You flash twrp via fastboot commands
fastboot flash recovery recovery.img
Although it is technically possible to flash twrp via twrp if you select image flash & select recovery as the image you are flashing but I'd stick with the fastboot method
I don't own this device anymore so no idea about files that are no longer available
Click to expand...
Click to collapse
Okay, so i flashed the twrp...but still therom isnt flashing....should i upload the rom so that you can see it?

basically;
if a rom has [64bit] in the title, then it's 64 bit, if it is then you need a 64bit recovery which you can easily find on the forum. you dont even need to know what that means.

Astitva_ said:
Okay, so i flashed the twrp...but still therom isnt flashing....should i upload the rom so that you can see it?
Click to expand...
Click to collapse
Just link to the rom on xda and give the twrp error
The rom either isn't for this device eg you are trying to flash a moto g5 plus or s rom or you are using the wrong twrp or you haven't formatted system data cache before flashing the rom

How to update with twrp and root access installed?

Hello,
i have version 11.0.2.0 Global on the device with twrp, magisk and edXposed.
Now I have seen that there is already a global version 11.0.6.0.
In my case, how can I update to a new version without losing the data and settings?
And one more question in general. Version 11.0.6.0 is not shown to me via OTA. Here it says, latest stable version 11.0.2.0. Is it not rolled out via OTA?
And if there was a newer version available via OTA, could I install the update despite TWRP?

hmarder said:
Hello,
i have version 11.0.2.0 Global on the device with twrp, magisk and edXposed.
Now I have seen that there is already a global version 11.0.6.0.
In my case, how can I update to a new version without losing the data and settings?
And one more question in general. Version 11.0.6.0 is not shown to me via OTA. Here it says, latest stable version 11.0.2.0. Is it not rolled out via OTA?
And if there was a newer version available via OTA, could I install the update despite TWRP?
Click to expand...
Click to collapse
I (without root) flashed the OTA on 11.0.2.0 global PGGMIXM to 11.0.6.0, but, to flash with root... Maybe (I dont know if it will brick) but you can try flash a recovery version of 11.0.6.0

hmarder said:
Hello,
i have version 11.0.2.0 Global on the device with twrp, magisk and edXposed.
Now I have seen that there is already a global version 11.0.6.0.
In my case, how can I update to a new version without losing the data and settings?
And one more question in general. Version 11.0.6.0 is not shown to me via OTA. Here it says, latest stable version 11.0.2.0. Is it not rolled out via OTA?
And if there was a newer version available via OTA, could I install the update despite TWRP?
Click to expand...
Click to collapse
I had exactly the same setup as you - here's what I did: 1 - Downloaded full rom from official Mi website (MIUI Global 11.0.6.0(PGGMIXM) 2 - Moved rom to root storage 3 - Flashed rom with TWRP, and voila! Updated to latest stable rom. Just remember to flash TWRP recovery again through Fastboot, because you will have stock recovery after update. I am using LTWRP- 3.3.1 -0924 and rooted and installed Magisk, without issues

hmarder said:
Hello,
i have version 11.0.2.0 Global on the device with twrp, magisk and edXposed.
Now I have seen that there is already a global version 11.0.6.0.
In my case, how can I update to a new version without losing the data and settings?
And one more question in general. Version 11.0.6.0 is not shown to me via OTA. Here it says, latest stable version 11.0.2.0. Is it not rolled out via OTA?
And if there was a newer version available via OTA, could I install the update despite TWRP?
Click to expand...
Click to collapse
One thing you forgot to mention is what region is your phone (not your Rom). If Chinese you may have to be extra cautious and steps above might not work for you.
Good luck!

KonahZave said:
I (without root) flashed the OTA on 11.0.2.0 global PGGMIXM to 11.0.6.0, but, to flash with root... Maybe (I dont know if it will brick) but you can try flash a recovery version of 11.0.6.0
Click to expand...
Click to collapse
Interesting. I'm still on rooted miui 10 4.5.0 PGGEUXM rooted magisk and twrp recovery-红米Note8Pro-3.3.1-9.0.img
I didn't update yet as bricking started to happen and I can't miss my phone as a daily driver.
Normally I would flash the full ROM, flash magisk, wipe cache and reboot.
So flashing full ROM doesn't break root?
Can't we flash recovery by twrp after flashing ROM instead by flashing by fastboot?

Isnt secure flash twrp after the ROM.

donkyshot said:
So flashing full ROM doesn't break root?
Can't we flash recovery by twrp after flashing ROM instead by flashing by fastboot?
Click to expand...
Click to collapse
Flashing a full rom will break root, and install stock recovery...
It is too risky to flash another recovery with twrp (possible brick)

so where to put official update on sd card?
download recovery rom?

unoturbo1 said:
I had exactly the same setup as you - here's what I did: 1 - Downloaded full rom from official Mi website (MIUI Global 11.0.6.0(PGGMIXM) 2 - Moved rom to root storage 3 - Flashed rom with TWRP, and voila! Updated to latest stable rom. Just remember to flash TWRP recovery again through Fastboot, because you will have stock recovery after update. I am using LTWRP- 3.3.1 -0924 and rooted and installed Magisk, without issues
Click to expand...
Click to collapse
I just brought rmn8p with miui 11.0.6.0 ,so it is ok to use LRTWRP-3.3.1 -0924. I came across a new version -1104, I'll try it after unlock the bootloader. After that flash preloader then trwp.

Use LR.TWRP, it got an option to make the TWRP persist on every OTA.
Also LR.TWRP = less headache on Xiaomi devices.
Here's the latest build: https://mega.nz/folder/cMAT3Q4b#7CbPV7sbEuSEdP7cehXJ-w

tze_vitamin said:
so where to put official update on sd card?
download recovery rom?
Click to expand...
Click to collapse
??
Put on external sd card dude

unoturbo1 said:
I had exactly the same setup as you - here's what I did: 1 - Downloaded full rom from official Mi website (MIUI Global 11.0.6.0(PGGMIXM) 2 - Moved rom to root storage 3 - Flashed rom with TWRP, and voila! Updated to latest stable rom. Just remember to flash TWRP recovery again through Fastboot, because you will have stock recovery after update. I am using LTWRP- 3.3.1 -0924 and rooted and installed Magisk, without issues
Click to expand...
Click to collapse
For chinese, this will brick the phone. See this instead.

Guys I Just see This video and in it shows the update process, with ltwrp, when the recovery capture the process and update even without losing data, its This True?, somebody has tried?
Link.

This will brick every phone. I brick my EU ROM, with this method of update rooted phone.

What is correct solution to update rooted phone?
Redmi Note 8 Pro, 11.0.2 QGGEUXM, TWRP 3.3.1 1210, Magisk 20.3 -> 12.0.1 QGGEUXM
System say there exists update, i choose download, select reboot, but after reboot i end up in TWRP but nothing happened. After exit i boot to old 11.0.2 system with message that update fail.
Edit 1: after 2. download/update/reboot TWRP start installing image ...
Edit 2: after automatic update system say 12.0.1, just loosing root (all apps stay)
Edit 3: installed TWRP again, Magisk (there was little problem because Magisk Manager say "not installed", but after some googlig i fix that. So i update system without reinstalling apps or loosing data.
Clear solution is probably download full rom from official Mi website and flash selected rom with TWRP (flash TWRP recovery again, repeat root process, to get root back). See next post.

RedMu said:
So what is correct solution to update rooted phone?
Redmi Note 8 Pro, 11.0.2 QGGEUXM, TWRP 1210, Magicks 20.3 -> 12.0.1 QGGEUXM
Now system say there exists update, i choose download, select reboot, but after reboot i end up in TWRP. After exit i boot to old 11.0.2 system with message that update fail.
So solution is probably downloaded full rom from official Mi website and flash selected rom with TWRP (flash TWRP recovery again, repeat root process, to get root back).
So what is correct way for update in this case?
Click to expand...
Click to collapse
This is how I upgraded, try at your own risk.
Download full recovery zip of MIUI 12 and latest magisk
Create twrp Backup just in case
In LR TWRP 10 mount & format system, cache, dalvik, vendor.
Flash full rom (not ota!)
Press home to return to the main screen Choose Advanced-File Manager item >system_root / system / folder at the bottom if there is a recovery_fromboot.p file delete it.
Go back to Advanced and select Close AVB2.0 and confirm with a swipe to the right.
flash Magisk
boot to system
First boot takes a while, relax and grab a drink
Remember to backup and close AVB!

Thank you so much for sharing these steps. I have questions for a couple of steps below:
donkyshot said:
This is how I upgraded, try at your own risk.
Download full recovery zip of MIUI 12 and latest magisk
Create twrp Backup just in case
In LR TWRP 10 mount & format system, cache, dalvik, vendor.
Click to expand...
Click to collapse
What is TWRP 10? Do I format first and then mount? I usually wipe system, cache, dalvik and then "install" the full rom (your next step), but i never try "mount" here. What does mount do here? what is wiping vender and mounting vender?
donkyshot said:
[*]Flash full rom (not ota!)
[*]Press home to return to the main screen Choose Advanced-File Manager item >system_root / system / folder at the bottom if there is a recovery_fromboot.p file delete it.
[*]Go back to Advanced and select Close AVB2.0 and confirm with a swipe to the right.
Click to expand...
Click to collapse
There are two check box here. one is "close the boot verification of avb2.0" the other is "close the DMVerity of avb2.0". Do O check one of both?
Thank you!

po1 said:
Thank you so much for sharing these steps. I have questions for a couple of steps below:
What is TWRP 10? Do I format first and then mount? I usually wipe system, cache, dalvik and then "install" the full rom (your next step), but i never try "mount" here. What does mount do here? what is wiping vender and mounting vender?
There are two check box here. one is "close the boot verification of avb2.0" the other is "close the DMVerity of avb2.0". Do O check one of both?
Thank you!
Click to expand...
Click to collapse
Recovery LR TWRP for Android 10
https://androidfilehost.com/?fid=8889791610682889486
First mount system, cache, dalvik, vendor
Than format system, cache, dalvik, vendor
Without mounting folders they won't be mounted
►go back to your main screen: ADVANCED- close AVB 2.0 then swipe to confirm, just tick only 1st box, ignore the second box

[Rom] [10] Resurrection Remix

Hey guys. Until the RR dev makes a thread, this will continue to stay in Discussion. I am NOT the dev for RR. So wanted to get the rom more exposure.
Rom: https://sourceforge.net/projects/resurrectionremix-ten/files/instantnoodlep/
Kernel source: https://github.com/luk1337/android_kernel_oneplus_sm8250
Changelog: https://get.resurrectionremix.com/ten/changelog/Changelog.txt
Be on OOS 10(both slots)(local upgrade last OOS 10 for slot b)
Flash twrp both slots(https://downloads.sourceforge.net/p...=cfhcable&r=https://forum.xda-developers.com/)
Flash rom
Reboot twrp
Wipe userdata(always a must when switching between OOS and custom)
(Optional) install kernel and magisk
Reboot
**UPDATE** this flash instructions work. I use these and ONLY these instructions. If you have a better way, good for you, but if you can't get it to boot, use these.
***UPDATE 2*** if you have installed Android 11 prior to installing this rom, you must msm back to OOS 10 and local upgrade OOS 10 again to slot b and only use Android 10 recovery

Nice one. :good:
Is twrp ok to wipe now? Or would we need stock to do so?
If the latter then may be worth booting twrp and retaining stock recovery to wipe.
Good to see a ROM thread for this.
Excellent.
My thanks to the dev too, it's appreciated.

dladz said:
Nice one. :good:
Is twrp ok to wipe now? Or would we need stock to do so?
If the latter then may be worth booting twrp and retaining stock recovery to wipe.
Good to see a ROM thread for this.
Excellent.
My thanks to the dev too, it's appreciated.
Click to expand...
Click to collapse
I've had no issues using latest twrp

jamescable said:
I've had no issues using latest twrp
Click to expand...
Click to collapse
Does it have oos cam?

areyouanand said:
Does it have oos cam?
Click to expand...
Click to collapse
Honestly, don't know. I don't use OOS can, but I don't think so

jamescable said:
Hey guys. Until the RR dev makes a thread, this will continue to stay in Discussion. I am NOT the dev for RR. So wanted to get the rom more exposure.
Rom: https://get.resurrectionremix.com/?dir=ten/instantnoodlep
Kernel source: https://github.com/luk1337/android_kernel_oneplus_sm8250
Be on OOS
Flash twrp both slots
Flash rom
Reboot twrp
Wipe userdata(always a must when switching between OOS and custom)
(Optional) install kernel and magisk
Reboot
Click to expand...
Click to collapse
Why to boot to twrp after flashing the rom?
We can just boot the twrp( not flash it)
Flash rom
Flash magisk ( optional)
Format data
Reboot

It should be mentioned that these builds are blind builds. The Dev doesn't own the device.

Kollachi said:
It should be mentioned that these builds are blind builds. The Dev doesn't own the device.
Click to expand...
Click to collapse
Correct but doesn't matter. I tested first few builds before they were released and now alots of people used them. They aren't beta or alpha but stable. So? What's your point?

cultofluna said:
Why to boot to twrp after flashing the rom?
We can just boot the twrp( not flash it)
Flash rom
Flash magisk ( optional)
Format data
Reboot
Click to expand...
Click to collapse
8pro has a recovery partition. So unless you flash a rom that overwrites twrp with another recovery (stock OOS, etc) then twrp will remain after rom flash

jamescable said:
Correct but doesn't matter. I tested first few builds before they were released and now alots of people used them. They aren't beta or alpha but stable. So? What's your point?
Click to expand...
Click to collapse
It's simple. If people run into issues or whatever he can't probably fix it. It was the same with treskmod for example.

Kollachi said:
It's simple. If people run into issues or whatever he can't probably fix it. It was the same with treskmod for example.
Click to expand...
Click to collapse
[Mod Edit] Telegram link removed.

jamescable said:
[Mod Edit] Telegram link removed.
Click to expand...
Click to collapse
He is blind building from latest los source that's all. Respect him for doing that, but it's not 100% guarantee for a fully working rom.

jamescable said:
8pro has a recovery partition. So unless you flash a rom that overwrites twrp with another recovery (stock OOS, etc) then twrp will remain after rom flash
Click to expand...
Click to collapse
This is something that i already know...
Questions are...
1. why to boot to twrp after flashing the rom( useless step)
2. Why to flash twrp on both slots and not inly boot it

cultofluna said:
This is something that i already know...
Questions are...
1. why to boot to twrp after flashing the rom( useless step)
2. Why to flash twrp on both slots and not inly boot it
Click to expand...
Click to collapse
1. Is NOT useless. That is for clean flashing which is ALWAYS recommend by every dev. When you dirty flash, it's at your own peril.
And 2. Once again. The OnePlus 8 pro has a recovery partition. So twrp does not get overwritten when you flash a rom. Like on 7 pro, we had to flash twrp after every rom flash. Not needed on 8 pro.

cultofluna said:
This is something that i already know...
Questions are...
1. why to boot to twrp after flashing the rom( useless step)
2. Why to flash twrp on both slots and not inly boot it
Click to expand...
Click to collapse
1. I think he meant to say reboot to recovery and not boot the twrp.img.
2. Yes you can boot twrp only. That's what im doing since OP7. But you will need to do this everytime you wanna flash something with twrp.

jamescable said:
1. Is NOT useless. That is for clean flashing which is ALWAYS recommend by every dev. When you dirty flash, it's at your own peril.
And 2. Once again. The OnePlus 8 pro has a recovery partition. So twrp does not get overwritten when you flash a rom. Like on 7 pro, we had to flash twrp after every rom flash. Not needed on 8 pro.
Click to expand...
Click to collapse
On your flashing instructions you said. "flash twrp on both slots"
So im asking one more time,... why not just to boot the twrp img on fastboot and flash the rom...
What is this about recovery partition ... everybody knows that the 8 pro has a separate recovery partition
EDIT..Reboot to twrp after flashing the Rom is useless...
I insist. .dont needed

cultofluna said:
On your flashing instructions you said. "flash twrp on both slots"
So im asking one more time,... why not just to boot the twrp img on fastboot and flash the rom...
What is this about recovery partition ... everybody knows that the 8 pro has a separate recovery partition
EDIT..Reboot to twrp after flashing the Rom is useless...
I insist. .dont needed
Click to expand...
Click to collapse
It's in the pic I uploaded. Even the twrp dev said to flash it. So you won't have to fastboot boot anymore. Once you flash it. It's on your phone and won't go away when you reboot recovery

Every phone used to have a boot(kernel) partition, system partition, modem/radio partition, bootloader, userdata, and a few other INCLUDING recovery partition. Recently, the recovery was missing but now it's back. So we no longer have to have to boot twrp but flash it

Hello everyone, I need help installing this rom please, I have the latest TWRP 3.4.0-14-Mauronofrio installed in both slots, latest stable OOS in both slots, I have an IN2025 and for some reason I get this error with TWRP. Thanks in advance guys.

oscarmaldonado said:
Hello everyone, I need help installing this rom please, I have the latest TWRP 3.4.0-14-Mauronofrio installed in both slots, latest stable OOS in both slots, I have an IN2025 and for some reason I get this error with TWRP. Thanks in advance guys.
Click to expand...
Click to collapse
That is strange. I also have 2025. Try moving the rom to phone instead of usb device. Since this is an updated twrp may be an issue. However. I did NOT have OOS installed on both slots. I flashed latest OOS full rom, used OOS recovery to wipe data. Booted and then flashed twrp to both slots, flashed RR, reboot recovery and flashed magisk