Database Develop

[Q] Kies Not Showing the Newest Open European Firmware for my Note

I recently purchased a Galaxy Note (Unlocked) and am loving the device. I was reading online that there was a newer open european firmware (LA3) but was perplexed as my phone was saying there are no upgrades for it. I installed Kies (the UK version) and it updated it's self to 2.2 yet it still does not show any newer firmware than what is on my phone (KKA).
Is there a way to force Kies to let me update? or am I missing a step (I never did create a samsung account).
Thank you in advance...

Hi there,
I also recently purchased a Note, and have been spending FAAAR tooo much time lurking on this forum trying to work out whats what with rooting/roming and all things GNote.
Fairly new to all this android malarky and tbh i'm kinda just responding to your question as a way to clarify what, i have, thus far, gleaned from by lurksome xda ways! And as an attempt to stop lurking so much and try and give back some of the understanding xda has given me.
Your question is something I was also rather confused by, but from what I understand - It seems that Samsung rolls out OTA and Kies updates to phones with different CSC codes at different times.
I think it is only the German (DBT) phone which has had the latest LB1 update. I know that my XEU phone is also still on KKA, with no ota or kies updates available.
From what I understand, the way one gets the updates without rooting is through flashing them with a Windows app called PC Odin with the phone in download mode.
Or via rooting your KKA rom
http://forum.xda-developers.com/showthread.php?t=1329360
and then flashing the updated firmware with either Mobile Odin or Clockwork Mod.
In all cases I believe you must download the firmware from either the sammobile site or http://forum.xda-developers.com/showthread.php?t=1424997
If any (or all!) of that is totally wrong - please someone with greater experience wade in and put me straight, but I just thought that seeing as no-one else had responded - i'd try and make something of all the hrs i've spent lurking on here since i got this phone
Anyhow I'm sure if you just follow the links i've posted to the brilliant work of Dr Ketan - you won't go far wrong
Personally, I've not actually put any of this to the test yet - wanna make sure I really do know my arse from my elbow or in this case - my dalvik from my build.prop before I go messing with a £500 phone....

knowayback said:
Hi there,
I also recently purchased a Note, and have been spending FAAAR tooo much time lurking on this forum trying to work out whats what with rooting/roming and all things GNote.
Fairly new to all this android malarky and tbh i'm kinda just responding to your question as a way to clarify what, i have, thus far, gleaned from by lurksome xda ways! And as an attempt to stop lurking so much and try and give back some of the understanding xda has given me.
Your question is something I was also rather confused by, but from what I understand - It seems that Samsung rolls out OTA and Kies updates to phones with different CSC codes at different times.
I think it is only the German (DBT) phone which has had the latest LB1 update. I know that my XEU phone is also still on KKA, with no ota or kies updates available.
From what I understand, the way one gets the updates without rooting is through flashing them with a Windows app called PC Odin with the phone in download mode.
Or via rooting your KKA rom
http://forum.xda-developers.com/showthread.php?t=1329360
and then flashing the updated firmware with either Mobile Odin or Clockwork Mod.
In all cases I believe you must download the firmware from either the sammobile site or http://forum.xda-developers.com/showthread.php?t=1424997
If any (or all!) of that is totally wrong - please someone with greater experience wade in and put me straight, but I just thought that seeing as no-one else had responded - i'd try and make something of all the hrs i've spent lurking on here since i got this phone
Anyhow I'm sure if you just follow the links i've posted to the brilliant work of Dr Ketan - you won't go far wrong
Personally, I've not actually put any of this to the test yet - wanna make sure I really do know my arse from my elbow or in this case - my dalvik from my build.prop before I go messing with a £500 phone....
Click to expand...
Click to collapse
I appreciate the help to answer your question you are in part correct (from what I can gather). Samsung does issue updates based on CSC codes and there is nothing for the UK CSC code. However they also release what is called open updates. Meaning any carrier in a given country can use a open update for that country. Beyond that they release what is called open European updates that any unlocked phone in Europe can use.
My question is the latest open European update is LXA or LLA or something like that which is farther along than the KK5 I am on. Since it is open European I should be able to update to it I would think. There could be something to the fact that the UK is considered part of the EU so it might not fall under even an open European release and if that is the case than so be it.
I am just trying to find out why my unlocked international version of the note can not seem to update to the latest open European update

