[HOWTO][AROMA][DUALBOOT]Flash all KK 4.4.2 with/without DorimanX[post30]

Search This thread
By:
Advanced…
marjune23

marjune23

Senior Member
Sep 1, 2011
2,205
4,057
rspcrew said:
Hi,

Got a question, i wanna DB my SGS2, 1st ROM ==> I9100XWMS3_NeatROM_v5.9_Aroma / 2nd ROM Ressurection Remix KK version

for now i only have Ressurection Remix on my phone.

Can i clone it to 2nd ROM and then wipe the first one and install Neat. Or should i completly wype and install them one by one ?

Also, i'm with a Kernel DorimanX 10.43v65 is that ok or i have to get the 8 ?

(Sorry for any errors in my english, obviously not my native language)
Click to expand...
Click to collapse
hahaha @Troubadour666, guess what? am here now oh yeah...:D:thumbup:

Mate, TDB's procedure is good and same with the @nik60's procedure ;););)

For more detailed procedure and for the links, go to my signature and you will find a link for dualbooting...
Just replace the AOSP NeatRom by RR KK Rom as per you want...
And in the end, just swap the Roms using the dual-option in dorimanx recovery to make your kk rom in 2ndRom and neatrom in 1stRom...;)

PS: If you're going to trace all the links of TDB, i suggest you not to do it anymore...
You'll just gonna confuse yourself hahaha...
Maybe am the only one who knows where to find those links.
As TBD already said, even him he didn't know where to find his works...:p:p:p
Too many to mention that's why he is now an RC...oh yeah...

If you want to use one of his best work, download the Modified NeatRom v5.9 on this post instead the one in Nik60's thread...:highfive:

My tapatalk Signature
 
Last edited:
  • Like
Reactions: Troubadour666, rspcrew and nik60
R

rspcrew

New member
Mar 13, 2014
3
4
Ok, thank u all for the answers.

I'll take a look when i'll got some time for it, it seems a bit tricky to me since i started mod 2 days ago :)

There's a lot of stuff / links and it don't appears to be really clear for my little brain.

Edit 1 -- 10:50... : followed @marjune23 topic, was pretty clear, for now i got RR KK on 1st ROM and i'm actually booting Neat for the 1st time on the 2nd ROM... it's long so let's hope it'll works.
 
Last edited:
  • Like
Reactions: Troubadour666 and marjune23
marjune23

marjune23

Senior Member
Sep 1, 2011
2,205
4,057
rspcrew said:
Ok, thank u all for the answers.

I'll take a look when i'll got some time for it, it seems a bit tricky to me since i started mod 2 days ago :)

There's a lot of stuff / links and it don't appears to be really clear for my little brain.

Edit 1 -- 10:50... : followed @marjune23 topic, was pretty clear, for now i got RR KK on 1st ROM and i'm actually booting Neat for the 1st time on the 2nd ROM... it's long so let's hope it'll works.
Click to expand...
Click to collapse

Good luck mate...keep on updating us...

PS: I hope @ssanjy will have success next time...
 
  • Like
Reactions: Troubadour666 and rspcrew
Troubadour666

Troubadour666

Inactive Recognized Contributor
Aug 3, 2012
3,140
7,035
43.7031 - 7.2661
rspcrew said:
Both ROM works !!!

Now i'm swapping them. keep hoping :)

Edit 11:35 ==> Swap ok.

TY for your help guys, i'm pretty sure i won't have find marjune23 topic without you (L). Now it's time for me to restore my apps/contact/sms etc... :)
Click to expand...
Click to collapse

Yeah....you win !!!! Good to ear again a simly success !

Sent from my GT-I9100 using Tapatalk
 
  • Like
Reactions: rspcrew and marjune23
marjune23

marjune23

Senior Member
Sep 1, 2011
2,205
4,057
rspcrew said:
Both ROM works !!!

Now i'm swapping them. keep hoping :)

Edit 11:35 ==> Swap ok.

TY for your help guys, i'm pretty sure i won't have find marjune23 topic without you (L). Now it's time for me to restore my apps/contact/sms etc... :)
Click to expand...
Click to collapse
Welcome to dualboot world mate...keep visiting our threads....we post everywhere hahaha...

For additional mods for dualboot of NeatRom v5.9, visit again my thread, post #2...;)

MockingJay1994 said:
learning
Click to expand...
Click to collapse
Keep on learning mate, I've been with your situations also...don't afraid to try everything:)

My tapatalk Signature
 
  • Like
Reactions: rspcrew and Troubadour666
Troubadour666

Troubadour666

Inactive Recognized Contributor
Aug 3, 2012
3,140
7,035
43.7031 - 7.2661
vagaerg said:
Is there any problem with downgrading MaliV3 to MaliV2?

I mean, will I loose performance? Will it be less stable?

Thank you
Click to expand...
Click to collapse

I use for now DorimanX kernel 8.43v99.4.test (LOL! the Release !)
so, I use many 4.4.2 roms with maliV2 inside, on 2nd rom, dualbooting NeatRom 4.1.2 on 1rst rom :)

Many 4.4.2 roms gave me Antutu results > 13000 with ,even we all know benchs dont say significants things :)

and rom usual to be stable seems to be still stable with mali downgrade :)

thanks.
 
  • Like
Reactions: vagaerg
V

vagaerg

Senior Member
Oct 31, 2009
81
11
27
Glasgow
www.estonoentraenelexamen.com
Troubadour666 said:
I use for now DorimanX kernel 8.43v99.4.test (LOL! the Release !)
so, I use many 4.4.2 roms with maliV2 inside, on 2nd rom, dualbooting NeatRom 4.1.2 on 1rst rom :)

Many 4.4.2 roms gave me Antutu results > 13000 with ,even we all know benchs dont say significants things :)

and rom usual to be stable seems to be still stable with mali downgrade :)

thanks.
Click to expand...
Click to collapse

Great! Will downgrade it then. Thank you very much ;)
 
  • Like
Reactions: Troubadour666
Troubadour666

Troubadour666

Inactive Recognized Contributor
Aug 3, 2012
3,140
7,035
43.7031 - 7.2661
  • Like
Reactions: vagaerg and Greg77970
K

Klaus20

