Database Users

Fixed - I9505 - kernel is not seandroid enforcing - Reboot & Hangs ! Easy !

S4 I9505
Problem:
Start up screen top left corner shows:
kernel is not seandroid enforcing
Hangs up or Reboots.
I updated my S4 to Version: I9505XXUEMKE
Then I used Odin to Flash a Root with Stock recovery & SU, something went WRONG!
Knox is now 0x1, which should not have happened, but what can I say.
BaM, I got the Reboots & Hang ups.
But, I still could get into Recovery & Download Mode!
SO HERE IS THE FIX:
1. Download, Odin 3 - THx 2 - daerragh
--- I used Ver.: Odin 3.07
2. Download, http://www.sammobile.com/firmwares/2/
--- Register
--- And download your Firmware, if you know which you had before it crashed choose that one otherwise Upgrade to latest.
--- For me it was the latest version - I9505XXUEMKE ---- THx 2 -- Repulsa for the tip.
3. Start Odin 3.07 --- [Should it "FAIL" Read note at the Bottom #6].
--- Make sure - Auto Reboot & F. Reset Time are checked - Nothing else.
--- Click on PDA choose your Firmware file in my case "I9505XXUEMKE"
--- this can take a minute or two, WAIT, the PDA will check mark itself.
4. To start Turn off your phone completely ! Now hold following buttons to get into Download Mode,
--- Volume Down
--- Home
--- and last Power
--- S4 will enter into DL Mode
Seeing you have already tried to root you phone, you should have you Samsung USB drivers.
5. Press Start
--- This will take time, after it Reboot itself,
--- remove the USB Cabel & wait
--- at least 5 minutes don't remember how long, I came back after 5 Minutes and it was done,
---------- so then if everything went well for you, have fun :good: .
6. FAIL
--- Should it Fail while uploading to your phone,
--- A. Remove Battery
--- B. Remove USB cabel
--- C. Restart.
--- Should it Fail again (which happend to me), then Do A. B. C. again.
--- and this time Touch your screen about every minute.
I Know that sounds weird, but it worked for me maybe something to do with "Stand by? no clue".
If this has help you in anyway please hit that :good: Thanks Bottun
I AM NOT RESPONSIBLE for anything happening to your phone as a result of you flashing this Rom.

[Help Please] TMO-S4- Kernel is not seandroid enforcing
Hello,
Let me start off by saying, I'm a complete newbie when it comes to rooting (Infact - It took me a few days to even convince myself to do this) and I did look around for several guilds on how to remove this error (Downloaded Odin - Got Stock TAR.MD5) But I still get this error on my phone when I start the phone, it wouldn't be much of a probelm, except it hangs for a while and then restarts.) It also gets stuck for a long time at the T-Mobile load screen. The Wifi Wont turn on their... Please Help.
Galaxy S4: SGH-M919
T-Mobile...

I'm not an expert in Android OS but I think this is not an error. It is more of a notification that the STOCK KERNEL has been change to a CUSTOM one.

eclpsues said:
I'm not an expert in Android OS but I think this is not an error. It is more of a notification that the STOCK KERNEL has been change to a CUSTOM one.
Click to expand...
Click to collapse
You are right :highfive:

Hi guys
A friend and I tried to update my rooted Samsung S4 i9505 to the official kitkat version. Had the unofficial one before. Unfortunatly we didn't turn on the usb debugging and there wasn't enough space on my memory card. After removing the data from the sd card it still didn't work (usb debuging?). My friend then tried to install a custom rom of some sort (I'm the noob here. He has some skills). No whenever I try to start my cell up the message KERNAL IS NOT SEANDROID ENFORCING pops up in the top left corner. Can I turn on the usb debugging from the pc? What should I do?
Thanks

illias9 said:
Hi guys
A friend and I tried to update my rooted Samsung S4 i9505 to the official kitkat version. Had the unofficial one before. Unfortunatly we didn't turn on the usb debugging and there wasn't enough space on my memory card. After removing the data from the sd card it still didn't work (usb debuging?). My friend then tried to install a custom rom of some sort (I'm the noob here. He has some skills). No whenever I try to start my cell up the message KERNAL IS NOT SEANDROID ENFORCING pops up in the top left corner. Can I turn on the usb debugging from the pc? What should I do?
Thanks
Click to expand...
Click to collapse
I tried to install the Gummy Rom but I got the same problem. It gets stuck in the rebooting or something. It wont pass the samsung start screen. What should I do?

