[ROM][UNOFFICIAL][10.0.0][r41][I9100] LineageOS 17.1

Tech-Hunter

New member
Nov 11, 2020
3
0
0
Hamburg
Magisk v20.4 is the proofed version in the article and it works fine on the phone...

I also DONT need root either - just because of CELL BROADCAST I would like to have root rights and disable the BROADCAST PROCESS.

Did you solved the CELL BROADCAST notification (cp. picture above) in any other way?
 

kalagani

Member
Feb 5, 2020
18
4
3
Flashing under Linux

Hello,
Is flashing pit and twrp removes or corrupt the stock firmware then it will correct. Otherwise Isorec patch and kernals are required to isolate kernal and to install custom TWRP recovery through reocovery mode flashing. Is this correct or not?:rolleyes:
pit is a new memory distribution because the old one doesn't meet the partition size level for the new ROM.
Without isorec patches, the S2 reboot on the Samsung recovery, never on the TWRP recovery, as far as I can remember!

did you flashed through odin or through recovery mode or through adb sideload or through official twrp app ? Which one you used to flash twrp.
My PC is under Linux so I didn't use ODIN but heimdall and adb tools.
In first time I used the lineage-15.1-20181010-UNOFFICIAL-i9100_SU_MicroG custom ROM,
Here is a translation of how I did it from the above link with it
note: the recovery, in fact the trwp3.1.0-0, once unzipped is simply called recovery.img while the kernel is called boot.img
the order 1)
before on S2 switch to download mode by pressing the 3 usual buttons simultaneously (volume down+home+power)
then to be carried out on the PC is
heimdall flash --repartition --pit I9100_1.5GB-System_6GB-Data_512MB-Preload_by-the.gangster.pit --KERNEL boot.img --RECOVERY recovery.img --no-reboot
the no-reboot option allows you to keep the flash result and the distribution on the screen.
the order 2)
to be carried out on the S2
first switch to recovery mode by pressing the 3 usual buttons simultaneously (volume up+home+power)
then move to the trwp recovery menu after switching to French to format (wipe)
2a) Formatting->Advanced formatting and area selection: Normal and Dalvik, System, Data and Internal-Storage caches
monitor the error messages on the latter 3, it may be necessary to repair or change the file system to resolve them
2b) Repair or Change the File System -> to specifically format the 3 partitions mentioned above ONE by ONE
either in Ext4 as in the origin
either in F2FS for Data and Internal-Storage partitions, keeping Ext4 for System
the F2FS having the particularity to be more adapted to Flash memory with faster write accesses (my choice)
there must be no error messages
the order 3)
3a ) on the S2
always in the twrp recovery it is necessary to activate the ADB transfer functionality.
Advanced Settings->Transfer via ADB
this one will then wait for the order
3b) on the PC
adb sideload lineage-15.1-20181010-UNOFFICIAL-i9100_SU_MicroG.zip
3c) on the S2 wait for the download to finish, then reboot, normally the installation will finish after a few minutes.
and at the end the LineageOS prompt will be displayed.
In a second time I flashed a LineageOS 17.1 coming with another pit, isorec and recovery
Here also translation of how I did it from the above link with it
...for this S2 a version of Android 10 has appeared on XDA
ROM] [UNOFFICIAL] [10.0.0] [r37] [I9100] LineageOS 17.1
it comes with the isorec that go well:
another recovery version TWRP i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.tar.md5
a new i9100-LOS-16.0-Emulated-Storage.pit distribution file
Please note:
TWRP must be de-skimmed to obtain the recovery.img form.
tar -xvf i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.tar.md5

So I replayed the orders 1 to 4) from the previous post
 
Last edited:

sirozan

Senior Member
Dec 8, 2014
67
14
28
[...] Magisk v20.4 Manager says: "unsupported / unknown image format" [...]
If i remember correctly, on s2 you can NOT use the Magisk manager app to install Magisk.

You have to flash both the ROM (lineage-17.1-20200926-UNOFFICIAL-i9100.zip) and special Magisk image (lineage-17.1-20200926-UNOFFICIAL-i9100_boot_magisk.img) in TWRP in the same session before you reboot to system.
(to flash an image in TWRP, during install click on "install image" in the bottom right. select the magisk image and flash it to boot, not recovery)
 

bersem

Senior Member
Jan 19, 2014
319
138
63
Hii, I have planned to install recent build from stock. Do I need to flash the isorec image individually or is it enough to flash PIT and mentioned TWRP directly through odin as mentioned by you?. :confused:
All what u have to do are in the OP on first page. PIT and Recovery for Android 10..

Regards !
 

stronkie

New member
Mar 17, 2016
3
0
0
Reboot on SD card format