Ok, so from the sounds of it - i think your definitely better informed than me on Samsung update protocol
Haven't heard any of that before. I was under the impression that the XEU code was the unlocked open euro code....
Anyway, just thought i'd let u know that i took the plunge today - deciding that I trusted XDA more than Samsung to update my phone
Rooted my stock KKA rom using dr ketans posts as my guide, then flashed the stock LB1 firmware and have since flashed Franco's kernel.....all seems well so far
Although one thing i did notice is that my Antutu score was significantly lower after flashing Lb1, but before flashing Franco's kernel (haven't tested since)....
Anyway good luck waiting for an official update - in my limited experience - I wouldn't hold your breath waiting for OEM's to issue OTA updates...

Valdeck said:
I am just trying to find out why my unlocked international version of the note can not seem to update to the latest open European update
Click to expand...
Click to collapse
This is cool. But how to find whether my phone is locked or not?
And what about if we try to involve the Samsung support on this question? I'm also stuck with kk5 and i'm also in Europe.

Spo0f said:
This is cool. But how to find whether my phone is locked or not?
And what about if we try to involve the Samsung support on this question? I'm also stuck with kk5 and i'm also in Europe.
Click to expand...
Click to collapse
If you want to know what region your phone is from plug it into the computer after you have installed samsung kies. Once you do if you look at the screen for your phone you will see three sets of letters and numbers. The last one in the string will have your CSC once you get that do a google for where it is from.
If you are on kk5 like me then you probably have a UK code.
An phone is unlocked by default when you import it from Europe as they use a different model for cell carriers than we do in the states.

The simple way to get the latest updates is....change your CSC with *#272*imei# in the dialer pad to the lastest update ( csc)! You don't need root or odin or mobile odin. Just change your country code. This will wipe your phone...but after restart you will get a promt to update your software as soo. As wou are connected to a wifi. There are many post about it...the csc change is described in sgs2 foruns and all over the net. About the country code, please visit sammobile.com and in firmware section you will find detailed info about those codes.
P.S. My note was originaly in XEH ( open Hungary), I'm from Romania so I changed my CSC to Open Germay (DBT-debitel) and after restart i got 2 consecutive updates.
Hope to help, sorry for my bad english
Sent from my GT-N7000 using xda premium

The easiest way to get updates is via XDA. Download PC Odin, and choose whatever Rom you fancy from the first sticky thread in Note development.

No phone signal

Hey everyone i have had massive problems with the IMEI on my i9000 finally managed to flash back to stock ROM but im still getting no signal. The IMEI is fine and i have a backup of the efs folder saved. What files do i need in this folder as i will delete all of the contents then start again.
Thanks

If your still getting no signal but are not getting "No Service" then either the modem you flashed in the stock ROM is utter pants for specific handset so trying flashing a different modem or a different ROM altogether :/
But if a different modem or ROM doesn't fix it then you have a antenna problem... sorry bud

Hey mate,
Cheers for the reply. I will try a new ROM can you recommend any small ROM's that will work on my device? I don't know a great deal abour ROM's and flashing in general tbh.

