[9.0][TREBLE]PixelExperience / PixelExperience Plus Pie [UNOFFICIAL] - Moto Z2 Play ROMs, Kernels, Recoveries, & Other D

[9.0][TREBLE]PixelExperience / PixelExperience Plus Pie [UNOFFICIAL] - Moto Z2 Play ROMs, Kernels, Recoveries, & Other D

{
"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

Related

[RECOVERY][UNOFFICIAL]TWRP:Team Win Recovery Project[P20 PRO]

I will use this post to share my work
Sorry for making another TWRP thread, but i've had enough with our current TWRP.
I have enabled logcat and strace.
This is the initial release so keep in mind that it has (probably) currently the same bugs with the official.
The only difference is that you can grab any kind of log and help me improve it and only when it will be stable enough , only then, i will push to the official.
------------------------------------------------------------------------------------------------------
VERSION: recovery-3.3.1-0-b.img | date: 15-06-2019
FIXED:
1. mounts correctly all partitions
2. backup to usb-otg enabled
3. backup all partitions except data (i need to fix decryption)
4. restore fixed.
5. ADB sideload fixed.
6. you can flash a kernel and a recovery .img directly inside TWRP. No more rebooting to bootloader.
NOT TESTED:
1. I don't know about format yet. i haven't tested it because im not ready to format yet.
If anyone is about to format anyway, please after format do:
Code:
adb pull /tmp/recovery.log
and
Code:
adb logcat -b all > logcat.txt
And send me these two logs so that i can fix format and we don't need stock Huawei recovery anymore.
2. Can't flash GAPPS exactly like in the official.
VERSION: recovery-3.3.1-0-c.img | date: 17-06-2019
FIXED:
1. GAPPS flashing fixed. Same goes for any other flashable package.
2. backup data and wipe data are fixed. (not tested restore yet)
NOT FIXED:
1. Even if wipe data and backup data are fixed, and even though we can restore data ! Sadly there are bugs when we wipe data or perform a restore. Until i fix (if i fix it) decryption, please keep using the stock Huawei recovery to format your data and avoid restoring data.
ISSUE: Data partition is fine and it sais that it's 128gb but apps think that we don't have enough "free space". It may just be an issue in vold too in the rom where i tested it.
VERSION: recovery-3.3.1-0-d + e.img | date: 20-06-2019
FIXED:
- minor bug fixes for stability
- added nvme partition which is needed during the decryption
- adb sideload fixed. No need to push and install
NOT FIXED:
- decryption
- format

It's great news man. Looking forward to your further progress! Fully functional twrp is the juice.

Amazing, hope we can have finally fully functional twrp
Thanks

aoryx said:
Amazing, hope we can have finally fully functional twrp
Thanks
Click to expand...
Click to collapse
adb sideload and gapps flashing are fine too.
Format data needs to be fixed and decryption

Legend.

Need to update my ROM, will test this tomorrow. Won't be formatting I hope, but if I do I'll be sure to grab logs..

dladz said:
Need to update my ROM, will test this tomorrow. Won't be formatting I hope, but if I do I'll be sure to grab logs..
Click to expand...
Click to collapse
not yet. gimme some hours. im trying to fix something and then ill share a new build.
i have 2 errors left:
1. linker: Warning: couldn't read "/system/etc/ld.config.txt" for "/sbin/sh" (using default configuration instead): error reading file "/system/etc/ld.config.txt": Too many symbolic links encountered
That problem is in bionic.
in bionic/linker/tests/linker_config_test.cpp or in
bionic/linker/ld.config.format.md. But i can't figure it out yet. That will fix the gapps flashing issue with latest TWRP and mine.
What's strange is that it doesn't happen to everyone. So i'm confused.
Me i can't flash any gapps, when others reported to me that they can.
Click to expand...
Click to collapse
We can finally backup data partition. And we can use MTP. And we can restore data. And everything is ok, BUT
i still can't decrypt the internal storage. it's a work in progress.
Click to expand...
Click to collapse
At least wait for 1. otherwise you may need 3.2 official TWRP to flash gapps and it's boring to flash other TWRP every time.

@kessaras
On my P20 Pro i dont have "/system/etc/ld.config.txt" but i have "/system/etc/ld.config.28.txt"

titi66200 said:
@kessaras
On my P20 Pro i dont have "/system/etc/ld.config.txt" but i have "/system/etc/ld.config.28.txt"
Click to expand...
Click to collapse
and mine has no ld.config at all. its beautiful , just beautiful.....
just use it then. if it can flash anything for you, then use it.
ill upload another one now that can also backup data.
For those who cant flash gapps just use twrp 3.2 official.
problem is symlink : system/etc to /etc.
@steadfasterX will help me with that.
EDIT:
VERSION: recovery-3.3.1-0-c.img | date: 17-06-2019
i found a temporary fix until @steadfasterX helps me out. its ok for flashing. system backup is not ok.

kessaras said:
and mine has no ld.config at all. its beautiful , just beautiful.....
just use it then. if it can flash anything for you, then use it.
ill upload another one now that can also backup data.
For those who cant flash gapps just use twrp 3.2 official.
problem is symlink : system/etc to /etc.
@steadfasterX will help me with that.
EDIT:
VERSION: recovery-3.3.1-0-c.img | date: 17-06-2019
i found a temporary fix until @steadfasterX helps me out. its ok for flashing. system backup is not ok.
Click to expand...
Click to collapse
stop working in RL the PR is waiting for you :laugh:
https://github.com/Suicide-Squirrel/android_device_huawei_charlotte/pull/1
as said: needs testing ofc as I do not own that device
.-

- Even though format is successful, TWRP will freeze and on next boot we can't boot or boot to TWRP.
We must format with stock Huawei recovery to fix that. So do not use the format yet in TWRP.
There must be some specific command that huawei uses to format the f2fs data partition. It's impossible to get that from a first boot from EMUI because adb logcat is not allowed until we unlock and enable
developer options. Plus that we can't selectively decrypt and encrypt again like we did a few years ago on older devices.... so i have to test several format command lines randomly until i get the right one.
- When i decrypt i get a fail, without a clear error. Decryption still has a looooong way to the fix and i don't have the time for that to do it daily, so be patient.
Well, at least we have a reliable TWRP now.

kessaras said:
- Even though format is successful, TWRP will freeze and on next boot we can't boot or boot to TWRP.
We must format with stock Huawei recovery to fix that. So do not use the format yet in TWRP.
There must be some specific command that huawei uses to format the f2fs data partition. It's impossible to get that from a first boot from EMUI because adb logcat is not allowed until we unlock and enable
developer options. Plus that we can't selectively decrypt and encrypt again like we did a few years ago on older devices.... so i have to test several format command lines randomly until i get the right one.
- When i decrypt i get a fail, without a clear error. Decryption still has a looooong way to the fix and i don't have the time for that to do it daily, so be patient.
Well, at least we have a reliable TWRP now.
Click to expand...
Click to collapse
Sounds painful, the other twrp does something similar..
Would the chap who made the unofficial one be able to assist?
His threads looked but he's still active .
Feel for you mate, sounds like a massive ballache.

kessaras said:
- Even though format is successful, TWRP will freeze and on next boot we can't boot or boot to TWRP.
We must format with stock Huawei recovery to fix that. So do not use the format yet in TWRP.
There must be some specific command that huawei uses to format the f2fs data partition. It's impossible to get that from a first boot from EMUI because adb logcat is not allowed until we unlock and enable
developer options. Plus that we can't selectively decrypt and encrypt again like we did a few years ago on older devices.... so i have to test several format command lines randomly until i get the right one.
- When i decrypt i get a fail, without a clear error. Decryption still has a looooong way to the fix and i don't have the time for that to do it daily, so be patient.
Well, at least we have a reliable TWRP now.
Click to expand...
Click to collapse
I did wipe system, cache, data and internal memory with success some weeks ago. But I didn't try the Format Data option.

djlukas1983 said:
I did wipe system, cache, data and internal memory with success some weeks ago. But I didn't try the Format Data option.
Click to expand...
Click to collapse
Lukas do not wipe data at an encrypted and non-decrypted partition.
When you will boot again to the rom, the system will think that data is clean so it will attempt to encrypt the already encrypted.
At settings you will see that you have 128gb data partition but you will have only a few mb actually.
wipe data does NOT remove encrption, only a format can remove the encryption.

djlukas1983 said:
I did wipe system, cache, data and internal memory with success some weeks ago. But I didn't try the Format Data option.
Click to expand...
Click to collapse
Did it actually wipe though? If it didn't the ROM may still boot as it would simply be a dirty flash.

Hi,
although I'm on a P20 Lite, does this work with EMUI9.x?
Is it possible to create TWRP also for ANE-LX1?
Does this work with GSI or only Stock ROMs?
Peter

pmatj said:
Hi,
although I'm on a P20 Lite, does this work with EMUI9.x?
Is it possible to create TWRP also for ANE-LX1?
Does this work with GSI or only Stock ROMs?
Peter
Click to expand...
Click to collapse
the only way to know that is to flash it and test it.
what are you afraid of ? if twrp doesn't boot, you can flash back the stock huawei recovery again.
>> the device won't have any issues if twrp is not for that device <<
It should work if it can boot. The only difference is our resolution. So if you see TWRP boot , then it's ok to use it.
* It will probably work because i don't force any specific resolution here.
But if it doesn't , change this to your resolution https://github.com/Suicide-Squirrel...43104c493e172dc469d7838153/BoardConfig.mk#L53
and build TWRP for p20 lite

Hm, ok, my P20Lite boots up, adb is initialized and I can also swipe to start but after 5-10 seconds, the phone just reboots to bootloader, so I cannot do anything useful with it....
I'm currently on EMUI9.1 (so A/B partitioned) and I already faced this behaviour on askuccios TWRP...

pmatj said:
Hm, ok, my P20Lite boots up, adb is initialized and I can also swipe to start but after 5-10 seconds, the phone just reboots to bootloader, so I cannot do anything useful with it....
I'm currently on EMUI9.1 (so A/B partitioned) and I already faced this behaviour on askuccios TWRP...
Click to expand...
Click to collapse
If it's a/b try talking to OnePlus 6/6t recovery.
They have a/b there too and if the dev answers to you then you probably have it

[ROM][UNOFFICIAL][9.0][tb8704f/x] LineageOS 16.0 for Lenovo TAB4 8 plus

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here 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.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
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.
What works:
Calls/SMS/Mobile data
Wifi
Bluetooth
GPS
Camera
Audio
FM radio
Torchlight
LED
USB and WLAN tethering
Fingerprint sensor
Broken
You tell me
Source code:
device : https://github.com/lenovo-devs/android_device_lenovo_TB8704, https://github.com/lenovo-devs/android_device_lenovo_tb-common
kernel: https://github.com/lenovo-devs/android_kernel_lenovo_msm8953/tree/lineage-16.0
vendor: https://github.com/lenovo-devs/proprietary_vendor_lenovo
2020-03-20
Enable DT2W
Update Lineage code
mailru: lineage-16.0-20200320-UNOFFICIAL-TB8704.zip
gdrive: lineage-16.0-20200320-UNOFFICIAL-TB8704.zip
boot.img for TB-8704V: boot-los16.0-tb8704v-test20200320.img (source code)
Previous versions:
2019-12-27
Fixed fingerprint scaner issue
mailru: lineage-16.0-20191227-UNOFFICIAL-TB8704.zip
gdrive: lineage-16.0-20191227-UNOFFICIAL-TB8704.zip
boot.img for TB-8704V: boot-los16.0-tb8704v-test20200316.img (source code)
2019-12-25
Fixed OTG mode
enable target ttl for thethering with some operators
Updated Lineage code
mailru: lineage-16.0-20191225-UNOFFICIAL-TB8704.zip
gdrive: lineage-16.0-20191225-UNOFFICIAL-TB8704.zip
2019-08-11
Fixed insert/remove detection for 3.5'' headset plug
Updated Lineage code
mailru: lineage-16.0-20190811-UNOFFICIAL-TB8704.zip
gdrive: lineage-16.0-20190811-UNOFFICIAL-TB8704.zip
2019-07-14
Initial release
mailru: lineage-16.0-20190721-UNOFFICIAL-TB8704.zip
gdrive: lineage-16.0-20190721-UNOFFICIAL-TB8704.zip
How to install
You have to had TWRP installed from this thread TWRP and ROOT for Tab 4 8/10 (Plus) (TB-8704X/F/V,TB-X704L/F, TB-8504X/F, TB-X304L/F)
In TWRP clean Data if you coming from stock ROM and do Install of this ROM. If you have android 8 stock rom installed you have to format Data with data loss, because used encryption is incompatible with android 7.1
TB-8704V (Verizon)
If you have TB-8704V tablet, you have to additionaly flash boot.img from link above after rom intsallation. This tablet has some hardware differences from x and f and requires custom kernel to work,
Thanks
Big thank to @mistersixt, who donated $$ for device.
XDA:DevDB Information
[ROM][UNOFFICIAL][9.0][tb8704f/x] LineageOS 16.0 for Lenovo TAB4 8 plus, ROM for the Lenovo Thinkpad Tablet
Contributors
highwaystar_ru
Source Code: https://github.com/lenovo-devs/android_kernel_lenovo_msm8953/tree/lineage-16.0-wip
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: LineageOs
Version Information
Status: Testing
Created 2019-07-21
Last Updated 2019-08-11

Installed it and everything seems to be working great. Many thanks for your work

Can't seem to get it boot on tb8704v (boot loop). I have unlocked rebooted and made sure oem unlock was still checked and installed twrp-3.2.3-0-tb_8704v and then installed rom and gapps. But it just boot loops on restart. I'm missing something?

Thank you so much for all your hard work.

I am unable to install gapps, its stuck on "mounting /persist /system" is there any work around?

wow! can't wait to flash this! thanks so much!
Just noticed in the OP you have "ROM OS Version: 7.x Nougat" Don't you mean 9.x?

Clean installed but stuck on lineage logo, any suggestion? Previously installed L14.1 without issue.

Acel337 said:
Clean installed but stuck on lineage logo, any suggestion? Previously installed L14.1 without issue.
Click to expand...
Click to collapse
Are you on tb8704f?

hunnia41 said:
Are you on tb8704f?
Click to expand...
Click to collapse
Yes, I'm on TB-8704F. Previously installed 14.1 without issue.
Did a clean install: format DATA and cache; again tried with clearing SYSTEM folder as well.
After installing, reboots as normal thenstuck on Lineage ARC loading with no end; left it alone for 30mins but never load into OS.

Acel337 said:
Yes, I'm on TB-8704F. Previously installed 14.1 without issue.
Did a clean install: format DATA and cache; again tried with clearing SYSTEM folder as well.
After installing, reboots as normal thenstuck on Lineage ARC loading with no end; left it alone for 30mins but never load into OS.
Click to expand...
Click to collapse
I did the same . but I had stock 8.1 installed. I installed mindthegapps as well as the ROM and rebooted and everything seems to be working fine.

I also had 14.1 installed before. Unfortunately I have the same problem as Acel337. I have the tb8704x.
Has anyone found a solution yet?
14.1 starts without problems after flashing again.

I dirty flashed over los 14. Then flashed openGapps 9 pico. Then reflashed the latest magisk. ROM boots after about 5 minutes without any issues.
Chrome reloads on occasion. I have root, don't have rw. The remount script doesn't work. Netflix casts well. That's as far as I've got.
Thank you for this!
Update: rw now working

Acel337 said:
Yes, I'm on TB-8704F. Previously installed 14.1 without issue.
Did a clean install: format DATA and cache; again tried with clearing SYSTEM folder as well.
After installing, reboots as normal thenstuck on Lineage ARC loading with no end; left it alone for 30mins but never load into OS.
Click to expand...
Click to collapse
For me evrythin works
8.0 stock rom
install magisk
install twrp
system writable
erase system data.
sideload pie and gapps.
Everyhing works perfectly.
Maybe the difference, that I started from 8.1 stock
Just a thought. It could be, that indirectly the (wrong) encryption cause the problem. Since when booting, the program tries to populate the data partition, and if it cannot do it, since it appears as 0 storage, it might just stuck in a loop.

How do you get /system to be writable?

Installed from stock 8.0 plop to Los16 with Pico gapps. Format data - reboot to recovery then continue with flash procedures (wipe system/cache dalvik etc) I'll be sending a Donation over the next day or so. Having LineageOS for this device is an absolute GodSend @drizzle123 flash the remount rw magisk.zip. I had problems with it previously on stock roms but it seems to be working ok atm fingers crossed. (here's link to post/file) https://forum.xda-developers.com/showpost.php?p=77781453&postcount=1014

