[ROM][FINAL][7.1.2][UNOFFICIAL] LineageOS 14.1

[MYEUHD]

Ooh, thanks for that link about there being potentially new blobs coming. I don't recall having seen them anywhere. My long-term plan was to try using the Linux blobs and shoehorning them into Android via drm-gralloc, but haven't even started trying that (would need a newer kernel). Do you know if Hummingbird (the Barnes and Noble one, not the chipset) has the SGX544 or the 540? I've seen newer blobs for the 544, but not the 540 (except for ones for x86 instead of ARM).

Oh, sorry for misleading you. It turns out that Hummingbird has the SGX544.
I initially thought it had the same GPU as our phone. Again, sorry!

I'm also considering u-boot and a newer kernel (but both of these are probably a dream that will never come to pass - biggest issue for newer kernel is that there's a bug in our current bootloader that prevents loading a kernel newer than ~3.6 which is why u-boot would have to be ported).

Well, I'm not sure about your variant but the galaxysmtd has a signed bootloader.
Here's a description of what that means for those seeing the term for the first time:
"it also occurs that the bootloaders are cryptographically signed with a private key. In that case, the bootrom will check the signature against a public key that cannot be replaced and only run the bootloader if the signature matches. That sort of tivoization prevents replacing pre-installed bootloaders, even when their sources are released as free software." -Replicant's website-
Thus, sadly, it's probably not possible to port u-boot or any other bootloader to our device (and variants).

 

[xc-racer99]

Oh, sorry for misleading you. It turns out that Hummingbird has the SGX544.
I initially thought it had the same GPU as our phone. Again, sorry!

No problem, I guess that's the way things go.

Well, I'm not sure about your variant but the galaxysmtd has a signed bootloader.
Here's a description of what that means for those seeing the term for the first time:
"it also occurs that the bootloaders are cryptographically signed with a private key. In that case, the bootrom will check the signature against a public key that cannot be replaced and only run the bootloader if the signature matches. That sort of tivoization prevents replacing pre-installed bootloaders, even when their sources are released as free software." -Replicant's website-
Thus, sadly, it's probably not possible to port u-boot or any other bootloader to our device (and variants).

Well, my plan was not to have u-boot as a first or second stage bootloader, but rather as a third-stage bootloader. Since the kernel doesn't have to be signed, you should be (theoretically) able to put u-boot in the boot stage where the kernel currently is (skipping most of the low-level init in u-boot) and then have a different, real, kernel partition. However, this is still at the concept stage.

The other option is using the unbrickable mod and/or bootloader hack (see https://xdaforums.com/showthread.php?t=1233273 and https://xdaforums.com/showthread.php?t=1333424 (this thread is T959V-specific, but an equivalent exists for most variants) - but obviously this is not ideal due to the hardware modification involved in the unbrickable mod (note: messing around with the onenand driver can cause the device to enter the "unbrickable" mode - I found this out by accident when trying to use cmdline mtd partitions).

 

[Dmrgrbz]

Hi I Installed this rom everything works well but can I get better performance with any settings ? and is this rom have superuser ?

 

[i9000isalive]

Hi!
- Has anybody succeeded in rooting the i9000 (running on this Rom lineage 14.1)? Installing up-to-date versions of Supersu and Magisk do not seem to work because of the different boot.img (signed bootloader). Any other ways to root? In the developer settings, there is no "root access" option, and the option "manage root accesses" is grayed out.
- I have only very little internal system storage, so I wanted to format my new SD card as internal storage. But everytime I try to do format it as internal, erasing and formating seems to work fine ("is ready" -"Done"), but then reports that the card is corrupted. I have tried this with three different cards (64GB, 4GB, 64MB). It never works. It works, however, to use the SD card as portable storage - but in this case, I cannot store my apps there. Does anybody know a solution for this?
- My phone also shows some part of the normal internal storage as an ejectable SD card. However, it is the built in storage of the phone. Anybody also having this?
- I had to diable a lot of the system apps, so that the phone runs smoothly. All it can cope with at the moment is installing one small additional app. I would like to improve this situation.
- Any ideas on how to improve the RAM situation? I was thinking of porting a swapping SD card, but this does not seem to be possible without root and so little free internal storage.

Would be very happy if somebody has some advice! Thanks

 

[xc-racer99]

Hi!
- Has anybody succeeded in rooting the i9000 (running on this Rom lineage 14.1)? Installing up-to-date versions of Supersu and Magisk do not seem to work because of the different boot.img (signed bootloader). Any other ways to root? In the developer settings, there is no "root access" option, and the option "manage root accesses" is grayed out.
- I have only very little internal system storage, so I wanted to format my new SD card as internal storage. But everytime I try to do format it as internal, erasing and formating seems to work fine ("is ready" -"Done"), but then reports that the card is corrupted. I have tried this with three different cards (64GB, 4GB, 64MB). It never works. It works, however, to use the SD card as portable storage - but in this case, I cannot store my apps there. Does anybody know a solution for this?
- My phone also shows some part of the normal internal storage as an ejectable SD card. However, it is the built in storage of the phone. Anybody also having this?
- I had to diable a lot of the system apps, so that the phone runs smoothly. All it can cope with at the moment is installing one small additional app. I would like to improve this situation.
- Any ideas on how to improve the RAM situation? I was thinking of porting a swapping SD card, but this does not seem to be possible without root and so little free internal storage.

Would be very happy if somebody has some advice! Thanks

For rooting, try flashing the "su (arm)" 14.1 version of the SU add-on from https://download.lineageos.org/extras - since it only modifies /system, it should work. Small nitpick on the reason SuperSU and Magisk don't work - it's not the signed bootloader, but rather that the i9000 doesn't use a standard Android boot.img so Magisk/SuperSU doesn't understand how to extract it to modify it.

For the adopted storage, I'm guessing it's the encryption that then has to be used that is causing issues. I've never tried adopting an SD card, so I don't even know if the kernel properly supports it.

Internal storage being shown as an ejectable SD is normal. This is because Android dropped supported for FAT32 storage on a partition which is what the i9000 has. As such, supported has been hacked in and so it shows as if it's ejectable.

For RAM management, you could try adjusting the the low memory killer values (google how they work). Also, I'm assuming you don't have gapps installed. Another thing you could try is finding a more lightweight launcher than the default LineageOS one. You could also reduce the number of background apps and/or services allowed. This will mean that you always will have to re-open an app, but it might allow more to be installed.

 

[MYEUHD]

Hi!
- Has anybody succeeded in rooting the i9000 (running on this Rom lineage 14.1)? Installing up-to-date versions of Supersu and Magisk do not seem to work because of the different boot.img (signed bootloader). Any other ways to root? In the developer settings, there is no "root access" option, and the option "manage root accesses" is grayed out.

For rooting, try flashing the "su (arm)" 14.1 version of the SU add-on from https://download.lineageos.org/extras - since it only modifies /system, it should work. Small nitpick on the reason SuperSU and Magisk don't work - it's not the signed bootloader, but rather that the i9000 doesn't use a standard Android boot.img so Magisk/SuperSU doesn't understand how to extract it to modify it.

The SU add-on doesn't work, as I have already mentioned in #12.
But the ROM is pre-rooted with Magisk. So, you just have to install the latest MagiskManager.apk from https://github.com/topjohnwu/Magisk/releases

Adding to what xc-racer99 said about RAM management, you can enable UA:CMA from Settings> Device Settings> UA CMA to free memory that's normally allocated to the camera/hardware decoding. more about it in this post https://xdaforums.com/showpost.php?p=74546267&postcount=22
Alternatively, you could extract the boot.img from xc-racer99's AOSP 7.1 ROM zip and flash it, as it supports 'regular' CMA which is like an automatic version of UA:CMA (though sometimes the allocation fails and you can't use the camera/hardware decoding).

 

[xc-racer99]

The SU add-on doesn't work, as I have already mentioned in #12.
But the ROM is pre-rooted with Magisk. So, you just have to install the latest MagiskManager.apk from https://github.com/topjohnwu/Magisk/releases

Adding to what xc-racer99 said about RAM management, you can enable UA:CMA from Settings> Device Settings> UA CMA to free memory that's normally allocated to the camera/hardware decoding. more about it in this post https://xdaforums.com/showpost.php?p=74546267&postcount=22
Alternatively, you could extract the boot.img from xc-racer99's AOSP 7.1 ROM zip and flash it, as it supports 'regular' CMA which is like an automatic version of UA:CMA (though sometimes the allocation fails and you can't use the camera/hardware decoding).

