Flashing Back to Stock ROM using Heimdall - Captivate Q&A, Help & Troubleshooting

I am having THE hardest time flashing back to stock rom using heimdall. I dont know how to use it, unfortunately i cannot use Odin..if anyone could instruct me on a step to step guide to getting this done, that would be great. i cannot seem to find one after looking for a good hour and a half :/ i got to samfirmware.com but once i download it asks me for a password and i input it (the one it shows to input) and it doesnt work.
Thank you

Just wondering, why can't you use Odin?
Sent from my Cappy using XDA App

something like this
Code:
$ heimdall flash --factoryfs factoryfs.rfs --cache cache.rfs ..... --kernel zImage
just type "heimdall" and it will print the usage format. you can flash whatever you want.

Tell us what OS you are using. Do you have the most current version of Heimdal?
Also, try unzipping the firmware with a different tool.(what are you using)?

The reason I cannot use odin is because I have a mac and odin is not mac compatible. I am using precision v3.5. Firmware 2.2.1 I've used the normal text editor and zipeg. And I have the most recent heimdall
Sent from my GT-I9000 using XDA App

FaithFor_TheFallen said:
The reason I cannot use odin is because I have a mac and odin is not mac compatible. I am using precision v3.5. Firmware 2.2.1 I've used the normal text editor and zipeg. And I have the most recent heimdall
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
so since you are already on a 2.2 rom we will hope you are not having the mac sbl.bin problems.
steps are:
1 grab the stock firmware from here if you want froyo
http://forum.xda-developers.com/showthread.php?t=963403
or find the equivalent eclair version in the forums or on the samsung firmwares site.
2 unpack the archive
3 unpack it again so you just have the various files in a folder. there are 4 important files in the froyo linked above and one .dll you can ignore.
4 put your phone in download mode
5 put the 4 file in the proper slots (see attached image)
6 hit start.. wait...
If Heimdall cannot see your phone you might be having the sbl problem. head over to the main heimdall support thread and search around... ther are quite a few mac users over there

Has anyone sucessfully been able to flash Samsung stock 2.2 using Heimdall?
For some reason when it's flashing factoryfs it fails at 43% "failed sending data packet"
I have downloaded KB1 from here http://forum.xda-developers.com/showthread.php?t=963403
And tried the .zip file that Kies downloads during it's upgrade process, both do the same thing.
Ultimately I'd like to find a universal flashing method to be able to restore my phone back to stock. While also being able to flash Clockwork kernels for rebuilding CM7.
The only way I've been able to get CM7 to load successfully is to Odin1Click back to JF6 then use Kies (which requires a different USB driver) to get 2.2 loaded.
Then install USB driver for Heimdall, to flash a Clockwork kernel for CM7 load.
If something goes sideways this process starts all over again.
Reinstalling USB drivers over and over again is getting rather tedious.
Would really like to find out why Heimdall is failing when flashing factoryfs.

why would you upgrade to 2.2 to get to CM7??? you can go to CM7 straight from 2.1 JF6

Bootloader question?
I made a post recently asking "What's the diff between 2.1 and 2.2 bootloaders?"
Nobody knows (or few cared to share their knowledge with the group). The best answer I got was, (paraphrased) 'none?'

Pirateghost said:
why would you upgrade to 2.2 to get to CM7??? you can go to CM7 straight from 2.1 JF6
Click to expand...
Click to collapse
Taken from Cyanogen Wiki wiki.cyanogenmod.com/wiki/Samsung_Galaxy_S:_Full_Update_Guide
Just above step one: "This guide assumes the Samsung Galaxy S already has Android 2.2 already installed on it."

JeffSchre said:
Taken from Cyanogen Wiki wiki.cyanogenmod.com/wiki/Samsung_Galaxy_S:_Full_Update_Guide
Just above step one: "This guide assumes the Samsung Galaxy S already has Android 2.2 already installed on it."
Click to expand...
Click to collapse
and what do you think is different about the 2 different versions in regards to a rom install?
both have to use the same recovery 2e and clockworkmod......the OS version doesnt mean ish to clockwork....

