Database Users

Cannot update S4

I bought a 'brand new Galaxy S4' which came with rooted. I have flashed the BTU firmware to the device but in Keis it says device not eligible for update.
How can I fix this?

roastspud said:
I bought a 'brand new Galaxy S4' which came with rooted. I have flashed the BTU firmware to the device but in Keis it says device not eligible for update.
How can I fix this?
Click to expand...
Click to collapse
You should be able to flash back to stock using odin then upgrade or flash the updated version with odin.
Sent from my SCH-I545 using xda app-developers app

You have to unroot your device and flash the firmware with corresponding CSC to your country. On top of that you have to flash the firmware that was ALREADY officialy in your country (best way is to download package from sammobile.com) after that the OTA will work. I know because I also had problems with OTA after rooting the device.

I have reflashed the BTU UK firmware I9505XXUAMDM via ODIN and my device now shows as running official rom
Kies now says...
Your devices current firmware version is not supported to update via Kies.
What gives?

Hi,
Recovery mode mentions multi csc. Could this be the problem?

roastspud said:
I have reflashed the BTU UK firmware I9505XXUAMDM via ODIN and my device now shows as running official rom
Kies now says...
Your devices current firmware version is not supported to update via Kies.
What gives?
Click to expand...
Click to collapse
Maybe go into stock recovery and wipe data/factory reset then reboot ??
Sent from my SCH-I545 using xda app-developers app

jds3118 said:
Maybe go into stock recovery and wipe data/factory reset then reboot ??
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Thanks.
Just tried that. Went back to recovery mode after and it said manual mode.. applied the csc again and mentioned multi csc exists

roastspud said:
Thanks.
Just tried that. Went back to recovery mode after and it said manual mode.. applied the csc again and mentioned multi csc exists
Click to expand...
Click to collapse
Recovery mode has a android bot lay down with a red exclamation mark

roastspud said:
I bought a 'brand new Galaxy S4' which came with rooted. I have flashed the BTU firmware to the device but in Keis it says device not eligible for update.
How can I fix this?
Click to expand...
Click to collapse
Hi,
Where did you buy a "Brand New S4" with root?
Not sure what you are trying to do.
You have root, so, just flash the latest stock ROM and you are up to date.
If you are trying to get back to "Official" stock, then, look HERE
Use Triangle Away to reset your counter, and you will be able to get Ota.
Sent telepathically from my S4

malybru said:
Hi,
Where did you buy a "Brand New S4" with root?
Not sure what you are trying to do.
You have root, so, just flash the latest stock ROM and you are up to date.
If you are trying to get back to "Official" stock, then, look HERE
Use Triangle Away to reset your counter, and you will be able to get Ota.
Sent telepathically from my S4
Click to expand...
Click to collapse
I bought the phone from Amazon as new.. This is my first Android phone and I only noticed the problem when I checked the apps and it had SuperSU istalled and Kies complained about not being supported for updates.
What I am trying to do is get the phone running as stock so it will update via Kies + OTA and also remove the yellow multi CSC writing from the boot recovery menu.
I have tried unrooting and flashing stock BTU firmware but then I still have the yellow writing in the boot recovery menu and cannot update via Kies.

roastspud said:
I bought the phone from Amazon as new.. This is my first Android phone and I only noticed the problem when I checked the apps and it had SuperSU istalled and Kies complained about not being supported for updates.
What I am trying to do is get the phone running as stock so it will update via Kies + OTA and also remove the yellow multi CSC writing from the boot recovery menu.
I have tried unrooting and flashing stock BTU firmware but then I still have the yellow writing in the boot recovery menu and cannot update via Kies.
Click to expand...
Click to collapse
Hi,
OK.
Did you use the link I gave you ?
You need to get Triangle Away from the market.

malybru said:
Hi,
OK.
Did you use the link I gave you ?
You need to get Triangle Away from the market.
Click to expand...
Click to collapse
Thanks for your help so far.
Yes I have Triangle Away but no root..

malybru said:
Hi,
OK.
Did you use the link I gave you ?
You need to get Triangle Away from the market.
Click to expand...
Click to collapse
Ok.. here is what I have done so far..
Rooted the rom and ran triangle away to reset my counter to 1 . I have removed root and flashed stock BTU firmware then wiped data/cache from the recovery menu.
But I still have the multi csc message in stock recovery that will not budge and Kies reports the phone is not supported for updates.
Could this be because the boot loader is locked?