Interesting, I missed the fact that the SU add-on didn't work. Did it fail to flash or just not function?

 

[MYEUHD]

Interesting, I missed the fact that the SU add-on didn't work. Did it fail to flash or just not function?

It just did not function. The "manage root access" option was grayed out even after flashing the add-on.

 

[Pufferine]

May I ask why I just get 104MB free space for the /system/ after the lineage 14.1 ROM is installed?

I don't know why the ROM occupies 780MB and my /system/ is just 885MB in total.

It is annoying since I cannot install the zip file of the GAPPS, even I selected the 'pico' version.

Is it just my problem and can I do some resizing of the /system/ storage?

 

[xc-racer99]

May I ask why I just get 104MB free space for the /system/ after the lineage 14.1 ROM is installed?

I don't know why the ROM occupies 780MB and my /system/ is just 885MB in total.

It is annoying since I cannot install the zip file of the GAPPS, even I selected the 'pico' version.

Is it just my problem and can I do some resizing of the /system/ storage?

Sounds like slightly more is used in /system than I'd expect, but entirely possible (I haven't used this particular ROM). You could try removing some apps from /system that you don't need.

It is possible to adjust the size of /system, have a look at the updater.sh in the zip file. Problem is that if you increase the /system partition by 500MB then you're decreasing the size of your /data partition by 500MB as well Note that this will also wipe /data.

 

[veloo]

bricked?

after flashing this, i am having bootloops please help

 

[bulentmsl]

Hello. I can't find the TWRP 3.1.1 version. Where can I download this

 

[xc-racer99]

after flashing this, i am having bootloops please help

We'll need a little more info to help you - bootloops is a very imprecise term. It's like going to the doctor and saying I'm sick without giving any symptons What's the last screen that you see when booting normally, can you get into recovery (if so, what recovery version is it). Also, please attach the *_mtd.log from your SD card if possible.

Hello. I can't find the TWRP 3.1.1 version. Where can I download this

On almost all first-gen Galaxy S devices, recovery is integrated into the boot.img - so to install TWRP you need to install a kernel/ROM with TWRP already built in. Typically, that means working your way up Android versions one at a time until you reach your desired stopping point.

 

[veloo]

thank you for responding. i spent my whole weekend trying to recover. i couldn't get into recovery, but could get into flashboot. even odin couldn't get help. finally i managed to stock rom it with heimdall. thankfully, i had a nandroid backup so i think i'm ok now. whew, and this is my daily phone. i was a bit adventurous there, and thought i would play with the a new android version for a few hours to kill.

 

[ale14e63]

buenas no reconoce la sim

 

[TheComrade]

Nice rom but unstable

 

[Deleted member 10638533]

Oreo possible?
S2 had 10

 

[xc-racer99]

Oreo possible?
S2 had 10

Possible, yes, but there's no known graphics drivers that work on Oreo (I tried with the JB 4.1.2 ones we've been using from the Nexus S). Software rendering would theoretically work, but it would be very slow and I never bothered to try.

 

[jirki88]

Guys, don't bother looking for twrp3.1.1. Twrp3.0.3 is good enough to install this rom.

I started from cm12 with twrp3.0.0. Then we need to upgrade to twrp3.0.2 by installing CM13. If you installed other versions of CM13, it may contain the wrong twrp. Then, install CM14.1 to get twrp3.0.3. That's how I get rid of error 7.

BTW, first boot takes like 30min, and I lost IMEI and baseband.

Hello. Can you help me find CM12 with TWRP 3.0.0?? i can find only 2.8.something.

 

[k2-18b]

Bootloops after Installation

After the reboot, the screen alternated between the old, large Samsung logo and the new, slightly more delicate one.
Ten seconds volume up + Home + Power press and hold, and the phone boots into recovery.

It works roughly (I tried a thousand monkey handles until it worked ...) like this: Gingerbread with CF-Root: Install 2x CM13> Wipe Factory Reset> Mount data> format data F2FS> Install 2x CM 14, then the Past Installation Zip> Factory Wipe> Reboot.
I tried today, the system works. Unfortunately didn't have time to try again.

after flashing this, i am having bootloops please help

---------- Post added at 08:55 PM ---------- Previous post was at 08:49 PM ----------

En mi S1 la SIM se reconoce y funciona. Alemania, Congstar, Telekom.

buenas no reconoce la sim