Database Info

[RECOVERY][UNOFFICIAL][Jasmine] TWRP 3.2.3.0 17-9-2018

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system, functions often unsupported by stock recovery images. It is, therefore, often installed when rooting Android devices, although it isn't dependent on a device being rooted to be installed.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
DOWNLOAD:
https://drive.google.com/open?id=10i5ddHcV0lt8JJ7nV1bJjqc1XXjLCp8n
Note this is just a hobby, but feel free to report bugs.
Kernel source: Prebuilt stock kernel
Boot to fastboot ( volume down and power )
in fastboot type:
Link comes later when stable
fasboot reboot and hold power up and volume
Click to expand...
Click to collapse
Note: this twrp is working with the orginal system, when ota happens just flash twrp again.
BUGS:
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Contributors
@bassbounce ( Compiled )
@Manish4586 ( Device tree )
Device tree: https://github.com/Manish4586/android_device_xiaomi_jasmine-twrp
Source Code: https://github.com/omnirom/android_bootable_recovery/
Version Information:
Status: testing
Created 17-9-2018
Last Updated 17-9-2018

Nice! So this is supposed to work without A/B conflicts - unlike the other TWRP project?
Edit: Awesome! This works great so far. I now have permanent TWRP on my device. It updates partition details perfectly and I was able to flash Magisk without an issue.
Thanks a lot for your work!

thedisturbedone said:
Nice! So this is supposed to work without A/B conflicts - unlike the other TWRP project?
Click to expand...
Click to collapse
U are right, this twrp just boots the stock android, the other did not do that.

bassbounce said:
U are right, this twrp just boots the stock android, the other did not do that.
Click to expand...
Click to collapse
Thank you. Edited my initial post with results. This would open our device to a lot of possibilities.

I have September update, can i install this?

ki69 said:
I have September update, can i install this?
Click to expand...
Click to collapse
I dont know, i didnt test it on the september .

bassbounce said:
Yes, it should be no problem.
Click to expand...
Click to collapse
Thanks man, can you build it for mi a2 lite (daisy) ?

Touch screen don't work
After flash twrp touch screen don't work
My device rooted and install magisk

s.arthit1993 said:
After flash twrp touch screen don't work
My device rooted and install magisk
Click to expand...
Click to collapse
Try flashing stock boot img

This is work for my Mi A2 Rooted Whit Magisk V17.1 ?

Unfortunately, I'm not a developer.
Can someone compile the code and make an available download for this image, please?
Many Thanks!

MMN said:
Unfortunately, I'm not a developer.
Can someone compile the code and make an available download for this image, please?
Many Thanks!
Click to expand...
Click to collapse
same problem here, I don't know how to download or install it, I would like to try it

Adairo said:
same problem here, I don't know how to download or install it, I would like to try it
Click to expand...
Click to collapse
Fastboot flash boot file.img
Restart phone and boot in to recovery volume up and power key.
If it works please report here,
I don't know if twrp works with the September update which is pulled back.
Also I need a 6gb 128 a2 to test this.

DOWNLOAD:
Some ppl reported touch problems we look in to that
Dont download yet

nvm

wi-fi does not work

bassbounce said:
Fastboot flash boot file.img
Restart phone and boot in to recovery volume up and power key.
If it works please report here,
I don't know if twrp works with the September update which is pulled back.
Also I need a 6gb 128 a2 to test this.
Click to expand...
Click to collapse
You have changed the file. The difference is enormous. Which one is correct?
-> twrp-jasmine-0.1.img (27.276kb) -> Link removed in the cited post
-> boot.img (37.252kb) -> Link in post #1
Mi A2 6/128GB is here.
dimaxxxxx said:
wi-fi does not work
Click to expand...
Click to collapse
And yes: wifi does not work on both images

WiFi not working, help please.

Testing without wifi:
* Magisk v17.1 (via TWRP/zip) -> works
* SuperSU (via Magisk) -> works
* SELinux-Manager (via TWRP/zip) and go to permissive mode -> works
* xposed (xposed-v90.2-sdk27-beta3, via TWRP) -> bootloop - I'll try direct installation through Magisk when wifi works.
What's about error message when deleting the cache in TWRP:
unable to find partition for path '/cache'?

