Database Info

Using the Canadian version of Kies (1.5), how does one upgrade to 2.2?

Hello, I have tried a few things, and so far have made no progress. Kies can't find any new updates, and now, after a reinstall, can't even find my device in the firmware update manager. Help!
EDIT: Kies can find the device, but under the Update Manager, it doesn't list anything needing an update.

If you have a US version of Captivate, it doesn't matter which version of Kies you use. Your phone reports its product id to Kies and it checks Samsung server to see if there is any updates. Right now, there is no update yet for US Captivate.
Sent from my SAMSUNG-SGH-I897 using XDA App

I'm using a Canadian i896 with Rogers.

how is it possible that rogers gets an update faster than att when att released frist lol

Getting kies to work is a huge hassle. Took at least a few hours to get kies to recognize on a friebds phone after trying so many methods. Kies just sucks, especially for the captivate. Try rooting abd flashing a new rom. It is much faster to get 2.2 or even 2.2.1
Sent from my SGH-I897 using XDA App

The thing is, I've had troubles with custom ROMs messing up my MMS settings, data settings, and the like, and I just want to get the stock 2.2 firmware.
EDIT: What steps did you use to get it to see your phone?

MorganFreeman911 said:
The thing is, I've had troubles with custom ROMs messing up my MMS settings, data settings, and the like, and I just want to get the stock 2.2 firmware.
EDIT: What steps did you use to get it to see your phone?
Click to expand...
Click to collapse
Since you've installed custom ROMs, the issue you are having is that the product code in your nv_data.bin has been changed to something other than what it needs to be for Kies to report that it's a Rogers I896 and should be eligible for the 2.2 upgrade. You can check what the product code it's reporting to Kies by using regedit. Go to HKEY_CURRENT_USER\Software\Samsung\Kies\DeviceDB\1 and look in the right hand pane at the Product Code entry. If it says anything other than SGH-I896ZKARWC it is not going to show that 2.2 is available to upgrade to.
If it is reporting another product code there then you need to either 1) modify your nv_data.bin to match the Rogers product code or 2) put a copy of your original nv_data.bin back on the phone and then try Kies again and it should detect that there is an update available almost right away. Have you restored to Rogers 2.1 stock, yet?
HTH

Riker2k said:
Since you've installed custom ROMs, the issue you are having is that the product code in your nv_data.bin has been changed to something other than what it needs to be for Kies to report that it's a Rogers I896 and should be eligible for the 2.2 upgrade. You can check what the product code it's reporting to Kies by using regedit. Go to HKEY_CURRENT_USER\Software\Samsung\Kies\DeviceDB\1 and look in the right hand pane at the Product Code entry. If it says anything other than SGH-I896ZKARWC it is not going to show that 2.2 is available to upgrade to.
If it is reporting another product code there then you need to either 1) modify your nv_data.bin to match the Rogers product code or 2) put a copy of your original nv_data.bin back on the phone and then try Kies again and it should detect that there is an update available almost right away. Have you restored to Rogers 2.1 stock, yet?
HTH
Click to expand...
Click to collapse
My product code is correct, I repaired it earlier, but I'm having the same issue.

Awesome, that's a good start. Are you on Rogers stock 2.1? Does Kies detect your device? When you click the update firmware button what does it say? Does the Kies entry in the registry show that it detects it as that product code? Does it show I896UXJI2/I896RWCJI2/I896UXJI2/I896UXJI2 in the HIDSWVER entry?

have Windows 7 Ultimate and Hard time Kies Recognizing my Phone. I used the same method which used to fix an iPhone Issue ages back
1) Download Your Uninstaller 2010 ( Free trial ) and removed currently installed KIES - it removes it plus cleans up form the registry
2) Download everything from http://www.voidtools.com/ - it's like an interactive search and picks everything in your PC. Search for Samsung and Kies, delete all files and folders which say Samsung and Kies
3) Reboot PC
4) Install Canadian Kies Ver http://www.samsung.com/ca/support/de...ub_class_cd=P#
5) Open Kies (You have to be in TW Launcher, not LauncherPro or other for Kies to detect the phone and do a firmware update)
6) Plug in your phone with Kies firmware update On (in Settings/Application/usb settings)
7) Select Firmware Update in Kies
8) Click the Update button
9) Wait for the download to finish then you will see another Windows POP up, DONT PRESS OK
10) Disconnect USB | Power OFF Phone
11) Power Phone ON with VOL Buttons ON, it will come to Downloading... Download mode (Black/yellow screen with a shovelling droid)
12) Connect USB after 5 seconds
13) Press OK on Kies so it pushed the update to the phone
14) Kies will say Update Completed and your phone should be sitting on Galaxy S, diconnect cable and you enter Froyo

Riker2k said:
Awesome, that's a good start. Are you on Rogers stock 2.1? Does Kies detect your device? When you click the update firmware button what does it say? Does the Kies entry in the registry show that it detects it as that product code? Does it show I896UXJI2/I896RWCJI2/I896UXJI2/I896UXJI2 in the HIDSWVER entry?
Click to expand...
Click to collapse
Yep, odin'd back to JI2. Kies connects no problem, but once I hit update firmware, and get to the list of devices that need firmware updates, it's empty. I've got 3 entries under DeviceDB, one of them has the correct info. Under HIDSWVER, I have I896UXJI2//I896UXJI2/I896UXJI2 instead. I'm betting I can't just edit it through there, can I?

