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.
Hey guys, new here but I have been lurking for a while.
On Androidforums I have a longer thread detailing what I did, if you want details pm me, I can't post a link yet as I am a noob on this forum.
To make a long story short:
1. I had stock eclair, then rooted with "ryans oclf" and used the lagfix.
2. I decided to try a version of cognition (unhelpfuls kernal). So I backed up my current "rom" using rom managers (which was the stock kernal).
3. Realized that I didn't back anything up so I tried to revert to my backup.
4. relized that I didn't undo the lag fix, and because of this my stock eclair wouldn't restore via rom manger's update.zip file
5. was forced to get cognition running again
6. extraded the files from the .img nandroid bacups from my stock eclair (which is a PITA since the .img files aren't regular mountable .img files - took about an hour of searching)
7. Found the sql databases to restore my text messages and contacts from my stock eclair to this new cognition.
NOW, after a long intro, my question:
The .img files I extracted contained a file named linux.ex2. I assume that this file is where ryans oclf must have been storing the stuff that is causing the restore to fail (it actually completes, but never boots)
Is there any way I can manually repair this nandroid backup? I would like to so that I have a nandroid backup of my stock eclair rom.
BTW, I am pretty good at this kind of thing, but I am not a computer programmer.
I don't have a lot of background info directly related to andorid phones but I am learning quick. I am a Senior in electrical and computer engineering so I do have a light background in programming. luckily I knew enough about sql and command prompts and such to get as far as I did with recovering my contacts/text messages.
If what I want to do is possible I would love to give it a shot. Any help/tips/ideas from you guys would be awesome!
Thanks
-Chad
To me it sounds like your screwed. You did a double bummer.. (backup with LF on, restore a backup with LF ON on your already LF ON rom).
Will see if any other more experienced with backup can help you out, but my answer to you is to go stock and redo sorry.
yeah, well I am willing to try a few different things. I forgot to mention that right before I installed cognition the first time, I did remove the lag fix, I just undid the lagfix before I made the backup.
I have been using cognition for about a week now. I don't really mind it as it seems to work just fine, as It is in fact faster.
Last night after posting my post here I removed the voodoo lag fix and then I made a backup of my current installation of cognition.... So if I have any issues trying to do this I at least have a working/functioning cognition rom.
BTW: I have an unrelated question that is slightly related. If I have to use the odin one click restore at some point, does it clear my internal sd card as well? I see that it says it will clear user data, but doesn't specifically make a clear separation of the internal SD card on the captivate and the 2 gb they setup for the android partition.
A far faster method would be to Odin back to stock, root, then take a nandroid backup right away, then flash back to what ever rom you want. Time consuming, yes, but faster and easier than trying to mod a backup.
OK, when I first started into this stuff, I tried to follow all the guidance that has been given before flashing my first ROM. I did a ROM Manager backup of my ROM the way I got it from AT&T. I did not write down my ID # or anything else. I'm assuming the backup has all the information that came with it. My question is how to re-load that original ROM. I've flashed quite a few ROMs now using the Odin one-click to go back to stock and Master Clear and never had a problem. I'm running P9 right now (w/ no problems) and decided to try something else. After seeing some of the threads on here about your original phone IDs, I wanted to try and recover that info by restoring the original backup. I did that straight from P9, but now I just get locked up on the DG boot screens. I'm going to One Click it again but I'm wondering how I can restore back to my original with the backup that I have. Any guidance would be appreciated.
Thanks
My apolopies if this is already posted somewhere but I can't find it
Your can not restore a 2.1 backup when on a 2.2 rom, if I understand you correctly. In fact I would only restore a backup if you are on the same rom as the backup, and even then you should disable the lag fix prior to restoring
Sent from my SAMSUNG-SGH-I897 using XDA App
Not to sure, I tried going to original with nandroid backup after flashing another rom and soft bricked. I actually got stuck at the AT&T screen which on Perc 9 (that what I was running) was the designgears boot screen. Odin 3 one click saved my sanity. if you can go 2.2 to 2.1 I don't know, but I'm not going to try it again. I just one clicked, master cleared, rooted, flashed Axura 2.5 and have been happy ever since. This was my fault, not Perc 9's, let me say that real clear.
Got it
Thanks. I did have to One Click restore to stock, Master Clear, and then restored my original backup. Now I gotta figure out what information I need off of it before I flash a new ROM. Probably a waste of time since I can't imagine going back to AT&T for anything, but thought I would get it since I was waiting to change to P10 soon.
BigMc71 said:
Thanks. I did have to One Click restore to stock, Master Clear, and then restored my original backup. Now I gotta figure out what information I need off of it before I flash a new ROM. Probably a waste of time since I can't imagine going back to AT&T for anything, but thought I would get it since I was waiting to change to P10 soon.
Click to expand...
Click to collapse
Um.. what information did you want off of it? If you just want your Android ID - there is an app for it on the Market (strangely enough called Android ID) You can then write it down and re-enter it at any time after flashing.
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.
Trying to create a nandroid backup in cement v4... (running uckj3, with boog's kj3 kernel) and every time i boot into recovery and perform a backup it gets stuck at "backup sd-ext" kinda confused as to why this is happening, also can't get the kj3 extended power menu to work, flashed the zip maybe 5 times, cleared the cache/dalvik cache and nothing, any and all suggestions are greatly appreciated. Thanks guys.
Sent from my SAMSUNG-SGH-I897, named Ginger, using XDA App.
The nandroid backup is not yet working in the Gingerbread Roms.
The extended power menu is for Deodexed Roms only.
Hope this info proves helpful.
update
Okay, so I was thinking about why it wasn't working and went to my clockworkmod folder on the SD and saw that the files were pretty large in size, all totally over 4 FBI, so i deleted some miscellaneous files to free up some additional space and tried to run cement backup again... still took a while and did think it got stuck again, but it actually finished..could i safely assume that it worked or should i not trust the files? Also, the more i think about it, do i really need a Nan backup? Meaning, if anything goes wrong with my phone i can always reflash stock and use titanium backup to restore my apps...any thoughts?
Like I said before, the Nandroid Backup does not work in the Gingerbread world. It may look like it is backing up but the restore part won't happen. If u try u may soft brick.
And yes, the fail safe is that you could always return to a Gingerbread stock of your choice and use Titanium Backup to restore your stuff.
nandroid works on gingerbread, just not I897 kernels. I9000 works fine.
although i don't use them personally.
^ Thanks for the clarification. I didn't realize that about the i9000 because I am always on i897.
It's amazing what is being accomplished on captivate kernels, reverse engineering and building "blind" but nothing beats having source code to work with, which is why the I9000 nandroid works.
So how can I tell if I'm running an I897 or I9000? Currently using UCKJ3 with boogs kernel and just flashed the samurai kernel
Sent from my SAMSUNG-SGH-I897 using XDA App
that is I897.
I897 firmwares usually start with a K
I9000 usualy a J
it will also usually say in the op of the thread...