Tried all of the above and no go.
Hi i have CM on my Australia XSA Samsung 19505 and i am trying to get it back to stock though when i try to flash it in Odin it fails all the time i cant get into recovery though i am able to access download mode.
I am using Odin 3.09 with the correct stock rom for my device and when i run it i get this error message
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUEMK9_I9505XSAEMK3_I9505XXUEMK9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> sbl1.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl2.mbn
<ID:0/007> sbl3.mbn
<ID:0/007> rpm.mbn
<ID:0/007> aboot.mbn
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And on my device is error message
start [224,1440]
sw rev check fail fused 4 binary 3.
I also have the "kernel is not seandroid enforcing" message.
When i restart my device i get an error message "Firmware upgrade encountered an issue please select recovery mode in kies and try again"
I have tried to use Kies both versions and it doesn't work, The only way to get it to work is flash CWM which allows me back into my device.
Any ideas on how to get back to stock Thanks?

Natza09 said:
Hi i have CM on my Australia XSA Samsung 19505 and i am trying to get it back to stock though when i try to flash it in Odin it fails all the time i cant get into recovery though i am able to access download mode.
I am using Odin 3.09 with the correct stock rom for my device and when i run it i get this error message
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUEMK9_I9505XSAEMK3_I9505XXUEMK9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> sbl1.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl2.mbn
<ID:0/007> sbl3.mbn
<ID:0/007> rpm.mbn
<ID:0/007> aboot.mbn
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And on my device is error message
start [224,1440]
sw rev check fail fused 4 binary 3.
I also have the "kernel is not seandroid enforcing" message.
When i restart my device i get an error message "Firmware upgrade encountered an issue please select recovery mode in kies and try again"
I have tried to use Kies both versions and it doesn't work, The only way to get it to work is flash CWM which allows me back into my device.
Any ideas on how to get back to stock Thanks?
Click to expand...
Click to collapse
Use a different usb port. Always use the ports on the back of your pc not the ones on the front.

Lennyz1988 said:
Use a different usb port. Always use the ports on the back of your pc not the ones on the front.
Click to expand...
Click to collapse
Thanks Lennyz for the reply, I tried the back usb 2.0 and 3.0 and both failed with the same error message as originally posted. Can i just restore the kernel some how and will that fix the issue?

Natza09 said:
Thanks Lennyz for the reply, I tried the back usb 2.0 and 3.0 and both failed with the same error message as originally posted. Can i just restore the kernel some how and will that fix the issue?
Click to expand...
Click to collapse
I think I know what you did. You try to flash an older stock firmware on to your device. Pick a newer firmware because downgrading is not possible.

Lennyz1988 said:
I think I know what you did. You try to flash an older stock firmware on to your device. Pick a newer firmware because downgrading is not possible.
Click to expand...
Click to collapse
I have tried to flash several Roms that are 4.4 and that are compatible with my device using clock work mod and it doesn't work as i keep getting a Status 7 error which i have found a possible fix for here in the forum i will attempt to resolve and report back.
---------- Post added at 11:40 PM ---------- Previous post was at 11:05 PM ----------
Natza09 said:
I have tried to flash several Roms that are 4.4 and that are compatible with my device using clock work mod and it doesn't work as i keep getting a Status 7 error which i have found a possible fix for here in the forum i will attempt to resolve and report back.
Click to expand...
Click to collapse
Ok so i put TWTP back on and i was able to install Goldeneye Rom 4.4.2, Which is working great. However when i reboot im still getting the Kernel is not seandroid enforcing message in red. As i can not restore to stock Rom as Australia XSA 4.4 isn't out yet is there any other way to get rid of this message. Thanks again.

did anyone tried this ??

Natza09 said:
Hi i have CM on my Australia XSA Samsung 19505 and i am trying to get it back to stock though when i try to flash it in Odin it fails all the time i cant get into recovery though i am able to access download mode.
I am using Odin 3.09 with the correct stock rom for my device and when i run it i get this error message
I have tried to use Kies both versions and it doesn't work, The only way to get it to work is flash CWM which allows me back into my device.
Any ideas on how to get back to stock Thanks?
Click to expand...
Click to collapse
iuts coz you are trying to downgrade the aboot file which is associated with know security check .. u have to flash the same or upgrade

franny23dmt said:
iuts coz you are trying to downgrade the aboot file which is associated with know security check .. u have to flash the same or upgrade
Click to expand...
Click to collapse
Yeah its all sorted now as version 4.4.2 has been officially released as stock on my Samsung S4, So back to "factory" now and no more message. Off to ebay it goes and Hello HTC One M8 .

Hi,
I'll Install WizCyan custom Rom on My GT-I9505 by TWRP mode. Its not a Error its a Premission That are allow when we use other roms.
●Press Volume Up and Volume Down Key at same
time and Hold it. This methode is use to Force Start your Rom

[Q] 4.4 Update via Odin Fail, Phone Bricked