TheEscapist said:
Yep, odin'd back to JI2. Kies connects no problem, but once I hit update firmware, and get to the list of devices that need firmware updates, it's empty. I've got 3 entries under DeviceDB, one of them has the correct info. Under HIDSWVER, I have I896UXJI2//I896UXJI2/I896UXJI2 instead. I'm betting I can't just edit it through there, can I?
Click to expand...
Click to collapse
Lol, unfortunately no, tried that myself for the product code and it just puts it back. One question, is your SIM installed when you connect it to Kies? Wondering because mine was and I'm wondering if maybe the fact that I have that 4th entry on HIDSWVER is related to that?

Riker2k said:
Lol, unfortunately no, tried that myself for the product code and it just puts it back. One question, is your SIM installed when you connect it to Kies? Wondering because mine was and I'm wondering if maybe the fact that I have that 4th entry on HIDSWVER is related to that?
Click to expand...
Click to collapse
Sim card is in. I'll try with it out.

TheEscapist said:
Sim card is in. I'll try with it out.
Click to expand...
Click to collapse
Ah, if SIM is in then that rules that out because I had mine in. It almost looks like a bad flash or something didn't get reverted quite right. Only difference is that I reflashed mine to stock with Heimdall and not Odin. A little more of a pain but worked great... You running Kies 1.53.something something?
Another question, when you fixed your nv_data.bin did you reset the ownership and permissions to the right ones in the /efs folder? Can't imagine that it should make a difference but...

Riker2k said:
Ah, if SIM is in then that rules that out because I had mine in. It almost looks like a bad flash or something didn't get reverted quite right. Only difference is that I reflashed mine to stock with Heimdall and not Odin. A little more of a pain but worked great... You running Kies 1.53.something something?
Another question, when you fixed your nv_data.bin did you reset the ownership and permissions to the right ones in the /efs folder? Can't imagine that it should make a difference but...
Click to expand...
Click to collapse
Maybe. I didn't use the .pit file when using Odin, maybe that's it? I'll reflash. And yeah, i have the right Kies.
And I would assume, I did the same method as the other guy in the main thread.
Edit: I don't seem to have a pit file.

TheEscapist said:
Maybe. I didn't use the .pit file when using Odin, maybe that's it? I'll reflash. And yeah, i have the right Kies.
And I would assume, I did the same method as the other guy in the main thread.
Edit: I don't seem to have a pit file.
Click to expand...
Click to collapse
No, don't use the pit and select repartition. The Rogers stock rom tar doesn't contain the dbdata partition and your phone will just end up stuck in recovery mode. You'll then have to flash the Odin 1-click to the AT&T firmware and then reflash to Rogers stock again. Learned that the hard way last night.
When you say the other guy in the main thread, which instructions? I'm only asking because there's a thread about fixing the nv_data.bin and the instructions are for the AT&T I897 version so it's not exactly the same for our I896. Very, very close but not quite. Obviously you've corrected the product code to match the Rogers one but wondering about the owner and group ownership settings + the permissions. The file should be owned by radio.radio and the permissions should be 700 (rwx --- ---) if you check with adb shell from a command line. Probably telling you stuff you already know, sorry if I'm going to far into the basics. Just want to try and cover that stuff to weed out potential issues. Took me almost 3 hours to fix mine last night because I had to search through many threads and places to finally piece it all together.

Riker2k said:
No, don't use the pit and select repartition. The Rogers stock rom tar doesn't contain the dbdata partition and your phone will just end up stuck in recovery mode. You'll then have to flash the Odin 1-click to the AT&T firmware and then reflash to Rogers stock again. Learned that the hard way last night.
When you say the other guy in the main thread, which instructions? I'm only asking because there's a thread about fixing the nv_data.bin and the instructions are for the AT&T I897 version so it's not exactly the same for our I896. Very, very close but not quite. Obviously you've corrected the product code to match the Rogers one but wondering about the owner and group ownership settings + the permissions. The file should be owned by radio.radio and the permissions should be 700 (rwx --- ---) if you check with adb shell from a command line. Probably telling you stuff you already know, sorry if I'm going to far into the basics. Just want to try and cover that stuff to weed out potential issues. Took me almost 3 hours to fix mine last night because I had to search through many threads and places to finally piece it all together.
Click to expand...
Click to collapse
It boots to recovery, but if you clear cache and user data, it boots fine after. Trust me, I've bricked enough times.
EDIT: Just realized you were talking about repartitioning, which I've never done, or had to. Whoops. >.>
And it suddenly works after a fresh flash, and master clear. Here goes.
Thanks for the time/help.

TheEscapist said:
It boots to recovery, but if you clear cache and user data, it boots fine after. Trust me, I've bricked enough times.
EDIT: Just realized you were talking about repartitioning, which I've never done, or had to. Whoops. >.>
And it suddenly works after a fresh flash, and master clear. Here goes.
Thanks for the time/help.
Click to expand...
Click to collapse
Yea, that repartitioning things cost me big time last night. I really, really didn't want to flash the odin 1 click to AT&T cause now I have that damn white AT&T worldphone logo which I hate but my phone is now running stock Rogers 2.2.
So far I'm kinda meh with it. It works, couple wonky things with haptic feedback and the wireless doesn't seem very stable, at least for me. Think I'm going back to di11igaf's 3.0.2 rom. Loved that one!
Enjoy your Cappy and glad to help.

