[ROM][11.0.0][TREBLE] LineageOS 18.1 DAILY (2022-01-20) - Lenovo Zuk Z2 Pro ROMs, Kernels, Recoveries, & Oth

[ROM][11.0.0][TREBLE] LineageOS 18.1 DAILY (2022-01-20) - Lenovo Zuk Z2 Pro ROMs, Kernels, Recoveries, & Oth

Hi!
I finally succeeded in having a recent rom on my Zuk Z2 Pro, with Treble. Fingerprints are working, Rooted OK with Magisk, Battery great. This guide can be used for other Treble roms.
Be advised, IT IS NOT EASY. But it's not THAT complicated either. Please read the whole post before attempting anything.
Pre-requisites :
1) twrp-3.2.3-1-z2_row.img installed as your recovery (higher versions are buggy with MTP)
2) Download Arrow-v11.0-z2_row-OFFICIAL-20200919-VANILLA.zip (or more recent)
3) Download lineage-18.1-20220120-UNOFFICIAL-treble_arm64_bvS-vndklite.img (or more recent) UNCOMPRESS IT IF IT'S A .IMG.XZ FILE.
4) Download Magisk-v24.0.apk and rename it into Magisk-v24.0.zip
5) (Optional) Download OpenGapps PICO (Arm64, 11.0, Pico) Heavier versions are too big and won't install.
Installation :
1) Backup your phone. Do it.
2) Go to your recovery, and wipe :
- Dalvik/Art Cache
- Cache
- System
- Data
- Internal Storage
3) Plug your phone on your computer, and move all the files you downloaded on your phone.
4) Install (use install/install zip) Arrow-v11.0-z2_row-OFFICIAL-20200919-VANILLA.zip It will update the vendor partition, necessary to be Treble compatible.
5) Wipe cache/dalvik, Reboot System, go to settings, and save ONE fingerprint (it will allow you to use the fingerprints with the treble rom, very important)
6) Reboot to recovery, then flash (use install/install image)lineage-18.1-20220120-UNOFFICIAL-treble_arm64_bvS-vndklite.img to the System partition, then wipe Dalvik/Art Cache
7) Install (use install/install zip) Magisk-v24.0.zip (Don't wipe dalvik/art cache after)
8) Resize System Partition (Wipe->Advanced Wipe->Tick "System"->Repair of change File System->Resize File System)
9) Install (use install/install zip) opengapps pico (Don't wipe dalvik/art cache after)
10) Reboot System
11) Now the worst part : Registering the new GSF ID. It will take several hours. If you don't use OpenGapps, skip this part.
You might have non-stop annoying notifications about your device not being certified for play protect. Put your phone in "don't disturb" mode or you'll become crazy.
- Get your GSF ID. It will reset every time you reset your phone. I used Device ID, installed it by placing it on the phone when plugged in to my computer in recovery mode, then installed with the "Files" app on the phone.
- Then go to https://www.google.com/android/uncertified/ with your google account, and register your GSF ID.
- WAIT. It will take several hours.
- You might have to force stop and clear storage of those 3 apps : google play services,google play store,google services framework (Display system apps when browsing apps in settings)
You'll then finally be able to finish your phone configuration and restore your settings/apps.
12) Great! You now have to disable the 3 buttons navbar (because our phone already have the physical button for the navigation), you'll need magisk :
[MOD][Magisk] Disable Navbar For 3rd-Party Navigation Gestures
If you're like me, you like using a 3rd party navigation gesture app with the navbar hidden. In Android 11, google disabled wm overscan which makes it difficult to hide the navbar. Luckily, it's possible with Magisk and a little bit of...
forum.xda-developers.com
su (gain root access)
props (open the hideprops menu)
5 (Add/edit prop values)
n (New custom prop)
qemu.hw.mainkeys (the build prop for whether to include softkey navbar)
1 (sets the build prop to disable the softkey navbar)
y (yes to continue with defaults)
y (yes to reboot)
Choose late stage or else it won't work at reboot.
I had it for two weeks and didn't notice any bug. Very happy with it.

Great Work

Hi, thanks for sharing.
I have LineageOS 15.1 in my ZUK Z2 PRO but I was never able to install anything else.
I tried your procedure but I keep getting the "mount /vendor" error with twrp-3.2.3-1-z2_row version.
Tried a different TWRP and I got "success" in the logs installing everything but neither Arrow nor LineageOS will boot, I only get fastboot.
Tried also Arrow-v10.0-z2_row-OFFICIAL-20200831-VANILLA with lineage-17.1-20210808-UNOFFICIAL-treble_arm64_bvS and those also won't boot.
Also tried starting with TWRP-3.2.3-0929-ZUK_Z2_PRO-CN-wzsx150 and Z2121_CN_OPEN_USER_Q00030.1_O_ZUI_4.0.247_ST_181017_qpst in advance to Arrow and LineageOS and nothing boots.
Had to restore from TWRP.
Any advice please?
Is my hardware different from yours or something?
Logs saying "success" are leaving blind and with no ideas here.
Thanks a bunch, take care.

I would stick to twrp 3.2.3.1, what is your "mount/vendor" error exactly, and when does it happen ? Did you try to go into twrp/mount and tick the vendor partition before ?
Flashing ZUI should restore your vendor partition.
You could also just try ArrowOS 10 (just flash it after wiping caches/system/data), without a treble rom on it, it's a good rom, coming from lineageOS 14.1, and a much simpler install.

