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?
Related
REQUIRE download directory in /cache partition
Hi to everyone,
i'm new in this section i buy today my i9003,
the first problem i encounter when install CM7 is not enought space free when i install app from market , this is my solution without formating cache or anything else
Code:
import com.peaple.disclaimer
i am not responsible for any damage on your phone, Libia war or dead SDCards
Required:
Human brain
Terminal into phone
Rooted
where's the problem?
Market ( Vending.apk ) Download the Temp apk into /cache partition under download directory , but its very small, you can symlink /cache/download to your internal SD to resolve all problem
Solution:
For first determine who create the directorys, what's my internal sdcard?
- if you use codeworkx's kernel it's mounted on /emmc ( or /mnt/emmc )
- if you use Official ROM or XXK* based its /sdcard ( or /mnt/sdcard )
(replace /emmc with /sdcard if you use XXK* Firmware )
Create dir , using File manager in your INTERNAL SDCARD not follow external_sd symlink, create cache directory, and into cache directory create market
Open your terminal, enter su
Allow Superuser request
enter into terminal this command:
Code:
cd /cache
rm -R download
ln -s /emmc/cache/market download
finish!
Offtopic, i'll very help this phone with CM7, it's beatiful phone and needed beatiful android!
Bye
Hey if you know drivers r hardware r smthing ekse needed to port cm7 and other mods to our device..pls help codeworkx and fuss and other devs...
Request
Sent from my GT-I9003 using xda premium
jasspreet said:
Hey if you know drivers r hardware r smthing ekse needed to port cm7 and other mods to our device..pls help codeworkx and fuss and other devs...
Request
Sent from my GT-I9003 using xda premium
Click to expand...
Click to collapse
your request was answered in the last sentence of his post
that's great info, THP! I'll try it next time I'm visiting the market
so we have to type the command everytime we receive the error from market or everytime the phone reboots?
KBS720 said:
so we have to type the command everytime we receive the error from market or everytime the phone reboots?
Click to expand...
Click to collapse
no. Every time you clear the cache
KBS720 said:
so we have to type the command everytime we receive the error from market or everytime the phone reboots?
Click to expand...
Click to collapse
I don't see that in the instructions. meaning, once you use su permissions to direct the market to use your newly created folder in the sd card, which should be able to hold lots more temporary data (based on free space) than the originally intended cache for market downloads, there will be no more "not enough free space" errors. download something big, reset your phone, then download something big again. test it and find out
edit: falex beat me
falex, so clearing cache will clear the instruction from the system's commands?
supergaijin said:
I don't see that in the instructions. meaning, once you use su permissions to direct the market to use your newly created folder in the sd card, which should be able to hold lots more temporary data (based on free space) than the originally intended cache for market downloads, there will be no more "not enough free space" errors. download something big, reset your phone, then download something big again. test it and find out
edit: falex beat me
falex, so clearing cache will clear the instruction from the system's commands?
Click to expand...
Click to collapse
in the instruction we should:
1. remove "download" directory from cache partition
2. create "download" directory in the sdcard
3. create symlink in the cache partition to the created directory
4. clearing the cache just format cache partition (of course formatting will remove everything from cache partition, and out symlink too)
To restore symlink we just should remove "download" directory from cache partition and create symlink (we already have "download" directory on the sdcard)
jasspreet said:
Hey if you know drivers r hardware r smthing ekse needed to port cm7 and other mods to our device..pls help codeworkx and fuss and other devs...
Request
Sent from my GT-I9003 using xda premium
Click to expand...
Click to collapse
Sure, i doesn't have big knowledge about driver and hardware, but i will learn and i had a lot knowledge about linux, kernel compiling, c, c++ and in last time java by school ,time a go i recompile cm7 for Acer Liquid s100 ( another cm unsupported phone ) but nothing to special...
theoretically the only differences between Android and Gentoo or another linux distro is Kernel compiled for arm arch, and build-in driver ( or modules ) if i not mistake
Kernel = C
Lower Level = C++
User App and another app = Java
but i dont think i have knowledge to do this
i can be tester ^^
KBS720 said:
so we have to type the command everytime we receive the error from market or everytime the phone reboots?
Click to expand...
Click to collapse
after this steps , is hard to get another like error , this is permanent fix it's reset only by formatting cache partition, this is our cache partition:
Code:
Filesystem/mount/dev 1K-blocks Used Free Us
3% /cache /dev/block/mmcb1k0p3 1935128 187680 1747448 1
if your format it by recovery, you need to resymlink again
falex007 said:
in the instruction we should:
1. remove "download" directory from cache partition
2. create "download" directory in the sdcard
3. create symlink in the cache partition to the created directory
4. clearing the cache just format cache partition (of course formatting will remove everything from cache partition, and out symlink too)
To restore symlink we just should remove "download" directory from cache partition and create symlink (we already have "download" directory on the sdcard)
Click to expand...
Click to collapse
right, be sure to "swap" it on Internal SD and not external sd :3
hey....codeworkx also need people who have knowledge in c++.and java..yeah..ask him for codes
Sent from my GT-I9003 using xda premium
Because of this post I tried to download a file with nearly 30MB from the android market. As I replied here, it didn't work. I saw this here and wanted to try it out. But when I typed "rm -R download" the terminal emulator trow out a error message. "No such file or directory." (or something like that) What's wrong?
Taraen said:
Because of this post I tried to download a file with nearly 30MB from the android market. As I replied here, it didn't work. I saw this here and wanted to try it out. But when I typed "rm -R download" the terminal emulator trow out a error message. "No such file or directory." (or something like that) What's wrong?
Click to expand...
Click to collapse
Are u in /cache directory when type rm -R download ?
Have you root privileges ? ( just type su )
What firmware do u use?
What market version do u use?
It didn't work because if u not remove old directory , u cant create symlink to sdcard ^^
Codeworkx need programmers
Click to expand...
Click to collapse
in this day im working on Offensive security courses and studying for school, for now i prefer doing tester also becouse i never had programmer linux kernel driver ^^ its too hard for me :3
As my signature suggests I am using a rooted Cranium ROM 3.1 (XXKPH)
The market is version 3.3.11 from here.
Shall I try to move the whole "/cache" folder to "/sdcard/cache" and after that create symlink at root "/"?
Here's the complete story:
{
"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"
}
translated: 'Error when downloading "AppSizeTest 30MB". Not enough free space on your device.'
Yes, I have enough free memory:
ext. SD: 544MB
int. SD: 715MB
other: 1,54GB
Taraen said:
Click to expand...
Click to collapse
This is why the code fails... There is no DOWNLOAD folder in the cache directory. (atleast for us that is, I'm using stock xxkpm with a few scripts btw). Market downloads go directly to the cache folder and not in any other folder/subfolder.
I'm sure your not suppose to remove the cache folder. But why is there a need to remove the DOWNLOAD folder even if it existed? (Sorry, just learning linux) Couldn't we just proceed with linking the cache folder to the sdcard cache?
Correct me if I'm wrong: This is what u enter next after typing "su"
ln -s /sdcard/cache/market cache
I simply tried it out.
Deleting / moving cache folder does not work and so also creating a symlink fails. I also tried to symlink the "downloadfile.apk", since it seemed that this is the temporary file that gets created. I noticed that the icon was the icon of "Font Installer" which was the last app I had downloaded. But when I tried to download the 30MB app my symlink was killed and the market throw out the same error as before.
I'm so sorry, in my xxkph market download apk temp file in /cache/download, i think xxkpm is as directory as xxkph...
KBS720 said:
This is why the code fails... There is no DOWNLOAD folder in the cache directory. (atleast for us that is, I'm using stock xxkpm with a few scripts btw). Market downloads go directly to the cache folder and not in any other folder/subfolder.
I'm sure your not suppose to remove the cache folder. But why is there a need to remove the DOWNLOAD folder even if it existed? (Sorry, just learning linux) Couldn't we just proceed with linking the cache folder to the sdcard cache?
Correct me if I'm wrong: This is what u enter next after typing "su"
ln -s /sdcard/cache/market cache
Click to expand...
Click to collapse
u can not remove /cache directory because everytime u boot system, in cache directory are mount cache partition, i dont know any solution for now, this night i ll download stock xxkpm i'll try
Anyway with MIUI , market version: 3.1.5 there is download directory under /cache , what's your market version? ^^
ok, i found where 's the problem:
i've install XXKPH stock with OLD MARKET
this is problem produce by 2.x market download apk file into /cache instead /cache/download
the only solution is update your market at least 3.1.x
EDIT1: Ok in some cases also update market it continue to download to /cache , i dont know solution , any cases if u have download directory , its ok
I tried 3.1.5, 3.2, 3.3.11 and they all don't have DOWNLOAD folder.
I also tried old market but it auto updates to 3.1.5.
Right now I just installed market 2.3.6 (according to titanium backup) from superteekz1.1 rom.
I used this rom before and extracted the market and it does not update to the newer version. Attached the vending.apk if u wanna use it.
The best feature is that u can install more than 30 mb of app from the market:
Also it doesn't use the have the downloadfile.apk file in /cache. So it doesn't use /cache? Any ideas or explanation?
I'd want to test in t but it crash...
I think it download it into data, but I'm insure
Sent from my GT-I9003 using XDA App
Your right, i found a 28mb downloadfile.apk inside /data/cache. Smaller download files still end up in /cache though.
So the old market seems to perform better at downloading larger market apps... why didn't they implement this in the new version? Maybe because newer phones are expected to have a larger cache?
Btw, if it's a factor, I forgot to mention that my rom is deodexed and the market app from superteekz rom was also deodexed. (sorry, don't know the compatibilities of deodexed and odexed roms and apps)
KBS720 said:
Your right, i found a 28mb downloadfile.apk inside /data/cache. Smaller download files still end up in /cache though.
So the old market seems to perform better at downloading larger market apps... why didn't they implement this in the new version? Maybe because newer phones are expected to have a larger cache?
Btw, if it's a factor, I forgot to mention that my rom is deodexed and the market app from superteekz rom was also deodexed. (sorry, don't know the compatibilities of deodexed and odexed roms and apps)
Click to expand...
Click to collapse
Sorry for this day,i have broken my computer and I buyed new one, and I have problem with ath9k module, Anyway yes there is a difference in oxed or deoxed rom
I'm now using cranium ROM
Sent my GT-I9003 using XDA App
.
Market link: Android Root Toolkit (free)
Root Toolkit for Android™
I wrote this little root utility for myself to help consolidate and automate some root functions that are available in various other apps, but nowhere all together.
Note: this utility does not root your Android device--it assumes that your device is already rooted.
If you are having problems or issues with it, please send me an email at [email protected] with as much detail as you can provide.
FEATURES:
display current root, /system and root (/) mount status, and root save status; will also display bootloader lock status for the Samsung Galaxy Nexus
reboot options (normal, recovery, bootloader)
power off device
remount rootfs (/) and/or /system in read-write or read-only mode; note: remount behavior changed in Android 4.2 and higher that causes remount effect to not be usable by apps other than the one that initiated the remount
save (protect) / restore root function; for 4.2 devices with ext2/3/4 /system partitons, a copy of su binary can be saved and later restored; for 4.3 devices, I've implemented Pau Oliva's 4.3+ "OTA rootkeeper" functionality (i.e., via keeproot.sh)
freeze (disable) or thaw (enable) an application (use caution when freezing a system app!); you can select showing user and/or system apps in the Freeze/Thaw Display Options in the Preferences/Settings menu
display system (getprop) property values
Galaxy Nexus and Nexus 7 (1st gen) only options:
flash a stock recovery
flash various custom recoveries
make recovery "stick" (keep stock recovery from overwriting your custom recovery)
identify currently installed recovery
bootloader lock, unlock, status (Galaxy Nexus only)
option to turn confirmation mode on / off (defaults to on)
option to turn "safe mode" on for the app to prevent any su or flashing operation from occurring
Warning / disclaimer: the author of this app is not responsible for any loss or damage caused by or related to its use.
If you are not comfortable with or knowledgeable about the proper use and functionality of this app, please discontinue its use and uninstall.
Click to expand...
Click to collapse
PERMISSIONS:
INTERNET - for downloading recoveries from the internet
WRITE_EXTERNAL_STORAGE - this is for the downloaded recoveries and work files used to identify which recovery is currently installed
ACCESS_SUPERUSER permission to support interaction with SuperSU
Keywords: root status, root checker, mount status, flash stock recovery, flash custom recovery, reboot recovery, reboot bootloader, power off device, remount system, make recovery stick, identify recovery, save root, restore root, freeze app, disable app, thaw app, enable app,
bootloader lock, bootloader unlock, bootloader status, getprop, system properties
Screen shots:
{
"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"
}
--------------------------------------
Android is a trademark of Google, Inc.
Version 1.3 just uploaded to the Market:
[version 1.3 - 22-April-2012]:
- support freezing (disabling) or thawing (enabling) applications
..(take care before deciding to freeze a system app)
These updates weren't as easy or straight-forward as I had imagined it would be--no wonder there's so few apps out there that have the freeze/thaw feature .
interesting and important tool
I am very interested in this tool and will have a try for sure. Number of questions:
1. Can your tool save current recovery as a blob, which is either cwm flashable or dd flasable(flash through "dd if=/sdcard/recovery_blob_backup of=/dev/block/mmcblk0p4"). My ASUS TF101 is rooted with stock recovery, I would like to try cwm recovery, but I want to save my stock recovery so that I can switch back to stock recovery when OTA is coming.
2. The most important features are those marked as "Galaxy Nexus only options". Is it harmful to try these on other devices such as ASUS transformer.
3. Does it work to use cwm recovery to flash official firmware package without any repacking. How about your tool?
Thanks in advance
---------- Post added at 03:51 PM ---------- Previous post was at 03:30 PM ----------
Two more questions:
4. The su backup made by Voodo rootkeeper is not "immutable", it can be revoced by "chattr -i" and then "rm". how about your backup?
5. If superuser.apk is removed or disabled, does your root protection tool
still work?
Thanks
e154037 said:
I am very interested in this tool and will have a try for sure. Number of questions:
1. Can your tool save current recovery as a blob, which is either cwm flashable or dd flasable(flash through "dd if=/sdcard/recovery_blob_backup of=/dev/block/mmcblk0p4"). My ASUS TF101 is rooted with stock recovery, I would like to try cwm recovery, but I want to save my stock recovery so that I can switch back to stock recovery when OTA is coming.
Click to expand...
Click to collapse
The app will not save a current recovery (not a currently implemented function).
I can tell you I tried copying the currently installed recovery on my GNex using exactly the process you described above. Unfortunately, the flash_image of that copy/backup does not appear to flash properly (and/or I got an error--I think I did get an error when doing the flash and ended-up trying several different versions of the flash_image utility to no avail). The resultant backup/copy of the recovery partition was usually about 12MB vs. approx. 5MB for a "normal" other recovery file that you would flash, so I don't know if its a size issue or limitation with the flash_image utility or not, but flashing a copy of the whole recovery partition did not work for me on the GNex.
I suppose "flashing" via the dd command might / would work, but I haven't yet tried that (dd is scary ).
2. The most important features are those marked as "Galaxy Nexus only options". Is it harmful to try these on other devices such as ASUS transformer.
Click to expand...
Click to collapse
I have product/device checks in the app that should keep those options from even being available to you on the main menu if its not a GNex device. The Setting / Preferences settings will still appear, but if you don't have a GNex, they should not appear on the actual main menu (I'd be very interested to know if they do ).
3. Does it work to use cwm recovery to flash official firmware package without any repacking. How about your tool?
Click to expand...
Click to collapse
My app uses the flash_image utility to flash its recoveries for the GNex. It does not use ROM Manager or ClockworkMod for any flashing operations that it undertakes.
4. The su backup made by Voodo rootkeeper is not "immutable", it can be revoced by "chattr -i" and then "rm". how about your backup?
Click to expand...
Click to collapse
Yep, works exactly the same .
The immutable property is apparently only supported on the ext2/3/4 type of filesystems (I think that's the right list)
5. If superuser.apk is removed or disabled, does your root protection tool
still work?
Click to expand...
Click to collapse
I never specifically tested removing Superuser.apk, but you should/would still be able to re-download that app from the Market and install it to complete the second half of root (the first being restoration of the su binary).
~ ~ ~
You should know that the GNex-only options that I support in the app were basically because I own a GNex and wanted to support some functions that I got tired of doing via other apps. Supporting devices other than the GNex is not currently in my plans since it these things are very device- and recovery-specific and I wasn't comfortable releasing features and functionality that I could not directly test and validate myself.
Cheers!
Thanks for the explanation. Where can I find the flash_image utility, is it device spacifilc? If it is not your self-made component, can you give me a copy of the utility.
e154037 said:
Thanks for the explanation. Where can I find the flash_image utility, is it device spacifilc? If it is not your self-made component, can you give me a copy of the utility.
Click to expand...
Click to collapse
Ah, there's a billion copies of it "out there", but you should be able to extract if from the .apk file of my app if you want.
Just make a copy of .apk file (its really just a .zip file, after all). Then use a file explorer or unzip utility and explore res/raw folder (I think that's where it is).
It should work on all Android devices (I've got/found multiple copies and versions of various ages and sizes that I'm sure are due to the different builds of Android).
The key thing you need to be careful of is making sure you've got the proper partition / area that you are going to be flashing to (i.e., the recovery partition is not located in the same place / name on every device and there's no way (that I'm aware of) to universally describe how to identify it (short of looking in the build code for your specific device)). Flashing a recovery to the boot partition is a quick and easy way to brick your device .
Also, making sure that you've verified that integrity of the file you are flashing (i.e., via and MD5 or SHA1 checksum) is always a good idea. There's no inherent checksum / integrity check done by the flash_image utility--it'll flash anything to anywhere you tell it (or at least try to).
All due caution and a current Nandroid backup is always your best friend .
Cheers!
Thanks.
Stupid me! I should have realized that the tool could be extracted from your apk or for ROM manager.
Question on image file used in flash_image:
Asus official firmware package's zip file contains a file "blob", unpack the blob one can find a number of images, including blob.SOS. This blob.SOS is the stock recovery image. To my knowledge, blob.SOS should be repacked when being flashed with dd.
Is this blob.SOS (witout any repack) the right one goes with flash_image (flash_image recovery /sdcard/blob.SOS)?
e154037 said:
Thanks.
Stupid me! I should have realized that the tool could be extracted from your apk or for ROM manager.
Question on image file used in flash_image:
Asus official firmware package's zip file contains a file "blob", unpack the blob one can find a number of images, including blob.SOS. This blob.SOS is the stock recovery image. To my knowledge, blob.SOS should be repacked when being flashed with dd.
Is this blob.SOS (witout any repack) the right one goes with flash_image (flash_image recovery /sdcard/blob.SOS)?
Click to expand...
Click to collapse
LOL, no worries! (I've had more than my share of those moments )
I'm not familiar with the Asus .zip package formats or the blobs.
But, I would think you could verify that you are talking apples-to-apples (so-to-speak) if you were to calculate the MD5 of a current blob recovery file with an extracted dd dump of the currently installed recovery's MD5 file (i.e., find the published blob that should match what you have installed; if they match, then you are on the right track, otherwise, you'll have to re-evaluate and dig a little deeper).
Cheers!
Says i dont have superuser.apk but i do ..
Sent from my VS910 4G using xda premium
motodroidfreak said:
Says i dont have superuser.apk but i do ..
Sent from my VS910 4G using xda premium
Click to expand...
Click to collapse
Hmm, do you know where it's actually installed (i.e., the full file path)?
My app checks for "Superuser.apk" or "SuperUser.apk" in the /system/app directory.
Lemme know where yours is installed and I'll make a quick tweak .
Cheers and thanks!
Android Root Toolkit: updated to version 2.6
New version just published to the Play Market...thanks!
Here's the most recent change log items:
[version 2.6 - 08-December-2013]:
- support save root for 4.3+ devices (credit/thanks to Pau Oliva (poliva) and Chainfire)
- fix FC caused in some devices that return weird (non-standard) Android version information
- 2012 N7 only: support 4.3 (jwr66y) and 4.4 (krt16s) stock recoveries
- Samsung Galaxy Nexus only: support recent stock recoveries for international and Sprint versions
- address transitory mount behaviour that apparently started in Android 4.2 and up
- display warnings for keeping a pre-4.3 saved root present before installing a 4.4+ OTA
- lots of other minor tweaks, cleanups, and enhancements
Click to expand...
Click to collapse
Hi all MTK6573/MTK6516 users !!!!
SEE SECOND POST FOR MTK6516 phones.
THIS POST IS FOR MTK6573 phones.
This is for all MTK6573 users with Android 2.3(.x). Also for all B63M phones !!
Follow this guide to backup your FULL ROM !! You can even flash your phone through FlashTools with this COMPLETE backup !!!
ROOT IS REQUIRED !!
Here is the guide:
1) ROOT is necessary. It is recommended to put the phone in 'Airplane mode' so that it won't disturb the process and make sure you have ~500 mb space in SD card.
2) Download 'MTK-6573-BackUpTools.rar' from attachments and extract it to your SD Card. You'll have 2 folders - 'gscript' and 'Install'.
3) Install 'GScriptLite.apk' from gscript folder.
3) After installation, open the 'GScriptLite' application -> Menu -> Add Script.
4) Tick 'Needs SU ?'
5) Click 'Load File' and select 'Back23.sh' and then select 'save'
6) Now Click on 'Back 23' and Super User will ask for Permission and allow it. Nothing more to touch. Wait for few minutes. After few mins, it will say 'Auto Close is Cancelled'. Now its safe to close.
7) Your Back-Up will be in 'backup_' folder located in your SD card's root.
It will have files named ' firmware.info, preloader.img, nvram.img, seccnfg.img, uboot.img, boot.img, recovery.img, secstatic. img, misc.img, logo.img, expdb.img, cache.img, system.img, data.img' in that folder. Copy it to your computer and keep it at a safe place. More Over if you are posting in the forums or sharing it online, don't include ' data.img, cache.img and nvram.img' as they contain your personal information.
NOTE: The backup script is not created by me. Gathered all information from the web !!
Hit THANKS if you find this useful !!
For MTK6516 !!
THIS POST IS FOR MTK6516 phones.
This is for all MTK6516 users with Android 2.2(.x).
Follow this guide to backup your FULL ROM !! You can even flash your phone through FlashTools with this COMPLETE backup !!!
ROOT IS REQUIRED !!
Here is the guide:
1) ROOT is necessary. It is recommended to put the phone in 'Airplane mode' so that it won't disturb the process and make sure you have ~500 mb space in SD card.
2) Download 'MTK-6516-BackUpTools.rar' from attachments and extract it to your SD Card. You'll have 2 folders - 'gscript' and 'Install'.
3) Install 'GScriptLite.apk' from gscript folder.
3) After installation, open the 'GScriptLite' application -> Menu -> Add Script.
4) Tick 'Needs SU ?'
5) Click 'Load File' and select 'Back23.sh' and then select 'save'
6) Now Click on 'Back 23' and Super User will ask for Permission and allow it. Nothing more to touch. Wait for few minutes. After few mins, it will say 'Auto Close is Cancelled'. Now its safe to close.
7) Your Back-Up will be in 'backup_' folder located in your SD card's root.
It will have files named ' firmware.info, preloader.img, nvram.img, seccnfg.img, uboot.img, boot.img, recovery.img, secstatic. img, misc.img, logo.img, expdb.img, cache.img, system.img, data.img' in that folder. Copy it to your computer and keep it at a safe place. More Over if you are posting in the forums or sharing it online, don't include ' data.img, cache.img and nvram.img' as they contain your personal information.
NOTE: The backup script is not created by me. Gathered all information from the web !!
Hit THANKS if you find this useful !!
A few questions!
Hello!
Thank you for this software, it worked with making a dump of my rom. How do you create a scatter file to use in SP Flash Tool? Or do you have another program that I can use to flash these files back onto the phone?
The SP Flash Tool I am using V2.1129.00 does not show as many partitions as what was backed up by my phone with the default MT6573 scatter file that it comes with.
I keep getting errors trying to load/burn the files to my phone.
PLEASE HELP!!
LeStonga said:
Hello!
Thank you for this software, it worked with making a dump of my rom. How do you create a scatter file to use in SP Flash Tool? Or do you have another program that I can use to flash these files back onto the phone?
The SP Flash Tool I am using V2.1129.00 does not show as many partitions as what was backed up by my phone with the default MT6573 scatter file that it comes with.
I keep getting errors trying to load/burn the files to my phone.
PLEASE HELP!!
Click to expand...
Click to collapse
You can try this:
Copy the backup_ folder from your sd card to your computer. Now place a copy of a the scatter file.txt in that folder.
Now in SP Flash tool, browse to the folder and select the scatter file that you placed.....all files will be loaded automatically......
It didnt work . . .
Hello!
I took your advice and attempted to load the scatter file from the same folder that the backup partitions are in.
A few of they files loaded on their own, not all of them, and their are still partitions missing.
When I open the scatter file in txt editor it shows all partitions.
When I open the scatter file in smart phone flash tool i only show
preloader
dsp
uboot*
bootimg*
recovery*
secro
logo*
android*
usrdata
The files above are what shows in sp flash tool program and the ones with the * are the files that load automatically.
I did try a smart phone flash tool version 5.1140 and the scatter file did load correctly with all the partitions, but again not all load and I get an error when I try to load them manually. In addition, I have never been able to successfully use version 5.1140 to flash.
I was able to flash in version 2.1129, but as I said I couldnt load every partition so I am missing my nvram and other partitions.
Can you recommend anything else?
Maybe a different version of sp flash tool that you know works? Maybe a different program all together?
THANKS!
@Bala
Yo, bro, its been awhile since our last chat ! You have been like an android modding/ hacking teacher/ guru & i'm sure alot of users will benefit from all of it...
@LeStonga
Yes, in fact your are correct, there is a software by linerty(these russians are so 'terror', not only hacking but coming out with tools to make it easier) that converts the extracted firmware.info back into scatter.txt...You can find the tuts & tools here.
The tuts even show you ways to upload with FlashTool too ! i know there is an upload function but never knew the way to use it though...
Hello balamu96m!
Thank you for your suggestions, that was the website which I first followed instructions for.
As you can see however, even when Bruno (administrator of the tutorial you provided in the link) opened his scatter file, nvram partition is not shown. I was able to use the program balamu96m pointed me to and it made perfect backups of all my partitions.
My problem is that sp flash tool loads my scatter file and it is the same as Bruno's which is lacking several partitions, especially the nvram partition.
If i use an updated sp flash tool (v5), when I load my scatter file all of my partitions are shown, including nvram, but I have never had any success flashing my phone with that version.
Maybe I can use that version but someone has to help me set up the configurations to flash . .. i.e. download with or without battery, com, baud rate, etc.
Sp flash tool V2.11 was easy to use and straight forward, but even though my scatter lists all my partitions (when i open in a text editor), it only loads the partitions shown in bruno's tutorial, not including nvram.
yuweng said:
@Bala
Yo, bro, its been awhile since our last chat ! You have been like an android modding/ hacking teacher/ guru & i'm sure alot of users will benefit from all of it...
@LeStonga
Yes, in fact your are correct, there is a software by linerty(these russians are so 'terror', not only hacking but coming out with tools to make it easier) that converts the extracted firmware.info back into scatter.txt...You can find the tuts & tools here.
The tuts even show you ways to upload with FlashTool too ! i know there is an upload function but never knew the way to use it though...
Click to expand...
Click to collapse
Hi yuweng bro!
It seems miui is going to release their source code........i read in the russian forum at 4pda that one mtk6573 was running miui 4 (ics).......is that true??
So when miui sources are out, can we build one for our mi-357/350n??
Waiting for your reply
@Bala
AFAIK, Miui public part of their source code before the launch of their first android phone, Xiaomi M1 & now launching their next version M2 which is based on ARM Cortex-A8 & coincidentally, its just been launch today ! Its fully supported by the Miui team & it has two ROM, one ROM for daily use & the other one for you to flash their 'nightly' built. Best is that you can switch over to either one of them at any time ! Great for android enthusiastic...
However, of all hundreds over MT65xx android phone manufacturer all over the world, non of them actually ported it to Miui ! There is only one answer to this, it will be copied over to all other MT65xx ! Thats what Chinese are best at...(Oopps, i'm a Chinese too...)
So, i think you won't see an official Miui phone on MT65xx platform... Currently, official Miui ROM is for single SIM... You can check out Miui sources here & here
If its really true that the russian has ported Miui to MT65xx, very soon we'll have Miui running on every MT65xx...
What you said on the other thread is true, if Mediatek keep on keeping their source code, i think very soon they can keep it to themself forever.... No android enthusiastic will ever buy their phone ever... Even HTC has released the source code for a whole bunch of devices recently after been pressured by android enthusiastic...
@LeStonga
AFAIK, FlashTool is not for flashing NVRam(IMEI). However, you can use it to backup NVRam then restore it. Typically, you only need to download boot, recovery, logo, android, usrdata. Normally, i just download 'android' partition only(system.img) I normally put a 'tick' at 'No Action' for NVRam...
{
"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"
}
There is a thread on how to backup & restoring your MT65xx IMEI by cybermaus just over a week ago...
help help
I have android phone china H4300. mediatek mtk6573. yesterday , i deleted stock launcher and format factory the phone. so i don't use it.
please help me up rom (i haved rom) or install the Launcher ,...
thank you
vanlaosonya said:
I have android phone china H4300. mediatek mtk6573. yesterday , i deleted stock launcher and format factory the phone. so i don't use it.
please help me up rom (i haved rom) or install the Launcher ,...
thank you
Click to expand...
Click to collapse
Do you have modded recovery??
balamu96m said:
Do you have modded recovery??
Click to expand...
Click to collapse
i only have stock recovery
Thanks it works on my MT6573 phone
Hey balamu....
Can you please tell me how to restore this backup...???
maitreyapatni said:
Hey balamu....
Can you please tell me how to restore this backup...???
Click to expand...
Click to collapse
Allow me to answer ...
To restore this backup, 1st you need to convert the firmware.info into your own scatter.txt file. Read here : http://bm-smartphone-reviews.blogspot.com/2012/04/creating-rom-dump-of-your-mt65x3-device.html
Then you run SPflash tool, choose your scatter file and the appropriate area to flash. You don't need to flash all area. Just boot+system (android) to restore is sufficient. You can change the file by double-click at the appropriate row. Untick to deselect, tick to select which area to flash.
Again, no need to flash the whole thing ... some file contains private info such as nvram/userdata. I've read that many device already bricked by flashing wrong file (specially uboot) unless it's from your own backup.
no cache.img, system.img, data.img
hi balamu, i need some help.
i have an mt6516 phone. i followed every step, but 3 files didn't show up i.e cache.img, system.img, data.img
in the end of running script, gscript show "no such files". my question are: is that normal? are those file important? any ideas to get these files?
i really need any help here.
so thx in advance
hisoka8888 said:
hi balamu, i need some help.
i have an mt6516 phone. i followed every step, but 3 files didn't show up i.e cache.img, system.img, data.img
in the end of running script, gscript show "no such files". my question are: is that normal? are those file important? any ideas to get these files?
i really need any help here.
so thx in advance
Click to expand...
Click to collapse
they are really important...................you can retry the process again.......it should work.....!
silly me
found out the problem. looks like i didn't do exactly one of your step "extract into sd card". i actually extract the content into a folder inside the sd card, so gscript can't find the "Install" folder. I copied the folder into sd card and redo the process then those file showed up. LOL.
anyway, nice share... :good::good:
n7000 note copy rom file i loss it help
n7000 note copy rom file i loss it help
mtk 6573
plz send rom file
mail id [email protected]
thanks in adwance
Hi,Thanks for tutorial,I backup my phone,create scatter file and all goes ok but now i have 1 litl problem,my phone is mobiwire aquila mt6573 platform, he got factory recovery e3 and i wanna change to cwm and Bruno say that cwm must be specific for phone so is any chance to find cwm for my phone or any hack/swap from backup recovery or any other method?
Sorry guys on bad english or wrong section
Thanks
The script is now completely rewritten and a lot easier to use.
This is the general walkthrough for this script, if you have more questions than this answers please ask in this thread.
Download and unpack the script to the root of your sdcard, the easiest way to do this is to download it to the root of the sdcard and do the following:
1. start terminal session
2. cd /sdcard
3. tar xvf MakeLoopROM-Android-V11.tar
===============================================================================================================================
NEW! READ THIS! - The original ROMs and Packages are now stored in /sdcard/MakeLoopROM/original-roms and /sdcard/MakeLoopROM/original-packages. Copy the ROMs and packages
that you want to convert into those folders!
===============================================================================================================================
Ok, once you're done there you're ready to start the script, it's now completely menu driven.
1. start terminal session
2. cd /sdcard/MakeLoopROM
3. sh startup
That will start up the menu, for a new ROM work your way from 1 - 4 to make your first loop ROM, at the end of 4 it will be ready for installation, for upgrades that install into
existing loop files (that you have made once with step 1) start at step 2.
The menu options and how they work:
1. Make system, data or both loop files
This option will allow you to do just what it says, make the system and data images you'll install your ROM into, it's very
straightforward but i'll give a brief summary of how
it works.
"Do you want to make an image file to hold the system for this ROM? (not neccessary if it's an upgrade from a previous ROM) Y
for yes N for no."
Pretty straightforward, if you don't have a system loop file enter y for yes, if you're going to upgrade then running this
step is completely unneccessary but since you have
chosen to run it, press no.
"What do you want to call your system image? (give it a name you'll remember, like cm-7-system for a cm-7 loop install)"
Name the system loop file, call it whatever you want but make it something relevant to the ROM or you'll end up wondering what
that file is for when you stumble upon it at a
later time. it'll be stored under /multiboot/system-loop-files when it's done.
"What size do you want your system image to be (in MB's)? (WARNING: if you make it too small your ROM +other packages like
gapps might not fit, make it 250)"
The size of /system for the loop ROM, read the thread you downloaded the ROM from to find out what size is ok, i just use 250
for everything in case i want to reuse it with full
at a later time.
"Do you want to make an image file to hold the data for this ROM? (not neccessary if it's an upgrade from a previous ROM or
you want to share a data image with another ROM)
Y for yes N for no."
Same as with the system loop file, if you don't have one, you'll want one, if you're upgrading you shouldn't be running this
step but there is another time when you want to say
no to this, when you want to share a loop file with another installation (not with NAND ROMS). Like for example if you want to
share the data partition between CM-10 and PA-JB.
"What do you want to call your data image? (give it a name you'll remember like cm-7-data for a cm-7 loopinstall)"
Same as for the system loop file, just name it something relevant, the name is of no importance to it's function.
"What size do you want your data image to be (in MB's)? (This file will hold all of your data, don't skimp on the size)"
How many apps do you plan to install? 10 - 50 - 500?
Make it a size that you can live with and that will fit on your sdcard, it really depends on how many apps you'll install.
2. Make a Loop ROM
It's exactly what it says, this will make your loop ROM ready for installation.
"Available ROMs:"
just enter the number that's next to the ROM you want to convert, if it's not there it's because you didn't copy it to /sdcard
/MakeLoopROM/original-roms, you can do so now and
hit r to refresh the list.
"You previously created the system loop file [nameofyourfile], do you want to use it for this ROM? (y/n)"
You'll only get this question if you created a system loop file by going through step 1. If you did so and that's the file you
want to use (check the [nameofyourfile]) then
answer y for yes, otherwise you answer n for no and the following question comes up.
"Available system loop files:"
This choice will only come up if you answered no to the previous question or didn't make your system loop file with the script
in step 1 during this session. Anyways, just enter
the number next to the file you want to use as a system loop file.
"You previously created the data loop file [nameofyourfile], do you want to use it for this ROM? (y/n)"
See the system loop file above, this is the same but for the data loop file
"Available data loop files:"
See the system loop file above, this is the same but for the data loop files
Do you want this installation to format the data image used with this ROM?
Answer Y for yes if it's a new installation and N for no if you are upgrading
and want to keep the data on the data image. (Say yes if you would run wipe
data/factory reset in recovery if this was a normal install)
Y if this is a new install or you're reusing an old data loop file that you want to wipe.
when done hit enter to get back to the menu.
3. Make a loop package (such as gapps)
This, like it says, is for converting non-rom packages (not kernel packages though) such as gapps or bravia or what have you.
"Available packages:"
type the number that is next to the package you want to convert, if the package isn't there you didn't copy it to /sdcard
/MakeLoopROM/original-packages
"You previously created the system loop file [nameofyourfile], do you want to use it for this ROM? (y/n)"
You'll only get this question if you created a system loop file by going through step 1. If you did so and that's the file you
want to use (check the [nameofyourfile]) then
answer y for yes, otherwise you answer n for no and the following question comes up.
"Available system loop files:"
This choice will only come up if you answered no to the previous question or didn't make your system loop file with the script
in step 1 during this session. Anyways, just enter
the number next to the file you want to use as a system loop file.
Repeat No. 3 for all your packages
4. Make (or update) NAND boot image.
This will read the information in your boot partition and store it as boot.img under /sdcard/multiboot so you can boot back to
your NAND installed ROM by running step 6 or
flashing nandboot.zip (also stored under /sdcard/multiboot) from cwm.
Run this every time you update your NAND ROM so the boot.img is fresh.
"This script will update your nand boot.img in the multiboot folder to the version of boot.img you're currently running, make
sure you're running the updated ROM and not
a loop ROM before hitting Y for yes here. If you're not sure type N for no."
If you updated your NAND ROM or haven't run this option before you have to say y for yes here, you have to run this option at
least once or you can't boot back to NAND. Just
make sure you've got your NAND ROM booted and not a loop rom because this will take the boot partition content of your
currently running ROM.
5. Remove a loop installation
If you've come this far you know what you're doing in this option. I'm not going to go through all combinations but they are
self-explanatory.
6. Boot an installed ROM.
Exactly what it says, just remember that even non-installed ROMs may be listed here, if you happen to try to boot to one of
those it will hang at boot, in that case, pull the
battery, reboot to recovery (press and hold vol down while you press power) and use the boot zips that have been created for
your roms.
the Boot zips are located in /sdcard/multiboot/nandboot.zip for the NAND and /sdcard/multiboot/loop-roms
/[namofyoursystemloopfile]/[nameofyourROM]boot.zips
I think that's all, if there is any questions, feel free to ask.
Android version: MakeLoopROM-Android-V11.tar
MD5: 1b33ad6c3078711444c01867e436b65a
===============================================DEPRECATED==============================================================
It took a while but i managed to sort out how to boot to loop filesystems stored on the SD-card.
This means that you don't have to partition anything and you can have as many ROMs installed as you can fit on your SD-card.
You don't have to worry about a2sd/S2E/mounts2sd or anything like that (just make your data partition large enough to hold your apps, you can share the data partition between as many loop ROMs as you like) but this doesn't prevent it either, your sd-ext partition will be untouched and mountable by any ROM you install into a loop file (if the ROM supports sd-ext, that is). Swap will work just fine too.
The script is self explanatory but there are a few things it doesn't explain so i'll explain it here.
Here we go:
1a. Download the MakeLoopROM(version).zip and unpack it to any directory of your choice, just remember where you put it, if you're going to do this under cygwin i suggest you put it in a directory that is easily accessible from the cygwin terminal (IE cygwin/home/"yourusername") and if you're using Linux, just unzip it to your home directory.
1b. Download the MakeLoopROM-Android.tar and unpack it to the root of your sdcard or copy the file to the root directory of your sdcard, open up a terminal session and run tar -xvf MakeLoopROM-Android.tar.
2. Copy the rom and gapps and whatever other package you want to convert to the MakeLoopROM directory that was created during the unzipping above.
3a. In Linux, open up a terminal, cd to the MakeLoopROM directory and type sudo ./makelooprom (losetup requires root permissions).
3b. In windows, open up the cygwin terminal, cd to the MakeLoopROM directory and type ./makelooprom-cygwin
3c. On Android, open up a terminal session, type su and hit enter, type cd /sdcard/MakeLoopROM and hit enter and then sh mkrom and hit enter.
4. Follow the instructions, it should be easy enough to understand.
5. If you want to convert a gapps package and/or other packages you repeat step 3 but type ./makeloopgapps instead of ./makelooprom it'll work for any package you want to install into your loop files, root is not needed for this step.
5a. For android you type sh mkgapps to make gapps and other packages.
6. To be able to reboot back to NAND (the ROM on your phones internal storage) you need to copy the boot.img of your current ROM into the multiboot directory.
6a. The android version now copies the running boot.img if you answer yes when you get the question if you want it to so there is no need to copy it in another way.
After you're done converting your ROM and the packages you'll find all important stuff in the multiboot folder within the MakeLoopROM directory, just copy the whole folder to the root of your SD-card (if you are running on android this step is unneccessary, the script will copy the files for you). You'll find your image files under multiboot (if you created them) along with the "nameofyourrom"boot.img and boot"namofyourrom".sh that you'll need to boot into the ROM from another ROM and finally under loop-roms/[nameofyoursysimage] you'll find all your converted ROMs and packages, ready for installation.
Now you're ready to install the loop ROM and the loop packages, it installs like any other ROM/package via your recovery of choice (I recommend my CWM Touch 6.0.1.1, it's what this is tested on but it should work fine on any recovery).
To switch between ROMs you open up a terminal window, type su to get root permissions, cd to the multiboot folder (cd /sdcard/multiboot) and type sh bootnand.sh to switch to your internal ROM or boot"nameofrom".sh (bootcm-7.2.0-blade.sh if you installed cm-7.2.0-blade for example) for any of the loop roms. You can also install script manager and script manager widgets and make widgets for those scripts on your homescreen, that way rebooting to another rom is as easy as pressing the icon on your homescreen.
I'm sure there'll be a lot of questions about things i haven't thought of, but if you should fail or do something wrong then just hit ctrl-c and start over, the script cleans up and restarts the build.
Thanks to:
[email protected] for some ideas.
championswimmer for some scripts from his Kernel Kitchen.
Tilal for suggestions that helped fix running this script on the phone itself as well as the app he's making to make reboots between the different installs much easier and better.
[email protected] for being a very patient tester.
Files:
Linux version: MakeLoopROM-Linux.tar
MD5: 8907e2519276f4abcbb5bab0de168ae5
Windows Cygwin version: MakeLoopROM-Windows.zip
MD5: 096921e7a08eba98329bb7ec486068f0
Android version: MakeLoopROM-Android-V8.tar
MD5: f4ee326faf65bd032a95a1e2b4e8bc9f
25/10:
* Completely rewritten, it's now entirely menu driven with choices so you don't have to type filenames.
* Fixed faulty boot flashing
* Now copies a flashable zip of each loop ROM and NAND ROM boot images to /sdcard/multiboot for NAND and /sdcard/multiboot/loop-roms/[nameofyoursystemloopfile/[nameofyourrom]boot.zip so you can flash it via CWM if you need to.
* Includes a cross compiled version of bash for arm to fix a lot of scripting problems.
12/10:
* Streamlined, a LOT faster now.
* Possible fix for the random faulty boot.img flashing when switching between ROMs, need feedback on this.
* Removed unnecessary file creation (all of it runs within one loop file and questions (if you create the system and data images you won't get the question twice, it checks if your ROM is a JB rom without your interference).
* Added cleanup script, to use it run sh cleanup as su and follow the instructions.
* Lots of other bits and pieces that makes it safer and faster to use.
3/9:
* Fixed the Android version to work with CM7 roms [changed let=size to size=$(expr], thanks to Sulthekk for the heads up on that
* Added a failsafe to the Android version on creation of system loop file if it already exists and on giving the script a name for system and data image that doesn't exist. You get one retry, if you can't get it right after that... It is possible to multitask on android, just open a file manager if you forgot the name of the system or data image.
* Fixed the Linux and Windows versions to work with JellyBean ROMs, thanks to jpeg729 for the heads up on that
* Change the file names to reflect which version is which
1/9:
* Finally fixed the problems with no permissions running the script on some ROMs.
1/9:
* Added the choice to copy your currently running roms boot.img to your multiboot automatically, no user interaction needed for the process.
31/8:
* Changed the android version to a tar to keep file permissions intact.
* Fixed it up so it runs on CM-10 and PA as well as all other roms (i hope).
30/8:
* Release of the Android version, now runs completely on your phone.
28/8:
* Changed the Linux version to tar format to ensure that permissions are correctly set.
* Fixed the Cygwin version so it can make the data and system image files, they will be formatted on install and if it's a new installation you have to choose y to format the data image file or it will not have a filesystem.
* Changed a few misspellings in user interaction texts and tried to make it easier to understand.
Woah. Cwm and Multiboot in a week's time?
When you getting your RD status?
Good work man
Sent from my Ouya
QuantumFoam said:
Woah. Cwm and Multiboot in a week's time?
When you getting your RD status?
Good work man
Sent from my Ouya
Click to expand...
Click to collapse
I've got one third project that i'm about to wrap up and after that i'll just do incremental updates on those three while devoting my time to kernel development which is sorely needed.
Found a util for windows called winDD, i'll check it out and include it in the next version if it's of any use. That will fix the problem with not being able to create the loop files on windows.
I've built makebootfs and makebootimg for android and will include them along with a script that works on android in the next release.
I'll make the next release a tar version along with a zip version for windows users, this is to preserve file permissions.
Any other suggestions are most welcome.
After a lot of issues i finally got the Android version ready, i've tested it and it works fine on my phone, both the makelooprom-android and the makeloopgapps.
I had to cross compile perl and the mkbootfs and mkbootimg files to run on armv6l which took a while because i kept getting errors, both are included with the script.
Then there was a problem with running split-bootimg.pl on the sdcard, fat32 doesn't support symbolic links so i had to make three different loopfiles within the script to use for bootimg-contents ramdisk-contents and output.
Anyway, now it runs just fine, try it out.
New version up and running.
Only for zte blade ?
Sent from my B15Q using XDA Free mobile app
- Dual booting is the process through which you can switch between any two or more roms without the need of wiping data or making backups before flashing, all you need to do is switch between the roms, meanwhile all the apps you've installed remain intact in their specific rom.
Click to expand...
Click to collapse
Strictly put forth by Developers for Developers! If you are inexperienced with Android Development then proceed forward with extreme caution! As for the experienced, this will be easy for you.
***DISCLAMER***
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. YOU are choosing to make these modifications!
Click to expand...
Click to collapse
As always, do anything at your own risk. The above warning/disclaimer is only there because unfortuantely there will be someone who messes this up. The following guide will be conducted straight from the phone so if you are more comfortable using a computer then you will need to adapt this guide to your prefered surroundings. Please insure you have multiple ways to go about restoring your device in case you failed to follow the instructions or misunderstood something within the instructions - A Nandroid Backup, and/or RUU, and/or a ROM fitted for your specific device which you can apply via adb sideload.
Credit goes to @dreccon for bringing this to my attention with a more clear understanding over at his thread,
[GUIDELINES]Dual-Boot on (theoretically) any Android device. He was very helpful to opening my mind and thus putting up this thread. This thread is initially based around working with K2 Variant devices, but I am also aware that this will work on many other devices too.
The following numbers I will be using for partitioning the SD Card is based on maximum used space from a Stock Rom of my own K2_CL device using 4.1.2 Jelly Bean! These numbers are not to be taken literally, so USE COMMON SENSE, and insure you know the sizes for your System, Data, and Cache Partitions!
To determine the proper sizes of your partitions you can use the apk called, Partition Table, mentioned for requirements below. That APK is literally self explanatory so I will not be going over it. You will use this APK to determine the size of each partition and its current format. Do this and take note of them.
The Secondary Rom should be equal to or greater than the Primary Rom OS.
Requirements:
Device SPECIFIC boot.img and custom recovery.img
A text editor of the sorts - I use Quoda Code Editor
A Class 6 or better SDCard (I am talking about the external)
Partition Table from the Play Store
Working roms for your device
A compression tool (I use ZArchiver from the Play Store)
AParted (SD Card Partition) from the Play Store
Steps:
A. PARTITIONING YOUR SD CARD:
Plug your memory card (SD Card) in to your computer using either a card reader or by plugging your device in via usb, and copy everything from it over to your PC as we are going to partition your SD Card (which means it WILL be wiped out). Be sure to unmount your device from your pc if plugged in via usb or any other known method.
Unmount your SD Card on your device by going to, settings > storage > unmount sdcard,on your phone and then proceed to open up the apk, AParted.
Grant root access when prompted. Decline the "Agreement" because it will just try to install junk. Tap configuration, then tap the drop box under Detected devices. You should see mmcblk0, mmcblk1, and usbdisk. If you don't have both "mmcblk0", & "mmcblk1", then stop here, because either something is wrong on your end or this guide isnt for you. If you do, then select mmcblk1 from the list, tap Save, then OK. Tap TOOLS, you should now see parts 1 through 4. "Part: 1" should say fat32, and say the size in MB of your external SD card. If it does, then tap the checkbox next to "Part: 1", next tap the drop box that says Create, select Delete and tap apply. Once done, all parts should say empty. We're going to create 4 partitions. The first partition is going to be the standard external sd partition that will show up in both roms. Tap Create on the top, tap "+", tap the box with "0MB" in it, set it to the size you want the card to be, keeping in mind, that we need space for the second ROMs' partitions. Repeat these steps for System, Data, and Cache as seen below and once completed you will tap the menu button, and tap Apply changes, when done we are finished with the partition setup.
Partition it as followed:
First Partition-FAT32 (total memory card size - I recommend at least 20mb or more depending upon the actual size of your SD Card as a whole) <----- SD CARD
This is the space you will see as your memory card (external sd) in both of your roms (Primary and Secondary).
Second Partition-EXT4 (1339mb) <------ SYSTEM
This will be the System Partition of your Secondary Rom
Third Partition-EXT4 (1165mb) <----- DATA
This is Data Partition of your Secondary Rom, apps will go here
Fourth Partition-EXT4 (220mb) <----- CACHE
You can reduce it a bit more if you want to.
B. PREPARING SECONDARY ROM'S ZIP:
Get the updater-script of the rom you want to dual boot and open it up using Quoda as mentioned in the requirements or with anything else similar to a text editor which won't disrupt the unix coding of that file when you save it later.
SEARCH FOR-mmcblk0p35 (may vary for different devices, look for "mount("ext4", "EMMC", "/dev/block/mmcblk0p35");" in the updater script in order to know what yours is)
Replace with-mmcblk1p2
Save it and move it back to its location in the rom zip (META-INF\com\google\android).
Note: if there is a data folder in the rom's zip then you also have to replace the data partition block with mmcblk1p3, like: mmcblk0p37-->mmcblk1p3
C. PREPARING SECONDARY ROM'S BOOT.IMG:
Unpack the boot.img of the rom you want to dual boot using the proper unpacking and packing binaries. This can be done using your PC and/or phone. There is also the dsixda Kitchen via Windows using Cygwin and/or Linux. However, my guide will be based on doing this directly from my phone so for those who qualify may use this thread - Unpack, Edit, Repack Boot.img/Recovery.img. Otherwise, you will need to approach this differently.
You will need to go through all files which are feasible to view and read within the ramdisk of your boot.img.
Then find and replace:
Find-[email protected]
Replace with-/dev/block/mmcblk1p2
Find-[email protected]
Replace with-/dev/block/mmcblk1p3
Find-[email protected]
Replace with-/dev/block/mmcblk1p4
Save all the files that have had these changes made to them and then repack the ramdisk with the kernel to your new dualboot.img.
D. PREPARING SECONDARY ROM'S RECOVERY (OPTIONAL IF YOU DON'T WANT TO CHANGE THE SECONDARY ROM AGAIN):
Unpack the recovery.img like you unpacked your boot.img and open '/etc/recovery.fstab'.
Edit from this (May vary with other devices):
Code:
# mount point fstype device [device2]
/boot emmc /dev/block/mmcblk0p20
/cache ext4 [COLOR="darkred"]/dev/block/mmcblk0p36[/COLOR]
/data ext4 [COLOR="darkred"]/dev/block/mmcblk0p37[/COLOR]
/devlog ext4 /dev/block/mmcblk0p25
/misc emmc /dev/block/mmcblk0p22
/int_sd vfat /dev/block/mmcblk0p38
/recovery emmc /dev/block/mmcblk0p21
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/system ext4 [COLOR="darkred"]/dev/block/mmcblk0p35[/COLOR]
to this
Code:
# mount point fstype device [device2]
/boot emmc /dev/block/mmcblk0p20
/cache ext4 [COLOR="red"]/dev/block/mmcblk1p4[/COLOR]
/data ext4 [COLOR="red"]/dev/block/mmcblk1p3[/COLOR]
/devlog ext4 /dev/block/mmcblk0p25
/misc emmc /dev/block/mmcblk0p22
/int_sd vfat /dev/block/mmcblk0p38
/recovery emmc /dev/block/mmcblk0p21
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/system ext4 [COLOR="red"]/dev/block/mmcblk1p2[/COLOR]
Save the file and repack the modified ramdisk with the kernel as dualrecovery.img.
E. MAKING THE UPDATE.ZIP FOR YOUR BOOT.IMG:
By now, you should have your edited boot.img (dualboot.img) and your edited updater-script. Just place both of them within the Secondary rom zip and you are now good to go to flash and/or share to others (but you better test it prior to sharing it!).
F. FLASHING/SWITCHING ROMS:
Just reboot to your recovery and flash the Secondary rom and after that flash your dualboot.img, unless you have already added it to the rom zip then you wont be required to flash the dualboot.img unless you are S-On.
To Switch between Roms just reboot to your recovery and flash your Boot for primary rom and DualBoot for secondary rom.
NOTE: you can literally flash just your stock boot.img and your primary stock rom will appear as if nothing ever happened.
Sent from my C525c using Tapatalk
Quick question. While I appreciate the tutorial greatly... wouldnt it be safer to use a recovery like SafeStrap?
What would the benefits be of using thia method over SS?
Posted from my I337 NB1 Dark Venom 3 SS version --- 20G Free Cloud --- https://copy.com?r=vtiraF
This is currently built with the K2 variant devices kept in mind. I will not guarantee anyone else who does not own a K2 variant that this will work. If you do not own a K2 variant and this does work, please, comment on this thread to let myself and other viewers know. Please specify your device and Rom. However, if you read my first post and everything you saw is fitting to your device and roms, then it is VERY LIKELY that this WILL work for you - Thanks.
To automatically generate your boot.img and/or rom zip to be 'dual bootable' you must download the DualBoot_v1.0 zip at the end of this post and extract it to the root of your internal sdcard. This will save you the hassle of manually unpacking, editing, and repacking the boot.img and as well as extracting, editing, and pushing back the updater-script originally from your rom zip. This process is really fast at accomplishing its goals while doing all the work for you .
The ZipEditor.sh will use my three binaries to edit your boot.img and while doing so, it will create a temporary repack.sh file to allow it to be properly rebuilt again. It will also create a backup of your original boot.img which will be named boot1.img. The dual boot.img will be named boot2.img.
This script is literally built around my three executable binaries - unmkbootimg, mkbootfs, and mkbootimg.
Of course, in order to use the scripts, you need to have had partitioned your SD card the way I described in the first post.
Initial Setup
First of all download the zip at the end of this post, unzip it and copy the DualBoot folder to the root of your SD card.
Install Script Manager from Play Store
How to use
A. ZipEditor.sh
Download the ROM you want to install and copy the zip into /sdcard/DualBoot/OriginalZIPs
Also download a suitable GAPPS.zip and copy it to the same directory (if this applies to you)
If you need to convert additional zips, the tool is designed to process as many as it finds in this directory
Open Script Manager, browse to /sdcard/DualBoot and tap on ZipEditor.sh
In the next screen, select the first two icons on top (Favorite and SU) and then select, Run.
The tool will give you some info about your device. Check them and if they are not right, then kill the script. If they are correct, press Enter to continue. The Editor will process the zips one by one. Everytime a zip is completed, it will prompt you to press Enter.
When all zips are processed you may reboot to recovery, make a backup of your current ROM and flash them.
When you reboot, your secondary ROM will load.
B. SwitchROM.sh
The name is self-explanatory. This tool can only function if it finds the files boot1.img and boot2.img inside the /sdcard/DualBoot/img folder.
These files will be automatically generated when you convert a ROM zip in the ZipEditor. Alternatively, if you know what you are doing, you can create and put them there yourself.
Tap it in Script Manager and again select the first two icons (Favorite and SU) and Run. It will automatically detect the current ROM, flash the boot.img of the other one and prompt you to reboot. Use your Power-Menu and reboot your device. Your device will now boot to the other ROM.
So, for now, you can automatically convert zips for installation to the external partitions with ZipEditor and you can switch between your two ROMs using SwitchROM. You will notice that your normal recovery cannot backup, restore, factory-reset or wipe your secondary ROM. Therefore, @dreccon is currently working on his next project to upload another script that will function as a full fledged Recovery for the secondary ROM, so stay tuned... Meanwhile, you will be required to edit your custom recovery image manually as described in the first post. This will allow you to flash to your secondary rom. For example, the ability to flash and root your secondary rom if it happens to not be rooted.
Click to expand...
Click to collapse
Credits for the ZipEditor.sh and SwitchROM.sh goes to @dreccon
Credits for the executable binaries goes to @Modding.MyMind - That's me
kevp75 said:
Quick question. While I appreciate the tutorial greatly... wouldnt it be safer to use a recovery like SafeStrap?
What would the benefits be of using thia method over SS?
Posted from my I337 NB1 Dark Venom 3 SS version --- 20G Free Cloud --- https://copy.com?r=vtiraF
Click to expand...
Click to collapse
Simple, using your sd card prevents hard bricks and or changes to your actual partitions. This prevents the user from screwing up their device, while also, this prevents malicious roms that have been improperly built to be prevented from destroying the users devices which is really helpful for those who are flashaholics and messing around with nightlies. In addition, when all is said and done, all they need to do is put back their primary Rom boot.img and they will have back their primary (or stock) Rom again as if nothing ever happened.
Buying an sd card are a dime a dozen (cell phones are not)
Sent from my C525c using Tapatalk
Oh... I dont think its a bad idea... but the could be done by creating multipe rom slots with SafeStrap.
I'm really just wondering what the benefit would be chooaing this route over another.
I for one think its a great tutorial and is definately a handy way to do it... not so keen on the sd card usage tho... just due to varying speed issues and googles words on write issues to it...
Posted from my I337 NB1 Dark Venom 3 SS version --- 20G Free Cloud --- https://copy.com?r=vtiraF
kevp75 said:
Oh... I dont think its a bad idea... but the could be done by creating multipe rom slots with SafeStrap.
I'm really just wondering what the benefit would be chooaing this route over another.
I for one think its a great tutorial and is definately a handy way to do it... not so keen on the sd card usage tho... just due to varying speed issues and googles words on write issues to it...
Posted from my I337 NB1 Dark Venom 3 SS version --- 20G Free Cloud --- https://copy.com?r=vtiraF
Click to expand...
Click to collapse
Aren't any issues. You are formating the sdcard to the same format as your system, data, and cache partitions. That would be ext4. With that said, I have done this on a 2gig sdcard using a deodex Rom and it ran faster and smoother than from the actual device itself. Even the first boot time of the deodex Rom was cut down dramatically.
Sent from my C525c using Tapatalk
NICE. Gotta be a class 10 card and the ext4 filesystem.
I would imagine with a slower card it would slow down... tho.
Very cool and great info.... thanks bud!
Posted from my I337 NB1 Dark Venom 3 SS version --- 20G Free Cloud --- https://copy.com?r=vtiraF
kevp75 said:
NICE. Gotta be a class 10 card and the ext4 filesystem.
I would imagine with a slower card it would slow down... tho.
Very cool and great info.... thanks bud!
Posted from my I337 NB1 Dark Venom 3 SS version --- 20G Free Cloud --- https://copy.com?r=vtiraF
Click to expand...
Click to collapse
Over time it may slow down some, but that would only be due to its available memory filling up which you can only imagine with a 2gig to have but only so much available space when you format it. Now, if you have like a 16 or 32 gig or something close to it, then you would be set . You could even go as far as using any extra space as a swap for more ram .
Sent from my C525c using Tapatalk
kevp75 said:
Oh... I dont think its a bad idea... but the could be done by creating multipe rom slots with SafeStrap.
Click to expand...
Click to collapse
I also failed to mention, that if you use some general common sense you can use the guidelines provided in this thread, and create additional space on the sdcard for more roms
So, instead of dual booting, you could technically have three, four, or even 5 depending on the sdcard and what your device can handle. Not to mention, it doesn't take up space on your device. It is just a matter of swapping out your sdcard which can be handy.
Sent from my C525c using Tapatalk
awesome... i'm going to bookmark this so when i can get a spare device I can give it a whirl =)
hopefully my daughter gets sick of her cracked glass s3 soon and i'll be able to do this on that HA!
Posted from my I337 NB1 Dark Venom 3 SS version --- 20G Free Cloud --- https://copy.com?r=vtiraF
kevp75 said:
awesome... i'm going to bookmark this so when i can get a spare device I can give it a whirl =)
hopefully my daughter gets sick of her cracked glass s3 soon and i'll be able to do this on that HA!
Posted from my I337 NB1 Dark Venom 3 SS version --- 20G Free Cloud --- https://copy.com?r=vtiraF
Click to expand...
Click to collapse
Sounds good, and remember to not flash anything to your secondary Rom with your custom recovery. It must be done with your dualrecovery. This is only optional for those who plan to keep their secondary Rom.
Sent from my C525c using Tapatalk
gotcha. Thanks for this.
Posted from my I337 NB1 Dark Venom 3 SS version --- 20G Free Cloud --- https://copy.com?r=vtiraF
Nicely written guide. Well done!
One alternative to constantly flashing the boot.img is to flash the secondary one into the recovery partition and then install bootstrap recoveries to both systems. This way, each ROM would have its own recovery and you would switch ROMs by key combination at bootup.
dreccon said:
Nicely written guide. Well done!
One alternative to constantly flashing the boot.img is to flash the secondary one into the recovery partition and then install bootstrap recoveries to both systems. This way, each ROM would have its own recovery and you would switch ROMs by key combination at bootup.
Click to expand...
Click to collapse
Would do this, but as my knowledge goes, we (meaning our K2 variants) currently do not have bootstrap support at this time, but if you know how to help in that matter, please pm me
Sent from my C525c using Tapatalk
Modding.MyMind said:
Would do this, but as my knowledge goes, we (meaning our K2 variants) currently do not have bootstrap support at this time, but if you know how to help in that matter, please pm me
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
I haven't tried it. It's just an idea but I'm sure it works. As for building a bootstrap recovery, no I don't know how it's done. I was hoping you already had one.
Sent from the 3rd dimension!
dreccon said:
I haven't tried it. It's just an idea but I'm sure it works. As for building a bootstrap recovery, no I don't know how it's done. I was hoping you already had one.
Sent from the 3rd dimension!
Click to expand...
Click to collapse
I'm confident it would work. I may need to work on bringing it over to us. Will see if I can find time for that though.
Hey guys, a script is in the mix for automating all of what I described within the OP. It will save you the trouble of editing the boot.img, updater-script, and so forth. Some changes need to be made, but I cannot take credit for this. It all goes to dreccon. He is the one writing it out, and I am testing it to insure its integrity. When it is ready, I will be posting it in the third post giving full detailed instructions on how to set it up and use it.
Edit: However, you will still be responsible for formatting the sdcard yourself.
Sent from my C525c using Tapatalk
Third post has been updated. You can now use the available attachment in the third post to automatically generate your dual Rom/dual boot.img. So for those who read my guide in the first post that are scratching their heads... You don't need to anymore lol. All that is required from you is to format your sdcard.
Sent from my C525c using Tapatalk
Hey guys, I will be reconstructing the instructions for post three. Nothing to be concerned about for any of you reading this. Just to keep in accordance with a simple request out of respect and to hold true with the XDA rules.
-- Happy Hunting!!
Sent from my C525c using Tapatalk
Modding.MyMind said:
This is currently built with the K2 variant devices kept in mind. I will not guarantee anyone else who does not own a K2 variant that this will work. If you do not own a K2 variant and this does work, please, comment on this thread to let myself and other viewers know. Please specify your device and Rom. However, if you read my first post and everything you saw is fitting to your device and roms, then it is VERY LIKELY that this WILL work for you - Thanks.
To automatically generate your boot.img and/or rom zip to be 'dual bootable' you must download the DualBoot_v1.0 zip at the end of this post and extract it to the root of your internal sdcard. This will save you the hassle of manually unpacking, editing, and repacking the boot.img and as well as extracting, editing, and pushing back the updater-script originally from your rom zip. This process is really fast at accomplishing its goals while doing all the work for you .
The ZipEditor.sh will use my three binaries to edit your boot.img and while doing so, it will create a temporary repack.sh file to allow it to be properly rebuilt again. It will also create a backup of your original boot.img which will be named boot1.img. The dual boot.img will be named boot2.img.
This script is literally built around my three executable binaries - unmkbootimg, mkbootfs, and mkbootimg.
Of course, in order to use the scripts, you need to have had partitioned your SD card the way I described in the first post.
Initial Setup
First of all download the zip at the end of this post, unzip it and copy the DualBoot folder to the root of your SD card.
Install Script Manager from Play Store
How to use
A. ZipEditor.sh
Download the ROM you want to install and copy the zip into /sdcard/DualBoot/OriginalZIPs
Also download a suitable GAPPS.zip and copy it to the same directory (if this applies to you)
If you need to convert additional zips, the tool is designed to process as many as it finds in this directory
Open Script Manager, browse to /sdcard/DualBoot and tap on ZipEditor.sh
In the next screen, select the first two icons on top (Favorite and SU) and then select, Run.
The tool will give you some info about your device. Check them and if they are not right, then kill the script. If they are correct, press Enter to continue. The Editor will process the zips one by one. Everytime a zip is completed, it will prompt you to press Enter.
When all zips are processed you may reboot to recovery, make a backup of your current ROM and flash them.
When you reboot, your secondary ROM will load.
B. SwitchROM.sh
The name is self-explanatory. This tool can only function if it finds the files boot1.img and boot2.img inside the /sdcard/DualBoot/img folder.
These files will be automatically generated when you convert a ROM zip in the ZipEditor. Alternatively, if you know what you are doing, you can create and put them there yourself.
Tap it in Script Manager and again select the first two icons (Favorite and SU) and Run. It will automatically detect the current ROM, flash the boot.img of the other one and prompt you to reboot. Use your Power-Menu and reboot your device. Your device will now boot to the other ROM.
Credits for the ZipEditor.sh and SwitchROM.sh goes to @dreccon
Credits for the executable binaries goes to @Modding.MyMind - That's me
Click to expand...
Click to collapse
dang it... now i gotta get me a 64G card
Rockin it from my Rockin Smartly Deadly Venom NE5 S4 (much thanks to: @Venom0642 @ted77usa @rebel1699 @iB4STiD ~ 20GB free cloud https://copy.com?r=vtiraF