Riker2k said:
Yea, that repartitioning things cost me big time last night. I really, really didn't want to flash the odin 1 click to AT&T cause now I have that damn white AT&T worldphone logo which I hate but my phone is now running stock Rogers 2.2.
So far I'm kinda meh with it. It works, couple wonky things with haptic feedback and the wireless doesn't seem very stable, at least for me. Think I'm going back to di11igaf's 3.0.2 rom. Loved that one!
Enjoy your Cappy and glad to help.
Click to expand...
Click to collapse
You can get rid of the AT&T logo, eh? There's a thread in the dev section about it.
I haven't had any issues, other than z4 not working. I'll super one click tomorrow. I have yet to find a rom for me to stick with though. CM 6.x is too laggy, CM 7 isn't ready yet, neither is sense, and everything else is just modded i9000 roms. No offense to the devs.
Sent from my SAMSUNG-SGH-I896 using XDA App

TheEscapist said:
You can get rid of the AT&T logo, eh? There's a thread in the dev section about it.
I haven't had any issues, other than z4 not working. I'll super one click tomorrow. I have yet to find a rom for me to stick with though. CM 6.x is too laggy, CM 7 isn't ready yet, neither is sense, and everything else is just modded i9000 roms. No offense to the devs.
Sent from my SAMSUNG-SGH-I896 using XDA App
Click to expand...
Click to collapse
Yea, going to look into the ATT logo replacement tomorrow. Too tired to take that on tonight.
As for ROMs, yea - tough call. I settled on Di11i's ROMs cause I liked the theme work and they are REALLY smooth and fast. I had a Galaxy S Vibrant before and one application I use - Touchdown for Exchange - was so damn slow on it I could barely stand to check my email. On the cappy with Di11i's ROM it's literally like butter. I coupled his ROM with the latest glitterballs kernel and BAM, wicked ROM with all the features I need, a nice theme and excellent battery life. Very happy with that.
I actually only upgraded to the stock Rogers 2.2 to do a /system pull for him to work with. Going back to it tomorrow, I think.
At least we have choices now, cause if it was left up to the carriers and manufacturer we'd suffer with whatever craptastic releases they come out with. To be fair, the Rogers ROM is really bloat free and actually pretty decent. With a change to Launcher Pro or Go Launcher I could probably deal with it for awhile.
Anyway, hope you find a rom you like or at least the Rogers 2.2 hangs on strong for ya!

I think I am in trouble

Hello Everyone,
I have a rogers captivate. I was trying to update to 2.3 android using Odin . I followed the whole process as stated. After rebooting, I got AT&T logo??? and the phone will not boot, go into recovery mode, or connect to my computer. Have I messed up my phone. Please advice.

how did you get an AT&T logo if it doesnt boot?
also what part of the process were you at? gingerbread shouldnt give the white ATT screen
it should give the "i9000" screen with gingerbread.
or were you flashing stock ATT first?
there is nothing wrong with having the wrong boot screen AND A FIX WAS RELEASED LAST NIGHT FOR GB
the fix for stock ATT has been out for a while. AND MY STOCK ROM FIXES IT TOO!
did you read the part about the button combos changing with gingerbread? or if you are on the ATT stock, use old button combos. Also you should have found my stock rom link before flashing, info there too!, its in my sig,
you have to give us more information to help you.

I beleive I was installing it to stock ATT first. That is when this happened. I was on Odin one click install. I remember the phone saying "do not disconnect the target". then all the installation was done from odin. This phone had 2.2 from samsung.Right now all that happens is that the phone starts and a flashing att logo on white background stays..
please let me know what other info is needed. i will post it all to the best possible

boot into download mode and flash ATT stock again. something messed up
are you using the "one click odin" or the other odin?
and what gingerbread are you trying after?

how do i do that. i have tried vol up+down+power combo. still the same flashing logo with no menus. i was using one click odin. and i was still on installing stock android. never got the chance to go to 2.3

If you can't get into download mode through the 3 button way you might need the jig. You got lucky since you're still able to boot up some have perma brick so try the jig and flash back to stock
Sent from my SAMSUNG-SGH-I897 using XDA App

HOLD VOL UP + DOWN
the plug in USB to PC.
keep buttons held until screen comes on!
i asked which gingerbread you were going to do AFTER

What is the build number on your phone, 4 numbers printed under the battery, mine is a 1010 for example, which mean oct. Of 2010 is when it was built. Some phones 1010 and after will not accept the one click odin rom and cause a bootloop like you are having, Try an odin package from TRusselo's sig instead.

my packages dont have the bootloaders. that might be whats screwed up with blinking att boot.
need download first before anything. i do have a GB bootloader package separately

something else:
try removing battery,
plug in USB to PC and Phone
Hold both Volume buttons
put battery back in.
should get you download mode

I really have noidea about what gingerbread i was after, i guess i wanted just the stock android without any custom software from samsung. I am total noob here as far as androids go.
the number on the battery say 2010.12.20 and the last forr nos under the battery at s/n are 11.02.
what is a jig. how do i use it. My phone cannot connect to the computer.
When I try to reset my device by any method, whether usb or power combos, it goes into either a. ATT logo flashing every few secs. or b. battery charging logo with nothing happeining.
Also my phone cannot be seen on my computer

gingerbread isnt for noobs
NOT THE DATE ON the battery
UNDER the battery ON THE PHONE
4 digit number
if you dont know what a jig or gingerbread or any of this stuff is,
you shouldnt have touched your friggin phone!

My apologies. the number is 1102. I understand I have screwed up. Any chance of having a working phone again.

GO GOOGLE A CAPTIVATE JIG AND BUY ONE
you wont be able to make one if you cant follow instructions.
that is your only hope. if not your phone is F'ed up perminantly.
your ONLY HOPE AFTER, is if your phone *somehow stops* turning on *forever*
and you send it back for warranty, and play dumb! ..... ..... ... .. .
PROGRAMMING a phone cant be learned it 5 minutes.
HELL you cant even read the friggin instructions (written for experienced users) in 5 minutes
this was an expensive lesson on researching and learning before doing