I tried to install the 4.4.2 N9005XXUENA6_N9005OXXENA5_N9005XXUENA2 update on my Note 3 via odin 3.09.
Got an ext4 update failed error.
After this, the phone's bricked and is stuck on the Kies Recovery Screen. I tried to go into recovery mode in Kies, but it says this model does not have initialization.
I tried installing a 4.3 N9005XXUDMK3_N9005TNLDMK1_N9005XXUDMK2, but again failed. Download mode shows SW REV CHECK FAIL : [aboot] Fused 3 > Binary 2
Can someone please guide me to unbrick my phone?
I don't know what ROM I was on initially. It was the stock ROM that came with the phone.
I dont have CWM and TWRM installed.

This is not a brick at all. Just add a .pit file and restart the upgrade via Odin again.
You should be fine.

MrAndroid12 said:
This is not a brick at all. Just add a .pit file and restart the upgrade via Odin again.
You should be fine.
Click to expand...
Click to collapse
Thank you for that advice. How do I add a .pit file, and would you happen to have a link where I can download it from?

rinuvimal said:
Thank you for that advice. How do I add a .pit file, and would you happen to have a link where I can download it from?
Click to expand...
Click to collapse
search better mate http://forum.xda-developers.com/showthread.php?t=2550823

tasked28m said:
search better mate http://forum.xda-developers.com/showthread.php?t=2550823
Click to expand...
Click to collapse
I've tried all the .pit files in that thread, bro. None work. Cannot generate own pit as in phone is in recovery mode.

rinuvimal said:
I've tried all the .pit files in that thread, bro. None work. Cannot generate own pit as in phone is in recovery mode.
Click to expand...
Click to collapse
i know cfautoroot has the correct pit file in , try rooting your phone with cfautoroot.

MrAndroid12 said:
This is not a brick at all. Just add a .pit file and restart the upgrade via Odin again.
You should be fine.
Click to expand...
Click to collapse
I tried a variety of N9005 .pits and each time, it shows PIT FAIL: TOTAL SECTORS (30777344) :crying:

(Read OP) . Try flashing the polish firmware again with odin v1.85 and try using different usb ports. Close most of your running applications such as firefox skype etc that can interrupt the process and flash official firmware.

tasked28m said:
(Read OP) . Try flashing the polish firmware again with odin v1.85 and try using different usb ports. Close most of your running applications such as firefox skype etc that can interrupt the process and flash official firmware.
Click to expand...
Click to collapse
Whenever I try the 4.4.2 polish, it fails at system.img.ext4. When I try 4.3, it fails at aboot.
Here's the Odin log for 4.4.2 polish:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> aboot.mbn
<ID:0/006> sbl1.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> sdi.mbn
<ID:0/006> NON-HLOS.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

bootloop note 3
After installig android 4.4.2, i tried to root with cf-root, now it is in a loop.
I cannot come into in recovery mode.
The phone starts with: -recovery booting,-recovery is not seandroid enforcing,- set warrant bit recovery
when i keep the battery out and then put it in, it says again -recovery booting,-recovery is not seandroid etc.
Who can help me????

rinuvimal said:
Whenever I try the 4.4.2 polish, it fails at system.img.ext4. When I try 4.3, it fails at aboot.
Here's the Odin log for 4.4.2 polish:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> aboot.mbn
<ID:0/006> sbl1.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> sdi.mbn
<ID:0/006> NON-HLOS.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
You won't be able to downgrade back to 4.3 - Use the PDA slot on ODIN and try flashing again.
poedy said:
After installig android 4.4.2, i tried to root with cf-root, now it is in a loop.
I cannot come into in recovery mode.
The phone starts with: -recovery booting,-recovery is not seandroid enforcing,- set warrant bit recovery
when i keep the battery out and then put it in, it says again -recovery booting,-recovery is not seandroid etc.
Who can help me????
Click to expand...
Click to collapse
I answered in your other thread about this...

rinuvimal said:
I tried to install the 4.4.2 N9005XXUENA6_N9005OXXENA5_N9005XXUENA2 update on my Note 3 via odin 3.09.
Got an ext4 update failed error.
After this, the phone's bricked and is stuck on the Kies Recovery Screen. I tried to go into recovery mode in Kies, but it says this model does not have initialization.
I tried installing a 4.3 N9005XXUDMK3_N9005TNLDMK1_N9005XXUDMK2, but again failed. Download mode shows SW REV CHECK FAIL : [aboot] Fused 3 > Binary 2
Can someone please guide me to unbrick my phone?
I don't know what ROM I was on initially. It was the stock ROM that came with the phone.
I dont have CWM and TWRM installed.
Click to expand...
Click to collapse
try to downlaod and flash the 4.4.2 tar again, you cant downgrade to 4.3 as your bootlaoder got upgraded
Edit- darn am i too slow or are you too fast today @radicalisto? second time...LOL :good:

Khizar said:
try to downlaod and flash the 4.4.2 tar again, you cant downgrade to 4.3 as your bootlaoder got upgraded
Edit- darn am i too slow or are you too fast today @radicalisto? second time...LOL :good:
Click to expand...
Click to collapse
15 hour sleep man, seems to have me buzzing around lol :highfive:

