CWM source is part of CM and is generally freely available, however, that is "only" the button controlled version at the mo. I'm sure Koush has his reasons for not pushing it yet.
I hold up and down on volume the entire process only takes a minute.
Sent from my LG-G2X
AOKP build 29 w/ Harsh P999-0604
Is the device appearing in Device Manager showing as a USB device?
Sent from my LG-G2X
AOKP build 29 w/ Harsh P999-0604
I can use the soft keys with my CWM which is 4.X.CWM source is part of CM and is generally freely available, however, that is "only" the button controlled version at the mo. I'm sure Koush has his reasons for not pushing it yet.
I followed the instructions in the OP and everything worked flawlessly. I'm able to boot into CWM 5.0.2.8 with no problem by holding Volume-Down & Power buttons until the blue LG logo appears.
But here's my question: Is there any way to get the ROM Manager app to recognize 5.0.2.8? When I attempt to boot into CWM from ROM Manager, it goes into 5.0.2.0. Which is surprising, as I thought it would've been replaced by the new version.
If there's no way to force ROM Manager to use it, no biggie. But, is it harmful in any way to have 2 different CWMs on the same device?
Sent from my LG-P999 using xda premium
Take 3 works for me. I booted into recovery from ROM. I can backup, restore, fix permissions, and also mount sdcard. Thanks
I followed the instructions in the OP and everything worked flawlessly. I'm able to boot into CWM 5.0.2.8 with no problem by holding Volume-Down & Power buttons until the blue LG logo appears.
But here's my question: Is there any way to get the ROM Manager app to recognize 5.0.2.8? When I attempt to boot into CWM from ROM Manager, it goes into 5.0.2.0. Which is surprising, as I thought it would've been replaced by the new version.
If there's no way to force ROM Manager to use it, no biggie. But, is it harmful in any way to have 2 different CWMs on the same device?
Sent from my LG-P999 using xda premium
The one you flashed with this guide is your real recovery that you use when you hold the power and Vol keys. The older one is the one that's fake flashed by Rom manager. You can update this from in the app. (i think 5.0.2.0 is the newest one that it uses though.)
Either way, as long as they are both newer than 5.0.x.x then you are fine, having 2 different versions hurts nothing.
Edit: it *may* screw up backups when they are done between the 2 different versions, but I'm not actually sure.
Sent from my LG-P999 using Tapatalk
I've had version 4 on my phone since I first rooted it an didn't updated it till now. A couple of backups ago I did it with the CWM in the ROM. 5.0.2.0. I tried to go to that nandroid through the v4. Wouldn't open. Took me a couple days realize this was the problem. Make your nandroids with the older version if you have 2 different ones.
Sent from my LG G2x with XDA app because I can.
By request a quick explanation of the difference between the two recoveries:
Usually, your recovery image will look on the external SD card for ROMs to flash, and backups to restore, and the external version here is no different. For the most part that is fine and dandy (unless you don't have an SD card I guess), however the stock O2X mounts it's internal SD card as /sdcard, which confuses ROM Manager a fair bit.
The internal version of the recovery mounts the internal storage as /sdcard as well, so ROM Manager can find backups it's made etc.
NOTE: Backups made with v5 are not compatible with earlier versions.
chmod +x flash-recovery.sh
./flash-recovery.sh
That's quite impressive, considering the first place I 'released' it on was XDA.Im being serious. I have absolutely no issues whatsoever with this recovery. Been running before it was even released on XDA. I have no reason to lie about it.
Sent from my LG-P999 using Tapatalk 2
I realized that that the model is still p990 so when a ROM uses get prop p999... KABOOM. It fails to flash. I might have a chance to fix that later today unless someone else does first.
I figured only the partition table needed to change, but couldn't decompile the .img.
Seems easy enough to fix anyway.