hitechchef said:
My apologies. the number is 1102. I understand I have screwed up. Any chance of having a working phone again.
Click to expand...
Click to collapse
Sorry for stepping in..
Yes there is. Might be a little complicated tho. You have some reading to do my friend.
Tru, I'll let you handle it but HiTechChef, you might've to go in for waranty and exchange it saying it did that after you tried to update through Kies. They'll check it and give you another one.

Thanks I will try this method

BWolf56 said:
Sorry for stepping in..
Yes there is. Might be a little complicated tho. You have some reading to do my friend.
Tru, I'll let you handle it but HiTechChef, you might've to go in for waranty and exchange it saying it did that after you tried to update through Kies. They'll check it and give you another one.
Click to expand...
Click to collapse
he's a rogers phone and it boots to ATT screen
it has to *stop* booting to get *warranty*

TRusselo said:
he's a rogers phone and it boots to ATT screen
it has to *stop* booting to get *warranty*
Click to expand...
Click to collapse
Oh right.. Wow..
Yep, go read about a JIG (it's pretty simple to use). You can either build it or buy one from mobiletechvideo or ebay.

TRusselo said:
he's a rogers phone and it boots to ATT screen
it has to *stop* booting to get *warranty*
Click to expand...
Click to collapse
Lol That kind of subtly is lost here... noone is picking up on your suggestion...

and thats how its going to stay,
ive said it before with almost the same words.
ive laid out all the tools....
correction of the original problem is necessary,
research is salvation,
resistance is futile.
there it is... i laughed... all is good again...

unknown imei,basband, and everything else.

aight so ive searched and searched for all kinda different methods. and done all of them. is it possible to have a permanent brick?
heres the story. i had been running cm10 for prolly 4 or 5 months. no problems. i wanted to check out liquid smooth rom. so i flashed it. no problems. had been running it for a month or so then one day at work when i went on break my network was gone. my apn's were deleted. came home inspected some more and my imei was unknown as well as baseband and many others were unknown. i took it back to stock many times using. gtg method. using heimdel. using odin. with different stock files. from different websites. including xda. i have tried just about everything to re do the phone. including going back to cm10. and other known working roms. ive *#*#4636#*#* and manually switched to gsm which wont change when i click it it still says unknown.
i dont belive it is a rom problem. i have been overclocked 1300mhz. what else is out there can i try. \
\
any help will be very appreciated

Have you by chance odined back to stock then reupgraded to JB? If not I can get you the necessary steps to do so...let me know
Sent from my SGH-I997 using xda premium

FauxAffliction said:
Have you by chance odined back to stock then reupgraded to JB? If not I can get you the necessary steps to do so...let me know
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
yea i went to stock and back to cm10. still nothing. buttt now im unable to do any kinda flashes. im on rooted 2.3.6 threw odin. and no matter what i flash it will say somthing on the lines of failed to find file signature or what ever that code is. i tried changing the cwm in different ways still wont get off the what is it 2.5.2 cwm blue. ive basicly gave up. it seems its to far bricked or whatever the case may be

im sorry i need to correct that. i have not been able to flash to any other roms. i didnt go to stock and then cm10, due the the signature deal on cwm. i was thinking of another time i had problems. so no i have no been able to go to jb after the imei has went unknown

Did you flash a custom kernel to get cwm after going back to stock?

andros11 said:
Did you flash a custom kernel to get cwm after going back to stock?
Click to expand...
Click to collapse
im in able to flash anything.....

really? no one can help me?

Are you trying to flash through Odin? Or through CWM?
Sent from my SGH-I997 using xda premium

psal217050 said:
Are you trying to flash through Odin? Or through CWM?
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
dont know how to flash a cwm threw odin. i tried loading a cwm threw rom manager and manually

kritz84 said:
dont know how to flash a cwm threw odin. i tried loading a cwm threw rom manager and manually
Click to expand...
Click to collapse
but im pretty sure the problem isnt with cwm im more interested in why and how to the imei isnt known and how to fix this problem if theres a cure

Download a heimdall one-click or odin back to stock pack. Open either one up and put your phone in download mode:
- turn off and have the usb cable connected to the pc.
- remove and reinsert battery
- hold both volume buttons and connect usb. Phone should now boot into download mode.
Run program and you will be good. Then look for entropy's dd kernel and flash it in download mode to get cwm.

andros11 said:
Download a heimdall one-click or odin back to stock pack. Open either one up and put your phone in download mode:
- turn off and have the usb cable connected to the pc.
- remove and reinsert battery
- hold both volume buttons and connect usb. Phone should now boot into download mode.
Run program and you will be good. Then look for entropy's dd kernel and flash it in download mode to get cwm.
Click to expand...
Click to collapse
i guess u didnt read my first post. ive already done that. ive done many things....
but anyway weirdest thing just happend. i have been using my phone via wifi. so its been on a while without a sim card inside of it.
\
i noticed i had signal bars. i looked at the imei and its was a number. it was a different iemi then what its supposed to be but there was a imei. baseband was still unknown but anyway i shut the phone done and inserted my sim card. btw its a straight talk sim. and restarted it now im back to unknown imei......

ok so im back on cm10. before i was on cm10 its was giving me the imei which wasnt my original imei. i guess cuz i flashed a efs.tar. but anyway i was able to make a phone call. now im flashed on cm10. and no imei no baseband nothin. i tried flashing the efs again with odin and still nothing. when i do the *#*#4636#*#* it still wont let me switch to gsm. and i cant add a apn.

kritz84 said:
ok so im back on cm10. before i was on cm10 its was giving me the imei which wasnt my original imei. i guess cuz i flashed a efs.tar. but anyway i was able to make a phone call. now im flashed on cm10. and no imei no baseband nothin. i tried flashing the efs again with odin and still nothing. when i do the *#*#4636#*#* it still wont let me switch to gsm. and i cant add a apn.
Click to expand...
Click to collapse
odin or heimdall back to stock.
follow andros11's guide on how to flash jb
he spent the time to write the guide; spend the same amount to time to read the guide

Seems IMEI was kidnapped about a month after Liquid
Ironically, I seem to have EXACTLY the same issue that this original poster has. I have been flashing my Infuse for a little over a year now and I Flashed Liquid, I'd say about 3 weeks ago, maybe end of November. Everything has been smooth sailing. About a 2 days ago I started noticing that my network would just drop - for no reason. But at first it came back. Ok, no problem, probably just a glitch. However yesterday morning it happened again and then I was without the use of data for most of the day until around 6pm. It came back but the bars were grey but I was able to make a phone call. Once I made another call it did not go through, I tried to hangup and it just hung there. there was nothing I could do to get it to hang up. Rebooting the phone resulted in no bars at all. Nothing, nada, ziltch. So last night I reflash it a couple times and notice that there was an update to Liquid (2.1 beta). cool. I wipe, flash 2.1b and it is beautiful. EXCEPT for the fact that I have no network. wifi works fine, but no carrier whatsoever. GRRRR. I decided to back every thing up (have done so several times in the past), stock back down to 2.3.6. Barebones and all it all looked great until I hung up the phone... Same thing. So I went all Rambo on the phone, wiped it down to the very last compound. AT&T wouldn't know the wiser if they took it from me. Master Reset, wiped files, data, I think I took an IC out with all of the wiping I did... Result? No IMEI, circle with the slash. Upset, disappointed and dejected I slumped back to XDA (after I went on Craigslist feeling my phone was broke) to see if I missed anything. That was where I found some links about missing IMEI. To make a long story short, I DO have an old copy of EFS thanks to QKSTER, but I have no idea how to restore. I swear I have been on this since 6:30am and just now am I finding these threads. Must have gone through about 50 others... Sigh. BTW, along the way of my flashing experience today, my network came back temporarily, but I have not relied on it because I knew it would leave me. Just don't know how to use Heimdall to restore. To make a long story short, using Windows, could someone please help me with how to restore my EFS to see if this would solve my dilemma?
808

Dnice808 said:
To make a long story short, I DO have an old copy of EFS thanks to QKSTER, but I have no idea how to restore. I swear I have been on this since 6:30am and just now am I finding these threads. Must have gone through about 50 others... Sigh. BTW, along the way of my flashing experience today, my network came back temporarily, but I have not relied on it because I knew it would leave me. Just don't know how to use Heimdall to restore. To make a long story short, using Windows, could someone please help me with how to restore my EFS to see if this would solve my dilemma?
808
Click to expand...
Click to collapse
What is the format of your EFS folder?
*.zip
*.tar
just a folder?
If you have lost the signal while on JB, see if you can factory reset the phone.
/settings/privacy -reset
Then put it into download mode.
Use the heimdall 1 click uclb3 and flash it once, then without closing heimdall, check the bootloader box and flash it again.
After this, check your imei and band. If it works, no further back up is needed.
If you're still missing the imei, you can flash one of the gb kernel in the second post to get cwm.
Then use the root pack in post #2,
http://forum.xda-developers.com/showthread.php?t=1629079 to install root and su.
install a root tool like root explorer (remember to toggle the r/o r/w) or adb and copy the /efs into the phone's root efs folder,
reboot
check the baseband.
you can also check this thread
http://forum.xda-developers.com/showthread.php?t=1895500

qkster said:
What is the format of your EFS folder?
*.zip
*.tar
just a folder?
So it is in the .tar format that your script backed it up in. Finding another link on the we (which he also linked back to XDA, http://forum.xda-developers.com/showthread.php?t=1264021 I was able to take my backup (that I used with your script) and follow his steps -mostly- (my/your backup had a 'root' folder that had the nv_data.bin file in the afs/settings folder while the instructions did not mention that. I followed the backup location settings (which in turn was also the same as the default that I had backed up)) and replace the EFS folder. It still did not restore it in any flash image just like that. Still had the the circle w/slash. However while I was still searching and typing out that loooong last passage I wrote, my phone network came back for a little while. I know this because I began receiving a bunch of texts. I was able to make a phone call. But it still happened again when I made another, it did not go through and when I hung up, it just stayed there looking at me with its grey, blank look. Even killing the phone app did not work. I rebooted back to the same drama.
If you have lost the signal while on JB, see if you can factory reset the phone.
/settings/privacy -reset
I actually was on 2.3.6 using your posts, first the basic rooted flash having to then using the Entropy kernel and then I did the lazy flash that was already rooted and just having to add the vold file to /system/etc/blah/blah. I do want to add that I DID have wifi active at this time and it may not be associated, but the first poster did mention he felt it may have had something to do with it. With wifi on, after awhile of me NOT looking at the phohe (actually doing so made me want to HULK SMASH), the network came on and my texts came in. I was able to look in settings and see ATT, and my IMEI. I was almost finished with my passage to you so I decided to update to Liquid 2.1 beta, but moving up to JB, then to LiquidSmooth. Of course doing so I got the circle w/slash, but wifi started restoring my apps.
Earlier I mentioned that I did a whole rubba dub dub, meaning I did do the /settings/privacy -reset thingy, wiping the phones carcass. I will do it again (at this point nothing to lose), following everything you ask to a 'T'.
808
Click to expand...
Click to collapse

qkster said:
What is the format of your EFS folder?
*.zip
*.tar
just a folder?
If you have lost the signal while on JB, see if you can factory reset the phone.
/settings/privacy -reset
Then put it into download mode.
Done.
Use the heimdall 1 click uclb3 and flash it once, then without closing heimdall, check the bootloader box and flash it again.
Done
After this, check your imei and band. If it works, no further back up is needed.
Sigh, did not do a darn thing. Circle w/slash.
If you're still missing the imei, you can flash one of the gb kernel in the second post to get cwm.
Done.
Then use the root pack in post #2,
http://forum.xda-developers.com/showthread.php?t=1629079 to install root and su.
install a root tool like root explorer (remember to toggle the r/o r/w) or adb and copy the /efs into the phone's root efs folder,
reboot
check the baseband.
Went in Root Explorer, did the toggle, deleted the contents of efs then copied the contents of my backup into there. Rebooted. Nada.
you can also check this thread
http://forum.xda-developers.com/showthread.php?t=1895500
I then was going to try the other link using Odin, but I cannot get Odin to see my phone. I read some thread talking about if I use Heimdall I will have problems using Odin because they use the same ports? How frustrating. The weird part is now that I have the flashed, rooted 2.3.6 image and using wifi, at some point tonight my network may come back on. Or it may not.
808
Click to expand...
Click to collapse
Bugged out, huh?!!???

Dnice808 said:
Bugged out, huh?!!???
Click to expand...
Click to collapse
I wasn't sure if there was a question there.
From my experience, flashing to JB (MTD partition) from GB without going through ICS may result in lost of imei.
Sometimes, it just happens. I had very limited experience with JB.
The few methods that I've tried worked for me. Just simply flashing back to stock with a re-partition ( (Heimdall -1-click for me) usually brings back the /efs and imei without doing anything extra.
If you haven't, and if you can, I would try the heimdall-1-click a few times.
If you want to use Odin, you may need to reinstall samsung drivers and use a different usb port on the PC than the one you used for heimdall.
You may also want to check the signal of the phone at your location. you may be getting poor signal and it has nothing to do with the phone's OS

qkster said:
I wasn't sure if there was a question there.
Click to expand...
Click to collapse
Me stating that it is bugged out, was me just confirming that it is Weird!
qkster said:
From my experience, flashing to JB (MTD partition) from GB without going through ICS may result in lost of imei.
Sometimes, it just happens. I had very limited experience with JB.
Click to expand...
Click to collapse
Ok just to explain myself better. I have been saying that I was going from GB to JB when in fact I meant to say that I was going from GB to ICS. Sorry for that. Also, the reason my responses have looked wacky is that I was trying to select the multi quote button and getting no response. Hopefully this response is a little more organized.
qkster said:
The few methods that I've tried worked for me. Just simply flashing back to stock with a re-partition ( (Heimdall -1-click for me) usually brings back the /efs and imei without doing anything extra.
If you haven't, and if you can, I would try the heimdall-1-click a few times.
Click to expand...
Click to collapse
See that is what confuses me too. I have flashed back and forth several times at this point, and sometimes the /efs and imei do come back, but now they have never stayed. It is the only reason why I have tried to pretty much rule out a hardware issue. Even when I flash and there is no imei, there is the same /efs folder. And when I wipe the whole thing sparkling clean, even the newly formed /efs folder has the correct imei but it is just not being recognized on the phone.
qkster said:
If you want to use Odin, you may need to reinstall samsung drivers and use a different usb port on the PC than the one you used for heimdall.
Click to expand...
Click to collapse
Of course what I did was accidentally leave my phone home preventing me from testing it out with Odin on another machine. Its all good though.
qkster said:
You may also want to check the signal of the phone at your location. you may be getting poor signal and it has nothing to do with the phone's OS
Click to expand...
Click to collapse
I have an AT&T prepaid phone and the sim from the Infuse works in it flawlessly...
808

[Q] Phone won't boot after flash

Hi there.
I'm on the CarbonRom 17 Nightly.. I think.
I flashed this before bed last night, and the associated Gapps according to GooManager was "AOKP-Cl3Kener-Build-1.1-Hercules.zip" ( http://forum.xda-developers.com/showthread.php?t=2151010 ) I thought it was some kinda' fancy Aroma installer for Gapps, so I just downloaded and flashed. I woke up to realize that I couldn't boot my phone after installing the nightly 17 & this file.
My phone will not boot. It will not go in to recovery, it will not boot in to download mode, it isn't detected by Odin, but at one point it was detected by windows by some absolutely weird name with USB in the middle of it.
The only options I see are: a) JTAG b) To the Verizon store I go!
Any other thoughts / ideas? Will Verizon be able to see that I have a 3rd party ROM on the phone? My method of flashing did not trip the counter, but there's still a different radio / rom / recovery.
I'm going to leave the battery, and sd card out of it overnight, see if that will do anything.
Thanks for your input.

I'm in the same boat as you, regrettably. I downloaded and installed Carbon no problem, had it running but all of my GApps kept force closing. So I had the bright idea to try the GApps that were listed on GooManager. As soon as the flash finished of the GApps, my phone was done. Black screen, no response, doesn't matter what key combo I try. Only thing I can do that gets anything to happen is plugging it in with no battery. When I do this, as you've stated the red LED comes on. It still won't do anything. Can anyone offer up any suggestions? I'm thinking a warranty exchange is probably our best option, but what do we tell the Verizon reps?

xation said:
The only options I see are: a) JTAG
Click to expand...
Click to collapse
Pay for jtag fix. Only download roms meant for d2vzw aka Verizon GSIII.
Seraph552 said:
I'm in the same boat as you, regrettably. I downloaded and installed Carbon no problem, had it running but all of my GApps kept force closing. So I had the bright idea to try the GApps that were listed on GooManager. As soon as the flash finished of the GApps, my phone was done. Black screen, no response, doesn't matter what key combo I try. Only thing I can do that gets anything to happen is plugging it in with no battery. When I do this, as you've stated the red LED comes on. It still won't do anything. Can anyone offer up any suggestions? I'm thinking a warranty exchange is probably our best option, but what do we tell the Verizon reps?
Click to expand...
Click to collapse
What Gapps zip did you flash? Btw, nobody here will help you scheme Verizon.
Sent from my SCH-I535 using xda app-developers app
Sent from my SCH-I535 using xda app-developers app

