so uhm i ... had first initially went to cm7... forgot version but according to phone, the firmware version is 2.3.3.... is the new cm7.1.. 2.3.6?? 2.3.7??
what do i go about doing the upgrade???
heard people back-up?? (what program to back-up) then format..?? then flash ??
or what is your way??
Back up you rom on clockwork mod recovery or RA recovery ...then wipe all...and flash away
Sent from my Sensation using XDA Premium App
theres a back up function on amun ra recovery? *looks*
Yes.
Sent from my Sensation using XDA Premium App
CM7.1 is 2.3.7. If you're using Amon Ra there is no option to wipe system partition.
You can use temasek's format-signed.zip to do a clean wipe of the phone.
Sent from my Transformer TF101 using Tapatalk
If you are coming from a previous CM7 based version, you *shouldn't* need to wipe the phone. It *should* upgrade cleanly. That being said, nothing works as it should every time, so make sure you make a nandroid backup within recovery, just in case things go wrong.
Right this backing up thing people do is usually through something you can access in your recovery called NANDROID. It shouldn't be necessary in this case but its always worth doing (just in case!). Oddly I'm running stock recovery right now so I can't give better instructions but have a quick look for something saying back-up or nandroid (or both i guess), can't remember how its written. Its a fairly simple process and then if you want you could wipe your phone before updating CM but once again you don't have to.
Hope that helps!
Related
I installed this ROM and rebooted and my screen doesnt advance pass the blue android splash screen
now i tried gingerbread and it made it through the splash but i got a message saying something about setup not working and forcing closed. then i went back to recovery and installed the gapps and it gets stuck on the splash screen
Are you using firerat mod? Also make sure to do a full data/ system, cache, and dalvik cache wipe. I usually do all three at least twice as I've had roms hang from leftover data. Also check to make sure files are downloading completely.
Sent from my HERO200 using XDA App
What recovery are you using??
Yea it's me again. With the
Modified Hero
im using clockwork recovery 3.0.0.5
i finally got gingerbread to work. i think my problem was with doing a complete wipe of the cache.
i want to try the froyo mod but dont want to end up back where i was of hanging on the splash screen.
do i need to delete the one click root file? heroroot010.apk?
Yes you should and just do a nand back up of your working rom and you should be good to try any different rom. Then if you want to go back just nand restore back to your old rom. And if you were able to get gb to work froyo shouldn't be a problem for you.
Yea it's me again. With the
Modified Hero
You also wanna ditch that customized recovery image. Use the recovery that comes with rom manager. That new one is missing some capabilities.
Sent from my HTC Hero CDMA using XDA App
theSlack said:
You also wanna ditch that customized recovery image. Use the recovery that comes with rom manager. That new one is missing some capabilities.
Sent from my HTC Hero CDMA using XDA App
Click to expand...
Click to collapse
I second that! Hated that recovery both days I had it. lol
That's not the new one. The heroroot apk. installs the old darchstar recovery img. The newest one is RA1.7 and it has all the features. Good luck
Yea it's me again. With the
Modified Hero
thanks guys
where can i find R.A. 1.7
Clockwork recovery 2.5.0.7 works great. And that's what rom manager will flash for you. Since you likely have rom manager already, you should go with that. Most people post instructions with clockwork in mind, so it will be easier in the long term.
Sent from my HERO200 using XDA App
theSlack said:
You also wanna ditch that customized recovery image. Use the recovery that comes with rom manager. That new one is missing some capabilities.
Sent from my HTC Hero CDMA using XDA App
Click to expand...
Click to collapse
Like what? Besides doing away with amend scripts (which is due to CWM 3.x being based on the official GB recovery), it's the same.
That's basically it. But it causes extra work. And the original clockwork recovery works fine.
So if the OP wants stuff to work every time...
Sent from my HERO200 using XDA App
Do I really need to flash to stock before I flash a ROM everytime? IT GETS SOO ANOYING.
I do, its not that big a deal. Place CWM update.zip in the root of your SD card, place desired ROM somewhere on the card. Odin to stock allow to fully boot, then restart into recovery. Flash CWM, then flash ROM from CWM. You don't need to root or use ROM manager.
Sent from my SAMSUNG-SGH-I897 using XDA App
quarlow said:
I do, its not that big a deal. Place CWM update.zip in the root of your SD card, place desired ROM somewhere on the card. Odin to stock allow to fully boot, then restart into recovery. Flash CWM, then flash ROM from CWM. You don't need to root or use ROM manager.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I do the same thing it's not that big of a deal to go back to stock. It eliminates any problems you might run into
Sent from my SAMSUNG-SGH-I897 using XDA App
I don't I have had my captivate since august and have only used odin three times. There are a lot of reasons why flashing stock is neccesary, but just switching from one rom to another is kind of a waste. One reason is 3e recovery. It is easier to flash stock 2.1 not 2.2 and then flash a new rom as the above post says just put the update.zip and newrom.zip on the root and install. Once you are on a custom rom with a custom kernal you can use the options in recovery to flash another rom. I just factory reset, wipe cache partition, wipe dalvik cache, and flash, if you really want to wipe everything you can go into mounts and storage and wipe everything, but the boot again. Then go to mount usb and copy over the rom from the computer, and then flash. The update script included in the new rom will wipe everything once again. If you have problems, like you got a bad flash, try flashing the same rom over again. Its kind of rare to get a bad flash. In short just flash over if you have problems then use odin.
Sent from my SGH-I897 using XDA Premium App
When switching kernels
I typically flash back to stock when I'm going from one kernel to another. If the ROM I'm on and the ROM I'm going to use the same kernel (or at least the same line, i.e. two different versions of SuckerPunch), I usually skip the back-to-stock step.
Some say that it is only worth doing if you run into problems with the Rom. I do it everyrime to avoid anything that might happen. Plus old habits die hard from my WM days where flashing stock was needed
Sent from the shadows
I do it everytime. It hardly takes 10 mins and I don't mind spending that 10 here than spend debugging later
Sent from my SAMSUNG-SGH-I897 using XDA App
I don't if I am going from froyo rom to froyo rom. Only time I have to is leaving 2.3.3
This is my Captivate. There are many like it but this one is mine
AndroidKaboom said:
Do I really need to flash to stock before I flash a ROM everytime? IT GETS SOO ANOYING.
Click to expand...
Click to collapse
About as annoying as seeing this question asked dozens of times when it can easily be answered by doing a search or just scanning the forum titles for a similar thread.
It is easy to do, but no real reason to do so unless on a 2.3.3 rom
MIUI
Thread closed
Hey guys. I have a question. I have flashed mcr rom on my o2x recently but before flashing, i saved a backup in cwm.
Now that i want to flash back to stock rom and kernel and the exact same original settings and rom, can i just restore using cwm or what do i do?
I am from Singapore using Starhub.
Thanks guys
Sent from my LG-P990 using XDA App
The main problem is that MCR will have converted your partition to ext4, which the stock ROM can't read. As far as I understand, there are two options
1. Use http://android.modaco.com/content/l...3-for-converting-your-device-er-back-to-ext3/ but make sure you have the backup on your SD card, so before you reboot, you can restore it (if you reboot without restoring, bad things happen).
2. Use nvflash to put the stock ROM back on, and then restore your CWM backup.
But. . . someone who has done this may be able to confirm - if you want to be extra safe, check in the MCR thread.
Thnks for the reply! So cwm is actually not really a rom backup image?
Sent from my LG-P990 using XDA App
It is, but because the disk format is changed when you install MCR, I don't think you can restore it, without changing the disk format back first (I guess it depends how low level the image goes, maybe?)
zhehao said:
Thnks for the reply! So cwm is actually not really a rom backup image?
Sent from my LG-P990 using XDA App
Click to expand...
Click to collapse
Pretty sure NAND restore would be fine.
I see.
So by right what i have to do essentially is to:
1. Convert back to EXT3.
2. Make sure my NANDRIOD backup is in SD Card.
3. Off phone and go into CWM then recover NANDRIOD.
Should be all?
Don't quite understand the nvflash. May i know what is that?
Intro
Hi guys, I just got my Galaxy Ace from my mom a month ago(She used it for a couple of months but was too "complex" for her that's why she just gave it to me). Anyway, I'm the type of person who wants to explore and unlock the full potential of things. The first thing I did when I received the phone was research about stuff like how to modify it, etc. I was able to successfully root(there's a "super user" icon in the menu) it. Today, I thought it'd be nice to add some metro ui theme on it. So I I downloaded 7 launcher from the play store. But, was not satisfied because it felt like it was only a "skin" and didn't changed the overall feeling of the phone. That's the time I started digging dipper into the realm of Android and came across this thing called "ROM"....
I followed an online guide on how to install roms. First, i downloaded the rom i wanted(it's called "WP7") and placed it at the root of my sd card. Just like what the tutorial suggested(in case something goes wrong), I made a "nandroid" with the use of Clock Work Mod. I then saved a copy of the nandroid into my computer just to be EXTRA safe. Everything seems to be in order so I proceeded with the operation. I accessed the recovery menu, and selected "wipe cache partition" and "wipe data/factory reset". After that, I went to "install zip from sd card" and selected the zip file. Everything went well. After the update, I rebooted the phone and it was successful.
The Problem
I checked the whole new ui design and it was what I expected it to be. But then, I immediately missed the old ui, so i decided to go back to the stock os/kernel/(whatever you guys call it ). I went to the recovery menu and selected "backup and restore". I chose the nandroid I just made through CWM. After loading, I rebooted my phone and bam... this is where my problem is. The Phone's name and model number appears in the screen but it's not loading. I waited for 2 minutes and nothing happened. So I restarted the phone by holding the power button and volume up. I accessed the recovery menu again and examined if I missed a step. After browsing the net, I concluded that I didn't wipe the cache and data before restoring . So I wiped both cache partition and data. I selected the nandroid and then rebooted the phone again. But, the boot loop is still there . I tried it again and again. Wiping, Restoring Rebooting. But the boot loop won't go away.
So I wiped it again but this time, I didn't select the nandroid and instead I went back to the new WP7 rom i just downloaded. My phone didn't do a boot loop and my phone is okay now. I'm stuck with my new rom for about an hour now. I'm starting to get used to it. Anyway, even though things are stable now and i'm on my new rom, I think it's still nice to go back to the phone's original kernel/os . Any ideas on how I can restore back my phone to the original/stock kernel/os without experiencing the boot loop? Or can you give me the causes why I'm experiencing the boot loop? My guess is, I think there's a problem with the nandroid I used. The wp7 rom doesn't experience any boot loop but when it comes to my nandroid, there's a boot loop.
Thanks in advance and sorry if it's too long to read. I just wanted it to be accurate and clear for you guys .
The only way would be flashing through Odin.
Enviado desde mi GT-S5830L usando Tapatalk 2
Search for your previous ROM around and flash it.
Here's a good TUTORIAL on how to flash ROMs
The only way to flash a stock rom is odin (its a pc program) .
after you flash back to stock, you should Be able to restore your nandroid backup without getting the bootloop
(at least, i'm pretty sure, can someone confirm this?)
Im sure ull find a guide on how to use odin somewhere on xda.
Sent from my GT-S5830 using xda premium
AaronvAce said:
The only way to flash a stock rom is odin (its a pc program) .
after you flash back to stock, you should Be able to restore your nandroid backup without getting the bootloop
(at least, i'm pretty sure, can someone confirm this?)
Im sure ull find a guide on how to use odin somewhere on xda.
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
Yea..u are correct..if it was a successful backup(without any errors)...then no problem in falshing nandroid backup after using odin
Best of luck
Sent from my GT-S5830 using xda premium
U need chainfire app to convert filesystem to rfs ... before returning to a backup of a stock rom! Otherwise u need a factoy reset from stock recovery
Hey guys. I came across a rom called stocklite and I was able to successfully install it. My new rom seems to speed up my phone and prolong its battery life. All of the bloatware that came with the stock os isn't present this rom. I don't think i'll be returning to the original stock os. So yeah, I appreciate all your help and cheers to everyone
is your keyboard ok in stocklite ROM
I can't type alphabets in 3*4 mode .
Now using s3 evolution beta3
Sent from my GT-S5830 using xda app-developers app
B A D R I said:
is your keyboard ok in stocklite ROM
I can't type alphabets in 3*4 mode .
Now using s3 evolution beta3
Sent from my GT-S5830 using xda app-developers app
Click to expand...
Click to collapse
The keyboard's working fine for me.
in my keypad it shows alphabet but when I type it shows numbers in screen. . Fed up so flashed back to s3 evolution beta 3 ultimate
Sent from my GT-S5830 using xda app-developers app
SunSleeper said:
Intro
...Any ideas on how I can restore back my phone to the original/stock kernel/os without experiencing the boot loop? Or can you give me the causes why I'm experiencing the boot loop?...
Click to expand...
Click to collapse
I know you're happy with your current ROM but just an FYI, I went through a similar process trying to unlock a T-Mo Samsung Dart T499 (similar to Mini/Galaxy Ace). I just flashed stock ROM via ODIN and it boot looped on me. After reading this post I went into stock recovery and clear cache partition and factory reset and voila!
So this post actually inspired me a bit! Haha! Thanks!
as already said, the batter way to solve that problem is clean up your device is flash a stock rom with Odin,
but then, you will need remake root, and install a CWM....
good Luck !!
I just got a nexus one for $35 that i plan on using mostly as an mp3 player. I rooted it using the one click method but it's still S-on. Part of my issue is that booting into recovery using CWM only works maybe 25% of the time. Not sure why that is. A couple times I've been able to flash a rom via recovery but after seeing the X screen, the phone bootloops on the next splash screen. This has happened on two GB roms - MIUI and CM 7.2.
Any guess on why this happens? One reason I want to flash a rom is that the camera doesn't work so I'm curious if it would work in a different rom.
nvillamob said:
I just got a nexus one for $35 that i plan on using mostly as an mp3 player. I rooted it using the one click method but it's still S-on. Part of my issue is that booting into recovery using CWM only works maybe 25% of the time. Not sure why that is. A couple times I've been able to flash a rom via recovery but after seeing the X screen, the phone bootloops on the next splash screen. This has happened on two GB roms - MIUI and CM 7.2.
Any guess on why this happens? One reason I want to flash a rom is that the camera doesn't work so I'm curious if it would work in a different rom.
Click to expand...
Click to collapse
Before flashing a ROM, clear cache/ dalvik-cache from recovery. If you don't do these, then you will see bootloops.
I had been doing that through rom manager but just did it through recovery. still bootlooping.
I wiped cache but did not factory reset
Sent from my Nexus 4 using xda app-developers app
nvillamob said:
I had been doing that through rom manager but just did it through recovery. still bootlooping.
I wiped cache but did not factory reset
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
If you are changing ROMs, its always advisable to do a factory reset in addition to clearing cache and dalvik. Try it
Sent from my Nexus One
Best advice is to skip ROM manager and always do everything manually in recovery, this has never been a problem for me
And just because, I would suggest using 4ext recovery as in my opinion it is by far the most superior recovery... Just saying
Sent from my Nexus 4 using xda premium
Unfortunately, I've tried flashing manually via recovery too...still bootloops
Check md5sum of ROM (maybe bad download)
Make sure you wipe fully (manually in recovery or with fastboot)
Make sure you meet requirements of ROM in op (as in you flashed gapps if needed or you have a large enough system partition etc)
Sent from my Nexus 4 using xda premium
yeah, i haven't checked the md5's but it's odd that it's happened with both official miui and cyanogenmod. i did wipe cache and dalvik. i think i'm just going to give up. i'd do a factory restore but don't want to do that because then i'd have to root my phone again. i rooted the phone using a Vista computer but now I'm back home and my computer runs windows 8. from what I can tell, installing the android SDK is kinda complicated on W8.
Factory reset is needed and will not mean you have to reroot your phone, this is something that would be done before each flash, in fact the cleaner the wipe the less chance of an issue.
Also there is no need for the SDK to root (but its easy to get for windows 8 anyway and tools such as fastboot and adb are very handy... Also there are other ways to get these tools without the SDK) but all that besides the point, these are your steps
Nandroid backup
Wipe everything as clean as possible
Flash ROM and anything else needed (gapps etc)
Reboot
This is the procedure you should follow for any ROM flash for any android and never a need to reroot in between
Best of luck
Sent from my Nexus 4 using xda premium
I really appreciate the help. the reason I mention the SDK is that my computer doesn't recognize my phone unless I install the SDK and the associated drivers. So I'd hate the wipe my phone so that I can flash a rom, but then be unable to flash a rom because I'm not rooted!
But you feel confident that if I factory reset, I won't loose root?
I factory reset daily! You'll be just fine, when you factory reset and wipe all partitions you are following the proper procedure to change roms. When you flash the new one you are sure to still have root access
Sent from my Nexus 4 using xda premium
well, did a factory reset last night but i'm still having the same problem. I'm at a loss.