So I was trying to flash a recovery mod and I went to go reboot the phone and it says "system software not authorized by att has been found on your phone. I tried to flash the most recent firmware in Odin but I get an error. I am wondering if anyone has a solution. I was on 4.4.2 and I can't find another thread with the newer firmware. Can anyone help??
You can flash NB1 and then update to NC1.
Read the return to stock section of http://forum.xda-developers.com/showthread.php?t=2616221
Tjw241 said:
So I was trying to flash a recovery mod and I went to go reboot the phone and it says "system software not authorized by att has been found on your phone. I tried to flash the most recent firmware in Odin but I get an error. I am wondering if anyone has a solution. I was on 4.4.2 and I can't find another thread with the newer firmware. Can anyone help??
Click to expand...
Click to collapse
The only recovery you can use is Safestrap ... If you are on stock 4.4.2 and have the 4.4.2 bootloader it is locked ... I did the same thing when I got my phone ... Cant use custom kernels either ............Root your phone then install safestrap reboot then you will get a splash screen that say Safestrap Recovery or Continue ...... select Recovery to boot into
you can only flash roms based off stock that are for safestrap and if you don't you will get the "system software not recognized" same goes with flashing kernels ... It might flash but when you check in settings you will see that it didn't flash
Related
Hi i had a stock rooted 4.2.2 mf9, then i saw the ota update that came out popped up on my notification bar so i deecided to find out how to update.
Ended up flashing that 4.4 gummy rom decided i didnt like it and tried to flash a stock rom onto it through clockwork again. the flash finished but it stopped after the boot where it says "Samsung Galaxy S4" and rebooted a few times...i couldnt get it to go to recovery so i decided i should flash it again this time through odin. got my stock rooted rom again but it keeps saying failed on odin and it always stops at the bootloader. plz help
not sure if there is a way to get a bootloader that will work or even a rom that will do the trick but im stuck without a phone atm
dmindlessflawd said:
Hi i had a stock rooted 4.2.2 mf9, then i saw the ota update that came out popped up on my notification bar so i deecided to find out how to update.
Ended up flashing that 4.4 gummy rom decided i didnt like it and tried to flash a stock rom onto it through clockwork again. the flash finished but it stopped after the boot where it says "Samsung Galaxy S4" and rebooted a few times...i couldnt get it to go to recovery so i decided i should flash it again this time through odin. got my stock rooted rom again but it keeps saying failed on odin and it always stops at the bootloader. plz help
not sure if there is a way to get a bootloader that will work or even a rom that will do the trick but im stuck without a phone atm
Click to expand...
Click to collapse
It sounds like you had the 4.3 update, because it sounds you like you are trying to install an older bootloader over the the locked MJA bootloader. So the update went through, now you cannot go back to MF9. The bootloader isn't corrupt, its locked and only the MJA bootloader can be flashed through Odin. You'll have to go to http://www.sammobile.com/firmwares/ and search for the 4.3 MJA file to flash to your fone, the cf-auto root, then flash a custom recovery...
Hi everyone,
I hope someone can help me with this problem. Basically I was updating my phone to mk2 BTU via kies and it failed. Kies stopped recognising the phone and it kept going in to stock recovery.
I tried manually flashing stock mk2 via odin but I kept getting the same result.
Then I got fed up and I rooted (cf auto root) and installed TWRP and my phone booted in to a rooted mk2. My knox is now triggered which is a bit annoying but at least it works now.
The problem is if I try to flash stock rom via odin it still does the same thing boots in to stock recovery and then I have to root and install twrp again. I blame all this on KIES!
Does anyone know how to fix this?
Thanks
Any ideas anyone?
evo6 said:
...
The problem is if I try to flash stock rom via odin it still does the same thing boots in to stock recovery and then I have to root and install twrp again. I blame all this on KIES!
Does anyone know how to fix this?
Thanks
Click to expand...
Click to collapse
Not clear here - by stock rom do you mean stock MK2 ROM (unrooted, same CSC as the rooted one that works)?
Have you also tried in Kies the special "emergency recovery mode" (under tools)?
xclub_101 said:
Not clear here - by stock rom do you mean stock MK2 ROM (unrooted, same CSC as the rooted one that works)?
Have you also tried in Kies the special "emergency recovery mode" (under tools)?
Click to expand...
Click to collapse
Hi,
Yes thats right MK2 stock unrooted and same CSC. I tried KIES the first time with emergency recovery but it kept saying device unsupported, that's when i rooted it and installed TWRP and it worked. I don't understand it.
I have rooted my Samsung Note 3 with a custom rom running Jellybean 4.3 with clockwork mod recovery. I have tripped knox due to rooting it. When Kitkat came out March 17th 2014, I wanted to upgrade and go back to official firmware with Kitkat to try it out. Since I have rooted my phone to run viper4android audio kernel I am unable to do an official OTA or Kies update. That said I went about downloading the new Bell Canada Note 3 firmware 4.4.2. I was told to flash a Jellybean Bell Firmware first before flashing the Kitkat version to avoid boot loops or other problems. Trying to do so with Odin in download mode ended in failure just trying to flash jellybean stock. Didnt get that far really. It showed a fail in the Note 3 screen to this effect in read this message (sw rev check fail : sbl1 fused 2 binary 1) . Odin didnt load like I am usually use to seeing by unzipping the firmware into a folder and adding it to the PDA field. After I loaded the .tar file (md5) file into pda it checked it and then told me its finished successfully but the next line it said CS Fail. After hitting start it said fail instantly in the odin window and on the Note 3 I did see a bar showing me the progress of install for 1 second until odin told me of the fail. Now my Note is in download mode and can't get past this problem to get it running again! Please any help would be greatfull to getting me past this problem and onto Kitkat or even back to Jellybean. Any other questions you may have I will supply you the info.
Thanks
Nervous Android user!
weston109 said:
I have rooted my Samsung Note 3 with a custom rom running Jellybean 4.3 with clockwork mod recovery. I have tripped knox due to rooting it. When Kitkat came out March 17th 2014, I wanted to upgrade and go back to official firmware with Kitkat to try it out. Since I have rooted my phone to run viper4android audio kernel I am unable to do an official OTA or Kies update. That said I went about downloading the new Bell Canada Note 3 firmware 4.4.2. I was told to flash a Jellybean Bell Firmware first before flashing the Kitkat version to avoid boot loops or other problems. Trying to do so with Odin in download mode ended in failure just trying to flash jellybean stock. Didnt get that far really. It showed a fail in the Note 3 screen to this effect in read this message (sw rev check fail : sbl1 fused 2 binary 1) . Odin didnt load like I am usually use to seeing by unzipping the firmware into a folder and adding it to the PDA field. After I loaded the .tar file (md5) file into pda it checked it and then told me its finished successfully but the next line it said CS Fail. After hitting start it said fail instantly in the odin window and on the Note 3 I did see a bar showing me the progress of install for 1 second until odin told me of the fail. Now my Note is in download mode and can't get past this problem to get it running again! Please any help would be greatfull to getting me past this problem and onto Kitkat or even back to Jellybean. Any other questions you may have I will supply you the info.
Thanks
Nervous Android user!
Click to expand...
Click to collapse
you cant flash back to 4.3 when you on 4.4.2 and did you succeed when flashing 4.4.2?
Flashing
hhai2pth said:
you cant flash back to 4.3 when you on 4.4.2 and did you succeed when flashing 4.4.2?
Click to expand...
Click to collapse
I havent been able to do anything. I was on Jellybean 4.3.2 custom rom with a custom recovery and tried to flash it back to a stock version of Jellybean before the update to Kitkat. I didnt get that far to even try flashing Kitkat because flashing Jellybean Canadian stock rom was unsuccessful with the errors I mentioned in my earlier post. Now I am stuck in download mode and unable to flash using odin.
weston109 said:
I havent been able to do anything. I was on Jellybean 4.3.2 custom rom with a custom recovery and tried to flash it back to a stock version of Jellybean before the update to Kitkat. I didnt get that far to even try flashing Kitkat because flashing Jellybean Canadian stock rom was unsuccessful with the errors I mentioned in my earlier post. Now I am stuck in download mode and unable to flash using odin.
Click to expand...
Click to collapse
I think you can power if off by pressing the power button for a few seconds. And then flash a custom recovery, reboot and flash a Kit Kat custom rom via Odin or Custom recovery. Hope it helps.
weston109 said:
I havent been able to do anything. I was on Jellybean 4.3.2 custom rom with a custom recovery and tried to flash it back to a stock version of Jellybean before the update to Kitkat. I didnt get that far to even try flashing Kitkat because flashing Jellybean Canadian stock rom was unsuccessful with the errors I mentioned in my earlier post. Now I am stuck in download mode and unable to flash using odin.
Click to expand...
Click to collapse
Knox was tripped. You said it yourself. Go and read up on Knox.
The answer will be very clear afterwards. It's quite clear to me.
Also, don't take this the wrong way.... but you probably should not have done any of this my friend. Your skill level makes this obvious.
I suggest not getting a Samsung phone next time as Knox is hard to get around (it's possible, I was rooted on 4.3 and I am now on 4.4.2 stock flashed with Odin and Knox is still 0x0).
weston109 said:
I havent been able to do anything. I was on Jellybean 4.3.2 custom rom with a custom recovery and tried to flash it back to a stock version of Jellybean before the update to Kitkat. I didnt get that far to even try flashing Kitkat because flashing Jellybean Canadian stock rom was unsuccessful with the errors I mentioned in my earlier post. Now I am stuck in download mode and unable to flash using odin.
Click to expand...
Click to collapse
what's the CSC of your phone? you should try the one newer vesion of 4.3 cause if it's an older firmware it refused flash
Hi, first of all i saw there is thread with simillar names but i didnt saw solution for my problem. So i decided to make new thread. I have been reading all day and im kinda desparate.
I decided to change my rom these days and i choosed Cyanogenmod11 (cm-11-20140217-NIGHTLY-jflteatt) but i forgot to install gapps and rebooted my device and it stuck on this screen: Samsung Galaxy S4 I was Safestrap Recovery 3.71, SuperSU (i post attachments with other details about device). I made Nadroid backup but since i cant enter into recovery its useless and wipe/ dalvik before installing CM11.
My last call was restore with odin, so i download stock rom( " I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5 ") and put phone into download mode connect it (have the proper usb driver) but Odin fails to Auth...
When i put phone in Download mode in the upper left corner says:
ODIN MODE
PRODUCT NAME: SGH-I337
SYSTEM STATUS: Official
CSB-CONFING-LSB 0x30
WRITE PROTECTION: ENABLE
...its strange becouse CM11 instalation was succsesful
Problem is the stock rom you are trying to flash. You have to flash the MF3 stock rom. You cannot flash any aosp roms with safestrap.
You also installed the wrong version of safestrap. Safestrap 3.71 is for 4.3, you have to install 3.65 on MF3.
Kaze105 said:
Problem is the stock rom you are trying to flash. You have to flash the MF3 stock rom. You cannot flash any aosp roms with safestrap.
You also installed the wrong version of safestrap. Safestrap 3.71 is for 4.3, you have to install 3.65 on MF3.
Click to expand...
Click to collapse
AT&T Galaxy S4 SGH-I337 UCUAMDB (Android 4.2.2) – Download
AT&T Galaxy S4 SGH-I337 UCUAMDL (Android 4.2.2) - Download (latest)
from this link: galaxys4root.com/galaxy-s4-stock-firmware/
couldn't find MF3 i googled and searched here in the forum but all i found was stock rom from recovery install and i dont have such option atm.
Safestrap was working fine i used my backup once, but with this rom just disappeared and now im kinda in dead end... only hope left to make odin work somehow, but im lost at the moment.
I know the search is for it but can anyone give me link for proper rom, i would be grateful... im really messed up, whole day spent reading about this and search for simillar problem.
I found my solution after i read tons of threads. This one i needed http://forum.xda-developers.com/showthread.php?t=2504311 thanks @Shockndrop !!!
PS: Can close this thread
I hit on UPDATE on the phone for an OTA update but it only says UNABLE TO CONNECT AT&T SERVER. When I bought it, it had 5.0.1 (I337UCUGOC3) out of the box. Searching on internet says that is bootloader locked (so I cant do anything).
- Can I Update to I337UCUGOK2 and bootloader will be unlocked (I mean, will I be able to do it)?
- Does anyone know where can I grab I337UCUGOK2 for offline install and is it ODIN safe to update it (remember I have I337UCUGOC3 bootloader locked)?
please help
Once the bootloader is locked, it will always be locked until someone finds a way to unlock it. Updating the bootloader will not allow it to be unlocked.
cybercuate said:
I hit on UPDATE on the phone for an OTA update but it only says UNABLE TO CONNECT AT&T SERVER. When I bought it, it had 5.0.1 (I337UCUGOC3) out of the box. Searching on internet says that is bootloader locked (so I cant do anything).
- Can I Update to I337UCUGOK2 and bootloader will be unlocked (I mean, will I be able to do it)?
- Does anyone know where can I grab I337UCUGOK2 for offline install and is it ODIN safe to update it (remember I have I337UCUGOC3 bootloader locked)?
please help
Click to expand...
Click to collapse
Unlocking/exploiting the bootloader for the AT&T is still in process, I think.
Bootloader locked means you can not install custom recovery like TWRP, CWM or custom kernel. You can still root, you can still use odin and you can still install custom rom using either safestrp or flashfire.
Here is the thread explaining how to upgrade stock or rooted stock roms.
The explanation starts from installation of NB1 firmware so that you can easily root the phone by using twolroot.
If you do not care for the root you can start reading from the step 2 "Flash update in stock recovery"
Since you are on OC3, you need OC3 to OC4 and OC4 to OK2 files to get OK2.
help... I want to RMA it
sway8966 said:
Unlocking/exploiting the bootloader for the AT&T is still in process, I think.
Bootloader locked means you can not install custom recovery like TWRP, CWM or custom kernel. You can still root, you can still use odin and you can still install custom rom using either safestrp or flashfire.
Here is the thread explaining how to upgrade stock or rooted stock roms.
The explanation starts from installation of NB1 firmware so that you can easily root the phone by using twolroot.
If you do not care for the root you can start reading from the step 2 "Flash update in stock recovery"
Since you are on OC3, you need OC3 to OC4 and OC4 to OK2 files to get OK2.
Click to expand...
Click to collapse
Everywhere says I need a kitkat rom as base.
My s4 came with 5.0.1 with OC3 and bootloader locked out of the box. I tried some post where says I can flash TWRP and CWM but my phone stucked on bootloops. Then I managed to get back to stock rom and now when I want to turn it on it says " SAMSUNG (and lower on the screen) Custom"
Camera began to fail and I want to return it as RMA but I was looking to reset the flash counter but every post I read is that OC3 bootloader locked users are just doomed.
Do you know a method that I can do for reset that counter?
Camera dont focus anymore and I tried all the posts about safemode, etc.
cybercuate said:
Everywhere says I need a kitkat rom as base.
My s4 came with 5.0.1 with OC3 and bootloader locked out of the box. I tried some post where says I can flash TWRP and CWM but my phone stucked on bootloops. Then I managed to get back to stock rom and now when I want to turn it on it says " SAMSUNG (and lower on the screen) Custom"
Camera began to fail and I want to return it as RMA but I was looking to reset the flash counter but every post I read is that OC3 bootloader locked users are just doomed.
Do you know a method that I can do for reset that counter?
Camera dont focus anymore and I tried all the posts about safemode, etc.
Click to expand...
Click to collapse
Flashing TWRP and CWM is for the AT&T S4 with older bootloader (MDL, MDB). After that two firmware versions the bootloader is locked.
For AT&T S4 the last full firmware released is NB1. After that they released incremental updates via OTA. That is why you need kitkat (NB1) as base.
For NB1, Muniz uploaded two firmwares. One is the stock and the other is rootable stock. Try the stock one and see you still have the custom symbol.
To reset the counter, there is an app calls Triangle away by Chainfire. However, it does not work on AT&T S4 with locked bootloader.
Trying Odin-Stock NB1
sway8966 said:
Unlocking/exploiting the bootloader for the AT&T is still in process, I think.
Bootloader locked means you can not install custom recovery like TWRP, CWM or custom kernel. You can still root, you can still use odin and you can still install custom rom using either safestrp or flashfire.
Here is the thread explaining how to upgrade stock or rooted stock roms.
The explanation starts from installation of NB1 firmware so that you can easily root the phone by using twolroot.
If you do not care for the root you can start reading from the step 2 "Flash update in stock recovery"
Since you are on OC3, you need OC3 to OC4 and OC4 to OK2 files to get OK2.
Click to expand...
Click to collapse
sway8966 said:
Flashing TWRP and CWM is for the AT&T S4 with older bootloader (MDL, MDB). After that two firmware versions the bootloader is locked.
For AT&T S4 the last full firmware released is NB1. After that they released incremental updates via OTA. That is why you need kitkat (NB1) as base.
For NB1, Muniz uploaded two firmwares. One is the stock and the other is rootable stock. Try the stock one and see you still have the custom symbol.
To reset the counter, there is an app calls Triangle away by Chainfire. However, it does not work on AT&T S4 with locked bootloader.
Click to expand...
Click to collapse
Thanks. I'll try Odin it with the stock rom from your link. I'll post news here when it finish flashing
1st part - Success
I'm on 4.4.2 NB1, flash counter back to normal but still bootloader locked
Now I have to go back to OC3 to RMA it.
OTA does nothing, smartswitch shows no updates neither kies.
I'll have to Odin it back to OC3
Can I have some help?
And Success. I'm back on stock OC3 no root.
time to RMA
- camera still doesn't focus
- boot screen is back to normal but when in odin mode the counter shows 0x1
- sometimes shows "sim card could not be detected" or similar messages and force me to restart the phone (just happend 2 times until now, never happend before)
I followed this thread
http://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642
Post 2
Thanks to sway8966