Solution
I also have Hong Kong N9005 32GB with N9005XXUBMI5 PDA, tried to flash 4.4.2 with Odin and stuck at "invalid ext4 image", was't able to flash anything after it.
But after 16 hours I finally found a solution:
1. Get leaked Polish ROM (that one with 4 files, do not use the official - it has one file rom)
2. Extract archive
3. Extract "CSC_OXX_N9005OXXENA5_327209_REV03_user_low_ship_MULTI_CERT.tar" and get your pitfile - HLTE_EUR_OPEN.pit
4. Flash your phone with this pitfile and other 4 files from archive (I used Odin 3.09) with repartitioning enabled.
After this procedure I have fully working android 4.4 :victory:

m1ndst0rm said:
I also have Hong Kong N9005 32GB with N9005XXUBMI5 PDA, tried to flash 4.4.2 with Odin and stuck at "invalid ext4 image", was't able to flash anything after it.
But after 16 hours I finally found a solution:
1. Get leaked Polish ROM (that one with 4 files, do not use the official - it has one file rom)
2. Extract archive
3. Extract "CSC_OXX_N9005OXXENA5_327209_REV03_user_low_ship_MULTI_CERT.tar" and get your pitfile - HLTE_EUR_OPEN.pit
4. Flash your phone with this pitfile and other 4 files from archive (I used Odin 3.09) with repartitioning enabled.
After this procedure I have fully working android 4.4 :victory:
Click to expand...
Click to collapse
Have you tried rooting it with Chainfire's CF-Auto Root yet?

m1ndst0rm said:
I also have Hong Kong N9005 32GB with N9005XXUBMI5 PDA, tried to flash 4.4.2 with Odin and stuck at "invalid ext4 image", was't able to flash anything after it.
But after 16 hours I finally found a solution:
1. Get leaked Polish ROM (that one with 4 files, do not use the official - it has one file rom)
2. Extract archive
3. Extract "CSC_OXX_N9005OXXENA5_327209_REV03_user_low_ship_MULTI_CERT.tar" and get your pitfile - HLTE_EUR_OPEN.pit
4. Flash your phone with this pitfile and other 4 files from archive (I used Odin 3.09) with repartitioning enabled.
After this procedure I have fully working android 4.4 :victory:
Click to expand...
Click to collapse
can you show the download link for the leaked rom with 4 files?

vndnguyen said:
can you show the download link for the leaked rom with 4 files?
Click to expand...
Click to collapse
I have no permission to post links yet, but try googling for N3KitKat.rar.torrent

Leaked download link is in my sig (not this cause I am on xda app l check my other posts)
Sent from my SM-N9005 using XDA Premium 4 mobile app

ManUtdRul3 said:
Have you tried rooting it with Chainfire's CF-Auto Root yet?
Click to expand...
Click to collapse
Just tried latest one, ended up in bootloop with "KERNEL IS NOT SEANDROID ENFORCING"...
Now flashing original ROM again.

m1ndst0rm said:
Just tried latest one, ended up in bootloop with "KERNEL IS NOT SEANDROID ENFORCING"...
Now flashing original ROM again.
Click to expand...
Click to collapse
Seems to be a common problem. Hopefully an update to it will fix it.

S4 I9500 Bricked while installing rom...

Hi, I had my S4 with stock rom 4.3 with adam kernel and philz touch recovery, tried to install via odin the stock rom 4.4.2 TTT but because of a CPU problem the usb connection was interrupted while installing. Now I'm stuck at download mode.
Here's details.
Download mode:
ODIN MODE
PRODUCT NAME: GT-I9500
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX WARRANTY VOID: 1
RP SWREV: A3
After attempting install rom via odin:
appears the same in download mode plus this line:
SW REV. CHECK FAIL. DEVICE:-3, BINARY:2
Odin log:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9500UBUEMK1_I9500UUBEMK1_I9500UBUEMK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've already tried the same with the PIT file but still doesn't work, anybody got a clue?

Anybody? I need my phone back :S

chemell said:
Anybody? I need my phone back :S
Click to expand...
Click to collapse
Odin was interrupted at the bootloader update (sboot.bin). You need the "factory ROM" to flash it, however I am not aware if anything for 4.2.2 would be available for now.

spamtrash said:
Odin was interrupted at the bootloader update (sboot.bin). You need the "factory ROM" to flash it, however I am not aware if anything for 4.2.2 would be available for now.
Click to expand...
Click to collapse
But can I use another rom? I don't care if isn't a 4.2.2 rom because I need the phone again doesn't matter with which rom or android version.

If u can boot to recovery flash a custom rom then flash stock via odin

