I'm really a noob in hacking my captivate. So please bear with me with all my questions.
I've tried my best to educate myself about different mods, especially clockworkmod and nandroid. But I couldn't understand what each of these does. I did "Backup Current ROM" in ROM manager recently. (1) Is that considered to be a ROM backup that I can use in the future if I want to restore to stock ROM?
If so, (2) what is the different between that backup method and Nandroid method? I didn't do Nandroid backup because I don't understand how to install it.
(3) If not, am I screwed? Cause I already performed several mods: Voodoo lagfix and ATT app removal. But my captivate is running fine.
I just wanna make sure I can restore back to my Stock ROM when 2.2 update is available. (4) Do I need to restore stock ROM in order to receive and install 2.2 update?
Please educate me on this matter. Thanks!
I use nandroid once I installed a firmware or ROM and apps (Titanium Backup User apps + System data and restored on the ROM Missing Apps + Data) to make a backup.
Now I can restore Nandroid and all my settings/apps are there.
Use Titanium backup to get your apps/settings onto a newly flashed firmware or ROM.
2 good options... My favorite is to use rom manager to do a rom backup.
Sent from my GT-I9000 using XDA App
hwibowo said:
I'm really a noob in hacking my captivate. So please bear with me with all my questions.
I've tried my best to educate myself about different mods, especially clockworkmod and nandroid. But I couldn't understand what each of these does. I did "Backup Current ROM" in ROM manager recently. (1) Is that considered to be a ROM backup that I can use in the future if I want to restore to stock ROM?
If so, (2) what is the different between that backup method and Nandroid method? I didn't do Nandroid backup because I don't understand how to install it.
(3) If not, am I screwed? Cause I already performed several mods: Voodoo lagfix and ATT app removal. But my captivate is running fine.
I just wanna make sure I can restore back to my Stock ROM when 2.2 update is available. (4) Do I need to restore stock ROM in order to receive and install 2.2 update?
Please educate me on this matter. Thanks!
Click to expand...
Click to collapse
1) clockwork mod and nandroid (ROM Manager) are the same thing.
2) as clockwork stands RIGHT NOW (should be changing soon), backing up your current ROM does NOT change your kernel or modem. clockwork is also incompatible with voodoo (you have to disable voodoo to use clockwork, and you can restore voodoo once you're done)
3) to restore to stock "out of the box" state, you will need to use the odin one-click downloader for the Captivate.
4) the process for updating to 2.2 is unknown at this time, we won't know more until the option starts rolling out.
Kaik541 said:
1) clockwork mod and nandroid (ROM Manager) are the same thing.
2) as clockwork stands RIGHT NOW (should be changing soon), backing up your current ROM does NOT change your kernel or modem. clockwork is also incompatible with voodoo (you have to disable voodoo to use clockwork, and you can restore voodoo once you're done)
3) to restore to stock "out of the box" state, you will need to use the odin one-click downloader for the Captivate.
4) the process for updating to 2.2 is unknown at this time, we won't know more until the option starts rolling out.
Click to expand...
Click to collapse
Thanks alot! That clears a lot of my confusion.
Kaik541 said:
3) to restore to stock "out of the box" state, you will need to use the odin one-click downloader for the Captivate.
Click to expand...
Click to collapse
Thing is, this isn't EXACTLY "out of the box" state. This is a new install of the stock ROM, but it's missing some things that are on the original phone like the file with the easy to get unlock codes.
What I would like to do is backup the entire device as is when it comes out of the box. Basically create an image of the existing device. That way, if I have to revert at any point I know I'm not just reinstalling the stock ROM, but actually reverting to this phones original state.
static416 said:
Thing is, this isn't EXACTLY "out of the box" state. This is a new install of the stock ROM, but it's missing some things that are on the original phone like the file with the easy to get unlock codes.
What I would like to do is backup the entire device as is when it comes out of the box. Basically create an image of the existing device. That way, if I have to revert at any point I know I'm not just reinstalling the stock ROM, but actually reverting to this phones original state.
Click to expand...
Click to collapse
Hmmm, good question. The only way to back up that I know of is to use ROM Manager. Since that requires rooting the "damage" may already be done.
The date of the kernel is different from the stock one as well, someone else tried to flash the original stock kernel but said while Odin showed the kernel took, the phone still shows the same with the different date. It would be nice if there was a way to get a completely original stock ROM, so if you have to exchange or something at ATT. I don't know how in depth they get at the store so maybe we'd be able to get away with just the Odin One-Click and they will accept it. If they check the kernel date though, you're screwed. Either way though, once the update comes out, rest assured that someone will post it on here for those of us not running completely original out of the box stock, which I always appreciate.
Related
Silly noob-like question, but I wanted to make sure before I continued messing with my phone.
Does ROM Manager back up EVERYTHING on the phone? For example, I backup my rom. Move the backup file onto my pc. Then I screw around with roms, lag fixes, etc. and totally screw it up. If I "restore" the backup made by ROM Manager, will all my apps, settings, desktop, data files, etc be exactly as they were before I started screwing around?
Or, would I need to use Odin to load the same ROM as that which was backed up and then run Rom Manager Restore?
Thanks!
Yes it does
Sent from my SAMSUNG-SGH-I897 using XDA App
Here's another question regarding this thread:
I have the lagfix mod which uses the internal sdcard. When I create a backup will it and restore exactly how it was including the lagfix partition? If yes, is it the same procedures or do I have to do it a different way with the extra partition?
Thanks in advance.
Deca4 said:
Here's another question regarding this thread:
I have the lagfix mod which uses the internal sdcard. When I create a backup will it and restore exactly how it was including the lagfix partition? If yes, is it the same procedures or do I have to do it a different way with the extra partition?
Thanks in advance.
Click to expand...
Click to collapse
Actually I am trying to figure out the same thing. I made a backup before I started messing around with lag fixes, different roms and so forth. Then the other day I tried to restore a rom it didn't work. Eventually I soft bricked the phone and had to make the USB Jig to get it working again. Needless to say I am very intrigued with what exactly Rom Manager does backup and its limitations but I can't seem to find it anywhere. I am thinking the reason my backup was screwed up was because of a lag fix, only problem is I can't remember what lag fix I had on it when I did the initial recovery.
Something from my experience to add here:
Scenario 1:
-----------
I backed up the original 2.1 JH7 on my phone.
Installed 2.2 custom ROM, and played around with it.
Backed up 2.2 ROM.
Messed up with my 2.2 custom ROM.
Went to ROM manager recovery, and recovered the backed up 2.1 JH7, and ended up messing up. My phone didn't even boot up.
Then I went back to recovery, and tried restoring the backed up version of 2.2.
Phone booted up into 2.2, but, started giving a lot of FCs.
Scenario 2:
-----------
Installed 2.2 custom ROM 1.
Backed it up.
Messed it.
Restored it - worked fine.
Installed 2.2 custom ROM 2.
Backed it up.
Restored the 2.2 custom ROM 1.
Everything working fine.
Looks like as long as the core OS is of the same version, it seems to work.
Maybe there is something in the boot sequence that's probably not being restored (???)
---------------
Edit: I do not have CWM app installed. I use the CWM update.zip recovery manager since its the least intrusive way.
diablo009 said:
Something from my experience to add here:
Scenario 1:
-----------
I backed up the original 2.1 JH7 on my phone.
Installed 2.2 custom ROM, and played around with it.
Backed up 2.2 ROM.
Messed up with my 2.2 custom ROM.
Went to ROM manager recovery, and recovered the backed up 2.1 JH7, and ended up messing up. My phone didn't even boot up.
Then I went back to recovery, and tried restoring the backed up version of 2.2.
Phone booted up into 2.2, but, started giving a lot of FCs.
Scenario 2:
-----------
Installed 2.2 custom ROM 1.
Backed it up.
Messed it.
Restored it - worked fine.
Installed 2.2 custom ROM 2.
Backed it up.
Restored the 2.2 custom ROM 1.
Everything working fine.
Looks like as long as the core OS is of the same version, it seems to work.
Maybe there is something in the boot sequence that's probably not being restored (???)
---------------
Edit: I do not have CWM app installed. I use the CWM update.zip recovery manager since its the least intrusive way.
Click to expand...
Click to collapse
Interesting, it would makes sense in what you are saying. My error that I go was when I went from my original JH7 backup, installed a rom based on JH6 and then tried to install my original backup. I might have to try JH6 roms and see if I can restore to them easily or not. I will have to wait for Micro USB cables to come in as I don't have a spare since I used my only cable to make the JIG.
The kernel and modem aren't backed up, so if your backups use different ones and you try to restore them you'll have issues.
I herd a rumor that rom manager doesn't work with froyo on the captivate. But I could be totally wrong.
Sent from my SAMSUNG-SGH-I897 using XDA App
peachpuff said:
The kernel and modem aren't backed up, so if your backups use different ones and you try to restore them you'll have issues.
Click to expand...
Click to collapse
This is what I have read about it as well
Voodoo
There is also a different version of CWM Recovery (what Rom Manager uses to back things up) for the voodoo lag fix.
tnerb123 said:
I herd a rumor that rom manager doesn't work with froyo on the captivate. But I could be totally wrong.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
It works. I backed up and restored a few variants of Froyo ROMs.
peachpuff said:
The kernel and modem aren't backed up, so if your backups use different ones and you try to restore them you'll have issues.
Click to expand...
Click to collapse
How do I backup these? Is there any way?
If Ron Manager does backup the kernel and modem why would so many people have problems restoring back to different Roms? This is why I am so puzzled with this software.
Sent from my SAMSUNG-SGH-I897 using XDA App
Rom Manager can backup EFS folder ??
i lost my imei and the only backup that i have its from Ron Manager
Absolutely it does there!
Maybe I'm old fashioned, but best bet is backup from recovery. Saves everything down to browser login data. Can't go wrong with a full backup! I make one every time I flash just about anything.
Sent from my SGH-I897 using xda app-developers app
Rom Manager vs CWM Recovery
yes Rom Manager can do backup of phone..but why not just do
a Nandroid Backup from CWM Recovery..
never had problem with Nandroid Backup from CWM Recovery :victory:
dobi3 said:
yes Rom Manager can do backup of phone..but why not just do
a Nandroid Backup from CWM Recovery..
never had problem with Nandroid Backup from CWM Recovery :victory:
Click to expand...
Click to collapse
Agreed!
Sent from my SGH-I897 using xda app-developers app
So I have tried many times to restore my phone from a backup made by recovery manager, but it never seems to work. It will always make it to the desktop, but either restart constantly or everything will constantly crash making it unusable. Is there something I'm doing wrong?
Sent from my SAMSUNG-SGH-I896 using XDA App
Is your back up the same base as what toy are on. Meaning 2.1 to 2.1. Are you trying to restore a stock backup over 2.2?
mcord11758 said:
Is your back up the same base as what toy are on. Meaning 2.1 to 2.1. Are you trying to restore a stock backup over 2.2?
Click to expand...
Click to collapse
No. The ROM I was running when doing the backup was Serendipity 3.0. I flashed back to Serendipity 3.0, then ran my restore. Everything constantly crashes.
EDIT: I've found uninstalling and reinstalling the applications works, but then there's no point in making a nandroid backup. I might as well just flash back to the ROM I was on and use TiBu in that case.
Anyone else have any ideas?
I'd really like to experiment more with ROMs and custom projects, but I don't want to unless I can basically go back to what I had with one click.
Get titanium backup pro. lts $5, but well worth it. Everything restores with one click.
Sent from my SAMSUNG-SGH-I897 using XDA App
sixstringsg said:
Get titanium backup pro. lts $5, but well worth it. Everything restores with one click.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Yeah, I guess I'll just backup absolutely everything with TiBU Pro and keep the installation files around for each ROM, since CWM backups do not seem to work properly.
Auridran said:
Yeah, I guess I'll just backup absolutely everything with TiBU Pro and keep the installation files around for each ROM, since CWM backups do not seem to work properly.
Click to expand...
Click to collapse
CWM backups work fine as long as you have matching firmware versions (2.1-2.1, 2.2-2.2, or 2.2.1-2.2.1)
also you need to be aware of lagfixes in the rom that you may currently be running, they are not always compatible between roms
nandroid does not backup your kernel or modem which is why you need to be moving within the same firmware versions
you cant make a stock nandroid backup, flash a 2.2 rom, then restore from that backup immediately. you will need to do a couple of things first.
keep a stock 2.1 cwm flashable kernel and modem on your sdcard
revert any lagfixes your phone may have prior to trying to restore your nandroid of stock
once lagfixes are removed, flash your kernel and modem (same firmware version as your nandroid backup)(its possible to have this set up within ONE zip file)
once you are rebooted back into CWM, restore your nandroid...reboot and profit
Pirateghost said:
CWM backups work fine as long as you have matching firmware versions (2.1-2.1, 2.2-2.2, or 2.2.1-2.2.1)
also you need to be aware of lagfixes in the rom that you may currently be running, they are not always compatible between roms
nandroid does not backup your kernel or modem which is why you need to be moving within the same firmware versions
you cant make a stock nandroid backup, flash a 2.2 rom, then restore from that backup immediately. you will need to do a couple of things first.
keep a stock 2.1 cwm flashable kernel and modem on your sdcard
revert any lagfixes your phone may have prior to trying to restore your nandroid of stock
once lagfixes are removed, flash your kernel and modem (same firmware version as your nandroid backup)(its possible to have this set up within ONE zip file)
once you are rebooted back into CWM, restore your nandroid...reboot and profit
Click to expand...
Click to collapse
Well like I said, I made a backup on my Serendipity 3.0 ROM I had going, flashed to something else, then even flashed back to Serendipity 3.0 before restoring and it still didn't work properly. All the apps I had installed just force-closed until I reinstalled them, or force-closed somewhere during use.
Hi all
Is Nandroid backing up all the apps I've got at that moment? Or it just saves system files?
Like a complete and exact "photo" or are there things that I should do on my own if I mean to recover exactly as it was...
I assume that no wipe is necessary...
Thanks!
What's the truth about Nandroid backup?!
i guess there's no need to open a new topic, because i got kinda the same question
before you guys start to redirect me to the "search" function, i want to assure you that i have been using it, but i have found myself in a very strange situation, one question, two different answers... and because i'm new to the whole root stuff, i want to learn everything correctly before starting to make modifications to my phone
The question is: Nandroid backup, does it also back up the kernel or not?
I mean, if i root and install a custom rom that also comes with a custom kernel, will i be able to use my previous Nandroid backup to restore my phone to the old rom & kernel?
Searching the forums, i have found 2 totally different answers!
Answer 1: Nandroid does not backup the kernel: http://forum.xda-developers.com/showthread.php?t=806340
Answer 2: Nandroid does backup the kernel: http://forum.xda-developers.com/showthread.php?t=844352
So, please make me and all of us root noobs understand once and for all, does it backup the kernel or not?, will we be able to restore from a custom rom+kernel in case we need to?
and does it backup apps?
OK...As I understand it....
What does Nandroid Backup?
The ROM Itself..Obviously.
All your system settings, emails, SMSes, etc
All the Apps you have installed, so no need for TB
The Kernel you have installed (though there is controversy about this, and to be honest, I have never restored a nandroid backup when I had a different kernel already installed...however it really doesn't matter since kernels are easy to flash)
What does Nandroid NOT backup - This is VERY IMPORTANT
The modem (not a big deal)
The File System setting (A BIG DEAL)
This I think is where the confusion arises concerning the kernel being included in the nandroid backup. For many people the kernel is all about the lagfix. If you have installed a lagfix on your phone via the kernel, say changing the file system to Ext4, and then flash a Nandroid backup that includes a stock kernel or other kernel that does NOT support Ext4, you are in for a world of hurt...and in this case hurt means endless bootloops.
The way you avoid this is, if you need to flash a Nandroid with a kernel that does not support your lagfix...go into recovery, disable whatever lagfix, tell it when it asks that you wish to REBOOT INTO RECOVERY after the change....then flash the nandroid you wish.
This is why it is very important to keep regular nandroid backups, and to wait and see if a ROM/Kernel are stable for you before applying lagfixes or other tweaks.
So, let me see if i got this right, Nandroid does backup up my current kernel along with my rom, but if i apply any changes (lagfix) to my kernel afterwards or change it with a custom one with lagfix, nandroid won't be able to restore it anymore...
so the whole problem here is that nandroid is not able to backup / restore The File System setting, this being the rfs / ext4 transition
If this is the case, it seems that the Nandroid type backup is not as powerful as i thought, you can't really change from one rom to another in just a few clicks, but then again i guess that all the customs roms already come with some type of lagfix and you can make a nandroid restore between them, the problem would be when you want to revert back to a stock kernel, then you'll have to disable the lagfixes or simply flash a stock kernel and then restore the stock nandroid backup
so, i got this right guys?
maranello69 said:
So, let me see if i got this right, Nandroid does backup up my current kernel along with my rom, but if i apply any changes (lagfix) to my kernel afterwards or change it with a custom one with lagfix, nandroid won't be able to restore it anymore...
so the whole problem here is that nandroid is not able to backup / restore The File System setting, this being the rfs / ext4 transition
If this is the case, it seems that the Nandroid type backup is not as powerful as i thought, you can't really change from one rom to another in just a few clicks, but then again i guess that all the customs roms already come with some type of lagfix and you can make a nandroid restore between them, the problem would be when you want to revert back to a stock kernel, then you'll have to disable the lagfixes or simply flash a stock kernel and then restore the stock nandroid backup
so, i got this right guys?
Click to expand...
Click to collapse
Yes as I understand it.
You see Nandroid can't convert your file system or change anything, all it can do is flash a disc image onto your phone. If that image can work with your file system, you are golden. If not, it is like flashing a Mac OS image onto a Windows machine....nothing will work right.
However the good news is that most custom kernels support Ext4...so really the only problem comes when you try to flash back to a stock image...or vice versa.
got it then, thanks for your answers
and, if i still got your attention, maybe one more question
i just downloaded a stock firmware from samfirmwares.com, and all i got is a .tar file, can i use it somehow to flash just the kernel from it or i have to flash the whole firmware?
if i flash the whole firmware, will it also change my PHONE and CSC?, because the .tar file must be put just in the PDA section in odin
maranello69 said:
got it then, thanks for your answers
and, if i still got your attention, maybe one more question
i just downloaded a stock firmware from samfirmwares.com, and all i got is a .tar file, can i use it somehow to flash just the kernel from it or i have to flash the whole firmware?
if i flash the whole firmware, will it also change my PHONE and CSC?, because the .tar file must be put just in the PDA section in odin
Click to expand...
Click to collapse
Yes, it will flash the PDA, csc, modem and kernel...the whole shooting match. The single file firmwares are designed like that to avoid mismatches and issues. Once you flash it, flash a kernel that supports cwm (I suggest speedmod or something by CHAINFIRE) via odin, then flash a new csc and modem if you wish from recovery.
Remember that installing a new csc will do a factory reset so do it before reinstalling apps.
Sent from my GT-I9000 using XDA Premium App
great stuff man
finally i got enough info and i can start my root & flash procedure, guess i'll also learn a few other tricks along the way, this community is definetly the place to be if you want to learn how to "really use" your device
the whole info about the issues with the Nandroid type backup should be integrated in one of those massive info topics, so the root noobs like me know what they're dealing with
maranello69 said:
great stuff man
finally i got enough info and i can start my root & flash procedure, guess i'll also learn a few other tricks along the way, this community is definetly the place to be if you want to learn how to "really use" your device
the whole info about the issues with the Nandroid type backup should be integrated in one of those massive info topics, so the root noobs like me know what they're dealing with
Click to expand...
Click to collapse
Good luck
Sent from my GT-I9000 using XDA Premium App
Hey guys i actually used the search button (yay) and this is definitely the most informative one regarding the topic.
However i still have one more question: does it backup files and folders as well? Ie. my Nexus S storage is mainly used up by my videos and music (about 7-10GB) which are in their own folders and not tied to any apps in particular. Hence if it does include those i wouldn't have enough storage space to create a nandroid backup am i right?
Edit: thanks to the search button i didn't realise that i posted on a Galaxy S forum please forgive me, the question should still be relevant to the topic though
frenccw said:
Hey guys i actually used the search button (yay) and this is definitely the most informative one regarding the topic.
However i still have one more question: does it backup files and folders as well? Ie. my Nexus S storage is mainly used up by my videos and music (about 7-10GB) which are in their own folders and not tied to any apps in particular. Hence if it does include those i wouldn't have enough storage space to create a nandroid backup am i right?
Click to expand...
Click to collapse
As I understand it, it does save folders and files, so yes if you have large data folders on your internal SD it will make GIGANTIC nandroid backups. You may want to store such files one your external SD.
I know that there is a version of CWM that does not backup /data/media in Nandroid on the Galaxy Tab 10.1...perhaps there is something similar that I don't know about for Galaxy phones. Does anyone know?
Here are my doubts: Captivate on 2.2 no root
1)Is andromeda3 and phoenix unleashed based on android 2.2 or 2.3?(recent versions)
2)I used Odin v1.0 to go back to stock,what is the difference betwen Odin 1.0 and Odin 1.7?
3)Are there any other methods to go back to stock, I have read "Use odin 1.0 in case of emergency"?
4)How can I back up my stock rom after root in the case I want to flash back and unroot?
5)Do I need to go back to stock every time I want to flash a different rom?
6)Andromeda3 has a ursa minor kernel do i need this to install there rom or can i just flash the rom without ursa minor?
7)In the phoenix unleashed thread it says to flash there custom rom use odin to go back to stock,does this mean i have to do the whole back to stock+root again?(Staring from scratch in other words)
8)Will flashing rage patch while using andromeda3 or phoenix unleashed mess something up?
I think that's all please put the same number of the question in front of the answer so I know witch answers witch.Thank you in advanced.
Here are my doubts: Captivate on 2.2 no root (Don't doubt the captivate - it can handle it! Isn't autocorrect great?)
1)Is andromeda3 and phoenix unleashed based on android 2.2 or 2.3?(recent versions)
Andromeda3 is 2.2 based, and as much as I can see, so is Phoenix Unleashed.
2)I used Odin v1.0 to go back to stock,what is the difference betwen Odin 1.0 and Odin 1.7?
They're the same program, just different revisions. I can't say what specifically has changed between the two of the, but my guess would be 1.7 would have more features/bug fixes/etc.
3)Are there any other methods to go back to stock, I have read "Use odin 1.0 in case of emergency"?
Going back to stock will consist of using some version of Odin (one-click or otherwise) to reflash the stock rom to your phone
4)How can I back up my stock rom after root in the case I want to flash back and unroot?
From a rom standpoint, there's no need to back up your stock rom, unless you have settings done a specific way you want. Flashing to stock with automatically put you back at a stock, unrooted state. I would recommend doing a nandroid backup from the CWM recovery menu (assuming you have CWM) and copying the EFS folder to a safe location before moving forwards.
5)Do I need to go back to stock every time I want to flash a different rom?
Need to? No. Is it a good idea? There's debate on this, but in general, it's not a bad idea to flash back to stock (relative to where you are - GB/Froyo/Eclair) before flashing a new rom. It will help keep things tidy.
6)Andromeda3 has a ursa minor kernel do i need this to install there rom or can i just flash the rom without ursa minor?
To the best of my knowledge, it is included in the rom - there's nothing to do on your part, as it will flash with the rom.
7)In the phoenix unleashed thread it says to flash there custom rom use odin to go back to stock,does this mean i have to do the whole back to stock+root again?(Staring from scratch in other words)
If you're still on stock Eclair, you do not need to go back to stock. If you're on something else, you will need to go back to stock, but you shouldn't have to root, as most roms now work without being rooted.
8)Will flashing rage patch while using andromeda3 or phoenix unleashed mess something up?
It won't hurt anything - it just covers a security flaw.
I think that's all please put the same number of the question in front of the answer so I know witch answers witch.Thank you in advanced.
jmtheiss said:
Here are my doubts: Captivate on 2.2 no root (Don't doubt the captivate - it can handle it! Isn't autocorrect great?)
1)Is andromeda3 and phoenix unleashed based on android 2.2 or 2.3?(recent versions)
Andromeda3 is 2.2 based, and as much as I can see, so is Phoenix Unleashed.
2)I used Odin v1.0 to go back to stock,what is the difference betwen Odin 1.0 and Odin 1.7?
They're the same program, just different revisions. I can't say what specifically has changed between the two of the, but my guess would be 1.7 would have more features/bug fixes/etc.
3)Are there any other methods to go back to stock, I have read "Use odin 1.0 in case of emergency"?
Going back to stock will consist of using some version of Odin (one-click or otherwise) to reflash the stock rom to your phone
4)How can I back up my stock rom after root in the case I want to flash back and unroot?
From a rom standpoint, there's no need to back up your stock rom, unless you have settings done a specific way you want. Flashing to stock with automatically put you back at a stock, unrooted state. I would recommend doing a nandroid backup from the CWM recovery menu (assuming you have CWM) and copying the EFS folder to a safe location before moving forwards.
5)Do I need to go back to stock every time I want to flash a different rom?
Need to? No. Is it a good idea? There's debate on this, but in general, it's not a bad idea to flash back to stock (relative to where you are - GB/Froyo/Eclair) before flashing a new rom. It will help keep things tidy.
6)Andromeda3 has a ursa minor kernel do i need this to install there rom or can i just flash the rom without ursa minor?
To the best of my knowledge, it is included in the rom - there's nothing to do on your part, as it will flash with the rom.
7)In the phoenix unleashed thread it says to flash there custom rom use odin to go back to stock,does this mean i have to do the whole back to stock+root again?(Staring from scratch in other words)
If you're still on stock Eclair, you do not need to go back to stock. If you're on something else, you will need to go back to stock, but you shouldn't have to root, as most roms now work without being rooted.
8)Will flashing rage patch while using andromeda3 or phoenix unleashed mess something up?
It won't hurt anything - it just covers a security flaw.
I think that's all please put the same number of the question in front of the answer so I know witch answers witch.Thank you in advanced.
Click to expand...
Click to collapse
Thank you this is very informative and what i meant by "Here are my doubts: Captivate 2.2 no root" is that my captivate is on stock 2.2 without root just to be clear.
I got one more question:
Whats is the EFS folder?
Im going to tell you my former situation so you can tell me what I did wrong:
I rooted my phone with super one click at the time
I used rom manager it was also supposed to save a backup of my stock rom
Somewhere in the CWM I was supposed to save the stock rom just in case something went wrong(i thought i did it correctly)
I flashed Cognition everything was great
I wanted to eliminate Cog when i went to CWM to find my back up of stock it didnt work it stayed in Cog
I have read that flashing other roms while having a custom rom isnt recommended that you need to go back to stock first
I was stuck on Cog all i did was update to the most current version
Till last week where i got the guts to use Odin to flash back to stock with some fear i might brick my phone
Now im looking to do it all over but do it right and not mess it up only with different rom
DudeWatsThat said:
Thank you this is very informative and what i meant by "Here are my doubts: Captivate 2.2 no root" is that my captivate is on stock 2.2 without root just to be clear.
I got one more question:
Whats is the EFS folder?
Im going to tell you my former situation so you can tell me what I did wrong:
I rooted my phone with super one click at the time
I used rom manager it was also supposed to save a backup of my stock rom
Somewhere in the CWM I was supposed to save the stock rom just in case something went wrong(i thought i did it correctly)
I flashed Cognition everything was great
I wanted to eliminate Cog when i went to CWM to find my back up of stock it didnt work it stayed in Cog
I have read that flashing other roms while having a custom rom isnt recommended that you need to go back to stock first
I was stuck on Cog all i did was update to the most current version
Till last week where i got the guts to use Odin to flash back to stock with some fear i might brick my phone
Now im looking to do it all over but do it right and not mess it up only with different rom
Click to expand...
Click to collapse
It actually doesn't sound like you did anything wrong - you may just be looking for things in the wrong places. The CWM backup, if I am correct, doesn't create a quick-swappable backup of your stock configuration. My understanding of how the nandroid backup works is that it creates a snapshot of the phone with a particular rom in place, so that if something bad happens, you can flash back to a clean version of that rom, apply the nandroid backup, and you'll be right back in business with your custom rom (Again, that's my understanding - someone more knowledgeable may chime in and give a better/more correct explanation).
If you made a backup using CWM, you should have a folder on your internal SD called "clockworkmod/backup", with a folder that has the date of the backup on it. I would copy that to somewhere safe (like your computer). Once you've done that, and assuming your phone is functioning normally as a phone, I would use a root-level file explorer (root explorer, adb pull command, etc.) to get a copy the folder "/efs" on your computer as well. (Take a look at the link in my signature about XDA terms and acronyms for what the EFS folder is).
Once you've done this, if you haven't already done so, back up your applications with Titanium backup. Then use the Odin one-click to get back to stock 2.1 Eclair. You won't have root access at that point, but that is not a problem. Once you're there, just follow the directions for the rom you want to flash - most will install without requiring the root permissions. The AIO captivate toolbox in the development thread is a good tool if you want something to walk you through the installation process (although it should really only be used on Froyo roms at this point).
PLEASE NOTE - THIS IS EXTREMELY IMPORTANT: If you are going to flash a Gingerbread-based rom (Mosaic, Apex, etc), please read up and follow all directions extremely carefully. Flashing Gingerbread involves flashing the bootloaders on your phone, and if something happens during that portion of the flashing process, you will have a true hard brick - not a clay (recoverable error state), but a phone that you can't use.
jmtheiss said:
It actually doesn't sound like you did anything wrong - you may just be looking for things in the wrong places. The CWM backup, if I am correct, doesn't create a quick-swappable backup of your stock configuration. My understanding of how the nandroid backup works is that it creates a snapshot of the phone with a particular rom in place, so that if something bad happens, you can flash back to a clean version of that rom, apply the nandroid backup, and you'll be right back in business with your custom rom (Again, that's my understanding - someone more knowledgeable may chime in and give a better/more correct explanation).
If you made a backup using CWM, you should have a folder on your internal SD called "clockworkmod/backup", with a folder that has the date of the backup on it. I would copy that to somewhere safe (like your computer). Once you've done that, and assuming your phone is functioning normally as a phone, I would use a root-level file explorer (root explorer, adb pull command, etc.) to get a copy the folder "/efs" on your computer as well. (Take a look at the link in my signature about XDA terms and acronyms for what the EFS folder is).
Once you've done this, if you haven't already done so, back up your applications with Titanium backup. Then use the Odin one-click to get back to stock 2.1 Eclair. You won't have root access at that point, but that is not a problem. Once you're there, just follow the directions for the rom you want to flash - most will install without requiring the root permissions. The AIO captivate toolbox in the development thread is a good tool if you want something to walk you through the installation process (although it should really only be used on Froyo roms at this point).
PLEASE NOTE - THIS IS EXTREMELY IMPORTANT: If you are going to flash a Gingerbread-based rom (Mosaic, Apex, etc), please read up and follow all directions extremely carefully. Flashing Gingerbread involves flashing the bootloaders on your phone, and if something happens during that portion of the flashing process, you will have a true hard brick - not a clay (recoverable error state), but a phone that you can't use.
Click to expand...
Click to collapse
Thanks again
I don't plan on flashing 2.3 roms until the official 2.3 release come out
Theres a Odin that flashes stock 2.2 instead of 2.1 can I use that one instead?
Theres a Odin that flashes stock 2.2 instead of 2.1
Click to expand...
Click to collapse
I wasn't aware that existed - could you please provide a link?
Just to point you in the right direction, at the end of the flashing you're currently doing, what rom do you want to have on your phone?
jmtheiss said:
I wasn't aware that existed - could you please provide a link?
Just to point you in the right direction, at the end of the flashing you're currently doing, what rom do you want to have on your phone?
Click to expand...
Click to collapse
Heres the link http://www.mobiletechvideos.com/blog/?page_id=186
The rom i want to use is either Andromeda3,Phoenix Unleashed or just go back to Cognition 4.5.3 or Cog 5 when its not in Beta.
DudeWatsThat said:
Heres the link http://www.mobiletechvideos.com/blog/?page_id=186
The rom i want to use is either Andromeda3,Phoenix Unleashed or just go back to Cognition 4.5.3 or Cog 5 when its not in Beta.
Click to expand...
Click to collapse
Thanks for the link - good to know about that file.
In my opinion, you would have the best luck going back to stock Eclair (2.1). The reason I say this is because it gives you the cleanest path to getting to the custom Rom you want. 2.1 doesn't have the signed 3e recovery problems that can exist with a 2.2 stock rom, so you'll save yourself a lot of hassle there. Plus, the 2.1 stock rom to custom rom path has been followed hundreds of times on this forum, so it's had the chance to get pretty much all the kinks worked out by this point.
Again, just my opinion.
jmtheiss said:
Thanks for the link - good to know about that file.
In my opinion, you would have the best luck going back to stock Eclair (2.1). The reason I say this is because it gives you the cleanest path to getting to the custom Rom you want. 2.1 doesn't have the signed 3e recovery problems that can exist with a 2.2 stock rom, so you'll save yourself a lot of hassle there. Plus, the 2.1 stock rom to custom rom path has been followed hundreds of times on this forum, so it's had the chance to get pretty much all the kinks worked out by this point.
Again, just my opinion.
Click to expand...
Click to collapse
I would gladly take your advice if it makes everything safer and easier but I upgraded my phone using Kies mini to 2.2 so will using odin to flash back to stock 2.1 cause any problems since its a downgrade from 2.2 to 2.1?
DudeWatsThat said:
I would gladly take your advice if it makes everything safer and easier but I upgraded my phone using Kies mini to 2.2 so will using odin to flash back to stock 2.1 cause any problems since its a downgrade from 2.2 to 2.1?
Click to expand...
Click to collapse
You shouldn't have any problems with the 2.2-2.1 transition if you use the one click Odin back to stock. The dangerous move is going from 2.3 to any other version, as that involves flashing the bootloaders.
For maximum safety, just include these items on your checklist prior to starting:
- Nandroid backup from CWM
- EFS backup (copying that folder to a safe location)
- Titanium backup of your apps (copy titaniumbackup folder to safe place)
- Back up pictures/music/other items you want to save
Once you've done that, use the one-click Odin to get to a clean stock. From there, you should be good to go with flashing a custom rom. Just make sure you read and follow all directions in the custom roms' post. (If there's nothing there, follow this guide.)
jmtheiss said:
You shouldn't have any problems with the 2.2-2.1 transition if you use the one click Odin back to stock. The dangerous move is going from 2.3 to any other version, as that involves flashing the bootloaders.
For maximum safety, just include these items on your checklist prior to starting:
- Nandroid backup from CWM
- EFS backup (copying that folder to a safe location)
- Titanium backup of your apps (copy titaniumbackup folder to safe place)
- Back up pictures/music/other items you want to save
Once you've done that, use the one-click Odin to get to a clean stock. From there, you should be good to go with flashing a custom rom. Just make sure you read and follow all directions in the custom roms' post. (If there's nothing there, follow this guide.)
Click to expand...
Click to collapse
Eh i got it into download mode and i pressed start on odin but i think its stuck did i have to root first and then use odin im kinda scared right now
Edit:its showing a phone a warning sign and a Pc like connect phone to pc
I know it's nerve racking, but as long as you weren't on a Gingerbread rom, you'll be ok. Rooting isn't required - Odin is automatically "rooted".
A quick questions while you're waiting - When you plugged it in, did Odin recognize a phone was attached (did a yellow text box show up saying COM:4 or something similar)? It should look similar to the attached file.
jmtheiss said:
I know it's nerve racking, but as long as you weren't on a Gingerbread rom, you'll be ok. Rooting isn't required - Odin is automatically "rooted".
A quick questions while you're waiting - When you plugged it in, did Odin recognize a phone was attached (did a yellow text box show up saying COM:4 or something similar)?
Click to expand...
Click to collapse
Eh yes its i managed to trouble shoot it and its reboting everything is ok and yes it did show a yellow text box as of right now i just need to pop in the sym and reboot i have succesfully flashed 2.1 i just need to root and get CWM thru Room manager correct me if im wrong.
I'm not that familiar with Rom manager, but the general idea of getting root (maybe through the super one click root application, or from the CWM recovery menu) and installing CWM recovery (however you need to accomplish that) is the right first steps to getting to a custom rom.
Good luck with the flashing process.
jmtheiss said:
I'm not that familiar with Rom manager, but the general idea of getting root (maybe through the super one click root application, or from the CWM recovery menu) and installing CWM recovery (however you need to accomplish that) is the right first steps to getting to a custom rom.
Good luck with the flashing process.
Click to expand...
Click to collapse
I just rooted now all I need is CWM and thank you for all your help!
Glad it worked out. Don't be afraid to ask more questions in the future, as a reply to a question you've asked could help someone else with the same question out.
Everything you asked about could have been answered by doing some searches and reading up on these items. Invest the time instead of just posting.
Miami_Son said:
Everything you asked about could have been answered by doing some searches and reading up on these items. Invest the time instead of just posting.
Click to expand...
Click to collapse
I did ALOT of searching before thinking of posting this,the reason I did it was because most of the post are from 2010 and I had doubts on if I should use those methods or if there where new ones.This is the Q&A sub-forum right?I did just that ask questions.
Hi all,
I have a Galaxy S running 2.3.3 stock JVO with voodoo lagfix kernal and I want to flash a customer ROM (Darky) but I wanted to clarify a few things first:
1. When looking for customer roms do i need to take in consideration i have a JVO device? What does JVO mean?
2. After doing some research I have found a Darky rom app on the market. The app. The app has an option to flash/install from SDCARD. Can i simply download the rom and use this feature? Do Darky roms (or any other for that matter) contain lagfix kernal?
3. Is there any option to have a vanilla ROM i.e. google nexus with nothing but android? Surely the device will be faster with nothing on it?
4. Can i use titainum backup to restore applications back to their original state or would i need to re-download them and then use titainum to restore?
5. Is there anyway to make a snapshot of my device in its current state so if it screws up then revert it back to its current state (inc kernal).
Many thanks!
-c
1) JVO refers to your firmware build, relevant as to how recent it is. You'd have to be more concerned if making a major change (eg froyo to GB), but JVO to say JVP is a small change.
2) Not sure, but I doubt an unrooted phone will be able to flash a new firmware via just an app.
3) Firmwares are somewhat more complicated, since they bundle all the drivers and so on into it. To have just a plain vanilla android rom they would need to reverse engineer/rewrite all the drivers for your phone, gps, gyrometer, etc. There are some options available now though, like CM7 and MIUI which are radically different from samsung roms, and claim to be much faster. Google will tell you more
4) Titanium can reinstall apps. Usually no issue, but if there are major firmware changes the restored app may be restored incorrectly and fail to work properly. Usually more of an issue when restoring data to system apps
5) nandroid backup from CWM, you need to have a kernel with clockwordmod already on it though.
thanks dude.
I went ahead and installed Darky 10.2.2 and the speed is AMAZING! But for some reason I cant get the device to vibrate when I get a new sms, whatsapp or email even though I have set the device to vibrate
Check my thread
http://forum.xda-developers.com/showthread.php?t=1142499