Develop Bugs

CWM Porting Help [Completed]

I have a found a developer that is willing to help port CWM to this device. He doesn't have this device. He needs the following files.
UPDATE
Got everything we needed so far. Thanks to all that helped! Consider sending the developer utkanos a little something if this is useful to you.
Initial testing is done. He has posted the official release thread. Hope see some cool stuff soon.
Feel free to join #utkanos on freednode as a tester or watch the progress.
...and we have liftoff!
I got CWMR booting on the 927r and thus far it appears stable. Very early stages right now so I'm testing it deeply thanks to a helpful owner as we speak. More details as they come.
Click to expand...
Click to collapse
Hi.
I need the following:
1) A boot.img or zImage
2) A dump of /proc/partitions
3) A dump of /proc/emmc or /proc/mtd (if they exist)
4) A dump of the 'mount' command
Click to expand...
Click to collapse
You need to be rooted to dump the files and I am not rooted. So the faster we get these files, the faster CWM can be ported. Attach or link to the files in your post and thanks.

vil33 said:
I have a found a dev that is willing to help port CWM to this device. He doesn't have this device and isn't on xda as far as I know. He needs the follwing files.
You need to be rooted to dump the files and I am not rooted. So the faster we get these files, the faster CWM can be ported. Attach or link to the files in your post and thanks.
Click to expand...
Click to collapse
Here:
cat /proc/partitions
major minor #blocks name
7 0 12506 loop0
7 1 2111 loop1
7 2 5229 loop2
7 3 3150 loop3
179 0 7552000 mmcblk0
179 1 12288 mmcblk0p1
179 2 614400 mmcblk0p2
179 3 319488 mmcblk0p3
179 4 3932672 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 2097152 mmcblk0p6
179 7 16384 mmcblk0p7
259 0 5120 mmcblk0p8
259 1 8192 mmcblk0p9
259 2 8192 mmcblk0p10
259 3 524288 mmcblk0p11
179 8 7782400 mmcblk1
179 9 7781376 mmcblk1p1
254 0 12505 dm-0
254 1 2110 dm-1
254 2 5229 dm-2
254 3 3150 dm-3
/proc/emmc doesn't exist
cat /proc/mtd
dev: size erasesize name
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=111 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
debugfs /sys/kernel/debug debugfs 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/usb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /app-cache tmpfs rw,relatime,size=8192k 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p2 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p1 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,journal_checksum,data=ordered 0 0
/dev/block/mmcblk0p6 /data ext4 rw,nosuid,nodev,noatime,barrier=1,journal_checksum,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/mmcblk0p3 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/vold/179:4 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime
=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro,discard 0 0
/dev/block/vold/179:9 /mnt/sdcard/external_sd vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,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:9 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,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/external_sd/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/net.skyscanner.android.main-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,
iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/com.flightradar24free-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iochar
set=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-2 /mnt/asec/org.scummvm.scummvm-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharse
t=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-3 /mnt/asec/org.scummvm.scummvm.plugin.scumm-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=c
p437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0

tcfx44 said:
Here:
Click to expand...
Click to collapse
Thanks for the quick response, I passed it on to the Dev and hopefully he can do this. Do you have the boot.img as well?

vil33 said:
Thanks for the quick response, I passed it on to the Dev and hopefully he can do this. Do you have the boot.img as well?
Click to expand...
Click to collapse
I'm still new to Android and cannot find boot.img. Can you help me with the location of the file?

tcfx44 said:
I'm still new to Android and cannot find boot.img. Can you help me with the location of the file?
Click to expand...
Click to collapse
okay, go ahead and laugh, i'm no dev or linux guy, but there is a boot.img file ready for download on the Rooting the captivate glide thread right? I believe it is on the step 2 of the process (with a link on CarrierIQ Free). When I download that file and extracted, I got boot.img in tar file. Can they use that?
I don't want to upload, unsure about it.

gabby131 said:
okay, go ahead and laugh, i'm no dev or linux guy, but there is a boot.img file ready for download on the Rooting the captivate glide thread right? I believe it is on the step 2 of the process (with a link on CarrierIQ Free). When I download that file and extracted, I got boot.img in tar file. Can they use that?
I don't want to upload, unsure about it.
Click to expand...
Click to collapse
Thanks I forgot about that. Sent him it and hopefully it's the right one.