To all restore the stock boot.img. To fix it
We need to find a solution. Don't flash the twrp.

[RECOVERY][UNOFFICIAL] TWRP for Galaxy S21 (Exynos)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
Supported Models:
Galaxy S21 G991B/N.
Download & Guide:
1. Unlock your bootloader.
2. Download S21: o1s.
3. Reboot to download mode
4. Put the TWRP TAR for your device with Odin in the AP slot, vbmeta_disabled_R.tar in USERDATA slot and click start.
5. Reboot to recovery via recovery key combo (Vol up + power + USB connected).
6. Disable encryption:
- Go to Advanced > Terminal, type: multidisabler.​If vendor complain about free space left on device, will attempt to resize vendor. and it ask to - Run multidisabler again!.​- Type: multidisabler again. will see - Finished. when done.​- Go back to Wipe > Format Data > type yes.​- Reboot to recovery.​7. Flash magisk apk in twrp.
8. Reboot to system, Enjoy.
Support:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Telegram group
Bugs:
- Encryption not fully working.
Thanks:
TWRP team
@ianmacd for multidisabler
Sources:
Kernel tree
Device tree

Changelog:
29.11.2021 - Update to TWRP 3.6.0
- Updated to latest kernel source
- Update multidisabler
- fstab clean up
- Fix haptic feedback
21.08.2021 - Add Symlinked dynamic partitions to fstab
- Fix dtbs issue from previous build
09.08.2021 - Updated to latest kernel source
- No vbmeta disable require
- fstab clean up
03.03.2021 - Initial Release.

Wait if this is for the S21 Ultra only what is this doing in the normal s21 forum?
Youre very fast gg

DeblaGaming said:
Wait if this is for the S21 Ultra only what is this doing in the normal s21 forum?
Youre very fast gg
Click to expand...
Click to collapse
My bad I missed that but you can know from G991B its regular not Ultra.

@afaneh92 The recovery supports flashing Magisk APK out-of-the-box?
So, no need to rename the .apk to .zip anymore?

I'm kinda casual, with haptic feedback not working do you mean the vibration motor in the phone stops working completely, or? I don't know what encryption not working means either.
I saw the same issues for the S20 FE.
Looking at both forums closely currently as I'm deciding which phone to buy dependent on which phone will have a better root experience.

Will this have to be done everytime there is a firmware update?? Or like other devices we can keep twrp and magisk when updating..
I currently have S20 which I dont have twrp on but can update new firmware and just reboot to odin after flashing new firmware and just flash patched boot.img and all is good. Will the S21 be the same

DJBhardwaj said:
@afaneh92 The recovery supports flashing Magisk APK out-of-the-box?
So, no need to rename the .apk to .zip anymore?
Click to expand...
Click to collapse
You can flash apk
orkavaneger said:
I'm kinda casual, with haptic feedback not working do you mean the vibration motor in the phone stops working completely, or? I don't know what encryption not working means either.
I saw the same issues for the S20 FE.
Looking at both forums closely currently as I'm deciding which phone to buy dependent on which phone will have a better root experience.
Click to expand...
Click to collapse
Vibration not working in twrp only, read more.
bigpotato107 said:
Will this have to be done everytime there is a firmware update?? Or like other devices we can keep twrp and magisk when updating..
I currently have S20 which I dont have twrp on but can update new firmware and just reboot to odin after flashing new firmware and just flash patched boot.img and all is good. Will the S21 be the same
Click to expand...
Click to collapse
Yes need to redo every step.

i got my s21 rooted with ap, and magisk install thing. now i want to get twrp, is it just followed the guide or should i factory ap first?

Emrah132 said:
i got my s21 rooted with ap, and magisk install thing. now i want to get twrp, is it just followed the guide or should i factory ap first?
Click to expand...
Click to collapse
Follow instructions.

i didnt need vibration its great job thank you afaneh92

can i flash twrp without lost magisk root?

What about encryption issue.. is there any clue on next release. I don't think I found a problem except for the two things that were mentioned above bugs

Hi,
I was able to install magisk. In the end, I want to install exposed framework. In the TWRP mode, whenever I try to install, I get an error.
-Mounting /system and /vendor read-write mount: can't find /system in /proc/mounts
!Failed: /system could not be mounted
In the end, it says "Updating partition details" .. done. Can you please help me in resolving this error.

