Database Info

[recovery][32A-OR/NR]RA-magic+-v2.2.1-bladyle

Hello,
I made this port some time ago with little help from seo, but didn't make a new thread for it. Now I want more people to look at it and use it because it have many new futures and make flashing ROMs more fun
So this is actually the amon_RA latest recovery for Nexus One.
What I made is just to port it to work with our phones.
Features :
Reboot system now :: reboot your phone
USB-MS Toggle :: enable/disable USB mass storage (use when the phone is connected to your PC)
Backup/Restore
Nand backup :: Make a selective Nandroid backup
Nand restore :: Restore a Nandroid backup
Backup Google proprietary system files :: Makes a backup of the Google proprietary system files in /cache/google
Restore Google proprietary system files :: Restores the Google proprietary system files from /cache/google
Flash zip from sdcard.
Choose zip from sdcard :: Flash a zip update file from any (sub)-directory on your sdcard
Toggle signature verification :: Toggles the signature verification for zip files.
Wipe
Wipe ALL data/factory reset :: wipes /data + /cache + entire ext partition + all apps installed on your sdcard (froyo a2sd).
Wipe /data :: wipes /data.
Wipe /cache :: wipes /cache.
Wipe /sdcard/.android_secure :: wipes all apps installed on your sdcard (froyo a2sd).
Wipe /sd-ext :: wipes the entire ext partition on your sd (if present).
Wipe Dalvik-cache :: wipes the dalvik-cache located in /cache + /data + /sd-ext is present.
Wipe battery stats :: reset the battery calibration.
Wipe rotate settings :: reset the sensor calibration.
Partition sdcard
Partition SD :: Interactive SD partitioning
Repair SD:ext :: Repair the ext partition
SD:ext2 to ext3 :: Convert ext2 to ext3
SD:ext3 to ext4 :: Convert ext3 to ext4
Mounts
(Un)Mount /system
(Un)Mount /cache
(Un)Mount /data
(Un)Mount /sd-ext
(Un)Mount /sdcard
Other
Fix apk uid mismatches :: Does extacly that
Move recovery.log to SD :: Moves the recovery log file to your sdcard. (Use when you want more detailed recovery log information)
Power off :: Powers off your phone
Click to expand...
Click to collapse
Use the trackball (up+down) to navigate through the menu, press the trackball to select items. Use the Volume-down key to go back to a previous menu.
Download:
recovery-RA-magic+-v2.2.1-bladyle.img
MD5sum: 98A8CAE41C0A7D2AEF69A4F62F2F6475
Install:
From fastboot:
Code:
Copy recovery-RA-magic+-v2.2.1-bladyle.img to a location where fastboot can find it.
Boot your phone into fastboot mode (power on while holding the back)
Connect your phone via usb to your pc/mac/...
fastboot devices (to make sure that fastboot "sees" your phone)
fastboot flash recovery recovery-RA-magic+-v2.2.1-bladyle.img
You can use RadioSwitchGUI_v4 too!
If you want just to try it:
Code:
fastboot boot recovery-RA-magic+-v2.2.1-bladyle.img
Thanks and credits go to :
Amon_RA
seo
carz12

sorry. ask a stupid question.is this recovery for 32a, 32b or both?
Sent from my Dream/Sapphire using XDA App

smartvincent said:
sorry. ask a stupid question.is this recovery for 32a, 32b or both?
Sent from my Dream/Sapphire using XDA App
Click to expand...
Click to collapse
sorry i forgot to mention this...it is for 32a only
I can try to make 32b version too but I need someone to test it.

Bladyle said:
sorry i forgot to mention this...it is for 32a only
I can try to make 32b version too but I need someone to test it.
Click to expand...
Click to collapse
If you make a 32b version i'd gladly test it

I've been using this recovery for some time and it runs perfectly. And it works in both new and old radio. Great work!
Note: It's features and not futures.

using this recovery too and im really happy with this! thank you Bladyle! great job!