It would be nice if your friend release CWM to prepare a guide on how he did it, I am learning myself, successfully compiled the kernel but I dont really understand the proccess for CWM, should it is included in the kernel like it is the case for a lot of samsung devices or should it be a recovery...
Thanks for the details

CarpeNoctem said:
It would be nice if your friend release CWM to prepare a guide on how he did it, I am learning myself, successfully compiled the kernel but I dont really understand the proccess for CWM, should it is included in the kernel like it is the case for a lot of samsung devices or should it be a recovery...
Thanks for the details
Click to expand...
Click to collapse
Hey you can meet him on the freenode irc network on channel #koush by the name utkanos, he's usually there 9-5 central. Also it would help if we had a rooted user to help the process out. He just emailed me that he wanted this:
Can you get into stock recovery and get me the recovery.log? Should be in cache or tmp.
Click to expand...
Click to collapse

Hi.
In addition to the recovery.log from stock recovery, I would like to see a build.prop (from system) please.
I do not post on XDA very much, usually over on rootzwiki or on freenode.

Here is the build.prop
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=GINGERBREAD
ro.build.display.id=GINGERBREAD.RUXKJ5
ro.build.version.incremental=RUXKJ5
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.5
ro.build.date=Fri Oct 14 15:36:02 KST 2011
ro.build.date.utc=1318574162
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEI-28
ro.build.tags=release-keys
ro.product.model=SAMSUNG-SGH-I927R
ro.product.brand=samsung
ro.product.name=SGH-I927R
ro.product.device=SGH-I927R
ro.product.board=SGH-I927R
ro.product.cpu.abi=armeabi-v7a
# Samsung Specific Properties
ro.build.PDA=I927RUXKJ5
ro.build.hidden_ver=I927RUXKJ5
ro.build.changelist=652095
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=CA
ro.wifi.channels=
ro.board.platform=tegra
# ro.build.product is obsolete; use ro.product.device
ro.build.product=SGH-I927R
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=SGH-I927R-user 2.3.5 GINGERBREAD RUXKJ5 release-keys
ro.build.fingerprint=samsung/SGH-I927R/SGH-I927R:2.3.5/GINGERBREAD/RUXKJ5:user/release-keys
# Samsung Specific Properties
ro.build.PDA=I927RUXKJ5
ro.build.hidden_ver=I927RUXKJ5
ro.build.changelist=652095
ro.tether.denied=false
ro.flash.resolution=1080
# end build properties
ro.opengles.version = 131072
wifi.interface=eth0
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/ttys0
ro.sf.lcd_density=240
dalvik.vm.heapsize=64m
# Samsung USB default mode
persist.service.usb.setting=0
# Set Default Timezone as America/New_York
persist.sys.timezone=America/New_York
#
# ADDITIONAL_BUILD_PROPERTIES
#
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=OPTIONAL
ro.com.google.gmsversion=2.3_r7
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
ro.com.google.clientidbase=android-samsung
ro.com.google.clientidbase.ms=android-samsung
ro.com.google.clientidbase.am=android-samsung
ro.com.google.clientidbase.gmm=android-samsung
ro.com.google.clientidbase.yt=android-samsung
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
keyguard.no_require_sim=true
ro.config.ringtone=S_Over_the_horizon.ogg
ro.config.notification_sound=01_Sherbet.ogg
ro.config.alarm_alert=Good_Morning.ogg
ro.config.media_sound=Media_preview_Touch_the_light.ogg
ro.monkey=0
ro.opengles.version=131072
ro.secdevenc=true
ro.wtldatapassword=true
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Here if the result of the cat proc/mounts
Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=111 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
debugfs /sys/kernel/debug debugfs 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/usb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /app-cache tmpfs rw,relatime,size=8192k 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p2 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p1 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,journal_checksum,data=ordered 0 0
/dev/block/mmcblk0p6 /data ext4 rw,nosuid,nodev,noatime,barrier=1,journal_checksum,data=ordered,noau
to_da_alloc,discard 0 0
/dev/block/mmcblk0p3 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0

