samsung kies/win 7 64 bit help please ( cant get gingerbread update) - Samsung Infuse 4G

running windows 7 64 bit home premium and trying to update my infuse 4g to gingerbread. but still getting a unregistered device and greyed out upgrade button on samsung kies mini. assuming because kies mini is not supported on 64 bit systems is there a work around and substitute? this is the only pc i have and all my friends have 64 bits systems as well. ugh i need help so i can get my phone updated!

pt5970 said:
running windows 7 64 bit home premium and trying to update my infuse 4g to gingerbread. but still getting a unregistered device and greyed out upgrade button on samsung kies mini. assuming because kies mini is not supported on 64 bit systems is there a work around and substitute? this is the only pc i have and all my friends have 64 bits systems as well. ugh i need help so i can get my phone updated!
Click to expand...
Click to collapse
Kies Mini works on Win7 64-bit just fine.
The problem is that you're running UCKH1, and most of the people running UCKH1 have yet to be able to upgrade. The current speculation is that Samsung is doing a controlled rollout to those on UCKH1, possibly based on IMEI.
If you have to have it right now, revert to UCKD5. Kies Mini has allowed everyone with UCKD5 to upgrade immediately.

gingerbread update issues
mcl said:
Kies Mini works on Win7 64-bit just fine.
The problem is that you're running UCKH1, and most of the people running UCKH1 have yet to be able to upgrade. The current speculation is that Samsung is doing a controlled rollout to those on UCKH1, possibly based on IMEI.
If you have to have it right now, revert to UCKD5. Kies Mini has allowed everyone with UCKD5 to upgrade immediately.
Click to expand...
Click to collapse
how can i revert to uckd5 if uckh1 was preinstalled on phone when i got it? factory reset on phone still uses that baseband. so annoying to want this update but cant lol
**UPDATE** found this post http://forum.xda-developers.com/showthread.php?t=1116251 trying that now see if it works.

pt5970 said:
how can i revert to uckd5 if uckh1 was preinstalled on phone when i got it? factory reset on phone still uses that baseband. so annoying to want this update but cant lol
Click to expand...
Click to collapse
GTG Ultimate Unbrick. http://forum.xda-developers.com/showthread.php?t=1116251

lol we posted like at the same time haha ok will let you know how this goes and ty for the help.

mcl said:
Kies Mini works on Win7 64-bit just fine.
The problem is that you're running UCKH1, and most of the people running UCKH1 have yet to be able to upgrade. The current speculation is that Samsung is doing a controlled rollout to those on UCKH1, possibly based on IMEI.
If you have to have it right now, revert to UCKD5. Kies Mini has allowed everyone with UCKD5 to upgrade immediately.
Click to expand...
Click to collapse
Kies Mini does NOT work on Windows 7 64-bit just fine. It seems to pick and choose which will work and which won't. It flat out refused to work on both my Windows 7 Pro 64-bit machines at work and home. I finally got Kies to work on my old laptop running XP. But I agree you should be on UCKD5 before you try.

pt5970 said:
lol we posted like at the same time haha ok will let you know how this goes and ty for the help.
Click to expand...
Click to collapse
I'm kinda puzzled why you have waited for an official release..and not waited a bit longer.
If you are willing to use Odin to mod your phone to uckd5, why not flash the leak uckl2 previously, run it for 2 months, then odin flash it today back to uckd5 to see what all the hub bub was about?
If you wanted to upgrade thru official means, why not wait a few days more?
Ooh well...I'm starting to sound like that raving Dani lunatic.

well using odin to get a official update a couple days early isnt a big deal but flashing custom roms and leaks is . i dont wanna be doing backups and reinstalling things repeatedly . once to get gingerbread is plenty. thats just me and im just saying.
**update** i odin flashed to the suggested uck.... and VIOLA!!!!! now updating to gingerbread as we speak!!!!!! ty for all the help . can now enjoy my phone again and see how the raved gingerbread works and how much better the battery life is only complaint i know i will have is not having silient in my status bar!!!! stupid, if i wanna use airplane mode i could hold power button haha