same boat, i went from stock rooted 4.1.2 and tried to flash root66_VZW_I535VRBMA2_nowipe.7z from http://forum.xda-developers.com/showthread.php?t=1984436 in mobile odin pro. after i clicked all the confirmations and thought it was rebooting, it stayed off, then nothing. same issues as yours, no key combinations work. only red light if plugged in without a battery (i treid 2 diff batteries)

dmxoneIuv said:
same boat, i went from stock rooted 4.1.2 and tried to flash root66_VZW_I535VRBMA2_nowipe.7z from http://forum.xda-developers.com/showthread.php?t=1984436 in mobile odin pro. after i clicked all the confirmations and thought it was rebooting, it stayed off, then nothing. same issues as yours, no key combinations work. only red light if plugged in without a battery (i treid 2 diff batteries)
Click to expand...
Click to collapse
Did you unzip the file before flashing in Mobile Odin?
Sent from my SCH-I535 using xda app-developers app

SlimSnoopOS said:
Did you unzip the file before flashing in Mobile Odin?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
yeah, i took the root66_VZW_I535VRBMA2_nowipe.tar.md5 file and it pulled it into mobile odin pro. it checked the md5 completely before turning off forever. about to go to verizon see what my options are. i bought the phone cash, but can't find the receipt but its less than a year since i got it so it should still be covered hopefully. otherwise last resort, send it to that guy to jtag