Pirateghost said:
and what do you think is different about the 2 different versions in regards to a rom install?
both have to use the same recovery 2e and clockworkmod......the OS version doesnt mean ish to clockwork....
Click to expand...
Click to collapse
At this point in time I'd be happy if I could get in back to 2.1....can't get either Odin1Click or Odin to reload 2.1...both are hanging when it tries to write the factoryfs files.
Which makes no sense at all...I had used 1Click twice earlier today and it worked fine...but now it's crapping out and no clue why.
Making me regret leaving my laptop at work...last time I had this issue I did the same process from my laptop and it worked.
Even stranger, first time I went through this process from this PC it worked...but isn't now.
Tried to get back to JF6 using download from samfirmware.com and using
Heimdall...will flash everything sucessfully (see attachment) except factoryfs. If factoryfs is selected, it chokes at 37%....attempted to flash factoryfs from command line and Heimdall fails with error "Failed to send data packet" or something along that line.

JeffSchre said:
At this point in time I'd be happy if I could get in back to 2.1....can't get either Odin1Click or Odin to reload 2.1...both are hanging when it tries to write the factoryfs files.
Which makes no sense at all...I had used 1Click twice earlier today and it worked fine...but now it's crapping out and no clue why.
Making me regret leaving my laptop at work...last time I had this issue I did the same process from my laptop and it worked.
Even stranger, first time I went through this process from this PC it worked...but isn't now.
Tried to get back to JF6 using download from samfirmware.com and using
Heimdall...will flash everything sucessfully (see attachment) except factoryfs. If factoryfs is selected, it chokes at 37%....attempted to flash factoryfs from command line and Heimdall fails with error "Failed to send data packet" or something along that line.
Click to expand...
Click to collapse
UPDATE: CM7 lives again, after Odin took 7 hrs. to push factoryfs to my phone only to have boot animation go garbled and lockup. I took my phone to work, used Heimdall on my laptop to flash JF6 and it was successful, was then able to re-flash Speedmod Kernel and CM7 nightly-50.
Next time I have to do this with my desktop I think I'm going to use USB Deview and blow away any Samsung devices listed.

i installed all required files in ubuntu , but i cant see gui interface ? like this
thanks.

JeffSchre said:
Taken from Cyanogen Wiki wiki.cyanogenmod.com/wiki/Samsung_Galaxy_S:_Full_Update_Guide
Just above step one: "This guide assumes the Samsung Galaxy S already has Android 2.2 already installed on it."
Click to expand...
Click to collapse
He's right though. All you need is cwm and your good. I've been on CM7 since March and have fts a few times. Did it yesterday and flashed CM7 from 2.1JF6. All good in the hood!
Sent from my SGH-I897 using XDA Premium App

