Database Info

[Recovery][Unofficial] TWRP 3.0.2-C [r7plusf]

This recovery will work ONLY for the Snapdragon 615 version of Oppo R7 Plus!
Here is an update to my UNOFFICIAL TWRP 3.0.2
Everything works well, with one caveat: It will reboot as soon as the display times out. The workaround is simple: Go to settings and disable Screen Timeout.
The -C revision is just to remind me that the recovery it is build on CyanogenMod.
If you don't need encryption and don't care about wrong date/time in your backups, then the official twrp will be all you need.
{
"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"
}
Full Source: Github.​Old stuff:
My goal with this UNOFFICIAL twrp recovery is to enable encryption on Oppo R7Plus-f(Snapdragon) version.
Tested with AICP on MarshMallow. Full encryption support.
All hard work was done by the TWRP Team and the R7 kernel gurus at CyanogenMod.
I just made a few additions and changed the official TWRP kernel to the CM kernel using the AICP build system.
To get your Oppo R7Plusf encrypted, there are a few points you must follow.
Note1: This wil not work with ColorOS. The ROM must support encryption. ColorOS does not!
Note2: You will LOOSE ALL DATA if you choose to encrypt your R7Plusf.
Here is a small howto:
1. Boot to bootloader and flash TWRP-3.0.2.u
2. Boot to recovery
3. Choose A or B to backup your data
....A: Backup Data and copy it to PC (Internal Storage - TWRP/BACKUPS/xxxxxxxx/BackupName)
....B: Backup Data to the Micro SDcard (Now, be careful not to format the Micro SD)
4. Wipe -> Format Data (type YES and tap the OK/Enter button)
....This command is slow, have patience!
5. Reboot to android. The install wizard should show - be sure to create a PIN or Pattern kode during the setup.
6. Charge the phone to 90-100%
7. Open Settings/Security and -> Encrypt phone
8. Follow instructions
Click to expand...
Click to collapse
Now the device will reboot a few times and finally it will boot to the login screen and ask for your pin code.
All this will take time, have patience.
On my AICP ROM it sometimes "hang" when Finishing boot and make some tick sounds. Turning the screen off and on a few times will make it boot to the login and you can enter the PIN or Pattern. It will boot again and quickly get into your Android system.
Once booted to Android, everything is smooth and there are no more issues (at least not encryption related )
This is an issue with my AICP ROM only, CM13 start without issues.

...reserved...
Please share your experience here, if you choose to check out encryption on the R7+. Thanks.

Major Props ! Great job and you actually fulfilled a request of mine ! Thanks

I have followed the steps and @ step 5 I wasnt asked to enter any PIN , Im on CM13 latest nighly on october 31 and twrp 3.0.2 , any advise Please ?
is the backup step A or B optional or a must ?

midterm_2003 said:
I have followed the steps and @ step 5 I wasnt asked to enter any PIN , Im on CM13 latest nighly on october 31 and twrp 3.0.2 , any advise Please ?
is the backup step A or B optional or a must ?
Click to expand...
Click to collapse
It is 6 months since I tried. At that time I was asked for the pin. Don't know if that is different for the latest cm.
Note that this recovery is not perfect. It handles encryption well, but has a few issues. To avoid these, you can flash the official twrp from http://twrp.me, but don't format data - it will break encryption.
Maybe CyanogenMod recovery is fully functional now, then it might be a better choice. @maniac103 ?
Yes backup is optional. It is always your choice.

It was my mistake I selected wipe instead of format , it works now ! :good: do you know what other issues this recovery have as I want to keep
Thanks

Small update - read OP.

teemo said:
Small update - read OP.
Click to expand...
Click to collapse
I have recently done a complete new TWRP from scratch including:
- LineageOS kernel 3.10.104
- decryption using 7.1.1 LineageOS blobs
- included misc for 7.1.1
- overlay graphics support
- modem binary flashing support (no zip file required) just select non-hlos.bin from Oppo's stock ROM
- proper IMEI Partition Backup
- flashimage support in TWRP (just like fastboot)
- latest TWRP 3.0.3-0
If you would like to build one or want me to provide you a build let me know.
I pushed the repo here: https://github.com/Celoxocis/android_device_oppo_r7plusf
Of course I made it for the R7S but our two devices are almost identical so I made the necessary changes to create a R7Plus repo.
Let me know what you think.

celoxocis said:
I have recently done a complete new TWRP from scratch including:
- LineageOS kernel 3.10.104
- decryption using 7.1.1 LineageOS blobs
- included misc for 7.1.1
- overlay graphics support
- modem binary flashing support (no zip file required) just select non-hlos.bin from Oppo's stock ROM
- proper IMEI Partition Backup
- flashimage support in TWRP (just like fastboot)
- latest TWRP 3.0.3-0
If you would like to build one or want me to provide you a build let me know.
I pushed the repo here: https://github.com/Celoxocis/android_device_oppo_r7plusf
Of course I made it for the R7S but our two devices are almost identical so I made the necessary changes to create a R7Plus repo.
Let me know what you think.
Click to expand...
Click to collapse
That is simply brilliant
I just started syncing down LineageOS from scratch again. You say decryption is from LOS 14.1, but I assume you build twrp on cm-13.0.
Overlay: I have always been puzzled over the slow graphics on twrp. My old 2012 HTC is super smooth in the same recovery. I saw you discuss it somewhere, maybe on IRC you mentioned one drawback by running on overlay, but don't remember what it was ?
Modem flashing: That will be handy for testing stuff.
Proper IMEI, wasn't aware it was broken?
Flash image, another great feature, although easily done from Android as well. I have been a few times in recovery, wanting to just flash an image.
Big thanks for taking time to update plusf. I will check it out and return
EDIT: Built with following changes:
- All CyanogenMod repos changed to LineageOS in localmanifest
- kernel and dt replaced with my latest, as the supplied boots into fastboot
Will test the next few days.
Huge thanks @celoxocis

