Database Develop

[Q] Stuck in clockworkmod

i cant get passed clockword mod after i did a factory reset. i tried to restore decraped and the stock rom. it says restore complete then it loads the phone vibrate then the lg symbol shows up then it goes back to clockworkmod. i tried booting system in advanced restore and regular restore
---------- Post added at 05:25 AM ---------- Previous post was at 05:04 AM ----------
i just remembered that i also deleted all files on my internal memory before i tried to install the new rom. maybe that the problem, if it is, how do i get those files back on my internal memory?

try flashingent to stock rom

what are the steps for that process?

Download the stock root rom I'm development. Place it in external sd.clockworkwod.backup. go to backup and restore and select advamted restore and restore system from the stock rom
Sent from my VS910 4G using Tapatalk

i already did that, i was on revolt 1.3 then i went back to stock because im selling my phone, when i went back to stock, i wiped cache and erase data, went to advanced restore then i selected system, after that the phone said restore complete, but it boots up the lg symbol shows us and the phone goes back to clockworkmod. i also found a note in the clorkwork mod folder saying this, "Starting recovery on Thu Sep 22 04:38:02 2011
framebuffer: fd 4 (480 x 800)
ClockworkMod Recovery v4.0.0.2
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /boot emmc /dev/block/mmcblk0p9 (null)
2 /cache ext3 /dev/block/mmcblk0p6 (null)
3 /data ext3 /dev/block/mmcblk0p13 (null)
4 /recovery emmc /dev/block/mmcblk0p14 (null)
5 /sdcard vfat /dev/block/mmcblk1p1 (null)
6 /system ext3 /dev/block/mmcblk0p12 (null)
7 /sd-ext ext4 /dev/block/mmcblk1p2 (null)
8 /emmc vfat /dev/block/mmcblk0p15 (null)
I:Completed outputting fstab.
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
ro.build.id=GINGERBREAD
ro.build.display.id=full_revolution-eng 2.3.4 GINGERBREAD eng.root.20110613.235937 test-keys
ro.build.version.incremental=eng.root.20110613.235937
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.4
ro.build.date=Tue Jun 14 00:00:02 PDT 2011
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=root
ro.build.host=thinserver
ro.build.tags=test-keys
ro.product.model=Full Android on Emulator
ro.product.brand=Android
ro.product.name=full_revolution
ro.product.device=revolution
ro.product.board=revolution
ro.product.cpu.abi=armeabi
ro.product.manufacturer=unknown
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=unknown
ro.build.product=revolution
ro.build.description=full_revolution-eng 2.3.4 GINGERBREAD eng.root.20110613.235937 test-keys
ro.build.fingerprint=Android/full_revolution/revolution:2.3.4/GINGERBREAD/eng.root.20110613.235937:eng/test-keys
keyguard.no_require_sim=true
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=qcom
ro.revision=0
init.svc.recovery=running
init.svc.adbd=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
No files found.
No files found.
No files found.
No files found.
-- Installing: /sdcard/update.zip
Finding update package...
I:Update location: /sdcard/update.zip
Opening update package...
E:Can't open /sdcard/update.zip
(No such file or directory)
Installation aborted.

That last post is interesting. But to get out of clockwork you need to flash the exitrecovery.zip found in the stuck in clockwork thread in the dev section.
Sent from my VS910 4G using xda premium

hey, mtmichaelson can u give me the link please

http://forum.xda-developers.com/showthread.php?t=1161537

mtmichaelson said:
That last post is interesting. But to get out of clockwork you need to flash the exitrecovery.zip found in the stuck in clockwork thread in the dev section.
Sent from my VS910 4G using xda premium
Click to expand...
Click to collapse
thanks it worked
---------- Post added at 09:25 PM ---------- Previous post was at 09:24 PM ----------
thanks for the link
---------- Post added at 09:25 PM ---------- Previous post was at 09:25 PM ----------
deftonesmw said:
http://forum.xda-developers.com/showthread.php?t=1161537
Click to expand...
Click to collapse
thanks for the link

[Q] Cannot format /sdcard Error in CWM