I need to finish my guides badly! Then I'd just be able to point you towards them :/
But since their not... cause I've been lazy, please head over to SamMobile/ and create an account if you haven't already done and download the correct firmware for you i9000.
Getting the right firmware is difficult, it's even more difficult since I'm guessing you don't know the PDA build from what the phone was running originally... for example by phone when I got it was running I9000BVJV7 which is actually Android 2.3.3 for the UK and sim locked to Orange.
When you take into account that the Android version, the country and the carrier have an effect on the specific firmwares for two (on the face) identical phones you can begin to see how many millions of different firmwares there are out there just for one phone...
So just try your best and read all the helpful info on SamMobile. If you get really really stuck or if something nasty happens to the phone while flashing either come back to this thread or PM me and I will talk you through a recovery kit that will hopefully restore the phone to a stock ROM (but not official stock ROM).
Since you're new to flashing please be reminded flashing can completely kill a phone to the point of no return, having said that I must have flashed a million times in both ClockworkMod and Odin but that doesn't mean death can't happen at any time.

Thanks mate i really am grateful for the help. I will give that a go and see what i can find.

Downloaded all of the vodaphone rom's and all of the orange roms. The device was used on vodaphone and im still getting the same error :/ any more ideas?

Rooting Galaxy s3 mini....

Hi, I posted about this on another thread, but was then told that there is a forum for the S3. I would like to root my S3 mini GT-18190N, running 4.1.2. Its still under guarantee so it needs to be able to unroot.
Somebody mentioned CydiaImpactor, as it would be the easiest. So I installed to my mac, ticked both usb debugging and accept unknown sources, and ran the program. Within seconds I got an error, 'Error signature bugs unavailable'.......which I posted to the thread, and heard nothing from there and still havent about what that meant. I eventually found out that it means the bug has been fixed. But that is all I got.
I just wondered, what does that mean, does it affect any other ways of rooting? I found another rooting program on here, was given the the stock firmware for my phone but that needs to be unlocked. I did ask about whether the same problem would affect that firmware, but no answer. It seems the advice given on the first thread I started, about taking this to the correct forums needs to be done, which is why I am asking here. Sorry for multiple posting its not spam, its on advice from members on here.
I am a complete novice, never rooted before. So could anybody show me a root system that works for my phone.
Thank you

johnmwc2 said:
Hi, I posted about this on another thread, but was then told that there is a forum for the S3. I would like to root my S3 mini GT-18190N, running 4.1.2. Its still under guarantee so it needs to be able to unroot.
Somebody mentioned CydiaImpactor, as it would be the easiest. So I installed to my mac, ticked both usb debugging and accept unknown sources, and ran the program. Within seconds I got an error, 'Error signature bugs unavailable'.......which I posted to the thread, and heard nothing from there and still havent about what that meant. I eventually found out that it means the bug has been fixed. But that is all I got.
I just wondered, what does that mean, does it affect any other ways of rooting? I found another rooting program on here, was given the the stock firmware for my phone but that needs to be unlocked. I did ask about whether the same problem would affect that firmware, but no answer. It seems the advice given on the first thread I started, about taking this to the correct forums needs to be done, which is why I am asking here. Sorry for multiple posting its not spam, its on advice from members on here.
I am a complete novice, never rooted before. So could anybody show me a root system that works for my phone.
Thank you
Click to expand...
Click to collapse
hi bro, maybe i will buy this s3mini because i notice that it cost only 114.50 euro in my country, more than 50% less than the official price
so...
about root:
you can root the s3mini flashing the firmware with odin
else you can use cydia impactor(be sure to download the latest version from official websites)
i notice that samsung patched the masterkey bug exploited by cydiaimpactor in other galaxy phone but i dont know about s3mini 18190
however i rooted an s3mini of one of my friend s1 months ago, he has never made a firmware update and after he enabled debug usb and installed driver it work! and got root access on his phone, after root you CAN'T do ota update! you an use odin however maybe samsung upgrade to kitkat android 4.4
did you do some firmware update?

-Install TWRP (this video might be of help)
-enter recovery mode and reboot. TWRP will ask you whether you want to root or not

