Use 1Click to Stock to move off of KB1? - Captivate Q&A, Help & Troubleshooting

I have been trying the stock 2.2 KB1 ROM and am ready to move back to a custom ROM. I read somewhere that you should not uses the 1 click back to stock, but 'use the files', whatever that means.
Can someone clarify for me the correct method to get back to stock, so that I can move to a custom ROM?
NOTE: I have done several custom ROMS from here in the past, my only uncertainty is correct method to get off of KB1.

I am not sure there is any reason to go back to "stock" as long as you are rooted and have changed the recovery to allow for unsigned zips you should be able to flash straight from there. Going back to "stock" should have no baring on your success in flashing here, especially if you are using no lag fix curretnly on KB1

Thanks. I do have a kernel wiht a lag fix.
Maybe what I should do is:
Turn off lagfix
put stock kernel back on
(Of course back up all stuff)
Hard reset back to stock
install new ROM
I am used to the mantra: Hard rest; master clear; etc.

Related

[Q] Backing up Stock ROM noob question

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.

An indepth guide explaining how to load ROMs?

I've been trying to read as much as I could about loading custom roms, but I haven't found a guide that explains everything. I've gone through all the stickies but I haven't gotten a clear idea of flashing roms.
In the past, I've rooted my captivate and then downloaded the Titanium backup manager. But after wanting to go back to stock, my phone completely died using Odin to go back to JF6 and then doing an OTA update.
So before experimenting with my phone again, I want to be sure I know exactly what I'm doing. So is there a detailed guide on about using custom roms? Such as, what exactly is the update.zip file? When should I create a copy of it? What is Clockwork? If I want to revert back to stock, how do you go back to JH7 instead of JF6?
Not really, not for the level of detail you are looking for.
I'd recommend trying before you know everything . Just make sure make sure you have download mode working via the 3 button combo
Sent from my SAMSUNG-SGH-I897 using XDA App
Update.zip is what android automatically uses in recovery mode - clockwork is an update.zip that leads you into a super cool recovery mode that lets u do more.
U don't really need to mess with it.
Just install ROM manager and it will handle it
Sent from my SAMSUNG-SGH-I897 using XDA App
Thanks!! If you flash one ROM and want to switch to another, do you have to use odin to go back to stock? Or can you use a rom manager to flash a different one on?
dngen said:
Thanks!! If you flash one ROM and want to switch to another, do you have to use odin to go back to stock? Or can you use a rom manager to flash a different one on?
Click to expand...
Click to collapse
Most of the time you can do it on top, but its considered a safe measure to go back to stock. Also make sure you disable lagfix if you have one or else it will screw everything up.
joeshmoe08 said:
Most of the time you can do it on top, but its considered a safe measure to go back to stock. Also make sure you disable lagfix if you have one or else it will screw everything up.
Click to expand...
Click to collapse
If you are going back to stock, disabling lagfix isn't necessary. Everything is completely overwritten. It's only necessary if you don't go back to stock and just upgrade instead.
I'm interested in this too - First Android device and being on a tiny bit of a learning curve...
Reading through the forums here, I see the popular safety first consensus seems to be Odin back to stock, then root/ROM Manager and on with the next ROM. Fair enough, I have no problem with that, but I'd like to know the reasoning?
So lets say I try to go from my current Cog 2.1.6 (voodoo disabled) to the latest Cognition 2.4.1 beta (or any other ROM) via ROM Manager. What disasters "will" befall me? What disasters "might" befall me? Why?
You may or may not get frequent crashes if you do not flash to stock first.
Just make sure you can get into download mode. Everything else will work out
Sent from my SAMSUNG-SGH-I897 using XDA App

[Q] Custom Roms and going back to Stock