cutiyar said:
i installed all required files in ubuntu , but i cant see gui interface ? like this
thanks.
Click to expand...
Click to collapse
you need to install the heimdall frontend (if you haven't already) - that is the heimdall gui.

pietro_spina said:
so since you are already on a 2.2 rom we will hope you are not having the mac sbl.bin problems.
steps are:
1 grab the stock firmware from here if you want froyo
http://forum.xda-developers.com/showthread.php?t=963403
or find the equivalent eclair version in the forums or on the samsung firmwares site.
2 unpack the archive
3 unpack it again so you just have the various files in a folder. there are 4 important files in the froyo linked above and one .dll you can ignore.
4 put your phone in download mode
5 put the 4 file in the proper slots (see attached image)
6 hit start.. wait...
If Heimdall cannot see your phone you might be having the sbl problem. head over to the main heimdall support thread and search around... ther are quite a few mac users over there
Click to expand...
Click to collapse
this will work to nexus s?

cutiyar said:
this will work to nexus s?
Click to expand...
Click to collapse
if you really want to use samsung touchwiz, i would be more than happy to trade you straight across a brand new captivate for a nexus s....

Any help for doing this with 1.3, since I have lion and 1.1 won't work.

Running Lion and Heimdall 1.3
I'm also on Lion and can only use 1.3. I have a Tmo Samsung Vibrant and would like to flash back to 2.1. I was able to root the phone just fine when it was on 2.1 from my Mac but since I updated to the official Froyo, I haven't found a way to root it again. Thanks in advance for any help.

Related

Where is the KB1 FactoryFS.rfs?

I can't seem to find the factoryfs.rfs file for AT&T Android 2.2 Froyo UCK.B1 . I am returning a phone for bad buttons and I would like to flash back to stock. The Odin3 one-click is missing some software and I'd like to just flash it back to stock.
AdamOutler said:
I can't seem to find the factoryfs.rfs file for AT&T Android 2.2 Froyo UCK.B1 . I am returning a phone for bad buttons and I would like to flash back to stock. The Odin3 one-click is missing some software and I'd like to just flash it back to stock.
Click to expand...
Click to collapse
can you flash jf6 with odin full and use kies to update to kb1?
uploading now. all you had to do was email me
just a Q...
what is one-click missing?
Done and done
Sent from my atrix
I have the filesystem extracted to my computer from this phone when I got it....
I'm trying to see the differences... There were 3 full pages of apps in the KB1 release whereas Odin3 1 click had only 2.5 pages.
GalaxySSupport.apk
WHERE_Samsung_GT-I900_Vegas_EN
It was some silly stuff.
AdamOutler said:
I have the filesystem extracted to my computer from this phone when I got it....
I'm trying to see the differences... There were 3 full pages of apps in the KB1 release whereas Odin3 1 click had only 2.5 pages.
GalaxySSupport.apk
WHERE_Samsung_GT-I900_Vegas_EN
It was some silly stuff.
Click to expand...
Click to collapse
thats because ODIN one click jf6 is 2.1 .... its not 2.2. the only one click for 2.2 is the leaked JI6 from way back when.....
I used the 2.2 version from DesignGears. DesignGears should release another one for 2.2 with an updated factoryfs, since his last release is not a 1-click back to stock, but a 1-click development release.
those would be odin packages, not one-clicks.. there is only one one-click..
Can you link to this one-click?
I know of Odin3 one-click for 2.1 and 2.2, and Super-one-click.
DG cant make a new one click. one click is closed source.. he posted this but didnt make it. All odin3 programs are from samsung.
Here is the one the only Odin3 one-click downloader.
http://forum.xda-developers.com/showthread.php?t=731989
the other stock flashes he posted are for " Odin3 " flashing utility and are internal betas from samsung firmware site.
not trying to be a smart ass... but..
note how you have to click PDA select file..., PIT select file.., and START.. (its a couple more than one click)
and super one click thats for rooting, and not odin...
oh ya you are a linux guy, you dont mess with odin just the packages!
the odin "one-click" is a flasher with the ATT 2.1 stock built into the installer. all nicely closed (sourced) up! the whole exe is 160mb or so...
and the odin3 flasher util there is versions 1.0 thru 1.82 (i have 5 versions) as far as i know now
^^ The only standard odin3 version you should use on the Captivate is 1.7. Their versioning system is by phone model. They make a new version per phone.
Here is designgear's 2.1 release of Odin3 1-click: http://forum.xda-developers.com/showthread.php?t=731989
Here is designgear's 2.2 release of Odin3 1-click: http://forum.xda-developers.com/showthread.php?t=797282
The 2.1 release is JF6. The 2.2 release is JI6. I assume he has source, or a friend who works at Samsung... However, JI6 was basically a beta version so why would Samsung release a 1-click?
I prefer to use heimdall for flashing though. It's open source, and safer as 1-clicks will modify the partition information tables, primitave bootloader and both secondary bootloaders... Those are the things that brick phones.
i stand corrected...
oh no sh!t didnt know about the beta... lets keep that quiet to not confuse the noobs.
and the other versions of odin work just fine for me, .81 and .82 have the option to flash bootloaders separately, but never used it..
flashed with .82 the past 2 nights i semi bricked trying to change my params.lfs
but i have read somewhere designgears telling people he does not have the source and cannot modify or edit the one-click,
hes been asked a million times "can you make a new one click for this...." (mosty froyo when it came out...)
everytime he or someone else says the same thing. "cant its closed source from samsung"
dunno how he got the beta though.... unless hes covering for somebody..
TRusselo said:
i stand corrected...
oh no sh!t didnt know about the beta... lets keep that quiet to not confuse the noobs.
and the other versions of odin work just fine for me, .81 and .82 have the option to flash bootloaders separately, but never used it..
flashed with .82 the past 2 nights i semi bricked trying to change my params.lfs
but i have read somewhere designgears telling people he does not have the source and cannot modify or edit the one-click,
hes been asked a million times "can you make a new one click for this...." (mosty froyo when it came out...)
everytime he or someone else says the same thing. "cant its closed source from samsung"
dunno how he got the beta though.... unless hes covering for somebody..
Click to expand...
Click to collapse
Oh man Tru admits he has been corrected haha kidding bud.
Although, nice read. Thanks guyz, got to learn a bunch
AdamOutler said:
^^ The only standard odin3 version you should use on the Captivate is 1.7. Their versioning system is by phone model. They make a new version per phone.
Here is designgear's 2.1 release of Odin3 1-click: http://forum.xda-developers.com/showthread.php?t=731989
Here is designgear's 2.2 release of Odin3 1-click: http://forum.xda-developers.com/showthread.php?t=797282
The 2.1 release is JF6. The 2.2 release is JI6. I assume he has source, or a friend who works at Samsung... However, JI6 was basically a beta version so why would Samsung release a 1-click?
I prefer to use heimdall for flashing though. It's open source, and safer as 1-clicks will modify the partition information tables, primitave bootloader and both secondary bootloaders... Those are the things that brick phones.
Click to expand...
Click to collapse
this is off topic but i have been using linux and it is all that is on my pc right now. i have win7 in a virtual machine but there must be a linux package missing that i used to have because i can only get the phone to pass throught to the virtual machine for kies in mtp mode. i used to be able to mount it to the virtual machine in any mode on an older install of mint 9. i am having issued with other devices too, it seems the whole system to mount devices has changed and i cant play some audio cd's. there is no fstab reference and the mount folder is empty, there is now a media folder that is empty untill something is mounted like a dvd.
i can live with the issues above if you cant help the linux forums are full of posts like mine with mount issues for cd's and advice that doesnt work relating to fstab so im not expecting a quick answer.
i do however need a way to flash the phone and have never compiled an application from source. what will i need for heimdal? and could you pm me with a brief explaination? or is it something that you'd have to walk me through?

[Q] [Assistance]AT&T Capitave 1104 - boot loop

Just got a "new" captivate due to defect in the last one.
This new Captivate worked fine at 2.2 I was in the beginning stages of a prep for Continuum when this happened.
The boot loop seems to be attributed to the Odin One-Click to 2.1, seems almost like there is a different partition layout in the newer build versus the older one. Is that possible? I read something about pit files maybe?
What has been done:
1. Built a jig
2. can reboot into download mode reliably with jig
3. Tried to flash OCD to 2.1 around 10x before I gave up.
4. Flashed the Ursa minor kernel, just sits after stating "converting XX partition"
5. Flashed "back" to 2.1 with OCD again. Boot loop [confirmed]
6. Brought phone into work and tried the re-install of 2.1 [boot loop]
So now I am looking for stock 2.2 images I can flash with Odin, only thing is I can only find Rodgers....
Who has some ideas?
sounds like you have a later build phone that doesnt like odin one click...thats all your gonna get out of it is a bootloop
get into download mode and use this package:http://forum.xda-developers.com/showthread.php?t=995143
if you go to gingerbread and want to revert back to stock bootloaders you will have to use one click, even though you will end up in a bootloop and then use the package i posted to get it up and running completly sotck.
I tried that right after I posted and that didn't seem to work either, it actually froze up. In the end I had a true brick, even the jig couldn't get it into download mode anymore. It was just dead. I'm thinking the internal SD got corrupted.
I returned the phone and got another that I am not doing anything with until the GB update from Samsung comes out.
As a follow up it seems the only way to get back to stock reliably with a greater than 1010 build is to use the stock froyo from this thread:
http://forum.xda-developers.com/showthread.php?t=963403
IF the partitioning is fscked:
I'm still researching but I assume it's due to a param.lfs and pit issue. I may rip open the archive when I get a second to see if they are in there.
I haven't tried this! This is not the gospel! Do this at your own risk.
My phone is still stock at the moment and may very stay that way until hell freezes over or the ATT update to 2.3.4 comes along.
Partitioning is in the .pit in fact that's exactly what pit stands for.
P= partitioning
I= Information
T= table
dan_maran said:
My phone is still stock at the moment and may very stay that way until hell freezes over or the ATT update to 2.3.4 comes along.
Click to expand...
Click to collapse
Smart money is on hell freezing over!
studacris said:
Partitioning is in the .pit in fact that's exactly what pit stands for.
P= partitioning
I= Information
T= table
Click to expand...
Click to collapse
I did get that much, but I remember mine failing at the param.lfs(in Odin) then I heard rumblings about the pit being the culprit when taking a >= 1010 build down to 2.1
Just trying to get all the information in one spot for myself and anyone else who has has this happen. Like finding a pit file from a stock 2.2 build etc.
edit: I don't know when this will go through as I have to wait 5 minutes... (tick tock tick tock)
Here is a post that has all the needed information:
http://forum.xda-developers.com/showthread.php?t=1134443
Scroll down to "For Build 1010's [+] that CANNOT use Odin One Click and coming from GB Bootloaders"

Need help with installing a custom rom.

Please help!!! I have searched and searched and searched the forums and have come across so many threads on how to add a custom rom to your Captivate.
To start, what I have been trying to do is add a custom rom after upgrading my phone from ver 2.2 to 2.3.3 GB. Some posts say you can just upgrade with the 2.3 on the phone, other posts say you need to take the phone back to the stock 2.1 rom. Then you find posts that say, make sure you have the stock bootloaders and kernals when you downgrade to the stock 2.1.
You can easily see how even a somewhat above novice can get confussed. To take my phone back to 2.1 I have followed posts that say use Odin 1.3. I have used odin before so no big deal. However in this case again you are getting different opionions and versions on this. Some have just the odin .exe and others have the .exe and the MD5 and .ini it the package. I am assuming that the one with just the .exe has everything built in as the size is quite big.
I have tried both ways and after I "Flash" it will not finish with the normal recovery mode and see the linux script. It will go to the ATT window and just keep rebooting over and over. I then will use my JIG and get back in download mode in order to reflash back to 2.3.3 just to get the phone to work again.
Can someone please give me a clue as to what I am doing wrong or direct me to the proper files and maybe some better step by step instructions.
Thanks in advance for the help.
What Rom is currently on you phone? Which Bootloaders do you have installed?
Sent from my blazing fast Captivate running Continuum GB ROM using Tapatalk Pro
Rhiannon224 said:
What Rom is currently on you phone? Which Bootloaders do you have installed?
Sent from my blazing fast Captivate running Continuum GB ROM using Tapatalk Pro
Click to expand...
Click to collapse
Here is the info:
Firmware: 2.3.3
Baseband: I897UCKF1
Kernel: 2.6.35.7-I897UCKF1-CL273832
Build: GIGERBREAD.UCKF1
^ From the looks of what u posted, it looks like u have the leaked i897uckf1 currently on ur phone. If that is the case, then u could Odin the Cognition Beta 2 Kernel and then flash the latest Cog Rom (having already copied it to ur internal sd).
Just flash the kernel through Odin then use button combo (volume +/- and power...release after u see the at&t screen) to get into CWM 4.0.0.5 and flash Cog 5 v 1.00 from there.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Are you plugging into a usb port in the back of your pc? Also, there are several methods for flashing back to stock now, once you upgrade to GB bootloaders you don’t ever want to use the Odin with the button fix because it will only flash the secondary bootloader and the primary bootloader will remain GB and the result will be a hardbrick. Also, some of the newer builds came with Froyo installed and using the older 1 click Odin by DesignGears will put those devices in a bootloop. So it really is dependent on your device and your needs. I now use the method outlined in the Continuum 6.1 thread which will not touch the bootloaders and brings you safely back to 2.1 stock. I always clear user data and cache in recovery, flash back to stock using Cezar's method (not a 1 click) prior to flashing a new Rom. Most devs recommend flashing to stock first because there is less chance of corruption.
Sent from my blazing fast Captivate running Continuum GB ROM using Tapatalk Pro
http://www.youtube.com/watch?v=UOyx5JQ_8_I
MobileTechVideos video is how i flashed my first gingerbread ROM. Its easy, straight forward and he has all the links you will need under the video.
piece-a-cake
Gupone said:
Please help!!! I have searched and searched and searched the forums and have come across so many threads on how to add a custom rom to your Captivate.
To start, what I have been trying to do is add a custom rom after upgrading my phone from ver 2.2 to 2.3.3 GB. Some posts say you can just upgrade with the 2.3 on the phone, other posts say you need to take the phone back to the stock 2.1 rom. Then you find posts that say, make sure you have the stock bootloaders and kernals when you downgrade to the stock 2.1.
You can easily see how even a somewhat above novice can get confussed. To take my phone back to 2.1 I have followed posts that say use Odin 1.3. I have used odin before so no big deal. However in this case again you are getting different opionions and versions on this. Some have just the odin .exe and others have the .exe and the MD5 and .ini it the package. I am assuming that the one with just the .exe has everything built in as the size is quite big.
I have tried both ways and after I "Flash" it will not finish with the normal recovery mode and see the linux script. It will go to the ATT window and just keep rebooting over and over. I then will use my JIG and get back in download mode in order to reflash back to 2.3.3 just to get the phone to work again.
Can someone please give me a clue as to what I am doing wrong or direct me to the proper files and maybe some better step by step instructions.
Thanks in advance for the help.
Click to expand...
Click to collapse
Listen, I'm new at this and learned watchin mobiletech videos from youtube. At first I found it hard but now is pretty easy (in my opinion). The first thin I do is back up apps with titanium and paste to my laptop (for me is faster to install them back), go back to stock 2.2, master reset using dialer (no odin), root, reboot, install rom on sd card, using odin i install bootloaders (I9000), flash talon kernel (odin), flash rom (CWM) and reboot. That's how I do it. Now, I could b wrong but doing it that way, in that pattern works for me. Like I said, I'm new at this but trust me....I've done it several times and it works for me. Keep reading and then decide how you want to do it. Good luck..."HONESTLY"!!!
It all depends on where you are now and where you want to go.
Sent from my SGH-I897 using XDA App
I'm new to all of this and have done a good amount of research but seems like the information never ends and there are a few ways to load a custom rom.
Method one
BACK UP!!!
Flash to stock (FTS)
Wait for your phone to reboot and then re-enable debugging
Hook phone back up to pc and Master Clear (MC) using Odin
Load Clockwork update.zip (DOWNLOAD)
Load FireFly_X-X.zip to phone memory
Remove sim and external SD, and unplug USB
Boot into recovery and reinstall packages (You may have to reinstall packages twice to get to Clockwork recovery)
Once in Clockwork recovery (Green Text), select install zip from SDcard
Next select choose zip from sdcard
Scroll down to FireFly_X-X.zip and select the file
This will run the script and install the ROM to your phone
After this is done, select go back and then select reboot phone
This may take a while, so leave your phone and go grab a snack!
Method 2
Load ROM file onto phone
Boot into recovery
Select ROM and flash it
Reboot, wait and enjoy
Wash, rinse, repeat!
What are the differences? Which one is better?
Seems like the first video is very simple and straight forward?
Am I missing something here? I'm already rooted and used titanium backup.
I'm on 2.2 Froyo and wanting to flash to Firefly 3.0
Thanks!

Help a rusty flasher! (can't go back to stock 2.1 X_X)

Hey folks, I'm a casual flasher and have done most of the pre-requisite background readings. Went from 2.1 -> 2.2 Cognition and then -> 2.3 Serendipity so I can scrape by normally.
Everything was good on 2.3.5 with the GB bootloaders but then I tried to update to ICSSGS 4 but it didn't go well. Got stuck at the boot screen (probably I should have reset to factory settings)..I thought I would try to re-flash Serendipity using Odin but it didn't work.
Ok this is bad..so I tried to restore to all the way back to stock using Odin 1 Click for Rogers. ( http://forum.xda-developers.com/showthread.php?t=979133 ). This successfully got me back to 2.1 and I seem to have retained the GB bootloaders as I still have the i1900 boot screen first. Attempts to re-flash back to 2.3.5 through Odin have resulted in errors, and soft-bricked (pc-!-phone screen). However, I have been able to get back into download mode to restore to 2.1.
So now I need to get back but I'm having issues...
1) can't seem to manually get into recovery mode anymore using 3 button.
2) Wasn't able to unroot using one click unroot...gave me an error type 7 whatever that means.
3) Trying to flash kernels through odin seems to have failed the 2 times I tried it. I'm kind of scared to test my luck to try it again without a jig.
4) So what's the best way to get a kernel with CWM so I can try to get back to 2.3.5 at least?
5) Should I try this new-fangled heimdall instead?
Any assistance is appreciated... I'm afraid of screwing this up even more..
phrenicthenub said:
Hey folks, I'm a casual flasher and have done most of the pre-requisite background readings. Went from 2.1 -> 2.2 Cognition and then -> 2.3 Serendipity so I can scrape by normally.
Everything was good on 2.3.5 with the GB bootloaders but then I tried to update to ICSSGS 4 but it didn't go well. Got stuck at the boot screen (probably I should have reset to factory settings)..I thought I would try to re-flash Serendipity using Odin but it didn't work.
Ok this is bad..so I tried to restore to all the way back to stock using Odin 1 Click for Rogers. ( http://forum.xda-developers.com/showthread.php?t=979133 ). This successfully got me back to 2.1 and I seem to have retained the GB bootloaders as I still have the i1900 boot screen first. Attempts to re-flash back to 2.3.5 through Odin have resulted in errors, and soft-bricked (pc-!-phone screen). However, I have been able to get back into download mode to restore to 2.1.
So now I need to get back but I'm having issues...
1) can't seem to manually get into recovery mode anymore using 3 button.
2) Wasn't able to unroot using one click unroot...gave me an error type 7 whatever that means.
3) Trying to flash kernels through odin seems to have failed the 2 times I tried it. I'm kind of scared to test my luck to try it again without a jig.
4) So what's the best way to get a kernel with CWM so I can try to get back to 2.3.5 at least?
5) Should I try this new-fangled heimdall instead?
Any assistance is appreciated... I'm afraid of screwing this up even more..
Click to expand...
Click to collapse
1) well if you have i9000 bootloaders recovery is 2 button combo. not 3
2) error 7 or whatever that means... search cwm error 7 and find out... and its not error 7, it is STATUS 7. when you get an error, write down the error and type it into google. phone/pc/life...
2b) that is the oldest way to root captivate. search/download " superOneClick Root " nuff said.
3 /4 ) best ONLY way to get a cwm kernel without having Cwm is odin or heimdall, you cant brick flashing kernel, jig not needed. make sure you are using a newer version of odin 1.5 or newer please...
5) not going to hurt trying, but quite different from odin.
Thanks for the quick replies and addressing my various points! Big fan of your one click to stock.
Perhaps a stupid question, but are there disadvantages to using one click odin rom flashing setups such as: http://forum.xda-developers.com/showthread.php?t=1285616 (stock 2.3.5)? Is this safe for me to use from 2.1 (with GB bootloaders)?
Just seems a lot easier than manually choosing files for pda spots etc.
that is the same thing as my one-click-to stock "odin one clicks" but that is ATT and mine is rogers.
however the ATT version is better and higher android version, so i used it myself. but stock roms suck. take some time read up, (read flashing link in my sig) find a nice cool custom rom.
TRusselo said:
that is the same thing as my one-click-to stock "odin one clicks" but that is ATT and mine is rogers.
however the ATT version is better and higher android version, so i used it myself. but stock roms suck. take some time read up, (read flashing link in my sig) find a nice cool custom rom.
Click to expand...
Click to collapse
True, I agree that custom roms are better than stock..I'd just like to get a better proper 'base' to flash my next rom than from 2.1 without cwm and root. I'll check out your guide.