Hi, before I did anything I took a copy of the phone which I have stored on the laptop, windows 7. Then with CWM rooted the phone, and installed a ROM I found. The first time it didnt work, so I had to find another ROM, and install that. This ROM works but its not from my Carrier, which is EE/Orange. The Base version ends in AMJ2, which I dont seem to be able to find to get the correct ROM. The Build Number I have which is the ROM is DMod v6. It works, but its causing problems with Samsung. I have given hope of getting back to the original, but if I could get it to work with EE, it would be better. DModv6 is a US based ROM.
I hope I have explained it ok, its the first time I have done this, so not sure. Please ask for more details.
Sorry it took me so long to answer, have not been very well.
Thank you for your help

What do you mean by it not working with EE/Orange? What functionality do you not have?
Sent from my GT-I8190 using xda app-developers app

Mermaid Man said:
What do you mean by it not working with EE/Orange? What functionality do you not have?
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
As I have already mentioned, its a US based ROM, which only recognises T-Mobile UK. My phone keeps loosing the connection all the time. and I have to reconnect. T-Mobile UK is the US version of T-Mobile even though we have T-Mobile in the country, but without the UK at the end of it. And believe me it is not working properly. The phone itself does work, its faster, the battery life is much longer than when it was on EE. But I am also now having problems with Samsung, they have stopped me from using their software, because they say my phone is not using the correct software.
My first try, I did get Kit Kat running, but without the CAMERA, it wouldnt work. But there again, it was on a US based ROM, and had problems keeping the connection going. That was awesome but without the Camera, it was a bit useless. If I could get a ROM thet had either EE or Orange,