Hemphiz said:
Installed from stock 8.0 plop to Los16 with Pico gapps. Format data - reboot to recovery then continue with flash procedures (wipe system/cache dalvik etc) I'll be sending a Donation over the next day or so. Having LineageOS for this device is an absolute GodSend @drizzle123 flash the remount rw magisk.zip. I had problems with it previously on stock roms but it seems to be working ok atm fingers crossed. (here's link to post/file) https://forum.xda-developers.com/showpost.php?p=77781453&postcount=1014
Click to expand...
Click to collapse
"I'll be sending a Donation "
I did too. The first time in my life for firmware. I have no problem so far. (Used it 24 hours.)
---------- Post added at 06:51 AM ---------- Previous post was at 06:34 AM ----------
Acel337 said:
Yes, I'm on TB-8704F. Previously installed 14.1 without issue.
Did a clean install: format DATA and cache; again tried with clearing SYSTEM folder as well.
After installing, reboots as normal thenstuck on Lineage ARC loading with no end; left it alone for 30mins but never load into OS.
Click to expand...
Click to collapse
Seemingly you did everything, which had to be done. If it is a problem with the firmware, maybe it has to do with the encryption. (Cannot encrypt the data.) Just a guess, since it works for so many people.
maybe you should reflash the 8.1 stock rom. If it works, try again to reinstall lineage pie. If it still fails, go back to stock until problem is solved.