thank you guys
BTW I need some testers to PM for 32B/MyTouch 1.2 port

I'm also using this on my Old Radio Magic, haven't tested on new radio yet
it works well

New radio, excellent work
Sent from my Sapphire using XDA Premium App

works like a charm with new radio

Bump. This amazing recovery need to be on the first page!

kanttii said:
Bump. This amazing recovery need to be on the first page!
Click to expand...
Click to collapse
Thanks mate!
This is my default recovery on my device.

Bladyle said:
Thanks mate!
This is my default recovery on my device.
Click to expand...
Click to collapse
For me too. When you first posted it, I didn't dare to try, but after a few days I did..and since then I have been using this all the time! A week ago I tried CWM to see if a ROM could be flashed through that, but since CWM is so frustrating with all the nonononono's I had to get back to yours. And it's amazing as I already said!
Thank you!

Hi bladyle ,
I´ve read this thread about your updated RA-recovery. Because of the fact, that I´ve a google branded magic, I can´t flash this recovery. So my ask to you, if you could make a 32B Version or could tell the steps, how to port a recovery from another device.
Greets

I would also be glad to test a 32B port of this. Just let me know!

Can somebody reupload this? Please...

blaster44 said:
Can somebody reupload this? Please...
Click to expand...
Click to collapse
first post updated

Bladyle said:
first post updated
Click to expand...
Click to collapse
my bad....

Wow...New radio version thanks for the great work
Sent from my HTC Magic

I'm glad you like it

Amon Ra Style Recovery for Supersonic

