how should i install miui over cm7 rom ??? Should i go back to stock or is it ok to use CM7 cwm recovery ???
You can just use the recovery that came with CM7, no need to flash to stock.
*Get Chance and Luck*
And what if i want to go back from miui to cm7? Should i have to go back to stock or miui cwm wil b ok to flash cm7 ?
again no need to flash to stock...as MiUI is based on CM7...only flash to stock if you are going to flash to non-CM7 (MIUI) rom.....
also flash to stock if you are stuck in bootloop....
To follow up / add on to what vinyl2cool said, you can think of it this way:
MIUI, CyanogenMod, and ICS are all based around CyanogenMod's take on Android. It may take a couple of reflashes in CWM to move between them, but they will all work together, no special steps (e.g. Odin or Heimdall) needed.
Any rom with a 3-letter acronym starting with J or K (e.g. KK4, JVZ) will allow you to jump to another one from CWM. It may take a couple of preparation steps, but again, you shouldn't need Odin or Heimdall.
Pretty much the only time you will need Odin or Heimdall for rom flashing is if you're jumping between those two camps. (That's not to say there aren't cases where Odin/Heimdall have other uses, but that's another topic for another day.)
Related
Hi,
I am currently on the Darky v7.0 and I wanted to flash to 7.0.2
Do I just copy the rom in the sd folder and flash using rom manager just as i did before?
or do i have to switch back to stock 2.1 (rogers) and then flash 7.0.2?
This will be my second time flashing.
Please advice.
Thanks
Just install it over 7.0 if you got the non wipe version.
peachpuff said:
Just install it over 7.0 if you got the non wipe version.
Click to expand...
Click to collapse
This is the thread and the link to it. it does say "No wipe".
[ROM] Official Darky Port v7.0.2 No Wipe]
http://forum.xda-developers.com/showthread.php?t=880859&page=53
so does it mean its ok to install over 7.0?
does no wipe mean i dont have to wipe/remove the rom before flashing a new one?
Thanks
I too am curious why we are told to revert back to 100% stock before every time we change a rom. Why can't we just use Clockwork Recovery to wipe data/factory reset just like we do with every other Android phone?
Phateless said:
I too am curious why we are told to revert back to 100% stock before every time we change a rom. Why can't we just use Clockwork Recovery to wipe data/factory reset just like we do with every other Android phone?
Click to expand...
Click to collapse
samsung, in their infinite wisdom, decided rfs was the best filestructure to use for this phone. some roms change that to ext4 with voodoo, some roms rely on ULF to convert to ext4 and some dont convert anything.
ODIN is the user-friendly way to wipe everything back to stock...completely. if you remember to revert any lagfix (voodoo, ULF) then load your rom, it will work fine.
HOWEVER, there are so many people that dont remember to do that, its easier to flash back to stock rather than troubleshoot what could have possibly happened during their flash
personally, i have found that it takes just as long to revert the lagfix as it does to use ODIN....so rather than hoping that my new flash isnt corrupted in some way by my old flash, i flash back to stock. takes me 5 minutes total. as long as you keep a copy of the CWM update.zip on your sdcard, there is not even a reason to boot back into stock and root/setup/install rom manager, etc.
Pirateghost said:
samsung, in their infinite wisdom, decided rfs was the best filestructure to use for this phone. some roms change that to ext4 with voodoo, some roms rely on ULF to convert to ext4 and some dont convert anything.
ODIN is the user-friendly way to wipe everything back to stock...completely. if you remember to revert any lagfix (voodoo, ULF) then load your rom, it will work fine.
HOWEVER, there are so many people that dont remember to do that, its easier to flash back to stock rather than troubleshoot what could have possibly happened during their flash
personally, i have found that it takes just as long to revert the lagfix as it does to use ODIN....so rather than hoping that my new flash isnt corrupted in some way by my old flash, i flash back to stock. takes me 5 minutes total. as long as you keep a copy of the CWM update.zip on your sdcard, there is not even a reason to boot back into stock and root/setup/install rom manager, etc.
Click to expand...
Click to collapse
Thank you, that's the answer I was looking for. I already noticed that CWM can be flashed through an update.zip, so if I'm currently running the stock rom I don't have to ODIN and wipe data, do I? I can just flash CWM, nandroid, then go ahead and flash whatever I want?
Then NEXT TIME I flash something else I'll have to ODIN first.
Or does the user data already present in the stock rom make enough of a difference that I should ODIN anyway?
Phone is my gf's so I would really like to have a nandroid of her setup exactly as it is now so we can go back if she doesn't like Cognition, or whatever rom we decide to flash.
Phateless said:
Thank you, that's the answer I was looking for. I already noticed that CWM can be flashed through an update.zip, so if I'm currently running the stock rom I don't have to ODIN and wipe data, do I? I can just flash CWM, nandroid, then go ahead and flash whatever I want?
Then NEXT TIME I flash something else I'll have to ODIN first.
Or does the user data already present in the stock rom make enough of a difference that I should ODIN anyway?
Phone is my gf's so I would really like to have a nandroid of her setup exactly as it is now so we can go back if she doesn't like Cognition, or whatever rom we decide to flash.
Click to expand...
Click to collapse
you are correct in assuming that if you are running stock currently, you do not have to odin first
if you remember to revert any lagfix that may have been applied (depends on rom) you wont have to ODIN
make a nandroid of her current setup.
now this is where it gets tricky. i just played around with doing this last night actually:
if you go from 2.1 to 2.2 or higher, you cannot just flash back to 2.1 nandroid restore. the nandroid doesnt backup or restore your modem and kernel
going backwards to 2.1, you will want to flash a 2.1 kernel, and modem prior to restoring your nandroid backup and vice versa if you make a nandroid of 2.2 and want to go back to it from 2.1
if you keep clockwork flashable versions of such needed kernels and modems as well as a nandroid of the original setup and the cwm update.zip file on your sdcard, you will never need odin...unless there is a major malfunction. this can all be done in CWM, but as i said, the noob-friendly, and surefire way to get a fresh install is ODIN. i dont think any other company has something like this available to flash back to stock, so the methods used on the roms in the galaxy s phones are slightly different than the roms for htc or motorola devices. to me, i think this is a major win for us, in that most things are easily recoverable using a windows tool
Pirateghost said:
you are correct in assuming that if you are running stock currently, you do not have to odin first
if you remember to revert any lagfix that may have been applied (depends on rom) you wont have to ODIN
make a nandroid of her current setup.
now this is where it gets tricky. i just played around with doing this last night actually:
if you go from 2.1 to 2.2 or higher, you cannot just flash back to 2.1 nandroid restore. the nandroid doesnt backup or restore your modem and kernel
going backwards to 2.1, you will want to flash a 2.1 kernel, and modem prior to restoring your nandroid backup and vice versa if you make a nandroid of 2.2 and want to go back to it from 2.1
if you keep clockwork flashable versions of such needed kernels and modems as well as a nandroid of the original setup and the cwm update.zip file on your sdcard, you will never need odin...unless there is a major malfunction. this can all be done in CWM, but as i said, the noob-friendly, and surefire way to get a fresh install is ODIN. i dont think any other company has something like this available to flash back to stock, so the methods used on the roms in the galaxy s phones are slightly different than the roms for htc or motorola devices. to me, i think this is a major win for us, in that most things are easily recoverable using a windows tool
Click to expand...
Click to collapse
That makes sense, thanks! Over in HTC-land we call them radios instead of modems, and kernel/spl/radio all have to be compatible. Most are compatible with each other so there is seldom a need to flash around.
So what I gather from your post is that if she starts on stock 2.1 and I flash cwm, then flash Cognition (2.2 rom) I will most likely need to update the modem to match? Or is that only the case with stock roms?
Phateless said:
That makes sense, thanks! Over in HTC-land we call them radios instead of modems, and kernel/spl/radio all have to be compatible. Most are compatible with each other so there is seldom a need to flash around.
So what I gather from your post is that if she starts on stock 2.1 and I flash cwm, then flash Cognition (2.2 rom) I will most likely need to update the modem to match? Or is that only the case with stock roms?
Click to expand...
Click to collapse
most all the custom roms you will find will flash a kernel and modem that match and work properly with that rom
it really only applies to nandroid backups going from 2.1 to 2.2 and vice versa
Pirateghost said:
most all the custom roms you will find will flash a kernel and modem that match and work properly with that rom
it really only applies to nandroid backups going from 2.1 to 2.2 and vice versa
Click to expand...
Click to collapse
So you're saying when you flash the rom it will flash the correct kernel and modem as part of update/install script?
So basically I just need to install CWM, flash the rom, and not worry about the rest?
Phateless said:
So you're saying when you flash the rom it will flash the correct kernel and modem as part of update/install script?
So basically I just need to install CWM, flash the rom, and not worry about the rest?
Click to expand...
Click to collapse
yep
you dont need to worry about the rest until it comes time to flash to something else
there are a few options when that time comes:
use ODIN to restore to stock, then flash the next rom of your choosing
revert lagfix (if applied from the current rom you are running), then flash next rom of your choosing
if going back to a 2.1 NANDROID, not custom rom, then you will either need to odin, then flash.
or
flash 2.1 compatible kernel+modem and then restore your nandroid
Pirateghost said:
yep
you dont need to worry about the rest until it comes time to flash to something else
there are a few options when that time comes:
use ODIN to restore to stock, then flash the next rom of your choosing
revert lagfix (if applied from the current rom you are running), then flash next rom of your choosing
if going back to a 2.1 NANDROID, not custom rom, then you will either need to odin, then flash.
or
flash 2.1 compatible kernel+modem and then restore your nandroid
Click to expand...
Click to collapse
Got it. That all makes sense except for the kernel. Shouldn't that be included in the nandroid? I know the modem probably resides on a separate partition...
Phateless said:
Got it. That all makes sense except for the kernel. Shouldn't that be included in the nandroid? I know the modem probably resides on a separate partition...
Click to expand...
Click to collapse
the nandroid doesnt backup the kernel OR the modem as far as i know. either that or it doesnt flash them on the restore...
Pirateghost said:
the nandroid doesnt backup the kernel OR the modem as far as i know. either that or it doesnt flash them on the restore...
Click to expand...
Click to collapse
At least with HTC the kernel is part of the Rom and IS included in nandroids.
I installed ROM manager and flashed clockworkmod recovery but when I hit reboot into recovery it goes into the normal android recovery screen. I also tried doing a backup of my old rom but it just reboots into stock recovery screen and doesn't actually do the backup. I tried installing ROM from SD, same thing. I've tried different recovery versions (2.5.1.1, 2.5.1.2) but they all do the same thing. I'm rooted and it has superuser permissions, so that's not the problem. I have ROM manager premium. I've tried uninstalling and reinstalling ROM manager. Please help.
Try installing it through stock recovery. (reinstall pakages)
What firmware you using?
rom manager is only good for eclair and froyo
there isnt a correct update.zip for the captivate on gingerbread.
if on gingerbread flash a kernel with CWM (clockwork) built in.
if on froyo/eclair you must select *reinstall package* from android recovery TWO TIMES in a row!
except FROYO has recovery3e also.....it will not allow unsigned update.zip files.
Ok. I'm on Froyo 2.2. Stock firmware. Trying to get either Fasty II or Cyan. First time doing all this. All this started with the GPS problem... (I know, I know. There's a thread for that.) Plus, I am interested in other ROMs. Just praying I don't kill my phone in the process.
you need to look at Odin/heimdall a CWM kernel, or fixing your recovery 3e to accept unsigned zips
^That. Fasty II needs Gingerbread bootloaders
OK. Well, really, I think I'd like to go Gingerbread. I dunno. There's too many to choose from. I want to get CWM working first. Where's the forum to install manually? There's so many places to look...
If you are going to GB flash a leaked stock first that contains boot loaders. Does your phone take well to 1 clicks?
Augh! I used Odin to flash the kernel. I had a temporary success. I had cwm up and it backed up my old rom. I rebooted twice into cwm. Third time, it reverted back to old android recovery. Like I said... Augh!
-Typed while driving on my Captivate- []
Flashed it again. Got CWM back up. Now, moving on to figuring out getting gingerbread. Any tips here are greatly appreciated as long as they make sense.
Also, what is 1 clicks?
Odin 1 click that will flash a leaked stock rom like 2.3.3 KF1 or 2.3.4 KH3 or 2.3.5 KI2. If they include Bootloaders you can just flash a cwm kernel and ready to flash any rom you like.
Hello i was wondering if someone could help me with an issue which may seem very minor to you, but i am a new bee in the rom business. I was running MIUI and wanted to switch to the Fasty 3 V1.3, so i go into recovery and then clear the cache and then the dalvic cache then i wiped all the user data. Then i applied the zip from my internal SD card and after installing the zip i would reboot then it would get stuck on the cynogen mod boot screen. So whenever i want to change to another rom i always have to go back to stock Eclair and then reroot and then ad a rom. Could anyone tell me what i am doing wrong?
When leaving MIUI or Cyanogen Mod and returning to "standard or regular" Roms you have to go back to "Stock" And Repartition.
MIUI and Cyanagen Mod use a different Partition Map ---- MTD
The other standard or regular (for lack of a better word at this time) i897 and i9000 Roms use the BML Partition Map.
And so when changing from a MTD Rom to a BML Rom you must flash to Stock Firmware that does a Full Wipe and Repartitions.
4-2ndtwin said:
When leaving MIUI or Cyanogen Mod and returning to "regular" roms you have to go back to "Stock" And Repartition.
MIUI and Cyanagen Mod use a different Partition Map ---- MTD
The other regular (for lack of a better word at this time) Roms i897 and i9000 use the BML Partition Map.
Click to expand...
Click to collapse
I beg to differ on repartition. If you were to use my kf1 packaged to go back to"stock" there is no repartition involved. There is not a pit file packaged with it. I have always thought that you are merely reformatting your existing partitions. Double check with someone more learned than i. I don't want to misinform anyone.
^
Thanks Mike for the correction. I was wrong in my initial post... Used the strike out to correct it.
I just finished going to Cyanogen Mod and MIUI from Stock i897uckk4 with Corn Kernel and returning successfully to kk4 from both of those using ur Safe KF1 Odin 3 File No Bootloaders. The Full Wipe has got to be the answer then, not the Repartition. The Reformatting, Not the Repartioning.
I have always used the Repartition along with the Full Wipe when returning to Stock from those MTD Roms and I thought I had learned somewhere along the way that that is what was necessary.
I sure don't wanna give out bad info...so thanks again.
So to switch roms i always have to go back to stock? Because when i do go back to stock i lose my root and three button fix and have to re-do them.
Info for AOSP to i897, i9000 roms
Not always. Just when going from a AOSP (CyanogenMod, MIUI, ICS, etc) to a I897 or I900 rom. As for the 3 button fix just flash GB bootloaders you don't EVER have to reflash those unless you wish too. Just remember to use "safe" or no bootloader packages. Root isn't important since most roms are rooted and ALOT of kernels have root.
I should be more clear. You will need GB bootloaders for Fasty 3. After you flash them always use "safe" or "no bootloader" packages for odin and you will never loose 3 button fix and save you from hard bricking in general.
Mental note: Need to remind myself to put tittle so searching is easier.....
I am having 5 Roms stored thru CWM, and I used to Nandroid restore one every time based in a certain rom property. This is normally an easy process.
The problem is when I am on CM7 or ICS and I want to revert back to restore gingerbread based roms then I have to use Odin for istalling the rom all over again!
whenever I see a blue recovery screen I know there will be a problem.
Is there an easy way for restoring rom without invloving the use of a laptop (Odin)? Sorry if this has been been discussed before, but I have checked thoroughly without luck.
Galaxy S-I9000
Happy new year.
The AOSP ROMs use a different file system to stock ROMs so you can't just CWM a stock ROM on top. You have to install a stock gingerbread rom with odin/heimdall with repartition then you can restore the CWM backup. (can't remember if you have to install a kernel after installing stock)
Thanks but I was hoping for an easier way. Later on I will backup a base ROM then will try to revert to it from AOSP ROMs and will restore the desired rom from there. I have just read from a similar post that is possible.
I will try to be as detailed as possible. I have been long time user here, but this is the first time I'm posting. I usually read the instructions and posts and that usually suffices my needs. I was on a rooted galaxy note running chasmodo's assylum rom for quite some time now. For Flashing a new rom, I used to go to recovery mode, flash abbysnote kernel (v 3.9) and install a new rom. A few days ago i tried to flash Ezaechiel XXLT6 KM edition - V2.1. I guess I should have checked md5 of the downloaded rom coz after flashing it, my phone refused to boot up. It always took me to the recovery mode screen where i tried to install abyssnote kernel and reinstall assylum. but it didn't work. So I went to dr. ketan's post and tried to flash a pre rooted rom (SGN_XX_OXA_KJ1_FACTORYFS.zip) using pc odin. Now my phone works fine but i'm on ginger bread. I tried to flash new roms using recovery mode (abbyssnote kernel method) but no new rom can be installed. Everytime I try to install a new rom i face boot loop or get stuck on the setup screen. So I follow the PC odin method to flash the same pre rooted rom (SGN_XX_OXA_KJ1_FACTORYFS.zip) to get my phone working again. I would like to go back to assylumrom because i got used to aosp jellybean so much now. Anybody who has faced a similar problem in the past, please help
Use one of PhilZ kernels and then in his recovery prepare your device for a clean install (there is an option that does more than only "factory reset". With the old ones you didn't clean /preload.
Then follow the instructions to install your preferred Rom.
Thanks
ThaiDai said:
Use one of PhilZ kernels and then in his recovery prepare your device for a clean install (there is an option that does more than only "factory reset". With the old ones you didn't clean /preload.
Then follow the instructions to install your preferred Rom.
Click to expand...
Click to collapse
Thanks for the quick reply thaidai. I will try the method and get back to you I used to do a clean wipe every time.
Mate first upgrade your stock ROM to ICS or JB. The ROMs like Asylum aren't supposed to be installed in GB, so first upgrade, then root and do a full wipe (data,cache,preload,dalvik) and get back to flash the ROM. No need to flash the Abyssnote every time, why do you do that?
Varad297 said:
Mate first upgrade your stock ROM to ICS or JB. The ROMs like Asylum aren't supposed to be installed in GB, so first upgrade, then root and do a full wipe (data,cache,preload,dalvik) and get back to flash the ROM. No need to flash the Abyssnote every time, why do you do that?
Click to expand...
Click to collapse
I tried installing Cassies Xtraliterom XLC1 after the PC odin method. Got boot loop. What I'm basically saying is, after trying the PC odin method to rescue the device, I can't seem to install any other rom on it using the recovery mode route. Not even other GB roms. What am I to do??
Varad297 said:
Mate first upgrade your stock ROM to ICS or JB. The ROMs like Asylum aren't supposed to be installed in GB, so first upgrade, then root and do a full wipe (data,cache,preload,dalvik) and get back to flash the ROM. No need to flash the Abyssnote every time, why do you do that?
Click to expand...
Click to collapse
I started using abyssnote kernel to install new roms after the "brick scare" of last year after which a lot of developers started recommending the method. I used to change between GB, ICS and JB roms easily using the abyssnote kernel. Don't know why it's not working anymore.