Project

General

Profile

GalaxySIIGTI9100G » History » Version 74

Denis 'GNUtoo' Carikli, 04/03/2020 05:44 AM

1 19 Denis 'GNUtoo' Carikli
h1. Galaxy S II (GT-I9100G)
2 2 Denis 'GNUtoo' Carikli
3 20 Denis 'GNUtoo' Carikli
{{>toc}}
4
5 21 Denis 'GNUtoo' Carikli
|/9. !galaxys2.png! | *Device* | Galaxy S II (GT-I9100G) |
6 20 Denis 'GNUtoo' Carikli
| *Manufacturer* | Samsung |
7 21 Denis 'GNUtoo' Carikli
| *Release date* | ? |
8 22 Denis 'GNUtoo' Carikli
| *Codename* | @i9100G@ ? |
9 20 Denis 'GNUtoo' Carikli
| *Status* | Not supported yet |
10 23 Denis 'GNUtoo' Carikli
| *Variants* | GSM: GT-I9100G |
11 20 Denis 'GNUtoo' Carikli
| *Latest images* | None |
12
13 17 Denis 'GNUtoo' Carikli
h2. History
14
15 56 Denis 'GNUtoo' Carikli
Long time ago, we had reports that the "Galaxy SII" had an unsigned bootloader, but we didn't manage to confirm to which exact model it applied to, or if people assumed that the bootloader of the GT-I9100 was unsigned because it uses Xloader which is GPLv2. Samsung also published the source code of various Xloader versions they used on the GT-I9100G for different Android versions. However until now we weren't able to confirm that any device were able to run unsigned bootloaders. Though we verified that at least the bootloader of the I9100G_CHN_CHN is signed.
16
17 17 Denis 'GNUtoo' Carikli
h2. Rationale
18 1 Denis 'GNUtoo' Carikli
19 57 Denis 'GNUtoo' Carikli
* Uses the samsung-ipc protocol
20 17 Denis 'GNUtoo' Carikli
* The modem probably uses MIPI, so it should be isolated
21
* 1G of ram => it should be enough for Replicant 6 and 9
22 1 Denis 'GNUtoo' Carikli
23 34 Denis 'GNUtoo' Carikli
h2. Wiki pages
24
25
* [[I9100GBootloader]]: Research on bootloader freedom for the GT-I9100G
26
27
h2. Various IRC logs of research on it.
28 24 Jens Korte
29 61 Denis 'GNUtoo' Carikli
TODO:
30
* Read the log below and remove what is not relevant
31
* Add what is relevant in various pages of the Replicant wiki or Wikidata and point to that if it's in another page that this one (or wikidata).
32
33 63 Denis 'GNUtoo' Carikli
h3. GT-I9100G bootloader related
34 1 Denis 'GNUtoo' Carikli
35
(08:47:20 PM) sensiblemn: GNUtoo: i just got a report from a postmarketOS developer saying that booting works with that free software x-loader repo for the i9100G that I found. they had to make a one line commit to get it building, but it boots. https://github.com/hpagseddy/i9100g_xloader/commit/0505138dd163959443f09b7178142c0472f60582
36 62 Denis 'GNUtoo' Carikli
(08:48:24 PM) sensiblemn: so early reports suggest that we found a Galaxy S2 that has a free software bootloader. they said it doesn't even need to be signed with signGP.c.
37 1 Denis 'GNUtoo' Carikli
(10:36:35 PM) hpagseddy[m]: So i have an i9100g and compiled this without any errors in case you guys are interested https://github.com/hpagseddy/i9100g_xloader
38
(10:49:32 PM) freekurt: thanks for jumping in here hpagseddy. we have been trying for quite some time to find a way to liberate the first stage bootloader on Exynos4 SoC based i9100 and i9300 devices. this is great news that the i9100G seems to have a free software first stage bootloader.
39 14 Kurtis Hanna
(10:51:08 PM) hpagseddy[m]: Yep, also there is a thing that i9100g is based on TI OMAP
40 63 Denis 'GNUtoo' Carikli
41 64 Denis 'GNUtoo' Carikli
h3. GT-I9100G Linux upstreaming
42 63 Denis 'GNUtoo' Carikli
43 14 Kurtis Hanna
(11:01:27 PM) hpagseddy[m]: Btw Droid 4 has mainline
44 1 Denis 'GNUtoo' Carikli
(11:02:42 PM) hpagseddy[m]: i9100g uses same display and digitizer with i9100, has a broadcom wifi but sadly a PowerVR GPU
45 64 Denis 'GNUtoo' Carikli
(11:10:48 PM) hpagseddy[m]: Since it uses same display and even same connectors
46
(11:11:06 PM) hpagseddy[m]: I know it because i am using i9100 display on my i9100g :)
47
(11:11:17 PM) hpagseddy[m]: Besides capacitive buttons, all functional
48
(11:11:48 PM) hpagseddy[m]: Even capacitive connector plugged in so if i do some kernel hacks i can get them working too
49
(11:11:50 PM) freekurt: we really appreciate your willingness to do testing if we decide to proceed with trying to mainline this device, which has yet to be determined.
50
(11:14:38 PM) freekurt: it seems as though this device would be quite attractive to other pmOS devs as well, now that the freedom of the bootloader appears to have been determined.
51
(11:15:19 PM) hpagseddy[m]: I hope so, i was the only maintainer over 2 years :)
52
(11:15:27 PM) hpagseddy[m]: Of this device
53
(11:15:37 PM) freekurt: :-) thanks for holding down the fort!
54
(11:15:52 PM) hpagseddy[m]: But if the device gets mainlined, things will definitely change
55 63 Denis 'GNUtoo' Carikli
56 71 Denis 'GNUtoo' Carikli
h3. OMAP4 blaze reference platform related
57 14 Kurtis Hanna
58
(07:17:23 PM) sensiblemn: GNUtoo: ah, it seems like some OMAP devices are GP and others are HS, so the question is whether we can find smartphones and tablets that are GP. Looks like the Blaze Tablet released by TI is GP. https://wiki.tizen.org/Tizen_IVI_Getting_Started_Guide_For_PandaBoard#x-loader_config_files [...]
59
(07:22:26 PM) sensiblemn: also this very odd looking OMAP Blaze cell phone seems to be GP rather than HS. https://www.slashgear.com/texas-instruments-omap-blaze-on-sale-now-1485657/
60
(07:23:30 PM) sensiblemn: https://www.ebay.com/itm/TI-Stereo-Camera-Blaze-development-Plattform-im-Wert-von-1-800USD/131690215016
61
(07:24:04 PM) sensiblemn: https://web.archive.org/web/20180903060622/http://omapedia.org/wiki/OMAP4_Blaze
62 1 Denis 'GNUtoo' Carikli
63 71 Denis 'GNUtoo' Carikli
TODO: add the blaze, zoom1 (omap3), zoom2 to the reviewd devices and to wikidata
64
65
h3. Android requirements
66
67 14 Kurtis Hanna
(10:58:08 PM) freekurt: 512 MB of RAM seems rough for AOSP 10, especially when we are trying to get it to work with 2D acceleration. 1GB should be much better.
68 1 Denis 'GNUtoo' Carikli
=> TODO: check Android 10 requirements and add them to the wiki
69 14 Kurtis Hanna
70 70 Denis 'GNUtoo' Carikli
h3. Service mode (of the I9100G ?)
71 14 Kurtis Hanna
72 74 Denis 'GNUtoo' Carikli
<pre>
73
hpagseddy[m]: its ok i found the code
74
hpagseddy[m]: So i am at the main menu
75
[...]
76
hpagseddy[m]: So the fullname is like SP6260_T1_01.1300
77
[...]
78
sensiblemn: are you seeing that in service mode?
79 14 Kurtis Hanna
(12:47:36 AM) hpagseddy[m]: no
80
(12:47:52 AM) hpagseddy[m]: i just saw SP6260_T1_01.1300
81
(12:48:22 AM) hpagseddy[m]: since the numbers match and XMM6260 used in S2
82
(12:48:31 AM) hpagseddy[m]: i made a conclusion like this
83
(12:51:03 AM) forkbomb: i'm pretty sure it would be XMM6260 or XMM6262, same as i9300
84
(12:51:21 AM) sensiblemn: oh, that sounds convenient!
85
(12:51:50 AM) hpagseddy[m]: Perfect
86 74 Denis 'GNUtoo' Carikli
87 14 Kurtis Hanna
(12:56:01 AM) forkbomb: hpagseddy[m]: ah, the i9100G is different i think
88
(12:56:06 AM) forkbomb: it's OMAP based
89
(12:56:10 AM) hpagseddy[m]: other one was for the development board??
90
(12:56:15 AM) hpagseddy[m]: Yes it is
91 1 Denis 'GNUtoo' Carikli
(12:56:23 AM) hpagseddy[m]: TI OMAP4430, same as Droid 4
92
(12:56:58 AM) sensiblemn: actually, this looks like the correct defconfig for it, still says xmm6260 https://github.com/LineageOS/android_kernel_samsung_t1/blob/cm-12.1/arch/arm/configs/android_t1_omap4430_r03_eng_defconfig#L1097
93
(12:57:38 AM) hpagseddy[m]: i think so
94 14 Kurtis Hanna
(12:57:48 AM) hpagseddy[m]: if it has t1 then it is i9100g
95
(12:58:17 AM) sensiblemn: dang, i messed that last link up. this is it. final answer. https://github.com/LineageOS/android_kernel_samsung_t1/blob/10ca03795f659f6f1fa995e8c300a08c3a133354/arch/arm/configs/cyanogenmod_i9100g_defconfig#L1107
96
(12:59:50 AM) hpagseddy[m]: the other one is most likely development board or prototype configs
97 74 Denis 'GNUtoo' Carikli
98
h3. I9300T
99
100
(12:51:55 AM) forkbomb: the i9300T is just a Telstra branded i9300 afaik
101
(12:52:49 AM) hpagseddy[m]: <freekurt "yeah, that might be it. https://"> i9300T has the same SP6260 naming as i9100g as this shows
102
(12:53:10 AM) sensiblemn: you're correct
103
(12:54:16 AM) sensiblemn: also, not sure if this is the correct defconfig, but this kernel from samsung suggests it is xmm6260 also https://github.com/LineageOS/android_kernel_samsung_t1/blob/10ca03795f659f6f1fa995e8c300a08c3a133354/arch/arm/configs/android_t1_omap4430_r03_eng_defconfig#L1097
104
(12:55:09 AM) hpagseddy[m]: t1, thats correct
105
(12:55:18 AM) hpagseddy[m]: but the defconfig isnt
106
(12:55:48 AM) hpagseddy[m]: https://github.com/LineageOS/android_kernel_samsung_t1/blob/10ca03795f659f6f1fa995e8c300a08c3a133354/arch/arm/configs/cyanogenmod_i9100g_defconfig
107
(12:55:52 AM) hpagseddy[m]: this is for the device
108
109
110 70 Denis 'GNUtoo' Carikli
111
h3. TODO: Notify forkbomb
112
113 14 Kurtis Hanna
(01:00:57 AM) sensiblemn: forkbomb: did you hear that we seem to have found a free software first stage bootloader for the i9100G and that it doesn't seem to require any signature checks?
114
(01:01:27 AM) hpagseddy[m]: yes i compiled and ran it on my device with no problem
115
(01:01:59 AM) hpagseddy[m]: also fixed the old build a bit
116
(01:02:02 AM) hpagseddy[m]: >So i have an i9100g and compiled this without any errors in case you guys are interested https://github.com/hpagseddy/i9100g_xloader
117 1 Denis 'GNUtoo' Carikli
(01:05:55 AM) forkbomb: no, i didn't. very nice!
118 14 Kurtis Hanna
(01:06:35 AM) hpagseddy[m]: well i dont know how to use it so just compiled and flashed with odin
119
(01:06:45 AM) hpagseddy[m]: also one line fix hehe
120
(01:07:33 AM) hpagseddy[m]: it compiled with no problem on 4.6 gcc
121
(01:14:47 AM) sensiblemn: hpagseddy: it is my understanding that, since x-loader is EOL, and since Replicant wants to upstream as much code as we can, we would have to upstream what x-loader is doing into u-boot SPL, which i don't know how long it would take to do. the fact that very similar devices are already in upstream u-boot likely will help though, if we decide to pursue it.
122
(01:16:01 AM) hpagseddy[m]: Since it is open source, it is ok to keep it untill we have the device booted in my opinion
123
(01:16:17 AM) sensiblemn: yes, for sure.
124
(01:17:00 AM) hpagseddy[m]: but well last decision is yours since you guys are the replicant devs :)
125 70 Denis 'GNUtoo' Carikli
126
h3. LineageOS support
127
128 14 Kurtis Hanna
(01:22:29 AM) sensiblemn: hpagseddy: have you tested LineageOS 13 on the device before? https://forum.xda-developers.com/galaxy-s2/development/rom-lineageos-13-0-t3620246
129
(01:23:21 AM) hpagseddy[m]: yes it had several issues but performance was good
130 1 Denis 'GNUtoo' Carikli
(01:23:33 AM) hpagseddy[m]: it had audio error which was so annoying
131 14 Kurtis Hanna
(01:23:41 AM) hpagseddy[m]: 12.1 was best
132
(01:24:22 AM) sensiblemn: what kind of audio error?
133
(01:25:51 AM) hpagseddy[m]: audio was some kind of disorted
134
(01:39:01 AM) sensiblemn: hpagseddy: did you notice any other issues?
135
(01:39:11 AM) sensiblemn: with 13?
136
(01:40:13 AM) hpagseddy[m]: Gps doesnt work
137
(01:40:18 AM) hpagseddy[m]: Night mode doesnt work
138 70 Denis 'GNUtoo' Carikli
139 14 Kurtis Hanna
01:56 <@GNUtoo> Did LineageOS or Cyanogenmod support it at some point?
140
01:57 < hpagseddy[m]> Cyanogenmod untill 13.0
141
01:57 < hpagseddy[m]> Omnirom 4.4 and 5.0.2
142
01:57 <@GNUtoo> ok, that explains why LineageOS has some stuff on it but nothing on the wiki
143
01:57 < hpagseddy[m]> thats all i remember and tested
144
[...]
145
01:58 < hpagseddy[m]> GNUtoo: yeah they just forked it and it just stays there
146
[...]
147
01:59 < hpagseddy[m]> but 12.1 is still cyanogen
148
02:00 < sensiblemn> there was an attempt made at 14.1 but it seems like it was unsuccessful because it wouldn't boot
149
02:00 < sensiblemn> https://github.com/xdaamg/android_device_samsung_i9100g/tree/cm-14.1
150
02:00 < hpagseddy[m]> also someone rebased cm11 to lineage 11
151 70 Denis 'GNUtoo' Carikli
152
h3. TODO: look at omap-usb-tool patches and merge them or ask for sending patches for review
153
154
(01:19:56 AM) sensiblemn: GNUtoo: this looks like omap-usb-tool but it was recently updated https://github.com/LukasTomek/omapboot
155
(01:21:37 AM) hpagseddy[m]: hmm, he forked this repo from https://github.com/kousu/omapboot
156
(01:22:03 AM) hpagseddy[m]: so he added sd card booting
157
(01:22:09 AM) hpagseddy[m]: and some fixed
158
(01:22:13 AM) hpagseddy[m]: fixes*
159
(01:22:25 AM) GNUtoo: https://git.paulk.fr/omap-usb-boot.git
160
(01:22:29 AM) GNUtoo: but it seems down right nw
161
(01:22:32 AM) GNUtoo: *right now
162
163
h3. Diff between the samsung xloader and hpagseddy xloader
164
165 73 Denis 'GNUtoo' Carikli
hpagseddy's fork consists of Samsung source code with the addition of "a fix to enable to build it (with more modern gcc?)":https://github.com/hpagseddy/i9100g_xloader/commit/0505138dd163959443f09b7178142c0472f60582 .
166 45 Denis 'GNUtoo' Carikli
167 28 Denis 'GNUtoo' Carikli
h2. Partitions
168
169
The PIT  of the Galaxy SII (GT-I9100G) can be found in the [[GalaxySIII9100GPit]] page.
170 36 Denis 'GNUtoo' Carikli
171 45 Denis 'GNUtoo' Carikli
|_. PIT |_. Linux name |_. mount point |_. partition type |_. block device |_. Description |
172 51 Denis 'GNUtoo' Carikli
| MLO |\2. Not visible on Linux | | | First stage of bootloader |
173
|\2. EFS | | | mmcblk0p1 | modem data partition |
174 52 Denis 'GNUtoo' Carikli
|\2. SBL1 | | | mmcblk0p2 | |
175 51 Denis 'GNUtoo' Carikli
|\2. SBL2 | | Empty | mmcblk0p3 | |
176
|\2. PARAM  | | | mmcblk0p4 | |
177
|\2. KERNEL | None | zImage | mmcblk0p5 | boot partition, See [[IsorecRecoveryIssue]] for more details |
178
|\2. RECOVERY | None | | mmcblk0p6 | recovery partition, See [[IsorecRecoveryIssue]] for more details |
179
|\2. CACHE| | | mmcblk0p7 | Android cache partition |
180
|\2. MODEM| | | mmcblk0p8 | modem firmware partition |
181
|\2. FACTORYFS| | | mmcblk0p9 | Android system partition |
182
|\2. DATAFS| | | mmcblk0p10 | Android application data |
183
|\2. UMS | | | mmcblk0p11 | user data (music, pictures, etc) |
184 35 Denis 'GNUtoo' Carikli
|\2. HIDDEN | | | mmcblk0p12 | contains some data, and Samsung APK |
185
186
This was constructed from the PIT, TODO: check the partitions content
187 46 Denis 'GNUtoo' Carikli
188
h3. MLO
189 53 Hpag Seddy
190 46 Denis 'GNUtoo' Carikli
On a I9100G_CHN_CHN with Android 2.3.6 with the OMAP reported as being in HS mode we have:
191
<pre>
192
--- Entry #0 ---
193
Binary Type: 0 (AP)
194
Device Type: 2 (MMC)
195
Identifier: 1
196
Attributes: 0 (Read-Only)
197
Update Attributes: 0
198
Partition Block Size/Offset: 0
199
Partition Block Count: 0
200
File Offset (Obsolete): 0
201
File Size (Obsolete): 0
202
Partition Name: X-loader
203
Flash Filename: MLO
204
FOTA Filename: 
205
</pre>
206
207
This doesn't give any indication of where is MLO, but it's clearly visible with an hexadecimal editor like vbindiff.
208 48 Denis 'GNUtoo' Carikli
209 46 Denis 'GNUtoo' Carikli
|_. Offset from mmcblk0 |_. size |_. comments |
210
| 0x20000 (256k) | 256k | MLO + potentially other stuff |
211
| 0x40000 (512k) | 256k | MLO + potentially less other stuff |
212
213 47 Denis 'GNUtoo' Carikli
214 46 Denis 'GNUtoo' Carikli
Though SBL1 and SBL2 have location and size reported my the bootloader with heimdall print-pit:
215
<pre>
216
--- Entry #2 ---
217
Binary Type: 0 (AP)
218
Device Type: 2 (MMC)
219
Identifier: 2
220
Attributes: 0 (Read-Only)
221
Update Attributes: 0
222
Partition Block Size/Offset: 49152
223
Partition Block Count: 4096
224
File Offset (Obsolete): 0
225
File Size (Obsolete): 0
226
Partition Name: SBL1
227
Flash Filename: Sbl.bin
228
FOTA Filename: 
229
</pre>
230
231
<pre>
232
--- Entry #3 ---
233
Binary Type: 0 (AP)
234
Device Type: 2 (MMC)
235
Identifier: 3
236
Attributes: 0 (Read-Only)
237
Update Attributes: 0
238
Partition Block Size/Offset: 53248
239
Partition Block Count: 4096
240
File Offset (Obsolete): 0
241
File Size (Obsolete): 0
242
Partition Name: SBL2
243
Flash Filename: 
244
FOTA Filename: 
245
</pre>
246 27 Denis 'GNUtoo' Carikli
247
h2. Recovery
248
249
The device is not supported by TWRP, but it was supported by cyanogenmod recoveries:
250
251 1 Denis 'GNUtoo' Carikli
https://web.archive.org/web/20190328070606/http://download.cyanogenmod.org:80/?device=i9100g
252 41 Denis 'GNUtoo' Carikli
253 31 Denis 'GNUtoo' Carikli
That recovery is a zImage. Note that this recovery may not be FSDG compliant, so the first step would be to make a Replicant recovery for this device/
254 43 Denis 'GNUtoo' Carikli
255
h2. CyanogenMod support and stock Android with the version that has a signed bootloader
256
257
According to the "I9100G CyanogenMod installation instructions":https://web.archive.org/web/20161224202727/https://wiki.cyanogenmod.org/w/Install_CM_for_i9100g , "Users running Android 2.3 on their I9100G MUST first upgrade to stock Android 4.x before installing CyanogenMod, or the device won't boot into the system due to it relying on a newer bootloader. A 4.1 bootloader is recommended."
258
259
However this approach has several issues.
260
261
The update doesn't work anymore. 
262
263
It also requires you to put a SIM card in the device, which results in privacy issues.
264
265
In addition to that, it requires you to give the device a network connection, knowing that the device is running a proprietary Android distribution.
266
267
Once you do that it still fails with "Processing failed".
268
269
Right before the failure you can see "Signup for a Samsung account" on the top of the window with "Terms and conditions".
270 44 Denis 'GNUtoo' Carikli
271
So it probably tries to access some page like https://bada.com/contents/deviceterms/china/208.txt which doesn't exist anymore, and it probably does that to show terms and conditions which were probably unacceptable. 
272
273 43 Denis 'GNUtoo' Carikli
They might also have legally prevented you to work on some part of Replicant if you agreed to them, depending on the country you are located in or you intend to travel to.
274
275 5 Denis 'GNUtoo' Carikli
This is most probably not an issue with the versions that don't have a signed bootloader as the first stage bootloader could simply be replaced by a free software xloader.
276 60 Denis 'GNUtoo' Carikli
277 59 Denis 'GNUtoo' Carikli
h2. Bootloaders
278 60 Denis 'GNUtoo' Carikli
279 15 Denis 'GNUtoo' Carikli
See [[GTI9100GBootloaderFreedom]] and [[GTI9100GBootloaderInterface]]
280 53 Hpag Seddy
281
h2. Hardware
282
283 67 Denis 'GNUtoo' Carikli
h3. Sumary
284
285 53 Hpag Seddy
As far is we get from what we've seen on the motherboard itself, here are our guesses about chips and what they do:
286 55 Hpag Seddy
287
* 6030B1A5 21ZEDL9G2 G1 --- Power IC based on sellers on the web
288
* TWL6040A2 22AH9SW G2 --- Audio codec made by TI https://www.alldatasheet.com/datasheet-pdf/pdf/862981/TI1/TWL6040A2.html
289
* I9811 V 1.0B XG626 F2076538  --- Modem IC
290
* SAMSUNG 210 KMVYLOOOLM-B503 --- EMMC Chip 16GB based on this forum thread https://www.mcrf.ru/forum/showthread.php?t=40277
291 5 Denis 'GNUtoo' Carikli
* K3PE7E700D-XGC1 --- DDR DRAM chip, most likely 1GB
292 1 Denis 'GNUtoo' Carikli
293 67 Denis 'GNUtoo' Carikli
h3. PCB details
294 65 Denis 'GNUtoo' Carikli
295 66 Denis 'GNUtoo' Carikli
Chips markings:
296
297
<pre>
298
Ti logo
299
6030B1A5
300
21ZEDL9G2
301
G1
302
</pre>
303
304
<pre>
305
TI logo
306
TWL6040A2
307
22AH9SW G2
308
G1
309
</pre>
310
311
I'm not sure about G1, maybe it's Gi or G|
312
313
Modem:
314
<pre>
315
I9811
316
V 1.0B
317
XG626
318
H1207
319
</pre>
320
And on the right side, there is F2076538 written.
321
322
323
There is a small battery soldered. That might be interesting if it's able to keep the correct time when the battery is removed. 
324
If not you need to run disable-modem.sh then to turn off the phone and remove the battery, and then put on the battery, set the correct time, and then enable-modem.sh
325
326
<pre>
327
SAMSUNG 210
328
K3PF7E700 XGC1
329
GKB2609G
330
</pre>
331
332
There are with many capacitors around
333
334
Links about similar chips:
335
* https://www.kynix.com/Detail/1185174/K3PE7E700D-XGC2.html
336
* https://memorylink.samsung.com/ecomobile/mem/ecomobile/product/productDetail.do?topMenu=P&subMenu=mobileDram&appNo=&appLabel=&partNo=K3PE7E700M-XGC1&partSetNo=LPDDR2
337
*  https://commons.wikimedia.org/wiki/File:Samsung_Galaxy_Tab_2_10.1_-_Samsung_K3PE7E700M-XGC1-3956.jpg Interesting
338
339
The links talk about things like LPDDR2. The links are not for the same chip but, for the second part number, the reference is pretty close ( K3PE7E700M-XGC1 )
340
341
The third link has a description with "Mobile DRAM LPDDR2" and "Package: FBGA"
342
343 65 Denis 'GNUtoo' Carikli
FBGA is "Fine Ball Grid Array based on ball grid array technology. It has thinner contacts and is mainly used in system-on-a-chip designs" "according to wikipedia":https://en.wikipedia.org/wiki/Ball%20grid%20array
344
345 69 Denis 'GNUtoo' Carikli
SOC (and eMMC?):
346 68 Denis 'GNUtoo' Carikli
<pre>
347
SAMSUNG 210
348
KMVYLOOOLM-B503
349 1 Denis 'GNUtoo' Carikli
CrBM60E1
350
Maybe MDL5 15
351 69 Denis 'GNUtoo' Carikli
</pre>
352 68 Denis 'GNUtoo' Carikli
353 69 Denis 'GNUtoo' Carikli
I'm not 100% sure of the last line (Maybe MDL5 15) as there are stuff printed with a blue ink on top (040321)
354 68 Denis 'GNUtoo' Carikli
355
* Some links talk about "CPU":
356
** https://sourcing.1688.com/buyoffer/detail.htm?entrySource=&id=20446920388
357
** http://www.cn5135.com/ProductDetail-1069992.html
358
* Other eMMC: http://forum.gsmhosting.com/vbb/f672/direct-emmc-connection-failed-pinout-wrong-1807131/
359
360 5 Denis 'GNUtoo' Carikli
h2. Links
361 26 Denis 'GNUtoo' Carikli
362 8 Denis 'GNUtoo' Carikli
* "Official support for CyanogenMod":https://web.archive.org/web/20161225042527/https://wiki.cyanogenmod.org/w/I9100g_Info
363 9 Denis 'GNUtoo' Carikli
* "Unofficial LineageOS 13 for the I9100G":https://forum.xda-developers.com/galaxy-s2/development/rom-lineageos-13-0-t3620246
364 12 Denis 'GNUtoo' Carikli
** "Source code for it":https://github.com/xdaamg
365 11 Denis 'GNUtoo' Carikli
* Infos on the bootloader: https://forum.xda-developers.com/galaxy-s2/development/guide-repair-totally-sleep-dead-boot-t1701471
366 13 Denis 'GNUtoo' Carikli
* "Infos on xloader and how to make a serial port adapter":https://blog.the-leviathan.ch/?p=408
367 1 Denis 'GNUtoo' Carikli
* https://forum.xda-developers.com/showpost.php?p=65159962&postcount=276