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

[cmags]

Well now, that didn't work...

So I was thinking of trying out the aospCMod ROM, but saw I should have a CWM recovery first.

Starting with ThunderC recovery 1.1, V9 radio and ThundeROM 1.6.2 (if those matter).

ADB output:

cmagnell@vulcan:~/android-sdk-linux_86/platform-tools$ ./adb shell
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
# cat /sdcard/flash_image > /system/bin/flash_image
/sdcard/flash_image: No such file or directory
# cat /sdcard/extracted/flash_image > /system/bin/flash_image
/sdcard/extracted/flash_image: invalid length
# cat /sdcard/extracted/flash_image/flash_image > /system/bin/flash_image
# chmod 755 /system/bin/flash_image
# mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
failed on '/system/etc/install-recovery.sh' - No such file or directory
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system
# flash_image recovery /sdcard/xionia_cwma_12518.6.img
mtd: read error at 0x00000000 (Out of memory)
mtd: read error at 0x00020000 (Out of memory)
mtd: read error at 0x00040000 (Out of memory)
mtd: read error at 0x00060000 (Out of memory)
mtd: read error at 0x00080000 (Out of memory)
mtd: read error at 0x000a0000 (Out of memory)
mtd: read error at 0x000c0000 (Out of memory)
mtd: read error at 0x000e0000 (Out of memory)
mtd: read error at 0x00100000 (Out of memory)
mtd: read error at 0x00120000 (Out of memory)
mtd: read error at 0x00140000 (Out of memory)
mtd: read error at 0x00160000 (Out of memory)
mtd: read error at 0x00180000 (Out of memory)
mtd: read error at 0x001a0000 (Out of memory)
mtd: read error at 0x001c0000 (Out of memory)
mtd: read error at 0x001e0000 (Out of memory)
mtd: read error at 0x00200000 (Out of memory)
mtd: read error at 0x00220000 (Out of memory)
mtd: read error at 0x00240000 (Out of memory)
mtd: read error at 0x00260000 (Out of memory)
mtd: read error at 0x00280000 (Out of memory)
mtd: read error at 0x002a0000 (Out of memory)
mtd: read error at 0x002c0000 (Out of memory)
mtd: read error at 0x002e0000 (Out of memory)
mtd: read error at 0x00300000 (Out of memory)
mtd: read error at 0x00320000 (Out of memory)
mtd: read error at 0x00340000 (Out of memory)
mtd: read error at 0x00360000 (Out of memory)
mtd: read error at 0x00380000 (Out of memory)
mtd: read error at 0x003a0000 (Out of memory)
mtd: read error at 0x003c0000 (Out of memory)
mtd: read error at 0x003e0000 (Out of memory)
mtd: read error at 0x00400000 (Out of memory)
mtd: read error at 0x00420000 (Out of memory)
mtd: read error at 0x00440000 (Out of memory)
mtd: read error at 0x00460000 (Out of memory)
mtd: read error at 0x00480000 (Out of memory)
mtd: read error at 0x004a0000 (Out of memory)
mtd: read error at 0x004c0000 (Out of memory)
mtd: read error at 0x004e0000 (Out of memory)
mtd: read error at 0x00500000 (Out of memory)
mtd: read error at 0x00520000 (Out of memory)
mtd: read error at 0x00540000 (Out of memory)
mtd: read error at 0x00560000 (Out of memory)
mtd: read error at 0x00580000 (Out of memory)
mtd: read error at 0x005a0000 (Out of memory)
mtd: read error at 0x005c0000 (Out of memory)
mtd: read error at 0x005e0000 (Out of memory)
mtd: read error at 0x00600000 (Out of memory)
mtd: read error at 0x00620000 (Out of memory)
mtd: read error at 0x00640000 (Out of memory)
mtd: read error at 0x00660000 (Out of memory)
mtd: read error at 0x00680000 (Out of memory)
mtd: read error at 0x006a0000 (Out of memory)
mtd: read error at 0x006c0000 (Out of memory)
mtd: read error at 0x006e0000 (Out of memory)
mtd: write error at 0x00000000 (Out of memory)
mtd: re-read error at 0x00000000 (Out of memory)
mtd: write error at 0x00000000 (Out of memory)
mtd: re-read error at 0x00000000 (Out of memory)
mtd: skipping write block at 0x00000000
mtd: write error at 0x00020000 (Out of memory)
mtd: re-read error at 0x00020000 (Out of memory)
mtd: wrote block after 1 retries
# reboot recovery
cmagnell@vulcan:~/android-sdk-linux_86/platform-tools$