Thanks for your efforts, dev! Everything working as expected.

Hello, is there any way to re-enable encryption after TWRP installation? No matter, FBE or FDE. It says "not fully working" and I see only not working at all, maybe I am doing something wrong?

A note on firmware updates:
It is possible to follow all the instructions from the original post but SKIP the step of wiping your data from within TWRP when updating your firmware. You need to run the multidisabler though. This works if you had already installed this TWRP version with encryption disabled, including a data wipe, but now want to update your firmware. So wiping data is only needed for the first time.
In fact, if you had installed this TWRP version and do a firmware update via odin but do not flash this TWRP version with vbbeta disabled, your phone simply won't start anymore. It will ask you to factory reset.
So once you go TWRP, you have to reinstall it for future updates.
@afaneh92 do you want to add this as a hint in your OP?

Thank you for your great work and the fast twrp publishing! I was able to install and boot a GSI.
Now I would like to flash microg/gapps to system, but the system partition does not have any free space left. In the twrp wipe menu I cannot find the system partition to increase size. Would it be possibe to add this feature or are other steps mandatory to increase system partition in size?
Again, thanks a lot for your efforts!

Hi, I have my S21 Rooted with Magisk Patched Stock Image.
It is possible to flash TWRP but without doing a Data Wipe?
It isn't clear if the Data Wipe is needed for Rooting after unlocking the bootloader (I already did that), or it is actually needed for getting TWRP to fully work.
Thanks.

WiS3 said:
Hi, I have my S21 Rooted with Magisk Patched Stock Image.
It is possible to flash TWRP but without doing a Data Wipe?
It isn't clear if the Data Wipe is needed for Rooting after unlocking the bootloader (I already did that), or it is actually needed for getting TWRP to fully work.
Thanks.
Click to expand...
Click to collapse
In your place I would just try. Take a backup and try the installation, skipping ONLY the data wipe. If this fails, either use your backup or include the wipe.
Though, I HIGHLY assume you need to wipe for the first install of TWRP to remove the encryption initially. In future TWRP updates, you can skip wiping.

J415GN/DS TWRP HELP

yo, can someone help or answer me. I can't seem to find any official/unofficial version of twrp for sm-j415gn/ds. Does anyone have any link?

lamawkalabaw said:
yo, can someone help or answer me. I can't seem to find any official/unofficial version of twrp for sm-j415gn/ds. Does anyone have any link?
Click to expand...
Click to collapse
https://forum.xda-developers.com/f/samsung-galaxy-j4-roms-kernels-recoveries-ot.8287/
There is one here.

