[DEV|WIP] Dualboot Kernel [GSM|CDMA-WIP] - Xperia Play Android Development

Credits:
DooMLoRD - BootManager and recoveries, autorooting and his scripts
Jerpelea (FXP) - zImage (kernel), boot splash logo
z - busybox knowledge, and his loop mount script.
GSM Only atm, CDMA not done yet, WIP.
Download:
Dualboot Kernel GSM: http://icxperia.com/keiran/r800i/dualboot.img
Data EXT2 image (~250MB), http://icxperia.com/keiran/r800i/data.ext2
How to dualboot:
What you will need:
An SD Card
ADB
Fastboot
7zip or alternative(Archive manager on linux is good)
Notepad++(gedit is good)
First, flash the dualboot.img
Code:
fastboot flash boot dualboot.img
How to partition SD Card for dual boot:
Code:
adb shell
sdparted -es 1024M -ss 0
When prompted to accept, make sure you use a capital Y
This operation will wipe your sd card :O lol
when it is done, type:
Code:
exit
in the command prompt/terminal
Now, put the data.ext2 image in the same folder as adb is
Second of all, you want to mount your second SD Card partition, using your computer with USB debugging enabled do this:
Code:
adb shell
busybox mount /dev/block/mmcblk0p2 /sd-ext
exit
then push the data partition image:
Code:
adb push data.ext2 /sd-ext/data.ext2
Now you have your system partition and data image set up for dualboot, you are also running a dualboot kernel
next thing to do is modify a ROM for boot from SD
We shall use CM7 in this example
Unzip the ROM, and go to /META-INF/com/google/android/ then open updater-script in notepad++, it will not work otherwise
Look for the lines:
Remove these lines:
Code:
assert(getprop("ro.product.device") == "R800i" || getprop("ro.build.product") == "R800i" || getprop("ro.product.board") == "R800i" ||
getprop("ro.product.device") == "R800a" || getprop("ro.build.product") == "R800a" || getprop("ro.product.board") == "R800a" ||
getprop("ro.product.device") == "R800at" || getprop("ro.build.product") == "R800at" || getprop("ro.product.board") == "R800at" ||
getprop("ro.product.device") == "zeus" || getprop("ro.build.product") == "zeus" || getprop("ro.product.board") == "zeus");
also, remove:
Code:
format("yaffs2", "MTD", "system");
also, replace:
Code:
mount("yaffs2", "MTD", "system", "/system");
with
Code:
set_perm(0, 0, 0777, "/sbin/systemsd.sh");
run_program("/sbin/systemsd.sh");
then save, then zip, then push to phone
Then, flash the update.zip (after doing a NANDROID) then boot phone into NAND.
To boot into SD ROM, do this:
Open terminal emulator and do the commands:
Code:
su
cd cache
cd recovery
touch dualboot
reboot
And you will reboot into SD ROM
You will not be able to use darktremor a2sd or any other a2sd script with any of the ROM's, but, you will be able to use standard stock rom app2sd, in CyanogenMod go into CM settings, then application then set install location to internal to avoid conflicts with .android_secure on both ROM's
Kernel source:
https://github.com/freexperia/semc-kernel-msm7x30
Keiran

Whoa....
Just done a quadrant from the rom of the SD - CM7, I got amazing IO speeds, probably because my SD card reads faster than NAND....
But, no overclock, Max,1GHz, min 144MHz, interactive:
{
"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"
}
Look at the green IO bit... lol looks like SD can boost performance
Sent from my R800i

can't wait to test it.
Wouldn't it be better to use a ICS ramdisk (or make serval kernels) so you can flash ICS and GB??
GB works also with ics ramdisk (i guess)

No, ICS requires a different ramdisk, so you would only be able to boot two of the sameish android versions, although doomlord said somethin about chrooting...
Sent from my R800i using DFR3.0.5 NAND + CM7 SELFKANG SD

I want some cm fun nice work
Sent from my R800i using xda premium

Next on my list of development is a linux tool, ftf2rom, what it will so is unpack an ftf and convert it into a flashable zip with the kernel there also, and then there will be ramdisk editor and such...
Keiran
Sent from my R800i using DFR3.0.5 NAND + CM7 SELFKANG SD

So us normal being's have a long wait lol
Sent from my R800i using xda premium

hitman980206 said:
So us normal being's have a long wait lol
Sent from my R800i using xda premium
Click to expand...
Click to collapse
Not really, just DFMiX might not see many new releases for a while. DFR will, and so will this kernel
Sent from my R800i using DFR3.0.5 NAND + CM7 SELFKANG SD

KeiranFTW said:
Not really, just DFMiX might not see many new releases for a while. DFR will, and so will this kernel
Sent from my R800i using DFR3.0.5 NAND + CM7 SELFKANG SD
Click to expand...
Click to collapse
Well I'm using dfr3 and its been great if I could have some cm7 fun when not needing touchpads would extra bonus
Sent from my R800i using xda premium

KeiranFTW said:
With the Xperia Play, comes an awesome gamepad, and it works as it should... on the stock rom.
So, people wanted to use CM, but they wanted touchpads, so they just kept stock. Not any more
What I have basically done (basic is not the word to use):
Made a script that is executed on boot that does the following if a certain file is present:
Unmounts NAND system and data partitions.
Mounts NAND partitions to /mnt/system and /mnt/data
Mounts sd-ext mmcblk0p2 to /system
Loops the /system/data.ext2 to loop3 - remember system is now mmcblk0p2
Mounts loop3 as /data
Then removes the temp file used for telling the phone to boot into recovery
So, you need an ext partition on sd that will hold /system files and /data IMG containing files.
I will show you how to adapt a Rom to dualboot when I upload the kernel.
Credits go to Jerpelea for zImage and DooMLoRD for base ramdisk.
Will upload 21st, Tuesday, currently polishing and studying lol.
CDMA to follow tomorrow too
Oh, it works
Keiran
Sent from my R800i using DFR3.0.5 NAND + CM7 SELFKANG SD
Click to expand...
Click to collapse
Alright, I got to give it up to you on this one. This was a crazy idea and you pulled it off. Much respect for this Kerian.