aayushkhajuria2842 said:
If u can boot to recovery flash a custom rom then flash stock via odin
Click to expand...
Click to collapse
I can't, I only got download mode...

Try the right key combination .....its nt possible that you can have download mode but nt recovery
Press and hold Volume Up, Home and Power

aayushkhajuria2842 said:
Try the right key combination .....its nt possible that you can have download mode but nt recovery
Press and hold Volume Up, Home and Power
Click to expand...
Click to collapse
Well it doesn't work, when I turn on the phone a black screen with a cellphone, a warning sign and a monitor appears and a text says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
With this screen I can only go into download mode but when I try recovery mode it just puts the screen black and back to the same text and pictures.
Another thing that worries me it's that I can't turn the phone off with the button, only if I pull the battery out.

This can be recovered I had same prblm some months ago bt I just flashed stock firmware nd it was fixed u may try flashing stock rom again

aayushkhajuria2842 said:
This can be recovered I had same prblm some months ago bt I just flashed stock firmware nd it was fixed u may try flashing stock rom again
Click to expand...
Click to collapse
I've already tried with the rom "I9500UBUEMK1_I9500UUBEMK1_I9500UBUEMK1_HOME.tar.md5" (I believe it's stock rom) and get the odin error that appears in my first post...

Try some other firmware of you own region ......... 4.3 or 4.4 whichever u have for your region .......I think then u will nt get same error

chemell said:
Hi, I had my S4 with stock rom 4.3 with adam kernel and philz touch recovery, tried to install via odin the stock rom 4.4.2 TTT but because of a CPU problem the usb connection was interrupted while installing. Now I'm stuck at download mode.
Here's details.
Download mode:
ODIN MODE
PRODUCT NAME: GT-I9500
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX WARRANTY VOID: 1
RP SWREV: A3
After attempting install rom via odin:
appears the same in download mode plus this line:
SW REV. CHECK FAIL. DEVICE:-3, BINARY:2
Odin log:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9500UBUEMK1_I9500UUBEMK1_I9500UBUEMK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've already tried the same with the PIT file but still doesn't work, anybody got a clue?
Click to expand...
Click to collapse
Hi, try to flash through kies emergency firmware recovery.

navdeepavi said:
Hi, try to flash through kies emergency firmware recovery.
Click to expand...
Click to collapse
Hi, I tried, but in Kies I can't get trough the "Connecting..." status so when I choose "Emergency firmware recovery" the list of devices appears empty.

I think u should try flashing some other stock firmware I hav had the prblm before

aayushkhajuria2842 said:
I think u should try flashing some other stock firmware I hav had the prblm before
Click to expand...
Click to collapse
Hi, I'm downloading another firmware now. But I don't think it will work, i've tried with a pack I found (firmware+pit+booloader+cp+csc) and didn't work. Also I tried just flashing only de BP file and keep getting the same error:
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
I don't know what to do but I'm downloading an ARO stock firmware (4.3) and I'll try...

It should work I did the same thing but cant say anything

aayushkhajuria2842 said:
I think u should try flashing some other stock firmware I hav had the prblm before
Click to expand...
Click to collapse
Obviously not. simple flash of ROM is not sorting out the corrupted bootloader problem.
---------- Post added at 07:52 AM ---------- Previous post was at 07:45 AM ----------
chemell said:
Hi, I'm downloading another firmware now. But I don't think it will work, i've tried with a pack I found (firmware+pit+booloader+cp+csc) and didn't work. Also I tried just flashing only de BP file and keep getting the same error:
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
I don't know what to do but I'm downloading an ARO stock firmware (4.3) and I'll try...
Click to expand...
Click to collapse
considering your situation, I doubt if it will work. you have to pick from two scenarios:
a) your download mode shows warranty void, knox void, custom: then you have to go to step 2 below.
b) your download mode shows all statuses samsung or official or 0x0 - then go to 1
1. Call samsung service center, they shall sort it out under the warranty.
2. More complicated, if you do not want to pay for repairs.
DELETED, procedure was for I9505 ONLY
you have to follow the procedure form this link instead.
Good luck.

spamtrash said:
Obviously not. simple flash of ROM is not sorting out the corrupted bootloader problem.
---------- Post added at 07:52 AM ---------- Previous post was at 07:45 AM ----------
considering your situation, I doubt if it will work. you have to pick from two scenarios:
a) your download mode shows warranty void, knox void, custom: then you have to go to step 2 below.
b) your download mode shows all statuses samsung or official or 0x0 - then go to 1
1. Call samsung service center, they shall sort it out under the warranty.
2. More complicated, if you do not want to pay for repairs.
You will need the PC with not faulty CPU, first.
Then, you have to use the PIT from here
Of course, you will need the Qualcomm drivers as well, from here or this one
Then, you have to follow the relatively simple procedure described here
That shall fix the corrupted bootloader, and I hope that you will not see the described there errors which would point to the hardware problem.
Good luck.
Click to expand...
Click to collapse
Warning!
He said he is in trouble with a I9500 device, so the Qualcomm drivers will not help....much.