ashyx said:
Unofficial release -TWRP recovery for the Galaxy J4 plus 2018 - SM-J415 MSM8917
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP 3.3.1-0 Released
May 22, 2019
TWRP 3.3.1-0 is out now for most currently supported devices.
What's new in 3.3.1-0:
* Fix selinux issues during formatting - dianlujitao
* Various fixes for toybox and toolbox builds - CaptainThrowback and bigbiff
* Flash both A and B partitions when installing a recovery ramdisk - Dees_Troy
* Add option to uninstall TWRP app from /system - Dees_Troy
* Create digest for subpartitions - bigbiff
Want to get notifications when we release new versions of TWRP? Install the TWRP app and select your device!
We need your help! The bulk of TWRP work is done by a handful of people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
Update - 17/8/2019
TWRP 3.3.1-1 OO/PP build released
Current status - Beta
Treble supported
Bugs: brightness slider
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
NOTE: ON ANDROID 5.1.1> DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
*****INSTALL INSTRUCTIONS:*****
Flash with ODIN in the AP slot.
1. Put your device in DOWNLOAD mode.
(Plug in the USB cable and then hold POWER + VOL DOWN + VOL UP)
2. Load the respective file below into the AP slot, uncheck Auto-reboot(not required for twrp_3.3.1-1) and hit start.
twrp_3.2.3-1_sm-j415f_30319
twrp_3.3.1-1_j415x_17819
3. After flashing and ODIN reports PASS immediately force reboot to recovery. (Not required for twrp_3.3.1-1 as it should auto reboot to recovery). You should now see TWRP recovery.
Do NOT let the device boot to the OS.
4. Flash the V3 RMM bypass zip
https://forum.xda-developers.com/showpost.php?p=79745844&postcount=627
NOTE: FAILURE TO FOLLOW THE STEPS ABOVE IMPLICITLY WILL RESULT IN STOCK RECOVERY REPLACING TWRP AT FIRST BOOT AND BECOMING RMM LOCKED FOR 7 DAYS.
I ALSO SUGGEST BACKING UP ANYTHING YOU NEED ON INTERNAL STORAGE. AT SOME POINT YOU MAY EXPERIENCE A 'VERIFICATION FAILED MESSAGE' .
THIS IS NORMAL, BUT WILL REQUIRE THE DATA PARTITION TO BE FORMATTED IN TWRP.
5. Reboot to TWRP (Do not boot to the OS yet)
***** ROOT INSTRUCTIONS:*****
OREO ONLY
1. Flash the Forced encryption disabler patch. This is only required if you wish to have full functionality in TWRP.
Flashing this will disable Samsung's forced encryption. Disabling encryption will allow TWRP to mount the data partition.
After flashing the patch it is necessary to *FORMAT* (not wipe) the /DATA partition using the FORMAT DATA button under the wipe options.
PLEASE NOTE THIS WILL DELETE EVERYTHING ON INTERNAL STORAGE AND FACTORY RESET THE DEVICE, SO BACK UP ANYTHING YOU WISH TO KEEP.
J4+J6+_oreo_forced_encryption_disabler
2. To root I suggest installing the latest Magisk beta as this is a currently supported project, SuperSu is no longer getting active development.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
(NOTE: The DEFEX patched Oreo kernel below may be needed for full root support if certain apps do not work with root):
https://androidfilehost.com/?fid=1395089523397921797
3. Enjoy your rooted device.
PIE ONLY
1. Due to some new securities in Samsung's latest Pie kernels, root will not work with the stock kernel. The patched kernel below is required to gain root on Pie.
Features:
Dmverity, proca, five and defex disabled.
OTG and NTFS file system support.
Selinux permissive switchable.
This kernel may require the U4 bootloader.
(NOTE: flashing a custom kernel on PIe breaks the lockscreen. Ensure NO lockscreen is enabled before installing the kernel.)
J415FXXU4BSF7_patched_boot_318919
2. To root I suggest installing the latest Magisk beta as this is a currently supported project, SuperSu is no longer getting active development.
https://forum.xda-developers.com/app...mless-t3473445
3. If you wish to have access to internal storage /DATA in TWRP then encryption will need to be disabled. See step 1 of the Oreo root instructions then instead of installing the J4+J6+_oreo_forced_encryption_disabler install the zip below with TWRP:
Disable_Dm-Verity_ForceEncrypt_Quota_08.02.2019
3. Reboot.
The device will take a good 10 mins to boot first time.
Enjoy your rooted device.
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, my tester @kapmino269 [MENTION=6037748]Zackptg5 for the DM-VERITY & FORCEENCRYPT DISABLER @teamwin, @corsicanu for RMM V3 bypass zip.
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
Click to expand...
Click to collapse
Here.

Kenora_I said:
Here.
Click to expand...
Click to collapse
yo thanks, but is it compatible for my model? i really am confused because i don't know if j415gn/ds and j415gn are the same.

lamawkalabaw said:
yo thanks, but is it compatible for my model? i really am confused because i don't know if j415gn/ds and j415gn are the same.
Click to expand...
Click to collapse
Lol there isnt a j415gn
Just the j415gn/ds
Anyway they are the same phone nonetheless but ive given the one specific to your phone
The devs dont put /ds for convenience probably.

Kenora_I said:
Lol there isnt a j415gn
Just the j415gn/ds
Anyway they are the same phone nonetheless but ive given the one specific to your phone
The devs dont put /ds for convenience probabl
Click to expand...
Click to collapse
Kenora_I said:
Lol there isnt a j415gn
Just the j415gn/ds
Anyway they are the same phone nonetheless but ive given the one specific to your phone
The devs dont put /ds for convenience probably.
Click to expand...
Click to collapse
gee, i owe you a lot man. I just wanted to get the best out of this phone since I'm just a student and broke. I am very nervous that i might hardbrick this since it's my only phone. Anyways, thanks again dude.