teemo said:
That is simply brilliant
I just started syncing down LineageOS from scratch again. You say decryption is from LOS 14.1, but I assume you build twrp on cm-13.0.
Overlay: I have always been puzzled over the slow graphics on twrp. My old 2012 HTC is super smooth in the same recovery. I saw you discuss it somewhere, maybe on IRC you mentioned one drawback by running on overlay, but don't remember what it was ?
Modem flashing: That will be handy for testing stuff.
Proper IMEI, wasn't aware it was broken?
Flash image, another great feature, although easily done from Android as well. I have been a few times in recovery, wanting to just flash an image.
Big thanks for taking time to update plusf. I will check it out and return
EDIT: Built with following changes:
- All CyanogenMod repos changed to LineageOS in localmanifest
- kernel and dt replaced with my latest, as the supplied boots into fastboot
Will test the next few days.
Huge thanks @celoxocis
Click to expand...
Click to collapse
Just the build tree is cm-13.0 but as you can see from the manifest everything that is required is from TWRP's Android 7.1. I.
I didn't want to test the build on an bleeding edge LineageOS 14.1 tree. As I wasn't sure about if it works and repo syncing the sources takes time.
Funny they boot into fastboot?
Kernel + DT.IMG were LineageOS 14.1 (7.1.1).
To my knowledge the kernel + DT.img are identical for the R7Plus,/R7S. The DT.img contains 15022 + 15018 as far as I know.
The only downside when using graphics overlay was that some users reported screenshot In recovery would not work. While I had one user report it works.

celoxocis said:
Just the build tree is cm-13.0 but as you can see from the manifest everything that is required is from TWRP's Android 7.1. I.
I didn't want to test the build on an bleeding edge LineageOS 14.1 tree. As I wasn't sure about if it works and repo syncing the sources takes time.
Funny they boot into fastboot?
Kernel + DT.IMG were LineageOS 14.1 (7.1.1).
To my knowledge the kernel + DT.img are identical for the R7Plus,/R7S. The DT.img contains 15022 + 15018 as far as I know.
The only downside when using graphics overlay was that some users reported screenshot In recovery would not work. While I had one user report it works.
Click to expand...
Click to collapse
Actually it didn't boot into the bootloader (fastboot screen), it was stuck on the Oppo screen. Did not respond to adb, but gave correct answer from 'fastboot devices'. Didn't check other fastboot commands though.
Screenshots works well

teemo said:
Actually it didn't boot into the bootloader (fastboot screen), it was stuck on the Oppo screen. Did not respond to adb, but gave correct answer from 'fastboot devices'. Didn't check other fastboot commands though.
Screenshots works well
Click to expand...
Click to collapse
I feel video overlay graphics in twrp recovery feels smoother than adf graphics.
Unfortunately I can't compare them side by side.
What do you think which feels smoother?

celoxocis said:
I feel video overlay graphics in twrp recovery feels smoother than adf graphics.
Unfortunately I can't compare them side by side.
What do you think which feels smoother?
Click to expand...
Click to collapse
For the filemanager, I feel it is a little smoother than before. Might be my imagination though.
It is very picky about how you scroll with your finger, sometimes mistaking it for a "tap". But old adf did the same.
I can say definitely, that the slider is much much better now. Not supersmooth as my HTC, but good enough for a recovery tool. Don't see any downsides yet.
EDIT: Funny, the slider animation is the same as on my 3.0.2-C. I made a video and compared. It's the same. I may have seen the slower animations on an older recovery, I am sure it was much more choppy before.

Is there any chance that this would be updated.?

kishd said:
Is there any chance that this would be updated.?
Click to expand...
Click to collapse
Yes I will update it. Just don't know when yet.
It's a long weekend here. So I might do it tomorrow.
I will post once updated.

