Database Info

OP 6 freezes at fastboot screen after miui 10

I followed instructions carefully. Unlocked boot loader, installed Beta 11 (newest one), flashed TWRP. Next, flashed windows flasher.bat.......... back to fastboot, booted into recovery, VOILA, no TWRP, standard recovery. Reboot and stuck on bootloader. Have to unbrick and back to square one. happened 2 times. Now, there is an option in MIUI 10 unpack that has "flasher windows no format.bat. Anyone else having this problem?

Reading the instruction on the miui rom thread, i guess to understand that you need to boot twrp, it means you need to boot it like when you go to install it, miui rom has no twrp integrated, so in bootloader run twrp img via adb then install it as usual then flash the last miui 10 fix zip... Note that i give you this advice only by reading the thread because i've not tried that rom

I understand your apprehension, I would also, but thanks for your input.

The issue is when you flash miui 10 via instructions, it wipes out everything, so you have to re install twrp, but miui10 fixes zip is gone, and therefore it reboots to a frozen fastboot. OH well.........

Why you don't try to flash bluespark twrp recovery in fastboot? perhaps you need to reboot to recovery and flash magisk

Toni Moon said:
Why you don't try to flash bluespark twrp recovery in fastboot? perhaps you need to reboot to recovery and flash magisk
Click to expand...
Click to collapse
I'll try blu spark, if that doesn't work, i'll try to flash the rom via twrp, and now cmd

You have to use OB8 in both slots or else MIUI 10 won't work.

ProtoDeVNan0 said:
You have to use OB8 in both slots or else MIUI 10 won't work.
Click to expand...
Click to collapse
how the heck do you do that??

could all this be because i'm on beta 11 and not 8?

Android 10 & Custom ROM & Slot A + B

Hello Android developers and enthusiasts,
I've been installing ROM since 2011 so I would not call myself a n00b however I seemingly cannot install an Android 10 ROM without issues. So this is a plea for help and advice!
I know you need to have OOS installed before you install a custom ROM so I use Auto Flash ROM to install OOS with Android 9 via System Update. I then boot and set up phone, install update, reboot and then install the OOS android 10 via the System Update. I then have a OOS installed with Android 10.
Why would I use such an elaborate method you may ask? Well, I tried to download latest OOS from OnePlus site and wipe phone and then install OOS but that fails (didn't record the error I'm afraid).
I then download all the ROM + dependencies on an USB stick and use fastboot to flash Mauronofrio TWRP. I then follow the steps in the ROM instructions. For EvolutionX these were:
First Time Install / Clean Flash
- Have OOS 10.3 flashed to both slots!!
- Boot to recovery
- Flash BUILD.zip (TWRP built-in)
- Wipe Cache
- Format data
- Reboot to recovery (optional)
- Flash Magisk.zip (optional)
- Reboot to system & #KeepEvolving
Click to expand...
Click to collapse
I followed these to the letter but when i rebooted system I got a snapdragon error and it wouldn't even boot into TWRP until I used fastboot to flash boot into TWRP. I also tried HavocROM and same happened.
I did manage to install Syberia using above method but I didn't like the ROM that much unfortunately.
Finally, I've also read up a lot on Slot A and B but it still is not very clear to me. I think I understand it but what happens does not confirm my theories
I therefore have some questions:
- Should I be able to wipe my phone and install OOS on a wiped phone and then install a custom ROM?
- When I install ROM and it says "Reboot Recovery" and then install ROM again. But if I check what slot is being used the reboot doesn't seem to change the slot. My assumption was that booting recovery was to install ROM in the other slot. Is that correct?
Any other tips you can give me?
Again, I like to stress I am not new to installing custom ROMs so I am a bit disappointed that this is causing me such grief.
Following some answers I will retry tomorrow so I can give some more details if needed. For now, appreciate any help.

