Read BEFORE flashing!!

[DOAlaboratories]

Let's keep this bumped.

Sent from my SAMSUNG-SGH-I897 using Tapatalk

 

[xredjokerx]

love it. *thumbs up*

 

[Verrigan]

I find it funny that the flaming in every other General thread in this section is not in this one.

 

[sschrupp]

this should definitely be a sticky.

 

[ice3186]

why isn't it already!

this should definitely be a sticky.

+1 for this, it would save years of time!

 

[Belaflek]

Amen to that bruddah

 

[ootz0rz]

I would also say its a good idea to back up your efs folder. Mine got all borked up when that jpc rom came out a while ago and it is a ton of work to fix. Sgs tools copies your nvdata.bin and. /nvdata.bak files to your sd card if you do a product code check. Or you can use root explorer.

Is making a nandroid backup not sufficient to cover that as well?

Sent from my SAMSUNG-SGH-I896

 

[lbbo2002]

I had to use this info recently so lets Sticky this beasty.

Personally if you have odin open, hold both volume buttons at the same time and plug in the USB to the phone it jumps right in to download mode every time (even with the sim and ext SD card in).

Anyone having issues with master clear.... seems the last few tries are not working for me, Weird.

 

[kaiser_tytnii]

if anyone could possibly help, it'd be much appreciated

my problem is described here...
http://forum.xda-developers.com/showthread.php?t=857538

 

[hillbilly12345]

Problem reinstalling packages

this is somewhat related to your post and maybe you can help.
I receive the following error message when i try reinstalling packages from recovery screen running Froyo 2.2 on captivate

E:failed to verify whole-file signature
E:signature verification failed

Installation aborted.

 

[malfuncion]

this is somewhat related to your post and maybe you can help.
I receive the following error message when i try reinstalling packages from recovery screen running Froyo 2.2 on captivate

E:failed to verify whole-file signature
E:signature verification failed

Installation aborted.

If you flashed the STOCK 2.2 ROM, via ODIN 1 click per say, the factory 3e recovery will not work with the Clockwork recovery. It cannot verify the signarture- the problem you have.

To fix this you will either need to flash some kernel from the threads here using the REAL ODIN (not 1 click) or you will need to flash another 2.2 rom from the factory 2.1 eclair (JH7).

 

[NightVVulf]

Thanks man! This is some great info, I sure wish I had this before I had to take my phone back to AT&T.

 

[slifer315]

I would just like to remind everyone that actually does read this before flashing to test if you have the button combination for recovery and download before flashing anthing to your phone. if you find out that you do not have the combinations enabled, you need to use the fix posted in the OP.

 

[nappent]

I just tried this and it just keeps going into the AT&T Logo loop... I think I'm really screwed

 

[CLShortFuse]

I suggest you add a section to say that you should get your unlock code while you're still on stock before jumping to 2.2 (which will wipe the code from your device)

I suggest SuperOneClick

 

[tazman171]

I just tried this and it just keeps going into the AT&T Logo loop... I think I'm really screwed

Tried what?

I suggest you add a section to say that you should get your unlock code while you're still on stock before jumping to 2.2 (which will wipe the code from your device)

I suggest SuperOneClick

It doesn't actually get wiped, there is a file that contains it in hex or something like that. I think there is an app for getting it from that file. But it's still a good idea to write it down with android ID changer or the app you mentioned.

 

[CLShortFuse]

Tried what?



It doesn't actually get wiped, there is a file that contains it in hex or something like that. I think there is an app for getting it from that file. But it's still a good idea to write it down with android ID changer or the app you mentioned.

Yes, that file gets the code wiped to 0xFFFFFF in hex

 

[tazman171]

I must have gotten lucky, I never lost mine. I do change it after every flash but it had been 5 or 6 cog froyos before I actually wrote it down when going to stock JF6. Copied and changed it with Android ID Changer and I suddenly had access to apps I hadn't been able to update for a while. I must have had it backed up somewhere that master clear, etc. hadn't touched it.

On the bricked note, last night I was flashing back to JF6 with Odin one click. About a quarter way into it windows decided that my samsung usb drivers should quit and disable my my flash. The phone screen went a real dim red and that was that. Waited for 10 min+ but Odin saw no device nor Windows, Win 7Pro 64 bit, for that matter. Pulled the battery and nothing, no battery charging graphic, no home button lights, vibration, NOTHING! So I fiddled with it, rebooted the comp to no avail.

My sim and sd were already removed before flashing so I resurrected my Tilt just in case and went to the forums.

I found a post somewhere (can't remember where, sorry) about just barely making battery contact with the contacts on the phone while holding vol +- and power down with the USB plugged in and Odin running to get some sign of life.

I did this for about 5 min after letting the phone sit for 30 secs or so with no battery or usb card and got 6 lines of red text to come up then disappear.

Kept doing the "trick" and after about 10 mins the phone suddenly came on in download mode! Yes! , flashed to stock then put Perception 8 non oc/uv on with no problems.

I wish I remembered who posted that but THANK YOU!

My phone acted 100% dead, no power, lights, etc. Battery was 100% before I tried flashing back to stock and out of over 20+ flashes I've never had this happen. So I guess even the dead captivate can rise, lol.

 

[Pirateghost]

I must have gotten lucky, I never lost mine. I do change it after every flash but it had been 5 or 6 cog froyos before I actually wrote it down when going to stock JF6. Copied and changed it with Android ID Changer and I suddenly had access to apps I hadn't been able to update for a while. I must have had it backed up somewhere that master clear, etc. hadn't touched it.

he wasnt talking about your android ID, he was talking about the UNLOCK code so that the phone can be used on other carriers

 

[tazman171]

he wasnt talking about your android ID, he was talking about the UNLOCK code so that the phone can be used on other carriers

Well, I totally missed that part. And I did read the previous pages.

LOL, sorry CL wasn't trying to argue anyway.