x
Help please...I'm stucked at the unlock bootloader...
First to say I have root but I got root only with kingroot app...is this a problem?
I have installed the color os r7plusfEX_11_151225 (didn't do full wype data, installed over the latest color os version), but with the oppo tools it didn't do nothing so I got root with kingroot.
I can go into fastboot but when I type "fastboot oem unlock" it always say this:
"C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.053s"
where I was wrong or where I miss something?
thanks for replies I really will to intall a custom rom on this phone........

celoxocis said:
Yes I will update it. Just don't know when yet.
It's a long weekend here. So I might do it tomorrow.
I will post once updated.
Click to expand...
Click to collapse
I hate to be a nuisance, but have you had a chance to look at this?

kishd said:
I hate to be a nuisance, but have you had a chance to look at this?
Click to expand...
Click to collapse
Yes i decided not to bring another unofficial release.
There will be an update for TWRP for the entire R7 series.
It will be made official soon.

[A-ONLY][TREBLE][9.0][A530F/A530W/A730F] Vendor Pie For Galaxy A8/A8+ 2018

I'm not responsible for whatever damage this could possibly cause to your device.
Before Starting Make Sure You Treble Your Device By This Guide here
If you appreciate the work i have done, Feel free to buy me a cup of coffee @paypal
Welcome to Pie Vendor For Galaxy A8/A8+ 2018 ONLY FOR A530F/A530W/A730F​
Some information you should know..
Full TREBLE Documentation here : https://source.android.com/devices/architecture
Generic System Image (GSI) Documentation here : https://source.android.com/setup/build/gsi
GSIs are not the most stable and many users prove they are unable to read. they just want ready stuff. with this project that is not the case. if you skip the instructions/F.A.Qs and notes, dont bother installing this project as you probably wont be able to get it running.
This is a fully featured VENDOR and KERNEL designed for this device to support project treble, it is based on other Exynos 7885 Vendors and modified to support our devices, i have also added few patches and fixes to this vendor to get the best possible experience
The vendor is pretty much bugles, therefore any bugs you face, Report them to the appropriate Threads of the GSI you installed or github issues section, as those are not mine to fix i only provide the vendor and kernel that allows GSIs to run on.
- VENDOR FEATURES:
Wi-Fi & Hotspot
Telephony & Ril (Mobile Data, Calls, SMS, MMS)
NFC
Camera
Bluetooth
GPS
Fingerprint
All Sensors
- STEPS FOR INSTALLING TREBLE VENDOR:
Make Sure You Treble Your Bevice By This Guide here
Boot into Twrp recovery
Wipe System, Data, Dalvik and Vendor.
Select Vendor_Dumpster.zip
- STEPS FOR INSTALLING GSIs:
Download the desired GSI (it MUST be A-only_arm64 Variant)
unpack it if it wasn't in .IMG format
Go to TWRP , Install , Install IMAGE
Pick your GSI and select SYSTEM IMAGE
Reboot to TWRP Recovery
- STEPS FOR INSTALLING GAPPS
Download the appropriate opengapps
Go to TWRP , Install
Pick your OpenGapps.zip
Reboot to System
- KNOWN BUGS:
Bluetooth calls are broken
Credits:
- @ananjaser1211 for his contribution
- @TaifAljaloo for testing
Downloads. Changelogs , F.A.Qs below
XDA:DevDB Information
Project Treble, Vendor for the Samsung Galaxy A8 (2018)
Kernel Source
Contributors
prashantp01
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Version Information
Status: Beta
Current Stable Version: v1
Created 2019-05-17
Last Updated 2019-05-17

{
"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"
}
Come hang with us on our chat : Telegram
----------------------------------------------------------------
Treble Pie Vendor Dumpster V1.0 [LATEST]
Treble folder : Gdrive
Recommended GSI : Gdrive
Generic System Image (list) : Github
---------------------------------------------------------------
Bugs :
1- some users might face SDCard issues
If you did , back up its data and format it in GSI.
2- If you face "Error 70: Insufficient storage space available in the system partition" while flashing Gapps
If you get do this : Wipe > Advanced Wipe > select system > Repair or Change File System > Resize File System
Go back and flash Gapps
V1.0
-initial release

F.A.Q
For more details related to this project, read our dedicated Wiki page here.
Q : Do i need to format internal storage ?
A : No
Q : Can i use the Treble recovery for normal ROMs ?
A : Yes, it is preferred especially when making backups. just be sure to wipe vendor when switching to non treble roms
Q : What Camera is recommended ?
A : Footej and open camera works the best
Q : Can i flash any GSIs ?
A : No, only A-ONLY_ARM64 Are supported
Q : Can i flash any sGSIs ?
A : No unless they match the Arch above

reserved

I just flashed the Lineage OS v16 GSI with this vendor and found no problems other than no network bars (as mentioned above) and there were no problems with the camera and fingerprint. I will notify you later if there is a bugs
Thanks for your hard work ?

Sweet! I'm gonna be up all night!

This is fantastic. The boot time has decreased immensely.
Finally got aosp extended 6.5 to boot. Well i didn't, you did.
What a difference. Ressurection Remix as well. The 9.0. That one seems a bit iffy no matter.
I am noticing a different mobile data icon. It'll say 4g+
Not too far from normal full usage. Thank you.

mindlery said:
This is fantastic. The boot time has decreased immensely.
Finally got aosp extended 6.5 to boot. Well i didn't, you did.
What a difference. Ressurection Remix as well. The 9.0. That one seems a bit iffy no matter.
I am noticing a different mobile data icon. It'll say 4g+
Not too far from normal full usage. Thank you.
Click to expand...
Click to collapse
Where you able to get gapps installed it always failed for me.
This has happened on most of these roms

Yes i was. My method is a bit harsh though. I am a fan of internal destruction
So for the gsi, i wipe everything including internal. Then i reboot to recovery. Swipe to allow modifications. Install vendor. Install system image. Then reboot recovery flash fix boot. I almost never bother with gapps anymore until it boots fully. Then i'll immediately go into recovery and flash gapps then reboot of course.
I got sick of errors myself. If you find one you like or want to go back to then it may be worth trying for that perfect install. Almost there.
---------- Post added at 04:33 AM ---------- Previous post was at 04:20 AM ----------
https://downloads.aospextended.com/treble_gsi
Before only 6.1 worked. Now 6.5 starts in a minute or so. 6.3 boot looped before so i am going to see what happens now.

mindlery said:
Yes i was. My method is a bit harsh though. I am a fan of internal destruction
So for the gsi, i wipe everything including internal. Then i reboot to recovery. Swipe to allow modifications. Install vendor. Install system image. Then reboot recovery flash fix boot. I almost never bother with gapps anymore until it boots fully. Then i'll immediately go into recovery and flash gapps then reboot of course.
I got sick of errors myself. If you find one you like or want to go back to then it may be worth trying for that perfect install. Almost there.
---------- Post added at 04:33 AM ---------- Previous post was at 04:20 AM ----------
https://downloads.aospextended.com/treble_gsi
Before only 6.1 worked. Now 6.5 starts in a minute or so. 6.3 boot looped before so i am going to see what happens now.
Click to expand...
Click to collapse
I'm using ion- v1.0.c 9.0 without any issues.
For some reason on the newer gsi roms you can't get gapps to install.
ion rom gapps are included.

mchlbenner said:
I'm using ion- v1.0.c 9.0 without any issues.
For some reason on the newer gsi roms you can't get gapps to install.
ion rom gapps are included.
Click to expand...
Click to collapse
I have never heard of that. Of course I am downloading but is there any information about it besides a file on android file host?

mindlery said:
I have never heard of that. Of course I am downloading but is there any information about it besides a file on android file host?
Click to expand...
Click to collapse
I had not heard of it also but it seems to work without issue.
Only thing on screenshot you have edit where photo is being stored.

Does this allow me to use system-as-root gsis? Since android 9 treble implementation is supposed to be system as root even on aonly, I would guess so, but I couldn't get my device to boot with one yet.

Weird, I can't even get aospextended to work... It just bootloops without bootanimation.
Edit: nvm, I got it to work, but I had to flash the oreo vendor first, and then the pie vendor.
Edit2: fingerprint doesn't seem to work even with fp patch (it's weird, it registers the fingerprint, and even validates it, but it does nothing on the lockscreen)
Edit3: restart fixed it