I'm on stock I9000XXJVU_I9000OXAJVU_OXA + CF-Root-XX_OXA_JVU_2.3.6-v4.3-CWM3RFS
I was getting random reboots so I wanted to wipe everything out including internal sdcard, but I can't.
Formatting /sdcard...
E: format_volume failed to unmount "/sdcard"
Error formatting /sdcard!
Click to expand...
Click to collapse
Any idea? Log below:
Starting recovery on Sun Dec 23 11:07:42 2012
framebuffer: fd 4 (480 x 800)
ClockworkMod Recovery v3.0.0.5
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /sdcard vfat /dev/block/mmcblk0p1 (null)
2 /system rfs /dev/block/stl9 (null)
3 /cache rfs /dev/block/stl11 (null)
4 /data rfs /dev/block/mmcblk0p2 (null)
5 /datadata rfs /dev/block/stl10 (null)
6 /boot bml boot (null)
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Checking for ext4 partitions...
Checking /system...
Checking /data...
Checking /datadata...
Checking /cache...
Done!
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "recovery"
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=0
ro.factorytest=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=herring
ro.revision=48
ro.build.id=GINGERBREAD
ro.build.display.id=GINGERBREAD.XXJVU
ro.build.version.incremental=XXJVU
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.6
ro.build.date=Thu Dec 29 16:42:13 KST 2011
ro.build.date.utc=1325144533
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEI-22
ro.build.tags=release-keys
ro.product.model=GT-I9000
ro.product.brand=samsung
ro.product.name=GT-I9000
ro.product.device=GT-I9000
ro.product.board=GT-I9000
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=s5pc110
ro.build.product=GT-I9000
ro.build.description=GT-I9000-user 2.3.6 GINGERBREAD XXJVU release-keys
ro.build.fingerprint=samsung/GT-I9000/GT-I9000:2.3.6/GINGERBREAD/XXJVU:user/release-keys
ro.build.PDA=I9000XXJVU
ro.build.hidden_ver=I9000XXJVU
ro.build.changelist=851880
ro.flash.resolution=720
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/ttyS0
ro.sf.lcd_density=240
dalvik.vm.heapsize=64m
ro.opengles.version=131072
persist.service.usb.setting=0
ro.config.ringtone=01_Minimal_tone.ogg
ro.config.notification_sound=01_Sherbet.ogg
ro.config.alarm_alert=Good_Morning.ogg
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.locationfeatures=1
ro.setupwizard.mode=DISABLED
ro.com.google.gmsversion=2.3_r7
wifi.interface=eth0
wifi.supplicant_scan_interval=15
ro.secdevenc=true
ro.error.receiver.default=com.samsung.receiver.error
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=true
ro.ril.hsxpa=1
ro.ril.gprsclass=10
media.stagefright.enable-player=false
media.stagefright.enable-meta=false
media.stagefright.enable-scan=false
media.stagefright.enable-http=true
media.stagefright.enable-rtsp=false
dev.sfbootcomplete=0
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.com.google.clientidbase=android-samsung
init.svc.console=running
init.svc.recovery=running
init.svc.adbd=running
init.svc.setup_fs=stopped
init.svc.tvout=stopped
ro.radio.noril=yes
ro.bt.bdaddr_path=/efs/bluetooth/bt_addr
status.battery.state=Slow
status.battery.level=5
status.battery.level_raw=50
status.battery.level_scale=9
ro.telephony.call_ring.multiple=0
ro.nfc.port=I2C
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
-- Wiping data...
Formatting /data...
I:Formatting unknown device.
Formatting /cache...
I:Formatting unknown device.
Formatting /datadata...
I:Formatting unknown device.
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
I:Formatting unknown device.
rm: can't remove '.' or '..'
rm: can't remove '.' or '..'
Data wipe complete.
-- Wiping cache...
Formatting /cache...
I:Formatting unknown device.
Cache wipe complete.
Error unmounting /sdcard!
Formatting /sdcard...
E:format_volume failed to unmount "/sdcard"
Error formatting /sdcard!
Back menu button disabled.
E:unknown volume for path [/sd-ext]
rm: can't remove '/data/dalvik-cache': No such file or directory
rm: can't remove '/cache/dalvik-cache': No such file or directory
rm: can't remove '/sd-ext/dalvik-cache': No such file or directory
Dalvik Cache wiped.
Click to expand...
Click to collapse

d1rX said:
I'm on stock I9000XXJVU_I9000OXAJVU_OXA + CF-Root-XX_OXA_JVU_2.3.6-v4.3-CWM3RFS
I was getting random reboots so I wanted to wipe everything out including internal sdcard, but I can't.
Any idea? Log below:
Click to expand...
Click to collapse
Which recovery do you use?
You could format the SD card also if you mount the phone to the pc in recovery mode and Monat the SD card to the pc and format it from there
Hope i helped

Havent done it via PC. Wanted to make it work through CWM. Using 3.0.0.5. Wondering why its not working from the phone
Sent from my GT-I9100 using xda app-developers app

maybe you could update the recovery to a newer version and try again

Isn't 3.0.0.5 the latest for i9000? (2.3.6)

d1rX said:
Isn't 3.0.0.5 the latest for i9000? (2.3.6)
Click to expand...
Click to collapse
i don't know because for the galaxy s plus the newest one is 6.0.1.9
you can use an actual cwm recovery for all android versions
(not only for CM7 or CM9)
hope i helped

Installed Semaphore kernel + CWM 6. It worked just fine. Thanks

d1rX said:
Installed Semaphore kernel + CWM 6. It worked just fine. Thanks
Click to expand...
Click to collapse
Great to read that :good:

Unheard of Semi-Brick situation!!! HELP!

