Related
Hi!
I have a poco f2 pro that was on the xiaomi.eu MIUI weekly.
Yesterday I installed a module for Magisk and got into a bootloop. From now everything's fine I usually know how to deal with this kind of stuff.
The mistake I did, is when I tried to boot into a new TWRP after flashing.
I did
Code:
fastboot flash boot ./twrp_xxx.img
instead of
Code:
fastboot flash recovery ./twrp_xxx.img
I tried many times flashing different boot.img without success, I didn't managed to install "magisk manager for recovery" so I did a clean flash of the rom, and then I even tried downloading the stock global from from https://xiaomifirmwareupdater.com/ and did a "flashall" without success (the phone boots on bootloader/recovery).
Fortunately I havent yet locked the bootloader so I can still flash everything.
Can someone help me figure out why my phone is doing this even after flashing everything please?
Did you try with Miflash?
try with MiFlash. Flash stock rom in fastboot mode
Hi! Thak you for the quick answer
I don't know why but I believed that the only thing miflash do is to execute the scripts from the folder.... I'll try this now
Thelm76 said:
Hi! Thak you for the quick answer
I don't know why but I believed that the only thing miflash do is to execute the scripts from the folder.... I'll try this now
Click to expand...
Click to collapse
Before MiFlash try delete the Magisk module causing the bootloop, use TWRP File Manager. Magisk modules are located in /data/adb/modules
dhaern said:
Before MiFlash try delete the Magisk module causing the bootloop, use TWRP File Manager. Magisk modules are located in /data/adb/modules
Click to expand...
Click to collapse
Well that the thing I tried when I accidentally replaced my boot partition... And my phone was only booting on twrp or fastboot... also the weird thing I found is that /data/adb didn't exist
But many thanks to you all it works now.
I'll maybe try to make a guide on how to install Magisk on the Xiaomi EU weekly rom, as android 11 is only supported by the canary build. (if I manage to find a way to properly remove defective modules in TWRP :fingers-crossed
Boot twrp via Fastboot. Download Rom, Install ROM (xiaomi.eu). This should fix ist already. Then you could test a bit, and eventually need to wipe data
Tecardo said:
Boot twrp via Fastboot. Download Rom, Install ROM (xiaomi.eu). This should fix ist already. Then you could test a bit, and eventually need to wipe data
Click to expand...
Click to collapse
That was the first thing I tried, but only miflash managed to bring my phone back to life , as current twrp doesn't like encrypted data partition (I don't know why but it won't mount /data and it says wrong password)
I think that's why I couldn't remove the defective module
If you want everything to work you need to format data!!
Thats the point why using android 11 roms is hard, twrp cant decrypt it (until you flash rom with a10 and then a11 because partition is encrypted in a10 style)
Thelm76 said:
That was the first thing I tried, but only miflash managed to bring my phone back to life , as current twrp doesn't like encrypted data partition (I don't know why but it won't mount /data and it says wrong password)
I think that's why I couldn't remove the defective module
Click to expand...
Click to collapse
That's easy to fix, you installed Android 11 or? Don't use pin, use gesture. Twrp can't decrypt android 11 pin right now
Thelm76 said:
Hi!
I have a poco f2 pro that was on the xiaomi.eu MIUI weekly.
Yesterday I installed a module for Magisk and got into a bootloop. From now everything's fine I usually know how to deal with this kind of stuff.
The mistake I did, is when I tried to boot into a new TWRP after flashing.
I did
Code:
fastboot flash boot ./twrp_xxx.img
instead of
Code:
fastboot flash recovery ./twrp_xxx.img
I tried many times flashing different boot.img without success, I didn't managed to install "magisk manager for recovery" so I did a clean flash of the rom, and then I even tried downloading the stock global from from https://xiaomifirmwareupdater.com/ and did a "flashall" without success (the phone boots on bootloader/recovery).
Fortunately I havent yet locked the bootloader so I can still flash everything.
Can someone help me figure out why my phone is doing this even after flashing everything please?
Click to expand...
Click to collapse
NO flash only fastboot boot twrp.img
Hello everyone! Thanks in advance for taking a look at this thread.
I recently upgraded from a Pixel 2 to a Pixel 5 and decide to root my old phone and mess around with that before doing the same with my new phone. It's been several years since I've messed around with rooting a device, so I've spent some time this week refreshing myself on how to do so.
I've already unlocked my bootloader, but the main issue that I'm running into is when I try to install TWRP or Magisk. For some reason, when I try to flash TWRP (version 3.3.0.0), I've managed to install it properly but loading into recovery mode just leaves me stuck at the TWRP splash screen, while booting directly into it doesn't allow me to backup my data (kicking out an error 255 each time). It would be nice to have TWRP to be able to back up rather than starting from scratch each time, even if I've gotten quick at flashing the stock image when I screw up later.
As for Magisk, I've tried flashing the patched boot image through TWRP and received errors (size of image is larger than target device) as well as the .zip file which just caused a bootloop. I know you can install Magisk without TWRP, so I've tried doing that as well. I've been working with both Magisk 23.0 and the Canary build with no luck; after patching the boot image and attempting to flash it using fastboot flash boot magisk_patched.img, I just repeatedly get an error showing "FAILED (remote: 'Error flashing partition')".
So far I've not really been able to find any solutions on how to fix this, so I feel a bit stuck at this point (and definitely questioning my ability to just follow directions). Any advice on how I might get around these errors?
Hello mate,
With regards to installing twrp, I think there is a workaround in the official twrp thread to get twrp installed with working decryption and working pin by rolling back to a pie build prior to encryption being broken for twrp. Personally I just fastboot it when needed to flash anything but sadly twrp back ups don't work (I'm on A11).
It sounds as if you have tried to install magisk a few ways but I found the simplest way was to install the latest magisk.apk then rename it to magisk.zip and flash it via fasbooted twrp.
It sounds as if you tried patching the image etc so may pay to reflash the stock boot.img and then do the APK/zip method to get magisk running.
Lastly, if you don't mind losing your data it may well pay to reflash a full stock.img and then try magisk again. It's solved a few dramas for me when stuff didn't seem to work first time round.
Hello, I had my OP7P rooted on android 11, but after updating to 11.0.6.1.GM21AA, I just couldn't get root to work.
I downloaded the OxygenOS 11.0.6.1.GM21AA from oneplus.com, extracted the boot.img, downloaded the new (supposedly with Android 11 support) TWRP (twrp-3.6.0_11-0-guacamole.img), booted to the TWRP, and installed root using the magisk APK, when I booted the phone had "Android Intellegnce stopped working" all sort of apps stopped working as well and some also crashed when I tried to open them, I flashed the original boot image and after some research I saw that using Magisk Canary build might help, so I tried with it too and same result.
I tried installing root using Magisk.apk, I tried patching a boot image using Magisk (both versions) but to no avail.
Some notes:
-Using the Canary build actually rooted my phone unlike the normal Magisk, but with problems still.
-When trying to use TWRP's "Flash Current TWRP" option, it overwrite my boot image and when trying to boot to fastboot or system it booted to recovery instead.
I will be glad for any help because having an unrooted device sucks.
Thanks in advance and sorry for any grammar mistakes (English is not my first language)
May be the first thing I'd think of trying it to disable any/all Magisk module installed.
Then, with the full OTA ROM stored in the main storage directory of your device... Basically a dirty Flash using the same OOS version you are using now and that should save the wipe/reset...
OTA Flash that and do not reboot and in Magisk manager check to see if manager is able to install Magisk as in install after OTA (?). That should work and then reboot device then verify. Don't forget to re-enable and Magisk modules...
Hope that can and will point you into the right direction.
I've not bothered with TWRP since I installed it then the next OTA went back to stock recovery. So, might be worth skipping TWRP for root as is not required so far as I can tell ... But I also have a Windows computer set up to flash via adb command alternatively.
Edit:. Think I forgot to say that the OTA update changed my TWRP back to stock recovery... But that's easy enough it change if desired
wugga3 said:
May be the first thing I'd think of trying it to disable any/all Magisk module installed.
Then, with the full OTA ROM stored in the main storage directory of your device... Basically a dirty Flash using the same OOS version you are using now and that should save the wipe/reset...
OTA Flash that and do not reboot and in Magisk manager check to see if manager is able to install Magisk as in install after OTA (?). That should work and then reboot device then verify. Don't forget to re-enable and Magisk modules...
Hope that can and will point you into the right direction.
I've not bothered with TWRP since I installed it then the next OTA went back to stock recovery. So, might be worth skipping TWRP for root as is not required so far as I can tell ... But I also have a Windows computer set up to flash via adb command alternatively.
Edit:. Think I forgot to say that the OTA update changed my TWRP back to stock recovery... But that's easy enough it change if desired
Click to expand...
Click to collapse
Hello, thanks for the reply, I wanna get a few things straight before doing anything that have the potential to brick my phone.
1. My phone rn isn't rooted, so I cant uninstall or disable Magisk modules, I CAN root my device but it is very unstable and im not sure doing it is a good idea, maybe there's another way to disable them?
2. What do you mean by dirty flash? Using the device update section and selecting the official OOS version I downloaded from OnePlus.com?
1) may be forget about root for now as that's probably not the priority at this time. Getting a stable operating system is the priority. And skip TWRP (don't see the point of if being needed at this step either).
2) my best guess is that I've used oxygen updater from the play store to download the full update (not incremental update) that exactly matches the one you have installed now - or search here and find the match to download or used the OnePlus cite to get the file. Then once that is downloaded to your device - go to settings/system/system updates/local update and install and reboot. That's the dirty Flash as in don't wipe/reset your device either before/after the installation. I'm hoping that this method will clean up both the recovery and boot images to stock and hopefully restore stability to your device without the wipe/reset.
Hope that helps and restore the device stability without TWRP nor root.
Hi wugga3, thanks again for your time, unfortunately a stable device is not my problem, I have managed to make a stable boot image by downloading the OOS version from the Oneplus website and flashing the boot image after attempting to root my device unsuccessfully.
My problem right now is that my device isn't rooted and I can't manage to root it using the methods I mentioned above, I currently have an unrooted stable OOS version 11.0.6.1.GM21AA.
NitayMa'ah said:
Hi wugga3, thanks again for your time, unfortunately a stable device is not my problem, I have managed to make a stable boot image by downloading the OOS version from the Oneplus website and flashing the boot image after attempting to root my device unsuccessfully.
My problem right now is that my device isn't rooted and I can't manage to root it using the methods I mentioned above, I currently have an unrooted stable OOS version 11.0.6.1.GM21AA.
Click to expand...
Click to collapse
How about installing just the magisk APK then taking the exctracted boot.img patching it in magisk APK, then disabling all security , take the patched boot.img and flash it in fast boot ( fastboot flash boot boot.img) reboot to system .
hammered58 said:
How about installing just the magisk APK then taking the exctracted boot.img patching it in magisk APK, then disabling all security , take the patched boot.img and flash it in fast boot ( fastboot flash boot boot.img) reboot to system .
Click to expand...
Click to collapse
Ill try it now thank you
NitayMa'ah said:
Hello, I had my OP7P rooted on android 11, but after updating to 11.0.6.1.GM21AA, I just couldn't get root to work.
I downloaded the OxygenOS 11.0.6.1.GM21AA from oneplus.com, extracted the boot.img, downloaded the new (supposedly with Android 11 support) TWRP (twrp-3.6.0_11-0-guacamole.img), booted to the TWRP, and installed root using the magisk APK, when I booted the phone had "Android Intellegnce stopped working" all sort of apps stopped working as well and some also crashed when I tried to open them, I flashed the original boot image and after some research I saw that using Magisk Canary build might help, so I tried with it too and same result.
I tried installing root using Magisk.apk, I tried patching a boot image using Magisk (both versions) but to no avail.
Some notes:
-Using the Canary build actually rooted my phone unlike the normal Magisk, but with problems still.
-When trying to use TWRP's "Flash Current TWRP" option, it overwrite my boot image and when trying to boot to fastboot or system it booted to recovery instead.
I will be glad for any help because having an unrooted device sucks.
Thanks in advance and sorry for any grammar mistakes (English is not my first language)
Click to expand...
Click to collapse
Here's a image file you can flash in fastboot. It's
NitayMa'ah said:
Hello, I had my OP7P rooted on android 11, but after updating to 11.0.6.1.GM21AA, I just couldn't get root to work.
I downloaded the OxygenOS 11.0.6.1.GM21AA from oneplus.com, extracted the boot.img, downloaded the new (supposedly with Android 11 support) TWRP (twrp-3.6.0_11-0-guacamole.img), booted to the TWRP, and installed root using the magisk APK, when I booted the phone had "Android Intellegnce stopped working" all sort of apps stopped working as well and some also crashed when I tried to open them, I flashed the original boot image and after some research I saw that using Magisk Canary build might help, so I tried with it too and same result.
I tried installing root using Magisk.apk, I tried patching a boot image using Magisk (both versions) but to no avail.
Some notes:
-Using the Canary build actually rooted my phone unlike the normal Magisk, but with problems still.
-When trying to use TWRP's "Flash Current TWRP" option, it overwrite my boot image and when trying to boot to fastboot or system it booted to recovery instead.
I will be glad for any help because having an unrooted device sucks.
Thanks in advance and sorry for any grammar mistakes (English is not my first language)
Click to expand...
Click to collapse
Here's an Orangefox prerooted OxygenOS 11 boot.img that works on 11 and 12. Just boot to fastboot, connect to a PC open a command prompt in the same directory and type..
fastboot flash boot boot-v9-root24.img...
Also it's easier to just flash both slots by this commands..
Fastboot flash boot_a boot-v9-root24.img and then fastboot flash boot_b boot-v9-root24.img...
I dual boot with this version of twrp and here's a solid boot img. You can flash it also in recovery or with "partition manager off play store. Check it out.
Fixed!
Thanks so much for the suggestions, which I might didn't fully consider in a rush...
The solution was to root my phone, reboot it all shaky and try to disable all Magisk modules (took me 2 tries because of the crashes and stuff), then flash again the original boot image, rebooting, creating a rooted boot.img using Magisk and flashing it.
Littlemether said:
Here's a image file you can flash in fastboot. It's
Here's an Orangefox prerooted OxygenOS 11 boot.img that works on 11 and 12. Just boot to fastboot, connect to a PC open a command prompt in the same directory and type..
fastboot flash boot boot-v9-root24.img...
Also it's easier to just flash both slots by this commands..
Fastboot flash boot_a boot-v9-root24.img and then fastboot flash boot_b boot-v9-root24.img...
I dual boot with this version of twrp and here's a solid boot img. You can flash it also in recovery or with "partition manager off play store. Check it out.
Click to expand...
Click to collapse
First of all thanks for the help but I ended up fixing it in another way.
Second of all, not really related but do you know if I can use this recovery on OP7Pro A12 custom Rom? (and flash it)
Hello everyone sorry i'm new here and also i don't know much about rooting my device Poco X 3 pro MIUI 13.0.3 Global and Andriod 12 .. sadly i messed up i had my boatloader unlocked fo my Poco x3 pro and i have installed custom recovery TWRP then i tried to install Magisk via the TWRP recovery but it won't work mainly because the data is encrypted and the TWRP can't acess in the internal storage so i used a OTG usb but gets error unable to mount /data/media/fox/.fox note that i tried both Orangefox and twrp still same error i assume its because the device is encrypted . also decrypt doesnt work it ask for password and i even removed all my accounts and disabled all lock screen but still not working at this point i thought that downgrading from MIUI 13 to 12 will fix this since i saw all videos who had it working used MIUI 12 and here where i messed up i used XiaoMiTool V2 then clicked custom ROM and used an offecial ROM from Xiaomi website ( miui_VAYUGlobal_V12.0.6.0.RJUMIXM_eccd7da42b_11.0.zip ) the phone booted into TWRP and started installing but ofcourse got the error first unable to mount /data/media/twrp then the process continued installing all the files then phone rebooted into TWRP LOOP now im stuck into TWRP and the USB debugging is turned off now as the phone appearntly did factory reset so i cant acess XiaoMiTool V2 again and when i try to wipe data from TWRP it says unable to wipe data ... please help im stuck on TWRP loop now
**UPDATE** i tried fastboot ROM using MiFlash tool but i get error since i'm stuck on twrp fastboot menue but after few restart it finally open the normal fastboot menue with the logo of the sitting rabbit which indecade this is miui 12 tried again to fash though Mifash tool and it worked (flashing the same version miui_VAYUGlobal_V12.0.6.0.RJUMIXM_eccd7da42b_11.0.zip but this time the fastboot version not the recovery one took few minutes then got error not catch checkpoint flash is not done then it reboot into the phone menue where i can click wipe data i click that and the phone (thankfully) opened into MIUI 12 LOGO screen
... theres an easier way to actually downgrade your MIUI using a trick through your phone only without root or pc or anything by changing the ROM file name before you click reboot wish i used that since its safer and official
omg finally Magisk installed successfully now didnt need to decrypt anything
now my last question is do i need custom ROM after rooting the device ? or does magisk mean its a custom root ? sorry first time rooting and i dont know if i need to install any apps or apply any setting or should i click update my MIUI now ?
Try the newest Unofficial TWRP from nebrassy (found in his thread here on XDA)
That supports decription.
I recommend arrowOS as custom ROM.
It's one of the oldest and works pretty well.
IMHO Stock ROM from Xiaomi is untrustworthy. Who knows what spyware they included.
Same for me now I have a question first I need a guide link how to install arrowOS or any better ROM also if I do that do I need to flash Magisk again or the device will be keep the Root ?
@Haldi4803 can you post the link of the TWRP as well ? There's many threads by nebrassy and they all seem old mine is the latest official and it doesn't work on miui 13 , I also heard of crdroid and derpfest ROMs for Poco x3 pro but I think they overheat much ? I didn't test so I'm just asking also what's the way to install a new ROM it seem little bit complicated but the ArrowOs thread doesn't explain all the steps in detail because I think it's for pro users I read on Google that there's way more steps to install a ROM
TWRP:
[RECOVERY] [12] [OFFICIAL] TeamWin Recovery Project
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com
Unofficial Builds from pling with Decryption working:
https://www.pling.com/p/1833617/ (just take the newer one)
Installation guide for Arrow OS:
Instructions
FIRST INSTALL?:
Remove any fingerprint, PIN, or password in MIUI
Unlock the bootloader
Transfer ROM to internal storage
Install any suitable recovery
Flash ROM zip file
Do a data wipe in recovery (format data)
Reboot to the system, wait and enjoy
There are decent picture guides here on xda on how to unlock bootloader.
After bootloader is unlocked you can simply install TWRP via fastboot flash recovery recovery.img.
Detailed instructions here: https://twrp.me/xiaomi/xiaomipocox3pro.html
After you have installed a ROM. and gapps you can simply reboot and use the rom.
Whenever you need root you can reboot into recovery and install magisk.
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