Cheers for that
edit: I believe I have what I need now, thank you to those who provided the files for me. I will update when I have something tangible for you.

Well I have some bad news for you guys.
The stock kernel provided is bitwise EXACTLY the size of the partition that holds it, and I need to add about 500KB of space to make recovery work.
Thus, repacking the ramdisk with a hacked recovery isn't going to be possible unless the kernel image can get much smaller to accommodate.

utkanos said:
Well I have some bad news for you guys.
The stock kernel provided is bitwise EXACTLY the size of the partition that holds it, and I need to add about 500KB of space to make recovery work.
Thus, repacking the ramdisk with a hacked recovery isn't going to be possible unless the kernel image can get much smaller to accommodate.
Click to expand...
Click to collapse
Isn't it possible to resize the partitions ?
also this mean Samsung has no intention to release any other kernel/version of android or the kernel needs to remains always the same?

Has anyone tried the kernel from the KL1 build? CIQ should be removed from that (it came out a few days after the CIQ fiasco), which could provide the space we're missing...

Symmetric said:
Has anyone tried the kernel from the KL1 build? CIQ should be removed from that (it came out a few days after the CIQ fiasco), which could provide the space we're missing...
Click to expand...
Click to collapse
Thanks for the tip, I think I might have something worth testing if someone wants to hop into IRC
I am on freenode as utkanos in #koush

...and we have liftoff!
I got CWMR booting on the 927r and thus far it appears stable. Very early stages right now so I'm testing it deeply thanks to a helpful owner as we speak. More details as they come.

Symmetric said:
Has anyone tried the kernel from the KL1 build? CIQ should be removed from that (it came out a few days after the CIQ fiasco), which could provide the space we're missing...
Click to expand...
Click to collapse
Good call

Work beautifully achieved

Symmetric said:
Has anyone tried the kernel from the KL1 build? CIQ should be removed from that (it came out a few days after the CIQ fiasco), which could provide the space we're missing...
Click to expand...
Click to collapse
Hooray for me!
Let the games begin?

utkanos said:
...and we have liftoff!
I got CWMR booting on the 927r and thus far it appears stable. Very early stages right now so I'm testing it deeply thanks to a helpful owner as we speak. More details as they come.
Click to expand...
Click to collapse
Amazing work utkanos, now I can get my flash fix on my GF's phone! Thanks a million!

[INFO][DEV] Wildfire S (marvel) partition information/recovery commands

Hello all,
Upon porting sense 4 I needed to mount a certain partition via a command that needed the exact dev block, so I decided to find out using adb and post my results here for other devs to see:
Filesystem........................Size......Used........Available......Use%........Mounted on
tmpfs...........................209.0M......48.0K.........209.0M...........0%................/dev
/dev/block/mmcblk0p1....861.1M....739.5M.........121.6M.........86%............/sdcard <-- May vary
/dev/block/mtdblock4.......35.0M.......1.3M...........33.7M...........4%............./cache
/dev/block/mmcblk0p2..1003.6M....330.8M..........672.8M.........33%............/sd-ext <-- May vary
/dev/block/mtdblock3.....269.4M....165.0M..........104.4M.........61%.........../system
/dev/block/mtdblock5.....150.0M.......1.5M..........148.5M...........1%............../data
I hope somebody finds this helpful. I was going to post this is general, but since it is not a question and is directed for developers like myself (and this is where I would look for this info TBH) I posted it here.
Okay guys, have fun

