Database Develop

unregistered device after i9000 flash back to JF6

I have searched about this but found nothing that helped. I have flashed a few ROMS from the CoG versions to some of the other FroYo builds. I have not had any issues going back and fourth till the I9000 ROM.
In the past I would ODIN back to the JF6 on click then Kies mini to get back to the JH7 update. However after trying the i9000 ROM I have decided to go back to stock and Kies mini is now telling me that I have an unregistered device. I have used the JH7 OTA .zip to get back to JH7 and still Kies says it unregistered.
I have tried the files that were listed in another thread to resolve this issue but it still states that I have an unregistered device.
I have done the ODIN master clean and re-flashed multiple times with no change. Is there something the i9000 ROM did to my phone that ODIN will not flash out of the phone?

xisruno said:
I have searched about this but found nothing that helped. I have flashed a few ROMS from the CoG versions to some of the other FroYo builds. I have not had any issues going back and fourth till the I9000 ROM.
In the past I would ODIN back to the JF6 on click then Kies mini to get back to the JH7 update. However after trying the i9000 ROM I have decided to go back to stock and Kies mini is now telling me that I have an unregistered device. I have used the JH7 OTA .zip to get back to JH7 and still Kies says it unregistered.
I have tried the files that were listed in another thread to resolve this issue but it still states that I have an unregistered device.
I have done the ODIN master clean and re-flashed multiple times with no change. Is there something the i9000 ROM did to my phone that ODIN will not flash out of the phone?
Click to expand...
Click to collapse
Correct me if I'm wrong, but don't the I9000 roms require a special kernel? Have you flashed back to the stock Captivate kernel yet?

miztaken1312 said:
Correct me if I'm wrong, but don't the I9000 roms require a special kernel? Have you flashed back to the stock Captivate kernel yet?
Click to expand...
Click to collapse
Yes I have gone back to the original ODIN multiple times. When I did that I was going to go to the update JH7 via KIES but both my computers tell me my phone is unregistered. I had to use the OTA file DG has to get back to JH7.
I have tried on two computers with Kies mini and the full kies and Kies mini says that its an unregistered device full kies says something similar.
I am now running JH7 but just had the question about what happened by flashing caused Kies not to like my phone. In the past trying the different ROMs I was always able to use kies to get back until now (after the i9K flash).

I am also having exactly the same issue
trying to find a solution

It sounds like maybe the nv_data.bin file has the wrong operator code - something to check anyway. Use a hex editor to look at offset 00188000 SGH-1897ZKAATT

alphadog00 said:
It sounds like maybe the nv_data.bin file has the wrong operator code - something to check anyway. Use a hex editor to look at offset 00188000 SGH-1897ZKAATT
Click to expand...
Click to collapse
Sorry to ask but where would that file be? Are the values that you have listed what it is supposed to be?

alphadog00 said:
It sounds like maybe the nv_data.bin file has the wrong operator code - something to check anyway. Use a hex editor to look at offset 00188000 SGH-1897ZKAATT
Click to expand...
Click to collapse
well looking at that offset it is ÿÿÿÿREV0.4....ÿA
but 00188010 is TT....SGH-I897ZK
so is this what the problem is?

I changed the value but still gave me that same unregistered device issue.
I would like to find a solution if possible TY for your help

Anyone else have any ideas?
I know the new update is comming soon and would like to be able to get this via Kies.
I know this is the phone and not the computers that I am using.

It sounds like you only used odin to get the captivate ROM refreshed. I had the same problem, odin back to stock. Unregistered device. Flash to Tuyetama latest i9000 all better. After odin refresh try reflashing the stock captivate kernal.
Sent from my GT-I9000 using XDA App

civicr95 said:
It sounds like you only used odin to get the captivate ROM refreshed. I had the same problem, odin back to stock. Unregistered device. Flash to Tuyetama latest i9000 all better. After odin refresh try reflashing the stock captivate kernal.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
That is what got me to the point of having an unregistered device.
Unless I am missing what your saying to do?
This is what I have done to this point
was on JH7 and went to try one of the i9000 roms but didnt get a good signal.
I went back to stock with the ODIN one click back to JF6. Then tried to Kies mini back to JH7 but this is a no go as it said unregistered device. I had to flash DGs JH7_OTA. This is where I am now but still unregistered.

i am in the same boat and would like to get this fixed as well.
I have reflashed with odin a few times with and without the one click and even loaded the JH7 OTA clockwork recovery and it still doesn't see my device properly.

