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!
Related
So it seems like the first time stuck so it restarted, now it's stuck at partition. I selected the PIT and the PDA stock file, but it's just sitting there ... I'm on the phone + PC logo.
Am I totally screwed? What to do?
What pit did you select?
gtg465x said:
What pit did you select?
Click to expand...
Click to collapse
The one from the xda thread additional infuse files
bella92108 said:
The one from the xda thread additional infuse files
Click to expand...
Click to collapse
Not seeing that thread. Please provide a link.
i think he means from lost1
@op i think the 512pit from the sgsphones will work
gtg465x said:
Not seeing that thread. Please provide a link.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1084837
in OP additional files
It gets stuck at "Setup Connection.."
im gonna go out on a limb here and say use h8rifts stock rom with the 512pit found in the i9000 and captivate sections. h8's rom is missing the param.ifs though, not sure if you will need that.
Dani897 said:
im gonna go out on a limb here and say use h8rifts stock rom with the 512pit found in the i9000 and captivate sections. h8's rom is missing the param.ifs though, not sure if you will need that.
Click to expand...
Click to collapse
So I've been able to use the 512 pit and get it to get back to the "Downloading... Do not turn off Target". ... but then when I go back in and try to flash the stock Rooted ROM I get the "Initialization..." then it just stops there... ideas?
not sure. let it sit for a while. h8rift or somebody said it took his like 20 minutes(if i remember right) which seems weird. also you should be logged in windows as admin and the usb plugged into a port that connects to the mother board not a expansion card or hub.
honestly though i have only used heimdall on the infuse. and never repartitioned because heimdall requires bootloaders for repartition. im not sure i trust lost1's bootloaders and if there is an issue with them there are no others to use.
it might be a driver issue. maybe samsung needs some updated drivers for the infuse.
also are you sure you have your .net framework up to date on windows? i cant think of everything odin depends on but i think having .netframework4 helps with some things on the phone, cant remember ifodin depends on it though
Dani897 said:
not sure. let it sit for a while. h8rift or somebody said it took his like 20 minutes(if i remember right) which seems weird. also you should be logged in windows as admin and the usb plugged into a port that connects to the mother board not a expansion card or hub.
honestly though i have only used heimdall on the infuse. and never repartitioned because heimdall requires bootloaders for repartition. im not sure i trust lost1's bootloaders and if there is an issue with them there are no others to use.
it might be a driver issue. maybe samsung needs some updated drivers for the infuse.
also are you sure you have your .net framework up to date on windows? i cant think of everything odin depends on but i think having .netframework4 helps with some things on the phone, cant remember ifodin depends on it though
Click to expand...
Click to collapse
So I've been able to get it to say FACTORYFS now. I decided to just try the NON-rooted stock file to see if maybe it'll work. Right now it says Firmware update Start.... and there's a tiny green line flashing, but it's just been sitting there for 5 mins alrady.... just let it sit?
bella92108 said:
So I've been able to get it to say FACTORYFS now. I decided to just try the NON-rooted stock file to see if maybe it'll work. Right now it says Firmware update Start.... and there's a tiny green line flashing, but it's just been sitting there for 5 mins alrady.... just let it sit?
Click to expand...
Click to collapse
cant hurt to leave it there a little longer. the captivate never took that long but we also had a true factory flash oneclick odin that they use to reset refurbished phones. no such luck on the infuse unless someone wants to see if designgears has some sort of connection at samsung who can get it like he somehow was able to get it for the captivate. the significance of odin oneclick is that is has all the files. param.ifs, boot.bin, sbl.bin, and all the first boot scripts. our stock roms have come from rom dumps. the captivate stock roms came from samsung.
i would leave it for a good 20 minutes. then try something else. you may need to try files from lost1's stock rom you can use 7zip to manipulate the .tar files and magic ISO to manipulate the .rfs files within the .tar files, but atleast one ofthe files from lost1 doesnt work. if i had 2 infuses id experiment with you to be able to post what works and what doesnt. with only one phone im hesitant to try anything that is not tested
Dani897 said:
cant hurt to leave it there a little longer. the captivate never took that long but we also had a true factory flash oneclick odin that they use to reset refurbished phones. no such luck on the infuse unless someone wants to see if designgears has some sort of connection at samsung who can get it like he somehow was able to get it for the captivate. the significance of odin oneclick is that is has all the files. param.ifs, boot.bin, sbl.bin, and all the first boot scripts. our stock roms have come from rom dumps. the captivate stock roms came from samsung.
i would leave it for a good 20 minutes. then try something else. you may need to try files from lost1's stock rom you can use 7zip to manipulate the .tar files and magic ISO to manipulate the .rfs files within the .tar files, but atleast one ofthe files from lost1 doesnt work. if i had 2 infuses id experiment with you to be able to post what works and what doesnt. with only one phone im hesitant to try anything that is not tested
Click to expand...
Click to collapse
I'm using H8rift's restore... and both of the two (rooted and non) have the same issue for me.
It just sits... I've used the rooted and non-rooted.... ugh.
It goes to firmware update start then has a little greenness in the progress bar on the computer, and a little blueness in the progress bar on the phone, but I let it sit for 30 minutes and it never progresses any further, so there's something going on.
I've tried other usb ports, updated drivers, every method of compatibility and admin mode, even reinstalled windows basic version, haha.... ugh, this is hopeless.
I think it's time to chalk this up to a very very expensive lesson learned and go out and buy a replacement... not happy about that :-(
bella92108 said:
I'm using H8rift's restore... and both of the two (rooted and non) have the same issue for me.
It just sits... I've used the rooted and non-rooted.... ugh.
It goes to firmware update start then has a little greenness in the progress bar on the computer, and a little blueness in the progress bar on the phone, but I let it sit for 30 minutes and it never progresses any further, so there's something going on.
I've tried other usb ports, updated drivers, every method of compatibility and admin mode, even reinstalled windows basic version, haha.... ugh, this is hopeless.
I think it's time to chalk this up to a very very expensive lesson learned and go out and buy a replacement... not happy about that :-(
Click to expand...
Click to collapse
Why did you use a .pit? Did I not state in the OP of the Odin thread not to use one? take out the .pit, uncheck re-partition and flash the package as it was originally attended. you will NEVER need to re-partition your phone until we actually start CHANGING your partitions sizes (i.e. CM7, MIUI, possibly Samsung's gingerbread, etc.)
h8rift said:
Why did you use a .pit? Did I not state in the OP of the Odin thread not to use one? take out the .pit, uncheck re-partition and flash the package as it was originally attended. you will NEVER need to re-partition your phone until we actually start CHANGING your partitions sizes (i.e. CM7, MIUI, possibly Samsung's gingerbread, etc.)
Click to expand...
Click to collapse
He doesn't follow directions well.This much we know. He royally screwed up flashing my ROM as well and then proceeded to blame his problems on my ROM being crappy.
gtg465x said:
He doesn't follow directions well.This much we know. He royally screwed up flashing my ROM as well and then proceeded to blame his problems on my ROM being crappy.
Click to expand...
Click to collapse
Sorry to hear that.
Sent from my SAMSUNG-SGH-I997 using Tapatalk
I am putting up another Odin package right now for him to try if h8rift's doesn't get him going since he tried to repartition.
gtg465x said:
I am putting up another Odin package right now for him to try if h8rift's doesn't get him going since he tried to repartition.
Click to expand...
Click to collapse
...... She ...
Sent from my SAMSUNG-SGH-I997 using XDA App
Gtg the man
hoofadoo said:
...... She ...
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
see how nice he was to help you! ive listened to these guys from day one never one problem and if there is they help you untill its fixed. they were once like us too bu now deserve respect in the developing\helping noob world lol
Poor bella, she seems to be having a tough time lately...
Sent from my Samsung Infuse 4G
For people that flashed the O2X baseband to the G2X and haven't figured out a way to flash the correct baseband yet, I have something for you to try. Mind you, I have not tried this myself and have no idea if it will work. But it is certainly worth a try.
It appears that the LG Update Utility has a recover feature that should bypass all checks and just flash the latest firmware to your device. If this works it will flash GB stock with the correct baseband.
Backup your data first. This method, if it works, will do a complete wipe of everything (not sure about internal user memory but better safe than sorry).
Have your device turned on and running. If Android won't boot then go into software update screen). Plug your USB cable into your computer but don't plug it into the phone yet. Of course, make sure you have all the LG USB driver package installed first.
1. Run the LG Update Utility
(disconnect all usb devices, turn off antivirus and firewall)
2. Under "Customer Support" select "Recovery Phone"
3. Select your model number (i.e., LGP999DW, LP999DWP, etc.)
4. Enter your IMEI number and press check
5. Enter your serial number (don't press check yet)
(IMEI and serial number are found on label under battery or on the box)
6. Press check and the software update flasher will launch. Plug in your phone.
7. The program should then download the firmware and flash it.
8. At any time during the update if you get a connection error don't do the battery pull as instructed. Just unplug the USB cable from your computer, wait for beep, plug cable back into the computer, wait for beep and click "Restart."
Hopefully this will perform a clean install and flash everything including your baseband. Please report back here on success or failure.
Just trying to find a way for people to repair baseband issues. I hope this works for you guys and gals stuck on wrong and corrupted basebands.
I've tried this before and it did not work. Just ended up sending back to LG and got a replacement. Such a headache the unknown baseband was!!!!
Sent from my LG-P999 using xda premium
Does the baseband even do anything. Both the original and "updated" version both share the same exact version numbers minus a date change.
I'm just curious because I'm still running on the original baseband. I don't think it ever fixed anything.
Also the Drivers and LG Updater here are not working (can't download). Any mirrors?
It fixed GPS and wifi issues. The baseband chip controls both Edge and 3/4G radios, wifi, bluetooth and even GPS reception. There's a lot of stuff packed into the new baseband chips.
Which is the lastest baseband version ?,
Mine is m6600a-scauntz-2.0.9720t 1 jul 15 2011
That's wrong baseband?
sukhochir said:
Which is the lastest baseband version ?,
Mine is m6600a-scauntz-2.0.9720t 1 jul 15 2011
That's wrong baseband?
Click to expand...
Click to collapse
That's the newest. The original baseband was dated March something.
d12unk13astard said:
I've tried this before and it did not work. Just ended up sending back to LG and got a replacement. Such a headache the unknown baseband was!!!!
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Ditto - I tried that route early on and it failed. Kept on getting "fatal error" notice when it quit.
jboxer said:
It fixed GPS and wifi issues. The baseband chip controls both Edge and 3/4G radios, wifi, bluetooth and even GPS reception. There's a lot of stuff packed into the new baseband chips.
Click to expand...
Click to collapse
Interesting. Didn't know this. I'm still running the march baseband. I think I'll update now after reading this.
player911 said:
Also the Drivers and LG Updater here are not working (can't download). Any mirrors?
Click to expand...
Click to collapse
Same question. Those links don't seem to be working here either.
mirrors:
LG updater tool
G2x Drivers
Good Luck
Something is not right. After doing this step ""4. Enter your IMEI number and press check"" it goes to the first screen below.
I then put in the information and plug in my phone before hitting next which then gets me the second screen.
EDIT: I tried starting the process over with the phone plugged in from Step 1 and it seems to be updating now right after clicking check in step 4. Step 5 seems unnecessary?.... I'll let you know if it updates correctly.
kuhla said:
Something is not right. After doing this step ""4. Enter your IMEI number and press check"" it goes to the first screen below.
I then put in the information and plug in my phone before hitting next which then gets me the second screen.
EDIT: I tried starting the process over with the phone plugged in from Step 1 and it seems to be updating now right after clicking check in step 4. Step 5 seems unnecessary?.... I'll let you know if it updates correctly.
Click to expand...
Click to collapse
Ok. Update seems to have worked. I have the new baseband: JUL 15 2011 10:00:00
Things I did differently than OP post:
Phone was plugged in and turned on before step 1.
Skipped step 5 and step 6 because as soon as I hit "Check" at the end of step 4 the program closed/minimized and the updater opened automatically and started downloading.
I walked away from my computer and ate dinner, cleaned up, came back maybe an hour later and the phone was already booted up with a fresh copy of ginger and the new baseband so I guess it finished by itself without my input.
Just wondering...
Were you running windows 7 or XP?
Sent from my LG-P999 using xda premium
d12unk13astard said:
Were you running windows 7 or XP?
Click to expand...
Click to collapse
Windows 7
10char
kuhla said:
Ok. Update seems to have worked. I have the new baseband: JUL 15 2011 10:00:00
Things I did differently than OP post:
Phone was plugged in and turned on before step 1.
Skipped step 5 and step 6 because as soon as I hit "Check" at the end of step 4 the program closed/minimized and the updater opened automatically and started downloading.
I walked away from my computer and ate dinner, cleaned up, came back maybe an hour later and the phone was already booted up with a fresh copy of ginger and the new baseband so I guess it finished by itself without my input.
Click to expand...
Click to collapse
My advice above was based on speculation as I stated. I am glad someone got it to work and fixed their phone. Now others know the correct steps to take to possibly revive their baseband.
I've fixed this problem before, made a thread about it.
Mine's being stupid. lmao. I'm JUST NOW upgrading the baseband. Figured why not.... well I had to download a 300mb+ nandroid backup, restore it back to 2.2 so the updater would recognize it... then it went to assume to download another 300mb+ file, now it just sits at 5%... been there a while too.
Absolutely the most horrible updater I've every seen.
I closed everything out and now its telling me my phone is already up to date.... except it only boots to the Software Updater. lmao. So now I'm in CWM Recovery and flashing a Rom to see if anything changed.
Probably screwed up my baseband and/or made no change.... Nope. Just stuck at the S/W Upgrade screen. Awesome LG! My phone works awesome now.
[Update]
****. I'm at a loss. The stupid software keeps telling me that I already have the latest version, but I can't get pas the stupid S/W Upgrade screen. I reflashed Stock Kernel and CWM, and various roms.... it's like in some weird mode. I've pulled the battery and yada yada but no dice. It just likes that screen.
Well that was a fun way to waste a nice little Tuesday afternoon. Any ideas?
player911 said:
Figured why not.... well I had to download a 300mb+ nandroid backup, restore it back to 2.2 so the updater would recognize it...
Click to expand...
Click to collapse
The updater recognized my phone and I was running a 2.3.3 OTA based custom ROM at the time, not stock. I'm not sure if it makes a difference but I just thought I'd mention it.
I talked to Tmobile and LG repair. They said once it gets to that point there is no way out other then sending it in for repair to reflash the whole unit.
I've tried NVFlashing it to both stock and several CWM recoveries but nothing works. Restoring Nandroid backups, flashing roms. I haven't tried flashing a custom kernel but I don't know if that will make any difference.
Now Tmobile is wanting to charge me $20 for replacing it or LG taking 3 weeks for repair.
Pisser is that I got mad at went to retentions, lol, and the guy was like, "Ok I put that request in". Wtf. So now I'm due to cancel my service Oct. 28th
What a crock. All the while she said, "we're the cheapest of all the national carriers for exchanges" but my gf's HTC Aria on AT&T was replaced without any discussion of "warranty exchange fees".
AT&T sucks at my house too. Maybe I'll just upgrade my Verizon business phone and get the Droid Prime or whatever (I hate Verizon though).
player911 said:
I talked to Tmobile and LG repair. They said once it gets to that point there is no way out other then sending it in for repair to reflash the whole unit.
I've tried NVFlashing it to both stock and several CWM recoveries but nothing works. Restoring Nandroid backups, flashing roms. I haven't tried flashing a custom kernel but I don't know if that will make any difference.
Now Tmobile is wanting to charge me $20 for replacing it or LG taking 3 weeks for repair.
Pisser is that I got mad at went to retentions, lol, and the guy was like, "Ok I put that request in". Wtf. So now I'm due to cancel my service Oct. 28th
What a crock. All the while she said, "we're the cheapest of all the national carriers for exchanges" but my gf's HTC Aria on AT&T was replaced without any discussion of "warranty exchange fees".
AT&T sucks at my house too. Maybe I'll just upgrade my Verizon business phone and get the Droid Prime or whatever (I hate Verizon though).
Click to expand...
Click to collapse
If your stuck at the s/w upgrade screen,even after trying to flash a rom or nandroid, check out a thread in development section called nvflash rom for recovery. I myself was stuck on the s/w screen and after following the directions was able to boot back into android.
http://forum.xda-developers.com/showthread.php?p=17258229
Sent from my LG-P999 using xda premium
OMG dude if that works I will jump for joy.
[UPDATE]
I LOVE XDA!!!!
Amazing, Truly Amazing
Back on September 14th I downloaded that 14 Mb update. Since then I've flashed many times between stock, special ROMs, and of course the Gingerbread leaks. Well, my current issue is that I'm stuck on UCKE3 which is the newest I could find (the one from early June.) So far I have had no luck re-updating my phone to UCKH1 from the 14th. I'm getting the constant, "Your phone is up to date. You may check back in 24 hr and 24 min" message. This is very frusterating to me since when I'm on stock I like to have to latest official updates. Anyone have any idea what's causing this? I've asked a similar question in the Q&A thread, but some kid gave me nothing but a link to GTG's modem collection which is not what I really needed and threw a whole you better thank me for helping you thing in my face, so I prefer to check in here.
I assume you're referring to gtg's "Return to stock" UCKE3? If you actually want to be stock, that's the one to go with. That OTA Update really doesn't gain you much value, except for possibly the KI3 modem (which of course you know you can install yourself, no thanks necessary )
Now for your actual question: I don't have a definitive answer for you, but a good guess that "Return to stock" may not be 100% stock. Obviously it's rooted, but there may be something else (don't know what) that might be just different enough that AT&T's firmware update utility no longer recognizes your ROM as a candidate for updates.
Sorry that's not a very solid answer, but if I were you I wouldn't sweat this particular update anyway.
I had the same problem. What I did was return to stock using gtg's unbrick then after the phone booted I did a factory reset from the settings menu. I was able to get the update installed after that. Just back up your SD cards if you try this.
Sent from my SAMSUNG-SGH-I997 using XDA App
UCKH1 updated the bootloader and modem. I'll find you the link so you can Odin it. it's the completely stock version.
http://hotfile.com/dl/129136963/92a8405/SGH-I997_I997UCKH1_ATT.rar.html
The password for the .RAR is samfirmware.com
Flashed the UCKI3 modem and now I'm back to FROYO.UCKH1! Don't know why I didn't do that in the first place... Oh well. That's what happens when you get 2 hours of sleep then wake up at 7 to PT, haha. I will be thanking your post, good sir.
Bandit_Kaine said:
UCKH1 updated the bootloader and modem. I'll find you the link so you can Odin it. it's the completely stock version.
http://hotfile.com/dl/129136963/92a8405/SGH-I997_I997UCKH1_ATT.rar.html
The password for the .RAR is samfirmware.com
Click to expand...
Click to collapse
This will come in handy for if I need it again, and honestly, I might as well just flash this to be completely safe. You will also be receiving a thanks.
Bandit_Kaine said:
UCKH1 updated the bootloader and modem. I'll find you the link so you can Odin it. it's the completely stock version.
http://hotfile.com/dl/129136963/92a8405/SGH-I997_I997UCKH1_ATT.rar.html
The password for the .RAR is samfirmware.com
Click to expand...
Click to collapse
Thank you for the link. I downloaded it and tried to Odin it... Odin recognised my phone "showing yellow in the top left bar), but the step stayed a "<1> connection setup" for a little under 10mins without doing anything more...
Any ideas what I'm doing wrong?
My phone is rooted and I'm on UCKE3.
Thank you
Unplug then plug it back in,if that doesn't start it, reboot and put it back in download mode. Rerun Odin.
Sent from my SAMSUNG-SGH-I997 using xda premium
Hello,
When I first purchased the SGS4G a few months ago I was able to follow a nice and user-friendly tutorial on how to root my phone using super-one-click. I wanted to delete all of the nasty bloatware and also unlock my phone. That worked lovely (thanks by the way) and everything was going well....
That is until I got a message from my friend telling me that Samsung has released an offical update (gingerbread) and that it will provide better battery life ect... I eagery followed the official steps and used something called Kies to update my phone!
Everything seemed fine until I noticed some of the bloatware had returned. No problem I thought, I'll use my titanium backup app to re-delete it, no luck... Basically it seems as if my phone has been re-rooted and SuperUser freezes when I try to open it. Have I hurt my phone by upgrading without putting it back to the factory settings? I don't want to flash my phone or anything fancy, I am just wondering if I can root my phone from gingerbread again (if so how) or if I have to live with the bloatware again.
Thanks in advance!
i wouldnt use kies anymore when you have a forum like this.
we have a ton of GB roms here, so you can look into those on your own. i would recommend following FBis251's GB Starter Pack.
to answer your question, to Root GB, just flash Drhonks GB kernels. that will give you root and CWM
Ok wow, that is a bit confusing to me as I am not super educated in the world of Android manipulation. I searched up some info regarding what you told me and it seems flashing will GIVE me gingerbread, but thats what I have already. Also, not sure what kernel or CWM means, sorry!
Thanks for your help though!
Aannon said:
Ok wow, that is a bit confusing to me as I am not super educated in the world of Android manipulation. I searched up some info regarding what you told me and it seems flashing will GIVE me gingerbread, but thats what I have already. Also, not sure what kernel or CWM means, sorry!
Thanks for your help though!
Click to expand...
Click to collapse
GB doesn't come on this phone, either you you don't have a Sgs4g our you have froyo.
Sent from my SGH-T959V using XDA App
cybok0 said:
GB doesn't come on this phone, either you you don't have a Sgs4g our you have froyo.
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
I am confused, but I'm not completely stupid... The whole point of this topic is to figure if it's possible to root a SGS4G with Gingerbread. I know the phone came with froyo, but my provider allowed for an offical update TO Gingerbread so I decided to update.
Aannon said:
I am confused, but I'm not completely stupid... The whole point of this topic is to figure if it's possible to root a SGS4G with Gingerbread. I know the phone came with froyo, but my provider allowed for an offical update TO Gingerbread so I decided to update.
Click to expand...
Click to collapse
There isn't a official release of GB for this phone, you must have a different one.
Sent from my SGH-T959V using XDA App
yea. there is no official gingerbread for this phone yet. what is your model number? (settings -->about phone--> model). also, what is your firmare version and build number? i'll walk you through it
jager555 said:
yea. there is no official gingerbread for this phone yet. what is your model number? (settings -->about phone--> model). also, what is your firmare version and build number? i'll walk you through it
Click to expand...
Click to collapse
Ok, though the update may not have been official I did it using Kies so I assumed it was, sorry guys. That being said, here's my info:
Model: SGH-T959P
Firm: 2.3.4
Build#: GINGERBREAD.PTLKH2
I don't know if this helps, but the program I used to unlock the first time was called super-one-click (or something similar) and the program installed on my phone is called Superuser. Now it doesn't work the same and other programs say my phone isn't rooted.
Hope this helps, I really appreciate the attention.
The issue that you are having is that you cannot use superoneclick to root GB.
To do this you must flash Dr honks kernel.
Now you are right when you looked it up and it said that you would flash to get GB. You will also flash to get root with GB. It will not replace the whole rom.
In the Dev section there is a post by Drhonk labelled [Kernel][GB][KG4/KG6/KH2/KI1/KI3] Stock Kernel + CWM + Voodoo EXT4 Lagfix.
Grab one of those kernels from his post. Just for ease say you use the new KI3 kernel.
There are 2 options. The Odin version or the CWM version. I really recommend using ODIN. It is easier in my opinion and you should get comfortable with ODIN anyways.
Once flashed you will not have to do anything additional. It will reboot your phone and as soon as its powered up you again will have root access (which will fix your superuser issues you mentioned as well) and give you red CWM.
Are you familiar with using ODIN at all?
no, jiggly, he has the wrong phone.
aannon, this forum is for the T959V, not p. I think you have a fascinate. look up the info on those forums.
never flash a rom from another phone. it will always brick. use odin to restore your phone to T959P stock and go from there.
Thanks for the heads up, I've done some more digging and because my phone is technically called the Fascinate 4G i think it is indeed slightly different. It's a phone from a Canadian provider, Telus and I think it's a bit of a blacksheep. The phone for all intents and purposes is almost identical to your 4G, but it is different enough to require its own software ect... Thanks for the warning! I may have to live with bloatware for now
I tried installing KIES on (2) different computers. I finally got it to recognize the phone, it started the update, then got stuck at 100% of "downloading firmware upgrade components". After about 5 minutes, the window closes and KIES locks up. I tried reinstalling KIES, no luck.
Is there any other way (besides rooting and installing a custom ROM) to upgrade the SGS Blaze to ICS?
...samsung should be ashamed to put out ****ware.
androidmonkey said:
I tried installing KIES on (2) different computers. I finally got it to recognize the phone, it started the update, then got stuck at 100% of "downloading firmware upgrade components". After about 5 minutes, the window closes and KIES locks up. I tried reinstalling KIES, no luck.
Is there any other way (besides rooting and installing a custom ROM) to upgrade the SGS Blaze to ICS?
...samsung should be ashamed to put out ****ware.
Click to expand...
Click to collapse
I'm pretty sure you are stuck using Kies without rooting
Its a pretty fast process to root/cwm and put on a ROM, probably 20 minutes or so including making a backup. You can still install the stock ROM from here if you want.
dispozable said:
I'm pretty sure you are stuck using Kies without rooting
Its a pretty fast process to root/cwm and put on a ROM, probably 20 minutes or so including making a backup. You can still install the stock ROM from here if you want.
Click to expand...
Click to collapse
Would folks find an odinable stock ICS useful? I thought there was one around already, lemme know if not
dwitherell said:
Would folks find an odinable stock ICS useful? I thought there was one around already, lemme know if not
Click to expand...
Click to collapse
There is a one click but it was for the i577 ICS rom, a stock blaze one would be great!
These are my parents phones, both SGS Blaze. I would rather not root them, since they aren't very tech savy. Its a shame that the largest smartphone manufacturer in the world cannot make decent software. It reminds me of really bad software from the mid 90's. That said, my parents are just fine with using GB, I just love ICS so much that I was hoping to get it installed for them.
androidmonkey said:
These are my parents phones, both SGS Blaze. I would rather not root them, since they aren't very tech savy. Its a shame that the largest smartphone manufacturer in the world cannot make decent software. It reminds me of really bad software from the mid 90's. That said, my parents are just fine with using GB, I just love ICS so much that I was hoping to get it installed for them.
Click to expand...
Click to collapse
Right on - I meant an untouched stock ODINable version - that way instead of needing Kies you just need ODIN to get you updated. Hell I could even whip up a stock CWM version, all bloated and odexed and what not. Sometimes such things are handy as options to "return to stock" and all. I am unsure how to automate the process like thomas.raines does, but I could make a file you can use the old-fashioned way with ODIN.
So this really doesn't exist elsewhere? I haven't needed it (and I'm inherently lazy) so I haven't really searched for it.
dispozable said:
There is a one click but it was for the i577 ICS rom, a stock blaze one would be great!
Click to expand...
Click to collapse
Correct me if I'm wrong, but I thought you all ready posted an ICS tar?
http://forum.xda-developers.com/showthread.php?p=32350776
Sent from my SGH-T769 using xda app-developers app
Sleeps17 said:
Correct me if I'm wrong, but I thought you all ready posted an ICS tar?
http://forum.xda-developers.com/showthread.php?p=32350776
Sent from my SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
LOL - yeah that looks like what Kies gives you anyway. That one can be problematic if you flash it with ODIN though - at least it was in my experience, which is why I removed some things and made CWM flashable variants to get around the issues (i.e. hung/failed on the modems).