MikeyFTL said:
Kies Mini does NOT work on Windows 7 64-bit just fine. It seems to pick and choose which will work and which won't. It flat out refused to work on both my Windows 7 Pro 64-bit machines at work and home. I finally got Kies to work on my old laptop running XP. But I agree you should be on UCKD5 before you try.
Click to expand...
Click to collapse
And yet, it worked on MY Win7 64-bit machines at home and work. And other people's.

mcl said:
And yet, it worked on MY Win7 64-bit machines at home and work. And other people's.
Click to expand...
Click to collapse
well if you read up^ you will see we figured out it wasnt the pc it was the basband on my phone that needed downgraded before it would let me do the update, that or me just wait another day or 2 or 3 lol kies mini works on win 7 we know cause after i odin flashed to stock etc im now running gingerbread!
but i am getting more headaches ugh lol pain trying to root 2.3 and dolphin browser hd crashes and wont run . bummer hope i can email devs on that and figure it out . otherwise im loving it

pt5970 said:
well if you read up^ you will see we figured out it wasnt the pc it was the basband on my phone that needed downgraded before it would let me do the update, that or me just wait another day or 2 or 3 lol kies mini works on win 7 we know cause after i odin flashed to stock etc im now running gingerbread!
Click to expand...
Click to collapse
I'm aware of that. I'm the one that explained it to you.

Related

[Q] I cannot upgrade firmware Galaxy S

Hi ! I have a Galaxy S, SGH-I897, AT&T, unlocked. I have been trying to use Kies (version 1.5.3.10093_80) to upgrade the firmware, as stated on Kies window.
Everytime I try it, I have "Firmware upgrade cannot proceed. Firmware upgrade will close." Also, Kies crashed after clicking on cancel after it.
Version installed: PDA:JF6 / Phone:JF6 / CSC: JF6
Most recent: PDA:JH7 / Phone:JF7 / CSC:JF6
Current firmware: 2.1-update 1
Baseband version: I897UCJF6
Kernel version: 2.6.29
Builder number: eclair
WIndows 7 - 64 bit
Please, any idea how to fix it?
Tks !
Bump !! Anyone ?
Kies sucks. Use Odin
Sent from my GT-I9000 using XDA App
willasb said:
Hi ! I have a Galaxy S, SGH-I897, AT&T, unlocked. I have been trying to use Kies (version 1.5.3.10093_80) to upgrade the firmware, as stated on Kies window.
Everytime I try it, I have "Firmware upgrade cannot proceed. Firmware upgrade will close." Also, Kies crashed after clicking on cancel after it.
Version installed: PDA:JF6 / Phone:JF6 / CSC: JF6
Most recent: PDA:JH7 / Phone:JF7 / CSC:JF6
Current firmware: 2.1-update 1
Baseband version: I897UCJF6
Kernel version: 2.6.29
Builder number: eclair
WIndows 7 - 64 bit
Please, any idea how to fix it?
Tks !
Click to expand...
Click to collapse
Samsung has Mini Kies (or Kies Mini) which is more stable then Kies. It is on their web site under support software for the captivate.
I have tried it already (Mini Kies) and does not work as well...
LinuxNewb said:
Kies sucks. Use Odin
Click to expand...
Click to collapse
Must I repeat what he said?
Kies sucks. Use Odin.
I'll even be nice and give you some links.
If you want Froyo 2.2 go here
If you want 2.1 JH7 go here
And for stock 2.1 JF6 go here
You should ALWAYS keep the one for JF6 on your computer incase you have a catastrophic failure of your phone and need to return to stock for any reason.
Got it ! Thanks !!!!!
I downloaded the 2.2 Odin and it does nothing... Not sure how Odin works...
Thanks in advance for your help... Oh... Miztaken do you work for ATT? If so, I wanted to ask you some quick questions if I could... Thanks!!
No I don't work for AT&T lol. For Odin to work you need to put your phone in download mode. Turn it completely off. Remove the USB cable. Start Odin. Hold both volume keys on the phone and plug in the USB cable. The phone should say download and do not turn off target. At this point Odin should see your phone. Click start on Odin and your phone should be updating. If you have any other questions just ask
Sent from my Captivate
Thanks so much for the info! As a newbie... gotta ask how do you put the phone in download mode? As I understand it, download mode is activated by the holding down of the buttons right? Thanks again!!
Does odin work even if your phone is rooted or should you unroot first like kies?
Sent from my SAMSUNG-SGH-I897 using XDA App
Just wanted to thank you again! I was able to run it and my phone is up and running now!
berd said:
Does odin work even if your phone is rooted or should you unroot first like kies?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Odin works regardless of if your phone is rooted or not.
Sent from my Captivate
Cool. Ill give it a try. Thanks
Sent from my SAMSUNG-SGH-I897 using XDA App
Successfully upgraded using Kies
If you want to be sure you are installing the official version try to upgrade to the latest version of Kies first.
I am running Win7 and had the same problem before upgrading Kies.
You have to do factory reset on phone after upgrade to froyo (could not find icon for market!)
so, finally the official froyo update is here.
but it sure needs a lag fix still... (i actually got slower results in J disk benchmark after upgrading to froyo)
Anyone knows if it is possible to apply lag fix to this version?
I am running:
firmware 2.2
I900XXJPM (PDA=JP6, PHONE=JPM)
Looks like Samsung has fixed the most obvious TouchWiz bugs!
Finally being able to create contacts in phone and make them sync to gmail.
Default option when creating entry in calendar is also to changed to make entry sync correctly.
Hello, i have a Samsung SGH-i987, i want to upgrade version 2.2 to version 4... Can some ine help me please?? Thx.

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!