The tablet was on latest official 8.1 then changed to LineageOS 14.1. Tried to install to this 16.0 then this issue started.
I have sucessfully installed 14.1 but not to latest 16.0. It's a strange issue.

Could we get some gamepads working up on this mofo please? That would be the Cherry

same here, TB-8704F stuck on lineage bootanimation too
Acel337 said:
The tablet was on latest official 8.1 then changed to LineageOS 14.1. Tried to install to this 16.0 then this issue started.
I have sucessfully installed 14.1 but not to latest 16.0. It's a strange issue.
Click to expand...
Click to collapse
coming from latest 8.1 (TB-8704F_S0010xx_190606_ROW with security update from April 5th) doing the following:
- installed recovery: fastboot flash recovery twrp-3.2.3-0-tb_8704x.img
- booted into recovery and format /data
- again rebooted recovery and wiped /system, /data /cache and /dalvik
- installed "lineage-16.0-20190721-UNOFFICIAL-TB8704.zip" , directly afterwards "open_gapps-arm64-9.0-pico-20190720.zip"
Now, TB-8704F stuck on bootanimation

robidick said:
coming from latest 8.1 (TB-8704F_S0010xx_190606_ROW with security update from April 5th) doing the following:
- installed recovery: fastboot flash recovery twrp-3.2.3-0-tb_8704x.img
- booted into recovery and format /data
- again rebooted recovery and wiped /system, /data /cache and /dalvik
- installed "lineage-16.0-20190721-UNOFFICIAL-TB8704.zip" , directly afterwards "open_gapps-arm64-9.0-pico-20190720.zip"
Now, TB-8704F stuck on bootanimation
Click to expand...
Click to collapse
I did exactly the same thing with the following exceptions. (whether they are significant or not I do not know.
1. Went into twrp without installing it and unrooted with Magisk. (side load)
(Then I do not remember whether I booted up in stock, to check by magisk whether dm-verify was off. It should be)
then I rebooted into fastboot and installed twrp and in my case I made system writable.
After this I proceeded as you discribed.

[ROM][G610X] H-ROM A7 PORT V6.0 [10.0][OneUI 2.0][64 bits][Treble]

{
"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 ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you
I've put a huge amount of time and effort in this SOLO project (no other dev has been involved), so respect me and respect my work. You are NOT allowed to use this rom, its vendor or any of the other files included as base for your projects.
FEATURES
OneUI 2.0 under Android 10, ported from the SM-A750FN
All G610 variants should be supported
Arm64 with Treble support
Fully deodexed
SIMPLE-KERNEL included, compiled from A600FNXXU5CTB9 sources. Built permissive
Deknoxed, debloated, and removed all samsung useless security stuff in rom and kernel level
N20 multi CSC with additional features (call recording, etc)
And many more!
KNOWN BUGS
Light in capacitive buttons for those devices with hardware buttons
Some 3rd camera apps like footej don't work. Whatsapp video calls could be bugged too. If so, use Whatsapp business
Other inherent bugs from OneUI and/or 7870 limitation
You tell me
DOWNLOAD
Current version: 6.0 (02/12/2020)
More info in 2nd post
INSTALLATION
Vendor partition is required.
Wipe system, data (clean install mandatory), vendor, dalvik&cache and cache
Flash rom zip
Reboot
First boot will take much time, be patient
SCREENSHOTS
https://imgur.com/a/Q5Ysvoz
ROOT
Flash Magisk canary. Stable Magisk will give bootloop.
SUPPORT
Telegram group
CREDITS
Me, for infinite hours spent with this project
Special thanks to @ananjaser1211, @SPARTANICUS and @Valera1978 for their huge contribution to the 7870 development
Thanks to my testers and @neel0210 for camera rework
And thanks one more time to @SaiFurR for his design work with banner
@topjohnwu for Magisk
DONATIONS
I don't need them, I don't need coffees or beers. I really hate see here people with high end devices asking for donations, but you can still donate money to charity. Donate money or simply help people that is really needed. If you like this rom you can make me very happy just pushing THANKS
XDA:DevDB Information
H-ROM A7 PORT, ROM for the Samsung Galaxy J7
Contributors
Astrako
Source Code: https://github.com/samsungexynos7870/android_kernel_samsung_exynos7870/tree/simple_q_permissive
ROM OS Version: Android 10
ROM Kernel: Linux 3.x
ROM Firmware Required: Oreo bootloader
Version Information
Status: Stable
Current Stable Version: 4.0
Created 2020-07-19
Last Updated 2020-08-27

H-ROM A7 PORT V6.0 (02/12/2020)
November security patch
Fixed Dual sim detection
Added High Perfomance mode
Setting volume in different apps should be fixed
You will need around a 3100Mb system partition, so if you dont have it, go and flash my repartition script
GoogleDrive folder
Mega
Md5: a9f3cacee034142024fd2802eed21b61
Spoiler: Old versions
H-ROM A7 PORT V5.0 (27/08/2020)
Spoiler: Old versions
Firmware ported from A750FNXXU4CTG2. July security patch
Added SIMPLE kernel
Echo in calls should be fixed. Other minor bugs can be present depending the phone/variant
You will need around a 3100Mb system partition, so if you dont have it, go and flash my repartition script
GoogleDrive folder
Mega
Md5: 87fc5ef5c031a2f586d762debcf7b3e0
Added a navbar enabler/disabler to the download folder
H-ROM A7 PORT V4.0 (19/07/2020)
Firmware ported from A750FNOXM4CTE3. June security patch
Specifig bugs: echo in calls
GoogleDrive folder
https://drive.google.com/drive/folders/13UG-hdqWU8nud1JCm6DD0vQXAQjeJCVP
Remember, a lot of time has been put in this project. If you like it and want to support me, no donations at all are required, just pushing thanks buttons.

Reserved

Great job

what is vendor partition? can you explain more detail? this is the first time im going to try treble rom. i dont understand what is vendor partition (what is that? is it a flashable file? or what?)

leo31 said:
what is vendor partition? can you explain more detail? this is the first time im going to try treble rom. i dont understand what is vendor partition (what is that? is it a flashable file? or what?)
Click to expand...
Click to collapse
Vendor partition is a partition that comes with treble supported phones j7 isnt one of them but with project spaget you can enable treble support on our phone so that it can install treble roms. To get the vendor partition got to this link and download the latest version (spaget x) and flash create vendor 2.0 and you will have a vendor partition.

which kernal is install ? .... i have downloaded h20 rom for g610f but i face some problem such as phone stuck and reboot automatically.... so i need to know whick kernal is installed......

Great work on the ROM
Kindly help with a working SIM Toolkit zip file for this ROM. Or anybody with a working SIM Toolkit zip file can help me with it. Thanks.

HELP! no me deja hacer vídeos llamadas en ws, en j7 prime
won't let me make video calls on

facing random reboot twice on setup screen, now it boot. no flash light on camera (light burst from screen?) like stock oreo.
hyperlapse - wide selfie nor working
i dont even know what is hyperlapse

@Astrako will you keep H-ROM A7 and S20 versions support simultaneously?

Adriano-A3 said:
@Astrako will you keep H-ROM A7 and S20 versions support simultaneously?
Click to expand...
Click to collapse
Don't ask ?... just install the rom and enjoy bro

Mscreams said:
Don't ask ... just install the rom and enjoy bro
Click to expand...
Click to collapse
Bruh

I can't install it please get me a complete manual for install
With spaget x project get bootloop l
Without show logo cant boot
Recovery: Orange Fox
Vendor 2
G610f/ds

use vendor create v1 not v2

yahiaashraf111 said:
use vendor create v1 not v2
Click to expand...
Click to collapse
And don't need change recovery ?
Now it's OrangeFox based twrp 3.4.0
Should install spaget x?

What working :
1. Wifi
2. Mobile data
3. Hotspot
4. Bluetooth
5. Gps
6. Camera
7. Phone
8. Live drawing camera
9. screen recording
10. Almost everything are working well
But, so far i found some 'not so important' bugs :
1. Opening battery usages give me FC.
2. I cant rename, remove files inside priv-app folder, but copying files to folder inside priv-app worked.
3. Removing app which located on priv-app folder using titanium backup, did not removed the apps. After reboot, the apps are there again. (Problem number 2, i cant remove apk inside priv-app)
4. no blue-light filter (i dont use it, so i dont care)
5. Some camera feature not working (hyperlase, wide selfie, front facing camera only support 4:3 size for taking photo, but video are fine). I dont know what is the function of icon at the right side of resolution inside camera (right side of 4:3 icon)
6. Since aod is not working and im not using it, better remove it.
7. Cant change clock style on lockscren (inside phone setting), but fixed by installing lockstar
8. Screen mode inside display setting has no effect at all (even stock rom does not have that feature, so.... No problem at all)
I really love this rom! Why? Because :
1. Battery life is PERFECT
2. Performance? This rom is running perfectly smooth on UI, and also while playing game and opening apps.
3. Multitasking is great
4. Android Q on 2016 device? Hell yeah.
Please fix the 1st and 2nd problem, because i need to replace gametool apk inside priv-app folder.

Installation variant 610mn-16gb
Installation variant 610mn-16gb
1- Have prepared the Vendor.zip and revertvendor files specifically this => Spaget Treble ARM64 Vendor V3.0 Based on A750FN Vendor <= not vendor v2.0 and it is not necessary to download Exynos7870_Spaget_X-V3.0. If you want root, download the magisk provided on the first page. Also have OrangeFox-R10.1_2-Unofficial-on7xelte and a version of a preferable rom oreo available to reverse the vendor and reinstall for anything.
2- Before flash create vendor, install OrangeFox-R10.1_2-Unofficial-on7xelte and restart fox recovery, then flash create vendor, without deleting anything and restarting recovery, once in TWRP-Fx, follow the steps on the first page , wipe 1DC, 2C, 3S, 4V, 5D. Internal memory is not necessary (if you view the preload between the partitions, in this step, read notes below), once the wipe has finished, install the ROM and restart. Everything should work perfectly, (at the end of the startup, perform a hard restart before configure, and then it starts without problems, that happened to me, in particular, since generally when finishing the installation of the ROM and when rebooting it usually restarts again, in this case it did not, I start directly until hello .. and then reboot)
3- Optional, once the startup is configured, restart TWRP-FX and flash magisk.
Notes: At the beginning, you could not install any ROMx64, or you needed the vendor partition, you can check the following: when you install TWRP 3.3 and when you start TWRP, the following appears in red letters at the top: “recovery is not seandroid enforcing… .. etc ”it only comes out with twrp from version 3.3, definitely you will not be able to install any rom x64, gsi, etc, since you don't have to get any errors or messages. It means that also like mine you have the smartphone since marshmallow 6.0 and it was root with supersu and odin, and you were making updates from that version; solution: restore with stock Firmware android 8.1 via odin all the partitions (BL-AP-CP-CSC-USERDATA) can be found on the network and downloaded according to your country, but always being oreo stock 8.1. Once this is done, install TWRP 3.2 with odin and then root with magisk latest stable version, not the one provided here. After that, you will be able to install several roms that you could not previously and will not have problems with the vendor, create and revert if you want. Some only install the AP to fix, but I decided on a full restore and start from scratch.
PD: I felt the need to share this experience with you so that those who have the 610mn and have problems can install it without problems, always remember to back up your important data before flashing and having a good battery charge *GOOGLE TRANSLATE*

RODRI2688 said:
Installation variant 610mn-16gb
1- Have prepared the Vendor.zip and revertvendor files specifically this => Spaget Treble ARM64 Vendor V3.0 Based on A750FN Vendor <= not vendor v2.0 and it is not necessary to download Exynos7870_Spaget_X-V3.0. If you want root, download the magisk provided on the first page. Also have OrangeFox-R10.1_2-Unofficial-on7xelte and a version of a preferable rom oreo available to reverse the vendor and reinstall for anything.
2- Before flash create vendor, install OrangeFox-R10.1_2-Unofficial-on7xelte and restart fox recovery, then flash create vendor, without deleting anything and restarting recovery, once in TWRP-Fx, follow the steps on the first page , wipe 1DC, 2C, 3S, 4V, 5D. Internal memory is not necessary (if you view the preload between the partitions, in this step, read notes below), once the wipe has finished, install the ROM and restart. Everything should work perfectly, (at the end of the startup, perform a hard restart before configure, and then it starts without problems, that happened to me, in particular, since generally when finishing the installation of the ROM and when rebooting it usually restarts again, in this case it did not, I start directly until hello .. and then reboot)
3- Optional, once the startup is configured, restart TWRP-FX and flash magisk.
Notes: At the beginning, you could not install any ROMx64, or you needed the vendor partition, you can check the following: when you install TWRP 3.3 and when you start TWRP, the following appears in red letters at the top: “recovery is not seandroid enforcing… .. etc ”it only comes out with twrp from version 3.3, definitely you will not be able to install any rom x64, gsi, etc, since you don't have to get any errors or messages. It means that also like mine you have the smartphone since marshmallow 6.0 and it was root with supersu and odin, and you were making updates from that version; solution: restore with stock Firmware android 8.1 via odin all the partitions (BL-AP-CP-CSC-USERDATA) can be found on the network and downloaded according to your country, but always being oreo stock 8.1. Once this is done, install TWRP 3.2 with odin and then root with magisk latest stable version, not the one provided here. After that, you will be able to install several roms that you could not previously and will not have problems with the vendor, create and revert if you want. Some only install the AP to fix, but I decided on a full restore and start from scratch.
PD: I felt the need to share this experience with you so that those who have the 610mn and have problems can install it without problems, always remember to back up your important data before flashing and having a good battery charge *GOOGLE TRANSLATE*
Click to expand...
Click to collapse
Hello
Thanks for your help
This installation help isn't for F variant?

SyntaxDroid said:
Hello
Thanks for your help
This installation help isn't for F variant?
Click to expand...
Click to collapse
Really if it could work, especially if you have been making updates from android v6, it is best to start the root from android v8.0 or 8.1, once achieved, try the installation, but if you already come from that version, you shouldn't have drawbacks. Try it, it's really worth it.

[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

[DEPRECATED][ROM][10][Unofficial][TUCANA] LineageOS17.1

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* Your warranty is now void.
*
* 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 ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
LineageOS is a free, community-built, aftermarket firmware distribution of Android 10, 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 restores 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 our Gerrit Code Review.
What's working:
Boots
RIL (Calls, SMS, Data)
Wi-Fi
Bluetooth
IR camera
Camera
Camcorder
FOD
Video Playback
Audio
Sensors
Flash
GPS/GNSS
VoLTE
Known issues:
Selinux permissive
Instructions:
Make sure you have a custom recovery installed
Make sure you have miui_TUCANAGlobal_V12.0.3.0.QFDMIXM or later installed (Android 10 only)
Download LineageOS 17.1 for tucana
Boot into recovery
Perform a DATA Format
Flash LineageOS 17.1 Rom
(Flash Gapps/Magisk) (for Magisk users see below)
Wipe DALVIK/CACHE
Reboot
Magisk:
To get Magisk working: First flash Magisk 20.4 and right after that Magisk 21.1 or later
Download:
lineage-17.1-20201206-UNOFFICIAL-tucana.zip
Prebuilt kernel source:
Kernel source
Donate:
Donation URL
Special thanks to:
LineageOS
Chema
AndroidHQ254
Hlcpereira
XDA:DevDB Information
LineageOS 17.1 tucana, ROM for the Xiaomi Mi Note 10
Contributors
alibei
Source Code: https://github.com/alibei/android_device_xiaomi_tucana
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: V12.0.3.0.QFDMIXM
Based On: LineageOS
Version Information
Status: Beta
Created 2020-11-28
Last Updated 2020-11-29

Changelog:
Code:
2020-12-06 ~ fixed the FOD brightness
2020-11-29 ~ Some improvements for FOD and UI (thanks Chema)
2020-11-28 ~ Initial release

Congratulations for your work .

Nice job!!!!

WoW....miui 12.0.3 do you need full ROM or just the firmware?

Kosecki99 said:
WoW....miui 12.0.3 do you need full ROM or just the firmware?
Click to expand...
Click to collapse
Full ROM, I checked before only vendor firmware and its didn't work.
You can get full ROM here: https://xiaomifirmwareupdater.com/miui/tucana/stable/V12.0.3.0.QFDMIXM/ very fast download speed

Congratulations on having achieved the impossible. Thank you for your effort and hours of selfless work. +1000

Great job :good:

Bug detected.
When you put security for the first time, be it fingerprint, pin, or whatever, there is no problem, but when you deactivate all security measures, the options Always Active and New Notifications on Screen + Screen Lock disappear without the possibility of see them again

You fixed Donation button, sweet
Code:
Transaction ID: 20444655146528013
ADB is fixed too

veimus said:
You fixed Donation button, sweet
Code:
Transaction ID: 20444655146528013
ADB is fixed too
Click to expand...
Click to collapse
Thank you for your donation

I've tried to flash it on my Mi Note 10, but I ended up stuck on bootloop.
Here's what I've exactly done:
- Since I was on MIUI 12.0.2, I've downloaded and flashed MIUI 12.0.3 (the one linked before, recovery version). Although I did flash it, I didn't boot up the phone, nor did go through setup wizard. I just rebooted back to TWR
- Performed Data format (advanced wipe - selected only "Data")
- flashed LOS
- format Dalvik/Cache
- Reboot
Could the issue be not going through first-boot setup after flashing to MIUI 12.0.3? Also, I'm trying to boot my phone on this MIUI right now, but it is definitely stuck on MIUI logo. I guess I screwed up big time.

tryingtogitgud said:
I've tried to flash it on my Mi Note 10, but I ended up stuck on bootloop.
Here's what I've exactly done:
- Since I was on MIUI 12.0.2, I've downloaded and flashed MIUI 12.0.3 (the one linked before, recovery version). Although I did flash it, I didn't boot up the phone, nor didn't go through setup wizard. I just rebooted back to TWRP
- Performed Data format (advanced wipe - selected only "Data")
- flashed LOS
- format Dalvik/Cache
- Reboot
Could the issue be not going through first-boot setup after flashing to MIUI 12.0.3? Also, I'm trying to boot my phone on this MIUI right now, but it is definitely stuck on MIUI logo. I guess I screwed up big time.
Click to expand...
Click to collapse
MIUI should normally boot. Maybe you can try the MIUI fastboot rom.

tryingtogitgud said:
I've tried to flash it on my Mi Note 10, but I ended up stuck on bootloop.
Here's what I've exactly done:
- Since I was on MIUI 12.0.2, I've downloaded and flashed MIUI 12.0.3 (the one linked before, recovery version). Although I did flash it, I didn't boot up the phone, nor didn't go through setup wizard. I just rebooted back to TWRP
- Performed Data format (advanced wipe - selected only "Data")
- flashed LOS
- format Dalvik/Cache
- Reboot
Could the issue be not going through first-boot setup after flashing to MIUI 12.0.3? Also, I'm trying to boot my phone on this MIUI right now, but it is definitely stuck on MIUI logo. I guess I screwed up big time.
Click to expand...
Click to collapse
The thing is, you went to advanced wipe and only picked "Data" only... If you do advanced wipe... You have to also choose "Internal," both "Cache's"and "System". It's easier to just go to "Wipe" press the "Format data" option and type in "yes".
Plus.... when coming from another Miui Rom, you have to wipe everything from the wipe options written above.
So do that.. and then follow the steps below.
-Reboot to TWRP (in case your PC does not see your phone connected to load 12.0.3.0).
-Then load the 12.0.3.0 full rom, flash... "format data option", type in "yes"...
-Reboot to TWRP again.....
-And then flash Lineage, GAPPS and the latest Magisk 21.1.. and reboot "System".
Now if it doesn't come through.. flash 20.4 Magisk first, reboot to TWRP.. flash 21.1 Magisk and reboot "System".

Wmateria said:
The thing is, you went to advanced wipe and only picked "Data" only... If you do advanced wipe... You have to also choose "Internal," both "Cache's"and "System". It's easier to just go to "Wipe" press the "Format data" option and type in "yes".
Plus.... when coming from another Miui Rom, you have to wipe everything from the wipe options written above.
So do that.. and then follow the steps below.
-Reboot to TWRP (in case your PC does not see your phone connected to load 12.0.3.0).
-Then load the 12.0.3.0 full rom, flash... format data..
-Reboot to TWRP again.....
-And then flash Lineage, GAPPS and the latest Magisk 21.1.. and reboot.
Click to expand...
Click to collapse
Of course, I did wrong data format! Now I've done it properly and it works, thank you!

Great work guys! Super props

Amazing work alibei , Chema and henrique thanks for this amazing rom

Is there any way to lunch camera and take pictures without unlocking the phone ? Can't find this option

veimus said:
Is there any way to lunch camera and take pictures without unlocking the phone ? Can't find this option
Click to expand...
Click to collapse
Can you explain please? I don't know what you mean.

any Rom type RR or ZenxOS? ... thanks

Database Develop

welcome