lamawkalabaw said:
gee, i owe you a lot man. I just wanted to get the best out of this phone since I'm just a student and broke. I am very nervous that i might hardbrick this since it's my only phone. Anyways, thanks again dude.
Click to expand...
Click to collapse
LOL IM NOT A DUDE
But yeah no issue lol
i kinda do this for fun anyway
i just like helping around
Yeah i hate dem hard bricks. Ive had phones become paperweights, but i seem to unbrick them in the end

Kenora_I said:
LOL IM NOT A DUDE
But yeah no issue lol
i kinda do this for fun anyway
i just like helping around
Yeah i hate dem hard bricks. Ive had phones become paperweights, but i seem to unbrick them in the end
Click to expand...
Click to collapse
lmao I'm sorry and thank you
i might ask for your help again if i had any problems.

lamawkalabaw said:
lmao I'm sorry and thank you
i might ask for your help again if i had any problems.
Click to expand...
Click to collapse
Sure! Ill be here.

Development [RECOVERY][UNOFFICIAL] TWRP 3.7.0_12-0 for OnePlus Nord 2T [karen]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
What's not working?
See https://github.com/oneplus-karen-ro...s_karen-twrp/issues/1#issuecomment-1272629658
- Using fastboot boot <image> doesn't work, due to a very common MediaTek bootloader bug.
- Backing up Data partition may fail due to possible FBE issue.
- Installing OxygenOS stock OTA zip probably fails, because OnePlus didn't add version numbers to their partititons.
Flash guide:
1. Make sure you have the stock boot.img ready that matches your current OxygenOS version.
There's a list of them on this great guide: How to Root Nord 2T with Magisk without TWRP
Add both boot.img and twrp-3.7.0_12-0-UNOFFICIAL-karen.img to your phone storage, using MTP or adb push for example.
2. Flash the TWRP release to the boot partition.
Code:
fastboot flash boot twrp-3.7.0_12-0-UNOFFICIAL-karen.img
fastboot reboot
3. Once you've rebooted to TWRP, install the stock boot.img
- [Install]
- Toggle [Install Image]
- Choose boot.img in the file browser
- Select partition: Boot
- Swipe, DO NOT REBOOT
4. Next we install the ramdisk.
- Press back
- Choose twrp-3.7.0_12-0-UNOFFICIAL-karen.img in the file browser.
- Select partition: Install Recovery Ramdisk
- Swipe (optional, if you want to root the phone, DO NOT REBOOT).
- If you don't want to root, you can reboot now.
Optional, rooting:
5. Save the repackaged boot for Magisk.
Code:
adb shell dd if=/dev/block/by-name/boot of=/sdcard/boot-with-twrp.img
6. Patching the image to root.
- Reboot the device, to normal OS.
- In the Magisk app, choose install and patch our boot-with-twrp.img image.
- Note the ..../Download/magisk_patched-XXXXXXX.img filename in the logs.
7. Install the rooted boot image.
- First switch to TWRP
Code:
adb reboot recovery
- In TWRP, [Install]
- Toggle [Install Image]
- Choose Download/magisk_patched-XXXXXXX.img in the file browser
- Select partition: Boot
- Swipe
- Reboot! You're (finally) done.
Download:
twrp-3.7.0_12-1-UNOFFICIAL-karen.img
twrp-3.7.0_12-0-UNOFFICIAL-karen.img
Source code:
GitHub - oneplus-karen-roms/android_device_oneplus_karen-twrp
Contribute to oneplus-karen-roms/android_device_oneplus_karen-twrp development by creating an account on GitHub.
github.com
Credits:
@SakilMondal for the TWRP denniz (Nord 2) tree this is largely based on.
@PattasuBalu for testing out alpha builds and troubleshooting.
Information:
TWRP version: 3.7.0_12-1-UNOFFICIAL
Created: 2022-10-09
Last Update: 2022-10-15

Reserved :]
Q&A:
Do you need to repeat the install steps after an OTA update?
Short answer: yes you do.
Longer answer
Can't we install Magisk as a zip from TWRP?
Maybe you can? I just don't recommend it.
And neither does Magisk.