roel1976 said:
Hello Android developers and enthusiasts,
I've been installing ROM since 2011 so I would not call myself a n00b however I seemingly cannot install an Android 10 ROM without issues. So this is a plea for help and advice!
I know you need to have OOS installed before you install a custom ROM so I use Auto Flash ROM to install OOS with Android 9 via System Update. I then boot and set up phone, install update, reboot and then install the OOS android 10 via the System Update. I then have a OOS installed with Android 10.
Why would I use such an elaborate method you may ask? Well, I tried to download latest OOS from OnePlus site and wipe phone and then install OOS but that fails (didn't record the error I'm afraid).
I then download all the ROM + dependencies on an USB stick and use fastboot to flash Mauronofrio TWRP. I then follow the steps in the ROM instructions. For EvolutionX these were:
I followed these to the letter but when i rebooted system I got a snapdragon error and it wouldn't even boot into TWRP until I used fastboot to flash boot into TWRP. I also tried HavocROM and same happened.
I did manage to install Syberia using above method but I didn't like the ROM that much unfortunately.
Finally, I've also read up a lot on Slot A and B but it still is not very clear to me. I think I understand it but what happens does not confirm my theories
I therefore have some questions:
- Should I be able to wipe my phone and install OOS on a wiped phone and then install a custom ROM?
- When I install ROM and it says "Reboot Recovery" and then install ROM again. But if I check what slot is being used the reboot doesn't seem to change the slot. My assumption was that booting recovery was to install ROM in the other slot. Is that correct?
Any other tips you can give me?
Again, I like to stress I am not new to installing custom ROMs so I am a bit disappointed that this is causing me such grief.
Following some answers I will retry tomorrow so I can give some more details if needed. For now, appreciate any help.
Click to expand...
Click to collapse
Hi!
I had this exact same problem a couple months ago. Rebooting to recovery used to change slots for me, but then it stopped.
What you can do is change active slot manually on Reboot section. By doing this, you don't even have to reboot to recovery in other to flash the other slot (altough I do it just to be safe).
And remember: the rom is flashed on the inactive slot, so after the final flash you gotta change slots one more time.

When you flash one ROM on top of another different ROM, particularly OOS to custom, always wipe data and not format data, because some custom ROMs do not support being unencrypted in the first time and then encrypt on the first boot. So do it like this:
Flash OOS
Flash TWRP
Reboot recovery
Flash OOS
Flash TWRP
Reboot system
Complete initial setup
Reboot to recovery
Wipe (not format) data
Flash custom ROM (start here for dirty flashing ROM update)
Flash TWRP
Reboot recovery
Flash custom ROM
Flash TWRP
Reboot recovery
Flash Magisk
Reboot system
I don't like built-in TWRP in custom ROMs. I always use @mauronofrio's TWRP. So regardless if the custom ROM I'm using has TWRP built-in or not, I always use the method above. I didn't have a problem with installing ROMs using his TWRP. Slots always switch when flashing ROM.

Thanks for the info, it really helps.
One question: in your experience can you wipe your phone and then installl OOS on the wiped phone?

So I just booted into TWRP, did standard wipe action: Data, Cache, and Dalvik. I then try to flash the latest OOS zip and I then get this error:
Error applying update: 7 (ErrorCode::kInstallDeviceOpenError)
Updater process ended withL ERROR: 1.
Error installing zip file: '/usbstorage/00, INSTALL/OnePlus6Oxygen_22_OTA_044_all_2002220042_a46425f1bfe43d2.zip
FIXED: I was using TWRP 3.3.1.11 and I then found out there was a newer version: 3.3.1.18 which you can get here: https://sourceforge.net/projects/mauronofrio-twrp/files/Enchilada/
I am now able to install OOS from scratch (ie wiped phone).

remewer said:
When you flash one ROM on top of another different ROM, particularly OOS to custom, always wipe data and not format data, because some custom ROMs do not support being unencrypted in the first time and then encrypt on the first boot. So do it like this:
Flash OOS
Flash TWRP
Reboot recovery
Flash OOS
Flash TWRP
Reboot system
Complete initial setup
Reboot to recovery
Wipe (not format) data
Flash custom ROM (start here for dirty flashing ROM update)
Flash TWRP
Reboot recovery
Flash custom ROM
Flash TWRP
Reboot recovery
Flash Magisk
Reboot system
I don't like built-in TWRP in custom ROMs. I always use @mauronofrio's TWRP. So regardless if the custom ROM I'm using has TWRP built-in or not, I always use the method above. I didn't have a problem with installing ROMs using his TWRP. Slots always switch when flashing ROM.
Click to expand...
Click to collapse
I tried this method and everytime I can't seem to flash oos onto the other slot because when it reboots to recovery the folder is encrypted so I can't see which file is the zip. How do I flash the seccond OOS if it shows up encrypted in TWRP.
I have a OnePLus 6 with the latest OOS now because I got into boot loop and i used a flash-all.bat to get back to stock. I also use maronofrio's twrp because that works.