dmxoneIuv said:
yeah, i took the root66_VZW_I535VRBMA2_nowipe.tar.md5 file and it pulled it into mobile odin pro. it checked the md5 completely before turning off forever. about to go to verizon see what my options are. i bought the phone cash, but can't find the receipt but its less than a year since i got it so it should still be covered hopefully. otherwise last resort, send it to that guy to jtag
Click to expand...
Click to collapse
did you by chance have an update in rom manager? there seems to be a problem with the update. odin back to rt66 flash older version of rom manager.
i see you used the no wipe after looking back. you have to wipe to get it to boot.

Okay, I called Verizon this morning, and they're overnighting a new phone to me. I have to return the paperweight.
Will they be able to revive my internal storage? I have evidence of rooting on there, and all my data. Is there any way I can destroy this data before I send it off to them?
Now, when I connect my device, I get a HSUSB device discovered, after googling around I found a driver for it, and installed. Now, in device manager it says Qualcomm HS-USB QDloader 9008 (COM8). So basically that's saying it's powered on, right? Odin still doesn't detect a thing, neither does fastboot or adb devices.
Do you think something like DBAN would work?

xation said:
Okay, I called Verizon this morning, and they're overnighting a new phone to me. I have to return the paperweight.
Will they be able to revive my internal storage? I have evidence of rooting on there, and all my data. Is there any way I can destroy this data before I send it off to them?
Now, when I connect my device, I get a HSUSB device discovered, after googling around I found a driver for it, and installed. Now, in device manager it says Qualcomm HS-USB QDloader 9008 (COM8). So basically that's saying it's powered on, right? Odin still doesn't detect a thing, neither does fastboot or adb devices.
Do you think something like DBAN would work?
Click to expand...
Click to collapse
Should have paid for the JTAG or bought a replacement used phone from swappa or some similar place, but JTAG is the cheaper option. It's a simple concept that we all assume a certain amount of risk when rooting and modding our phones - you break it, you buy it. Don't submit a phone for a warranty claim for something you did. If you don't send the paperweight back, or if they can tell you've modded the phone, they will charge you full retail for the replacement. Like I said, and like SlimSnoopOS said above, JTAG was your best option.