Fantastic work. Congrats and a huge thank you

Thanks for the TWRP, now the question is, what happen when we receive OTA updates?
Why seems not possible to directly flash magisk zip (apk renamed) to patch boot img?
I think is better to add this first Q&A in a FAQ list.

cioce said:
Thanks for the TWRP, now the question is, what happen when we receive OTA updates?
Why seems not possible to directly flash magisk zip (apk renamed) to patch boot img?
I think is better to add this first Q&A in a FAQ list.
Click to expand...
Click to collapse
When you recieve an OTA update you have do the entire process again.

garylawwd said:
Fantastic work. Congrats and a huge thank you
Click to expand...
Click to collapse
Thanks for the kind words. :] Was a fair bit of a learning curve but nothing quite as troublesome as now trying to build a full ROM. No luck on that yet.

cioce said:
Thanks for the TWRP, now the question is, what happen when we receive OTA updates?
Why seems not possible to directly flash magisk zip (apk renamed) to patch boot img?
I think is better to add this first Q&A in a FAQ list.
Click to expand...
Click to collapse
(Added the TL;DRs to the second post)
Do you need to repeat the install after an OTA?
Indeed you will need to repeat the process after an OTA.
With an asterisk. Because in theory you could speed this up if you have root access.
The Magisk app has a feature to "Install to Inactive Slot". And the TWRP app could be doing something similar, but I find it needs some work to be more reliable in doing that :]
So if 1. this becomes an OFFICIAL build, and 2. the TWRP app gets some love. It could be done.
Why can you not install Magisk as an APK?
Maybe you can though? I just don't recommend it.
I'm not a Magisk dev so I might miss the finer details why, but they state this method is no longer recommended and deprecated. So it wasn't on my checklist to try or support it.
I suspect though that the patching script will need to make a load of assumptions about how that recovery environment is set up, while the app would be more reliable.

Small update, https://github.com/oneplus-karen-ro...karen-twrp/releases/tag/3.7.0_12-1-UNOFFICIAL
Update the kernel and dtbo.img to use A.15 version.
Rebuild with upstream patch, that should fix the lpdump utility.
Note: you only really need to update if you're interested in using lpdump in TWRP.

Thanks for the update, what about SafetyNet test after TWRP + Root?
Is there any Magisk module that working 100%?

cioce said:
Thanks for the update, what about SafetyNet test after TWRP + Root?
Is there any Magisk module that working 100%?
Click to expand...
Click to collapse
SafteyNet is working fine. Using Universal SafteyNetFix by kdrag0n and added play services to blocklist on Zygisk.

Will the OnePlus Nord 2T be getting any Custom ROM's being built for it in the future?

ArmashOnXDA said:
Will the OnePlus Nord 2T be getting any Custom ROM's being built for it in the future?
Click to expand...
Click to collapse
I hope that yes It's simillar to previous model, we have the kernel etc. Beanow is doing well job with preparing recovery, so it should works We need to find only someone with skills and free time to prepare e.g. LineageOs for us

Beanow Could you tell me if you will continue working on the reocvery?​

hi,
can I use this twrp to install full ROM zip file?
what is the right order to install:
1. full zip ROM
2. twrp.img
3. magisk patched boot.img
is it ok?

nutfile said:
hi,
can I use this twrp to install full ROM zip file?
what is the right order to install:
1. full zip ROM
2. twrp.img
3. magisk patched boot.img
is it ok?
Click to expand...
Click to collapse
It depends if the rom has ramdisk or not but I've seen techkaran's video and he had ramdisk the rom had ramdisk

Did anybody install a ROM in this device yet? Is is possible to install a ROM from the regular Nord 2?

simongaiteiro said:
Did anybody install a ROM in this device yet? Is is possible to install a ROM from the regular Nord 2?
Click to expand...
Click to collapse
There is not yet a rom but u could flash gsi with dsu sideloader

Stephanizgo said:
There is not yet a rom but u could flash gsi with dsu sideloader
Click to expand...
Click to collapse
Never tried to install a GSI before. Did you already tried it on this phone?

