Stuck in CWM recovery. -Without root

[jezzie bumatay]

how about output from

adb shell ls /dev/

you have to wipe mtd8, it's the problem causing the boot loop.

C:\Users\jezzie\Desktop\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-x8
6_64-20130522\sdk\platform-tools>adb shell ls /dev/
adsp msm_amrnb_in smd22 tty34
alarm msm_amrwb smd27 tty35
alps_io msm_audio_dev_ctrl smd36 tty36
android_adb msm_audio_misc smd7 tty37
android_adb_enable msm_camera smd_pkt_loopback tty38
ashmem msm_evrc smd_sns_dsps tty39
binder msm_evrc_in smdcntl0 tty4
block msm_fm smdcntl1 tty40
bma222 msm_mp3 smdcntl2 tty41
chg_logo msm_mp3_lp smdcntl3 tty42
console msm_mvs smdcntl4 tty43
cpu_dma_latency msm_pcm_dec smdcntl5 tty44
device-mapper msm_pcm_in smdcntl6 tty45
diag msm_pcm_lp_dec smdcntl7 tty46
full msm_pcm_out smem_log tty47
gemini0 msm_qcelp snd tty48
graphics msm_qcelp_in socket tty49
i2c-0 msm_rotator tgt tty5
i2c-1 msm_vidc_dec tty tty50
i2c-10 msm_vidc_enc tty0 tty51
i2c-11 msm_vidc_reg tty1 tty52
i2c-12 msm_wma tty10 tty53
i2c-13 msm_wmapro tty11 tty54
i2c-14 network_latency tty12 tty55
i2c-15 network_throughput tty13 tty56
i2c-2 nmea tty14 tty57
i2c-3 null tty15 tty58
i2c-4 oncrpc tty16 tty59
i2c-6 pmem tty17 tty6
i2c-7 pmem_adsp tty18 tty60
i2c-8 pmem_audio tty19 tty61
i2c-9 pn544 tty2 tty62
input ptmx tty20 tty63
keychord pts tty21 tty7
kgsl-2d0 qmi0 tty22 tty8
kgsl-3d0 qmi1 tty23 tty9
kmem qmi2 tty24 ttyGS0
kmsg radio0 tty25 ttyGS1
log random tty26 ttyHS0
mem recovery_mode tty27 ttyMSM1
msm_a2dp_in rfkill tty28 uinput
msm_aac rmt_storage tty29 urandom
msm_aac_in rtc0 tty3 vcs
msm_acdb rtc1 tty30 vcs1
msm_adc sdio_al_test tty31 vcsa
msm_adpcm smd0 tty32 vcsa1
msm_amrnb smd21 tty33 zero

C:\Users\jezzie\Desktop\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-x8
6_64-20130522\sdk\platform-tools>

 

[bigsupersquid]

crud.
your recovery kernel is not mounting devices where I'm used to.
did you say this wasn't an optimus v phone?
it'll take more work to find the device list.

adb shell ls /

 

[jezzie bumatay]

crud.
your recovery kernel is not mounting devices where I'm used to.
did you say this wasn't an optimus v phone?
it'll take more work to find the device list.

adb shell ls /

Its VM Optimus Elite

 

[jezzie bumatay]

C:\Users\jezzie\Desktop\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-x8
6_64-20130522\sdk\platform-tools>adb shell ls /
boot etc sdcard
bootimages init sys
cache init.qcom.sh system
chargerimages init.rc tmp
data proc ueventd.goldfish.rc
default.prop res ueventd.rc
dev root
emmc sbin

C:\Users\jezzie\Desktop\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-x8
6_64-20130522\sdk\platform-tools>

idk if this info would help you but the optimus elite has a built in sdcard.. ive had problems with it downloading stuff into the built in sdcard instead of the _externalsd which is in the sdcard folder which is already in the phone

 

[bigsupersquid]

I don't know the filesystem layout or anything about that phone.
let's see what we can learn

adb shell ls

 

[vector84an]

Different phone means different instructions are going to be needed - though a similar enough LG phone that the general process is the same...

I think the Optimus Elite mounts its main partitions as /dev/block/mmcblk0p0-21 ?
(ref: Looking For DEV To Help Port CWM For LG Optimus Elite - xda-developers)

