08-24-2013 08:15 PM
63 123
tools
  1. bigsupersquid's Avatar
    closer!
    try this.
    Code:
    adb wait-for-device
    adb shell mount -o remount,rw / /
    adb push flash_eraseall /sbin/
    adb shell flash_eraseall /dev/mtd/mtd8
    adb reboot recovery
    the wait-for-device line should take care of the timing issue.
    06-29-2013 11:37 AM
  2. jezzie bumatay's Avatar
    tried the new one and this is what i got

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

    C:\Users\jezzie\Desktop\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-x8
    6_64-20130522\sdk\platform-tools>adb wait-for-device
    * daemon not running. starting it now on port 5037 *
    * daemon started successfully *

    And its still looping
    06-29-2013 11:40 AM
  3. bigsupersquid's Avatar
    push <CTRL><C> to stop adb wait-for-device
    type
    Code:
    adb root
    to restart adb
    and try this again.
    Code:
    adb wait-for-device
    adb shell mount -o remount,rw / /
    adb push flash_eraseall /sbin/
    adb shell flash_eraseall /dev/mtd/mtd8
    adb reboot recovery
    06-29-2013 11:43 AM
  4. vector84an's Avatar
    might need to chmod flash_eraseall after pushing it?

    "adb shell chmod 755 /sbin/flash_eraseall"
    06-29-2013 11:47 AM
  5. bigsupersquid's Avatar
    maybe.
    but I forgot that even in recovery, / is mounted ro.
    and since recovery is all ramdisk, it has to be pushed after every reboot since it won't stick through a reboot.
    06-29-2013 11:48 AM
  6. jezzie bumatay's Avatar
    push <CTRL><C> to stop adb wait-for-device
    type
    Code:
    adb root
    to restart adb
    and try this again.
    Code:
    adb wait-for-device
    adb shell mount -o remount,rw / /
    adb push flash_eraseall /sbin/
    adb shell flash_eraseall /dev/mtd/mtd8
    adb reboot recovery
    it says adbd is already on root then adb doesnt seem to respond after the wait-for-device command
    06-29-2013 11:55 AM
  7. bigsupersquid's Avatar
    ok, you'll have to ditch the wait-for-device command and try to time it right instead.
    Code:
    adb shell mount -o remount,rw / /
    adb push flash_eraseall /sbin/
    adb shell flash_eraseall /dev/mtd/mtd8
    adb reboot recovery
    I was hoping it'd co-operate with the easier way.
    06-29-2013 11:56 AM
  8. jezzie bumatay's Avatar
    ok, you'll have to ditch the wait-for-device command and try to time it right instead.
    Code:
    adb shell mount -o remount,rw / /
    adb push flash_eraseall /sbin/
    adb shell flash_eraseall /dev/mtd/mtd8
    adb reboot recovery
    I was hoping it'd co-operate with the easier way.
    i got this.. dunno why permission is denied

    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/
    1813 KB/s (74273 bytes in 0.040s)

    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/mtd/mtd8
    /sbin/sh: flash_eraseall: Permission denied

    C:\Users\jezzie\Desktop\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-x8
    6_64-20130522\sdk\platform-tools>adb reboot recovery
    06-29-2013 12:11 PM
  9. bigsupersquid's Avatar
    ok, vector84an was correct.
    Code:
    adb shell mount -o remount,rw / /
    adb push flash_eraseall /sbin/
    adb shell chmod 755 /sbin/flash_eraseall
    adb shell flash_eraseall /dev/mtd/mtd8
    adb reboot recovery
    it is such a PITA trying to do tech support through the forums, but this way everybody can see how do do things and what can go wrong...

    the flash_eraseall on 4shared wasn't chmod'ed before uploading.
    the attachment in this thread is.
    I'll fix the 4shared upload but its link will probably change.
    06-29-2013 12:13 PM
  10. jezzie bumatay's Avatar
    ok, vector84an was correct.
    Code:
    adb shell mount -o remount,rw / /
    adb push flash_eraseall /sbin/
    adb shell chmod 755 /sbin/flash_eraseall
    adb shell flash_eraseall /dev/mtd/mtd8
    adb reboot recovery
    it is such a PITA trying to do tech support through the forums, but this way everybody can see how do do things and what can go wrong...

    the flash_eraseall on 4shared wasn't chmod'ed before uploading.
    the attachment in this thread is.
    I'll fix the 4shared upload but its link will probably change.
    got /dev/mtd/mtd8: no such file directory this
    time
    06-29-2013 12:22 PM
  11. jezzie bumatay's Avatar
    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/
    3296 KB/s (74273 bytes in 0.022s)

    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/mtd/mtd8
    flash_eraseall: /dev/mtd/mtd8: No such file or directory

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

    C:\Users\jezzie\Desktop\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-x8
    6_64-20130522\sdk\platform-tools>
    06-29-2013 12:27 PM
  12. jezzie bumatay's Avatar
    And again your android wizardry is much appreciated.. learning sooo much!! lol
    06-29-2013 12:28 PM
  13. bigsupersquid's Avatar
    what is the output from
    Code:
    adb shell ls /dev/mtd
    06-29-2013 12:30 PM
  14. jezzie bumatay's Avatar
    what is the output from
    Code:
    adb shell ls /dev/mtd
    should i try it w/o the /mtd8??
    either way it says no such file directory
    06-29-2013 12:32 PM
  15. bigsupersquid's Avatar
    how about output from
    Code:
    adb shell ls /dev/
    you have to wipe mtd8, it's the problem causing the boot loop.
    06-29-2013 12:41 PM
  16. jezzie bumatay's Avatar
    how about output from
    Code:
    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>
    06-29-2013 12:48 PM
  17. bigsupersquid's Avatar
    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.
    Code:
    adb shell ls /
    06-29-2013 12:53 PM
  18. jezzie bumatay's Avatar
    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.
    Code:
    adb shell ls /
    Its VM Optimus Elite
    06-29-2013 12:55 PM
  19. jezzie bumatay's Avatar
    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
    06-29-2013 12:59 PM
  20. bigsupersquid's Avatar
    I don't know the filesystem layout or anything about that phone.
    let's see what we can learn
    Code:
    adb shell ls
    06-29-2013 01:05 PM
  21. vector84an's Avatar
    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
    bigsupersquid likes this.
    06-29-2013 01:08 PM
  22. jezzie bumatay's Avatar
    I don't know the filesystem layout or anything about that phone.
    let's see what we can learn
    Code:
    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>
    06-29-2013 01:17 PM
  23. bigsupersquid's Avatar
    Code:
    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.
    06-29-2013 01:18 PM
  24. jezzie bumatay's Avatar
    Code:
    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
    06-29-2013 01:27 PM
  25. bigsupersquid's Avatar
    aha!
    since it's an ext4 filesystem instead of mtd, flash_eraseall isn't required.
    try this instead.
    Code:
    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!
    06-29-2013 01:32 PM
63 123
LINK TO POST COPIED TO CLIPBOARD