I have a few questions
I used to flash the usual custom roms so is this is the same thing i mean that if i can use it to flash custom roms
And which roms exactly working perfectly on this device without any issues
Also should i root my phone before installing it or what exactly should i do
Is it stable and doesn't have any problems or will i face some problems while im using it

For some reason on aosp extended gsi the phone will stay stuck at the charging screen (gray one without percentage) when charging when its turned off, disconnecting the cable doesn't do anything, it stays stuck on this screen till i force reboot

CoinKiller said:
For some reason on aosp extended gsi the phone will stay stuck at the charging screen (gray one without percentage) when charging when its turned off, disconnecting the cable doesn't do anything, it stays stuck on this screen till i force reboot
Click to expand...
Click to collapse
Did you install GSI_Fix_boot.zip?

So I want to install Google phone but I cannot get it to work. Can you give me an alternative ?

If I want to install a different GSI I follow the steps again (install vendor, flash GSI, flash boot fix and fixes if needed) or just wipe system, data, cache and flash the new image+ boot fix

slawdos said:
Did you install GSI_Fix_boot.zip?
Click to expand...
Click to collapse
Yes but i had to format /vendor after installing that zip (it wasnt the zip fault!), Didn't that get installed in /system?

[ROM][UNOFFICIAL][prague][9] LineageOS 16.0

{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (Pie), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
What's not working :
You tell me
Instructions :
Download the latest build, gapps and nfc fix
Reboot to recovery
Flash the latest build, gapps and nfc fix
Reboot
Downloads :
Lineage Builds : https://sourceforge.net/projects/darkjoker360-developements/files/Huawei/P8 Lite 2017/Pie/LineageOS/
Lineage Recovery : https://sourceforge.net/projects/da...ge-16.0-20201119-recovery-prague.img/download
Nfc fix : https://sourceforge.net/projects/da.../Pie/LineageOS/Nfc Fix LineageOS.zip/download
Root addon : https://download.lineageos.org/extras
Google Apps : https://wiki.lineageos.org/gapps.html
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
XDA:DevDB Information
LineageOS , ROM for the Huawei P8lite/P8 Lite
Contributors
DarkJoker360
Source Code: https://github.com/LineageOS
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Based On: LineageOS
Version Information
Status: Stable
Current Stable Version: 16.0
Stable Release Date: 2020-11-17
Created 2020-11-17
Last Updated 2020-11-20

NOTE: Those builds require Emui 8.

Installed using Pretoriano80's TWRP but the pone doesn't boot past the warning screen.

Jhon_Locke said:
Installed using Pretoriano80's TWRP but the pone doesn't boot past the warning screen.
Click to expand...
Click to collapse
Bootloops for me as well.
Installed the rom from TWRP after wiping system and formating data, to no avail.
EDIT: It finally worked for me after a couple of additional reboots, not sure why. Testing right now...
EDIT2: BLE works, even if I received a couple of error messages at the start, it managed to sync my Mi Band 3 with this ROM.
So, the steps that worked for me are:
- Install Haky86's TWRP v3.4.
- From TWRP, wipe system.
- Install Lineage OS + NFC Fix + OpenGApps v9.0 ARM64 Nano.
- Do normal wipe.
- Format /data.
- Reboot into system.
- If it reboots twice and gets into eRecovery, reboot normally again.

So, today Bluetooth Low Energy (BLE) doesn't work, I'm constantly receiving the "Bluetooth keeps stopping" error message.
Tried to reboot the phone, but it didn'help.
I will try to provide logs this afternoon after work.

Hi,
Can you help me. I've stuck on this...

Released a new update with January 2021 security pathces, fixed occasional lags/junks and properly fixed the hwc blur issue !

Hello everyone and thank you for the work you do, especially thanks to DarkJoker360 for this and the other Rom.
Can you help me please I installed the latest Rom on S2 with cyanogenmod it's been some time.
Latest Stock Rom: PRA-LX1 8.0.0.370 (C55)
I installed:
-TWRP_3.4.0-0-prague_DarkJoker360_20200801
-lineage-16.0-20210109-UNOFFICIAL-prague
-Nfc Fix LineageOS
-open_gapps-arm64-9.0-nano-20210110
After rebooting it stops on the home screen and after waiting it enters Huawei eRecovery.
I would like to install this Rom because I read that it is not possible (I have tried and confirmed) to use "sm set-force-adoptable true" in fact I get this "Error: java.lang.IllegalStateException: Adoptable storage not available on device with native FBE", this feature is only available from android 9 (https://source.android.com/security/encryption/file-based).
I would like to install apps on SD by any method (even Stock).
Can you help me solve this problem?
I uploaded some logs I don't know if they are fine.
Thanks again
Ps: sorry but I use goggle translate

Hi, are we flash LineageOS with normal TWRP, or with Lineage Recovery?

İts okay I understand

Oğuz Karagöz said:
Hi, are we flash LineageOS with normal TWRP, or with Lineage Recovery?
Click to expand...
Click to collapse
Hello
1 HAVE STOK
2 INSTALL WITH FASTBOOT lineage-16.0-20201119-recovery-prague.img
3 Wipe cache data system dalvik / art cache
4 INSTALL WITH FASTBOOT TWRP 3.2.1-0_Dil3mm 4
5 TWRP INSTALL lineage-16.0-20210109-UNOFFICIAL-prague
6 without exiting FAI -> wipe -> advanced -> system -> resize (DO NOT FORMAT THIS TIME!)
7 flash Nfc fix, Root addon, Google Apps
8 reboot
Used very little just to see that it was not possible to use Adoptable storage.
Problem I solved by returning to stok with Android 7.
Bay

aragorn2931 said:
2 INSTALL WITH FASTBOOT lineage-16.0-20201119-recovery-prague.img
3 Wipe cache data system dalvik / art cache
Click to expand...
Click to collapse
hi,
are you sure for this one ?
when booting on lineage-16.0-20201119-recovery-prague.img, there is no possibility to wipe
EDIT : I finally found the options.
ask for confirmation for data and system, not for cache so I don't know if it really wiped cache.
and no option for wiping dalvik
after all that, result : I'm stuck on "your device is booting now..."
only difference, I used TWRP_3.4.0-0-prague_DarkJoker360_20200801.img instead of Dil3mm4
I also tried with dil3mm4 : same result

Hello, when I try to pair an external bluetooth device, such as a scale or a smartwatch, the device is recognized by the mobile phone but I cannot pair it
the message "the bluetooth app keeps interrupting" appears
the bluetooth headphones are paired correctly
how could i solve?

does anyone notice that theyre phone starting to get rlly hot after flashin this rom?

Everywhere I go said:
does anyone notice that theyre phone starting to get rlly hot after flashin this rom?
Click to expand...
Click to collapse
yes , my phone was burn. now it's ok
I think this is magisk problem.
disable the magiskhide & re-enable it.
Magiskd high CPU usage. · Issue #1279 · topjohnwu/Magisk
Magiskd is keeping the CPU running high all the time till I disable the magiskhide & re-enable it. Lineage OS 16.0 here, using Magisk canary 19.0. Its observed since 18.0 till latest build. Log her...
github.com

Is it possiible to fix to ise netflix? I had magisk root hide saftynet passes every thing is ok even serticified on play store i can download netflix login but cant watch anything.

Just a noob question
Why is the nfc fix not integrated in the rom
And why is system partition set so small I have to resize system partition or use gapp nano.
Also I am unable to boot this rom, keep saying
your device has been unlocked and can't be trusted
it does not boot custom rom.

B3rtm3n said:
Just a noob question
Why is the nfc fix not integrated in the rom
Click to expand...
Click to collapse
It was before and it still is, but since latest LineageOS updates I wasn't able to get this working anymore.
It can be turned on/off but it's not really working without the fix zip, even if files are the same included.

ok thx a lot for your answers, it has been quiet some years I flashed a smartphone and things have changed.
I have 3 more questions
1) I noticed that not only twrp made specially for the hardeware specs is needed nowadays but also adapted for each rom, is this correct?
2) do I need to be root to install a customs rom on a p8 lite 2017 or is bootloader unlocked enough?
3) does lineage recovery replaces twrp ? and if yes, how do I install it.
Ok found already that root is not needed.
I have a huge problem with resizing system partition, unable to have it resized using twrp. According to another dude I found on Youtube this can happen so I need another version of twrp.
I am using this one
Huawei P8 Lite 2017
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
and resizing does not work so each rom I flash has a too small system partition.
Is there another good twrp I could use?