I was previously on Gingerbread 2.3 with CF-Root kernel. I flashed Ultimate XXLSC JB ROM v5.1 from here This ROM flashed fine from CWM as far as I know. It had a few issues since i forgot to wipe the data. I rebooted into recovery to do that. After which i lost root (im not sure if i had it before wiping the data though). The su binary was corrupted in some way (ES File explorer could not get its properties) and SuperSU said 'Installation failed'. I tried installing a simple rooting zip from CWM. This got stuck at 'Unmounting system' and did no effect to the su and busybox binaries. CWM was also causing problems. It refused to boot into system normally and could not unmount /system. I could not make a backup of this system since it would crash on backing up 'busybox'. I could not reflash the zip as it would not go further than the intial text logo. Here is the normal boot into recovery log:
Starting recovery on Sat Jan 26 17:22:13 2013
framebuffer: fd 4 (800 x 1280)
E:unknown volume for path [/system]
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc /dev/block/mmcblk0p5 (null) 0
2 /recovery emmc /dev/block/mmcblk0p6 (null) 0
3 /efs ext4 /dev/block/mmcblk0p1 (null) 0
4 /cache ext4 /dev/block/mmcblk0p7 (null) 0
5 /system ext4 /dev/block/mmcblk0p9 (null) 0
6 /data ext4 /dev/block/mmcblk0p10 (null) 0
7 /preload ext4 /dev/block/mmcblk0p12 (null) 0
8 /modem emmc /dev/block/mmcblk0p8 (null) 0
9 /emmc vfat /dev/block/mmcblk0p11 (null) 0
10 /sdcard vfat /dev/block/mmcblk1p1 (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
PhilZ Touch 3
CWM Base version: 6.0.1.9
Command: "recovery"
ro.sec_debug.enable=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.bootloader=unknown
ro.debug_level=unknown
ro.emmc_checksum=unknown
ril.dualmode.change=unknown
ro.hardware=smdk4210
ro.revision=8
ro.factorytest=0
ro.uart_debug=0
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=mtp
init.svc.ueventd=running
ro.crypto.keyfile.userdata=/efs/metadata
init.svc.recovery=running
adb.recovery=1
init.svc.adbd=running
service.adb.root=1
I:Checking for extendedcommand & OpenRecoveryScript...
I:Skipping execution of extendedcommand, file not found...
I:Skipping execution of OpenRecoveryScript, file not found...
IS THE RED PART THE ISSUE? HOW DO I FIX THIS? CAN I GO BACK TO A CWM BACKUP OF MY OLD GB SYSTEM SAFELY? The OS functions fine for now though.

You forgot to wipe when installing the JB CR. So the beginning gave you an unstable system.
And that's why you should install a fresh stock Rom with Odin.
After everything is working you might restore your GB backup (using a safe kernel like Philz 3.99).
I have to admit that I have difficulties to follow your steps.

Internal storage to external storage swap for cm11 (temporary workaround)

Hello friends..here i wanna share flashable zip to swap internal to external storage for cm11, works for me on tonyp cm11.
I'm not a dev..this is just edited script made by @Rox and @Souffre from xda cm11 thread,i just modify it a little for used in our device...
Flashable Zip on Attachment
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Att:
DWYOR, THIS SCRIPT IS NOT AS 4.4 STANDARD at least it works for me..
Sent from my LG-P990

Careful with that script, it's not totally conform to 4.4 standards.
Use it at your own risks.
Envoyé de mon GT-I8160 en utilisant Tapatalk

Souffre said:
Careful with that script, it's not totally conform to 4.4 standards.
Use it at your own risks.
Envoyé de mon GT-I8160 en utilisant Tapatalk
Click to expand...
Click to collapse
Yeah..that's why i tested myself...i hope better workaround to find..for now it's quite enough...everything works fine so far...
Sent from my LG-P990

your scripts is worked. i'm on cm11 20131226 tonyp. thx for the temp solution.

You're welcome..btw..if you wanna back into normal...you need to wipe all first...
Sent from my LG-P990

I have found an issue.
After I use this, All of not-English characters in file's name is showing '?'
For example, korean character '가' is showing '?' in file manager apps.
Sent from my LG-SU660 using xda app-developers app

mhkim4886 said:
I have found an issue.
After I use this, All of not-English characters in file's name is showing '?'
For example, korean character '가' is showing '?' in file manager apps.
Sent from my LG-SU660 using xda app-developers app
Click to expand...
Click to collapse
Hmmmmmmm..dunno about that...i'm using full character font for droidsansfallback...for general i'm not losing any character at all...
But you're using su660?are you sure the mount point is the same with p990?afaik a font character not related with sdcard...
Sent from my LG-P990

ivaneris said:
Hmmmmmmm..dunno about that...i'm using full character font for droidsansfallback...for general i'm not losing any character at all...
But you're using su660?are you sure the mount point is the same with p990?afaik a font character not related with sdcard...
Sent from my LG-P990
Click to expand...
Click to collapse
I'm using CM11 + LG Stock Font(which has full character fonts)
I'm using SU660 and probably same with p990's mountpoint.
I think that this issue is related with file system and characters encoding: because before I use this patch then non-English characters are OK.

mhkim4886 said:
I'm using CM11 + LG Stock Font(which has full character fonts)
I'm using SU660 and probably same with p990's mountpoint.
I think that this issue is related with file system and characters encoding: because before I use this patch then non-English characters are OK.
Click to expand...
Click to collapse
That's why it's strange..font should be unrelated to sdcard...unless there's a corupt in system partition...and cm11 stock font still noy full character..it's about ~3mb in size...full character is about ~9mb but still afaik stock droidsans still got korean character...why don't you try with restore your 'perfect settings' first...see if problem still exist...or...try to reflash rom and flash this patch (i'm using twrp and use batch flash install )
I'm still doubt it's related to swapping...unless it's corupt your system partition
Sent from my LG-P990