xation said:
Hi there.
I'm on the CarbonRom 17 Nightly.. I think.
I flashed this before bed last night, and the associated Gapps according to GooManager was "AOKP-Cl3Kener-Build-1.1-Hercules.zip" ( http://forum.xda-developers.com/showthread.php?t=2151010 ) I thought it was some kinda' fancy Aroma installer for Gapps, so I just downloaded and flashed. I woke up to realize that I couldn't boot my phone after installing the nightly 17 & this file.
My phone will not boot. It will not go in to recovery, it will not boot in to download mode, it isn't detected by Odin, but at one point it was detected by windows by some absolutely weird name with USB in the middle of it.
The only options I see are: a) JTAG b) To the Verizon store I go!
Any other thoughts / ideas? Will Verizon be able to see that I have a 3rd party ROM on the phone? My method of flashing did not trip the counter, but there's still a different radio / rom / recovery.
I'm going to leave the battery, and sd card out of it overnight, see if that will do anything.
Thanks for your input.
Click to expand...
Click to collapse
I did the same thing. Called verizon and they sent me a new phone I don't know yet if i'll have to pay for a new phone yet. I thought the same thing about a aroma installer dont know why this would be in the link with carbon rom in goo manager . Good Luck.

Stock Verizon OTA 4.1.2
Anyone know where I can get the stock Verizon OTA 4.1.2 (VRBMA2)?

