Related
I haven't found this mentioned elsewhere on the forum but this afternoon I was notified of a KJ4/KJ4/KJ4(DBT) to KK9/KK5/KK9(DBT) upgrade by Kies.
(I'm posting here because it is not a "ROM Development" post.)
Based on feedback in the thread I believe the update only applies to phones sourced from Germany, such as those supplied by amazon.de. There will be a (DBT) suffix after the KK4 bit
I'm afraid I can't answer questions about the contents of the update or provide any technical advice about installation. I don't have the answers. I'm just bringing the availability of the update to people's attention. Hopefully, if you do have questions, someone with more knowledge of these things will chime in. This is my first Samsung phone and I've never been through the Kies update procedure before.
FWIW I'm doing a full Titanium Backup of everything and also a backup in Kies. I have not yet applied the update. I did try to do a Nandroid backup, but without installing CWM the option to backup is not available, and apart from rooting with Zerglings I do not want to mess with the phone beyond that.
Thanks, updated my EU Note to 2.3.6 and KK9 from 2.3.5 and KJ4.
P.S. lost root. Going to do a factory reset, root and reinstall my apps with titanium backup.
P.P.S. re-rooted the Note using Easy Rooting Toolkit, can't install CWM yet since there is not a version for KK9 yet.
When I connect to Kies I'm getting this:
Why does Kies say: Your device does not support software upgrading via Kies?
My note is stock
this is my 1st Android phone, do I need to backup before update if it's available from system update? Thanks
System update on the phone did not find any new update for me.
You need to connect the Note to Kies and a pop up box should come up to let you know there is an update, the whole process was around 15 mins in my case.
I think Kies will auto backup your phone before install the new update, and all your apps and files should be there when the update is done as this update does not wipe your device.
Just did the update, it shows now 2.3.6 . Le't see the improvements
Steelduines said:
When I connect to Kies I'm getting this:
Why does Kies say: Your device does not support software upgrading via Kies?
My note is stock
Click to expand...
Click to collapse
Have you changed your product code to something other than it came stock? (i.e. have you changed CSC manually).
If you have - you will need to change it back to the original one and then Kies will let you update.
Let us know improvement you've noticed so far...
My phone is on PDA:KK2 / PHONE:KK1 / CSC:KK2 (TTT) and won't update...
clubtech said:
Have you changed your product code to something other than it came stock? (i.e. have you changed CSC manually).
If you have - you will need to change it back to the original one and then Kies will let you update.
Click to expand...
Click to collapse
Nope I didn't change anything on my Note it's completely stock....
Edit:
N7000XXKJ4
CSC:OXAKJ4
My upgrade is complete. I didn't time it but it seemed to proceed very slowly - I can't imagine what it was doing that could take so long - and then timed out part way through the process. I restarted from the beginning and it all went through OK, but again very slowly.
I could not get Kies to backup my data prior to the upgrade as it kept giving an error. I don't know whether that was anything to do with having rooted the phone, so I unrooted as a precaution and decided just to get on with the upgrade.
I didn't unroot, but normally, i lose root after flashing.
After that rooted with the simple zergRush method, working like a charm.
What version of kies were you using
I am not getting the update.
I get what I've attached in Kies 2.1.0.11095_121.
I bought my Note from Negrielectronics, I think it's Polish, but I've left it stock.
Think its country specific?
I am not sure if it's country specific.
Can anybody who has received the update say whether or not it makes the UI less laggy?
Steelduines said:
When I connect to Kies I'm getting this:
Why does Kies say: Your device does not support software upgrading via Kies?
My note is stock
Click to expand...
Click to collapse
I have the same problem the other day when I tried it with mine.....
Is yours Polish Version? Mine is, and I got it from handtec....
Will try it again soon, and if it doesn't work...I will have to make a complaint to handtec!!!
virtuatony said:
I am not getting the update.
I get what I've attached in Kies 2.1.0.11095_121.
I bought my Note from Negrielectronics, I think it's Polish, but I've left it stock.
Click to expand...
Click to collapse
I dont know if it's about the country where you are. I've read in the one development forum thread that you might have to do a factory reset. Many people reply that it worked for them...
rdosti said:
What version of kies were you using
Click to expand...
Click to collapse
Kies 2.1.0.11095_121.
I don't know how Samsung has all this organised, but my Note is a European model from amazon.de and I am running Kies from within the UK.
My Note was on KJ4/4/4. If your Note is on some other ROM version at the moment then I doubt very much that you will get the update to KK9/5/9.
I did not have to perform a factory wipe before or after the upgrade. As far as I can tell everything is intact but now I am on 2.3.6 instead of 2.3.5.
hmm, kies is still telling me KJ4 is the latest. polish version here.
stock rom untouched,
PDA: KJ4 PHONE: KJ4 CSC: KJ3 (PLS)
Just a "heads up", I just did the OTA update to I9300XXEMG4 (4.1.2) - United Kingdom (BTU) on my SIII. Working perfectly before the update on the previous most recent stock.
After the OTA update, the phone gets as far as the Samsung boot animation and goes no further. Factory reset via recovery menu but it makes no difference. The phone has never been modified in any way.
It's going off for repair/replacement back to Samsung UK but as it might happen to others out there, I thought it was worth mentioning.
My gut feeling is that this is a symptom of SDS, showing up only at update time.
Sigh.....
READ
*** ATTENTION *** STOCK FIRMWARE I9300XXEMG4 -> Changes EFS Folder
If it boots into download mode copy what it says and post,, my guess is this is kies being it's usual self, in which case if everything is ok in download mode then download the Rom and flash with Odin
The fact that it gets as far as it does means it's not broken and it's not the result of the XXEMG4 firmware at all. STop this fear mongering.
However, since you're totally unmodified you do right in returning ti to Samsung.
It was an OTA update, not using Kies...
ODIN MODE
PRODUCT NAME: GT-I9300
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
zardoz99 said:
It was an OTA update, not using Kies...
ODIN MODE
PRODUCT NAME: GT-I9300
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
Click to expand...
Click to collapse
All is good there, so you have a choice of returning it to Samsung or flash the Rom with Odin
Again, doesn't mean the update broken your device, not when many of us are installing the Kies version with Odin just fine :/
I'm not having any problems with EMG4, flashed with mobile Odin just fine including root.
I also don't think that Samsung will release the MG4 as a broken firmware knowing that it can be flashed/OTA'ed by masses who owns an international variant of the S3.
My guess is your download of the update got corrupted while in the middle of the file transfer. And the fact that your device can still go to download mode doesn't mean it's bricked.
KIES updated my S3 to EMG4 yesterday no problems at all. Unfortunately it still doesn't like USB chargers, like the ones provided by Samsung! Probably just bad luck. You're quite right to send it back.
zardoz99 said:
Just a "heads up", I just did the OTA update to I9300XXEMG4 (4.1.2) - United Kingdom (BTU) on my SIII. Working perfectly before the update on the previous most recent stock.
After the OTA update, the phone gets as far as the Samsung boot animation and goes no further. Factory reset via recovery menu but it makes no difference. The phone has never been modified in any way.
It's going off for repair/replacement back to Samsung UK but as it might happen to others out there, I thought it was worth mentioning.
My gut feeling is that this is a symptom of SDS, showing up only at update time.
Sigh.....
Click to expand...
Click to collapse
It's not SDS for sure, had the same problem when I war trying to go back to EME2 of WANAM.
EFS backup is required perior dealing with this update.
update to emg4
zardoz99 said:
Just a "heads up", I just did the OTA update to I9300XXEMG4 (4.1.2) - United Kingdom (BTU) on my SIII. Working perfectly before the update on the previous most recent stock.
After the OTA update, the phone gets as far as the Samsung boot animation and goes no further. Factory reset via recovery menu but it makes no difference. The phone has never been modified in any way.
It's going off for repair/replacement back to Samsung UK but as it might happen to others out there, I thought it was worth mentioning.
My gut feeling is that this is a symptom of SDS, showing up only at update time.
Sigh.....
Click to expand...
Click to collapse
Dude,
For the heck of it I flashed emg4 firmware using Odin Mobile. No issues whatsoever. I'd use odin on the desktop. If the device is still bricked, use odin on the desktop to dump the firmware. you can try an older firmware for your own comfort. It's definitely something with your Kies.
Flashed mine this morning OTA. Working perfectly.
Sent from my GT-I9300 using xda premium
It's definitely going back under warranty. Samsung are sending a return envelope for it.
It's possible that I'm just unlucky as my wife's S3 updated just fine at exactly the same time. "adb" cannot see it and as it's still under the two year warranty, I'll let Samsung figure it out. Glad it wasn't hers that died.. Life would be "interesting".
Maybe they'll give me a nice 32GB version as a replacement
I'm more than a little concerned that this update messes about with the EFS information. Any idea why?
zardoz99 said:
It's definitely going back under warranty. Samsung are sending a return envelope for it.
It's possible that I'm just unlucky as my wife's S3 updated just fine at exactly the same time. "adb" cannot see it and as it's still under the two year warranty, I'll let Samsung figure it out. Glad it wasn't hers that died.. Life would be "interesting".
Maybe they'll give me a nice 32GB version as a replacement
I'm more than a little concerned that this update messes about with the EFS information. Any idea why?
Click to expand...
Click to collapse
know how it killed your S3 did you get that encryption unsuccessful message?
I got nothing... It just never gets beyond the Samsung boot animation.
zardoz99 said:
I got nothing... It just never gets beyond the Samsung boot animation.
Click to expand...
Click to collapse
ah well i got that encryption thing and now i don't go past the samsung boot animation either.
what should i say to samsung for them to RMA it?
Contact Samsung support by phone and tell them what happened. That's all I did. I explained that I had tried the normal "customer" recovery methods (factory reset etc) and there was no argument at all. Because it's my main phone and I need it to be reliable for work, it was completely unmodified, so there should be no problems.
They just wanted my details, the phone serial/IMEI and the purchase date.
Was your phone encrypted? I had decided not to do that with mine as it's a significant performance hit.
Please change the title of the thread to something more factual.
XXEMG4 - services 4 files
This is official factory 4-files firmware XXEMG4 for emergency recovery . ( TORRENT ).
Update for Galaxy Note 8.0 LTE (GT-N5120) are out today
Model: GT-N5120
Country: United Kingdom
Version: Android 4.2.2
Changelist: 1210063
Build date: Thu, 01 Aug 2013 12:21:19 +0000
Product Code: BTU
PDA: N5120XXCMH1
CSC: N5120BTUCMH1
MODEM: N5120XXCMG7
Get it Here
Changelist is the same as the former UK 4.2.2 release, so no idea what changed really.
Will download, update and report back
Slipurson said:
Update for Galaxy Note 8.0 LTE (GT-N5120) are out today
Model: GT-N5120
Country: United Kingdom
Version: Android 4.2.2
Changelist: 1210063
Build date: Thu, 01 Aug 2013 12:21:19 +0000
Product Code: BTU
PDA: N5120XXCMH1
CSC: N5120BTUCMH1
MODEM: N5120XXCMG7
Get it Here
Changelist is the same as the former UK 4.2.2 release, so no idea what changed really.
Will download, update and report back
Click to expand...
Click to collapse
Any update on what the differance is over the previous release?
If this ROM causes the S-Pen to have an offset, please let us know here:
4.2.2 Update S-Pen Inaccuracy Thread
KTM690 said:
Any update on what the differance is over the previous release?
Click to expand...
Click to collapse
I cant find any differences at all actually, the offset for the S-Pen is there still and everything else works just as it did with the previous 4.2.2
CafeKampuchia said:
If this ROM causes the S-Pen to have an offset, please let us know here:
4.2.2 Update S-Pen Inaccuracy Thread
Click to expand...
Click to collapse
Ill post my findings in the thread.
I am assuming you are talking about the browser bug? That was an issue with chrome's zoom being inaccurate on, frankly, every Galaxy Note up until now. They fixed it recently.
Sent from my SAMSUNG-SGH-I467 using xda premium
'H+' vs 'H' Icon
Hi
Just flashed this ROM on my HK Note N5120 LTE (CSC Was TGY). The device came from Panamoz.com as I was struggling to buy the LTE version sim free in the UK for reasonable money, and Kies was not offering to upgrade the stock 4.1.2 firmware to 4.2.2.
Used this method: http://forum.xda-developers.com/showpost.php?p=44241666&postcount=4
All worked fine, Answered 'No' when asked about making CWM recovery permanent. The CSC became BTU (UK) after the flash. CWM recovery was replaced with stock during the flash.
Since I am in the UK, I flashed the modem files that came with the ROM, and still get 4G. I have the same issue as everyone else regarding the S-Pen offset - probably not bad enough to flash back to 4.1.2 for me, but hopefully Samsung will fix.
My main issue is that compared to 4.1.2, I hardly ever see the device show 'H+', only 'H'. I travel the same route on the train daily, and now, I see 'H+' 10% of the time rather than 90% of the time. My other device on the same network still shows H+.
Maybe others have seen my 'H' vs 'H+' issue?
Does this device support DC-HSPA?? I recall that with the S3 and Note2, one gained DC-HSPA+42 (so called 3.75G theoretical max 42Mbps), when one bought the LTE version of the phone. The non LTE versions only had HSPA+21. Reason I am asking is I am wondering if the 'H+' now only shows for DC-HSPA rather than for HSPA+21 ??
Tempted to flash the old modem files again, see if my H+ returns to normal operation - and of course to see if its any faster.
My device is still rooted with the flash counter == 2, and It does still appear to be recognized by kies when connected to the PC. Time will tell whether I will get updates via Kies still. If not then maybe I will need to use Triangle to reset the flash counter, and then do a full unroot.
Nigel
veletron said:
Hi
Just flashed this ROM on my HK Note N5120 LTE (CSC Was TGY). The device came from Panamoz.com as I was struggling to buy the LTE version sim free in the UK for reasonable money, and Kies was not offering to upgrade the stock 4.1.2 firmware to 4.2.2.
Used this method: http://forum.xda-developers.com/showpost.php?p=44241666&postcount=4
All worked fine, Answered 'No' when asked about making CWM recovery permanent. The CSC became BTU (UK) after the flash. CWM recovery was replaced with stock during the flash.
Since I am in the UK, I flashed the modem files that came with the ROM, and still get 4G. I have the same issue as everyone else regarding the S-Pen offset - probably not bad enough to flash back to 4.1.2 for me, but hopefully Samsung will fix.
My main issue is that compared to 4.1.2, I hardly ever see the device show 'H+', only 'H'. I travel the same route on the train daily, and now, I see 'H+' 10% of the time rather than 90% of the time. My other device on the same network still shows H+.
Maybe others have seen my 'H' vs 'H+' issue?
Does this device support DC-HSPA?? I recall that with the S3 and Note2, one gained DC-HSPA+42 (so called 3.75G theoretical max 42Mbps), when one bought the LTE version of the phone. The non LTE versions only had HSPA+21. Reason I am asking is I am wondering if the 'H+' now only shows for DC-HSPA rather than for HSPA+21 ??
Tempted to flash the old modem files again, see if my H+ returns to normal operation - and of course to see if its any faster.
My device is still rooted with the flash counter == 2, and It does still appear to be recognized by kies when connected to the PC. Time will tell whether I will get updates via Kies still. If not then maybe I will need to use Triangle to reset the flash counter, and then do a full unroot.
Nigel
Click to expand...
Click to collapse
Just got mine from the same place. Your post has helped me with some questions I had. Thanks.:good:
No OTA For me
So, the next stage was to run Triangle away, which worked fine (counter reset to 'No'). Just be brave and accept the big red warning.
Following on from that, I unrooted using the unroot option in Super User app that was installed by chainfire's 'auto root'.
This worked too, and I confirmed root gone. After a reboot, I reconnected to Kies, to check that it recognized the firmware on the device as the 'latest'. It was.
I then tried the 'Software Update' option under Settings->about device, unfortunately, this no longer works it just says 'connecting to server' forever and eventually comes up with a message: 'your device has been modified, software updates are not available'. So No OTA for me.
Any idea how to get OTA working again??
Here is the screenshot from the downloading screen, showing 'official' for all the firmwares on the device. Could it have something to do with the CSC? (TGY on 4.1.2 and BTU on 4.2.2) ?
http://photos.veletron.com/index.php/album151/P1070688
If I goto Settings-->About Device-->Status, and wait an age while the 'Device Status' field updates, it reports 'custom'. I guess this is why, but how come given that the 'download' screen reports as per the above screen shot?!
Prior to running Triangle Away, and unrooting, the OTA check on the device, span for a while before reporting no new updates available.
Nigel
veletron said:
Hi
Just flashed this ROM on my HK Note N5120 LTE (CSC Was TGY). The device came from Panamoz.com as I was struggling to buy the LTE version sim free in the UK for reasonable money, and Kies was not offering to upgrade the stock 4.1.2 firmware to 4.2.2.
Used this method: http://forum.xda-developers.com/showpost.php?p=44241666&postcount=4
All worked fine, Answered 'No' when asked about making CWM recovery permanent. The CSC became BTU (UK) after the flash. CWM recovery was replaced with stock during the flash.
Since I am in the UK, I flashed the modem files that came with the ROM, and still get 4G. I have the same issue as everyone else regarding the S-Pen offset - probably not bad enough to flash back to 4.1.2 for me, but hopefully Samsung will fix.
My main issue is that compared to 4.1.2, I hardly ever see the device show 'H+', only 'H'. I travel the same route on the train daily, and now, I see 'H+' 10% of the time rather than 90% of the time. My other device on the same network still shows H+.
Maybe others have seen my 'H' vs 'H+' issue?
Does this device support DC-HSPA?? I recall that with the S3 and Note2, one gained DC-HSPA+42 (so called 3.75G theoretical max 42Mbps), when one bought the LTE version of the phone. The non LTE versions only had HSPA+21. Reason I am asking is I am wondering if the 'H+' now only shows for DC-HSPA rather than for HSPA+21 ??
Tempted to flash the old modem files again, see if my H+ returns to normal operation - and of course to see if its any faster.
My device is still rooted with the flash counter == 2, and It does still appear to be recognized by kies when connected to the PC. Time will tell whether I will get updates via Kies still. If not then maybe I will need to use Triangle to reset the flash counter, and then do a full unroot.
Nigel
Click to expand...
Click to collapse
I can not say anything about the OTAupdates since I never use Kies to update, but as for the modem, I am running the "old" 4.1.2 modem and it is working well for me, tho I have not compared my note now and before in regards to how ofteni see H+ or just H, most often I see the 4G icon where I usually hang out.
But I would try the 4.1.2 modem for your region and see if it changes anything.
Sent from Galaxy no. N5120 via the LTE-network
Got mine updated to 4.2.2 yesterday.
Not sure why but my battery life seemed to have taken a hit since upgrading.
On 4.1.2 i used to be able to last a day easily with about 30 - 40% left each day (7am till 9pm). after updating to 4.2.2 I am down to 30% in 5 hrs. Tab gets hotter too. Anyone experience the same issue?
I am back on 4.1.2 for now. Everything's good again.
thanks man for update.
Just for info
After the update to 4.2.2 Mh1 by flashing the firmware here, I never got OTA again (says device status custom). Stock rom and flash counter zero. I was however able to update to MH2 via kies. I am still told device status custom!
No difference for me re pen pointer offset on MH1/MH2 not sure Samsung will ever bother to fix this.
My device now BTU but it started as Hong Kong. I suspect this is why it reckons it's "custom".
Nigel
veletron said:
Just for info
After the update to 4.2.2 Mh1 by flashing the firmware here, I never got OTA again (says device status custom). Stock rom and flash counter zero. I was however able to update to MH2 via kies. I am still told device status custom!
No difference for me re pen pointer offset on MH1/MH2 not sure Samsung will ever bother to fix this.
My device now BTU but it started as Hong Kong. I suspect this is why it reckons it's "custom".
Nigel
Click to expand...
Click to collapse
I have the same device but not the same problem. I also updated to MH2 via Odin and my status is normal. The offset for me is much better than previous, and I have no problem with the battery lasting more than a day using WiFi and push mail along with the normal use. However although recognized by Kies it would not update, I recon because of the CSC.
craylim said:
Not sure why but my battery life seemed to have taken a hit since upgrading.
On 4.1.2 i used to be able to last a day easily with about 30 - 40% left each day (7am till 9pm). after updating to 4.2.2 I am down to 30% in 5 hrs. Tab gets hotter too. Anyone experience the same issue?
I am back on 4.1.2 for now. Everything's good again.
Click to expand...
Click to collapse
Sent from my GT-N5120 using XDA Premium HD app
Battery seem to drain faster since I upgraded to 4.2.2
Multi Window
Hey,
I've update my rom on my 5120 to the MH2 and still having problem with multi window greyed out in the setting>display
Has anybody else have this problem?
Is they any way to fix it?
I upgraded the rom using the odin version 1.85 had the tick in auto reboot and F. Rest time and I ticked PDA and put the md5 file on the pda line where I placed the tick is that all correct or should I've used a different version?
Please can anybody help me.
Thanks
Gigino
THANK YOU! THANK YOU! THAAAAAAAANK YOOOOOOOU! (if it didn't look and/or feel weird, I'd kiss you! *LOL* I wouldn't it was a joke)
BUT you saved my stupid self from self pity. You see, I didn't realize - until too late - that there were 3 versions of this device, and attempted to install a 5110 ROM. That caused me 5 DAYS of hell until I cam across this, and voila! I got my tablet back. So again - TANK YOU THANK YOU THANK YOU!
One Note: Baseband I467MVLAMG2 and Build Number: JDQ39.N5120XXCMH2 (not 1)
_Allan_ said:
THANK YOU! THANK YOU! THAAAAAAAANK YOOOOOOOU! (if it didn't look and/or feel weird, I'd kiss you! *LOL* I wouldn't it was a joke)
BUT you saved my stupid self from self pity. You see, I didn't realize - until too late - that there were 3 versions of this device, and attempted to install a 5110 ROM. That caused me 5 DAYS of hell until I cam across this, and voila! I got my tablet back. So again - TANK YOU THANK YOU THANK YOU!
One Note: Baseband I467MVLAMG2 and Build Number: JDQ39.N5120XXCMH2 (not 1)
Click to expand...
Click to collapse
Great post. I feel your joy
THere is a newer version. Does anyone know how we can go from JDQ39.N5120XXCMH2 to the new JDQ39.N5120XXCMI2 version?
My phone also says custom like Nigels problem above, I am having same problem that he was having when he first went to 4.2.2 from 4.2.1... I'm currently on 4.2.2 trying to go to the new CMI2.
CCJ22 said:
THere is a newer version. Does anyone know how we can go from JDQ39.N5120XXCMH2 to the new JDQ39.N5120XXCMI2 version?
My phone also says custom like Nigels problem above, I am having same problem.
Click to expand...
Click to collapse
I downloaded the CMI2 version from samsmobile site. It was a KIES file extracted the file and using mobile odin flashed it to my device. All working fine.:good:
Hi All,
I have used CF-Auto-Root when I first got my phone about 3 months ago and rooted successfully and it changed my device status from Official to custom and therefore I was never able to check for OTA or install them.
I have also tried CF's Triangle Away at that time but it never set the status back to Official until last night when I installed the latest TA version 3.05 and this had worked it's magic and my phone status is now back to Official and I found an available OTA and downloaded it but I have not installed it yet. Why? Because I am almost sure I will lose root after installing the OTA update and I am not sure if I am able to re-root it again as I have heard and read that Samsung is trying to lock things down to make it harder for us to play around with our phones.
I My current build number is JDQ39.I9505XXUAMDE so if I am not mistaken, that means I am on firmware XXUAMDE.
The phone does not tell me any info after it completed the OTA download about this upfate apart "Stability Improvement"
My questions are:
1. How can I tell if this new firmware is not going to lock things down?
2. Would I be able to easily re-root after completing the firmware update?
I just plugged in my phone to my computer and Samsung Kies is telling me this:
Current firmware version : PDA:MDE / PHONE:MD8 / CSC:MD8 (VAU)
Latest firmware version : PDA:MG4 / PHONE:MG1 / CSC:MG1 (VAU)
and asking me if I want to upgrade.
Can someone help me answer my questions and clear this for me?
Sorry for all these questions but I am just a little worried this update will be a bad move and I don't want to regret it.
Thanking you in advance for putting up with me and my apologies if some of these questions are repeated or dumb.
AFAIK, MG4/MG1 is not sooo new, and it's still not afected by the 'knox' bootloader thing.
I upgraded to MGA (AMN) some 3 weeks ago, using KIES, temporarylly lost root, but flashet CF Auto Root again, and .... voila! good to go again.
.... oh yes, I had to install supersu again from play store (somehow it was rooted, but the application was not there).
Hope that can help you!
Bak
Thanks Bak for the info.
I was doing some more googling and I came across these 2 pages:
http://www.ibtimes.co.uk/articles/4...ial-android422-xxuamde-jellybean-firmware.htm
http://www.ibtimes.co.uk/articles/4...roid422-xxuamdn-jellybean-official-update.htm
There is something wrong here as my phone is I9505 and it came with the amde unlike what is suggesting that official firmware for I9505 is amdn.
I got my phone from Voda Australia hence the VAU.
If I am reading this correctly:
Current firmware version : PDA:MDE / PHONE:MD8 / CSC:MD8 (VAU)
Latest firmware version : PDA:MG4 / PHONE:MG1 / CSC:MG1 (VAU)
Then after the OTA update then I should be on XXUAMG4 ? I really don't get this whole PDA / PHONE / CSC variables.
I am just tempted to install it and thinking if anything goes wrong or not to my liking then I can use the link I provided above to flash my phone with the official xxaumdn and this does not have the "knox" bootloader thing?
good decision mate! dont flash to the latest MH8 firmware cuz it locks out your fone.
sadly i've flashed mine without reading around. little did in know, MH8 includes knox with locked my phone.
right now i'm having root problems. tried using CF 1.60 the latest one.. which they said can bypass the knoxx thing. we'll i'm still having problems getting root access.. IDK why.
just wait and see. a dev might come up with some work around this KNOX bootloader thing
Saturn007 said:
Thanks Bak for the info.
I was doing some more googling and I came across these 2 pages:
http://www.ibtimes.co.uk/articles/4...ial-android422-xxuamde-jellybean-firmware.htm
http://www.ibtimes.co.uk/articles/4...roid422-xxuamdn-jellybean-official-update.htm
There is something wrong here as my phone is I9505 and it came with the amde unlike what is suggesting that official firmware for I9505 is amdn.
I got my phone from Voda Australia hence the VAU.
If I am reading this correctly:
Current firmware version : PDA:MDE / PHONE:MD8 / CSC:MD8 (VAU)
Latest firmware version : PDA:MG4 / PHONE:MG1 / CSC:MG1 (VAU)
Then after the OTA update then I should be on XXUAMG4 ? I really don't get this whole PDA / PHONE / CSC variables.
I am just tempted to install it and thinking if anything goes wrong or not to my liking then I can use the link I provided above to flash my phone with the official xxaumdn and this does not have the "knox" bootloader thing?
Click to expand...
Click to collapse
Just checked with www.samfirmware.com
If you select the 'check your firmware', you'll see that the last version for i9505 and Australia VAU (vodaphone) is PDA:MG4 / PHONE:MG1 / CSC:MG1
So your carrier (vodaphone) hasn't released the MHx version yet (versions MHx hsve the knox thing)
PDA / PHONE / CSC are different pieces of the software/firmware, and may have different releases (you can even play with different ones, for instance, a diferent PHONE to be able to sim unlock, etc....)
If I was you, I'd let KIES do the update (it's the safest, together with the OTA), and re-root it.
Good luck
Bak
Thanks Bak. I upgraded over the weekend and re-rooted it and all is back to normal now.
I even got Triangleaway to reset counter and back to official status.
Thanks for all your info.
Hi
Picked up an S5 after years of iPhones, Which i bought from the three store in the UK.
After installing a few apps i started to get error 24 installing netflix. I didnt fancy doing a factory reset so i routed my phone to use a root browser to remove the temp files which resolved my issue (but of course i still had to do a factory reset) However i didn't realise that android confirms if its official or not and then doesn't receive OTA updates.
I'm not much into messing with releases these days so i downloaded the stock UK firmware (NCE) from sammobile and it now says official after flashing it.
However i notice that there is an OTA update out today (NC2) which i'm not getting when i check for updates (the message says latest update installed).
Is this simply a case of the update not having rolled out to everyone yet or does the update checker use the serial number of my phone to check that it should be on the H3G UK firmware rather than the stock UK firmware? Kies also states the firmware is up to date.
Thanks for any advice
Scottw1975 said:
Hi
Picked up an S5 after years of iPhones, Which i bought from the three store in the UK.
After installing a few apps i started to get error 24 installing netflix. I didnt fancy doing a factory reset so i routed my phone to use a root browser to remove the temp files which resolved my issue (but of course i still had to do a factory reset) However i didn't realise that android confirms if its official or not and then doesn't receive OTA updates.
I'm not much into messing with releases these days so i downloaded the stock UK firmware (NCE) from sammobile and it now says official after flashing it.
However i notice that there is an OTA update out today (NC2) which i'm not getting when i check for updates (the message says latest update installed).
Is this simply a case of the update not having rolled out to everyone yet or does the update checker use the serial number of my phone to check that it should be on the H3G UK firmware rather than the stock UK firmware? Kies also states the firmware is up to date.
Thanks for any advice
Click to expand...
Click to collapse
Rather than waiting for ota would I just be as well flashing the new stock uk firmware through Odin?