Root - Lenovo P2 Guides, News, & Discussion

I tried flashing magisk via twrp but everytime it used to stuck at flashing boot image for hours ..then I manually flashed the patched boot image of magisk....it showed me success but no root was there... after that I flashed my original boot IMG and then tried flashing SuperSU with twrp but this time too same case stucked at flashing boot image .and no further improvement
Note I am on viper os ROM and have tried to root with both f2fs and ext4 but no results... pls help

I don't use this ROM at my phone, but as you can see in this Video from "Tio Hetfield"
the root method from LineageOS does also work.
Simply download the suitable file for your Phone and flash it.
https://download.lineageos.org/extras
If your Rom is based on Android 7.1 download the file for LineageOS 14.1 the processor architecture of the Lenovo P2 is "arm64"
To activate root after flashing unlock the Developer settings and activate root in the new menu entry.
This is only for root access, not the magisk framework

Repair system partition and also ensure data it ext4. This fixed it for me.

Solution for being stuck at "flashing boot image"
Ishann15 said:
I tried flashing magisk via twrp but everytime it used to stuck at flashing boot image for hours ..
Click to expand...
Click to collapse
I had the same problem, but found a solution!!!
I restarted the Phone by pressing the power button for 20 or so seconds.
Then again thanged into TWRP Recovery mode and there I installed the new beta SuperSU file SR1-SuperSU-v2.82-SR1-20170608224931.zip
That one just worked!

Related

[guide] how to root zenfone 3 official oreo firmware

