[Custom Recovery] Xionia Clockwork (CWMA v1.2518.6)

[CullenWebb]

You enter those commands inside of adb shell.

Make sure you have the "#" prompt indicating root login privileges.

If your prompt is "$", then turn on your phone, make sure you aren't in the lock screen, type "su" in the adb shell, look for a prompt asking for root privileges, accept the prompt.

I don't have a clue what the adb shell is. Is that done via a windows command prompt or something on my phone?

I am rather "flash illiterate". Hold my hand?

Thanks!

 

[sfhub]

Go through the first 3-4 steps of this post:

http://forum.androidcentral.com/lg-...custom-roms-optimus-s-edition.html#post474783

 

[the_mastermind]

I've followed all the directions, all the lines and everything. but when i reboot through adb, its still the original android recovery!

I did it 2 times already, still no hope and all i see is the android recovery screen!

Help!

 

[sfhub]

I've followed all the directions, all the lines and everything. but when i reboot through adb, its still the original android recovery!

I did it 2 times already, still no hope and all i see is the android recovery screen!

Help!

Post each step you did and the output of that command.

 

[the_mastermind]

Post each step you did and the output of that command.

dont have access a computer that can run all this stuff right now so i have do it off memory.

Well since i couldnt get z4root to work, i rooted my phone through adb and rooted the phone based on this thread:

http://forum.androidcentral.com/lg-optimus-s-rooting-roms-hacks/43108-how-root-lg-optimus-s.html

that was a headace, couldnt get the "#" sign for awhile, but eventually it worked and i used superuser & titanium backup to backup my data etc.

Then used the directions in thread, but i couldnt get adb again to get the "#" but eventually got it to work and used the commands.

from there when i run the command "reboot recovery" it reboots my phone, but it boots to the stock recovery everytime. i tried this 3 times already. yes, all the files are on my sd card and in my computer's tools directory. kept the zip file zipped (flash_image), unzipped the rar file (xionia_cwma_12518.6.img)

is it possible that its something with the superuser app? was the superuser app supposed to ask for permission for adb to be a superuser?

thanks for all your help

 

[drewwalton19216801]

dont have access a computer that can run all this stuff right now so i have do it off memory.

Well since i couldnt get z4root to work, i rooted my phone through adb and rooted the phone based on this thread:

http://forum.androidcentral.com/lg-optimus-s-rooting-roms-hacks/43108-how-root-lg-optimus-s.html

that was a headace, couldnt get the "#" sign for awhile, but eventually it worked and i used superuser & titanium backup to backup my data etc.

Then used the directions in thread, but i couldnt get adb again to get the "#" but eventually got it to work and used the commands.

from there when i run the command "reboot recovery" it reboots my phone, but it boots to the stock recovery everytime. i tried this 3 times already. yes, all the files are on my sd card and in my computer's tools directory. kept the zip file zipped (flash_image), unzipped the rar file (xionia_cwma_12518.6.img)

is it possible that its something with the superuser app? was the superuser app supposed to ask for permission for adb to be a superuser?

thanks for all your help

You copied flash_image.zip to /system/bin/flash_image, didn't you? You were supposed to extract flash_image out of the flash_image folder that is inside the flash_image ZIP file.

That's why flash_image is failing to flash anything.

I can't tell you to read the directions again because the directions don't specifically say to extract it from the flash_image ZIP file

Zefie, please update the directions to include this important info!

 

[sfhub]

In spite of the instructions though, there should have been error messages for some of the steps. Those should not be ignored unless explicitly noted as expected errors.

 

[drewwalton19216801]

In spite of the instructions though, there should have been error messages for some of the steps. Those should not be ignored unless explicitly noted as expected errors.

Not necessarily. If you were to "cat /sdcard/flash_image.zip > /system/bin/flash_image" there would be no error. It would just do it. Then when you ran flash_image there would also be no error. The shell will just spit out the command you entered and give no further feedback.

 

[sfhub]

Not necessarily. If you were to "cat /sdcard/flash_image.zip > /system/bin/flash_image" there would be no error. It would just do it. Then when you ran flash_image there would also be no error. The shell will just spit out the command you entered and give no further feedback.

It would spit out an error because the magic number for the executable would be incorrect:

$ su
su
# mount -o remount,rw -t yaffs2 /system /system
mount -o remount,rw -t yaffs2 /system /system
# cat /sdcard/flash_image.zip > /system/bin/flash_image2
cat /sdcard/flash_image.zip > /system/bin/flash_image2
# chmod 755 /system/bin/flash_image2
chmod 755 /system/bin/flash_image2
# /system/bin/flash_image2 recovery /sdcard/xionia_cwma_12518.6.img
/system/bin/flash_image2 recovery /sdcard/xionia_cwma_12518.6.img
/system/bin/flash_image2: 1: Syntax error: "(" unexpected
#

 

[drewwalton19216801]

It would spit out an error because the magic number for the executable would be incorrect:

You have me there. I was only speaking from experience helping another member who had done that same thing, and it did not produce said error.

 

[sfhub]

You have me there. I was only speaking from experience helping another member who had done that same thing, and it did not produce said error.

It could behave like that if the executable was an empty file, but not for the example you gave. However, if the empty file got created, then the earlier "cat" command most likely would have given an error because the source file wasn't specified properly.

 

[drewwalton19216801]

It could behave like that if the executable was an empty file, but not for the example you gave. However, if the empty file got created, then the earlier "cat" command most likely would have given an error because the source file wasn't specified properly.

Your forum tag "Android Genius" seems to be right on the money

I do seem to remember in that particular instance the /system/bin/flash_image file size was exactly zero, so you're right on that one.

 

[the_mastermind]

You copied flash_image.zip to /system/bin/flash_image, didn't you? You were supposed to extract flash_image out of the flash_image folder that is inside the flash_image ZIP file.

That's why flash_image is failing to flash anything.

I can't tell you to read the directions again because the directions don't specifically say to extract it from the flash_image ZIP file

Zefie, please update the directions to include this important info!

i think thats where im possibly stuck? it says theres no directory for that step.

i looked on my sd card and there is no directory for /system/bin/flash_image

i put the flash image in the "data" fold on my sd card

i really do appreciate everyone's help, but honestly all these instructions are not clear. i didnt even know i had to get the rageagainstthecage.bin file had to figure that one out on my own. no where does it say to download that, which cost me a great deal of time and then now i have to repeatedly try to get the damn $ to # each time trying to flash! but thank you!

 

[tirith]

Copy flash_image and xionia_cwma_12518.6.img to the root of your sdcard. RAR file is protected with recovery record in case of corrupt download. Please extract rar before attempting to flash.
To flash: via adb shell or terminal type this from root # shell

No offense, but it does say to extract it... I never had to deal with the rageagainstthecage.bin file either.... *shrug*

 

[sfhub]

No offense, but it does say to extract it... I never had to deal with the rageagainstthecage.bin file either.... *shrug*

The one being referenced is flash_image. The link is a zip file. The extract portion only references the image file, not the zip file for flash_image.

 

[cloroxx.l]

Helppppp!! Can not boot into custom recovery

Everything is working fine, I have an Optimus S.. filkes are in sd card and i have repeted the terminal steps... i am rooted and displaying #. i get no errors besides the negkectable "no such file" error you had said to skip past. so im assuming it is installed... with no errors i am finding myself confused.. i hold vol down+home+power and i am being brought into "android system recovery" i have tried a few recoverys and i am never able to open ANYTHING besides the stock recovery....... with no error messages and everything running smooth im finding myself confused. how can i open this recovery?!
Thankyou.

 

[Tabarnak]

I followed all of the above steps but I'm taken to an "Android system recovery <3e>" console... i don't see backup anywhere... just reboot, apply update.zip, and 2 wipe options!

Any ideas?

 

[Onyoursix]

This may be a dumb question, but does this recovery only support gingerbread roms? I'm getting error "E:Wrong digest:Meta-INF/com/google/android/update-script E:signature verification failed Installation aborted." When trying to flash a rom. It's a 2.2 based rom.

 

[O.a.T.]

This may be a dumb question, but does this recovery only support gingerbread roms? I'm getting error "E:Wrong digest:Meta-INF/com/google/android/update-script E:signature verification failed Installation aborted." When trying to flash a rom. It's a 2.2 based rom.

No, it is not limited to flashing gingerbread roms.

 

[CarrieK]

Everything is working fine, I have an Optimus S.. filkes are in sd card and i have repeted the terminal steps... i am rooted and displaying #. i get no errors besides the negkectable "no such file" error you had said to skip past. so im assuming it is installed... with no errors i am finding myself confused.. i hold vol down+home+power and i am being brought into "android system recovery" i have tried a few recoverys and i am never able to open ANYTHING besides the stock recovery....... with no error messages and everything running smooth im finding myself confused. how can i open this recovery?!
Thankyou.

Have you tried rebooting into recovery using Terminal Emulator on your phone?