Starting from actual LineageOS 15.1 and following your procedure step by step, Arrow10 fails with error "Failed to mount '/vendor' (Invalid argument)" at the beginning and at the end of the installation. I read this is a known issue with TWRP, maybe just with ZUK Z2 PRO. I guessed this is way I had to stay with 3.2.1-0 back when I got LineageOS 15.1 to work.
At the moment, after the restore, I don't have the /vendor folder at all and I didn't find any issue so far after restoring last night.
If I understood you correctly, I tried yesterday flashing Z2121_CN_OPEN_USER_Q00030.1_O_ZUI_4.0.247_ST_181017_qpst and it didn't boot as well.
I tried Arrow10 (with different TWRP so I wouldn't have the TWRP so called known issue) so that I could reproduce your step 5) regarding the fingerprint but no joy, won't boot even though TWRP for Arrow10 said SUCCESS.
My phone was ordered from China a few years ago, is it possible that I am experiencing an hardware incompatibility?
Sorry and thanks again.

Tried again with Z2121_CN_OPEN_USER_Q00030.1_O_ZUI_4.0.247_ST_181017_qpst and if I try to mount vendor and/or factory I can see both full of stuff in Advanced \ File Manager but those won't show in Wipe.
Tried this ZUI, Arrow, Lineage16, Kang, AospExtended, nothing boots.
Back to LineageOS 15.1 with no updates ;(

pringau said:
Tried again with Z2121_CN_OPEN_USER_Q00030.1_O_ZUI_4.0.247_ST_181017_qpst and if I try to mount vendor and/or factory I can see both full of stuff in Advanced \ File Manager but those won't show in Wipe.
Tried this ZUI, Arrow, Lineage16, Kang, AospExtended, nothing boots.
Back to LineageOS 15.1 with no updates ;(
Click to expand...
Click to collapse
Have you flashed factory to vendor?

I did yes, I used factory2vendor_z2_row.zip and didn't noticed any difference to neither new ROM nor LineageOS 15.1 if for example I install it without Restore. Meaning that new won't boot at all and LineageOS 15.1 works correctly with fresh or restored data.

Ok, so I guess I could try to delete all my spam here and just say THANK YOU.
But I believe trying and failing is learning.
Your guide is correct but I assumed that I could resolve any missing pieces flashing Z2121_CN_OPEN_USER_Q00030.1_O_ZUI_4.0.247_ST_181017_qpst with TWRP, because TWRP was not throwing any error.
I did flash it with QFIL and everything after is just following your guidance.
My bad by not doing it earlier, before coming here, but I don't have Windows at hand and QFIL with VM is tricky while passing the USB device.
You guys rock, long live to those who share.
Take care.

Hi, issues found:
SELinux shows Disabled. I believe this is the reason why I can't get some banks to work and get Failed on SafetyNet Status. getenforce says permissive, if I try to setenforce 1 the device shuts down.
Hotspot doesn't seem to work. It switches On and changes to Off and it says Error in the status.
Selecting second SIM Card seems impossible while texting SMS. If set to Ask every time SMS won't send saying No preferred SIM selected for sending SMS messages (weird, found the same in other ROMs - why Android 11 has Ask every time if it is not usable). I later found that to select a different card you should touch the name of the card (on the left of the circles) and not the numbered circle itself - which was what I was doing in LineageOS 15.1 if I remember correctly.
{
"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"
}
Gave it a try to ArrowOS 11 (official), hotspot bug was also there.
Jumped to AOSPExtended 8.4 (official) and no bugs found so far, hotspot working, banks working and ZUK Z2 PRO key working out of the box.
[EDIT] AOSPExtended 8.4 (official) has some bugs. Will try AOSPExtended 9 once there is a version without gapps.

Hello!
I'm right now following this guide on my device, and I get the following errors when trying to flash Arrow v11 using TWRP:
Updating partition details...
Failed to mount '/vendor' (Invalid argument)
...done
…
Patching vendor image unconditionally...
E2001: Failed to update vendor image.
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/.Z2 Pro OS & system files/Arrow-v11.0-z2_row-OFFICIAL-20200919-VANILLA.zip'
Updating partition details...
Failed to mount '/vendor' (Invalid argument)
...done
So well, there's something wrong with my partitioning, I mean, there's no /vendor partition in my device, or the problem is there for some other reason. How can I fix this? By installing factory2vendor.zip? 0K, done; didn't work at all.
I need to somehow manage to flash Z2121_CN_OPEN_USER_Q00030.1_O_ZUI_4.0.247_ST_181017_qpst, then.

Related

[TWRP][64 bit][3.2.1_r12][UNOFFICIAL]Moto Z2 Play[Albus]

TWRP 3.2.1_r12 Moto Z2 Play (albus)
{
"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 changelog : Here
Working/Bugs : Need to press power button two times for touch to work
Please do read the installation guide note !
IMPORTANT NOTE :
1. At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) . To avoid this you have to flash either SuperSU or flash any of the verity disabler zips there in xda
2. Encryption is enabled by default
3. If in case decryption doesn't go fine, twrp will popup a dialog box asking for password and that means decryption went wrong and you would need to wipe data once via twrp wipe options and reboot back to twrp for functioning of /data
Installation Guide :
1. Make sure you have unlocked bootloader
2. Reboot to bootloader
3. fastboot flash recovery twrp-xxxx.img (if you want permanent flash) or
fastboot boot twrp-xxxx.img (if you want temporary boot)
Download Link :Here
Tree : Here
XDA:DevDB Information
TWRP-ALBUS, Tool/Utility for the Moto Z2 Play
Contributors
rahulsnair
Source Code: https://github.com/TeamWin
Version Information
Status: Beta
Created 2018-01-03
Last Updated 2018-02-03

I've been using this today to set up my phone fresh. I created a backup, installed stock twrp flashable rom, installed magisk, and magisk module zips all just fine.
Thanks for this.

Trying to set up my new Moto Z2 Play today.
I just unlocked the bootloader, so I'm good there. I wanted to install Magisk and leave it mostly stock. If I was going to just "fastboot boot twrp.img'' (instead of flashing) can I use this TWRP or should I just follow the instructions and use the TWRP version in this other thread?
Is this version more functional?
Would I be able to make a backup if I boot the TWRP instead of flashing?
Can I use the SD Card/internal storage with this version or do I have to still use the OTG cable and a flash drive to hold the DM Verity and Magisk ZIPs?

Hi,
I tried several times to backup my StockROM before modification, but TWRP always stuck at "Updating Partition Details". Any ideas what to do to solve this Problem? By the way, I just booted into TWRP, didn't flash it to my device. Thx

JRapsky said:
Hi,
I tried several times to backup my StockROM before modification, but TWRP always stuck at "Updating Partition Details". Any ideas what to do to solve this Problem? By the way, I just booted into TWRP, didn't flash it to my device. Thx
Click to expand...
Click to collapse
my experience is, you have to flash TWRP.
I don't think it has the necessary read/write permissions to do a full backup otherwise.

3.1.2_r18 version released. Check download link in OP

hi guys.
I successed to twrp temporary boot.
Successed to full backup (with all check).
Is it safe for permanent flash twrp right now?
p/s: After backup success, I reboot my phone and check TWRP folder but nothing here
so why?

fastboot boot twrp-xxxx.img
freeze at teamwin logo
O flash twrp and its ok

rodacoregio said:
fastboot boot twrp-xxxx.img
freeze at teamwin logo
Click to expand...
Click to collapse
Twrp temporary boot works fine for me.
Some guys said install it can fix your problem.

I'm trying to flash, but it show me
(bootloader) Image not signed or corrupt
But Temporary boot works fine, how do I fix that.
Bootloader was unlocked.
On restarting, it show me BAD KEY. is it normal?

Mark2014 said:
I'm trying to flash, but it show me
(bootloader) Image not signed or corrupt
Temporary boot works fine, how do I fix that.
Bootloader was unlocked.
On restarting, it show me BAD KEY. is it normal?
Click to expand...
Click to collapse
That's normal,
TWRP isn't 'signed' by MOTOROLA.
Just reboot and enjoy.

kewlzter said:
That's normal,
TWRP isn't 'signed' by MOTOROLA.
Just reboot and enjoy.
Click to expand...
Click to collapse
It show me No command when i reboot to recovery mode by command
adb reboot recovery
was I wrong somethings ?
OS's still boot fine.

Mark2014 said:
It show me No command when i reboot to recovery mode.
was I wrong somethings ?
Click to expand...
Click to collapse
Flash TWRP again. it didn't take.
I flashed it three times in a row.
that "no command" with Robot, is the stock recovery.

kewlzter said:
Flash TWRP again. it didn't take.
I flashed it three times in a row.
that "no command" with Robot, is the stock recovery.
Click to expand...
Click to collapse
tks. it works.
I trying format Internal Memory: TWRP ->Wipe Memory -> Format Data; write "yes"
, but its show Failed
Àfter that, I check Internal Memory and it's empty.
I want to flash [ROM][UNOFFICIAL][64Bit][11-Mar]LineageOS-15.1[Albus][Moto Z2 Play]
in https://forum.xda-developers.com/z2-play/development/rom-lineageos-15-1-t3731228
Now can I continues flash that ROM copied in SD card?

Mark2014 said:
tks. it works.
I trying flash Internal Memory: TWRP ->Wipe Memory -> Format Data; write "yes"
, but its show Failed
Àfter that, I check Internal Memory and it's empty.
I want to flash [ROM][UNOFFICIAL][64Bit][11-Mar]LineageOS-15.1[Albus][Moto Z2 Play]
in https://forum.xda-developers.com/z2-play/development/rom-lineageos-15-1-t3731228
Now can I continues flash that ROM in SD card?
Click to expand...
Click to collapse
Did you do a FULL backup including your EFS?
IF so try it and see, I haven't tried the Lineage build yet, still too many bugs.
but so long as you backup you shouldn't be afraid to explore.

kewlzter said:
Did you do a FULL backup including your EFS?
IF so try it and see, I haven't tried the Lineage build yet, still too many bugs.
but so long as you backup you shouldn't be afraid to explore.
Click to expand...
Click to collapse
Tks. I did a full backup .
tks again.
I will try now.

I make a full backup, so can I restore that backup file after LineageOS?

This works when go command fastboot boot .... ?

I'm having an issue... I've successfully flashed r18, but it cannot seem to mount the data partition. It fails to mount (just hangs for a moment when you check the box next to data), fails to wipe (Could not mount/data and unable to find crypto footer... Failed to mount '/data' (Invalid argument)).
Never mind... I just tried it a 3rd time and it worked. Not sure what's going on there.
**OK** Now, I've flashed the Unofficial LOS and OpenGapps from the thread by OP, following all instructions, and the phone boots to recovery every time I try to boot to system...

Recent success, z2 Play XT1710-06
Just to add to the success stories: A newly-purchased Moto z2 Play, variant XT1710-06 dual SIM, Android 7.1.1, RETLA release channel, build NPSS26.118-19-1-6. My object was to install root only, not (at this time) do any custom ROM flashes.
With this in mind: I used TWRP-3.2.1-0(Albus) after doing the initial bootloader unlock. Quirks noted during install was that I needed to repeat the 'fastboot flash recovery' option 3-4 times to get TWRP to stay put in the 'recovery' partition. Also, as an experiment, I tried renaming the TWRP image to 'recovery.img' (which seems to help).
Once TWRP was in place, I downloaded and installed the most current Magisk (v16). It worked perfectly, the first time, no issues at all (and it even knew to install its management app on its own). Despite my initial leanings, I chose not to try SuperSU due mainly to the developer changes at Chainfire HD (original developer retired, product bought up by some unnamed Chinese group).
Now I get to reinstall all my apps... (sigh). Such is the price of getting the phone we Really Want...
I hope this makes life easier for others.
Keep the peace(es).

[RECOVERY][OFFICIAL][3.6.1-x] TWRP for Galaxy S9 and S9+ 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"
}
Official TWRP 3.6.1-* For Galaxy S9/S9+ ExynosOnly for exynos variants - G960F (Europe, Global Single-SIM); G960FD (Global Dual-SIM); G960N (South Korea); G965F (Europe, Global Single-SIM); G965FD (Global Dual-SIM); G965N (South Korea);
Disclaimer
I am 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 recovery 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.
Features:
Code:
- built from Android 10 kernel source
- built from android-9.0 recovery sources
- built in full 64 mode
- fully compatible with Android 9.0/10.0
Downloads:
S9 - https://twrp.me/samsung/samsunggalaxys9.html
S9+ - https://twrp.me/samsung/samsunggalaxys9plus.html
Instructions:
Odin
Download latest Odin zip from downloads.corsicanu.ro/samsung
Download and install Samsung Drivers (if you have them installed you can skip this step)
Go to settings/Developer options and enable OEM unlock (If you don't see developer settings, go into Settings/About phone/Software info and tap "Build number" 10 times to show Developer options menu)
Download TWRP_*.tar
Switch off the phone
Use Bixby Key+Volume Down+Power to enter Download Mode and connect the device to usb
Open Odin and untick autoreboot in "options" tab. Also make sure that your device is detected
Put TWRP_*.tar.md5 file into AP tab
Click Start
When Odin shows "PASS", take your device in hands, disconnect the usb cable and press simultaneously the "Bixby key" + "Vol. Down" + "Power" buttons until the downoad mode disappears
At the precise moment the screen becomes black, immediately release the "Vol.Down" button and press the "Bixby key" + "Vol. UP" + "Power" buttons during 10 to 15sec to forcefully enter TWRP
If it didn`t worked, redo the steps from #1 more careful this time.
TWRP
Download TWRP_*.img, push it into phone storage, choose install image in your current recovery, navigate to downloaded *.img file, select it, select to flash as recovery.
After booting in TWRP download and flash no-verity-opt-encrypt-6.1 zip to disable data partition encryption
If for any reason you fail to install TWRP multiple times/different methods, make sure you check this thread
Sources:
S9 Device tree - https://github.com/TeamWin/android_device_samsung_starlte
S9+ Device tree - https://github.com/TeamWin/android_device_samsung_star2lte
Kernel - https://github.com/corsicanu/android_kernel_samsung_universal9810/tree/android-9.0
Recovery - https://github.com/omnirom/android_bootable_recovery
Credits:
TeamWin, jesec, geiti94, dyneteve, testers, donors and anyone else involved in making this possible

Misc links:
TeamWin official website
Telegram Support Group
Telegram Channel
Bootloaders / modems zips
Latest Magisk stable or canary

FAQ / Further reading
Q: TWRP can't mount data partition, what to do?
A: Make sure you formatted data partition.
Q: Phone is not booting even after 20 minutes
A: Try to reboot. If still not booting, make sure you formatted data partition.
Q: How to format data partition?
A:
Q: Phone is showing only Samsung logo
A: Try to reboot. If still not booting, consider installing an older TWRP build or a more recent firmware.
Q: I get "Failed to mount /preload message", what to do?
A: From wipe menu select Advanced Wipe, select preload partition to be wiped and reboot recovery.
Q: Why do i need to format data partition?
A: Because old rom encrypted your data partition and new rom can't decrypt and use that content / root needs access to data partition to place misc files / phone not booting after flashing root until data partition gets formatted.

First:laugh:
Nice af!

support f2fs？

Many Thanls bro ?

Thanks

Congratz Corsi
Thanks for your hard work?

Data decryption working?

thank you bro its working well
but when i go to TWRP i fount the data still encrypted and cannot be mounted although i did full data format and wipe. everytime i need to use TWRP i need to format data.
any solution around?
thanks

Is the issue described here:
https://forum.xda-developers.com/showpost.php?p=81072679&postcount=1832
fixed with this release?

jamaljmys said:
thank you bro its working well
but when i go to TWRP i fount the data still encrypted and cannot be mounted although i did full data format and wipe. everytime i need to use TWRP i need to format data.
any solution around?
thanks
Click to expand...
Click to collapse
I think I have a similar problem. These were my steps:
flashed TWRP through Heimdall
booted into TWRP
wiped data
flashed the no verity opt encrypt zip
flashed LineageOS (official nightly from May 1st), gapps and Magisk
After that I booted the system and encryption was forced during boot. When I rebooted into recovery I was prompted to enter the password, which was not successful (decrypt failed because it took too long).
Before all that I was running an official and up-to-date Android 10 Samsung (April security patch).

Hi. I need emergency help. I'm new on s9+ & flashed twrp as well formatted data partition then flashed no-verity-opt-encrypt-6.1 but whenever entered to system then returned to recovery mode then i lost internal storage again again & again. Please help me. I'm on latest android 10 firmware.

Hi ?
Will you update the SHRP to latest TWRP Base ?
And will be very good if you will support the Orange Fox Recovery
I like those two recoveries because of password protection and they have more features…
Thanks for your work for our devices!

Seems the dl link isn't working. I tried connecting to the dl site on my phone and my PC and both returned with a "This site can't be reached" error.
I just tried contacting TeamWin through the contact form on the TWRP website and it seems as though the submit file for the form was deleted.

Could I live WITHOUT disabling encryption via flashing no-verify? I want to have my /data encrypted.

Hi Mate just wondering would this working with a Samsung Galaxy S9 plus
Model SM-G96F
Android version 10
One UI version 2.1
Cheers

Dan Ger said:
Lineages os not support encryption ..so that why you have it problem like that...feel free to check on telegram support group So you will understand
Click to expand...
Click to collapse
So are you saying that LOS does not support disabling encryption? I tried the whole procedure multiple times and it seems that the patch fails because the fstab entries are not found in LOS.
Could an encrypted data partition cause issues recognizing the sim card? I find this hard to imagine, but I have both issues pretty persistently.
Cheers

The OP says:
Download TWRP_*.tar
Switch off the phone
Use Bixby Key+Volume Down+Power to enter Download Mode and connect the device to usb
Open Odin and untick autoreboot in "options" tab. Also make sure that your device is detected
Put TWRP_*.tar.md5 file into AP tab
I've downloaded twrp-3.3.1-1-starlte.img.tar (as recommended elsewhere for my S9) but how do I do the last part?
What is TWRP_*.tar.md5 file? How do I get it?

Is there anyone who got TWRP 3.4.0 working with encryption on a Samsung Galaxy S9?
My experiences after 1 hard week:
1. On Stock: TWRP always showed an unlock option via PIN, but it was never able to decrypt (neither default_password, nor disabling lockscreen, nor setting another PIN/Password in locksetings helped)
2. On Magisk: TWRP never showed an unlock option & was never able to decrypt
3. Only option was to disabled encryption --> the old encryption disabler from OP doesn't work, updated Disable_Dm-Verity_ForceEncrypt_03.04.2020 has to be used ( https://forum.xda-developers.com/an...rceencrypt-t3817389/post77091359#post77091359 ) --> patter lock & fingerprint cannot be used in the future
A little disappointing considering that the unlock option of TWRP & changelog suggests that decrypting should work.
@moocou
BTW: Put TWRP_*.tar file into AP tab

[9.0][TREBLE]PixelExperience / PixelExperience Plus Pie [UNOFFICIAL]

{
"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"
}
PixelExperience for Moto Z2 Play [albus]
What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Our mission is to offer the maximum possible stability and security, along with essential features for the proper functioning of the device
Based on Android 9.0
Install stock oreo before installing Custom ROMs, see notes below for further info
Whats working?
Wifi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
Fingerprint reader
NFC
Lights
Sound / vibration
Moto Mods/Moto Snaps
Encryption
FM Radio
Known issues
VoLTE/VoWIFI
Moto Snap Hasselblad Zoom Camera
Moto Snap Projetor is unknown to work
DON'T FLASH GAPPS, ALREADY INCLUDED
Download PixelExperience from AFH
Download PixelExperience Plus from AFH
Telegram channelD
Z2 Play Custom ROMs Group
Z2 Play Global Group
Instructions:
Always have a backup of the EFS partition made with TWRP stored somewhere, as you may lose IMEI. Restore it if you get 0 as IMEI when booted into the ROM.
Before installing, make sure oreo was the last stock ROM you installed. See notes below if you come from Stock Pie
Download Official TWRP from twrp.me
Flash the TWRP via fastboot
Enter TWRP, go to wipe menu and Wipe Dalvik, Cache, Data, System and Internal Storage.
In TWRP Wipe Menu, do Format Data, then reboot into recovery
Flash the latest build
Reboot
Notes
TWRP
If the touchscreen doesn't work when rebooting into recovery, press the power button twice to turn off and on the screen. The touchscreen will now work just fine.
GSIs
This LineageOS build ships with Project Treble compatibility (lite VNDK), meaning you can flash a GSI as System Image from TWRP. Please don't report GSI bugs here, report them instead to the GSI's maker. A Format Data from TWRP is required after flashing a GSI in order to avoid problems.
Technical details on our Treble implementation:
This device is a community-treble device, meaning other devs before us made it compatible with Project Treble (lite VNDK), using the oem partion as a vendor. GSIs still have some problems regarding cpu frequency scaling and camera. You have been warned.
Coming from stock pie?
For the sake of simplicity, I said that coming from stock oreo was needed. In reality you just need to flash the oreo modem files. There's a script that does exactly that, made by @juniorpassos: https://mega.nz/file/IRxjGDjL#vkdvh4JcMy-LuWgQz4rHhgpWV80029X4ql0_zcMpVug. The script will erase your userdata and cache.
Before starting this script, make sure you have a backup of your EFS partition stored somewhere safe, outside phone's internal storage. After the backup is done, you can reboot your phone into fastboot mode and start the script. Now reboot into TWRP, go into "Wipe" menu and Format Data. Now you can reboot into the ROM. If you get 0 as IMEI, or any other problem related to RIL, go into TWRP and restore the EFS backup made previously.
Wanna help?
If you find a problem or a bug, please share a logcat with us, alongside an explanation of the problem and steps to reproduce. We won't accept bug reporting without a logcat. Collect logcat with:
Code:
adb logcat -b all > logcat.txt
Thanks
Many thanks to @marcost22 for the pair-working we are doing in this adventure, to @davidsonsjesus for his work on KVT, to @jeferson1979 for his help and teaching. Thanks to all the testers that have helped us testing this ROM.
Sources
Device tree
Vendor tree
Kernel
ROM Source code: https://github.com/PixelExperience
ROM Developer: jhenrique09
XDA:DevDB Information
PixelExperience 9.0, ROM for the Moto Z2 Play
Contributors
EmaMaker, marcost22, rahulsnair, @erfanoabdi @vache @kubersharma @jeferson1979
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: ALBUS_OPS27.76-12-25_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC
Based On: PixelExperience
Version Information
Status: Stable
Current Stable Version: 9.0
Stable Release Date: 2020-09-27
Created 2020-09-27
Last Updated 2020-09-30

Reserved

Changelog
2020-12-08: Cleanup and uprev kernel (3.18.113->3
18.116). Update camera blobs: fix Electronic Image Stabilization, bring back laser focus sensor, fix recording in WhatsApp., fix issues with video recording in Snap cam Fix encryption and decryption (official twrp over at twrp.me is needed for this to fully work). SeLinux is now Enforcing. Update VNDK to full enforcement. Update graphics props. This is the final build for Android Pie 9.0. We will will soon start the Q bringup, and will not be building any Pie ROM anymore, unless some critical bug is discovered:
https://www.androidfilehost.com/?w=files&flid=317960
2020-09-26: Initial build https://www.androidfilehost.com/?w=files&flid=317960

Great! The Z2 is still alive! What's the diference between the normal and the plus version?

Failed to mount '/data' (Invalid argument)
...done
Unable to mount storage

OldUncle said:
Failed to mount '/data' (Invalid argument)
...done
Unable to mount storage
Click to expand...
Click to collapse
Enter TWRP and Format Data, then reboot to TWRP again. You may need to repeat this a couple of times

ramelco said:
Great! The Z2 is still alive! What's the diference between the normal and the plus version?
Click to expand...
Click to collapse
Normal version is plain PixelExperience. Plus version includes some tweaks we all like: a bit of customization for status bar and themes (dark theme included for system and notifications!), some gestures like the three-finger-screenshot, advanced restart and others. I think you can find more info on the PE website

when i flash and then boot to system, it prompts me to enter a password, but...i don't have one.
edit: i have not gotten it to work. i just reflashed it.
when i did that, i wiped the cache and dalvik and all that, but rebooted back to bootloader, then ran the script (i came from 9.0 stock), and it flashed, everything rebooted, i got into the phone, and it doesn't think there's a cellular signal. the IMEI seems fine, it's the right string of numbers, but nothing i do will get it to actually register the sim is in.. or rather, it does read the sim. it knows what phone number is on it, but absolutely nothing else.
is this a case where i have to restore me EFI? when i try to do that, it tells me i failed to select a partition, but there's no partition to actually select...

Tried re installing the script? Or flash the oreo modem file via fastboot

ramelco said:
Tried re installing the script? Or flash the oreo modem file via fastboot
Click to expand...
Click to collapse
yeah. i tried that, and then i even went back to stock 9.0 (no idea how to go back to 8, i've tried just flashing normally through fastboot like you do for 9, but it just doesn't work), flashed the 8.0 modem, nada. even on stock 9 i my cellular radio just doesn't seem to work.
in twrp, when i go to restore my EFS backup, it complains that there was no partition selected, but i don't actually get a partition to select. i honestly have no idea what the hell i did to achieve this, but i did.
edit: i was able to get the radio working in stock pie, by fastboot loading erase modemst1/st2 but that doesn't appear to work on this rom
edit 2: let me describe the steps i'm taking here. i boot into twrp, i wipe dalvik/cache, cache, system, data, storage, reboot back into twrp, format data and reboot back into twrp. flash the rom, reboot to bootloader, run the script, boot back into twrp and flash data.
i don't see anything i'm doing wrong, but maybe i am?

likehelly said:
yeah. i tried that, and then i even went back to stock 9.0 (no idea how to go back to 8, i've tried just flashing normally through fastboot like you do for 9, but it just doesn't work), flashed the 8.0 modem, nada. even on stock 9 i my cellular radio just doesn't seem to work.
in twrp, when i go to restore my EFS backup, it complains that there was no partition selected, but i don't actually get a partition to select. i honestly have no idea what the hell i did to achieve this, but i did.
edit: i was able to get the radio working in stock pie, by fastboot loading erase modemst1/st2 but that doesn't appear to work on this rom
edit 2: let me describe the steps i'm taking here. i boot into twrp, i wipe dalvik/cache, cache, system, data, storage, reboot back into twrp, format data and reboot back into twrp. flash the rom, reboot to bootloader, run the script, boot back into twrp and flash data.
i don't see anything i'm doing wrong, but maybe i am?
Click to expand...
Click to collapse
Why would you go back to stock pie, when the instructions clearly say stock Oreo. There's a tutorial on the forums and everything, flashing any version of stock is the same procedure, you just need the specified Oreo version listed in the firmware section of the OP. Not that hard

[ROM][UNOFFICIAL][gta4xl/gta4xlwifi][11] LineageOS 18.1 for Galaxy Tab S6 Lite

CHANGELOG
2021-01-23
Changelog was moved to github pages: https://lineage.linux4.de
2021-01-16
Fixed hotspot
2021-01-15
Fixed wifi direct
2021-01-07
Update to Linux 4.14.213
2021-01-05 system securitypatch
2020-12-01 vendor securitypatch
Improved BT audio quality (BT audio HAL v2)
Improved performance and batterylife
2020-12-12
Update to Linux 4.14.210
Add glove mode / high touch sensitivity mode
2020-12-05 system securitypatch
2020-11-24
Enable MAC randomization again
Netflix now works without liboemcrypto disabler (L3 only, Samsung doesn't seem to allow L1 with custom ROM installed)
Fixed small UI lags
2020-11-01 vendor securitypatch
2020-11-19
Fixed RIL on LTE variant
2020-11-18
Initial release

reserved

Reserved

Linux4: Tried to install last night; wiped data and cache per the instructions and checked that /data was ext4. Flash failed with errors "failed to mount /odm (invalid argument) ', with similar errors for /product and /vendor, and I believe /system_root as well. Tried reformatting partions (except storage partitions) and full factory reset, all ending in the same errors described above. Rebooting defaulted into fastboot mode. I reflashed 17.1 and everything worked, and now back to normal. NB: I'm not a developer, and still in the process of learning the ins and outs of Android. Again, thank you for your work on this ROM!

Chnouphi said:
Linux4: Tried to install last night; wiped data and cache per the instructions and checked that /data was ext4. Flash failed with errors "failed to mount /odm (invalid argument) ', with similar errors for /product and /vendor, and I believe /system_root as well. Tried reformatting partions (except storage partitions) and full factory reset, all ending in the same errors described above. Rebooting defaulted into fastboot mode. I reflashed 17.1 and everything worked, and now back to normal. NB: I'm not a developer, and still in the process of learning the ins and outs of Android. Again, thank you for your work on this ROM!
Click to expand...
Click to collapse
Installation Lineage OS 17.1/18 and bitgapps
1) Boot TWRP ( #twrp3.4.0-3-wifi , #twrp3.4.0.3-lte )
2) Wipe - > Format Data - > yes
3) Install LINEAGEOS 17.1/18.0
4) Wipe Cache/Dalvik
5) Reboot System
6) Install bitgapps Q/R (#bitgapps)
7) Wipe Cache/Dalvik
8) Reboot
9)Enjoy Enjoy
Did you do it that way???
And which twrp did you use?
I have installed both variants, unfortunately don't check out at xda so often, if any questions are happy to report via Telegram (Support Group)

Up to step 3, which is where the errors occurred. Progressing beyond that did not appear to be an option.

Chnouphi said:
Up to step 3, which is where the errors occurred. Progressing beyond that did not appear to be an option.
Click to expand...
Click to collapse
Try the wipe, a reboot into recovery and flashe then....
Can you take a screenshot of twrp? After you press down on the 3 strokes and the changelog is displayed there?

mu1989 said:
Try the wipe, a reboot into recovery and flashe then....
Can you take a screenshot of twrp? After you press down on the 3 strokes and the changelog is displayed there?
Click to expand...
Click to collapse
Thanks mu1989. I will give this a try later today and let you know.

I tried to install Lineage 18 several times, but failed.
I'm on latest TWRP v.3.
Changed /data to Ext4 partition
Factory reset
Format data ->yes
reboot recovery
Install lineage 18 from external SD-card
Reboot system.
After 1 failed boot, system boots into TWRP again.
When installing Lineage again, TWRP gives message in red text "Android Rescue Party trigger! Possible solutions? Either:
1. Wipe caches, and/or
2. Format data, and/or
3. Clean flash your ROM.
The reported problem is:
"-reason=set_policy_failed:/data/app'

Iceman66 said:
I tried to install Lineage 18 several times, but failed.
I'm on latest TWRP v.3.
Changed /data to Ext4 partition
Factory reset
Format data ->yes
reboot recovery
Install lineage 18 from external SD-card
Reboot system.
After 1 failed boot, system boots into TWRP again.
When installing Lineage again, TWRP gives message in red text "Android Rescue Party trigger! Possible solutions? Either:
1. Wipe caches, and/or
2. Format data, and/or
3. Clean flash your ROM.
The reported problem is:
"-reason=set_policy_failed:/data/app'
Click to expand...
Click to collapse
This is because TWRP doesn't wipe /data/media and other things, someone at TWRP might have thought it would be a good idea to make factory reset not wipe everything but it completely breaks FBE.
You could run rm -rf /data/* (will really delete everything on /data) from TWRP shell to fix this problem, I will upload lineage recovery builds later/tomorrow with which this will not happen.

Thx, that did the trick.
Rooted with Magisk 21.1 Beta, did not pass Safetynet.

Iceman66 said:
Thx, that did the trick.
Rooted with Magisk 21.1 Beta, did not pass Safetynet.
Click to expand...
Click to collapse
1) install Magisk Hide props
2) open terminal
3) su
4) 1 edit device fingerprint
5) f pick a certificated fingerprint
6) search one plus (21)
7) I took the one plus 8t (android 11) (44)
8) y and y
8) Reboot
Look afterwards if magisk hide is activated and magisk is hidden

Mine says only official released binaries are allowed to be flashed (recovery) on the twrp step.

pyst2 said:
Mine says only official released binaries are allowed to be flashed (recovery) on the twrp step.
Click to expand...
Click to collapse
Have you installed lineage recovery?
When you make the sideload, you need to confirm the installation on the tab,
There is a window at the top where you can choose yes or no

Hello all. Tried flashing again, with identical results described previously. Booted to TWRP 3.4.0, then factory reset followed by format data - - > yes, rebooted into recovery, then tried flashing 18 (not directly after wiping like I did before). Same 'failed to mount /odm (etc), invalid arguement' errors. (Sorry, neglected to do a screen grab.)

Twrp is not so confident, please use Lineage Recovery for the installation process.
the installation then takes place via adb sideload

Chnouphi said:
Hello all. Tried flashing again, with identical results described previously. Booted to TWRP 3.4.0, then factory reset followed by format data - - > yes, rebooted into recovery, then tried flashing 18 (not directly after wiping like I did before). Same 'failed to mount /odm (etc), invalid arguement' errors. (Sorry, neglected to do a screen grab.)
Click to expand...
Click to collapse
Did you perform the trick of @Linux4 in the terminal?

Chnouphi said:
Hello all. Tried flashing again, with identical results described previously. Booted to TWRP 3.4.0, then factory reset followed by format data - - > yes, rebooted into recovery, then tried flashing 18 (not directly after wiping like I did before). Same 'failed to mount /odm (etc), invalid arguement' errors. (Sorry, neglected to do a screen grab.)
Click to expand...
Click to collapse
c
It seems that TWRP doesn't clean the /data/ partition well.
Linux4 gave a tip:
In TWRP, got to advanced->terminal-> type rm -rf /data/* enter, and proceed with installing Lineage 18.

You can also try to get from the original to Lineage 18.0, then twrp would also have to delete everything

[RECOVERY][UNOFFICIAL][3.5.2] TWRP for Galaxy M31

{
"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"
}
Disclaimer:
I am 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 recovery 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.
Kernel Features:
latest kernel source release
disabled security stuff/knox/proca/logging/audit/useless features
Recovery Features:
TWRP 3.5.2, Android 10
Built in 64-bit mode
Super partition support
Added custom super binary to help with managing super partitions ( more on that in post #3 )
Native rw mount dynamic partitions
Native GSI flashing
Native dynamic partitions resize/wipe/backup/restore
Working MTP and ADB only!
How to install?
Spoiler: ODIN(Windows)
Prerequisites: Samsung USB drivers, Odin v3.14.1
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Press the volume down + volume up button whilst the phone is connected to a pc to boot in download mode;;
Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol down + bixby key + usb cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, factory reset data and redo from step 5!
Download TWRP.tar from download link below;
Open odin and place the TWRP.tar file in AP slot and press start. Once you press start, keep holding power and volume up button and the device will reboot to recovery mode.
* If you're coming from stock, go to "Wipe" > ""Format Data" > type "yes" to format data. If you skip this Internal storage won't work in TWRP
Flash the encryption_disabler.zip from the link below to disable internal storage encryption and patch stock recovery restoration.
Additionally, flash TWRP_Bootlogo_patcher to patch warning screens when booting the device.
If you want to root, flash Magisk.
Spoiler: TWRP
If you're coming from other TWRP versions, download TWRP.img, reboot to recovery, tap Install > Install Image > Navigate to downloads folder > select TWRP.img > Select Recovery and swipe to confirm flash. Go to reboot and reboot to recovery and the changes will have taken place.
Downloads:
TWRP-3.5.2-m31-v1.0
Encryption Disabler
TWRP_Bootlogo_patcher
Sources:
Device Tree: https://github.com/soulr344/android_device_samsung_m31
Kernel Source: https://github.com/soulr344/android_kernel_samsung_m21nsxx/tree/prebuilt
TWRP Source: https://github.com/soulr344/android_bootable_recovery/commits/android-10.0
Credits:
TeamWin, corsicanu, ananjaser1211, jesec, epicX67, exynos-nigg, testers and anyone else who made this possible.

Changelog:
v1.0
Initial Release
More in github release page
MISC LINKS
Telegram Channel
Telegram Group
TeamWin Official Website

FAQ
Q: TWRP can't mount data partition, what to do?
A: Make sure you formatted data partition.
Q: Phone is not booting even after 20 minutes
A: Try to reboot. If still not booting, make sure you flashed encryption disabler zip / formatted data partition.
Q: How to format data partition?
A:
Q: Phone is showing only Samsung logo
A: Try to reboot. If still not booting, consider installing a more recent firmware. If you still don't succeed, post here some details about your device and previous firmware and we might be able to help.
Q: Why do i need to format data partition?
A: Because old firmware encrypted your data partition and new rom can't decrypt and use that content / root needs access to data partition to place misc files / phone not booting after flashing root until data partition gets formatted.
Q: I can't flash anything with TWRP. Internal Storage has some random folders with weird name.
A: Format Data and flash encryption disabler.

Info about custom super partition helper binary. (Irrelevant because of native logical partitions but yeah, its present)
It's meant to help with managing partitions inside the super partition itself. It has some functions built in like mount, unmount, flash and format. Here is a brief rundown on what each of them do.
Partitions that are supported are:
system, system_root, vendor, odm, product
Click to expand...
Click to collapse
Please note that system_root is an alias of system and umount is an alias of unmount.
All of these commands are runnable through TWRP Terminal ONLY!
Code:
super mount partition
This will mount partition in rw mode in mountpoint in fstab.
Code:
super unmount[or umount] partition
This command will unmount given partition and make it read only.
Code:
super format partition
This command will format given partition as ext4 inside super partition.
Code:
super flash partition /path/to/image.img
Flashes image.img to partition.
You can also flash GSI (Generic System Image) using this command. Simply run:
Code:
super flash system /path/to/gsi.img
For Custom ROM Developers:
You can use this as an alternative to mount/format/unmount partitions that are inside super partition normally.
Code:
run_program("/sbin/super", "format", "system"); # formats system
run_program("/sbin/super", "mount", "system"); # mounts system as rw
run_program("/sbin/super", "unmount", "system"); # unmounts system and makes it ro

Hello there,
I followed all steps and in the end ended up having with the device only showing the Samsung logo after I flashed magisk (magisk version here: https://magisk.me/zip/). I had a 64gb version of the SM-M315 running the latest android 11 version provided by samsung (current date: 10.04.2021). I have not yet managed to escape the bootloop, veen when trying to restart the warnings appear and then the samsung logo displays. I have made a pre-root version backup, but have not yet managed to return to the recovery.
Edit: I am aware that I have might bricked my device and just wanted to ask if there is anything that I could do just in the case that my assumption is wrong.

Karen3443 said:
Hello there,
I followed all steps and in the end ended up having with the device only showing the Samsung logo after I flashed magisk (magisk version here: https://magisk.me/zip/). I had a 64gb version of the SM-M315 running the latest android 11 version provided by samsung (current date: 10.04.2021). I have not yet managed to escape the bootloop, veen when trying to restart the warnings appear and then the samsung logo displays. I have made a pre-root version backup, but have not yet managed to return to the recovery.
Edit: I am aware that I have might bricked my device and just wanted to ask if there is anything that I could do just in the case that my assumption is wrong.
Click to expand...
Click to collapse
nope, you havent bricked. start by flashing stock rom again, the flash twrp, AND BE SURE to flash encryption disabler and format data. thats all and it should boot. if you skip encryption dissabler, then the stock recovery will auto restore itself(which seems your case)

if i do this:
11* If you're coming from stock, go to "Wipe" > ""Format Data" > type "yes" to format data. If you skip this Internal storage won't work in TWRP
will i lose my data? because i dont have sd card so if i lose my data i wont be able to do the next steps.

Thanks. I successfully installed twrp and rooted my phone. I also successfully installed Encryption Disabler. But, unfortunately couldn't install TWRP_Bootlogo_patcher. Every time I try to flash it, it always ended with Error: 1, showing “device is not compatible.”
I am on latest one UI 3.1, which released just yesterday. Is this happening as my rom is too latest for ur supplied zip file? Hope, u will answer soon. Thanks again.
NB: I already formatted data by typing “yes”.

drcarlox said:
if i do this:
11* If you're coming from stock, go to "Wipe" > ""Format Data" > type "yes" to format data. If you skip this Internal storage won't work in TWRP
will i lose my data? because i dont have sd card so if i lose my data i wont be able to do the next steps.
Click to expand...
Click to collapse
yes, you'll lose your data. so, backup anthing important

Ahamadmusa said:
Thanks. I successfully installed twrp and rooted my phone. I also successfully installed Encryption Disabler. But, unfortunately couldn't install TWRP_Bootlogo_patcher. Every time I try to flash it, it always ended with Error: 1, showing “device is not compatible.”
I am on latest one UI 3.1, which released just yesterday. Is this happening as my rom is too latest for ur supplied zip file? Hope, u will answer soon. Thanks again.
NB: I already formatted data by typing “yes”.
Click to expand...
Click to collapse
tap tag on the github page of bootlogo patcher and download the latest version

soulr344 said:
tap tag on the github page of encryption disabler and download the latest version
Click to expand...
Click to collapse
Thanks, it worked. Now waiting for custom rom.

soulr344 said:
tap tag on the github page of encryption disabler and download the latest version
Click to expand...
Click to collapse
i'm getting 404 page not found error,can you provide link?

kogkita said:
i'm getting 404 page not found error,can you provide link?
Click to expand...
Click to collapse
ok found it by searching through google,thx buddy.

M31 Android 11 ONEUI 3.1 TWRP_Bootlogo_patcher couldn't install

If any custom rom comes for m31 in future,is there any possibility to decrease cpu and gpu voltage offsets?(custom kernel support ?)

dont work on android 10
w ont install any thing
w ont format partition
wont mont any partition
système data or cache or dalvik cache

zrekkab said:
dont work on android 10
w ont install any thing
w ont format partition
wont mont any partition
système data or cache or dalvik cache
Click to expand...
Click to collapse
it might be a mistake here(states android 10),but on telegram page it was mentioned android 11 only,try upgrading to 11 and flash,all modules perfectly worked for me.

ensonahmet said:
M31 Android 11 ONEUI 3.1 TWRP_Bootlogo_patcher couldn't install
Click to expand...
Click to collapse
htt ps :/ /github. com/corsicanu /TWRP_Bootlogo_patcher /releases/tag/ v1.3 ,remove the spaces and download this 1.3v file

Thanks
Now build v2

I solved the solution by installing the Indian version of SM-M315F INU M315F XXU2BUC1

Database Develop

welcome