roastspud said:
Ok.. here is what I have done so far..
Rooted the rom and ran triangle away to reset my counter to 1 . I have removed root and flashed stock BTU firmware then wiped data/cache from the recovery menu.
But I still have the multi csc message in stock recovery that will not budge and Kies reports the phone is not supported for updates.
Could this be because the boot loader is locked?
Click to expand...
Click to collapse
Hi,
The bootloader is not locked.
You should have reset the counter to "0"
Then, flashed the stock firmware without rebooting the phone.

Does the recovery says that it "applied BTU" ? If not then your region code is not proper and that's why OTA does not work. Unfortunately it is hard to change CSC right now as Samsung has blocked the keystrings for user packages, keystrings works only for engineer builds.
And about that flash counter, it does not matter if its 100 or 0. The OTA will work as long as the status in download mode is official for both variables, and in Settings > About device is official too.
As I work at Samsung's R&D I know that you have to flash the firmware which was RELEASED for your country with proper CSC, the CSC has to be set (you can check it in recovery mode) and then both variables in download mode have to "Official" and status in About device also has to be Official. Then the OTA will work (At least over-the-air, not through Kies). Best way to check the OTA is to flash first firmware released for your country and check the updates. Ive done it dozen times on various devices and it always worked. You cannot be rooted and need stock recovery. The only major problem might be changing CSC on your own, because as I said it is not easy right now as Samsung blocked *#272* keystring in user packages (released for the market). Flashing engineering build will make the all keystrings work, but I guess you won't find any of those odin flashables on the net.

tehaerpl said:
Does the recovery says that it "applied BTU" ? If not then your region code is not proper and that's why OTA does not work. Unfortunately it is hard to change CSC right now as Samsung has blocked the keystrings for user packages, keystrings works only for engineer builds.
And about that flash counter, it does not matter if its 100 or 0. The OTA will work as long as the status in download mode is official for both variables, and in Settings > About device is official too.
As I work at Samsung's R&D I know that you have to flash the firmware which was RELEASED for your country with proper CSC, the CSC has to be set (you can check it in recovery mode) and then both variables in download mode have to "Official" and status in About device also has to be Official. Then the OTA will work (At least over-the-air, not through Kies). Best way to check the OTA is to flash first firmware released for your country and check the updates. Ive done it dozen times on various devices and it always worked. You cannot be rooted and need stock recovery. The only major problem might be changing CSC on your own, because as I said it is not easy right now as Samsung blocked *#272* keystring in user packages (released for the market). Flashing engineering build will make the all keystrings work, but I guess you won't find any of those odin flashables on the net.
Click to expand...
Click to collapse
It says applied BTU but multi CSC exists. How do I find the original CSC code out? SO its not possible to change this at all or at least get rid of that stupid message?
Is a green andriod bot with a red exclamation mark anything to be worried about?
OTA updates now work fine However they dont work via Kies. Is this normal?
FYI the flash counter was at 3 so somebody had obviously messed with this.
Sorry for all the questions. This is my first Android device having switched from Crapple
It is weird because the box was sealed and had the protectors on the phone.

Multi CSC means that the file that was flashed contains few regions code and that it can be changed inside the OS with keystring. So nothing to worry about as long as it is set to your country and OTA works. As for the icon, it is normal after entering recovery, my device also has that icon, it does not mean that there is some error. Kies does not always wants to cooperate I do not know why, but as long over-the-air works you're not missing anything apart from cable update.

tehaerpl said:
Multi CSC means that the file that was flashed contains few regions code and that it can be changed inside the OS with keystring. So nothing to worry about as long as it is set to your country and OTA works. As for the icon, it is normal after entering recovery, my device also has that icon, it does not mean that there is some error. Kies does not always wants to cooperate I do not know why, but as long over-the-air works you're not missing anything apart from cable update.
Click to expand...
Click to collapse
Thanks everyone Now I just need to find some decent apps

Have fun with Android, in case of any questions you can always send a PM

roastspud said:
It says applied BTU but multi CSC exists. How do I find the original CSC code out? SO its not possible to change this at all or at least get rid of that stupid message?
Is a green andriod bot with a red exclamation mark anything to be worried about?
OTA updates now work fine However they dont work via Kies. Is this normal?
FYI the flash counter was at 3 so somebody had obviously messed with this.
Sorry for all the questions. This is my first Android device having switched from Crapple
It is weird because the box was sealed and had the protectors on the phone.
Click to expand...
Click to collapse
Hi,
That is why I questioned the fact that you bought a phone , and it came "Out-of-the-box" with root.
This just does not happen.
Anyway,glad you got it sorted.

HELP ON getting Galaxy note 3 n900 unroot for receiving stock updates

guys,i rooted my note 3 n900 by cf-auto root but now i want to unroot my note 3 ...so that i can receive all sorts of official software updates from samsung......PLEASE HELP ME PLEASE....i'm stucked.and tell me can i fully unroot my note 3 by getting back knox warranty...is it possible? is chainfire working on the fix to get back knox warranty? i use an international n900 variant.HELP

As far as I understood, once you have triggered knox 0x1 or the counter for flashing, the OTAs won't be available any more.
I have the same thing. Checking for OTA updates works though, if you use something like wanam which can be setup to fool the phone into thinking that it's ok. I was able to download an update with SuperUser turned off (and reboot afterwards), but couldn't install.
So actually, I just check every now and then on the forums if there's an update and then just wait for a regular download via PC and flash with ODIN. Works quite well, and by the time downloads become available via PC, you'll also already know if there are glitches with newer updates, too. Takes about a day or two compared to the OTA.

help
Mikegrmn said:
As far as I understood, once you have triggered knox 0x1 or the counter for flashing, the OTAs won't be available any more.
I have the same thing. Checking for OTA updates works though, if you use something like wanam which can be setup to fool the phone into thinking that it's ok. I was able to download an update with SuperUser turned off (and reboot afterwards), but couldn't install.
So actually, I just check every now and then on the forums if there's an update and then just wait for a regular download via PC and flash with ODIN. Works quite well, and by the time downloads become available via PC, you'll also already know if there are glitches with newer updates, too. Takes about a day or two compared to the OTA.
Click to expand...
Click to collapse
Where can I get updates via pc...link please

Tawhidz13 said:
Where can I get updates via pc...link please
Click to expand...
Click to collapse
Sammobile.com/firmwares usually has the latest firmwares. If you prefer pre-rooted firmwares just search for it right here in the forum. Before you download and install any firmware though, check that you download the right one. The latest EU fw is N9005XXUDMUJ7. But you also have to check your CSC. What happens when this is wrong, I don't know. But you may get boot loops. Just use the forums search and read through CSC, ODIN and the latest fw name. You'll find all that you need. And with the latest CF-Autoroot, rooting your phone is just a mouse click away.

Updates are available via KIES on your PC if you have rooted your phone (you will lose root and have to re-reoot though), just cannot get OTA. - I updated my rooted MJ6 to MJ7 via KIES with no issues. (KNOX 0x1) - KIES will say something like " software update might not work because of modified phone" but mine worked fine. - or alternatively try sammobile.com and manually flash the firmware yourself.
As for your KNOX, no way back currently from 0x1..

radicalisto said:
Updates are available via KIES on your PC if you have rooted your phone (you will lose root and have to re-reoot though), just cannot get OTA. - I updated my rooted MJ6 to MJ7 via KIES with no issues. (KNOX 0x1) - KIES will say something like " software update might not work because of modified phone" but mine worked fine. - or alternatively try sammobile.com and manually flash the firmware yourself.
As for your KNOX, no way back currently from 0x1..
Click to expand...
Click to collapse
I tried Kies initially, too. But Kies just told me that I would have an unsupported phone, so I went ODIN.

If I am rooted with vroot, knox not tripped will unrooting in any way trip it?

