Develop Bugs

[Q] Newb question: How do you flash custom ROMS

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.

[01 FEB][RECOVERY] ClockworkMod Recovery for HD2 - v1.3

READ ALL OF THE OP BEFORE POSTING QUESTIONS​
The Intro;
As we now have NAND booting for the HD2, its time we also had a way to flash ROMs from the SD aswell so here we have ClockworkMod Recovery compiled for the HD2. It is fully working except ROM Manager is not supported.
Recovery can now boot from NAND instead of the old SD Card boot method, to flash the rom, download the recovery with the partition layout you require, then flash as you would a standard NAND rom using DAF and MAGLDR USB Flasher. then select AD Recovery to load into recovery.
Click to expand...
Click to collapse
MAGLDR v1.13 IS REQUIRED, OLDER VERSIONS ARE NOT SUPPORTED, DOWNLOAD v1.13 HERE​
Click to expand...
Click to collapse
Kind note to Devs;
Please stop posting modified flash.cfg files for use with CWM
CWM is designed to make it easier to flash roms without needing a windows PC, if you post a different flash.cfg in each rom thread then it defeats this purpose as a pc will be required for flashing each layout.
Stick to using the default partition layouts or use USB flasher
Click to expand...
Click to collapse
WARNING MESSAGES:
GOING FROM A DAF FLASHED ROM TO A RECOVERY FLASHED ROM WILL WIPE ALL DATA
IF YOU FLASH ANOTHER ROM USING DAF, RECOVERY WILL NO LONGER WORK CORRECTLY, YOU WILL NEED TO REFLASH RECOVERY
Click to expand...
Click to collapse
Features;
-Flash ROMs in update.zip format
-Backup and restore ROMs using Nandroid
-Flash ROMs from the SD card without use of a PC
-Easilly Wipe all Data/Cache
-Repartition SD card for use with Apps2SD
-Full Root ADB access
-Fix app permissions
Click to expand...
Click to collapse
How to use;
For MAGLDR NAND Boot;
1. Download recovery with partition size for the type of rom you plan on using, see guide below if unsure.
2. Extract downloaded file and load magldr into USB Flasher mode.
3. Run DAF.exe and follow instructions
4. After completed and phone reboots, hold power key and select AD Recovery from list
5. Recovery will now load
Click to expand...
Click to collapse
For old style SD Boot;
1. download one of the partition files for SD Boot, if you don't know which one you need, use the 250M one or check with rom developer.
2. Extract downloaded zip to a folder of your choice
3. Copy contents of copy_to_sd_root (initrd.gz and zImage) to the root of your sd card
4. boot into magldr and select USB Flasher option while phone is connected to PC
5. Run DAF.exe included in the zip and follow onscreen instructions.
6. After complete, again boot into magldr and select "Boot AD SD" option
7. ClockworkMod recovery should load, you can flash a rom from here.
Click to expand...
Click to collapse
Video Tutorials;
How To Install Clockwork Mod Recovery On The HD2 (Courtesy of GFurr)
How to Install NAND Android on HTC HD2 with ClockworkMod Recovery? (Courtesy of jayceooi)​
Click to expand...
Click to collapse
Downloads;
Latest;
-Download v1.3 150MB-
-Download v1.3 250MB-
-Download v1.3 400MB-
Old Versions;
-v1.2- DOWNLOAD
-v1.1- DOWNLOAD
-v1.0- DOWNLOAD - MegaUpload Mirror
Old Partition Layouts for SD Boot;
-150MB System-
-250MB System-
-400MB System-​
Click to expand...
Click to collapse
Changelog;
v1.3;
-Supports AD Recovery in MAGLDR
-MAGLDR v1.13 REQUIRED Download HERE
-400MB Partition layout now works with 512MB LEO for roms with Data2SD
v1.2;
-Fixed SD-EXT Backup/Restore/Wipe
v1.1;
-Updated ClockworkMod to 3.0.0.5, now based on Gingerbread Source
v1.0;
- Initial Release
Click to expand...
Click to collapse
Q&A;
Q. Ive flashed v1.3 but cant access recovery anymore.
A. Make sure you are using MAGLDR 1.13 and are selecting "AD Recovery" instead of "Boot AD SD"
Q. Ive downloaded v1.3 but there is no copy_to_sd folder
A. Recovery no longer requires any files on the SD card, just flash it like a standard nand rom and select "AD Recovery in magldr menu
Q. Can I change the partition sizes used for CWM
A. You can by editing the flash.cfg but this is not recommended, CWM is designed to make it easier for switching roms, by flashing a custom partition size you may stop other roms working and require reflashing a new partition size when you want to change roms.
Q. I dont know which partition size to download
A. Depending on what type of roms you plan on using, you should choose the partition size based on the following.
150MB Partition - For bare roms including CyanogenMod, AOSP, and MiUI
250MB Partition - For Standard sense roms including Desire and EVo based ROMs, can also be used for some squashed HD builds
400MB Partition - For Larger roms including unsquashed Desire HD and Z roms, ROMs REQUIRE data2sd for EU HD2 with 512MB NAND
Click to expand...
Click to collapse
*I AM NOT RESPONSIBLE FOR ANY DAMAGE CAUSED TO YOUR DEVICE BY USING THIS RECOVERY IMAGE*
​
Click to expand...
Click to collapse
Notes for devs;
Please add tags to the title of your threads stating if they are to be flashed with recovery or DAF, [ZIP] for recovery update.zip and [USB] if its installed over usb using daf.
The cache partition is only 10MB so that recovery can still use it, to get cache to work in android, make a directory in data called cachemnt and on boot symlink /cache to /data/cachemnt, this does not apply when using 150M partition size
Click to expand...
Click to collapse
Credits go to;
-Cotulla + DFT for the great work for Android on NAND
-CyanogenMod team for work on recovery
-Anyone else who has made the HD2 a great device
Click to expand...
Click to collapse