harshybar said:
I tried this method and everytime I can't seem to flash oos onto the other slot because when it reboots to recovery the folder is encrypted so I can't see which file is the zip. How do I flash the seccond OOS if it shows up encrypted in TWRP.
I have a OnePLus 6 with the latest OOS now because I got into boot loop and i used a flash-all.bat to get back to stock. I also use maronofrio's twrp because that works.
Click to expand...
Click to collapse
If you can boot OOS fine, try to do a local update so that both slots have OOS. Then try to flash a custom ROM again using the method I've mentioned.

remewer said:
If you can boot OOS fine, try to do a local update so that both slots have OOS. Then try to flash a custom ROM again using the method I've mentioned.
Click to expand...
Click to collapse
When you say local update you mean while I am running the rom, go to settings then do update from local source?

harshybar said:
When you say local update you mean while I am running the rom, go to settings then do update from local source?
Click to expand...
Click to collapse
Exactly

GuestD2559 said:
When you flash one ROM on top of another different ROM, particularly OOS to custom, always wipe data and not format data, because some custom ROMs do not support being unencrypted in the first time and then encrypt on the first boot. So do it like this:
Flash OOS
Flash TWRP
Reboot recovery
Flash OOS
Flash TWRP
Reboot system
Complete initial setup
Reboot to recovery
Wipe (not format) data
Flash custom ROM (start here for dirty flashing ROM update)
Flash TWRP
Reboot recovery
Flash custom ROM
Flash TWRP
Reboot recovery
Flash Magisk
Reboot system
I don't like built-in TWRP in custom ROMs. I always use @mauronofrio's TWRP. So regardless if the custom ROM I'm using has TWRP built-in or not, I always use the method above. I didn't have a problem with installing ROMs using his TWRP. Slots always switch when flashing ROM.
Click to expand...
Click to collapse
@Cypher_01, Try this guide. This worked for me. I did not reinstall Nikgapps. Maybe that's where the problem lies? Don't forget to change the update slot at the end before you restart.​

very frustrating to install lineage

i just need to know which steps to take, in which order.
i can later add details to the steps.
but every f*&(^*( time i have to upgrade phone (ota doesnt work to upgrade to guacamole)
i have to rediscover which order.... finally i'm on a quest to log it all
1) install fastboot/adb on pc/linux/mac
2) unlock phone
3) fastboot flash boot twrp.img
4) reboot to recovery (should go to twrp)
5) flash twrp.zip
6) flash magisk
7) flash lineage_nightly.zip
8) reboot to os
Lineage will finally load... "about phone" says i'm in 17.1 guacamole doing this now my sim card won't read.... & i can't rotate screen (a problem i've had when the last lineage 16.? worked)
i can't flash oxygen.. cuz an error comes up
i need help
(i did wipe all data etc.. but i need to place the wipes in the order above)
(after flashing to lineage, the settings say im encrypted(maybe that matters))
EDIT: to make matters easier.. i can get into fastboot mode now, and my linux pc recognizes the phone
how can i fix this

Did you also FORMAT your data?

