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.
Related
Hello all,
I would like to share a method that solved this tricky issue with my S4 GT-I9500. While flashing with some new ROMs, I ended up with a generic IMEI on my S4. I read everything I could find here in XDA foruns, and no method worked for me. This one below, from fellow colleage douglasgalves at brasildroid foruns saved my phone. Here the link to the original post (portuguese only, sorry)
http://brasildroid.com.br/discussoe...efs-resolver-esse-problema-11.html#post299796
The method is quite simple, and althogh it does not make complete sense (why Trinida Tobago for example) it worked for me! Here it is.
1. You have a I9500 with a generic IMEI.
2. Install a official stock ROM with ODIN. Not any Stock ROM, but specifically Trinida & Tobago April 2013 ROM. You can browse it on Sammobile, or also get it from this link on XDA -> http://forum.xda-developers.com/showthread.php?t=2257645
The ROM I used is:
Build Date: 24.04.2013
Region: TTT (Trinidad and Tobago)
PDA: I9500UBUAMDK
Changelist: 534999 Android: 4.2
3. Once installation is finished, disconnect the cable;
4. Reboot to recovery and wipe data and cache;
5. Install KIES on your PC and let it update to its latest version.
6. Once KIES is updated, connect your S4 to the PC, no need for USB Debug, etc, just connect it.
7. KIES will detect it and say a new version of firmware is available. Perform the update. It takes a long time.
8. Once the update is finished, you get a dialog in KIES asking you to disconnect and connect the cable again, with a confirm button "Confirm". This is the moment it fixes your IMEI. One more reboot and voilà, your IMEI should be back.
I have no idea how/why this worked, if someone more experienced can explain, I would like to understand.
Also, no idea if this would work on other models, with a different ROM, or on a Mac instead of a PC, or with steps on different order. All I know is that, by doing exactly this, I gave life back to my beloved S4.
Now, off to make some 5 backups of the /efs folder before flashing ROMs again.
Good luck there with your generic-IMEIed S4s!
Did some more tweaking to try to understand what happened. Hope some guru can jump in and help me.
1. After I recovered my IMEI, I installed Philz Touch 5.11.2. It went well, I rebooted in CWM recovery, then chose Reboot->Root. It rebooted the phone. Then I went to make a backup of the /efs folder with Root Explorer, and discovered that despite it looking as rooting went well, the phone was not rooted.
Question 1: Why does Philz did not get to root the device? At that stage the firmware version was MG9 for region TTT (Trinidad & Tobago). Is that firmware somehow imcompatible for Philz to root?
Then ...
2. I flashed Firmware for Colombia with ODIN (my phone was bought in Colombia) from April, version UBUAMDE. Got Generic IMEI again. Then followed the same procedure from post 1, and got my IMEI back with KIES. The strange thing is that on KIES, my phone still shows as TTT (Trinidad) after that.
Question 2: It looks like more than the ROMs, it is the last step on KIES that recovers the IMEI. Is it so tha ODIN may be screwing up the IMEI?
Question 3: why I keep with my phone showing as TTT? Is that a problem?
3. Then I flashed the ChainFire recovery. Strangely, this went well and rooted my phone, so it may be something with Philz. I again flashed Philz and it installed well.
Question 4: may I get any problems by using Philz but having rooted with Chainfire?
Thanks a lot for any clarification you gurus out there can give me!
Thanks
You've given a considerable amount of hope to those that are stuck on the genereic imei. Thank you for providing this solution.
However, I am stuck:
After using ODIN 3.07; clicking nothing other than PDA for selecting the firmware you said to download: Hotfile:GT-I9500-TTT-I9500UBUAMDK-1366814146.zip The firmware was successfully installed.
Then before the boot completed, I went into recovery and wiped data and cache. The phone restarted and it booted up, Kies was already updated to the latest version. So once the phone booted up, I connected the phone to the computer and kies displayed this message:
Your device's current firmware version is not supported to update firmware via Kies.
Current firmware version: PDA:MDK / PHONE:MDK / CSC:MDK (XXX)
How can I go about resolving this issue?
As I said in the second post, I also got successful using the ROM for Colombia from April.
I would sugesst you to go to sammobile's firmware database. Download any older ROM which supports firmware via KIES (there is an icon showing that over there) and do the same procedure. It looks like what really solves it is the final step in KIES.
Sent from my GT-I9500 using XDA Premium 4 mobile app
I think this is due to flashing Previous Version of Modem (Its Including in Stock Firmware). When You flash Previous Version of Modem, Somehow IMEI retains. Here are some facts:
1) When we try to Flash any MOD of any dev then its depend on which Modem (i.e country's Firmware) the dev is using.
2) After flashing the MOD, Our IMEI becomes Fake.
3) Flashing Previous Version of Modem take back the IMEI.
In your above method you did the same. You flashed the Whole stock firmware but too old by date. After flashing, it retains.
BTW, have you checked your IMEI after flashing the Firmware using ODIN.? It was there.? was it Generic.?
Notice that I never refer to mod ROMs. I got a fake IMEI by flashing stock ROMs with ODIN.
Even during the recovery process, when I flashed the old stock ROM, the IMEI is not back. It only gets back at the last step with KIES.
When checking the IMEI after flashing with ODIN I get always the generic 499 IMEI.
Looks to me like something not going well with ODIN and 9500.
Sent from my GT-I9500 using XDA Premium 4 mobile app
partimers said:
Notice that I never refer to mod ROMs. I got a fake IMEI by flashing stock ROMs with ODIN.
Even during the recovery process, when I flashed the old stock ROM, the IMEI is not back. It only gets back at the last step with KIES.
When checking the IMEI after flashing with ODIN I get always the generic 499 IMEI.
Looks to me like something not going well with ODIN and 9500.
Sent from my GT-I9500 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Flashing ROM from ODIN given you Fake IMEI.? This is something strange. We all flashed from ODIN & never got that. BTW, If its like that, I would recommend above ^ ^ your steps but wait...... Did you flashed any other country's firmware.?
Disturbed™ said:
Flashing ROM from ODIN given you Fake IMEI.? This is something strange. We all flashed from ODIN & never got that. BTW, If its like that, I would recommend above ^ ^ your steps but wait...... Did you flashed any other country's firmware.?
Click to expand...
Click to collapse
It is indeed strange Disturbed, but I can reproduce it. I flash for example, April ROMs (happened with all countries that I tested, Trinidad, Colombia and Brazil), the IMEI gets generic. It is not that the /efs folder is deleted. It is there, it is just that somehow, the IMEI does not get correctly read from the files that are there.
It only gets fixed after KIES updates the ROM for the latest one, and only at the very last stage where KIES ask to disconnect/reconnect the cable.
I first get into trouble when after flashing CWM Philz, I tried to restore stock ROM.
I live in Brazil, but travel very often on business to Colombia, and bought the phone on a good sale. That is why I am trying different countries, but the problem first happened when re-installing Stock ROM for the first time, and at that time I was just using the ROM for Colombia.
Only when things got bad (generic IMEI) I tried other countries ROMs, modems, etc, and finally got to this method that fixed it for me.
[/QUOTE]
Hi have you taken a backup of the EFS and saved?
U are a lucky guy u hv it all this working
As per what i know possibly there will be 1 more folder in the system root other then efs main which has imei details etc which must be corrupted and takes place while flashing so u have fake imei
Also check do u have any lockscreen issue???
I m telling this coz I was mad solving imei issue for 2 days with note 2 just a week ago
Sent from my GT-I9505 using XDA Premium 4 mobile app
exclaimed said:
I connected the phone to the computer and kies displayed this message:
Your device's current firmware version is not supported to update firmware via Kies.
Current firmware version: PDA:MDK / PHONE:MDK / CSC:MDK (XXX)
How can I go about resolving this issue?
Click to expand...
Click to collapse
*FIX*
I had the same problem, so I did the following to fix the problem:
Root the device,
Install CSC Changer,
Select the CSC which matches the firmware you are trying to update,
Then start the guide above again from the beginning (including reinstalling the firmware through Odin, even if you are currently using it - to remove the root...)
and now Kies is updating my device!
*UPDATE*
IMEI is not fixed...
Thank you for your suggestion.
I've tired CSC Changer, but to no avail. After changing my CSC to TTT, the phone is restarted, and I put it in download mode; follow all the steps above, but I still see XXX on KIES.
I even tried changing my CSC by opening Preconfig via android terminal emulator, but I still see XXX on KIES.
exclaimed said:
Thank you for your suggestion.
I've tired CSC Changer, but to no avail. After changing my CSC to TTT, the phone is restarted, and I put it in download mode; follow all the steps above, but I still see XXX on KIES.
I even tried changing my CSC by opening Preconfig via android terminal emulator, but I still see XXX on KIES.
Click to expand...
Click to collapse
Please note that KIES does not require Download mode, just connect the phone to the PC running KIES. Maybe it is that, I don`t know.
Hi have you taken a backup of the EFS and saved?
U are a lucky guy u hv it all this working
As per what i know possibly there will be 1 more folder in the system root other then efs main which has imei details etc which must be corrupted and takes place while flashing so u have fake imei
Also check do u have any lockscreen issue???
I m telling this coz I was mad solving imei issue for 2 days with note 2 just a week ago
Sent from my GT-I9505 using XDA Premium 4 mobile app[/QUOTE]
Hey 123hiten, I had no lockscreen issues, only Generic IMEI. Solve it with KIES.
So now I have tried this solution in many different ways,
even though kies does update the FW, it doesn't restore the IMEI,
So on several occasions after updating and not see'ing the IMEI being restored
I put the old Columbian FW back on and restarted the process following every last detail exactly as stated but to no avail....
So I can only conclude that this solution must not work for the I9500 (Exynos S4)....
SmilerOnline said:
So now I have tried this solution in many different ways,
even though kies does update the FW, it doesn't restore the IMEI,
So on several occasions after updating and not see'ing the IMEI being restored
I put the old Columbian FW back on and restarted the process following every last detail exactly as stated but to no avail....
So I can only conclude that this solution must not work for the I9500 (Exynos S4)....
Click to expand...
Click to collapse
It is really frustrating when a solution works in some cases and not on others. Sorry to hear it did not fix it for you. But for my I-9500 it fixed it perfectly. I do not know why :/
One thing I may remark: the IMEI only came back on the very last stage, when after finishing the upgrade to latest firmware in KIES, I rebooted the phone, disconnect the cable, connected it again and pressed "Confirm" on KIES. At that exact point it fixed it. I did not have to do anything with CSC.
partimers said:
It is really frustrating when a solution works in some cases and not on others. Sorry to hear it did not fix it for you. But for my I-9500 it fixed it perfectly. I do not know why :/
One thing I may remark: the IMEI only came back on the very last stage, when after finishing the upgrade to latest firmware in KIES, I rebooted the phone, disconnect the cable, connected it again and pressed "Confirm" on KIES. At that exact point it fixed it. I did not have to do anything with CSC.
Click to expand...
Click to collapse
I did exactly as you said but the Kies button said "OK" not "Confirm"...
and the only reason the CSC change was required for me was to allow my device to be updated by kies (if your device was from Columbia & you updated it with that fw that may be why you didn't need to change the csc... as the csc was already the Columbia csc)
Device is from Colombia but somehow it let me update via KIES using the TTT rom
Sent from my GT-I9500 using XDA Premium 4 mobile app
partimers said:
Device is from Colombia but somehow it let me update via KIES using the TTT rom
Sent from my GT-I9500 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
@partimer, I am curious, what app or program did you use to backup your IMEI after restoring it to its original form or did you just copy the efs folder.
Thanks.
Copy the efs folder using root Explorer to the Sd card. From there I created a tarball and backed it up to my file server and cloud.
Sent from my GT-I9500 using XDA Premium 4 mobile app
From my time on the S2 I had efs problems too. It was established that the IMEI number is individual to each device and is not included on any firmware be it stock or custom. Several roms now automatically create backups when being flashed so it's worth exploring your system to find any backups.
Sent from my GT-I9505 using XDA Premium 4 mobile app
This evening, due to some slightly buggy behavior that I attribute to removing too many things during a recent "debloat session", I attempted to restore my rooted N3 to stock using the most current firmware and Odin. Something went very wrong and the flash failed. My N3 now advises that "Firmware Upgrade encountered an issue. Please select recovery mode in Kies and try again". So I tried Kies Emergency Device Recovery, but Kies will not connect to my phone in any screen I am able to access. The phone will only boot to the Odin Mode screen. I can't get to the recovery, either.
I've tried Kies in both Windows 7 and Mac OS Mavericks, tried different cables and USB ports, updated Kies as well as drivers, but I'm not making any headway.
I've tried using Kies option to upgrade the firmware, but my N3 doesn't have the S/N printed anywhere on the phone. I'm away from home, but I have a call in to a friend to get the S/N off the box... But I'm not holding my breath that this path will succeed.
I'd bite the bullet and go to Sprint, but as I'm sure you are aware, a rooted Note 3 clearly shows 0x1 under Knox Warranty Void on the Odin Mode screen (which again, is the only screen I can access).
I'm well and truly stuck. Are there any options I'm missing? Something I've overlooked?
nathanotis said:
This evening, due to some slightly buggy behavior that I attribute to removing too many things during a recent "debloat session", I attempted to restore my rooted N3 to stock using the most current firmware and Odin. Something went very wrong and the flash failed. My N3 now advises that "Firmware Upgrade encountered an issue. Please select recovery mode in Kies and try again". So I tried Kies Emergency Device Recovery, but Kies will not connect to my phone in any screen I am able to access. The phone will only boot to the Odin Mode screen. I can't get to the recovery, either.
I've tried Kies in both Windows 7 and Mac OS Mavericks, tried different cables and USB ports, updated Kies as well as drivers, but I'm not making any headway.
I've tried using Kies option to upgrade the firmware, but my N3 doesn't have the S/N printed anywhere on the phone. I'm away from home, but I have a call in to a friend to get the S/N off the box... But I'm not holding my breath that this path will succeed.
I'd bite the bullet and go to Sprint, but as I'm sure you are aware, a rooted Note 3 clearly shows 0x1 under Knox Warranty Void on the Odin Mode screen (which again, is the only screen I can access).
I'm well and truly stuck. Are there any options I'm missing? Something I've overlooked?
Click to expand...
Click to collapse
Hi mate try and flash this rom it's like a super rom it fixes anything http://forum.xda-developers.com/showthread.php?t=2461929
It's got me out of trouble a few times
jaythenut said:
Hi mate try and flash this rom it's like a super rom it fixes anything http://forum.xda-developers.com/showthread.php?t=2461929
It's got me out of trouble a few times
Click to expand...
Click to collapse
These seem to be only 9005 and 900 ROMS, ie, not for the N900P (Sprint).
nathanotis said:
These seem to be only 9005 and 900 ROMS, ie, not for the N900P (Sprint).
Click to expand...
Click to collapse
Oh bugger
What about Cwm can you flash that then flash a custom rom
nathanotis said:
...
I've tried using Kies option to upgrade the firmware, but my N3 doesn't have the S/N printed anywhere on the phone.
...
Click to expand...
Click to collapse
My N9005 (and to be honest every single original Samsung phone that I have seen in last year, and the number is pretty big) have BOTH the IMEI and the SN written on a sticker under the battery.
xclub_101 said:
My N9005 (and to be honest every single original Samsung phone that I have seen in last year, and the number is pretty big) have BOTH the IMEI and the SN written on a sticker under the battery.
Click to expand...
Click to collapse
I know where it's *supposed to be*, but the only numbers on said sticker are; DEC, HEX, Model and FCC ID (which I tried, just in case). There is NOTHING else on that sticker.
jaythenut said:
Oh bugger
What about Cwm can you flash that then flash a custom rom
Click to expand...
Click to collapse
Last night I tried flashing the most current firmware and when that failed, I tried an older copy I have that has worked before. Neither succeeded and both result in the Odin screen on the phone saying: "sw rev check fail fused 2 binary 1" (which I've been googling but found no working answers yet).
The message Odin gives is "FAIL! (Auth)". I've read this morning about how the most current firmware (MI3) removes root and plugs some security holes. Some think it won't be rootable...
Is this my problem?
nathanotis said:
This evening, due to some slightly buggy behavior that I attribute to removing too many things during a recent "debloat session", I attempted to restore my rooted N3 to stock using the most current firmware and Odin. Something went very wrong and the flash failed. My N3 now advises that "Firmware Upgrade encountered an issue. Please select recovery mode in Kies and try again". So I tried Kies Emergency Device Recovery, but Kies will not connect to my phone in any screen I am able to access. The phone will only boot to the Odin Mode screen. I can't get to the recovery, either.
I've tried Kies in both Windows 7 and Mac OS Mavericks, tried different cables and USB ports, updated Kies as well as drivers, but I'm not making any headway.
I've tried using Kies option to upgrade the firmware, but my N3 doesn't have the S/N printed anywhere on the phone. I'm away from home, but I have a call in to a friend to get the S/N off the box... But I'm not holding my breath that this path will succeed.
I'd bite the bullet and go to Sprint, but as I'm sure you are aware, a rooted Note 3 clearly shows 0x1 under Knox Warranty Void on the Odin Mode screen (which again, is the only screen I can access).
I'm well and truly stuck. Are there any options I'm missing? Something I've overlooked?
Click to expand...
Click to collapse
this happened with me too "Firmware Upgrade encountered an issue. Please select recovery mode in Kies and try again".
If you can still go to ODIN/Download mode everything is fine.
Just download the latest firmware for your phone, old firmware won't do as you can not downgrade bootloader. Then flash it in ODIN.
vikas724 said:
this happened with me too "Firmware Upgrade encountered an issue. Please select recovery mode in Kies and try again".
If you can still go to ODIN/Download mode everything is fine.
Just download the latest firmware for your phone, old firmware won't do as you can not downgrade bootloader. Then flash it in ODIN.
Click to expand...
Click to collapse
I can get into Odin mode, so that's great news... Unfortunately I tried to flash the most current firmware and got the same result. The failure message in Odin is "Fail (Auth)". at the same time the device says something in red text about a "SW REV" issue.
I'm downloading the most current FW again from Samsung. (WHY DOES IT TAKE SO LONG?!) I'll post back when I try again.
I'm back up and running! I had downloaded a firmware ending in mi3, the MOST current is mj4, which flashed over to my N3 without issue.
Thanks all for the assist.
nathanotis said:
I know where it's *supposed to be*, but the only numbers on said sticker are; DEC, HEX, Model and FCC ID (which I tried, just in case). There is NOTHING else on that sticker.
Click to expand...
Click to collapse
Sprint is CDMA right? CDMA phone got no IMEI.
It got the same purpose of IMEI called MDN or something. But it got NO IMEI.
Try latest stock ROM, coz if you're on newer bootloader, it wont allow you to flash downgrade....
Hi guys! I hope someone could help me. I just bought a Galaxy Note 3 (international version) yesterday. The phone's fine. It's just that I am unable to update. I am able to download it but when my phone reboots it shows a dead android with a red triangle on its chest. I read flashing the firmware via odin can fix it but problem is our internet is hella slow. I couldn't even complete downloading my brother's Note 2 firmware. Any way I can make it install the firmware successfully? By the way it's OTA. I am able to download the update, just won't let me finish installing it. Goes around 35% then the android on the black screen dies with a red triangle on its chest.
EDIT:
I have official firmware, never rooted, just got it yesterday. Still factory new.
version 4.3, build # JSS15J.N9005ZHUBMI7, baseband version N9005XXUBMI5, Kernel version 3.4.0-1626679
Have you tried reseting your phone go into recovery mode factory reset
Mygadgetgeek.com
mygadgetgeek.com said:
Have you tried reseting your phone go into recovery mode factory reset
Mygadgetgeek.com
Click to expand...
Click to collapse
not yet, but i have a lot of data now on my phone. will try that though. in case that doesn't work, any other advice?
cptnappy said:
Hi guys! I hope someone could help me. I just bought a Galaxy Note 3 (international version) yesterday. The phone's fine. It's just that I am unable to update. I am able to download it but when my phone reboots it shows a dead android with a red triangle on its chest. I read flashing the firmware via odin can fix it but problem is our internet is hella slow. I couldn't even complete downloading my brother's Note 2 firmware. Any way I can make it install the firmware successfully? By the way it's OTA. I am able to download the update, just won't let me finish installing it. Goes around 35% then the android on the black screen dies with a red triangle on its chest.
EDIT:
I have official firmware, never rooted, just got it yesterday. Still factory new.
version 4.3, build # JSS15J.N9005ZHUBMI7, baseband version N9005XXUBMI5, Kernel version 3.4.0-1626679
Click to expand...
Click to collapse
Was your phone brand new? And did you check your KNOX status? -- reason I ask, after you've rooted a phone you are unable to recieve OTA updates, unless you use Wanam to fake system status, then you can download the OTA update but it stalls on the install about 35% or so in..
Best advice, is grab the stock image from sammobile (ballache to download I know) then use ODIN to flash her back to original state.
radicalisto said:
Was your phone brand new? And did you check your KNOX status? -- reason I ask, after you've rooted a phone you are unable to recieve OTA updates, unless you use Wanam to fake system status, then you can download the OTA update but it stalls on the install about 35% or so in..
Best advice, is grab the stock image from sammobile (ballache to download I know) then use ODIN to flash her back to original state.
Click to expand...
Click to collapse
i didn't root the phone when i got it. it's fresh and on official firmware. have no idea about KNOX, that's new to me. if it helps, my device status says "official"
unfortunately the internet in my area is very slow, i couldn't download firmwares from sammobile. i tried several times
cptnappy said:
i didn't root the phone when i got it. it's fresh and on official firmware. have no idea about KNOX, that's new to me. if it helps, my device status says "official"
unfortunately the internet in my area is very slow, i couldn't download firmwares from sammobile. i tried several times
Click to expand...
Click to collapse
Ah Ok, if it says Official it should be good to go. Seems like maybe the download has gotten corrupt due to an intermittent internet connection.
cptnappy said:
i didn't root the phone when i got it. it's fresh and on official firmware. have no idea about KNOX, that's new to me. if it helps, my device status says "official"
unfortunately the internet in my area is very slow, i couldn't download firmwares from sammobile. i tried several times
Click to expand...
Click to collapse
OK, then maybe you should learn a few things before trying to update - Knox is a security system in latest Samsung phones that is supposed to be triggered/set when you root (or install any custom kernel/recovery). Your initial (old) firmware could still let you root without triggering the Knox flag, and then you can update to the latest firmware for your region using Mobile Odin Pro and still keep your root AND without triggering the Knox flag. However once you update using Samsung OTA / Odin / Kies to a firmware more recent than MJ3 you can no longer root without also triggering your Knox warrany flag - read more about this in the Universal Root De La Vega thread!
i gave up after several tries, since i'm on 4.3 i think that would do for now. maybe it's just downloading a stability update or something? everytime i do an OTA update, it tells me that the download of the new firmware is complete then reboot. when i get to 32% the droid falls flat on its back and shows the red triangle on its chest, over and over. i don't lose my phone data or anything. just won't update. i'll wait for 4.4 Kitkat instead. hope i'll be able to update to that when it comes out.
EDIT: i tried going into recovery mode, wiping cache, and factory reset.. still no dice. maybe Odin's the only way i guess. problem is my internet connection lol
@cptnappy - i also have the same problem...got my note3 n9005 a week ago and I also have the same problem as you....error at 30+%
tried update thru Kies with no luck...same error appears
Sent3 said:
@cptnappy - i also have the same problem...got my note3 n9005 a week ago and I also have the same problem as you....error at 30+%
tried update thru Kies with no luck...same error appears
Click to expand...
Click to collapse
i managed to update mine using Samsung Kies3 (not Kies, but Kies3). Hope updating OTA is fixed in the future with the update i just did
I rooted my phone two weeks ago with towelroot and disabled Knox with supersu.Note: my device status said official I'm still running stock firmware. Have to send my phone back for warranty problem so I unrooted with supersu and reset my phone. So now when I look at my device status it says custom (never flashed any roms or nothing) so I factory reset and notice unlock padlock and custom on my reboot startup screen. I also put phone in Odin mode the binary still said Samsung official but now the other say custom. And Knox says 0×0. I was told to use Odin so I installed odin3v3.09, drivers, stock firmware on the PC tried to flash it but got a Auth: Fail in the left lower box.
My replacement phone will be here today and will send the old back Monday to give me a couple more days to figure this out. What did I do wrong?
PLEASE HELP!
UPDATE
I just notice when I was using Odin I tried to flash G900AUCU1ANCE stock firmware. My phone says I'm running G900AUCU2AND3. I wonder if that's why I've been getting that auth: Fail
Where can I get the G900AUCU2AND3 stock firmware from?
Try going to the sammobile website (cant post link because I'm a new member). It should be there
Sent from my SM-G900F using XDA Premium 4 mobile app
tmadekush said:
I just notice when I was using Odin I tried to flash G900AUCU1ANCE stock firmware. My phone says I'm running G900AUCU2AND3. I wonder if that's why I've been getting that auth: Fail
Where can I get the G900AUCU2AND3 stock firmware from?
Click to expand...
Click to collapse
Your warranty should be honoured because it still shows Knox 0x0. But it would be prudent to resolve the custom message as you are trying to do. It's showing custom because you disabled Knox. Flashing a full stock firmware should restore Knox and resolve the custom message.
Odin flashes can fail for many reasons e.g. trying to flash non-Odin versions of firmware, bad signatures, poor quality USB cables, wrong firmware version e.g. one meant for a different phone, et cetera.
Back up your files, then do a full system reset from the settings menu. Then put your phone into download mode and use Odin to flash a full stock firmware. Ideally use the latest firmware version for carrier that the phone originally came from (i.e. it should match the baseband). Google will find many firmware repositories e.g. sammobile, samsung-updates and this site.
.
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