HERE IS A STEP BY STEP GUIDE TO ROOT ZENFONE 3 FOR PEOPLE WHO HAVE UNLOCKED THEIR BOOTLOADER AND ROOTED THEIR NOUGAT ROM PREVIOUSLY.
-first of you need to update your firmware to oreo.
-if you have unlocked your phone bootloader and/or rooted, you need to download and flash the latest nougat firmware through stock recovery which is 'WW-14.2020.1712.85' here https://www.asus.com/Phone/ZenFone-3-ZE552KL/HelpDesk_BIOS/
-after you finished flashing the latest nougat firmware, boot your phone as usual. and then download the official oreo firmware which is 'WW-15.0410.1712.31 here https://www.asus.com/Phone/ZenFone-3-ZE552KL/HelpDesk_BIOS/
-then put that 'WW-15.0410.1712.31' firmware to your SD card
-your phone will automatically detect an oreo firmware is available to be flashed that are located on your SD card then click on update
-then your phone will go to the updating/flashing process took around 5-10 minutes. after you're done your phone are now using the official stock firmware.
-then to proceed to root your oreo firmware, you need to flash a TWRP recovery. you can download twrp recovery here https://drive.google.com/drive/folders/1KYX8G6wgOa_X7uJfIar7ENuk2Q1nQyWB
-choose the right model for your phone either ZE520KL(5.0inch) or ZE552KL(5.5inch)
-rename the twrp recovery you just downloaded to "oreo_twrp_recovery.img"
-then put your phone to 'fastboot' mode and connect usb to laptop/pc
-put the twrp recovery that you just downloaded inside the 'Kit Root Zenfone 3' on your laptop/pc
-press shift and right click then click on 'Open command window here'
-then on cmd, type "fastboot flash recovery oreo_twrp_recovery.img" and click enter
-it will tell you flashing is finished
-then click on cmd type 'fastboot reboot' and click enter
-then your phone are now using TWRP recovery instead of the stock recovery
-next, go to magisk manager . com (no space)
-download the magisk manager apk version 5.5.5 [2.4mb]
-download magisk v15 [5.81mb] zip file
-boot your phone and install the magisk manager apk like normal
-then put the magisk v15 zip file to your SD card
-then boot your phone to TWRP recovery and flash the magisk v15 zip file
-after done, reboot system from twrp recovery
-open the magisk manager app and you're ROOTED!
done. your welcome.
[MY REVIEW OF THE OFFICIAL OREO FIRMWARE AFTER ALMOST A WEEK OF USE]
-oreo battery life sucks compare to stock nougat rom
-i can notice the battery drain faster than when im on nougat
-system performance, for me 5-10% faster than on nougat, especially the in settings or swiping the notification panel, other than its the same
-gaming performance are 10-15% worse than on nougat. when i play a game called 'Dokdo', moving the ship around the ocean are smoother when im on nougat and the framerate are stable, but when i play the game on oreo, the framerate are lower and i can feel the difference when im playing on nougat and oreo. the game feels more smoother when im on nougat compare to oreo. other games performance also noticeable when i play 'Rules of Survival', i can feel the framerate are slightly smoother on nougat compare to oreo
-there's no bugs that i found so far
[MY FINAL REVIEW OF ZENFONE 3 OFFICIAL OREO FIRMWARE]
-oreo battery life is real ****, i dont even have many apps installed and the battery life is already ****
-i prefer the nougat firmware compare to oreo.
-the only thing that i like about oreo is the quick settings icon are changed, it looks cleaner and smaller compare to nougat the quick settings icons are bigger and doesn't look good
-everyday i check on https://www.asus.com/Phone/ZenFone-3-ZE552KL/HelpDesk_BIOS/ hoping there's a new oreo firmware update saying 'battery life improved' or something thats all i want
*14 february guide updates*
incase you guys hasn't already know, there's a second(current latest) oreo updates from asus, the firmware is called 'Version WW-15.0410.1801.40'.
if you are on rooted oreo firmware 'Version WW-15.0410.1712.31' and you want to update to the latest oreo version and root it again. follow this steps below:
*NOTE: you can't proceed to flash the stock firmware if you're phone are rooted so you need to unroot or remove magisk root first before flashing the oreo firmware otherwise the flashing process will fail or a possible of bootloop will occur, so follow the steps below carefully*
-first, you need to remove magisk root by downloading the magisk uninstaller zip file from the magisk manager . com (no space) or from their xda page
-then flash/install the magisk uninstaller zip file from TWRP recovery
-after you flashed the uninstaller, you're phone are now unrooted. then you can proceed to flash the 'Version WW-15.0410.1801.40' firmware.
-after you flashed the 'Version WW-15.0410.1801.40' firmware your TWRP recovery will be replaced back to asus stock recovery
-so you need to reinstall TWRP recovery as usual through fastboot
-reboot your phone as usual and as you know your phone root access is currently gone since you uninstalled magisk earlier
-to root your phone back, download and install the latest magisk manager from their site or xda site
-click on download zip file, and put that magisk zip file on your SD CARD
-boot to twrp recovery
-flash the magisk zip file that are located on your SD CARD
-reboot system
-now your latest 'Version WW-15.0410.1801.40' firmware are now rooted again.
YES I KNOW IT IS SUCH A HASSLE, BUT THIS IS WHAT YOU MUST GET THROUGH IF YOU WANT ROOT ACCESS. ANDROID IS NOT EASY.
By the way, don't go to magiskmanager<dot>com. It's not official.
Download Magisk from the official thread here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
w1040 said:
-next, go to magisk manager . com (no space)
Click to expand...
Click to collapse
Careful with that site, as that's not an official distribution site for Magisk. There was a tweet from XDA regarding that site within the past few weeks. The only 100% trustworthy place to get it is from the official thread.
I'm getting better battery life on Oreo than I did on Nougat. I did do a factory reset after installing Oreo, though, so if you haven't done that it's worth a try.
You're right about the framerate issue with some games. Some that ran fine on Nougat get oddly choppy at times on Oreo. The last Oreo beta (although it had the same version number) was a heck of a lot worse than the release version, so hopefully the next update will help.
the reason why i put the magisk manager official site is because i rooted my phone by downloading both the magisk manager apk and the zip file and the app and the zip file from their official site works for rooting my phone so i think there is no harm. if you feel insecure you can just go to https://forum.xda-developers.com/app...mless-t3473445
Not working.
I exactly followed the steps but I could not install twrp. Stock recovery still keeps running.
However, If I use the previous version of twrp (20180203) phone cannot boot, then had to flash roms from M to O.
Edit: I tried over and over again and succeeded at last, but I do not know how exactly!
asenler said:
I exactly followed the steps but I could not install twrp. Stock recovery still keeps running.
However, If I use the previous version of twrp (20180203) phone cannot boot, then had to flash roms from M to O.
Edit: I tried over and over again and succeeded at last, but I do not know how exactly!
Click to expand...
Click to collapse
at cmd when you're phone on fastboot. after you typed "fastboot flash recovery (name of your recovery)".img and enter, make sure it says flashing successful.
new firmware
How about ZE552KL_ WW_15.0410.1801.40 ?
asenler said:
How about ZE552KL_ WW_15.0410.1801.40 ?
Click to expand...
Click to collapse
what about it? i have yet to flash it
So the same procedure applies.
Flash the update + go to fastboot + re-install magisk.
Success.
Thanks everyone.
asenler said:
So the same procedure applies.
Flash the update + go to fastboot + re-install magisk.
Success.
Thanks everyone.
Click to expand...
Click to collapse
yes, its the same procedure. the latest firmware update is still oreo afterall
GUIDE UPDATES - 14 february
Hi !
So yesterday I tried flashing TWRP but no luck.
I'm on the latest firmware (1801), bootloader unlocked, stock recovery with no root.
When I try to flash TWRP with fastboot, I get no error message but I still have the stock recovery instead of TWRP.
I tried multiple times and downloaded the file again but it doesn't work.
Any idea ?
aftee you flashed twrp through fastboot. type on "fastboot reboot" on cmd. then if your phone directs you to stock recovery instead of twrp. click on reboot system in your stock recovery. then it will brings you to twrp. i know its weird. but thats what happen to me too at first.
then if you finally got to twrp and you reboot system from twrp but your phone still brings you back to twrp recovery everytime or it stucks on asus logo (bootloop), dont panic, go to twrp and flash your stock oreo firmware that are located from ur sdcard from twrp, then when you reboot system from twrp, then your phone will boot to normal. dont worry it wont erase data.
try this. it works for me.
Guys. Can I use the above, android already oreo but not in unlock bootloader.
Putra.dim said:
Guys. Can I use the above, android already oreo but not in unlock bootloader.
Click to expand...
Click to collapse
its not possible to root zenfone 3 without unlocking bootloader.
w1040 said:
its not possible to root zenfone 3 without unlocking bootloader.
Click to expand...
Click to collapse
I've been looking for how to unlock zen 3 oroe. but i did not find it. please help me. i want to root my phone.
Here is the official unlock method.
You will not be able to get OTA updates then, but zenfone3 may not get any upgrade anyway.
I found the solution to my problem (couldn't boot into twrp after flashing it)
1-After flashing twrp, do not fastboot reboot !
2-Unplug the device
3-Power it off (long press power key)
4-Power it on into recovery mod (long press power key + low volume key)
You should end up in twrp recovery or on a screen suggesting to boot into recovery which you do
5-A message will appear asking to allow modification of twrp recovery. Swipe to allow.
6-Done !
w1040 said:
aftee you flashed twrp through fastboot. type on "fastboot reboot" on cmd. then if your phone directs you to stock recovery instead of twrp. click on reboot system in your stock recovery. then it will brings you to twrp. i know its weird. but thats what happen to me too at first.
then if you finally got to twrp and you reboot system from twrp but your phone still brings you back to twrp recovery everytime or it stucks on asus logo (bootloop), dont panic, go to twrp and flash your stock oreo firmware that are located from ur sdcard from twrp, then when you reboot system from twrp, then your phone will boot to normal. dont worry it wont erase data.
try this. it works for me.
Click to expand...
Click to collapse
After updating on 15.0410.1801.40, i flash TWRP through fastboot, and i get stuck in bootloop on Asus logo. I go back in TWRP,flash the 15.0410.1801.40 zip, and i remain in bootloop.
With a custom recovery, we didn't need any No Verity File Encrypt like root in Nougat? (On nougat I root my ZE552KL by following this process: https://forum.xda-developers.com/zenfone-3/how-to/twrp-recovery-3-0-2-root-zenfone-3-t3569926)
siberflyers said:
After updating on 15.0410.1801.40, i flash TWRP through fastboot, and i get stuck in bootloop on Asus logo. I go back in TWRP,flash the 15.0410.1801.40 zip, and i remain in bootloop.
With a custom recovery, we didn't need any No Verity File Encrypt like root in Nougat? (On nougat I root my ZE552KL by following this process: https://forum.xda-developers.com/zenfone-3/how-to/twrp-recovery-3-0-2-root-zenfone-3-t3569926)
Click to expand...
Click to collapse
if you got bootloop after trying to reboot ur phone from twrp after flashing twrp. flashing the stock oreo rom from twrp again will make your phone boot. thats how i did it. im not sure why it doesn't work for you.
we still need "no verity..." message in oreo. that no verity message appears are actually caused by your phone bootloader unlocked not because of your phone rooted.

No Wi-Fi after rooting OnePlus 7 Pro with LineageOS 16

I tried to root my Oneplus 7 Pro with LineageOS 16 using Magisk
I flashed the Magisk zip file with TWRP but after booting into my phone, I couldn't connect to WiFi (like, it would appear that the WiFi was turned off but if I tried to turn it on it simply wouldn't) so I read somewhere that I needed to flash an stock OS img as boot on TWRP and flash Magisk again
After downloading an recovery img of lineageOS for the phone I went to TWRP. I had to perform a Cache/Davilk wipe since I couldn't find my files, but after doing so and booting into TWRP again, I could find the files for the img and the Magisk zip file.
I flashed the LineageOS img as boot and flashed Magisk zip file again and rebooted, but the phone went into a bootloop, so I had to perform a factory reset (gladly I had nothing to lose)
Am I doing something wrong? How can I have the WiFi again after rooting? (My phone is currently unrooted but I wanna try again later)