B3rtm3n said:
ok thx a lot for your answers, it has been quiet some years I flashed a smartphone and things have changed.
I have 3 more questions
1) I noticed that not only twrp made specially for the hardeware specs is needed nowadays but also adapted for each rom, is this correct?
2) do I need to be root to install a customs rom on a p8 lite 2017 or is bootloader unlocked enough?
3) does lineage recovery replaces twrp ? and if yes, how do I install it.
Ok found already that root is not needed.
I have a huge problem with resizing system partition, unable to have it resized using twrp. According to another dude I found on Youtube this can happen so I need another version of twrp.
I am using this one
Huawei P8 Lite 2017
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
and resizing does not work so each rom I flash has a too small system partition.
Is there another good twrp I could use?
Click to expand...
Click to collapse
Download TWRP for prague
Download TWRP Open Recovery for prague
dl.twrp.me
this is good one

will therre be a lineage 17?

[ROM][11.0][4.9][AOSP][KUGO] Explosive Lobster

[ROM][11.0][4.9][AOSP][KUGO] Explosive Lobster
KUGO F5321
Hi! Just wanna share with you Android 11 ROM builded for Sony Xperia X Compact
Many Thanks for development @Cubbins
I'm not responsible for any damage caused with your device after flashing this ROM. Flash only on your own risk.
This ROM bring us Treble support ( ARM64 A/B ) structure for all GSI images based on 11 Android. Just flash any GSI at System partition after it.
How to Install:
1) Copy ROM to SD card and flash with recovery
2) Download SW_BINARIES_FOR_XPERIA_ANDROID_9.0_2.3.2_V9_LOIRE.ZIP, unzip and copy image to sdcard too
3) Flash Binaries with recovery to OEM/ODM partition
4) reboot
5) After reboot we need to flash/format userdata partition. So, download it and flash with ADB: fastboot flash userdata userdata.img or fastboot erase userdata
6) reboot.
Warning:
We use /cache partition at thid ROM as a /vendor, so if you format /cache partition on recovery - you'll catch a bootloop.
Features:
Working:
- Wi-Fi
- Bluetooth
- Fingerprint
- Sensors
- Camera
- Calling
- Music Playing
- GPS
Not Working:
You tell me
Sources:
build ROM sources:
github.com/ExplosiveLobster
kernel sources:
github.com/ExplosiveLobster/kernel_sony_msm-4.9
bug reports:
github.com/ExplosiveLobster/bug_tracker/issues
Screenshots:
{
"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"
}
Download:
Google Drive
Explosive Lobster - Google Drive
drive.google.com
Mega
3.11 GB folder on MEGA
12 files and 3 subfolders
mega.nz

