{
"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 12L (S), 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. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.
GPL compliance:
Device tree source code: LineageOS/android_device_xiaomi_beryllium
Kernel source code: LineageOS/android_kernel_xiaomi_sdm845
Working:
Camera (and flashlight)
WiFi
Bluetooth
Telephony (Calls and Data)
IMS (RCS, VoLTE and WiFi Calling)
Audio (Record and Playback)
Video Playback
Sensors
GPS
Encryption (FBE)
WiFi Display
Broken:
Nothing (?)
Compatibility:
Compatible with all Xiaomi Poco F1 variants.Builds are based off the Xiaomi's Android 10 firmware with proprietary blobs from MIUI v12.0.3.0 global stable package.
Device wiki:
Official wiki link
Downloads:
Official download links
Installation:
Follow instructions found in the respective wiki page
Wow. So I just tried from TWRP upgrading my pocof1 to LineageOS 19.1 and 20220521. And despite seeing nothing in the change log, this one prompted at boot for an unlock password and a after the usual long delay at a major OS change it came up!
Just wow.
I can live with manually going into TWRP and updating from /data/lineageos_updates the OTA updates.
Encryption still listed with "getprop ro.crypto.type" as block.
Though it does seem now like TWRP may be unable to decrpt /data. Not sure why, as we are still FDE and it that doesn't seem to have changed....a bit weird.
Are there any downsides to the Lineage recovery as opposed to TWRP? I've only ever used TWRP before but apparently Lineage recovery seems to work more reliably for this build. Is it true that TWRP won't work with encryption and OTA updates need to be flashed manually in TWRP?
With Lineage recovery, can I still backup, restore, root with Magisk, and install Gapps?
@bgcngm Offline charging is broken, I suspect it's a kernel problem.
I used firmware:
fw_beryllium_miui_POCOF1Global_V12.0.3.0.QEJMIXM_cf3fccffce_10.0
and latest LineageOS build.
I can't grab a log because to trigger it you have to connect it to the power adapter once it's turned down, anyway it stays stuck forever on the POCOPHONE by Xiaomi logo unless I force shut down it.
All of the features are working perfectly and its stable.Its a good ROM
There is a bug of offline charging,do fix it if possible
Thank you for the rom
@bgcngm
Lineage Recovery is more limited. You can still flash Magisk and gapps. But it doesn't seem to be able to mount /data either (well in a user accessible way from what I have seen). So to flash Magisk and Gapps you need to use adb or have them on a (I guess non adopted) sdcard, which is what I have done on a tablet I have. i.e. the sdcard needs to be plain exfat, vfat etc.
The big downside for me is the backup/restore. Lineage are recommending seedvault, but this doesn't appear to be in the same league as a backup/restore from TWRP which will do a full restore of your /data (so everything, a true snapshot of all settings). Seedvault seems to do most app settings but not all and not all OS settings. Not tried restoring from seedvault, so I'm maybe being harsh but doesn't seem to be the nice out of band backup that TWRP did.
But I guess it looks like this will no longer able to mount /data in TWRP after a 19.1 update even though still FDE. So I guess that upside is now gone too....sad. So maybe Seedvault it is!
just to chime in : I too just upgraded my FDE device to 19.1. the 21-05 update worked flawlessly in this regard
simpz said:
But I guess it looks like this will no longer able to mount /data in TWRP after a 19.1 update even though still FDE. So I guess that upside is now gone too....sad. So maybe Seedvault it is!
Click to expand...
Click to collapse
doesn't that just mean we need to wait until TWRP fully supports 12L encryption ?
fairyrobot said:
doesn't that just mean we need to wait until TWRP fully supports 12L encryption ?
Click to expand...
Click to collapse
Maybe. But given new devices only do FBE and not FDE not sure if the TWRP guys will support any update to FDE, might be FBE.
afaik neither FBE nor FDE work (well) with current TWRP, so maybe one fix on their side fixes it all ? we'll see
fairyrobot said:
afaik neither FBE nor FDE work (well) with current TWRP, so maybe one fix on their side fixes it all ? we'll see
Click to expand...
Click to collapse
Did anyone from the TWRP team ever give any hints when 12 support may be ready? Really want to update to 12.1 in some capacity but LinRec is just so frustratingly limited.
Alias X said:
Did anyone from the TWRP team ever give any hints when 12 support may be ready? Really want to update to 12.1 in some capacity but LinRec is just so frustratingly limited.
Click to expand...
Click to collapse
no ETA was ever given, but there was some activity in the repo : https://github.com/TeamWin/android_bootable_recovery/commits/android-12.1
Munzu said:
Are there any downsides to the Lineage recovery as opposed to TWRP? I've only ever used TWRP before but apparently Lineage recovery seems to work more reliably for this build. Is it true that TWRP won't work with encryption and OTA updates need to be flashed manually in TWRP?
With Lineage recovery, can I still backup, restore, root with Magisk, and install Gapps?
Click to expand...
Click to collapse
Lineage recovery is the only official supported at the moment. Of course it can't decrypt userdata, but that was never intended anyway.
Reynald0 said:
Offline charging is broken, I suspect it's a kernel problem.
Click to expand...
Click to collapse
I am aware of that and will try to fix it as soon as I have time. Not something with big priority.
fairyrobot said:
afaik neither FBE nor FDE work (well) with current TWRP, so maybe one fix on their side fixes it all ? we'll see
Click to expand...
Click to collapse
I doubt that we will ever see a TWRP recovery that supports FBE decyption on this device.
simpz said:
Lineage are recommending seedvault, but this doesn't appear to be in the same league as a backup/restore from TWRP which will do a full restore of your /data
Click to expand...
Click to collapse
Seedvault is a horrible backup solution and there are many reasons why which I won't go into on this thread, but the main cause is because Seedvault uses the ADB backup method which gives apps the rights to whether you are allowed to backup your own data. This is why you see so many "app doesn't support" backup excuses from Seedvault. It is a useless backup implementation, even for non-technical users - saying this from having to use Seedvault to try to restore my own data before the restore just didn't work at all and I was left with restoring my TWRP image to fix it and use a proper backup utility.
NeoBackup (OAndBackupX) has never given me any issues, so if you want to use Android 12, this should help until TWRP is available:
GitHub - NeoApplications/Neo-Backup: backup manager for android
backup manager for android. Contribute to NeoApplications/Neo-Backup development by creating an account on GitHub.
github.com
Best part? You can backup all your data for each app, including protected device data, not being forced to only be able to backup certain apps because the app tells Seedvault you aren't allowed to which is a limitation of Seedvault itself and other annoying issues:
Add an option to disregard the `allowBackup` option for Android 12 · Issue #165 · seedvault-app/seedvault
Android 11 ignores the allowBackup manifest attribute for device to device transfers (https://developer.android.com/about/versions/11/behavior-changes-11#device-to-device-file-transfer). That means...
github.com
Choose what apps will get restored · Issue #309 · seedvault-app/seedvault
Somewhat related to #100 When I restore a backup, maybe I don't want to restore some apps, I used to have before. IIRC this option was not offered but I know some device transfer services/apps like...
github.com
I've been using sanity's google cam v9.5 since 2019. after update and clean install to the latest 21-05 19.1. it says "app not installed". downgrade to 07-05 and same error happen. but it worked fine before(on 18.1 or 07-05 19.1)
x1a2leader said:
I've been using sanity's google cam v9.5 since 2019. after update and clean install to the latest 21-05 19.1. it says "app not installed". downgrade to 07-05 and same error happen. but it worked fine before(on 18.1 or 07-05 19.1)
Click to expand...
Click to collapse
Did you tried sanitys 9.6 from my collection? It's modded to work with new android versions.
the music player does not delete tracks.
I noticed yesterday that gesture typing on the AOSP keyboard does not work for dutch, but _does_ work for english. is this a known bug ? (seen on 21-05 build)
fairyrobot said:
I noticed yesterday that gesture typing on the AOSP keyboard does not work for dutch, but _does_ work for english. is this a known bug ? (seen on 21-05 build)
Click to expand...
Click to collapse
Yeah, me too. I also can't use the AOSP spellchecker in Dutch, because the dictionary for Dutch doesn't exist. Switched to Microsoft SwiftKey in the meantime.
Abdel1993 said:
Yeah, me too. I also can't use the AOSP spellchecker in Dutch, because the dictionary for Dutch doesn't exist. Switched to Microsoft SwiftKey in the meantime.
Click to expand...
Click to collapse
it seems to download a dictionary, but it still doesn't work. but it seems it's not just me then
Related
{
"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, which is designed to increase performance and reliability over stock android for your device.
All the source code for LineageOS is available in the LineageOS Github repo. If you would like to contribute to LineageOS, please visit our Wiki for more details.
IMPORTANT NOTES:
1. If you use twrp it will ask if you want to install the twrp app. Make sure you tap "DO NOT INSTALL".
2. If you care about your stuff, make a backup in TWRP first, just in case. Transfer it to a pc, along with all your stuff in internal storage.
3. The newest vendor, radio, & bootloader img's are included in the rom zip, so no need to worry about flashing those manually.
4. Lineage comes with adb root that you can enable in developer options, but if you want root for apps, flash magisk in recovery (after renaming magisk.apk to magisk.zip). Just don't flash it during initial lineage install, as it's known to cause bootloop if you do.
Downloads:
marlin rom: https://download.lineageos.org/marlin
sailfish rom: https://download.lineageos.org/sailfish
gapps: (gapps are optional) link WARNING: Only use nano or pico because the system partition is too small on our device.
google fi gapps addon: if your carrier is Google Fi, flash this zip right after flashing the gapps zip. https://androidfilehost.com/?fid=8889791610682871038
Instructions:
FOR INITIAL INSTALL
marlin: https://wiki.lineageos.org/devices/marlin/install
sailfish: https://wiki.lineageos.org/devices/sailfish/install
FOR UPDATING
For normal updating from official 17.1 to a newer official 17.1, follow these steps:
marlin: https://wiki.lineageos.org/devices/marlin/update
sailfish: https://wiki.lineageos.org/devices/sailfish/update
Protip: Enable "Prioritize update process" in the Updater preferences to make it go faster
NOTE: If you're updating from my unofficial build to the official nightlies, follow steps here.
Alternative manual updating instructions:
1. boot into lineage recovery.
2. install rom zip.
3. if you use gapps or magisk, select the "reboot into recovery" option, then install those zips.
FOR UPGRADING (From official 16.0 to official 17.1, for example)
marlin: https://wiki.lineageos.org/devices/marlin/upgrade
sailfish: https://wiki.lineageos.org/devices/sailfish/upgrade
Changelog
marlin
sailfish
Bug reporting
https://wiki.lineageos.org/bugreport-howto.html
Source Code:
Marlin Device tree: https://github.com/LineageOS/android_device_google_marlin/tree/lineage-17.1
Sailfish Device tree: https://github.com/LineageOS/android_device_google_sailfish/tree/lineage-17.1
Kernel tree: https://github.com/LineageOS/android_kernel_google_marlin/tree/lineage-17.1
Vendor tree: https://github.com/TheMuppets/proprietary_vendor_google/tree/lineage-17.1
Credits:
Many thanks to my fellow LineageOS team members and all the contributors out there in the community. :good:
Android version: 10
Kernel version: 3.18.137
Status: Nightly
That's great! Does this have Google dialer included?
Thank you for your awesome work
Intriguing ?.
<Mod edit: Quoted OP removed>
A lot of Google's apps crushing , the rest is all good . I know is a beta so no complaints
Hello!! I installed this assembly, I liked it, but later can I switch to nightly assemblies from this assembly?
alin919 said:
A lot of Google's apps crushing , the rest is all good . I know is a beta so no complaints
Click to expand...
Click to collapse
I had that but it was because I also wiped system and cache. I reflashed stock and only wiped data and now Google apps work except for Gmail
Just reporting, I am not passing safety net
alin919 said:
A lot of Google's apps crushing , the rest is all good . I know is a beta so no complaints
Click to expand...
Click to collapse
Do you have Magisk installed? I removed Magisk and now all Google apps work
Zehlek said:
Do you have Magisk installed? I removed Magisk and now all Google apps work
Click to expand...
Click to collapse
I do now , but is weird ... now drive is working and calendar and gmail not ( second time installed clean and downloads the apps from playstore before got root )
Try this, it helped me
Zehlek said:
Just reporting, I am not passing safety net
Click to expand...
Click to collapse
This video helped me pass safety-net
https://youtu.be/8ATH032lIXs
An easy fix, for anyone with the gmail issue, you just have to go to settings->apps->gmail->permissions, and allow permissions to contacts and calendar.
EDIT: I'll try to figure out the issue of why gmail is not being granting permissions automatically, like it should.
But in the meantime, i'll just include gmail in my builds. That way it has that right permissions and just works like it should. If you don't want the app, you can just go to settings and disable it.
EDIT#2: New builds are available in first post. One notable feature that was added is, network traffic monitor in statusbar. :good:
Note: I don't have a sailfish so that build is untested, but it should work fine. Please someone give it a try and let us know if it's ok. Confirmed, it's working good on sailfish too.
razorloves said:
EDIT#2: New builds are available in first post. One notable feature that was added is, network traffic monitor in statusbar.
Note: I don't have a sailfish so that build is untested, but it should work fine. Please someone give it a try and let us know if it's ok. :good:
Click to expand...
Click to collapse
Incredible thanks!! I'll test this out
Is the system mounted r/w on this rom?
razorloves said:
An easy fix, for anyone with the gmail issue, you just have to go to settings->apps->gmail->permissions, and allow permissions to contacts and calendar.
EDIT: I'll try to figure out the issue of why gmail is not being granting permissions automatically, like it should.
But in the meantime, i'll just include gmail in my builds. That way it has that right permissions and just works like it should. If you don't want the app, you can just go to settings and disable it.
EDIT#2: New builds are available in first post. One notable feature that was added is, network traffic monitor in statusbar.
Note: I don't have a sailfish so that build is untested, but it should work fine. Please someone give it a try and let us know if it's ok. :good:
Click to expand...
Click to collapse
So far so good, I saw this that root is disabled, is there anyway to enable it without using Magisk?
cyberbandit1998 said:
Is the system mounted r/w on this rom?
Click to expand...
Click to collapse
ikr, it was read only on the stock rom, immediately went back to Los16 lol
so, it seems as if there are no real game-breaking issues out of the gate?? I'm looking forward to trying this later but was holding off for some more feedback, so far it seems to be pretty positive... one (stupid) question... After flashing this can you easily just flash back to a PIE rom if need be, or once you go Android 10 you can't go back?
yes you can
johnblundon said:
so, it seems as if there are no real game-breaking issues out of the gate?? I'm looking forward to trying this later but was holding off for some more feedback, so far it seems to be pretty positive... one (stupid) question... After flashing this can you easily just flash back to a PIE rom if need be, or once you go Android 10 you can't go back?
Click to expand...
Click to collapse
I have flashed stock pie from Android 10 a couple of times
Zehlek said:
So far so good, I saw this that root is disabled, is there anyway to enable it without using Magisk?
Click to expand...
Click to collapse
not yet. have to use magisk.
johnblundon said:
After flashing this can you easily just flash back to a PIE rom if need be
Click to expand...
Click to collapse
yep, i did it the other day. went from lineage 17 to 16, with just a data wipe. no issues.
So device personalization services app kept crashing so I uninstalled it
also trying to enable black theme in settings makes settings app crash
Also had the Gmail permission bug thanks for posting the fix ?
Also why was twrp overwritten by stock Google recovery ?
I didn't see a warning about that anywhere in op
Note I did a clean install wiped all partitions but internal storage in twrp 3.3.0.0 before flashing rom and then magisk zip
{
"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"
}
Background:
This is a natural continuation/extension of the LineageOS 17.x GSIs I've been making since November 2019.
LineageOS is a free, community built, aftermarket firmware distribution of Android, 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. 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 Gerrit Code Review.
Click to expand...
Click to collapse
Disclaimer:
This is still mostly a LineageOS team / PHH @phhusson effort, credits to them and all associated for making all this possible.
No flashing instructions will be offered. If you're here in this forum, you should know what you're doing.
No guarantees that everything would work. This is a GSI, bugs are bound to happen.
Download:
https://sourceforge.net/projects/andyyan-gsi/files/
Compressed as .xz archives - extract first.
Vanilla except for these changes:
Modifications needed to make it build/boot/feature-complete
Revived navbar layout tuning via sysui_nav_bar tunable
Disabled "vendor mismatch" warning on boot
Signature spoofing support from MicroG
Default stretch-to-fullscreen (force apps to render in longer than 16:9)
Stuff on GitHub (builders-only):
Since builders' stuff aren't really interesting to end users, I decided not to separately document the modifications needed in this post; instead just check out the scripts/patches, where most things should be self-explanatory: lineage_build_unified, lineage_patches_unified (where patches_treble_phh contains PHH's treble_patches adjusted for LOS). Not the cleanest code, but should help if you need some clues.
Donate?
https://paypal.me/AndyCGYan
Reserved
Couple of things to note:
I now have a rather taxing day job, and can't devote nearly as much time/effort into this as I did as a student.
As always, you are strongly advised to try PHH's AOSP first and identify/report issues there, before moving onto other GSIs that are based on his work. Please report bugs here only if it's specific to this GSI.
Thanks to patches from @eremitein , Magisk compatibility is partially restored. For devices that still don't play well with it (e.g. kernel restrictions implemented by OEM), use PHH-SU instead. Install the app and you'll get root for apps.
A-only and VNDKLite targets are now generated from AB images instead of built from source, see sas-creator. Kinda hacky and might be buggy. Move on to an AB device if you can.
To mount /system RW on AB devices, refer to this.
exfat SD cards still don't seem to work. Any help related to this would be appreciated.
Initial builds are based on PHH v300.j and December security patches.
Building-related bits have been published, but only for AB targets - I'm not sure if I want to integrate sas-creator yet.
Dear AndyYan. Thank you very much for all your work on these Roms. Do you think that I can flash the latest BitGapps R19 which was available a few weeks ago on the BitGapps website ?
Great job dude! I ammire you
Relesse 18 thank You my friend
Arm64 avS can't flash the beta versions of GApps and NikGApps, otherwise, constantly restart to TWRP.
Test again, it should be GApps problem, SD821 vndk27 Aonly everything is fine. Thank you.
The ROM bootlooped on Moto E6, though this is a very new ROM so I think I'll revert back to your LOS 17.1 ROM until things are a bit more ironed out.
I think this is the only Android 11 GSI so we all greatly appreciate your work. We're rooting for you
koyo said:
I think this is the only Android 11 GSI so we all greatly appreciate your work. We're rooting for you
Click to expand...
Click to collapse
Hey hey, it's still based on PHH's AOSP R, which has been out there for quite a while, just without an XDA thread. Let's all thank him first
Booted up just fine but no mobile data for me even after trying the IMS settings. Great work and thank you for the release!
Works perfectly on xt1962-1 or moto g7 river using LOS17.1 base
'just a report, tried it on oldies J730G booted fine wifi works, sim works, unable to play medias, reboots by itself about every 10mins or so, very snappy though. Thanks. Off to flashing another one, I'm developing a bad habit, just because I can doesn't mean I should
Edited:
Thanks to Phh for fixing ussd on v300L
Successfully installed the a/b-GSI from 2020-12-19 on Xiaomi MI 10T lite (gauguin) via fastbootd (necessary to handle dynamic partitions!).
Camera quality is awefull (;-) ) but the rest i tested so far looks promissing (WiFi works, Fingerprint works ... well see what make problems ;-) ).
Well done guys!!!
Cheers Kurt
Installed it successfuly on my Honor 9 (A/B). Almost everything works. Except:
- SD-Card don't work (as mentioned)
- Can't flash gapps, because of missing twrp for my device
Saftpresse99 said:
Installed it successfuly on my Honor 9 (A/B). Almost everything works. Except:
- SD-Card don't work (as mentioned)
- Can't flash gapps, because of missing twrp for my device
Click to expand...
Click to collapse
For my gauguin, i used root and Franko-Kernel-Manager to flash NikGapps ... had to mount /system rw manually, but at least it worked.
Cheers
Kurt
Kurt Krummbein said:
For my gauguin, i used root and Franko-Kernel-Manager to flash NikGapps ... had to mount /system rw manually, but at least it worked.
Cheers
Kurt
Click to expand...
Click to collapse
Thanks. I now using phhusson gsi. With gapps.
Perhaps it is easier to mount r/w with a vndklite Version.
Does anybody know, if it possible to switch between this rom and phhusson rom, without loose data?
Saftpresse99 said:
Thanks. I now using phhusson gsi. With gapps.
Perhaps it is easier to mount r/w with a vndklite Version.
Does anybody know, if it possible to switch between this rom and phhusson rom, without loose data?
Click to expand...
Click to collapse
Already tested between caosR and los18, just wipe system, cache and dalvik/art via twrp , flash new system img (+gapps if existed before), and reboot.
AndyYan said:
Background:
This is a natural continuation/extension of the LineageOS 17.x GSIs I've been making since November 2019.
Disclaimer:
This is still mostly a LineageOS team / PHH @phhusson effort, credits to them and all associated for making all this possible.
No flashing instructions will be offered. If you're here in this forum, you should know what you're doing.
No guarantees that everything would work. This is a GSI, bugs are bound to happen.
Download:
https://sourceforge.net/projects/andyyan-gsi/files/
Compressed as .xz archives - extract first.
Vanilla except for these changes:
Modifications needed to make it build/boot/feature-complete
Revived navbar layout tuning via sysui_nav_bar tunable
Disabled "vendor mismatch" warning on boot
Signature spoofing support from MicroG
Default stretch-to-fullscreen (force apps to render in longer than 16:9)
Stuff on GitHub (builders-only):
Since builders' stuff aren't really interesting to end users, I decided not to separately document the modifications needed in this post; instead just check out the scripts/patches, where most things should be self-explanatory: treble_build_los, treble_patches (PHH's treble_patches adjusted for LOS). Not the cleanest code, but should help if you need some clues.
Donate?
https://paypal.me/AndyCGYan
Click to expand...
Click to collapse
AndyYan said:
Background:
This is a natural continuation/extension of the LineageOS 17.x GSIs I've been making since November 2019.
Disclaimer:
This is still mostly a LineageOS team / PHH @phhusson effort, credits to them and all associated for making all this possible.
No flashing instructions will be offered. If you're here in this forum, you should know what you're doing.
No guarantees that everything would work. This is a GSI, bugs are bound to happen.
Download:
https://sourceforge.net/projects/andyyan-gsi/files/
Compressed as .xz archives - extract first.
Vanilla except for these changes:
Modifications needed to make it build/boot/feature-complete
Revived navbar layout tuning via sysui_nav_bar tunable
Disabled "vendor mismatch" warning on boot
Signature spoofing support from MicroG
Default stretch-to-fullscreen (force apps to render in longer than 16:9)
Stuff on GitHub (builders-only):
Since builders' stuff aren't really interesting to end users, I decided not to separately document the modifications needed in this post; instead just check out the scripts/patches, where most things should be self-explanatory: treble_build_los, treble_patches (PHH's treble_patches adjusted for LOS). Not the cleanest code, but should help if you need some clues.
Donate?
https://paypal.me/AndyCGYan
Click to expand...
Click to collapse
Thanks for your work . Your system working very fast , I share your system https://forum.xda-developers.com/t/gsi-11-lineageos-18-x-gsi-all-archs.4211857/ . Thanks for this system.
Sir ur BvS builds never pass safety net for me not even on A10 ur BvN were flawless....can u help please how to pass...I tried phh/secuize, magisk hide, changing fingerprint to various pixel devices, adding secure file but nothing works
I am on 18.1 rn and using Nokia 8.1 sdm 710
Or can u please just switch back to BvN
{
"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"
}
Background:
This is a natural continuation/extension of the LineageOS 18.x GSIs I've been making since 2020.
LineageOS is a free, community built, aftermarket firmware distribution of Android, 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. 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 Gerrit Code Review.
Click to expand...
Click to collapse
Disclaimer:
This is still mostly a LineageOS team / PHH @phhusson effort, credits to them and all associated for making all this possible.
No flashing instructions will be offered. If you're here in this forum, you should know what you're doing.
No guarantees that everything would work. This is a GSI, bugs are bound to happen.
Must-read:
You are STRONGLY ADVISED to try PHH's AOSP of equivalent version FIRST and identify/report issues there, before moving onto other GSIs that are based on his work, including this one.
If you do find bugs on this GSI and want to report, then you MUST try reproducing on AOSP, and ONLY proceed to report here when it's specific to this GSI. This filters out bugs common to all PHH-based GSIs, which you should let PHH know, not me. I might silently ignore your report if you skip this.
Download:
https://sourceforge.net/projects/andyyan-gsi/files/
Compressed as .xz archives - extract first.
Stuff on GitHub (builders-only):
Since builders' stuff aren't really interesting to end users, I decided not to separately document the modifications needed in this post; instead just check out these repos, where most things should be self-explanatory. Not the cleanest code, but should help if you need some clues.
lineage_build_unified - my unified script for building
lineage_patches_unified - my unified patches for building, including patches from PHH
sas-creator - generates VNDKLite and secure variants, can be used without a building environment
Donate?
https://paypal.me/AndyCGYan
Reserved
Notes:
I now have a rather taxing day job, and can't devote nearly as much time/effort into this as I did as a student.
GAPPS builds are offered as-is without guarantees. Read #10 for more.
/system is RO on regular builds and RW on VNDKLite builds. VNDKLite builds can be used on most non-VNDKLite devices as well.
ADB is intentionally insecure, even on first boot (turned on by default and no authentication needed). GSIs are more fragile compared to device-specific custom ROMs, both on first boot (no-boot issues) and on subsequent boots (after tuning certain Treble settings), and I insist that no-auth ADB is a must-have for debugging and general fail-safe.
Signature spoofing (MicroG) is supported, but only for priv-apps. This is a security consideration from PHH.
Magisk support should be on par with A11 (thanks @eremitein). The "abnormal state / unsupported SU" warning can be ignored. For devices that still don't play well with Magisk (e.g. kernel restrictions implemented by OEM), use PHH-SU instead. Install the app and you'll get root for apps.
Initial builds are based on PHH v400.c and November security patches.
Sigh, I don't really want to make a thread this early...
BTW, 32-bit and A-only users, you should really move on.
Big work thank You
Hey How to flash this Gsi Guys can someone answer me????
Thank you so much. Are gapps included ?
walid77dz said:
Thank you so much. Are gapps included ?
Click to expand...
Click to collapse
From an earlier post...
AndyYan said:
32*/A32* users, I'm not stopping your monthly builds just yet, but 32-bit is getting phased out, and you should upgrade soon. Similar goes for A-only. Ideally in the future we'll only have 64B, making room for other much needed variants such as GAPPS.
Click to expand...
Click to collapse
Their deprecation does seem likely now, so I'll try a GAPPS build or two when I have time.
Do you consider this alpha usable as daily driver?
And, does it require clean installation from LOS 18 GSI?
Avraham Tsaban said:
Do you consider this alpha usable as daily driver?
And, does it require clean installation from LOS 18 GSI?
Click to expand...
Click to collapse
I am using it as my daily driver - I enabled Gallery and LiveDisplay for just that purpose.
Out of curiosity I did try a dirty install from 18.1. It booted and most apps work, to my surprise, but Messaging won't allow me to select contacts properly no matter what, and that was a blocker, so don't.
People who love LOS, insist on using GAPPS with it, and had been asking me for such builds all this time - I now have a lil something for you, a test LOS19 build with GAPPS built-in. It's intentionally in the "personal" flavor to discourage use as your daily driver, but also shared-blocks (unlike previous "personal" builds) to save some space.
It was more trivial to build than I thought, but that doesn't mean I'll build it alongside vanilla yet...
Every variant takes disk space and build time
The image itself is huge and won't fit in even slightly older devices
Too many archs/variants confuse users
I cannot make any guarantees about it
I've seldom mentioned the last point, yet it's critical - I'm in China and I don't use GAPPS at all, so I have little idea about what counts as "properly working" for GAPPS and how to troubleshoot them. Even if I do eventually build with GAPPS, I can only provide builds as-is, and you'll have to help each other out on GAPPS-related/-induced issues. At the end of the day, I still recommend using other ROMs that are built around GAPPS, e.g. @ponces ' PE, for a more cohesive experience and better support.
For now, all I know is this test build logs in (after registering the device here), can open Play Store and download apps, nothing beyond that.
Huawei P20L mobile data doesn't work
confirmed working on huawei mediapad m5 (cmr-w09 model name)
thx so much AndyYan
first degoogled android 12
su working via phh su app - magisk wasn't working proper
I do the installation through fastboot, because I don't have twrp, The installation is successful, but when I start to start the installation it gives an error: Invalid sparse file format at header magic, and after that it installs normally, but when I start the system, it gets stuck in the logo of the manufacturer of my device, Any solution?
Flashed this ROM on my Oneplus 9 Pro and was surprised how great and smooth it is.
I read on a thread how to fix fingerprint issue on GSI ROM by editing /vendor/build.prop, tried it and ended up in bootloop and I have to start all over.
What's the right way to do this?
Thanks in advance.
Geoz said:
fix fingerprint issue on GSI ROM
Click to expand...
Click to collapse
You don't - no A12 GSIs support UDFPS yet.
AndyYan said:
You don't - no A12 GSIs support UDFPS yet.
Click to expand...
Click to collapse
Good to know. I appreciate you taking the time to explain this.
Thanks.
Geoz said:
Good to know. I appreciate you taking the time to explain this.
Thanks.
Click to expand...
Click to collapse
BTW, I believe most OPlus devices have read-only vendor, so even in the future you probably shouldn't head down that road.
AndyYan said:
BTW, I believe most OPlus devices have read-only vendor, so even in the future you probably shouldn't head down that road.
Click to expand...
Click to collapse
What of if I use Lineage OS as the base?
Thanks again.
Geoz said:
What of if I use Lineage OS as the base?
Thanks again.
Click to expand...
Click to collapse
That depends on your maintainer (LuK), and also PHH only deals with issues with stock vendors.
Speaking of which, looks like someone else also can't wait for LuK's 19.0, hehe...
AndyYan said:
That depends on your maintainer (LuK), and also PHH only deals with issues with stock vendors.
Speaking of which, looks like someone else also can't wait for LuK's 19.0, hehe...
Click to expand...
Click to collapse
First time on GSI ROM but I'm really impressed. I've learned a lot from you in a very short time. All information I read on the internet is not valid rather from a developer like you.
I appreciate you.
{
"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 12 (S), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
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. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.
GPL compliance:
Device tree source code: https://github.com/Inkypen79/device_xiaomi_odin
Kernel source code: https://github.com/Inkypen79/kernel_xiaomi_odin
Working:
Almost everything
Broken:
You tell me
Downloads:
https://sourceforge.net/projects/xiaomi-odin/files/13/LineageOS
https://sourceforge.net/projects/xiaomi-odin/files/12/LineageOS
https://sourceforge.net/projects/xiaomi-odin/files/11/LineageOS
Installation:
Reboot to recovery
Copy LineageOS zip to internal storage
Install LineageOS zip package
Install [optional] a Google Apps package of your choice
Format data (wiping is not sufficient, formatting requires you to type "yes")
Reboot
Important notes:
GApps can only be flashed on clean installs.
Formatting data (all user data is wiped, including internal storage) is a must if MIUI was previously installed and device was encrypted.
Contributors
Inkypen
ROM OS Version: Android 12
ROM Kernel: Linux 5.4
Based On: AOSP
Official TWRP thread:
https://forum.xda-developers.com/t/recovery-11-official-teamwin-recovery-project.4374117
TWRP Notes:
Currently the official TWRP has issues installing on custom ROMs. It can be permanently installed on with MIUI but any AOSP based ROM causes it to hang. Until this gets fixed the only way into TWRP is to use the fastboot boot method. Also the official TWRP currently has some bugs (sideload not working, boot slot selection not working, vibration not working) which I have fixed. I've submitted these fixes to the official channels so the next official build should have these problems fixed. My unofficial TWRP build is available here:
https://sourceforge.net/projects/xiaomi-odin/files/twrp-3.6.1-odin.img/download
Extra Installation Notes:
TWRP cannot currently decrypt A12 partitions meaning you can't access your files in recovery mode. This is a TWRP problem, not a ROM bug. If you need to install something, either sideload it or use USB OTG.
Lineage 19 requires MIUI 13/Android 12 firmware. You can get that here: https://xiaomifirmwareupdater.com/firmware/odin/stable/V13.0.4.0.SKMCNXM/
Lineage 18 requires MIUI 12/Android 11 firmware, available here: https://xiaomifirmwareupdater.com/firmware/odin/stable/V12.5.12.0.RKMCNXM/
This is freaking awesome !
I know this may be a very dumb question, what's Screen off FOD ?
The fingerprint scanner while the screen is Off, with screen on it works
I've heard that the selfie cam of MIX 4 doesn't work with LineageOS on telegram.Did this bug fixed??
santimaster2000 said:
This is freaking awesome !
I know this may be a very dumb question, what's Screen off FOD ?
Click to expand...
Click to collapse
It means you can't use fingerprint when you closed your display of the phone
calledJona said:
The fingerprint scanner while the screen is Off, with screen on it works
Click to expand...
Click to collapse
Oh OK, now I get it.
@Inkypen I have managed to install this with OpenGapps pico and everything seems to look good - except for SIM cards None of the SIM slots are recognized... so uninstalling it now, since I need my phone BUT other than that I am super pumped - finally something other than MIUI and my beloved Lineage! Throwing you thank yous via PayPal in a moment Keep up the good work!
er453r said:
@Inkypen I have managed to install this with OpenGapps pico and everything seems to look good - except for SIM cards None of the SIM slots are recognized... so uninstalling it now, since I need my phone BUT other than that I am super pumped - finally something other than MIUI and my beloved Lineage! Throwing you thank yous via PayPal in a moment Keep up the good work!
Click to expand...
Click to collapse
Flash it again. I've discovered that if you flash to slot A you won't have SIM cards or sensors working but everything works properly when flashed to slot B. I have a feeling it's related to TWRP, for example it's currently a bit broken and can't be permanently installed on AOSP based ROMs.
@Inkypen just tried both B and A (in that order) and still no SIM detected. I am using your TWRP from that thread :/
Also, how to change SELinux status? Lineage Trust app complains about it.
Great work. Thank you.
Cts profile failed, selinux off. And safety tests not passing.
Any idea how fix it?
@shulfei and does the SIM card work for you?
er453r said:
@shulfei and does the SIM card work for you?
Click to expand...
Click to collapse
Yes. Everything work fine.
er453r said:
@Inkypen just tried both B and A (in that order) and still no SIM detected. I am using your TWRP from that thread :/
Also, how to change SELinux status? Lineage Trust app complains about it.
Click to expand...
Click to collapse
Not sure what is wrong here, or if it's even the same issue I have when flashing to slot A. I'll need logs to investigate. Also you can turn off the SELinux warning in Trust settings.
shulfei said:
Great work. Thank you.
Cts profile failed, selinux off. And safety tests not passing.
Any idea how fix it?
Click to expand...
Click to collapse
CTS profile and Safetynet failures are both related to SELinux. There is a hack to hide SELinux status from Google services but I forgot to add it in (although I did add in the hack for the unlocked bootloader check). It's possible to add the SELinux hack onto a running phone but it's complicated. Good news is I'm wokring on SE policy in order to get it fully enforcing.
Don't try to force enable SELinux to enforcing, your phone will quite likely stop working properly until you set it back to permissive.
Inkypen said:
Good news is I'm wokring on SE policy in order to get it fully enforcing.
Click to expand...
Click to collapse
Will be waiting your updates.
Thak you very much.
shulfei said:
Will be waiting your updates.
Thak you very much.
Click to expand...
Click to collapse
I might be the one user, who is mostly excited with the prospect of leaving MIUI behind.
Buti have to ask,what kind of procedure, did you use to flash the LOS-Build? I tried it like the way described but, it did not go well. Btw, i come from MIUI 13.
SanHelios said:
I might be the one user, who is mostly excited with the prospect of leaving MIUI behind.
Buti have to ask,what kind of procedure, did you use to flash the LOS-Build? I tried it like the way described but, it did not go well. Btw, i come from MIUI 13.
Click to expand...
Click to collapse
Reboot phone to fastboot mode.
Boot to twrp (get Inkypen version twrp-odin.img) via command
"""
fastboot boot twrp-odin.img
"""
Wipe all data how wrote Inkypen:
"""
Formatting data (all user data is wiped, including internal storage) is a must if MIUI was previously installed and device was encrypted.
Format data (wiping is not sufficient, formatting requires you to type "yes")
"""
Install LineageOS.
Install gapps arm64.
I mean between formatting data and install LOS, do you restart recovery?
SanHelios said:
I mean between formatting data and install LOS, do you restart recovery?
Click to expand...
Click to collapse
No need to restart Recovery. But I suggest you to Install the Los/Gapps first, and than format data, otherwise the Rom won't boot. Also, make sure u flash the Rom on Slot B, although I had problem with flashing it on MiUi Beta. You can try it, anyway. Cheers.
New build succesfully installed .
Thanks for the update and especially gapps build this time.
LineageOS 20.0 for Sony Xperia XZ1
{
"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"
}
RELEASE
This is an alternative ROM for the Sony Xperia XZ1, offering several privacy features.
Please report any issues you observe apart from the ones listed below. Logs are needed for me to fix anything (preferably dmesg and logcat).
DOWNLOAD
You can download the latest releases here:
poplar (G8341):
https://sourceforge.net/projects/yoshino/files/poplar/twrp/
https://sourceforge.net/projects/yoshino/files/poplar/lineage-20.0/
poplar_dsds (G8342):
https://sourceforge.net/projects/yoshino/files/poplar/twrp/
https://sourceforge.net/projects/yoshino/files/poplar/lineage-20.0/
poplar_canada (G8343):
https://sourceforge.net/projects/yoshino/files/poplar/twrp/
https://sourceforge.net/projects/yoshino/files/poplar/lineage-20.0/
poplar KDDI (SOV36)
https://sourceforge.net/projects/yoshino/files/poplar/twrp/
https://sourceforge.net/projects/yoshino/files/poplar/lineage-20.0/
RECOMMENDED GAPPS (others works too)
https://androidfilehost.com/?w=files&flid=322935
INSTALLATION
Before first install: flash and boot into the TWRP provided in this thread, format data, reboot to recovery and wipe all internal partitions, then flash the ROM, GApps and root (if needed).
Note: There is not going to be a LOS su addon anymore. If you need root, flash a root manager of your choice. No guaranteed support from LOS for this.
When updating from previous builds, simply dirty flash the ROM is enough, decryption in new TWRP works now
Recommended GApps: MindTheGapps provided in this thread.
KNOWN ISSUES
Stock camera is not working anymore due to incompatibility of stock library (libimageprocessorjni.so) with new libgui
Currently, LOS isn't feature complete yet, so some things, buttonn, advanced menù etc. may be still missing
You tell me...
Contributors
derf elot, modpunk, Rooted_Ansh
Source Code
poplar: https://github.com/whatawurst/android_device_sony_poplar
poplar_dsds: https://github.com/whatawurst/android_device_sony_poplar_dsds
poplar_canada: https://github.com/whatawurst/android_device_sony_poplar_canada
poplar_KDDI: https://github.com/whatawurst/android_device_sony_poplar_kddi
kernel: https://github.com/whatawurst/android_kernel_sony_msm8998
Rom Information
ROM OS Version: Android 13
ROM Kernel: Linux 4.4
Version Information
Status: Stable
Current Stable Version: 1.2
Stable Release Date: 2023-05-06
ALL CREDITS TO DERF ELOT AND THE OTHER DEVS BEHIND THE ROM, I'M ONLY POSTING IT.
---------------------------------------
Changelogs:
v1.2 (2023-05-10):
- Updated to T QPR2 release (LineageOS upstream)
- Updated to May 2023 Security updates (both ROM and kernel)
- Our kernel now includes updates by CIP and is up-to-date with tag st40 - thanks also to Flamefire for help with some of these (1)
- Reduced zram size to 25% (1gb) of out total RAM to have more to use freely
- Updated BT stuff for QPR2 (maybe offloading is working again? needs confirmation)
- Added the option to reflash the mbn via OpenCS (see Xperia Parts) - thanks also to shank03 & Flamefire (2)
- Fully enabled IMS on Congstar Germany via overlay on lilac
- Possibly some battery/performance optimizations here and there
- Fixed Android Auto support
- Added new LineageOS "Charging control hal" for battery charging care (3)
- Maybe more I forgot...
(1) The CIP kernel includes fixes for issues and security vulnerabilities from 4.14 kernel (see https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git)
(2) A somehwat lengthy explanation: This option is off by default on fresh installs. When upgrading, this should be enabled because we enforced this for everybody previously. However, this option is only required for certain carrier mbns that enable IMS. Personally, I know that the O2/Telefonica Germany mbn needs this, otherwise you get a crashing modem at every boot (unless you switch to 3g before rebooting and back to LTE after boot). I generally recommend playing with this option, and if you don't need it (e.g. modem doesn't crash on boot), just keep it off - like mentioned before, this is now the default behavior of OpenCS on fresh installs anyway.
(3) This is not finalized or merged upstream is LineageOS yet, but seems like a nice feature to have and test drive already. Some bugs may be possible.
v1.1 (2023-01-08):
Updated to T QPR1 release (LineageOS upstream)
New default camera app (LineageOS upstream) - yes, we cannot change video fps currently (thanks Sony!)
Any other updates by LineageOS upstream
Kernel security updates (also thanks to Flamefire)
Dropped keyprovd service - it is useless on unlocked BL anyway
Show 4G instead of LTE icon - saves some space too
Enable IMS by default - this still only works if carrier is supported
Fix some selinux denials (also thanks to Flamefire)
Fixup ViLTE dependencies - this might in theory work again, but it's not enabled yet
v1.0 (2022-10-02):
Initial release
Can’t wait to try it !!! Thanks tux
Can i flash this using old twrp version like 3.6.2 - 9?
The rom is great but every time the device reboots and finishes the boot animation it repeats one more time boot animation.
According to the picture, I can't scroll down as usual, can only use those 4 buttons @@ until rebooting (I had landscape rotation to watch youtube then rotate the screen again when the video ends and it's like that
).
rarely but the sound doesn't play even if i keep the volume high or switch to listening to music or watching youtube until the device is restarted
(sorry if I said wrong or wrong grammar, I'm not very good at English. )
raffyei8ht said:
Can i flash this using old twrp version like 3.6.2 - 9?
Click to expand...
Click to collapse
No idea, but for internal memory decription the new one is needed.
Tux111 said:
No idea, but for internal memory decription the new one is needed.
Click to expand...
Click to collapse
What is the use of internal decription if you don't mind me asking
raffyei8ht said:
What is the use of internal decription if you don't mind me asking
Click to expand...
Click to collapse
By default android protect (encrypt) your internal memory. TWRP lacked decryption for a long time, now its supported. This means, with new recovery, you can see and manage your internal memory via TWRP using your lockscreen password. Before, you simply can't.
The fingerprint sensor doesn't work, auto brightness is also not working, does anyone know how to fix it
Each time I reinstalled a rom, some function which worked just fine on that rom stopped functioning, do you guys know how to prevent this
This is a very good ROM. Good for daily use. Didn't encounter any problem. Can't wait for the Pixel Experience Android 13.
ecrissor said:
The fingerprint sensor doesn't work, auto brightness is also not working, does anyone know how to fix it
Click to expand...
Click to collapse
FP perfectly working.
ecrissor said:
Each time I reinstalled a rom, some function which worked just fine on that rom stopped functioning, do you guys know how to prevent this
Click to expand...
Click to collapse
I guess you have some missing files or something like that. Try reflashing stock rom and persist.img, something wrong with your files.
Maybe this is a dumb question, but what is the difference between the twrp provided here and the 'stock' twrp from twrp.me? Will both work?
Nice room
great work
poplar_dsds said:
Maybe this is a dumb question, but what is the difference between the twrp provided here and the 'stock' twrp from twrp.me? Will both work?
Click to expand...
Click to collapse
Both works but this one should be able to decrypt internal memory. No idea if the one from twrp.me does the same or if its the same file.
Tux111 said:
Both works but this one should be able to decrypt internal memory. No idea if the one from twrp.me does the same or if its the same file.
Click to expand...
Click to collapse
Okay i see, thank you! I updated to your version of twrp and dirty flashed the rom from 19.x to this version, worked great, even with apps and so on!
Also thanks for the ROM!
Hi there,
I'm a complete noob on XDA, but I just flashed this TWRP (twrp-3.6.2_12-0-20221002-poplar) over another TWRP (twrp-3.7.0_9-0-poplar) and now, when entering recovery mode I get stuck in loading screen of teamwin Recovery Project 3.6..2_12-0
I can get out of loading screen by pressing all buttons, and device turns off.
I rebooted into fastboot and flashed back the 3..7 TWRP and now things are back to normal.
Any sugestions on what I can do to install this TWRP?
xdatomsgmail said:
Hi there,
I'm a complete noob on XDA, but I just flashed this TWRP (twrp-3.6.2_12-0-20221002-poplar) over another TWRP (twrp-3.7.0_9-0-poplar) and now, when entering recovery mode I get stuck in loading screen of teamwin Recovery Project 3.6..2_12-0
I can get out of loading screen by pressing all buttons, and device turns off.
I rebooted into fastboot and flashed back the 3..7 TWRP and now things are back to normal.
Any sugestions on what I can do to install this TWRP?
Click to expand...
Click to collapse
So, I was able to install lineage-20.0-20221002-UNOFFICIAL-1.0-poplar.zip from this post using TWRP 3.6..2_12-0, without problems.
Did not try to flash twrp-3.7.0_9-0-poplar again.
Is there a thread with future requests? I would like the default browser not to default to google, as the whole point for me is to de-google my phone.
Hi, so I've been absent from Custom Roms for the last couple years - since I got my XZ1 and the DRM key extraction was too much of a hassle for me as I didn't miss much from the stock rom.
Since I got some spare time over the years I was thinking to finally tackle that topic, but I have two questions:
1) The opening post says this
Tux111 said:
Stock camera is not working anymore due to incompatibility of stock library (libimageprocessorjni.so) with new libgui
Click to expand...
Click to collapse
is it even still relevant for me to back up my DRM keys / back up the TA partition if I don't want to go back to stock? what camera are you using then? is the quality comparable? is slow motion still possible?
2)
i know that in the past, safety net checks were just looking for bootloader / root, but they changed to checking if the ROM is signed with a proper signingkey, right? is this rom signed with a non-test-key?
I've got a couple of banking apps on my phone and it would obviously prevent it from being a daily driver if they were not supported anymore :/
Thanks in advance!
New LOS Update 1.1 is here! Enjoy!
xdatomsgmail said:
So, I was able to install lineage-20.0-20221002-UNOFFICIAL-1.0-poplar.zip from this post using TWRP 3.6..2_12-0, without problems.
Did not try to flash twrp-3.7.0_9-0-poplar again.
Is there a thread with future requests? I would like the default browser not to default to google, as the whole point for me is to de-google my phone.
Click to expand...
Click to collapse
By default the browser isn't Google Chrome afaik, so i don't see the problem. Also, tbh, this makes no sense considering Android=Google. Chromium is builded inside the ROM,is part of the ROM,so once you install Android, you are installing something from Google. So i don't get it.
If you don't install gapps, then you don't have Chrome as default browser. Otherwise, flash gapps and remove Chrome.