KeiranFTW said:
Not really, just DFMiX might not see many new releases for a while. DFR will, and so will this kernel
Sent from my R800i using DFR3.0.5 NAND + CM7 SELFKANG SD
Click to expand...
Click to collapse
so can I dual boot stock and MIUI with this kernel ? or only CM7 at this moment ?

You couldn't boot stock and MIUI as they require a diffrent kernel.
Sent from my R800i

is it possible to instead booting into cm to boot into debian or something like that?

So, if i would want to use this dual booting, i wouldn't be able to use a2sd?

KeiranFTW said:
Not really, just DFMiX might not see many new releases for a while. DFR will, and so will this kernel
Sent from my R800i using DFR3.0.5 NAND + CM7 SELFKANG SD
Click to expand...
Click to collapse
Yes! More DFR (and hopefully more frequent DFMix updates as well... ehehe..) updates! Thanks a lot man. With the touchpads working the same as the stock firmware it'll be a perfect rom. Well, almost since everything can't be perfect

Need little bit help for understanding...
With this kernel it is possiblem to boot for example the STOCK .42 Firmware from NAND and CM7 or any other rom from the SD Card?
If so it is perfect, because i love stock but i like cm7 so i can switch between the two roms without wipes and kernel flashing?

evo_racer said:
Need little bit help for understanding...
With this kernel it is possiblem to boot for example the STOCK .42 Firmware from NAND and CM7 or any other rom from the SD Card?
If so it is perfect, because i love stock but i like cm7 so i can switch between the two roms without wipes and kernel flashing?
Click to expand...
Click to collapse
The way i understand it is as long as it uses the same kernel/ramdisk it will work so stock .42 and CM7 should be fine but ICS wouldnt work
Sent from my R800i using xda premium

thereverend86 said:
The way i understand it is as long as it uses the same kernel/ramdisk it will work so stock .42 and CM7 should be fine but ICS wouldnt work
Sent from my R800i using xda premium
Click to expand...
Click to collapse
Correct,
You could get A2SD to work with third ext partition, mmcblk0p3, but it would be pointless unless for stock ROM...
Releasing kernel and dualboot compatible CM in about 2+ hours need to work on it, found a problem with it
Sent from my R800i using DFR3.0.5 NAND + CM7 SELFKANG SD

Nice work.. can you write a how to for me? Im happy with my play at the moment.. stock with many many games on it so i will not wipe my data

Excellent news
You could get MIUI to work with dual booting CM7 + MIUI. Basically, 3G PreLinked CM7 dual booted with MIUI and a 3G PReLinked Kernel
@everyone Let him at least finish it, then once it is uploaded begin to ask questions. Remember this is a development section!

Related

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 ??

[DEVs only] EXT4 system/data/cache partition for x10