johnmwc2 said:
As I have already mentioned, its a US based ROM, which only recognises T-Mobile UK. My phone keeps loosing the connection all the time. and I have to reconnect. T-Mobile UK is the US version of T-Mobile even though we have T-Mobile in the country, but without the UK at the end of it. And believe me it is not working properly. The phone itself does work, its faster, the battery life is much longer than when it was on EE. But I am also now having problems with Samsung, they have stopped me from using their software, because they say my phone is not using the correct software.
My first try, I did get Kit Kat running, but without the CAMERA, it wouldnt work. But there again, it was on a US based ROM, and had problems keeping the connection going. That was awesome but without the Camera, it was a bit useless. If I could get a ROM thet had either EE or Orange,
Click to expand...
Click to collapse
Hey mate,
Try to use Maclaw's Recovery and KitKat ROM. They work perfectly! Flash Maclaw's recovery first (TWRP) and then wipe cache and dalvik and then flash the kitkat ROM (CM 11).
find them all here: maclaw.pl/downloads/ (stupid 10 post rule for new accounts doesn't let me post the link to HELP the user (johnmwc2)
---------- Post added at 06:32 PM ---------- Previous post was at 06:28 PM ----------
Also the reason that your phone has gone all crazy is because of the ROM you flashed (US version) probably only supports the US frequencies which is why you only get t-mobile network (in some places) as the frequencies change in each location as the phone masts give out different frequencies in different locations according to their surroundings (some frequencies penetrate walls much easier but may not go as far and vice versa).
Im 70% sure the ROM is the problem. the other 30% is me thinking maybe the ROM might not have anything to do with allowing the phone to receive phone signal ( in terms of SOFTWARE not hardware - before anyone tries flaming me). My other instinct tells me maybe its the baseband/modem version thats incompatible witht the US ROM?
just use Maclaws KitKat and TWRP!
They work a treat! :laugh:

[Q] Android 4.3 C5303 Update problem!

Hello to everyone!
This is my first post to this great forum. Recently I bought a Sony SP C5303 and now I face a complicated problem and I want your help.
The situation:
The phone was bought as unlocked (and not rooted) and when I got it, it prompt me to update to the 4.1.2 12.0.A.2.254 as previously had an older build version. I successfully did the update and everything works fine BUT right now I am wondering why I can't see the official update for 4.3
After a lot of search I realised that the phone was supplied from T-mobile (UK) as it has customization version 1272-7168_R6A
So, the phone is unlocked, unrooted and since I bought it operates on Three network.
However either when I connect it with PC companion, or I do the manual search for updates through the headset, I am unable to see the update to 4.3
I am wondering if there is any conflict between the T-mobile unlock and the Three network that I operate the phone.
Is there any way so I can trigger the update? Should I wait a little bit more? I am not sure and I am not so good with these things.
The only I want is not to cause the phone to lock somehow or to install a custom rom, neither root it.
Thank you very much for your help and your answers!

I would stay on 4.1.2. 4.3 is a piece of crap. I made the mistake of upgrading and had to downgrade. I tired many roms and did not like any of them. Stock, root and xposed frameworks still best for stability, features and battery life.

spsony120 said:
Hello to everyone!
This is my first post to this great forum. Recently I bought a Sony SP C5303 and now I face a complicated problem and I want your help.
The situation:
The phone was bought as unlocked (and not rooted) and when I got it, it prompt me to update to the 4.1.2 12.0.A.2.254 as previously had an older build version. I successfully did the update and everything works fine BUT right now I am wondering why I can't see the official update for 4.3
After a lot of search I realised that the phone was supplied from T-mobile (UK) as it has customization version 1272-7168_R6A
So, the phone is unlocked, unrooted and since I bought it operates on Three network.
However either when I connect it with PC companion, or I do the manual search for updates through the headset, I am unable to see the update to 4.3
I am wondering if there is any conflict between the T-mobile unlock and the Three network that I operate the phone.
Is there any way so I can trigger the update? Should I wait a little bit more? I am not sure and I am not so good with these things.
The only I want is not to cause the phone to lock somehow or to install a custom rom, neither root it.
Thank you very much for your help and your answers!
Click to expand...
Click to collapse
This is due to the mobile operator themselves. I am with o2 and do not have the 4.3 update for my SP either, it is down to the operator to decide when they release the update as they have to fill it with their bloatware first!
You can of course flash 4.3 yourself using flashtool I did, their are plenty of guides on this forum

kidicarus1602 said:
This is due to the mobile operator themselves. I am with o2 and do not have the 4.3 update for my SP either, it is down to the operator to decide when they release the update as they have to fill it with their bloatware first!
You can of course flash 4.3 yourself using flashtool I did, their are plenty of guides on this forum
Click to expand...
Click to collapse
To be honest I am a little bit confused what determines if the phone is going to update or not.
I mean that is the provider responsible for delivering the update or the customization version? If we think that with no sim, we just plug the phone to pc companion and it is able to see the update, then it depends on customization version.
Is there any official reference for how the phone is determined to be valid for the update?
I still believe that there is a conflict here between the current provider I operate the phone (Three) and the customization version that comes from T-mobile (the phone was unlocked from T-mobile).
Thanks guys!
P.S @xEaGLeNeC Wow!!I heard completely the opposite from many people. They claimed that the phone battery last more with 4.3! I will try to search more if it finally worth to update or not.

Flashing an Xfinity variant, and finding original firmwares

Hey guys, I'm planning on moving my phone to the Pie beta, but I had some concerns.
The biggest one is I can't find an original version of my firmware anywhere: N960USQU1ARJ6
I've found a bunch of ARJ5s, and few ARH6s but no ARJ6 versions.
I'm concerned by this because Comcast was SUPER DRAMATIC about how it had to be their phone and their version of the phone and I don't really want to break whatever thing they did.
Has anyone had any success flashing others? I've tried looking around, but the only thing I've found is if it's not the right version it will break Wifi calling. (Which I rather like)
Thanks

You will have to Odin back to this:
https://www.sammobile.com/firmwares/galaxy-note9/SM-N960U/CCT/
Your phone will update 3 times and you'll be back on the latest Xfinity firmware. I have done it a few times.