I'm currently running DINC2HD, and was wondering how boot manager works exactly. I'm going to be camping on the 10th, and I'm not sure if I'll have a reliable charging source. I was planning on running MIUI while I was gone. I don't wanna have to restore a backup and take the extra time for that. Can someone please tell me exactly how boot manager works??
Sent from my DINC2HD
if its anything like a multi-boot pc, it creates separate partitions on your card and saves each each install there and inside each partition is all the apps and whatnot, just like a regular install of a ROM is, but that's just me guessing, i don't have the app seeing as i usually stick to just one rom lol
digitalsynner85 said:
if its anything like a multi-boot pc, it creates separate partitions on your card and saves each each install there and inside each partition is all the apps and whatnot, just like a regular install of a ROM is, but that's just me guessing, i don't have the app seeing as i usually stick to just one rom lol
Click to expand...
Click to collapse
I usually do too, but like I said, I'm gonna be camping, and I'm not sure when/where I'll be able to charge, so I was gonna use a ROM I KNOW has amazing battery life.
When installing in BM, do I need to wipe and all that stuff, or is that only if I'm overwriting a slot?
tylerlawhon said:
When installing in BM, do I need to wipe and all that stuff, or is that only if I'm overwriting a slot?
Click to expand...
Click to collapse
Boot manager itself is just an app like any other, you don't need to wipe anything.
So here's a very basic description of how it works... It doesn't partition your SD card, it just creates a folder of it's 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, etc. 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 flashable 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.
ChrisDDD said:
Boot manager itself is just an app like any other, you don't need to wipe anything.
So here's a very basic description of how it works... It doesn't partition your SD card, it just creates a folder of it's 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, etc. 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 flashable 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, you're saying in theory I should be able to click install zip, find MIUI and without clicking any of the wipe options I should be able to make a usable MIUI setup that I can go back and forth to?
tylerlawhon said:
So, you're saying in theory I should be able to click install zip, find MIUI and without clicking any of the wipe options I should be able to make a usable MIUI setup that I can go back and forth to?
Click to expand...
Click to collapse
I think it's recommended that you wipe all three images when you initially install a rom, but that's the 3 images Boot Manger creates. I was just making the point that you don't need to wipe anything on your phone's currently installed rom.
But yea, after that, Miui should install and run just fine. You will need to install GApps to get the market on MIUI, since Boot Manager needs to install itself on each new rom you instal. This is so you can manage and reboot to other roms from roms installed through it. After that, you should be able to reboot back and forth at will.
I never had to install g-apps on MIUI before.... is that a recent thing?
Also, what Ext type should I choose? Ext4, or Ext2?
tylerlawhon said:
I never had to install g-apps on MIUI before.... is that a recent thing?
Also, what Ext type should I choose? Ext4, or Ext2?
Click to expand...
Click to collapse
Sorry, I was thinking about CM7, which doesn't include with the market app.
I've always installed as Ext2... never had much luck with 4.
I tried Boot manager while running CM7 and I was able to install it but got a force close when I open the app, I also try it with MIK's Inc2 HD 3D rom and didn't work either.
Related
I rooted my EVO running stock Froyo last night with Unrevoked 3.2. It worked flawlessly and phone is experiencing no problems. Now i'm all excited to run the custom ROMS but kind of confused as how the flashing of the custom ROMS works. Do I have to wipe out the entire contents of my SD card everytime I want to run a custom ROM? I only have the 8gig card. I was under the assumption that I could save my current stock setup and download and flash into a custom ROM and revert back to the stock rooted setup when I wanted. I downloaded a program called ROM Manager v2.0.2.6 but unsure how to use it. Looks like a 1-click solution to loading custom ROMs but I dont want it to wipe out my phone. Can someone please help me to understand the steps to take to load a custom ROM? I was thinking of trying out Fresh or something similar which still has HTC Sense in it. Feel free to message me on here. Thanks in advance.....
lostsoul1977 said:
Do I have to wipe out the entire contents of my SD card everytime I want to run a custom ROM?
Click to expand...
Click to collapse
No.
I'm not sure about using ROM manager, perhaps somebody else can help with that.
The process is simple...
Connect your EVO to your PC and enable disk drive.
Transfer the ROM zip to the root of your sd card (if your computer mounts as drive F: ... just transfer to F:\)
Eject/disable disk drive
Boot into recovery (turn device off, hold volume down and power button at same time until you see your hboot screen, choose recovery)
Perform a nandroid backup (just in case you need to get back to where you are)
Perform wipe
Use recovery option to flash zip from sdcard
Select the ROM zip
Those are the quick and dirty instructions, I'm a newb with this stuff, I've had my EVO for 2 weeks and I've not had a single problem. I had CM6 on it and I just flashed Fresh 3.2 to test that out and test 4G this weekend.
I would advise doing a Nandroid backup of your current setup. Then go the development section and choose a rom that suits you. Each developer normally will tell you how to go about flashing there rom.
Basically you would need to go into recovery and choose the flash from zip...
ok first no you dont have to erase your sd card every time you flash a rom.
you should however do a factory dalvik and cache wipe. this will erase all settings yuo previously had and will uninstall all apps.
to combat this you can use programs like Titanium back up to back up all your apps. (system settings are not recommended to be blind restored as they can cause issues between roms)
You can also make a back up of your stock rom you have now to do this through rom manager simply make sure you have the latest clockwork recovery flashed (very top button in rom manager) then go down to where it says back up rom click it and it will do the rest. This is recommended before you do anything.
once you ahve your nand back up (the back up through rom manager) and have your apps backed up through something like titanium back up. place the rom yuo want to flash on your sd card and follow these steps.
boot into recovery (either through rom manager or by powering down the phone and then holding vol down and power until it launches the boot loader and select recovery)
select wipe data/factory reset
select wipe cache partition
Select install zip from sd
select choose zip rom sd
scroll to and select the rom you moved to the sd card
select yes and let it do its thing once done select reboot phone.
It will take a little extra time the first time it boots up vs normal jsut let it sit and it should after a while boot into the custom rom.
or follow link
http://lmgtfy.com/?q=How+do+you+flash+a+custom+rom+on+an+evo
video assistance
Thanks everyone! I'm running titanium backup at the moment and backing up the entire system. I had ROM Manager do a backup of my stock ROM last night, so I think i'm good. ROM Manager also downloads ROMs for me and sets them to load at boot up. Most of the ROMS suggest doing a full wipe?
a full wipe jsut means factory/data cache and dalvik which is basically wiping all info on the phone itself. the sd card however doesnt need to be wiped
i installed baked1.7 and all loaded smoothly. I'm assuming I now have to re-download titanium backup to restore my apps and all?
Also, i'm finding no info on how to load the wimax update and the htc radio update files and the custom kernels for baked1.7
lostsoul1977 said:
Also, i'm finding no info on how to load the wimax update and the htc radio update files for baked1.7
Click to expand...
Click to collapse
Load those updates onto the root of your sd card. Get quickboot from the market to easily boot into recovery mode. Or you can power off, then hold vol down while powering on to get into bootloader and select recovery. Flash zip file and select those files. Reboot and your wimax/radio should be updated.
So, just messing around after i wiped my phone to install a different ROM, I did a backup of my wiped phone. If their is nothing on the phone, what is it actually backing up? It was like 365mb file, and I was to scared to run it after the fact (because I just know one of these times I'm going to push the limits and screw my phone up with my curious thoughts).
It's backing up the /system directory (mostly) along with the bootloader and clockworkmod recovery. The "wipe" option simply deletes everything on your cache and data partitions. You use it when:
~ You want to switch from (example) a rom to a different kind of rom, say virtuitous to cyanogenmod
~ You want to start from scratch again
Clockworkmod wouldn't let you delete your system partition without installing a new rom... this would be a bad idea
You can restore and boot off of that recovery you just made. It'll boot up with the "touch the android to begin" and google account setup wizard.
Sent from my T-Mobile G2 running Cyanogenmod.
ibemad1 said:
It's backing up the /system directory (mostly) along with the bootloader and clockworkmod recovery. The "wipe" option simply deletes everything on your cache and data partitions. You use it when:
~ You want to switch from (example) a rom to a different kind of rom, say virtuitous to cyanogenmod
~ You want to start from scratch again
Clockworkmod wouldn't let you delete your system partition without installing a new rom... this would be a bad idea
You can restore and boot off of that recovery you just made. It'll boot up with the "touch the android to begin" and google account setup wizard.
Sent from my T-Mobile G2 running Cyanogenmod.
Click to expand...
Click to collapse
Ok, so What ROM will be running though? Would it be the one that I had before the wipe?
---US Cellular / CDMA Desire--- not GSM!
I'm officially sick of waiting for USCC's 2.2 update, and I'm going to hope they release a RUU sometime in the future, so I can send in for warranty if I have to.
But I'll take that chance. Getting ready for my jump, so far I understand.
1) unrEVOked is the best way to get custom recovery (CWR), root, and S-OFF.
2) From the CWR, I perform a nandroid backup of my stock USCC rom.
3) From the CWR, I perform a wipe.
4) From the CWR, I apply the Cyanogen .zip
5) From the CWR, I apply the gapps .zip
And then I'll at least have 2.2 and app2sd+
So far so good?
In the future I would like to learn cMTD, and look at Phoenix or FTRapid roms that let me resize partitions for even more space, but one thing at a time.
Bonus question : If I want to modify the Cyanogen .zip file before I apply them, to like remove ADW and add a different launcher, I simply have to change the zip and then re-sign it using the SDK, right?
Really? 50 views and no one can tell me if I'm on the right track or missing something? I don't want to mess this up, and xda I was told is the only place to trust for real good info.
I never rooted a CDMA version Desire, but your steps seems to be OK.
But you forgot something. If you want to use the a2sd+, you must create an ext partition on your SD card.
Modifying the .zip? You can remove the apks by simply deleting from the zip file and copy over the new ones (does not know if you have to modify something else).
Also you don't need to sign it, just click on Toggle signature verification in CWR and you should be fine (at least it's working for me with unsigned .zips)
yes that is pretty much it, just make sure the rom file you downloaded is compatible withcdma desire
And when using cwm there is no need to resign zips, as it should not check the signature by default. Also instead of editing the rom file, you could always just remove the apps afterwards
Yep, looks good, although I would add cmtd and vork kernel.
Edit: Here is a walkthrough for everything. CMTD instructions courtesy of TheUltimateDroid.com
You can download firerat's CMTD files on MIUI: http://miui-dev.com/forums/showthre...ns-for-MIUI-in-4-Simple-Steps!&highlight=cmtd (download the files marked a,b,c,d)
Here is the 11/29 compile of Vork kernel. It's not the newest, but I found it to be the fastest. Courtesy of Navalynt: http://www.4shared.com/file/d8v4Ztz2/vorkKernel_bravoc_1129.html
Boot into recovery (you should already be rooted with clockwordmod recovery and s-off before you get to this point)
PERFORM A NANDROID BACKUP! (Under Backup and Restore select Backup) - you should have done this earlier
Select Install zip from sdcard
Select Choose zip from sdcard and select recovery-v1.5.6-CustomMTD_S.zip
Press the physical back arrow twice to make sure you are at the main menu of the recovery
Select Advanced then Reboot Recovery
Once you are back in recovery you need to select Wipe data/factory reset
Scroll down to Mounts and Storage then select to format /boot and /system
** At this point the recovery has been patched with the cMTD and all of the partitions have been correctly formatted so you can install your ROM
Now go to choose zip from SD card, select the CM version you downloaded and install
after that's complete, select the google addon (gapps) and install
after that's complete, select vork kernel and install
after that's complete, select the boot-v1.5.6-CustomMTD_S.zip and reboot.
You should be up and running after this with about 290mb of internal storage, CM6/2.2 and everything that entails and pulling down around 1900 in quadrant (on a clean install).
Awesome, thanks so much guys! Time to break some warranty~
fyi, you need SetCPU to take full advantage of that overclock kernel.
Akilldema: Thanks for the info on cMTD and the kernel. Seems very straightforward and I think I will try that right away too.
I love it when the thousands of threads and searches come up with 5 different ways to do 1 thing grrr......
Good thing XDA has a forum community willing to help a starter.
Thanks again!
tufkal said:
Akilldema: Thanks for the info on cMTD and the kernel. Seems very straightforward and I think I will try that right away too.
I love it when the thousands of threads and searches come up with 5 different ways to do 1 thing grrr......
Good thing XDA has a forum community willing to help a starter.
Thanks again!
Click to expand...
Click to collapse
If you're planning on doing cmtd, just follow those steps above exactly, it's everything you need to get the rom/kernel/cmtd installed. It's better to do cmtd when you initially flash the rom IMO, I've had trouble applying it later.
Success! Everything suggest here worked great, and everything is fabulous!
One quick followup, I noticed that Cyanogen doesnt actually use APP2SD+, they use their own modified version of the official FroYo APP2SD, which doesnt require a ext partition. (I think? Is that right?)
I have no problem making a ext partition and going the APP2SD+ route, but....how?
Can I do APP2SD+ with Cyanogen? Is the Cyanogen mod w/ the 290mb of space I have gonna be fine?
tufkal said:
Success! Everything suggest here worked great, and everything is fabulous!
One quick followup, I noticed that Cyanogen doesnt actually use APP2SD+, they use their own modified version of the official FroYo APP2SD, which doesnt require a ext partition. (I think? Is that right?)
I have no problem making a ext partition and going the APP2SD+ route, but....how?
Can I do APP2SD+ with Cyanogen? Is the Cyanogen mod w/ the 290mb of space I have gonna be fine?
Click to expand...
Click to collapse
You are right. For me personally, 290mb and the ability to move most of the app to SD is plenty of space. I have a ton of apps (everything I see that I want) and still only have 1 or 2 moved to sd. I never did the official apps2sd, it does cause slightly more strain on the card and I never neeeded it. However, here are instructions on how to do DarkTremor's apps2sd. http://www.theultimatedroid.com/forum/index.php?/topic/333-running-low-on-space/
You have to register there to see it, but link includes all files and instructions on how to do it all. Again, for me, it was unneeded.
Okay these are the steps I took and put as simple as possible.Some steps may be skipped depending on if you have done them or not.These are written based off my setup and what i did.
Disclaimer:Me nor Tassadar or bigsupersquid are responsible for any damage done to your phone so use at your own risk.
Multirom Install:
1.Format through cwm your sd card to have an ext(Recommended 512 mb)
2.Download the two zips from bigsupersquid posted here:http://forum.xda-developers.com/showthread.php?p=20626123#post20626123
3.Place them both onto your sd card.
4.Boot into cwm and flash the cwm zip you downloaded from squid's thread.
5.Now reboot your phone and then boot again into cwm(It should have blue text if it flashed correctly and the multirom option)
6.Now I highly recommend you make a backup of your current rom just in case anything goes wrong.(I made a copy of it onto my pc as well.)
7.Now flash the other zip titled "Multirom..." and wait for it to install.Now reboot to see if it boots.If boots then everything has been done correctly.
Rom on SD Card setup/install:
For this I have install on phone the latest build of cm for oV and will be using the same rom to setup on sd card just for test.
1.Now here Make another backup of your current rom through recovery(Will be used trust me)
2.Now flash the rom you want to use on sd card.(If using a 2.3 rom then the sd card crom msu also be 2.3 and vice versa for 2.2 roms).Reboot phone(a must so dalvik is created correctly).(Make sure to do the appropriate steps fro flash rom like wiping etc.)
3.Reboot back into recovery.Go to multirom and select "Create from current rom". (flash the multirom zip again if it says folder not found)(ROM on the sdcard is placed in /sd-ext/multirom/rom/).
4.After it finished you can go ahead and restore the backup you made in step 1. and the reboot after finished and wait until boot manager shows up.
5.Select boot from sd card and it should boot into the rom you chose to install to sd.(If it doesn't then you did one of the steps wrong).
6.That's it you now have multirom booting enjoy it !
MultiROM recovery menu description:
Active/deactive state is for recovery only, you can boot ROMs from backup in boot manager - that means its N-times boot rather than dual-boot.
When not active(boot from internal memory):
Activate (move from backup) - when you already have backup, this will move it to active folder (fast).
Activate (copy from backup) - same as above, but it copies it instead of moving
Create from current ROM - pretty self-explanatory
When active(boot from sdcard):
Deactivate (move to backup) - Moves current ROM to backup folder, so next boot will be from internal memory
Backup - Creates backup of current ROM
Erase current ROM - Deletes current rom, next boot will be from internal memory
Copy modules from int mem - Copies modules from ROM in internal memory to SDcard. Try this if WiFi does not work in SDcard ROM.
Thanks to Tassadar,bigsupersquid,everyone behind cm7 for optimus v and anyone else that contributed to this
Sounds awsome, gotta try the noob friendly lol....dont have patience for the more detailed one ;P
Sent from my LG-VM670 running ICS2.3.7 oc 806~825
any way to get link2sd to work with this. sdext doesn't appear to handle both multirom and link
what are the pro's n cons of this? someone please explain this to me b4 i attempt this. thanks.
Ventrue05 said:
what are the pro's n cons of this? someone please explain this to me b4 i attempt this. thanks.
Click to expand...
Click to collapse
Well pros would be you can dual boot between roms.Cons would be not many different roms since most are based off cm7 lol
why would i want to switch on the go from roms? im not being a **** or anything just wondering why someone would want to do that.
Ventrue05 said:
why would i want to switch on the go from roms? im not being a **** or anything just wondering why someone would want to do that.
Click to expand...
Click to collapse
Some just like the choice of having two different roms customized differently with different apps and such.
DarkLG said:
Well pros would be you can dual boot between roms.Cons would be not many different roms since most are based off cm7 lol
Click to expand...
Click to collapse
Plus you can partition a bigger space on your SD card giving you more room for apps
What is the likeliness this recovery will prevent you from flashing a different recovery.
There are a couple people trying to flash the rzrecovery and getting failed attempts.
eollie said:
What is the likeliness this recovery will prevent you from flashing a different recovery.
There are a couple people trying to flash the rzrecovery and getting failed attempts.
Click to expand...
Click to collapse
Hmm guess nobody has a answer to this...
eollie said:
What is the likeliness this recovery will prevent you from flashing a different recovery.
There are a couple people trying to flash the rzrecovery and getting failed attempts.
Click to expand...
Click to collapse
If you flash the recovery image using flash_image while booted into android, I think it's safe to say just about zero.
tdmcode said:
If you flash the recovery image using flash_image while booted into android, I think it's safe to say just about zero.
Click to expand...
Click to collapse
Something was not working right because a couple people using the multi recovery couldnt get rzrecovery to install. Not sure if they got IHO installed or not. I have a feeling something is not allowing flash_image to work properly with that recovery.
I just wanted to see what the devs of this recovery thought.
Tetris from recovery is worth it by itself! havn't installed a second rom yet but this is cool anyways
I accidentally wiped the system in TRWP and the phone won't boot, it just shows white screen with HTC logo and the red text down.
Did I just wiped my android from the phone?
I can get into bootloader and recovery. But I dont have rom in my internal storage. (because I deleted everything) How can I put rom.zip into my storage again and do the flash?
PLEASE HELP!
delete please have found an answer
JernejB2 said:
delete please have found an answer
Click to expand...
Click to collapse
Threads typically aren't deleted on XDA. If you found a solution, post it for the benefit of others that may have the same/similar issue.
In the future, you shouldn't be wiping anything, if you have no idea what it is, or what the outcome will be. It says right on the TWRP Wipe section, that the default wipe is the only one you need most of the time. And it says that for a reason. And the remaining options are also called "Advanced" for good reason.
Yes, "system" is the Android Operating System. By wiping it, you wiped the whole OS.
Recovering from this is typically done by putting a ROM on removable SD, or alternately using adb push to put a ROM on the phone. Then boot into TWRP and install the ROM.
You should also typically have TWRP backup of your current ROM, for easy recovery. Basic good practice to always have a TWRP "nandroid" backup whenever messing with the phone (root, ROMs, other mods). And there is usually not a good reason to wipe "everything" (all at the same time) and therefore also wipe your backups wherever they may be (internal storage or SD card).