Trying to update to ICS, KIES sucks!!

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).

Atrix 2 ICS update failed

Hello, I'm new to these forums and I have tried to find a helpful answer to my issue but cannot, so here it goes. I have an Atrix 2 thats running Android 2.3.6, the phone was rooted with SuperOneClick last year. I updated to 2.3.6 OTA and had no problems at all. The ICS update is out I cannot get it OTA. I can download the update then the phone restarts, it appears to start installing but then stops and a triangle with "!" appears and the phone restarts. Once the phone restarts it says "Update Failed".
I have seen several others with the same issue but I do not understand how to fix it. And I am not sure if my stock ROM has been modified either.
I would greatly appreciate some help, I don't understand what I've done wrong here, Motorola says its because the phone is rooted, I've un-rooted it with no luck...
godfella691981 said:
Hello, I'm new to these forums and I have tried to find a helpful answer to my issue but cannot, so here it goes. I have an Atrix 2 thats running Android 2.3.6, the phone was rooted with SuperOneClick last year. I updated to 2.3.6 OTA and had no problems at all. The ICS update is out I cannot get it OTA. I can download the update then the phone restarts, it appears to start installing but then stops and a triangle with "!" appears and the phone restarts. Once the phone restarts it says "Update Failed".
I have seen several others with the same issue but I do not understand how to fix it. And I am not sure if my stock ROM has been modified either.
I would greatly appreciate some help, I don't understand what I've done wrong here, Motorola says its because the phone is rooted, I've un-rooted it with no luck...
Click to expand...
Click to collapse
usually updates fail when bloatware or some other stock apps are removed. I believe the best way to get ICS on your phone is by flashing FXZ. But first we need more info about your Atrix 2. Is it an AT&T branded one?
Waiting4MyAndroid said:
usually updates fail when bloatware or some other stock apps are removed. I believe the best way to get ICS on your phone is by flashing FXZ. But first we need more info about your Atrix 2. Is it an AT&T branded one?
Click to expand...
Click to collapse
Ya im in the same boat, im running on at&t. I heard u need to flash back to 2.1.1 or someghing like that. If thats the case where could I get the stock rom to do so? Also could I use odin to achieve this?
Thanks in advance.
"Jebus save me!" - H.S
JLloydMedia said:
Ya im in the same boat, im running on at&t. I heard u need to flash back to 2.1.1 or someghing like that. If thats the case where could I get the stock rom to do so? Also could I use odin to achieve this?
Thanks in advance.
"Jebus save me!" - H.S
Click to expand...
Click to collapse
You do NOT use odin on moto phones.
Please take a look here, it will explain all of the ins and outs that you need to know.
http://forum.xda-developers.com/showthread.php?t=1396650
Updating to ICS on an AT&T phone even without the bloatware is very easy, just flash the ICS FXZ for AT&T, using the latest version of RSD lite.
AT&T ICS FXZ:
http://sbf.droid-developers.org/edison/InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml.zip
You will need to find RSD lite from moto on your own though, as it has been posted in the dev section a few times, and we do not usually link to the moto site since they are like nazi's over there about XDA.
jimbridgman said:
You do NOT use odin on moto phones.
Please take a look here, it will explain all of the ins and outs that you need to know.
http://forum.xda-developers.com/showthread.php?t=1396650
Updating to ICS on an AT&T phone even without the bloatware is very easy, just flash the ICS FXZ for AT&T, using the latest version of RSD lite.
AT&T ICS FXZ:
http://sbf.droid-developers.org/edison/InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml.zip
You will need to find RSD lite from moto on your own though, as it has been posted in the dev section a few times, and we do not usually link to the moto site since they are like nazi's over there about XDA.
Click to expand...
Click to collapse
Agreed on the Mot-azi. Im banning them after my next upgrade. A bunch of pigs they are.
On a much more positive note, thank you for making it easy. Ive been away from the android community for the last few years, but man has it grown! Im lovin it. Now only if we could get some better suport from the big app companies.
Has ubuntu ever been attempted in the atrix 2? Now that would be marvelous!
"Jebus save me!" - H.S
JLloydMedia said:
Agreed on the Mot-azi. Im banning them after my next upgrade. A bunch of pigs they are.
On a much more positive note, thank you for making it easy. Ive been away from the android community for the last few years, but man has it grown! Im lovin it. Now only if we could get some better suport from the big app companies.
Has ubuntu ever been attempted in the atrix 2? Now that would be marvelous!
"Jebus save me!" - H.S
Click to expand...
Click to collapse
I have it running on my "dev phone" (Galaxy Nexus) right now, and it is nice, but a ton of things are not working yet, so I would not advise trying out just yet. I will try and get it working for the A2 in time, but a few things need be addressed first, mainly that it takes 500+MB of /system space, and the A2 is limited to 475MB in /system, so.... in getting it working, it is a meld between CM10.1 and the ubuntu UI on top of the CM 10.1 device files and drivers, but... to get the 100% real thing ported, will probably not be possible since the a2 has a locked bootloader, and the boot.img is very important to the ubuntu phone os, so.... we will see as time goes on, if I and others in here can get working on the a2 in at least the hybrid with cm10.1 format.
Also you do know that the webtop included with the A2 in 2.3 is ubuntu, right? I have a hack to get all the ubuntu stuff running in webtop, if that is something you might be interested in, but it does not work in ICS. That is why I stayed on leak 1 and never went to the official ICS version, so I could go back to GB for webtop when needed.
My webtop ubuntu hack for 2.3.5/6:
http://forum.xda-developers.com/showthread.php?t=1375042
godfella691981 said:
Hello, I'm new to these forums and I have tried to find a helpful answer to my issue but cannot, so here it goes. I have an Atrix 2 thats running Android 2.3.6, the phone was rooted with SuperOneClick last year. I updated to 2.3.6 OTA and had no problems at all. The ICS update is out I cannot get it OTA. I can download the update then the phone restarts, it appears to start installing but then stops and a triangle with "!" appears and the phone restarts. Once the phone restarts it says "Update Failed".
I have seen several others with the same issue but I do not understand how to fix it. And I am not sure if my stock ROM has been modified either.
I would greatly appreciate some help, I don't understand what I've done wrong here, Motorola says its because the phone is rooted, I've un-rooted it with no luck...
Click to expand...
Click to collapse
I updated mine the day it came out and I had a terrible time with it. The FXZ was not available at the time so I had ATT give me replacement phone. I used 2.3.6 for a little while, then I updated it again. This time though I did a factory reset before updating and everything went great. So I'd recommend doing a factory reset before updating and maybe you will have better luck. Or do as Jim suggested and flash the update yourself with RSDLite.
Waiting4MyAndroid said:
usually updates fail when bloatware or some other stock apps are removed. I believe the best way to get ICS on your phone is by flashing FXZ. But first we need more info about your Atrix 2. Is it an AT&T branded one?
Click to expand...
Click to collapse
Yes mine is ATT branded and yes I have removed all the att bloatware with Root Uninstaller once I rooted it.
I honestly don't care what pigs motorola are, I just asked about getting my phone to ICS because I keep getting the update failed message.
jimbridgman> I got RSD lite already and I clicked on the link you provided for the ICS FXZ so how do I apply this?
dmroeder said:
I updated mine the day it came out and I had a terrible time with it. The FXZ was not available at the time so I had ATT give me replacement phone. I used 2.3.6 for a little while, then I updated it again. This time though I did a factory reset before updating and everything went great. So I'd recommend doing a factory reset before updating and maybe you will have better luck. Or do as Jim suggested and flash the update yourself with RSDLite.
Click to expand...
Click to collapse
Yeah, I have already done a factory reset. Still can't get the OTA update to work. So my only option looks like I need to flash it myself.
One other thing that's completely off subject, One thing I don't like about this forum there are too many restrictions regarding spam...although I understand it needs to be completely filtered and not allowed the admins have too many restrictions on this forum. Why should there be a restriction were a new user has to wait 5 minutes between posts? That makes absolutely no since. (BTW thanks to the admins for the 5 minutes between posts I had to kill, I got to mention this)
godfella691981 said:
I got RSD lite already and I clicked on the link you provided for the ICS FXZ so how do I apply this?
Click to expand...
Click to collapse
Here's some good tutorials on flashing an fxz as well as other useful information:
http://forum.xda-developers.com/showthread.php?t=1909319
And here:
http://forum.xda-developers.com/showthread.php?t=1396650
Brought to you by time and relative dimensions in space.
1BadWolf said:
Here's some good tutorials on flashing an fxz as well as other useful information:
http://forum.xda-developers.com/showthread.php?t=1909319
And here:
http://forum.xda-developers.com/showthread.php?t=1396650
Brought to you by time and relative dimensions in space.
Click to expand...
Click to collapse
So when I run RSDlite and apply the fxz the phone will have ICS on it afterwords?
godfella691981 said:
So when I run RSDlite and apply the fxz the phone will have ICS on it afterwords?
Click to expand...
Click to collapse
As long as it's an ICS FXZ, then yes.
Brought to you by time and relative dimensions in space.
I guess you did some tweaks with it like installing CWM. You remove it and files associated with it, you can take update OTA with no probs (i was through it and finally could take the update like a noob ). An fxz would be a much easier choice.
- - - - - - - - - - - - - - - - - - - - - - - - - -
LIFE!
IT'S WHAT YOU MAKE OUT OF IT!
1BadWolf said:
As long as it's an ICS FXZ, then yes.
Brought to you by time and relative dimensions in space.
Click to expand...
Click to collapse
Yea, so I finally got around to trying to flash my phone, well when I put the phone in boot loader mode and connect it to my computer it tries to install a driver called "Edison S" it says installation failed everytime, I've updated my motorola drivers reset my computer and everything I do not understand whats going wrong.
godfella691981 said:
Yea, so I finally got around to trying to flash my phone, well when I put the phone in boot loader mode and connect it to my computer it tries to install a driver called "Edison S" it says installation failed everytime, I've updated my motorola drivers reset my computer and everything I do not understand whats going wrong.
Click to expand...
Click to collapse
Is RSD lite showing your phone as connected?
Brought to you by time and relative dimensions in space.
1BadWolf said:
Is RSD lite showing your phone as connected?
Brought to you by time and relative dimensions in space.
Click to expand...
Click to collapse
No, RSD is not showing its connected. This error occurs before I even open RSD lite, I have tried opening RSD and then connecting the phone still windows keeps looking for drivers that it never finds.
jimbridgman said:
I have it running on my "dev phone" (Galaxy Nexus) right now, and it is nice, but a ton of things are not working yet, so I would not advise trying out just yet. I will try and get it working for the A2 in time, but a few things need be addressed first, mainly that it takes 500+MB of /system space, and the A2 is limited to 475MB in /system, so.... in getting it working, it is a meld between CM10.1 and the ubuntu UI on top of the CM 10.1 device files and drivers, but... to get the 100% real thing ported, will probably not be possible since the a2 has a locked bootloader, and the boot.img is very important to the ubuntu phone os, so.... we will see as time goes on, if I and others in here can get working on the a2 in at least the hybrid with cm10.1 format.
Also you do know that the webtop included with the A2 in 2.3 is ubuntu, right? I have a hack to get all the ubuntu stuff running in webtop, if that is something you might be interested in, but it does not work in ICS. That is why I stayed on leak 1 and never went to the official ICS version, so I could go back to GB for webtop when needed.
My webtop ubuntu hack for 2.3.5/6:
http://forum.xda-developers.com/showthread.php?t=1375042
Click to expand...
Click to collapse
Hallelujah..will wait earnestly for it!!
godfella691981 said:
No, RSD is not showing its connected. This error occurs before I even open RSD lite, I have tried opening RSD and then connecting the phone still windows keeps looking for drivers that it never finds.
Click to expand...
Click to collapse
Maybe uninstall/reinstall the Moto drivers. Also, which version of RSD lite are you using? I think 6 or greater is recommended.
Brought to you by time and relative dimensions in space.

