Same here. It's a pity I can't use this fantastic ROM because of this one issue. :crying:
[ROM][UNOFFICIAL][9.0.0][r46][I9100] LineageOS 16.0
- Thread starter rINanDO
- Start date
How do I get my recent apps list or browser tabs? Holding down the home button does nothing, nor does double tapping it...
I'm using Evie launcher (not sure if that's he problem) but pretty sure I had the same issue before I restored Evie.
I'm using Evie launcher (not sure if that's he problem) but pretty sure I had the same issue before I restored Evie.
How well does the official lineage 14 release run compared to this? I'm tempted to downgrade as its having a few issues. Or even lineage 17?
If I do a TWRP backup can I just downgrade and then restore the data?
If I do a TWRP backup can I just downgrade and then restore the data?
Any planned updates on this? Still unable to get the recent apps up. Battery isn't too bad but phone does crash sometimes, not sure why. I'm running it on MicroG. Also, the lineage snap camera images don't show in gallery if stored to SD Card, this is a known issue in lineage. You have to manually browse to the files folder to access images taken with Snap.
Hi. I've been using the lastest build for a while, and in performs rather well. I have a problem, though: Magisk modules don't install, and they ask for a 20.0 version to install, which I have. How can I resolve this issue?
Last edited:
It's working but you've got to install magisk in a certain order all at once...
Installing LOS will encrypt your internal memeory by default.
But if you flash, first, the LOS image, after that magisk module AND after that gapps, without cleaning ANYTHING, becouse you can't do that anyway after flashing LOS (becouse the internal memory is allready encrypted), magisk and gapps will install without any problem... I don't know how, but it will work.
Nice oneCode:/* ** 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. ** **/
Hi all,
This is an unofficial Pie build for the Galaxy S2 (i9100) based on LineageOS 16.0.
Yes Pie on our ancient Galaxy S2. I had it working in September 2018 but waited after I had Autosleep ported to our kernel. The biggest issues before I started porting Pie was the Display stuff. We needed at least HWC 1.3 and we had our old HWC 1.0. Surfaceflinger removed all legacy stuff, so how to upgrade to a new HWC??? I got no knowledge how that works.... Then I remembered that @Fourkbomb was rebasing the kernel for i9300 and was working on HWC. He was working on HWC 1.4, so I tried to port those drivers in our kernel with success! Got display running! After that I fixed a minor thing in system/vold, adding patches we already have in LOS 15.1 and after 3 weeks I got it booting! But batterylife was horrible due lack of AutoSleep. So I ported AutoSleep first to our stable unofficial LOS 15.1 kernel. And now that works, lets publish this first unofficial version of Pie on our S2!
Update 2-2-2019:
I decided to switch to emulated storage. The storage issues are probably because of the legacy partitioning. The crash of the Files-app crashes because of this. The only downside I see is that you need to repit if you want to go back to stock or CM-15.1 or less. We need to use repit anyway for the 1.5GB System partition, so why not? Maybe because you are using LOS 16.0 allready and have some stuff on sdcard0 (the phone' s internal SDCard). I developed 2 years a ago a migration recovery but lost focus. Before you install LOS 16.0 Build#7 and higher, please follow the following instruction:
Upgrade from Build 7-13 to Build #14 and higher
Flash i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.img and reboot recovery. In TWRP-3.3.1-1 you will then be able to (dirty) flash
lineage-16.0-20190707-UNOFFICIAL-i9100.zip
Upgrade from Samsung stock ROM to Build #14 and higher using ODIN 3.07
Copy lineage-16.0-20190707-UNOFFICIAL-i9100.zip to your Micro SD-card before flashing.
Pit: i9100-LOS-16.0-Emulated-Storage.pit UPDATED ON 15-7-2019 due an error in previous PIT
PDA: i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.tar.md5
1. Boot your phone into Download-mode (Volume down + Power/Standby + Home and hold for 10 seconds).
2. Start ODIN 3.07 on your PC.
3. Connect your phone via USB to your PC.
4. Press volume up on your phone, ODIN should detect your phone.
5. In ODIN:
Auto Reboot : unchecked
Re-Partition: checked
PIT : i9100-LOS-16.0-Emulated-Storage.pit
PDA : i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.tar.md5
6. Press Start.
7. After succesful flash, reboot phone into Recovery:
- Press Volume up + Power/Standby + Home and hold for 10 seconds.
The phone shuts down.
- Repeat Press Volume up + Power/Standby + Home and hold for 10 seconds
Phone boots in recovery TWRP 3.3.1-1.
8. Swipe to Allow Modifications
9. In TWRP 3.3.1-1 you need to format partions
- Wipe -> Format Data -> Type [yes]
- Wipe -> Advanced Wipe -> Select:
* Davik / ART Cache
* Cache
* System
* Non-emulated Storage
-> Swipe to Wipe
10. Install LOS-16.0 + Gapps or MicroG
To prevent "Uncryption unsuccessful" error of GAPPS at first start:
- Reboot to recovery and Wipe -> Format Data -> Type [yes] again
11. Boot System
Known issues:
Wifi works and connects, but no Internet. (Network unreachable)Battery drain when Wifi-scanning is enabled (by default when installing GAPPS)Camera doesn't workNo SU, don't know why...Graphical glitchesSoftboots or hang due bugs in HWCVSync not working properly like in LOS 15.1GAPPS is slow and crashes after connecting to WifiLiveDisplay not implementedSometimes graphical glitch at wake up (mDNIe related)SIM pincode broke since build #13. Disable your SIM pincode before using this rom or have your PUK code standby.
Source code:
https://www.github.com/lineageos
https://www.github.com/rinando
Credits to:
@forkbomb444 for his port of HWC 1.4
@Chronomonochrome for teaming up Exynos4 fixes
@TALUAtXDA for porting exFAT
and everyone testing our ROMS!
Build #21 2020-03-20
Overall state: Stable
Android build: 9.0.0-r46
Required recovery: TWRP 3.3.1-1
- Updated sources
- Updated boot-image for Magisk v20.3
Known issues:
- Call recording only records microphone
Please report if there are more issues.
Downloads
i9100-LOS-16.0-Emulated-Storage.pit
i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.tar.md5
i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.img
Download LineageOS 16.0 SU (arm) addon/removal here
lineage-16.0-20200320-UNOFFICIAL-i9100.zip
lineage-16.0-20200320-UNOFFICIAL-i9100_boot_magisk.img
Old builds
XDA:DevDB Information
[ROM][UNOFFICIAL][9.0.0][r46][I9100] LineageOS 16.0, ROM for the Samsung Galaxy S II
Contributors
rINanDO
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.0.x
Version Information
Status: Alpha
Created 2018-10-05
Last Updated 2020-03-20
yes, of corse. But how can I do --> repit to old sizes ?. Please help with instruction
You can star reading here http://forum.xda-developers.com/gal...ivatives/mod-increase-partition-size-t3011162 in pit_files.zip you can find the STOCK pit file and instructions to use it with odin
many thanks.
And what size should I make ? I don't know what the old size was.
Last edited:
As I wrote in the previous post, the one with STOCK in the name. That is the original, the other are changes for the newer developed roms.
I've used Heimdall on Linux and flashed your provided PIT and the TWRP. Everything is working fine. Thank you. Can I update to the official TWRP 3.5 when I flash it inside your TWRP 3.3.1-1 or will this cause any problems? I want my device encrypted as well. Is that possible?
I want to use this device as an air gapped device without any internet connection. Always flight mode turned on. Any advices for this? Which of your ROMs should I use? Does it matter? Should I leave the TWRP as read only (as asked when I enter the recovery) for this?
Which package installer should I use? I think I am not able to install APKs without one (not using GAPPS or F-Droid).
Many questions
Thanks for your help.
I want to use this device as an air gapped device without any internet connection. Always flight mode turned on. Any advices for this? Which of your ROMs should I use? Does it matter? Should I leave the TWRP as read only (as asked when I enter the recovery) for this?
Which package installer should I use? I think I am not able to install APKs without one (not using GAPPS or F-Droid).
Many questions
Thanks for your help.
Last edited:
I've used Heimdall on Linux and flashed your provided PIT and the TWRP. Everything is working fine. Thank you. Can I update to the official TWRP 3.5 when I flash it inside your TWRP 3.3.1-1 or will this cause any problems? I want my device encrypted as well. Is that possible?
I want to use this device as an air gapped device without any internet connection. Always flight mode turned on. Any advices for this? Which of your ROMs should I use? Does it matter? Should I leave the TWRP as read only (as asked when I enter the recovery) for this?
Which package installer should I use? I think I am not able to install APKs without one (not using GAPPS or F-Droid).
Many questions
Thanks for your help.
Hi,
unfortunately I'm not a developer but can try to answer on a couple of questions.
TWRP change may or may not work correctly, I have 3.4.0 on my S2 but with LOS 17.1, still didn't change to 3.5.0. You have to which one is the last tested with the rom you want to use.
Roms can work even without a sim or with an not active one, keep it simple, just set flight mode once powered up.
You don't need GAPPS or F-Droid, you can just search the rom (with file manager) and install. Play store or other are just repository, of course you have to download apk on a PC and copy it to micro sd.
I realized that I can install APK yesterday. Didn't know why it just opened the ZIP archive on the first run instead of installing it.
Thanks for your help.
Have you managed to encrypt your device? I got it to work one time yesterday but I wasn't really sure if it is really working. The process just didn't took any time but I was asked for the unlock password when I started the phone. I coulnd't imaging that it is working, so I was opening TWRP and I thought if it work it should ask me for password there also. But it didn't but it also didn't show me any files on my storage. So I was still unsure, did it work maybe?
I just restarted the process of flashing with the PIT provided here and the TWRP 3.3.1-1 but I never got it to work again. The encryption just starts and never finished. I am searching now for a ROM where it works because that's my most important requirement to the phone. I don't need phone calls, bluetooth or a fast phone.
Thanks for your help.
Have you managed to encrypt your device? I got it to work one time yesterday but I wasn't really sure if it is really working. The process just didn't took any time but I was asked for the unlock password when I started the phone. I coulnd't imaging that it is working, so I was opening TWRP and I thought if it work it should ask me for password there also. But it didn't but it also didn't show me any files on my storage. So I was still unsure, did it work maybe?
I just restarted the process of flashing with the PIT provided here and the TWRP 3.3.1-1 but I never got it to work again. The encryption just starts and never finished. I am searching now for a ROM where it works because that's my most important requirement to the phone. I don't need phone calls, bluetooth or a fast phone.
Unfortunately, I can't help with encryption, I never used it. Maybe you can find info searching in this forum.
But I'm pretty sure that this can be done on every LOS for our S2. In this case, you have just to get the ROM you like more. From my point of view newer is better but this means also that needs more space and power, so phone becomes a bit slower.
Thanks for your help. I have tried several ROMs now with different TWRP versions but all I get when I press "encrypt phone" button is an Android robot for one second or two and then the phone just restarts
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
102Code:
/* ** 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. ** **/
Hi all,
This is an unofficial Pie build for the Galaxy S2 (i9100) based on LineageOS 16.0.
Yes Pie on our ancient Galaxy S2. I had it working in September 2018 but waited after I had Autosleep ported to our kernel. The biggest issues before I started porting Pie was the Display stuff. We needed at least HWC 1.3 and we had our old HWC 1.0. Surfaceflinger removed all legacy stuff, so how to upgrade to a new HWC??? I got no knowledge how that works.... Then I remembered that @Fourkbomb was rebasing the kernel for i9300 and was working on HWC. He was working on HWC 1.4, so I tried to port those drivers in our kernel with success! Got display running! After that I fixed a minor thing in system/vold, adding patches we already have in LOS 15.1 and after 3 weeks I got it booting! But batterylife was horrible due lack of AutoSleep. So I ported AutoSleep first to our stable unofficial LOS 15.1 kernel. And now that works, lets publish this first unofficial version of Pie on our S2!
Update 2-2-2019:
I decided to switch to emulated storage. The storage issues are probably because of the legacy partitioning. The crash of the Files-app crashes because of this. The only downside I see is that you need to repit if you want to go back to stock or CM-15.1 or less. We need to use repit anyway for the 1.5GB System partition, so why not? Maybe because you are using LOS 16.0 allready and have some stuff on sdcard0 (the phone' s internal SDCard). I developed 2 years a ago a migration recovery but lost focus. Before you install LOS 16.0 Build#7 and higher, please follow the following instruction:
Upgrade from Build 7-13 to Build #14 and higher
Flash i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.img and reboot recovery. In TWRP-3.3.1-1 you will then be able to (dirty) flash
lineage-16.0-20190707-UNOFFICIAL-i9100.zip
Upgrade from Samsung stock ROM to Build #14 and higher using ODIN 3.07
Copy lineage-16.0-20190707-UNOFFICIAL-i9100.zip to your Micro SD-card before flashing.
Pit: i9100-LOS-16.0-Emulated-Storage.pit UPDATED ON 15-7-2019 due an error in previous PIT
PDA: i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.tar.md5
1. Boot your phone into Download-mode (Volume down + Power/Standby + Home and hold for 10 seconds).
2. Start ODIN 3.07 on your PC.
3. Connect your phone via USB to your PC.
4. Press volume up on your phone, ODIN should detect your phone.
5. In ODIN:
Auto Reboot : unchecked
Re-Partition: checked
PIT : i9100-LOS-16.0-Emulated-Storage.pit
PDA : i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.tar.md5
6. Press Start.
7. After succesful flash, reboot phone into Recovery:
- Press Volume up + Power/Standby + Home and hold for 10 seconds.
The phone shuts down.
- Repeat Press Volume up + Power/Standby + Home and hold for 10 seconds
Phone boots in recovery TWRP 3.3.1-1.
8. Swipe to Allow Modifications
9. In TWRP 3.3.1-1 you need to format partions
- Wipe -> Format Data -> Type [yes]
- Wipe -> Advanced Wipe -> Select:
* Davik / ART Cache
* Cache
* System
* Non-emulated Storage
-> Swipe to Wipe
10. Install LOS-16.0 + Gapps or MicroG
To prevent "Uncryption unsuccessful" error of GAPPS at first start:
- Reboot to recovery and Wipe -> Format Data -> Type [yes] again
11. Boot System
Known issues:
Wifi works and connects, but no Internet. (Network unreachable)Battery drain when Wifi-scanning is enabled (by default when installing GAPPS)Camera doesn't workNo SU, don't know why...Graphical glitchesSoftboots or hang due bugs in HWCVSync not working properly like in LOS 15.1GAPPS is slow and crashes after connecting to WifiLiveDisplay not implementedSometimes graphical glitch at wake up (mDNIe related)SIM pincode broke since build #13. Disable your SIM pincode before using this rom or have your PUK code standby.
Source code:
https://www.github.com/lineageos
https://www.github.com/rinando
Credits to:
@forkbomb444 for his port of HWC 1.4
@Chronomonochrome for teaming up Exynos4 fixes
@TALUAtXDA for porting exFAT
and everyone testing our ROMS!
Build #21 2020-03-20
Overall state: Stable
Android build: 9.0.0-r46
Required recovery: TWRP 3.3.1-1
- Updated sources
- Updated boot-image for Magisk v20.3
Known issues:
- Call recording only records microphone
Please report if there are more issues.
Downloads
i9100-LOS-16.0-Emulated-Storage.pit
i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.tar.md5
i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.img
Download LineageOS 16.0 SU (arm) addon/removal here
lineage-16.0-20200320-UNOFFICIAL-i9100.zip
lineage-16.0-20200320-UNOFFICIAL-i9100_boot_magisk.img
Old builds
XDA:DevDB Information
[ROM][UNOFFICIAL][9.0.0][r46][I9100] LineageOS 16.0, ROM for the Samsung Galaxy S II
Contributors
rINanDO
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.0.x
Version Information
Status: Alpha
Created 2018-10-05
Last Updated 2020-03-2028New build is up!
I'm using this build a couple of days now stable as daily drive. HWC still needs work, but at least it doesn't crash after a while and doesn't 'leak' memory. Therefore I find it BETA worthy.
Happy testing!
Build #5 2019-1-13
Overall state: Stable-ish
Android build: 9.0.0-r30
- Updated sources
- Fixed high-res display statusbar issue
- Fixed memory leak and crash in hwc
- ZRAM set to 200MB
- Applied GO config for 512mb devices
Known issues:
- Graphical glitches
Download here: lineage-16.0-20190112-UNOFFICIAL-i9100.zip26New build is up!
Happy testing!
Build #9 2019-2-25
IMPORTANT: You need to migrate to emulated storage using TWRP 3.1.0-EMU-MIGRATION-M-20170318
See opening post for detailed installation instructions.
Overall state: Stable
Android build: 9.0.0-r31
- Updated sources
- Moved Exynos4 framework hacks to device tree's thanks to @ChronoMonochrome
- Move Target SDK to shims to allow textrelocation for gps, sensors and ril (removed bionic/libc-hacks)
- Removed AshMem-tracking hack thanks to @ChronoMonochrome for hacking our libsecril.so!
- Fixed GAPPS crash at first startup. (I think it was Ashmem-tracking hack)
- Wakelock on flashlight (Flashlight turned off after 10 secs)
Known issues:
I hope none Please report
Downloads:
TWRP 3.1.0-EMU-MIGRATION-M-20170318.zip
lanchon-repit-20170115-system=1.5G-data=max-sdcard=min+wipe-preload=min+wipe-i9100.zip
lineage-16.0-20190224-UNOFFICIAL-i9100.zip25New build is up!
Build #15 2019-07-22
Overall state: Stable
Android build: 9.0.0-r44
Required recovery: TWRP 3.3.1-1
- Updated sources
- Reenabled multi-user in low_ram
- Pinnerservice: Drop camera- and launcher apps, resulting more memory for other apps
- Camera: Fixed autofocus in preview (tested with WhatsApp)
- Set ro.config.small_battery-flag. Deep sleep kicks in 15 minutes instead of 30 minutes
- Fixed wakelock issue after using flashlight once
- Dropped Lineage SU in build, download and install seperately from Lineage website
Known issues:
- Call recording only records microphone
Please report if there are more issues.
Downloads
i9100-LOS-16.0-Emulated-Storage.pit
i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.tar.md5
i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.img
Download LineageOS 16.0 SU (arm) addon/removal here
lineage-16.0-20190721-UNOFFICIAL-i9100.zip24
Hi all,
I got a little update. I hope you all enjoyed Xmas and if I'm to busy to post here this year, happy new year to you all!
It is all because off hwc issues. There is a memory leak after the screenshots fix. It eats memory and if surfaceflinger doesn't crash first, you will have low memory problems and lags. I got a fix but it is still in test. After a while of use the phone soft boots with corrupt display because of memory allocation issues. The high resolution status bar issue is a separate issue. Something with allocating memory with less than 32 pixels height can't use overlay I suspect... Don't know why... Disabling overlay works, but consumes cpu and battery because we bypass the gpu this way.
