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

You need to fix this problem first. There is no flash_image file on your /sdcard thus you just created a 0 length file for /system/bin/flash_image
I figured it out, I was stupidly running through the adb shell while I was still connected to the computer with USB transfer, so the phone couldn't see the SD card.
 
when i am doing this i keep getting:
# cat /sdcard/flash_image > /system/bin/flash_image
cat /sdcard/flash_image > /system/bin/flash_image
cannot create /system/bin/flash_image:read-only file system

Help
 
when i am doing this i keep getting:
# cat /sdcard/flash_image > /system/bin/flash_image
cat /sdcard/flash_image > /system/bin/flash_image
cannot create /system/bin/flash_image:read-only file system

Help

Did you successfully complete this step as mentioned in the first post?
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
 
# mount -o remount,rw -t yaffs2/dev/block/mtdblock5/system
mount -o remount,rw -t yaffs2/dev/block/mtdblock5/system
Usage: mount [-r] [-w] [-o options] [-t type] device directory

I appreciate your help with this matter, its driving me crazy
 
# mount -o remount,rw -t yaffs2/dev/block/mtdblock5/system
mount -o remount,rw -t yaffs2/dev/block/mtdblock5/system
Usage: mount [-r] [-w] [-o options] [-t type] device directory

I appreciate your help with this matter, its driving me crazy
You missed some "spaces" between the parameters.

mount -o remount,rw -t yaffs2/dev/block/mtdblock5/system
should be
mount -o remount,rw -t yaffs2[space]/dev/block/mtdblock5[space]/system

where you replace [space] with the space bar on the keyboard.
 
Running into an MD5 mismatch problem here, and hoping for a more elegant solution (i.e., more elegant than manual flash_image command for each flash partition).

So I changed the name of the nandroid restore under CWMA from the date/time stamp given to a more easily remembered name (i.e., Stock_Rooted). Unfortunately, when I try and restore back to that through CWMA, I get the error "MD5 mismatch" (MD5 must be generated using file/folder name as well, apparently), and the restore aborts. Thoughts about how to get around the MD5 mismatch error (i.e., without just doing a manual flash)?

Thanks in advance.
 
Running into an MD5 mismatch problem here, and hoping for a more elegant solution (i.e., more elegant than manual flash_image command for each flash partition).

So I changed the name of the nandroid restore under CWMA from the date/time stamp given to a more easily remembered name (i.e., Stock_Rooted). Unfortunately, when I try and restore back to that through CWMA, I get the error "MD5 mismatch" (MD5 must be generated using file/folder name as well, apparently), and the restore aborts. Thoughts about how to get around the MD5 mismatch error (i.e., without just doing a manual flash)?

Thanks in advance.
md5 should be file only. if its failing then one of your files is corrupted. check your sd card for errors and replace the file.
 
md5 should be file only. if its failing then one of your files is corrupted. check your sd card for errors and replace the file.

I second that. If you look inside your backup folder, you will find an md5 file that lists md5 check sums for all the other files, not the back up as a whole, but all the components.

I rename my folders past the data stamp, (ex. 2011-03-22.CM7 or 2011-03-22.ThundeROM). This makes it easy enough to run different ROM's without needing to keep notes on which backup is which.
 
Can you please give me the adb instructions(code) for flashing xionia cwma recovery v.?.?.?.?.......just reverted to ZV9 from ZVD using KP500 to gain rooting ability. I know I know......i was lazy and rooted with z4.apk and accidentally installed ClockworkMod 2.5.1.3 from ROM Manager premium and cant seem to manually boot into recovery.
 
Can you please give me the adb instructions(code) for flashing xionia cwma recovery v.?.?.?.?.......just reverted to ZV9 from ZVD using KP500 to gain rooting ability. I know I know......i was lazy and rooted with z4.apk and accidentally installed ClockworkMod 2.5.1.3 from ROM Manager premium and cant seem to manually boot into recovery.

The ADB instructions are towards the bottom in the very first post of this thread.
http://forum.androidcentral.com/lg-optimus-s-rooting-roms-hacks/59359-custom-recovery-xionia-clockwork-cwma-v1-2518-6-a.html#post596820
 
  • Like
Reactions: arrogant437
I've already copied the flash_image file (did not unzip just copied) and the xionia rar image file (unzipped) onto my sdcard. but im still not understanding what to do next.... how do i flash the post doesn't tell how to use adb and i dont have a unix account for the root # shell code.........yes im a newb....but ive read ALOT of forums to get this far
 
The flash_image.zip file needs to be unzipped, and it contents (1 file) gets copied to your SD card, not the zip file itself.

The ADB terminal is part of the Android-SDK that you should install on your PC. Just so we are all on the same page, do you already have root access on your phone?
 
I've already copied the flash_image file (did not unzip just copied) and the xionia rar image file (unzipped) onto my sdcard. but im still not understanding what to do next.... how do i flash the post doesn't tell how to use adb and i dont have a unix account for the root # shell code.........yes im a newb....but ive read ALOT of forums to get this far

As gub23 said, starting with the basics, do you have root?

If so, and you haven't installed the android-sdk files, there is another option.

download and install connectbot. it is a free terminal app for your phone. once installed, select local, and then type in a nickname (doesn't matter what you put in)

then type the lines one at a time from the first post. if you follow them exactly, it should work for you.
 
  • Like
Reactions: arrogant437
ok. open a command prompt.

type this in:
(below is example from my computer, basically path to the folder that holds adb.exe)
cd c:\android-sdk-windows\platform-tools\

then you'll want to type:

adb shell

it should start the adb client, and then bring up:

#


if you get the #, then you are good to enter all the lines one at a time.
if you get $, then try typing:
su
then make sure phone screen us unlocked and superuser app should come up asking if you want to allow the root access. click yes

that help?
yes and sdk platform on pc as well
 
  • Like
Reactions: rootz86
yes and sdk platform on pc as well.....but ill try connectbot...sounds much easier

it is a lot easier to be honest. hard part of adb shell is getting the client started up. i struggled with it at first too, because a lot of people just say, "type this into adb shell" and i was always like "how do i get adb shell running?"

connectbot is a quick/free terminal shortcut

SORRY, when you get into connectbot, it will probably show: $
type: su
then click allow when superuser comes up. (you have the superuser app installed correct?)
once you get: # , you are good to go
 
I got $ and then it said permission denied, Ill try connectbot now, do i stay in debugging mode on phone?
 

Latest posts

Trending Posts

Forum statistics

Threads
956,831
Messages
6,970,230
Members
3,163,634
Latest member
joemommajack23