Need some help, new here

guys, i found this phone lying around and decided to battery it up, it works, it's on 2.3.6, i read around and found lots of roms made by super devs. i want to root it, i couldn't get my hands on a PIT file, and then i read i can update this to ICS using KIES? i tried through the phone it said cannot connect to server... should i just download KIES and run the upgrade or what? a simple to do would suffice i guess... anyone feeling helpful? kinda lost on how this one works since i've been using HTC a lot
jafferkhan said:
guys, i found this phone lying around and decided to battery it up, it works, it's on 2.3.6, i read around and found lots of roms made by super devs. i want to root it, i couldn't get my hands on a PIT file, and then i read i can update this to ICS using KIES? i tried through the phone it said cannot connect to server... should i just download KIES and run the upgrade or what? a simple to do would suffice i guess... anyone feeling helpful? kinda lost on how this one works since i've been using HTC a lot
Click to expand...
Click to collapse
If I remember, kies is very simple. Download kies, plug phone in and it should offer the update, no problems. I had to use kies to update my wife's and mine.
Once you've updated, uninstall kies. Rooting the Blaze and kies do not play together at all!
Try it, if you have issues come back and we'll see if we can't get it to work. Rooting with ics is the way to go...
Sent from my VS980 4G using XDA Premium 4 mobile app

Categories

Resources