08-04-2011 08:28 PM
34 12
tools
  1. IP IHI II IL's Avatar
    OK, so a few months ago, I was bored and had done everything I could do to my EVO... I saw my Girlfriend's phone laying around, and (as a favor to HER, of course) rooted it, and flashed ThunderRom.

    Long story short, she hates it, and has nothing but problems with the phone since I "helped her".

    I have long searched for an "RUU" but sad to say none exist (that I know of yet). I played with it tonight, as my back is killin' me from sleeping on it. I had a lot of problems running ADB on her Win7 machine (mine died, and not 'cause I did anything to it...lol) so I tried to load a factory dump from the "how to unroot..." thread, and now I'm stuck in a recovery loop of sorts.

    No matter what I do (restore, flash a new ROM, anything) when I reboot or power off, the damn thing goes straight to recovery.

    Ultimately, I want this thing back to stock, but don't have ADB available. I need a tool that will return the phone back to stock, or an update.zip or a better nand dump, or $50 to get her a new Optimus S, or an act of god...etc...

    Can anyone help me? Can I help myself? Please, any help anyone can provide would dub you an official hero!

    Thanks in advance!
    04-11-2011 04:58 AM
  2. tirith's Avatar
    No access to adb? what is the problem there? The largest problem most people have is driver recognition... Especially on win 7
    04-11-2011 05:38 AM
  3. IP IHI II IL's Avatar
    I'm not sure, really... Not very used to, nor do I like Win7...

    I get:
    'C:\' is not recognized as an internal or external command,
    operable program or batch file.

    replace C:\ with any other path, same problem...
    04-11-2011 05:44 AM
  4. tirith's Avatar
    Cd is a key function, cd meaning change directory. Try cd c:\

    I know on older win os's you didn't need cd to change to c:
    04-11-2011 05:51 AM
  5. IP IHI II IL's Avatar
    that worked, thank you, but I can't get anything else working. None of the other commands work, since the phone's stuck in recovery... Looks like I'm gonna' have to unroot the EVO and give it to her 'til I get this working.

    SO FRUSTRATED! Can't wait 'til the EVO 3D is released, and we can afford it so i can just give her my EVO, so that we'll both have phones I can fix if I F it up...lol
    04-11-2011 06:07 AM
  6. tirith's Avatar
    Downloaded sdk tools? In win 7,

    from cmd.exe on c:
    Cd program files (c86)
    Cd android
    CD android-sdk
    Cd platform-tools

    Type "adb devices" with your phone plugged in

    tell me what you see. Might be a min for a reply ... I'm driving

    Swyped from my g-breaded optimus prime.
    04-11-2011 06:11 AM
  7. IP IHI II IL's Avatar
    some of those commands didn't work, but I think I got to where I needed to be...

    Came up with:
    c:\Android\android-sdk-windows\platform-tools>adb devices
    List of devices attached
    A000002846CAAB recovery


    c:\Android\android-sdk-windows\platform-tools>

    This is all new to me, so 1) you're well on your way to gaining a comic with your name on it, 2) THANK YOU! and 3) please don't help me while driving, I don't want anyone tracking me down to avenge your injuries or worse...lol

    THANK YOU!

    Here's everything I've done in CMD so far:


    c:\>Android\android-sdk-windows\platform-tools\adb
    Android Debug Bridge version 1.0.26

    -d - directs command to the only connected USB devic
    e
    returns an error if more than one USB device is
    present.
    -e - directs command to the only running emulator.
    returns an error if more than one emulator is r
    unning.
    -s <serial number> - directs command to the USB device or emulator w
    ith
    the given serial number. Overrides ANDROID_SERI
    AL
    environment variable.
    -p <product name or path> - simple product name like 'sooner', or
    a relative/absolute path to a product
    out directory like 'out/target/product/sooner'.

    If -p is not specified, the ANDROID_PRODUCT_OUT

    environment variable is used, which must
    be an absolute path.
    devices - list all connected devices
    connect <host>[:<port>] - connect to a device via TCP/IP
    Port 5555 is used by default if no port number
    is specified.
    disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
    Port 5555 is used by default if no port number
    is specified.
    Using this ocmmand with no additional arguments

    will disconnect from all connected TCP/IP devic
    es.

    device commands:
    adb push <local> <remote> - copy file/dir to device
    adb pull <remote> [<local>] - copy file/dir from device
    adb sync [ <directory> ] - copy host->device only if changed
    (-l means list but don't copy)
    (see 'adb help all')
    adb shell - run remote shell interactively
    adb shell <command> - run remote shell command
    adb emu <command> - run emulator console command
    adb logcat [ <filter-spec> ] - View device log
    adb forward <local> <remote> - forward socket connections
    forward specs are one of:
    tcp:<port>
    localabstract:<unix domain socket name>
    localreserved:<unix domain socket name>
    localfilesystem:<unix domain socket name>
    dev:<character device name>
    jdwp:<process pid> (remote only)
    adb jdwp - list PIDs of processes hosting a JDWP transport

    adb install [-l] [-r] [-s] <file> - push this package file to the device and i
    nstall it
    ('-l' means forward-lock the app)
    ('-r' means reinstall the app, keeping its data
    )
    ('-s' means install on SD card instead of inter
    nal storage)
    adb uninstall [-k] <package> - remove this app package from the device
    ('-k' means keep the data and cache directories
    )
    adb bugreport - return all information from the device
    that should be included in a bug report.

    adb help - show this help message
    adb version - show version num

    DATAOPTS:
    (no option) - don't touch the data partition
    -w - wipe the data partition
    -d - flash the data partition

    scripting:
    adb wait-for-device - block until device is online
    adb start-server - ensure that there is a server running
    adb kill-server - kill the server if it is running
    adb get-state - prints: offline | bootloader | device
    adb get-serialno - prints: <serial-number>
    adb status-window - continuously print device status for a specifie
    d device
    adb remount - remounts the /system partition on the device re
    ad-write
    adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
    tloader or recovery program
    adb reboot-bootloader - reboots the device into the bootloader
    adb root - restarts the adbd daemon with root permissions
    adb usb - restarts the adbd daemon listening on USB
    adb tcpip <port> - restarts the adbd daemon listening on TCP on th
    e specified port
    networking:
    adb ppp <tty> [parameters] - Run PPP over USB.
    Note: you should not automatically start a PPP connection.
    <tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
    [parameters] - Eg. defaultroute debug dump local notty usepeerdns

    adb sync notes: adb sync [ <directory> ]
    <localdir> can be interpreted in several ways:

    - If <directory> is not specified, both /system and /data partitions will be u
    pdated.

    - If it is "system" or "data", only the corresponding partition
    is updated.

    environmental variables:
    ADB_TRACE - Print debug information. A comma separated list
    of the following values
    1 or all, adb, sockets, packets, rwx, usb, sync
    , sysdeps, transport, jdwp
    ANDROID_SERIAL - The serial number to connect to. -s takes prior
    ity over this if given.
    ANDROID_LOG_TAGS - When used with the logcat option, only these de
    bug tags are printed.

    c:\>adb
    'adb' is not recognized as an internal or external command,
    operable program or batch file.

    c:\>Android\android-sdk-windows\platform-tools\adb
    Android Debug Bridge version 1.0.26

    -d - directs command to the only connected USB devic
    e
    returns an error if more than one USB device is
    present.
    -e - directs command to the only running emulator.
    returns an error if more than one emulator is r
    unning.
    -s <serial number> - directs command to the USB device or emulator w
    ith
    the given serial number. Overrides ANDROID_SERI
    AL
    environment variable.
    -p <product name or path> - simple product name like 'sooner', or
    a relative/absolute path to a product
    out directory like 'out/target/product/sooner'.

    If -p is not specified, the ANDROID_PRODUCT_OUT

    environment variable is used, which must
    be an absolute path.
    devices - list all connected devices
    connect <host>[:<port>] - connect to a device via TCP/IP
    Port 5555 is used by default if no port number
    is specified.
    disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
    Port 5555 is used by default if no port number
    is specified.
    Using this ocmmand with no additional arguments

    will disconnect from all connected TCP/IP devic
    es.

    device commands:
    adb push <local> <remote> - copy file/dir to device
    adb pull <remote> [<local>] - copy file/dir from device
    adb sync [ <directory> ] - copy host->device only if changed
    (-l means list but don't copy)
    (see 'adb help all')
    adb shell - run remote shell interactively
    adb shell <command> - run remote shell command
    adb emu <command> - run emulator console command
    adb logcat [ <filter-spec> ] - View device log
    adb forward <local> <remote> - forward socket connections
    forward specs are one of:
    tcp:<port>
    localabstract:<unix domain socket name>
    localreserved:<unix domain socket name>
    localfilesystem:<unix domain socket name>
    dev:<character device name>
    jdwp:<process pid> (remote only)
    adb jdwp - list PIDs of processes hosting a JDWP transport

    adb install [-l] [-r] [-s] <file> - push this package file to the device and i
    nstall it
    ('-l' means forward-lock the app)
    ('-r' means reinstall the app, keeping its data
    )
    ('-s' means install on SD card instead of inter
    nal storage)
    adb uninstall [-k] <package> - remove this app package from the device
    ('-k' means keep the data and cache directories
    )
    adb bugreport - return all information from the device
    that should be included in a bug report.

    adb help - show this help message
    adb version - show version num

    DATAOPTS:
    (no option) - don't touch the data partition
    -w - wipe the data partition
    -d - flash the data partition

    scripting:
    adb wait-for-device - block until device is online
    adb start-server - ensure that there is a server running
    adb kill-server - kill the server if it is running
    adb get-state - prints: offline | bootloader | device
    adb get-serialno - prints: <serial-number>
    adb status-window - continuously print device status for a specifie
    d device
    adb remount - remounts the /system partition on the device re
    ad-write
    adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
    tloader or recovery program
    adb reboot-bootloader - reboots the device into the bootloader
    adb root - restarts the adbd daemon with root permissions
    adb usb - restarts the adbd daemon listening on USB
    adb tcpip <port> - restarts the adbd daemon listening on TCP on th
    e specified port
    networking:
    adb ppp <tty> [parameters] - Run PPP over USB.
    Note: you should not automatically start a PPP connection.
    <tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
    [parameters] - Eg. defaultroute debug dump local notty usepeerdns

    adb sync notes: adb sync [ <directory> ]
    <localdir> can be interpreted in several ways:

    - If <directory> is not specified, both /system and /data partitions will be u
    pdated.

    - If it is "system" or "data", only the corresponding partition
    is updated.

    environmental variables:
    ADB_TRACE - Print debug information. A comma separated list
    of the following values
    1 or all, adb, sockets, packets, rwx, usb, sync
    , sysdeps, transport, jdwp
    ANDROID_SERIAL - The serial number to connect to. -s takes prior
    ity over this if given.
    ANDROID_LOG_TAGS - When used with the logcat option, only these de
    bug tags are printed.

    c:\>adb shell
    'adb' is not recognized as an internal or external command,
    operable program or batch file.

    c:\>Android-sdk-windows SDK Manager
    'Android-sdk-windows' is not recognized as an internal or external command,
    operable program or batch file.

    c:\>Android\android-sdk-windows\SDK Manager
    'Android\android-sdk-windows\SDK' is not recognized as an internal or external c
    ommand,
    operable program or batch file.

    c:\>Cd program files (c86)
    The system cannot find the path specified.

    c:\>cd program files (c86)
    The system cannot find the path specified.

    c:\>cd android

    c:\Android>cd android-sdk
    The system cannot find the path specified.

    c:\Android>android-sdk
    'android-sdk' is not recognized as an internal or external command,
    operable program or batch file.

    c:\Android>platform tools
    'platform' is not recognized as an internal or external command,
    operable program or batch file.

    c:\Android>cd platfprm tools
    The system cannot find the path specified.

    c:\Android>platform tools
    'platform' is not recognized as an internal or external command,
    operable program or batch file.

    c:\Android>cd platform tools
    The system cannot find the path specified.

    c:\Android>android-sdk-windows
    'android-sdk-windows' is not recognized as an internal or external command,
    operable program or batch file.

    c:\Android>cd android-sdk-windows

    c:\Android\android-sdk-windows>cd platform-tools

    c:\Android\android-sdk-windows\platform-tools>cd adb
    The system cannot find the path specified.

    c:\Android\android-sdk-windows\platform-tools>adb devices
    List of devices attached
    A000002846CAAB recovery


    c:\Android\android-sdk-windows\platform-tools>
    04-11-2011 06:25 AM
  8. BKMSTR's Avatar
    Did you set your path for adb in the system properties or wherever it needs to be? I forget exactly where you place the path for adb but there are youtube vids to show where to place it. That was my first mistake when I got this phone.
    04-11-2011 07:08 AM
  9. tirith's Avatar
    Got no problem driving and typing. Sitting at a dead stop anyway. The good news is adb recognizes the phone. You should be able to push the stock kernel and reset everything.

    From here the unroot thread should be able to help you

    Swyped from my g-breaded optimus prime.
    04-11-2011 07:10 AM
  10. sfhub's Avatar
    c:\Android\android-sdk-windows\platform-tools>
    This is the directory you need to be in to run adb for your installation.

    When you open a command prompt (Start Menu->Run->cmd.exe) you should first type
    C:
    cd \Android\android-sdk-windows\platform-tools
    This will set the current working directory (the default directory) to the one containing the adb.exe program. Previously you were in different directories which didn't contain the adb.exe executable, thus the errors.

    As long as your "prompt" says
    c:\Android\android-sdk-windows\platform-tools>
    Then you are in the proper directory to run adb.exe and don't need to type C:, cd, etc.

    Even though it is possible to preserve your GFs data and fix her phone, there is a chance you'll lose the data trying different methods to recover the phone. In some cases, you might have a chance to backup important data prior to losing it. Just preparing you for different scenarios.

    Is it correct to assume after the phone boots to recovery, you can choose the first option and it will start Android? Or can you not start Android at all and are always stuck in Recovery?
    04-11-2011 08:28 AM
  11. IP IHI II IL's Avatar

    Even though it is possible to preserve your GFs data and fix her phone, there is a chance you'll lose the data trying different methods to recover the phone. In some cases, you might have a chance to backup important data prior to losing it. Just preparing you for different scenarios.

    Is it correct to assume after the phone boots to recovery, you can choose the first option and it will start Android? Or can you not start Android at all and are always stuck in Recovery?
    Thanks SFHub,

    I knew her junk was gone before I started, so I backed anything not backed up by Google on a Hard Drive. The phone won't boot past recovery. I WISH I could just reboot it from recovery and have it at least work, but nope, just that turquoise font I'm begining not to like so much...

    I was up until 5am trying to figure it out to no avail, 'so my GF's off galavanting about with my EVO (my baby) until I get it fixed. Gonna' practice the ADB mehod a few times...

    Thanks everyone for your help! If anyone else has any quick fix ideas, or has run into this, please let me know!
    04-11-2011 01:16 PM
  12. sfhub's Avatar
    Have you tried:
    1) restoring the V8 Nandroid backup from here:
    http://files.mysticmidnight.net/zefi...c-V8-STOCK.zip

    or

    2) reinstalling the ThundeROM zip

    or

    3) if you have access to adb
    adb shell flash_image misc /dev/zero
    adb shell flash_image persist /dev/zero

    Please only do ONE at a time and see the results before trying the next.
    04-11-2011 01:24 PM
  13. IP IHI II IL's Avatar
    Have you tried:
    1) restoring the V8 Nandroid backup from here:
    http://files.mysticmidnight.net/zefi...c-V8-STOCK.zip

    or

    2) reinstalling the ThundeROM zip

    or

    3) if you have access to adb
    adb shell flash_image misc /dev/zero
    adb shell flash_image persist /dev/zero

    Please only do ONE at a time and see the results before trying the next.

    I've tried all of that, but just to say I did it, I tried all 3 again:

    Both using the Stock recovery and flashing ThunderRom again just go straight to Android System Recovery (RA-thunderc-1.1.0-GNM)

    I was FINALLY able to get ADB working, thanks to your help, and this is all I've tried:
    I SHOULD note that I THINK I may have unrooted the phone by accident, which put me in this recover loop to begin with. I know there is no "default recovery" so I think that the boot order is pointing straight to custom recovery, and not to the Android OS. I tried the ADB cmds to remove custom recovery, but they did not work, maybe 'cause I don't have root?)

    Microsoft Windows [Version 6.1.7600]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.


    c:\Android>cd \Android\android-sdk-windows\platform-tools

    c:\Android\android-sdk-windows\platform-tools>adb shell
    adb server is out of date. killing...
    * daemon started successfully *
    / # adb shell
    adb shell
    /sbin/sh: adb: not found
    / # mount/sdcard
    mount/sdcard
    /sbin/sh: mount/sdcard: not found
    / # flash_image recovery recovery.img
    flash_image recovery recovery.img
    error opening recovery.img: No such file or directory
    / # cd /sdcard/nandroid/mem=477M/BCDMRS12-20101122-1915
    cd /sdcard/nandroid/mem=477M/BCDMRS12-20101122-1915
    /sbin/sh: cd: can't cd to /sdcard/nandroid/mem=477M/BCDMRS12-20101122-1915
    / # $
    $
    /sbin/sh: $: not found
    / # adb push recovery-RA-GNM-thunderc-s-1.1.0.img /sdcard/
    adb push recovery-RA-GNM-thunderc-s-1.1.0.img /sdcard/
    /sbin/sh: adb: not found
    / # adb
    adb
    /sbin/sh: adb: not found
    / # su
    su
    /sbin/sh: su: not found
    / # adb push recovery-RA-GNM-thunderc-s-1.1.0.img /sdcard/
    adb push recovery-RA-GNM-thunderc-s-1.1.0.img /sdcard/
    /sbin/sh: adb: not found
    / # adb shell
    adb shell
    /sbin/sh: adb: not found
    / # cd adb shell
    cd adb shell
    /sbin/sh: cd: can't cd to adb
    / # mount/sdcard
    mount/sdcard
    /sbin/sh: mount/sdcard: not found
    / # flash_image recovery recovery.img
    flash_image recovery recovery.img
    error opening recovery.img: No such file or directory
    / # cd /sdcard/nandroid/mem=477M/BCDMRS12-20101122-1915
    cd /sdcard/nandroid/mem=477M/BCDMRS12-20101122-1915
    /sbin/sh: cd: can't cd to /sdcard/nandroid/mem=477M/BCDMRS12-20101122-1915
    / # adb shell flash_image misc /dev/zero
    adb shell flash_image misc /dev/zero
    /sbin/sh: adb: not found
    / # adb shell flash_image persist /dev/zero
    adb shell flash_image persist /dev/zero
    /sbin/sh: adb: not found
    / #
    04-11-2011 02:09 PM
  14. sfhub's Avatar
    Please do NOT remove custom recovery. You will be worse off. Trust me. Adb won't work and you won't be able to do nandroid restores.

    Your phone is booting to recovery either because /system is hosed or because the misc or persist partitions are in a state thet forces recovery.

    If you have "#" sign in your adb prompt, you have root permissions (and can get permanent root for Android very simply). Don't worry about that for now.

    Please be very careful what you are doing. Some of the commands you are typing were supposed to be done in a windows command prompt but you are entering in an adb shell session (and vice versa). You can really make your phone a lot worse.

    Even though you feel you have tried everything I suggested, it seems you are entering some commands, ignoring the errors, and considering that suggestion completed.

    Now, inside of your "adb shell" session, which is a terminal session running on your phone denoted by the "/ #" prompt, type

    flash_image misc /dev/zero

    flash_image persist /dev/zero
    It is important you type all the spaces so I emphasized them. Also those are 2 separate commands.

    After that, reboot and see where you are at.
    04-11-2011 04:05 PM
  15. Robchaos_'s Avatar
    In all your copy paste stuff I see more then one instance where it looks like you omitted spaces in your commands. Instead of typing them out yourself why don't you go back to the unroot your phone stickied thread and start from the beginning but this time copy and paste the shell commands instead of re typing them.
    04-11-2011 04:18 PM
  16. athanos's Avatar
    I also noticed that some of the errors you are getting is because you are typing 'adb' inside the shell. Once you are in the shell and have the # symbol to the left of your cursor you no longer need to proceed each command with 'adb'.
    04-11-2011 04:28 PM
  17. Tree Dude's Avatar
    This is exactly why I have not rooted my wife's phone, even though she has begged me to. If I have an issue, I can only blame myself, if she has one, she blames me and I never hear the end of it.

    It took me a bit to learn the commands as well. Once you get the syntax down though it won't look so greek.
    04-11-2011 04:39 PM
  18. IP IHI II IL's Avatar
    Let me start by sayin' ou guys are AWESOME!

    Ok, so thank you for pointing out what I'm doing wrong, I'm really learning a lot!

    SFHUB: here's the result from the commands you asked me to try:
    Microsoft Windows [Version 6.1.7600]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.

    C:\Users\charos22>cd c:\Android>cd \Android\android-sdk-windows\platform-tools
    The system cannot find the path specified.

    C:\Users\charos22>cd \Android\android-sdk-windows\platform-tools

    C:\Android\android-sdk-windows\platform-tools>adb shell
    adb server is out of date. killing...
    * daemon started successfully *
    / # flash_image misc /dev/zero
    flash_image misc /dev/zero
    error writing misc: No space left on device
    / # flash_image persist /dev/zero
    flash_image persist /dev/zero
    error writing persist: No space left on device
    / #

    I'm being more careful not to mix code, I didn't realize that even though a command was unsuccessful it could still affect the next. I checked, and the return from those 2 commands are wrong, there's plenty of space, and I know I'm prob'ly taking those messages too litterally, and that they're most likely referring to SOMETHING ELSE I don't understand...lol

    Thanks again for your help so far, it's more appreciated than I can explain! (although when I try to reassure my GF that I'm making progress, she seizes, and her eyes roll. I have her on our SUPER OLD Palm Treo, that only functions as a phone and I'm being hounded for the laptop as we speak... "I NEED TO CHECK MY E-MAIL, AND YOU RUINED MY PHONE, SO I NEED THE LAPTOP!!!!!!")

    Word of advice, don't try to "hook your GF up", 'cause you think you're knowledgable, EVER! Odds are, you're not, and she won't be impressed after a few minutes...
    04-11-2011 06:57 PM
  19. Robchaos_'s Avatar
    Ok... Please forgive me if you have already done this, but go back to the official unroot thread and start from the beginning. This time copy and past the commands!
    It seems that you have not tried that while properly entering the commands. It looks like you did not mount your SD card properly, or flash the recovery image properly if I am interpreting your copied text right.
    Also the fact that you keep getting pushed back to your recovery, but as you indicated in your first post, it is still a custom recovery, makes me even more sure you just flubbed one of the commands. If you still have access to GNM's v1.1.0 Recovery Kernel, that means you already are rooted and have the flash_image binary in your phone already. That means you can skip the first 12 steps and go straight to booting phone into recovery.

    Have you tried this yet?
    04-11-2011 09:23 PM
  20. sfhub's Avatar
    / # flash_image misc /dev/zero
    flash_image misc /dev/zero
    error writing misc: No space left on device
    / # flash_image persist /dev/zero
    flash_image persist /dev/zero
    error writing persist: No space left on device
    / #
    This is the expected output. /dev/zero is a device that will output 0x00 forever and you are using this to clear out the misc and persist partitions. Those are the ones running out of space, which is ok, as it means you just wrote zeros to the entire partition until it ran out of space.

    Now I would suggest you reboot once, just in case there is improvement. Don't expect any change, but there is a remote chance.

    Assuming no change, reboot into recovery, and follow steps 13-24 ONLY of the unroot thread.
    http://forum.androidcentral.com/lg-o...urn-stock.html

    You don't need to do 1-12 because you already have ThunderC custom recovery. You don't want to do 25-29 because you *want* to keep ThunderC recovery.
    04-11-2011 10:19 PM
  21. scifan's Avatar
    As several above have commented... this is why I don't mess with my wife's phone...
    04-11-2011 11:42 PM
  22. ccrs8's Avatar
    As several above have commented... this is why I don't mess with my wife's phone...
    My wife still has a razr, so luckily there isn't much I can mess up on it (although I've tried).
    04-12-2011 07:45 AM
  23. IP IHI II IL's Avatar
    So I booted up the Optimus to follow your instructions, SFHub, and oddly enough, it boots perfectly, and now I CAN'T boot into recovery! I haven't done anything to it since I pushed the commands you asked me to (maybe it just needed a break...lol), so THANK YOU! I'll have to check all of the functionality later, as we don't have it active on cell service, and I can't "choose an ID", but I think it's safe to assume that it's back to it's annoying (but more suited for my GF) stock state!

    Thanks SOO MUCH to everyone, Especially SFHub! This is the most help I've received on any forum (and I'm a member of all of them I've found so far)

    Starfox, I was planning out a long drawn out response, detailing the struggles of raising an autistic/emotionally distressed 5 year old boy, and his emotionally distressed 8 year old sister, the hardships of helping them through the unmentionable abuse they used to receive from their biological father, as well as dealing with having my own 3 year old daughter taken from me by her schizophrenic mother and fighting to get her back, miscarriages, the hardships of working in the EMR field on contract, 'cause there are no permanent jobs available, as well as supporting all 6 of my family on a $30k salary by myself (and doing it WELL), all the extra work I had to do and what I had to give up in order to get the ONE toy (my EVO) I've bought for myself in 3 years without making anyone else in my family have to suffer, etc....... but judging by the way you type, you're too caught up in your perfect forum world where no one should ask for help, or gets sidetracked by real life when attempting to fix a mistake. There's too much ignorance in the REAL world for it to be perpetuated on the internet. Thanks for being a nanite troll hater, though! Makes the victory THAT much sweeter!

    Thanks again everyone! I seriously appreciate your response, and willingness to help! I also learned a TON!
    thekid likes this.
    04-12-2011 12:51 PM
  24. bblaze's Avatar
    I don't know if this is helpful in this situation, but I remembered seeing this in Zefie's VCRom thread.

    Guys with the Custom Recovery Boot Loop:
    First off this is NOT a recovery image and do NOT flash it, follow the instructions provided!

    1) Download recovery.bin
    2) Extract file with 7zip or WinRAR or whatever.
    3) Open a command prompt to the same folder as where you placed extracted recovery.bin

    4) Run these adb commands
    adb push recovery.bin /rec
    adb shell chmod +x /rec
    adb shell /rec

    5) Now you should see LG's recovery menu. Simply hit "reboot" (first option).
    6) Boot loop should now be gone.

    Tech Details: LG has some funny voodoo going on and only their recovery can tell the phone to stop booting into recovery. This is why it says "do not remove the battery" on their recovery.
    04-12-2011 01:31 PM
  25. IP IHI II IL's Avatar
    I don't know if this is helpful in this situation, but I remembered seeing this in Zefie's VCRom thread.
    Oh man!

    That would have helped! I think LG's Voodoo actually helped me in this case, as the phone seemingly fixed itself after SFHub shared a few commands!

    Thanks for that, though! I plan on saving this whole thread for reference, as I really did learn a WHOLE LOT!
    04-12-2011 01:37 PM
34 12
LINK TO POST COPIED TO CLIPBOARD