Database Info

Any Kernel Updater (Moded for eMMC)

I have just edited the AnyKernel updater script by koush to work with eMMC devices :-D
hope ppl can make use of this
its very simple
1) grab the attached .zip file
2) extract
3) add the zImage to the /kernel/ directory
4) add .ko modules to /system/lib/modules/ directory
5) **optional** change the boot partition location in the updater-script (not normaly needed)
6) zip up the file
7) its ready to flash in CWM
Credits
Koush for the original boot unpack / repack bin's and scripts
IEF for the stand alone dd binary

Apache14 said:
I have just edited the AnyKernel updater script by koush to work with eMMC devices :-D
hope ppl can make use of this
its very simple
1) grab the .tar.gz file
2) extract
3) add the zImage to the /kernel/ directory
4) add .ko modules to /system/lib/modules/ directory
5) **optional** change the boot partition location in the updater-script (not normaly needed)
6) zip up the file
7) its ready to flash in CWM
Credits
Koush for the original boot unpack / repack bin's and scripts
IEF for the stand alone dd binary
Click to expand...
Click to collapse
When you say grab the .tar.gz file, your referring to the file attached correct?
Just making sure I have everything clear before I use this.
Thanks! Great work!!

BAh yep thats a typo lol the .zip file

Apache14 said:
BAh yep thats a typo lol the .zip file
Click to expand...
Click to collapse
Thanks! I figured it was.

[i9003][FAQ] Read this first!