I recall from the original Xionia thread that "adb shell strings /dev/__device__" should be helpful in figuring out where the flags are... I don't think it would be 6, 12, 13, 14, beyond that, not sure that I can be more specific...



PS: a bit of googling turns up some Optimus Elite communities (some with a few of the same devs that worked on this phone even...) ... you should try asking over there, they might be able to help you with considerably less detective work

 

[jezzie bumatay]

I don't know the filesystem layout or anything about that phone.
let's see what we can learn

adb shell ls

C:\Users\jezzie\Desktop\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-x8
6_64-20130522\sdk\platform-tools>adb shell ls
boot etc sdcard
bootimages init sys
cache init.qcom.sh system
chargerimages init.rc tmp
data proc ueventd.goldfish.rc
default.prop res ueventd.rc
dev root
emmc sbin

C:\Users\jezzie\Desktop\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-x8
6_64-20130522\sdk\platform-tools>

C:\Users\jezzie\Desktop\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-x8
6_64-20130522\sdk\platform-tools>

 

[bigsupersquid]

adb shell mount -o remount,rw / /
adb push flash_eraseall /sbin/
adb shell chmod 755 /sbin/flash_eraseall
adb shell flash_eraseall /dev/block/mmcblk0p5
adb reboot recovery

according to the xda link, mmcblk0p5 is the persist partition.
that's the one that matches mtd8 on the optimus V.
maybe this'll work.

 

[jezzie bumatay]

adb shell mount -o remount,rw / /
adb push flash_eraseall /sbin/
adb shell chmod 755 /sbin/flash_eraseall
adb shell flash_eraseall /dev/block/mmcblk0p5
adb reboot recovery

according to the xda link, mmcblk0p5 is the persist partition.
that's the one that matches mtd8 on the optimus V.
maybe this'll work.

C:\Users\jezzie\Desktop\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-x8
6_64-20130522\sdk\platform-tools>adb shell mount -o remount,rw / /

C:\Users\jezzie\Desktop\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-x8
6_64-20130522\sdk\platform-tools>adb push flash_eraseall /sbin/
3153 KB/s (74273 bytes in 0.023s)

C:\Users\jezzie\Desktop\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-x8
6_64-20130522\sdk\platform-tools>adb shell chmod 755 /sbin/flash_eraseall

C:\Users\jezzie\Desktop\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-x8
6_64-20130522\sdk\platform-tools>adb shell flash_eraseall /dev/block/mmcblk0p5
libmtd: error!: "/dev/block/mmcblk0p5" is not a character device
flash_eraseall: mtd_get_dev_info failed

C:\Users\jezzie\Desktop\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-x8
6_64-20130522\sdk\platform-tools>adb reboot recovery

 

[bigsupersquid]

aha!
since it's an ext4 filesystem instead of mtd, flash_eraseall isn't required.
try this instead.

adb shell cat /dev/zero > dev/block/mmcblk0p5
adb reboot recovery

and, vector84an makes a good point, it's hard to get support for one device in the home forum of another.
Lucky I'm stubborn!

 

[jezzie bumatay]

aha!
since it's an ext4 filesystem instead of mtd, flash_eraseall isn't required.
try this instead.

adb shell cat /dev/zero > dev/block/mmcblk0p5
adb reboot recovery

and, vector84an makes a good point, it's hard to get support for one device in the home forum of another.
Lucky I'm stubborn!

C:\Users\jezzie\Desktop\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-x8
6_64-20130522\sdk\platform-tools>adb shell cat /dev/zero > dev/block/mmcblk0p5
The system cannot find the path specified.

C:\Users\jezzie\Desktop\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-x8
6_64-20130522\sdk\platform-tools>adb reboot recovery

even if u dont get it, thnx for helping.

 

[bigsupersquid]

@&*!@
no /dev/zero
try yet another method.

adb shell ls /sbin/

so I can see what the recovery uses to format the mmcblk partitions.

 

[jezzie bumatay]

@&*!@
no /dev/zero
try yet another method.

adb shell ls /sbin/

so I can see what the recovery uses to format the mmcblk partitions.