[Help] OMG! Did i Brick my new note 3!? :(

Hey guys. Ive had a note 3 before in the past and have used the Root DelaVega to root successfully. This was early in the year. I sold my old note 3 for an HTC One. Well today i traded my HTC One back for a note 3 as i missed the Note 3. As soon as i came home i attempted to use the Root DelaVega method to foot (just like i did before) and immediately it failed.
I have been stuck on a screen saying "firmware update encountered an issue - select recovery in Kies" so i tried Kies 3.2 however it says my device is not compatible. Come to find out after doing research (talking to the original owner i traded my HTC One for) the Note 3 i have is on the latest version of KitKat 4.4.2 that is not compatible with the Root DelaVega method or any root method - so i screwed that up. I can successfully boot in and out of download mode. Ive tried to flash N900XXUDNA6 4.4.2 in Odin several times, it begins then fails almost immediately and the bar on the phone itself (in download mode) begins then freezes shortly after beginning. Ive also tried to flash N900XXUDNC1 JellyBean thru odin and get the same results - almost immediately fail and the blue status bar on the phone freezes when it barley begins. What else can i do??? am i totally screwed? Ive been researching and trying to fix this for 6 straight hours now! My gf is about to kill me for being online so long Is there anything i can do at this point? Am i stuck.

Do you know what Region the phone was originally? I had a similar issue and I had to get the Hong Kong (in my case) version of a stock ROM and flash that to get things working again. Not all partitions are the same - you might need a PIT file to match your original region and then flash the ROM.
What info do you get in DL mode?

Journyman16 said:
Do you know what Region the phone was originally? I had a similar issue and I had to get the Hong Kong (in my case) version of a stock ROM and flash that to get things working again. Not all partitions are the same - you might need a PIT file to match your original region and then flash the ROM.
What info do you get in DL mode?
Click to expand...
Click to collapse
Yes the phone is for AT&T so it's US. When I go into DL mode Knox counter is still 0x0. Is there a certain firmware I need then to match with the AT&T model? Or a pit?

jthornton71707 said:
Yes the phone is for AT&T so it's US. When I go into DL mode Knox counter is still 0x0. Is there a certain firmware I need then to match with the AT&T model? Or a pit?
Click to expand...
Click to collapse
Go to Sammobile and see if you can find the version you had, sounds like an older JB if kingo app didn't trip Knox. Reflash that using ODIN.
I don't know if there was a problem with American bootloader, see if there's an AT&T Note 3 forum. Might find answers there...

jthornton71707 said:
Hey guys. Ive had a note 3 before in the past and have used the Root DelaVega to root successfully. This was early in the year. I sold my old note 3 for an HTC One. Well today i traded my HTC One back for a note 3 as i missed the Note 3. As soon as i came home i attempted to use the Root DelaVega method to foot (just like i did before) and immediately it failed.
I have been stuck on a screen saying "firmware update encountered an issue - select recovery in Kies" so i tried Kies 3.2 however it says my device is not compatible. Come to find out after doing research (talking to the original owner i traded my HTC One for) the Note 3 i have is on the latest version of KitKat 4.4.2 that is not compatible with the Root DelaVega method or any root method - so i screwed that up. I can successfully boot in and out of download mode. Ive tried to flash N900XXUDNA6 4.4.2 in Odin several times, it begins then fails almost immediately and the bar on the phone itself (in download mode) begins then freezes shortly after beginning. Ive also tried to flash N900XXUDNC1 JellyBean thru odin and get the same results - almost immediately fail and the blue status bar on the phone freezes when it barley begins. What else can i do??? am i totally screwed? Ive been researching and trying to fix this for 6 straight hours now! My gf is about to kill me for being online so long Is there anything i can do at this point? Am i stuck.
Click to expand...
Click to collapse
Hi mate,
if you are stuck, maybe you can try this.
http://forum.xda-developers.com/show....php?t=2701062
it's a way to unbrick your software.
and if the older owner of your N3 said it's on the latest firmware of kitkat.
maybe your problem is the firmware in the sammobile were before the firmware you have install on your device via OTA update.
Yours firmware came throw out via OTA update and with some reason you can't see any latest firmware USA N900A in sammobile.
try the method in the link and reply if you have been successful.
cumps

Ik Knox is 0×0,then u can try samsung service centre ?
Sent from my SM-N900 using XDA Premium 4 mobile app

WIFI not working after using KIES to update

Hi all,
Phone Details:
Spring Galaxy S4
Baseband Version L720TVPUBNG5
Used CF autoroot
This all started a few days ago. The latest OTA update came out and my phone kept telling me I had insufficient storage for the update. I figured it was because I had it rooted. I followed QBking77's video for Unroot / Unbrick. Downloaded all files recommended in the video.
Every time I try to flash with ODIN I get a failure. I have tried three different .tar versions at this point, it always seems to fail after "aboot" attempts to flash. Two different cables, both came with an SGS4.
I finally had enough and used the factory reset. After factory reset I used KIES for my update. The phone took it fine and rebooted. Although now I have no WIFI.
When initiating WIFI it will tell me that the security application has rejected a request to protect my phone. I deleted lookout security even though I have never used it.
Does this have something to do with KNOX? Knox flag is at 0x1 so I know it is tripped. Is there a way to completely flash my phone back to a stock state with the original recovery and rom?
Are there any options for me to get my phone back in order. I really dont give a **** about root or roms, I just need my WIFI. Would my best bet be to use a custom firmware?

Your correct thread have to go: HERE.

cannot update s5 software with kies, help?

my galaxy s5 model number is sm-g900t, android version is 4.4.2, ..not sure what other info might help, but anyway, i cannot update the software/firmware over the air because the device is rooted through steps on here and its been rooted awhile now. so anyway, i downloaded the kies 3 from the samsung site, it says all im supposed to do is plug the phone in, a box is supposed to pop up showing an update is needed......well, the kies box does pop up, but all it shows is current firmware version and shows my internal and external storage availabilty, and so on.... no auto update thing came up. so in kies i went into tools up a t the top, i hit firmware upgrade and initialization, then a smaller box pops up saying---does not support initializing, so now what? nothing else i can do in kies except move pic files around and such. i need to update the software. any advice? i attached 2 pics.....pic 1 is the initial message when phone is plugged in, #2 is when i go into tools and hit ugrade

knight1701 said:
my galaxy s5 model number is sm-g900t, android version is 4.4.2
Click to expand...
Click to collapse
Samsung has now embedded a security flag called KNOX in it's later devices. Unfortunately after you flash a package/custom ROM or whatever with a different signature than Samsungs own it trips that KNOX flag.
When your KNOX flag is tripped you can no longer update your phone via official methods. It is just the way it is, and there is nothing to be done. Once KNOX flag is tripped, there is no way to "untrip" it, so you will never be able to update via KIES again.
Im not really sure whether flashing a stock lollipop rom via odin works when KNOX is tripped, i have never tried it, so you should wait for any other member for confirmation. As far as i know, it shouldn't be a problem.
What i can tell you, if you have the time, is that you flash a ROM that is compatible with 4.4.2 (Omega v13 or AllianceROM v5.6 etc) and then flash it's ROMs lollipop update after a full wipe. It is the only thing i personally am sure about (i have done it before).

I'm by no means an expert on the matter but I'm pretty sure that if you can't get the Ota due to being rooted, then updating vIA Kies isn't going to work either.
Go to settings> about device> status
scroll to bottom of list and respond here what it says under "device status" (it's gong to say either official, or custom).
If it says official, you could unroot, maybe check that the proper drivers are installed on your computer, and try once again to apply the update via kies.
If it says custom, then knox has been tripped and I cannot help further.
The biggest issue here is that if you take the OTA update you'll lose the option to root or downgrade so you should probably use TWRP to install a ROM that's pre-rooted rather than trying to get the OTA

Akalsemann said:
Samsung has now embedded a security flag called KNOX in it's later devices. Unfortunately after you flash a package/custom ROM or whatever with a different signature than Samsungs own it trips that KNOX flag.
When your KNOX flag is tripped you can no longer update your phone via official methods. It is just the way it is, and there is nothing to be done. Once KNOX flag is tripped, there is no way to "untrip" it, so you will never be able to update via KIES again.
Im not really sure whether flashing a stock lollipop rom via odin works when KNOX is tripped, i have never tried it, so you should wait for any other member for confirmation. As far as i know, it shouldn't be a problem.
What i can tell you, if you have the time, is that you flash a ROM that is compatible with 4.4.2 (Omega v13 or AllianceROM v5.6 etc) and then flash it's ROMs lollipop update after a full wipe. It is the only thing i personally am sure about (i have done it before).
Click to expand...
Click to collapse
well i hear what your saying, but on my other phone, same setup, rooted and all.......updated just fine---did it about a month ago...updated to android 5 from 4.4.2..just plugged in the phone and boom it did its thing............on this other phone though, daughters phone, it wont work

Swimguy14 said:
I'm by no means an expert on the matter but I'm pretty sure that if you can't get the Ota due to being rooted, then updating vIA Kies isn't going to work either.
Go to settings> about device> status
scroll to bottom of list and respond here what it says under "device status" (it's gong to say either official, or custom).
If it says official, you could unroot, maybe check that the proper drivers are installed on your computer, and try once again to apply the update via kies.
If it says custom, then knox has been tripped and I cannot help further.
The biggest issue here is that if you take the OTA update you'll lose the option to root or downgrade so you should probably use TWRP to install a ROM that's pre-rooted rather than trying to get the OTA
Click to expand...
Click to collapse
ok, on the phone in question, device status says--- custom, guess that ends that..........on my phone howerver, it says official which is why i guess i was able to update mine

just download a rom for your phone from sammobile and install with odin and your done