0. REMEMBER use search option on this forum before ask some question: it's about 90% that this question was posted and already discussed on this forum.
1. My phone gets heated upto 45C during using it and charging. Is this a bug?
2. Can we flash firmware from Samsung Galaxy S (i9000) onto Samsung Galaxy SL (i9003)?
3. What firmware can I flash to my phone? I have XXXX firmware. What is better fw for me to flash?
4. I downloaded the firmware in .rar file, but it asks password. What is password?
5. Can I reflash back my own firmware without any problem?
6. Will I loose warranty on my phone after reflashing?
7. How to flash firmware? My firmware has only 1 file. What should I do?
8. What is factory reset? How to do factory reset?
9. What is rooting of phone? Is it necessary to root the phone? How to root phone?
10. What is "Deodexing"? Is it necessary to deodex the phone? How to deodex my phone?
11. Does i9003 have Gingerbread Android (2.3)?
12. Please help! I removed xxx.apk from my phone and I forget to make backup. Somebody give me it.
13. What is Clockwork Mod (CWM)?
14. How to flash CWM?
15. My GPS locking takes too much time. What should I do?
16. Do the i9003 have custom ROMs? How can I install it?
17. How can I convert rfs to ext4? I applied ext4 conversion, but now I has boot loop. Where can I find ext4 script for XXXX ROM?
1. My phone gets heated upto 45C during using it and charging. Is this a bug?
A: (thanks to supergaijin) think about it this way: your phone is a smartphone, not a computer. a computer can shunt the incoming power from the A/C when the battery is charged, but your phone can't. instead, the phone shuts off the charger connection at 100%. have you read about people who leave their phone plugged into the charger and when they remove it, their battery drops to 93% or whatever? it's cause the phone was not charging after reaching 100% to avoid overcharging
did you know you can run a laptop without the battery installed, as long as the A/C cord is plugged in? can you remove your phone battery and leave the A/C cord plugged in and start the phone? no. why? because all charge in the phone must go through the battery before reaching the rest of the phone's circuits for operation since there is no shunt.
so here's the deal: charging your phone without doing anything causes some heat in the battery. running things on your phone causes heat as your batter drains. so, charging the phone at the same time it's discharging will cause even more heat. take a break, or make the phone run slower for less heat
2. Can we flash firmware from Samsung Galaxy S (i9000) onto Samsung Galaxy SL (i9003)?
A: No. If you do this you will get full bricked phone. and only service center can repair it.
3. What firmware can I flash to my phone? I have XXXX firmware. What is better fw for me to flash?
A: You can flash any firmwares created for i9003. The list of them you can see in kkrraazzyy's post or on samfirmware.com.
Now the most users decided that firmware XXKB3 is most stable and bug-less firmware. For this firmware a lot of developers create their modifications and themes. But some users from America said, that after flashing with XXKB3 they lose ability to connect through 3G. When they returned back to their fw this ability didn't appear.
Also we have releases of gingerbread firmware XXKPH/XXKPM/JPKP5/JPKP5. They have some bugs, but it's usable enough and many users switched to use GB ROMs
Before flashing any FW it's highly recomended to make backup of your /efs partition. Because there is saved your IMEI number and if you remove it you will loose ability to make calls. To make backup you have to root your device
A2: There are different firmwares for different regions. They have different setting different locale support. The region of firmware encoded in its name (first 2 letters). here you can see what this letters mean.
4. I downloaded the firmware in .rar file, but it asks password. What is password?
A: read everything from post you downloaded this file! If it's kkrrassyy's post or samfirmware.com the password is "samfirmware.com"
5. Can I reflash back my own firmware without any problem?
A: Yes you can, but with some limitations: if your firmware contain only 1 file and before you flashed your phone with firmware contained 3 files, there is possibility that you can have some problems with network connection (like loosing APN settings or 3G internet), because your firmware doesn't contain modem file with all settings for GSM modem that are used in your region.
6. Will I loose warranty on my phone after reflashing?
A: Yes. But some of the forum users said that their service centers helped them without any problems. Also you can always flash back your firmware (if it's in the lists of point 2 of this FAQ) and said that you don't do anything with your phone, but it became broken. If in service center won't make detailed research of your phone, it can be successful for you.
7. How to flash firmware? My firmware has only 1 file. What should I do?
A: process of flashing is very good described in kkrraazzyy' post [I9003] [HOWTO] flash Samsung I9003 Galaxy SL Firmware. But read this post to the end before flash. if you have only 1 .tar file in your firmware you shouldn't use .pit file and flash you phone only with 1 pda file.
Never check "Phone EFS clear" option in Odin application! You will loose your IMEI number and can't make calls!
8. What is factory reset? How to do factory reset?
A: Factory reset means that you will clean all user settings and installed applications. And your phone becomes with empty ROM. But remember that factory reset doesn't clean the internal or external sd cards. There are several ways to make full (factory) reset:
1. Go to settings->Privacy->Factory data reset.
2. power off your phone. go to recovery console (press Volume UP and Home, then don't releasing this buttons press to power button till the phone vibrate, then release power button, then release other buttons). And select "wipe data/factory reset"
3. enter as a phone *2767*3855# Attention! In this case full reset starts after entering "#" and it cleans internal sdcard
9. What is rooting of phone? Is it necessary to root the phone? How to root phone?
A: Some operations in your phone usually hidden from usual user. It's for don't give to you destroy your phone or remove some special programs without what the phone became only expansive bookreader with small screen. When you became root of your phone this means that you became administrator of your phone and can do anything you want. You can remove/change/add any data to the system partitions, remove/change your IMEI number and so on. Some applications need the root access to make backup of full system (like Titunium Backup), setup firewall settings (like DroidWall) and so on. Also if you want to append some mods to your phone or for deodexing you need the root. Is it necessary to root you phone: make up your mind by yourself. How to root the phone is described in rahiljnmc's post [GT-i9003] [HOWTO] Root Samsung Galaxy SL or you can use CWM to root your phone without PC [I9003][CWM] Root Update.zip 2.2.1
10. What is "Deodexing"? Is it necessary to deodex the phone? How to deodex my phone?
A: To make applications faster their resources are compiled to special format during application start. Then this binary data is put into the cache (and it saves the time in next start). But we also can save the time of the first start and space in cache if we get application, compile all its resources, remove resources from application and put .odex file near the .apk
IE .odex file is compiled resources of .apk. And they save the time of start and space. But we can't modify compiled resources. That's why for customization we need deodexed applications.
OK. Now answer to your question:
Deodexing -- process to decompile compiled resources from .odex file and put these resources into .apk file
Positives: we can easy change application look (by changing images of it) or behavior(by changing .xml files)
Minuses: first start of application will be longer, also it will take some space into cache.
Usually stock firmwares are released odexed. If you want to attach new mod, or change the look-and-feel of your phone with different theme, you need deodex your phone.
How to deodex the phone you can find here or here. Also if you flash your phone with XXKB3 firmware you can use this post with already deodexed firmware files.
Remember to deodex your firmware you need to root your phone before!
11. Does i9003 have Gingerbread Android (2.3)?
A: Yes. The official ROM for the Europe is XXKPH. It's based on Gingerbread Android (2.3.4). Here is feedback
Before flash the firmware just read the thread. There are described some problems and sollutions.
12. Please help! I removed xxx.apk from my phone and I forget to make backup. Somebody give me it.
A: Don't worry you already have it at your PC.
1. unpack PDA.......tar file. here you can see system.rfs file.
2.1 For Windows: open it with MagicISO
2.2 For Linux: mount it as loop device ( mount -o loop system.rfs /mnt ) Remember you have to be root to mount files.
REMEMBER: if you are using deodexed firmware you need deodexed applications
13. What is Clockwork Mod (CWM)?
A: Clockwork Mod is a modification of recovery console that gives you some extra ability:
1. You can make full backup of your phone. and restore it even if your phone is soft bricked (but you can go into recovery console).
2. You can apply unsigned update.zip files that created by other developers to easy apply some mods or themes. Also you can even don't rename that file to "update.zip", just place it in some directory of your external sd card and use "install zip from sd card" option.
3. you can create access to your external sd card from PC even if your phone is in the recovery menu
14. How to flash CWM?
A: look at this thread and look at CWM created for your firmware. REMEMBER: CWM created for other firmware can soft brick your phone.
If you find it flash it with Odin like it's a PDA file. If not, you can send to Skin1980 your normalboot.img and he can create CWM for your firmware if he will have time for this. How to take this file described in his post
Also there is an universal CWM from Gingerbread ROMs by amit.bagaria. You can apply it to any GB based ROMs
15. My GPS locking takes too much time. What should I do?
A: At the first you have to understand that if it's a lot of clouds in the sky or the view of sky is limited (IE you have bad signals from GPS satellites) the locking will take a lot of time with any devices.
But it's common problem of firmwares was released before February. Try to flash to XXKB3 or other firmwares released after XXKB3.
Also you can read this thread and follow the instructions. I'm staying on XXKB3 and using GPS Aids from the market, and it enough for me to take locking for 10 seconds.
16. Do the i9003 have custom ROMs? How can I install it?
A: Yes. Look at the next post for the details.
17. How can I convert rfs to ext4? I applied ext4 conversion, but now I has boot loop. Where can I find ext4 script for XXXX ROM?
A: At the first you have to know that it's not real conversion. You can't convert rfs to ext4 without data loosing. Because it's just formatting partition to ext4. This means, that you have to make full backup before applying ext4 script, then apply it, then DO NOT REBOOT and restore your backup. Also because this is just formatting you can use this script for any ROMs. The only requirement is supporting ext4 by the kernel. script for formatting is here
Also you can read FAQ for i9000. there some questions are described very good.

Some tweaks
1. Two finger Google map rotation Do not need for Gingerbread firmwares.
2. What stock application I can remove safely? How can I do it?
A: Before remove anything I recommend to make backup of it at your sdcard. In this case you can easy restore this application using adb shell
In this thread you can read what applications you can easy remove. to do this you can go to /system/app directory and remove the corresponded files. You can do it with adb shell or root explorer. But for novices there are some powerful tools that gives to you this ability (you can find them in the market):
SGS tools: go to "Cleanup System App". It can make backup of removed applications
Titanum Backup
nitrality: go to "Applications" and uncheck unneeded aplications
Also you can remove sounds from /system/media/audio (but don't touch /system/media/audio/ui) if you use your own sounds for alarms, notifications and calls
3. For taking more faster application start you can convert your system partitions to ext4 filesystem.
To do this you have to follow this instructions. Also remember after converting to ext4 and before restoring backup DO NOT RESTART YOUR PHONE, else you will have soft bricked phone and should to reflash your firmware
4. Graphics Performance BOOOST Fix can boost the speed of applications in OpenGL games
Also you can take some info from the following threads:
1. about Custom ROMs - MODs
2. about Themes

For developers
I wanted to make FAQ how to make themes: SCIENTYREAL was the first. OK here his post
HOW-TO Create update.zip
Remember:
1. All update.zip files should have special structure of directories inside the ZIP archive:
META-INF — directory contains signature of your package and updater-script that executes when you apply this archive from the recovery console
script should be placed in the path update.zip/META-INF/com/google/android/updater-script
The sript needs binary file from its work. The binary is placed in the path update.zip/META-INF/com/google/android/update-binary
I attached it to this post
all other directories contain content should be applied.
If you will create package for CWM you don't need to sign your update.zip. You can read this topic how to sign your update.zip by test signature. And this post with detailed instruction how to create update.zip for custom recovery
2. About syntax of updater-script you can read here, here and here
Here is description of commands (thanks to sk0t from 4pda.ru)
package_extract_dir
Syntax: package_extract_dir("<src-dir>", "<dst-dir>");
Extracts files from <src-dir> into <dst-dir>. All files from <dst-dir> that exist into <src-dir> will be rewritten
Example: package_extract_dir("system", "/system"); Copy files from update.zip/system into /system
package_extract_file
Syntax: package_extract_file("<src-file>", "<dst-file>");
Copies file <src-file> to <dst-file>. If file <dst-file> exists it will be rewritten.
Example: package_extract_file("test.sh", "/tmp/test.sh"); Copies test.sh from update.zip into /tmp/test.sh
format
Syntax: format("MTD", "<root>");
Formats partition <root>.
Example: format("MTD", "system"); Formats /system . NOTE: it will remove everything from partition /system!
delete
Syntax: delete("<file1>"[, "file2", ..."fileN"]);
Rempves file(s)
Example: delete("/system/app/Calculator.apk"); Removes Calculator.apk from /system/app.
delete_recursive
Syntax: delete_recursive("<dir1>"[, "dir2", ..."dirN"]);
Removes directory(-ies) recursivelly
Example: delete_recursive("/data/dalvik-cache"); Removes directory /data/dalvik-cache with everything inside.
run_program
Syntax: run_program("<filetorun>"[, "<opt1>", "<opt2>", "<opt3>"]);
Starts program (script) <filetorun> [with parameters].
Example: run_program("/tmp/install_busybox.sh"); Starts script /tmp/install_busybox.sh.
set_perm
Syntax: set_perm(<uid>, <gid>, <mode>, "<pathtofile>"[, ... "pathtofileN"]);
Sets owner, group and permissions for file or directory (like chmod, chown and chgrp in unix)
Example: set_perm(0, 2000, 0550, "/system/etc/init.goldfish.sh"); Sets owner, group and permissions for file /system/etc/init.goldfish.sh
set_perm_recursive
Syntax: set_perm_recursive(<uid>, <gid>, <dir-mode>, <file-mode>, "<path>"[, ... "<pathN>"]);
The same as set_perm, but works recursively. <dir-mode> - permissions for directories, <file-mode> - permissions for files.
Example: set_perm_recursive(0, 0, 0755, 0644, "/system/app"); Sets permissions for content of /system/app, for directories - 0755, for files - 0644.
show_progress
Syntax: show_progress(<fraction>, <duration>);
Moves progressbar to <fraction> parts each <duration> seconds. <duration> can be 0 for moving progressbar by command set_progress, but not by time.
Example: show_progress(0.100000, 1); Increses progress on 0.1 part every 1 second
set_progress
Syntax: set_progress(<fraction>);
Sets position of progress bar to <fraction>.
Example: set_progress(0.500000);
symlink
Syntax: symlink("<link-target>", "<link-path1"[, "<link-path2>", "<link-path3>"]);
Creates symlink (like ‘ln -s’).
Example: symlink("/data/app_s", "/system/app"); Creates symlink /data/app_s for directory /system/app
mount
Syntax: mount("<kind>", "<what>", "<path>");
Mounts <what> in the path <path>. <what> should be name of partition if <kind> is "MTD", or block device if <kind> is "vfat"
Example: mount("MTD", "userdata", "/data");
unmount
Syntax: unmount("<path>");
Unmount <path>.
Example: unmount("/data");
ui_print
Syntax: ui_print("<message>");
Prints on screen message <message>
Example: ui_print("Formatting SYSTEM...");
Example of the script file
Code:
show_progress(0.100000, 0);
ui_print("Mounting SYSTEM...");
mount("MTD", "system", "/system");
show_progress(0.100000, 0);
ui_print("Extracting files...");
package_extract_dir("system", "/system");
show_progress(0.400000, 0);
ui_print("Setting permissions...");
set_perm(0, 0, 0644, "/system/framework/framework-res.apk");
show_progress(0.200000, 0);
ui_print("Unmounting SYSTEM...");
unmount("/system");
show_progress(0.100000, 0);
Remember to mount system partition when you are changing something there. Because CWM doesn't mount it
3. OK. Now we are ready to create our own update.zip script:
For example you created modification of theme. The modification contains: /system/framework/framework-res.apk, /system/framework/framework.jar, /system/framework/twframework-res.apk and /system/app/Phone.apk
3.1. create the directory where you will reproduce the structure of update.zip. For example c:\update Create the following directories inside that directory:
{
"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"
}
3.2. Update script content is described below as example
3.3. Archive the content of that directory as ZIP archive (inside archive shouldn't be update directory!)
That's all! Unsigned update.zip is created

good job. I thing to write aboutClockworkMod Recovery

brilliant woork falex
thumbs up!!!!!
all the noobs cntinuously ask theese sily questions...
i think u should also write about custom roms cyanogen mod and give link for the themes...

good work. I thing you should about CWM

podanimesh said:
brilliant woork falex
thumbs up!!!!!
all the noobs cntinuously ask theese sily questions...
i think u should also write about custom roms cyanogen mod and give link for the themes...
Click to expand...
Click to collapse
I have questions in my PM, also I have answered and read the answers of the same questions, that's why I decide to write this FAQ.

Nice work falex

Awesome, falex007! Brilliant work!
Enviado desde mi GT-I9003 usando Tapatalk

umarian said:
good work. I thing you should about CWM
Click to expand...
Click to collapse
OK. I'll write it now

hey falex can u add something extra on ur thread title llike all questions on I9003 like this because every one is unnecessarily making new threads and making this I9003 section bulky i hope u understand..

podanimesh said:
hey falex can u add something extra on ur thread title llike all questions on I9003 like this because every one is unnecessarily making new threads and making this I9003 section bulky i hope u understand..
Click to expand...
Click to collapse
I can add everything to my post. Just I don't understand what I should add Or may be you don't enter correct link to your post
Also a little bit later I want to add some FAQ about creating themes, creating update.zip updates for CWM

Good God, Someone please sticky this man's thread!! , THIS. I repeat. THIS is what people with ignorance need to read, Sorry as that might sound harsh. But it saves 50 useless threads from being made.
Also a bigass thumbs up from me. And a 5* Rating.

Please make it sticky thread. Its an awsome thread...for this already i have pressed thanx button for u.

Thanks! I think the number of "new threads" will now decrease!

Excellent work and very valuable info, but wait a sec..
falex007 said:
10. When will i9003 have stable GB?
A: i9003 will have stable stock GB firmware when Samsung decide that their firmwares don't have the bugs. For some info we will have this firmware at the September of 2011.
Click to expand...
Click to collapse
did u just say september, what happened to mid july?!

android_and_me said:
Excellent work and very valuable info, but wait a sec..
did u just say september, what happened to mid july?!
Click to expand...
Click to collapse
It's already 19 as of now, I think "Mid July" didn't happen

android_and_me said:
Excellent work and very valuable info, but wait a sec..
did u just say september, what happened to mid july?!
Click to expand...
Click to collapse
I know 3 messages about GB release for i9003:
1. Samsung Mobile India said at May about release in middle of July.
2. Samfirmware.com after posting XXKP7 ment that stable GB for i9003 will be at September.
3. Samsung Mobile Russia said several days before that work is going and they expect the release of GB at neareast weeks, but they can't say the date.
That's why I posted the worst expectation.
Sent from my GT-I9003

hey falex change threas name from faq to post ur questions here...today someone has made a new thread for asking questions.
these stupid people are just useless.so please change the thread title to post all ur questions here. it would be great

podanimesh said:
hey falex change threas name from faq to post ur questions here...today someone has made a new thread for asking questions.
these stupid people are just useless.so please change the thread title to post all ur questions here. it would be great
Click to expand...
Click to collapse
I've changed it. But I think not many people from this forum read the stickies.
For example at the top of all subsections inside "Samsung Galaxy S I9000" section we can see the sticky "[NEW!] SGS Forum Etiquette [i9000] [i9003] [i9000B] [i9000T] [i9000M] [M240S] [02B] +". How many people read and follow instruction in this topic?

[mod][tool]dual boot for zte blade/modify-tool

Hello guys. This my dual booting project for our amazing ZTE BLADE!
What is this?
>This mod works on the basis of two scripts which are to be executed in the terminal emulator or script manager and a modified boot.img to boot the rom from sdcard instead of NAND.
FOR ADVANCED USERS ONLY!!!
I WILL NOT BE RESPONSIBLE FOR ANY BRICKED DEVICES, DAMAGED SDCARDS ETC.
DO IT AT YOUR OWN RISK!!!
It is in alpha stage, so lot of work is still needed to make it more safer and convenient.
I will add this mod for more ROMS like CM10, Paranoidandroid etc.
Downloads:
Cyanogenmod9(KonstaKang)
Boot.img - Download
Updater-script - Download
Cyanogenmod10
Boot.img - Download
Updater-script - Download
Gapps::
Jelly Bean Gapps Updater-script - Download
Tool:
Modify-Boot - Download
Now no need to wait for me to mod your boot.img.Mod your boot image for dual boot with this tool!!!
Guide for the tools is on the second post.
Thanks go to:
Sulthekk for guiding me towards right way.
SNAP.iT for giving me some mounting ideas.
All the people who have helped me(can't remember all names ).
And the big community to test it for me.
SCROLL DOWN to 2nd POST FOR THE WHOLE GUIDE...

GUIDE
So here is the full guide:
PARTITIONING SD CARD TO MOUNT /SYSTEM AND /DATA
Take the backup of your sd card data first
Make sure you have partitioned your sdcard before.
Connect your phone to your computer and mount usb storage.
Download the EASEUS partition manager from here.
Open partition manager and delete all partitions of your sdcard.
Right click on the 'unallocated' and click create partition.Don't label it select partition type as primary and filesystem as FAT32 and enter the partition size bot remember this will hold your photos,media etc,you should leave about 600 mb space free click OK.
right click again and create partition as primary and filesystem as EXT3 and size of 250 mb click OK.
Repeat above step again.
Apply all the changes by cliking on apply tap and you have succesfully partitioned your sdcard for dual booting.
​
GUIDE FOR THE TOOL
Extract the downloaded zip file extract to any concinient directory.Here I will explain the guide as a cygwin user.
Extract the zip to directory say c:\
The extracted folder will look like 'Modify-boot".Now open the terminal or cygwin bash and mount the directory by typing
cd c:\modify-boot
Click to expand...
Click to collapse
Now drop your boot.img in the WORKING_313 folder and execute the script by typing
./modify-boot.txt
Click to expand...
Click to collapse
It will mod your boot.img for dual booting.Output boot.img will be in the WORKING_313 folder as boot.img.
MODDING THE ROM FOR DUAL BOOTING
Open the ROM.zip.
Get the modded boot.img from the tool and replace with the original one.
Now download the attached updater-script from 1st post and replace the orignal one with this modded one(path to udater-script META-INF/com/google/android).
Zip up the rom.
ADAPTING A ROM TO INSTALL IN THE SD CARD
If you want to mod your own rom other than the posted here,then you have to mod the updater-script in the rom
For that open your rom zip go to /META-INF/com/google/android and open the updater script
Now replace every line looking like following as;
From
mount("yaffs2", "MTD", "system", "/system");
Click to expand...
Click to collapse
TO
run_program("/sbin/mount", "dev/block/mmcblk0p3", "/system");
Click to expand...
Click to collapse
and this one
From
format("yaffs2", "MTD", "system", "0");
Click to expand...
Click to collapse
TO
run_program("/sbin/mkfs.ext2", "dev/block/mmcblk0p3");
Click to expand...
Click to collapse
and add the following line next to the line written above
run_program("/sbin/mkfs.ext2", "dev/block/mmcblk0p2");
Click to expand...
Click to collapse
Save the file and zip up the rom.Your rom is ready to install to SD CARD!!!!
FLASHING GUIDE
Remember, before partitioning the sd card you should wipe data and cache in the recovery during NAND rom installation or it will erase the partitions created before.
First flash the rom you want to install in the NAND,do not wipe data or anything do it before partitioning.
Then install the rom without wiping data or anything.
reboot the system. You will be in your sd card rom!!!
Now create folder in the sd card as /sdcard/multiboot.
Take both boot.img from NAND rom and cm9 rom rename the cm9 boot.img to bootsd.img and keep the NAND boot.img as it is.
Copy both imgs to multiboot folder.
Now download attached(or use above link for unregistered users) bootnand.sh and bootsd.sh and place at the root of the sdcard.
Open terminal emulator,type su and execute bootsd.sh to boot into sd card rom or execute bootnand.sh to boot into NAND rom.
THAT'S IT . ENJOY DUAL BOOT ON YOUR ZTE BLADE!!!!

[email protected] said:
So here is the full guide:
PARTITIONING SD CARD TO MOUNT /SYSTEM AND /DATA
Take the backup of your sd card data first
Make sure you have partitioned your sdcard before.
Connect your phone to your computer and mount usb storage.
Download the EASEUS partition manager from here.
Open partition manager and delete all partitions of your sdcard.
Right click on the 'unallocated' and click create partition.Don't label it select partition type as primary and filesystem as FAT32 and enter the partition size bot remember this will hold your photos,media etc,you should leave about 600 mb space free click OK.
right click again and create partition as primary and filesystem as EXT3 and size of 250 mb click OK.
Repeat above step again.
Apply all the changes by cliking on apply tap and you have succesfully partitioned your sdcard for dual booting.
​
MODDING THE CM9 ROM FOR DUAL BOOTING
Open the konstakang.zip (currently only supported rom, will add more soon).
Download modded boot.img from here extract it and rename the .img file to boot.img.
Delete the boot.img from the cm9 rom and put the downloaded one.
Now download the attached updater-script (remove .txt) or from here (for unregistered users)and replace the orignal one with this modded one(path to udater-script META-INF/com/google/android).
Zip up the rom.
FLASHING GUIDE
Remember, before partitioning the sd card you should wipe data and cache in the recovery during NAND rom installation or it will erase the partitions created before.
First flash the rom you want to install in the NAND,do not wipe data or anything do it before partitioning.
Then install the cm9 rom without wiping data or anything.
reboot the system. You will be in your sd card rom!!!
Now create folder in the sd card as /sdcard/multiboot.
Take both boot.img from NAND rom and cm9 rom rename the cm9 boot.img to bootsd.img and keep the NAND boot.img as it is.
Copy both imgs to multiboot folder.
Now download attached(or use above link for unregistered users) bootnand.sh and bootsd.sh and place at the root of the sdcard.
Open terminal emulator,type su and execute bootsd.sh to boot into sd card rom or execute bootnand.sh to boot into NAND rom.
THAT'S IT . ENJOY DUAL BOOT ON YOUR ZTE BLADE!!!!
Click to expand...
Click to collapse
hi, thank u ....... the link for 'boot.img' is not working. Pls fix it

Can't thank you enough for this,if it works.. Great stuff btw.. At least,you were the first one that tried and got it working..
Sent from my LT26i using xda premium

karthiknr said:
Can't thank you enough for this,if it works.. Great stuff btw.. At least,you were the first one that tried and got it working..
Sent from my LT26i using xda premium
Click to expand...
Click to collapse
+1
We've been waiting on this ever since karthik and wbaws discussion made it sound impossible

Just reported as a news tip for the portal

Thanks!!

New update coming for tool soon!!!

Its a great achievement .. future updates will be easy to go on for basic user. Btw thanks man. .
Sent from my Blade using Tapatalk 2

I've found that making four partitions and installing /data to mmcblk0p4 and /system to mmcblk0p3 helps with certain roms that have S2E configured.
I'm also trying to get it to boot two mounted loop filesystems instead, i installed SSRLS7 and GB-Gapps as per your instructions in the OP (just changed the partitions for installation and the updater-script and init.rc so that it would work) did a dd of the entire partitions to files on the sdcard and edited the init.rc like this:
Code:
on fs
# mount mtd partitions
chmod 777 /sbin/busybox
symlink /sbin/busybox /sbin/losetup
mount vfat /dev/block/mmcblk0p1 /mnt/sdcard
losetup /dev/block/loop0 /mnt/sdcard/multiboot/snow/system.img
losetup /dev/block/loop1 /mnt/sdcard/multiboot/snow/data.img
mount ext2 /dev/block/loop0 /system
mount ext2 /dev/block/loop1 /data
mount yaffs2 [email protected] /cache nosuid nodev
on post-fs
# ZTE_JCD_CTSCONFIG, 2011.05.03, BEGIN
mkdir /system/lost+found 0770
chmod 0770 /system/lost+found
# ZTE_JCD_CTSCONFIG 2011.05.03, END
# once system is setup, no need to modify /system , ZTE_BOOT_LIWEI_20110331
mount ext2 /dev/block/loop0 /system ro remount
I also copied busybox to /sbin in the ramdisk before letting the process finish and make bootsd.img
It doesn't work though and i have no idea why not. I've mounted the system.img and data.img files on the phone via the terminal to test if the procedure works and it does mount them just fine.
If anyone has any clue why this doesn't work then please tell me.

Dual boot on ideos x6
[email protected] said:
hello guys. This my dual booting project for our amazing zte blade!
What is this?
>this mod works on the basis of two scripts which are to be executed in the terminal emulator or script manager and a modified boot.img to boot the rom from sdcard instead of nand.
For advanced users only!!!
I will not be responsible for any bricked devices, damaged sdcards etc.
Do it at your own risk!!!
It is in alpha stage, so lot of work is still needed to make it more safer and convenient.
I will add this mod for more roms like cm10, paranoidandroid etc.
Downloads:
cyanogenmod9(konstakang)
boot.img - download
updater-script - download
cyanogenmod10
boot.img - download
updater-script - download
gapps::
Jelly bean gapps updater-script - download
tool:
Modify-boot - download
now no need to wait for me to mod your boot.img.mod your boot image for dual boot with this tool!!!
Guide for the tools is on the second post.
Thanks go to:
Sulthekk for guiding me towards right way.
Snap.it for giving me some mounting ideas.
All the people who have helped me(can't remember all names ).
And the big community to test it for me.
Scroll down to 2nd post for the whole guide...
Click to expand...
Click to collapse
dear friends is it possible on huawei ideos x6?
Plz reply

vimi93 said:
dear friends is it possible on huawei ideos x6?
Plz reply
Click to expand...
Click to collapse
Seriously? Dude can't u see this is the Blade forum. It will not work on any other phones

QuantumFoam said:
Seriously? Dude can't u see this is the Blade forum. It will not work on any other phones
Click to expand...
Click to collapse
Actually, it'll work on any phone that runs android and has a working recovery that can be used to install boot.img and system files via an updater script.
It works fine on my Mini and Huawai G300.

Jinxxed said:
Actually, it'll work on any phone that runs android and has a working recovery that can be used to install boot.img and system files via an updater script.
It works fine on my Mini and Huawai G300.
Click to expand...
Click to collapse
I stand corrected.
---------- Post added at 01:42 AM ---------- Previous post was at 01:37 AM ----------
Oh and btw, [email protected], check the xda portal. You're on the front page.
Congratulations

Jinxxed said:
Actually, it'll work on any phone that runs android and has a working recovery that can be used to install boot.img and system files via an updater script.
It works fine on my Mini and Huawai G300.
Click to expand...
Click to collapse
Will try it out on my LG P500 then!

thanks
Jinxxed said:
Actually, it'll work on any phone that runs android and has a working recovery that can be used to install boot.img and system files via an updater script.
It works fine on my Mini and Huawai G300.
Click to expand...
Click to collapse
thank you for the reply

[DUAL_BOOT][ANY_ANDROID]Dual booting in an android phone with external SD card

So here you come. To read and perform this tutorial, you obviously need a first hand experience on flashing a ROM and/or kernels. Otherwise this tutorial and my efforts to get you a device with two OSes running might end up giving you a bricked device. So, if you're hearing the terms "flashing" or 'kernels' for the first time and thinking it's kinda good food, then bro, just go and taste those first.
Something's to remind before we gonna dig deep into this tutorial->
Noone but you will be responsible for what you end up with.
The warranty of your device will be voided after this if it isn't already after rooting. For MI users, the good news is that you can reclaim it by just flashing the fastboot ROM for your device.
Enough lectures. Bro let's get to work.
Things you'll be needing =>
One working Windows PC(because I doesn't know any replacement of bootimg.exe on any other OS. If you know, then let me).
ADB, fastboot and the device drivers (easily found in XDA)
Any custom CWM based recovery installed.(since TWRP is most popular, I will demonstrate using it. You can use any other you want overall process will be the same)
A custom ROM and kernel for your phone(the second os)
A class 10 memory card ( I recommend 32GB for the spaces)
PART 1: MODIFYING THE BOOT
At first, how does your device boots up? What are the partitions called /data and /system? The answer is quite simple. It's your kernel that points out the location from where the OS should be picked up. So for booting into the second OS we need some modifications to it at first.
Search and download bootimg.exe on XDA, I'll post a link later. Create two folders. Name them "Internal OS" and "External OS" respectively. Put the zip file of the OS you're currently using to the first one and the OS you're gonna use on the external storage to the second one. Rename the second OS to originalExternalOS.zip. Extract originalExternalOS.zip. Pick the boot.img file from the root of the extracted folder and move it to a new folder named "boot2". Extract the IMG using bootimg.exe. Navigate to the initrd folder and you will get a file named 'fstab".
Basically it's the file that tells the kernel which partition does the OS resides in.
Open the file in your favourite text editor.
Replace every instance of the first line with the second one:
/dev/block/bootdevice/by-name/system => /dev/block/mmcblk1p2
/dev/block/bootdevice/by-name/userdata => /dev/block/mmcblk1p3
/dev/block/bootdevice/by-name/cache => /dev/block/mmcblk1p4
Save the file without giving any extension to it. Repack it using the same tool. You'll have boot-new.img and boot-old.img. Rename boot-new.img to boot.img and replace the one in the root folder with this. Basically what we're doing here is replacing the old boot.img with the modified one.
For your knowledge, blocks are the partitions of any storage you have on your device. For example, your internal storage is partitioned to near about 30 different blocks each starting with prefix "mmcblk0p". We here just told the kernel to load the OS from the blocks mentioned. We'll be creating these blocks in the external SD card next.
PART 2: PARTITIONING THE SD CARD
Connect your device with the memory card inserted to your PC. If you haven't installed fastboot, ADB, and the drivers, do it now.
READ THE FOLLOWING CAREFULLY
Reboot the device to recovery mode. Type the commands in cmd:
Code:
adb shell
parted
unit MB
print
quit
umount external_sd
Read and store the minimum and maximum capacity of your card. Since different cards will have different capacities I will point it as variable MIN_SIZE and MAX_SIZE. You'll need to calculate and put the values in the commands. Now type the following commands on cmd:
Code:
parted /dev/block/mmcblk1
rm 1
//START_BLOCK = MAX_SIZE - 5000
mkpartfs primary fat32 MIN_SIZE START_BLOCK
//SYS_START = START_BLOCK+1
//SYS_END = SYS_START + 1200
mkpartfs primary ext2 SYS_START SYS_END
//DATA_START = SYS_END+1
//DATA_END = DATA_START + 3500
mkpartfs primary ext2 DATA_START DATA_END
//CACHE_START = DATA_END + 1
mkpartfs primary ext2 CACHE_START MAX_SIZE
//We have partitioned the memory card. Let's format them. Ignore all "Do you wish to continue" question in the next commands as we're already mentioning yes.
mkfs yes 1 fat32
mkfs yes 2 ext2
mkfs yes 3 ext2
mkfs yes 4 ext2
quit
//Now they are almost ready. Just make the newly created blocks readable by the OS.
make_ext4fs /dev/block/mmcblk1p2
make_ext4fs /dev/block/mmcblk1p3
make_ext4fs /dev/block/mmcblk1p4
//Now you get where does the blocks come in the kernel right?
exit
//You've covered up the hardest part. Let's get some coffee.
PART 3: MODIFYING THE NEW OS
You've left the OS extracted in the "External OS" folder right? It's time to do some magic in it. We're gonna tell the OS to be installed in the blocks we created just like the kernel. But wait, where does the OS know before installing where it should get installed? Well, the answer hides in the updater-script in the folder META-INF > com > google > android. Navigate yourself in it. Open the updater-script file in your favourite editor ( I use notepad++ ) and modify it in the same way as the boot.
Replace every instance of the first line with the second one:
/dev/block/bootdevice/by-name/system => /dev/block/mmcblk1p2
/dev/block/bootdevice/by-name/userdata => /dev/block/mmcblk1p3
Leave the /dev/block/bootdevice/by-name/boot as it's the fundamental block and we can't replicate it. Don't think for the /cache partition as we've already done that in the boot.img file. Now navigate to the root of the folder where you extracted the External OS. Select all files, add them to a zip file using WinRAR. Name the file to newOS.zip. Open newOs.zip and originalExternalOS.zip with WinRAR and compare them if you find any change in the folder tree. They must and they should be exactly the same. You're 80% done.
PART 4: MODIFYING THE RECOVERY
We often flash many zips including very popular Xposed and other mods to our OS right? They also look for the /system partition. So what are we gonna do? Modifying each of them? Nah. Let's modify where they get which one the /system is. The recovery. Extract the img of the recovery you're using with the same bootimg.exe. Modify exactly the same things. I.e.
Replace every instance of the first line with the second one:
/dev/block/bootdevice/by-name/system => /dev/block/mmcblk1p2
/dev/block/bootdevice/by-name/userdata => /dev/block/mmcblk1p3
/dev/block/bootdevice/by-name/cache => /dev/block/mmcblk1p4
in the following files : initrd/fstab.qcom
initrd/etc/recovery.fstab
initrd/etc/twrp.fstab(For TWRP only)
Save them. Repack. And you got your recovery-new.img and recovery-old.img. Put recovery-new.img and newOS.zip in the same folder. Now wake up, it's time for some action.
PART 5 : INSTALLING THE OS
Open cmd in the folder where newOS.zip resides. Reboot the device in fastboot mode. Type the following commands:
Code:
adb push newOS.zip external_sd
fastboot flash recovery recovery-new.img
fastboot boot recovery
Now your device should boot up in recovery mode. To check if everything has gone fine mount system using TWRP. Use twrp's built in file manager and navigate to system folder. It's empty? Yup. You've done a great job. Now flash the newOS.zip using TWRP and your device should boot up in the new OS. To cross check again remove the SD card and try to boot. If you're headed towards recovery or bootloop after that then it's a win. Put the SD card back again and watch the new OS to boot.
PART 6: SWITCHING BETWEEN THE TWO
Extract the boot.img from the "Internal OS" zip file and put it together with recovery-old.img. To check if your old system is untouched type the following commands in fastboot mode:
Code:
fastboot flash recovery recovery-old.img
fastboot flash boot boot.img
fastboot boot system
Your device should take you back to the old one. Surprised? Now let's make a switch between the two. There are two methods.
METHOD 1: USING FLASHIFY
Create two folders in your SD card. Put boot.img and recovery-old.img to one and boot-new.img and recovery-new.img to the other. To switch to the external OS, just flash boot-new.img as boot and recovery-new.img using flashify. Ignore reboot now dialog and reboot directly to the system. To go back, first install flashify in the new OS and flash boot.img and recovery-old.img. Easy right?
METHOD 2: USING ZIPS
I'm gonna tell you that tomorrow as I can write no more today.
More to come....
CREDITS:
justzzshadz from MIUI forum for this revolutionary concept. @iamsubhranil for adding TWRP, Flashify support and completely rewriting the tutorial.

Thank u so much for ur efforts... It helps me a lot
I don't understand members on xda ...why they don't give thnaks on thread ..they only see the thread and go away...
Sry 4 my english ..
Thanks again
---------- Post added at 08:07 AM ---------- Previous post was at 07:48 AM ----------
Pls lemme know that if i can use dsixda's kitchen for modifying boot.img (kernal ) ???
Coz i didn't find bootimg.exe tool... If u have then pls give me the link.
Thanks

yes you can use android kitchen

When You Will Continue Writing The Thread Im Really Interested in trying it

Faisal Z Ahmad said:
When You Will Continue Writing The Thread Im Really Interested in trying it
Click to expand...
Click to collapse
I will after a while as I'm having final exams you can still try with flashify bro

sc123001.11 said:
Thank u so much for ur efforts... It helps me a lot
I don't understand members on xda ...why they don't give thnaks on thread ..they only see the thread and go away...
Sry 4 my english ..
Thanks again
---------- Post added at 08:07 AM ---------- Previous post was at 07:48 AM ----------
Pls lemme know that if i can use dsixda's kitchen for modifying boot.img (kernal ) ???
Coz i didn't find bootimg.exe tool... If u have then pls give me the link.
Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/redmi-1s/general/guide-unpack-repack-kernel-t2908458
Most comfortable

iamsubhranil said:
I will after a while as I'm having final exams you can still try with flashify bro
Click to expand...
Click to collapse
Yeah I Know I Can Try But i Need To Know Method 2 To Switch ROMS Because Second One Is Faster Using Zips Otherwise Great Post And Guide ,Thank You
Good Luck With Your Exams

Nice tutorial.
Dual boot for Mediatek devices is so easy to me. But I don't have any idea for Other devices like Samsung or Sony.
When I bought some SD Card, I'll try this one.
Keep it up!

Faisal Z Ahmad said:
Yeah I Know I Can Try But i Need To Know Method 2 To Switch ROMS Because Second One Is Faster Using Zips Otherwise Great Post And Guide ,Thank You
Good Luck With Your Exams
Click to expand...
Click to collapse
Thanx a lot
BTW flashify is also very convenient method
1)Just choose boot image from the option
2)Find and select the internal or external boot image to boot
3)Have a normal reboot

jbliz said:
Nice tutorial.
Dual boot for Mediatek devices is so easy to me. But I don't have any idea for Other devices like Samsung or Sony.
When I bought some SD Card, I'll try this one.
Keep it up!
Click to expand...
Click to collapse
This one is universal bro

iamsubhranil said:
This one is universal bro
Click to expand...
Click to collapse
I did not see you make any modification to boot.img.
Sry My bad. I didn't read at the top.

iamsubhranil said:
Thanx a lot
BTW flashify is also very convenient method
1)Just choose boot image from the option
2)Find and select the internal or external boot image to boot
3)Have a normal reboot
Click to expand...
Click to collapse
I am gonna try this anyway, maybe tomorrow
Because i want two ROMS mainly, one for CM cuz i love it, daily drivers and everday usage, second one mainly focused on battery life (when i don't use my device much)

Another Question ,How do I Flash Zips (from recovery) To A Specific ROM?
And I Have CM 12.1 And Im Using M5 Kernel so Where Do the Edit Goes?

Faisal Z Ahmad said:
Another Question ,How do I Flash Zips (from recovery) To A Specific ROM?
And I Have CM 12.1 And Im Using M5 Kernel so Where Do the Edit Goes?
Click to expand...
Click to collapse
The edit goes to the recovery. At the end of the process you'll have two different recovery files for two OSes. Flashing any zips via modified recovery will flash them straight to the new os. Switch between those recoveries as required. Read the TUT carefully.

[HOW-TO] (GT-I8262) Fix "unable to mount /system" when installing a ROM

Some people with this device have problems installing a ROM including me. That's because there is some difference in devices even though it seems like they are all the same.
After installing a ROM, if you have these type of messages:
"unable to mount /system"
"unable to mount /lost+found"
You should continue reading because somehow, no one else was able to fix this.
It's a partition issue. Not all devices are partitioned the same, for some reason.
To fix this, we have to change the ROM's installation script (updater-script) and do the script's work ourselves.
Pre-reqs:
7zip
Notepad++
First, extract the updater-script file from zip file with 7zip:
/META-INF/com/google/android
Now, open the updater-script file with Notepad++.
Press Ctrl+F and find these lines:
Code:
format("ext4", "EMMC", "/dev/block/mmcblk0p21", "0", "/system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p21", "/system");
Delete these lines and save the file.
Move the file you saved into the zip file, in /META-INF/com/google/android.
Replace it.
When installing a ROM from TWRP, you should enter Wipe > Advanced Wipe and select Dalvik Cache, Cache, Data, System and wipe it.
Than, in Mount, remount System.
After that, install the ROM.

Letzen said:
Some people with this device have problems installing a ROM including me. That's because there is some difference in devices even though it seems like they are all the same.
After installing a ROM, if you have these type of messages:
"unable to mount /system"
"unable to mount /lost+found"
You should continue reading because somehow, no one else was able to fix this.
It's a partition issue. Not all devices are partitioned the same, for some reason.
To fix this, we have to change the ROM's installation script (updater-script) and do the script's work ourselves.
Pre-reqs:
7zip
Notepad++
First, extract the updater-script file from zip file with 7zip:
/META-INF/com/google/android
Now, open the updater-script file with Notepad++.
Press Ctrl+F and find these lines:
Delete these lines and save the file.
Move the file you saved into the zip file, in /META-INF/com/google/android.
Replace it.
When installing a ROM from TWRP, you should enter Wipe > Advanced Wipe and select Dalvik Cache, Cache, Data, System and wipe it.
Than, in Mount, remount System.
After that, install the ROM.
Click to expand...
Click to collapse
Bro thank you for the nice guide.
Is new twrp recovery (3.0.2) works for your device???

Sheref said:
Bro thank you for the nice guide.
Is new twrp recovery (3.0.2) works for your device???
Click to expand...
Click to collapse
As far as I remember it worked nicely, but I reverted back to the older one.

Letzen said:
As far as I remember it worked nicely, but I reverted back to the older one.
Click to expand...
Click to collapse
No New TWRP also has this problem you have to reboot recovery after every system format

Gautam Maini said:
No New TWRP also has this problem you have to reboot recovery after every system format
Click to expand...
Click to collapse
Can you explain it detail please.

Sheref said:
Can you explain it detail please.
Click to expand...
Click to collapse
The problem of unable to mount /system is still there in new TWRP . After you perform
1).System Partition Format
2).and Install Rom After System partition Modifications
You still have to follow @Letzen's Guide or reboot after modifications to system partition before installing anything from recovery
Conclusion:- New TWRP is good but still have the old problems