Twrp boot loop

I patched twrp img with magisk and then ran fastboot flash boot "patched file" in fastboot mode. Now, whenever and however I start my system I get only the twrp menu. My device is Lenovo tab 4 8(tb-8504f)
Re-flash tablet's Stock ROM to get rid off of all modifications you applied so far.
re flash the ROM. dont flash the magisk or twrp after it. you will be saved.
you can use twrp via adb boot twrpxx.img So flashing it not needed.
Magisk installation has now become trickier simply flashing via recovery won't work
jwoegerbauer said:
Re-flash tablet's Stock ROM to get rid off of all modifications you applied so far.
Click to expand...
Click to collapse
hello thanks for replying. Could you provide me with the official rom. I've found one but not sure how reliable it is. I also in the twrp menu installed the patched twrp image from sd card to boot. After rebooting I again get the twrp menu but the file is not being show in sdcard anymore.
suraj123 said:
re flash the ROM. dont flash the magisk or twrp after it. you will be saved.
you can use twrp via adb boot twrpxx.img So flashing it not needed.
Magisk installation has now become trickier simply flashing via recovery won't work
Click to expand...
Click to collapse
I also in the twrp menu installed the patched twrp image from sd card to boot. After rebooting I again get the twrp menu but the file is not being show in sdcard anymore. Does this include what you've refused me to do so? And can u pls provide me the official link?

Unable to make a stable boot image?

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)

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

Categories

Resources