Related
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 flashed the 0817_charge_recovery.tar.md5. I didnt see that it worked and then went back into download, thru Odin, tried to flish cwm_Recovery4008.tar. Got a fail and now when i try to turn on it just shows an icon of a phone with a yellow triangle exclamation point between that and a computer icon. it still goes into download mode with volume down and usb connection but it wont flash the default VZW rom back.
Suggestions?
Battery in or out?
battery in = (phone) ... ! ... (cpu)
battery out = can still go into download mode
Did you come from another rom? I think if you want to flash back to stock from another rom via odin you need to also flash the pit file. At least thats what I had to do.
Sent from my SCH-I510 using XDA App
No i had reverted back to the stock (pentafive ee4 full factor tar).
Have you tried everything from imnuts Fix your Phone thread?
http://forum.xda-developers.com/showthread.php?t=1111486
Ya i got a fail for that as well on Odin. Also tried the Samsung PST and it said error download there as well
DRO1DZ1LLA said:
Ya i got a fail for that as well on Odin. Also tried the Samsung PST and it said error download there as well
Click to expand...
Click to collapse
Are you keeping the battery out during the entire process? You're using the PIT too with the Re-partition box checked (unchecked Auto Restart and F. Time)?
I left the battery in cause in step 4b he says to but anyways it worked. the first time i tried i was using the ed2 file cause for some reason the ed1 link wasnt loading. then i realized i had that file already from somewhere else and used that and it went through
DRO1DZ1LLA said:
I left the battery in cause in step 4b he says to but anyways it worked. the first time i tried i was using the ed2 file cause for some reason the ed1 link wasnt loading. then i realized i had that file already from somewhere else and used that and it went through
Click to expand...
Click to collapse
Nice, bro! Glad to hear you're back up!
thanks for all the help tho! so should i not try to re-root/rom/kernel this ***** or what?
DRO1DZ1LLA said:
thanks for all the help tho! so should i not try to re-root/rom/kernel this ***** or what?
Click to expand...
Click to collapse
Right now, your best bet is to apply whatever system updates there are. If your phone doesn't get you up to EE4 on its own, then you should follow imnuts' instructions here: http://rootzwiki.com/topic/10202-how-to-prepare-for-the-gb-ota/
At some point today, someone will be able to confirm whether the update.zip (leaked) is truly 100% identical to the update.zip that Verizon is pushing out for EP4. If it is, then we'll be safe update to EP4 ahead of the OTA, root, restore any backups, and apply working EP4 themes. I'm anxiously awaiting the ability to depoop my phone--rolled back to stock EE4 last night and have hated my phone ever since!
Haha same. I returned initially for the same reason and then was so sick of it i pushed ahead and messed it up. Still haven't gotten the update tho
Happened to me once. Used stock ee4 odin with the charge .Pit file imnuts posted and it brought me back to stock
Sent from my SCH-I510 using Tapatalk
ok i see since it has been so long since all the rogers development started people dont really remember about all the rainbow problems and how they were fixed and how the fix needs source code.
we now have bootloaders available in leaks from samsung. they are needed with the stock kernels that come in the leaks to avoid rainbow garbage. i am providing the bootloaders to be flashed in heimdall without having to flash a whole rom.
i would like to make this explicitly clear that if this bricks your phone i am not to blame. there is a significant risk when flashing bootloaders! though the infuse seems to have safety measures i strongly recommend only flashing once. and if your phone becomes a brick you will need to solder things to the phone to fix it via j-tag or adam outlers unbrickable mod. be cautious! dont flash boot.bin without sbl.bin, dont flash sbl.bin without boot.bin, dont mix up the partitions, and if the phone bricks i dont want to know about it unless you want to pay me to fix it!
heimdall package
http://www.multiupload.com/GXUTF4QCJX
odin package (untested)
http://www.multiupload.com.... REMOVED May be failing to flash. very dangerous situation...
bootloaders for heimdall to be added through the "flash" tab (unzip first! ibl/pbl-boot.bin, sbl-sbl.bin)
http://www.multiupload.com/NAIA23JZL1
good luck!
Thanks for posting this. Hopefully it will help out with leak questions that tend to get asked over and over again.
Sent from my SAMSUNG-SGH-I997
Yeah. Thanks for posting, Dani.
do you know if there its any difference in bootloaders amongst different gingerbread leaks?
I have been running the first leaked gingerbread's bootloaders since Prezkit gave them to us and have had zero issues. I think it was kk1? I've been taking an "if it ain't broke" stance. its going good!
MattSoRaven said:
Yeah. Thanks for posting, Dani.
do you know if there its any difference in bootloaders amongst different gingerbread leaks?
I have been running the first leaked gingerbread's bootloaders since Prezkit gave them to us and have had zero issues. I think it was kk1? I've been taking an "if it ain't broke" stance. its going good!
Click to expand...
Click to collapse
there is difs. but I couldn't tell you what. I saw posts by Linux bozo who did binary diferencials but I don't see any difference.
I know the bootloaders have a counter for customer kernels. if you flash the parameters.ifs from the ultimate unbrick it resets it. I also know they changed the galaxy s 2 bootloaders so it was harder to reset the counter so don't expect to be able to reset it when the official update comes along. I also have been using the "if it ain't broke " theory and honestly don't remember which I am using. the packages here are uckk3. if people can test if the counter can still be reset by flashing param.ifs let me know. ill post older bootloaders if it can't otherwise I can't think of any reason to pick one over another.
If i am flashing the bootloaders via odin does the .tar file go in the pda slot. thank you for this.
Sent from my SAMSUNG-SGH-I997 using xda premium
bigbadwolf311 said:
If i am flashing the bootloaders via odin does the .tar file go in the pda slot. thank you for this.
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
yes. that's how I would do it. the PDA slot seems to be automatic as far as partition sorting. the phone slot is for modems but if a modem is included in a package for the PDA slot it flashes just fine. the bootloaders are in the PDA packages normally so that's how I would do it.
please report results because I don't run windows and did not test that package.
I will report back once i get around to flashing the bootloaders. Thanks again for this.
Sent from my SAMSUNG-SGH-I997 using xda premium
Dani897 said:
there is difs. but I couldn't tell you what. I saw posts by Linux bozo who did binary diferencials but I don't see any difference.
I know the bootloaders have a counter for customer kernels. if you flash the parameters.ifs from the ultimate unbrick it resets it. I also know they changed the galaxy s 2 bootloaders so it was harder to reset the counter so don't expect to be able to reset it when the official update comes along. I also have been using the "if it ain't broke " theory and honestly don't remember which I am using. the packages here are uckk3. if people can test if the counter can still be reset by flashing param.ifs let me know. ill post older bootloaders if it can't otherwise I can't think of any reason to pick one over another.
Click to expand...
Click to collapse
I've been using the UCKJ2 bootloaders since they came out with no issues.
Entropy512 said:
I've been using the UCKJ2 bootloaders since they came out with no issues.
Click to expand...
Click to collapse
Same here.
Sent from my SAMSUNG-SGH-I997 using xda premium
bigbadwolf311 said:
I will report back once i get around to flashing the bootloaders. Thanks again for this.
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
Wonder if u can give me directions for the odin method. Should i put it in download mode like im flashing back to stock? Can i Flash this over a custom rom?
schmidtty661 said:
Wonder if u can give me directions for the odin method. Should i put it in download mode like im flashing back to stock? Can i Flash this over a custom rom?
Click to expand...
Click to collapse
don't select repartition, no need for a pit, the rom shouldn't matter, the file should go in the PDA slot. remember I haven't tested it in Odin. I don't run windows and have little interest in using Odin for anything. phone needs to be in download mode just like flahong a rom. it should only take a second or two to flash. good luck
Cool i should be able to figure this out. Thanks for the quick response.
It didn't work. I had auto restart, f.reset and the PDA slot checked after i opened the file in the PDA slot and after clicking start it just sat at setup for 45 min until i gave up and flashed back to stock. I had to pull the cord while in download mode and the screen turned black with green dots so i had to flash blindly. I tried it twice and the same thing. Has anyone else tried this?
schmidtty661 said:
It didn't work. I had auto restart, f.reset and the PDA slot checked after i opened the file in the PDA slot and after clicking start it just sat at setup for 45 min until i gave up and flashed back to stock. I had to pull the cord while in download mode and the screen turned black with green dots so i had to flash blindly. I tried it twice and the same thing. Has anyone else tried this?
Click to expand...
Click to collapse
I have a bunch of downloads but nobody reported anything at all till now.
ill pull the Odin version for now. try it in heimdall. its not any harder to use.
Can you post an odin package.
I had an Odin package. I got a few downloads, didn't get any people thanking for it, didn't get any positive feedback that it worked and had one user report problems, see the last couple posts. I pulled the file for lack of evidence that it worked. I don't run windows and prefer heimdall so I haven't tested it in Odin. sorry but I suggest you either flash an entire rom leak then flash a non secure kernel through Odin ( any custom kernel should do also flashing back to stock should also do just fine) and then flash a rom or learn heimdall which works on windows as well as Mac and Linux. I would have done a oneclick package but it still requires the installation of the heimdall back end and I figured it was really no harder to just use the heimdall package system.
any chance of relink thats not at multiupload?
edit: disregard, found a workaround. might be useful in future tho.
I tried to unroot my sgh-i727 Samsung Galaxy S2 Skyrocket back to stock setting. I downloaded and unzipped ODIN as well as the stock tar file. Everything ran fine, or so it seemed. Now it seems that every app that has anything to do with google force closes and I get an error message. Then same goes for when I hit my phone button to try to make a call. I get the same error message. I'm a noob here so any help would be greatly appreciated.
Did u install the uclc5/note radio at any point? Download completely stock firmware from here and flash via odin
http://www.sammobile.com/firmware/?page=3&t=1&o=1&m=SGH-I727R&r=5
Kudos to xcrazy for finding a complete firmware image
icenight89 said:
Did u install the uclc5/note radio at any point? Download completely stock firmware from here and flash via odin
http://www.sammobile.com/firmware/?page=3&t=1&o=1&m=SGH-I727R&r=5
Kudos to xcrazy for finding a complete firmware image
Click to expand...
Click to collapse
Ice (or anyone else), do you know what the differences to this stock firmware build? http://forum.xda-developers.com/showthread.php?t=1349207&highlight=uckj2
The one in that thread is 282.6mb, but the one on the sammobile site is 314.9mb...
I haven't actually downloaded it.myself, just checked out the site to make sure they had it. I credit the size increase to the fact that its complete firmware, it includes the radio and everything else. I however trust xcrazy, he knows what he's doing
icenight89 said:
Did u install the uclc5/note radio at any point? Download completely stock firmware from here and flash via odin
http://www.sammobile.com/firmware/?page=3&t=1&o=1&m=SGH-I727R&r=5
Kudos to xcrazy for finding a complete firmware image
Click to expand...
Click to collapse
The above link is for the Rogers (727R) version, correct link for AT&T version I727UCKJ2 is: http://www.sammobile.com/firmware/?page=3&t=1&o=1&m=SGH-I727&r=5
The sam mobile tar's are the official firmware, go with that.
icenight89 said:
I haven't actually downloaded it.myself, just checked out the site to make sure they had it. I credit the size increase to the fact that its complete firmware, it includes the radio and everything else. I however trust xcrazy, he knows what he's doing
Click to expand...
Click to collapse
The one in the XDA link I posted also flashes the radio (I've used it several times). Maybe just a little extra bloat from Sammy on the other one?
I'd say use the one from sammobile first, of course, I'm just curious if there's a real difference.
I'm trying the radio flash now I'll let you guys know how it goes. Thank You!
Heres another question while I'm waiting on this download. Is the skyrocket upgradeable to 4.0 ICS yet? If not what android version is the most up to date?
When I flash roms via ODIN will the process always be the same? By that I mean taking out the battery then replacing it. Hold down the volume buttons and then plugging the phone into the computer?
bmhampshire said:
When I flash roms via ODIN will the process always be the same? By that I mean taking out the battery then replacing it. Hold down the volume buttons and then plugging the phone into the computer?
Click to expand...
Click to collapse
Yup. I don't bother with the battery though, or the usb plug in, I just restart the phone by holding the power button > 10 secs, and when it vibrates quickly hold the volume buttons, and it goes into download confirm mode. Then i plug in the usb and press up to confirm, and presto.
ok so i tried reflashing the radio and that didn't work. I'm probably messing something up. Heres what I'm doing for you guys to let me know what I'm doing wrong.
I opened ODIN and the only thing check marked is Auto Reboot.
After that I opened the the stock tar file (SGH-I727-UCKJ2-k0nane.tar) under PDA then I started the reboot. That got everything back to normal besides alot of apps force closing to include not being able to make calls. After that I flashed the HOME_SGH-I727user_CL626051_REV02.tar.md5 file under PDA for the radio. I'm a super noob so can someone break it down Barney style for me PLEASE? You guys are awesome by the way!!!
I still think the fc's are a radio issue. Flash this first, method 3:
http://forum.xda-developers.com/showthread.php?t=1611796
Both of these include the radio, but vary in size. The first one is 250mb while the second is 315:
This one is a system dump from an xda member:
http://forum.xda-developers.com/showthread.php?t=1349207&highlight=uckj2
This one is the complete firmware image from samsung, but you have to sign up to download:
http://www.sammobile.com/firmware/?page=3&t=1&o=1&m=SGH-I727&r=5
When I open up ODIN do I flash everything through PDA one at a time? What are the other options for i.e. bootloader, phone, csc?
U need to flash cwm through odin:
http://forum.xda-developers.com/showthread.php?t=1340526
Then you have to flash the first link i posted through cwm. As for the second and third, they are the same thing. You pick, based on the descriptions i used. The second one you flash through cwm, the third one is an ODIN flash.
doesn't it have to be a .tar file through ODIN?
It is a tar, flash the clockwork mod file u downloaded. It may be zipped, you might have to extract it
If it prompts you for a password when unzipping the downloaded file for the stock firmware, try sampro.pl
EDIT: It will likely have a file extension of .tar.md5. This is fine. Just put it in the pda slot. Do not put anything in any other slot. DO NOT CHECK REPARTITION. Only Auto-Reboot should be checked.
Sent from my SAMSUNG-SGH-I727 using xda premium
bmhampshire said:
Heres another question while I'm waiting on this download. Is the skyrocket upgradeable to 4.0 ICS yet? If not what android version is the most up to date?
Click to expand...
Click to collapse
Ahem....Have you checked the "development" section at all?
chappatti said:
Ahem....Have you checked the "development" section at all?
Click to expand...
Click to collapse
Ha!!! I kind of just ignored that post--wasn't feeling like getting all trolly today. My mood may change however...
skrambled said:
The one in the XDA link I posted also flashes the radio (I've used it several times). Maybe just a little extra bloat from Sammy on the other one?
I'd say use the one from sammobile first, of course, I'm just curious if there's a real difference.
Click to expand...
Click to collapse
It is the complete official tar. It has everything, untouched, just how it comes from the factory. It is official and does not trip the counter
If you are downloading the rogers version, this should be the password
samfirmware.com
Yes, everyone knows by now
ICS for Rogers Skyrocket is available through Kies as an Update as of this morning!!!
Also ROOT works too!!!
Sorry guys for my writing style, hope this is the right place to post it.
Just wanted to pass some news and tips so you know 100% what works and what doesn't.
-----------------------------------------------------------------------
ROM UPDATE
-----------------------------------------------------------------------
Make sure your Kies is up to date and you have all Samsung Drivers correctly installed. If you update drivers and/or Kies software REBOOT YOUR COMPUTER.
It did not work for me when I was on another ISC leak ROM (ICS->ICS no no, GB->ICS yes! makes sense)
So went back and first flashed Rogers Radio/Modem (Radio_I727RUXKJ7.zip) and then ODIN Stock ROM (SGH-I727R-UCKJ2-k0nane.tar)
Thanks k0nane!
After doing that, Update through Kies went with no issues.
(it takes about 15 min so make sure your battery is fully charged and depending on your Internet connection it may be longer or faster)
Some screensots from Kies are attached below.
Pay attention to the messages, especially for the last NOTICE after update shows 100%.
The phone WILL REBOOT ON ITS OWN AFTER COUPLE MINUTES.
DO NOT PULL THE CABLE OUT!!!
-----------------------------------------------------------------------
ROOT
-----------------------------------------------------------------------
It works.
Just follow instructions from starskyrob in THIS Guide
Thanks starskyrob!
It actually ONLY works with this version (Superuser-3.0.7-efghi-signed.zip)
I know that because, of course I got too lazy and used SGSII Toolkit to do dirty work but it only ODINed proper CWM for me and then superuser.zip it tries to flash is 3.0.5 so this version does not work.
Just use Superuser-3.0.7-efghi-signed.zip and everything will be fine.
Hope it helps some of you.
We waited waaaaay too long for this!!!
Except you tripped your flash counter if you used k0nane's "stock" tar. You're better off using the stock tar from the Sammobile website. I can confirm first hand that k0nane's trips the counter, the stock tar from Sammobile does NOT.
pixelens said:
Except you tripped your flash counter if you used k0nane's "stock" tar. You're better off using the stock tar from the Sammobile website. I can confirm first hand that k0nane's trips the counter, the stock tar from Sammobile does NOT.
Click to expand...
Click to collapse
Correct sir! K0nane's trip counter every single time... Always use the sammobile tar. Just register and look for your device in my case "i727" downloading official tar does not trip counter, I really don't know why K0nane has not updated it yet.
Sent from my SAMSUNG-SGH-I727 using xda premium
r3dp0is0n2012 said:
Correct sir! K0nane's trip counter every single time... Always use the sammobile tar. Just register and look for your device in my case "i727" downloading official tar does not trip counter, I really don't know why K0nane has not updated it yet.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Thanks guys, I had no idea the one from Samobile is better. Must check that out next time.
Honestly, it does not even matter to me because there is counter reset zip so it clears that easily and if phone ever breaks it will justify getting S3 LOL
wating for the ATT version
wilczy said:
Thanks guys, I had no idea the one from Samobile is better. Must check that out next time.
Honestly, it does not even matter to me because there is counter reset zip so it clears that easily and if phone ever breaks it will justify getting S3 LOL
Click to expand...
Click to collapse
Yeah, not as huge a deal now - but when I was doing it there was no counter reset.
As well, the two files are different in size, I can't recall which is larger though so something's not jiving.
not going to the stock official, going to wait for some devs to cook up some nice roms and kernels and flash the new stuff via CWM.
hope 4.0.4 stock is working well for all though. Good to see it is finally here with the new modem file !
What would happen if an att i727 is flashed with an odin tar of rogers ICS ? I heard that modem works fine on att i727
mahanddeem said:
What would happen if an att i727 is flashed with an odin tar of rogers ICS ? I heard that modem works fine on att i727
Click to expand...
Click to collapse
Proven to soft brick at the least
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
unibombz said:
not going to the stock official, going to wait for some devs to cook up some nice roms and kernels and flash the new stuff via CWM.
hope 4.0.4 stock is working well for all though. Good to see it is finally here with the new modem file !
Click to expand...
Click to collapse
i did flash rogers ics, too boring so went back to skyics to wait for new rom development
is nfc enabled/working on this?
Sent from my SAMSUNG-SGH-I727 using xda premium
waiters said:
is nfc enabled/working on this?
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Yes it is, but I have no way to check if it works.
There is few more NFC apps in the system folder comparing to other roms.
pixelens said:
Except you tripped your flash counter if you used k0nane's "stock" tar. You're better off using the stock tar from the Sammobile website. I can confirm first hand that k0nane's trips the counter, the stock tar from Sammobile does NOT.
Click to expand...
Click to collapse
you know you can reset counter. i totally forgot that u have to wipe data and cache and i odined my tar 5 times use the reset cwm zip and bam offical and zero count again
heere is the thread
http://forum.xda-developers.com/showthread.php?t=1575712
---------- Post added at 01:24 AM ---------- Previous post was at 01:22 AM ----------
boring rom tho nothing exciting back to cm9 or skyics
intenseone said:
you know you can reset counter. i totally forgot that u have to wipe data and cache and i odined my tar 5 times use the reset cwm zip and bam offical and zero count again
heere is the thread
http://forum.xda-developers.com/showthread.php?t=1575712
---------- Post added at 01:24 AM ---------- Previous post was at 01:22 AM ----------
boring rom tho nothing exciting back to cm9 or skyics
Click to expand...
Click to collapse
As mentioned previously, yes you can reset the counter. As also mentioned, I noticed there's a size difference between the two so added to the fact that k0nane's "stock" tar trips the counter and is a different size than the Sammobile one, I'd be inclined to use the Sammobile one. Also, why add extra steps like having to clear the flash counter? Might be worthwhile adding a note about that in the OP for those that don't read the whole thread and are unaware of the flash counter tripping situation.
WiFi problems after rooting official Rogers ICS 4.0.4
Hey everyone,
I just updated from stock Rogers GB to the official ICS - no problems there; however right after I rooted it using the file/method suggested above (again, without any issues), I started having issues with WiFi - it seems to be random but say, about 4/5 times, the WiFi would fail to connect after the phone gets restarted - although the WiFi service is running (the WiFi button is green). Sometimes there is also a system flash showing the message "?WiFi available" with a question mark before the message. If I manually stop/restart the WiFi, it eventually recognizes the hotspot and it connects. I have the Superuser & Busybox Pro PROPERLY installed, furthermore, no other program that requires root permissions seems to be having any problems whatsoever (Titanium Backup, Rom Manager, Superuser, Tasker, CallRecorder, etc).
Although I didn't spent much time playing around BEFORE applying the root, it seems obvious to me that this only occurs after rooting - personally I suspect that ICS 4.0.4 doesn't go along very well with this rooting method (mismatching binaries). I am also aware about a known bug in ICS 4.0.4, causing the WiFi to frequently drop - could it be one and the same?
FYI: I tried installing/reinstalling ICS several times: initially I have updated through Kies, than I flashed the ROM from Sammobile through Odin, and then another couple of time I just reformatted the system in CWM and reinstalled everything again.. At first I used some backups from TB (no system files, only 3rd party), but then, suspecting that backups made in GB might conflict with ICS structure, I didn't use any backups at all - just fresh installations - no difference, same problem.
UPDATE: I have flashed & done some tests with SKY-ICS by seanzscreams. Unfortunately, since it's based on the same Rogers' ROM, it comes with the same problem. I guess this only confirms my observation.
Anybody else having this issue?
Super user 3.0.7 does not flash in recovery, gives an error
It works with this Recovery
http://forum.xda-developers.com/showthread.php?t=1566613
odeccacccp said:
Super user 3.0.7 does not flash in recovery, gives an error
It works with this Recovery
http://forum.xda-developers.com/showthread.php?t=1566613
Click to expand...
Click to collapse
Well, actually it DOES work while YES, it does give an error - all you have to do is ignore the error and keep trying; the 3rd or the 4th attempt shall be successful and it'll confirm the process successfully completed.
HOWEVER
Super User 3.0.7 and CWM are two completely different things. The Super User 3.0.7 combined with the binaries (as it comes zipped) is intended to root the phone, while the CWM is a set of tools - having nothing to do with rooting.
My concern is that even the developer of the package Super User 3.0.7.zip admits that the binaries were intended for all Android versions up to 4.0.3 - while, like many others, I was hoping to also work with 4.0.4 - which it does...but it doesn't.
A direct reference can be found here.
Has anyone heard whether or not Chainfire, as come up with a non Odin one click, with CWM Touch & root?
I get the feeling that can do all this in his sleep!
Sent from, The Eclectic Chair.
Ok, I've got a couple of probably very dumb questions. So sorry!
I updated my phone to the rogers ICS using kies. Everything is great, but I no longer have Root.
In reading Copperheads instructions this is what I don't get.
I already have
The the superuser zip on my external sd card, as well as Rom Manager, CWM Recovery and titanium etc. They're all present in my app drawer & as short cuts on the phone. What is missing is the root access, why is the message I get when trying to open any of them Is there no way to flash what's already on my phone? Or do I basically have to start from scratch with Odin So I apologize again for the question, it's just hard for me to figure out why, if everything is actually on the phone now?
Sent from, The Eclectic Chair.
quick question
Okay so quick question,
If it's better to use the stock odin tar from sammobile to flash back to stock.
Would it be better to flash the I727RUXLF3(ICS) from sammobile right away or go back to stock gingerbread and upgrade through kies.