HTML:
Credit for koush for Droid2 Bootstrap
Credit for edgardcastro for sharing lots of information about 2nd-boot on Milestone1
Credit for Skrilax_CZ for 2nd-init and sh hijack
Credit for r2beta0 for how to 2nd-init on M2
Hello guys,
after weeks of work and trouble with the m2 i finally got a booting 2.2 AOSP image for the m2.
This is still work in progress, many things are not working, i am just releasing this one
to show that it's possible to build custom roms (even without the possibility of a custom kernel, for now).
Because i had some trouble to put the compiled android on the system partition without ending
with a not booting phone, i pulled the compiled system on the preinstall partition.
Installation is a little bit tricky but if you guys do as i describe below anything should work
without problems.
What's not working:
- Many things (Baseband, WLAN...)
What's working:
- Touchscreen (So you can at least play a little bit with the UI)
- Vibration
- Keyboard
- Light sensors
- 3D Gallery
- BT
The phone is faster without Motoblur.
Development is still in progress, but you can give this one already a try.
Based on MILA2_U6_3.12.0_SIGNED_US1MILESTONE2RETBRB125LA016.0R_GSXMILETRETBRLA_P026_A009_M012_HWp2a_Service1FF.sbf
What you need:
Rooted Milestone 2
Droid 2 Bootstrapper
PC with ADB installed
How to install:
1) Extract the files contained in the zip to the root of your sdcard
2) Reboot into recovery mode with usb cable connected
3) Restore the system partition with the image contained in the zip (nandroid restore over recovery)
4) Now open the adb shell and type:
-# cd /preinstall
-# rm -r app
-# rm -r md5
-# rm -r mml
-# unyaffs /sdcard/preinstall.img
5) Perform a full wipe
6) Reboot system
Whe the phone is turned off and you try turn on the phone, you will end in recovery.
Simply choose "Reboot system" to reboot into android.
If you have problem with battery, simply wipe battery stats.
Download
Demo Video
This is first relay rom, thanks
any screen ?
Without motoblur the phone is faster? Great!!! Looking forward to any ongoing development!
This deserves some attention!!!
This sounds good will give it a try if the wifi and baseband get fixed.
Sent from my A953 using XDA App
This made my vacation
Is there any possibility for you to run quadrant, just out of curiousity. even though there is still a lot of stuff not working.
Keep up the good work!
I boot it and it a work very fast
BT IS WORK
Looking forward to this.. Congrats on your feats so far..
Unfortunately i dont get it to boot.. bootloop so today im not going to test it .. maybe tommorow when i have time, yet i dont know why it causes a bootloop since i did it like you've said.. maybe because i forgot the preinstall, pushed it after restore and then did the rest (well its actually the same ... shouldnt cause a bootloop)
Got any screens for us?
Sounds very promising. Can't wait to see any further developments to this!
inheme said:
Got any screens for us?
Click to expand...
Click to collapse
Google "android 2.2"
It's just stock froyo. You'd better be off asking him for photos, but you could always try it yourself though. If you screw up, just follow my tutorial!
Sent from my MotoA953 using XDA App
So the system is basically located in /preinstall and you're using a minimal android build in /system?
Or do you mean you told te update.zip to install files into /preinstall and manually copied them over? Then what are the contens of the preinstall image?
I'll investigate when I have more time.
Sent from my MotoA953 using XDA App
Congratulations ! You are great, Thank you for giving more zest for life to m2
can u update the zip to u.115.com?
you know, we can not visit many american websites in CN,such as your "download" web.
Unfortunately i dont get it to boot.. bootloop so today im not going to test it .. maybe tommorow when i have time, yet i dont know why it causes a bootloop since i did it like you've said.. maybe because i forgot the preinstall, pushed it after restore and then did the rest (well its actually the same ... shouldnt cause a bootloop)
Click to expand...
Click to collapse
Did you do the full wipe? Wich rom do you have on your phone as base?
So the system is basically located in /preinstall and you're using a minimal android build in /system?
Or do you mean you told te update.zip to install files into /preinstall and manually copied them over? Then what are the contens of the preinstall image?
I'll investigate when I have more time.
Click to expand...
Click to collapse
Yes the compiled system is located on /preinstall.
The /system partition is still there for the 2nd-init and the recovery bootstrap.
This is just an experimental build, once i have something that can be released i will move try to move things on the /system partition, but i have tried this for weeks without success.
The system informations says that it is android 2.2, but for real it is 2.2.1. The 2.2 value is read from the build.prop file on the system partition, so don't think that is the stock rom with some customization, but a 100% Froyo AOSP.
Congrats. At least u gave us something real unlike fission Angdroid
Sent from my MotoA953 using XDA App
m0rph3us said:
Did you do the full wipe? Wich rom do you have on your phone as base?
Yes the compiled system is located on /preinstall.
The /system partition is still there for the 2nd-init and the recovery bootstrap.
This is just an experimental build, once i have something that can be released i will move try to move things on the /system partition, but i have tried this for weeks without success.
The system informations says that it is android 2.2, but for real it is 2.2.1. The 2.2 value is read from the build.prop file on the system partition, so don't think that is the stock rom with some customization, but a 100% Froyo AOSP.
Click to expand...
Click to collapse
Great, we (Owain94 and I) appreciate you sharing this information with us. We will build our alpha and beta builds using this method untill we find a way to install to /system. Thanks for your ideas!
Mikevhl said:
Great, we (Owain94 and I) appreciate you sharing this information with us. We will build our alpha and beta builds using this method untill we find a way to install to /system. Thanks for your ideas!
Click to expand...
Click to collapse
No prob. I am currently recompiling, it seems the wifi modules etc have problems if they are launched from /preinstall, i also found a way to get the system boot from /system, but i will be sure later when the build is finished. I will give you more information later.
Related
Hi All!
I pushed my fork back to GITHUB
I compiled CM recovery for Galaxy 3, it was long journey
I need some help. My development speed is very low, I'm not dev at all and my C knowledge is very limited. Also I can't invest many time in porting CM recovery.
Thing that worked for my setup (/system - rfs /data ext2 /cache - ext2):
1. it compiled!
2. partitioning SD card
3. making backup
4. restoring data partition (other parts and boot/recovery not tested)
5. wipe cache paritions
6. running fix_permissions scripts
7. running keypress test
I want You to help me choose that to do next: make update.zip worked or try to do backup/restore fully working?
Also I need link for update.zip that surely worked for JPM to test it.
recovery is in pre-alpha stage, I don't want do public alphas, because it simply not tested, and really may brick phones
Now recovery in private alpha testing stage, PM me if you brave, want to test alpha and accept risk of bricking you device
good job.
I don"t know if I can help you much but I will try if you need to.
FS supported by builds:
Build # /system /data /cache
26 rfs ext2 ext2
27 ext2 ext2 ext2
30 ext2 ext4 ext2
Good job
You can give it to some testers though willing to test even at the risk of bricking so that devs like you are motivated and get feedback
Testing really helps
I can help too
if you are porting cwm recovery latest version it uses newer scripting language and thus old update.zip files wont work anyway.
finally! SG3 is becoming a good phone lol ! thanks!
subscribed...
i´d suggest to make nandroid backup work first, then the danger of having a softbrick is much smaller.
That's fantastic news !
Backup/recovery should be top priority I think. Flashing update.zip is not something we could do before, so we won't miss that.
Bubble-be said:
That's fantastic news !
Backup/recovery should be top priority I think. Flashing update.zip is not something we could do before, so we won't miss that.
Click to expand...
Click to collapse
we could do it with eclair...
FadeFx said:
if you are porting cwm recovery latest version it uses newer scripting language and thus old update.zip files wont work anyway.
Click to expand...
Click to collapse
My developing speed is really slow, I start porting it ~1.5 months ago
Version is ClockworkMod Recovery v2.5.1.8 is it old or new version for update.zip ?
making everything to work would be awesome... i believe in you ppl! you will make it work! you have to make it work! because no one else is even close to being capable of doing the magic that you are doing!
the new script version is out for 3 or month or 4 so already...
Nice work
Do you know when you release the 1st beta?
its done when its done... dont ask dont tell...
deskjeti said:
Nice work
Do you know when you release the 1st beta?
Click to expand...
Click to collapse
dude read>
recovery is in pre-alpha stage, I don't want do public alphas, because it simply not tested, and really may brick phones
mumbozver said:
Hi All!
I compiled CM recovery for Galaxy 3, it was long journey
Click to expand...
Click to collapse
Maybe the best news concerning the g3 in a long time. Keep it up man! I am not able to do much but I'm eager to beta test!
sent from my kirillos' v.3 fugumod 2.2 BE oc'd JIT enabled nokia 3210
can you gine me workin fix_permissions scripts to use it from internal use ?> thanks in advance
You can test the recovery by using terminal.But there's a problem that u can't return to normal system.I think it 's because the video driver return to basic mode etc.(Just guess it)I sugggest u don't compile all parts of the cwm but a little part.For we just need a little function now.Test it in terminal.While I have a computer.I will try to help,but I can't promise anything...Haha
Sent from my GT-I5800 using XDA Premium App
WHEN I USING ENGLISH IN COMUNNICATING WITH OTHERS. SOMEONE WILL TELL ME:U CAN PASS THE CET-4 EASILY....
nikkpap said:
can you gine me workin fix_permissions scripts to use it from internal use ?> thanks in advance
Click to expand...
Click to collapse
"worked" mean it runs fine from recovery menu, and do its job.
It's unmodified, and I'm not sure it fully correct for our phone.
You may find it here: https://github.com/CyanogenMod/android_bootable_recovery/blob/froyo-stable/utilities/fix_permissions
instead of making update.zip work, u can complete the nandroid and backup\restore
i flashed cm7 in my friend's X8
the update.zip did not work properly so i extracted the rom files and made them as a backup and restored the rom with that backup-worked like a charm
we can install roms if the dev's provided it as a backup file(which is safer than using update.zip)
Dual Boot Support
DualBoot Helper APP is now on the market! (See bottom of this post for more info)
DISCLAIMER: I am not responsible for anything, ever. It is not my fault if you do not read. I do not explain things because I enjoy banging on the keyboard. If you do not read this entire post before jumping in then do not expect me or anyone else to be much help. By following this guide and any links YOU assume all responsibility for your device and anything that happens with it.
What is it?
Dual booting allows you to run two separate roms on your device at one time. It is done by intercepting the mount points during the startup of the device. This is accomplished by checking the sdcard for a specifically named file when the kernel first loads and uses the appropriate files to boot with the correct partitions. Reading from the sdcard is slower than reading from the internal memory of the phone so the speed of your sdcard will drastically determine the speed any rom runs. On the same note a rom flashed to the sdcard will take longer than usual on the first boot.
What does it do for me?
Running two separate roms has many uses for just about everyone. Users can use dual booting to try different roms, themes, apps, modifications, or anything while keeping their existing installation intact. The uses are just about endless. Besides testing different roms, this allows the user try these things and make sure they are compatible and stable before pushing the changes to their internal memory. Rom developers have all of the above options plus a few. Rom developers can additionally use dual booting to test builds of their roms without fear of soft bricking their device. For advanced users, you can mount the partitions of the other rom (be it sdcard or internal) and fix bad apk files or messed up files. The options really are limitless!
What do I need?
Sdcard 2GB or larger
Dual boot compatible kernel
Other things I should know...
*The kernel MUST support BOTH roms you flash. Unfortunately this means you can NOT mix froyo and gingerbread roms. Make sure you know what the kernel supports before you flash anything!
*If you compare roms, benchmarks will hold no value due to the sdcard being so much slower than internal memory.
*Faster sdcards will perform better than slower ones. Note: the stock 16GB sdcard is a class 2 which simply classifies it's minimum speed. A higher class sdcard will more than likely perform faster but the class rating is a minimum and not a maximum. It is entirely possible that a certain class 2 card can out perform a different class 6 card. Keep this in mind when researching to buy a new faster sdcard. More info in this post.
*First boot takes longer than usual. Up to 15 minutes! Please wait until the rom boots and the initial media scanner is done before you judge usability.
*Using a rom from the sdcard will cause the sdcard to wear faster. This is due to many more reads and writes of data than normal. The Epic simply does not have the internal capacity to run dual roms on the NAND. That being said the sdcard is our next option. While it may reduce the over all life of the sdcard keep in mind there are other android devices like the Nook Color and the other Galaxy S phones that have internal sdcards running the Android operating system. My personal opinion with is with other devices running off internal sdcards and with the price of sdcards getting cheaper and cheaper it was worth it to explore this option for the Epic.
Ok ok, so how do I get started?
I am going to break the steps down into sections. Please read everything to ensure you understand what all is involved in getting everything working. I recommend making a backup in Clockwork Mod and saving it to your PC before you even get started.
Section 1 - Setting up the environment
Step 1. Flash a compatible kernel (Kernel developers, PM me if you add my dual boot support to your kernel and I will update the list below) Remember you can NOT mix a eclair, froyo, or gingerbread roms and the kernel MUST support both roms!
Currently compatible kernels:
Genocide 2.0 Supported Roms: EC05, EB13, and DK28
Section 2 - Preparing sdcard
Important information!!!! This will destroy ALL data on your sdcard so if you lose pictures of your dog, cwm backups, nudies of your spouse, etc then you can't blame me. BACKUP YOUR SDCARD!
The easy way:
Reboot into recovery mode with a program like Rom Manager, Quick Boot, or type 'reboot recovery' from a terminal. (NOT 3-finger boot to recovery...this will NOT work)
The easy way WILL erase your sdcard with NO confirmation....you have been warned!
Choose one of the following flashable zips to automatically partition your sdcard
DualBoot_Partition_RFS.zip
DualBoot_Partition_EXT4.zip
The manual way:
Reboot into recovery mode with a program like Rom Manager, Quick Boot, or type 'adb reboot recovery' from a command line. (adb commands assume you have a working install of the Android SDK)
While in recovery issue the following commands:
Code:
adb shell
cd /sbin
./dbpart.sh --help
I put many hours into the partitioning script to make it as simple to use as possible. Simply follow program usage instructions.
Section 3 - Preparing a rom
Since we have blank partitions on the sdcard we need to populate them with data. There are multiple ways to accomplish this and you can choose which solution best suits your needs. I am not going to cover ALL methods here but enough to suffice any likely scenario needed.
The dd method will clone your current setup to the sdcard (these commands may take up to 15 minutes)
The easy way:
Flash this dd script: DualBoot_Clone_to_sdcard.zip
The manual way:
Code:
adb shell
dd if=/dev/block/stl9 of=/dev/block/mmcblk0p2
dd if=/dev/block/stl10 of=/dev/block/mmcblk0p3
dd if=/dev/block/stl11 of=/dev/block/mmcblk0p4
Preparation is complete. Please skip down to booting from sdcard.
The flash method is for flashing a new rom to the sdcard.
The easy way:
There is no sure fire easy way just yet. Stay tuned though.
The manual way:
This method is not that difficult so there is no need to be intimidated by it. It requires editing a few lines of the script that Clockwork Mod executes when flashing a rom or addon. For this example I am going to use a file named epicrom.zip but you can use any name you wish.
Step 1. On your PC, open epicrom.zip (I recommend using a program like 7zip)
Step 2. Navigate to the META_INF\com\google\android\ folder.
Step 3. Drag the file updater-script out of the zip to your desktop.
Step 4. Open the updater-script file with a text editor such as notepad (I recommend notepad++ or textpad)
Step 5. Change every instance of /dev/block/stl9 to /dev/block/mmcblk0p2
Step 6. Change every instance of /dev/block/stl10 to /dev/block/mmcblk0p3
Step 7. Change every instance of /dev/block/stl11 to /dev/block/mmcblk0p4
Step 8. Delete the entire line for any lines that contain /dev/block/bml7 or /dev/block/stl7 to disable flashing another kernel and breaking dual boot support.
Step 9. Save the file and drag and drop it back into epicrom.zip and let it replace the old one.
Note: If you get a status 6 or some other error when trying to flash it is likely you made a typo or your text editor did no save the updater-script file correctly. Recommended action is to correct the typo and/or use one of the recommended text editors note in Step 4.
Section 4 - Flashing to sdcard
Flashing a rom from this point is the same as you usually do. Put the modified rom on your sdcard and flash with Clockwork Mod like usual. I recommend doing a backup in Clockwork Mod BEFORE you flash in case you messed anything up by accident and end up flashing over internal memory when you meant to flash to the sdcard.
Section 5 - Booting sdcard
To boot from the sdcard place a file in the root of your sdcard called 'bootsdcard'. If you named it correctly upon reboot, the kernel will load the rom from the sdcard and not internal memory.
To boot back into internal memory simply remove this file from your sdcard and reboot.
You can switch back and forth using this method. If the file is there it boots sdcard, if the file is not there it boots normally. Pretty simple right?
Section 6 - Other flashables (not roms)
Themes, addons, and anything else that is flashable with Clockwork Mod must be modified in the same fashion as the rom. Use the same procedure documented in Section 3, The flash method.
Kernel Developers:
If you would like to add dual boot support to your kernel please refer to this commit: https://github.com/Rodderik/Genocide-Kernel/commit/a5dfd9f369ae4f2c90c1e7fc7d8995f88f72bd01
I will update this section if I push any specific changes to dual booting.
Now with an APP!
DualBoot Helper
VenumX coded up an APK to work with Clockwork Mod to run the scripts.
http://forum.xda-developers.com/showthread.php?p=15486144#post15486144
Questions, concerns, gripes, or complaints can be left in this thread. If you need to report any problems please be as detailed as possible.
woot
Thats my boy!!!! Make me proud!!!!!!!!!!
w00t! go man go!
Holy ****! This is huge! Thanks!
Sent from my SPH-D700 using Tapatalk
OMFG this is way amazing ;P
Thr genious once again with another first
Sent from my SPH-D700 using XDA Premium App
Edit
nevermind...
good work!!!!!!!!!!!!
davidrules7778 said:
I got a question...
Would i be able to run dual versions of android
Ex 2.1 and 2.2
or 2.2 and 2.3
if the kernal is compatible?
Click to expand...
Click to collapse
if the kernEl was compatible yes...but none of them are...and likely won't be
Good damn job bro.. Let's keep the dev community developing
Rodderik said:
if the kernEl was compatible yes...but none of them are...and likely won't be
Click to expand...
Click to collapse
what if u made one of the eclair kernal compatible or gingerbread whenever we get custom kernals for it?
Or is it not possible to make eclair kernals compatible?
i think i could make a GB kernel now.. but you wouldnt be able to mix gb with froyo or eclair, because a GB kernel wont boot those builds..
Awesome work bro! Amazing...simply amazing!
chris41g said:
i think i could make a GB kernel now.. but you wouldnt be able to mix gb with froyo or eclair, because a GB kernel wont boot those builds..
Click to expand...
Click to collapse
yup i'm going to help chris41g put together a gb kernel for you guys
as far as eclair...honestly who still uses eclair? and why?
Rodderik said:
as far as eclair...honestly who still uses eclair? and why?
Click to expand...
Click to collapse
Just what I was thinking.
Tested on EC05 just now. I uhh... likey? =)
to bad no multi android versions though =(
why cant the kernel read off the sdcard? do you need drivers from samsung once again?
Shoulon said:
Tested on EC05 just now. I uhh... likey? =)
to bad no multi android versions though =(
why cant the kernel read off the sdcard? do you need drivers from samsung once again?
Click to expand...
Click to collapse
well the kernel is stored in bml7 and called by sbl/param during boot so unless we can get a bootloader to intercept the initial loading of the kernel and pass it off we are stuck with one kernel at a time
Very Nice Work !!!
Hey rodd... I think you should work on an aosp gingerbread kernel ... this is a great advancement in devlopment man... right when it was slowing again
Sent from my SPH-D700 using XDA App
this is amazing, thanks for this!!
You cannot make a cross OS kernel. We cannot integrate this into GB yet because there is no GB source, no GB source, no custom kernel. This is Froyo only, and well, someone else can make an eclair only kernel, but that is stupid.
First of all... Thanks Chainfire!!!! This is totally based on your work.... i made only some MOD....
Ok, the work is quite finished... the CF-ROOT for I9003 is ready!
I called this "beta version" (since i need your tests/opinions) but all might work.
IMPORTANT: This is only for KPH Firmware!!!
You can flash this over any other CWM or over the stock FW.
Many people will ask "Why i have to install this?"... because with this your phone will have:
- Root ( don't need to use SOC or any ZIP);
- Busybox 1.17.2;
- Sqlite3 v3.7.2;
- init.d support (you can put in the folder /system/etc/init.d all the script that you want to be loaded at the startup);
- New fixed CWM ( unyaffs issue has been fixed - offline charge fixed - USB storage mode while in CWM fixed);
- Add EXT4 support to the phone ( so you can convert the filesystem to ext4 to improve performance);
- full working CWM Manager (backup - restore - delete backup - install apk - flash update.zip - flash kernel - reboot to CWM);
- Tweaks Manager with various tweak ( Ram Min Free - SD Speed - I/O Scheduler - Kernel Scheduler - CPU Conservative Governor - Swappiness - Ram Script by Juwe11 - Media Stagefright)---> Many people asked for Juwe Ram Script ---> to enable it completely choose in the Tweaks Manager: Ram Script - Ram Min Free and Swappiness;
- Auto ZIP-Align on boot - You can choose it in the tweaks app(NEW)
- Reviewed tweaks values (some from darky's rom some from hardcore some from other post in XDA)( thanks to bigeyes0x0 and Misledz )(NEW)
- Custom Boot-Animation support (place your custom bootanimation in /system/media/ and call it sanim.zip)(NEW)
To do:
- other tweaks suggested by you...
- whatever can be added.
Let me know what you think
HERE you can find the original post.
HOW TO INSTALL:
1- Flash with Odin the .tar file
or...if you went from a previous version of CF-ROOT
2- Download the .zip file into the external SD the open CWM Manager --> flash Kernel --> select the file you have just downoaded
IMPORTANT:
If you cannot find the two apps on your app drawer maybe you haven't space left on /system so delete some unused apps like aldiko, delere /system/cfroot folder and reboot
IMPORTANT/2: after the flash the phone might take some time to boot. You might think that it freeze on Samsung Logo but it's normal cause the auto-zipalign proc need some time. Just Wait.
UPDATE: Added CF-ROOT with my custom kernel. This have Ext4 inside the kernel (no modules) and OC to 1.1 Ghz. I think that it is secure. I haven't test it very well so please report me the issues you will find.
!
Version 05.09.2011 Changelog:
- added Graphics Boost Tweak (thanks Gana)
- added acid tweaks (thanks to the people that worked on it .. specially Bigeyes0x0);
- reviewed 00tweaks file by Bigeyes0x0;
To disable journaling on ext4 partition apply the attached journaloff.zip in CWM (Not CWM Manager app - it must be fixed).
There're two version of the CF-ROOT, the version with **CWM_Manager** can be flashed with CWM Manager App (select flash kernel) the other with odin (like always)
UPDATE 20.10.2011:
CF-ROOT for XXKPM can be found HERE:
- Standard Version --> http://www.multiupload.com/S463K75UED
- Surprise version ( i suggest you this) --> http://www.multiupload.com/G20L6PL5WC
What's new ?
- I finally finished the custom bootanimation support.... now works like he have to works. Just copy your bootanimation into /system/media and rename it to sanim.zip.... i think that here you can find what you need http://forum.xda-developers.com/showthread.php?p=17322814#post17322814
IMPORTANT!!!
If you have installed the beta version you must know that the ext4 conversion for that doesn't work properly. Ok, system, cache and dbdata will be on ext4 but data not. This because the init binary check on boot if /data have rfs FS and, if not, it format the partition wiping all your data.
In the new version i modified the init binary so it cannot do it more
I must say that i became mad to discover this damn thing !
A few questions: Are you using the latest fixed version of CWM? Also you mentioned that you would be releasing another update soon regarding the Nandroid backup image corruption issue. Is it in this release?
Also: Is this an alternative to ROM manager, apart from the inclusion of the tweaker tool?
Regarding the enhancements, could you please elaborate on some of them and what is safe/not safe to use (particularly in the tweaks and what they do)?
What I understood, after looking over all the posts, was that you optimized the CF-Root by chainfire for the i9003, by using a compatible Root, CWM, and adding an ext4 kernel? Are you going to port the ext4 converter tool as well? Will we be able to use an external SD card with ext4 formatting (Could be used to store files larger than 4GB)?
Sorry about the ton of questions. Trying to learn, and what better way to learn than from the best!
I'm going to take it out for a test drive now on XXKPE with ext4! Will report back later!
Thanks for your valuable work, I'm a huge fan!!!
Cheers
Update: Confirming that the passive charging bug has been fixed! Thanks Skin1980!
I cannot find the CWM or Tweaks icons in the app drawer as indicated in your screenshots. I can access CWM recovery mode using the 3 button combo though.
I had installed the last version of CWM by Amit and formatted with ext4 and I just used ODIN to flash over that install. I tried flashing again, still not appearing in app drawer. Any solutions?
Great job skin.. Hoping for the early release of a stable one.. Will test it later
Sent from my GT-I9003 using XDA Premium App
it's great...>.<
Auguri! Ok wow, This is pure genius . I've always been wondering what our CWM were based off. I guess using this would fix most issues people get when flashing CWM, since it's based off the original firmware
Also I'm loving the tweaks, they seem to make the phone more smooth, Although I've seen a few bugs after applying this I can't seem to use the V6 charger script anymore I get an error, will be posting one shortly. There are some minor hiccups in between and I tend to get FC on some apps when I multitask.
Edit: Turns out It's busybox related, no shell access. I've tried launching Busybox by Stericsons to check and It says no root access was given and boots me out.
i happy that u r belong to this community
Is there any recovery module or tweak available, in which we can handle basic file operation like copy, move from sd card to system or any thing similar?
Erahgon said:
A few questions: Are you using the latest fixed version of CWM? Also you mentioned that you would be releasing another update soon regarding the Nandroid backup image corruption issue. Is it in this release?
Also: Is this an alternative to ROM manager, apart from the inclusion of the tweaker tool?
Regarding the enhancements, could you please elaborate on some of them and what is safe/not safe to use (particularly in the tweaks and what they do)?
What I understood, after looking over all the posts, was that you optimized the CF-Root by chainfire for the i9003, by using a compatible Root, CWM, and adding an ext4 kernel? Are you going to port the ext4 converter tool as well? Will we be able to use an external SD card with ext4 formatting (Could be used to store files larger than 4GB)?
Sorry about the ton of questions. Trying to learn, and what better way to learn than from the best!
I'm going to take it out for a test drive now on XXKPE with ext4! Will report back later!
Thanks for your valuable work, I'm a huge fan!!!
Cheers
Update: Confirming that the passive charging bug has been fixed! Thanks Skin1980!
I cannot find the CWM or Tweaks icons in the app drawer as indicated in your screenshots. I can access CWM recovery mode using the 3 button combo though.
I had installed the last version of CWM by Amit and formatted with ext4 and I just used ODIN to flash over that install. I tried flashing again, still not appearing in app drawer. Any solutions?
Click to expand...
Click to collapse
1- The CWM used is always the last... if i'll update the CWM i'll update the CF-ROOT;
2- The CWM fixed reguard nandroid backup is under test;
3- My CWM isn't ROM Manager compatible... with the CWM Manager from Chainfire you can do a lot of things without going into CWM
4 - to convert in EXT4 just follow the guide on the other thread;
5- Not sure if you can format in XT4 your external_sd... try ;
6- The tweak are all sure... now i haven't time to exlplain better... some don't work.... some other work.
7- If the icon don't appear in app drawer try to check into system/app if the two files are there... if not try to remove /system/cfroot folder and reboot. Maybe your system folder is full so you can install they manually, the original apk are inside /res/misc/ folder.
8- bye
for me wifi not working obtaining ip address,gps not lock can i flas normel bootimg.ur work is awesome thx
bala242 said:
for me wifi not working obtaining ip address,gps not lock can i flas normel bootimg.ur work is awesome thx
Click to expand...
Click to collapse
I'm sorry.. for me everything is working...Before my CF-ROOT all works?
ur a superhero man!!
great ;-)
Skin1980 said:
I'm sorry.. for me everything is working...Before my CF-ROOT all works?
Click to expand...
Click to collapse
ya everything work before,can i reflas ur ver cwm?any body get this error?
Is there any tweak for increasing the 2g speed ??
or getting 3g speed in 2g plans...
I need this very badly...
I am not getting exact idea that what exact cf root does??? Or how cf root is so special...?? Will this make our work easy to do changes in kernal (that would be great)...???
Please can anybody in simple language....!!!
anigr88 said:
Is there any tweak for increasing the 2g speed ??
or getting 3g speed in 2g plans...
I need this very badly...
Click to expand...
Click to collapse
What your asking for is impossible.
Update!
The problem I had turned out to be due to the lack of space in the "/system" folder - as you had predicted Skin1980! Once I deleted some unnecessary software, I was up and running fully within minutes!
The phone works great! The fixes are really good! Having no issues except for one so far. I can't seem to mound "sdcard" in CWM recovery mode and cannot do a restore, for the same reason, from the CF-ROOT menu.
I have a feeling it's something I did wrong earlier, so I'll reflash completely and try again ('cause I have a lotta time on my hands atm and I want the bestest possible phone I can get).
Note: This doesn't seem to be compatible with DDKB2. Assuming that this is mainly for GB firmwares? Can someone corroborate this?
As usual, thanks!
Erahgon said:
The problem I had turned out to be due to the lack of space in the "/system" folder - as you had predicted Skin1980! Once I deleted some unnecessary software, I was up and running fully within minutes!
The phone works great! The fixes are really good! Having no issues except for one so far. I can't seem to mound "sdcard" in CWM recovery mode and cannot do a restore, for the same reason, from the CF-ROOT menu.
I have a feeling it's something I did wrong earlier, so I'll reflash completely and try again ('cause I have a lotta time on my hands atm and I want the bestest possible phone I can get).
Note: This doesn't seem to be compatible with DDKB2. Assuming that this is mainly for GB firmwares? Can someone corroborate this?
As usual, thanks!
Click to expand...
Click to collapse
after a whole day of using it. The phone will tend to lag and build up after a while. You'll notice the phone becomes slow again. I don't know what's going on.
Misledz said:
What your asking for is impossible.
Click to expand...
Click to collapse
I just want a small boost in the speed ....
Misledz said:
after a whole day of using it. The phone will tend to lag and build up after a while. You'll notice the phone becomes slow again. I don't know what's going on.
Click to expand...
Click to collapse
I did notice that initially it was fast. But as I kept it going through the day to recalibrate the battery, it did slow down and start to lag. I thought it was something to do with that. Also I felt that I had done something wrong with the flashing.
Going to overhaul my phone completely: Format, re-partition, XXKPE install (flashing twice), flash fixed CWM from the other thread, root using SOP 2.1.1, install busybox requirements for deodexing (this failed for me the last few times), restore settings using Titanium Backup, Nandroid backup, ext4 this baby, restore, and then install CF-ROOT to monitor.
Wish me luck! See you guys on the other side... again!
anigr88 said:
I just want a small boost in the speed ....
Click to expand...
Click to collapse
You've got the wrong thread mate!
Your bandwidth is capped by you operator and is dependent on how much they allocate you. On top of that 2G is physically limited to certain speeds which, usually, cannot be surpassed by legal means, and the illegal ones give you too less of a boost vs complications and errors to even bother about (I mean big ass hardware)!
Disclaimer: this is for testing only, I assume no liablity to any potential damage. If you feel this is a violation to your copyrighted software, feel free to contact me and I will respond accordingly.
It's released only on forum.xda-developers.com and bbs.mfunz.com , please refer to either thread depending on you prefered language.
Hi, after a few days of trying, I'm releasing a prelimitary Dual OS solution for Defy. It's not very complete yet but it's good enough for daily use (the 'dual' part, not the MS2 port or MIUI).
Before you ask, yes I've tried using SDCARD (system+data or data-only), it's just too slow for daily use. app2sd would be a better solution.
Features:
Well it's a Dual OS, what can I say. (MS2 port + MIUI)
You can update the two system independently (admittedly a bit hard for the 2nd OS as of now)
Advance Settings in the 1st OS, try it!
Draw backs:
It eats up 327MB (may size down a bit in future releases) of your /data and the two OS use the same space for it's apps so you have 700~800MB free /data to split between two systems. I'm using memhack to save some space.
The two OS included isn't very stable
Only 2.2 kernel supported as of now
Installation:
Root your defy and install any ClockWorkMod/Bootmenu/Snd-init if you don't already have one
Download the RAR file and extract 'clockworkmod' folder to the root directory of your SDCARD
Boot to your CWM, choose restore, and restore "DualDefy_v2.11". DO NOT WIPE after restoring or you loose the 2nd system.
Reboot system and it will boot into the primary system
To enter MIUI, press VolDown during blue LED when booting and enter Bootmenu, choose boot -> 2nd-boot and wait
Note:
It will reboot once during first-ever boot to generate a overclock(etc.) config file. *Do not use the overclock function in bootmenu* It's in "Settings -> Advanced Settings".
How to wipe:
To perform a wipe correctly (without loosing one of the system), follow the instructions:
To wipe 2nd OS, just delete /data/2nd-data with RootExplorer or "adb shell rm -r /data/2nd-data" in the CMD/Terminal window without quote. -- While booted into th 1st OS of course
To perform a full wipe, backup the 2nd OS, just copy /data/system.img to the root of your SDCARD (/sdcard/system.img), the wip as you normally do. It will be copied back if you choose 2nd-boot again.
To wipe the 1st OS: boot into 2nd OS, delete everything in /data2 except "/data2/2nd-data" folder and "/data2/system.img"
Thanks:
To all the devs who layed the ground work (Skrilax_CZ, CyanogenDefy team and many more) which ultimately made this possible.
And thanks to all the people who were helping me test it over at bbs.mfunz.com
Download:
http://mir.cr/44DQ1SOC
looks nice looking forward for 2.3 kernel support
wait till it stable,but it clearly awesome job
was waiting for this....
Interesting finding. Let's hope it will come a day when we could select those 2 ROM's that are installed... so it will be possible install a stable ROM as primary, for daily use, while for the second we can opt for some test beta ROM's.
Super! Works very well but there is no multi-language. I'll wait: D
crub55 said:
Super! Works very well but there is no multi-language. I'll wait: D
Click to expand...
Click to collapse
I'm thinking of stealing walter79's version in the next release.
I am already on the latest version of walter79 and it worked fine in my (green lens)
Awsome
Sent from my MB525 using XDA App
can i install cm7 instead of miui???
j have a beug the video does not work even with or without the patch Simplestas
J have the green lens
It has been publicly tested for green lens -- was made for green lens after all
Sent from my MB860
racca said:
It has been publicly tested for green lens -- was made for green lens after all
Sent from my MB860
Click to expand...
Click to collapse
He want to say: the video didnt work for green lens (same is at mine) on MS2 not MIUI.
pictures are ok, i can make pics and see them in gallery.
when i press on video mode and start, the application block himself and no video recording.
And for the second rom (you chose MIUI) better please chose the MIUI from miuiandroid.com because the one from miui.us have many, many chinesse letter in menu after i chose english (i just tryed).
Will be nice when all work fine to help us and learn how to put 2 roms that we want
darktyroll said:
He want to say: the video didnt work for green lens (same is at mine) on MS2 not MIUI.
pictures are ok, i can make pics and see them in gallery.
when i press on video mode and start, the application block himself and no video recording.
And for the second rom (you chose MIUI) better please chose the MIUI from miuiandroid.com because the one from miui.us have many, many chinesse letter in menu after i chose english (i just tryed).
Will be nice when all work fine to help us and learn how to put 2 roms that we want
Click to expand...
Click to collapse
Sorry, missed that spot, it wasn't done by me and there are many many things I'm dissatisfied about the one I released.
This was put together in a rush before I have no time (like right now) to do anything further.
I am planning on making it a bit more flexible. And I have already made MIUI OTA via recovery usable as of now.
racca said:
I'm thinking of stealing walter79's version in the next release.
Click to expand...
Click to collapse
--------> ;-)
This work for say like cm7quarx and stock nordic
Sent from my MB525 using XDA App
Yes, with minor modifications
Sent from my MB860
Racca
can we choisire the rom for the dual system?
do it ourselves!
can you do a quick how to for install of your recovery, recovery files, and permisions that need to be set. I already know how to do the system image?
appreciated
cheers
rdannar said:
can you do a quick how to for install of your recovery, recovery files, and permisions that need to be set. I already know how to do the system image?
appreciated
cheers
Click to expand...
Click to collapse
I'll be doing a more simplified version with easier scripting to aid other dev. Just give me some time pls.
Sent from my MB860
Hola peoples!!! Ok so I just thought I'd create my own thread on this matter. Mustangtim started one in apps and themes (and here is the link to that thread) but since I'm taking over this project it was brought to our attention that this should be in the dev section as its no longer just an app.. I am actually tearing .imgs apart trying to figure out what the deuce.
FIRST OFF THIS IS A WORK IN PROGRESS, WE ARE NOT YET FULLY SUPPORTED. HOWERVER I'M DOING MY BEST TO CHANGE THAT.
Secondly if you want to help get this started please visit the market and grab the app here. Its a $3 dollar app for unlimited amount of roms, based on your SD card storage capacity anyway. And speaking of which you need AT LEAST a class 4 or better SD card to make this run smoothly.
Also feel free to visit the forums at http://forum.init2winitapps.com/
Ok so here it is, Boot Manager Pro. Its been a long time coming for the g2x to dual boot. First off let me say long story short, I currently have a bootable SD Rom, known as ROM1. I have yet to be able to recreate my findings tho. But it works and it doesnt brick at all. However it is a bit laggy on my class 4 SD card. Luckily I've already done my research on this project as there are many threads of such awesome info so I'm just going to be lazy about it and quote the good people of xda versus re-writing it based off of their info.
ChrisDDD said:
So here's a very basic description of how it works... It doesn't partition your SD card, it just creates a folder of its own, and then sub-folders to hold the different roms you install. When you install a rom, it basically creates images of the usual Android partitions - system, data, cache, & boot. These are standard .img files, just like the ones Clockwork creates when you do a backup. After the images are created and wiped (formatted, which you should do initially) it installs your rom into these essentially the same way as Clockwork installs a rom to your phone's actual partitions. I assume it modifies the kernel that comes with each rom to mount the image files on the SD card instead of the phone's partitions.
When you want to boot a rom, it just replaces your current boot image with the modified one and restarts the phone. With the modified boot image, the system, data and cache images on the SD card are mounted to the correct locations and Android starts up none the wiser. The rom will initially run a little slow, because the SD card is slower than the internal memory, but after things get cached it speed up considerably.
When you want to reboot to another rom, or back to the phone's rom, Boot Manager again swaps boot images that mount the desired rom's partitions (in the case of the phone's rom) or files (in the case of an SD card installed rom).
When you first run Boot Manager, it makes a Clockwork flash able backup of your current boot image, which you can flash if a rom hangs or loops on startup. Alternatively, you can also simply boot into recovery and do an advanced restore, choosing just the boot image to restore from a backup. It accomplishes the exact same thing.
It can be a little hit or miss, with some roms just plain refusing to start through Boot Manager, but it does work and when it does, it's pretty amazing given what it's actually doing.
Click to expand...
Click to collapse
So basically upon installing the app you need to setup your phone so that way you can properly install a ROM, follow these steps:
1. Go into the supersu(or superuser app) and then go to settings then disable logging or click none.
2. Then go into the BMP app and press the menu button on your phone, not the app, and go to settings. Once in settings put a check mark in force large boot.img, screen on during install, and then go into variables, leave tegra alone but change the sdcard block to show mmcblk1p1. Then press finish and let the app restart. By the way I didnt change any of the sizes of the .imgs but feel free to do so. But be warned do not decrease the size of the system.img only increase it, if desired.
3.Then after you've done the above you need to setup the phone rom. Click on 'Setup Phone' under phone rom and follow that process to setup your phone rom.
4. Once your phone rom is setup you may begin to install a zip to rom1 or rom2 or whatever slot you want. This is the tricky part. I have done tons of reading and most people say that if your using CWM, which us g2x'ers do, then you will probably have a better chance of getting a bootable rom by restoring from a nandroid backup you did versus installing new.
5. So after you decide which path you will take, nandroid backup or fresh rom install, choose install. If you choose a fresh rom, wipe system, data, and cache right away. If nandroid, then wipe after the install.
6. Now once you have clicked install put your phone down, DONT MESS WITH YOUR PHONE AT ALL! PUT IT DOWN AND WALK AWAY OR SOMETHING! Don’t mess with it, text from it, xda from it, dont even use the screen as a mirror!!!! lol seriously the app is picky and while under the .img creation process you want nothing to mess that up or you will not get it booted. You may however drag down the notifications bar to follow the progress of the install.
7. Once its complete, tap the install complete notification in the notification bar and let the app do its thing to finalize the install and get you back to your rom selection screen. Now if you did a nandroid back up here is where you click 'manage slot' and then factory reset the backup you did. Just do it, dont ask why.
7.1 Also so if you desire to install gapps and/or possibly a different kernel, now would be the time to do so while your here. I have read mixed reviews of doing this process right after the rom installs. However when I set up my rom1, I booted into it first all happily then realized I had no gapps. So I had to reinstall BMP on rom1 then boot back to phone rom and then I installed GB gapps and had no issues booting back into rom1.
8. Once the above steps are done if your feelin lucky go ahead and tap on boot the rom you installed, and if all goes well it will boot up.
9. If it boots up you need to post confirmation here!!! Provided info such as phone rom and the info on the sd rom you used and slot number and such.
Hopefully it will just work for you. I have done all the above steps using HFP 2.1 as my phone rom and only been able to get 1 bootable rom. Being it was for testing I used HFP as my phone rom and as well as my rom1.
So if the above steps dont wortk out for you and your boot lopped or what ever, then turn your phone off and reboot into cwm. You have 2 options to resolve the boot issue you just created. 1, you may go to restore then advanced restore then restore your boot. Or 2. select install a zip and nav to the bootmanager folder then phone rom then flash the update zip there.. then reboot and you should be back at your phone rom.
Here is a basic run down of everything that I have done so far:
When I first started working on this project I wasn’t doing any dev'ing to change any of the stuff in the boot.img. I just changed settings in the app per all the research I did. So when all was said and done I restored HFP 2.1 to ROM1 and it actually booted!! And it works lovely btw.. I can still boot into this rom today. I then decided to pass the word and ways that I created the working rom1, well I nor anyone else I passed the info to was able to get it working. Only one other person was able to confirm that rom1 works but only after I copied all my rom1 info and sent it to him for testing.. and he was able to boot into my created rom1… As I see it, it was a blue moon event that I have yet to repeat. So I thought eff it lets do some dev'in so I unpacked the boot.img from rom1 then compared that to the unpacked boot.img from rom2 that I created in my trial and error experiences. So in doing so I noticed 4 differences; 1, the mount points obviously, 2, in the sbin folder had a ueventd file from the working rom1 was a text file viewable by gedit in ubuntu. In rom2 it was just a non-readable file. 3, in the init.rc file was also missing a chmod command for system, (the command is in rom1 but not rom2) and 4, there was a ueventd.tegra file that was in rom1 that wasn’t in rom2, but everything else is the same. So I decided to plug and play with the differences to see if she boots and no go. I don’t understand why its boot looping because I am using the same rom as phone rom as for rom1 and rom2. So it boot looped. So I had to restore my boot.img many times in cwm.
So then I said eff it lets do some more research, then I noticed in the .zips folder plus the individual rom folder there are .zips that will let you flash via cwm if you get boot loops and 'should' get you booting to your desired sdrom. I then tried that way and no go.. so then I opened up the zip and had a look at the internals.. first there is the moveboot.sh file that the app runs in cwm flash the given boot.img. I then checked out the meta-inf and opened up the updater-script thinking that the app wasn’t actually flashing the boot.img which is why it loops... Well I think im half way right. However the script itself is lil dodgy... first thing I noticed was at the end of the script they have a command to cp the log from /tmp to /sdcard/bootmanager well the command was wrong so it never copied the log. So I fixed that. I also saw that the assert command was pointing to ‘boot’ instead of mmcblk0p5, so I changed that too. Then I decided to do away with the assert command and the moveboot.sh file they have going on to utilize the same functions that the kernel zips use, which is a kernel folder that holds the boot.img and a run_program that dd's the boot.img to 0p5. plus I even updated the update-binary that the file uses. I used the one from the g2x nullifier as I know that one was made for our phone and should have no issues.. plus there was a noticeable difference in the sizes of the provided binary to that replaced binary. So with the updated.zip file I then rebooted into cwm to flash that being that I was using a different command to flash the boot.img as well as the other changed stuff and still it boot looped. So as of now the only thing I don’t think ive done was grab the boot.img from rom1 then change the mount points, only change that, and then use that for rom2 and see if it boots. I don’t think I’ve done that yet. But every dam process I do I get boot loops. So basically I have came to the conclusion that it’s now NOT a boot.img issue being that I have done everything to change the boot.img and to make sure it flashes, which it does indeed and now creates the log too… I think maybe it has issues with the system.img as that’s what comes next in the boot process. But that’s just my hypothesis. I won’t be able to confirm this till I liberate rom1’s boot.img then change the mount points to point to rom2 and then see if it boots.. if it don’t work then that would mean to me that there is an issue with system.img created. But that’s just my hypothesis…
What I don’t understand is why the eff when I didnt hack the app I got a working sd-rom, but when I do change some stuff with it still don’t work!!???!! I guess maybe ill just edit/hack the apk to see what’s up.. This is getting way more complicated than it needs to be, since it worked prior to all my major changes to the script its using for flashing and the boot.img and what not. Anyone have any ideas feel free to add them.
My next steps are to edit rom1 boot.img one last time to change the mount points to point to rom2 and then if that’s a no go then it’s got to be the system.img that’s getting created. By the way this whole process I have only been restoring my nandroid backup for HFP 2.1. I have not attempted to flash new as with thru my research more times than not people would get a bootable rom via restoring versus flashing new.. so if anyone wishes to experience an sd rom let me know, ill send you a link to download my rom1 to get it going. Mind you that its not perfect and you need a class 4 or better sdcard. Everything works but it just takes a bit longer to load things and get things cached as its on the sdcard and not nand. Also if you have any input or are wishing to help pm me I need more heads to get this sorted as I can’t be the only one who knows how to edit scripts and unpack imgs and such. Either way I will continue to do this until I get it right damit!!! Oh and I just ordered a class 10 sdcard to help with this process…
That was copied from the other thread that mustangtim started. Last night when I went home the first thing I did was change the mount points on rom1 to reflect rom2, I changed nada else, then I tried to boot it... it boot looped. So maybe its a permissions issue or the system.img.
So just as a proof of concept and before anyone calls bs on my work/findings Here is the link to my rom1 that boots and is HFP2.1. *Update, 'm just going to
leave it on my DB for now till I find something better I guess. xda wont let me attach the file since its 233MB. Oh well here is the link :
Code:
[URL="http://db.tt/eBZwrOrs"][U][B]Here it is, my Rom1 HFP 2.1[/B][/U][/URL].
I have also attached my updated script file to flash back to rom1, for now.
The boot.img points to rom1 instead of phone rom, ill add to phone rom
as well, just not the now. :) Feel free to flash this via cwm versus
restoring...
Also this is part of the this: the ‘.zips’ folder you need to replace the file in
that folder as well. It’s an update file for rom1 to flash the boot.img.
..
If you’re going to use this you need install a random rom to rom1 then replace those created files in rom1 with these files in the 7z file..
So I am doing this new thread to get the devs or people with know how to help me out with my findings. I have edited the boot.img so much I could pretty much re-write everything in there by now including using magic to create to my own kernel eff!! lol jk but seriously I need people with knowhow to provide confirmation of go or no go. Basically I have people whom have helped out but It seems that I'm the only one who has dug this far into this app(unless i've been misinformed) and I have no one on my level to talk with except the init2winit devs. Which are very helpful btw.
And lastly:
Conap said:
Guys if it's failing to make the boot.img first make sure your using the market version....others have released cracked versions of our app which they broke...if your using the actual market version just send me a pm or email [email protected] and send your log.txt from BootManager folder on sdcard and we'll get it straightened out. Thanks.
Click to expand...
Click to collapse
or post here or PM me, I'm always down to help out.
Also thanks go to the init2win team, Gflam and Conap as they started this app. and as well to Mustangtim as he brought me into the light of BMP.
So you got all that???!!!??? Now lets get this party started and get full support for dual booting. I will not rest until I get this working. Thanks for your time and possible assistance.
Ok so since I have a book above I thought this is a good place for links and such...
So just incase anyone is curious, here is the Official Boot Manager Manual
Here is a nice link for Tips and Tricks while Installing ROM's that so far has good info to help you watch via adb what the BMP is doing in its creation process.
Some FAQs:
When should I set up my phone ROM?
Set up your phone ROM EVERYTIME you install a new ROM to your phone so you can get back to your phone ROM and won't get stuck on your SD ROM.
My SD ROM seems to lag how can I fix this?
SD ROM lagging may be due to a few things which all have easy fixes. First fix is that most of you have class 2 cards which are what usually come with your phones. These have a much lower read/write then cards of a higher class, we recommend a class 6 card or above. Another easy solution is overclocking merely install a better kernel and use CPU Boost (or any other overclock app) to overclock your phone.
Can I nandroid my SD ROM slots?
Yes and no you can't nandroid them in the traditional sense of the word using recovery but this app works as a recovery for your SD ROM slots and you can back up your ROM slots within the app in the Manage Installed ROMs section which works as a nandroid for your slots by fully backing up your slots to your sdcard which can later be restored.
What if I want to change the sizes of my images, how may I determine the individual sizes easily?
Easiest way is to open up terminal emulator in your app drawer. Type 'su', then grant permissions if need be, then type 'df -h' and it will display such information. You may also use adb in the same fashion. Connect via usb, open up command prompt/terminal and get adb connected and then type 'df - h' again and the same info will show. I will say this again just because, do not decrease the size of your system.img ever! Unless you want mad issues!
Here is the changlog link and just for heck of it the info based on that link:
Code:
V3.2.6
Fixed DroidX/Droid2 Install issue
Fixed UI theme issues
Fixed issue with spaces in name of pic when selecting photo for screen shot
V3.2.5
Fix to allow continue of install if no boot.img is found.
V3.2.4
Added support for HTC Rezound
Added support for rom's with multiple boot.img's
Added support for rom's made for multiple phones
AutoDetect sdcard for usb mounting
Fix for installing ICS gapps
Optimized SDRom Install process
Added support for Motorola RAZR
Added install queue
V3.2.3
Fixed issues with rom's not showing when on emmc on Droid Incredible
Fixed issues with not showing correct booted rom in app
More improvements to sms sync(all rom's will need updated app for changes to apply)
Fix issues with loader
Fixed issue with switching to backup server when main server goes down
Fixed 1x1 widget to show unlimited rom slots
Added 2x2 widget that works with unlimited rom slots
V3.2.2
Fixed force close for img's over 1Gb when resizing
Fixed current booted rom displaying correctly on gnex
Fixed issue with wrong busybox downloading on gnex which should fix alot of install/boot issues
V3.2.1
Fix for errors causing installs to fail.
Fix for some of the licensing stuff.
Removed sdbooster prefs from Galaxy Nexus(Since they don't have sdcard).
V3.2
Changed 4 sd slots to infinite slots!
Galaxy Nexus Support
Sms and Call Log synced between ROMs (you choose what ones too also requries updating boot manager in all slots)
License Check extended to a week
ROMs do not need market installed for boot manager to run (requires updating boot manager in all slots)
Hide su toasts (superuser elite only)
Fix for force close when setting screen shot in MIUI rom's
Thunderbolt defaulted to force large boot.img
Fixed unsupported device using a key
Manually setting variables only accepts numbers
V3.1.1
Fix for various force closes in rom installs and Nand restores
V3.1
Added su binary check
User selectable colors for everything
Better navigation (press title for quick action)
Added compatability for new twrp backups
Better compatiblitlity with memory tweak scripts(i.e. supercharger script and liquids default scripts)
Fix for install process being killed by android
Fix for some themes erasing img's
Fix more force closes during install
Force smaller boot.img option in settings(Fix for some phone's who's boot.img won't fit on the phone after BootManager edit's it)
Improved gapps checker
Improved security
Boot Manager now accepts keys pay for by paypal (see http://init2winitapps.com/stories/BootManager.html)
Added Evo 3d GSM Support
Added notifcation sound/vibrate for finished install (turn on in settings)
Improved data check
V3.0.3
Fix some force closes
V3.0.2
Added backup server (Sorry our server dropped out)
Fixed some force closes
2nd init fixes for Liquid's ROMs
V3.0.1
Last minute UI fixes
V3.0
UI Completely redone
Includes screen shot of each slot
Custom Info
Custom Dialogs
Custom Animations
Custom everything!
Bug Fixes
Added Droid 2 Global support
Screen shot with long press of search
V2.2.1
Bug fixes in file browsers
File browsers only show relevent files
Kernel installer fix
Droid 2 bug fix
V2.2
New security (more advanced and requires data only once a day)
Installs no longer require data
Added Italian translation thanks Black-Ice
Droid X support
Droid 2 support
Fixed status bar notifications
Fixed phone rom rebooter if gapps aren't installed
Bug fixes
V2.1
Restore android_secure to sd from nandroids
Added TWRP nandroid support
Added CWM tar nandroid support
Added Spanish translation
Made widgets easier to use
SD Booster added (Change SD read cache for better preformance)
Added current settings to manually set variables.
Added option to keep screen on during install in settings
Fixed usb layout
Updated Security
Bug Fixes
V2.0
Install now runs from the foreground (status bar)
Restore Nandroids to slots also in the foreground
User can cancel installs as they run
4 new themes added including one by apophis9283
Some phones such as tb moved to new install code (Fix for some sense rom's)
V1.3
Added third theme to app (Red Theme)
Added 4x1 widget and new widget styling
Fixed in app messenger
Added support for Htc Evo 3D
Added support for Htc Sensation
Added Support for Htc Incredible 2
Added Support for Htc Incredible S
Added Support for Htc Desire S
Added support for LG Ally
V1.2
Added option to reboot to phone rom to install gapps in license check dialog
Better error checking and error logging
Automatically install's ext2 libs if not present
Moved Set Names to Manage rom's
Fix for add-on's not installing correctly
Better compatiblility for rom's that use data2ext or apps2sd(user must set larger img's in manual variables)
Trash cleaner added to extras
Better Fix for WiFi issues on Droid 1
Added display to show what rom you are booted into
Fix for updater-script not found errors
Added support for Htc NexusOne
Added support for Htc MyTouch4G
More compatiblity for ext4 support
V1.1
Fix WiFi issues on Droid 1
Fix bug in rom installer for setting permissions correctly
Fix bug for cache size not setting correctly in setting variables manually
Fix for decimals entered into partition sizes causing force close
Fix force close in widget
Fix force closes in installer
Added Wipe data/Factory reset to Manage Rom's section
Added code to show what file's are being unzipped in dialog
Added support for rom's that extract files to sdcard so the files actually end up on your sdcard
Added support for Htc Desire (apps2sd and data2sd rom's support is experimental. Please email if you test it and it works/doesn't work)
Added support for Htc Inspire4g
Added support for Htc DesireHD
Added option to use ext4 filesystem if rom's support it-Experimental Won't work with all rom's.
Added log.txt file to sdcard to log errors during install
V1.0
Initial Release
YEZZZ
glad to finally see this here!
jookdakang23 said:
glad to finally see this here!
Click to expand...
Click to collapse
indeed... hopefully it wont be before too long that I get this app fully supported for us!
This app will be extremely useful for G2X owners and makes the G2X more versatile and desirable.
da-pharoah said:
indeed... hopefully it wont be before too long that I get this app fully supported for us!
Click to expand...
Click to collapse
idk how you get it booted. lol i keep getting bootloops
jookdakang23 said:
idk how you get it booted. lol i keep getting bootloops
Click to expand...
Click to collapse
Are you using the files I supplied or the ones that BMP created for you?
Woo hoo good job bud
Sent from my LG-P999 using xda premium
x0xhellx0x said:
Woo hoo good job bud
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
LOL thanks bro.... Go Team Hellfire!!!!
da-pharoah said:
Are you using the files I supplied or the ones that BMP created for you?
Click to expand...
Click to collapse
i remember requesting the files but think you ever sent them
jookdakang23 said:
i remember requesting the files but think you ever sent them
Click to expand...
Click to collapse
no we had a miscommunication due to our avail times and GB's lacking ability to utilize two accounts on gtalk.... I have posted those files in the op however...
First, I want to thank everyone who has helped with us on this app. Second, I know I picked the right man for the job, did you see that OP! All kidding aside, a lot of you know I write for ACS under screen name artifintel. I just had too much on my plate to give this project the attention and direction it needs. The right guy is in charge, he's a stand up person and very knowledgeable with this app. Good luck everyone!
[email protected]
I tried installing CM9, it didnt work, stuck on first boot screen after the LG logo.
I'm using rooted stock 2.3.4
Rafase282 said:
I tried installing CM9, it didnt work, stuck on first boot screen after the LG logo.
I'm using rooted stock 2.3.4
Click to expand...
Click to collapse
what rom are using as phone rom? and you installed to rom1?
da-pharoah said:
what rom are using as phone rom? and you installed to rom1?
Click to expand...
Click to collapse
As phone rom i;m using rooted stock 2.3.4 v21y
The to rom1 I installed CM9 kang from oiwan with gapps and harsh kernel
Rafase282 said:
As phone rom i;m using rooted stock 2.3.4 v21y
The to rom1 I installed CM9 kang from oiwan with gapps and harsh kernel
Click to expand...
Click to collapse
and no bootloop you say?? well then it may be the stock rom your using... The app is very picky and if you get a bootloop, I feel that those can get booted with tweaks... but stuck on lg screen is just no bueno.. Try a different rom... maybe one that has its partitions at ext3 format just to try it.. I think owains rom uses ext4, but I could be wrong. I havent fully researched his rom yet..
hands down, a badass app...
SiL3nTKiLL said:
hands down, a badass app...
Click to expand...
Click to collapse
lol +1 for sure!
da-pharoah said:
I think owains rom uses ext4, but I could be wrong. I havent fully researched his rom yet..
Click to expand...
Click to collapse
positive on ext4