simongaiteiro said:
Never tried to install a GSI before. Did you already tried it on this phone?
Click to expand...
Click to collapse
I tried dsu loader on a different phone and it partialy worked but it's ment for the devs
But it's easy u just unlock the bootloader and download dsu sideloader. Then connect to pc and type some command and dsu will sideload sideload your preferred GSI

Now using DSU side loader with magisk patched boot.img working fine

CrDroid-v9.0 Pixel 4 XL

crDroid-v9.0 android 13.0
INSTALLATION.
1. download boot image and crDroid-v9.0 zip file
2. reboot bootloader
3. fastboot -w
4. fastboot flash boot boot.img --slot all
5. reboot into recovery
6. sideload zip file (adb sieload zip file)
7. reboot to recovery if you want to install gapps
8. reboot system
DOWNLOADS
official builds can be found here = https://sourceforge.net/projects/crdroid/files/coral/9.x
boot.img & build.zip = https://www.androidfilehost.com/?w=files&flid=336916
GAPPS
13.0 = https://androidfilehost.com/?fid=14871746926876840643
CREDITS
crDroid devs
LineageOS Team
Alessandro Astone
SOURCES
Kernel: https://github.com/putzwon/android_kernel_google_msm-4.14
Device tree: https://github.com/putzwon/android_device_google_coral
Vendor: https://github.com/putzwon/proprietary_vendor_google_coral
ElmyraService: https://github.com/putzwon/android_packages_apps_ElmyraService

putzwon said:
crDroid-v9.0 android 13.0
INSTALLATION.
1. download boot image and crDroid-v9.0 zip file
2. reboot bootloader
3. fastboot -w
4. fastboot flash boot boot.img --slot all
5. reboot into recovery
6. sideload zip file (adb sieload zip file)
7. reboot to recovery if you want to install gapps
8. reboot system
DOWNLOADS
boot.img & build.zip = https://www.androidfilehost.com/?w=files&flid=336916
GAPPS
13.0 = https://androidfilehost.com/?fid=14871746926876840643
CREDITS
crDroid devs
LineageOS Team
Alessandro Astone
SOURCE
device=https://github.com/LineageOS/android_device_google_coral
kernel=https://github.com/LineageOS/android_kernel_google_msm-4.14
vendor=https://github.com/TheMuppets/proprietary_vendor_google_coral
Click to expand...
Click to collapse
what about flame? is it updated build?

cRdroid rocks the PX4!!! Thank you putzwon!!!

what the different with this version..?
link

Thank you so much sir
putzwon said:
crDroid-v9.0 android 13.0
INSTALLATION.
1. download boot image and crDroid-v9.0 zip file
2. reboot bootloader
3. fastboot -w
4. fastboot flash boot boot.img --slot all
5. reboot into recovery
6. sideload zip file (adb sieload zip file)
7. reboot to recovery if you want to install gapps
8. reboot system
DOWNLOADS
boot.img & build.zip = https://www.androidfilehost.com/?w=files&flid=336916
GAPPS
13.0 = https://androidfilehost.com/?fid=14871746926876840643
CREDITS
crDroid devs
LineageOS Team
Alessandro Astone
SOURCE
device=https://github.com/LineageOS/android_device_google_coral
kernel=https://github.com/LineageOS/android_kernel_google_msm-4.14
vendor=https://github.com/TheMuppets/proprietary_vendor_google_coral
Click to expand...
Click to collapse
thaaaaaaaaaaaaaaaaaaaaaanks

can i just boot into twrp and install this firmware as usual? wipe system/wipe data/install crdroid/reboot? Or does it have to be done exactly as instructed?

very good
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

anonras said:
what the different with this version..?
link
Click to expand...
Click to collapse
This is the latest Android 13 (crDroid-v9.0 android 13.0), your link is the older 12.1 Android

vlbr said:
can i just boot into twrp and install this firmware as usual? wipe system/wipe data/install crdroid/reboot? Or does it have to be done exactly as instructed?
Click to expand...
Click to collapse
It might work, but stick with OP steps, those 110% WORK, but up to you. I gave up on TWRP when A/B partitions came out and chose to just stick with and use stock ROM recovery. That will always work, TWRP, maybe not so much, IDK, it might, but you wont get the same type of help if you choose your own path (TWRP).
Also, just an FYI on nomenclature, this isn't firmware, but ROM, firmware contains all partitions, drivers, ETC., this is just the OS (ROM).

