Related
Hello xda, we are looking for a DEV because we are having trouble porting CWM on the new LG Optimus Elite and us Optimus Elite user's would GREATLY appreciate if someone could help us! We currently have root. The LG Optimus Elite forum is located at this link: http://androidforums.com/lg-optimus-elite/ Thanks!!
Android311 said:
Hello xda, we are looking for a DEV because we are having trouble porting CWM on the new LG Optimus Elite and us Optimus Elite user's would GREATLY appreciate if someone could help us! We currently have root. The LG Optimus Elite forum is located at this link: http://androidforums.com/lg-optimus-elite/ Thanks!!
Click to expand...
Click to collapse
+1
We need it bad if we there is any chance of getting custom roms. I would donate to the cause. Our user base at the phandroid forums are banging their heads atm trying to get it done. Any and all help is greatly appreciated. Thank you.
Yes I'm willing to donate and im sure user's here and over at androidforums are willing to donate as well! Help is Appreciated
I too would donate to get us a custom recovery.
Dat Bump! we need recovery bad!
+1
+1
This phone is a decent cheap phone.
+1 I really like this phone.
Is it just the CWM recovery that you're asking for? Need to know the partition information of your device.. (is there separate partition available for recovery or it uses the boot partition itself)
superatmos said:
Is it just the CWM recovery that you're asking for? Need to know the partition information of your device.. (is there separate partition available for recovery or it uses the boot partition itself)
Click to expand...
Click to collapse
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>cd C:\android-sdk-windows\platform-tools\
C:\android-sdk-windows\platform-tools>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
$ su
su
# cat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 3864576 mmcblk0
179 1 2048 mmcblk0p1
179 2 2048 mmcblk0p2
179 3 7168 mmcblk0p3
179 4 1 mmcblk0p4
179 5 16384 mmcblk0p5
179 6 237568 mmcblk0p6
179 7 4096 mmcblk0p7
179 8 24576 mmcblk0p8
179 9 8192 mmcblk0p9
179 10 4096 mmcblk0p10
179 11 4096 mmcblk0p11
179 12 368640 mmcblk0p12
179 13 925696 mmcblk0p13
179 14 8192 mmcblk0p14
179 15 2023424 mmcblk0p15
179 16 28672 mmcblk0p16
179 17 4096 mmcblk0p17
179 18 8192 mmcblk0p18
179 19 28672 mmcblk0p19
179 20 8192 mmcblk0p20
179 21 16384 mmcblk0p21
# cat /proc/mounts
cat /proc/mounts
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/extasec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/extobb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p12 /system ext4 rw,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p13 /data ext4 rw,nosuid,nodev,relatime,resuid=1000,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p6 /cache ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p5 /persist ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p21 /mpt ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/vold/179:15 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:15 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
# cat /proc/emmc
cat /proc/emmc
/proc/emmc: No such file or directory
# cat /proc/mtd
cat /proc/mtd
dev: size erasesize name
# exit
exit
$ exit
exit
C:\android-sdk-windows\platform-tools>adb shell
$ su
su
# cat /cache/recovery/last_log
cat /cache/recovery/last_log
Starting recovery on Fri Jan 11 04:38:09 1980
framebuffer: fd 4 (320 x 480)
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /cache ext4 /dev/block/mmcblk0p6 (null)
2 /misc emmc /dev/block/mmcblk0 (null)
3 /boot emmc /dev/block/mmcblk0p9 (null)
4 /system ext4 /dev/block/mmcblk0p12 (null)
5 /data ext4 /dev/block/mmcblk0p13 (null)
6 /recovery emmc /dev/block/mmcblk0p14 (null)
7 /sdcard vfat /dev/block/mmcblk0p15 /dev/block/mmcblk0
8 /sdcard/_ExternalSD vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
Command: "/sbin/recovery"
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=1
ro.build.id=ZV4.GWK74
ro.build.display.id=ZV4.GWK74
ro.build.version.lge=VM696ZV4
ro.build.version.incremental=47C45DFC
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.7
ro.build.date=Thu Apr 5 14:53:48 KST 2012
ro.build.date.utc=1333605228
ro.build.type=user
ro.build.user=VM696
ro.build.host=builder1.nuribom.com
ro.build.tags=release-keys
ro.product.model=LG-VM696
ro.product.brand=lge
ro.product.name=m3s_virgin_us
ro.product.device=m3s
ro.modem.version=
ro.brand.name=LG Optimus Elite
ro.product.board=lge_m3s
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=LGE
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm7k
ro.build.product=m3s
ro.build.description=m3s_virgin_us-user 2.3.7 ZV4.GWK74 47C45DFC release-keys
ro.build.fingerprint=lge/m3s_virgin_us/m3s:2.3.7/ZV4.GWK74/47C45DFC:user/release-keys
rild.libpath=/system/lib/libril-qc-qmi-1.so
rild.libargs=-d /dev/smd0
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
ril.subscription.types=NV,RUIM
DEVICE_PROVISIONED=1
debug.sf.hw=1
dalvik.vm.heapsize=32m
dev.pm.dyn_samplingrate=1
persist.cne.UseCne=false
persist.cne.bat.range.low.med=30
persist.cne.bat.range.med.high=60
persist.cne.loc.policy.op=/system/etc/OperatorPolicy.xml
persist.cne.loc.policy.user=/system/etc/UserPolicy.xml
persist.cne.bwbased.rat.sel=false
persist.cne.snsr.based.rat.mgt=false
persist.cne.bat.based.rat.mgt=false
persist.cne.rat.acq.time.out=30000
persist.cne.rat.acq.retry.tout=0
lpa.decode=true
ro.use_data_netmgrd=true
ro.emmc.sdcard.partition=16
ro.config.ehrpd=true
media.stagefright.enable-player=true
media.stagefright.enable-meta=false
media.stagefright.enable-scan=false
media.stagefright.enable-http=true
ro.opengles.version=131072
ro.qualcomm.bluetooth.dun=false
ro.bluetooth.remote.autoconnect=true
ro.cdma.home.operator.alpha=Virgin Mobile
ro.cdma.home.operator.numeric=311490
gsm.sim.operator.alpha=Virgin Mobile
gsm.sim.operator.numeric=311490
gsm.sim.operator.iso-country=us
gsm.operator.alpha=Virgin Mobile
gsm.operator.numeric=311490
gsm.operator.iso-country=us
gsm.sim.state=READY
persist.service.usbport.enable=1
ro.multi.rild=true
ro.qualcomm.bluetooth.ftp=true
debug.bt.discoverable_time=120
ro.bluetooth.request.master=false
ro.setupwizard.mode=DISABLED
ro.com.google.gmsversion=2.3_r9
ro.config.notification_sound=Pebble.ogg
ro.config.alarm_alert=Alarm1.ogg
ro.com.google.clientidbase=android-lge
ro.com.google.clientidbase.yt=android-virgin-us
ro.com.google.clientidbase.am=android-virgin-us
ro.com.google.clientidbase.gmm=android-lge
ro.com.google.clientidbase.ms=android-virgin-us
ro.config.ringtone=Beyond_the_Dream.ogg
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=3122137e
ro.bootmode=unknown
ro.baseband=msm
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=qcom
ro.revision=0
ro.emmc=1
persist.radio.adb_log_on=0
persist.radio.mem_leak_debug=0
persist.radio.voip_enabled=0
persist.sys.language=en
persist.sys.country=US
persist.sys.localevar=
persist.sys.timezone=America/Chicago
persist.sys.sound_enable=2
init.svc.recovery=running
init.svc.adbd=running
Check sdcard for GOTA update : /sdcard/update.zip
Finding update package in sdcard...
I:Update location: /sdcard/update.zip
I:Update file path: /sdcard/update.zip
no image found in sdcard
E:failed to open /sdcard/update.zip (No such file or directory)
# exit
exit
$ exit
exit
Here is a fresh pull of the boot, system and recovery partitions as img files using dd commands:
Download req-files-for-custom-recovery-build-20120716.zip from Sendspace.com - send big files the easy way
Also, here are img files I pulled earlier for somebody else who tried to build CWM. These were pulled using cat commands and have been renamed to boot.img, system.img and recovery.img This zip also contains ADB output, build.prop, and last_log info:
Download Req-files-for-CWM-build.zip from Sendspace.com - send big files the easy way
Thank you very much for the help.
k_t_b said:
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>cd C:\android-sdk-windows\platform-tools\
C:\android-sdk-windows\platform-tools>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
$ su
su
# cat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 3864576 mmcblk0
179 1 2048 mmcblk0p1
179 2 2048 mmcblk0p2
179 3 7168 mmcblk0p3
179 4 1 mmcblk0p4
179 5 16384 mmcblk0p5
179 6 237568 mmcblk0p6
179 7 4096 mmcblk0p7
179 8 24576 mmcblk0p8
179 9 8192 mmcblk0p9
179 10 4096 mmcblk0p10
179 11 4096 mmcblk0p11
179 12 368640 mmcblk0p12
179 13 925696 mmcblk0p13
179 14 8192 mmcblk0p14
179 15 2023424 mmcblk0p15
179 16 28672 mmcblk0p16
179 17 4096 mmcblk0p17
179 18 8192 mmcblk0p18
179 19 28672 mmcblk0p19
179 20 8192 mmcblk0p20
179 21 16384 mmcblk0p21
# cat /proc/mounts
cat /proc/mounts
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/extasec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/extobb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p12 /system ext4 rw,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p13 /data ext4 rw,nosuid,nodev,relatime,resuid=1000,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p6 /cache ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p5 /persist ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p21 /mpt ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/vold/179:15 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:15 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
# cat /proc/emmc
cat /proc/emmc
/proc/emmc: No such file or directory
# cat /proc/mtd
cat /proc/mtd
dev: size erasesize name
# exit
exit
$ exit
exit
C:\android-sdk-windows\platform-tools>adb shell
$ su
su
# cat /cache/recovery/last_log
cat /cache/recovery/last_log
Starting recovery on Fri Jan 11 04:38:09 1980
framebuffer: fd 4 (320 x 480)
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /cache ext4 /dev/block/mmcblk0p6 (null)
2 /misc emmc /dev/block/mmcblk0 (null)
3 /boot emmc /dev/block/mmcblk0p9 (null)
4 /system ext4 /dev/block/mmcblk0p12 (null)
5 /data ext4 /dev/block/mmcblk0p13 (null)
6 /recovery emmc /dev/block/mmcblk0p14 (null)
7 /sdcard vfat /dev/block/mmcblk0p15 /dev/block/mmcblk0
8 /sdcard/_ExternalSD vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
Command: "/sbin/recovery"
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=1
ro.build.id=ZV4.GWK74
ro.build.display.id=ZV4.GWK74
ro.build.version.lge=VM696ZV4
ro.build.version.incremental=47C45DFC
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.7
ro.build.date=Thu Apr 5 14:53:48 KST 2012
ro.build.date.utc=1333605228
ro.build.type=user
ro.build.user=VM696
ro.build.host=builder1.nuribom.com
ro.build.tags=release-keys
ro.product.model=LG-VM696
ro.product.brand=lge
ro.product.name=m3s_virgin_us
ro.product.device=m3s
ro.modem.version=
ro.brand.name=LG Optimus Elite
ro.product.board=lge_m3s
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=LGE
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm7k
ro.build.product=m3s
ro.build.description=m3s_virgin_us-user 2.3.7 ZV4.GWK74 47C45DFC release-keys
ro.build.fingerprint=lge/m3s_virgin_us/m3s:2.3.7/ZV4.GWK74/47C45DFC:user/release-keys
rild.libpath=/system/lib/libril-qc-qmi-1.so
rild.libargs=-d /dev/smd0
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
ril.subscription.types=NV,RUIM
DEVICE_PROVISIONED=1
debug.sf.hw=1
dalvik.vm.heapsize=32m
dev.pm.dyn_samplingrate=1
persist.cne.UseCne=false
persist.cne.bat.range.low.med=30
persist.cne.bat.range.med.high=60
persist.cne.loc.policy.op=/system/etc/OperatorPolicy.xml
persist.cne.loc.policy.user=/system/etc/UserPolicy.xml
persist.cne.bwbased.rat.sel=false
persist.cne.snsr.based.rat.mgt=false
persist.cne.bat.based.rat.mgt=false
persist.cne.rat.acq.time.out=30000
persist.cne.rat.acq.retry.tout=0
lpa.decode=true
ro.use_data_netmgrd=true
ro.emmc.sdcard.partition=16
ro.config.ehrpd=true
media.stagefright.enable-player=true
media.stagefright.enable-meta=false
media.stagefright.enable-scan=false
media.stagefright.enable-http=true
ro.opengles.version=131072
ro.qualcomm.bluetooth.dun=false
ro.bluetooth.remote.autoconnect=true
ro.cdma.home.operator.alpha=Virgin Mobile
ro.cdma.home.operator.numeric=311490
gsm.sim.operator.alpha=Virgin Mobile
gsm.sim.operator.numeric=311490
gsm.sim.operator.iso-country=us
gsm.operator.alpha=Virgin Mobile
gsm.operator.numeric=311490
gsm.operator.iso-country=us
gsm.sim.state=READY
persist.service.usbport.enable=1
ro.multi.rild=true
ro.qualcomm.bluetooth.ftp=true
debug.bt.discoverable_time=120
ro.bluetooth.request.master=false
ro.setupwizard.mode=DISABLED
ro.com.google.gmsversion=2.3_r9
ro.config.notification_sound=Pebble.ogg
ro.config.alarm_alert=Alarm1.ogg
ro.com.google.clientidbase=android-lge
ro.com.google.clientidbase.yt=android-virgin-us
ro.com.google.clientidbase.am=android-virgin-us
ro.com.google.clientidbase.gmm=android-lge
ro.com.google.clientidbase.ms=android-virgin-us
ro.config.ringtone=Beyond_the_Dream.ogg
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=3122137e
ro.bootmode=unknown
ro.baseband=msm
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=qcom
ro.revision=0
ro.emmc=1
persist.radio.adb_log_on=0
persist.radio.mem_leak_debug=0
persist.radio.voip_enabled=0
persist.sys.language=en
persist.sys.country=US
persist.sys.localevar=
persist.sys.timezone=America/Chicago
persist.sys.sound_enable=2
init.svc.recovery=running
init.svc.adbd=running
Check sdcard for GOTA update : /sdcard/update.zip
Finding update package in sdcard...
I:Update location: /sdcard/update.zip
I:Update file path: /sdcard/update.zip
no image found in sdcard
E:failed to open /sdcard/update.zip (No such file or directory)
# exit
exit
$ exit
exit
Here is a fresh pull of the boot, system and recovery partitions as img files using dd commands:
Download req-files-for-custom-recovery-build-20120716.zip from Sendspace.com - send big files the easy way
Also, here are img files I pulled earlier for somebody else who tried to build CWM. These were pulled using cat commands and have been renamed to boot.img, system.img and recovery.img This zip also contains ADB output, build.prop, and last_log info:
Download Req-files-for-CWM-build.zip from Sendspace.com - send big files the easy way
Thank you very much for the help.
Click to expand...
Click to collapse
Ok. You gave good amount of details.
Anyway, there looks like two separate partitions for boot as well as recovery but sometimes recovery partition might not be used at all.
I will try to make a recovery.img file and provide it here. You can use dd command to push it to recovery partition.
# cat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 3864576 mmcblk0
179 1 2048 mmcblk0p1
179 2 2048 mmcblk0p2
179 3 7168 mmcblk0p3
179 4 1 mmcblk0p4
179 5 16384 mmcblk0p5
179 6 237568 mmcblk0p6
179 7 4096 mmcblk0p7
179 8 24576 mmcblk0p8
179 9 8192 mmcblk0p9
179 10 4096 mmcblk0p10
179 11 4096 mmcblk0p11
179 12 368640 mmcblk0p12
179 13 925696 mmcblk0p13
179 14 8192 mmcblk0p14
179 15 2023424 mmcblk0p15
179 16 28672 mmcblk0p16
179 17 4096 mmcblk0p17
179 18 8192 mmcblk0p18
179 19 28672 mmcblk0p19
179 20 8192 mmcblk0p20
179 21 16384 mmcblk0p21
# cat /proc/mounts
cat /proc/mounts
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/extasec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/extobb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p12 /system ext4 rw,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p13 /data ext4 rw,nosuid,nodev,relatime,resuid=1000,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p6 /cache ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p5 /persist ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p21 /mpt ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/vold/179:15 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:15 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
# cat /proc/emmc
cat /proc/emmc
/proc/emmc: No such file or directory
# cat /proc/mtd
cat /proc/mtd
dev: size erasesize name
# exit
exit
$ exit
exit
C:\android-sdk-windows\platform-tools>adb shell
$ su
su
# cat /cache/recovery/last_log
cat /cache/recovery/last_log
Starting recovery on Fri Jan 11 04:38:09 1980
framebuffer: fd 4 (320 x 480)
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /cache ext4 /dev/block/mmcblk0p6 (null)
2 /misc emmc /dev/block/mmcblk0 (null)
3 /boot emmc /dev/block/mmcblk0p9 (null)
4 /system ext4 /dev/block/mmcblk0p12 (null)
5 /data ext4 /dev/block/mmcblk0p13 (null)
6 /recovery emmc /dev/block/mmcblk0p14 (null)
7 /sdcard vfat /dev/block/mmcblk0p15 /dev/block/mmcblk0
8 /sdcard/_ExternalSD vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
Command: "/sbin/recovery"
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=1
ro.build.id=ZV4.GWK74
ro.build.display.id=ZV4.GWK74
ro.build.version.lge=VM696ZV4
ro.build.version.incremental=47C45DFC
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.7
ro.build.date=Thu Apr 5 14:53:48 KST 2012
ro.build.date.utc=1333605228
ro.build.type=user
ro.build.user=VM696
ro.build.host=builder1.nuribom.com
ro.build.tags=release-keys
ro.product.model=LG-VM696
ro.product.brand=lge
ro.product.name=m3s_virgin_us
ro.product.device=m3s
ro.modem.version=
ro.brand.name=LG Optimus Elite
ro.product.board=lge_m3s
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=LGE
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm7k
ro.build.product=m3s
ro.build.description=m3s_virgin_us-user 2.3.7 ZV4.GWK74 47C45DFC release-keys
ro.build.fingerprint=lge/m3s_virgin_us/m3s:2.3.7/ZV4.GWK74/47C45DFC:user/release-keys
rild.libpath=/system/lib/libril-qc-qmi-1.so
rild.libargs=-d /dev/smd0
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
ril.subscription.types=NV,RUIM
DEVICE_PROVISIONED=1
debug.sf.hw=1
dalvik.vm.heapsize=32m
dev.pm.dyn_samplingrate=1
persist.cne.UseCne=false
persist.cne.bat.range.low.med=30
persist.cne.bat.range.med.high=60
persist.cne.loc.policy.op=/system/etc/OperatorPolicy.xml
persist.cne.loc.policy.user=/system/etc/UserPolicy.xml
persist.cne.bwbased.rat.sel=false
persist.cne.snsr.based.rat.mgt=false
persist.cne.bat.based.rat.mgt=false
persist.cne.rat.acq.time.out=30000
persist.cne.rat.acq.retry.tout=0
lpa.decode=true
ro.use_data_netmgrd=true
ro.emmc.sdcard.partition=16
ro.config.ehrpd=true
media.stagefright.enable-player=true
media.stagefright.enable-meta=false
media.stagefright.enable-scan=false
media.stagefright.enable-http=true
ro.opengles.version=131072
ro.qualcomm.bluetooth.dun=false
ro.bluetooth.remote.autoconnect=true
ro.cdma.home.operator.alpha=Virgin Mobile
ro.cdma.home.operator.numeric=311490
gsm.sim.operator.alpha=Virgin Mobile
gsm.sim.operator.numeric=311490
gsm.sim.operator.iso-country=us
gsm.operator.alpha=Virgin Mobile
gsm.operator.numeric=311490
gsm.operator.iso-country=us
gsm.sim.state=READY
persist.service.usbport.enable=1
ro.multi.rild=true
ro.qualcomm.bluetooth.ftp=true
debug.bt.discoverable_time=120
ro.bluetooth.request.master=false
ro.setupwizard.mode=DISABLED
ro.com.google.gmsversion=2.3_r9
ro.config.notification_sound=Pebble.ogg
ro.config.alarm_alert=Alarm1.ogg
ro.com.google.clientidbase=android-lge
ro.com.google.clientidbase.yt=android-virgin-us
ro.com.google.clientidbase.am=android-virgin-us
ro.com.google.clientidbase.gmm=android-lge
ro.com.google.clientidbase.ms=android-virgin-us
ro.config.ringtone=Beyond_the_Dream.ogg
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=3122137e
ro.bootmode=unknown
ro.baseband=msm
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=qcom
ro.revision=0
ro.emmc=1
persist.radio.adb_log_on=0
persist.radio.mem_leak_debug=0
persist.radio.voip_enabled=0
persist.sys.language=en
persist.sys.country=US
persist.sys.localevar=
persist.sys.timezone=America/Chicago
persist.sys.sound_enable=2
init.svc.recovery=running
init.svc.adbd=running
Can someone share only stock recovery.img and stock boot.img separately??
superatmos said:
Can someone share only stock recovery.img and stock boot.img separately??
Click to expand...
Click to collapse
boot partition: http://www.sendspace.com/file/89l97v
recovery partition: http://www.sendspace.com/file/zlibfl
BTW, I did try builder.clockworkmod.com http://jenkins.cyanogenmod.com/job/recovery/757/ and that recovery did not work.
k_t_b said:
boot partition: http://www.sendspace.com/file/89l97v
recovery partition: http://www.sendspace.com/file/zlibfl
BTW, I did try builder.clockworkmod.com http://jenkins.cyanogenmod.com/job/recovery/757/ and that recovery did not work.
Click to expand...
Click to collapse
for one, the partitions are all wrong. and most likely the kernel base address and cmdline are wrong also. "adb pull /proc/last_kmsg" run that and post here please. also review the output for any personal info, i.e. esn, msid, and so forth
also, pm me your gtalk. Im working on this right this second....
jmztaylor said:
for one, the partitions are all wrong. and most likely the kernel base address and cmdline are wrong also. "adb pull /proc/last_kmsg" run that and post here please. also review the output for any personal info, i.e. esn, msid, and so forth
also, pm me your gtalk. Im working on this right this second....
Click to expand...
Click to collapse
ESN has been replaced with 00000000000000
http://www.sendspace.com/file/ate07b
New last_kmsg after trying new recovery.img
http://www.sendspace.com/file/cgzcxm
Bump
Hi out there!
I think I´m a little bit in the wrong topic - bt I try to get a working CWM for LG Optimus 3D Max (LGP920).
For my device the recovery partiion is mmblck0p6.
I ran the CWM Online Builder too and copyed this new image to /dev/block.
But if I try booting into CWM, I only get a black screen and nothing happens.
Maybe you know what to do?!
I made a own thread here!
jmztaylor said:
for one, the partitions are all wrong. and most likely the kernel base address and cmdline are wrong also. "adb pull /proc/last_kmsg" run that and post here please. also review the output for any personal info, i.e. esn, msid, and so forth
also, pm me your gtalk. Im working on this right this second....
Click to expand...
Click to collapse
Here is a second build - http://jenkins.cyanogenmod.com/job/recovery/2467/
I still can't get it to work.
/proc/config.gz
CONFIG_PHYS_OFFSET=0x00200000
CONFIG_CMDLINE="init=/sbin/init root=/dev/ram rw initrd=0x11000000,16M mem=88M ip=dhcp"
recovery.fstab:
# mount point fstype device [device2]
/boot emmc /dev/block/mmcblk0p9
/cache ext4 /dev/block/mmcblk0p6
/data ext4 /dev/block/mmcblk0p13
/misc emmc /dev/block/mmcblk0
/recovery emmc /dev/block/mmcblk0p14
/system ext4 /dev/block/mmcblk0p12
/sdcard vfat /dev/block/mmcblk0p15 /dev/block/mmcblk0
/sdcard/_ExternalSD vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
I took the recovery.img which builder.clockworkmod.com spit out and padded it so it was the same size as the stock recovery:
$ su
# tr "\000" "\377" < /dev/zero | dd ibs=512k count=16384 of=/sdcard/recovery-final.img
16384+0 records in
16384+0 records out
8388608 bytes transferred in 0.356 secs (23563505 bytes/sec)
tr: short write
# busybox dd if=/sdcard/recovery.img of=/sdcard/recovery-final.img conv=notrunc
10920+0 records in
10920+0 records out
5591040 bytes (5.3MB) copied, 0.103271 seconds, 51.6MB/s
#
I zeroed out the recovery partition so I could boot into Fastboot:
$ su
# cat /dev/zero > /dev/block/mmcblk0p14
Then I renamed recovery-final.img to recovery.img and used Fastboot to flash it:
C:\Windows\system32>cd C:\Program Files\Android\android-sdk\platform-tools
C:\Program Files\Android\android-sdk\platform-tools>fastboot devices
3122137e fastboot
C:\Program Files\Android\android-sdk\platform-tools>fastboot flash recovery recovery.img
sending 'recovery' (8192 KB)...
OKAY [ 2.487s]
writing 'recovery'...
OKAY [ 5.478s]
finished. total time: 7.971s
C:\Program Files\Android\android-sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.439s
C:\Program Files\Android\android-sdk\platform-tools>
I checked the md5sum for the partition to make sure it matched the recovery.img:
$ su
# busybox md5sum /dev/block/mmcblk0p14
561a27f5fcff924820758659b00422ea /dev/block/mmcblk0p14
I still can't boot into CWM recovery. Anybody have any ideas?
---------- Post added at 06:48 AM ---------- Previous post was at 06:28 AM ----------
last_kmsg:
http://www.sendspace.com/file/pmlauo
Here you can download a kernel with ClockworkMod Recovery built into it, which allows you to flash zips and to make and restore backups.
This version of ClockworkMod Recovery is the ICS version, so it is the latest (until there is a jellybean one).
Nickholtus has prepared for you an easy to flash package here for you:
Xperia P: http://forum.xda-developers.com/showthread.php?p=28778819
Xperia U: http://forum.xda-developers.com/showthread.php?p=28819512&postcount=282
Xperia Sola (working external sdcard): http://forum.xda-developers.com/showthread.php?p=28957468&postcount=412
To flash this recovery, download the kernel, put it in your fastboot folder and name it kernel.elf.
Then open up a command prompt and in that folder do:
Code:
fastboot flash boot kernel.elf
This is a joint effort of I, nickholtus, K900 and championswimmer, our sources are at https://github.com/AOKPXperia, our main aim is to make trees that will build on AOSP and any other android source tree (AOKP - unicorns).
Thanks to Arakmar for clearing things up for me on how to individually compile the recovery binary.
Keiran
Nice to say devs coming up...Thank you for your efforts ..
Edit: Thank you Thank you Thank you...
Woah!
By the end of the week? That's fast
Do help Kieran get his phone here
Sent from my ST25i using xda premium
Wow !!!!
Thanks For Ur Efforts
Thanks bro!!!
Inviato dal mio LT22i con Tapatalk 2
That would be awesome Hoply we will see some rom development then
Sent from my LT22i using xda premium
Here is my progress:
Got minimal device tree set up for kumquat (ST25i, Xperia U)
All I need now is to make recovery.fstab, can people post mount info for P, U and Sola?
Then after that I edit ram disk to allow booting into recovery and I will post it on this thread.
hi,
here is the /proc/mount file of my xperia sola.
i hope it is what you need?
greetings
Progress:
Got minimal device tree done - check
Compiled recovery - check
Now all we need to do is inject recovery into boot image, then you can have recovery on stock kernel
Our sources are at https://github.com/AOKPXperia
Current repo I am using is device_sony_kumquat
Keiran
Edit: from above info /sdcard is at /dev/block/vold/179:14
Awsome!!! I will wait this...
Code:
C:\Program Files\Android\android-sdk\platform-tools>Adb shell cat /proc/partitio
ns
major minor #blocks name
7 0 10427 loop0
7 1 4190 loop1
7 2 4190 loop2
179 0 7757824 mmcblk0
179 1 1023 mmcblk0p1
179 2 512 mmcblk0p2
179 3 128 mmcblk0p3
179 4 1 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 3072 mmcblk0p6
179 7 5120 mmcblk0p7
179 8 8192 mmcblk0p8
179 9 16384 mmcblk0p9
179 10 1048576 mmcblk0p10
179 11 2097152 mmcblk0p11
179 12 256000 mmcblk0p12
179 13 16384 mmcblk0p13
179 14 4173824 mmcblk0p14
254 0 10426 dm-0
254 1 4189 dm-1
254 2 4189 dm-2
C:\Program Files\Android\android-sdk\platform-tools>
here u go again xperia U mounts....
---------- Post added at 04:10 PM ---------- Previous post was at 04:05 PM ----------
Code:
# mount
mount
rootfs / rootfs rw,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
tmpfs /dev/shm tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/block/mmcblk0p10 /system ext4 rw,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p6 /modemfs ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordere
d 0 0
/dev/block/mmcblk0p11 /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered,
noauto_da_alloc 0 0
/dev/block/mmcblk0p12 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered
0 0
/dev/block/mmcblk0p8 /data/idd ext4 rw,nosuid,nodev,noatime,barrier=0,data=order
ed 0 0
/dev/block/vold/179:14 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,
uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharse
t=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:14 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioc
harset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.trust5.odp-1 vfat ro,dirsync,nosuid,nodev,relatime
,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mix
ed,utf8,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/teenpatti.com.ibibo-1 vfat ro,dirsync,nosuid,nodev,rel
atime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortnam
e=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-2 /mnt/asec/play.ibibo.rummy.cash-1 vfat ro,dirsync,nosuid,nodev,r
elatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortn
ame=mixed,utf8,errors=remount-ro 0 0
#
should help u too
Yeah I got that
/cache is mmcblk0p12
/data is mmcblk0p11
/system is mmcblk0p10
/sdcard is mmcblk0p14
/boot is mmcblk0p9
Can anyone verify this for me?
Keiran
Keiran can you make this possible for Locked bootloaders btw ?
DeanBoro said:
Keiran can you make this possible for Locked bootloaders btw ?
Click to expand...
Click to collapse
Do this for me,
adb shell "cd /dev/block ; ls ;"
And post here the output
If this device gets root on locked boot loader, maybe.
Keiran
KeiranFTW said:
Do this for me,
adb shell "cd /dev/block ; ls ;"
And post here the output
If this device gets root on locked boot loader, maybe.
Keiran
Click to expand...
Click to collapse
Here is the output you requested
Code:
* daemon started successfully *
vold
mmcblk0p14
mmcblk0p13
mmcblk0p12
mmcblk0p11
mmcblk0p10
mmcblk0p9
mmcblk0p8
mmcblk0p7
mmcblk0p6
mmcblk0p5
mmcblk0p4
mmcblk0p3
mmcblk0p2
mmcblk0p1
mmcblk0
loop7
loop6
loop5
loop4
loop3
loop2
loop1
loop0
ram15
ram14
ram13
ram12
ram11
ram10
ram9
ram8
ram7
ram6
ram5
ram4
ram3
ram2
ram1
ram0
DeanBoro said:
Here is the output you requested
Code:
* daemon started successfully *
vold
mmcblk0p14
mmcblk0p13
mmcblk0p12
mmcblk0p11
mmcblk0p10
mmcblk0p9
mmcblk0p8
mmcblk0p7
mmcblk0p6
mmcblk0p5
mmcblk0p4
mmcblk0p3
mmcblk0p2
mmcblk0p1
mmcblk0
loop7
loop6
loop5
loop4
loop3
loop2
loop1
loop0
ram15
ram14
ram13
ram12
ram11
ram10
ram9
ram8
ram7
ram6
ram5
ram4
ram3
ram2
ram1
ram0
Click to expand...
Click to collapse
You have p9, p9 is visible, is boot partition... don't know if you can flash to it though, may be protected on locked bl - anyway you need root first.
KeiranFTW said:
You have p9, p9 is visible, is boot partition... don't know if you can flash to it though, may be protected on locked bl - anyway you need root first.
Click to expand...
Click to collapse
I cant unlock the bootloader as the fastboot is locked unfortunately (N) . Do you have any suggestions on how I could attempt to gain ROOT on it, or maybe even possibly Temp ROOT?
DeanBoro said:
I cant unlock the bootloader as the fastboot is locked unfortunately (N) . Do you have any suggestions on how I could attempt to gain ROOT on it, or maybe even possibly Temp ROOT?
Click to expand...
Click to collapse
No idea but recovery isn't working, bootrec won't execute
KeiranFTW said:
No idea but recovery isn't working, bootrec won't execute
Click to expand...
Click to collapse
ahhh that sucks!
S1 apparently doesnt enable Fastboot for the new Xperia line atm so I cant really do much development
Okay, so from some hard work and testing from nickholtus (hats off to him) we have fixed up bootrec and he is currently using a recovery compiled by me on his P
With this you can even back up boot/kernel partition on the go! No need for fastboot!
Not working:
Mass storage (we are using ICS recovery sources, with different USB gadget implementation to gingerbread)
Everything else works for now
We will post recovery when we have patched stock kernel ram disk for the devices.
Keiran
[email protected]:/dev/block/platform/dw_mmc.0/by-name $ ls -la
ls -la
lrwxrwxrwx root root 2013-03-26 16:07 BOOT -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2013-03-26 16:07 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-03-26 16:07 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-03-26 16:07 CACHE -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2013-03-26 16:07 CARRIER -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2013-03-26 16:07 CDMA -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2013-03-26 16:07 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2013-03-26 16:07 HIDDEN -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2013-03-26 16:07 OTA -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2013-03-26 16:07 PARAM -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2013-03-26 16:07 PERSDATA -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2013-03-26 16:07 RADIO -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2013-03-26 16:07 RECOVERY -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2013-03-26 16:07 RESERVED2 -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2013-03-26 16:07 SYSTEM -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2013-03-26 16:07 TDATA -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2013-03-26 16:07 TOMBSTONES -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2013-03-26 16:07 USERDATA -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2013-03-26 16:07 m9kefs1 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-03-26 16:07 m9kefs2 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-03-26 16:07 m9kefs3 -> /dev/block/mmcblk0p6
[email protected]:/ $ cat /proc/cpuinfo
cat /proc/cpuinfo
Processor : ARMv7 Processor rev 3 (v7l)
processor : 0
BogoMIPS : 1590.88
processor : 1
BogoMIPS : 1590.88
processor : 2
BogoMIPS : 1590.88
processor : 3
BogoMIPS : 1590.88
Features : swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva id
ivt
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x2
CPU part : 0xc0f
CPU revision : 3
Hardware : UNIVERSAL5410
Revision : 0009
Serial : xxxxxxxxxxx4d00ee10
Build.prop
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JDQ39
ro.build.display.id=JDQ39.I9500XXUAMC6
ro.build.version.incremental=I9500XXUAMC6
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.2.2
ro.build.date=Mon Mar 11 22:42:39 KST 2013
ro.build.date.utc=1363009359
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEP-127
ro.build.tags=release-keys
ro.product.model=GT-I9500
ro.product.brand=samsung
ro.product.name=ja3gxx
ro.product.device=ja3g
ro.product.board=universal5410
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=exynos5
# ro.build.product is obsolete; use ro.product.device
ro.build.product=ja3g
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=ja3gxx-user 4.2.2 JDQ39 I9500XXUAMC6 release-keys
ro.build.fingerprint=samsung/ja3gxx/ja3g:4.2.2/JDQ39/I9500XXUAMC6:user/release-keys
ro.build.characteristics=lightTheme
# Samsung Specific Properties
ro.build.PDA=I9500XXUAMC6
ro.build.hidden_ver=I9500XXUAMC6
ro.build.changelist=265143
ro.product_ship=true
ro.chipname=exynos5410
# end build properties
This is the 16gb model if I am correct? Interesting it's ext4.
Sent from my HTC One S using xda app-developers app
Closed Source Project said:
This is the 16gb model if I am correct? Interesting it's ext4.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Why is that interesting?
Toss3 said:
Why is that interesting?
Click to expand...
Click to collapse
+1 :angel:
Samsung has been on EXT4 after the S1. Google forced them over. Its not surprising.
I want to ask you, to do into terminal
Code:
su
cd dev/block/platform/dw_mmc/by-name
ls -l
and upload result..
after this, if you can, make dump partitions: boot, recovery, system, cache, hidden, modem, param
Code:
su
dd if=dev/block/mmcblk0p[partition number] of=sdcard/[image file]
Then I will try make ROM for flash via odin
my S4 not have root！ Can you ROOT my S4?
zhangqip said:
my S4 not have root! Can you ROOT my S4?
Click to expand...
Click to collapse
But for this i need any stock rom or system dump from cwm
p.s.
try load phone into recovery mode, connect to kies and choose restore device, kies must download 3th files service ROM, on PC
zhangqip said:
my S4 not have root！ Can you ROOT my S4?
Click to expand...
Click to collapse
If you want it to root plant it in the ground and water it...
Sent from my HTC One S using xda app-developers app
Here are more details extracted from Screener device, credits goes to him.
Partition sizes:
Code:
major minor #blocks name
179 0 15388672 mmcblk0
179 1 4096 mmcblk0p1
179 2 4096 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 4096 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 4096 mmcblk0p6
179 7 20480 mmcblk0p7
259 0 8192 mmcblk0p8
259 1 8192 mmcblk0p9
259 2 8192 mmcblk0p10
259 3 8192 mmcblk0p11
259 4 8192 mmcblk0p12
259 5 90112 mmcblk0p13
259 6 262144 mmcblk0p14
259 7 4096 mmcblk0p15
259 8 573440 mmcblk0p16
259 9 12288 mmcblk0p17
259 10 4096 mmcblk0p18
259 11 2121728 mmcblk0p19
259 12 2830336 mmcblk0p20
259 13 9379840 mmcblk0p21
and Mount points:
Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
/dev/block/mmcblk0p17 /persdata/absolute ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/mmcblk0p20 /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/mmcblk0p3 /efs ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,errors=panic,data=ordered 0 0
/dev/block/mmcblk0p19 /cache ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/mmcblk0p21 /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/data/media /mnt/shell/emulated sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,mode=050,gid=1028 0 0
/data/media /storage/emulated/0 sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
/data/media /storage/emulated/0/Android/obb sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
/data/media /storage/emulated/legacy sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
/data/media /storage/emulated/legacy/Android/obb sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
[/COLOR]wanam you're a genius, finally, today I will make system.img... with root for Odin
well done
http://forum.xda-developers.com/showthread.php?t=2213775
Closed Source Project said:
If you want it to root plant it in the ground and water it...
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Hahahahaha rooting made simple lol
Sent from my GT-I9500 using xda app-developers app
wanam said:
Here are more details extracted from Screener device, credits goes to him.
Partition sizes:
Code:
major minor #blocks name
179 0 15388672 mmcblk0
179 1 4096 mmcblk0p1
179 2 4096 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 4096 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 4096 mmcblk0p6
179 7 20480 mmcblk0p7
259 0 8192 mmcblk0p8
259 1 8192 mmcblk0p9
259 2 8192 mmcblk0p10
259 3 8192 mmcblk0p11
259 4 8192 mmcblk0p12
259 5 90112 mmcblk0p13
259 6 262144 mmcblk0p14
259 7 4096 mmcblk0p15
259 8 573440 mmcblk0p16
259 9 12288 mmcblk0p17
259 10 4096 mmcblk0p18
259 11 2121728 mmcblk0p19
259 12 2830336 mmcblk0p20
259 13 9379840 mmcblk0p21
and Mount points:
Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
/dev/block/mmcblk0p17 /persdata/absolute ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/mmcblk0p20 /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/mmcblk0p3 /efs ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,errors=panic,data=ordered 0 0
/dev/block/mmcblk0p19 /cache ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/mmcblk0p21 /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/data/media /mnt/shell/emulated sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,mode=050,gid=1028 0 0
/data/media /storage/emulated/0 sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
/data/media /storage/emulated/0/Android/obb sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
/data/media /storage/emulated/legacy sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
/data/media /storage/emulated/legacy/Android/obb sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
Click to expand...
Click to collapse
with this in future can have more space in internal card??
e
GT-I9500 cihazımdan Tapatalk kullanılarak gönderildi
Deleted because I found what I was looking for :thumbup:
Sent from my GT-I9500
Output from cat /proc/partitions, names shown in red do not appear, they have been taken from different files in the system, they could be wrong!
Code:
[email protected]:/ $ cat /proc/partitions
major minor #blocks name
31 0 1024 mtdblock0
179 0 3866624 mmcblk0
179 1 128 mmcblk0p1
179 2 512 mmcblk0p2 [COLOR="Red"] mbm[/COLOR]
179 3 512 mmcblk0p3
179 4 1 mmcblk0p4 [COLOR="Red"] ebr[/COLOR]
179 5 512 mmcblk0p5 [COLOR="Red"] cdt[/COLOR]
179 6 4096 mmcblk0p6 [COLOR="Red"] pds[/COLOR]
179 7 1536 mmcblk0p7
179 8 1024 mmcblk0p8 [COLOR="Red"] logo.bin[/COLOR]
179 9 16384 mmcblk0p9[COLOR="Red"] boot[/COLOR]
179 10 16384 mmcblk0p10[COLOR="Red"] recovery[/COLOR]
179 11 512 mmcblk0p11
179 12 512 mmcblk0p12
179 13 8192 mmcblk0p13
179 14 262144 mmcblk0p14 [COLOR="Red"] system[/COLOR]
179 15 262144 mmcblk0p15 [COLOR="Red"] cache[/COLOR]
179 16 131072 mmcblk0p16 [COLOR="Red"] customize[/COLOR]
179 17 3160064 mmcblk0p17 [COLOR="Red"] data[/COLOR]
179 64 2048 mmcblk0boot1
179 32 2048 mmcblk0boot0
To encourage more research and developments, use the donate button on the right! thanks!
in case needed, heres output for mount
Code:
[email protected]:/ $ mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
pstore /sys/fs/pstore pstore rw,relatime 0 0
/dev/block/mmcblk0p14 /system ext4 ro,seclabel,relatime,discard,data=ordered 0 0
/dev/block/mmcblk0p15 /cache ext4 rw,seclabel,nosuid,nodev,noatime,discard,data=ordered 0 0
/dev/block/mmcblk0p17 /data ext4 rw,seclabel,nosuid,nodev,relatime,discard,noauto_da_alloc,data=ordered 0 0
/dev/block/mmcblk0p6 /pds ext4 rw,seclabel,nosuid,nodev,noatime,discard 0 0
/dev/block/mmcblk0p16 /customize ext4 rw,seclabel,nosuid,nodev,relatime,discard,noauto_da_alloc,data=ordered 0 0
none /sys/kernel/debug debugfs rw,relatime,mode=755 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
Hey guys!
I'm searching around and I couldn't find a way to root SM-R500 Samsung Galaxy Watch Active (Tizen 4.0.0.3). I found a lot of firmware on different websites, but I couldn't find a rooted one. Any suggestions ...
Thanks
Depend what you expect...
Factory/Service Firmware called Combination Firmware is rooted...
I am using Combination Firmware as base... as Engineer sboot.bin (Bootloader) Engineer Kernel is inside...
From Stock Firmware only rootfs.img is modified... to have su Binary...
Problem...
SM-R500 nor other Galaxy variant tested...
Sugestion for you...
Flash Combination Firmware to see what kind of Root you can expect...
I could help you to modify Firmware Files... but OWN RISK...
Best Regards
adfree said:
Depend what you expect...
Factory/Service Firmware called Combination Firmware is rooted...
I am using Combination Firmware as base... as Engineer sboot.bin (Bootloader) Engineer Kernel is inside...
From Stock Firmware only rootfs.img is modified... to have su Binary...
Problem...
SM-R500 nor other Galaxy variant tested...
Sugestion for you...
Flash Combination Firmware to see what kind of Root you can expect...
I could help you to modify Firmware Files... but OWN RISK...
Best Regards
Click to expand...
Click to collapse
I don’t mind to give it a try. Please share what you have?
Sorry.
I waste tooo much time with Tizen...
I have limited time... and energy...
The long way is here:
https://forum.xda-developers.com/smartwatch/gear-s3/gear-s3-android-wear-port-wip-t3584588
Somewhere inside this Thread are infos how to play with rootfs.img...
The "faster" way for you or both of us... is.
Flash Combination Firmware for SM-R500 to see if this is what you want...
Code:
COMBINATION-FT40_R500XXU1ASA5.tar.md5
COMBINATION-FT40_R500XXU1ASG1.tar.md5
These 2 FT40 seems leaked and available... maybe somewhere in public...
I am too lazy to search for you.
TRy hard enough and in 2 days you can pm me... if you not able to find it...
Maybe I will upload for you...
But again.
What kind of magic you expect from Rooting of your SM-R500?
So I can make decission to help you... or maybe waste my time with other things.
Best Regards
Edit 1.
Code:
COMBINATION-FT40_R500XXU1[B]ASA5[/B].tar.md5
ASA5 I have on my HDD... I could upload...
Edit 2.
Uupsi.. I have both FT40...
Still no idea if somewhere public Link available...
Edit 3...
Lesson 1.
https://forum.xda-developers.com/showpost.php?p=73503787&postcount=150
You "need" netOdin Tool for Flashing Firmware...
I will upload for you:
Code:
COMBINATION-FT40_R500XXU1ASA5.tar.md5
Need some time for upload...
Plese remember:
Own risk!
Best Regards
---------- Post added at 04:28 AM ---------- Previous post was at 03:35 AM ----------
Code:
COMBINATION-FT40_R500XXU1ASA5.tar.md5
https://www.file-upload.net/download-13786815/COMBINATION-FT40_R500XXU1ASA5.tar.md5.7z.html
Own risk!
Best Regards
adfree said:
Sorry.
I waste tooo much time with Tizen...
I have limited time... and energy...
The long way is here:
https://forum.xda-developers.com/smartwatch/gear-s3/gear-s3-android-wear-port-wip-t3584588
Somewhere inside this Thread are infos how to play with rootfs.img...
The "faster" way for you or both of us... is.
Flash Combination Firmware for SM-R500 to see if this is what you want...
Code:
COMBINATION-FT40_R500XXU1ASA5.tar.md5
COMBINATION-FT40_R500XXU1ASG1.tar.md5
These 2 FT40 seems leaked and available... maybe somewhere in public...
I am too lazy to search for you.
TRy hard enough and in 2 days you can pm me... if you not able to find it...
Maybe I will upload for you...
But again.
What kind of magic you expect from Rooting of your SM-R500?
So I can make decission to help you... or maybe waste my time with other things.
Best Regards
Edit 1.
Code:
COMBINATION-FT40_R500XXU1[B]ASA5[/B].tar.md5
ASA5 I have on my HDD... I could upload...
Edit 2.
Uupsi.. I have both FT40...
Still no idea if somewhere public Link available...
Edit 3...
Lesson 1.
https://forum.xda-developers.com/showpost.php?p=73503787&postcount=150
You "need" netOdin Tool for Flashing Firmware...
I will upload for you:
Code:
COMBINATION-FT40_R500XXU1ASA5.tar.md5
Need some time for upload...
Plese remember:
Own risk!
Best Regards
---------- Post added at 04:28 AM ---------- Previous post was at 03:35 AM ----------
Code:
COMBINATION-FT40_R500XXU1ASA5.tar.md5
https://www.file-upload.net/download-13786815/COMBINATION-FT40_R500XXU1ASA5.tar.md5.7z.html
Own risk!
Best Regards
Click to expand...
Click to collapse
Sorry for the late reply and thank you adfree for your effort, but I already have and tested the combination firmware and It is not what I'm looking for! Now I'm trying to figure the pinout so I can connect it directly.
Done first attempt with DSL1 Firmware...
Waiting for feedback...
Meanwhile...
A
To enable Root access... SDB Tool required...
Code:
sdb root on
A.1
To enable su from Shell...
Additional steps required...
Code:
sdb root on
sdb shell
mount -vo remount,rw /
chmod -v +sx /usr/bin
Code:
sdb root off
Then you can su from shell...
Code:
su
then it asks for password... password is:
Code:
tizen
B
To check if you can now play with rootfs.img "on the fly"...
Code:
sdb root on
Or you have enbled the other way...
Code:
sdb shell
Code:
mount -vo remount,rw /
Now you can for instance delete poweron poweroff Animation... you can do more but this is safe... nothing will explode.
Code:
sdb root on
Switched to 'root' account mode
sdb shell
sh-3.2# cd /usr/share/edje
sh-3.2# ls -a1l
total 1280
drwxr-xr-x 5 root root 4096 Jun 27 2019 .
drwxr-xr-x 131 root root 4096 Jun 27 2019 ..
-rw-r--r-- 1 root root 322470 Apr 19 2019 360x360_PowerOff.edj
-rw-r--r-- 1 root root 227171 Apr 19 2019 360x360_PowerOn.edj
-rw-r--r-- 1 root root 6065 Apr 19 2019 csc-ani.edj
-rw-r--r-- 1 root root 6221 Apr 19 2019 factory-reset-util.edj
drwxr-xr-x 2 root root 4096 Jun 27 2019 images
drwxr-xr-x 2 root root 4096 Jun 27 2019 include
-rw-r--r-- 1 root root 295340 Apr 19 2019 poweroff.edj
-rw-r--r-- 1 root root 411726 Apr 19 2019 poweron.edj
-rw-r--r-- 1 root root 5656 Apr 19 2019 voice-control-elm.edj
drwxr-xr-x 2 root root 4096 Jun 27 2019 xwalk
Code:
rm poweron.edj
and/or
Code:
rm poweroff.edj
Be carefully what you remove or replace...
Best Regards
Seems to work... DSL1 rooted... tested in coop with:
Code:
COMBINATION-FT40_R500XXU1[B]ASL2[/B]
For some dump action I need some infos about partition layout...
Code:
[B]cat /proc/partitions[/B]
Example output from SM-Z130H and SM-R760...
Code:
major minor #blocks name
7 0 10052 loop0
7 1 17408 loop1
254 0 146152 zram0
179 0 3817472 mmcblk0
179 1 1024 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 1024 mmcblk0p3
179 4 1024 mmcblk0p4
179 5 1024 mmcblk0p5
179 6 1024 mmcblk0p6
179 7 1024 mmcblk0p7
179 8 1024 mmcblk0p8
179 9 8192 mmcblk0p9
179 10 9216 mmcblk0p10
179 11 2048 mmcblk0p11
179 12 2048 mmcblk0p12
179 13 2048 mmcblk0p13
179 14 8192 mmcblk0p14
179 15 8192 mmcblk0p15
179 16 8192 mmcblk0p16
179 17 8192 mmcblk0p17
179 18 8192 mmcblk0p18
179 19 4096 mmcblk0p19
179 20 2048 mmcblk0p20
179 21 32768 mmcblk0p21
179 22 131072 mmcblk0p22
179 23 2641920 mmcblk0p23
179 24 917504 mmcblk0p24
179 96 512 mmcblk0rpmb
179 64 4096 mmcblk0boot1
179 32 4096 mmcblk0boot0
179 128 7749632 mmcblk1
179 129 7748608 mmcblk1p1
Code:
sh-3.2# ls -l /dev/disk/by-partlabel
total 0
lrwxrwxrwx 1 root root 15 Apr 6 09:52 boot -> ../../mmcblk0p8
lrwxrwxrwx 1 root root 15 Apr 6 09:52 cm -> ../../mmcblk0p7
lrwxrwxrwx 1 root root 15 Apr 6 09:52 cpnvcore -> ../../mmcblk0p3
lrwxrwxrwx 1 root root 15 Apr 6 09:52 csa -> ../../mmcblk0p2
lrwxrwxrwx 1 root root 16 Apr 6 09:52 csc -> ../../mmcblk0p11
lrwxrwxrwx 1 root root 16 Apr 6 09:52 module -> ../../mmcblk0p10
lrwxrwxrwx 1 root root 15 Apr 6 09:52 param -> ../../mmcblk0p6
lrwxrwxrwx 1 root root 15 Apr 6 09:52 ramdisk1 -> ../../mmcblk0p5
lrwxrwxrwx 1 root root 15 Apr 6 09:52 ramdisk2 -> ../../mmcblk0p4
lrwxrwxrwx 1 root root 15 Apr 6 09:52 recovery -> ../../mmcblk0p9
lrwxrwxrwx 1 root root 16 Apr 6 09:52 rootfs -> ../../mmcblk0p14
lrwxrwxrwx 1 root root 16 Apr 6 09:52 steady -> ../../mmcblk0p15
lrwxrwxrwx 1 root root 16 Apr 6 09:52 system-data -> ../../mmcblk0p12
lrwxrwxrwx 1 root root 15 Apr 6 09:52 tup -> ../../mmcblk0p1
lrwxrwxrwx 1 root root 16 Apr 6 09:52 user -> ../../mmcblk0p13
Code:
sh-3.2# ls -l /dev/disk/by-label
total 0
lrwxrwxrwx 1 root root 16 Apr 6 09:52 modules -> ../../mmcblk0p10
lrwxrwxrwx 1 root root 10 Apr 6 09:52 ramdisk -> ../../ram0
lrwxrwxrwx 1 root root 15 Apr 6 09:52 ramdisk-recovery -> ../../mmcblk0p4
lrwxrwxrwx 1 root root 16 Apr 6 09:52 rootfs -> ../../mmcblk0p14
lrwxrwxrwx 1 root root 16 Apr 6 09:52 tizen -> ../../mmcblk0p13
Code:
sh-3.2# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 320K 1 loop /opt/share/zoneinfo
loop1 7:1 0 13.6M 1 loop /usr/share/locale
zram0 254:0 0 279.3M 0 disk [SWAP]
mmcblk0rpmb 179:24 0 512K 0 disk
mmcblk0boot0 179:8 0 4M 1 disk
mmcblk0boot1 179:16 0 4M 1 disk
mmcblk0 179:0 0 3.7G 0 disk
|-mmcblk0p1 179:1 0 32M 0 part
|-mmcblk0p2 179:2 0 8M 0 part /csa
|-mmcblk0p3 179:3 0 2M 0 part
|-mmcblk0p4 179:4 0 20M 0 part
|-mmcblk0p5 179:5 0 8M 0 part
|-mmcblk0p6 179:6 0 8M 0 part
|-mmcblk0p7 179:7 0 3M 0 part
|-mmcblk0p8 259:0 0 16M 0 part
|-mmcblk0p9 259:1 0 16M 0 part
|-mmcblk0p10 259:2 0 16M 0 part /usr/lib/modules
|-mmcblk0p11 259:3 0 190M 0 part /opt/system/csc
|-mmcblk0p12 259:4 0 158M 0 part /opt
|-mmcblk0p13 259:5 0 1.9G 0 part /opt/usr
|-mmcblk0p14 259:6 0 1.3G 0 part
| `-rootfs 253:0 0 1.2G 1 crypt /
`-mmcblk0p15 259:7 0 256K 0 part
Thanx in advance.
Best Regards
Here the answer.
Thanx. :good:
SM-R500 DSL1
Code:
sh-3.2# cat /proc/partitions
major minor #blocks name
1 0 20480 ram0
1 1 20480 ram1
7 0 34240 loop0
7 1 384 loop1
254 0 284980 zram0
179 0 3817472 mmcblk0
179 1 8192 mmcblk0p1
179 2 2048 mmcblk0p2
179 3 1024 mmcblk0p3
179 4 512 mmcblk0p4
179 5 512 mmcblk0p5
179 6 28160 mmcblk0p6
179 7 20480 mmcblk0p7
259 0 8192 mmcblk0p8
259 1 2048 mmcblk0p9
259 2 6144 mmcblk0p10
259 3 3072 mmcblk0p11
259 4 18432 mmcblk0p12
259 5 18432 mmcblk0p13
259 6 10240 mmcblk0p14
259 7 4096 mmcblk0p15
259 8 194560 mmcblk0p16
259 9 172032 mmcblk0p17
259 10 1873408 mmcblk0p18
259 11 1439744 mmcblk0p19
259 12 256 mmcblk0p20
179 24 512 mmcblk0rpmb
179 16 4096 mmcblk0boot1
179 8 4096 mmcblk0boot0
Code:
sh-3.2# ls -l /dev/disk/by-partlabel
total 0
lrwxrwxrwx 1 root root 16 Feb 8 11:11 afpc -> ../../mmcblk0p15
lrwxrwxrwx 1 root root 16 Feb 8 11:11 boot -> ../../mmcblk0p12
lrwxrwxrwx 1 root root 16 Feb 8 11:11 cm -> ../../mmcblk0p11
lrwxrwxrwx 1 root root 15 Feb 8 11:11 csa -> ../../mmcblk0p1
lrwxrwxrwx 1 root root 16 Feb 8 11:11 csc -> ../../mmcblk0p16
lrwxrwxrwx 1 root root 15 Feb 8 11:11 module -> ../../mmcblk0p5
lrwxrwxrwx 1 root root 16 Feb 8 11:11 nad_fw -> ../../mmcblk0p14
lrwxrwxrwx 1 root root 15 Feb 8 11:11 nad_refer -> ../../mmcblk0p3
lrwxrwxrwx 1 root root 15 Feb 8 11:11 param -> ../../mmcblk0p9
lrwxrwxrwx 1 root root 15 Feb 8 11:11 ramdisk1 -> ../../mmcblk0p8
lrwxrwxrwx 1 root root 15 Feb 8 11:11 ramdisk2 -> ../../mmcblk0p7
lrwxrwxrwx 1 root root 16 Feb 8 11:11 recovery -> ../../mmcblk0p13
lrwxrwxrwx 1 root root 16 Feb 8 11:11 rootfs -> ../../mmcblk0p19
lrwxrwxrwx 1 root root 15 Feb 8 11:11 smsn -> ../../mmcblk0p4
lrwxrwxrwx 1 root root 16 Feb 8 11:11 steady -> ../../mmcblk0p20
lrwxrwxrwx 1 root root 16 Feb 8 11:11 system-data -> ../../mmcblk0p17
lrwxrwxrwx 1 root root 15 Feb 8 11:11 tup -> ../../mmcblk0p6
lrwxrwxrwx 1 root root 15 Feb 8 11:11 tyd -> ../../mmcblk0p2
lrwxrwxrwx 1 root root 16 Feb 8 11:11 up_param -> ../../mmcblk0p10
lrwxrwxrwx 1 root root 16 Feb 8 11:11 user -> ../../mmcblk0p18
Code:
sh-3.2# ls -l /dev/disk/by-label
total 0
lrwxrwxrwx 1 root root 15 Feb 8 11:11 ramdisk -> ../../mmcblk0p8
lrwxrwxrwx 1 root root 15 Feb 8 11:11 ramdisk-recovery -> ../../mmcblk0p7
lrwxrwxrwx 1 root root 16 Feb 8 11:11 tizen-csc -> ../../mmcblk0p16
lrwxrwxrwx 1 root root 16 Feb 8 11:11 tizen-rootfs -> ../../mmcblk0p19
lrwxrwxrwx 1 root root 16 Feb 8 11:11 tizen-system-da -> ../../mmcblk0p17
lrwxrwxrwx 1 root root 16 Feb 8 11:11 tizen-user -> ../../mmcblk0p18
Code:
sh-3.2# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 33.4M 1 loop /usr/share/locale
loop1 7:1 0 384K 1 loop /opt/share/zoneinfo
mmcblk0 179:0 0 3.7G 0 disk
|-mmcblk0p1 179:1 0 8M 0 part /csa
|-mmcblk0p2 179:2 0 2M 0 part
|-mmcblk0p3 179:3 0 1M 0 part
|-mmcblk0p4 179:4 0 512K 0 part
|-mmcblk0p5 179:5 0 512K 0 part
|-mmcblk0p6 179:6 0 27.5M 0 part
|-mmcblk0p7 179:7 0 20M 0 part
|-mmcblk0p8 259:0 0 8M 0 part
|-mmcblk0p9 259:1 0 2M 0 part
|-mmcblk0p10 259:2 0 6M 0 part
|-mmcblk0p11 259:3 0 3M 0 part
|-mmcblk0p12 259:4 0 18M 0 part
|-mmcblk0p13 259:5 0 18M 0 part
|-mmcblk0p14 259:6 0 10M 0 part
|-mmcblk0p15 259:7 0 4M 0 part
|-mmcblk0p16 259:8 0 190M 0 part /opt/system/csc
|-mmcblk0p17 259:9 0 168M 0 part /opt
|-mmcblk0p18 259:10 0 1.8G 0 part /opt/usr
|-mmcblk0p19 259:11 0 1.4G 0 part /
`-mmcblk0p20 259:12 0 256K 0 part
mmcblk0boot0 179:8 0 4M 1 disk
mmcblk0boot1 179:16 0 4M 1 disk
mmcblk0rpmb 179:24 0 512K 0 disk
zram0 254:0 0 278.3M 0 disk [SWAP]
Code:
mmcblk0p1 CSA
mmcblk0p2 TYD
mmcblk0p3 NAD_REFER
mmcblk0p4 SMSN
mmcblk0p5 MODULE
mmcblk0p6 TUP
mmcblk0p7 RAMDISK-RECOVERY
mmcblk0p8 RAMDISK
mmcblk0p9 PARAM
mmcblk0p10 UP_PARAM
mmcblk0p11 CM
mmcblk0p12 BOOT
mmcblk0p13 RECOVERY
mmcblk0p14 NAD_FW
mmcblk0p15 AFPC
mmcblk0p16 CSC
mmcblk0p17 SYSTEM-DATA
mmcblk0p18 USR
mmcblk0p19 ROOTFS
mmcblk0p20 STEADY
mmcblk0boot0 BOOT0
mmcblk0boot1 BOOT1
mmcblk0rpmb RPMB --->protected... NOT readable
mmcblk0 Full 4 GB eMMC
Best Regards
SM-R500 DSL1 summary for dd action... dump partitions... :angel:
We have 20 partitions p1 - p20
+ 3 additional
We are writing to USR partition p18... remember limited space... ca, 1500 MB free
Code:
dd if=/dev/mmcblk0boot0 of=/opt/usr/media/bootloader0.bin
dd if=/dev/mmcblk0boot1 of=/opt/usr/media/bootloader1.bin
[COLOR="Red"][B]dd if=/dev/mmcblk0rpmb of=/opt/usr/media/rpmb.bin[/B][/COLOR]
dd if=/dev/mmcblk0p1 of=/opt/usr/media/csa.bin
dd if=/dev/mmcblk0p2 of=/opt/usr/media/tyd.bin
dd if=/dev/mmcblk0p3 of=/opt/usr/media/nad_refer.bin
dd if=/dev/mmcblk0p4 of=/opt/usr/media/smsn.bin
dd if=/dev/mmcblk0p5 of=/opt/usr/media/module.bin
dd if=/dev/mmcblk0p6 of=/opt/usr/media/tup.bin
dd if=/dev/mmcblk0p7 of=/opt/usr/media/ramdisk-recovery.bin
dd if=/dev/mmcblk0p8 of=/opt/usr/media/ramdisk.bin
dd if=/dev/mmcblk0p9 of=/opt/usr/media/param.bin
dd if=/dev/mmcblk0p10 of=/opt/usr/media/up_param.bin
dd if=/dev/mmcblk0p11 of=/opt/usr/media/cm.bin
dd if=/dev/mmcblk0p12 of=/opt/usr/media/boot.bin
dd if=/dev/mmcblk0p13 of=/opt/usr/media/recovery.bin
dd if=/dev/mmcblk0p14 of=/opt/usr/media/nad_fw.bin
dd if=/dev/mmcblk0p15 of=/opt/usr/media/afpc.bin
dd if=/dev/mmcblk0p16 of=/opt/usr/media/csc.bin
dd if=/dev/mmcblk0p17 of=/opt/usr/media/system-data.bin
[COLOR="Red"][B]dd if=/dev/mmcblk0p18 of=/opt/usr/media/usr.bin[/B][/COLOR]
[COLOR="Red"][B]dd if=/dev/mmcblk0p19 of=/opt/usr/media/rootfs.bin[/B][/COLOR]
dd if=/dev/mmcblk0p20 of=/opt/usr/media/steady.bin
Red marked Commands...
rootfs to dump is not really usefull... remember free space...
usr is written to usr partition... so never possible to dump in 1 step...
rpmb read protected,,, found no way on Wearables...
To pull all files from Media folder...
Code:
sdb pull /opt/usr/media/
Or pull file by file with filename... example:
Code:
sdb pull /opt/usr/media/[B]csa.bin[/B]
Best Regards
To dump "whole" eMMC...
Limitation we have only maximum 1,8 GB... so we have tiny problem to put whole 4 GB...
To check free space...
Example taken from my SM-R760...
Code:
sh-3.2# df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 1.3G 1.1G 200M 84% /
devtmpfs 340M 0 340M 0% /dev
/dev/mmcblk0p14 1.3G 1.1G 200M 84% /
/dev/mmcblk0p12 139M 85M 51M 63% /opt
/dev/mmcblk0p10 14M 253K 13M 2% /usr/lib/modules
tmpfs 352M 24K 352M 1% /dev/shm
tmpfs 352M 2.6M 349M 1% /run
tmpfs 352M 0 352M 0% /sys/fs/cgroup
tmpfs 352M 60K 352M 1% /tmp
/dev/loop0 384K 384K 0 100% /opt/share/zoneinfo
/dev/loop1 34M 34M 0 100% /usr/share/locale
/dev/mmcblk0p11 183M 101M 80M 56% /opt/system/csc
/dev/mmcblk0p2 6.8M 1.2M 5.0M 20% /csa
/dev/mmcblk0p13 1.9G 120M 1.8G 7% /opt/usr
tmpfs 71M 80K 71M 1% /run/user/5001
tmpfs 71M 0 71M 0% /run/user_ext/5001
/dev/mmcblk0p13 1.9G 120M 1.8G 7% /opt/usr/media
/dev/mmcblk0p13 1.9G 120M 1.8G 7% /opt/usr/apps
/dev/mmcblk0p13 1.9G 120M 1.8G 7% /opt/usr/home/owner/media
/dev/mmcblk0p13 1.9G 120M 1.8G 7% /opt/usr/media
sh-3.2# df -a
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 1298824 1064480 204612 84% /
devtmpfs 347224 0 347224 0% /dev
none 0 0 0 - /proc
sysfs 0 0 0 - /sys
/dev/mmcblk0p14 1298824 1064480 204612 84% /
/dev/mmcblk0p12 141376 86868 51276 63% /opt
/dev/mmcblk0p10 13847 253 13287 2% /usr/lib/modules
securityfs 0 0 0 - /sys/kernel/security
smackfs 0 0 0 - /sys/fs/smackfs
tmpfs 359712 24 359688 1% /dev/shm
devpts 0 0 0 - /dev/pts
tmpfs 359712 2628 357084 1% /run
tmpfs 359712 0 359712 0% /sys/fs/cgroup
cgroup 0 0 0 - /sys/fs/cgroup/systemd
pstore 0 0 0 - /sys/fs/pstore
cgroup 0 0 0 - /sys/fs/cgroup/net_cls
cgroup 0 0 0 - /sys/fs/cgroup/cpu,cpuacct
cgroup 0 0 0 - /sys/fs/cgroup/freezer
cgroup 0 0 0 - /sys/fs/cgroup/memory
debugfs 0 0 0 - /sys/kernel/debug
tmpfs 359712 60 359652 1% /tmp
configfs 0 0 0 - /sys/kernel/config
/dev/loop0 384 384 0 100% /opt/share/zoneinfo
/dev/loop1 34176 34176 0 100% /usr/share/locale
/dev/mmcblk0p11 187373 102462 81020 56% /opt/system/csc
/dev/mmcblk0p2 6907 1218 5117 20% /csa
/dev/mmcblk0p13 1936976 122612 1797980 7% /opt/usr
tmpfs 71940 80 71860 1% /run/user/5001
tmpfs 71940 0 71940 0% /run/user_ext/5001
/dev/mmcblk0p13 1936976 122612 1797980 7% /opt/usr/media
/dev/mmcblk0p13 1936976 122612 1797980 7% /opt/usr/apps
vip_cgroup 0 0 0 - /sys/fs/cgroup/vip
/dev/mmcblk0p13 1936976 122612 1797980 7% /opt/usr/home/owner/media
/dev/mmcblk0p13 1936976 122612 1797980 7% /opt/usr/media
Taken from here:
https://opensource.com/article/18/7/how-check-free-disk-space-linux
First attempt:
Code:
dd if=/dev/mmcblk0 of=/opt/usr/media/full4GB_eMMC.bin
dd stopps if usr partition is full...
Could lead to sideeffect...
But could be enough to pull result...
Code:
sh-3.2# dd if=/dev/mmcblk0 of=/opt/usr/media/full4GB_eMMC.bin
dd: writing to `/opt/usr/media/full4GB_eMMC.bin': [COLOR="Red"][B]No space left on device[/B][/COLOR]
3596569+0 records in
3596568+0 records out
1841442816 bytes (1.8 GB) copied, 151.265 s, 12.2 MB/s
Code:
sh-3.2# df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 1.3G 1.1G 200M 84% /
devtmpfs 340M 0 340M 0% /dev
/dev/mmcblk0p14 1.3G 1.1G 200M 84% /
/dev/mmcblk0p12 139M 83M 53M 61% /opt
/dev/mmcblk0p10 14M 253K 13M 2% /usr/lib/modules
tmpfs 352M 24K 352M 1% /dev/shm
tmpfs 352M 2.5M 349M 1% /run
tmpfs 352M 0 352M 0% /sys/fs/cgroup
tmpfs 352M 60K 352M 1% /tmp
/dev/loop0 384K 384K 0 100% /opt/share/zoneinfo
/dev/loop1 34M 34M 0 100% /usr/share/locale
/dev/mmcblk0p11 183M 101M 80M 56% /opt/system/csc
/dev/mmcblk0p2 6.8M 1.2M 5.0M 20% /csa
[COLOR="Red"][B]/dev/mmcblk0p13 1.9G 1.9G 0 100% /opt/usr[/B][/COLOR]
tmpfs 71M 80K 71M 1% /run/user/5001
tmpfs 71M 0 71M 0% /run/user_ext/5001
[COLOR="Red"][B]/dev/mmcblk0p13 1.9G 1.9G 0 100% /opt/usr/media
/dev/mmcblk0p13 1.9G 1.9G 0 100% /opt/usr/apps
/dev/mmcblk0p13 1.9G 1.9G 0 100% /opt/usr/home/owner/media
/dev/mmcblk0p13 1.9G 1.9G 0 100% /opt/usr/media[/B][/COLOR]
Code:
sdb pull /opt/usr/media/full4GB_eMMC.bin
pulled full4GB_eMMC.bin 100% 1756MB
1 file(s) pulled. 0 file(s) skipped.
/opt/usr/media/full4GB_eMMC.bin 552 KB/s (1841442816 bytes in 3255.896s)
Pull seems 1 hour...
Best Regards
Code:
sh-3.2# dd if=/dev/mmcblk0 | gzip > /opt/usr/media/full4GB_eMMC.bin.gz
gzip: stdout: No space left on device
Creates corrupt/unfinished archive file... but have 2200 MB inside... few more as uncompressed...
Better we split... and find other way for user partition...
.
.
.
Best Regards
Maybe found something...
Code:
sdb shell dd if=/dev/mmcblk0boot1>testme11.bin
sdb shell dd if=/dev/mmcblk0boot0>testme11more.bin
sdb shell dd if=/dev/mmcblk0rpmb>testme11moreAA.bin
Now need more time for next attempt...
Code:
sdb shell dd if=/dev/mmcblk0>FULLeMMCoverSDB_WiFi.bin
4 GB !
IMHO 1 - 2 hours...
Best Regards
Rooted SM-R500 DSL1 Firmware is here:
https://forum.xda-developers.com/showpost.php?p=81762345&postcount=838
If Questions... better ask BEFORE...
Best Regards
Hmmm... I don't know why...
But if I direct dump to PC... then additional crap is written...
2 Bytes...
Code:
0D0D
I have Tizen handset... SM-Z130H... with Tizen 2.4...
Here this work as it seems, tested with Command:
Code:
sdb shell dd if=/dev/mmcblk0boot1>Z1_boot1.bin
This partition is ever empty... contains only 00... so IMHO good reference...
But my Z1 is connected via USB cable...
No idea if 0D0D cames because some TCP problem...
Best Regards
With SM-R760 we have luck...
Combination Firmware not mandatory for Tizen 4 Root...
Only RAMDISK taken from Combination Firmware...
Maybe this is also working for SM-R500... need to be tested.
Attached is ramdisk.img from FT40 ASL2 for SM-R500...
Best Regards
I0T said:
Hey guys!
I'm searching around and I couldn't find a way to root SM-R500 Samsung Galaxy Watch Active (Tizen 4.0.0.3). I found a lot of firmware on different websites, but I couldn't find a rooted one. Any suggestions ...
Thanks
Click to expand...
Click to collapse
Hey there! Could you finally root the SM-R500? Is it still alive? Have the same model here... I used to root all Samsung I had but this is my very first watch so I do not want to mess it yet without anyone proofs
Your Firmware Version?
I have only rooted DSL1 for SM-R500...
Best Regards
adfree said:
Your Firmware Version?
I have only rooted DSL1 for SM-R500...
Best Regards
Click to expand...
Click to collapse
Hi adfree, It seems DSL1, lastest Samsung update.. I have read about combination firmwares etc.. but not tired anything without being sure cause is the most expensive watch i ever bought..
The most combinations firms seems for others than R500, I don't know either about knox on watch if will be tripped too and will left samsung pay useless or it works different than phones..
Yesterday I downloaded all tizen SDK tools etc... and sideloaded tpk apps to watch, they install but could not run them propperly.. but I guess all this is about to test yet as it is a "new watch" ...sorry my ignorance but I come from a LG watch from 2015 omg I had to update myself... xD
Thank you and have a nice day !
@Albayeah
Sorry.
In main I am talking with my self... about Rooting...
No idea why user not confirm in public...
I know he used the old method with Combination Firmware first... then my rooted rootfs,img...
The new way... is to flash only RAMDISK from Combination Firmware, then my rooted files.
So Round 1:
with netOdin
https://forum.xda-developers.com/showpost.php?p=81799723&postcount=15
Round 2.
with netOdin
IGNORE the Combination Firmware files
https://forum.xda-developers.com/showpost.php?p=81762345&postcount=838
Only this:
https://www.file-upload.net/download-13891175/2020_DSL1_smR500_ROOT_v1.7z.html
Own Risk!
But I am 99,9 % sure this is working. :angel:
Best Regards
adfree said:
@Albayeah
Sorry.
In main I am talking with my self... about Rooting...
No idea why user not confirm in public...
I know he used the old method with Combination Firmware first... then my rooted rootfs,img...
The new way... is to flash only RAMDISK from Combination Firmware, then my rooted files.
So Round 1:
with netOdin
https://forum.xda-developers.com/showpost.php?p=81799723&postcount=15
Round 2.
with netOdin
IGNORE the Combination Firmware files
https://forum.xda-developers.com/showpost.php?p=81762345&postcount=838
Only this:
https://www.file-upload.net/download-13891175/2020_DSL1_smR500_ROOT_v1.7z.html
Own Risk!
But I am 99,9 % sure this is working. :angel:
Best Regards
Click to expand...
Click to collapse
Many thanks! I am going to save your files by the moment because I am still afraid of messing something definetly on the watch with no reverse..
Maybe I have to do more research..
I hope I dont bother you with my questions but if you already rooted.. could you use samsung apps as usual..? Like samsung health, samsung pay.. won't prompt a security message or disable any functions, any apps..?
Sorry cause i am kinda confused with that details..
On phone I use Samsung apps hiding with magisk etc... cause it is rooted but it is Android, but what about watch with tizen and no magisk..? Will disable the apps just like in the phone, or is it knox unrecoverable? :silly:
Sorry for my inexperience maybe all this sounded silly to you XDD
Best wishes to all on these hard times :good: