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.

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:

Used P9 - Missing Stock Apps

Hello everyone!
I just bought an used P9 (EVA-L19) in pristine condition. It arrived with the nougat update but it is missing all Huawei apps. I don't think I really mind not having those (less bloat, hurray!), but I really want at least the camera app! What should I try? This thing is full stock (unrooted), and I'd rather keep it that way... Should I just flash the full stock firmware? HiSuite claims my phone is up to date, but I've got no idea how to check what build my current firmware is.
Thanks!

Oooh... the build seems to be NRD90M "test-keys", which appears to be an old beta build from my googling. Do I have to go back to MM and then upgrade to Nougat? Hopefully I can do all that without a custom recovery...

You have an intermediate firmware.
Search here the B378 for C432 if you want the european version (wich is working fine; some other last updates may have some problems - for example, with B383 me and others have problems with the battery).
Where are you from ??

Shymmy said:
You have an intermediate firmware.
Search here the B378 for C432 if you want the european version (wich is working fine; some other last updates may have some problems - for example, with B383 me and others have problems with the battery).
Where are you from ??
Click to expand...
Click to collapse
I'm from Brazil, but I know for a fact this phone isn't brazilian. It comes with a bunch of stuff written in spanish rather than portuguese, and a warranty certificate citing a bunch of spanish-spekaing latin american countries. I'm browsing through the forums and trying to find out what is my Cust yet. But thanks for the response.
Also, if I have to flash something, is it better to stick with Nougat or is Marshmallow more hassle-free?
(I've attached a screenshot of the status screen from Huawei P9 Tool, this is all the data I could gather so far)

I can't read the screenshot ...
On the "About the phone - Version number" what do you have ??
For example, mine has EVA-L19C432B378, where:
-EVA-L19 is the phone model (P9 dual sim);
-C432 is the european version;
-B378 is the firmware version.
Also, you can read that thread too ... https://forum.xda-developers.com/p9/how-to/how-to-downgrade-nrd90m-to-marshmallow-t3541400

Shymmy said:
I can't read the screenshot ...
On the "About the phone - Version number" what do you have ??
For example, mine has EVA-L19C432B378, where:
-EVA-L19 is the phone model (P9 dual sim);
-C432 is the european version;
-B378 is the firmware version.
Also, you can read that thread too ... https://forum.xda-developers.com/p9/how-to/how-to-downgrade-nrd90m-to-marshmallow-t3541400
Click to expand...
Click to collapse
All it says on "Version number" is "NRD90M test-keys". I've read that thread, but to downgrade you need a ROM, and without knowing my Cust ID I'm not sure which ROM I should get.
The screenshot shows my serial number (XVV7N16425001010), the model (EVA-L19 - Dual Sim 32GB Rom 3GB RAM) and a weird build string (eng.jenkin.20161230.130431)

absynte said:
Hello,
do you have dual sim , or single sim and NFC ?
Dual sim: EVA-L19 ou L29
Single sim and NFC EVA-L09 (Européan version)
Click to expand...
Click to collapse
Dual SIM EVA-L19 - No idea if I've got NFC or not. Can't find anything NFC-related on the menus, but it might be that I do not know where to look. Long time Windows Phone user here, just migrated back to Android :laugh:

absynte said:
NFC is an connectivity option.
If you don't have, you have dual sim
Click to expand...
Click to collapse
It does have dual SIM, and is the EVA-L19. So no NFC then. Does it help? I'm currently looking for debranding guides because I can't find what branding this phone originally had.

Oooh well... so far:
1- *#*#2846579#*#* doesn't work (nothing happens), can't enable Manufacturer mode for DC Unlocker
2- The HUAWEI EMUI site doesn't give me a bootloader unlock code, so can't unlock the bootloader with the official method
So, so far, I can't install TWRP, so I can't flash a C432 oeminfo.bin
Also, the Rollback instructions at https://forum.xda-developers.com/p9/how-to/rollback-eva-l19-android-7-0-emui-5-0-t3496091 fail, as the rollback intermediate firmware just fails at 5% claiming to be incompatible with my device.
Aside from blindly trying to flash random firmwares with the three button method, do you guys have ANY ideas at all? I need a rest, just wasted the whole day trying to get this damned thing fixed
Sad thing: even with a borked firmware install this is still orders of magnitude better than my old Lumia 930.
EDIT: GODDAMMIT, BLUETOOTH ALSO DOESN'T WORK!

absynte said:
Ok so you've got to google this or to find on xda some answers.
https://forum.xda-developers.com/p9/how-to/how-to-downgrade-nrd90m-to-marshmallow-t3541400
For exemple....2 or 3 clicks....
bye
Click to expand...
Click to collapse
I'll give the instructions of the first post a try, though they did not work for the OP.
EDIT: AAAAAND the 800mb file is downloading at 28kbps... this won't be fun

I'm not sure if it would've been better to edit the last post or add a new one, so if this is agains the rules (I've read them and couldn't find it), please inform me and I'll change things accordingly... buuuut.... IT WORKED.
The OP on the topic absynte pointed out never really posted the outcome of his issue and it looked like he never got it to work, so here is what I did:
Flashed the zip file
I flashed the zip file linked in this post through starting up with vol up + vol down + power. Exactly like the guy over there it did not solve my issue, but did uncover I had exactly the same build as him (EVA-L19C185B361 - Middle East / Asia)
Flashed the intermediate firmware
I download the correct intermediate firmware (C185B300) from here and flashed the same way. The *#*#... menu did not work (as in the menu itself didn't show up)
Flashed a MM build
I downloaded and flashed C185B180 for whatever reason (could've gone with tha latest MM build right away AFAIK). Worked great, all stock apps were there and so was bluetooth
Let the phone update itself through OTA
It updated itself to B210 (or B220, don't remember well) and then B385. Seems to be working fine, but I haven't given the battery a fair chance (constantly flashing and updating stuff) to judge its performance.
Thanks everyone for the help!

alexanrsousa said:
I'm not sure if it would've been better to edit the last post or add a new one, so if this is agains the rules (I've read them and couldn't find it), please inform me and I'll change things accordingly... buuuut.... IT WORKED.
The OP on the topic absynte pointed out never really posted the outcome of his issue and it looked like he never got it to work, so here is what I did:
Flashed the zip file
I flashed the zip file linked in this post through starting up with vol up + vol down + power. Exactly like the guy over there it did not solve my issue, but did uncover I had exactly the same build as him (EVA-L19C185B361 - Middle East / Asia)
Flashed the intermediate firmware
I download the correct intermediate firmware (C185B300) from here and flashed the same way. The *#*#... menu did not work (as in the menu itself didn't show up)
Flashed a MM build
I downloaded and flashed C185B180 for whatever reason (could've gone with tha latest MM build right away AFAIK). Worked great, all stock apps were there and so was bluetooth
Let the phone update itself through OTA
It updated itself to B210 (or B220, don't remember well) and then B385. Seems to be working fine, but I haven't given the battery a fair chance (constantly flashing and updating stuff) to judge its performance.
Thanks everyone for the help!
Click to expand...
Click to collapse
how u downgrade to MM?

spring80 said:
how u downgrade to MM?
Click to expand...
Click to collapse
I did exactly what I said in the last post: flashed C185B300 (from http://www.carbontesla.com/2016/11/downgrade-huawei-p9-nougat-marshmallow-os-middle-east-russia/), then flashed C185B180 (from http://www.carbontesla.com/2016/11/download-huawei-p9-b180-marshmallow-update-l09l19-middle-east/)

alexanrsousa said:
I did exactly what I said in the last post: flashed C185B300 (from http://www.carbontesla.com/2016/11/downgrade-huawei-p9-nougat-marshmallow-os-middle-east-russia/), then flashed C185B180 (from http://www.carbontesla.com/2016/11/download-huawei-p9-b180-marshmallow-update-l09l19-middle-east/)
Click to expand...
Click to collapse
thanks for your answer my friend , i will try and update u
---------- Post added at 01:56 PM ---------- Previous post was at 01:25 PM ----------
working my friend , but be sure to backup first because u will lost everything

samsung note 5 firmware unknown

hi, i tried flashing my note 5 to nougat using SM-N920V-VZW-N920VVRS3CQK1 with Odin. when the phone starts it shows the red page with verizon logo and then an error message. initially my model number was SM-N920V and lollipop 5.1.1. But at the back of the phone its written made in vietnam. After some online reading, am thinking my phone should be a cloned version, and that's why flashing the original verizon upgrade doesn't work. which means if originally my phone is not sm-n920v, then i dont know which firmware to use. what can i do???

franckyben said:
hi, i tried flashing my note 5 to nougat using SM-N920V-VZW-N920VVRS3CQK1 with Odin. when the phone starts it shows the red page with verizon logo and then an error message. initially my model number was SM-N920V and lollipop 5.1.1. But at the back of the phone its written made in vietnam. After some online reading, am thinking my phone should be a cloned version, and that's why flashing the original verizon upgrade doesn't work. which means if originally my phone is not sm-n920v, then i dont know which firmware to use. what can i do???
Click to expand...
Click to collapse
I don't have this device but, your best bet is to post this question within the following thread.
https://forum.xda-developers.com/showthread.php?t=3220229
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

S20FE Not Updating since OneUi 3 and Android 11

Hello all.
My S20FE (SM-G780F) has not updated from OneUi 3 and Android 11. It always says that I'm using the latest software. I've tried factory resetting the phone and using Smart Switch to no avail.
I'm in the UK. Never lived anywhere else. I reside here permanently. It's where I bought my phone brand new.
I checked the service provider software version and it says ZT0/ZTO,ZTO/EUX . However, when I use the dialler method to check the same information it says the CSC is BTL3.
I researched and ZTO seems to refer to Brazil. I've never been to Brazil or anywhere in that vicinity so I don't know why it says ZTO as the service provider information.
Could this be why I'm having issues updating? If the phone thinks it's Brazilian then it would stop me updating if I'm in the UK? Is that correct?
Samsung suggested I send it to them to flash the drive but they require a proof of purchase and as I bought the phone over 2 years ago I can't for the life of me find the original order email.
Just for clarification the phone has never been rooted or modded and all software etc is "official." I've looked into flashing the software with Odin. Would I need ro download the update file for the CSC my phone says it is or for the CSC it should be? Do I only download the latest update or would I have to stack them and download all the previous ones my phone missed too?
Please help before I tear my hair out.

flashing the phone yourself with Odin is very easy, there are dozens of YouTube vids to get an idea from. actually downloading the firmware is more difficult.
whoever sold you the phone is who you should be angry at, it obviously wasn't intended for use here. let me know if you want help flashing!

Same thing happened to my Mom's phone (a Galaxy A series device).
Use this guide and manually flash the latest firmware.