(Ignore the cat errors - that was my bad not extracting flash_image, then not pathing out to the full path of the image. Got it right the last time which is what's important.)

After this, it hung at the LG logo. Pulled the battery and tried home+voldown+power until LG logo then release - black screen (on but blank). Battery pull, try again - same thing. Battery pull and just power on. Comes up to ThundeROM no problem. "reboot recovery" from terminal - LG logo hang.

So I've hosed my recovery. Should I just try again or is there a better way to recover my recovery (recovery recovery? lol)? I read something about using fastboot to erase the recovery and reflash but I dunno what that is.

Edit: Ok, tried again, no errors this time but same results - no accessibility into recovery. Redownloaded all files and tried again, same results. Any suggestions?

 

[C_Romans116]

Ok so I was reverted to zv9 and I get a blank screen for my recovery screen. Now I'm trying to get a custom recover so I can install a rom. I'm useing terminal emulator app to type in the process and I get stuck on step two. It tells me that flash_image file is a read only file. Can anyone help?

 

[cmags]

Ok so I was reverted to zv9 and I get a blank screen for my recovery screen. Now I'm trying to get a custom recover so I can install a rom. I'm useing terminal emulator app to type in the process and I get stuck on step two. It tells me that flash_image file is a read only file. Can anyone help?

be sure that you typed the first command exactly right as it is what makes the /system writable. There are spaces that you may have missed (extra spaces added here for emphasis, use only one when typing):

# mount _ -o _ remount,rw _ -t _ yaffs2 _ /dev/block/mtdblock5 _ /system

Also, if using the terminal emulator, make sure you first type "su" so you get from the $ prompt to the # prompt. You must be rooted to do this, and give Terminal Emulator superuser access.

 

[anon(182107)]

Any chance of getting your version of clockworkmod available through Rom manager? What would it take?

Sent from my LS670 using Tapatalk

I found a way to confirm that rom manager works with cwm for optimus (v)
See my thread here
The source code for the Xionia cwm recovery would have to be sent to and accepted by the rom manager dev for us to have a chance at getting official support.
I figured both phones are Optimus CDMA (pretty much same models) and the recoveries are both obviously cwm, the same method from my thread would work.

The recovery works with rom manager, it just needs to be submitted for official support.

(Think of the future for if this phone ever got official cm7 support, or to just make life easier.)

 

[mercrapper]

I found a way to confirm that rom manager works with cwm for optimus (v)
See my thread here
The source code for the Xionia cwm recovery would have to be sent to and accepted by the rom manager dev for us to have a chance at getting official support.
I figured both phones are Optimus CDMA (pretty much same models) and the recoveries are both obviously cwm, the same method from my thread would work.

The recovery works with rom manager, it just needs to be submitted for official support.

(Think of the future for if this phone ever got official cm7 support, or to just make life easier.)

There is already a CWM recovery that works with Rom Manager for the Optimus. I was built for the Optimus V so you use the home button to select instead of the menu button.

xda-developers - View Single Post - [ROM] aospCMod for LG Optimus V | AOSP 2.3.3 / CM7 (Gingerbread) [04/03/2011]

 

[mercrapper]

Ok so I was reverted to zv9 and I get a blank screen for my recovery screen. Now I'm trying to get a custom recover so I can install a rom. I'm useing terminal emulator app to type in the process and I get stuck on step two. It tells me that flash_image file is a read only file. Can anyone help?

There's a chance that you might have a phone with a newer lcd screen that requires new video drivers that is only available on VC and VD (or newer).

If Xionia CWM was built with the older video drivers (V9 or before), then you will not be able to see anything even though it is up and running. You can test it by booting into recovery (wait for it to get to the blank screen, then press menu and see if it reboots. If your phone reboots into normal android, then the recovery is working, but with the wrong video drivers. In that case, I would recommend getting the CWM recovery from aospMOD over at XDA.

xda-developers - View Single Post - [ROM] aospCMod for LG Optimus V | AOSP 2.3.3 / CM7 (Gingerbread) [04/03/2011]

 

[C_Romans116]

Thanks for the help.

@cmags-I am pretty confident I typed it corectly, but to make sure is the mount area a zero or the letter o.
@mercrapper-If I use the LG update tool to upgrade to VC or VD would I be able to see the recovery and keep my root access, also I tried pressing menu in the blank recovery screen but nothing happened. Suggestions?

 

[anon(182107)]

There is already a CWM recovery that works with Rom Manager for the Optimus. I was built for the Optimus V so you use the home button to select instead of the menu button.

xda-developers - View Single Post - [ROM] aospCMod for LG Optimus V | AOSP 2.3.3 / CM7 (Gingerbread) [04/03/2011]

I know that's what I use. I'm saying without official support these recoveries only work with rom manager premium. Also it wouldn't hurt to have OTA supported. ( I have rom manager premium so I'm good, I was just trying to help others who might want the support.)


Sent from my Optimus V using Tapatalk

 

[zothes]

Hell yea this wasn't that hard to figure out, ends up i just had to run my z4rooter another 2-3 times so that it would properly root my phone (i realized this because my phone had not reset on any of my roots, until the final attempt)

for anyone with the $ -> # permission issue

 

[sfhub]

If Xionia CWM was built with the older video drivers (V9 or before), then you will not be able to see anything even though it is up and running.

Xionia CWMA .4 and .6 work with the new LCD. .5 does not.

 

[tirith]

Is there any way to get the set of Directions for clear data/cache (THIS IS NOT OPTIONAL FOR .....) somewhere above the directions on INSTALL DEBUG, ROM, GAPPS in that order... someone might miss them and temp brick their phone...

just sayin

 

[Blake1288]

Hey ... I have ADBshell open ... I need to know exactly what to type. I know it's posted, yes, but is it all one long sentence? Do I type root # shell to start it? Nothing is working.

 

[Blake1288]

None of this works ... at all. I can get past the first sentence then I'm met with these; "cannot create due to read only, unable to chmod no file, permission denied, and operation not permitted."

What gives?

 

[Guppy]

None of this works ... at all. I can get past the first sentence then I'm met with these; "cannot create due to read only, unable to chmod no file, permission denied, and operation not permitted."

What gives?

Read the first post completely a couple of times, of all wroks you probably missed a step and all steps need to be followed.

Sent from my LS670 using Tapatalk

 

[lichan]

I'm trying to create a second partition on my sdcard to try the Homemade Apps2SD thread started by Simon.Ponder. I got into the Advanced menu and created the partition and it removed the space from the FAT32 partition, but I don't see it in Root Explorer. Do I need to do some other things in the Recovery to complete the action? Do I need to mount it and format it?

 

[RavenSEAL]

Awesome job! Thank you!

 

[cmags]

Anyone have any input on the errors I posted a few days ago? I've tried re applying the recovery a few times with no change. I'm now running with no recovery and I don't feel comfortable doing so... =(

Sent from my LS670 using Tapatalk

 

[picasticks]

Not exactly, but I tried flashing CWMA 1.2518.6 and also ended up stuck on the LG screen. I was coming from thunderc recovery, VD, TR 1.8.2.

I did the same thing, pulled the battery and did a regular boot with no problem. But was unable to boot from recovery.

Anyway, I then reflashed thunderc and booted into it no problem. So, worst case you can probably put thunderc back on your phone.

I haven't done any real investigating and am going to be too busy for a few days so this is where I left it. But one quick thing I'd try is to erase the recovery partition before doing flash_image. i.e. "cat /dev/zero > /dev/mtd/mtd2" assuming your phone is like mine and mtd2 is the recovery partition. (Do not erase the wrong partition, check /proc/mtd first.)

 

[CullenWebb]

I don't even know where to begin. I have my Optimus S rooted and ready to go, it has the files you provided on the SD card, and I extracted the image from the RAR file.

Now what? I don't know where to input the commands you listed.

Thanks,
Cullen

 

[sfhub]

I don't even know where to begin. I have my Optimus S rooted and ready to go, it has the files you provided on the SD card, and I extracted the image from the RAR file.

Now what? I don't know where to input the commands you listed.

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.