Senior Member
Nov 20, 2013
394
63
Hi Troubadour666,
I tryed to fix my 2ndRom Neat 3.6 (Toggles are not well working) and made following:
1. WIPE 2nd Rom data/cache
2. WIPE 2nd Rom dalvin-cache
3. install zip to 2nd ROM from internal SD (
I prepared the orginal Neat 3. Zip with following:
copy folder : /system/lib/egl/*.* to rom3.6.zip : /system/lib/egl/*.*
changing boot.img in ZIP with zImage from kernel zip v76
I hope this is the way as you told me once ??
I get following messages:
Finding update package ..
Opening Update package ..
Warning: No file contens =====

Backing up EFS
Installing system ..
Symlinks and permissions ..
set_metadata_recursive: some changes failed
E:\Error in /emmc/ path .........
(Status 7)
Installation aborted

Can you help me once again ??

Regards Klaus

P.S: Now I get also an error while restoring Error while formatting /sd-ext !
 
Last edited:
  • Like
Reactions: marjune23
Troubadour666

Troubadour666

Inactive Recognized Contributor
Aug 3, 2012
3,140
7,035
43.7031 - 7.2661
Klaus20 said:
Hi Troubadour666,
I tryed to fix my 2ndRom Neat 3.6 (Toggles are not well working) and made following:
1. WIPE 2nd Rom data/cache
2. WIPE 2nd Rom dalvin-cache
3. install zip to 2nd ROM from internal SD (
I prepared the orginal Neat 3. Zip with following:
copy folder : /system/lib/egl/*.* to rom3.6.zip : /system/lib/egl/*.*
changing boot.img in ZIP with zImage from kernel zip v76
I hope this is the way as you told me once ??
I get following messages:
Finding update package ..
Opening Update package ..
Warning: No file contens =====

Backing up EFS
Installing system ..
Symlinks and permissions ..
set_metadata_recursive: some changes failed
E:\Error in /emmc/ path .........
(Status 7)
Installation aborted

Can you help me once again ??

Regards Klaus

P.S: Now I get also an error while restoring Error while formatting /sd-ext !
Click to expand...
Click to collapse

Kernel recovery ? stanTRC ?
and have you change libMali.so in AOSP.ZIP/system/lib/ too?

about error, set_metadata_recursive command only work with new stanTRC recovery with DorimanX 8.43vXX (XX>= 91 or 92 dont remember).

if you want to use "stable" release as well as 8.43v76 to flash 4.4.2 rom, if we can say 'stable' for a build test kernel , you have to change some lines in updater-script, be aware about patches i post somewhere which use set_perm commands.

i use for now

http://dorimanx.casoncia.org/V8-Tes...9.4-test-[22-38]-[21-03]-JB-SGII-PWR-CORE.zip

to dualboot 4.1.2/4.4.2 roms without updater-script modification. Some releases with stanTRC new recovery have some trouble while formatting, restoring....its why i ask you version you are using actualy to "play" on 2nd rom.

thanks
 
  • Like
Reactions: marjune23
K

Klaus20

Senior Member
Nov 20, 2013
394
63
Thanks for your quick answer .

Troubadour666 said:
Kernel recovery ? stanTRC ?
Click to expand...
Click to collapse
Can you tell me something about ??

and have you change libMali.so in AOSP.ZIP/system/lib/ too?
Click to expand...
Click to collapse
Yes
about error, set_metadata_recursive command only work with new stanTRC recovery with DorimanX 8.43vXX (XX>= 91 or 92 dont remember).
Click to expand...
Click to collapse
if you want to use "stable" release as well as 8.43v76 to flash 4.4.2 rom, if we can say 'stable' for a build test kernel , you have to change some lines in updater-script, be aware about patches i post somewhere which use set_perm commands.
Click to expand...
Click to collapse
???

i use for now
http://dorimanx.casoncia.org/V8-Tes...9.4-test-[22-38]-[21-03]-JB-SGII-PWR-CORE.zip
Click to expand...
Click to collapse
your link is not working anymore -I try this one
http://dorimanx.casoncia.org/V8/Kernel_Dorimanx-V8.43v99.1-Comp-[13-43]-[24-03]-JB-SGII-PWR-CORE.zip

It is working now - you are still the greatest !!

Regards Klaus
 
  • Like
Reactions: marjune23 and Troubadour666
Troubadour666

Troubadour666

Inactive Recognized Contributor
Aug 3, 2012
3,140
7,035
43.7031 - 7.2661
  • Like
Reactions: marjune23
A

areynoldsnz

Senior Member
Mar 30, 2011
75
9
Christchurch
Hi there,

I am trying to follow your setup but had a bootloop with NeatRom v5.6 with Kernel_Dorimanx-V8.43v98-[19-24]-[15-03]-JB-SGII-PWR-CORE.zip

Which exact version are you using please? I am going to try:

Kernel_Dorimanx-V8.43v76-cybernetus-[00-02]-[17-02]-JB-SGII-PWR-CORE.zip
or
Kernel_Dorimanx-V8.43v64-cybernetus-[15-56]-[20-01]-JB-SGII-PWR-CORE.zip

or do I need to use Kernel_Dorimanx-V8.43v99.4-test?

What are the steps I would use if I use Kernel_Dorimanx-V8.43v99.4-test? Could you please help with the basic steps?

Cheers
 
Last edited:
You must log in or register to reply here.

Similar threads

Intratech
[ROMS]Official i9100 carrier branded firmware download for Odin Flash
Replies
1K
Views
1M
X
Xander20190
Guitarfreak26
Post your desktop!!
Replies
11K
Views
3M
Z
zhudm66
Crussader
[THEME|AROMA][4.1.2 / 4.0.4] JB/ICS Style Reloaded - [ 26/Dec - KitKat Patch :( ] -
Replies
4K
Views
744K
xn0live
xn0live
O
[KERNEL] Insecure Kernels for use with rooting
Replies
611
Views
1M
R
rkreza
Luba25
  • Locked
A few more wallpapers - GS 2 [WALLPAPER LADY] will be posting everyday
Replies
6K
Views
819K
misulik79
misulik79

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 19
    Troubadour666
    Troubadour666
    Please , if you want to know the dualboot 4.1.2/4.4.2 method, go directly here , check post relative to ERROR STATUS 7....


    ALL USE OF THIS IS AT YOUR OWN RISK

    NO TROUBLE TO BACKUP PRELOAD PARTITION readHERE,
    BACKUP/RESTORE IN RECOVERY MOD ARE REALY SAFE WITH THIS METHOD OF USING ROM BECAUSE ONLY SYSTEM AND DATA PARTITION ARE USE BY DORIMANX V8.XX and CWM doesnt know PRELOAD partition.



    Hi to all.

    You know i want to run all JB 4.1.2 ROM i found in 2nd ROM and for that i only use @dorimanx any version 8.XX kernel.
    The only way i found for that is to bypass the use of PRELOAD partition in ZIP of ROMs i test and fortunaly V8.xx permit that sort of managment rom.
    I want to give here all necessary tweaks for ppl who want to test that if interested.

    I see now that we can have multiple combinations with any ROM in Dual-Boot ppl signature .

    1rst rom : NeatROM, Biftor, VIVEK and many other JB SAMMY 4.1.2
    2nd rom : Rootbox or Resurrection Remix or CM10.X

    1rst rom : Rootbox or Resurrection Remix or CM10.X
    2nd rom : NeatROM, Biftor, VIVEK and many other JB SAMMY 4.1.2

    1rst rom : Rootbox or Resurrection Remix or CM10.X
    2rst rom : Rootbox or Resurrection Remix or CM10.X

    1rs rom : NeatROM, Biftor, VIVEK and many other JB SAMMY 4.1.2
    2nd rom : NeatROM, Biftor, VIVEK and many other JB SAMMY 4.1.2

    prerequis tools :
    WINRAR to manipulate ZIP ROM and other ZIP
    DORIMANX KERNEL any V8.XX downloaded here to replace kernel if you want to DualBoot
    Notepad ++ to edit script files


    In all case of flashing a 2nd rom, if it's your 1rst use, you have to flash DorimanX kernel V8.xx 1rst stage before continuing. i cant explain here all the steps to change your kernel in I9100, and how to use recovery mode to initiate 2nd ROM space for your DualBoot, many threads for that. thanks.

    So, when you flash a ZIP ROM in 2nd position, you have to reflash DorimanX kernel immedialty after to validate run of new 2nd rom you went to flash.
    This take many manipulation and the day i began to "thread" for 2nd ROM use on XDA forum, i decided to provide updater-script for 2nd ROM without keeping lines relevant to kernel and modem flash.

    Today, as i want to make an universal I9100 updater-script for 1rst rom and 2nd rom without the use of PRELOAD partition with DorimanX V8.xx, and without modify the structure of the ZIP ROM,
    i decided to keep the relevant lines to kernel flash, and change kernel image in ZIP ROM by zImage (renamed boot.img sometimes) extrated from DorimanX kernel ZIP, before my flash, in 1rst rom or 2nd rom, even in a ROOTBOX ZIP, CM10.1 ...

    For this universal updater-script, i have to make the choise about the modem too, but i think relevante lines to modem can be deleted or kept, depend of user :)

    You can delete relevant lines to Modem because you already have a rom in use which have a modem, in 1rst rom or 2nd rom.

    I repeat, only if you plan to flash on 1rst position, you have to keep the relevant lines to kernel but not necessary those concern by Modem flash (red lines)
    if you plan to flash in 2nd rom, relevant lines to kernel and modem can be deleted.
    Sometimes, you find rom that doesnt flash any modem because DEV provider supose you already have one and doesnt impose one during flash, and he gives you the choise of modem to flash in its thread.

    With the tweaks i give here, anybody can keep or delete the relevant lines to modem (and kernel, why not, only if flash will concern 2nd rom)

    generaly, this kernel and modem relevant lines are located the end of updater-script, see some sample :

    Base on ROOTBOX ROM No MODEM
    Code: 
    [COLOR="Green"][B]package_extract_file("system/bin/backuptool.sh", "/tmp/backuptool.sh");
package_extract_file("system/bin/backuptool.functions", "/tmp/backuptool.functions");
set_perm(0, 0, 0777, "/tmp/backuptool.sh");
set_perm(0, 0, 0644, "/tmp/backuptool.functions");
run_program("/tmp/backuptool.sh", "restore");
delete("/system/bin/backuptool.sh");
delete("/system/bin/backuptool.functions");[/B][/COLOR]
show_progress(0.200000, 10);
[COLOR="Red"][B]assert(package_extract_file("boot.img", "/tmp/boot.img"),
       write_raw_image("/tmp/boot.img", "/dev/block/mmcblk0p5"),
       delete("/tmp/boot.img"));[/B][/COLOR]

    RESURRECTION REMIX ROM No MODEM
    Code: 
    [COLOR="Red"][B]assert(package_extract_file("boot.img", "/tmp/boot.img"),
       write_raw_image("/tmp/boot.img", "/dev/block/mmcblk0p5"),
       delete("/tmp/boot.img"));[/B][/COLOR]
    Base on CM10.2 ROM (10.1 too) No MODEM
    Code: 
    [COLOR="Green"][B]package_extract_file("system/bin/backuptool.sh", "/tmp/backuptool.sh");
package_extract_file("system/bin/backuptool.functions", "/tmp/backuptool.functions");
set_perm(0, 0, 0777, "/tmp/backuptool.sh");
set_perm(0, 0, 0644, "/tmp/backuptool.functions");
run_program("/tmp/backuptool.sh", "restore");
delete("/system/bin/backuptool.sh");
delete("/system/bin/backuptool.functions");[/B][/COLOR]
show_progress(0.200000, 10);
[COLOR="Red"][B]assert(package_extract_file("boot.img", "/tmp/boot.img"),
       write_raw_image("/tmp/boot.img", "/dev/block/mmcblk0p5"),
       delete("/tmp/boot.img"));[/B][/COLOR]

    NeatRom Lite V4.8
    Code: 
    [COLOR="Green"][B]ui_print("Backing up EFS");
package_extract_file("Sale/efs_backup.sh", "/tmp/efs_backup.sh");
set_perm(0, 0, 0755, "/tmp/efs_backup.sh");
run_program("/tmp/efs_backup.sh");[/B][/COLOR]
[COLOR="Red"][B]ui_print("Flashing kernel ...");
package_extract_file("Sale/flash_image", "/tmp/flash_image");
set_perm(0, 0, 0777, "/tmp/flash_image");
assert(package_extract_file("Sale/zImage", "/tmp/zImage"),
       run_program("/tmp/flash_image", "/dev/block/mmcblk0p5", "/tmp/zImage"),
       delete("/tmp/zImage"));[/B][/COLOR]
[COLOR="Blue"][B]ui_print("Flashing modem ...");
assert(package_extract_file("Sale/modem.bin", "/tmp/modem.bin"),
       run_program("/tmp/flash_image", "/dev/block/mmcblk0p8", "/tmp/modem.bin"),
       delete("/tmp/modem.bin"));[/COLOR]
[COLOR="Red"]delete("/tmp/flash_image");[/B][/COLOR]
delete("/tmp/symlink_preload");
[COLOR="Green"][B]delete("/tmp/efs_backup.sh");[/B][/COLOR]

    BIFTOR V11 ROM
    Code: 
    [COLOR="Green"][B]ui_print("Backing up EFS");
package_extract_file("Biftor/efs_backup.sh", "/tmp/efs_backup.sh");
set_perm(0, 0, 0755, "/tmp/efs_backup.sh");
run_program("/tmp/efs_backup.sh");[/B][/COLOR]
[COLOR="Red"][B]ui_print("Flashing kernel ...");
package_extract_file("Biftor/flash_image", "/tmp/flash_image");
set_perm(0, 0, 0777, "/tmp/flash_image");
assert(package_extract_file("Biftor/zImage", "/tmp/zImage"),
       run_program("/tmp/flash_image", "/dev/block/mmcblk0p5", "/tmp/zImage"),
       delete("/tmp/zImage"));[/B][/COLOR]
[COLOR="Blue"][B]ui_print("Flashing modem ...");
assert(package_extract_file("Biftor/modem.bin", "/tmp/modem.bin"),
       run_program("/tmp/flash_image", "/dev/block/mmcblk0p8", "/tmp/modem.bin"),
       delete("/tmp/modem.bin"));[/B][/COLOR]
delete("/tmp/symlink_preload");
[COLOR="Red"][B]delete("/tmp/flash_image");[/B][/COLOR]
[COLOR="Green"][B]delete("/tmp/efs_backup.sh");[/B][/COLOR]

    when you edit updater-script you can remove the red or blue colored block lines as you want accordingly the flash you plan, 1rst rom or 2nd rom position.
    And what you plan , always keep the colored green block of lines that concern Backing up EFS or backuptool.sh script.
    I DONT TALK HERE ABOUT LINE BEFORE OR AFTER.

    KEEP IN MIND THAT IF YOU FLASH IN 1RST ROM, YOU HAVE TO KEEP LINES RELATIVE TO KERNEL FLASH ON YOUR MODDED UPDATER-SCRIPT.

    depend of your choice, you can have to replace kernel image in ZIP ROM, how to do that ?
    how to change kernel image in ZIP ROM with another image extracted from CWM kernel flasher :

    - for DualBoot, exclusive use of DorimanX any V8.xx only. (i never have trouble with this method and have never use ODIN)
    1 - extract zImage from ZIP of DorimanX V8.xx kernel you want for your dual-boot.
    2 - open ZIP ROM with WINRAR
    2 - find kernel image in ROM ZIP opened where is located, sometimes it's named boot.img instead of zImage.
    3 - if kernel in ROM ZIP is named boot.img, rename zImage file you have extracted in step1 to boot.img
    4 - finaly WINRAR open at place where is kernel image DEV, drag and drop in your new renamed (or not) kernel image (zImage or boot.img depends of rom)

    At this step, if you never plan to flash JB SAMMY 4.1.2 stock or custom ROM on 2nd ROM, you can stop here.

    - For many jb sammy 4.1.2 rom, there is an symlink_preload file in structure of ZIP ROM (i wont explain here the reason of PRELOAD partition added by SAMSUNG).
    Originaly, this script is use during flash to simlink APKs system files from /preload/symlink/system/app folder in PRELOAD partition to /system/app/ in SYSTEM partition.
    you have to modify this file too , like i preconise because all files which are in preload folder of ZIP ROM will be installed in /data/sec_data/ folder of you rom after flash.

    BEFORE
    Code: 
    #!/system/bin/mksh
mount -o remount rw /system
cd /preload/symlink/system/app
# Can't create array with /sbin/sh, hence we use mksh
apk_list=( `ls | grep .apk` )
odex_list=( `ls | grep .odex` )
items=${apk_list[*]}" "${odex_list[*]}
for item in ${items[@]}
do
  ln -s /preload/symlink/system/app/$item /system/app/$item 
done

    AFTER
    Code: 
    #!/system/bin/mksh
mount -o remount rw /system
cd /data/sec_data
# Can't create array with /sbin/sh, hence we use mksh
apk_list=( `ls | grep .apk` )
odex_list=( `ls | grep .odex` )
items=${apk_list[*]}" "${odex_list[*]}
for item in ${items[@]}
do
  ln -s /data/sec_data/$item /system/app/$item 
done


    STAGE CONCERNING KERNEL AND MODEM AND SYMLINK_PRELOAD SCRIPT DONE and now, you know why there are some obligations in this concept.

    Have a look on some updater-script of <> type of CM10.x or 4.2.2 ROM :

    SLIM-i9100-UNOFFICIAL-SaberMod-4.9-20130720
    Code: 
    mount("ext4", "EMMC", "/dev/block/mmcblk0p9", "/system");
package_extract_dir("system/addon.d", "/system/addon.d");
package_extract_file("system/bin/backuptool.sh", "/tmp/backuptool.sh");
package_extract_file("system/bin/backuptool.functions", "/tmp/backuptool.functions");
set_perm(0, 0, 0777, "/tmp/backuptool.sh");
set_perm(0, 0, 0644, "/tmp/backuptool.functions");
run_program("/tmp/backuptool.sh", "backup");
unmount("/system");
show_progress(0.500000, 0);
ui_print("");
ui_print("");
ui_print("Slim Roms");
ui_print("");
ui_print(" www.slimroms.net  ");
ui_print("");
ui_print("");
ui_print("Format and Mount System, Mount Data...");
unmount("/system");
format("ext4", "EMMC", "/dev/block/mmcblk0p9", "0", "/system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p9", "/system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p10", "/data");
package_extract_dir("recovery", "/system");
package_extract_dir("system", "/system");
package_extract_dir("data", "/data");
    Base CM 10.x ROM
    Code: 
    assert(getprop("ro.product.device") == "galaxys2" || getprop("ro.build.product") == "galaxys2" || 
       getprop("ro.product.device") == "i9100" || getprop("ro.build.product") == "i9100" || 
       getprop("ro.product.device") == "GT-I9100" || getprop("ro.build.product") == "GT-I9100" || 
       getprop("ro.product.device") == "GT-I9100M" || getprop("ro.build.product") == "GT-I9100M" || 
       getprop("ro.product.device") == "GT-I9100P" || getprop("ro.build.product") == "GT-I9100P" || 
       getprop("ro.product.device") == "GT-I9100T" || getprop("ro.build.product") == "GT-I9100T");
mount("ext4", "EMMC", "/dev/block/mmcblk0p9", "/system");
package_extract_file("system/bin/backuptool.sh", "/tmp/backuptool.sh");
package_extract_file("system/bin/backuptool.functions", "/tmp/backuptool.functions");
set_perm(0, 0, 0777, "/tmp/backuptool.sh");
set_perm(0, 0, 0644, "/tmp/backuptool.functions");
run_program("/tmp/backuptool.sh", "backup");
unmount("/system");
show_progress(0.500000, 0);
unmount("/system");
format("ext4", "EMMC", "/dev/block/mmcblk0p9", "0", "/system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p9", "/system");
package_extract_dir("recovery", "/system");
package_extract_dir("system", "/system");
    Base RootBox ROM
    Code: 
    assert(getprop("ro.product.device") == "galaxys2" || getprop("ro.build.product") == "galaxys2" || 
       getprop("ro.product.device") == "i9100" || getprop("ro.build.product") == "i9100" || 
       getprop("ro.product.device") == "GT-I9100" || getprop("ro.build.product") == "GT-I9100" || 
       getprop("ro.product.device") == "GT-I9100M" || getprop("ro.build.product") == "GT-I9100M" || 
       getprop("ro.product.device") == "GT-I9100P" || getprop("ro.build.product") == "GT-I9100P" || 
       getprop("ro.product.device") == "GT-I9100T" || getprop("ro.build.product") == "GT-I9100T");
mount("ext4", "EMMC", "/dev/block/mmcblk0p9", "/system");
package_extract_file("system/bin/backuptool.sh", "/tmp/backuptool.sh");
package_extract_file("system/bin/backuptool.functions", "/tmp/backuptool.functions");
set_perm(0, 0, 0777, "/tmp/backuptool.sh");
set_perm(0, 0, 0644, "/tmp/backuptool.functions");
run_program("/tmp/backuptool.sh", "backup");
unmount("/system");
show_progress(0.500000, 0);
unmount("/system");
format("ext4", "EMMC", "/dev/block/mmcblk0p9", "0", "/system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p9", "/system");
package_extract_dir("recovery", "/system");
package_extract_dir("system", "/system");
    RESURRECTION REMIX
    Code: 
    assert(getprop("ro.product.device") == "galaxys2" || getprop("ro.build.product") == "galaxys2" || 
       getprop("ro.product.device") == "i9100" || getprop("ro.build.product") == "i9100" || 
       getprop("ro.product.device") == "GT-I9100" || getprop("ro.build.product") == "GT-I9100" || 
       getprop("ro.product.device") == "GT-I9100M" || getprop("ro.build.product") == "GT-I9100M" || 
       getprop("ro.product.device") == "GT-I9100P" || getprop("ro.build.product") == "GT-I9100P" || 
       getprop("ro.product.device") == "GT-I9100T" || getprop("ro.build.product") == "GT-I9100T");
show_progress(0.500000, 0);
unmount("/system");
format("ext4", "EMMC", "/dev/block/mmcblk0p9", "0", "/system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p9", "/system");
package_extract_dir("recovery", "/system");
package_extract_dir("system", "/system");
    As you can see, these type of ROMs dont manage PRELOAD partition but all FORMAT SYSTEM PARTITION BEFORE FLASH, it's mostly the case on Nighty ROMs , so, nothing to modify for them, change image kernel inside ZIP ROM by DorimanX V8.xx as i explain and flash, in 1rst rom or 2nd ROM if it exist. Dont forget to wipe data if necessary, depends which rom you come from.

    Let's see updater-script from 4.1.2 JB SAMMY ROM :

    NEATROM LITE 4.8
    Code: 
    unmount("/system");
unmount("/cache");
[COLOR="Red"][B]unmount("/preload");[/B][/COLOR]
run_program("/sbin/mount", "/dev/block/mmcblk0p9", "/system");
run_program("/sbin/mount", "/dev/block/mmcblk0p10", "/data");
run_program("/sbin/mount", "/dev/block/mmcblk0p7", "/cache");
[COLOR="Red"][B]run_program("/sbin/mount", "/dev/block/mmcblk0p12", "/preload");[/B][/COLOR]
delete_recursive("/system");
delete_recursive("/cache");
delete_recursive("/data/dalvik-cache");
[COLOR="Red"][B]delete_recursive("/preload");[/B][/COLOR]
delete("/data/system/batterystats.bin");
package_extract_dir("data", "/data");
set_perm(2000, 2000, 0771, "/data/local");
set_perm_recursive(1000, 1000, 0771, 0644, "/data/app");
ui_print("Installing system ...");
show_progress(0.500000, 80);
package_extract_dir("system", "/system");
[COLOR="Red"][B]package_extract_dir("preload", "/preload");[/B][/COLOR]

    Biftor V11
    Code: 
    unmount("/system");
unmount("/cache");
[COLOR="Red"][B]unmount("/preload");[/B][/COLOR]
ui_print("mounting...");
ui_print("mount System");
run_program("/sbin/mount", "/dev/block/mmcblk0p9", "/system");
ui_print("mount data");
run_program("/sbin/mount", "/dev/block/mmcblk0p10", "/data");
ui_print("mount cache");
run_program("/sbin/mount", "/dev/block/mmcblk0p7", "/cache");
[COLOR="Red"][B]ui_print("mount preload");
run_program("/sbin/mount", "/dev/block/mmcblk0p12", "/preload");[/B][/COLOR]
delete_recursive("/system");
delete_recursive("/cache");
delete_recursive("/data/dalvik-cache");
[COLOR="Red"][B]delete_recursive("/preload");[/B][/COLOR]
[COLOR="Green"][B]delete_recursive("/data/data/com.android.providers.settings");
delete_recursive("/data/data/com.android.settings");
delete_recursive("/data/data/com.android.SystemUI");[/B][/COLOR]
delete("/data/system/batterystats.bin");
package_extract_dir("data", "/data");
set_perm(2000, 2000, 0771, "/data/local");
set_perm_recursive(1000, 1000, 0771, 0644, "/data/app");
ui_print("Installing system ...");
show_progress(0.500000, 80);
package_extract_dir("system", "/system");
[COLOR="Red"][B]package_extract_dir("preload", "/preload");[/B][/COLOR]

    In this type of ROMs, no format of system, simply some delete_recursive and extract command .

    because we are in recovery during flash and we have DorimanX kernel installed,
    - we can delete relevant lines to mount and unmount preload partition. (in red)
    - as we plan to switch preload extracted folder destination to /data/sec_data/ folder in rom. (in red)

    we have to change red lines like that :

    if we came from another JB 4.1.2 2nd ROM, without wipping data, if not, write it anyway, you can have to reflash rom.

    delete_recursive("/preload"); must be replaced by delete_recursive("/data/sec_data");

    and in all cases

    package_extract_dir("preload", "/preload"); must be replaced by package_extract_dir("preload/symlink/system/app", "/data/sec_data");

    the green lines are relevant from DEV, sometimes more but can be useful and you can add some more.

    delete_recursive("/data/data/com.android.providers.settings");
    delete_recursive("/data/data/com.android.settings");
    delete_recursive("/data/data/com.android.SystemUI");

    personaly i add this block of lines to flash my Best Biftor 2nd ROM :

    delete_recursive("/data/data/com.android.vending");
    delete_recursive("/data/data/com.android.providers.downloads");
    delete_recursive("/data/data/com.google.android.gsf");
    delete_recursive("/data/data/com.Biftor.Biftorteam");
    delete_recursive("/data/data/com.Biftor.Biftorteam.NavBar");
    delete_recursive("/data/data/com.Biftor.BiftorTeamAppRestart");
    delete_recursive("/data/data/com.Biftor.Biftorteamstatusbar");

    Finaly, the two sample modified here, personaly mine :

    NEATROM LITE 4.8 ROM
    Code: 
    unmount("/system");
unmount("/cache");
run_program("/sbin/mount", "/dev/block/mmcblk0p9", "/system");
run_program("/sbin/mount", "/dev/block/mmcblk0p10", "/data");
run_program("/sbin/mount", "/dev/block/mmcblk0p7", "/cache");
delete_recursive("/system");
delete_recursive("/cache");
delete_recursive("/data/dalvik-cache");
delete_recursive("/data/sec_data");
delete_recursive("/data/data/com.android.providers.settings");
delete_recursive("/data/data/com.android.settings");
delete_recursive("/data/data/com.android.SystemUI");
delete_recursive("/data/data/com.android.vending");
delete_recursive("/data/data/com.android.providers.downloads");
delete_recursive("/data/data/com.google.android.gsf");
delete_recursive("/data/data/com.Biftor.Biftorteam");
delete_recursive("/data/data/com.Biftor.Biftorteam.NavBar");
delete_recursive("/data/data/com.Biftor.BiftorTeamAppRestart");
delete_recursive("/data/data/com.Biftor.Biftorteamstatusbar");
delete("/data/system/batterystats.bin");
package_extract_dir("data", "/data");
set_perm(2000, 2000, 0771, "/data/local");
set_perm_recursive(1000, 1000, 0771, 0644, "/data/app");
ui_print("Installing system ...");
show_progress(0.500000, 80);
package_extract_dir("system", "/system");
package_extract_dir("preload/symlink/system/app", "/data/sec_data");


    Biftor V11 ROM
    Code: 
    unmount("/system");
unmount("/cache");
ui_print("mounting...");
ui_print("mount System");
run_program("/sbin/mount", "/dev/block/mmcblk0p9", "/system");
ui_print("mount data");
run_program("/sbin/mount", "/dev/block/mmcblk0p10", "/data");
ui_print("mount cache");
run_program("/sbin/mount", "/dev/block/mmcblk0p7", "/cache");
delete_recursive("/system");
delete_recursive("/cache");
delete_recursive("/data/dalvik-cache");
delete_recursive("/data/sec_data");
delete_recursive("/data/data/com.android.providers.settings");
delete_recursive("/data/data/com.android.settings");
delete_recursive("/data/data/com.android.SystemUI");
delete_recursive("/data/data/com.android.vending");
delete_recursive("/data/data/com.android.providers.downloads");
delete_recursive("/data/data/com.google.android.gsf");
delete_recursive("/data/data/com.Biftor.Biftorteam");
delete_recursive("/data/data/com.Biftor.Biftorteam.NavBar");
delete_recursive("/data/data/com.Biftor.BiftorTeamAppRestart");
delete_recursive("/data/data/com.Biftor.Biftorteamstatusbar");
delete("/data/system/batterystats.bin");
package_extract_dir("data", "/data");
set_perm(2000, 2000, 0771, "/data/local");
set_perm_recursive(1000, 1000, 0771, 0644, "/data/app");
ui_print("Installing system ...");
show_progress(0.500000, 80);
package_extract_dir("system", "/system");
package_extract_dir("preload/symlink/system/app", "/data/sec_data");
    View
    13
    Troubadour666
    Troubadour666
    Final PURPOSE of updater-script for Biftor V11

    For my personal use, i have make some choices i expose you to flash NEW Biftor V11 in my 2nd ROM :
    In /Biftor/ folder of ZIP ROM :
    I replace zImage extracted from http://dorimanx.shine.sk/kernels-jb...nx-V8.35-[18-00]-[16-07]-JB-SGII-PWR-CORE.zip.
    I replace symlink_preload file by one with script i detail at top of post
    with this updater-script i have only 2 apks in /system/app/ : SuperSU.apk and STweaks.apk
    SYSTEM partition is 458 MB large
    /DATA/SEC_DATA/ folder is 222MB large with 141 apks system and placeholder file :) , all are symlinked in /system/app/ except placeholder file.

    copy it in a text file opened in Notepad++ and compare it to original from Biftor to see the differences i mean.

    Code: 
    show_progress(0.500000, 0);
ui_print("");
ui_print("");
ui_print("!..............................................!");
ui_print("!.........Welcome To Biftor Rom V11 JB..........!");
ui_print("!.........Welcome To Biftor Rom V11 JB..........!");
ui_print("!.........Welcome To Biftor Rom V11 JB..........!");
ui_print("!.........Welcome To Biftor Rom V11 JB..........!");
ui_print("!.........Welcome To Biftor Rom V11 JB..........!");
ui_print("!.........Welcome To Biftor Rom V11 JB..........!");
ui_print("!.........Welcome To Biftor Rom V11 JB..........!");
ui_print("!..............................................!");
ui_print("A       R        M       I       N");
ui_print("AA       RR       MM       II       NN");
ui_print("AAA       RRR       MMM       III       NNN");
ui_print("AAAA       RRRR       MMMM       IIII       NNNN");
unmount("/system");
unmount("/cache");
ui_print("mounting...");
ui_print("mount System");
run_program("/sbin/mount", "/dev/block/mmcblk0p9", "/system");
ui_print("mount data");
run_program("/sbin/mount", "/dev/block/mmcblk0p10", "/data");
ui_print("mount cache");
run_program("/sbin/mount", "/dev/block/mmcblk0p7", "/cache");
delete_recursive("/system");
delete_recursive("/cache");
delete_recursive("/data/dalvik-cache");
[COLOR="Red"][B]delete_recursive("/data/sec_data");[/B][/COLOR]
delete_recursive("/data/data/com.android.providers.settings");
delete_recursive("/data/data/com.android.settings");
delete_recursive("/data/data/com.android.SystemUI");
[COLOR="Red"][B]delete_recursive("/data/data/com.android.vending");
delete_recursive("/data/data/com.android.providers.downloads");
delete_recursive("/data/data/com.google.android.gsf");
delete_recursive("/data/data/com.Biftor.Biftorteam");
delete_recursive("/data/data/com.Biftor.Biftorteam.NavBar");
delete_recursive("/data/data/com.Biftor.BiftorTeamAppRestart");
delete_recursive("/data/data/com.Biftor.Biftorteamstatusbar");[/B][/COLOR]
delete("/data/system/batterystats.bin");
ui_print("Installing system ...");
show_progress(0.500000, 80);
package_extract_dir("data/app", "/data/sec_data");
package_extract_dir("data/Biftor-Tweaks", "/data/Biftor-Tweaks");
package_extract_dir("system", "/system");
[COLOR="Red"][B]delete_recursive("/system/app");
package_extract_dir("system/media/video/shutdown", "/system/app");
package_extract_file("system/app/Superuser.apk", "/system/app/Superuser.apk");
delete("/system/app/shutdown.qmg");
package_extract_dir("system/app", "/data/sec_data");
delete("/data/sec_data/Superuser.apk");[/B][/COLOR]
package_extract_dir("preload/symlink/system/app", "/data/sec_data");
set_perm(2000, 2000, 0771, "/data/local");
set_perm_recursive(1000, 1000, 0771, 0644, "/data/app");
set_perm(0, 1000, 0755, "/system/xbin/busybox");
run_program("/system/xbin/busybox", "--install", "-s", "/system/xbin");
symlink("/system/xbin/busybox", "/system/bin/busybox");
ui_print("Simlinking ...");
symlink("Roboto-Regular.ttf", "/system/fonts/DroidSans.ttf");
symlink("Roboto-Bold.ttf", "/system/fonts/DroidSans-Bold.ttf");
symlink("busybox", "/system/xbin/[");
symlink("busybox", "/system/xbin/[[");
symlink("busybox", "/system/xbin/acpid");
symlink("busybox", "/system/xbin/addgroup");
symlink("busybox", "/system/xbin/adduser");
symlink("busybox", "/system/xbin/adjtimex");
symlink("busybox", "/system/xbin/ar");
symlink("busybox", "/system/xbin/arp");
symlink("busybox", "/system/xbin/arping");
symlink("busybox", "/system/xbin/ash");
symlink("busybox", "/system/xbin/awk");
symlink("busybox", "/system/xbin/basename");
symlink("busybox", "/system/xbin/bbconfig");
symlink("busybox", "/system/xbin/beep");
symlink("busybox", "/system/xbin/blkid");
symlink("busybox", "/system/xbin/bootchartd");
symlink("busybox", "/system/xbin/brctl");
symlink("busybox", "/system/xbin/bunzip2");
symlink("busybox", "/system/xbin/bzcat");
symlink("busybox", "/system/xbin/bzip2");
symlink("busybox", "/system/xbin/cal");
symlink("busybox", "/system/xbin/catv");
symlink("busybox", "/system/xbin/chat");
symlink("busybox", "/system/xbin/chattr");
symlink("busybox", "/system/xbin/chgrp");
symlink("busybox", "/system/xbin/chpasswd");
symlink("busybox", "/system/xbin/chpst");
symlink("busybox", "/system/xbin/chroot");
symlink("busybox", "/system/xbin/chrt");
symlink("busybox", "/system/xbin/chvt");
symlink("busybox", "/system/xbin/cksum");
symlink("busybox", "/system/xbin/clear");
symlink("busybox", "/system/xbin/comm");
symlink("busybox", "/system/xbin/conspy");
symlink("busybox", "/system/xbin/cp");
symlink("busybox", "/system/xbin/cpio");
symlink("busybox", "/system/xbin/crond");
symlink("busybox", "/system/xbin/crontab");
symlink("busybox", "/system/xbin/cryptpw");
symlink("busybox", "/system/xbin/cttyhack");
symlink("busybox", "/system/xbin/cut");
symlink("busybox", "/system/xbin/dc");
symlink("busybox", "/system/xbin/deallocvt");
symlink("busybox", "/system/xbin/delgroup");
symlink("busybox", "/system/xbin/deluser");
symlink("busybox", "/system/xbin/depmod");
symlink("busybox", "/system/xbin/devmem");
symlink("busybox", "/system/xbin/dhcprelay");
symlink("busybox", "/system/xbin/diff");
symlink("busybox", "/system/xbin/dirname");
symlink("busybox", "/system/xbin/dnsd");
symlink("busybox", "/system/xbin/dnsdomainname");
symlink("busybox", "/system/xbin/dos2unix");
symlink("busybox", "/system/xbin/dpkg");
symlink("busybox", "/system/xbin/dpkg-deb");
symlink("busybox", "/system/xbin/du");
symlink("busybox", "/system/xbin/dumpkmap");
symlink("busybox", "/system/xbin/dumpleases");
symlink("busybox", "/system/xbin/echo");
symlink("busybox", "/system/xbin/ed");
symlink("busybox", "/system/xbin/egrep");
symlink("busybox", "/system/xbin/eject");
symlink("busybox", "/system/xbin/env");
symlink("busybox", "/system/xbin/envdir");
symlink("busybox", "/system/xbin/envuidgid");
symlink("busybox", "/system/xbin/ether-wake");
symlink("busybox", "/system/xbin/expand");
symlink("busybox", "/system/xbin/expr");
symlink("busybox", "/system/xbin/fakeidentd");
symlink("busybox", "/system/xbin/false");
symlink("busybox", "/system/xbin/fbset");
symlink("busybox", "/system/xbin/fbsplash");
symlink("busybox", "/system/xbin/fdflush");
symlink("busybox", "/system/xbin/fdformat");
symlink("busybox", "/system/xbin/fdisk");
symlink("busybox", "/system/xbin/fgconsole");
symlink("busybox", "/system/xbin/fgrep");
symlink("busybox", "/system/xbin/find");
symlink("busybox", "/system/xbin/findfs");
symlink("busybox", "/system/xbin/flash_eraseall");
symlink("busybox", "/system/xbin/flash_lock");
symlink("busybox", "/system/xbin/flash_unlock");
symlink("busybox", "/system/xbin/flashcp");
symlink("busybox", "/system/xbin/flock");
symlink("busybox", "/system/xbin/fold");
symlink("busybox", "/system/xbin/free");
symlink("busybox", "/system/xbin/freeramdisk");
symlink("busybox", "/system/xbin/fsck");
symlink("busybox", "/system/xbin/fsck.minix");
symlink("busybox", "/system/xbin/fsync");
symlink("busybox", "/system/xbin/ftpd");
symlink("busybox", "/system/xbin/ftpget");
symlink("busybox", "/system/xbin/ftpput");
symlink("busybox", "/system/xbin/fuser");
symlink("busybox", "/system/xbin/getopt");
symlink("busybox", "/system/xbin/getty");
symlink("busybox", "/system/xbin/grep");
symlink("busybox", "/system/xbin/gunzip");
symlink("busybox", "/system/xbin/halt");
symlink("busybox", "/system/xbin/hdparm");
symlink("busybox", "/system/xbin/head");
symlink("busybox", "/system/xbin/hexdump");
symlink("busybox", "/system/xbin/hostid");
symlink("busybox", "/system/xbin/hostname");
symlink("busybox", "/system/xbin/httpd");
symlink("busybox", "/system/xbin/hush");
symlink("busybox", "/system/xbin/hwclock");
symlink("busybox", "/system/xbin/ifdown");
symlink("busybox", "/system/xbin/ifenslave");
symlink("busybox", "/system/xbin/ifplugd");
symlink("busybox", "/system/xbin/ifup");
symlink("busybox", "/system/xbin/inetd");
symlink("busybox", "/system/xbin/init");
symlink("busybox", "/system/xbin/inotifyd");
symlink("busybox", "/system/xbin/install");
symlink("busybox", "/system/xbin/ipaddr");
symlink("busybox", "/system/xbin/ipcalc");
symlink("busybox", "/system/xbin/ipcrm");
symlink("busybox", "/system/xbin/ipcs");
symlink("busybox", "/system/xbin/iplink");
symlink("busybox", "/system/xbin/iproute");
symlink("busybox", "/system/xbin/iprule");
symlink("busybox", "/system/xbin/iptunnel");
symlink("busybox", "/system/xbin/kbd_mode");
symlink("busybox", "/system/xbin/killall");
symlink("busybox", "/system/xbin/killall5");
symlink("busybox", "/system/xbin/klogd");
symlink("busybox", "/system/xbin/last");
symlink("busybox", "/system/xbin/length");
symlink("busybox", "/system/xbin/less");
symlink("busybox", "/system/xbin/linux32");
symlink("busybox", "/system/xbin/linux64");
symlink("busybox", "/system/xbin/linuxrc");
symlink("busybox", "/system/xbin/loadfont");
symlink("busybox", "/system/xbin/loadkmap");
symlink("busybox", "/system/xbin/logger");
symlink("busybox", "/system/xbin/login");
symlink("busybox", "/system/xbin/logname");
symlink("busybox", "/system/xbin/logread");
symlink("busybox", "/system/xbin/losetup");
symlink("busybox", "/system/xbin/lpd");
symlink("busybox", "/system/xbin/lpq");
symlink("busybox", "/system/xbin/lpr");
symlink("busybox", "/system/xbin/lsattr");
symlink("busybox", "/system/xbin/lspci");
symlink("busybox", "/system/xbin/lsusb");
symlink("busybox", "/system/xbin/lzcat");
symlink("busybox", "/system/xbin/lzma");
symlink("busybox", "/system/xbin/lzop");
symlink("busybox", "/system/xbin/lzopcat");
symlink("busybox", "/system/xbin/makedevs");
symlink("busybox", "/system/xbin/makemime");
symlink("busybox", "/system/xbin/man");
symlink("busybox", "/system/xbin/md5sum");
symlink("busybox", "/system/xbin/mdev");
symlink("busybox", "/system/xbin/mesg");
symlink("busybox", "/system/xbin/microcom");
symlink("busybox", "/system/xbin/mkdosfs");
symlink("busybox", "/system/xbin/mke2fs");
symlink("busybox", "/system/xbin/mkfifo");
symlink("busybox", "/system/xbin/mkfs.ext2");
symlink("busybox", "/system/xbin/mkfs.minix");
symlink("busybox", "/system/xbin/mkfs.reiser");
symlink("busybox", "/system/xbin/mkfs.vfat");
symlink("busybox", "/system/xbin/mknod");
symlink("busybox", "/system/xbin/mkpasswd");
symlink("busybox", "/system/xbin/mkswap");
symlink("busybox", "/system/xbin/mktemp");
symlink("busybox", "/system/xbin/modinfo");
symlink("busybox", "/system/xbin/modprobe");
symlink("busybox", "/system/xbin/more");
symlink("busybox", "/system/xbin/mountpoint");
symlink("busybox", "/system/xbin/mt");
symlink("busybox", "/system/xbin/nameif");
symlink("busybox", "/system/xbin/nc");
symlink("busybox", "/system/xbin/nice");
symlink("busybox", "/system/xbin/nmeter");
symlink("busybox", "/system/xbin/nohup");
symlink("busybox", "/system/xbin/nslookup");
symlink("busybox", "/system/xbin/ntpd");
symlink("busybox", "/system/xbin/od");
symlink("busybox", "/system/xbin/openvt");
symlink("busybox", "/system/xbin/passwd");
symlink("busybox", "/system/xbin/patch");
symlink("busybox", "/system/xbin/pgrep");
symlink("busybox", "/system/xbin/pidof");
symlink("busybox", "/system/xbin/ping6");
symlink("busybox", "/system/xbin/pipe_progress");
symlink("busybox", "/system/xbin/pivot_root");
symlink("busybox", "/system/xbin/pkill");
symlink("busybox", "/system/xbin/popmaildir");
symlink("busybox", "/system/xbin/poweroff");
symlink("busybox", "/system/xbin/printf");
symlink("busybox", "/system/xbin/pscan");
symlink("busybox", "/system/xbin/pwd");
symlink("busybox", "/system/xbin/raidautorun");
symlink("busybox", "/system/xbin/rdate");
symlink("busybox", "/system/xbin/rdev");
symlink("busybox", "/system/xbin/readlink");
symlink("busybox", "/system/xbin/readprofile");
symlink("busybox", "/system/xbin/realpath");
symlink("busybox", "/system/xbin/reformime");
symlink("busybox", "/system/xbin/reset");
symlink("busybox", "/system/xbin/resize");
symlink("busybox", "/system/xbin/rev");
symlink("busybox", "/system/xbin/rpm");
symlink("busybox", "/system/xbin/rpm2cpio");
symlink("busybox", "/system/xbin/rtcwake");
symlink("busybox", "/system/xbin/run-parts");
symlink("busybox", "/system/xbin/runlevel");
symlink("busybox", "/system/xbin/runsv");
symlink("busybox", "/system/xbin/runsvdir");
symlink("busybox", "/system/xbin/rx");
symlink("busybox", "/system/xbin/script");
symlink("busybox", "/system/xbin/scriptreplay");
symlink("busybox", "/system/xbin/sed");
symlink("busybox", "/system/xbin/sendmail");
symlink("busybox", "/system/xbin/seq");
symlink("busybox", "/system/xbin/setarch");
symlink("busybox", "/system/xbin/setfont");
symlink("busybox", "/system/xbin/setkeycodes");
symlink("busybox", "/system/xbin/setlogcons");
symlink("busybox", "/system/xbin/setsid");
symlink("busybox", "/system/xbin/setuidgid");
symlink("busybox", "/system/xbin/sha1sum");
symlink("busybox", "/system/xbin/sha256sum");
symlink("busybox", "/system/xbin/sha512sum");
symlink("busybox", "/system/xbin/showkey");
symlink("busybox", "/system/xbin/slattach");
symlink("busybox", "/system/xbin/smemcap");
symlink("busybox", "/system/xbin/softlimit");
symlink("busybox", "/system/xbin/sort");
symlink("busybox", "/system/xbin/split");
symlink("busybox", "/system/xbin/start-stop-daemon");
symlink("busybox", "/system/xbin/stat");
symlink("busybox", "/system/xbin/strings");
symlink("busybox", "/system/xbin/stty");
symlink("busybox", "/system/xbin/sulogin");
symlink("busybox", "/system/xbin/sum");
symlink("busybox", "/system/xbin/sv");
symlink("busybox", "/system/xbin/svlogd");
symlink("busybox", "/system/xbin/swapoff");
symlink("busybox", "/system/xbin/swapon");
symlink("busybox", "/system/xbin/switch_root");
symlink("busybox", "/system/xbin/sysctl");
symlink("busybox", "/system/xbin/syslogd");
symlink("busybox", "/system/xbin/tac");
symlink("busybox", "/system/xbin/tail");
symlink("busybox", "/system/xbin/tar");
symlink("busybox", "/system/xbin/taskset");
symlink("busybox", "/system/xbin/tcpsvd");
symlink("busybox", "/system/xbin/tee");
symlink("busybox", "/system/xbin/telnet");
symlink("busybox", "/system/xbin/telnetd");
symlink("busybox", "/system/xbin/test");
symlink("busybox", "/system/xbin/tftp");
symlink("busybox", "/system/xbin/tftpd");
symlink("busybox", "/system/xbin/time");
symlink("busybox", "/system/xbin/timeout");
symlink("busybox", "/system/xbin/touch");
symlink("busybox", "/system/xbin/tr");
symlink("busybox", "/system/xbin/traceroute");
symlink("busybox", "/system/xbin/traceroute6");
symlink("busybox", "/system/xbin/true");
symlink("busybox", "/system/xbin/tty");
symlink("busybox", "/system/xbin/ttysize");
symlink("busybox", "/system/xbin/tunctl");
symlink("busybox", "/system/xbin/tune2fs");
symlink("busybox", "/system/xbin/ubiattach");
symlink("busybox", "/system/xbin/ubidetach");
symlink("busybox", "/system/xbin/udhcpc");
symlink("busybox", "/system/xbin/udhcpd");
symlink("busybox", "/system/xbin/udpsvd");
symlink("busybox", "/system/xbin/uname");
symlink("busybox", "/system/xbin/uncompress");
symlink("busybox", "/system/xbin/unexpand");
symlink("busybox", "/system/xbin/uniq");
symlink("busybox", "/system/xbin/unix2dos");
symlink("busybox", "/system/xbin/unlzma");
symlink("busybox", "/system/xbin/unlzop");
symlink("busybox", "/system/xbin/unxz");
symlink("busybox", "/system/xbin/unzip");
symlink("busybox", "/system/xbin/uptime");
symlink("busybox", "/system/xbin/usleep");
symlink("busybox", "/system/xbin/uudecode");
symlink("busybox", "/system/xbin/uuencode");
symlink("busybox", "/system/xbin/vconfig");
symlink("busybox", "/system/xbin/vi");
symlink("busybox", "/system/xbin/vlock");
symlink("busybox", "/system/xbin/volname");
symlink("busybox", "/system/xbin/wall");
symlink("busybox", "/system/xbin/watch");
symlink("busybox", "/system/xbin/watchdog");
symlink("busybox", "/system/xbin/wc");
symlink("busybox", "/system/xbin/wget");
symlink("busybox", "/system/xbin/which");
symlink("busybox", "/system/xbin/who");
symlink("busybox", "/system/xbin/whoami");
symlink("busybox", "/system/xbin/xargs");
symlink("busybox", "/system/xbin/xz");
symlink("busybox", "/system/xbin/xzcat");
symlink("busybox", "/system/xbin/yes");
symlink("busybox", "/system/xbin/zcat");
symlink("busybox", "/system/xbin/zcip");
symlink("dumpstate", "/system/bin/dumpcrash");
symlink("toolbox", "/system/bin/cat");
symlink("toolbox", "/system/bin/chmod");
symlink("toolbox", "/system/bin/chown");
symlink("toolbox", "/system/bin/cmp");
symlink("debuggerd", "/system/bin/csview");
symlink("toolbox", "/system/bin/date");
symlink("toolbox", "/system/bin/dd");
symlink("toolbox", "/system/bin/df");
symlink("toolbox", "/system/bin/dmesg");
symlink("toolbox", "/system/bin/getevent");
symlink("toolbox", "/system/bin/getprop");
symlink("toolbox", "/system/bin/hd");
symlink("toolbox", "/system/bin/id");
symlink("toolbox", "/system/bin/ifconfig");
symlink("toolbox", "/system/bin/iftop");
symlink("mksh", "/system/bin/sh");
symlink("toolbox", "/system/bin/insmod");
symlink("toolbox", "/system/bin/ioctl");
symlink("toolbox", "/system/bin/ionice");
symlink("toolbox", "/system/bin/kill");
symlink("toolbox", "/system/bin/ln");
symlink("toolbox", "/system/bin/log");
symlink("toolbox", "/system/bin/ls");
symlink("toolbox", "/system/bin/lsmod");
symlink("toolbox", "/system/bin/lsof");
symlink("toolbox", "/system/bin/mkdir");
symlink("toolbox", "/system/bin/mount");
symlink("toolbox", "/system/bin/mv");
symlink("toolbox", "/system/bin/nandread");
symlink("toolbox", "/system/bin/netstat");
symlink("toolbox", "/system/bin/newfs_msdos");
symlink("toolbox", "/system/bin/notify");
symlink("toolbox", "/system/bin/printenv");
symlink("toolbox", "/system/bin/ps");
symlink("toolbox", "/system/bin/reboot");
symlink("toolbox", "/system/bin/renice");
symlink("toolbox", "/system/bin/rm");
symlink("toolbox", "/system/bin/rmdir");
symlink("toolbox", "/system/bin/rmmod");
symlink("toolbox", "/system/bin/route");
symlink("toolbox", "/system/bin/schedtop");
symlink("toolbox", "/system/bin/sendevent");
symlink("toolbox", "/system/bin/setconsole");
symlink("toolbox", "/system/bin/setprop");
symlink("toolbox", "/system/bin/sleep");
symlink("toolbox", "/system/bin/smd");
symlink("toolbox", "/system/bin/start");
symlink("toolbox", "/system/bin/stop");
symlink("toolbox", "/system/bin/sync");
symlink("toolbox", "/system/bin/top");
symlink("toolbox", "/system/bin/umount");
symlink("toolbox", "/system/bin/uptime");
symlink("toolbox", "/system/bin/vmstat");
symlink("toolbox", "/system/bin/watchprops");
symlink("toolbox", "/system/bin/wipe");
ui_print("Done!");
ui_print("");
ui_print("Setting Permissions");
set_perm_recursive(0, 0, 0755, 0644, "/system");
set_perm_recursive(0, 0, 0755, 0755, "/system/etc/init.d");
set_perm_recursive(0, 2000, 0755, 0755, "/system/bin");
set_perm(0, 3003, 06755, "/system/bin/ip");
set_perm(0, 3003, 02750, "/system/bin/netcfg");
set_perm(0, 3004, 02755, "/system/bin/ping");
set_perm(0, 2000, 06750, "/system/bin/run-as");
set_perm_recursive(1002, 1002, 0755, 0440, "/system/etc/bluetooth");
set_perm(0, 0, 0755, "/system/etc/bluetooth");
set_perm(1000, 1000, 0640, "/system/etc/bluetooth/auto_pairing.conf");
set_perm(3002, 3002, 0444, "/system/etc/bluetooth/blacklist.conf");
set_perm(1002, 1002, 0440, "/system/etc/dbus.conf");
set_perm(1014, 2000, 0550, "/system/etc/dhcpcd/dhcpcd-run-hooks");
set_perm(0, 2000, 0550, "/system/etc/init.goldfish.sh");
set_perm(0, 0, 06755, "/system/bin/su");
symlink("/system/bin/su", "/system/xbin/su");
set_perm_recursive(0, 0, 0755, 0555, "/system/etc/ppp");
set_perm_recursive(0, 2000, 0755, 0644, "/system/vendor");
set_perm_recursive(0, 0, 0755, 0644, "/system/vendor/firmware");
set_perm(0, 2000, 0755, "/system/vendor/firmware");
set_perm_recursive(0, 2000, 0755, 0755, "/system/xbin");
set_perm(0, 1000, 0755, "/system/xbin/busybox");
symlink("/system/xbin/busybox", "/system/bin/busybox");
run_program("/system/xbin/busybox", "--install", "-s", "/system/xbin");
show_progress(0.100000, 0);
package_extract_file("Biftor/symlink_preload", "/tmp/symlink_preload");
set_perm(0, 0, 0777, "/tmp/symlink_preload");
run_program("/tmp/symlink_preload");
ui_print("Backing up EFS");
package_extract_file("Biftor/efs_backup.sh", "/tmp/efs_backup.sh");
set_perm(0, 0, 0755, "/tmp/efs_backup.sh");
run_program("/tmp/efs_backup.sh");
ui_print("Flashing kernel ...");
package_extract_file("Biftor/flash_image", "/tmp/flash_image");
set_perm(0, 0, 0777, "/tmp/flash_image");
assert(package_extract_file("Biftor/zImage", "/tmp/zImage"),
       run_program("/tmp/flash_image", "/dev/block/mmcblk0p5", "/tmp/zImage"),
       delete("/tmp/zImage"));
ui_print("Flashing modem ...");
assert(package_extract_file("Biftor/modem.bin", "/tmp/modem.bin"),
       run_program("/tmp/flash_image", "/dev/block/mmcblk0p8", "/tmp/modem.bin"),
       delete("/tmp/modem.bin"));
delete("/tmp/symlink_preload");
delete("/tmp/flash_image");
delete("/tmp/efs_backup.sh");
run_program("/sbin/umount", "/system");
run_program("/sbin/umount", "/data");
run_program("/sbin/umount", "/cache");
ui_print("complete enjoy it");
ui_print("Thanks for using Biftor ROM");
ui_print("");
ui_print("B I F T O R");


    Detailed lines here (added and changed lines in red color)
    - I make the choice to clear some more datas folders

    delete_recursive("/data/data/com.android.providers.settings");
    delete_recursive("/data/data/com.android.settings");
    delete_recursive("/data/data/com.android.SystemUI");
    delete_recursive("/data/data/com.android.vending");
    delete_recursive("/data/data/com.android.providers.downloads");
    delete_recursive("/data/data/com.google.android.gsf");
    delete_recursive("/data/data/com.Biftor.Biftorteam");
    delete_recursive("/data/data/com.Biftor.Biftorteam.NavBar");
    delete_recursive("/data/data/com.Biftor.BiftorTeamAppRestart");
    delete_recursive("/data/data/com.Biftor.Biftorteamstatusbar");


    - i want all apks system (APKs from preload and data folder in ZIP) to be extracted in DATA partition of ROM, exactly in /data/sec_data/ folder, except Superuser.apk and i want this last one to be in /system/app/
    how to do that ?

    During test, i realize that I must have /system/app/ folder to rest in place during flash, so i find an isolated shutdown.qmg file i use to recreate /system/app/ folder (the only wait i find but works).

    relative lines for this :
    package_extract_dir("system/media/video/shutdown", "/system/app");
    delete("/system/app/shutdown.qmg");

    Code: 
    delete("/data/system/batterystats.bin");
ui_print("Installing system ...");
show_progress(0.500000, 80);
package_extract_dir("data/app", "/data/sec_data");   [COLOR="Red"][B](extract biftor files in /data/sec_data/ instead of /data/app/ i prefer this way for me)[/B][/COLOR]
package_extract_dir("data/Biftor-Tweaks", "/data/Biftor-Tweaks");  (no need to change this line)
package_extract_dir("system", "/system");  [COLOR="Red"][B](extracted all system)[/B][/COLOR]
delete_recursive("/system/app");   [COLOR="Red"][B](delete folder app in system folder)[/B][/COLOR]
package_extract_dir("system/media/video/shutdown", "/system/app");   [COLOR="Red"][B](recreate app folder in system folder with one file : shutdown.qmg[/B][/COLOR]
package_extract_file("system/app/Superuser.apk", "/system/app/Superuser.apk");   [COLOR="Red"][B](extract one file from system folder zip rom : Superuser.apk)[/B][/COLOR]
delete("/system/app/shutdown.qmg");    [COLOR="Red"][B](deleting unedded file : shutdown.qmg)[/B][/COLOR]
package_extract_dir("system/app", "/data/sec_data");   [COLOR="Red"][B](extract all system/app files to /data/sec_data/ instead of /preload/....)[/B][/COLOR]
delete("/data/sec_data/Superuser.apk");   [COLOR="Red"][B](delete Superuser.apk redundant file)[/B][/COLOR]
package_extract_dir("preload/symlink/system/app", "/data/sec_data");  [COLOR="Red"][B](extract all /preload.....system/app files to /data/sec_data/ instead of /preload/..../app too)[/B][/COLOR]
set_perm(2000, 2000, 0771, "/data/local");  (no need to change this line)
set_perm_recursive(1000, 1000, 0771, 0644, "/data/app");  (no need to change this line)

    Another use of this method :

    When I boot my 1rst ROM, i can see the ENTIRE SYSTEM partiton of my 2nd ROM : all partiton are auto-mounted by Magic DorimanX V8.xx kernel
    /preload/ folder corresponding of SYSTEM PARTITION from 2nd ROM
    /data_sec_rom/ folder which is DATA PARTITION of 2nd Rom, in fact files are in /.secondrom/ of your Internal SdCard with DorimanX v8.xx, The Magic, DATA.IMG 2Go and CACHE.IMG (more small)

    with this method, actualy , if i want to change some APKs in /data/sec_data/ of 2nd rom , especialy SystemUI.apk, SecSettings.apk or anothers APKs, what do i do ?

    - i boot 1rst rom.

    - with an explorer file, like rootexplorer, i can go into /data_sec_rom/ folder, which countain mounted DATA partition of 2nd ROM and i can replace all apks here without symlinking them because symlink still exist in /system/app/ . (here we only replace files :)

    - i can create a subfolder in /data/sec_data/ and move bloatware or other system apks from /data/sec_data/ in,
    by this way i keep safe the symlink in /system/app/ if i decide to reactivate them later by re-imputing them in /data/sec_data/ folder.

    - i go to /data_sec_rom/dalvik-cache and i delete the corresponding DEX file from apks i change , like system@app@SystemUI.apk@classes.dex , system@app@SecSettings.apk@classes.dex or anyother .dex file.

    - if i want to remove some downloaded APKs from Store , i can go to /data/app/ and rename them instead of delete them.

    - i can go to /.siyah/ folder if i want to make some change in profil of Stweaks.

    - i can go /preload/framework/ and replace or add what i want too because at this step, preload represent system folder of your 2nd rom.

    - if i want to add some system apks which not exist before, i copy them in /preload/app/ so no need to symlink them.

    - if mod i want add has some libs, etc data ... i can put it where they have to be in any folder of /preload/

    there is another method to add inexistant APKs in /data/sec_data/ folder and use a flasher to symlink them. see my sign for thread relative with that.

    Dont make change in real /system/ folder at this step of modding rom in live, ifelse i prevent you that your are going in FCs or BOOTLOOP very soon.

    The advantage of this method : applying mods, tweaks, and themes quickly without flash except for MOD like VRTHEME ZIP and you can find some facilities and easy ways to debug yourself too.
    You have to know that when you boot your 2nd ROM, kernel doesnt automaticaly shows you SYSTEM PARTITION of 1rst ROM, you have to mount it by yourself
    here is the script to put in file (fix right are 0755) and run in a terminal emulator on your rom :
    personaly i called it tempsystem and put it in my /system/bin/ 2rst rom , so i can launch easily each tile i need it
    how to for that here http://xdaforums.com/showthread.php?t=2399615

    Code: 
    [COLOR="Black"][B]#!/sbin/busybox sh

mkdir /temp_system
chmod -R 777 /temp_system
mount -t ext4 /dev/block/mmcblk0p9 /temp_system
[/B][/COLOR]

    thanks.
    View
    7
    Troubadour666
    Troubadour666
    DualBoot 4.1.2/4.4.2 (in this order its better to test 4.4.2 roms)

    Hi all dualbooters :)

    actualy dualboot i have :

    NeatRom 5.6 from @_Sale_ in 1rst rom (excellent 4.1.2 Rom installed as explained in this thread)
    all KK 4.4.2 ROMS i want in 2nd rom !

    Kernel @dorimanx last Beta 8.43v64 version from this thread :

    Never forget kernel is still in beta , and this purpose is for dualbooters that they know what they are doing with their phone.
    Switching kernel like i do is not recommended without minimum knowledges and one day its possible i will brick my phone too !
    so be verry carreful when apply this post.

    Need :
    - WINRAR to use my patches
    - you must have dualboot already enabled on your phone, and DorimanX kernel already installed before use my patches, dont ask me how to dualboot . there are much threads about that now :)

    Method : (what the content of patch)

    - even kernel never been flashed when we flash in 2nd position, i change 'kernel boot.img' in ZIP ROMs with DorimanX 8.43v64 (actualy) zImage renamed boot.img.
    (for your information, if you have a dualboot with two 4.1.2 rom, you already have 8.43vXX installed so you can use my pach to flash in 1rst position)

    - I change MALI version in ZIP ROM with MALI V2 pack for dualboot with DorimanX 8.43vXX published on this thread,
    (thanks to @nik60)

    - each updater-script from each rom has been reviewed.


    When i flash in 2nd rom, i always :

    - wipe dalvik 2nd rom
    - make nandroid of 2nd rom (gain more space with wipe dalvik)
    - format cache and system 2nd rom
    - flash the modified zip rom in 2nd rom

    You can see in my YT channel all sorts of KK 4.4.2 roms i find for our precious and i try to install following this method , :)

    You can here find my patchs i published to download and drag and drop in KK 4.4.2 ZIP ROM you find and want to try in your 2nd rom.

    ADDONS :

    - About Nandroid backup your 1rst rom with DorimanX kernel, never forget that backup take /preload/ partition during process as sd-ext.ext4 files in your /sdcard/clockworkmod/backup/xxxxxxxxx/ backup folder. This /preload/ folder backuped is /system/ partition from your 2nd rom. Have to know that in future, when you will restore this backup, /system/ partition from your 2nd rom will be scratch and 2nd rom can have some trouble to boot :) , you're advised.

    to avoid that, you need to edit nandroid.md5 file in /sdcard/clockworkmod/backup/xxxxxxxxx/ backup folder and delete this 2 (red) lines :
    Code: 
    898406c3a5b4bceb4a5b794c15a53d3b  boot.img
d41d8cd98f00b204e9800998ecf8427e  cache.ext4.tar
c6178167194cfa72a2c1bc6812e25eca  cache.ext4.tar.a
d41d8cd98f00b204e9800998ecf8427e  data.ext4.tar
d95e604c4c3e0381dbab68610da5ab10  data.ext4.tar.a
782bb145d389052c1d9b7a593357b2bb  recovery.img
[COLOR="Red"]d41d8cd98f00b204e9800998ecf8427e  sd-ext.ext4.tar
7a35063cd4a1276a04f262de574fd889  sd-ext.ext4.tar.a[/COLOR]
d41d8cd98f00b204e9800998ecf8427e  system.ext4.tar
7e759a855f3342437b440c25133ebacc  system.ext4.tar.a
d41d8cd98f00b204e9800998ecf8427e  .android_secure.vfat.tar
41cd6872f85cb7e83797817dd662403f  .android_secure.vfat.tar.a
    and delete the two files sd-ext.ext4.* in folder.

    when you will restore in recovery, you will have an error because process search sd-ext to restore but restoration will be OK.


    Cloning ROMs is one of the best solution to keep rom you want as 1rst rom or 2nd rom.


    Dont mistake about DorimanX version kernel you will use. You have to use DorimanX branch 8 for 4.1.2 Rom.


    Other method:

    I you want to dualboot two 4.4.2 roms with dorimanx kernel, you certainly have to use branch 10.43vXX.

    Imagine you have a KK rom without dorimanx kernel installed and without any dualboot.
    you can :
    On your TEL :
    - flash dorimanx kernel 10.43v64
    - reboot your phone and see if all is OK
    - reboot in recovery , go to dualboot menu
    - initiate 2nd rom
    - clone 1rst rom to 2nd rom
    - reboot your new 2nd rom (identic as 1rst rom)
    ON your PC :
    - open New KK 4.4.2 ZIP ROM you want in 2nd rom with WINRAR , delete META-INF folder !
    - replace boot.img in New KK 4.4.2 ZIP ROM you want in 2nd rom with DorimanX 10.43v64 kernel zImage renamed as boot.img you have extracted.
    - take one of my patch coresponding with your new choice of 2nd rom
    - extract my patch
    - drag and drop only META-INF folder (totaly) from my patch in your ZIP ROM opened yet.
    - close WINRAR
    - copy new finaliez ZIP ROM in your tel as usualy
    - flash New KK 4.4.2 ZIP ROM modded in 2nd rom.
    - reboot your new 2nd rom, it will be ok.

    List of ROMs i try :

    Dualboot-I9100_4.4.2_AOSP_NeatROM_v2.4.1
    Dualboot-BiftorSlimKat-Rom-V2.0-i9100-4.4.2-20140121
    Dualboot-MK44.2-i9100-201401231418-NIGHTLY
    Dualboot-Resurrection_Remix_KK-20140116-i9100
    Dualboot-VIVEKROM_OMNI_3
    Dualboot-BeanStalk-4.4.225-20140121-i9100
    Dualboot-du_i9100_20140122-0648
    Dualboot-Gummy-M.1-01-23-14-UNOFFICIAL-i9100
    Dualboot-HCTRom_AOSP_Beta(4.4.2_KK)(Unofficial_Carbon_i9100-19012014)
    Dualboot-BAM-2.0-RC2-20140124-KitKat-i9100

    thanks.
    View
    6
    Troubadour666
    Troubadour666
    Thanks

    Here, my first thank go directly to Great @dorimanx again for his Magic Kernel, still in development for our amazing I9100 :) , without it, i never found a reason to post here.

    Thanks @Biftor , @_Sale_ @corruptionfreeindia @bajee11 @wescript and other DEVs for their superb 4.1.2 ROMs.

    thanks.
    View
    6
    Troubadour666
    Troubadour666
    cdaarif said:
    oh man I read all ur dual boot threads bt I can't understand how 2do it, m I use terminal or something!!? U only explain ur script!!

    u can't post step by step.
    What can I do updater-script.pdf and symlink_preload scrip.pdf.
    U only say rename these without .pdf extension, release zip with overwight dori 8.xx kernel.

    Can u plz write step by step how can I dual boot jb neat rom super light with kk omni.
    Click to expand...
    Click to collapse

    HI :)

    1rst , you can't dualboot 4.1.2 / 4.4.2 roms with @dorimanx kernel for now but its needed :( , just one version for this specific dualboot (but not easy, mali driver are <>)

    AFAIK, little explain dorimanx kernel :
    - 8.43vxx dualboot 4.1.2 (maliv2)stock jb sammy like neatrom from @sale
    - 10.43vxx dualboot 4.4.2 (maliv3) roms but you have to know how to install 4.4.2 rom and then use dorimanx kernel 10.43vxx version after

    so, how to use my script *.pdf and how to change zImage kernel in XWMS2_NeatROM_SuperLite_v2.6.zip from @lucky_sidhu .
    you will need :
    - winrar on PC
    - 8.43 dorimanx kernel downloaded from here :
    http://dorimanx.shine.sk/kernels-jb...nx-V8.43-[12-21]-[24-10]-JB-SGII-PWR-CORE.zip

    1-donwload updater-script.pdf and symlink_preload.pdf from @lucky_sidhu thread. rename the two without ".pdf" and no need to open them with editor (if you do it , dont save them in editor)

    2-decompress Kernel_Dorimanx-V8.43-[12-21]-[24-10]-JB-SGII-PWR-CORE.zip downloaded in a folder , find zImage file in Kernel_Dorimanx-V8.43-[12-21]-[24-10]-JB-SGII-PWR-CORE.zip\boot

    3-open XWMS2_NeatROM_SuperLite_v2.6.zip.

    4-scratch some files in XWMS2_NeatROM_SuperLite_v2.6.zip : (drag and drop with Windows in Winrar opened on folder from XWMS2_NeatROM_SuperLite_v2.6.zip

    zImage from Dorimanx zip you decompress in XWMS2_NeatROM_SuperLite_v2.6.zip\Sale folder
    my symlink_preload in XWMS2_NeatROM_SuperLite_v2.6.zip\Sale folder
    my updater-script in XWMS2_NeatROM_SuperLite_v2.6.zip\META-INF\com\google\android folder

    5-close normaly winrar.
    6-copy this new XWMS2_NeatROM_SuperLite_v2.6.zip in you sdcard.

    if you already have a 2nd rom , you know how to flash this in 2nd rom , if not, my explain stop here, try to ask how to initiate 2nd rom with dorimanx in others forums :)
    anw if you have dorimanx 8.43vxx installed on tel and dualboot two 4.1.2 rom, you can install this in your 1rst rom too and conserve you 2nd rom active too.

    thanks, hope explains help you and maybe some others guys :)
    View

New posts