I have had several requests for a supersonic recovery from my forked Amon Ra source.
The recovery binary and several binaries have been compiled for armv7-neon so it should be faster. Also many new features have been added/updated. Capactive keys also work.
To also make it clear this recovery will restore both existing clockwork mod backups and Amon Ra backups.
Recovery Features:
ADB as root user
USB-MS Toggle :mounts sdcard as mass storage
Backup/Restore:
Nand Backup : Select Items to backup with the [X]
Nand Restore : browse to and select nandroid backup to restore
Nand Restore Clockwork : browse to and restore cwm backup
Flash Zip From Sdcard: Update.zip must be in root of sdcard or you can directory browse.
Toggle Signature Verify : Turn of signature checking on flashing zips
Wipe Menu:
Wipe data/factory reset: wipes all
Wipe cache
Wipe Dalvik cache : Wipes Dalvik cache in all possible locations if moved by apps2sd
Wipe SD:ext : Wipes Apps2sd ext partition
Wipe Battery Stats
Wipe rotate settings
Wipe data only
Wipe system
Wipe sdcard
Wipe .android secure : Wipes froyo native .android_secure on sdcard
Partition Sdcard:
Partition SD: Partition's sdcard for apps2sd (this formats card so all non backed-up data is lost)
Repair Sd:ext
SD:ext2 to ext3 : coverts apps2sd ext2 partition to ext3
SD:ext3 to ext4 : same as above but ext3 to ext4 (
Mounts:
Gui mounts to avoid typing in terminal to mount and cd into a dir to mount system, data, cache, sd-ext (if exists), sdcard
Other:
Fix Permissions
Move recovery log to SD
Key Test : Output keycodes for debugging recovery
Check Battery Lvl
Developer menu:
Make and flash boot from zimage : This makes a mkboot folder on sdcard and mounts sdcard as mass storage then you copy a zImage and kernel modules into this folder and it will create a new boot like anykernel and flash it.
Install su & superuser: Installs or fixes su & superuser install (removes old if exists)
Install eng (unguarded) su: Installs engineering su that doesn't use superuser (removes old su & superuser if exists)
Reboot to bootloader: reboots to bootloader/hboot
Reboot recovery : reboots phone back into recovery
I have included flash_eraseall binary to recovery which can be used to fix/erase corrupted partitions that will not mount correctly to nandroid restore to.
Useage from adb shell is : flash_eraseall /dev/mtd/mtd4 (where mtd4 is the number of the partition from "adb shell cat /proc/mtd" you want to erase)
Trouble Shooting:
Use option under Other menu to move recovery log to sd. Mount your sdcard to pc and read that file called recovery.log. It should have detailed cause of error.
Special Thanks:
Thanks to :
Amon Ra
Koush
Testers
Latest v3.11 is here http://forum.xda-developers.com/showpost.php?p=21004734&postcount=383
Changelog 3.07:
As per captain throwback's suggestion this one allows a selective restore of backup items on a nandroid restore.
PC36IMG-AmonRA-3.07-gnm.zip
MD5 =940b7d56701473731da2fb58bbaae9a6 PC36IMG-AmonRA-3.07-gnm.zip
recovery-ra-supersonic-3.06-gnm.img
MD5= 2976958267bb43c5c15a18739f90ace4 recovery-ra-supersonic-3.06-gnm.img

Well done, sir!
Capacitive Back button works, ability to restore CWM backups, and no graphical anomaly on Reboot.
This one's definitely a winner, and my new recovery .
Any known bugs at this time?

Captain_Throwback said:
Well done, sir!
Capacitive Back button works, ability to restore CWM backups, and no graphical anomaly on Reboot.
This one's definitely a winner, and my new recovery .
Any known bugs at this time?
Click to expand...
Click to collapse
Nope none at all

Do we just change to PC36IMG.zip and update thru bootloader?
Sent from my PC36100 using Tapatalk

latingonzo86 said:
Do we just change to PC36IMG.zip and update thru bootloader?
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Yeah, I was wondering too. I tried to do it through terminal with the "flash_image recovery" command as SU and kept getting denied.

I used Android Flasher to do it.

Well I just tried thru hboot and no dice. It started to parse the package then it said not zipped correctly. Could u maybe zip it for us bro?
Sent from my PC36100 using Tapatalk

Should be able to add your android-info.txt from an ruu and rename to recovery.img and zip it up as PC36IMG.zip or flash via fastboot flash recovery nameofrecovery.img if you have it or via flash_image.
To clarify the android-info.txt and recovery named recovery.img are what you zip to make a PC36IMG.zip

I'm on the 3D now, but I gave you a thanks anyway man, used to use your work all the time back in the WM days!
Infected in 3D

latingonzo86 said:
Well I just tried thru hboot and no dice. It started to parse the package then it said not zipped correctly. Could u maybe zip it for us bro?
Click to expand...
Click to collapse
hboot and fastboot commands didn't work for me either. i grabbed an old amon-ra PC36IMG file and replaced that recovery image with this new one. worked for me. here it is. no promises that your phone won't blow up.
http://www.mediafire.com/?n8yafvl318ulv39
Just make sure you rename it to PC36IMG.zip and place it on the root of your SD card. Reboot into Bootloader/Hboot. Once it scans your memory card, it'll automatically ask you if you want to flash the new recovery. Follow on-screen prompts.
Glad to see it works for you guys!

Thanks bro.
Sent from my PC36100 using Tapatalk

So what are going to name this Amon RA SRS i assume right.\ Anyways pretty damm good i say.

mercado79 said:
hboot and fastboot commands didn't work for me either. i grabbed an old amon-ra PC36IMG file and replaced that recovery image with this new one. worked for me. here it is. no promises that your phone won't blow up.
http://www.mediafire.com/?n8yafvl318ulv39
Just make sure you rename it to PC36IMG.zip
Click to expand...
Click to collapse
worked great for me. thanks button has been hit for both you and OP. maybe OP can put the .zip file in OP. lol

So this will restore CM back ups, but not restore AMon Backups correct?

joetowel said:
So this will restore CM back ups, but not restore AMon Backups correct?
Click to expand...
Click to collapse
Pretty sure it will restore AR backups

Will try in the morning.
Sent from my PC36100 using xda premium

Just flashed it,works like a charm! I really like the "wipe sdcard" is the last option.. Will definitely stop alot of people from accidentally wiping it haha.
Sent From my Verizon powered Evo 4G!

You rock brother. Amazing work. Thanks.
Sent from my PC36100

joetowel said:
So this will restore CM back ups, but not restore AMon Backups correct?
Click to expand...
Click to collapse
It works for both. I updated the nandroid but made sure it stayed backwards compatible.

Just wanna say thanks. Op says update.zip has to be in root of sd, does that mean any file I flash has to be in root or can I flash from within a folder. Also does this support edify or amend, or both?

[Q] Enrcyption Support for ClockWorkMod Recovery

Hello,
i have just installed the official stock ICS 4.0.3 Rom to my Nexus S and everything was really fine... until i tried to root it. As someone who tries to take security seriously, i immediately encrypted the device using the tools provided by ics (works ok).
but unfortunatly it's now not possible anymore to mount /sdcard while in recovery, which makes rooting and installing updates impossible (or is there any other way? eg. fastboot?).
therefore my question: will clockworkmod recovery support ics encrypted devices in the (near) future? i know its gonna be a p.i.a. to type a password with only the volume buttons, but hey
i like the encryption and would like to keep it, but not beeing able to use recovery like before is a big drawback...
greetings
Georg

Same for me.
Hope to see encryption support in clockworkmod soon.
I bought Rom manager premium even if I never flash from rm just to support the developers... hope they will be able to get it sorted out

Op -- I'm interested in this for when my phone (EVO 3D) finally gets ICS. Will you post an update to this thread if you hear anything?
BTW, with TWRP getting touchscreen support, it can't be too much longer before CWM gets touchscreen since I think the guys in TWRP were going to start contributing to CWM, from what I've heard anyway. So that would solve the password typing problem.

Georg, thanks for asking this question as I've been wondering the same exact thing. Hopefully we'll get a good answer soon.

Alternatives for ClockworkMod Recovery
I encrypted my device (the Exchange account I added required it) n... now I cant do anything in recovery ... it wont mount the drive ... any suggestions for a replacement ...
thanks ...

mrosensweig said:
I encrypted my device (the Exchange account I added required it) n... now I cant do anything in recovery ... it wont mount the drive ... any suggestions for a replacement ...
thanks ...
Click to expand...
Click to collapse
Its because the way encryption works you have to boot and enter code, that's the whole point, no recovery can do it atm
Sent from my ice cream powered Nexus S

small update:
nothing new on the subject, but i didnt check out the new touch recovery (anyone tried it yet?).
in the mean time i went back to an unencrypted CM9...

I didn't read anything about encryption so did not upgraded to the touch recovery yet

you should lock the bootloader if someone is nagging you

jomir said:
small update:
nothing new on the subject, but i didnt check out the new touch recovery (anyone tried it yet?).
in the mean time i went back to an unencrypted CM9...
Click to expand...
Click to collapse
Jomir, what was the procedure you used to get back to CM9? Is it possible to repartition, erasing the encrypted partitions so a new rom can be flashed? How?
Thx,
rmsilva

rmsilva123 said:
Jomir, what was the procedure you used to get back to CM9? Is it possible to repartition, erasing the encrypted partitions so a new rom can be flashed? How?
Thx,
rmsilva
Click to expand...
Click to collapse
Restore a backup or do a clean install(format boot, system, cache and data)
Sent from my ice cream powered Nexus S

DarkhShadow said:
Restore a backup or do a clean install(format boot, system, cache and data)
Sent from my ice cream powered Nexus S
Click to expand...
Click to collapse
Thanks for the reply, DarkhShadow. The problem is that CWM can't wipe or format these partitions, since it can't mount /sdcard (which is encrypted). If I could only access the external sdcard from within CWM, I could just wipe everything and then install a new rom. But since it can't mount /sdcard, I can't access sd-ext. nvflash is not an option, since my TF101 is B90. Is there a way to either restore the stock recovery (overwrite CWM) or boot from the external SD so I can run a script such as "super wipe full" (http://forum.xda-developers.com/showthread.php?t=1245892)? Maybe there's a way to run the wipe script through adb? If I can just format the partitions (which is what the script does), then CWM would be able to mount /sdcard and, consequently, the external SD and I can flash a new rom (such as revolution HD 3.0.1).
Thanks,
rmsilva

Honestly idk then, try a factory reset on phone(ie booted up) and then maybe it will be unencrypted?
Sent from my ice cream powered Nexus S

The funny thing is that stock recovery on an encrypted phone can write to the disk, but only from a warm reboot (perhaps the kernel stays resident?).
When I say write to disk I say apply the leaked OTA update, 4.0.4 for the VZ Gnex. And correct me if I am wrong, it's writing and mounting the disk, no?
Anyhow, this is done from stock recovery which is open source. So you ask yourself, why can't Koush support mounting the disk from a warm recovery state reboot? Maybe he doesn't know this?
DarkhShadow said:
Its because the way encryption works you have to boot and enter code, that's the whole point, no recovery can do it atm
Sent from my ice cream powered Nexus S
Click to expand...
Click to collapse

rmsilva123 said:
Jomir, what was the procedure you used to get back to CM9? Is it possible to repartition, erasing the encrypted partitions so a new rom can be flashed? How?
Thx,
rmsilva
Click to expand...
Click to collapse
i did a factory reset (from the settings menu), installed recovery per adb/fastboot and installed cm9 from sdcard in recovery.

Use tmpfs to install a new ROM in crypted system
Hello Everyone
To flash a new ROM you can do as follows:
boot in Recovery
format cache partition
from your PC use adb to mount /sdcard as tmpfs:
adb shell mount -t tmpfs none /sdcard​
put your ROM on the (fake) sdcard
adb push <your rom> /sdcard​
use the recovery to flesh the ROM as usual
This worked form me.
Sorry to be late...

What about a nandroid backup or restore? How big is /cache?
orcruin said:
Hello Everyone
To flash a new ROM you can do as follows:
boot in Recovery
format cache partition
from your PC use adb to mount /sdcard as tmpfs:
adb shell mount -t tmpfs none /sdcard​
put your ROM on the (fake) sdcard
adb push <your rom> /sdcard​
use the recovery to flesh the ROM as usual
This worked form me.
Sorry to be late...
Click to expand...
Click to collapse

Sorry I didn't try with a nandroid backup but I think it is too big to fit the device memory...
You can backup data inside the sd partiton (phone up and running, just to don't lose data...), boot into recovery, format sdcard partition, mount it, put the backup in the sdcard and after install the nandroid backup...
I think that it could work but I am not sure. If after formatting the sdcard you can mount it, the task is done. You can put the backup on it using adb push and flash using recovery.
If you try please give me some news.
Regards

orcruin said:
Hello Everyone
To flash a new ROM you can do as follows:
boot in Recovery
format cache partition
from your PC use adb to mount /sdcard as tmpfs:
adb shell mount -t tmpfs none /sdcard​
put your ROM on the (fake) sdcard
adb push <your rom> /sdcard​
use the recovery to flesh the ROM as usual
This worked form me.
Sorry to be late...
Click to expand...
Click to collapse
I'm kind of a noob when it comes to adb. What is that process doing exactly? How big is the fake sdcard? I want to make sure I understand all the implications before I dive in. Of course I need HTC to release a ICS ROM first. ;-)

thx1200 said:
I'm kind of a noob when it comes to adb. What is that process doing exactly? How big is the fake sdcard? I want to make sure I understand all the implications before I dive in. Of course I need HTC to release a ICS ROM first. ;-)
Click to expand...
Click to collapse
First it formats the cache partition. Then mount the /sdcard so that you can access it from your pc. After you mount the /sdcard, you can put your rom zip into it. After the zip has been transferred into /sdcard, you can flash the zip as usual.
Since nexus s doesn't have sdcard slot, it mounts the internal storage as '/sdcard' to treat it like a sdcard, thus 'fake' sdcard. The 'fake' sdcard is around 13GB.

[Q] [Help] CWM can't mount sd-ext? (LG-P500)

As I was getting low on my LG-P500 phone, I tried looking for some app2sd solution, doing the following steps:
- Backup all SD card content to PC
- Boot into recovery (CWM5.0.2.7)
- From recovery, create sd-ext partition
- From recovery, format the new partition
- From recovery, mount usb device, restore all SD card content from PC.
- Reboot device, installed link2sd and managed to link applications to sd.
Now link2sd seems to work fine- I tried linking quite a few applications and all of them work fine, no complaints. It only gave me an error with some apps which I have previously *moved* to SD using Titanium backup, but upon moving them to internal storage link2sd picked them okay.
However, I noticed that using file explorer, root explorer etc- they all show the sd-ext partition as empty, with size of 0 bytes??
Then, I booted into recovery and tried to mount the sd-ext partition, but I get an error message... (all other partitions I can mount/unmount just fine).
To be sure, after each reboot it looks like all the applications linked2sd work appropiately, so everything looks fine.
However, now I am concerned whether I can create (and restore, of course) nandroid backups- what will happen with all these apps linked to sd? Am I right that CWM may not be able to backup (and therefore restore) anything that is on this partition?
Am I going to lose all these apps and data? Does TiB backup these apps+data and be able to restore them fine to sd-ext? I'm asking about TiB as a mediocre workaround of restoring applications that were in sd-ext (and thus omitted by CWM backup). That is, after restoring nand backup- doing an additional restore from TiB??
Any help/insight is welcome
Ah, yes, some more info:
Phone: LG optimus P500
ROM: Lupohirps CM9 4.0.3 from this thread http://forum.xda-developers.com/showthread.php?t=1558213
Recovery: CWM 5.0.2.7 (By the way, whenever I try to flash 5.0.2.0 I get an error...)

that's weird since the app working. what ekstension do you have on sd card fat? fat32?

Can you open Android Terminal (https://play.google.com/store/apps/details?id=jackpal.androidterm) and issue these commands:
su
busybox ls -la /sd-ext/
busybox mount
If /sd-ext doesn't show up in mount, then it is not mounted.
Actually CM9 for P500 lacks file /system/etc/init.d/05mountsd (this file is responsible for mounting /sd-ext). IMHO You should ask ROM developer about sd-ext support.
If you want to test (and potentially restore your Nandoid backup or reflash CM9 afterwards) I can give you this script from CM7 (actually modified version that allows any ext version).

Your sd-ext files are actually in data/sdext2, not in /sd-ext.
Also Try using Amonra 3.0.6, overall it has better sd-ext support, I find it mounts and wipes things like dalvick cache inside the sd-ext partition as well , which is handy, unlike CWM.

Thanks for all your replies!
Sdcard file system is fat32. For the partition I have no idea as cwm didn't ask for any specific (e.g. ext2/3/4) and I haven't seen any way to get this Info...
Anyway, following this thread, I did find that all the app/data is in /data/sdext2- not sure what it means in terms of nandroid backup& recovery but it looks more reassuring..
As to RA recovery, I'm not in particular in love with cwm- it is just what I'm used to from other android devices I've been using. Actually on my htc mt4g I was using ext4 touch recovery and that one I really liked, but it is not supported in lots of devices. That phone was stolen, unfortunately. I'll give it a try, though.
Sent from my GT-P7510 using Xparent Cyan Tapatalk 2

DavisNT said:
Can you open Android Terminal (https://play.google.com/store/apps/details?id=jackpal.androidterm) and issue these commands:
su
busybox ls -la /sd-ext/
busybox mount
If /sd-ext doesn't show up in mount, then it is not mounted.
Actually CM9 for P500 lacks file /system/etc/init.d/05mountsd (this file is responsible for mounting /sd-ext). IMHO You should ask ROM developer about sd-ext support.
If you want to test (and potentially restore your Nandoid backup or reflash CM9 afterwards) I can give you this script from CM7 (actually modified version that allows any ext version).
Click to expand...
Click to collapse
Thanks! Looks likeb system/ cache/ data are all yaffs2, /mnt/Sdcard is vfat and /data/sdext2 is ext4. Not sure what all the output means (relatime, barrier=1, data= ordered etc. etc.)
So, can I figure out where the /data/sdext2 is physically stored? Is it actually the sd-ext/ext4 partition? Looks like must have, as its contents are way bigger than phone's 200MB internal storage...
Thank you all again
Sent from my GT-P7510 using Xparent Cyan Tapatalk 2

jaibar said:
Thanks! Looks likeb system/ cache/ data are all yaffs2, /mnt/Sdcard is vfat and /data/sdext2 is ext4. Not sure what all the output means (relatime, barrier=1, data= ordered etc. etc.)
So, can I figure out where the /data/sdext2 is physically stored? Is it actually the sd-ext/ext4 partition? Looks like must have, as its contents are way bigger than phone's 200MB internal storage...
Thank you all again
Sent from my GT-P7510 using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
/data/sdext2 is the mountpoint for the ext4 partition thats on your sd card, physically its obviously on your sd card, but If you use linux, data/ is where the all partitions other then home partition get "attached"/mounted to, the 11link2sd script made by link2sd in yout init.d folder actually mounts it sdext2, the name means nothing, just something link2sd names it as.
---------- Post added at 08:40 PM ---------- Previous post was at 08:30 PM ----------
So Basically nandroid will not back it up under /data/sdext2 as the script runs after recovery, the best way to backup apps that are on the ext partion is back them up using Titanium Backup, as that saves the real apks, and when you restore all your apps, select link2sd to automatically move them to sd-ext partition.

Hi at all,
at first sorry for my bad english.
I had a similar case. If I made a backup with cwm 5.0.2.7, cwm cant mount/read the sd-ext.
In a other thread a user wrote, that cwm 5.0.2.8 had problems with the sd-ext.
And he does downgrade to cwm 5.0.2.0, and than cwm will work.
So, I did this:
I open the rommanager and choose the option "install Clockworkmod", now I choose the "LG Optimus One (old BB)".
But i have the new baseband on my O1.
The basis of this is, if you choose the new baseband in the rommanager, he will install cwm 5.0.2.7. For the old is it the 5.0.2.0 version.
Now, Rommanger made the installation with cwm 5.0.2.0. to my phone.
After this i go in to the recovery and made my nand-backup. It works perfekt!
No problems with the sd-ext, after I did this.
May be this will help.

Fietz said:
Hi at all,
I open the rommanager and choose the option "install Clockworkmod", now I choose the "LG Optimus One (old BB)".
But i have the new baseband on my O1.
The basis of this is, if you choose the new baseband in the rommanager, he will install cwm 5.0.2.7. For the old is it the 5.0.2.0 version.
Click to expand...
Click to collapse
Thanks for the tip..
I have tried in the past to flash cwm 5.0.2.0 via Rom Manager, but I kept getting an error message, so I gave up.
Now I thought to give it a second chance, but as it fails to flash with Rom Manager (in the menu when I choose LG optimus one I don't get any choice between old BB or new or anything- it just reflashes 5.0.2.7) and from the "all recoveries menu I can only choose 5.0.2.0 but it gives an error message), so I downloaded the zip files from this thread http://forum.xda-developers.com/showthread.php?t=1523050 (including also Amon Ra 3.06) and tried to manually flash from recovery.
It flashed and showed recovery as "5.0.2.0" but nothing worked- every submenu that I tried to enter was black screen (with the CWM logo on background) and it gave me the creeps- I don't like being stuck without a functional recovery so I rebooted and flashed 5.0.2.7 again from Rom Manager.
I'll try to flash Amon Ra and see how it works.
[EDIT] flashed AmonRa 3.06 and it seems to work fine- able to mount/unmount all partitions including sd-ext, and it also has an option to check each of them in separate during nandroid backups.
A noobish question: it has also an option to include the ".android_secure" . Isn't this one a redundancy with sd-ext (e.g. contains all the apps/data that has been moved/linked2sd)?

jaibar said:
As I was getting low on my LG-P500 phone, I tried looking for some app2sd solution, doing the following steps:
- Backup all SD card content to PC
- Boot into recovery (CWM5.0.2.7)
- From recovery, create sd-ext partition
- From recovery, format the new partition
- From recovery, mount usb device, restore all SD card content from PC.
- Reboot device, installed link2sd and managed to link applications to sd.
Now link2sd seems to work fine- I tried linking quite a few applications and all of them work fine, no complaints. It only gave me an error with some apps which I have previously *moved* to SD using Titanium backup, but upon moving them to internal storage link2sd picked them okay.
However, I noticed that using file explorer, root explorer etc- they all show the sd-ext partition as empty, with size of 0 bytes??
Then, I booted into recovery and tried to mount the sd-ext partition, but I get an error message... (all other partitions I can mount/unmount just fine).
To be sure, after each reboot it looks like all the applications linked2sd work appropiately, so everything looks fine.
However, now I am concerned whether I can create (and restore, of course) nandroid backups- what will happen with all these apps linked to sd? Am I right that CWM may not be able to backup (and therefore restore) anything that is on this partition?
Am I going to lose all these apps and data? Does TiB backup these apps+data and be able to restore them fine to sd-ext? I'm asking about TiB as a mediocre workaround of restoring applications that were in sd-ext (and thus omitted by CWM backup). That is, after restoring nand backup- doing an additional restore from TiB??
Any help/insight is welcome
Ah, yes, some more info:
Phone: LG optimus P500
ROM: Lupohirps CM9 4.0.3 from this thread http://forum.xda-developers.com/showthread.php?t=1558213
Recovery: CWM 5.0.2.7 (By the way, whenever I try to flash 5.0.2.0 I get an error...)
Click to expand...
Click to collapse
Hi, Jaibar
I have LG Optimus One with JB 4.2.2, CM 10.1.
Here what I have done in order to gain extra space on my internal memory. All the steps that you have followed are the same as I did. BUT! There are two important things that I have followed that had greatly helped to succeed:
1) For every 100Mb internal memory - NO MORE than 512Mb of SD card memory(for my LG I have separated 965Mb on the SD card)
2) INT2EXT+ works with EXT2/3/4 partitions BUT INT2EXT4+ works with ONLY EXT4 partition. After I have watched this short video, and this blog post I have been able to restart my phone with extended internal memory.
Believe me, for three days I have been flashing my phone, trying to find the correct way. At the end I have noticed that the problem was that I couldn't mount /sd-ext I thought that maybe following this two rules will help - and it did!
I hope that it will help! Good luck

Can't backup sd-ext even though I partitioned it correctly.

Hi,
I used ROM Manager Premium v5.0.1.5 to partition my sd card and linked the apps with link2sd which worked just fine.
Problem is, when I wanted to backup the system ROM Manager didn't recognize my partition.
Why would that happen since I used ROM Manager itself to create the partition in the first place?
Doesn't make much sense that the app creates it and then can't backup it at all.
Can anyone shed some light on this issue?
Thanks!

Used EASEUS Partition Manager and it actually showed the partition as OTHER so I formatted it into EXT3. Still no luck mounting it through ROM Manager.
EDIT: Flashed CWM Recovery v.5.0.2.0 and after partitioning the sd card again it now mounts/backups it correctly. You can get it from: http://forum.xda-developers.com/showthread.php?t=1523050
EDIT: The earlier version of CWM doesn't work either. Flashed AmunRa recovery and it seems to work now.

i think its prblm with the clockwork mod recovery. instead of usng it try amonra recovery(flash amonra recovery and dnt use rom manager for this)

clockworkmod told me sd-ext backup is not supported on my device...
when i cleared my sdcard partition and did a backup it backed up sd-ext also.
i believe i just had not enough space on my sdcard..? may fix your problem