[Multiboot] [Update 14/6/11] Create, manage and boot your ROM options via CWM! - Sony Ericsson XPERIA X10 Mini

Introduction
This thread describes an experimental mod that allows you to boot into other boot images stored in your sdcard. It's a good reason for users to upgrade to CWM recovery since it allows for much more extended functionality. It's also another good reason for devs to support CWM recovery.
Our 'petit' X10mini does not have enough internal memory to store more than one android image, thus we have to use the sdcard for this.
WARNING:
This mod is experimental, and for advanced users only. Use it at your own risk
Requirements (READ THEM CAREFULLY):
- CWM recovery pre-installed
- You need a FAST enough sdcard. I'd suggest not using this mod if your sdcard is less than Class 6
- Your sdcard should have enough free space. Each 'boot option' that you create reserves 400MB of space in your sdcard
- In order to create a new boot option, you need a flashable zip of the ROM you wish to boot to, as well as a patch for it's ramdisk.tar (if this is a custom ROM, stock ROMs don't need this). The flashable zip of the ROM is the same that is used for usual ROM installation. The patch should be provided by the ROM's cook.
Instructions for devs only
To create a bootable image, you have two options:
- Make use of CWM recovery (which can create boot images from update.zip) and provide a patch for your ROM that makes sure: app2sd is disabled, ramdisk.tar does not mount mtd* partitions under /system, /data, or /cache. This patch is also flashable via the new multiboot menu of CWM. If you need more info, see the attached MiniCM7-multiboot.zip
OR
- Manually create ext2 system.img, data.img and cache.img for users to push under /sdcard/clockworkmod/multiboot/<name>/
Multiboot mod Installation
- Flash the attached CWM multiboot zip via CWM
Multiboot ROM Installation
The following scenario is provided as a proof of concept in order to install MiniCM7 as a boot from sdcard option
- Reboot into the new recovery and navigate to the new 'multiboot' menu. There you'll see the following options:
Select default boot option
Unset default boot option
Create boot option from zip
Delete existing boot option
Flash zip to boot option
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- Select multiboot->Create boot option from zip and then pick the MiniCM7 flashable zip (which you can find in the MiniCM7 thread). Be patient, this step reserves the space and flashes the selected zip to the system.img in the sdcard
- Select multiboot->Flash zip to boot option, pick your newly created boot option and then pick the MiniCM7-multiboot.zip. This will flash the patch needed for MiniCM7 in order to make it run from sdcard. You can use this option in order to flash any zip you want to any of the boot options you have already created
- Select multiboot->Select default boot option and pick your newly created boot option
- Reboot (first boot will take some time depending on your sdcard speed).
To verify you have booted to your newly created boot option, check 'adb shell mount', it should say that /system /data and /cache is mounted from /loop* devices and not from mtd*
Uninstall
- Practically, if you flash a ROM image it will revert CWM / chargemon to its original state. There is not problem in keeping this CWM / chargemon version though.
- To revert booting from your phone's memory instead of the sdcard, navigate to multiboot->Unset default boot option
- To remove installed boot options, navigate to multiboot->Delete existing boot option and pick you choice. Alternatively remove the boot option you want from /sdcard/clockworkmod/multiboot/
Disclaimer:
I can't be held responsible if this mod bricks your device / trashes your sdcard or makes it explode in your hands! Use it at your own risk!
​

wao great experiment NAA,
perfect time to install stock 2.1 and miniCM7

Damn, Great job nAa! My sdcard is lower than Class 6 (I am still using the stock 2GB sdcard!!) so I can't try this one. Waiting for other people's opinion about this.

Great work! =)

A class 4 sd is good?
Enviado desde mi X10mini usando Tapatalk

twins.7 said:
wao great experiment NAA,
perfect time to install stock 2.1 and miniCM7
Click to expand...
Click to collapse
IMHO, stock 2.1 should be installed as a 'multiboot option' and MiniCM7 in the internal phone's memory - not the other way round.
I'm hoping some dev could chip in with an update.zip for a stock 2.1 ROM that can be installed as a multiboot option

Damn, where the f**k is the "Thanks" button in tapatalk!?
Another great addition mate! Thank you for giving us, mods that other devices hadn't even dreamed of!
Regards,D_d
Sent from my Desire HD using Tapatalk

nobodyAtall said:
IMHO, stock 2.1 should be installed as a 'multiboot option' and MiniCM7 in the internal phone's memory - not the other way round.
I'm hoping some dev could chip in with an update.zip for a stock 2.1 ROM that can be installed as a multiboot option
Click to expand...
Click to collapse
why?
can I use this step below?
- backup my stock in recovery
- copy the backup file to multiboot folder

twins.7 said:
why?
can I use this step below?
- backup my stock in recovery
- copy the backup file to multiboot folder
Click to expand...
Click to collapse
No you can't do that.
You need to install the boot option from an update.zip.
Already created backups have a different fs type that can't be mounted seperately.

Does it works with miniCM6?

Hello nobodyAtall, can we install CM7 and CM6 in this multiboot? if yes how to do that? ( I have cm7 2.0.2 installed ) Thanks