Just an observation, you said you have no recovery right? So have you tried just flashing the tar of PhilZ recovery using Odin to get it back?
At least then you'll have a recovery again and can move forward with a custom ROM install
Sent from my GT-I9505 using XDA Premium HD app

lolo9393 said:
Warning!
He said he is in trouble with a I9500 device, so the Qualcomm drivers will not help....much.
Click to expand...
Click to collapse
right. the correct one provided.

[Q] Soft brick at&t note 3?

Hi
I have AT&T Note 3 , sim unlock from carrier, successful kingo root 0x0 Knox (startup splash screen says Custom Unlock)
So, I was hopped up on percocets because of my recent surgery and i decided i was in conscious enough mind to tackle getting AWS unlock. I wasn't.
I was reading about chainfire regionaway app, so i went to the app store and downloaded the first chainfire app that popped up - 3D. so now i am stuck in the note 3 splash screen. yes i know i should have read it more carefully, etc. but i just wasn't all there at the time. Please help me save this $500 brick!
I've been reading these methods:
http://www.droidviews.com/how-to-unbrick-att-galaxy-note-3-sm-n900a/
i can get the phone recognized in ODIN, but the secure check fail: cache occurs
http://forum.xda-developers.com/showthread.php?t=2567133
i can't download any of these files...
http://forum.xda-developers.com/showthread.php?t=2507403
tried this but didn't work.
i'm really not making any headway... any help would be much appreciated.
side note:
can i send this in for warranty? Since AT&T just release the kitkat update can i claim that i tried to update and it failed?
current binary: samsung official
system status: custom (not official)
Knox lock 0x0
Knox warranty void 0x0
EDIT: After doing the ODIN fail - it is stuck in ODIN mode and says "firmware upgrade encountered an issue. Please select recory mode in Kies & try again."
Can not enter download mode. But still connects in ODIN
thanks!

Yes you can return. Best bet as Knox counter is still 0.
If you try other methods and they don't work, you may tripe Knox.
Even you connect to your pc is the phone on download mode?

kenny1991 said:
Yes you can return. Best bet as Knox counter is still 0.
If you try other methods and they don't work, you may tripe Knox.
Even you connect to your pc is the phone on download mode?
Click to expand...
Click to collapse
when i connect to PC it recognizes in ODIN but KIES does not recognize it.
It won't go into reboot mode (vol up + power + home)
it only boots into ODIN mood

firstsx said:
when i connect to PC it recognizes in ODIN but KIES does not recognize it.
It won't go into reboot mode (vol up + power + home)
it only boots into ODIN mood
Click to expand...
Click to collapse
Lol?
What are you trying to do here? Flashing anything?
Is it 4.3 or 4.4 os?
Never run kies side by side Odin add the last one hates the first. Kies is useless.
Kill it and restart your pc. Don't run kies services when using Odin.
I think you should download your firmware from sammobile.com and flash it.
Take battery out and then try download mode again. After killing kies you should be able to use Odin to flash.
---------- Post added at 10:35 PM ---------- Previous post was at 10:32 PM ----------
I don't know. But flashing kitkat may tripe Knox i don't know atnt models. If you don't want to flash then return it.

kenny1991 said:
Lol?
What are you trying to do here? Flashing anything?
Is it 4.3 or 4.4 os?
Never run kies side by side Odin add the last one hates the first. Kies is useless.
Kill it and restart your pc. Don't run kies services when using Odin.
I think you should download your firmware from sammobile.com and flash it.
Take battery out and then try download mode again. After killing kies you should be able to use Odin to flash.
Click to expand...
Click to collapse
lol sorry!
ok if i run KIES (because the screen says connect to kies and do recovery mode) it does not recognize. I am not trying to connect ODIN and kies at the same time!
it was 4.3
i download the sammobile file - it says:
SQ Rev Check fail: [sbl1]Fused 2 > Binary 1

firstsx said:
lol sorry!
ok if i run KIES (because the screen says connect to kies and do recovery mode) it does not recognize. I am not trying to connect ODIN and kies at the same time!
it was 4.3
i download the sammobile file - it says:
SQ Rev Check fail: [sbl1]Fused 2 > Binary 1
Click to expand...
Click to collapse
Where does it say? Kies? Again kies is useless. I don't think it supports note 3.
This is your firmware. http://www.sammobile.com/firmwares/3/?download=25106
You know how to flash?