ok just went from tayutamas I9000 rom with voodoo/lag fix jpm rom, back to Odin one click captive factory fresh.
1. reflashed back to a jpk modem using CWM.
2. opened Odin 1click
3. rebooted into recovery
4. hit start on Odin after 5min. phone rebooted all works fine. Last time i tryed to flash back to stock using Odin I also had an unregistered device issue. The only change in my order of doing things was i flashed the jpk modem before i went back to stock. Just my experience not sure if it will help you all hope it helps SOMEONE.

civicr95 said:
ok just went from tayutamas I9000 rom with voodoo/lag fix jpm rom, back to Odin one click captive factory fresh.
1. reflashed back to a jpk modem using CWM.
2. opened Odin 1click
3. rebooted into recovery
4. hit start on Odin after 5min. phone rebooted all works fine. Last time i tryed to flash back to stock using Odin I also had an unregistered device issue. The only change in my order of doing things was i flashed the jpk modem before i went back to stock. Just my experience not sure if it will help you all hope it helps SOMEONE.
Click to expand...
Click to collapse
So your still have the unregistered device issue?
The flash of the JPK modem didnt help?
I am up and running with JH7 just want Kies to see my phone right.

No sorry I didnt clarify, yes my device is back to normal, Registered and non rooted. I apologize I should have been more clear. Hope this helps.

civicr95 said:
No sorry I didnt clarify, yes my device is back to normal, Registered and non rooted. I apologize I should have been more clear. Hope this helps.
Click to expand...
Click to collapse
do you have a link to the JPK modem? if you would like I would appreciate it.
I will try what you have done.

Here you go.
http://forum.xda-developers.com/showpost.php?p=8867525&postcount=57

followed your steps to a T and still it shows as an unregistered device.

anyone else have any ideas?

Wonder if this should be asked in the Devs section.
Sent from my SAMSUNG-SGH-I897 using Tapatalk

Flashing Back to Stock ROM using Heimdall

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.

[Q] Can't Go Back To Stock!

First I have a Captivate 1007.
Very easy to get into Download Mode so I know the phone isn't bricked.
I was running a version of Serendipity Rom. I wanted to try something different.
So I used what I always use the ODin3 One-Click Stock back to Eclair.
I get nothing but a boot cycle showing the AT&T screen.
Must I go to Stock Froyo now?
Would appreciate some guidance as I'm stuck after a few hours of searching!

Have you tried to flash odin again
CM7

Frawgg said:
First I have a Captivate 1007.
Very easy to get into Download Mode so I know the phone isn't bricked.
I was running a version of Serendipity Rom. I wanted to try something different.
So I used what I always use the ODin3 One-Click Stock back to Eclair.
I get nothing but a boot cycle showing the AT&T screen.
Must I go to Stock Froyo now?
Would appreciate some guidance as I'm stuck after a few hours of searching!
Click to expand...
Click to collapse
have read someone something the same what only works with him is flashing the leaked froyo. you may flash back to stock eclair after everything is working.

The leaked Froyo from Eugene?
I have that one I was just hesitant to flash it.
There is no .PIT file with it though. Is that ok?
EDIT:
Just tried with Odin3 1.7 got Eugene_JK2_Froyo.tar (2).md5 is invalid.
Going to try this one I897UCJI6-OCD-REV02-Low-designgears.exe

Frawgg said:
The leaked Froyo from Eugene?
I have that one I was just hesitant to flash it.
There is no .PIT file with it though. Is that ok?
EDIT:
Just tried with Odin3 1.7 got Eugene_JK2_Froyo.tar (2).md5 is invalid.
Going to try this one I897UCJI6-OCD-REV02-Low-designgears.exe
Click to expand...
Click to collapse
the designgears revo 2

mcord11758 said:
Have you tried to flash odin again
CM7
Click to expand...
Click to collapse
I have 1007 build, I would have to agree with ^^this^^.
Something might of happened in the flash. Try it again.

Use these specifically.
2.1 - http://www.megaupload.com/?d=SBSMALFJ
2.2 - http://www.megaupload.com/?d=QL6NX702

Working now after flashing with I897UCJI6-OCD-REV02-Low-designgears_1_.exe
What do you guys recommend flashing now back to original Eclair stock or staying?

Really up to you at this point. I don't bother with stock (original) firmware as they are bloated and whatnot.

Indeed. Going to try something with good battery life now!
Thank you for all the help fellas!
EDIT: Also I can't go back to 2.1 Stock. Only 2.2 Stock!

[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"

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.