ivaneris said:
That's why it's strange..font should be unrelated to sdcard...unless there's a corupt in system partition...and cm11 stock font still noy full character..it's about ~3mb in size...full character is about ~9mb but still afaik stock droidsans still got korean character...why don't you try with restore your 'perfect settings' first...see if problem still exist...or...try to reflash rom and flash this patch (i'm using twrp and use batch flash install )
I'm still doubt it's related to swapping...unless it's corupt your system partition
Sent from my LG-P990
Click to expand...
Click to collapse
um, what did you mean 'perfect settings'?

mhkim4886 said:
um, what did you mean 'perfect settings'?
Click to expand...
Click to collapse
°º°=))Hªªhªªhªªhªª°°º...i mean your latest backup
Btw..still i'm not guarantee anything...
In worst case you'll need to clean install (i'm always restore my nandroid backup if anything bad happen thought..)
Sent from my LG-P990

ivaneris said:
°º°=))Hªªhªªhªªhªª°°º...i mean your latest backup
Btw..still i'm not guarantee anything...
In worst case you'll need to clean install (i'm always restore my nandroid backup if anything bad happen thought..)
Sent from my LG-P990
Click to expand...
Click to collapse
um.. I have installed patch after full wipe...
I just deleted your patch, then everything works fine.
I re-flashed your patch, the bug happened again.
The patch is the cause of this issue, I think.

mhkim4886 said:
um.. I have installed patch after full wipe...
I just deleted your patch, then everything works fine.
I re-flashed your patch, the bug happened again.
The patch is the cause of this issue, I think.
Click to expand...
Click to collapse
Strange...i have no prob it.....i can even read korean character...
Well just to make sure..check your mount point
Check in terminal
Mount | grep sdcard0
Mount | grep sdcard1
Sent from my LG-P990

ivaneris said:
Strange...i have no prob it.....i can even read korean character...
Well just to make sure..check your mount point
Check in terminal
Mount | grep sdcard0
Mount | grep sdcard1
Sent from my LG-P990
Click to expand...
Click to collapse
I checked:
Mount | grep sdcard0
Mount | grep sdcard1
then I can see the iocharset option setted isocharset=iso8859-1. I think this is the error: I'll try set it to utf8.
Add: I added option "iocharset=utf8" but this script not running: no switching (I think there is some error)

Let's see it again
Code:
#!/system/bin/sh
LOG=/data/extsd2.log
echo 'mark 1' > $LOG
umount /storage/sdcard0
umount /storage/sdcard1
umount /mnt/secure/asec
umount /mnt/media_rw/sdcard0
umount /mnt/media_rw/sdcard1
mount -t vfat -o umask=0000,uid=1000,gid=1015 /dev/block/vold/[COLOR="Red"]179:49[/COLOR] /mnt/media_rw/sdcard0 1>>$LOG 2>>$LOG
mount -t vfat -o umask=0000,uid=1000,gid=1015 /dev/block/vold/[COLOR="Red"]179:49[/COLOR] /storage/sdcard0 1>>$LOG 2>>$LOG
echo 'mark 2' >> $LOG
mount -t vfat -o umask=0000,uid=1000,gid=1015 /dev/block/vold/[COLOR="Purple"]179:11[/COLOR] /mnt/media_rw/sdcard1 1>>$LOG 2>>$LOG
mount -t vfat -o umask=0000,uid=1000,gid=1015 /dev/block/vold/[COLOR="Purple"]179:11[/COLOR] /storage/sdcard1 1>>$LOG 2>>$LOG
echo 'mark 3' >> $LOG
mount -t vfat -o umask=0000,uid=1000,gid=1015 /dev/block/vold/[COLOR="Red"]179:49[/COLOR] /mnt/secure/asec 1>>$LOG 2>>$LOG
How to get your own code number?
Like before..Just, run terminal emulator
tap this text
Su
mount | grep sdcard0
mount | grep sdcard1
See this number...dunno about su660 but afaik it had different partition layout:
179:49 = Number code for sdcard0 ,and
179:11 = Number code for sdcard1
And there is...p990 mount point red for sdcard 0 (wich actually external) and purple for sdcard1 (wich is actually internal)
Hope this'll help
Sent from my LG-P990

[email protected]:/ $ su
[email protected]:/ # mount | grep sdcard0
mount | grep sdcard0
/dev/block/vold/179:49 /mnt/media_rw/sdcard0 vfat rw,noatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
/dev/block/vold/179:49 /storage/sdcard0 vfat rw,noatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
[email protected]:/ # mount | grep sdcard1
mount | grep sdcard1
/dev/block/vold/179:11 /mnt/media_rw/sdcard1 vfat rw,noatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
/dev/block/vold/179:11 /storage/sdcard1 vfat rw,noatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
This is my result, no difference with p990. (After script run, so the result is switched) I think because I use p990-ICS partiton layout.
Sent from my LG-SU660 using xda app-developers app

mhkim4886 said:
[email protected]:/ $ su
[email protected]:/ # mount | grep sdcard0
mount | grep sdcard0
/dev/block/vold/179:49 /mnt/media_rw/sdcard0 vfat rw,noatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
/dev/block/vold/179:49 /storage/sdcard0 vfat rw,noatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
[email protected]:/ # mount | grep sdcard1
mount | grep sdcard1
/dev/block/vold/179:11 /mnt/media_rw/sdcard1 vfat rw,noatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
/dev/block/vold/179:11 /storage/sdcard1 vfat rw,noatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
This is my result, no difference with p990. (After script run, so the result is switched) I think because I use p990-ICS partiton layout.
Sent from my LG-SU660 using xda app-developers app
Click to expand...
Click to collapse
Yeah...it's the same...
Sent from my LG-P990