Use MSM Tool
csmooth2001 said:
i just need to know which steps to take, in which order.
i can later add details to the steps.
but every f*&(^*( time i have to upgrade phone (ota doesnt work to upgrade to guacamole)
i have to rediscover which order.... finally i'm on a quest to log it all
1) install fastboot/adb on pc/linux/mac
2) unlock phone
3) fastboot flash boot twrp.img
4) reboot to recovery (should go to twrp)
5) flash twrp.zip
6) flash magisk
7) flash lineage_nightly.zip
8) reboot to os
Lineage will finally load... "about phone" says i'm in 17.1 guacamole doing this now my sim card won't read.... & i can't rotate screen (a problem i've had when the last lineage 16.? worked)
i can't flash oxygen.. cuz an error comes up
i need help
(i did wipe all data etc.. but i need to place the wipes in the order above)
(after flashing to lineage, the settings say im encrypted(maybe that matters))
EDIT: to make matters easier.. i can get into fastboot mode now, and my linux pc recognizes the phone
how can i fix this
Click to expand...
Click to collapse
Same thing happened to me, I went from locked boot loader to unlock + lineage. When I tried to go back, the error kept popping up and the only thing that worked was fastboot.
Use MSM tool linked below and you should be good.
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
Note : IMPORTANT ! msm tool will also relock your bootloader, so you will lose any data you might have on your phone.

csmooth2001 said:
i just need to know which steps to take, in which order.
i can later add details to the steps.
but every f*&(^*( time i have to upgrade phone (ota doesnt work to upgrade to guacamole)
i have to rediscover which order.... finally i'm on a quest to log it all
1) install fastboot/adb on pc/linux/mac
2) unlock phone
3) fastboot flash boot twrp.img
4) reboot to recovery (should go to twrp)
5) flash twrp.zip
6) flash magisk
7) flash lineage_nightly.zip
8) reboot to os
Lineage will finally load... "about phone" says i'm in 17.1 guacamole doing this now my sim card won't read.... & i can't rotate screen (a problem i've had when the last lineage 16.? worked)
i can't flash oxygen.. cuz an error comes up
i need help
(i did wipe all data etc.. but i need to place the wipes in the order above)
(after flashing to lineage, the settings say im encrypted(maybe that matters))
EDIT: to make matters easier.. i can get into fastboot mode now, and my linux pc recognizes the phone
how can i fix this
Click to expand...
Click to collapse
Wrong order. First flash LOS, then TWRP Installer and then Magisk. When you flash LOS after TWRP and Magisk, your TWRP and root will be gone.

n2851991m said:
Same thing happened to me, I went from locked boot loader to unlock + lineage. When I tried to go back, the error kept popping up and the only thing that worked was fastboot.
Use MSM tool linked below and you should be good.
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
Note : IMPORTANT ! msm tool will also relock your bootloader, so you will lose any data you might have on your phone.
Click to expand...
Click to collapse
crap... my link is old.. may not work.. i'll try yours.... fingers crossed

csmooth2001 said:
Lineage will finally load... "about phone" says i'm in 17.1 guacamole doing this now my sim card won't read.... & i can't rotate screen (a problem i've had when the last lineage 16.? worked)
Click to expand...
Click to collapse
I can confirm the auto rotate issue with 17.1. In my situation, this was with a tmo 1915 variant. When I loaded OOS 9.5.13 and LOS 16, no mobile data but rotation. If I loaded OOS 10.3.1 firmware with LOS 17.1, had mobile data but no rotation. I even flashed the modem from OOS 10.3.1 into 9.5.13 that produced mobile data but no rotaion. No matter which firmware I tried which was many, I could never have both mobile data and rotation!! I wound up returning the tmo 1915 and ordered a 1917. .Have not received it yet. Maybe better luck with the international variant.
As a side note, luk1337, one of the los 17.1 maintainers for guac, is using the EU 1913 variant and confirmed that los 17.1 was not tested with the 1915 variant. So if you gots a tmo 1915, lots of luck. Searching around, they are supposed to be the same hardware but due to tmo locking tihs down, I dont know.
As for flashing, the thing to remember is that when you flash roms, you are flashing to the OTHER slot. When you are flashing mods, you are flashing to the CURRENT slot. Flashing roms and mods in recovery without changing the slot between will hose your install.
Official install method from maintainers:
1. Download the latest build
2.. Boot to recovery (the current slot. Could be A or B)
3. Flash the latest build
4. Boot to recovery again (now you are in the other slot)
5. Flash magisk
6. Reboot
Hope that helps.