Try using this thread (select same option on flashing bootchains). I just followed and used successfully.
http://forum.xda-developers.com/showthread.php?p=30386309
From GalS3xy-i535 via Tapatalk²

xation said:
Okay, I called Verizon this morning, and they're overnighting a new phone to me. I have to return the paperweight.
Will they be able to revive my internal storage? I have evidence of rooting on there, and all my data. Is there any way I can destroy this data before I send it off to them?
Now, when I connect my device, I get a HSUSB device discovered, after googling around I found a driver for it, and installed. Now, in device manager it says Qualcomm HS-USB QDloader 9008 (COM8). So basically that's saying it's powered on, right? Odin still doesn't detect a thing, neither does fastboot or adb devices.
Do you think something like DBAN would work?
Click to expand...
Click to collapse
if you have the full protections,,it covers water stolen just about anything..i did the same thing with my nexus last year...all i did was reported stolen but i had to pay 100 bucks...but got a bran new one..then i was able to fix the broken nexus now i have 2...so maybe just put it on water so it can have water damage..but make sure you have the total protection

[Q] Veizon S3 Insurance claim, pre-rooted? OTA Update? Not sure what's been done

Hello all! I need to know what has been done to my insurance replacement phone, and how I can safely update my phone to VRBMV1.
The short version...
I hard bricked my Verizon Galaxy S3 phone by installing a custom ROM wrong, I got an insurance replacement that came pre-rooted, has Clockworkmod already installed and I believe has an unlocked bootloader. Clockworkmod stopped the OTA Update, but I want the update installed. I need to know what to do.
The long, more informative version...
So, I wanted to increase the volume of my Bluetooth headset and after trying different apps and nothing working, I found some modded system files that had a great review that increase all of the phones volumes. The instructions said the phone had to be rooted. Well I rooted the phone and the modded files didn't work. So reading the reviews of the mod, people were saying it worked great with the OMEGA AOPK ROM. So I rooted my Verizon Galaxy S3 i535 phone and installed a the custom rom and hard bricked my phone. I didn't pay enough attention and installed a rom for an i9000 not a i535, at least I think that's what happened... Anyways, I got a new phone through my insurance and the screen wouldn't rotate, so they sent me a 2nd replacement. I got that one in the mail today and it appears to already be rooted, and possibly have an unlocked bootloader, but i'm not sure how to do the VRBMV1 OTA update now.
The first thing the phone did once I activated it was do an OTA update from Verizon, so I let it. Clockworkmod popped up and said it couldn't verify the publisher for the files it was trying to install and asked if I wanted to continue. I clicked NO.
So, since I recently found out what Clockworkmod was and know it's not stock on the S3, I knew someone had done something to the phone. So i'm trying to figure out what exactly has been done, and if it's safe for me to do the OTA update or not.
After searching this forum I found out I can use an app to see if the phone is rooted or not, so I checked it and the app say "root access granted". I also see an app already installed on the phone called SuperSU. So I now know the phone is rooted.
After searching more I found one way to possibly tell if the bootloader is unlocked is to restart the phone, if the Samsung logo goes away within 1 second you probably have an unlocked bootloader. The logo goes away instantly on my phone, so i'm guessing the bootloader is unlocked?
The rest of the phone appears to be the same visually and settings wise as my old S3, so I think it's the stock ROM. "About phone" says Android Version 4.1.2 - Baseband Version i535VRBMB1 - Kernel Version 3.0.13-861013 [email protected] #1 SMP PREEMPT Thu Feb 14 15:16:58 KST 2013 - Build Number JZ054K.I535VRBMB1. Putting the phone Download Mode says everything is "Official", whereas it said "Custom" just before I bricked my old phone.
Sorry this is getting so long. I'll get to the questions now...
From what I've read on the forum, it appears to not be a good idea to do the OTA updates. Without knowing what else has been done to the phone, how can I "safely" get VRBMV1 installed? It appears to fix some problems with battery life and 4G signal, so it would be nice to have.
I for sure don't want to brick another phone as my insurance most likely will not like me anymore. So i'm not sure i'm comfortable trying anymore custom ROMs that already have the update in them. Is there a way to take the phone back to factory with having any of the backups that may or may not have been done before the phone was modded?
Thank you very much!

Odin flash VRBMB1 tar.

SlimSnoopOS said:
Odin flash VRBMB1 tar.
Click to expand...
Click to collapse
And you will be on the very latest OEM OTA version , no need to worry about updates. QED

SlimSnoopOS said:
Odin flash VRBMB1 tar.
Click to expand...
Click to collapse
That worked PERFECT! Thank you very much!!!! :good:

You may have gotten one of my 5 returns...
However i am fairly certian I returned them with the stock recovery, and rom unless I missed that step on one or two... I was having screen issues when they sent me refurbs
Sent from my SCH-I535 using xda premium

Colomonster said:
You may have gotten one of my 5 returns...
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Well everything seems to work perfectly on it, so thank you for not breaking it! :fingers-crossed: