I'm sure that a lot of people already know about the -=V6 SuperCharger=- by zeppelinrox.
If you are not familiar with his great work please follow the link above and read more about it on his thread.
Those of you who have already tried it on their HTC One S (stock) will probably know that there is a whole different level of complexity when it comes to installing it on an ICS ROM. First of all, on any ICS ROM you have to patch the framework library services.jar to get the full functionalaty of the V6 SuperCharger. To make matters worse the HTC Sense is an odexed ROM meaning that you have to do all the patching manually, which is by no means a trivial exercise. Of course you may decide that you don't want to go patching any files and you may be happy with the limited functionality that you get from the V6 SuperCharger as it is. If that's the case you probably won't find this thread very useful...
However, if you're one of those who will not settle for anything less than the full functionality, you need not worry anymore!
Over the last few days I've done all the hard work of decompiling and manually patching the stock services.odex library so people don't have to do it themselves anymore. Not only that, but I've prepared separate versions of the services.odex for each of the three launcher SuperCharge options available:
1. Hard-to-Kill (downloads 1 & 5)
2. Die-Hard (downloads 2 & 6)
3. Bullet-Proof (downloads 3 & 7)
In addition, I'm also including the stock services.odex file so you can restore it back to your system in case you have any problems with the patched files.
4. Stock services.odex (download 4)
Installation procedure:
DISCLAIMER: I take no responsibility whatsoever for anything that might go wrong with your phone, for any and all data loss, for bricking your phone, etc. You do this at your own risk and it is 100% your responsibility.
WARNING! The files provided are specifically for, and have only been tested on, HTC One S with Stock Sense ROM v1.53.401.2 (Europe). These files may also work fine on different versions of the Stock Sense ROM but I haven't tested that. However, if you use them on any other (custom) ROM they are most likely to get your phone either stuck at boot or into a boot loop!
REQUIREMENTS:
a. First and foremost your phone needs to be rooted and have BusyBox v1.16.2 or higher installed. This is a requirement for the V6 SuperCharger script to run so there's no way to get around it.
b. To install the patched services.odex file you ideally need to have a custom recovery installed, such as ClockworkMod. This way you can just flash the patched services.odex from the recovery and if anything goes wrong, simply flashing the stock services.odex over should get you out of trouble (stock file also provided as a recovery update). While it is not absolutely necessary to save a recovery image of your ROM, I would strongly advise you to do so as it's always a good idea to have a recent recovery image to hand just in case (e.g. there is a chance that the stock services.odex included in here may not work if you have a region/operator specific Sense ROM on your HTC One S). Please keep in mind that the stock services.odex included in here comes from Stock Sense ROM v1.53.401.2 (Europe) so it may not work on other versions of Sense ROM!
c. If you don't want to use the recovery update file, you can also download just the services.odex and install it manually. However, if you choose to do this then you're on your own as I don't have enough time to write a tutorial on how to install it manually.
Step 1. If you haven't already done it, go to the -=V6 SuperCharger=- thread by zeppelinrox and read up on the script and what it does.
Step 2. Follow the instructions on the thread (see Step 1) on how to install the -=V6 SuperCharger=- on a typical non-ICS system.
You can get the latest version of the script from this post: http://forum.xda-developers.com/showpost.php?p=18703418&postcount=5021
Step 3. Forget about manually patching the services.jar or the services.odex file! Just download the version you need from the bottom of this post AS WELL AS THE STOCK VERSION! You will need the stock if your phone gets stuck on boot. For the installation, see the two options below. Before you do anything however, I strongly advise you to save a system recovery image just in case.
a.The first 4 attached files, named update-services.odex-[something].zip, are recovery update files meant to be flashed via a custom recovery such as ClockworkMod. After flashing the recovery update, also wipe cache and dalvik cache and then reboot.
b. The last 3 attached files are just archives of the patched service.odex files. If you want to go this route you can find some guidance on the -=V6 SuperCharger=- thread in terms of where it needs to be installed and what permissions it should have. Also, if you're using this method don't forget to do a SuperClean & Reboot using the option in the V6 SuperCharger script.
Step 4. It is normal for the first boot after installation to take longer than usual. If your phone has gone past the boot animation and is displaying a windows saying something like 'upgrading applications...' then it's all gone fine so just wait for it to finish. If your phone hangs on the boot animation longer than usual it means that it's probably stuck there and the patched services.odex file is not compatible with your ROM. DO NOT PANIC! Simply go to the recovery instructions further on.
Recovery.
a. If you phone is stuck on the boot screen, hold the power button pressed for about 10 seconds so that the phone goes into hard power off (the touch keys below the screen will start blinking after a few seconds, that's normal).
b. After that just boot into recovery as you nomally do (while holding the volume down pressed, also press the power button briefly and the phone should start into the boot menu; in there, scroll using the volume up / down keys and select the RECOVERY option by pressing the power key).
c. In the recovery simply flash the stock services.odex update file, wipe cache and dalvik cache and reboot. Now the phone should start up fine but your services.odex will not be patched.
d. If your phone is again stuck on the boot screen, you'll have to do a full restore of your ROM from the image that I have strongly advised you to save earlier.
Good luck and I hope you find this useful!
Oh, and pleeease use the Thanks button!
thanx, just installed busybox then flashed "Hard to kill" thru recovery, booted right up on Noble 4.0
Bxrxyxaxn said:
thanx, just installed busybox then flashed "Hard to kill" thru recovery, booted right up on Noble 4.0
Click to expand...
Click to collapse
Thanks, but if you're using this patch on Noble 4.0 it will have absolutely no effect.
That's because Noble 4.0 is a deodexed ROM which means that the services.odex file you've just installed is simply ignored by the system.
Instead you should patch the services.jar file using the online patching tool for deodexed ROMs provided on the V6 SuperCharger thread.
will try on stock T-MobileUS nand later...but thanx for the heads up, will do, edit: Noble already has it
Flashed bullet-proof on stock TMOUS rooted ROM. Caused boot loop. No surprise, it's a different ROM but thought I would give it a go anyways.
Thanks for the post, will definitely use if I go with an EU ROM.
tmobile us
Will this work on the tmobile us one s? Update: noticed the post above stating it doesnt work for T-Mobile us.
Related
I'm pleased to present my repack of the stock ROM for the HTC Desire HD! READ THIS WHOLE POST BEFORE YOU START! No, really, it contains everything you need to know.
Remember that if you use this ROM, you do so entirely at your own risk!!
About MoDaCo stock ROM repacks
Unlike a MCR (MoDaCo Custom ROM) release, a stock ROM repack is as close to the stock ROM as possible. Only root / Superuser and an insecure boot image are added. The benefits of the repack are providing a rollback option in update zip format as well as providing an online kitchen to remove parts that are not required.
A MCR release of this version will follow soon!
Requirements
In order to use this ROM on your device, you must have a custom recovery image installed (Clockwork Mod).
Features
Repack of the 1.32.405.6 ROM
Pre-rooted with su and Superuser Permissions by ChainsDD
Insecure boot image (ro.secure=0)
Changelog
Please see the post below this one for the changes in each release.
Installation
To install this ROM:
Download the zip file of your choice from the links below (or the online kitchen) and copy to your SD card
Restart your device in recovery mode
PERFORM A NANDROID BACKUP FROM THE MENU
Select the option to apply an update zip, and select the zip file you copied to your memory card
Upgrading
No wipe is explicitly required in order to use this ROM (unless you are coming from a 'Sense' ROM), however if you do encounter issues of any kind, it is recommended that you wipe your device and reproduce the issue before raising it here.
Downloads
This ROM is now available in the online kitchen! In addition to the kitchen, a prebaked download is available.
DOWNLOAD
Thanks
It's impossible to mention everyone who contributes to the Android community by name, but to everyone out there who does great work and shares it with us all - you have my gratitude and respect.
And finally...
Details on how to donate should you wish to do so are in download topic at MoDaCo.
Enjoy!
P
Changelog
17/Nov r1
Initial Release
This is the STOCK ROM kitchen, the MCR kitchen will be online tomorrow!
P
YESYESYESYES
Can't wait for the MCR kitchen to be online!
sorry for noob question but this is my first experience with android...how can i make a nandroid backup...or if there is a guide can someone give me a link??
thanks
vitodecataldo said:
sorry for noob question but this is my first experience with android...how can i make a nandroid backup...or if there is a guide can someone give me a link??
thanks
Click to expand...
Click to collapse
You can perform a nandroid backup inside the clockwork mod.
1. Boot into Recovery (power off, hold volume down button and power on, then select recovery.
2. inside clockwork go to option 'backup and restore'
3. hit backup
4. wait a bit
5. your done
ther amybe a quicker/easier way to do this but this is how i did it.
I did not get this, I want the stock ROM. And the lastest one, I have not found a stable costum rom for my usage yet. I have looked at htc.com but I were not able to find anything to download. How can I get the lastest ROM from HTC? I'm going to change the kernel, but that's it. I want a stock ROM:
Did you guys know we can use androidiani open recovery on our xt720. lots of thing work like installing JITv7, memhack, zipalign. try it out beware tho i dont know what works and what doesnt. every thing i tried worked except spliting image for apps to sd and when you click console its goes landscape and expects you to type with the keyboard, and then you have to do a battery pull. and apps2sd symlink doesnt work either went to infinite reboot. try it out lots of stuff to play with way more that regular openrcovery. installs just like open recovery but at first will always go to lite version so you have to apply the update.zip to get to his recovery. and for those who have open recovery already installed jus replace and OpenRecovery folder on sdcard with one from androidiani, and place the update.zip on root of sdcard as well. good luck heres link http://forum.xda-developers.com/showthread.php?t=796679
Edit: kernal optimization option works to. Dont know what it does but installs correctly. And phone boots up fine.
Wow, I tried and it works! Really improved performance on my Gameloft HD games after using kernel optimization!
Thanks for sharing this!
any guides or step by step on how to do it?
I'm assuming the included(?) copy of Open Recovery 1.46 in Androidiani isn't compatible with the XT720? Which is why installing a modified Open Recovery for the XT720 first is necessary?
Regardless, I was able to get it to work by doing the following:
EDIT: The first boot after running zipalign seems to take much longer than usual, but it's not frozen. Just be patient.
- Following the Open Recovery 1.46 install steps from here (under Download & Installation: XT720):
modmymobile.com/forums/563-motorola-milestone-roms/531599-open-recovery-v1-46-11-21-2010-a.html
- Turn off phone, turn back on holding the Volume Up button and make sure it boots into Open Recovery. ('reboot openrecovery' from adb shell is supposed to work, but my phone rebooted into bootloader mode for some reason.)
- Reboot Phone
- Download Androidiani-OpenRecovery 3.3 from here:
code.google.com/p/androidiani-openrecovery/downloads/list
- Extract
- Overwrite the OpenRecovery folder on your SD card with the OpenRecovery folder from Androidiani-OpenRecovery.
- Power off phone and turn on while holding Volume Up to enter Open Recovery again.
Features I was able to get working (I haven't tested nearly all of them yet, however):
- Eclair Modding Menu > Install Jit7
- Menu Utility > Kernel Optimization Eclair
- Zipalign Compatible with Eclair and Froyo > Zipalign complete on entire system
Theoretically a number of the other Eclair mods should work too, but I haven't had the time to test them yet. Performance has improved with JitV7, Zipalign, and the Kernel Optimization though.
Interestingly, the .zip files along with Open Recovery and the Androidiani modification don't seem to be used.
Actually if you just put the openrecovery folder and update.zip from androidini and then follow the regular install directions from openrecovery it works also. And if u replace the lib and bin from jitV9 with the lib and bin from the openrecovery/mod/jit folder you can use the V9 instead of V7
easye420 said:
Actually if you just put the openrecovery folder and update.zip from androidini and then follow the regular install directions from openrecovery it works also. And if u replace the lib and bin from jitV9 with the lib and bin from the openrecovery/mod/jit folder you can use the V9 instead of V7
Click to expand...
Click to collapse
Maybe a dumb question...but where does one acquire jitV9? I don't see it on the Frozen Eclair page.
Riley600 said:
Maybe a dumb question...but where does one acquire jitV9? I don't see it on the Frozen Eclair page.
Click to expand...
Click to collapse
I was wondering about this also.
Look at the development sections there's a thread called new jit. But instead of replacing in the optimizer script I replaced it in the recovery for easy access and change.
do u guys try bench before and after when apply this..
my result when apply kernel optimize and zipalign is become slow .
after apply this my lingpack score only 10++..wth..if not 15++..also my productivity index with smartbench also reduce from 1000++ to 700++..
update#
need to restart after bootup..then my bench up again to 15++ mflop n 1000+ with smrtbench...hehe
Update 10/02/11:
For existing users of the ROM, flash the 2.2GB_NoCG_31_39.sbf (Link below). This will flash the rest of the ROM apart from the part that stops the ROM from being downgradable and system - Don't worry your ROM will be as it was before after flashing - you won't loose any data.
##CAN PEOPLE POST WHETHER THEY ARE HAVING GTALK/MARKET ISSUES PLEASE## Please also post if it is working ok for you
Back up after needing to sort out a few niggles and an issue with the rom including my Titanium backup license key. Now RC2.
Higgsy Modded 3.4.2 GB Froyo for Motorola Defy.
Fully working, no niggles ROM. Everything works. Its a blank canvas, All social networking blur stuff removed, some widgets, some other stuff.
Included:
Launcher Pro
Milestone Overclock
Titanium Backup
Widgetsoid2
Clockworkmod Recovery
Es File Explorer
Also:
Deodexed
Rooted/Busbox (Busybox installed in /system)
Over clock Script included with following freq/vsel 1000/52, 600/36, 300/26. (milestone overclock is not loaded as default - just go in and load module and set to apply on boot then forget about it)
Install process - this must be followed to the last letter - there is no variation so please don't ask.
If you have already followed the process to get onto a downgradable base, (i.e. you already flashed RC1, or, you followed the other thread Here then all you need to do is boot into clockworkmod, wipe data/cache and restore this. It will wipe everything again, sorry about that.
I never flashed a non downgradable .sbf before, such as 2.51 Eclair, or the GB/US Froyo, so can't vouch for whether it will work correctly on peoples devices that have done that, you should however just be able to flash the system/image if you've already got a 3.4.2 froyo base. If you have never either recieved the phone/flashed one of the undowngradable .sbfs, this process will ensure you keep you downgradibility.
Files Needed to complete This:
2.2 Chinese .sbf(Unzip the .sbf from the archive)
Higgsy_Modded_3.4.2_GB_Froyo_RC2 (Unzip and put folder in the sdcard/goapkrev/backup folder)
Superoneclick Root
Clockworkmod Recovery
2.2GB_NoGG_31_39.sbf(Unzip the .sbf from the archive)
1)Make a backup of all your apps with Titanium backup on your current ROM.
2)Boot into Stock recovery (Power On/Vol Down, then press bottom right hand corner of the screen when you see the warning sign) Then perform a data wipe.
3)Using RSD Lite flash the 2.2 Chinese ROM (Guide Here if you need it!)
4)Once the phone has rebooted, skip set up, root via superoneclick and then install clockworkmod recovery/apply.
5)Boot into Clockworkmod Recovery and wipe data/cache
6)Now got to backup/restore and restore the Higgsy_Modded_3.4.2_GB_Froyo.
6)Important! Once the restore is complete pull the battery, as you are reconnecting the battery hold volume up, so that it goes straight into bootloader.
7)Once in bootloader flash the 2.2GB_NoCG_31_39.sbf by RSD Lite
8)Once the above is completed it should reboot and you are done
PLEASE READ:
I don't recommend restoring settings via titanium backup, only apps/app data, in the past I have done this and found it problematic. I suggest to redo your settings manually.
If you want to use setvsel (as it now works fine with froyo) you need to remove the setscaling scripts I put in for overclock and also milestone overclock. Setscaling scripts are located: /system/xbin/setscaling.sh + /system/etc/install-recovery.sh
If you report a bug I need to know what roms /things you have flashed before, there are too many variables, most notably if you been on non downgradable roms
Enjoy!!!
Thanks go to:
Sorensiim - Hosting all my files
mcm_xyz - for the haptics fix
Bizzaboy - for info on updating media profiles, so improving video recording
Authors of all the apps included in here, donate or buy the full versions they are worth it!
Further updates I intend to release as update.zip's, looking at themes, bugfixes (even though there aren't any that I can find) etc etc...... Please don't pester me for these, I do it as a hobby and sometimes don't have time for days to do things.
Change log:
03/02/11
RC2 release
Removed my TI Backup license that I had inadvertently included
Removed various info from the data.img, that I believe could have been cuasing some of the niggly issues people were having.
01/02/11
RC1 Initial Release
fantastic work !!!! will try after i'm gone from work
+1 looking forward to trying after work today
how to edit the overclock script ?
my phone could run on [email protected] , [email protected], [email protected] , [email protected] very stable
008325 said:
how to edit the overclock script ?
my phone could run on [email protected] , [email protected], [email protected] , [email protected] very stable
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=880851
Hey higgsy, i didn't flash your ROM yet but i have a question
At the moment I have a Defy which is on 2.34, and I didn't upgrade yet because i NEED a downgradable ROM (for warranty reasons, the DE version is still at 2.21)
now thanks to your tutorial, i can upgrade to froyo while being able to downgrade to the official 2.21 if needed, but here's my question:
what happens if i nand restore a different ROM based on the 3.42 UK rom (like HandlerExploit's upcoming Vanilla version), will I still be able to downgrade?
(e.g. does restoring a backup WITHOUT flashing a new sbf make your device undowngradable?)
yozgatg said:
Hey higgsy, i didn't flash your ROM yet but i have a question
At the moment I have a Defy which is on 2.34, and I didn't upgrade yet because i NEED a downgradable ROM (for warranty reasons, the DE version is still at 2.21)
now thanks to your tutorial, i can upgrade to froyo while being able to downgrade to the official 2.21 if needed, but here's my question:
what happens if i nand restore a different ROM based on the 3.42 UK rom (like HandlerExploit's upcoming Vanilla version), will I still be able to downgrade?
(e.g. does restoring a backup WITHOUT flashing a new sbf make your device undowngradable?)
Click to expand...
Click to collapse
Its flashing the sbf what locks you out of being undowngradable. simply restoring a system and/or data partition should not cause an issue. Ask the authors of the other ROMs, I can't comment on what effect there releases will have on your phone.
could we have some screens?
fabianowerner said:
could we have some screens?
Click to expand...
Click to collapse
Screens are pointless mate, its a blank canvas there is no theming etc. the screens in my 2.2 CN thread are pretty much the same
Looks nice,
so far running very smooth every thing ive tested and works well as far as i can tell!!
although I cannot got into recovery just get a black screen
Overall very nice cheers!!
Duh! I just flashed the uk rom posted by iaio72. I just realize it is not deodexed and i *must* (must?) replace that statusbar. If i understand correctly, it is not possible to theme odexed roms, right? Do you think i can just flash your system image or may this raise some issues ?
Higgsy, first of all thanks you very much for this rom, but I have a "little" problem. With a clean nandroid and with your, I have problems with gmail notification and "google talk connection problem" (don't know how is exactly writen, I have in another language)
what can be?
Edit: Just say: "Google Talk failed to login. If this is a google Apps account, confirm that Chat service is enabled for this account."
add.thebad said:
I cannot got into recovery just get a black screen.
Click to expand...
Click to collapse
Just a blind guess: you did disable usb debugging before booting into recovery, right? This is mandatory for froyo (don't know why though).
Another, market is not the new.
Edit: Now is up to date, it just didn't want to update, or install app. Removed data and restarted. Somebody know something about the other issue?
If I already followed the safe upgrade to 3.4.2, it should be good enough to simply do a nandroid restore and flash devtree again, right? I so want to get rid of blur
Camera not working!
Everything run smooth but the camera is not working.
if i'm already on 2.51 (it came stock), how do I go about flashing this froyo release?
Can anyone help? thanks.
Hi, Thanks for the good work
I've the same problem with Talk, authentification problem...
I've another problem with the LED from camera doesn't work.
Any idea?
gratias mate, for your work.
I had the blur-UK ROM installed, so I was able to restore your system.img only. Non of my data got lost and it's running smooth on your deblured version
I've got some questions regarding the install documentation of Simply Honey 5.1 Revolution for SGS ROM
Install Instructions Coming From Froyo OR ECLAIR(CM7/MIUI ODIN TO STOCK FIRST)
First Question regarding CM7 - Does this include CM7.1 as well? The example outside the parenthesis says Froyo or Eclair - CM7 is GB so this is not clear
- 1. Disable any Lagfix.
- 2.Download - xxx LINK REMOVED xxx This is the light version with hardly any apps and only one keyboard and 4 lock screens.
- 3. Flash via ODIN. USE 512PIT FILE.
- 4. Let phone boot. Wait 15 minutes and reboot.
- 5. Enjoy. You may now proceed to the MediumOR Large.
What is the difference between medium and large? Where are these files? I see a Light and Full but nothing else.
[/SIZE]
Install Instructions
Coming from Any Gingerbread Rom (If bootloaders aren't installed or you have trouble follow steps above.)
CM7 issue listed above. Any GB rom sounds like any - including CM7 this adds to the confusion of what will/won't work here.
1. You must first be running a Gingerbread rom (Doesn't matter Lindroid, Rainbows, your cousins top secret GB rom.) If you are not then please follow instructions above.
2. Place SimplyHoney5Beta1.zip on your SD card
Filename is out of date. Please link new file or list correct filename. If the ROM is out of Beta, the filename in the instructsions should reflect this.
3. Use rom manager or flash through recovery.
4. Let phone boot. Wait 15 minutes and reboot.
5. Enjoy
The new script is wipe for who come from SH <3.3 and from Froyo/GB!
It doesn't do wipe if you're running SH 3.5+ ROMs! Very Simple and automatic!
I've called it the "Anti-Noob" Script!
ONLY FOR CWM VERSIONS!! ODIN VERSIONS ALWAYS DO WIPE!!
Downloads CWM Full Roms
Simply Honey 5.1 Final
Light: xxx LINK REMOVED xxx 5 Locks Screens/ Modify Power Control Menu Options
Full: xxx LINK REMOVED xxx 10 Lock Screens
What is the purpose of Update1? Should this be flashed after Full? Is it flashed through CWM recovery? Some additional information here might be helpful. It is linked but no indication of why or when one would use it.
- Update1 - Gallery3D, Polaris Office, SNS Account -
xxx LINK REMOVED xxx
Is this section below a second set of instructions - you seem to list a If you have problems section above; however this one is more comprehensive. I'm not sure which one to follow if I have problems.
HOW TO
The anti-noob install script is a double edge sword so to speak. On one hand it is convinient as it doesn't do a wipe install if already on Simply Honey 3.5 and up. On the other some data needs to occasionally be wiped. That said if you experience ANY problem please follow the steps below.
1. Force Close of certain apps...go to settings/applications/manage applications/all and clear data of the offending app.
If that doesn't work then use Tiatnium backup to wipe data and uninstall the app (as long as it's not a system app such as phone or contacts or settings, you get the picture. Now you are free to re-install the app.)
2. The next step is to try and re-install the rom. Boot into recovery and select install from SD. After it's done and you reboot give it the 15 minutes. Now try again to recreate the original problem.
3. If the problem persists then boot recovery and wipe data factory reset and re-install the rom.
4. Problem still there then ODIN to stock (Stock ROM recommendation?)with repartition, ODIN the Simply3.8 Odin/Heim package. After rebooting boot into recovery and install the latest release of Simply Honey.
If these instructions are still useful, please link to SH 3.8 Odin/Heim package pls.
5. If all else has failed make a backup of everything you want saved to your computer. Boot recovery and go to mounts and storage and select format SD. After it's done reinstall Simply Honey's latest release.
6. If your problem still remains after doing all of this or just the last step then I suggest finding another rom as this one may not be for you.
I made an attempt to convert from CM7.1 this weekend; it wasn't clear what was going wrong but I couldn't get SH 5.1 to load properly. I tried to Odin the SimplyHoney 5.1 light version as per the first group of instructions, however, it was unclear whether I needed to repartition or not. the phone began the robot voice indicating partitions were not correct. I odin'd back to stock and reflashed CM7 with no problems.
Please understand I'm not trying to be critical, and I have rooted/flashed a number of phones over the years. Although I've been a fan of CM in the past, it's absolutely not where it needs to be on the Galaxy S/Vibrant and the Nightlies are not getting there fast enough. After reading the settings/features and positive comments for this ROM I'd really like to try it out, but the vague instructions and lack of links are not making this process easier.
If one of the developers can answer some of these questions, I'd be willing to assist writing documentation for this and future SH releases.
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