razorshiv said:
I can confirm the auto rotate issue with 17.1. In my situation, this was with a tmo 1915 variant. When I loaded OOS 9.5.13 and LOS 16, no mobile data but rotation. If I loaded OOS 10.3.1 firmware with LOS 17.1, had mobile data but no rotation. I even flashed the modem from OOS 10.3.1 into 9.5.13 that produced mobile data but no rotaion. No matter which firmware I tried which was many, I could never have both mobile data and rotation!! I wound up returning the tmo 1915 and ordered a 1917. .Have not received it yet. Maybe better luck with the international variant.
As a side note, luk1337, one of the los 17.1 maintainers for guac, is using the EU 1913 variant and confirmed that los 17.1 was not tested with the 1915 variant. So if you gots a tmo 1915, lots of luck. Searching around, they are supposed to be the same hardware but due to tmo locking tihs down, I dont know.
As for flashing, the thing to remember is that when you flash roms, you are flashing to the OTHER slot. When you are flashing mods, you are flashing to the CURRENT slot. Flashing roms and mods in recovery without changing the slot between will hose your install.
Official install method from maintainers:
1. Download the latest build
2.. Boot to recovery (the current slot. Could be A or B)
3. Flash the latest build
4. Boot to recovery again (now you are in the other slot)
5. Flash magisk
6. Reboot
Hope that helps.
Click to expand...
Click to collapse
so if I boot to recovery in the current slot A
so if i flash a ROM, it will install to B ?
ok ok ok.. i was told that i have to flash a rom, then twrp.zip then magisk
but according to you (i think)
i flash a rom, reboot to recovery.. then flash twrp.zipo then magisk?
im guessing big time
is there a forum just for GM1915 ??? anywhere in the world...

csmooth2001 said:
so if I boot to recovery in the current slot A
so if i flash a ROM, it will install to B ?.
Click to expand...
Click to collapse
yes.
ok ok ok.. i was told that i have to flash a rom, then twrp.zip then magisk
but according to you (i think)
i flash a rom, reboot to recovery.. then flash twrp.zipo then magisk?
Click to expand...
Click to collapse
flash rom, flash twrp, reboot recovery, flash magisk.
is there a forum just for GM1915 ??? anywhere in the world..
Click to expand...
Click to collapse
They are scattered around the op7pro forum. Just do a search for tmo or tmobile.

boot to other slot & sim will work

Possibly bricked my poco f2 pro, is there a way to fix this?