kenny1991 said:
Where does it say? Kies? Again kies is useless. I don't think it supports note 3.
This is your firmware.
You know how to flash?
Click to expand...
Click to collapse
yes i know its useless, the phone itself tells me to connect to kies. I just tried it once to see if it would rexognize but it does not!
Yes i downloaded the firmware from sammobile, put it into the AP portion of ODIN and start.
but when i run it, it fails and says this on my phone
SQ Rev Check fail: [sbl1]Fused 2 > Binary 1

firstsx said:
yes i know its useless, the phone itself tells me to connect to kies. I just tried it once to see if it would rexognize but it does not!
Yes i downloaded the firmware from sammobile, put it into the AP portion of ODIN and start.
Click to expand...
Click to collapse
hm. Still no recovery mode?
Past your Odin log so someone can see why it fails.

<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900AUCUBMI9_N900AATTBMI9_N900AUCUBMI9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Need pit file?

kenny1991 said:
Need pit file?
Click to expand...
Click to collapse
sammobile doesn't say anything about pit file?
i only used the AP file from there
i have HLTE__USA_ATT_32G_pit file even when i use that PIT file with the AP file it still gives me the same fail error...
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900AUCUBMI9_N900AATTBMI9_N900AUCUBMI9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

firstsx said:
i download the sammobile file - it says:
SQ Rev Check fail: [sbl1]Fused 2 > Binary 1
Click to expand...
Click to collapse
This means you are trying to flash a version older than what is currently installed. Try the next higher revision, or find one that doesn't include a bootloader.
Sent from my leanKernel 2.3 powered stock 4.4.2 SM-N900T

toastido said:
This means you are trying to flash a version older than what is currently installed. Try the next higher revision, or find one that doesn't include a bootloader.
Sent from my leanKernel 2.3 powered stock 4.4.2 SM-N900T
Click to expand...
Click to collapse
how can there be a newer version, it was never updated to kitkat?
sammobile only lists that version and i'm quite certain it was 4.3
so if i don't flash the bootloader, what do i flash?
can i not use these files?
AP_N900AUCUBMJ5.zip
BL_N900AUCUBMJ5.zip
CP_N900AUCUBMJ5.zip
HLTE_USA_ATT_32G.pit

firstsx said:
how can there be a newer version, it was never updated to kitkat?
sammobile only lists that version and i'm quite certain it was 4.3
so if i don't flash the bootloader, what do i flash?
can i not use these files?
AP_N900AUCUBMJ5.zip
BL_N900AUCUBMJ5.zip
CP_N900AUCUBMJ5.zip
HLTE_USA_ATT_32G.pit
Click to expand...
Click to collapse
Hi mate,
if you are stuck, maybe you can try this.
http://forum.xda-developers.com/showthread.php?t=2701062
it's a way to unbrick your software.
and update to 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

Markudsc said:
Hi mate,
if you are stuck, maybe you can try this.
http://forum.xda-developers.com/showthread.php?t=2701062
it's a way to unbrick your software.
and update to 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
Click to expand...
Click to collapse
can i use this method
http://forum.xda-developers.com/showthread.php?t=2559715
it seems pretty much the same, except yours includes updating to kitkat.
if i do kitkat, can i still keep root?
will this trip knox?

Ok i did this method
http://forum.xda-developers.com/showthread.php?t=2559715
i re-downloaded all the files because the files i had just wouldn't work in ODIN or anything. so based your advice i just downloaded new files.
ODIN flash was successful
then i did the rest of the steps successfully! and i am back!

Soft Bricked S4