help with flashing back to stock!

hey guys have the rogers captivate 896. I have a jig for download mode. Ok so I was on miui gingerbread. I wanted to try with weUI ics. So I followed their procedure correctly. Install completed but like another user I got it hanging at the MI boot screen. So having to flash to stock before I felt comfortable. So I've always used odin 1.32. I set the pit file that came with it and downloaded the rogers. 2.2 stock files. I get in d/l mode, run odin does some things, and it gets halfway through the factoryrs file and fails. I'm freaking lost here. Any ideas on how to get this back to stock?
If its the same files you used before I'm willing to bet its a funky usb cable. But before you go buy another (unless you have a spare) Try rebooting machine running as admin re-downloading the firmware. Also probably not the issue Odin 1.35 is kinda older version, but thats just my personal thing.
on both of those and still no factoryrs pass. switched new usb cable, switched all ports. so if the ics files installed, would I be able to go back to 2.2 stock rom? can anyone walk me through this as I think I'm doing this write. I even tried clicking reset bootloaders and that didn't work. So here's what I'm doing.
have jig, go into d/l mode
start odin 1.82. check repart, and leave the other two checked. load 512 pit, phone tar file and start.
this seems insanely easy. did this before but even after 10 attempts it fails. could ics be messing this up?
Don't check repartition and try it.
shouldn't you always repartition it though?
going to try flashing from a different pc. so i'm able to get in d/l mode which I know is good. I don't know what took on my phone, I'm thinkin ics installed, so can anyone point out the proper procedure to go back to 2.2 on a rogers captivate? is it merely odin, 2.2 stock, check repartition, set pit and tar, then flash?
Search for a member that goes by trusselo he has done some good stuff for the Rogers captivate
Here is his xda page. look in his signature
http://forum.xda-developers.com/member.php?u=3531712
hey I tried 3 different cords, 2 computers and multiple usb slots. All fail on factoryrs.rfs. So even in unchecking re-partition this tanks. I have a jig so getting into d/l mode is easy, I just can't get this darn thing back to stock. so i'm guessing (big guess here) I have ics files on my phone, how would I get back to 2.2. Be gentle I'm still slightly new at this!
xtracrispy69 said:
shouldn't you always repartition it though?
Click to expand...
Click to collapse
I've used Odin to get out of ICS and I never checked repartition or use pit file. But I use I897's firmware. Never used i896.
Sent from my ICS powered Captivate using Tapatalk
prbassplayer said:
I've used Odin to get out of ICS and I never checked repartition or use pit file. But I use I897's firmware. Never used i896.
Sent from my ICS powered Captivate using Tapatalk
Click to expand...
Click to collapse
what did you flash? I tried flash 2.1 and 2.2 both fail factoryrs.rfs. even tried odin 1.81. so it has to be something with the 2.2 and 2.1 rom. Just want to get this darn thing back to stock. any ideas?
Any GB firmware I had laying around. KH4, KJ3, KF1. I don't usually use GB anymore but I've needed to go back a few times to try things out.
see most posts i've read say you must repartition with 2.2 and below and can't use a pit file with 2.3. I'm wondering what'll happen if I just flash a gb 2.3.
xtracrispy69 said:
see most posts i've read say you must repartition with 2.2 and below and can't use a pit file with 2.3. I'm wondering what'll happen if I just flash a gb 2.3.
Click to expand...
Click to collapse
Go for it 10char
xtracrispy69 said:
hey guys have the rogers captivate 896. I have a jig for download mode. Ok so I was on miui gingerbread. I wanted to try with weUI ics. So I followed their procedure correctly. Install completed but like another user I got it hanging at the MI boot screen. So having to flash to stock before I felt comfortable. So I've always used odin 1.32. I set the pit file that came with it and downloaded the rogers. 2.2 stock files. I get in d/l mode, run odin does some things, and it gets halfway through the factoryrs file and fails. I'm freaking lost here. Any ideas on how to get this back to stock?
Click to expand...
Click to collapse
Are you using 2.1 and 2.2 packages that have bootloaders on them?

Categories

Resources