Here is a list of commands you can use in recovery/installation scripts.
[ flash_lock mesg setserial
[[ flash_unlock mkdir setsid
adbd flashcp mkdosfs sh
adjtimex flock mke2fs sha1sum
arp fold mkfifo sha256sum
ash free mkfs.ext2 sha512sum
awk freeramdisk mkfs.vfat sleep
base64 fs mknod sort
basename fsync mkswap split
bbconfig ftpget mktemp stat
bbinstall.sh ftpput modinfo strings
blkid fuser modprobe stty
blockdev getopt more sum
brctl grep mount swapoff
bunzip2 groups mountpoint swapon
busybox gunzip mpstat sync
bzcat gzip mv sysctl
bzip2 halt nanddump tac
cal head nandwrite tail
cat hexdump nbd-client tar
catv htcbatt nc taskset
chattr htcdumlock netstat teamwin
chgrp id nice tee
chmod ifconfig nohup telnet
choice_fn insmod nslookup telnetd
chown install ntpd test
chroot iostat od tftp
clear ip offmode_charging tftpd
cmp kill parted time
comm killall patch timeout
cp killall5 pgrep top
cpio less pidof touch
crond libbmlutils.so pigz tr
crontab libc.so ping traceroute
cut libcutils.so pipe_progress true
date libdl.so pkill ttysize
dc libext2_blkid.so pmap tune2fs
dd libext2_com_err.so power_test ueventd
depmod libext2_e2p.so poweroff umount
detect_key libext2_profile.so printenv uname
devmem libext2_uuid.so printf uncompress
df libext2fs.so ps unexpand
diff libflashutils.so pstree uniq
dirname liblog.so pwd unix2dos
dmesg libm.so pwdx unlzma
dnsd libmmcutils.so rdev unlzop
dos2unix libstdc++.so readlink unpigz
du libstlport.so realpath unxz
dump_image libz.so reboot unzip
e2fsck linker recovery uptime
echo ln renice usleep
ed losetup reset uudecode
egrep ls resize uuencode
env lsattr rev vi
erase_image lsmod rm watch
expand lsof rmdir wc
expr lsusb rmmod wget
false lzcat route which
fbsplash lzma run-parts whoami
fdisk lzop rx xargs
fgrep lzopcat sdparted xz
find man sed xzcat
fix_permissions.sh md5check.sh seq yes
flash_image md5sum setconsole zcat

Looking For DEV To Help Port CWM For LG Optimus Elite

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

Metasploit console on ADB without chroot, working!

Well I've been working on getting the Kali Linux toolkit to run on Android without a chroot and I did it, just gotta mount all the subfiletree's or whatever to where they belong in Androids root dir ,"/" (NOT "/root") and set up the paths in the enviroment a it seems to be working.
I spent way more time researching and planning out exactly how I was going to exicute this, it still has some kinks as some of the filesystems clash or have files of the same name but with slightly moified content, I guess I gotta dig through all those and patch em up so it all flows together, I just ran on the presumtion that it was all compiled for arm and I think it all runs on the android kernel when you chroot into an img file. I basically just mounted the kali.img file and instead of chrooting into that I went backwords and moved everything into Androids root.
Im working on a script with sanity checks and error collection and all that, I am still learning bash, linux, kernel, android, all like a summer cram session so please forgive me if I dont know or it takes time to share something I think is even slightly worthy for ya'll.
Anyways for those interested here is a bit of the tail end of what all this research has become, I think metasploit uses ruby, so if msf is working I guess that is too... here it is
Code:
localhost etc # ls
CHANGELOG-CM.txt gps.conf ppp
CHANGES.txt hosts recovery-resource.dat
NOTICE.html.gz init.d security
apns-conf.xml init.goldfish.sh snd_soc_msm
audio_effects.conf init.qcom.efs.sync.sh ssh
audio_policy.conf init.qcom.mdm_links.sh system_fonts.xml
bash init.qcom.modem_links.sh terminfo
bluetooth init.qcom.post_boot.sh thermald-8064.conf
boot_fixup init.qcom.thermal_conf.sh thermald-8930.conf
build-manifest.xml media_codecs.xml thermald-8960.conf
dbus.conf media_profiles.xml thermald.conf
dhcpcd mkshrc vold.fstab
event-log-tags nano wifi
fallback_fonts.xml nfcee_access.xml
firmware permissions
localhost / # mount --rbind $subset/etc /etc
localhost / # which apt-get
/usr/bin/apt-get
localhost / # which mfsconsole
localhost / # which msfconsole
/usr/bin/msfconsole
localhost / # msfconsole
IIIIII dTb.dTb _.---._
II 4' v 'B .'"".'/|\`.""'.
II 6. .P : .' / | \ `. :
II 'T;. .;P' '.' / | \ `.'
II 'T; ;P' `. / | \ .'
IIIIII 'YvP' `-.__|__.-'
I love shells --egypt
Easy phishing: Set up email templates, landing pages and listeners
in Metasploit Pro's wizard -- type 'go_pro' to launch it now.
=[ metasploit v4.7.0-2013071701 [core:4.7 api:1.0]
+ -- --=[ 1131 exploits - 638 auxiliary - 180 post
+ -- --=[ 309 payloads - 30 encoders - 8 nops
stty: standard input: Bad file number
msf > exit
localhost / # ls
acct init.trace.rc
bin init.usb.rc
cache initlogo.rle
charger lib
config lpm.rc
d media
data mnt
default.prop opt
dev persist
efs proc
etc res
extSdCard root
firmware run
fstab.qcom sbin
init sdcard
init.cm.rc srv
init.goldfish.rc storage
init.qcom.class_core.sh sys
init.qcom.class_main.sh system
init.qcom.early_boot.sh tmp
init.qcom.lpm_boot.sh tombstones
init.qcom.rc ueventd.goldfish.rc
init.qcom.sh ueventd.qcom.rc
init.qcom.syspart_fixup.sh ueventd.rc
init.qcom.usb.rc usbdisk0
init.qcom.usb.sh usr
init.rc var
init.recovery.qcom.rc vendor
init.target.rc
localhost / # exit
exit
[email protected]:/ #
EDIT: Please note that to get this working I had to "su -c bash" so that some of the mount commands would work properly, this is why is says "localhost / #" and not "[email protected]:/ #", its bash and thats the same interpreter the normal chroot throws you into. This is bash from Androids / directory.

My kind of thinker. I'll have to look into this!
Sent from my SPH-L710 using xda app-developers app

Haven't gotten time to try out your mod yet but thought I'd let you know I did get Kali Linux installed on my GS3 and metasploit runs relatively well ssh'ing through terminal!
Sent from my SPH-L710 using xda app-developers app

Mac Address Getting Reset on Reboot

I wiped /data/misc/ to get out of a recovery bootloop. Turns out that doing so breaks the wifi mac address in CM. I'm able to temporarily set my address in /data/wifi/misc/config:
Code:
echo "cur_etheraddr=XX:XX:XX:XX:XX:XX" > /data/misc/wifi/config
The problem is that when I reboot, that file goes back to 00:00:00:00:00:00.
Digging around CM kernel source showed me what files are important.
Code:
CONFIG_BCMDHD_FW_PATH="/system/etc/firmware/fw_bcmdhd.bin"
CONFIG_BCMDHD_NVRAM_PATH="/system/etc/wifi/bcmdhd.cal"
CONFIG_BCMDHD_CONFIG_PATH="/data/misc/wifi/config"
/system/etc/wifi/bcmdhd.cal is showing a good mac address.
I KDZ'ed back to stock and everything worked great there. As soon as I flashed CM14.1 again it didn't work. It isn't a problem with the build, since it was working until I wiped /data/misc/.
Does anyone know how to fix this? I'm curious what config says on a working device, so could someone tell me what it says for them? I want to know 1) if /data/misc/wifi/config exists and 2) if it shows a real mac address or a bunch of zeros. I can't get CM file manager to open the file, so here's how to do it in adb:
Code:
adb shell "su 0 cat '/data/misc/wifi/config'"
What files are in /data/misc/wifi?
I'm not really looking for a workaround, since I could add that first script to a startup script or something. I want a permanent fix that won't go away next time I flash a rom.
Sorry for the long post. Any help would be appreciated. I've spend hours on this already.

Hi!
I also use your workaround now and i automated it, so thanks for ending my pain for the moment, but i would also like to see a permanent fix for this. I tried every available stock rom and all available methods to aply it to bring back what cm seams to be depending on for setting the mac - but no success. To me this looks like a bug - not a very common one, but still a bug because the stock roms do not have any problem at all, only cm does.
br, Martin

theprogramguy said:
Does anyone know how to fix this? I'm curious what config says on a working device, so could someone tell me what it says for them? I want to know 1) if /data/misc/wifi/config exists and 2) if it shows a real mac address or a bunch of zeros.
.
Click to expand...
Click to collapse
I am on RR ROM which is CM based
What I can say is yes this file exists and yes it contains my real MAC address
theprogramguy said:
What files are in /data/misc/wifi?
.
Click to expand...
Click to collapse
[email protected]:/ # ls -la /data/misc/wifi
total 152
drwxrwx--- 4 wifi wifi 4096 2016-12-14 08:12 .
drwxrwx--t 32 system misc 4096 2016-12-04 19:44 ..
-rw-r--r-- 1 system wifi 32 2015-01-02 02:58 config
-rw-rw---- 1 system wifi 21 2015-01-22 07:44 entropy.bin
-rw-rw---- 1 system wifi 252 2016-11-17 15:05 hostapd.conf
-rw------- 1 system system 868 2016-11-14 08:33 ipconfig.txt
-rw------- 1 system system 29695 2016-12-13 11:04 networkHistory.txt
-rw-rw---- 1 wifi wifi 219 2015-01-22 07:44 p2p_supplicant.conf
drwxrwx--- 2 wifi wifi 4096 2015-01-22 07:44 sockets
-rw------- 1 system system 41 2016-11-17 14:54 softap.conf
drwxrwx--- 2 wifi wifi 4096 2015-01-02 02:58 wpa_supplicant
-rw-rw---- 1 wifi wifi 1647 2016-12-14 08:12 wpa_supplicant.conf
[email protected]:/ #
My first thought was that the mac address is generated from the misc partition but as far as I can see it seems to be not. At least I can't find a string matching my current mac.
interesting is that I searched the misc partition (I love Linux and the tool strings) and found my imei written in there..
Well as you wrote you haven't the problem on stock:
Do you cleaned out the WiFi config file before when testing stock? Afaik it should be cleaned out automatically though but just to be sure.. What happens when you delete that file on stock and reboot? Will it get regenerated?
You identified it that the ROM sources are the reason good. But I don't think you should look at the kernel sources only. Check the CM sources as well I believe here you will get better findings.
.

steadfasterX said:
[email protected]:/ # ls -la /data/misc/wifi
total 152
drwxrwx--- 4 wifi wifi 4096 2016-12-14 08:12 .
drwxrwx--t 32 system misc 4096 2016-12-04 19:44 ..
-rw-r--r-- 1 system wifi 32 2015-01-02 02:58 config
-rw-rw---- 1 system wifi 21 2015-01-22 07:44 entropy.bin
-rw-rw---- 1 system wifi 252 2016-11-17 15:05 hostapd.conf
-rw------- 1 system system 868 2016-11-14 08:33 ipconfig.txt
-rw------- 1 system system 29695 2016-12-13 11:04 networkHistory.txt
-rw-rw---- 1 wifi wifi 219 2015-01-22 07:44 p2p_supplicant.conf
drwxrwx--- 2 wifi wifi 4096 2015-01-22 07:44 sockets
-rw------- 1 system system 41 2016-11-17 14:54 softap.conf
drwxrwx--- 2 wifi wifi 4096 2015-01-02 02:58 wpa_supplicant
-rw-rw---- 1 wifi wifi 1647 2016-12-14 08:12 wpa_supplicant.conf
[email protected]:/ #
Click to expand...
Click to collapse
Here's mine. It seems practically the same just missing hostapd.conf. I think I've seen it here before though.
h811:/ # ls -la /data/misc/wifi
total 44
drwxrwx--- 4 wifi wifi 4096 2016-12-14 17:07 .
drwxrwx--t 39 system misc 4096 2014-12-31 19:21 ..
-rw-r--r-- 1 system wifi 32 2016-12-12 18:32 config
-rw-rw---- 1 system wifi 21 2016-12-13 03:15 entropy.bin
-rw------- 1 system system 166 2016-12-13 03:25 ipconfig.txt
-rw------- 1 system system 3814 2016-12-14 17:07 networkHistory.txt
-rw-rw---- 1 wifi wifi 237 2014-12-31 19:26 p2p_supplicant.conf
drwxrwx--- 2 wifi wifi 4096 2016-12-13 03:15 sockets
-rw------- 1 system system 49 2014-12-31 19:25 softap.conf
drwxrwx--- 2 wifi wifi 4096 2014-12-31 19:21 wpa_supplicant
-rw-rw---- 1 wifi wifi 949 2016-12-14 17:07 wpa_supplicant.conf
steadfasterX said:
My first thought was that the mac address is generated from the misc partition but as far as I can see it seems to be not. At least I can't find a string matching my current mac.
Click to expand...
Click to collapse
Maybe it matches the mac in /system/etc/wifi/bcmdhd.cal (macaddr=)? I found that I had a slightly different one there.
steadfasterX said:
You identified it that the ROM sources are the reason good. But I don't think you should look at the kernel sources only. Check the CM sources as well I believe here you will get better findings.
Click to expand...
Click to collapse
https://github.com/CyanogenMod/android_device_lge_g4-common/blob/cm-14.1/hwaddrs/getmac.c
I found this earlier and it shows CM mounting misc and doing something with /data/misc/wifi/config. I thought it was reading config, but it looks like it's actually writing it there after reading it from somewhere else in misc. That would explain why it gets reset. Do you understand where it's reading from? I'm having a hard time reading C.
Specifically this part:
Code:
int fd1, fd2;
char macbyte;
char macbuf[3];
int i;
fd1 = open("/dev/block/bootdevice/by-name/misc",O_RDONLY);
fd2 = open("/data/misc/wifi/config",O_WRONLY|O_CREAT|O_TRUNC,S_IRUSR|S_IWUSR|S_IRGRP|S_IROTH);
write(fd2,"cur_etheraddr=",14);
for (i = 0; i<6; i++) {
lseek(fd1,0x3000+i,SEEK_SET);
lseek(fd2,0,SEEK_END);
read(fd1,&macbyte,1);
sprintf(macbuf,"%02x",macbyte);
write(fd2,&macbuf,2);
if (i!=5) write(fd2,":",1);
}
It looks like our bluetooth mac is getting set in the same way later on.
I'm thinking about setting up a CM build environment again and playing with my own builds to try to see what's up.
steadfasterX said:
interesting is that I searched the misc partition (I love Linux and the tool strings) and found my imei written in there..
Click to expand...
Click to collapse
Nice. I just looked at what CM is reporting my IMEI as, to see if it got reset, but it looks good. I know that cell data is still working, so I'd expect my IMEI to be right.
steadfasterX said:
Well as you wrote you haven't the problem on stock:
Do you cleaned out the WiFi config file before when testing stock? Afaik it should be cleaned out automatically though but just to be sure.. What happens when you delete that file on stock and reboot? Will it get regenerated?
Click to expand...
Click to collapse
I didn't try that. I was in a hurry to get back to CM so I could set it up for daily use. I'll try doing stuff like that soon if we don't figure have anything else to go on. It's getting too late to do it here tonight.
Yesterday I tried to extract misc.img from the kdz but none of the tools I found were able to successfully do it. Something was corrupt. My plan was to look at it or flash it in fastboot and see if anything changes.

GOT IT!
It's actually pretty simple, but I've never done anything quite like this before.
Overview:
Make an img of misc
Edit it in a hex editor
Overwrite misc with the img
Reboot
You could do this entirely on your phone, but I'll walk you through doing it using adb on your computer.
1. Make an img of misc and pull it to your computer.
Code:
adb shell "su -c 'dd if=/dev/block/bootdevice/by-name/misc of=/sdcard/misc.img'"
adb pull /sdcard/misc.img
2. Edit misc.img in a hex editor (I used HexEdit on Windows)
Find the hex offset 3000. Now edit 3000-3005 with your wifi mac address. For example "00 90 3D F1 A2 31".
The bluetooth mac address appears to be stored at 4000, so you could set it there if you wanted/needed to.
3. Write the img
Code:
adb push misc.img /sdcard/misc_edited.img
adb shell "su -c 'dd if=/sdcard/misc_edited.img of=/dev/block/bootdevice/by-name/misc'"
4. Reboot
Code:
adb reboot
If it all works, it's okay to delete the img files we left in /sdcard
Code:
adb shell "rm /sdcard/misc*.img"

Makes totally sense! Just for your information the file in
/system/etc/wifi/bcmdhd.cal
contains a mac address but it is not the same as in the Wi-Fi config file
Thanks for sharing this walkthrough it will help others having the same issue

Thank you!!
You are a MF genius!!! I have the same problem but with an LG G3 Beat, and I wanted to know if this works the same with my device. Thank you bro!