Hi guys!

Not very experienced with custom roms but using the guide I was able to get the latest version running on my GS2. So far so good. (TWRP 3.4 and 9-26 rom version)
But when I try to format an SD card the GS2 reboots (when progress is at ~20%). SD card is a standard 1GB card and works well in other phone and laptop.
Any idea what seems to be the issue? (I am definitely not excluding the user here ;))
 

teigaff

Member
Jul 8, 2019
6
5
0
I also installed newest version today with this guide. I formatted a 8GB Sandisk SD card. No problem. After 20% the process is quickly finished.

---------- Post added at 09:58 AM ---------- Previous post was at 09:51 AM ----------

How did you install microG? I followed this guide and want F-Droid app and microG installed.
F-Droid: OTA zip installed in TWRP. But in LOS it is not visible.
MicroG: I don't know how to install.
Thanks for your help
 

anton-

Member
Jul 25, 2013
24
8
0
How did you install microG? I followed this guide and want F-Droid app and microG installed.
F-Droid: OTA zip installed in TWRP. But in LOS it is not visible.
MicroG: I don't know how to install.
Thanks for your help
You can install MicroG with the F-droid app: "Aurora Droid" https://f-droid.org/en/packages/com.aurora.adroid/ You have to activate de MicroG repository from the list of repositories and then you can install the MicroG apps as normal app.
 

rINanDO

Senior Member
Dec 17, 2009
611
4,217
123
New build is up!

Hi everyone,
I have been busy at work and private so I hadn't got much time to release a new build. Since Lineage 18.0 there hasn't been an update above R41 anyway. I have updated the sources and I noticed the new version of Magisk. So we got the new Magisk v21.1 supported kernel here :). RIL is still dropping when it suspends after 4 or 5 days uptime on my daily drive phone. It happens rarely in my use and thereby I can't get logs and troubleshoot further (still trying though...).
I hope you all are still healthy in this Corona situation. Take care!


Build #20 2020-11-27
Overall state: Stable
Android build: 10.0.0-r41
Required recovery: TWRP 3.4.0-i9100 for Android 10

Changes:
- Updated sources
- Fixed audio on Bluethooth headset
- Magisk v21.1 supported kernel image

Downloads
i9100-LOS-16.0-Emulated-Storage.pit
TWRP-3.4.0-i9100-Android-10.img

lineage-17.1-20201127-UNOFFICIAL-i9100.zip
lineage-17.1-20201127-UNOFFICIAL-i9100_boot_magisk.img
 

jo-so

New member
Nov 23, 2020
4
1
3
NULL pointer dereference at virtual address 000001fc

Build #20 2020-11-27
Overall state: Stable
Android build: 10.0.0-r41
Required recovery: TWRP 3.4.0-i9100 for Android 10
I've installed the build #20 as a clean install (wipe of all partitions mentioned in the first post) and the app OpenFoodFacts (f-droid(dot)org/de/packages/openfoodfacts.github.scrachx.openfood/) crashes the kernel. When opening the burger menu the system restarts.