gatobadio said:
Hello nobodyAtall, can we install CM7 and CM6 in this multiboot? if yes how to do that? ( I have cm7 2.0.2 installed ) Thanks
Click to expand...
Click to collapse
We need to 'edify' MiniCM6 first for that

nobodyAtall said:
We need to 'edify' MiniCM6 first for that
Click to expand...
Click to collapse
10Q !!! We'll be waiting for it

Going to try to boot CM7 on my CM6. Going to post results a bit later.
Thank you nobodyAtAll for another magnificent tool!
edit: Well, no harm for my device but no CM7 either. Tool created IMG's to my sdcard but doesn't boot from there.

Speechless with just a big smile in my face!!!
Thanks nobotyatall for this it's all you mate!!
My regards,
Ribben

just shifted to optimus 2x as my main device but decided to keep my Mini for my daughter and guess what (for nAa's absolute marvels) to keep my tweaking going on.
Great achievement nAa for that. you have made this small device a great value. addition. Thanks to you for that.

parthabhatta said:
just shifted to optimus 2x as my main device but decided to keep my Mini for my daughter and guess what (for nAa's absolute marvels) to keep my tweaking going on.
Great achievement nAa for that. you have made this small device a great value. addition. Thanks to you for that.
Click to expand...
Click to collapse
It's cause of SE having crippled it so badly that it's interesting to work on this stuff

Successfully boot cm7 from cm6 using my class 2 8gb sd card. But how can I boot back to my original cm6?
Send from my x10 mini using XDA premium app

@nobodyAtall
dude awesome work!!!
we need to talk!!!
i need ur help for this:
http://forum.xda-developers.com/showthread.php?t=1114544
does fix_permissions fix ownership/permissions on /system & /data ????

Is this method works with app2sd ( /data mounted on sd ext partition ) ?
And can I use this method to boot CM7 from SE 2.1.1.A.0.6 firmware ?

Related

[RECOVERY][5/6/11] ClockworkMod Recovery for X10mini / X8 - 3.2.0.0-r3

This is ClockworkMod Recovery (v.3.2.0.0) ported to work on X10mini / X10mini pro / X8
Introduction
ClockworkMod Recovery is the default recovery option by the CyanogenMod, it has several additional features over plain old xRecovery and uses Edify exclusively:
CyanogenMod said:
Amend scripting (update-script) is no longer supported
Amend scripting was deprecated by Google in Android 1.5.
It was necessary to remove it when upgrading to the ClockworkMod 3.0 Gingerbread based recovery.
Please switch to Edify scripting (updater-script and update-binary) to create working update zip packages.
Click to expand...
Click to collapse
Despite the non-support for Amend scripts, it's the future of Recoveries and cooks should get used to this kind of scripting when making their zips.
Update:
CWM 3.2.0.0-r3 introduces two new features that validate and restore the currently installed recovery and it's deps before reboot / shutdown. If the current recovery doesn't appear to be correct, it will prompt for a recovery restore option that at least guarantees that the phone can boot into recovery. This is NOT:
- a way to make any ROM that you installed boot
- an idiot proof mechanism (e.g. if you are prompted and omit restoring, you are on your own)
Features
ADB root shell
reboot system now
apply update from sdcard
wipe data / factory reset
wipe cache partition
install zip from sdcard
backup and restore
backup (also backs up ext partition and installed apps to sdcard)
restore (also restores ext partition and installed apps to sdcard)
restore from xRecovery (Use this in case you want to restore backups done with xRecovery)
advanced restore
mounts and storage
mount / unmount /cache
mount / unmount /data
mount / unmount /sdcard
mount / unmount /system
mount / unmount /sd-ext
mount / unmount /cache
format /cache
format /data
format /sdcard
format /system
format /sd-ext
mount USB storage
advanced
reboot recovery
wipe Dalvik Cache
wipe Battery Stats
report Error
key Test
partition SD Card
Ext Size (formatting as ext4)
Swap Size (Set this to 0)
Rest Size is for vfat
fix permissions
validate recovery
restore recovery
power off
Usage
When booting your phone and when the 'Sony Ericsson' letters appear, press and release continuously the 'back' button.
Once you are in the CW recovery, use the volume keys to navigate upwards / downwards, the 'home' or camera button key to select, the 'back' key to go back.
Requirements
Stock 2.1 ROM
Busybox from the market
Root
Installation
EITHER:
If you have xRecovery: Flash the CWM recovery Amend zip
OR:
If you have a previous version of CWM Recovery: Flash the CWM recovery Edify zip
OR:
If you don't have a recovery installed, using Root explorer: manually extract any of the above CWM recovery zips and copy the contents of the system folder (system/bin and system/xbin) to /system, then give 755 permissions to those files, especially to /system/bin/chargemon, or you'll get bootloop.
Notes to everyone
Do NOT use this recovery if you are not in Stock 2.1 firmware. If you have a custom ROM, your cook should incorporate this to his ROM first
Notes to Devs/Cooks
To incorporate this to your ROM, extend the chargemon file to contain the needed part required in order to boot your ROM, the rest of the files need no changes.
Switch to Edify when giving updates for your ROMs. Search xda and google for that, there are plenty of resources out there. E.g: http://forum.xda-developers.com/showthread.php?t=936175
Also use the attached update-binary which is modified and tested to work correctly with this recovery.
Credits:
DaRk_dOg for his testing / support
koushd for writing the piece of software the first place
zdzihu for his rm -rf tip
Cyanogen for the obvious reasons...
Disclaimer:
I can't be held responsible if this Mod bricks your device or makes it explode in your hands! Use it at your own risk!
​
Changelog:
ClockworkMod Recovery v.3.2.0.0-r2:
- Added restore from xRecovery option
- Fixed letters cutoff at the bottom of the screen
ClockworkMod Recovery v.3.2.0.0-r1 for x10mini
- Ported default CM7 Recovery option
Thank you mate! Another great addition!
very cool but does this mean i cant install it when i am using your miniCM7 ??
freebordjunky said:
very cool but does this mean i cant install it when i am using your miniCM7 ??
Click to expand...
Click to collapse
That means you should bother the dev of your ROM.
....
And also check the MiniCM7 thread
Thanks a million! Will try on MiniCM6-1.0.1!
Sent from my X10mini using XDA Premium App
Great work. Thanks
o2gulo said:
Thanks a million! Will try on MiniCM6-1.0.1!
Sent from my X10mini using XDA Premium App
Click to expand...
Click to collapse
Uhm, you shouldn't.....
nobodyAtall said:
Notes to everyone
Do NOT use this recovery if you are not in Stock 2.1 firmware. If you have a custom ROM, your cook should incorporate this to his ROM first
Click to expand...
Click to collapse
Nobody.... I have one question. Though my phone gets stuck up in SE screen the CWM recovery works fine and shows up on repeated pressing of back button. Now once you upload the rectified ".zip" file can I not reflash it with CWM recovery and boot my device normally instead of going through the entire process of updating through SEUS?
This seems great as with all your work. May I bother you enough to make it work with MiniCM6, as the one you posted effed up my cellphone?
Keep up the great work, nAa
parthabhatta said:
Nobody.... I have one question. Though my phone gets stuck up in SE screen the CWM recovery works fine and shows up on repeated pressing of back button. Now once you upload the rectified ".zip" file can I not reflash it with CWM recovery and boot my device normally instead of going through the entire process of updating through SEUS?
Click to expand...
Click to collapse
Hi,
This thread is for Stock 2.1 ROMs only.
At the state you are, you need to reflash with SEUS and restore with xrecovery.
Good Thing I reverted Back to 2.1 ..
One question, If we use xRec and Flash it, will xRec be removed?
Is backward compatible with xRecovery? I mean themes updates and Backups made for xRecovery will work?
Sent from my X10mini using XDA App
It replaced xRecovery.. No problems at all... Works great... Thanks dude..
When want to replace my recovery i get:
E:Can't chown/mod /system/bin/charger
(No such file or directory)
E:Failure at line 4:
set_perm 0 0 0755 SYSTEM:bin/charger
Edit: well it seemed like it worked, well recovery is orange now
Now it is stuck on SE screen, i dit revert back to stock 2.1
nobodyAtall please help
a couple of questions,
1. i did a backup with the new cwm so the old backups from xrecovery wont work so can i delete them?
and
what is key test?
X10mini miniCM7 2.0.1 using XDA Premium App
This is really awesome, porting to mini pro right now! Thanks nAa, you're the man
cheers, d4.
EDIT:
@nAa Still some wrong on sizes, hope you can fix it, or upload sources, but awesome work, ported to mini pro, ofc all crdtis for you
EDIT2:
Can you please upload a modded version that says Mini pro? Thanks
I flashed the file zip, but the phone forces close..it doesn't work..i repaired the software with SE
Sent from my X10mini using XDA Premium App
the last line when making backup or something others is half cutted by backup is this : Backing up System
the words shows me like this (example from PC) :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
seams it isnt fixed on right resolution
*edit*
Great Port thx to all for make this happen
bitmovel said:
also, "fix permissions" does not work. the phone stops working. only battery off can make it run again
Click to expand...
Click to collapse
DJxSpeedy said:
the last line when making backup or something others is half cutted by backup is this : Backing up System
the words shows me like this (example from PC) :
seams it isnt fixed on right resolution
*edit*
Great Port thx to all for make this happen
Click to expand...
Click to collapse
Yeah, same here, btw, tried to make a edify script for flashing old xRecovery, and it gives me error ?, I used chumby's amend2edify tool

[RECOVERY] ClockworkMod Recovery for X10 Mini Pro - 3.2.0.0-r3

First, I need to say that this was not made by me!, all credits go to nobodyAtall, I just changed chargemon to make it work on mini pro, all roms, Please read original post here for more info
This is the latest ClockworkMod Recovery (v.3.2.0.0) ported to work on X10 mini pro
Introduction
ClockworkMod Recovery is the default recovery option by the CyanogenMod, it has several additional features over plain old xRecovery and uses Edify exclusively:
CyanogenMod said:
Amend scripting (update-script) is no longer supported
Amend scripting was deprecated by Google in Android 1.5.
It was necessary to remove it when upgrading to the ClockworkMod 3.0 Gingerbread based recovery.
Please switch to Edify scripting (updater-script and update-binary) to create working update zip packages.
Click to expand...
Click to collapse
Despite the non-support for Amend scripts, it's the future of Recoveries and cooks should get used to this kind of scripting when making their zips.
Update:
CWM 3.2.0.0-r3 introduces two new features that validate and restore the currently installed recovery and it's deps before reboot / shutdown. If the current recovery doesn't appear to be correct, it will prompt for a recovery restore option that at least guarantees that the phone can boot into recovery. This is NOT:
- a way to make any ROM that you installed boot
- an idiot proof mechanism (e.g. if you are prompted and omit restoring, you are on your own)
Features
ADB root shell
reboot system now
apply update from sdcard
wipe data / factory reset
wipe cache partition
install zip from sdcard
backup and restore
backup (also backs up ext partition and installed apps to sdcard)
restore (also restores ext partition and installed apps to sdcard)
restore from xRecovery (Use this in case you want to restore backups done with xRecovery)
advanced restore
mounts and storage
mount / unmount /cache
mount / unmount /data
mount / unmount /sdcard
mount / unmount /system
mount / unmount /sd-ext
mount / unmount /cache
format /cache
format /data
format /sdcard
format /system
format /sd-ext
mount USB storage
advanced
reboot recovery
wipe Dalvik Cache
wipe Battery Stats
report Error
key Test
partition SD Card
Ext Size (formatting as ext4)
Swap Size (Set this to 0)
Rest Size is for vfat
fix permissions
validate recovery
restore recovery
power off
Usage
When booting your phone and when the 'Sony Ericsson' letters appear, press and release continuously the 'back' button.
Once you are in the CW recovery, use the volume keys to navigate upwards / downwards, the 'home' or camera button key to select, the 'back' key to go back.
Requirements
Working on any ROM .. Unified chargemon (For stock last version supported it's 2.1.1.A.0.6!, if you have newer, downgrade, don't working for stock 1.6)
Busybox from the market
Root
Installation
Install through CWM recovery (sorry no more support for xRecovery)
Credits:
nobodyAtall for porting this amazing software to mini, thumbs up to him PLEASE
All credits on original post
Fast Disclaimer: I'm not responsible if this brick your lovely device
Installing right now
Sent from my U20i using XDA Premium App
Just installed it on my mini pro, works fine. Much appriciated.
Thx to nobodyAtall too
Hey, awesome, I've been waiting for this on our Mini Pro's Thanks to you and nobodyatall! just a question - does this mean, we can use ROM Manager?
Ravencz said:
Hey, awesome, I've been waiting for this on our Mini Pro's Thanks to you and nobodyatall! just a question - does this mean, we can use ROM Manager?
Click to expand...
Click to collapse
I think it still need some changes, but we're close to get CWM recovery 100% functional
Ravencz said:
Hey, awesome, I've been waiting for this on our Mini Pro's Thanks to you and nobodyatall! just a question - does this mean, we can use ROM Manager?
Click to expand...
Click to collapse
This is the goal actually (or some other easy way to install updates), at least for MiniCM
Glad it works for you guys too
the last line when making backup or something others is half cutted by backup is this : Backing up System
the words shows me like this (example from PC) :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
seams it isnt fixed on right resolution
*edit*
Great Port thx to all for make this happen
With the ClockworkMod it's possible recorevy backup of the xrecovery??
Download now, hehe
DJxSpeedy said:
the last line when making backup or something others is half cutted by backup is this : Backing up System
the words shows me like this (example from PC) :
seams it isnt fixed on right resolution
*edit*
Great Port thx to all for make this happen
Click to expand...
Click to collapse
same error here.
also, "fix permissions" does not work. the phone stops working. only battery off can make it run again
Andreson01 said:
With the ClockworkMod it's possible recorevy backup of the xrecovery??
Download now, hehe
Click to expand...
Click to collapse
Testing as we speak. Please remember you cannot use xrecovery folder anymore. you must move it to new clockworkmod foler
bitmovel said:
same error here.
also, "fix permissions" does not work. the phone stops working. only battery off can make it run again
Testing as we speak. Please remember you cannot use xrecovery folder anymore. you must move it to new clockworkmod foler
Click to expand...
Click to collapse
Please make this reports on X10 mini thread, nAa sure will give us a answer
Just tested:
Yes! It can restore xrecovery backups. Just move them to the new directory
Thank you!!
D4rKn3sSyS said:
Please make this reports on X10 mini thread, nAa sure will give us a answer
Click to expand...
Click to collapse
ive quoted my post here with bitmovel's post to mini thread
thanks
bitmovel said:
thanks
Click to expand...
Click to collapse
no problem
31 download and 4 thanks ... Some of you guys dont really appreciate the dev's work, same with nAa post, i dont care thanks on me, but at least thank to nAa, he's a awesome dev
D4rKn3sSyS said:
31 views and 4 thanks ... You guys dont really appreciate the dev's work, same with nAa post
Click to expand...
Click to collapse
Hey mate i love your work! I'm on mobile i give you a thanks tomorrow! Use the force dev and never say die! You are great! ;-)
Inviato dal mio U20i usando Tapatalk
Just tested it on my mini pro and seems to work just fine. Only the last line in the "loogging" part is sligtly under the screen and therefore cut-off but that's not a big issue as the text is still very readable
Testing report: fix permissions IS working, as normal it take a while, exactly equal that on xRecovery, so test it again people who are having problems, will take about 2 mins, seems to be that clean battery status it's not working.. im doing tests
EDIT: Confirmed working on r2, nicely working, only 1 bug left, sd-ext mount, already reported to nAa
D4rKn3sSyS said:
Testing report: fix permissions IS working, as normal it take a while, exactly equal that on xRecovery, so test it again people who are having problems, will take about 2 mins, seems to be that clean battery status it's not working.. im doing tests
Click to expand...
Click to collapse
thanks.
looks like I didnt wait enough time.
I miss your xrecovery backgrounds... hehe

Dual-boot your favourite custom ROM with stock firmware

To encourage developers and users to switch to the new xRecovery, I prepared a package that allows dual-booting between custom ROM and stock firmware. This is just a proof of concept, I am not going to develop it further nor support it as usual project release. Instead, I hope that developers will find many useful things inside to use in their own pojects
It also may be useful for people using 2.3 ROMs without camera/camcorder.
Tested with: FreeX10 beta4, Woflbreak's CM, AOSP 2.3
PLEASE READ CAREFULLY:
- it works from NAND rather than SD Card - should not suffer fom performance issues
- it will work with any custom 2.2/2.3 ROM of reasonable size
- it WON'T work with custom 2.1 ROMs - not enough storage space
- it uses 200MB of your /system and 256MB of your /data partition - make sure you've got enough free space
- it requires xRecovery 1.0.0 (the old one doesn't allow custom boot)
- it cannot be accessed via recovery, but it's possible to mod it to do so (devs/adv.users)
- it works with baseband 49/52!
- if you back up your system with nandroid backup, the 2.1 ROM will be included in this backup
Click to expand...
Click to collapse
Install:
Flash the dualboot 2.0.A.0.504.zip via xRecovery 1.0.0.
Uninstall:
Remove the following folders using Root Explorer:
Code:
/data/dualboot
/system/dualboot
Boot into stock 2.1 firmware:
Boot into xRecovery, select "Boot custom ROM/kernel"
Download:
dualboot 2.0.A.0.504.zip
Cheers,
z
You genius you've done another amazing things for our phone thank you
Sent from my SEX10 using XDA App
Nice work mate!
What kind of genies do we have hear :O?!
I told everyone so, updating recovery has an advantage.
U really rock man
zdzihu said:
To encourage developers and users to switch to the new xRecovery, I prepared a package that allows dual-booting between custom ROM and stock firmware. This is just a proof of concept, I am not going to develop it further nor support it as usual project release. Instead, I hope that developers will find many useful things inside to use in their own pojects
It also may be useful for people using 2.3 ROMs without camera/camcorder.
Tested with: FreeX10 beta4, Woflbreak's CM, AOSP 2.3
Install:
Flash the dualboot 2.0.A.0.504.zip via xRecovery 1.0.0.
Uninstall:
Remove the following folders using Root Explorer:
Code:
/data/dualboot
/system/dualboot
Boot into stock 2.1 firmware:
Boot into xRecovery, select "Boot custom ROM/kernel"
Download:
dualboot 2.0.A.0.504.zip
Cheers,
z
Click to expand...
Click to collapse
Thanks for the work buddy..... I don't have access to mediafire from workplace will check once i reach home....
As you said its for developer's so i assume all source code's are included in it.
How to revert back to the first rom?
Thanks Z..u r the best
astrall said:
How to revert back to the first rom?
Click to expand...
Click to collapse
Remove this:
/data/dualboot
/system/dualboot
FINALLY
something awesome to play with!!!
downloading now...
will test it out this weeked for dual booting using FreeX10/CM7
also i think we can integrate custom kernel booting into this... for those roms which require it...
finished d/ling:
@anantshri:
Code:
#!/sbin/sh
# zdzihu: let's get some Ubuntu fun!
insmod /system/kernel/splboot.ko
sync
cat /system/kernel/miniloader > /proc/splboot/image
cat /system/kernel/boot-stock.img > /proc/splboot/boot_img
sleep 3
echo > /proc/splboot/boot
interesting eh???
guess i will heave to search for that splitbootimg binary/app again...
Genius @work
Thank you Z without you there would be no fun using the X10...
DooMLoRD said:
Code:
#!/sbin/sh
# zdzihu: [b]let's get some [size=4]Ubuntu[/size] fun[/b]!
insmod /system/kernel/splboot.ko
sync
cat /system/kernel/miniloader > /proc/splboot/image
cat /system/kernel/boot-stock.img > /proc/splboot/boot_img
sleep 3
echo > /proc/splboot/boot
Click to expand...
Click to collapse
Lawl, I forgot to rename my script Damn Ubuntu never booted fine anyway...
Cheers,
z
oh i see...
so basically we are flashing 2.1 ROM on top of custom rom....
so the 2.1 rom is actually in the .ext2 files!!!
zdzihu said:
Lawl, I forgot to rename my script Damn Ubuntu never booted fine anyway...
Cheers,
z
Click to expand...
Click to collapse
so for multibooting we can actually jsut store the img files on sdcard check flags set by users... copy those img files to /data & /system and then jsut continue booting with the modded kernel u posted...
hu i think that should work...
DooMLoRD said:
so for multibooting we can actually jsut store the img files on sdcard check flags set by users... copy those img files to /data & /system and then jsut continue booting
Click to expand...
Click to collapse
It does work. But it's not pretty. I played with both /system and /data being stored on SD Card, but the system suffered from terrible freezes/"x stopped responding" (like FreeX10 alpha). Also, first boot took around 7-8min.
DooMLoRD said:
with the modded kernel u posted...
Click to expand...
Click to collapse
With any kernel really. It's ramdisk that's important (mounting images).
Cheers,
z
V/Nice!
Q: Is this using CM7_Passion sources? cm_passion_full-xx - would be nice to compile and maybe add some extra's in.. possible?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
zdzihu said:
It does work. But it's not pretty. I played with both /system and /data being stored on SD Card, but the system suffered from terrible freezes/"x stopped responding" (like FreeX10 alpha). Also, first boot took around 7-8min.
With any kernel really. It's ramdisk that's important (mounting images).
Cheers,
z
Click to expand...
Click to collapse
ya i got that... i actually ment the ramdisk which doesnt remount NAND MTDs
Great works !!
Please teach me how to make system.ext2 & data.ext2 files ??

[RECOVERY] ClockworkMod Recovery for Xperia X8 - 4.0.1.5 [UPDATE - 24/9/2011]

The Clockworkmod recovery is working on our X8 now
* I am not responsible for any brick or damage to your phone, so be cautious!
The package script for CWM recovery is different from xRecovery, don't try to flash xRecovery script with CWM recovery, errors might occur
If you want to create update.zip for CWM recovery, please go to here.
Use the attached update-binary which is modified and tested to work correctly with this recovery.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Features
- reboot system now
- apply update from sdcard
- wipe data / factory reset
- wipe cache partition
- install zip from sdcard
- backup and restore
------ backup (also backs up ext partition and installed apps to sdcard) (please make sure you have enough space on the sd card!)
------ restore (also restores ext partition and installed apps to sdcard)
------ Advanced restore
- mounts and storage
------ mount / unmount /cache
------ mount / unmount /data
------ mount / unmount /sdcard
------ mount / unmount /system
------ mount / unmount /sd-ext
------ mount / unmount /cache
------ format /cache
------ format /data
------ format /sdcard
------ format /system
------ format /sd-ext
------ mount USB storage
- advanced
------ reboot recovery
------ wipe Dalvik Cache
------ wipe Battery Stats
------ report Error
------ key Test
------ show log
- power off
How to use?
The method booting into it is same as booting to the xRecovery, just click the 'back' button continuously when see the white 'Sony Ericsson'
Installation requirements
1) Rooted
2) Busybox installed from the market
Installation
- If you are having xRecovery, flash "Amend" package
- If you are having previous version of ClockWorkMod Recovery, flash "Edify" package
Downloads
see attachments
Credits:
dbts25 for testing
puppet13th for dual mode recovery
---------------------------------------------------------------------------
If you like this thread, please feel free to click the 'THANKS' button!!
Changelog:
[24/9/2011]
- CWM recovery updated to 4.0.15
- removed some useless functions
[23/8/2011]
- Fixed errors of 4.0.14-r2
[9/8/2011]
- CWM recovery updated to 4.0.14
[15/6/2011]
- CWM recovery can work on Floyo, FroyoBread and Hackdroid 0.98 now.
- Dual recovery supported in CWM recovery and FreeXperia Recovery
[11/6/2011]
- CWM recovery can only work on stock X8 rom.
already tested,in my case i cant install another rom.stuck with froyobread n the end im using seus.this is my experience, maybe different with other
If is possible you can copy part of chargemon script to other chargemon of custom Rom and overwrite xrecovery script. So your custom zips will work with custom rom.
Sent from my X8 using XDA Premium App
sendalterbang said:
already tested,in my case i cant install another rom.stuck with froyobread n the end im using seus.this is my experience, maybe different with other
Click to expand...
Click to collapse
So I take it CWM still doesn't work with binary updates...
CWM doesn't support old update-scripts, I don't know which ones (amend or edify) - you have to convert them.
Xrecovery is using Amend script and CWM Recovery is using Edify script
Hi just want to ask for what we have xrecovery and cwm recovery? Its the same as i see
Sent from my X8 using Tapatalk
proadi96 said:
Hi just want to ask for what we have xrecovery and cwm recovery? Its the same as i see
Sent from my X8 using Tapatalk
Click to expand...
Click to collapse
Read the thread.............
my phone boots into recovery but no longer boots into android wtf ?
Omg,this is stupid...its the same thing as xrecovery...
Sent from my X8 using Tapatalk
xperiauser132 said:
Omg,this is stupid...its the same thing as xrecovery...
Sent from my X8 using Tapatalk
Click to expand...
Click to collapse
Sorry to say that, but you're stupid yourself This has similar functionality to xrec, but is hardly the same
I didnt say you were stupid -.-
But thanks.
Sent from my X8 using Tapatalk
xperiauser132 said:
Omg,this is stupid...its the same thing as xrecovery...
Sent from my X8 using Tapatalk
Click to expand...
Click to collapse
ClockworkMod recovery has a purpose of existence.
CM7 is build on Gingerbread sources so it is vital to use a common source based recovery.
Also edify scripting and the advanced syntax check that CWM performs, is by itself, a proof of superiority against xrecovery.
The correct order is think-search-discuss and NOT vice-versa.
Regards, D_d
But ill stay on xrecovery,i like it better.
Sent from my X8 using Tapatalk
Great work!
Sent from my X8 using XDA Premium App
It can create SD card partition? wow. xD
xperiauser132 said:
But ill stay on xrecovery,i like it better.
Sent from my X8 using Tapatalk
Click to expand...
Click to collapse
yes, because almost all of those custom ROM for X8 now is using Amend script (update-script), and i think only miniCM that is using Edify script (updater-script).
you know, that CWM can backup EXT partition on your SD Card?
CWM and Xrecovery/FreeXperia Recovery is different, and you should have noticed it if you see the options on the screenshot
also, if you want to convert update-script to updater-script, you can use dsixda's kitchen, just search XDA, and its a very easy thing to do.
So, to understand, if i'm in stock 2.1 i can use this and flash whetever cyanogen rom-mod (as hackdroid) i want (if i use the amend one) or i can use it if i'm already in the hackdroid rom? thanks
So i cant try it on xgin 5.1 ??
Sent from my X8 using Tapatalk

[Multiboot] [Update 1/7/11] Create, manage and boot your ROM options via CWM!

Introduction
This thread describes an experimental mod that allows you to boot into other boot images stored in your sdcard.
The N1 does not have enough internal memory to store more than one android image, thus we have to use the sdcard for this.
NOTE:
This mod is experimental, and for advanced users only
Requirements (READ THEM CAREFULLY):
- A rooted and unlocked phone
- A FAST enough sdcard. This mod will work with any sdcard but I'd suggest at least a Class 4 card for performance reasons
- Your sdcard should have enough free space. Each 'boot option' that you create reserves 400MB of space in your sdcard
- In order to create a new boot option, you need a flashable zip over CWM of the ROM you wish to boot to. The flashable zip of the ROM is the same that is used for usual ROM installation. Also the zip should be using the latest update-binary format as is scripted in updater-script (e.g. the mount command takes 4 args, etc.)
Advanced Information regarding the process
- The mod requires a boot.img that is flashed by the zip. This is used for extracting the ramdisk, commenting out the mount mtd commands and using this ramdisk for chrooting into the ROM environment
- If no boot.img is existing, the ramdisk is picked up from /sdcard/ramdisk/
- The kernel used for booting all boot options is the one installed in the phone's boot mtd. This means that you need the respective kernel modules (e.g. WiFi) for this kernel, not the one that is bundled in the ROM that is multibooted. For example, if your main ROM is CM, pick the kernel modules from this one and push them to the multibooted ROM's /system/lib/modules/
Multiboot mod Installation
Download: N1_CWM-4.0.0.5-nobodyAtall-r2.img
Install via fastboot
Code:
Copy N1_CWM-4.0.0.5-nobodyAtall-r1.img to a location where fastboot can find it.
Boot your phone into fastboot mode (power on while holding the trackball)
Connect your phone via usb
fastboot devices (to make sure that fastboot "sees" your phone)
fastboot flash N1_CWM-4.0.0.5-nobodyAtall-r1.img
Install via adb
Code:
adb push N1_CWM-4.0.0.5-nobodyAtall-r1.img /sdcard/
adb shell 'flash_image recovery /sdcard/N1_CWM-4.0.0.5-nobodyAtall-r1.img'
adb reboot recovery
Multiboot ROM Installation
- Boot into the recovery and navigate to the new 'multiboot' menu. There you'll see the following options:
Boot into selected option!
Select default boot option
Unset default boot option
Create boot option from zip
Delete existing boot option
Flash zip to boot option
- Select multiboot->Create boot option from zip and then pick the flashable ROM zip. Be patient, this step reserves the space and flashes the selected zip to the system.img in the sdcard
- If you need to flash additional zips for this ROM, Select multiboot->Flash zip to boot option, pick your newly created boot option and then pick the zip you need to flash.
- Select multiboot->Select default boot option and pick your newly created boot option
- Select multiboot-> Boot into selected option! (first boot will take some time depending on your sdcard speed).
To verify you have booted to your newly created boot option, check 'adb shell mount', it should say that /system /data and /cache is mounted from /loop* devices and not from mtd*
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ROMS verified to multiboot
Well, any ROM should be able to multiboot provided the requirements stated above are covered. The following ones have been verified to work:
[ROM] CyanogenMod-7.1 for Nexus One
[ROM] NEXUS N1 Passion MIUI.us Presents MIUI Pure English [AOSP]
CM 7 ExtremeMod ROM by Ken Mood
Uninstall
- Normal reboots will boot from the phone's mtd partitions.
- This mod makes no changes to your phone's mtd partitions. Flashing a new recovery will uninstall the old one obviously.
- To remove installed boot options, navigate to multiboot->Delete existing boot option and pick you choice. Alternatively remove the boot option you want from /sdcard/clockworkmod/multiboot/
Disclaimer:
I can't be held responsible if this mod bricks your device / trashes your sdcard or makes it explode in your hands! Use it at your own risk!
​
Changelog:
(1/7/11) N1_CWM-4.0.0.5-nobodyAtall-r2.img
Fixed bug that flashed the multiboot ROM kernel in the phones kernel partition
Improved error reporting
(30/6/11) N1_CWM-4.0.0.5-nobodyAtall-r1.img
First version of CWM recovery providing the multiboot options
woww thanks
Well, this could be freaking awesome. I'll check it out at work
Nice one. Can we use CM nightlies that came after the RC?
method77 said:
Nice one. Can we use CM nightlies that came after the RC?
Click to expand...
Click to collapse
You can use it with any CM7 ROM
I am interested in this, i'm surprised that it hasn't created more of a stir.
I have installed the recovery, but don't want to do anything else without Nandroiding first. Only Nandroid seems to get stuck on "Backing up system..."
Any i doing something wrong?
Hello shorza,
To be honest, I've only been testing the multiboot part.
However, I think that backup works fine here:
Also the backup folder is created correctly:
~ # ls -la /sdcard/clockworkmod/backup/2011-07-01.06.49.58
drwxrwxrwx 2 root root 4096 Jul 1 06:52 .
drwxrwxrwx 5 root root 4096 Jul 1 06:49 ..
-rwxrwxrwx 1 root root 93489792 Jul 1 06:52 .android_secure.img
-rwxrwxrwx 1 root root 3670016 Jul 1 06:50 boot.img
-rwxrwxrwx 1 root root 37359168 Jul 1 06:52 cache.img
-rwxrwxrwx 1 root root 184136832 Jul 1 06:51 data.img
-rwxrwxrwx 1 root root 222 Jul 1 06:53 nandroid.md5
-rwxrwxrwx 1 root root 4194304 Jul 1 06:50 recovery.img
-rwxrwxrwx 1 root root 146908608 Jul 1 06:50 system.img
On another note, I'll be doing an update today to fix some bugs related to multiboot.
CWM 4.x has problems backing sd-ext, so that might be the reason why you don't see it (your pic shows you don't have an sd-ext partition to backup) and shorza does. It is also the reason why I haven't tried this yet - if it was based on AmonRa's I'd have jumped immediately, but since it is based on CWM I wanted first to see some feedback here...
Thanks for the help. Backup eventually worked, it just took a long time.
The problem is after zipping a new rom in multiboot, selecting it, then trying to boot into it, it took too long and I lost patience. It looked like it froze.
I'll try again tomorrow.
Maybe my sdcard is too slow.
shorza said:
Maybe my sdcard is too slow.
Click to expand...
Click to collapse
You need to be patient. It takes a long time to boot (especially for the first boot) and if the recovery seems frozen, this is a good sign - it means it's booting.
Posted -r2.
This fixes a bug that would flash the multiboot ROM's kernel to the phone's kernel partition. Also improves logging in case of errors.
Testing this out right now ... just got latest cyanogenmod nightly and latest miui (as of today) going on it and just switched back and forth. sucks about having to go into recovery to switch, needs to have a boot option when starting the phone haha.
So wifi doesn't work in the latest version of miui.us when using it as a multiboot option. such says in logcat "Failed to load Wi-Fi driver." it works when the rom is installed as normally so it must be the kernel from this application. but wifi on cyanogenmod works so that is good.
Will this work like a nandroid backup where it saves everythn from my last boot? Or will it save everythn on that same img. when i switch roms
looking at the directory structure, per multiboot rom it saves the boot.img, cache.img, data.img, and system.img .... I don't know how it uses them, but linux is magical in mounting images as a partition, doesn't have to be physical
This is because the ROM is run using the device's kernel and not the one that comes with the ROM as stated in the first post.
To make wifi work, simply copy your wifi kernel module from /system/lib/modules to this same did within the multibooted ROM.
Ellises said:
So wifi doesn't work in the latest version of miui.us when using it as a multiboot option. such says in logcat "Failed to load Wi-Fi driver." it works when the rom is installed as normally so it must be the kernel from this application. but wifi on cyanogenmod works so that is good.
Click to expand...
Click to collapse
Sent from my Nexus One using XDA App
This actually works pretty well, however, the phone get quite hot.
[Q]Bug fixed??
I succeed multibooting
I got miui(main)&CM7(sub)
but subrom,cm7 can't use wifi
so I changed kernel but failed
and display
[mount expects 4 3args]
[error /sdcard/xxx... ]
[ status7 ]<<maybe
If you know what's the problem, plz teach me the way
thx and pardon my English

Categories

Resources