I have been going through many things ,
REQUIRES UNLOCKED BOOTLOADER
And finally made this ,
This is a flash able zip which requires cwm4 recovery and a rom which supports ext4 partition after that
Otherwise the partition gets removed
Since we don't have many roms with Ext4
I'll just include this zip
I just heard someone wanted a good dev who would make something good , other than barebones
http://www.mediafire.com/?5gotc36iav7hphy
This should be interesting . Apparently EXT4 provides a significant boost in speed right?
Quick question. With a rooted X10 I can format system/data/cache anytime I want to install a new ROM. So my question is....why cannot (with a locked bootloader) format it to ext4? Is there something stopping the filesystem from booting when formatted in ext4?
The reason I ask is other devices can do this with only a rooted device and no BL unlock.
EDIT: and yes it is supposed to provide a boost in OS speed. Mainly in multicore phones but should help with ours as well.
kantk20111 said:
This should be interesting . Apparently EXT4 provides a significant boost in speed right?
Click to expand...
Click to collapse
Yeaah it does It would be great if we could get this working on our phones...
EXT3 and EXT4 both are journaling FS. That's where the speed came in. It doesn't boost the OS but it made the storage performance better. Thus resulting in a faster system.
Sent from my SO-01C using XDA App
Good show! My current phone is ext4 now and it definitely does boost speed
Awesome work
Yes but whatever the reasons you have, never do this on your SD card as it will result in memory wear.
Anyways, nice job here spaarc.
Sent from my SO-01C using XDA App
This would never really work correctly right now
This needs to be included in the original updater-script as well
the sdcard needs to be of a higher class (class 6 and above) to actually gain some performance benefits.... else it will all lag..
btw we can get multiboot based on this...
EDIT:
based on the update.zip u posted...
Code:
ui_print("-Formatting Data");
format("ext4", "EMMC", "/dev/block/mmcblk0p26");
ui_print("-Formatting System");
format("ext4", "EMMC", "/dev/block/mmcblk0p25");
ui_print("-Writing System");
mount("ext4", "EMMC", "/dev/block/mmcblk0p25", "/system");
package_extract_dir("system", "/system");
show_progress(0.400000, 0);
ui_print("-Formatting Cache");
assert(unmount("/cache"), ui_print("/cache unmounted"));
format("ext4", "EMMC", "/dev/block/mmcblk0p27");
u do realize that ppl dont have 25+ partitions on SDCARD right?
also the init.rc files will have to be changed... cause the init*.rc files mount the /system /data & /cache as MTD
DooMLoRD said:
the sdcard needs to be of a higher class (class 6 and above) to actually gain some performance benefits.... else it will all lag..
btw we can get multiboot based on this...
Click to expand...
Click to collapse
hmm i'm using a class 2 on my incredible s and definitely no lag at all...
What class does the stock 8gb have?
@doom so many winks in ur post?
Sent from my X10i using xda premium
spaarc said:
I have been going through many things ,
REQUIRES UNLOCKED BOOTLOADER
And finally made this ,
This is a flash able zip which requires cwm4 recovery and a rom which supports ext4 partition after that
Otherwise the partition gets removed
Since we don't have many roms with Ext4
I'll just include this zip
I just heard someone wanted a good dev who would make something good , other than barebones
http://www.mediafire.com/?5gotc36iav7hphy
Click to expand...
Click to collapse
wow
This project is very interesting for me.
If you have any orders, please tell me
DooMLoRD said:
the sdcard needs to be of a higher class (class 6 and above) to actually gain some performance benefits.... else it will all lag..
btw we can get multiboot based on this...
EDIT:
based on the update.zip u posted...
Code:
ui_print("-Formatting Data");
format("ext4", "EMMC", "/dev/block/mmcblk0p26");
ui_print("-Formatting System");
format("ext4", "EMMC", "/dev/block/mmcblk0p25");
ui_print("-Writing System");
mount("ext4", "EMMC", "/dev/block/mmcblk0p25", "/system");
package_extract_dir("system", "/system");
show_progress(0.400000, 0);
ui_print("-Formatting Cache");
assert(unmount("/cache"), ui_print("/cache unmounted"));
format("ext4", "EMMC", "/dev/block/mmcblk0p27");
u do realize that ppl dont have 25+ partitions on SDCARD right?
also the init.rc files will have to be changed... cause the init*.rc files mount the /system /data & /cache as MTD
Click to expand...
Click to collapse
That's why I had to write "Devs only"
But every one comes in
This is still alpha and needs to be corrected
I don't know it that well , but It's a start ...
Can you briefen on the topic and any solutions etc .????
---------- Post added at 08:04 PM ---------- Previous post was at 08:02 PM ----------
ThJap said:
wow
This project is very interesting for me.
If you have any orders, please tell me
Click to expand...
Click to collapse
Can you start converting your ROM to updater-script and update-binary
Can u get CWM4 Recovery running ?
That would allow to run it right now
sahibunlimited said:
What class does the stock 8gb have?
@doom so many winks in ur post?
Sent from my X10i using xda premium
Click to expand...
Click to collapse
2, stay on topic - this sounds amazing guys - i have a 6 and a 10 so would be willing to test on my "spare" samsung c6 8gb.
best regards.
nice one my friend ,
cheers
Achotjan
Can some one help me improve this ?
sent from my lunched full_x10 eng.root using xda's git repo
spaarc said:
That's why I had to write "Devs only"
But every one comes in
This is still alpha and needs to be corrected
I don't know it that well , but It's a start ...
Can you briefen on the topic and any solutions etc .????
Click to expand...
Click to collapse
yes dont worry i can help u out with this...
i was actually working on a bootmenu:
{
"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"
}
we can add an option to it saying:
"boot into SDCARD OS"
spaarc said:
Can some one help me improve this ?
sent from my lunched full_x10 eng.root using xda's git repo
Click to expand...
Click to collapse
yes i can
wait we need to get a few things ready before...
here is wht we need:
1) willing testers, who are ready to repartition SDCARD (may render SDCARD unusable later on!!!!)
2) a CLEAN ROM (no tweaks/etc) [we can add them later]
3) ramdisk which we will use (i can help out with that)
4) bootmenu (i already have most of it ready)
DooMLoRD said:
yes dont worry i can help u out with this...
i was actually working on a bootmenu:
we can add an option to it saying:
"boot into SDCARD OS"
yes i can
wait we need to get a few things ready before...
here is wht we need:
1) willing testers, who are ready to repartition SDCARD (may render SDCARD unusable later on!!!!)
2) a CLEAN ROM (no tweaks/etc) [we can add them later]
3) ramdisk which we will use (i can help out with that)
4) bootmenu (i already have most of it ready)
Click to expand...
Click to collapse
Im in .
Willing to risk my sd card ( i have 2gb spare sd card , but if it won't suite for the job i have my daily 8gb one . )
And plz give detailed instructions cause im a noooob .
For a rom , I think z's freex10 suites for the job.
Oodie said:
Im in .
Willing to risk my sd card ( i have 2gb spare sd card , but if it won't suite for the job i have my daily 8gb one . )
And plz give detailed instructions cause im a noooob .
For a rom , I think z's freex10 suites for the job.
Click to expand...
Click to collapse
Same here
Sent from my X10_AOSP using xda premium
likewise - as said before i have a sacrificial card, but it's a good c6, so perhaps when you need a higher class card tested let me know!!

Pls Help, can't flash LeeDroid kernel, cwm recovery status 7

I haven't yet tried a custom rom. Everything's been running nicely. S-Off, rooted, a few apps with su permissions installed, and some junk (facebook, kidmode, etc.) removed from the rom via Root Uninstaller...
I thought I might try LeeDroid's GB kernel. I was led to believe it could be flashed over stock HTC rom... Device is a BB Flyer (16 GB Wifi only)...
original hboot was 1.11.0003
original build was (android 2.3.3) BrightstarUS_WWE 1.36.1540.32
after one OTH upgrade to (android 2.3.4) current build is now 2.27.1540.31
S-Off via Revolutionary, and rooted with su-3.0-beta4-efgh-signed.zip
Everything runs with no issue, and I've made Nandroid backup(s).
Multiple attempts to upgrade to LeeDroid GB kernel only (not ROM) have failed with Status 7.
A few pics...
{
"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"
}
I'm a little confused as to why this is and what to do about it. I've searched, but haven't found any answers specific to this device.
Zip was put on the root of the external SDHC... system (ES File Explorer) sees it as /sdcard/ext_sd and also as /sdcard2 - I don't know how cwm deals with it. Is my version of CWM the wrong one?
This flash disabled my ability to boot into hboot so I had to do this via adb and then run the cwm restore of boot and system... so everything is back and running nicely. No problems. Everything works well but I'm still confused about the state of what I have here...
It's S-Off. It's rooted. CWM works. Why can't I flash this?
Any help, advice, or explanations would be appreciated.
Thanks, -Rob
Have you tried a re download
Or
Fastboot flash the extracted boot.img
Sent from my HTC Flyer P510e using xda premium
mcord11758 said:
Have you tried a re download
Click to expand...
Click to collapse
No, but I did upgrade CWM Recovery from Revolutionary CWM4 to DooMLoRD's GB CWM5... tried again, and got the same results.
mcord11758 said:
Or... Fastboot flash the extracted boot.img? ...
Click to expand...
Click to collapse
I just did re-download the file and I've extracted the zip contents... but I don't know how to Fastboot flash the extracted boot.img... (I mean), I don't see a "boot.img" or any .img and I'm not sure what to do with the extracted files.
Any quick advice?
Forget the boot.img idea
ReDownload the kernel and try again
Sent from my HTC Flyer P510e using xda premium
mcord11758 said:
Forget the boot.img idea
ReDownload the kernel and try again ...
Click to expand...
Click to collapse
Yes, done, a few times... have all been the same - FAIL.
I've read that Status 7 errors have to do with the updater-script (in META-INF). I've opened the script in a Notepad and noticed a 'minor' difference in one of the assert statements relative to my build.prop...
Attempts to edit this and reflash have failed.
I had d/l'ed that Kernel file from the LeeDroid GB thread (here at XDA)... Now I've re-downloaded the Kernel file from LeeDroid's mini site...
Now something about ext4 & EMMC (system/script didn't recognize EMMC) whatever... this is all a bit over my head, but I'm still reading up on ways to accomplish - what should be a simple thing.
I've tried installing from the external SD... the internal SD... ??? and WTF is EMMC anyway??? Haha Lol,
I'll get it.
[edit] - speaking off the top of my (half-empty) head... I'm pretty certain that there is no ext4 partition on my Flyer, and if this has to do with the mount points (or changing them), I'm still clueless... Anyway this might work if I knew how to properly edit the updater-script... but I don't - and whatever else it is, I don't know.
(LeeDroid where are you???) - help me... please
This is the updater-script.
#Updater-script LeeDrOiD
#For the HTC Flyer
#Follow me on Twitter @LeeDrOiD
show_progress(0.500000, 0);
ui_print("-Checking Model ID");
assert(getprop("ro.product.device") == "flyer" || getprop("ro.build.product") == "flyer" || getprop("ro.product.board") == "flyer");
ui_print("-Success!");
ui_print("-Model ID - HTC Flyer");
ui_print("-Ok to proceed");
ui_print("-Now flashing LeeDrOiD Flyer V3.1.0-KERNEL");
show_progress(0.500000, 40);
ui_print("Extracting modules");
mount("ext4", "EMMC", "/dev/block/mmcblk0p25", "/system");
package_extract_dir("system", "/system");
set_perm_recursive(0, 2000, 0755, 0755, "/system/etc/init.d");
unmount("/system");
ui_print("Extracting zImage...");
package_extract_dir("kernel", "/tmp");
ui_print("Adding kernel boot.img...");
set_perm(0, 0, 0777, "/tmp/dd");
set_perm(0, 0, 0777, "/tmp/mkbootimg.sh");
set_perm(0, 0, 0777, "/tmp/mkbootimg");
set_perm(0, 0, 0777, "/tmp/unpackbootimg");
ui_print("Packaging boot.img...");
run_program("/tmp/dd", "if=/dev/block/mmcblk0p22", "of=/tmp/boot.img");;
run_program("/tmp/unpackbootimg", "/tmp/boot.img", "/tmp/");
run_program("/tmp/mkbootimg.sh");
ui_print("Flashing boot.img ...");
assert(write_raw_image("/tmp/newboot.img", "boot"),
delete("/tmp/boot.img"));
ui_print(" ");
ui_print("-Flashing Complete");
ui_print("Welcome to the world of");
ui_print(" ");
ui_print("L EEEE EEEE DDD RRR OO IIIII DDD ");
ui_print("L E E D D R R O O I D D ");
ui_print("L EEE EEE D D R R O O I D D ");
ui_print("L E E D D R R O O I D D ");
ui_print("LLLL EEEE EEEE DDD R R OO IIIII DDD ");
ui_print(" ");
show_progress(0.100000, 0);
-----------------------------------------------------------------------------
(I know) there is no "ro.build.product" statement in my build.prop... there is an "ro.product.model" ...and my editing to match did nothing.
Also, from what I see... the flash crashes here; "assert(write_raw_image("/tmp/newboot.img", "boot")" ...but I don't know how to fix.
Anyone?
Feel free to chime-in.
-Rob
Try run the Honeycomb RUU upgrade guide on XDA and then downgrade to GB again then try flash again. Takes some time but it should work then
zummer22 said:
Try run the Honeycomb RUU upgrade guide on XDA and then downgrade to GB again then try flash again. Takes some time but it should work then
Click to expand...
Click to collapse
Good advice. Thank you, it just might work. I've read though that entire thread (with the thought of an upgrade to HC), but considering, I have no use for the pen and don't own one... and everything as is works so well for me in GB... I think I'll just leave my Flyer as is. Good as Lee's Kernel may be, I'm not yet convinced that it's worth taking the time & jumping through all those hoops to get it. ---This should've been a quick clean painless install. If someone (here at XDA) could explain to me just why this isn't working the way it should, I might have the impetus to go the long way around... but for now, I'll just chill with what I have.
Thank you for the good suggestion.
mcord11758 said:
Forget the boot.img idea
ReDownload the kernel and try again
Sent from my HTC Flyer P510e using xda premium
Click to expand...
Click to collapse
Reloading the kernel (many times) didn't work, and had unpleasant repercussions. TG 4 cwm, so all's well...
but the boot.img wasn't really a bad idea. I couldn't do it with the kernel.zip (because there wasn't one to extract), but I did d/l Lee's Rom, extracted the boot.img and flashed it via fastboot. It worked! but it also broke my wifi...
TG 4 cwm. (Lol)
Thinking this might still be a good idea, I d/l'ed Nicki Berli's FlyHigh Rom, extracted the boot.img for his upgraded kernel, and tried again. Got similar results, (Lol), - I'm getting good practice here.
TG 4 cwm.
zummer22's idea to do a complete downgrade and try again (I think) might probably work... but, I'm still rooted, everything works as it should, GB's pretty snappy, I've jettisoned a lot of bloat with root uninstaller, still enjoying the stock Sense launcher and switching off to GoLauncherEX now & then (to keep it interesting)...read-up enough on HC to know that I don't want it ...and I'm not convinced that any of the custom GB roms are any more polished and less trouble-free than what I have now. But, but maybe for S & G's... I'll try something, again, another day.
Thanks for the help anyway.

Color OS 2.0.6 Beta +PreRooted+Customized

Dear All
Since many are having problems flashing color os 2.0.6 beta with root (plus chinese websites downlaods are amazing slow in countries like mine), i thought to create this thread.this is a highly customized rom from the chinese Forum. i have been playing for a couple of hours and everything looks good
This comes prerooted with lots of amazing feautures and is a stripped down version of color os.
The advantage you get over CM11 are many the main ones are MIUI Like customized theme and Amazing camera quality
Please Note that you have to use the Chinese recovery provided in the zip as it does not work with any other recovery. the recovery will be in Chinese (i believe the first one is reboot, second one is install from zip, third option is wipe factory data, fourth is wipe cache )
Alternatively you could also use the following command
fastboot boot recovery.img (but rename the recovery file to "recovery" first, this does not flash the recovery only boots it up so make sure the usb cable stays connected until you boot up color os )
UNZIP THE FILE FIRST(as it includes the recovery)
once the colors os is booted you would have to change the language, once you go to settings in the first (general tab third last row there is a language and input method, use that to change to english)
This ROM-based version 7.25 Date Coloros2.0.6 streamline modifications to optimize, adding a number of optimization and stability testing. This ROM is carefully modified, expect everyone's advice and support, has introduced more and better ROM to select local friends.
Feautures
Delete the official recovery, and all script
two streamlined out security center, delete QQ, microblogging and other pre-installed software.
3 Add the latest full version root.
4 forced GPU rendering.
5 optimize brightness:
Auto Brightness: 8 Maximum 215 Minimum brightness
manually Brightness: 255 Default minimum 8 maximum 80
June optimized GPS, speed up the positioning speed.
7 integration Bravia_Engine_V3 imaging engine.
8 Update Host library block ads + Google login.
9 Add _Fly-On_Mod new optimization:
10 optimized touch-screen effect
11. optimize cpu running
12.zipalign optimize application
13. optimized memory management
database optimization 14.SQL
15. optimize network
16. optimize battery power
17 degrees to mention 4096 memory reads
18. improve the overall touch response
19. reducing dialing time
20. improve the picture quality to 100%
21. optimization window animations optimized
22. improve the quality of pictures and video of
23. improve fluency and reaction slide
24. improve the black screen problem after the call ends
25. repair some application error problem
26. unlocked FPS improve performance 2D/3D
27. upgrade virtual memory to 128M_build
28. modify some scripts to optimize and streamline redundant depth streamline
29.FM join the most popular Koala FM, replacing the input method for the most succinct Iflytek input method, cocoa Replace the App Store's most comprehensive national database Baidu mobile assistant
part of the streamlining of the list:
ApplicationsProvider.apk
BasicDreams.apk
Browser.apk
CertInstaller.apk
DayDreamVideo.apk
DigitalPenWorkService.apk
Email.apk
etao_huoyan.apk
Exchange.apk
FaceDetectService.apk
FaceLock.apk
FreeWeatherLiveWallpaper.apk
HTMLViewer . apk
IFlySpeechService.apk
KeKeGameCenter.apk
KeKeMarket.apk
LiveWallpapers.apk
MHeiGB18030C_Medium.apk
NoiseField.apk
OppoActionParser.apk
OppoBaiduTranslateService.apk
OppoBootReg.apk
OppoDigitalClockWidget.apk
OppoDriveMode.apk
OppoFileTransfer.apk
OppoLockScreenCard.apk
OppoLockScreenGlassBoard.apk
OppoLockScreenTravel.apk
OppoScratch.apk
OppoSpeechAssist.apk
OppoSpeechService.apk
PhaseBeam.apk
PicoTts.apk
QuickSearchBox.apk
Reader.apk
SharedStorageBackup.apk
SogouIME-build54468_20140717.apk
UserDictionaryProvider.apk
VoiceSearch.apk
Voiceprint.apk
{
"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"
}
Mods: mods should you feel that this thread is unnecessary, redundant or does not belong here please feel free to trash it anytime.
Credits to
DMO7.26
MIUI Indifferent
Note: UNZIP THE FILE FIRST
ROM: https://mega.co.nz/#!AlE0AAjI!ibyFA5Lxan2u5qFQSRgLlidQEztKOWkyaX_JNxKATzM
Working Gaps for Color OS
http://www.androidfilehost.com/?fid=23189362627840912
Download now..thanx
Sent from my One using XDA Premium 4 mobile app
Just as an FYI... You can modify updater-script in a way that it is flashable via TWRP like I did. I can provide my zip later, then you can root it if you want to.
Sent from my A0001 using XDA Premium 4 mobile app
dansou901 said:
Just as an FYI... You can modify updater-script in a way that it is flashable via TWRP like I did. I can provide my zip later, then you can root it if you want to.
Sent from my A0001 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
that would be perfect and would benefit all, thanks
Root color os using this zip
Just for information....
One can flash this zip http://d-h.st/zJ8 to root successfully color os for oneplus one...
Thanks...
:good:
---------- Post added at 05:52 PM ---------- Previous post was at 05:51 PM ----------
alybhamani said:
that would be perfect and would benefit all, thanks
Click to expand...
Click to collapse
See this link ... http://d-h.st/zJ8
flashable zip
dansou901 said:
Just as an FYI... You can modify updater-script in a way that it is flashable via TWRP like I did. I can provide my zip later, then you can root it if you want to.
Sent from my A0001 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
hello
could you please provide the zip file so i can install it through twrp, im not able to flash the Chinese recovery.
thanks in advance
mr_wehbe said:
hello
could you please provide the zip file so i can install it through twrp, im not able to flash the Chinese recovery.
thanks in advance
Click to expand...
Click to collapse
If you have the color os rom zip with you, then open it with 7zip and just extract the file
META-INF/com/google/android/updater-script
then edit it with notepad ++ ,
remove the 1st line .....
assert(getprop("ro.product.device") == "A0001" getprop("ro.build.product") == "A0001");
or
edit the 1st line as ...
assert(getprop("ro.product.device") == "A0001" || getprop("ro.product.device") == "bacon" || getprop("ro.build.product") == "bacon" || getprop("ro.build.product") == "A0001");
Then put back the edited file in the opened ROM Zip file (by 7zip)
Save...
Then try flashing the zip from TWRP,
let me know in case of any issue ...
Mnt-XDA said:
If you have the color os rom zip with you, then open it with 7zip and just extract the file
META-INF/com/google/android/updater-script
then edit it with notepad ++ ,
remove the 1st line .....
assert(getprop("ro.product.device") == "A0001" getprop("ro.build.product") == "A0001");
or
edit the 1st line as ...
assert(getprop("ro.product.device") == "A0001" || getprop("ro.product.device") == "bacon" || getprop("ro.build.product") == "bacon" || getprop("ro.build.product") == "A0001");
Then put back the edited file in the opened ROM Zip file (by 7zip)
Save...
Then try flashing the zip from TWRP,
let me know in case of any issue ...
Click to expand...
Click to collapse
If you want to eliminate every error, you have to look for the line "wipe.data()" (or similar) and remove it (that line produces an error, but the ROM boots fine)
Sent from my A0001 using XDA Premium 4 mobile app
The Data Monitor doesn't work, it need to be configured first but the configuration offers to choose only Chinese telecom providers.
Edit :
Sorry mate, your optimization maybe too much, only google apps can access cellular data, there is no connection for any other apps.
I just installed the regular beta 2.06 and every apps can access internet .
lapocompris said:
The Data Monitor doesn't work, it need to be configured first but the configuration offers to choose only Chinese telecom providers.
Edit :
Sorry mate, your optimization maybe too much, only google apps can access cellular data, there is no connection for any other apps.
I just installed the regular beta 2.06 and every apps can access internet .
Click to expand...
Click to collapse
is any one facing problem with youtube?
i have problem after flashing the gapps in youtube
regards
closed at OP request...
so...OTAs are not available for colorOS when rooted? also, no matter what root zip i use, supersu says it can't root and i dont have root, though colorOS complains i have rooted and will thus neuter the os. Any advice from anyone on fixing either of these issues?
Anyone can share camara app?
Anyone tried this with MultiRom? I want to try this with Multirom
darkerm said:
Anyone tried this with MultiRom? I want to try this with Multirom
Click to expand...
Click to collapse
me too... If someone tell us if it works thanks you
Is the link correct?
i also want to know if this work with multirom, no one has tried it yet?
Google Play?
chailee said:
i also want to know if this work with multirom, no one has tried it yet?
Click to expand...
Click to collapse
It works, but only if you switch Color OS to primary every boot and after you're done you have to switch it back to secondary. This takes approx. 5 min and is annoying as hell.
The reason for this is that Color OS doesn't have a custom kernel since it's closed source. MultiROM needs the kernel of the primary ROM to have the kexec-hardboot patch included. The secondary ROM's kernels don't need this patch.
So when you install it as Primary, your secondary ROMs won't work because the kexec-hardboot patch is missing, but as a secondary ROM with a primary ROM that does have the patch it won't boot.
I hope that suffices as an explanation.
-Mats
I'm use flashify for backup coloros kernel and secondary ROM kernel and i restore the correct kernel , after i switch the ROM.

[GUIDE] Make any rom OS2SD

OS2SD for any rom ​
As I see there is many P500 users interested to put their ROM to sd card, so I'm providing this tutorial how to make any rom bootable from sd.
Requirements:
Linux or cygwin for Windows
Boot.img tools
Modified updater-script
Modified fstab
Correctly partitioned sdcard (Guide)
TWRP-OS2SD or TWRP-MULTI
Steps:
Replace updater-script in your's ROM zip with provided. It will probably work with all kitkat based roms. If not the idea is mounting /system on sd card so change all "mount("yaffs2", "MTD", "system", "/system");" lines with "mount("ext4", "EMMC", "/dev/block/mmcblk0p2", "/system");" in original updater-script
Extract bootimg-tools.zip and paste boot.img from your rom in same foder
Open terminal or cygwin, locate folder with boot.img tools and type "./extractboot boot.img"
This will create out folder. Replace fstab.p500 and init.qcom.rc in out/ramdisk with provided (they might need rework on older roms)
In terminal type "./packboot"
Now rename boot_new.img to boot.img and pase it to rom zip
Flash rom zip with one of provided TWRP versions
should probably work back thru 4.0 but froyo/gingerbread init won't mount any sd partitions before boot is completed.
just curious, why this partition layout?
I used p2 for /data until wiping it by accident several times swapping my sd to a phone with pre-os2sd recovery.
of course, I've modded my own os2sd partition map several times now experimenting, and the order doesn't seem to matter.
and i was wondering, could you post your twrp modifications for internal/os2sd hybrid? i had one kinda working but it was glitchy.
I used this configuration to keep swap working if enabled, because default is p3. Also p4 for /data because it not used by anything else, so it's safe. I think you are right, order doesn't impact performance. Will send you config of twrp then be on pc.
Sent from my LG-P500 using xda premium
HardLight said:
I used this configuration to keep swap working if enabled, because default is p3. Also p4 for /data because it not used by anything else, so it's safe. I think you are right, order doesn't impact performance. Will send you config of twrp then be on pc.
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
I'm not seeing any other ROMs of this style floating around.
The only reason I didn't leave p3 for swap is that it wasn't being used yet when I started with the os2sd stuff. I tried sticking it on p2 (instead of the stubby sd-ext I had there to satisfy the odd this-or-that which demanded sd-ext,) and that worked ok, but I hadn't set sd-swap as a default in any builds.
since you're building similar stuff now, maybe I'll drift mine into your partition map in the interest of some sort of unification. and I'd like to match up the twrps, too.
especially if the sd-swap is working well on the p500.
everybody who's been dealing with my versions for any length of time now since it came out in February, is used to having to upgrade recovery and deal with incompatible backups from earlier releases anyway.
thanks for your contributions.
Thank You
HardLight said:
OS2SD for any rom ​
As I see there is many P500 users interested to put their ROM to sd card, so I'm providing this tutorial how to make any rom bootable from sd.
Requirements:
Linux or cygwin for Windows
Boot.img tools
Modified updater-script
Modified fstab
Correctly partitioned sdcard (Guide)
TWRP-OS2SD or TWRP-MULTI
Steps:
Replace updater-script in your's ROM zip with provided. It will probably work with all kitkat based roms. If not the idea is mounting /system on sd card so change all "mount("yaffs2", "MTD", "system", "/system");" lines with "mount("ext4", "EMMC", "/dev/block/mmcblk0p2", "/system");" in original updater-script
Extract bootimg-tools.zip and paste boot.img from your rom in same foder
Open terminal or cygwin, locate folder with boot.img tools and type "./extractboot boot.img"
This will create out folder. Replace fstab.p500 and init.qcom.rc in out/ramdisk with provided (they might need rework on older roms)
In terminal type "./packboot"
Now rename boot_new.img to boot.img and pase it to rom zip
Flash rom zip with one of provided TWRP versions
Click to expand...
Click to collapse
Thank You for posting the guide as requested. Awesome, now I will try to make some ROMs bootable in sdcard, and try them in my phone.
bigsupersquid said:
should probably work back thru 4.0 but froyo/gingerbread init won't mount any sd partitions before boot is completed.
Click to expand...
Click to collapse
i think that you are wrong
i have a gingerbread installed on SD (and kitkat CM11 by mukulsoni on internal)
i used Multirom manager 5.1 by arnab321 based on work by Tassadar
http://forum.xda-developers.com/showthread.php?t=1828151
HardLight: can you make this procedure work like the one in Multirom ?
it allows me to have GB and KitKat installed at the same time, both are bootebel using the same recovery and im only a boot away from moving from one to the oder
danielboro said:
i think that you are wrong
i have a gingerbread installed on SD (and kitkat CM11 by mukulsoni on internal)
i used Multirom manager 5.1 by arnab321 based on work by Tassadar
http://forum.xda-developers.com/showthread.php?t=1828151
HardLight: can you make this procedure work like the one in Multirom ?
it allows me to have GB and KitKat installed at the same time, both are bootebel using the same recovery and im only a boot away from moving from one to the oder
Click to expand...
Click to collapse
multirom has preinit of its own, runs before GB init, and uses busybox to mount sd folders. It also mods init.rc to not mount the MTD partitions.
it would have to be recoded because, among other things, init.rc doesn't mount the filesystems anymore, it's moved to init.qcom.rc or init.device.rc (init.p500.rc or init.thunderc.rc in the current OS2SD versions.)
to use OS2SD like multirom, it would have to bind-mount folders or filesystem images from the card instead of mounting partitions directly, unless android can 'see' more than 4 card partitions now. It used to be limited to 4 back in GB.
Plus unless kexec is working every OS installed has to work with the kernel in the boot.img for tasssadar's original code (the app you're using is reflashing a new boot.img every time you change OS's, which will eventually trash your boot NAND memory,)
bigsupersquid said:
multirom has preinit of its own, runs before GB init, and uses busybox to mount sd folders. It also mods init.rc to not mount the MTD partitions.
it would have to be recoded because, among other things, init.rc doesn't mount the filesystems anymore, it's moved to init.qcom.rc or init.device.rc (init.p500.rc or init.thunderc.rc in the current OS2SD versions.)
to use OS2SD like multirom, it would have to bind-mount folders or filesystem images from the card instead of mounting partitions directly, unless android can 'see' more than 4 card partitions now. It used to be limited to 4 back in GB.
Plus unless kexec is working every OS installed has to work with the kernel in the boot.img for tasssadar's original code (the app you're using is reflashing a new boot.img every time you change OS's, which will eventually trash your boot NAND memory,)
Click to expand...
Click to collapse
ill start at the end
flashing boot is no worse then flashing a new rom but its less work and less time
i like GB for the speed and batt use but from time to time i need to run ting that wont work on GB(at list not on the 1 i chose after trying ~12 rom`s)
having kitkat installed and using multirom to change is faster
so, any chance of implementing the bind-mount option?
prite please
:fingers-crossed:
danielboro said:
ill start at the end
flashing boot is no worse then flashing a new rom but its less work and less time
i like GB for the speed and batt use but from time to time i need to run ting that wont work on GB(at list not on the 1 i chose after trying ~12 rom`s)
having kitkat installed and using multirom to change is faster
so, any chance of implementing the bind-mount option?
prite please
:fingers-crossed:
Click to expand...
Click to collapse
Just install your GB rom to internal memory and cm11 OS2SD to sd card, then make two flashable zips (or backups) of both roms boot.img and flash them respectively to rom you want to boot. Just keep in mind that GB won't be able to use sd-ext, because it's os2sd system partition.
Sent from my LG-P500 using xda premium
HardLight said:
Just keep in mind that GB won't be able to use sd-ext,
Click to expand...
Click to collapse
this is way i was hoping for the mount-bind
at the moment GB is on P2, swap on P3 and kitkat uses P4 as /sd-ext
i have some limited knowledge, ill try to see if i can do something wen ill have the time
any pointer on how i can use mount-bind ?
all the work on developing the p500 helps extend it life
thanks
p.s.
what is the MULTI in TWRP-MULTI?
danielboro said:
this is way i was hoping for the mount-bind
at the moment GB is on P2, swap on P3 and kitkat uses P4 as /sd-ext
i have some limited knowledge, ill try to see if i can do something wen ill have the time
any pointer on how i can use mount-bind ?
all the work on developing the p500 helps extend it life
thanks
p.s.
what is the MULTI in TWRP-MULTI?
Click to expand...
Click to collapse
the multi can flash os2sd & normal rom, so you have not to change between recoveries
ThAnKs
Thanks alot for this guide.....
have anyone tried it on an ICS rom ?
getting this error using cygwin
{
"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"
}
maybe it doesnt work with cygwin , i am trying to make genetICS 9.1.6 OS2SD compatible ..
nomancoolboy said:
getting this error using cygwin
maybe it doesnt work with cygwin , i am trying to make genetICS 9.1.6 OS2SD compatible ..
Click to expand...
Click to collapse
For starters , you need Perl installed for that script.
Second, ics don't use fstab, you'll have to change init.rc
And maybe even recompile init with a delay inside, like on GB.
otherwise init may not mount the card partitions.
The easy way to run ICS from card is tasssadar's multirom. You can find the thread buried in this forum.
I'm using HardLight's GenetICS 9.1.7 with the OS2SD mod. It's the most stable and smoothest with long battery life and 1.5GB in the data partition for my apps. Also successfully made it with Hephappy's ICS Plus simply modifying the updater-script inside the zip and search the mounting points in the 'init.rc' and 'init.qcom.rc', then just have to modify the lines following the first post.
Greetings from Costa Rica!
Enviado desde mi LG-P500 usando Tapatalk
@HardLight
This is twrp-multi, renamed to boot.img. I have previously extracted recovery images this way using apktool.
[email protected]:~/bootimg-tools$ ./extractboot boot.img
Page size: 2048 (0x00000800)
Kernel size: 2803424 (0x002ac6e0)
Ramdisk size: 2294087 (0x00230147)
Second size: 0 (0x00000000)
Board name:
Command line: mem=471M console=ttyMSM2,115200n8 androidboot.hardware=p500 no_console_suspend
Writing boot.img-kernel ... complete.
Writing boot.img-ramdisk.gz ... complete.
gzip: ../../boot.img-ramdisk.gz: not in gzip format
cpio: premature end of archive
Any other tools needed to make this work? (ubuntu 14.04)
manu3193 said:
I'm using HardLight's GenetICS 9.1.7 with the OS2SD mod. It's the most stable and smoothest with long battery life and 1.5GB in the data partition for my apps. Also successfully made it with Hephappy's ICS Plus simply modifying the updater-script inside the zip and search the mounting points in the 'init.rc' and 'init.qcom.rc', then just have to modify the lines following the first post.
Greetings from Costa Rica!
Enviado desde mi LG-P500 usando Tapatalk
Click to expand...
Click to collapse
Can you share the modified files to be replaced in the rom.
hi all - thanks for these instructions. I tried to apply these to cm-9.1.5-GenetICS-Final-P500+gapps.zip and cm-9.1.7-GenetICS-HardLight-p500.zip.
In those roms I had to update the updater-script (I had to remove the format command otherwise the install would fail - but i figured that should be ok since the ext4 partition can be formatted externally - if i remember to do it).
I also updated the init.rc in the (mount mtd partitions section), but no updates to the init.qcom.rc
Each time I try to install a ROM, the device gets stuck at the LG boot logo.
I get the same problem with those zip's installing from TWRP MULTI's "Internal" mode. So I suspect something else is wrong...
interestingly, the only zip I can install successfully is the cm11.0.0-20160101-os2sd-ext4-p500.zip. Works like a charm, just dies in a matter of hours with Wifi on.
eldamobo said:
hi all - thanks for these instructions. I tried to apply these to cm-9.1.5-GenetICS-Final-P500+gapps.zip and cm-9.1.7-GenetICS-HardLight-p500.zip.
In those roms I had to update the updater-script (I had to remove the format command otherwise the install would fail - but i figured that should be ok since the ext4 partition can be formatted externally - if i remember to do it).
I also updated the init.rc in the (mount mtd partitions section), but no updates to the init.qcom.rc
Each time I try to install a ROM, the device gets stuck at the LG boot logo.
I get the same problem with those zip's installing from TWRP MULTI's "Internal" mode. So I suspect something else is wrong...
interestingly, the only zip I can install successfully is the cm11.0.0-20160101-os2sd-ext4-p500.zip. Works like a charm, just dies in a matter of hours with Wifi on.
Click to expand...
Click to collapse
roms not built for kernel swapped system/userdata (kitkat only built this way, and not older kitkat versions) will flash to the wrong partition and won't boot.
change your updater-script to switch system and userdata for older roms to flash correctly with the twrp-multi in internal mode.

Categories

Resources