Related
As you all know GSI image alone not sufficient to get fully functional robust stable OS running on Lenovo p2. There are many flashable zip files which need to be flashed individually to get most of the features working. Which makes GSI image meaning less.
So post/discuss all the available GSI and device specific features for Lenovo P2 here.
It will be helpful for Devs and users.
** Requesting Devs to work on device specific feature support over GSI image. **
So far our Dev helped us getting up to this level. We need little more effort to make the GSI image successful on our device.
Expecting Users active support for Devs.
Edited: request only to make device specific features which lacks in GSI image.
Refer post #3.
What do you mean by device specific GSI? What's the point of doing this while GSI (Generic) means (for us) that you can actually flash it over multiple Treble devices out there?
If you recompile system image with device specific patches it will be basically device specific standard ROM (but with Treble which is basically not needed now) and not GSI anymore.
I don't get why are you people actually need "Treble" compatible ROM while existing standard ROMs are working great for now. Because they're Treble ROMs? What does it change? GSIs created using phhusson scripts are one big hack at the moment and their state is experimental. Of course they will work but they're lacking of device specific build.prop's.
Oreo one's are actually fully compatible with Lenovo P2 and stable because I tested them myself. Probably all of them (but all I tested) share the same device specific bugs. Even FP gestures works but this function needs to be activated by "setprop persist.sys.fp.navigation 1" after boot. The fix zip provided in P2 Mods subforum is actually copying script to system which will actually do that after every boot, nothing more. Google told on their AMA that they will make official documentation of making GSIs in the near future so I believe that will fix our current problems and device specific build.props could be generated and added to ROMs without touching system partition integrity state and recompiling them.
Until Android Pie ROMs will be stable as GSIs you will also not benefit too much from creating device specific system image because you will need to wait for Mike or someone else to create compatible vendor image and kernel (Probably Mike will be the first so you will need to wait for official release of LOS16).
Recompiling ROMs just for adding few fixes is a waste of resources. You need approx ~250GB of memory to compile and maitain one ROM, time (depending on memory you are using) and a lot of electricity.
In my personal opinion, creating Magisk module for P2 devices which will fix build.prop systemless-ly and add that command for activating FP gestures will be better alternative for now. I could personally look into it when I get some time.
If you still think that you need these device specific system images for every ROM at all costs, you could build them and maitain yourself or ask someone who will do this. Maybe Fullbustah will be eager to do some requests because he already built some popular ROMs on Mike's sources lately. You could also extract system.img's from his last builded ROM's and they will be device specific system images you are looking for . The only problem is that I don't think he is willing to maitain all of them at once.
I'm sorry if my previous post conveyed wrongly.
All we need is GSI images should be flashed directly. I didn't conveyed anywhere to build a sperate image from GSI.
May be I asked to maintain device specific vendor/system tweaks in a one place which will be flashed on top of any GSI image to get all the features working in our device.
Hope this helps!
MAILUS said:
I'm sorry if my previous post conveyed wrongly.
All we need is GSI images should be flashed directly. I didn't conveyed anywhere to build a sperate image from GSI.
May be I asked to maintain device specific vendor/system tweaks in a one place which will be flashed on top of any GSI image to get all the features working in our device.
Hope this helps!
Click to expand...
Click to collapse
Ah, okay. It changes a lot. I tested few Oreo GSIs about a month ago an everything was working fine and stable for me. The only tweak needed was FP gesture fix but it was messing with the system partition and I was too lazy to make to improve it so I just gave up using it. And another missing thing was build.prop because device is named "Phh's Treble ARM64" or something like that after installing GSI. Also build fingerprint is always messed up so I had problems passing SafetyNet even with Magisk.
Only these fixes are required for making Oreo GSI's working perfectly or almost perfectly (like official LOS) so I'm going to do Magisk module that will cumulate all of these fixes into one, easy to install solution. If I missed something just let me know.
Hello A7600-F Tablet owners, It's been awhile since there has been an updated ROM for this tablet. I have released ported ROMs for this tablet before, however they all had some annoying bugs and many of you reported issues with corrupted SD card partitions. The goal of this ROM is to provide as close to daily driver material for this old tablet as possible.
What better ROM than Resurrection Remix to do the job! :good:
Instructions:
Follow carefully! This process involves going back to STOCK firmware FIRST! This is to ensure your Internal storage gets properly formatted.
SAVE YOUR PERSONAL DATA! (Some where other than your tablet) You will lose it when flashing stock firmware. Don't worry about the struggles of getting ROOT on stock firmware, I have expedited the process greatly.
STEP 1: Get back to stock firmware. THIS STEP ERASES EVERYTHING, so save your data!!! Don't skip this step.
- Get any stock firmware file from here and follow the tutorial also in this link!
- The SP-Flash tool and drivers are all conveniently included with the firmware download.- Don't worry about taking the battery out when the tutorial says to.- If you have issues with the driver provided in the download, try these. (Run dpinst.exe) - Once completed boot into the new firmware just to ensure that you were successful. (Don't worry about going through initial setup we don't need it)
STEP 2: Install TWRP without root. You should now have a stock A7600-F Tablet, lets put TWRP back on.
- We will install TWRP with the same SP-Flash tool so that root is not required.
- Download the SP-Flashable TWRP image and scatter file from here.
- Follow the instructions in the tutorial linked in step 1 again but use the extracted TWRP scatter file you just downloaded instead of the stock firmware scatter file.
- You should only see "RECOVERY" listed in SP Flash Tool instead of all the stock partitions like last time - Once complete unplug the USB and use Vol-UP and Power buttons to get into TWRP
STEP 3: Wiping Instructions. THIS IS IMPORTANT! You should have TWRP installed and running at this point.
- DO NOT WIPE INTERNAL STORAGE! Doing so will cause the Corrupt SD-Card errors!
- Just don't do it! There is never any need to wipe internal storage on most devices.
- Go to Wipe -> Advanced Wipe
- Select only: Dalvik/Art Cache, System, Cache, and Data
- Wipe it.
STEP 4: Installing RR 7.1.2. You should now have an A7600-F with the stock partitions restored, and no ROM installed, sitting in the TWRP main menu.
- ROM Download: here
- GAPPS Download: here (Select Arm, 7.1, and whatever size you want)
- Now simply flash the ROM ZIP followed by the Gapps ZIP.
Reboot and Enjoy!
Things I improved over previous ROM PORTS:
- Better Audio quality
- Smoother Substratum OMS Support
- Camera Fixes
- FM Radio (Headphones only)
Kernel Source: here
Just yesterday I've dusted off this tablet, and so I was browsing the forums to see what rom I can put inside, and lickily, about the same time this thread was created! Installing it right now, gonna post a follow-up once I'm finished tinkering with it.
OK, firstly wanna thank you for this awesome rom, it's stable and fast, no major issue with it. What I did find, however, is that the camera flash is not working along with the night mode which is not turning on. Besides those two issues, everything seems to be in working order
Cheers!
LukaHM said:
OK, firstly wanna thank you for this awesome rom, it's stable and fast, no major issue with it. What I did find, however, is that the camera flash is not working along with the night mode which is not turning on. Besides those two issues, everything seems to be in working order
Cheers!
Click to expand...
Click to collapse
Thanks for the report.
Camera flash? My A7600 Does not have a flash. No actual LED to produce a flash.
As for the Night mode, I have ported a lot of ROMS to this device and I havn't ever seen the night mode work right. If I even do get it to turn on, it lags the whole device.
SaberShip said:
Thanks for the report.
Camera flash? My A7600 Does not have a flash. No actual LED to produce a flash.
As for the Night mode, I have ported a lot of ROMS to this device and I havn't ever seen the night mode work right. If I even do get it to turn on, it lags the whole device.
Click to expand...
Click to collapse
Haha, I've turned the damn thing over, looked at the sensor, and you're right. Havent actually used this device previously to know about it, so glad we have that one sorted out!
Thanks SaberShip. The ROM works great for general use and apps but I'm having an issue downloading files. It says SD card not found Download to default folder. I attempt to download to Downloads folder where it says I have 10.43gb stroage available but it keeps telling me SD card not found. I don't use an SD card for storage on the device. Do I need to use one or can you offer any other advice? I've carefully gone through above installation steps 3 times.
---------- Post added 08-02-2019 at 12:38 AM ---------- Previous post was 07-02-2019 at 11:57 PM ----------
caoiveen said:
Thanks SaberShip. The ROM works great for general use and apps but I'm having an issue downloading files. It says SD card not found Download to default folder. I attempt to download to Downloads folder where it says I have 10.43gb stroage available but it keeps telling me SD card not found. I don't use an SD card for storage on the device. Do I need to use one or can you offer any other advice? I've carefully gone through above installation steps 3 times.
Click to expand...
Click to collapse
So I put in an sd card and I then had option to save to downloads or sd. I still could not select downloads but I could select sd card which is worrying for me now. Thanks again Sabership. Nice work
caoiveen said:
Thanks SaberShip. The ROM works great for general use and apps but I'm having an issue downloading files. It says SD card not found Download to default folder. I attempt to download to Downloads folder where it says I have 10.43gb stroage available but it keeps telling me SD card not found. I don't use an SD card for storage on the device. Do I need to use one or can you offer any other advice? I've carefully gone through above installation steps 3 times.
---------- Post added 08-02-2019 at 12:38 AM ---------- Previous post was 07-02-2019 at 11:57 PM ----------
So I put in an sd card and I then had option to save to downloads or sd. I still could not select downloads but I could select sd card which is worrying for me now. Thanks again Sabership. Nice work
Click to expand...
Click to collapse
What app are you using? I have not seen any issues with downloading yet. If you see 10.43Gb it sounds like your internal storage is formatted correctly. I haven't seen any download issues with Firefox and ES-File Explorer.
Unable to flash firmware - because unable to install Android USB driver on Windows 10
Thank you for the new firmware. However, the instructions to install the Android USB driver in smartphone flash tool (link below) the link below does not work.. There is a signature error and everyone (as per youtube video comments) is having same problem.
https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
Pls advise.
D2sx34 said:
Thank you for the new firmware. However, the instructions to install the Android USB driver in smartphone flash tool (link below) the link below does not work.. There is a signature error and everyone (as per youtube video comments) is having same problem.
https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
Pls advise.
Click to expand...
Click to collapse
Main post updated with signed drivers. Please try it now.
Thank you @SaberShip!
The installation of Resurrection Remix 5.8.5 was successful after installing the signed Android USB driver!. System is stable and fast. Thank you again.
App issues:
1. Netflix app (not available on playstore, but at netflix web site) works online, but does not allow video downloads.
Netflix diagnostic error for download is OF.NA.4 -which probably means device does not meet security requirements. ? any workarounds?
// Amazon Prime video works, with offline video downloads as well. Google chrome works. Tried other apps as well.
Documentation issues (minor):
1. "- GAPPS Download: here (Select Arm, 7.1, and whatever size you want)" --> Google Apps Super package did not install since the device ran out of space (error 70). Google Apps "Nano" worked.
System issues:
1. Wifi still does not auto-reconnect after Wireless Access Point is rebooted, but given that this has happened with different ROMs I am concluding it is due to a hardware issue with this device (and not ROM specific).
// Skype camera issue fixed. Camera image is NO longer upside down.
D2sx34 said:
Thank you for the new firmware. However, the instructions to install the Android USB driver in smartphone flash tool (link below) the link below does not work.. There is a signature error and everyone (as per youtube video comments) is having same problem.
https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
Pls advise.
Click to expand...
Click to collapse
Netflix app not working on ROM due to Widevine DRM
Great job on the ROM!! - it is fast and stable.
I have been investigating why the <latest> Netflix app with offline download capability does not work with Resurrection Remix 5.85 ROM.
I found that some other ROM has similar problem, and it was caused because Widevine DRM was not supported. Netfix (latest app and offline download) started working after Widevine DRM support was added to that ROM.
Is it possible to support Widevine DRM in this ROM?
Here is the quote from another ROM:
"Quote:
Originally Posted by Federek
I recently found out the reason why after opening the Netflix app it shows the error "this app is not compatible with your device". The only workaround right now is to download an old APK directly from Netflix website (it doesn't support the feature of downloading movies). After some digging, I'm pretty sure the error is due to the fact that on, I think any Oreo rom available for bacon, Widevine Drm is not supported (as u can see in the screenshot below). I think it's connected to the files in the screenshot below, but I didn't manage to find a solution. I believe it must be implemented by someone directly in the rom code (I'm absolutely not an expert). I'm also sure it's not connected with root or anything else (the Netflix app is available in the play store for me).
(sorry is my first post)
[/IMG]"
SaberShip said:
Hello A7600-F Tablet owners, It's been awhile since there has been an updated ROM for this tablet. I have released ported ROMs for this tablet before, however they all had some annoying bugs and many of you reported issues with corrupted SD card partitions. The goal of this ROM is to provide as close to daily driver material for this old tablet as possible.
What better ROM than Resurrection Remix to do the job! :good:
Instructions:
Follow carefully! This process involves going back to STOCK firmware FIRST! This is to ensure your Internal storage gets properly formatted.
SAVE YOUR PERSONAL DATA! (Some where other than your tablet) You will lose it when flashing stock firmware. Don't worry about the struggles of getting ROOT on stock firmware, I have expedited the process greatly.
STEP 1: Get back to stock firmware. THIS STEP ERASES EVERYTHING, so save your data!!! Don't skip this step.
- Get any stock firmware file from here and follow the tutorial also in this link!
- The SP-Flash tool and drivers are all conveniently included with the firmware download.
- Don't worry about taking the battery out when the tutorial says to.
- If you have issues with the driver provided in the download, try these. (Run dpinst.exe) - Once completed boot into the new firmware just to ensure that you were successful. (Don't worry about going through initial setup we don't need it)
STEP 2: Install TWRP without root. You should now have a stock A7600-F Tablet, lets put TWRP back on.
- We will install TWRP with the same SP-Flash tool so that root is not required.
- Download the SP-Flashable TWRP image and scatter file from here.
- Follow the instructions in the tutorial linked in step 1 again but use the extracted TWRP scatter file you just downloaded instead of the stock firmware scatter file.
- You should only see "RECOVERY" listed in SP Flash Tool instead of all the stock partitions like last time - Once complete unplug the USB and use Vol-UP and Power buttons to get into TWRP
STEP 3: Wiping Instructions. THIS IS IMPORTANT! You should have TWRP installed and running at this point.
- DO NOT WIPE INTERNAL STORAGE! Doing so will cause the Corrupt SD-Card errors!
- Just don't do it! There is never any need to wipe internal storage on most devices.
- Go to Wipe -> Advanced Wipe
- Select only: Dalvik/Art Cache, System, Cache, and Data
- Wipe it.
STEP 4: Installing RR 7.1.2. You should now have an A7600-F with the stock partitions restored, and no ROM installed, sitting in the TWRP main menu.
- ROM Download: here
- GAPPS Download: here (Select Arm, 7.1, and whatever size you want)
- Now simply flash the ROM ZIP followed by the Gapps ZIP.
Reboot and Enjoy!
Things I improved over previous ROM PORTS:
- Better Audio quality
- Smoother Substratum OMS Support
- Camera Fixes
- FM Radio (Headphones only)
Click to expand...
Click to collapse
SaberShip, thank you for all your work and caring about the A7600-F! Your instructions are clean and elegant. It's great to be able to install your ROM without root. It looks and performs great.
I installed your ROM a week ago. Unfortunately, I've spent much time since then trying to get NordVPN to work. It worked fine on the stock version of my tablet. Now, it connects to NordVPN servers, but fails to adopt the remote IP address (whatismyv6.com reports my ISP IP).
I've exhausted [email protected] I'd be grateful for any pointers you might have.
Hello,
so i will thank Sabership, too, for his new build. I went the way as most builds are normally flashed - reboot from AIM build into TWRP, did a factory reset, and flashed RR and a new GApps build. Everything went fine, i am just typing on it. The bug with WiFi not connecting automatically i am hoping will be gone, it was the only bug i found in AIM for me.
One question: the security patch date is of November 2017. Will there be an update (as asked in AIM, too)?
Regards
jfaheyfan said:
SaberShip, thank you for all your work and caring about the A7600-F! Your instructions are clean and elegant. It's great to be able to install your ROM without root. It looks and performs great.
I installed your ROM a week ago. Unfortunately, I've spent much time since then trying to get NordVPN to work. It worked fine on the stock version of my tablet. Now, it connects to NordVPN servers, but fails to adopt the remote IP address (whatismyv6.com reports my ISP IP).
I've exhausted [email protected]. I'd be grateful for any pointers you might have.
Click to expand...
Click to collapse
I believe VPN connectivity may have been one of the issues with the original ROM even before I ported it to the A7600F. Therefore, there isn't much I can do unfortunately.
If you absolutely need VPN, your options are to use Stock ROM or find a different ROM that has VPN working. Another possible workaround is to setup NordVPN on your router or whatever gateway is between you and the internet: https://support.nordvpn.com/Connectivity/Router/1047409322/Setting-up-a-router-with-NordVPN.htm
Catfish78 said:
Hello,
so i will thank Sabership, too, for his new build. I went the way as most builds are normally flashed - reboot from AIM build into TWRP, did a factory reset, and flashed RR and a new GApps build. Everything went fine, i am just typing on it. The bug with WiFi not connecting automatically i am hoping will be gone, it was the only bug i found in AIM for me.
One question: the security patch date is of November 2017. Will there be an update (as asked in AIM, too)?
Regards
Click to expand...
Click to collapse
I have witnessed wifi disconnection issues on every ROM I've ever ported/used for this device aside from Stock I wish there was more that I could do. As mentioned in the title and before, this ROM is ported from another device. What this means is that I don't have the source code and therefore cannot update things like Android security patch dates. If this were a ROM built from source, I would simply have to sync with updated RR sources to get the new patches and RR bugfixes/features. To do it with a port, I need to find a whole new ROM with the updated sources and then port the whole ROM over to this device again. That is just too much work.
As a side note, I had intended this to be the last ROM I ported for this device due to its age, however If there is enough demand and I can find one, maybe someday I will port a more updated Oreo ROM to this device. Good quality MT6582 Oreo ROMs built from source are still not really common.
SaberShip said:
I believe VPN connectivity may have been one of the issues with the original ROM even before I ported it to the A7600F. Therefore, there isn't much I can do unfortunately.
If you absolutely need VPN, your options are to use Stock ROM or find a different ROM that has VPN working. Another possible workaround is to setup NordVPN on your router or whatever gateway is between you and the internet: https://support.nordvpn.com/Connectivity/Router/1047409322/Setting-up-a-router-with-NordVPN.htm
I have witnessed wifi disconnection issues on every ROM I've ever ported/used for this device aside from Stock I wish there was more that I could do. As mentioned in the title and before, this ROM is ported from another device. What this means is that I don't have the source code and therefore cannot update things like Android security patch dates. If this were a ROM built from source, I would simply have to sync with updated RR sources to get the new patches and RR bugfixes/features. To do it with a port, I need to find a whole new ROM with the updated sources and then port the whole ROM over to this device again. That is just too much work.
As a side note, I had intended this to be the last ROM I ported for this device due to its age, however If there is enough demand and I can find one, maybe someday I will port a more updated Oreo ROM to this device. Good quality MT6582 Oreo ROMs built from source are still not really common.
Click to expand...
Click to collapse
Thanks for your answer. If only i could do something like that of my own... i have so much interests, i don't know if i could learn that in a usefull time!
By the way, why did you call it "old"? i'm using the Galaxy S2 build 2011, with LineageOS 16. I think this is an old device , like my Galaxy Tab 1 and 2.
But anyway, thanks for your work. After some time i'll write again about issues i found, if it will be helpful.
Regards
Thank you, SaberShip. It's been on my list to get a DD-WRT enabled router, so maybe now's the time.
I've had no problems with WiFi.
If you build an updated Oreo ROM, I volunteer to test it. I'm fond of my A7600-F.
SaberShip said:
Hello A7600-F Tablet owners, It's been awhile since there has been an updated ROM for this tablet. I have released ported ROMs for this tablet before, however they all had some annoying bugs and many of you reported issues with corrupted SD card partitions. The goal of this ROM is to provide as close to daily driver material for this old tablet as possible.
What better ROM than Resurrection Remix to do the job! :good:
Instructions:
Follow carefully! This process involves going back to STOCK firmware FIRST! This is to ensure your Internal storage gets properly formatted.
SAVE YOUR PERSONAL DATA! (Some where other than your tablet) You will lose it when flashing stock firmware. Don't worry about the struggles of getting ROOT on stock firmware, I have expedited the process greatly.
STEP 1: Get back to stock firmware. THIS STEP ERASES EVERYTHING, so save your data!!! Don't skip this step.
- Get any stock firmware file from here and follow the tutorial also in this link!
- The SP-Flash tool and drivers are all conveniently included with the firmware download.
- Don't worry about taking the battery out when the tutorial says to.
- If you have issues with the driver provided in the download, try these. (Run dpinst.exe)
- Once completed boot into the new firmware just to ensure that you were successful. (Don't worry about going through initial setup we don't need it)
STEP 2: Install TWRP without root. You should now have a stock A7600-F Tablet, lets put TWRP back on.
- We will install TWRP with the same SP-Flash tool so that root is not required.
- Download the SP-Flashable TWRP image and scatter file from here.
- Follow the instructions in the tutorial linked in step 1 again but use the extracted TWRP scatter file you just downloaded instead of the stock firmware scatter file.
- You should only see "RECOVERY" listed in SP Flash Tool instead of all the stock partitions like last time
- Once complete unplug the USB and use Vol-UP and Power buttons to get into TWRP
STEP 3: Wiping Instructions. THIS IS IMPORTANT! You should have TWRP installed and running at this point.
- DO NOT WIPE INTERNAL STORAGE! Doing so will cause the Corrupt SD-Card errors!
- Just don't do it! There is never any need to wipe internal storage on most devices.
- Go to Wipe -> Advanced Wipe
- Select only: Dalvik/Art Cache, System, Cache, and Data
- Wipe it.
STEP 4: Installing RR 7.1.2. You should now have an A7600-F with the stock partitions restored, and no ROM installed, sitting in the TWRP main menu.
- ROM Download: here
- GAPPS Download: here (Select Arm, 7.1, and whatever size you want)
- Now simply flash the ROM ZIP followed by the Gapps ZIP.
Reboot and Enjoy!
Things I improved over previous ROM PORTS:
- Better Audio quality
- Smoother Substratum OMS Support
- Camera Fixes
- FM Radio (Headphones only)
Click to expand...
Click to collapse
Does usb otg work?
thierry_w said:
Does usb otg work?
Click to expand...
Click to collapse
Just tested, It works perfectly with my USB wireless Keyboard and mouse combo.
When I tried a USB flash drive it did not mount automatically, however "SDA" does appear in the /dev/block/ directory so you can likely mount the flash storage manually with some terminal commands. YMMV
USB OTG works with both my wired and wireless trackballs (Logitech).
I mount/unmount flash drives with StickMount and explore them with Total Commander.
excellent. Works very well
This project is for both LG Phoenix 4 users and all Aristo 2 users. Feel free to collaborate.
ABOUT:
This is a new idea that I had to make a universal Micro Stock OS. The OS's will be stripped down to the bare minimum to let both the Phoenix 4 and Aristo 2 users have a ROM with as much space and customization as possible. This is kind've like my AR-OS where I De-Odexed, De-Bloated, and Optimized the entire system. The only difference it will be build entirely upon the user.
HOW TO CONTRIBUTE:
Leave a post about what you were able to remove from the Pure Stock LG OS, without getting issues. (Make sure you backup your device before doing this though). When I see the input I will start updating this page to add more elements to it. When all is done and well, we will work on the customization part. Anyone who has suggestion on things such as "Stock Home Screen", you are welcome to post them in detail.
ADVANCED CONTRIBUTIONS:
For those of you who know how to modify the System OS a little better I will be needing help removing all of LG's Junk Licences and pulling just the Raw material from the OS or the building blocks for a GitHub page.
Thanks to everyone who will help!
I have the lg k8+ 2018 (lg aristo 2 us cellular model) I would like one without the root detection that slows down your phone and rooted with magisk . Also maybe a customizable ui
Working on 2 new rooted Oreo ROMs
I wanted to let everyone know that I am currently working on 2 new rooted Oreo ROMs.
Both are based on the latest available LG firmware for the given phone.
#1 is a new ROM for the Aristo 2 (Metro by T-Mobile), based on firmware 20g.
#2 is a new ROM for the K8 plus (US Cellular), based on firmware 20c.
These ROMs both feature:
Installation of the latest available TWRP, paired with LG's latest kernel to insure compatibility.
Pre-rooting of the boot image using the latest available Magisk.
Additional mods to the boot image to facillitate removal of LG's Root Checking Tool.
Pre-installation removal of existing encrypted partitions and associated encryption keys.
Removal of the possibility of encryption being forced on any user partitions via modification of multiple fstab files.
Removal of LG's performance degrading Root Checking Tool and it's defined service.
New modifications to the system image that are now required to successfully boot the altered system.
Removal of unneeded vendor software that can be removed without issues, freeing up additional storage.
Installation of useful root related utilities that add additional functionality to your phone.
Preservation of existing user installed apps.
Automatic alteration of system settings necessary for seamless functionality of the ROM when possible.
Mods to the vendor image that reliably prevent android system updates from being forced to the phone. This is very necessary, as all LG system updates are now very destructive, resulting in bricking of the phone.
I am looking for anyone willing to test these new images.
Just reply to this post and I will PM you.
Thanks.
I have a lg phoenix 4 (LM-X210APM) from AT&T, but it is not updated because I'm from Venezuela, is there a method to force the updates of that phone?
tecknight said:
I wanted to let everyone know that I am currently working on 2 new rooted Oreo ROMs.
Both are based on the latest available LG firmware for the given phone.
#1 is a new ROM for the Aristo 2 (Metro by T-Mobile), based on firmware 20g.
#2 is a new ROM for the K8 plus (US Cellular), based on firmware 20c.
These ROMs both feature:
Installation of the latest available TWRP, paired with LG's latest kernel to insure compatibility.
Additional mods to the boot image to facillitate removal of LG's Root Checking Tool.
Removal of the possibility of encryption being forced on any user partitions via modification of multiple fstab files.
New modifications to the system image that are now required to successfully boot the altered system.
Installation of useful root related utilities that add additional functionality to your phone.
Automatic alteration of system settings necessary for seamless functionality of the ROM when possible.
Mods to the vendor image that reliably prevent android system updates from being forced to the phone. This is very necessary, as all LG system updates are now very destructive, resulting in bricking of the phone.
I am looking for anyone willing to test these new images.
Just reply to this post and I will PM you.
Thanks.
Click to expand...
Click to collapse
I've a K8+ 2018 I'd be willing to test on.
Have Phoenix 4
I have an att Phoenix 4 I'd be willing to test this on. I just have to root first xD
I would also be willing to try out rom 1
I have the Aristo 2 Plus by mobile. If i cam helped.
I removed a bunch id have to take screen shot
In on rooted nougat can i have the link to the rooted oreo
Yeh I'll test the aristo 2 plus
I'm not a fan of Android 12's Material You, i.e. dull color schemes, ginormous headers and copious amounts of whitespace. Screens got bigger over time, but information density is getting lower and lower. It's crazy. Anyway, I'll spare you the rant.
As the LineageOS project stopped publishing builds for LineageOS 18.1, but they continue to patch their 18.1-branch with Android's monthly security updates, I decided to start building it myself following the instructions here.
You can download the builds here:
LineageOS 18.1 for Pixel 4a (sunfish) - Browse Files at SourceForge.net
Unofficial builds for those who wish to stay on 18.1 a bit longer.
sourceforge.net
I usually publish an update every month.
Additional tweaks
Default maximum lockscreen password length of 64 characters (instead of 16) [more info]
FirmwareIt's probably best to run the latest Android 11 firmware, since this is Android 11. You can download the last official Android 11 factory image from Google and flash it from fastboot mode (your data will be erased).
Clean install
Download the latest lineage-18.1-xxxxxxxx-UNOFFICIAL-sunfish-boot.img and lineage-18.1-xxxxxxxx-UNOFFICIAL-sunfish.zip from aforementioned link
Boot to bootloader a.k.a. fastboot
Flash the boot image with this command (replace filename with actual filename):
fastboot flash boot lineage-18.1-xxxxxxxx-UNOFFICIAL-sunfish-boot.img
Boot to recovery
Factory reset > Format data/factory reset > confirm (your data will be erased)
Apply update > Apply from ADB
Sideload the ROM with this command (replace filename with actual filename):
adb sideload lineage-18.1-xxxxxxxx-UNOFFICIAL-sunfish.zip
(If it asks "Signature verification failed. Install anyway?" answer Yes)
Optionally flash Gapps or anything else:
Advanced > Reboot to recovery
Run adb sideload with your zip
Reboot system now
UpdatingUpdates are delivered through the built-in updater (Settings > System > Updater).
If you use Magisk, deny the Updater's request to reboot at the end of the update process, open Magisk, tap Install and then "Install to Inactive Slot (After OTA)". Tap reboot after the process completes.
Migrating from last official LineageOS 18.1 buildSo it turns out builds are signed with a secret cryptographic key and when you install an update it has to have the same cryptographic signature or bad things will happen. This means you can't directly update from the last official build (signed by the LineageOS team) to my build (signed by me).
The solution: build and install (as an update a.k.a. dirty flash) a so called "migration build", which "resets the keys on all packages at every boot." I guess after booting into this build once, you can just update to the regular build using the updater (the LineageOS wiki is very concise on this topic and doesn't explain much).
You can download the migration build and boot image from the aforementioned link, they are marked MIGRATION instead of UNOFFICIAL. Don't run this build any longer than necessary, it's a security risk by its very nature.
When I tried this migration, my system wouldn't boot (stuck on boot logo). ADB worked and I could see in dmesg or logcat that, among other errors, SystemUI failed to start. Was it because I didn't reflash Gapps? But I never reflashed Gapps when using LineageOS' builtin updater...
Later I did some testing. I did a clean install of the latest official build, then my migration build, then my normal build, all was fine. Then I did a clean install of the latest official build WITH Gapps, then flashed the migration build WITHOUT Gapps, and the system booted up just fine. Huh? Then I flashed my normal build DIRECTLY over the latest official build, without migration build in between, and all was STILL FINE! So uhm... what's happening, how does this signing work and when does it become a problem? I have no clue.
If you decide to try the migration route, make sure to backup any data you don't want to lose and let us know how it went!
AcknowledgementsThanks to the original maintainers PeterCxy, cdesai and mikeioannina for bringing LineageOS 18.1 to the Pixel 4a!
Source code
LineageOS
A free and open-source operating system for various devices, based on the Android mobile platform. This is a mirror of https://review.lineageos.org/ - LineageOS
github.com
GcamYou can just install it from the Play Store. There are a few bugs:
In photo mode, slide up to record video doesn't work
Motion Photos doesn't work
It doesn't scan QR codes without Google Lens
App versions without Material YouIf, like me, you try to avoid Material You like the plague, here's a list of the last versions of Google apps that I use(d) that don't have Material You. Note that LineageOS includes its own versions of some of them and all of them are optional anyway. You can find them on e.g. APKMirror.
Calculator 7.8
Calendar 2021.35.3
Camera 8.2.400
Clock 6.4.1
Contacts 3.49.2
Gboard 10.8.05
Maps 10.80.1
Phone 68.0.3
Photos 5.58.0
Translate 6.24.0.02
Is it wise to run older software? You decide. In an ideal world security updates and bug fixes would be separate from UI and "we decided you don't need this functionality so we removed it" updates. I've long ago stopped regularly updating my apps (i.e. turned off automatic updates) because I like to be able to trust my device will look & work the same tomorrow as it did today.
P.S. After you've installed the regular 20220815 build, the updater will keep showing an August 16 update which is actually the build you're already running. This is because I had to move the timestamp one day forward in order to enable updating from the MIGRATION build, which was also build on 20220815 and wouldn't see the regular 20220815 build as an update otherwise. This will be remedied with the next update I publish.
The September update is now live.
Does banking app works?
My bank's app has always worked fine on LineageOS. Your bank's hasn't?
icantlogin said:
My bank's app has always worked fine on LineageOS. Your bank's hasn't?
Click to expand...
Click to collapse
I had never tried this rom want to try if bank apps works out of box
icantlogin said:
The September update is now live.
Click to expand...
Click to collapse
Been using this for several days now without a hiccup , fast ,,smooth, and google proofed, Thanks!!
Thanks for keeping LOS 18.1 alive with these security updates. I recently upgraded to 19.1 to try it out for a few months but I just couldn't get used to or appreciate the new UI. With every app update they also make it more like A12 and it just wasn't working for me.
Just installed your September update and all is well so far.
The October update is live!
A little background: I'm building this ROM on a Google Cloud Compute Engine instance, which is a virtual computer (also called virtual machine or VM) running in a Google data center. To keep the VM around is very costly, as it uses 300 GB of SSD storage which doesn't come cheap. So I create a new VM every month and dismantle it afterwards. This means I have to set up the build environment from scratch every time, which consists of a lot of steps. So from the beginning, I've put most of those steps in a Bash shell script (the VM runs Ubuntu 20.04) to speed things up drastically.
Last week I added some code that generates the updater.json file (that's read by your phone when it checks for updates) which I had been creating by hand before. I also added code to automatically upload the build to SourceForge. So yesterday all I had to do was create the VM, upload the script and run it. Six hours later, your phone was able to download the update without any further intervention on my part.
What can I say, the geek in me is very happy
Hi, I thank you for your work. Would you know if I can install microg without magisk, maybe via nanodroid or similar while maintaining OTA updates?
I have no experience with that. I assume you would have to apply the signature spoofing patch and install microG before booting from the updated system partition. So after installing the OTA update boot into recovery and do this?
Hello ! How to you push the google apps on this one ?
I'd like to get a pico gapp installed to get some game running
It's in the instructions in the first post, after flashing the ROM:
Optionally flash Gapps or anything else:
Advanced > Reboot to recovery
Run adb sideload with your zip
I'm using NikGapps Core myself.
This only works if you do it before first boot by the way, as far as I know you can't put Gapps on an installation you're already using.
Hi! Do you know if this will retain microg if I dirty-flash it on top of a lineage.microg.org build (the last official release) using your MIGRATION build? If you're not sure I'll back up my stuff and give it a shot and report back Thanks a lot for your your work!
Well... I don't think that would work, since this ROM doesn't include microg and the needed signature spoofing, so my guess would be you'll just loose that—if the migration works at all. Let me know what your findings are though!
icantlogin said:
Well... I don't think that would work, since this ROM doesn't include microg and the needed signature spoofing, so my guess would be you'll just loose that—if the migration works at all. Let me know what your findings are though!
Click to expand...
Click to collapse
Here is what I found, in case it helps someone: flashing the migrate ROM and then the latest proper ROM works perfectly, however I did lose microg, system f-droid, etc, and anything which is in the lineage.microg.org build but not in this one.
Now since you are building monthly ROMs, would you consider applying the signature spoofing patch to your builds? This would make it easy for those who want to run microg instead of google play framework/gapps. As far as I understand it you just need to apply this patch with `cd android_frameworks_base; patch -p1 -i /path/to/android_frameworks_base-R.patch`. Thanks again for your efforts
I'm open to consider this, but as I somewhat but not fully grasp the security implications of enabling signature spoofing, and not everyone might want to have this enabled by default, it would have to be a toggle in Developer Options and disabled by default, or I would produce a separate build with the patch applied.
If you could find a patch for me that implements the toggle in Developer Options, that would be great. As I researched it a bit I read that some ROMs have this.
Interesting that the migration worked, by the way!
Some more thoughts on this: it seems with signature spoofing enabled on the ROM, an app still has to ask for the permission to spoof its signature, so for advanced users like us who know what we're doing, I guess that's good enough. I'll have to read up on this a bit more though. I know the LineageOS devs are against implementing it but most everyone else says it's actually not that big of a security risk.
I just reply to show you my gratitude for maintain LoS 18. I updated to 19 two weeks ago and I was literally suffering with the system theme. IDK what they were thinking but it was terrible. Also for me, on 4a, was having lag: An example is when I shuffle songs on Musicolet, they take a good while to update the information (song name, basically) while with 18 it updates as soon as I press next.
BTW, can you recommend me a good KERNEL? Thanks!
I understand that the TWRP team is apparently still working on an official release for Android 13, but is there even an unofficial build available for the P7Pro? If not, is there a recovery alternative? I really want to be able to do a full system (all partitions) backup of my device. Thanks!
You can create dumps of your partitions using ADB shell in system; TWRP is not required to do this.
Though it wouldn't necessarily be any good for doing full partition backups, I'm currently running the recovery from the StagOS ROM in combination with the stock Pixel ROM. I like it because it allows flashing recovery zips without having to say "Yes" every time due to signature stuff.
A very similar thread with the same topic has been discussed a few days ago - you can check here
Anyone can compile TWRP - it's opensource. Pixel 6+ owners are unlikely to get an official build from TWRP since it requires a volunteer to maintain the repo, deal with bug reports, etc.
It's recommended to simply compile the image on an individual basis (you really don't want to rely on a third-party supplied image when you have no way of knowing whether it's safe or not). Compiling isn't a difficult process, but does require an hour or two of reading TWRP's and Google's applicable developer pages, along with ~30 - 60 minutes of set up time on a PC/laptop (I prefer to compile within an Ubuntu VM, but I believe it can also be done in Windows' WSL).
robroy90 said:
I understand that the TWRP team is apparently still working on an official release for Android 13, but is there even an unofficial build available for the P7Pro? If not, is there a recovery alternative? I really want to be able to do a full system (all partitions) backup of my device. Thanks!
Click to expand...
Click to collapse
They still haven't finished official support for Android 12. Since recovery resources on A12+ are located in vendor_boot, bigbiff is trying to figure out a decent way for TWRP to live there, at least as far as the Pixel 5 is concerned. Not sure what other obstacles may be present on the Pixel 6 series and above.
nooted1 said:
Though it wouldn't necessarily be any good for doing full partition backups, I'm currently running the recovery from the StagOS ROM in combination with the stock Pixel ROM. I like it because it allows flashing recovery zips without having to say "Yes" every time due to signature stuff.
Click to expand...
Click to collapse
Hey thanks for this! How did you flash just the recovery partiton on the Pixel? I am an old hand with Odin on the Samsung devices, but Google official devices are still new to me. Will the StagOS recovery recognize an external USB-C flash drive for storage?
s3axel said:
A very similar thread with the same topic has been discussed a few days ago - you can check here
Click to expand...
Click to collapse
Thank you, I went over there and read everything. Much appreciated!