i think i just wet myself....thanks so much

RaiderX303 said:
As we now have NAND booting for the HD2, its time we also had a way to flash ROMs from the SD aswell so here we have ClockworkMod Recovery compiled for the HD2. It is fully working except ROM Manager support still has some issues. See below for features and how to use.
Because ROMs are not flashed using DAF, a set partition layout is required before flashing any ROMs using recovery, included in the download is DAF which is configured to create the required partitioning, just run as you normally would to flash a NAND ROM and you are set to flash a new ROM through recovery
WARNING: GOING FROM A DAF FLASHED ROM TO A RECOVERY FLASHED ROM WILL WIPE ALL DATA
WARNING: IF YOU FLASH ANOTHER ROM USING DAF, RECOVERY WILL NO LONGER WORK CORRECTLY, YOU WILL NEED TO REFLASH THE PARTITIONING TO USE RECOVERY AGAIN
Features;
-Flash ROMs in update.zip format
-Backup and restore ROMs using Nandroid
-Flash ROMs from the SD card without use of a PC
-Easilly Wipe all Data/Cache
-Repartition SD card for use with Apps2SD
-Full Root ADB access
-Fix app permissions
How to use;
1. Copy content of copy_to_sd_root folder to the root of your SD card
2. Power on phone holding power button to access magldr menu
3. Select "USB Flasher" option
4. Run DAF.exe and go through installer to set required partition layout
5. After reboot repeat step 2 to access menu again
6. Select "Boot AD SD" and recovery will load
Download;
-v1.0-DOWNLOAD
Changelog;
v1.0
- Initial Release
*I AM NOT RESPONSIBLE FOR ANY DAMAGE CAUSED TO YOUR DEVICE BY USING THIS RECOVERY IMAGE*
Request for devs;
Please add tags to the title of your threads stating if they are to be flashed with recovery or DAF, [ZIP] for recovery update.zip and [USB] if its installed over usb using daf.
Credits go to;
-Cotulla + DFT for the great work for Android on NAND
-CyanogenMod team for work on recovery
-Anyone else who has made the HD2 a great device
Click to expand...
Click to collapse
You have to be ****ting me!!! Great work!!! Soon... Nandroid Got Your Back. LOL.
---
Sent from my HD2 DROID.

Great.
Sent from my HTC HD2

@Raiderx
Is the rom manager support you are talking about the ability to flash different themes and stuff of that nature in recover mode? Also can we expect it in the future?

This is now officially an android phone. Finally get to back up Roms awesome!!!!

Rom manager support is an app that allows you to control the recovery from within Android and then reboot to recovery to run the commands
Sent from my Desire HD using XDA App