*****************Thread can be closed as issue has been resolved*****************
I think I have soft bricked my phone.
I tried this tutorial and everything went according to the instructions except that the wifi couldn't be turned on.
So I opened a thread asking for help regarding my wifi, I was advised to flash a custom ROM (Android 5.0.1 Lollipop SDK 21) thru TWRP but I must have done something wrong because the phone was stuck in Android System Recovery.
Then I was advised to flash the original firmware thru Odin (Android 4.2.2) and that's where I think the brick happened.
The phone can go into download mode but there is a gray line that says "Write protection: Enable" and everything I try to flash thru Odin gives the same fail error:
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Urgent help is much appreciated as I have no other phone and I have been incommunicated for a week+ now
UPDATE:
I just tried to go into Android System Recovery just now it worked! I swear I wasn't able to. It says on top:
LRX22C.I337UCSGOK3 (I was on NB1, where could have this come from?)
And has a couple extra options I had never seen before (last 3 or 4 from the list:
reboot system now (tried it and gets stuck on Samsung logo)
apply update from ADB
apply update from external storage
apply update from cache
wipe data/factory reset
wipe cache partition
reboot to bootloader
power down
view recovery logs
Enable cp logging
Disable cp logging
At the end of the recovery screen there are 2 lines in red:
failed to mount "/system" (Invalid Argument)
E: failed to mount /system (Invalid Argument)

What is the model # in download mode?

audit13 said:
What is the model # in download mode?
Click to expand...
Click to collapse
It says:
Product Name: SGH-I337
PS: Sorry I didn't specify because I thought this forum section was only that model.

The bootloader on the sgh-i337 is locked while the bootloader on the sgh-i337m is unlocked. which means you cannot flash TWRP or CWM to the sgh-i337.
Look here: https://forum.xda-developers.com/ga...-to-update-to-i337oc3-5-0-1-keeproot-t3075814 and note the following comments from that thread.
Notes:
1. The above process will not affect your Knox Warranty Flag.
2. The process will update your Modem, Non-hlos, System, Kernel, and Stock Recovery.
3. No need to wipe prior to flashing! The ROM will automatically perform a factory data reset.
4. If you are not already rooted (or to unbrick) you must first flash the I337UCUFNB1_Rootable_Full_Odin.tar (use Odin's PDA slot (AP in Odin v3.09+).​

audit13 said:
The bootloader on the sgh-i337 is locked while the bootloader on the sgh-i337m is unlocked. which means you cannot flash TWRP or CWM to the sgh-i337.
Look here: https://forum.xda-developers.com/ga...-to-update-to-i337oc3-5-0-1-keeproot-t3075814 and note the following comments from that thread.
Notes:
1. The above process will not affect your Knox Warranty Flag.
2. The process will update your Modem, Non-hlos, System, Kernel, and Stock Recovery.
3. No need to wipe prior to flashing! The ROM will automatically perform a factory data reset.
4. If you are not already rooted (or to unbrick) you must first flash the I337UCUFNB1_Rootable_Full_Odin.tar (use Odin's PDA slot (AP in Odin v3.09+).​
Click to expand...
Click to collapse
Mine is not the "M" version.
What am I supposed to get from those notes? Are you suggesting I follow the steps in that thread?
I'm not too technical, but I can follow steps.

If you are to unbrick you must first flash the I337UCUFNB1_Rootable_Full_Odin.tar (use Odin's PDA slot (AP in Odin v3.09+)

What bootloader are you on? Only the MDL bootloader can use the 4.2.2 Odin firmware.

audit13 said:
If you are to unbrick you must first flash the I337UCUFNB1_Rootable_Full_Odin.tar (use Odin's PDA slot (AP in Odin v3.09+)
Click to expand...
Click to collapse
I am on NB1, will try this tru Odin and will report back.

StoneyJSG said:
What bootloader are you on? Only the MDL bootloader can use the 4.2.2 Odin firmware.
Click to expand...
Click to collapse
Is the bootloader that one at the top of the Android System Recovery? If so, mine says:
LRX22C.I337UCSGOK3

audit13 said:
If you are to unbrick you must first flash the I337UCUFNB1_Rootable_Full_Odin.tar (use Odin's PDA slot (AP in Odin v3.09+)
Click to expand...
Click to collapse
It seems that I already had tried this because when I extracted the file it had to be replaced on my Desktop. Anyways I tried it again and it said the same thing:
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

UPDATE:
Somehow I can go into recovery now and it says LRX22C.I337UCSGOK3 and unable to mount /system. Please refer to first post for complete info about this.

Publish the Odin log of possible.
You tried using different usb cables and usb ports?

audit13 said:
Publish the Odin log of possible.
You tried using different usb cables and usb ports?
Click to expand...
Click to collapse
I have successfully flashed stuff using this cable. I do swicth usb ports every time I get a fail just to make sure.
I really think the fail is due to the "Write Protection: Enabled" legend that appears on my screen as it wasn't there before and I was able to flash without mayor issues.
I'll try using a new cable now but I don't think I'll get a different result.
Will post the entire logs when I do.

Holy_Purple said:
I have successfully flashed stuff using this cable. I do swicth usb ports every time I get a fail just to make sure.
I really think the fail is due to the "Write Protection: Enabled" legend that appears on my screen as it wasn't there before and I was able to flash without mayor issues.
I'll try using a new cable now but I don't think I'll get a different result.
Will post the entire logs when I do.
Click to expand...
Click to collapse
OMG! I tried a new cable and it went thru!!! I cannot believe my eyes! and the wifi is working!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUFNB1_TWRootable_Full_Odin.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004> tz.mbn
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> persdata.img.ext4
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> non-hlos.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)

You were on the OK3 bootloader. Now you're on the NB1 bootloader. You're stuck with using safe strap recovery and can only boot custom ROMs based on touchwiz as your bootloader is locked and can no longer be exploited with loki doki.

StoneyJSG said:
You were on the OK3 bootloader. Now you're on the NB1 bootloader. You're stuck with using safe strap recovery and can only boot custom ROMs based on touchwiz as your bootloader is locked and can no longer be exploited with loki doki.
Click to expand...
Click to collapse
Thanks for the info! I won't be messing with my phone any more, haha :victory:

Glad you got it fixed
I always have a few Samsung cables on hand for flashing.