So good to see some people still working on this device. I'm considering leaving the official rom to this one as soon as GPS is operational. Thank you very much.

mhemart said:
So good to see some people still working on this device. I'm considering leaving the official rom to this one as soon as GPS is operational. Thank you very much.
Click to expand...
Click to collapse
GPS Working fine with latest build, so you can try it right now

lubik1 said:
GPS Working fine with latest build, so you can try it right now
Click to expand...
Click to collapse
Really good, I have to backup my data and I'll give a try tonight. Thanks !

[QUOTE = "lubik1, post: 84244519, member: 5897890"]
Which vendor should I use?

mister-13x said:
Which vendor should I use?
Click to expand...
Click to collapse
F5321 is for X compact.

mister-13x said:
Which vendor should I use?
Click to expand...
Click to collapse
SW_binaries_for_Xperia_Android_9.0_2.3.2_v9_loire.img
The one vendor binaries for both devices - suzu and kugo

Are the Flame Gapps in your Google Drive the Gapps you recommend, or can we just use OpenGapps as usual? This is my first experience with Android 11.
Edit1: Installation worked like a charm with your description. For me, there was no change after flashing userdata.img. The phone behaved the same way, whether I flashed userdata.img or I did not. What did NOT work was just to delete userdata - then my phone would show an error message after boot and just shut down again.
After every boot, I receive the error message “There’s an internal problem with your device Contact your manufacturer for details”. According to Google, this has something to do with Treble. I will install my apps now and get the tests going. Thank you SO much for this. If you leave your PayPal here somewhere, I will send you some small bucks that I can afford for the good development.

Spaceoid said:
Are the Flame Gapps in your Google Drive the Gapps you recommend
Click to expand...
Click to collapse
You can flash any Gapps you want, but this gapps was tested with EL ROM and work fine.
Spaceoid said:
Thank you SO much for this. If you leave your PayPal here somewhere
Click to expand...
Click to collapse
It's allways on my profile, on section "about"

Hello. I had no time to perform an install yet but I have a question (maybe stupid ?). I noticed the binaries were for Android 9 but I saw that there was a newer version called SW_binaries_for_Xperia_Android_10.0.7.1_r1_v7a_loire (no more binaries for android 11). Do you think it could be used with your ROM ? Maybe it would prevent the message that Spaceoid see at every boot ?
Just in case, here is the link to the newest version : https://developer.sony.com/file/download/software-binaries-for-aosp-android-10-0-kernel-4-14-loire/

I just send you two coffees via PayPal for the good work. I know it is not much, sadly I am a student with little income... But I hope it keeps you energized for further improvements to the ROM!
After half a day of testing the pure ROM, without any apps and just Gapps, here is what I found so far:
- Wifi is working, but, at least for me, after like 30 minutes after every boot, it seems to break. After that, I am not able to reconnect to my home wifi network, or to find any Wifi networks in general. Only a reboot fixes this.
- Regarding the error message mentioned in my last post, I found this:
How to Fix Android system There's an internal problem with your device
How to Fix Android system error "There's an internal problem with your device Contact your manufacturer for details" and How to remove NFC Service 'NFC keeps stopping'.
www.recovery-mode.com
I cannot say how reliable/safe this procedure is, though.
- Connected to this, the NFC tile in the pulldown menu (from the status bar) does not work. I can activate NFC via the settings, though; I did not try yet if it really works, but at least it can be activated.
- After every reboot, the phone forgets the time and date until it is connected to cellular network or wifi for the first time.
(- one minor thing - the alarm clock does work well, but it does only sound the alarm and not wake up the screen. So, before disabling the alarm, one has to unlock the screen first.)
Will start installing my apps now and keep on further testing.

mhemart said:
Hello. I had no time to perform an install yet but I have a question (maybe stupid ?). I noticed the binaries were for Android 9 but I saw that there was a newer version called SW_binaries_for_Xperia_Android_10.0.7.1_r1_v7a_loire (no more binaries for android 11). Do you think it could be used with your ROM ? Maybe it would prevent the message that Spaceoid see at every boot ?
Just in case, here is the link to the newest version : https://developer.sony.com/file/download/software-binaries-for-aosp-android-10-0-kernel-4-14-loire/
Click to expand...
Click to collapse
I was about to ask the same. Are the 10 binaries not compatible?

@betacrypt
Binaries for 10 are available however the kernel development was abadoned. Kernel 4.14 did not mature into an operational state. Kernel 4.9 is the current stable version, using the 9 binaries are the most recent option at the moment.

@lubik1
This is being trebled? SELinux is permissive? If that's the case, I imagine the cache.img and boot.img can be used to GSI other OS'.
Warning:
We use /cache partition at thid ROM as a /vendor, so if you format /cache partition on recovery - you'll catch a bootloop. [QUOTE/]
Click to expand...
Click to collapse

&(*) said:
@betacrypt
Binaries for 10 are available however the kernel development was abadoned. Kernel 4.14 did not mature into an operational state. Kernel 4.9 is the current stable version, using the 9 binaries are the most recent option at the moment.
Click to expand...
Click to collapse
Ah that makes sense. Somehow I thought 4.14 was stable.
Also thanks @lubik1 for your efforts to create this! Glad to see continued support for the XC - was worried we'd lost support for it. I own two and had been hoping to see an update.

betacrypt said:
Ah that makes sense. Somehow I thought 4.14 was stable.
Also thanks for your efforts to create this! Glad to see continued support for the XC - was worried we'd lost support for it. I own two and had been hoping to see an update.
Click to expand...
Click to collapse
Don't forget to thank @Cubbins too for the build.

