Please help me get off my couch and sleeping in my bed again...

[IP IHI II IL]

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!

 

[tirith]

No access to adb? what is the problem there? The largest problem most people have is driver recognition... Especially on win 7

 

[IP IHI II IL]

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...

 

[tirith]

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:

 

[IP IHI II IL]

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

 

[tirith]

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.

 

[IP IHI II IL]

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>

 

[BKMSTR]

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.

 

[tirith]

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.

 

[sfhub]

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?

 

[IP IHI II IL]

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!

 

[sfhub]

Have you tried:
1) restoring the V8 Nandroid backup from here:
http://files.mysticmidnight.net/zefie/files/cell/LG670/roms/nandroid-thunderc-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.

 

[IP IHI II IL]

Have you tried:
1) restoring the V8 Nandroid backup from here:
http://files.mysticmidnight.net/zefie/files/cell/LG670/roms/nandroid-thunderc-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
/ #

 

[sfhub]

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.

 

[Robchaos_]

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.

 

[athanos]

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'.

 

[Tree Dude]

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.

 

[IP IHI II IL]

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...

 

[Robchaos_]

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?

 

[sfhub]

/ # 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-...45403-how-unroot-your-phone-return-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.