[Brent Patton]

Thanks in advance for reading. If anyone can help it would be very much appreciated.

I've been searching google for hours trying to find a fix with no luck. First I have an optimus v that only will go into the cwm 4.0.1.5 recovery. second I cannot access my sd card (this was an issue because of physical damage when the phone was working). I am trying to install a new rom using quick adb pusher which will allow me to send the file to the device but the cwm version I have will only allow me to install new .zip file from sd card, which for me is actually impossible. If anyone has advice I would love to hear it.

Thanks in Advance.

[upconvert]

Is the sdcard damaged, or is it because of your phone's sd slot?

[Brent Patton]

I believe the phone slot is damaged. I dropped the phone while running the stock rom and it gave me an error saying that it could not read the sd card. What I had in mind was to push the new rom zip to the internal memory with adb but my recovery will not let me install a rom from internal memory, only sd card. Thanks for taking a look

[AndyOpie150]

Have you: Put SD card in computer and seen if any data shows up? If it doesn't auto show a window, try going to: Stsrt/Computer and click on the SD card icon. If it shows all your data then transfer data to a folder.
When done: Right click on SD card icon and select format. After formatting SD card to stock (FAT32) format put in phone and power on.
Once on and booted go to menu/settings/storage and select to erase SD card. After done reboot phone.
Check with file managed to see if the phone put the proper folders on the sd card. If yes pt back into computer and transfer data back.

This is what worked for me.
May not for you. I don't know what youv'e tried.

If this worked.
Go to the ZenGarden thread. Scroll down a little ways, it's not too far down the lists of threads,
Select the zipped version. Keep it zipped and put with the folders on the sd card (not in any foldr).
In the recovery flash the ZenGarden zip.
When done go to the advanced sction and select to reboot the recovery.
It will now boot into the ZenGarden recovery.
Brain fart: It has an option to fix the recovery loop you are in.

If you put a ROM on the sd card now would be a good time to flash it.

I wrote all this in hopes the above advice with the sd card worked.
If not, I'll scratch head, rack brain (whats left of it), and put thinking cap on?

Sent from my LG-VM670 using Android Central Forums

[Brent Patton]

Thanks so much for the reply, I'll try that and see if it works. May take me a day to get it all checked. I'll post my results tomorrow after I know more. Without racking your brain anymore than you have to, is there anyway to install a new recovery image to the optimus v without the sd card available. If you would rather wait till I post the results I would understand completely as to not do extra thinking on this already complicated puzzle. Thanks again

[Brent Patton]

followed your steps, tried 3 sd cards to no avail. once they formatted I placed them into the phone and still got the unable to mount sd error.

[EarthnFire78]

followed your steps, tried 3 sd cards to no avail. once they formatted I placed them into the phone and still got the unable to mount sd error.

You have access to the recovery through adb right?

[Brent Patton]

I think so. when I do adb devices I get my serial number and it says recovery after. I can do adb shell and access the phone but don't really know what to do from there.

[EarthnFire78]

have you formatted anything?

[Brent Patton]

Yeah, everything is wiped. can you install a recovery with adb or fastboot that lets you install a rom from internal memory

[EarthnFire78]

Try the following, this should trigger the update_package command in the recovery, that is if it has not been removed.

Factory/Data Reset from recovery

adb shell mkdir -p /cache/recovery
adb push "/path to the zip/name of the zip" /data/

Next you are going to format the system, and boot; but do not format anything else.

$ adb shell

chmod 0777 /cache && chmod 0777 /cache/recovery && touch /cache/recovery/command && echo '--update_package=" /data/Name of zip"' > /cache/recovery/command
reboot recovery

[Brent Patton]

Thank you so much, the only question I have is what .zip file are you wanting me to get and use

[EarthnFire78]

Thank you so much, the only question I have is what .zip file are you wanting me to get and use

Go with either MiRaGe-CM7.2-IHO or Harmonia 2.09. OM-Mandylion you will have a boot problem because your sdcard is not working.

[Brent Patton]

thank you I will give it a try tomorrow, I have to be up early unfortunately. I will post and let you know how it goes. again thanks for the help

[Brent Patton]

Ok, so I entered the the code and received the error E:unknown volume for path. What is very strange is that after the push the .zip file will be in the data folder but after the reboot it will no longer be there. I have checked with two programs and can verify they are gone after reboot recovery

[EarthnFire78]

Ok, so I entered the the code and received the error E:unknown volume for path. What is very strange is that after the push the .zip file will be in the data folder but after the reboot it will no longer be there. I have checked with two programs and can verify they are gone after reboot recovery

The data partition needs to be mounted before pushing the file, but even then data partition is unmounted causing the recovery to not find the file. I'm better with fastboot for installing a ROM then I am with adb. You can try converting the zip into an image file and use fastboot to flash the image.

[Brent Patton]

Is there another place I can place the .zip file so that the phone will mount? I will do some research on converting the file to a flash image but don't know anything about fastboot. You've been extremely helpful Thank you

Ok I've gotten to the point where it now tells me the signature verification failed. Installation aborted. I think that is progress but still working on how to get past that.

[EarthnFire78]

Is there another place I can place the .zip file so that the phone will mount? I will do some research on converting the file to a flash image but don't know anything about fastboot. You've been extremely helpful Thank you

Figured out the problems writing the recovery cache command from recovery does not work out, but there is a way to force the recovery to flash the zip I'll look into it for you. There maybe away to convert the system folder of the zip into an image file that fastboot can then flash as well.

