Over a week ago the OTA update for the note 2 came out for my phone (in the US). I have rooted it and changed the DPI, everything else is stock. The update fails every time. I tried changing my dpi back (though it shouldn't matter) and still nothing. I then decided I would just use kies to update the firmware but kies says my phone isn't compatible on two Windows 7 computers and a Windows 8 computer. Any ideas on why I can't update to 4.1.2?
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Related
When I connect my Note II to my pc and launch Kies to sync and backup my info on my phone it says "Your device's current firmware version is not supported to update via Kies.
Current Firmware: PDA:MA4 / PHONE:MA4 / CSC:MA4 (ATT)
Is this correct on Kies or do I have a different firmware on my Note II? I have the factory firmware. The Only thing that I have updates on my Note II is when that Update patch was released via OTA. How do I get Kies to recognize my Phone's firmware?
One that other hand kinda off topic for this forum: I currently have the Galaxy Tab 2 10.1 from At&t and it has 4.0.4 firmware. Any word on it getting updated to 4.1.2 or 4.2.2 via Kies or OTA?
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Viper0580 said:
When I connect my Note II to my pc and launch Kies to sync and backup my info on my phone it says "Your device's current firmware version is not supported to update via Kies.
Current Firmware: PDA:MA4 / PHONE:MA4 / CSC:MA4 (ATT)
Is this correct on Kies or do I have a different firmware on my Note II? I have the factory firmware. The Only thing that I have updates on my Note II is when that Update patch was released via OTA. How do I get Kies to recognize my Phone's firmware?
One that other hand kinda off topic for this forum: I currently have the Galaxy Tab 2 10.1 from At&t and it has 4.0.4 firmware. Any word on it getting updated to 4.1.2 or 4.2.2 via Kies or OTA?
Click to expand...
Click to collapse
have the same problem here ! need help!
actually similar but not exact problem, I cannot get my Kies app store to sync downlaoded app to my note 2
Viper0580 said:
When I connect my Note II to my pc and launch Kies to sync and backup my info on my phone it says "Your device's current firmware version is not supported to update via Kies.
Current Firmware: PDA:MA4 / PHONE:MA4 / CSC:MA4 (ATT)
Is this correct on Kies or do I have a different firmware on my Note II? I have the factory firmware. The Only thing that I have updates on my Note II is when that Update patch was released via OTA. How do I get Kies to recognize my Phone's firmware?
Click to expand...
Click to collapse
This is normal. AT&T just pushed an OTA and Kies has yet to update with the new firmware version. I think it will get updated soon as UCAMA4 has just appeared on the SamMobile website.
http://www.sammobile.com/firmwares/
Edit: As of 4/6/13, Kies now reflects UCAMA4 as the latest firmware.
I recently bought and rooted my newish (bought used) galaxy note 2 and flashed jedi x 13, but I hate the 4.1.2 update to the phone. I have terrible battery life even with trickster mod plus it prevents me unlocking the phone to use internationally. So my question is since im no pro at this... if I downgrade the firmware from 4.1.2 to 4.1.1 with jedi x rom installed will it mess up the phone? Or cause any compatibility issues? Hate to bother people with questions that are probably no brainers but ive looked everywhere to see if jedi x 13 is compatible with the downgrade.
You'll be fine. ODIN flash stock 4.1.1 and boot into factory recovery when done and do a factory reset.
Sent from my SGH-T889 using xda premium
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Why you wanna downgrade, just use Odin thru the toolkit in the original development thread for note 2
Sent from my SGH-T889 using xda premium
UPDATE - firmware downgrade was a success but heres what to expect when doing so in case theres anyone else wanting to try this thats new to this kind of thing.
I flashed the firmware to the device using odin and then factory reset and wiped cache (through recovery by holding vol up home and power). If you dont do these two things and try to reboot the phone normally you will get stuck in a boot loop due to the phone trying to load both firmwares. After the wipe and phone is rebooted if your device was rooted it will no longer be so and you will have to reroot. I would expect anyone who is trying this to already know how to root your device. After rerooting and using clockworkmod to reinstall my jedi x 13 rom almost everything was working as it should. The only thing that is not functioning properly is my data connection. I unlocked the phone after downgrading through the special menu and put my sim in and calling and messaging is working A okay. The data issue is that it will not get my at&t 4g lte and the connection on the phone displays it changing from 4g to hspa+ to 3g all the time. If anyone knows why this is please let me know.
OmmNomNom said:
Why you wanna downgrade, just use Odin thru the toolkit in the original development thread for note 2
Sent from my SGH-T889 using xda premium
Click to expand...
Click to collapse
Because I was having a wifi issue with the 4.1.2 update. I could be out in the street from my house and still get full wifi signal, after getting the update I would only have maybe one bar of signal just outside on my back porch. And also for using the phone internationally since I have to constantly switch sims.
I have an unlocked AT&T Galaxy S3 but my new carrier is T-Mobile. My question is, is it safe to try and update the phone's software through the phone settings "Software Update"? This because the android version on the phone is 4.0.4 and I'll like to update it to a jellybeans. Any advises?
NB: The phone has been previously rooted.
you can make in recovery a full backup in case it will not be good, but I want to say let's go! F*ck a duck and try to fly!
Give it a shot, the worst it will do is tell you your phone is not supported. It won't flash a T-Mobile image or anything.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
You can do that or VIA KIES and it will update to the latest 4.1.1 from ATT. If the phone is unlocked it will not re-lock. You will just have to disable the ATT and Samsung bloatware.
yanngates said:
I have an unlocked AT&T Galaxy S3 but my new carrier is T-Mobile. My question is, is it safe to try and update the phone's software through the phone settings "Software Update"? This because the android version on the phone is 4.0.4 and I'll like to update it to a jellybeans. Any advises?
NB: The phone has been previously rooted.
Click to expand...
Click to collapse
If you do not want a rooted device, I highly suggest Kies as mentioned already just to be sure. However, if you are comfortable with being rooted, you can always ODIN the rooted AT&T Jellybean rom (do not odin T-Mobile). Your phone will remained unlocked.
Personally I'm running the 1700 mod on T-Mobile with cm10. It was a bit to set up, seeing I'm not using the nv backup way but it was well worth it. I have 3g in areas that were not refarmed yet and the phone is faster than hell. I would highly recommend this way and if you need help getting it working just ask.
Were you let out of your contract early too?
Sent from my Nexus 7 using XDA Premium HD app
Please read forum rules before posting
Questions and help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
I tried updating from AT&T server but it didn't work. I got a server's connection error. As suggested here, I also tried Kies but for some reason it doesn't recognize the phone. I tried it on windows, MacOX but nothing. I'm somehow new to this so I'm kind of scare to do it manually, but I think that's the only option left
yanngates said:
I tried updating from AT&T server but it didn't work. I got a server's connection error. As suggested here, I also tried Kies but for some reason it doesn't recognize the phone. I tried it on windows, MacOX but nothing. I'm somehow new to this so I'm kind of scare to do it manually, but I think that's the only option left
Click to expand...
Click to collapse
The server connection error is not surprising since you are not on AT&T. As far as Kies is concerned, this is most likely a driver issue. Fix the driver and you should be good to go. What version of windows did you use?
I'm using Windows XP and I downloaded, unistalled, redownloaded new drivers but when I plug in the phone it still says connecting endlessly. I have being struggling with Kies for almost 4 days now but it still doesn't recognize the phone. I think the last solution is to do it manually. I'll give it a try this week end.
My phone finally passed the one year mark - no more warranty now so naturally, it's time to root and have some fun. I got root and bought the latest CWM touch recovery and have it installed and functioning properly. However, when I try flashing the latest CM10.1, I get a status 7 error. I've read all kinds of things about the phone being classified as a d2can, not d2att and changing the build.prop or update script but haven't the slightest clue as to how to do it. All the threads I've searched vaguely say how the people bypassed this error and not how to do it. I never ran into this problem with my old Optimus G2X so this is foreign land to me.
So I have a Bell GS3 i747M running the latest (rooted) 4.12 i747MVLDMF1 update with CWM 6.0.3.1. I'm also running Windows 7 if that makes any difference.
If anyone can help me out I'd really appreciate it!
Thanks,
Spike
53Spike said:
My phone finally passed the one year mark - no more warranty now so naturally, it's time to root and have some fun. I got root and bought the latest CWM touch recovery and have it installed and functioning properly. However, when I try flashing the latest CM10.1, I get a status 7 error. I've read all kinds of things about the phone being classified as a d2can, not d2att and changing the build.prop or update script but haven't the slightest clue as to how to do it. All the threads I've searched vaguely say how the people bypassed this error and not how to do it. I never ran into this problem with my old Optimus G2X so this is foreign land to me.
So I have a Bell GS3 i747M running the latest (rooted) 4.12 i747MVLDMF1 update with CWM 6.0.3.1. I'm also running Windows 7 if that makes any difference.
If anyone can help me out I'd really appreciate it!
Thanks,
Spike
Click to expand...
Click to collapse
Hi there, just would like to direct you to the Q&A forum as this thread belongs there, just a heads up so you know where to find it when it get's moved by a forum moderator, so for next time now you know where this kind of post belongs
Have you updated to the latest bootloader? what was the last stock firmware you flashed in odin?
also to edit build.prop for newer users, easiest way would be to download rom toolbox and inside there is a feature for "build.prop" edit,
changed I747M to I747, d2can to d2att and d2uc to d2v1 in the first few lines of the build.prop then save and reboot. once you are rebooted update you're recovery to get a d2att recovery.
cheers
Please read forum rules before posting
Questions and help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Danvdh said:
Hi there, just would like to direct you to the Q&A forum as this thread belongs there, just a heads up so you know where to find it when it get's moved by a forum moderator, so for next time now you know where this kind of post belongs
Have you updated to the latest bootloader? what was the last stock firmware you flashed in odin?
also to edit build.prop for newer users, easiest way would be to download rom toolbox and inside there is a feature for "build.prop" edit,
changed I747M to I747, d2can to d2att and d2uc to d2v1 in the first few lines of the build.prop then save and reboot. once you are rebooted update you're recovery to get a d2att recovery.
cheers
Click to expand...
Click to collapse
Thanks for telling me about the proper forum location and I apologize for a late reply, work got hectic the last couple of days, but alas, the long weekend is ahead!
I've updated my phone to the most recent Bell stock build so I'd assume the bootloader is recent as well. I then flashed the most recent stock ROM with root injected from here: http://forum.xda-developers.com/showthread.php?t=1739426 so build I747MVLDMF1.
With regards to the build.prop changes, I selected the d2att CWM recovery when I went to install one so I figured installing the d2att recovery would do the same as changing the build.prop parameters then installing the d2att recovery, no?
Thanks,
Spike
I just want to bump this in case anyone can help me out.
I have a s3 currently running on 4.0.4.. (this was just used as a backup phone, now since my iphone is broken i have to use this one)
I tried to update OTA but everytime I check for an update, my phone always says its up to date. So is there a manual way I can perform this update? Can someone please refer me to a thread if this question has already been answered? It would gladly be appreciated. Samsung tech support wasn't any help and the people at best buy want 200.00 just to update which is bull.
You have a few options. You can update through kies, but I personally never liked kies so couldn't help much there.
Or you can flash the firmware via Odin. You can get up to 4.1.2 from http://sammobile.com/firmwares
Or you can get 4.3 firmware from enewman17 in the development section. If you want to update all the way to 4.4.2, follow his how to update thread in the General section.