[ROM][I9100G][CM11.0] LineageOS 11.0 [UNOFFICIAL][Android 4.4.4][Patchlevel 07/2017]

I'm not allowed to post into Galaxy S II I9100G Android Development. So I have to use this forum which is definitely the wrong place.
I've forked the old CM-11 branch for the Galaxy I9100G, translated it to the LineageOS brand (like for the boot animation) and compiled it with LineageOS' Android 4.4.4 Sources including Patches from Google up until July 2017.
first rom image download:
http://ge.tt/8WKmALm2
newer build with a little newer kernel:
http://ge.tt/3WdCcOm2
(still waiting for AFH upload/dev membership, so I have to use some other one-click-hoster)
Feel free to fork the sources and compile yourself. I used the following guide / how-to, with the exception of "i9100g" instead of "manta" as the target for breakfast, brunch, etc.:
http://www.lineageosrom.com/2017/01/how-to-build-lineageos-rom-for-any.html
And of course I have modified the part for the i9100g, you can find my sources on github:
https://github.com/hede5562/android_device_samsung_i9100g/tree/cm-11.0
Clone them to ~/android/system/device/samsung/i9100g/ if you use the guide in question.
All other sources (including the kernel) are provided by the LineageOS repository (https://github.com/LineageOS) - they get automatically downloaded if you follow the guide.

OP's Github, CM11 tree: https://github.com/hede5562/android_device_samsung_i9100g/tree/cm-11.0

Correct, that's the right repository. Thanks. Hopefully my reputation will rise the next days so that I can link to binaries (image files), screenshots, etc. so others can test it.
BTW: I know this CM-11 image is quite useless if there are working CM-12 and CM-13 builds. At least CM-12 seams to be quite stable. (This one seems even more stable; I cannot reproduce known bugs on CM-12/13 like GPS, flashlight, network selection -> it's all working here.)
Nevertheless my main intention is to show: There are still patches to Android 4! If you are using Android 4 that doesn't implicitly mean you are vulnerable to known security issues. (Nothing new for most people here I think.)
And btw. maybe there are other use cases I don't think about right now ... I just wanted to play with the Android build system.

Hello, you can write useful messages and help users of the forum in other topics that you know.
You will help people, they will help you, you will have good grades and reputation.

der_hede said:
I'm not allowed to post into Galaxy S II I9100G Android Development. So I have to use this forum which is definitely the wrong place.
I've forked the old CM-11 branch for the Galaxy I9100G, translated it to the LineageOS brand (like for the boot animation) and compiled it with LineageOS' Android 4.4.4 Sources including Patches from Google up until July 2017.
Neither I'm allowed to attach files nor there seems to be some easy way to upload files to androidfilehost; it seems there's something needed which is only knowable with watching a video tutorial. I refuse to watch several minutes youtube video for something which is said in a simple twoliner... not my problem - I do have my image here.
If you wanna have this image, tell me how to upload it here or somewhere else or feel free to fork it and compile yourself:
Search for hede5562/android_device_samsung_i9100g on github - yes, I'm not allowed to link it here.
Screenshots: It seems I'm not even allowed to attach pictures...
Click to expand...
Click to collapse
The easiest way is if you sign up for AndroidFileHost and you request a file upload via ftp.

ze7zez said:
The easiest way is if you sign up for AndroidFileHost and you request a file upload via ftp.
Click to expand...
Click to collapse
I've requested developer status to upload files back then - seems to be the official way. Still no response yet.

Playing around with kernel patches...
I won't update to some newer kernel, but an increased sublevel is still possible.
The CyanogenMod/LineageOS kernel sources for t1 (I9100G) are based on Linux 3.0.31. There's 3.0.101 as the latest 3.0-version. The android_kernel_samsung_smdk4412 actually is 3.0.101, so why not also update android_kernel_samsung_t1 to 3.0.101?
Challenge accepted. First tests are promising. I patched 31->32->33->34 so far and most things work without much manual interaction.
And btw: It's September in a few hours but the patchlevel is still July... I think I have to investigate further into this.

der_hede said:
Challenge accepted. First tests are promising. I patched 31->32->33->34 so far and most things work without much manual interaction.
Click to expand...
Click to collapse
Nevermind. Others have already done that work. Like: https://github.com/aidfarh/android_kernel_samsung_t1

Well done and keep it up. I think this lineage 11.0 build is still useful for some people.
Especially because lineage 12.1 sources do not get android security patches any longer, which also runs well on i9100g. And newer versions have some problems with gps and sound.
edit: t1 kernel sources are old, with lot of security fixes missing. I noticed espressowifi/espresso3g have switched to a new kernel lately. It's a kernel for galaxy tab and nexus devices (omap4). It's well maintained, but i think no one wants to spent 'countless hours' to add i9100g support.
About android patch level: cm-11.0 branch often gets those patches between mid or end of month. August patches were added 27./28.08. but are still unmerged. But at least this branch gets updates.

adxamg said:
Well done and keep it up. I think this lineage 11.0 build is still useful for some people.
Especially because lineage 12.1 sources do not get android security patches any longer, which also runs well on i9100g. And newer versions have some problems with gps and sound.
Click to expand...
Click to collapse
That's one good reason. For me it's just fun and to show: Even Android 4 is no sufficient criterion for having an unsecure phone.
Btw... with unpatched kernels this is still the case so:
edit: t1 kernel sources are old, with lot of security fixes missing. I noticed espressowifi/espresso3g have switched to a new kernel lately. It's a kernel for galaxy tab and nexus devices (omap4). It's well maintained, but i think no one wants to spent 'countless hours' to add i9100g support.
Click to expand...
Click to collapse
Thanks for this hint. Kernel 3.4 would be absolutely fine. It's still an official kernel.org longterm branch. I will try to find out how much work has to be done to use this one / parts from both / whatever...
I'm not new to embedded Linux, but I'm new to Androids kernel space, so I don't know if it's possible at all. If there's any non-SoC hardware with only closed source drivers/modules for linux 3.0.x then we're stuck on 3.0.
AFAIK omap4 doesn't include the gsm stack for example.
About android patch level: cm-11.0 branch often gets those patches between mid or end of month. August patches were added 27./28.08. but are still unmerged. But at least this branch gets updates.
Click to expand...
Click to collapse
I thins you have to live with some drawbacks using such an old branch...
What does "unmerged" mean? Is there an easy way to get those unmerged patches for including them in my build?

Check https://review.lineageos.org/#/q/branch:cm-11.0+topic:asb-2017.08-cm-11.0. When it gets approved, status will change to merged and your sources will be updated when you next time do a 'repo sync'. Just wait, it should be merged within some days. If not, maybe it's not complete yet or not working.
You could manually apply those changes and/or 'cherry pick' those changes.
About kernel for omap4 devices check also https://github.com/Unlegacy-Android
Devs are using it for aosp builds (different omap4 devices, but not i9100g). There are 3.0 and 3.4 kernels. For example: https://github.com/Unlegacy-Android/android_kernel_ti_omap4

Hi!
From user point of view I experienced some trouble with this ROM. To get "contact" to the Google Play Store I installed the GApps from
Code:
opengapps.org
version arm 4.4 nano. But after successfull installation using recovery mode I get no connection to the Google server, if I send my account loggin. I checked host file, activated Download manager and did a second flash of GApps. No success. Next I wanted to flash all new. But now I can't flash the rom a second time.
recovery log sequence:
Code:
-- Installing: /storage/sdcard1/lineage-11-20170830-UNOFFICIAL-i9100g.zip
Finding update package...
I:Update location: /storage/sdcard1/lineage-11-20170830-UNOFFICIAL-i9100g.zip
Opening update package...
minzip: Missed a local header sig (at 13)
E:Can't open /storage/sdcard1/lineage-11-20170830-UNOFFICIAL-i9100g.zip
(bad)
Installation aborted.
I:Cannot load volume /misc.
I:Can't partition non-vfat: /storage/sdcard0 (vfat)
I:Can't partition non mmcblk device: /devices/platform/omap/omap_hsmmc.0/mmc_host/mmc1
Any ideas what's wrong?
Regards, Bodo
recovery log full (without external links which are not allowed for Newbies)
Code:
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Starting recovery on Sat Jan 1 00:00:02 2000
framebuffer: fd 4 (480 x 800)
CWM-based Recovery v6.0.5.1
recovery filesystem table
=========================
0 /system ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/FACTORYFS 0
1 /cache ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/CACHE 0
2 /efs ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/EFS 0
3 /preload ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/HIDDEN 0
4 /data ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/DATAFS 0
5 /storage/sdcard0 vfat /devices/platform/omap/omap_hsmmc.1/mmc_host/mmc0 0
6 /storage/sdcard1 auto /devices/platform/omap/omap_hsmmc.0/mmc_host/mmc1 0
7 /storage/usbdisk0 auto /devices/platform/omap/musb-omap2430/musb-hdrc/usb1 0
8 /boot emmc /dev/block/mmcblk0p5 0
9 /recovery emmc /dev/block/mmcblk0p6 0
10 /tmp ramdisk ramdisk 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sdcard during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
W:Unable to get recovery.fstab info for /external_sd during fstab generation!
I:Completed outputting fstab.
I:Connected to Vold..
I:110 0 sdcard0 /storage/sdcard0 1 -
I:110 0 sdcard1 /storage/sdcard1 1 -
I:110 0 usbdisk0 /storage/usbdisk0 0 -
I:200 0 Volumes listed.
I:Processing arguments.
I:Cannot load volume /misc.
I:Cannot load volume /misc.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.bq.gpu_to_cpu_unsupported=1
ro.cm.device=i9100g
ro.cm.display.version=11-20170825-UNOFFICIAL-i9100g
ro.cm.version=11-20170825-UNOFFICIAL-i9100g
ro.cm.releasetype=UNOFFICIAL
ro.sf.lcd_density=240
ro.com.google.clientidbase=android-google
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.com.android.wifi-watchlist=GoogleGuest
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.url.legal=
ro.url.legal.android_privacy=
ro.boot.emmc=0
ro.boot.mode=reboot_recovery
ro.boot.hardware=t1
ro.boot.serialno=xxxxxxxxxxx
ro.boot.debug_level=0x4f4c
ro.boot.emmc_checksum=3
ro.emmc=0
ro.hwui.disable_scissor_opt=true
ro.wifi.channels=
ro.allow.mock.location=0
ro.board.platform=omap4
ro.build.id=KTU84Q
ro.build.date=Fri Aug 25 08:31:01 UTC 2017
ro.build.date.utc=0
ro.build.host=android
ro.build.tags=test-keys
ro.build.type=userdebug
ro.build.user=michael
ro.build.display.id=lineage_i9100g-userdebug 4.4.4 KTU84Q 080c67fecb test-keys
ro.build.product=GT-I9100G
ro.build.selinux=1
ro.build.version.sdk=19
ro.build.version.base_os=
ro.build.version.release=4.4.4
ro.build.version.codename=REL
ro.build.version.incremental=080c67fecb
ro.build.version.security_patch=2017-07-01
ro.build.description=GT-I9100G-user 4.1.2 JZO54K I9100GXXLSR release-keys
ro.build.fingerprint=samsung/GT-I9100G/GT-I9100G:4.1.2/JZO54K/I9100GXXLSR:user/release-keys
ro.build.characteristics=default
ro.config.ringtone=Orion.ogg
ro.config.alarm_alert=Hassium.ogg
ro.config.notification_sound=Argon.ogg
ro.secure=1
ro.carrier=unknown
ro.cmlegal.url=lineageos.org/legal
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.name=GT-I9100G
ro.product.board=t1
ro.product.brand=samsung
ro.product.model=GT-I9100G
ro.product.device=GT-I9100G
ro.product.locale.region=US
ro.product.locale.language=en
ro.product.manufacturer=samsung
ro.baseband=unknown
ro.bootmode=reboot_recovery
ro.hardware=t1
ro.opengles.version=131072
ro.revision=7
ro.serialno=xxxxxxxxxx
ro.telephony.call_ring.delay=3000
ro.telephony.call_ring.multiple=false
ro.telephony.ril_class=SamsungExynos4RIL
ro.bootloader=unknown
ro.debuggable=1
ro.modversion=11-20170825-UNOFFICIAL-i9100g
ro.rommanager.developerid=cyanogenmod
ro.factorytest=0
ro.setupwizard.enterprise_mode=1
com.ti.omap_enhancement=true
net.bt.name=Android
net.change=net.bt.name
init.svc.adbd=running
init.svc.vold=running
init.svc.healthd=running
init.svc.ueventd=running
init.svc.recovery=running
init.svc.setup_adbd=stopped
omap.enhancement=true
rild.libargs=-d /dev/ttyS0
rild.libpath=/system/lib/libsec-ril.so
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
dalvik.vm.heapsize=128m
dalvik.vm.lockprof.threshold=500
dalvik.vm.heapmaxfree=2m
dalvik.vm.heapminfree=512k
dalvik.vm.dexopt-flags=m=y
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.stack-trace-file=/data/anr/traces.txt
dalvik.vm.heaptargetutilization=0.25
persist.sys.dun.override=0
persist.sys.usb.config=mtp,adb
persist.sys.dalvik.vm.lib=libdvm.so
persist.sys.dalvik.multithread=false
persist.sys.root_access=1
persist.sys.recovery_update=false
service.adb.root=1
keyguard.no_require_sim=true
mobiledata.interfaces=pdp0,wlan0,gprs,ppp0
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
I:Cannot load volume /misc.
I:605 Volume sdcard0 /storage/sdcard0 state changed from 1 (Idle-Unmounted) to 3 (Checking)
I:/storage/sdcard0: Checking
I:613 sdcard0 /storage/sdcard0
I:614 sdcard0 /storage/sdcard0
I:605 Volume sdcard0 /storage/sdcard0 state changed from 3 (Checking) to 4 (Mounted)
I:/storage/sdcard0: Mounted
I:200 0 volume operation succeeded
-- Wiping data...
Formatting /data...
Creating filesystem with parameters:
Size: 2147483648
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 8192
Label:
Blocks: 524288
Block groups: 16
Reserved block group size: 127
Created filesystem with 11/131072 inodes and 17193/524288 blocks
Formatting /cache...
Creating filesystem with parameters:
Size: 104857600
Block size: 4096
Blocks per group: 32768
Inodes per group: 6400
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 25600
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/6400 inodes and 1438/25600 blocks
Formatting /sd-ext...
E:unknown volume for path [/sd-ext]
Formatting /storage/sdcard0/.android_secure...
I:605 Volume sdcard0 /storage/sdcard0 state changed from 4 (Mounted) to 5 (Unmounting)
I:613 sdcard0 /storage/sdcard0
I:614 sdcard0 /storage/sdcard0
I:605 Volume sdcard0 /storage/sdcard0 state changed from 5 (Unmounting) to 1 (Idle-Unmounted)
I:/storage/sdcard0: Idle-Unmounted
I:200 0 volume operation succeeded
I:Formatting unknown device.
I:605 Volume sdcard0 /storage/sdcard0 state changed from 1 (Idle-Unmounted) to 3 (Checking)
I:/storage/sdcard0: Checking
I:613 sdcard0 /storage/sdcard0
I:614 sdcard0 /storage/sdcard0
I:605 Volume sdcard0 /storage/sdcard0 state changed from 3 (Checking) to 4 (Mounted)
I:/storage/sdcard0: Mounted
I:200 0 volume operation succeeded
rm: can't remove '.' or '..'
rm: can't remove '.' or '..'
I:605 Volume sdcard0 /storage/sdcard0 state changed from 4 (Mounted) to 5 (Unmounting)
I:613 sdcard0 /storage/sdcard0
I:614 sdcard0 /storage/sdcard0
I:605 Volume sdcard0 /storage/sdcard0 state changed from 5 (Unmounting) to 1 (Idle-Unmounted)
I:/storage/sdcard0: Idle-Unmounted
I:200 0 volume operation succeeded
Data wipe complete.
I:Cannot load volume /misc.
I:605 Volume sdcard0 /storage/sdcard0 state changed from 1 (Idle-Unmounted) to 3 (Checking)
I:/storage/sdcard0: Checking
I:613 sdcard0 /storage/sdcard0
I:614 sdcard0 /storage/sdcard0
I:605 Volume sdcard0 /storage/sdcard0 state changed from 3 (Checking) to 4 (Mounted)
I:/storage/sdcard0: Mounted
I:200 0 volume operation succeeded
-- Wiping cache...
Formatting /cache...
Creating filesystem with parameters:
Size: 104857600
Block size: 4096
Blocks per group: 32768
Inodes per group: 6400
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 25600
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/6400 inodes and 1438/25600 blocks
Cache wipe complete.
I:Cannot load volume /misc.
I:Can't partition non-vfat: /storage/sdcard0 (vfat)
I:Can't partition non mmcblk device: /devices/platform/omap/omap_hsmmc.0/mmc_host/mmc1
rm: can't remove '/data/dalvik-cache': No such file or directory
rm: can't remove '/cache/dalvik-cache': No such file or directory
rm: can't remove '/sd-ext/dalvik-cache': No such file or directory
Dalvik Cache wiped.
I:Cannot load volume /misc.
I:605 Volume sdcard1 /storage/sdcard1 state changed from 1 (Idle-Unmounted) to 3 (Checking)
I:/storage/sdcard1: Checking
I:613 sdcard1 /storage/sdcard1
I:614 sdcard1 /storage/sdcard1
I:605 Volume sdcard1 /storage/sdcard1 state changed from 3 (Checking) to 4 (Mounted)
I:/storage/sdcard1: Mounted
I:200 0 volume operation succeeded
-- Installing: /storage/sdcard1/lineage-11-20170830-UNOFFICIAL-i9100g.zip
Finding update package...
I:Update location: /storage/sdcard1/lineage-11-20170830-UNOFFICIAL-i9100g.zip
Opening update package...
minzip: Missed a local header sig (at 13)
E:Can't open /storage/sdcard1/lineage-11-20170830-UNOFFICIAL-i9100g.zip
(bad)
Installation aborted.
I:Cannot load volume /misc.
I:Can't partition non-vfat: /storage/sdcard0 (vfat)
I:Can't partition non mmcblk device: /devices/platform/omap/omap_hsmmc.0/mmc_host/mmc1

@der_hede greetings brother, thanks or your efforts! Rom is working perfectly and the battery life is great.

Sorry, I haven't done anything in the last weeks and won't find time to continue my work before October.
I haven't tried Gapps so far. Will do that next time.

der_hede said:
Sorry, I haven't done anything in the last weeks and won't find time to continue my work before October.
I haven't tried Gapps so far. Will do that next time.
Click to expand...
Click to collapse
Thanks again, for doing ANYThing with this phone!
I have noticed that the backlight for the capacative keys lights up instead of the notification light. Is this happening for you also?
Gapps is working fine for me, ARM 4.4 Pico
Many blessings.

der_hede said:
Sorry, I haven't done anything in the last weeks and won't find time to continue my work before October.
I haven't tried Gapps so far. Will do that next time.
Click to expand...
Click to collapse
I just installed lineage-11-20170830-UNOFFICIAL-i9100g and I must say it works flawlessly.
Thanks for all the effort you put into this. Vielen Dank!
For the record, I used the following gapps, downloaded from here: http://opengapps.org/
open_gapps-arm-4.4-mini-20170930.zip

der_hede said:
Sorry, I haven't done anything in the last weeks and won't find time to continue my work before October.
I haven't tried Gapps so far. Will do that next time.
Click to expand...
Click to collapse
BROTHER why it gets stuck at bootloop when advanced restarted?
---------- Post added at 09:41 PM ---------- Previous post was at 09:38 PM ----------
Franz.Xaver said:
I just installed lineage-11-20170830-UNOFFICIAL-i9100g and I must say it works flawlessly.
Thanks for all the effort you put into this. Vielen Dank!
For the record, I used the following gapps, downloaded from here: http://opengapps.org/
open_gapps-arm-4.4-mini-20170930.zip
Click to expand...
Click to collapse
yeah exactly everything is flawless except for Advanced restart. whenever put into recovery using advanced restart it gets stuck at bootloop, do you know how to fix this problem?

@der_hede
usb OTG and Hotspot not working. still testing other function

for xposed
https://androidfilehost.com/?fid=24421527759884030
for gapps
https://androidfilehost.com/?fid=95916177934546917

I am now getting constant "Google Play Store has stopped" errors. Anyone else have this? @der_hede Sorry to ask, but are you still working on this?