@lubik1 ,
Can you also provide a GSI variant (of boot.img and cache.img) for those of us who like to use other systems?

Anything different to do when rooting with Magisk? I flashed the latest Magisk in TWRP successfully but when I boot into system the Magisk App says no root.

betacrypt said:
Anything different to do when rooting with Magisk? I flashed the latest Magisk in TWRP successfully but when I boot into system the Magisk App says no root.
Click to expand...
Click to collapse
Strange. I did the same this morning, downloaded latest Magisk version from Github, and it worked for me. I already used root for Titanium Backup. I used v21.2.
On another note, after one day of usage, I'd already consider this ROM quite stable. The wifi problem really is the main problem, as I only can connect to my home wifi in 20% of the day. I already lost all my mobile data because of that, now I am surfing in less than 2G speed on my phone xD

Spaceoid said:
- Wifi is working, but, at least for me, after like 30 minutes after every boot, it seems to break. After that, I am not able to reconnect to my home wifi network, or to find any Wifi networks in general.
Click to expand...
Click to collapse
We'll switch to another wi-fi driver on next build.
Spaceoid said:
- Regarding the error message mentioned in my last post, I found this:
Click to expand...
Click to collapse
Will be Fixed on next build
Spaceoid said:
- Connected to this, the NFC tile in the pulldown menu (from the status bar) does not work. I can activate NFC via the settings, though; I did not try yet if it really works, but at least it can be activated.
Click to expand...
Click to collapse
Will be added on next build
Spaceoid said:
- After every reboot, the phone forgets the time and date until it is connected to cellular network or wifi for the first time.
Click to expand...
Click to collapse
Missing rtc-service, will be added on next build

[ROM][Huawei][12] LeaOS - Lineage 19.1 for Huawei device (EMUI 9)

Non-Official Lineage 19.1 for EMUI 9 hi6250 Huawei (anne) - LeaOS
{
"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"
}
LeaOS is a project which based on LineageOS 19.1 with Andy Yan's and phhusson's Treble GSI patches. I have added my personnals patches for Huawei devices : Assisted GPS, NFC, CAST/Miracast, Default Sound etc..) and some eremitein patch
Changelog :
LeaOS September 2022 version
September 2022 SPL
Synchronize with last Lineage Source
Add /splash2 and /modem_log support
Add kirin and huawei properties
Support permissive or enforce kernel
Update Lite Google Apps to 2.6
LeaOS August 2022 version
Jul + Aug 2022 SPL
Synchronize with last Lineage Source and v415 phh
Port new functionnalities Treble Setting from 18.1 version (Dump log, restart ui, dynamic root, safetynet, auto run, nolog)
Add miracast support
Add scanner QR support
LeaOS Jun 2022 version
Jun 2022 SPL
Synchronize with last Lineage Source and v414 phh
Fix MediaScanner crash and no default sound (ringtone, alarms..)
Add support of EMUI 9.1.0.405 (preav partition)
Pre-requisite :
You must have TWRP installed if you want install patch. and a phone with unlock bootloader
Installation (crypt or uncrypt)
Download file : “LeaOS-19.1-20220911-iceows-ane.7z" and extract img file
Flash system image : fastboot flash system <drag system.img here>
Flash twrp image: fastboot flash recovery_ramdisk <drag twrp img here>
Boot into twrp: power + vol+ while NOT connected to pc
Resize system: Wipe > Advanced Wipe > System > Repair or Change File System > Resize File System > Swipe
Wipe cache, dalvik/art cache, internal storage, data
(optional) install AGPS patch : 4-Huawei-AGPS-AB-v1.1-signed.zip
(optional) install DRM patch for EMUI 9.1.0.405 : 8-Huawei-FixPreav-AB-v1.0-signed.zip
(optional) install now Google Apps Lite : LiteGapps_arm64_12.1_v2.6_official.zip
reboot to System and set up the phone with Lineage first start assistant. You can also add most user
Enjoy !!!
More informations to install here : https://forum.xda-developers.com/t/guide-emui9-p20-lite-basics.4341373/
Not working :
Offline charging
Bluethooth pairing with code (use app)
Source Code:
https://github.com/Iceows
ROM OS Version: Android 12L (12.1)
ROM Kernel: Linux Huawei 4.9.148 or Phenix 4.9.319
ROM Firmware Required: EMUI 9
Based On: Lineage 19.1
Credits:
@Frax3r (Testing)
@PHH
@eremitein
@RakinTheGreat (GCam)
@TureX (Kernel)
And all the others who tested my patches and helped me improve this ROM
Support Group

Screencopy

Hello, exciting to see android 12 on this phone! A few questions:
* is this good enough to be used as daily driver?
* i remember previous lineage versions having problems with signal strength icon. Do your fixes include fix for this?
* i read some people having problems with wifi and fingerprint on lineage, but fixed them by going to previous stock version with better drivers, is that correct and not related to rom?
* do payments work with this rom? Google Pay and banking apps
* according to your instructions, we have to flash image through fastboot and not twrp as explained in other threads? will twrp flash produce the same result? maybe that's trivial, but i still do not understand the concept fully
* in other threads i read that you need to do factory reset from eRecovery after flashing lineage, do you not have to do that here?
* i could not find information about what this a/ab version is. can you explain?

Signal strengh and wifi are fixes by me since Lineage 18.1. I gave my patches to all the main developers of the GSI
This version of lineage 19.1 have for the moment two problems :
- offline charging
- bluetooth pairing not working
For daily use , use LeaOS Lineage 18.1 please