Hell Yes
How will I install roms and where will I get them I am confused!

mattfmartin said:
@Raiderx
Is the rom manager support you are talking about the ability to flash different themes and stuff of that nature in recover mode? Also can we expect it in the future?
Click to expand...
Click to collapse
Rom manager is just the app that that you get from the market to flash without booting to recovery we could wait on that.

what the doctor
this is progress and what ive been looking to add

Just to clarify the instructions... Do we extract the Downloaded zip to the Root of the Sd Card then flash What ROM we will be using? Words in bold are my keys...
Thanks
EDIT: Scratch that.. I guess I should have opened the Zip first.
This is Bad Ass!!

Wow! My dreams have come true
Thanks!

Oh man, this is amazing! Any chance of Amon Ra at some point?

to cool
However I am confused about where I will get roms for this. Do I just use a nand rom and rename it update.zip? If so which files I am happy. Feels like the old G1 days. I am very confused about where to get the roms though.
HELP SOMEONE PLEASE!!!!!!!!

@Raider x
What I was getting at, I always see native android threads talking about flashing themes through recovery. Well we be able to do that with this?

jhr5474 said:
However I am confused about where I will get roms for this. Do I just use a nand rom and rename it update.zip? If so which files I am happy. Feels like the old G1 days. I am very confused about where to get the roms though.
HELP SOMEONE PLEASE!!!!!!!!
Click to expand...
Click to collapse
Devs will need to release ROMs in update.zip format, there are none currently released although i am in the process of uploading one, you then copy the zip the dev provides to the root of the SD, and flash like you did on the G1
mattfmartin said:
@Raider x
What I was getting at, I always see native android threads talking about flashing themes through recovery. Well we be able to do that with this?
Click to expand...
Click to collapse
you will be able to flash themes using recovery once theme devs create them

SWEET!!!!!!!!!!!!

jhr5474 said:
However I am confused about where I will get roms for this. Do I just use a nand rom and rename it update.zip? If so which files I am happy. Feels like the old G1 days. I am very confused about where to get the roms though.
HELP SOMEONE PLEASE!!!!!!!!
Click to expand...
Click to collapse
+1 good question, are we clear to load nand roms already or do the devs have to modify what they have? I think I will wait until more clarification.
Edit: thanks for the clarification

APJG said:
Oh man, this is amazing! Any chance of Amon Ra at some point?
Click to expand...
Click to collapse
What do u want from me? LOL As a matter of fact if i read this correctly this is almost what i need, a way to flash android ROMs without the usage of a pc (USB port). Can anyone tell me if it is correct

jhr5474 said:
However I am confused about where I will get roms for this. Do I just use a nand rom and rename it update.zip? If so which files I am happy. Feels like the old G1 days. I am very confused about where to get the roms though.
HELP SOMEONE PLEASE!!!!!!!!
Click to expand...
Click to collapse
Yeah, We need some ROMS converted to flashable.zip's... I'm goning to load up CW now just so I can see it. LOL

[Q] Making sure I do it right.

---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.

Boot manager

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.

[Q] Many questions (CWM, ROMs)