Code:
<6>[20733.594144] c0 mif: link_pm_irq_handler: gpio [HWK] get [0]
<6>[20733.594474] c0 s5p-ehci s5p-ehci: host_phy_resume
<6>[20733.629980] c0 mif: link_pm_irq_handler: gpio [HWK] get [1]
<6>[20733.682349] c0 mif: usb_port_resume: 1283, 4
<6>[20733.684357] c1 mif: IPC-RX(16): 7f 0e 00 00 0b 00 ff ca 07 01 03 ff 01 00 05 7e
<6>[20733.995698] c1 s5p-ehci s5p-ehci: host_phy_susp
<1>[20734.236234] c0 Unable to handle kernel NULL pointer dereference at virtual address 000001fc
<1>[20734.296864] c0 pgd = c283c000
<1>[20734.298628] c0 [000001fc] *pgd=00000000
<0>[20734.338551] c0 Internal error: Oops: 5 [#1] PREEMPT SMP
<4>[20734.342450] c0 Modules linked in: Si4709_driver
<4>[20734.346965] c0 CPU: 0    Tainted: G        W    (3.0.101-lineage-g57a94fbaace4 #3)
<4>[20734.354528] c0 PC is at rt_fill_info.isra.38.constprop.42+0x234/0x468
<4>[20734.360946] c0 LR is at rtnetlink_put_metrics+0xec/0x11c
<4>[20734.366237] c0 pc : [<c093e140>]    lr : [<c08ea110>]    psr: 60070013
<4>[20734.366269] c0 sp : c2807b00  ip : 00000000  fp : c2807b54
<4>[20734.378214] c0 r10: 00000000  r9 : c058546c  r8 : c027d000
<4>[20734.383678] c0 r7 : c2807b24  r6 : df8ba180  r5 : c27d5dc0  r4 : d90c90a4
<4>[20734.390447] c0 r3 : 00000000  r2 : 00000000  r1 : d90c90e8  r0 : 00000000
<4>[20734.397220] c0 Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
<4>[20734.404598] c0 Control: 10c5387d  Table: 4283c04a  DAC: 00000015
You can find the full last_kmsg here: files.jo-so(dot)de/last_kmsg (I didn't know how to attach files in this forum.)

BTW: `adb logcat -L` doesn't work for me, should it?
 

rINanDO

Senior Member
Dec 17, 2009
611
4,217
123
I've installed the build #20 as a clean install (wipe of all partitions mentioned in the first post) and the app OpenFoodFacts (f-droid(dot)org/de/packages/openfoodfacts.github.scrachx.openfood/) crashes the kernel. When opening the burger menu the system restarts.



You can find the full last_kmsg here: files.jo-so(dot)de/last_kmsg (I didn't know how to attach files in this forum.)

BTW: `adb logcat -L` doesn't work for me, should it?
I asume previous build #19 was working fine?
 

jo-so

New member
Nov 23, 2020
4
1
3
I asume previous build #19 was working fine?
I don't know. Build #20 was the first one I have installed. Until last weekend I had used LOS 14.1, but smashed it and had to install a new image. So I picked this one. Is a downgrade (20 -> 19) possible and would this help?
 

SaudMujahid

New member
Oct 18, 2020
2
0
1
twrp 3.4.0 does not work

i tried alot to install after flashing the image you provided however it shows"unable to mount sd card" . i tried installing older coms with your twrp version but same error message and when i flash your old twrp 3.3.1 version everything seems to work just fine even the newer builds which clearly says to use the last version:/. any fix?
 

MaddogIT

Senior Member
Sep 17, 2018
65
24
8
Gradisca d'Isonzo (GO)
i tried alot to install after flashing the image you provided however it shows"unable to mount sd card" . i tried installing older coms with your twrp version but same error message and when i flash your old twrp 3.3.1 version everything seems to work just fine even the newer builds which clearly says to use the last version:/. any fix?
TWRP 3.4.0-0 here, last released rom updated from SD without problems. Last Magisk.
 
Nov 19, 2020
8
0
1
Lederhosnland
big thank you!

I almost cant believe that it is possible for you to do the work of the manufacturer (the manufacturer would have less trouble as you guys) and give very good devices as the s2 new life and save them from obsolescence. I like this device more than the new smartphones, it is very battery efficient, small (fits in your hands), has good camera and display. And you developers make it so easy for a noob like me to flash it, its astonishing, and the software is a thousand times better than the stock bloatware. You have my respect.
 

jo-so

New member
Nov 23, 2020
4
1
3
is this ROM usable for a basic backup device?
is it too slow in the interface?
No, it's pretty fast. Depending on you old image, it has the advantage of merged /data and /sdcard. Hence, if you ran out of space for apps on your current image (Android < 9), you should use this new image.
 

jo-so

New member
Nov 23, 2020
4
1
3
Bluetooth doesn't work (I don't know if it works with build #19, because #20 is the first one I've installed.)

When I enable Bluetooth I get a crash:

Code:
I hwservicemanager: getTransport: Cannot find entry [email protected]::IBluetoothHci/default in either framework or device manifest.
W libc    : Unable to set property "ctl.interface_start" to "[email protected]::IBluetoothHci/default": error code: 0x20
E hwservicemanager: Failed to set property for starting [email protected]::IBluetoothHci/default
F libc    : Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 11818 (bt_hci_thread), pid 11782 (droid.bluetooth)
I chatty  : uid=1002(bluetooth) expire 1 line
I chatty  : uid=1002(bluetooth) expire 29 lines
I /system/bin/tombstoned: received crash request for pid 11818
W /system/bin/tombstoned: crash socket received short read of length 0 (expected 12)
I ActivityManager: Process com.android.bluetooth (pid 11782) has died: psvc PER
D BluetoothManagerService: BluetoothServiceConnection, disconnected: com.android.bluetooth.btservice.AdapterService
E BluetoothManagerService: MESSAGE_BLUETOOTH_SERVICE_DISCONNECTED(1)
D BluetoothManagerService: Broadcasting onBluetoothServiceDown() to 5 receivers.
 
  • Like
Reactions: florencebirée

ammar

Senior Member
Apr 5, 2004
278
14
48
All went ok . Just one thing! my S2 has 32GB of storage but after LOS 17.1 update it show now only 16GB!!!
I think it has to do with the PIT file.
Can someone advise how to fix?
thanks