Related
I am aware that you cannot use TWRP with any factory based ROMs past 9 but can I flash an AOSP 10 based rom with TWRP?
Joe333x said:
I am aware that you cannot use TWRP with any factory based ROMs past 9 but can I flash an AOSP 10 based rom with TWRP?
Click to expand...
Click to collapse
You can't flash TWRP on the Pixel 3a (overwriting the "recovery" partition...which isn't even a real separate partition on Pixel's AFAIK). BUT you can still boot TWRP, I think it's officially called "OTG".
Here's how I have successfully ran TWRP on my Pixel3a with Android 9:
Code:
$ fastboot boot twrp-3.3.1-1-sargo.img
Next I tried to install a ZIP file (Magisk-v20.1.zip) once inside TWRP...and that didn't work. In fact it failed miserably, I got into a bootloop and had to recover. I'm assuming that's what you were asking using the "Install" functionality of TWRP? So to answer your question in a long and detailed way YMMV!
TWRP with Android 9 works. 10 and later will not work unless TWRP team rewrites a bunch of code. The link below is the nitty gritty of why. It has nothing to do with a "recovery partition." Since Android 7, a lot of devices have recovery in the ramdisk of the boot partition. The issue with TWRP on Android 10 up is how partition linking is done in the ramdisk now. (See link below)
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
Update: Reinstalled the ROM without TWRP and Magisk and it is working fine.
How should I approach the desire to root then?
Hi,
short story:
unlocked my Xiaoxin Pad Pro running Android 11 ZUI 12.6.X. Worked fine afterwards.
Installed TWRP 3.4.2. from here https://unofficialtwrp.com/twrp-3-4-2-root-lenovo-tb-j706f/?amp
and followed the guide.
"fastboot format userdata" didnt work though and I found no solution, so I skipped it.
Error was mke2fs failed, Cannot generate image for userdata.
Nandroid backup didnt work either:
"Cannot create /data/media/0/twrp' folder (required key not available).
Failed to make backup folder."
Also, there was no system partition when I tried to back it up, only "super".
Solved the backup not possible problem by formating data in TWRP and trying it again.
Installed Magisk with adb sideload and booted..... into a fastboot brick.
Couldnt be solved by factory reset in TWRP and couldnt install new Global ROM .zips from here:
https://mirrors.lolinet.com/firmware/lenovo/Tab_P11_Pro/TB-J706F/
It said the files were corrupted.
Changed to Slot B in TWRP and the system booted normally.
Then I wanted to flash a Global ROM with QFIL.
It worked, but once the system booted up it told me "The current system is not compatible with the hardware. The device will power off automatically. It can work normally after flashing back to the factory version system"
In another XDA thread it was said, it is a kind of blocking thing in ZUI 12.6 (and maybe earlier) to prevent installing a Global ROM (on a chinese device). Tried to install the chinese version from the website then,
didnt work either.
Tried the older versions, all tested Android 10 versions are working, no A11 version is working though.
So question 1 is: "How can I change to A11 with root on Global ROM?"
Installed the newest one (the A11 ones arent working) as well as TWRP and Magisk
and it "worked".
But now the display isnt reaction in many cases. Have to click something like 5-10 times or I swipe up,
the screen goes up but when I lift my finger it goes down again instead of e.g. unlocking the screen.
Update 2: I can install OTA updates even with unlocked bootloader and Android 11 isnt available in my region (yet?), so maybe that's the reason the A11 versions didnt work for me.
The ZUI design was way better thouhj
Thxx
Spend the whole day looking through websites such as Magisk and TWRP as well as bunch of YouTube videos. I have unlocked the bootloader via DC Unlocker (Paid $4.50). For the most part, I have Magisk Manager installed but have no idea how to get Magisk itself installed via a boot image from their website.
Specs on Magisk shows Ramdisk: Yes, A/B: No, SAR: No.
Skipping that part, I did try a few of the img files on TWRP for Huawei Honor 8. Used the Minimal ADB and Fastboot steps. On the last step to "adb reboot recovery", it gets stuck on the loading screen and never reaches the TWRP screen. Any idea?
My end goal is to only use this phone for spoofing on Pokemon Go. That's all.
If your on Android 7, you should use this twrp:
[TWRP][H8][3.1.1-1][EMUI 5.x / AOSP N][DECRYPTION SUPPORT]
This is only for Honor 8 (FRD) OpenKirin presents unofficial TWRP for stock EMUI 5.x with decryption support. Intended for usage on stock emui 5.x in combination with unlocked bootloader and modded boot image with disabled dm-verity (depending...
forum.xda-developers.com
If your on android 8, you should use this twrp:
[Recovery][BKL][EMUI 8.x only][Unofficial]TWRP 3.2.1-0 [14/04/2018]
Disclaimer This software comes wth no warranty,XDA staff ,myself or TeamWin stuff can't be hold responsible for any damage it may cause to your device. Note: Currently Oreo 8.1 custom roms are supported only on BKL-L04 with EMUI 8.1 Download...
forum.xda-developers.com
Even though it is for Honor View 10, it works for Honor 8 on android 8
CHECK_123 said:
If your on Android 7, you should use this twrp:
[TWRP][H8][3.1.1-1][EMUI 5.x / AOSP N][DECRYPTION SUPPORT]
This is only for Honor 8 (FRD) OpenKirin presents unofficial TWRP for stock EMUI 5.x with decryption support. Intended for usage on stock emui 5.x in combination with unlocked bootloader and modded boot image with disabled dm-verity (depending...
forum.xda-developers.com
If your on android 8, you should use this twrp:
[Recovery][BKL][EMUI 8.x only][Unofficial]TWRP 3.2.1-0 [14/04/2018]
Disclaimer This software comes wth no warranty,XDA staff ,myself or TeamWin stuff can't be hold responsible for any damage it may cause to your device. Note: Currently Oreo 8.1 custom roms are supported only on BKL-L04 with EMUI 8.1 Download...
forum.xda-developers.com
Even though it is for Honor View 10, it works for Honor 8 on android 8
Click to expand...
Click to collapse
Thank you for the reply. I actually did stumble on the Android 7 link that you just posted. Though it's a complete mess now. After many more hours of trying to follow up guides, I did get TWRP recovery to work and to get there I always have to use the command on ADB. Following another guide I did get SuperSU to install. Then the bad news was Pokemon Go doesn't work with SuperSU and only Magisk. Though I haven't been able to get Magisk to work prior to trying SuperSU.
Then I tried Magisk-v23.0.zip again and I got the TWRP 1 Error. Probably the only way to fix it would be to unroot SuperSU and then try Magisk again. Not sure what I did next but phone keeps automatically booting into TWRP recovery (unable to boot to regular ROM, I did not backup or know how to backup).
Looking through the ROM forums with no experience, I assumed I just need to flash any of the ROMs for Honor 8 and then restart and see if I can get Magisk to work. Unfortunately, I tried a few such as: ResurrectionRemix-M-v5.7.4-20170106-frd, aicp_frd_n-12.1-UNOFFICIAL-20170704 but none were flashing correctly (I think something about MD5).
Unfortunately, now when I boot up phone (see the "Your device has been unlocked and can't be trusted" screen), then it stays pitch black. Usually it would start up the phone afterwards or in the recent case was directly to TWRP recovery. I sort of gave up for now.
etsai3 said:
Thank you for the reply. I actually did stumble on the Android 7 link that you just posted. Though it's a complete mess now. After many more hours of trying to follow up guides, I did get TWRP recovery to work and to get there I always have to use the command on ADB. Following another guide I did get SuperSU to install. Then the bad news was Pokemon Go doesn't work with SuperSU and only Magisk. Though I haven't been able to get Magisk to work prior to trying SuperSU.
Then I tried Magisk-v23.0.zip again and I got the TWRP 1 Error. Probably the only way to fix it would be to unroot SuperSU and then try Magisk again. Not sure what I did next but phone keeps automatically booting into TWRP recovery (unable to boot to regular ROM, I did not backup or know how to backup).
Looking through the ROM forums with no experience, I assumed I just need to flash any of the ROMs for Honor 8 and then restart and see if I can get Magisk to work. Unfortunately, I tried a few such as: ResurrectionRemix-M-v5.7.4-20170106-frd, aicp_frd_n-12.1-UNOFFICIAL-20170704 but none were flashing correctly (I think something about MD5).
Unfortunately, now when I boot up phone (see the "Your device has been unlocked and can't be trusted" screen), then it stays pitch black. Usually it would start up the phone afterwards or in the recent case was directly to TWRP recovery. I sort of gave up for now.
Click to expand...
Click to collapse
Some of the roms for Honor 8 does not give like a custom Vendor partition. You should use this rom
[ROM][7.1.2][OpenKirin's RROS v5.8.4 For Honor 8 ][ Update 12/08/2017 ]
Resurrection Remix N v5.8.4 For Honor 8 (FRD) > Officially Supported Devices : FRD-L02,L04,L09,L14,L19,AL00&AL10 < *** Stable Version *** About Resurrection Remix the ROM has been based on LineageOS, and including some...
forum.xda-developers.com
Make sure you download the one that says "Full Version" 5.8.3, because it installs a custom Vendor partition.
Make sure to Format Data before installing.
Also after installing, you should press the button that clears "Dalvik Cache" so that you do not get stuck in boot logo.
Also to disable Forced Encryption so that the "Data" partition does not get encrypted when you boot the rom so that you can backup "Data" partiton, install this after installing the rom:
[Deprecated] Universal DM-Verity, ForceEncrypt, Disk Quota Disabler [11/2/2020]
Hi all! For the past couple of months, I've been looking into making a more universal solution to disable dm-verity and forceencrypt. Needing to take different zips, modify them for different devices, and then cross your fingers when you switch...
forum.xda-developers.com
CHECK_123 said:
Some of the roms for Honor 8 does not give like a custom Vendor partition. You should use this rom
[ROM][7.1.2][OpenKirin's RROS v5.8.4 For Honor 8 ][ Update 12/08/2017 ]
Resurrection Remix N v5.8.4 For Honor 8 (FRD) > Officially Supported Devices : FRD-L02,L04,L09,L14,L19,AL00&AL10 < *** Stable Version *** About Resurrection Remix the ROM has been based on LineageOS, and including some...
forum.xda-developers.com
Make sure you download the one that says "Full Version" 5.8.3, because it installs a custom Vendor partition.
Make sure to Format Data before installing.
Also after installing, you should press the button that clears "Dalvik Cache" so that you do not get stuck in boot logo.
Also to disable Forced Encryption so that the "Data" partition does not get encrypted when you boot the rom so that you can backup "Data" partiton, install this after installing the rom:
[Deprecated] Universal DM-Verity, ForceEncrypt, Disk Quota Disabler [11/2/2020]
Hi all! For the past couple of months, I've been looking into making a more universal solution to disable dm-verity and forceencrypt. Needing to take different zips, modify them for different devices, and then cross your fingers when you switch...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks. I will have to revisit this another time. Since my phone was stuck in a loop after trying the other ROMs, I tried the eRecovery by Huawei and now it's just stuck on the loading screen. I think it also completely wiped out everything so I have to unlock bootloader again. I forgot the steps as well besides having the unlock code through DC Unlocker (I watched some video for this step but couldn't find it).
But either way, it's just stuck on loading screen. lol Frustrating to root just for Pokemon Go.
etsai3 said:
Thanks. I will have to revisit this another time. Since my phone was stuck in a loop after trying the other ROMs, I tried the eRecovery by Huawei and now it's just stuck on the loading screen. I think it also completely wiped out everything so I have to unlock bootloader again. I forgot the steps as well besides having the unlock code through DC Unlocker (I watched some video for this step but couldn't find it).
But either way, it's just stuck on loading screen. lol Frustrating to root just for Pokemon Go.
Click to expand...
Click to collapse
Okay! I also would recommand saving the bootloader code, just incase DC Unlocker stops working.
I think that "download latest firmware" button in eRecovery might download the android 8 emui firmware instead of android 7 emui firmware.
I think that the first boot takes a long time on EMUI, is really stuck in the loading screen? Maybe you have to wait maybe 15-20 minutes for it to boot.
I think that you did not have to restore using eRecovery, the roms that you flashed might have edited maybe the boot, vendor and system partitions. And that could of been fixed by flashing the RROS 5.8.3 full version because it edits all boot, vendor, and system partitions.
CHECK_123 said:
Okay! I also would recommand saving the bootloader code, just incase DC Unlocker stops working.
I think that "download latest firmware" button in eRecovery might download the android 8 emui firmware instead of android 7 emui firmware.
I think that the first boot takes a long time on EMUI, is really stuck in the loading screen? Maybe you have to wait maybe 15-20 minutes for it to boot.
I think that you did not have to restore using eRecovery, the roms that you flashed might have edited maybe the boot, vendor and system partitions. And that could of been fixed by flashing the RROS 5.8.3 full version because it edits all boot, vendor, and system partitions.
Click to expand...
Click to collapse
Yes, I actually did save the bootloader code, I just don't remember what I did / the steps to unlock the phone.
You are right about the 20 minute wait. After waiting for 20 minute, it allowed me to factory reset everything (Still Android 7.0).
I see. I have no idea about these ROM stuff and only you responded since last Wednesday. lol
So my steps should be to:
1. Unlock the bootloader again (I need to try to find the steps)
2. Install TWRP 3.1.1.1
3. Try to flash Magisk-v23.0.zip (Haven't been able to get this flashed for some reason)
4. I think there's another step called Smali Patcher or something, this was in the spoofing guide for Pokemon Go (Haven't gone that far yet to try)
So I actually probably don't need the RROS 5.8.3 ROM. I think.
EDIT:
I unlocked bootloader flashed the TWRP but TWRP recovery doesn't pop up this time. Hm.
etsai3 said:
Yes, I actually did save the bootloader code, I just don't remember what I did / the steps to unlock the phone.
You are right about the 20 minute wait. After waiting for 20 minute, it allowed me to factory reset everything (Still Android 7.0).
I see. I have no idea about these ROM stuff and only you responded since last Wednesday. lol
So my steps should be to:
1. Unlock the bootloader again (I need to try to find the steps)
2. Install TWRP 3.1.1.1
3. Try to flash Magisk-v23.0.zip (Haven't been able to get this flashed for some reason)
4. I think there's another step called Smali Patcher or something, this was in the spoofing guide for Pokemon Go (Haven't gone that far yet to try)
So I actually probably don't need the RROS 5.8.3 ROM. I think.
EDIT:
I unlocked bootloader flashed the TWRP but TWRP recovery doesn't pop up this time. Hm.
Click to expand...
Click to collapse
When trying to boot into TWRP using "Power + Volume Up", make sure that the phone is not connected to the charger, or to the computer. That might be the reason why TWRP mignt not be popping up.
After that, TWRP should boot up.
CHECK_123 said:
When trying to boot into TWRP using "Power + Volume Up", make sure that the phone is not connected to the charger, or to the computer. That might be the reason why TWRP mignt not be popping up.
After that, TWRP should boot up.
Click to expand...
Click to collapse
Thank you. The Power + Volume Up worked. Got Magisk installed. Just haven't figured out the last steps to get Pokemon Go spoofing to work.
Hello there,
I have some sort of a problem (although my phone is still working.. yet)
I recently flashed my OnePlus 6 with LineageOS 19.1 (coming from OxygenOS 11.1.2.2).
I flashed "copy_partitions.zip" first and then the official LineageOS 19.1 ROM without GApps,
but because I wanted to use some features, which needed at least the presence of Google Services, I flashed the "LineageOS for microG" (19.1) ROM.
Which worked like a charm.. besides I was very unhappy because of the lack of customization regarding color-theming and the changes made to the QuickSettings of Android 12 in general..
So I thought I could clean flash LineageOS 18.1 / ("Lineage for microG") to get the old theming back..
So what I did was installing the official custom LineageOS recovery from 18.1 (because microG had none for 18.1),
hit "Factory Reset" and afterwards applied the Lineage 18.1 zip over adb.
A message "Update package is older than the current build, expected a build newer than timestamp [...] but package has timestamp [...] and downgrade not allowed" along with the Question to install anyway appeared right after sideloading it to the phone.
I decided to hit "Yes" because I don't needed to backup any data from the phone and wanted to wipe clean anyways... (which I thought I did with "Factory Reset)
So I installed and afterwards rebooted to recovery to flash Magisk aswell..
After rebooting to system then, the phone entered the fastboot loop.
No matter what I do, it still doesn't boot to system after installing 18.1 from LineageOS recovery (also tried with the newest microG recovery from 19.1).
I also known you would wipe system, cache and data (and maybe vendor aswell) prior to a clean custom ROM flash (via TWRP)..
So flashed TWRP 3.6.2 (latest) for enchilada and tried to wipe my system, vendor and cache, but didn't manage to find "system" or "cache" on the advanced wipe menu, so I formatted and wiped data and wiped vendor.
Then installed LOS 18.1 via TWRP also..
But same problem - fastboot only.
also after my TWRP journey, sometimes when flashing the LOS recovery and booting it, a message appears on screen:
Failed to bind mount /mnt/staging/emulated/media/0 [...]
The thing is, I can install LOS 19.1 (microG) without any problems and it would boot,
but I just want to downgrade and I found no guide for my device (or any with ramdisk and A/B slots)..
And there is also no link to MSMDownloadTools for Android 10 (because onepluscommunityserver.com is offline)..
The links from this post and some other posts I found aren't working anymore..
- Is there a way to go back to LineageOS 18.1? What would be the intended way (not doing a downgrade but flashing clean)?
- Is my phone softbricked somehow? (partitions broken or corrupt?)
- Is it a firmware problem?
(I am on security patch from November 2021)
But I don't know what exactly happened to my firmware when flashing Lineage 19.1 over OOS 11.1.2.2
This is my first post as it is my first Android phone/flashing experience in general.. so I hope I got everything right from all I found out until now..
I really appreciate any help / even if it is just saying I messed up and need to go EDL mode... (if it truly is the case)
Thanks in advance.
You people are great!
o/
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