So I'm finally going to make the jump into custom ROMS. A couple questions though.
- I know most ROMs require going back to stock (JF6) - but would flashing from JH7 stock be fine as well (I think it's alright for Axura)?
- When running Odin to return to stock, does everything return to stock - Kernel and all or must that be done in separate steps? In other words, to go back to stock - is it a one step (Odin) procedure or multiple step - as in disabling a lag fix, swapping kernels, reflashing and so on?
Thanks!
One step. You open odin, get into download mode, and click start. About 3 minutes later the phone is like the first time you turned it on.
Sent from my SAMSUNG-SGH-I897 using XDA App

[Q]Andromeda 3,phoenix unleashed and more..

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.

[Q] Rooting my captivate, can't copy root file to phone

Hey folks. I'm bailing on Gingerbread because it was causing me too many problems. I'm trying to get back on Firefly 3.0 and I'm stuck at getting the phone rooted.
Whenever I try to copy the Root.zip from the AIO folder over to the phone's root folder, I get an error about the parameter being incorrect. I'm not sure what to do at this point.
Use Fugu root? Easier.... Also depending on what Gingerbread you are on there are kernels that have the root scrip baked in them.
^ you misread he's not on gingerbread, he wants to flash firefly.
You don't need root to flash a ROM. Odin a kernel that has cwm baked in. boot into recovery and flash the ROM.
Thought he was on GB trying to get on... you know what ya I missread. @OP do what Studa said xD. Wonder why people think they need root to flash roms..... I blame Rom Manager.
I know I don't need to root the phone, but in order to get certain things done on the phone, it's necessary.
I'm actually at a wall right now. I used SamsungCaptivate-SGHi897-UCKB2-Rooted-One-Click which successfully booted my phone to ATT 2.2 firmware, but I can't get any Odin to pick up on it now. I've tried five different Odins.
At this point, I think once I get the phone up and running on Firefly, I'll be walking away from flashing until I get another phone. Then I can use this for testing, etc.
On a side note, before I started this project yesterday, my modem was messed up. Now it would seem I have a successful connection to wifi, which I couldn't get.
As great as that is, I still can't get Odin to pick up my phone. Any thoughts?
Was that kb2 package heimdall?
If so you have to uninstall the heimdall driver and reinstall the Samsung driver.
Either way I would reinstall the Samsung drivers but it is a must if you used heimdall add the drivers conflict.
Alright. That's done, but I'm on I896UXJL1-stock now, and I'm pretty sure in doing that through Odin 1.85 I unrooted the phone. Correct me if I'm wrong. That's why I used the ATT stuff, because it auto-rooted the phone.
So it would seem I have some issues to work through. I can either root my phone and be stuck with ATT firmware that I don't want, or I can unroot the phone and use Rogers stock and hope for the best with Firefly.
This is by far the most confusing computer-related issue I've ever worked with. There's too many options to play with and they all work differently.
Why would you be stuck on at&t firmware? Why do you need to root before flashing firefly? Why don't you root Rogers stock?
you're confusing everyone involved lol
Okay, so maybe I'm a little in the dark on the rooting issue. Basically, I'm going back to Firefly because I thought it was amazing. Fast, responsive, and no issues I can think of on my phone.
I'm rooting the phone because it's my understanding that in order to spoof my location in order to get certain apps (Google Music), I'd need to be rooted.
I'm having a hell of a time trying to get this done, and my biggest problem, to reiterate, is that I have about fifteen different Roms, all either ATT or Rogers, three different Pit files, and so, so many Odin programs.
I'm now on 2.1 with that Toronto stock firmware, in order to work around the 3e error in recovery mode when trying to put on Clockwork. Unfortunately, now I'm getting some other error in regards to the Update.Zip file, Status 7.
I apologize for confusing people, but I promise I've read as much as I can about the tools I'm using, but I'm running in circles, flashing back and forth trying to find solutions.
you do not need to root before flashing the rom. it will be rooted after and then you can do what you need to do to get your apps working if you need to (firefly contains canadian locale cause its based off of rogers froyo firmware) changing stuff before you flash so apps can work is a waste of time as the flash will overwrite the firmware you just tweaked.
now, since your on eclair i'm attaching an update.zip that contains cwm, put it in the root folder of your sdcard boot into recovery select reinstall packages twice and it should boot into cwm where you can then flash firefly.
You're a frickin' genius, Studa. Don't let anyone tell you otherwise. I've got Firefly on thanks to that Update file, and I'm getting the ball rolling on everything else. If I wasn't so broke, I'd donate, but I hope my thanks is good enough. I really appreciate the help. It cut through twelve hours of stupid.

Categories

Resources