Thank good bro. Please you can create a version same this version V9, but face id use camera, same same this version 7.2 so you made ( https://androidfilehost.com/?w=files&flid=333516). Because i not enough money to buy the normal 4xl, i just enough to buy one no face id. Thank you for your time

tonyhieu said:
Thank good bro. Please you can create a version same this version V9, but face id use camera, same same this version 7.2 so you made ( https://androidfilehost.com/?w=files&flid=333516). Because i not enough money to buy the normal 4xl, i just enough to buy one no face id. Thank you for your time
Click to expand...
Click to collapse
huh?

GROOVYJOSHCLARK said:
huh?
Click to expand...
Click to collapse
My 4XL can't face id 3d as normal different 4XL. So have a way to use face unlock, It's using font camera to use face unlock.

tonyhieu said:
My 4XL can't face id 3d as normal different 4XL. So have a way to use face unlock, It's using font camera to use face unlock.
Click to expand...
Click to collapse
Interesting, this is new to me (unable to scan face for a PX4), what type of pixel 4 XL is it then? Or are there hardware issues I missed? I cant comment on this fix (I am not the dev here) but I might be able to help you once I know the scope of work.

@putzwon, I have used this OS (ROM) since Friday, and thoroughly testing EVERYTHING! WOW, I am literally floored at how well EVERYTHING works!!
I have NO ISSUES, NO BUGS, NO SHOWSTOPPERS, nada. Even Now Playing works, I am floored by all of this! It is amazing, and I rarely say that about a ROM (with no bugs also being reported - at the same time), and as I noted earlier, in the past, cRdroid wasn't great for me (random bugs, and/or missing features I rely on). NOT this version, this version IS GREAT FOR ME, I have EVERY SINGLE possible tweak I want/need/use, PLUS functional services / RIL (Radio Interface Layer) I.E. CALLs/TXT/MMS, PLUS no bugs, or FCs, or anything that would keep me away!
Normally, I use LOS, and LOS only (while testing all other ROMs for users and myself), but always landing back with LOS, not this time! I am STICKING WITH cRdroid for the foreseeable future, it is my DailyDriver and will remain so until something changes (but doubtful at this point)!! I have everything I need, baked right into the ROM, so I don't even need my LSPosed modules (other than SafetyNetFix once ROOT'ng)!
EXTREMELY WELL DONE and THANK YOU FOR THIS ROM!!!! For the rest of XDA users, this ROM WORKS! It works EXTREMELY WELL, is bug-free (from my extensive testing and standpoint). I haven't found any bugs yet (not a single one)!

GROOVYJOSHCLARK said:
Interesting, this is new to me (unable to scan face for a PX4), what type of pixel 4 XL is it then? Or are there hardware issues I missed? I cant comment on this fix (I am not the dev here) but I might be able to help you once I know the scope of work.
Click to expand...
Click to collapse
Yes, this is a type of 4XL, it's cheaper to 20% .

Installed it yesterday and almost everything is working perfectly. The only feature that seems to be missing Soli which is a shame since it's a fun novelty.

best rom ever love you

thaaanks

Thanks for the rom. Perhaps anyone could advice me if there is an easy switch from LOS 20 to this rom? If possible I'd like to avoid installing all apps again ... including the "security" features for a couple of sensitiv apps like bank apps.
Perhaps someone knows if restoring a swiftbackup would work.
Thanks

ojessie said:
Thanks for the rom. Perhaps anyone could advice me if there is an easy switch from LOS 20 to this rom? If possible I'd like to avoid installing all apps again ... including the "security" features for a couple of sensitiv apps like bank apps.
Perhaps someone knows if restoring a swiftbackup would work.
Thanks
Click to expand...
Click to collapse
it is easy
i do it everytime I flash a custom rom
you need to root your phone using magisk
then instal
Migrate - ROM backup 5.0.1​from play store
open it and take a full backup of your installed apps
copie this backup to your laptop
and after flashing this perfect rom
copie the backup from the laptop to the phone
and root the phone again
and instal
Migrate flasher​from play store
open it
and flash the file you backed up
this way you will have allll your apps including your banking apps with all your data
you will not have to instal anything twise...
good luck
it is easy
don't worry..