Hi all.
Today I unlocked my phone to flash the crDroid rom. First I went into fastboot to flash mauro's twrp and that worked fine. Then I flashed the miui 12.0.3 full stock image from twrp, which might have been a mistake since I flashed the full image instead of an extracted vendor / firmware version. Then I wiped system, cache and data and flashed twrp but when I tried to boot the phone it went into an infinite boot screen. Then I wiped and flashed the whole stock miui image again in the hope that I would at least be able to boot miui but that also failed, since the phone kept booting back to recovery and there was no boot screen at all.
I have also tried flashing the stock image (ver 12.0.6) from fastboot but it fails because of the anti rollback check error. The image I tried to flash has an antirollback version of 0 while my phone has a version of 1, so "current device antirollback version is greater than this package" is what I got. Now my options are very limited because for some reason my laptop can't access the file system of the phone so I can't transfer files to the phone anymore and the ADB sideload feature from twrp is not working, so I only have fastboot (adb also won't recognize my device). What can I do to save my phone? Any help is greatly appreciated.

Flash the MIUI with MiFlash.

Had sort of the same issue...
Try using adbfastboot tool ( it's a java programme ) to swap recoveries.
I got the bootloop after installing the LOS recovery , installed twrp from adbfastboot tool and got it working.
Nice to have working recovery but since adb sideload is broken in twrp i needed LOS recovery.
Tried to reflash the LOS recovery from the tool and this time it worked

Flash with Miflash (the latest version https://xiaomiflashtool.com/ option CLEAN ALL) the rom that was on your phone when you bought it.
For the roms It is better to flash firmwares with Miflash because TWRP is not 100% functional.

grt67DFqyu said:
Flash the MIUI with MiFlash.
Click to expand...
Click to collapse
Man I can't believe such a simple suggestion would work but it did thanks! Initially I did not flash with miflash because it prompted me to install drivers and it crashed when I clicked the install button, turns out all I had to do was create a folder named log in the miflash directory lol. So flashing the stock image works. And it definitely boots correctly to miui with the clean all and lock option.
But now when I try to flash crdroid or pixel experience I still end up with an infinite boot screen even when using exactly the specified firmware :/ Like you see crdroid and pixelexp boot animations correctly but it lasts forever. I must be doing something wrong with the firmware still because that's the only reason I can think of why it won't boot. After I flash the firmware in miflash I don't have to boot miui up first right? I'm using the 'save user data' option in miflash if that matters.

In my post, I specified CLEANALL, but anyway, you must format data before flashing.
Which rom do you want to install Cdroid or Pixel?

NOSS8 said:
In my post, I specified CLEANALL, but anyway, you must format data before flashing.
Which rom do you want to install Cdroid or Pixel?
Click to expand...
Click to collapse
I'm now trying to flash crdroid. After flashing V12.0.3.0.QJKMIXM in miflash with flash_all, I formatted data in twrp (the one where you have to type yes) but also with a decrypt & normal factory reset I still get the same result. After the format, I flashed crdroid without magisk and gapps, and it'll just hang on the crdroid boot screen :/. The weird thing is, before I flash the crdroid rom it can boot in MIUI just fine and it'll show that it's indeed the correct 12.0.3.0 in the settings so I have no idea if it's just the crdroid ROM at this point.

Flash with miflash V12.0.3.0.QJKMIXM reboot system and go fasboot when affiche "devices is locked",flash chinesse twrp ,reboot twrp,format data reboot twrp,wipe all ecxept OTG reboot twrp,flash Cdroid format data,reboot twrp flash gapps,reboot system( take time ).

NOSS8 said:
Flash with miflash V12.0.3.0.QJKMIXM reboot system and go fasboot when affiche "devices is locked",flash chinesse twrp ,reboot twrp,format data reboot twrp,wipe all ecxept OTG reboot twrp,flash Cdroid format data,reboot twrp flash gapps,reboot system( take time ).
Click to expand...
Click to collapse
This ended up working perfectly Crdroid is now running like a charm with gapps and magisk. Thank you guys a lot for helping me out with this!

TWRP can't decrypt + Fastboot loop

Unsure if this is the place since its also related to TWRP 3.7, any help is appreicated
Got stuck in a weird situation and wondering if anyone has ideas.
Current State:
Slot_A on OOS 11, can boot TWRP via Fastboot
Slot_B on OOS 12, can only boot into Fastboot
Originally on OOS 11, booted TWRP and made backups of all partitions (data, boot, system image, vendor image, etc.). Forgot to move this to computer so this is all still stored on device.
Proceeded with OOS 12 upgrade (into Slot B). Patched magisk, rebooted, then flashed TWRP 3.7 (FBEv1), direct installed magisk, rebooted. - Everything was functional, but decided to go back to OOS 11.
Thinking I could just use the TWRP backup made on OOS 11, I did the following:
Booted into 3.7 TWRP
Restored the backup for boot, system image, and vendor image
Set active slot to Slot A and reboot
It doesn't allow me to boot into the OS (Presumably because the data was re-encrypted for OOS 12?)
Set active-slot=b and reboot, but it's locked to fastboot.
I've attempted a few things, but I can't boot back into OOS. I would prefer to retrieve my TWRP backups first before doing an MSM reset.
When on Slot_A (older), I can only boot into TWRP 3.6.2 and 3.7. I'm guessing 3.6.2 can't decrypt since it's only configured for A11 and under, but not sure why 3.7 can't decrypt my data.
- It doesn't even ask for pin when TWRP launches; maybe it's reading the System for Slot_A and thinks i'm still on A11?
- running `twrp decrypt {pin}` doesn't seem to work. Unsure if there's something done to my lockscreen pin to be used as the encryption key/password?
When on Slot_A, attempting to boot into either the system or TWRP hangs.
Things I've tried:
Flashing A11 boot.img and magisk-patched boot.img to Slot_A -> Hangs on 1+ Spinning dots
Flashing A12 boot.img and magisk-patched boot.img to Slot_B -> Hangs on 1+ logo (Does show up on ADB though)
Booting Slot_B into TWRP 3.6.2 (Official, and Nebrassy unofficial for A12) and TWRP 3.7 -> Gets stuck on "Fastboot Mode" screen (fastboot cli still responds) or Hangs on snapdragon logo
Edit: Ended up using MSM. Needed device for work

I have a similiar problem to flash twrp to my phone ,
each time i try i get a fastboot loop too and i have to reset/unbrick it with the msm tool back to android 11
i use the OnePlus_7_Pro_Global_OxygenOS_11.0.5.1 package to unbrick the phone , i dont know how long and often i tried now to get twrp to work so that i can flash a custom fw ... i want root and a android 13 based cfw but i dont get it to work :/

I got it working with crdroid. heres some stuff
guacamole - Google Drive
drive.google.com
be carefull
¯\_(ツ)_/¯​
------------------------------------
I got stable and decrypted fs RW working on crdroid 9.1 firmware other than some weird bugs
i put it in the 2023-twrp

MissAnthropin said:
I have a similiar problem to flash twrp to my phone ,
each time i try i get a fastboot loop too and i have to reset/unbrick it with the msm tool back to android 11
i use the OnePlus_7_Pro_Global_OxygenOS_11.0.5.1 package to unbrick the phone , i dont know how long and often i tried now to get twrp to work so that i can flash a custom fw ... i want root and a android 13 based cfw but i dont get it to work :/
Click to expand...
Click to collapse
I have the exact same problem! Have you found a fix yet? This seems to happen when I try to install Android 13 based roms, and when I install a rom like Lineage OS, using their recovery, it works just fine.

No, and I don't know why, maybe i do something wrong or it is the Modell that make this trouble.
I thinking to sell my OP7PRO and buy another one ( and then I have the same problem with the new phone )
No no let the jokes aside, it must work, i mailed with OnePlus Support Germany but they only helped me to install A11 w/root and recovery, i thought ok now I can update to A13 so I loaded A13, unpacked the boot.img, Patched the boot.img
Installed A13 w/out errors, rebooted - Fastboot loop

RIP
Started ranting instead

TWRP for guacamole development seems to be fairly scarce, last working recovery I tried was when they started using fastboot boot to enter it. It was pretty hacky even then, currently it seems that nebrassy is the maintainer for twrp for guacamole.
Github: https://github.com/nebrassy Android 12 thread: https://forum.xda-developers.com/t/recovery-12-official-teamwin-recovery-project.4269551/ Nebrassys Telegram has helpful info as well: https://t.me/NSSFB
last update I found was 2022:10:2 - https://www.pling.com/s/Phones/p/1835156
after a few days of torture I read a thread on here saying if you flashed twrp via magisk like you would if it was a magisk moule it would work normally. It worked on my device so I assume that its universal. I have filled my computer with guacamole related files Im uploading here before im forced to reinstall my os:
guacamole - Google Drive
drive.google.com
Just a fyi from what I have gathered from my experience you can get a stable twrp recovery with persistant / read write access and disabled encryption and basically use it with little error up until you try flashing a newer custom rom. My guess is when flashing a cfw the bootloader gets rewritten causing our boot image to become corrupted. Flashing twrp over / booting to twrp via fastboot or trying to install it via another custom recovery causes boot / recovery failures... meaning you cant really use it for flashing custom roms. I cant find the post with the install instructions I seen that helped me so here is what I think it was,
Found it: https://forum.xda-developers.com/t/how-to-make-twrp-work-in-your-stock-a12.4522667/#post-87985325
~ I have bricked this device constantly while ****ing around so unless youre prepared to go to war with the ****er, Id quit messing with it.
MSM flashing with windows is the only way to recover from the void.
Click to expand...
Click to collapse
using Linux systems for EDL is a bit more difficult to figure out but can be done > EDL https://github.com/bkerler/edl/blob/master/edl | https://github.com/andersson/qdl
Click to expand...
Click to collapse
~If you do brick I created a fastboot flashable A13 Oxygen os recovery rom and uploaded it to my google drive found under recovery_brick_fastboot.zip ~
Click to expand...
Click to collapse
lastly be mindful of a/b partition configuration or youll find yourself lost or bricked
Installation:
1. Obviously unlock the bootloader - OEM Unlock
2. Flash custom recovery (lineage/crdroid/etc)
3. (Personally I root here and again on the active slot so) flash magisk.zip
4. Reboot into installed ROM and install magisk android app and complete setup, reboot system
5. (another thing I like to do before flashing twrp) setup magisk enable all the basic options like prophide, deny list then set root userspace option to global.
6. Flash TWRP .zip (https://dl.twrp.me/guacamolev2/twrp-installer-3.7.0_12-0-guacamolev2.zip) via magisk
Alright! After all that you should be able to reboot into recovery via adb reboot recovery / fastboot or power menu and you find a working twrp recovery installed.
If you need help or want to **** around with the device you can @ me anytime and ill do my best to halp
2600 IRC (cornelius.scuttled.net >Nick captain >channel #guac)
Telegram https://t.me/+pxvpKToFo6pkMGYx
Discord https://discord.gg/MhvWgEfY

Pics

RolandStoner said:
Pics
Click to expand...
Click to collapse
You Confussing me a lot with your Posts before ...
i´m unsure what you mean exactly,
my bootloader is unlocked, with magisk i got a working root but after that i fail
what you mean with flash twrp with magisk ?
after unlocking the bootloader and get root, i tryd to flash twrp like before on other devices but that seems not working because i get then the fastboot loop
on another thread i found here on xda too, the guy wrote dont forget to activate the fastboot loop fix in the advanced options
but i not tried it yet again , so what should i do now ?
for now , i´m back on android11 , with stock oxygen os firmware
i have to do now the things like i did before again , unpack boot.img from the firmware that is installed on the device
patch it with magisk, flash it with "fastboot flash boot boot-patched.img" or is this step senseless ?
i mean you only wrote unlock bootloader and flash a cfw , but i don´t have a chance to flash a custom fw without a custom recovery ??
my recovery on my op7pro have no options for "install zip" or something else
addendum:
like i said you confused me a lot
addendum two:
or i do what i said before .. i sell my op7pro and buy me a one where i havent so much trouble installing twrp and root
i never had a phone before that made so much trouble in installing simple twrp ...
but i don´t found a phone yet that is compatible with kali and the pentest tools or wardriving tools like the oneplus , so i have a problem ,... i think i should drink now my selfmade blackberry liquor ( or blackberry booze ? ) and let the smartphone be a smartphone for now and power off my brain for a while

Yes, you need to patch your boot image via magisk and flash it with fastboot.
After you let magisk do its first time setup and then once it reboots you go to Magisk > Modules and flash the twrp recovery .zip file you got from twrp. link:https://twrp.me/oneplus/oneplus7pro.html just like you would if it was a magisk module.

the password for twrp decryption is your pin. Here are simpler instructions
https://forum.xda-developers.com/t/how-to-make-twrp-work-in-your-stock-a12.4522667/#post-87985325

****... I forgot a step.
after flashing twrp as a module in magisk you dont reboot, you go back to the main screen hit the install button and choose direct install

Now I understand it more, i had before rooted the phone successful with magisk, but then I made a wrong decision and booted into Fastboot and flashed TWRP in Fastboot Mode as I did it before with all my Smarties i had before, coz those way with Fastboot worked before all the time so I never thought that this is the error in the procedure
I give the twrp flashing with magisk a try.
Thx for the help

MissAnthropin said:
Now I understand it more, i had before rooted the phone successful with magisk, but then I made a wrong decision and booted into Fastboot and flashed TWRP in Fastboot Mode as I did it before with all my Smarties i had before, coz those way with Fastboot worked before all the time so I never thought that this is the error in the procedure
I give the twrp flashing with magisk a try.
Thx for the help
Click to expand...
Click to collapse
Thank @yassine2217 because I would never have done so either.... Still many bugs but twrp is twrp