Betrakiss said:
Hello, exciting to see android 12 on this phone! A few questions:
* is this good enough to be used as daily driver?
* i remember previous lineage versions having problems with signal strength icon. Do your fixes include fix for this?
* i read some people having problems with wifi and fingerprint on lineage, but fixed them by going to previous stock version with better drivers, is that correct and not related to rom?
* do payments work with this rom? Google Pay and banking apps
* according to your instructions, we have to flash image through fastboot and not twrp as explained in other threads? will twrp flash produce the same result? maybe that's trivial, but i still do not understand the concept fully
* in other threads i read that you need to do factory reset from eRecovery after flashing lineage, do you not have to do that here?
* i could not find information about what this a/ab version is. can you explain?
Click to expand...
Click to collapse
-I can't say that for any gsi for our device but it is subjective nonetheless.
-Signal strength is fixed by AltairFR (iceows). Darkjoker360 (Simone) included his fix in his latest emui 8 los 18.1 build as well.
-Fingerprint as in sensor or build fingerprint? Fingerprint sensor will say failed to enroll if you had fingerprint enrolled in emui but did not remove it from emui settings. Factory reset should remove it as well. As for wifi, if you install this rom on top of latest emui build wifi will work just fine. But if you switch your kernel to something else other than stock or harmonyos based kernel it will not connect to wifi. This is not related to rom.
Emui version <9.1.0.300 : You can use any kernel
Emui version >9.1.0.300 : You can only use stock kernel from your emui version or harmonyos based ones. (Turex posted a test kernel in his thread) if you want functioning wifi.
-Google pay is not present in my country so I can't test but it is possible to pass safetynet which should allow you to use it ig.
-As long as twrp you use works properly it shouldn't matter.
-Instructions is missing a step atm, you don't need to do a factory reset if you flash an additional zip file before flashing AGPS patch. 1-Huawei-DataPrep-Crypt-AB to keep encryption or 1-Huawei-DataPrep-DeCrypt-AB to remove it. These zips replicate folder structure of factory reset so you don't need to "reboot, flash stock recovery, factory reset, reboot, flash twrp". Wait for updated instructions or check the link below instructions (Vanilla GSI steps in Flashing Any GSI part).
-AB in gsi builds means system-as-root which p20 lite is. AB in device means a and b slots for each image which isn't present in p20 lite. In short you use A-only builds in emui 8 vendor but use AB builds in emui 9 vendor. Since AltairFR builds for both vendors his sourceforge includes a and ab zips and builds. If it says A, it's not for emui 9 vendor.

Update AGPS fix and Google Apps

hi thanks for the ROM but, i putted correct wifi password but it doesn't work. Why?

freddie993 said:
hi thanks for the ROM but, i putted correct wifi password but it doesn't work. Why?
Click to expand...
Click to collapse
Wifi password on wpa3 ?

AltairFR said:
Wifi password on wpa3 ?
Click to expand...
Click to collapse
No wpa2, I also tried to Hotspot from another device without protection and doesn't work again

I've had this kind of problem before. It usually comes from the kernel or the emui version. What version are you on?

AltairFR said:
I've had this kind of problem before. It usually comes from the kernel or the emui version. What version are you on?
Click to expand...
Click to collapse
i have emui 9

freddie993 said:
i have emui 9
Click to expand...
Click to collapse
Ok but indicate minor version please

scuse me, what does minor version means? i read android 12, version lineageOS: LeaOS i don't have other information.
When i go to the update section, it gives me an error "your device does not support OTA updates!"

freddie993 said:
scuse me, what does minor version means? i read android 12, version lineageOS: LeaOS i don't have other information.
When i go to the update section, it gives me an error "your device does not support OTA updates!"
Click to expand...
Click to collapse
Minor version of emui 9. my version is 9.1.0.405 and you?
Please exec to have exact of your emui version :
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION

ah ok, i didn't understand, i already have those information . Please check this thread , in one post i had attached the image with those information.
Thank you

Ok , try phenix kernel please , version 4.9.235 phenix 1.0, it is my kernel on my ANE-LX1:
[GUIDE] [EMUI9] P20 Lite Basics
Special key combos: Power + Vol+ = Recovery Mode While USB connected, Power + Vol+ = Erecovery Mode While USB connected, Vol- = Fastboot Plug USB while holding down Vol+ + Vol- = Download Mode Power + Vol+ + Vol- = Force Dload Flashing Any GSI...
forum.xda-developers.com
Because you have version emui > 300
[KERNEL][EMUI 9][P20 lite] Phenix kernel
PHENIX KERNEL Disclaimer: Use this kernel at your own risk. Flashing it may brick your device. I'm not responsible for any software/hardware and any kind of damages/losses. NOTE : Use only on EMUI9 base(stock or custom) REQUIREMENTS ...
forum.xda-developers.com

Ok, I must follow the first link??

freddie993 said:
Ok, I must follow the first link??
Click to expand...
Click to collapse
Yes or just flash kernel in the attachment of the second link

What does "DRM patch for EMUI 9.1.0.405" do?
Another question: I can not pass SafetyNet. I have tried to remove root using PHH Settings => Misc Settings => Securize, but it does nothing. Even if I install PHH's SuperUser app (the Google Play does not have one any more, so I used v.1.0.3.3 from another source) I can not get it to work. I understand I am missing something, but do not know what. Any help would be appreciated.

luka_bubi said:
What does "DRM patch for EMUI 9.1.0.405" do?
Another question: I can not pass SafetyNet. I have tried to remove root using PHH Settings => Misc Settings => Securize, but it does nothing. Even if I install PHH's SuperUser app (the Google Play does not have one any more, so I used v.1.0.3.3 from another source) I can not get it to work. I understand I am missing something, but do not know what. Any help would be appreciated.
Click to expand...
Click to collapse
DRM allows you to play protected videos in Chrome or Netflix. Without this chrome patch freeze as soon as there is a video. If you need to be root use the dynamic root option (treble setting) If you want to pass safetynet install the pixel experience instead