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

[ashleysreyes]

Okay great...thanks!!

 

[psaurus81]

Congrats!. You now have a custom recovery! You can now place roms and kernels on the root of your SD card and flash them. Make sure you upgrade your radio to VD using the LG tool. I run Thunderom 1.8.2 and Xionia kernel.

 

[Hugh Johnson]

Make sure you upgrade your radio to VD using the LG tool.

Can someone explain this one - I'm a bit confused. Thanks! :-[

 

[sfhub]

Can someone explain this one - I'm a bit confused. Thanks! :-[

Radio/baseband controls the low level functions of the phone. Version LS670ZVD of the Optimus software came with ZVD radio/baseband. Many new ROMs require the ZVD (or ZVC) radio to function properly.

You should get the ZVD radio via LG Mobile Updater tool to maintain compatibility with latest ROMs. If you get the ZVD radio via the OTA update from Google/Sprint, then it will kill your capability to root. Following a specific procedure in the stickies to get the ZVD radio will preserve your ability to root. That latter method includes using the LG Mobile Updater tool.

If you don't care about the latest ROMs and your phone is otherwise working fine, don't worry about ZVD radio/baseband.

 

[doncharlie]

Oh the pain. I feel like I'm so close to getting this custom recovery in place and finally rooting permanently, but I suspect I missed something. I followed this to the letter, installed z4root, then can't get any su in the shell. All $$$ for me. My phone still shows android version 2.2.1 and some posts elsewhere said z4root doesn't work well in that case.

Any ideas what may have gone wrong here?

 

[00_wrath_00]

If your already in zv9 why not try using super one click then open sdk and command prompt and install custom recovery and permant root using adb?

Sent from my LS670 using Tapatalk

 

[doncharlie]

I guess that's my next move. Will report back later this evening.

EDIT: That one worked. Dunno what was up with z4root. It could have been a locked screen issue mentioned below. This is my second time rooting and I still don't know what 90% of these instructions are actually doing. Long story short, I'm rooted with ThundeROM installed. All is good with the world.

THANKS A TON!

 

[sfhub]

Oh the pain. I feel like I'm so close to getting this custom recovery in place and finally rooting permanently, but I suspect I missed something. I followed this to the letter, installed z4root, then can't get any su in the shell. All $$$ for me. My phone still shows android version 2.2.1 and some posts elsewhere said z4root doesn't work well in that case.

Any ideas what may have gone wrong here?

When you said you "installed" z4root, does that mean you selected permanent root?

If so, have you made sure your phone isn't on the lock screen, then typed "su" in the adb shell, then looked back on the phone for a prompt asking you for root privileges (which you then subsequently accept)?

 

[dishe]

is it safe to assume that "wipe cache partition" will wipe the dalvik cache, but not delete my user data?

 

[sfhub]

is it safe to assume that "wipe cache partition" will wipe the dalvik cache, but not delete my user data?

Don't know if the recovery is being more proactive and figuring out where dalvik-cache is being kept. It probably depends on whether you have stock behavior where dalvik-cache is kept on /data or customized behavior where dalvik-cache is kept in /cache.

 

[dishe]

Don't know if the recovery is being more proactive and figuring out where dalvik-cache is being kept. It probably depends on whether you have stock behavior where dalvik-cache is kept on /data or customized behavior where dalvik-cache is kept in /cache.

Interesting- so then what would be the proper way to wipe the Dalvik cache? On my old custom recovery, there was an option in the menu just for that.
Not sure that I even need it, but I'm experimenting here and I noticed the option wasn't there.

 

[sfhub]

Well if you are running TR, then it moved the dalvik-cache to /cache, so wiping /cache should wipe dalvik-cache also.

If you have dalvik-cache in /data, you can try wiping cache then check and see if dalvik-cache gets erased.

 

[debh945]

Interesting- so then what would be the proper way to wipe the Dalvik cache? On my old custom recovery, there was an option in the menu just for that.
Not sure that I even need it, but I'm experimenting here and I noticed the option wasn't there.

The option is there under "Advanced"

Sent from my LS670 using Tapatalk

 

[simon1419]

I haven't been able to get past the 2nd step in flashing the ROM.

It gets stuck at:
'# cat /sdcard/flash_image > /system/bin/flash_image'
and tells me 'The system cannot find the path specified.'

I have pasted the unzipped file flash_image into the SD card and in ASTRO is currently shows up in /mnt/sdcard is there something I am doing wrong?

 

[password230]

adb root shell access and navigation for newbie

If this isn't already posted it should be and if it is, sorry, maybe it'll help anyway...

For all newbies like myself: root # shell is accessed by typing:
adb shell
from the location of your adb.exe file
For me it looked EXACTLY like this:

C:\android\tools>adb shell
$ su
#

It pulled up that "$" sign after which i typed the letters "su" which brought up the ever sought after "#" sign.

If you did not change your filename for android sdk to simply "android" as I did, and if you installed it on your desktop your prompt may require something more like this:

C:\Users\name\Desktop\android-sdk_r07-windows\android-sdk-windows\platform-tools>

It would be from there that you would type "adb shell", get the "$" sign and type "su" to get the "#" sign.

Also, when su is typed your phone must be unlocked with the screen on so that you can allow access to your root from your phone.

Hope this helps some other newbies 'cause I was getting pretty frustrated with the holes in the directions from the creators of some of the kernels.

 

[mxl360]

Do you think you'll be able to fix the USB storage issue with TR ?

 

[wamuzu]

Hello, I tried flashing this, and I did, but now each time my phone boots it just says "Android system recovery!! Do not pull out battery!"

And it says "formatting data, cache" and etc.

Then it just sends me to the bootloader... What can I do to get this recovery flasher working? I tried holding down Vol. Down, Home, And power, but it just gives a black screen for a moment and then does the same thing.


If i flashed it incorrectly, then is it possible to know how to do it correctly from bootloader?

 

[sean.kirk]

same situation here, it was MUCH simpler on the pre...

 

[Guppy]

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

Sent from my LS670 using Tapatalk

 

[flumpy]

Thnx so much. (seriously)