11-09-2011 09:29 PM
64 123
tools
  1. takehull's Avatar
    Thanks to getinowmarketing over at Android Forums, we now have a custom recovery made specifically for this device. In order for some of the USB functions to work, I had to reinstall the drivers for the phone. I take no credit what so ever for this, I'm just compiling info for everyone here.

    Instructions: Re-installing drivers:
    1) Have the USB cord already plugged in, but don't have the phone connected.
    2) Download and install drivers found here.
    3) After the instillation is done, reconnect the phone and allow for the drivers to reinstall. All USB functions(ADB, USB Mass Storage) should be functional on all Windows OS's(don't know about Linux or Mac)

    Materials: Custom Recovery
    Android SDK for Windows, found here.
    or you can enter the codes in an emulator on your phone.
    The custom recovery found here.
    flash_image which can be found at the end of the first post here.

    Instructions, Custom Recovery:
    Please read before proceeding. It is important to follow correctly and completely
    1) Download the custom recovery and flash_image, and extract each file to the root of your sdcard
    2)Start and adb shell, or open up a terminal emulator on your phone
    3)Enter the following codes:
    su
    mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
    cat /sdcard/flash_image > /system/bin/flash_image
    chmod 755 /system/bin/flash_image
    mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system
    flash_image recovery /sdcard/recovery-thunderc-v-1.2.0-GNM.img
    reboot recovery

    You should then reboot into the custom recovery built just for the Optimus V. The button mapping issue, as well as USB functions have been fixed with this. Also, never flash a radio through recovery, unless you want to brick your phone.

    For a complete rundown of everything that this recovery can do, and to go thank getitnowmarketing, go here.
    02-06-2011 10:58 PM
  2. Franzferdinan51's Avatar
    I'll test give time to flash and back up I'll report back soon

    Sent from my VM670 using Tapatalk
    02-06-2011 11:30 PM
  3. takehull's Avatar
    I'll test give time to flash and back up I'll report back soon

    Sent from my VM670 using Tapatalk
    This should work, I personally have tested it. I didn't develop it...

    Just provided the dumps for it, is all.
    02-06-2011 11:42 PM
  4. greenmonster's Avatar
    Is there a typo in this line: "flash_image /recovery"? Should it it be recovery and not /recovery?
    02-06-2011 11:46 PM
  5. takehull's Avatar
    Is there a typo in this line: "flash_image /recovery"? Should it it be recovery and not /recovery?
    Fixed
    02-06-2011 11:48 PM
  6. Franzferdinan51's Avatar
    yeah their WAS a typo this is confirmed working with me


    USB-MS toggle dont work tho same with mounting the SD card from recovery
    02-06-2011 11:54 PM
  7. takehull's Avatar
    yeah their WAS a typo this is confirmed working with me


    USB-MS toggle dont work tho same with mounting the SD card from recovery
    What OS?

    Did you reinstall the USB drivers?

    Also, have you flashed a custom recovery?
    02-06-2011 11:56 PM
  8. gfurr24's Avatar
    Had an issue with this version not recognizing certain .zip files on my sdcard. The file was the 1.1 Rodimus update.zip file. It would show up on the Optimus S 1.1.0 recovery but for some reason it wont show up on 1.2.0 for the V. Kinda wierd and im not sure why. I flashed back to the S 1.1.0 recovery and the files show up again. Has anyone else had that issue?
    02-07-2011 05:49 PM
  9. Franzferdinan51's Avatar
    yes i have im on Froyo 2.2 when i did it yes i did reinstall the drivers
    02-07-2011 07:18 PM
  10. Lenoh's Avatar
    Had an issue with this version not recognizing certain .zip files on my sdcard. The file was the 1.1 Rodimus update.zip file. It would show up on the Optimus S 1.1.0 recovery but for some reason it wont show up on 1.2.0 for the V. Kinda wierd and im not sure why. I flashed back to the S 1.1.0 recovery and the files show up again. Has anyone else had that issue?
    I initially placed the zip files in the root folder, but was not able to see them. I read somewhere that people create a folder named " Roms" or "Rom Folder" or something like that to place their rom files. I made a folder on the root of sd card Rom Folder, placed the RodimusROM inside, reboot to recovery, navigate to folder and voila, I have the rodimus rom.

    Thanks takehull for bringing the info here.
    02-07-2011 11:35 PM
  11. takehull's Avatar
    I initially placed the zip files in the root folder, but was not able to see them. I read somewhere that people create a folder named " Roms" or "Rom Folder" or something like that to place their rom files. I made a folder on the root of sd card Rom Folder, placed the RodimusROM inside, reboot to recovery, navigate to folder and voila, I have the rodimus rom.

    Thanks takehull for bringing the info here.
    Thank you for explaining this while I was at work
    02-07-2011 11:40 PM
  12. RevolutionRed's Avatar
    Any chance of getting this thread stickied mods? It'd be nice have this and the thread on how to restore to stock at the top where people can see them.
    02-08-2011 03:52 PM
  13. idbl_fanatic's Avatar
    Where does this store the backups?
    02-10-2011 05:50 PM
  14. r00t's Avatar
    Thanks takehull, everything went well. Can you add the saving procedures as well, I almost didn't backup.
    02-11-2011 08:17 AM
  15. takehull's Avatar
    Where does this store the backups?
    In a folder on the sdcard. I will check and edit it in here.

    The folder is named nandroid. The.backups are saved in a subfolder.


    Sent from my VM670 using Tapatalk
    02-11-2011 04:03 PM
  16. completetech's Avatar
    getting error of invalid length on
    cat /sdcard/flash_image > /system/bin/flash_image

    any ideas?
    02-12-2011 04:33 PM
  17. r00t's Avatar
    Any chance of getting this thread stickied mods? It'd be nice have this and the thread on how to restore to stock at the top where people can see them.
    Definitely agree, this thread should be pinned.
    02-13-2011 02:52 PM
  18. Devcomm's Avatar
    Hey guys, active member on a few other forums related to Android and the Optimus V, but this seems to be my best bet to get some help with my issue. If not, and you could direct me somewhere better that would be awesome. Here is the outline:

    Flashing seems to have completed, but when I reboot to recovery from adb I get a blue screen that says:

    Fastboot mode started
    gpio_i2c: invalid khz: 0
    bl: i2c write error
    udc_start()
    -- suspend --
    -- reset --
    -- portchange --
    -- reset --
    -- portchange --
    STALL GET_DESCRIPTOR 128 6 1006 0 18
    fastboot: processing commands

    and it just stays there. Buttons do nothing.

    I pulled the battery and tried to manually enter recovery and I get the same blue screen but now it says:

    Fastboot mode started
    udc_start()

    and it stops.

    I also had the error when attempting to rename the recoveryinstall.sh file but read to just move on if this happens. Could that have any affect?

    Any insight on what the problem is would be very much appreciated. I reflashed the stock recovery and it works fine for now, but would very much like to get this custom one working.
    02-14-2011 12:48 AM
  19. idbl_fanatic's Avatar
    In a folder on the sdcard. I will check and edit it in here.

    The folder is named nandroid. The.backups are saved in a subfolder.


    Sent from my VM670 using Tapatalk
    Thank you!!
    02-15-2011 09:55 AM
  20. denshigomi's Avatar
    I want to be able to revert to the stock recovery. Please let me know if I'm doing anything wrong or if there's a preferred method over what I am suggesting:
    • backup stock recovery
      1. root phone
      2. launch adb shell
      3. cat /proc/mtd
        dev: size erasesize name
        mtd0: 00700000 00020000 "boot"
        mtd1: 06e20000 00020000 "cache"
        mtd2: 00700000 00020000 "recovery"
        mtd3: 00140000 00020000 "splash"
        mtd4: 00100000 00020000 "FOTA_STO"
        mtd5: 0a480000 00020000 "system"
        mtd6: 0b2e0000 00020000 "userdata"
        mtd7: 00080000 00020000 "misc"
        mtd8: 00180000 00020000 "persist"
      4. (recovery is located on mtd2)
      5. cat /dev/mtd/mtd2 > /sdcard/stock-recovery.img
      6. stock recovery backup is complete
    • flash custom recovery from this thread
    • flash stock recovery
      1. root phone
      2. launch adb shell
      3. mount -o remount,rw -t yaffs2 /system /system
      4. cat /sdcard/flash_image > /system/bin/flash_image
      5. chmod 755 /system/bin/flash_image
      6. mount -o remount,ro -t yaffs2 /system /system
      7. flash_image recovery /sdcard/stock-recovery.img
      8. reboot recovery


    Does this correctly backup and flash the stock recovery?
    Thank you for your time.
    02-16-2011 04:10 AM
  21. santino405's Avatar
    i hope so, a true vm stock recovery would be nice, the one thats floating around the fourms is the sprint one, which works fine but will probably cause issues if theres ever an update sent our way.
    02-16-2011 10:02 AM
  22. takehull's Avatar
    The recovery.img in my stock package was pulled straight from my Optimums V.

    Sent from my VM670 using Tapatalk
    02-16-2011 11:25 AM
  23. santino405's Avatar
    really? i assumed it was a sprint one since the menu and home buttons where swaped around.
    02-16-2011 10:22 PM
  24. takehull's Avatar
    really? i assumed it was a sprint one since the menu and home buttons where swaped around.
    They aren't switched. The stock recovery uses the "home" button as the trigger. The custom recovery uses the "menu" button.
    02-16-2011 11:39 PM
  25. takehull's Avatar
    I want to be able to revert to the stock recovery. Please let me know if I'm doing anything wrong or if there's a preferred method over what I am suggesting:
    • backup stock recovery
      1. root phone
      2. launch adb shell
      3. cat /proc/mtd
        dev: size erasesize name
        mtd0: 00700000 00020000 "boot"
        mtd1: 06e20000 00020000 "cache"
        mtd2: 00700000 00020000 "recovery"
        mtd3: 00140000 00020000 "splash"
        mtd4: 00100000 00020000 "FOTA_STO"
        mtd5: 0a480000 00020000 "system"
        mtd6: 0b2e0000 00020000 "userdata"
        mtd7: 00080000 00020000 "misc"
        mtd8: 00180000 00020000 "persist"
      4. (recovery is located on mtd2)
      5. cat /dev/mtd/mtd2 > /sdcard/stock-recovery.img
      6. stock recovery backup is complete
    • flash custom recovery from this thread
    • flash stock recovery
      1. root phone
      2. launch adb shell
      3. mount -o remount,rw -t yaffs2 /system /system
      4. cat /sdcard/flash_image > /system/bin/flash_image
      5. chmod 755 /system/bin/flash_image
      6. mount -o remount,ro -t yaffs2 /system /system
      7. flash_image recovery /sdcard/stock-recovery.img
      8. reboot recovery


    Does this correctly backup and flash the stock recovery?
    Thank you for your time.

    That should work.
    That is what I did to pull the stock recovery.img from my phone.
    denshigomi likes this.
    02-17-2011 12:33 AM
64 123
LINK TO POST COPIED TO CLIPBOARD