Hi,
I'm new here and I'd like to install a new ROM on my Gio but I want to make sure I know what I'm doing before trying something and bricking my phone. :angel:
ClockWorkMod
I installed CWM v5.2.0.6 (followed the instructions here). Is this ok, or do I need to install v5.0.2.7? And if I do need a newer version, is there a way to get an update or do I have to follow the same steps as before?
1.Download the CWM 5.0 v2 and copy to the Root (not in any folder) of your SD card
2. Put your phone in recovery Mode(press: Home button + Power button toghether)
3. In recovery mode, select the downloaded file from SD-card(Use Volume keys to navigate and home button for enter).
4. Search for the root gb updated.zip file on your SD-card
5. Run the update
6. Reboot
Click to expand...
Click to collapse
I tried creating a backup with the CWM version I have, but I get this error: "Can't mount /system".
CWM does create a folder in sdcard/ clockworkmod/ backup/ date, but it only contains the following files:
recovery.img and boot.img.
However, this post says I should actually have more files in the backup folder:
.android_secure.vfat.tar ,boot.img , cache.ext4.tar , data.ext4.tar , nandroid.md5 , recovery.img, system.ext4.tar.
Is this because of my CWM version? Or maybe because I still have the operating system that came with my device (+updates)?
What I really want to know is: can I rely on this backup, will it work?
ROMs
I want to install CM10.1.5 from here, but I have many questions and I don't really know where to look for answers. (Sorry, I really am a complete noob.)
What's the difference between androidarmv6 jenkins build and mardon build? And what's the difference between the 3 versions? Can I just install the Version with CM-Superuser and not worry about it?
Should the updates be installed via CWM - apply update from SDcard? What about the additions - CWM --> install zip from SDcard?
How can I install extras if they are "not CWM flashable"?
What happens to my apps when I install a new ROM? Do I have to install them all again? Is all data lost? Or will they all be restored from my google account and the SD card or something like that?
Finally, how can I use the ext2 partition in my SDcard to install apps? Is this function included in the ROM? Or do I need to install something else? a2sd darktremor? If yes, how (I find the instructions here confusing and overwhelming, and the post is old, so probably outdated)? Or should I use the "Link2SD" addition to the ROM?
I'm sorry for asking so much, but I'm feeling kind of lost.
Thanks in advance.

Anyone?
I've continued trying to figure things out when I have time. I'll post what I find in this thread, in case someone else comes here looking for answers to similar doubts/problems.
In trying to understand what's going on with ClockWorkMod Recovery, I found this very useful link:
wwwDOTtechbiiDOTcom / cwm-recovery-cant-mount-system-error-solution-how-to/
(sorry for the DOTs and spaces, can't post outside links yet)
CWM Recovery – Can’t Mount System Error Solution [How To]
(...)
The error is an expected one and happens generally when you are trying to backup a stock ROM using the clock work mod recovery. Please, note that you can’t do a completed nandroid backup of a stock firmwares. So, just install any custom ROM and then you can backup and restore anytime.
Click to expand...
Click to collapse
If I understood correctly, the best (only?) way to return to stock ROM is to install Odin or similar firmware flashing tool and to get the stock firmware from sites like sammobile.com and sampro.pl. However, it also says that not all firmwares might be available and I haven't looked more into it all of this yet.

Did you root your phone yet?
That should solve the problem from the can't mount system, data, etc
If you need more information, then look at this post http://forum.xda-developers.com/showthread.php?t=1397120

HerroYou said:
Did you root your phone yet?
That should solve the problem from the can't mount system, data, etc
If you need more information, then look at this post http://forum.xda-developers.com/showthread.php?t=1397120
Click to expand...
Click to collapse
Yes, I used the instructions there to root my phone and install CWM (v5.0.2.6), but that thread is 2 years old, so I'm afraid it won't be up to date in relation to certain things. For example, I did create an ext2 partition on my SD card using those instructions, but I found an easier way to move apps from my phone to the SDcard (using the link2SD app, available on Google Play). The information about ROMs is also not up to date.

If you want to install a custom rom just
-wipe data factory reset
-wipe cache partition
-advance>wipe dalvik cache
-install zip from sdcard
-reboot
NOTE: the zip is the rom

HerroYou said:
If you want to install a custom rom just
-wipe data factory reset
-wipe cache partition
-advance>wipe dalvik cache
-install zip from sdcard
-reboot
NOTE: the zip is the rom
Click to expand...
Click to collapse
Thank you.
My main concern at the moment is how to restore my original ROM if something should go wrong, though. I've found some interesting information in this thread but I've been busy this week and I'll need to go back and read it all with more attention before I try something.

Download ODIN 4.42 and GIO ops and a sotckrom MD5 file then put it into the odin and put your phone into recovery mdoe and plug it into your computer. Then click start

you have to put your phone in downloadmode to flash with odin as far as i know,but i have an other question;
can you use heimdall with the samsung galaxy gio

I am trying to flash a new recovery on my samsung galaxy gio with ODIN after it is bricked flashing tass- 6.0.4.5.zip(this cwm seems for the mini!!!) is this possible and if so,which one can?and how to do that...
thanks in advance

Yes it is possible and you need ODIN 4.42, GiPS and a Stock Rom extracted out of the zip.
Here is a video to help you because I am too lazy to explain
http://www.youtube.com/watch?v=euZqtaAMe5c