C:\Users\jezzie\Desktop\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-x8
6_64-20130522\sdk\platform-tools>adb shell ls /sbin/
[ hexdump rev
[[ id rm
adbd insmod rmdir
ash install rmmod
awk kill rmt_storage
basename killall run-parts
bbconfig killall5 sdparted
blkid killrecovery.sh sed
bootlogo length seq
bunzip2 less setconsole
busybox lge_fota setprop
bzcat ln setserial
bzip2 losetup setsid
cal ls sh
cat lsattr sha1sum
catv lsmod sha256sum
chargerlogo lspci sha512sum
chattr lsusb sleep
chgrp lzcat sort
chmod lzop split
chown lzopcat stat
chroot makedevs strings
cksum md5sum stty
clear minizip swapoff
cmp mkdir swapon
cp mke2fs sync
cpio mke2fs_static sysctl
cut mkfifo tac
date mkfs.ext2 tail
dc mknod tar
dd mkswap tee
dedupe mktemp test
depmod mkyaffs2image time
devmem modinfo top
df modprobe touch
diff more tr
dirname mount true
dmesg mountpoint ttysize
dos2unix mv tune2fs
du nanddump tune2fs_static
dump_image nandroid ueventd
e2fsck nandroid-md5.sh umount
e2fsck_static nandwrite uname
echo nice unexpand
edify nohup uniq
egrep od unix2dos
env parted unlzma
erase_image patch unlzop
expand pgrep unxz
expr pidof unyaffs
false pkill unzip
fdisk postrecoveryboot.sh uptime
fgrep printenv usleep
find printf uudecode
fix_permissions ps uuencode
flash_image pstree volume
fold pwd watch
free rdev wc
freeramdisk readlink which
fuser realpath whoami
getopt reboot xargs
grep recovery xzcat
groups renice yes
gunzip reset zcat
gzip resize
head resize2fs_static

C:\Users\jezzie\Desktop\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-x8
6_64-20130522\sdk\platform-tools>

 

[bigsupersquid]

adb shell busybox mke2fs -t ext4 /dev/block/mmcblk0p5
adb reboot recovery

 

[jezzie bumatay]

C:\Users\jezzie\Desktop\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-x8
6_64-20130522\sdk\platform-tools>adb shell busybox mke2fs -t ext4 /dev/block/mmc
blk0p5
unknown option -- t
BusyBox v1.20.2-cm9 static (2012-07-14 01:52 +0200) multi-call binary.

Usage: mke2fs [-Fn] [-b BLK_SIZE] [-i INODE_RATIO] [-I INODE_SIZE] [-m RESERVED_
PERCENT] [-L LABEL] BLOCKDEV [KBYTES]

-b BLK_SIZE Block size, bytes
-F Force
-i RATIO Max number of files is filesystem_size / RATIO
-I BYTES Inode size (min 128)
-L LBL Volume label
-m PERCENT Percent of blocks to reserve for admin
-n Dry run


C:\Users\jezzie\Desktop\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-x8
6_64-20130522\sdk\platform-tools>adb reboot recovery

 

[bigsupersquid]

adb shell busybox mke2fs /dev/block/mmcblk0p5
adb reboot recovery

kind of a wussy busybox they put in there.

 

[jezzie bumatay]

C:\Users\jezzie\Desktop\adt-bundle-windows-x
6_64-20130522\sdk\platform-tools>adb shell b
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
4096 inodes, 16384 blocks
819 blocks (5%) reserved for the super user
First data block=1
Maximum filesystem blocks=262144
2 block groups
8192 blocks per group, 8192 fragments per gr
2048 inodes per group
Superblock backups stored on blocks:
8193

C:\Users\jezzie\Desktop\adt-bundle-windows-x
6_64-20130522\sdk\platform-tools>adb reboot

 

[bigsupersquid]

is it still bootlooping?
other than clearing the persist partition, since the misc partition doesn't exist on your device, I'm out of information.
Sorry

 

[jezzie bumatay]

yup still looping... should i give up?

 

[bigsupersquid]

don't give up, but you'll have to pester the devs who know what's going on with your device.
without one of those in-hand to test things on, I can't help any more that what I've suggested already.
Trying to format any other partitions could brick you permanently without knowing what's being done internally with them.
or, well, you could clear the cache partition safely to test.

adb shell busybox mke2fs /dev/block/mmcblk0p6
adb reboot recovery

a quick search implies the mpt partition may have LG crud in it too, let those devs know, they can advise whether it's safe to wipe that partition or not.
it's located at /dev/block/mmcblk0p21