[Brent Patton]

Figured out the problems writing the recovery cache command from recovery does not work out, but there is a way to force the recovery to flash the zip I'll look into it for you. There maybe away to convert the system folder of the zip into an image file that fastboot can then flash as well.

Ok I've gotten to the point where it now tells me the signature verification failed. Installation aborted. I think that is progress but still working on how to get past that.

[EarthnFire78]

Ok I've gotten to the point where it now tells me the signature verification failed. Installation aborted. I think that is progress but still working on how to get past that.

What ROM are you flashing?

[Brent Patton]

What ROM are you flashing?

I'm using the mirage file you recommended but I am doing it using this method

All of the recoveries - both the stock and custom recoveries - look for a "command" file when they first start up.

It literally is named "command", i.e.: /cache/recovery/command

... and it is a simple text file with as few as one line(s) in it.

Here is an example from the most recent OTA of the contents of /cache/recovery/command:
Code:
--update_package=CACHE:8e3b63f96149.OTA_Desire_C_Verizon_WWE_2.37.605.4_2.36.605.1_release.zip
basically, it's just a single line with the following format:

--update_package=CACHE:filename.zip

So, if you are trying to get an installer to run without an SD card, you would:

1) Boot to Amon_RA
2) Wipe the cache if necessary (wipe -> wipe data/factory reset also clears /cache)
3) Push your zip file to cache:
Code:
adb push mycustominstall.zip /cache/
4) Create a command file (say, named "command.txt") with the contents:
Code:
--update_package=CACHE:mycustominstall.zip
5) Push it to the phone:
Code:
adb push command.txt /cache/recovery/command
6) reboot directly back into recovery with
Code:
adb shell reboot recovery
When the recovery boots up again, it will immediately start unpacking your "mycustominstall.zip" file.


After I thought this all the way through, I realized, though: a lot of the ROM files are only about 100 MB, and cache is about 128 Mb, so

.... wait for it .....

... wait for it ....

it might be a worthwhile experiment to just push an untouched ROM file right to cache and then use that ROM file's name in your "command" file.

So long as /sbin/recovery does not unpack files to /cache (I can't remember if it does this or not!), you could use original ROM files -- just what you wanted originally. If it unpacks things to cache, though, it will only get part way through the install and fail.

It's worth a shot; if it fails, you'll have a mess that is no worse to clean up than what you've presently got. (If it fails, to be on the safe side it might be wise to go in using adb and clean things up in /cache a little bit so that the next recovery boot has some wiggle room in /cache - e.g. "adb shell rm -rf /cache/*" )

bftb0

[EarthnFire78]

I'm using the mirage file you recommended but I am doing it using this method

All of the recoveries - both the stock and custom recoveries - look for a "command" file when they first start up.

It literally is named "command", i.e.: /cache/recovery/command

... and it is a simple text file with as few as one line(s) in it.

Here is an example from the most recent OTA of the contents of /cache/recovery/command:
Code:
--update_package=CACHE:8e3b63f96149.OTA_Desire_C_Verizon_WWE_2.37.605.4_2.36.605.1_release.zip
basically, it's just a single line with the following format:

--update_package=CACHE:filename.zip

So, if you are trying to get an installer to run without an SD card, you would:

1) Boot to Amon_RA
2) Wipe the cache if necessary (wipe -> wipe data/factory reset also clears /cache)
3) Push your zip file to cache:
Code:
adb push mycustominstall.zip /cache/
4) Create a command file (say, named "command.txt") with the contents:
Code:
--update_package=CACHE:mycustominstall.zip
5) Push it to the phone:
Code:
adb push command.txt /cache/recovery/command
6) reboot directly back into recovery with
Code:
adb shell reboot recovery
When the recovery boots up again, it will immediately start unpacking your "mycustominstall.zip" file.


After I thought this all the way through, I realized, though: a lot of the ROM files are only about 100 MB, and cache is about 128 Mb, so

.... wait for it .....

... wait for it ....

it might be a worthwhile experiment to just push an untouched ROM file right to cache and then use that ROM file's name in your "command" file.

So long as /sbin/recovery does not unpack files to /cache (I can't remember if it does this or not!), you could use original ROM files -- just what you wanted originally. If it unpacks things to cache, though, it will only get part way through the install and fail.

It's worth a shot; if it fails, you'll have a mess that is no worse to clean up than what you've presently got. (If it fails, to be on the safe side it might be wise to go in using adb and clean things up in /cache a little bit so that the next recovery boot has some wiggle room in /cache - e.g. "adb shell rm -rf /cache/*" )

bftb0

Push the zip to the data partition as the cache partition is to small. The text should look like this "--update_wiped=/data/nameofthezip.zip"

What it turned out to be, was the command to write the to the command file was wrong.

[AndyOpie150]

You know your going to have to write a tutorial on this when your done. Right?

Sent from my LG-VM670 using Android Central Forums

[Brent Patton]

Push the zip to the data partition as the cache partition is to small. The text should look like this "--update_wiped=/data/nameofthezip.zip"

What it turned out to be, was the command to write the to the command file was wrong.

It returned: Invalid command argument on that code.

[EarthnFire78]

This gives me an idea AndyOpie150, because of the way that ZenGarden is setup this kind of install well not work as things are wiped after then auto backup is complete, so the zip well also be wiped. So tomorrow well start writing a new packages install command.

--update_nosdcard