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

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.

Galaxy Grand 2 (SM-G7102) stuck in Recovery Booting after firmware update via ODIN

Ok am new here and have to admit that I've had a pretty long day trying to figure out what exactly went wrong with my Galaxy Grand 2 (SM-G7102) after flashing the 4.4.2 Official firmware I downloaded from sammobile to the device using Odin. The process is successful, no errors whatsoever from Odin but when the device restarts it shows the usual Samsung Galaxy Grand 2 logo with some tiny blue text at the top "Recovery Booting" and from there nothing else happens.
I have tried to flash the firmware again using a different PC, USB cable and even Odin version but I get the same result. Previously my device was running Android 4.3 and I wanted to upgrade to Android 4.4.2.
Here is what I get from Odin.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G7102DDUBNK1_G7102ODDBNK1_G7102DDUBNK1_HOME.tar.md 5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.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> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
--------------------------------------------------------------------------------------------------
And this is what I get when I enter download mode on my phone:
ODIN MODE
PRODUCT NAME: SM-G7102
CURRENT BINARY: Official
SYSTEM STATUS: Official
KNOX WARRANTY VOID: 0X1 (4)
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWEREV: S2, T2, A2, A2, P1
SECURE DOWNLOAD: ENABLE
UDC START
------------------------------------------------------
So you know, I have even tried flashing a number of custom recoveries such as CWM and the likes to no avail, I either get: "RECOVERY IS NOT SEANDROID ENFORCING" or "COULD NOT DO NORMAL BOOT".
Please help me out guys, I have flashed countless Samsung devices with Odin before but I have never encountered such a situation, what could be the problem here? And better yet, how can it be fixed?

edutchz said:
Ok am new here and have to admit that I've had a pretty long day trying to figure out what exactly went wrong with my Galaxy Grand 2 (SM-G7102) after flashing the 4.4.2 Official firmware I downloaded from sammobile to the device using Odin. The process is successful, no errors whatsoever from Odin but when the device restarts it shows the usual Samsung Galaxy Grand 2 logo with some tiny blue text at the top "Recovery Booting" and from there nothing else happens.
I have tried to flash the firmware again using a different PC, USB cable and even Odin version but I get the same result. Previously my device was running Android 4.3 and I wanted to upgrade to Android 4.4.2.
Here is what I get from Odin.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G7102DDUBNK1_G7102ODDBNK1_G7102DDUBNK1_HOME.tar.md 5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.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> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
--------------------------------------------------------------------------------------------------
And this is what I get when I enter download mode on my phone:
ODIN MODE
PRODUCT NAME: SM-G7102
CURRENT BINARY: Official
SYSTEM STATUS: Official
KNOX WARRANTY VOID: 0X1 (4)
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWEREV: S2, T2, A2, A2, P1
SECURE DOWNLOAD: ENABLE
UDC START
------------------------------------------------------
So you know, I have even tried flashing a number of custom recoveries such as CWM and the likes to no avail, I either get: "RECOVERY IS NOT SEANDROID ENFORCING" or "COULD NOT DO NORMAL BOOT".
Please help me out guys, I have flashed countless Samsung devices with Odin before but I have never encountered such a situation, what could be the problem here? And better yet, how can it be fixed?
Click to expand...
Click to collapse
Hi bro i have exactly the same problem and try to flash cystom recovires and i tried to back to 4.3 byt odin give me fail
So please if you solve it tell how

try this
1. Boot to recovery, turn off the phone then press Home +
Power + Volume up
2. wipe data / factory reset
3. Wipe Cache partition
4. Remove battery and put it back after 30 seconds
5. Boot to Download Mode, turn off the phone then press
Home + Power + Volume Down then volume up
6. Flash Firmware via ODIN be sure uncheck
AUTO REBOOT and wait to be completed
7 when odin show message 'pass' unplug the cable and Remove battery again and put it back after 30 seconds
8 now switch on the mobile but don't restart it just goto to recovery mode agAin and and follow the the step 1 and 2 again
then reboot
your problem solved
its just like downgrading of mobile but it work
(if this not work the try to install custom recovery like cwm)
note: I am not responsible for any harm or brick of your mobile try it own your risk
this step are my opinion not recommendations
but I had test this method for same problem)

@android_smater bro it's won't boot to recovery at all that is the problem

altayeb hoota said:
@android_smater bro it's won't boot to recovery at all that is the problem
Click to expand...
Click to collapse
does it go automatically into download mode or just hang on when samsung galaxy grand 2 sm-g7102 apper
try to install cwm and then goto recovery mode

android_smater said:
does it go automatically into download mode or just hang on when samsung galaxy grand 2 sm-g7102 apper
try to install cwm and then goto recovery mode
Click to expand...
Click to collapse
i tried to install cwm or twrp but still nothing happen just galaxy grand2 sm-g7102 logo with blue text"recovery booting at the top"
i can't access recovery with stock recovery or any custom recovery at all
and also i can't be able to flash android 4.3 odin gives me "fail" but kitkat flashed fine but when it finished i got the same problem

edutchz said:
Ok am new here and have to admit that I've had a pretty long day trying to figure out what exactly went wrong with my Galaxy Grand 2 (SM-G7102) after flashing the 4.4.2 Official firmware I downloaded from sammobile to the device using Odin. The process is successful, no errors whatsoever from Odin but when the device restarts it shows the usual Samsung Galaxy Grand 2 logo with some tiny blue text at the top "Recovery Booting" and from there nothing else
try to downgrade to NH6 use my thread it will work
http://forum.xda-developers.com/galaxy-grand-2/general/how-to-downgrade-to-nh6-t2913368
Click to expand...
Click to collapse

then take your mobile to service centre. .

please help me.i have this problem with grand 2
i dont know how can i fix it...please tell me..if you resolved.

For anyone who still has this problem on their Galaxy Grand 2, apparently I never found a way to fix it. But after giving up on the phone and giving it to my cousin, he was more patient than me and he left the phone powered on while stuck on the Logo screen and after say 30 minutes to 1 hour the phone booted up.
The phone works normally, however should you power it down..turning it on again will take it roughly 30 mins to an hour to get past the initial Logo screen, am not sure why but that is how it now behaves.
Try connecting it to a charger while you wait for it to boot, hopefully it will work for you as well.

Thanks

I no how to fix the problem is i think u have not downloaded of ur region

Same damn problem here
Problem seems to be related to fake Samsung Phones. I went to the Samsung assistance centre in Guangzhou (China) and they felt quite embarrassed to tell me that although I may accept to pay any fee they charge they cannot fix my phone because it is not made by Samsung and that is easily the reason why it has a faulty boot manager, probably hacked by incompetents.
Either the phone is fake or the official Samsung Service centre here is, in any case there seems to be no way around it.
I a looking now for some way to reload the original boot loader and then restart from there.

I am having exactly this same problem. I actually installed a Custom ROM from here, but the ROM had some bugs and I later decided to go back to the official firmware from Smasung, only to get stuck on the Samsung boot.

i am here with the same problem with some minor changes
my galaxy grand 2 duos showing
Could not do normal boot.
ODIN MODE
PRODUCT NAME:SM G 7102
CURRENT DINARY:Custom
SYSTEM STATUS:Custom
KNOX WARRANTY VOID:0*0
QUALCOMM SECUREBOOT:Enable <CSD>
RP SWREV: S2, T2,R2,A2,P2
SECURE DOWNLOAD:ENABLE
UDC START
AFTER A BIG GREEN ANDROID LOGO
Downloading...
Do not turn off target!!

Has anyone found solution yet? I'm having same problem with my Grand 2 Duos.
only download mode is working. Can't boot to recovery or normal.
After leaving in charging for 15-20 mins, I got white flash-logo( something new then ever).
So keeping it in charging for more time. let's see...!
PS: phone starts with grand 2 logo and then samsung comes up with audio. that's it ! after 3-4 mins later reboots and so on.
in recovery mode it shows android symbal and loading bar.. then it reboots in normal mode. and so on.

I guess you guys have downloaded a wrong firmware. I mean, sure it says it's for Grand 2 but the "Region" is different. Try downloading the one for your region like if you are from India, you gotta need indian version that is INS.
Sent from my SM-G7102 using Tapatalk

My SM G7102 does not go to download mode or recovery mode! It keeps restarting automatically after inserting battery! If i somehow go to recovery mode or download mode i would repair this . Please anyone help about this

oodjacid said:
My SM G7102 does not go to download mode or recovery mode! It keeps restarting automatically after inserting battery! If i somehow go to recovery mode or download mode i would repair this . Please anyone help about this
Click to expand...
Click to collapse
take the battery out and try go in to download mode

SoUnd001 said:
take the battery out and try go in to download mode
Click to expand...
Click to collapse
It doesn't go to recovery/download mode without battery

[Q] Installing stock ROM on S4 with Cyanogenmod

Hello,
Unfortunately, I have Cyanogenmod on my Galaxy S4 GT-I9505 (in UK on O2). I want to unlock the phone, which apparently involves going back to a stock ROM.
After much searching around, I've eventually managed to download a stock ROM that wasn't corrupt, and Odin, and USB drivers. But when I try to do the firmware upgrade thing, it fails. I now seem to have a brick. How I hate Cyanogenmod!
Here's what happens in Odin:
<OSM> I9505XXUEMK8_I9505O2UEMK1_I9505XXUEMK8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
...and all I get on the screen of my phone is "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". Except I can't use Kies (or Smartswitch) because it's a stupid Cyanogenmod phone so Kies (or Smartswitch) doesn't recognise its existence! GRRRRR!
So, do I have a brick that is completely useless? I've only had this phone a month or so (I bought it, tragically, with cyanogenmod on it).
Any suggestions/help/sympathy would be GREATLY appreciated! (please!)
- Paul

hellopaul said:
Hello,
Unfortunately, I have Cyanogenmod on my Galaxy S4 GT-I9505 (in UK on O2). I want to unlock the phone, which apparently involves going back to a stock ROM.
After much searching around, I've eventually managed to download a stock ROM that wasn't corrupt, and Odin, and USB drivers. But when I try to do the firmware upgrade thing, it fails. I now seem to have a brick. How I hate Cyanogenmod!
Here's what happens in Odin:
<OSM> I9505XXUEMK8_I9505O2UEMK1_I9505XXUEMK8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
...and all I get on the screen of my phone is "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". Except I can't use Kies (or Smartswitch) because it's a stupid Cyanogenmod phone so Kies (or Smartswitch) doesn't recognise its existence! GRRRRR!
So, do I have a brick that is completely useless? I've only had this phone a month or so (I bought it, tragically, with cyanogenmod on it).
Any suggestions/help/sympathy would be GREATLY appreciated! (please!)
- Paul
Click to expand...
Click to collapse
It has nothing to do with Cyanogenmod all your problems. You are putting the blame in the wrong corner. Kies not recognizing, the failure of the flash, not being sim-unlock has nothing to do with Cyanogenmod. But with you not reading enough.
You want to flash a 4.2.2 rom and you can only do that if you are not on a knox bootloader. What is the text when you boot in download mode?
And btw, as far as I know you don't need to downgrade your FIRMWARE, but only your MODEM.

Thanks for your quick reply!
Lennyz1988 said:
You want to flash a 4.2.2 rom and you can only do that if you are not on a knox bootloader. What is the text when you boot in download mode?
Click to expand...
Click to collapse
Here's the text:
ODIN MODE
PRODUCT NAME: GT-I9505
CURRENT BINARY: Custom
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE: enabled​
And btw, as far as I know you don't need to downgrade your FIRMWARE, but only your MODEM.
Click to expand...
Click to collapse
Is that an easier process?
I was using Android 5.0.2 with Cyanagenmod. I'm not sure what version the ROM I downloaded was - it actually downloaded and wasn't a corrupt .zip file, which seems to be a very very rare thing. Might attempting to install a 4.x.x firmware over a 5.x.x cause problems? Is there anywhere I can reliably download a 5.x.x ROM that actually works? I've wasted several days searching for a UK O2 ROM. I can recommend plenty of sites that CLAIM to have it, but it's corrupted or just doesn't download due to any number of errors.

hellopaul said:
Thanks for your quick reply!
Here's the text:
ODIN MODE
PRODUCT NAME: GT-I9505
CURRENT BINARY: Custom
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE: enabled​
Is that an easier process?
I was using Android 5.0.2 with Cyanagenmod. I'm not sure what version the ROM I downloaded was - it actually downloaded and wasn't a corrupt .zip file, which seems to be a very very rare thing. Might attempting to install a 4.x.x firmware over a 5.x.x cause problems? Is there anywhere I can reliably download a 5.x.x ROM that actually works? I've wasted several days searching for a UK O2 ROM. I can recommend plenty of sites that CLAIM to have it, but it's corrupted or just doesn't download due to any number of errors.
Click to expand...
Click to collapse
Here an whole post with firmwares.
http://forum.xda-developers.com/showpost.php?p=41072392&postcount=2
Try flashing a 4.4.2. firmware. If flash is succesfull, then downgrade modem to 4.2.2.
If it's not, then pick an 5.0.1 firmware and downgrade modem to 4.2.2.
4.2.2 modem:
http://d-h.st/CXx
When you are done with what you want to do ( I assume something with region away). Flash AGAIN the 4.4.2 firmware or 5.01. You cannot stay on the 4.2.2 modem.

Thank you for your help with this!
I managed to un-brick my phone (hooray!) using 'Philz Touch' and some of the advice here: http://forum.xda-developers.com/galaxy-s4/general/guide-t3018625
I just re-downloaded that firmware from the site you suggested - that's where I managed to download the (exact same) firmware before. I've just tried installing it again, but got exactly the same error in Odin. I've currently got another ROM downloading from one of the dodgy 'teenage-hacker' sites (Rapidgator.net). I assume that it won't even unzip, but it will be tomorrow before it's completed the download.
I'm guessing that I need to download firmware that's UK and O2 (I'm in the UK and my phone's locked to O2). This rather limits my options - there only seem to be a couple of places on the net with this ROM (neither of which work). If I installed, say, a Vodafone ROM, then unlocked the phone, should that (in theory) then work with my O2 (or any other) SIM? I plan to switch to BT Mobile (running on the EE network) shortly - hence wanting to unlock the phone.

hellopaul said:
Thank you for your help with this!
I managed to un-brick my phone (hooray!) using 'Philz Touch' and some of the advice here: http://forum.xda-developers.com/galaxy-s4/general/guide-t3018625
I just re-downloaded that firmware from the site you suggested - that's where I managed to download the (exact same) firmware before. I've just tried installing it again, but got exactly the same error in Odin. I've currently got another ROM downloading from one of the dodgy 'teenage-hacker' sites (Rapidgator.net). I assume that it won't even unzip, but it will be tomorrow before it's completed the download.
I'm guessing that I need to download firmware that's UK and O2 (I'm in the UK and my phone's locked to O2). This rather limits my options - there only seem to be a couple of places on the net with this ROM (neither of which work). If I installed, say, a Vodafone ROM, then unlocked the phone, should that (in theory) then work with my O2 (or any other) SIM? I plan to switch to BT Mobile (running on the EE network) shortly - hence wanting to unlock the phone.
Click to expand...
Click to collapse
You are not reading what I wrote. You CANNOT flash the firmware you tried before. It's impossible because that version is to old. You are downloading a 4.2.2 and you need need 4.4.2 minimal (possible even 5.0.1 minimum).

I have no way of telling which version that firmware was - it was listed under United Kingdom and had O2 in the filename. No version number.
So - back to my previous question - should I be able to use, say, a Vodafone 4.4.2 firmware without risk of bricking my phone? Or maybe the BTU 5.0.1 version? And then be able to do the standard Samsung S4 process to unlock it? I guess I'll just try it and see if it works.

No. You need to download the latest ROM for your carrier, here. Once you have installed that firmware, you must install through Odin a 4.2.2 modem found at the link Lennyz1988 provided. Only then can you use the service menu method or RegionLock Away to unlock the S4. After that, extract the modem from the firmware package you downloaded and flash it through Odin.
Honestly, spend the money and unlock the phone, if O2 won't do it. An unlock code is virtually guaranteed to work, unlike the unlock methods in the forums.

Unfortunately that firmware you linked to is one of the many corrupt .zip files out there, and will not decompress at all.
I've got another firmware downloading (very very slowly) from Rapidgator. It will probably also be corrupt.
I've called a couple of local phone unlocking shops, and they don't have a clue what Cyanagenmod is, and whether it will affect the unlockability of the phone. I'll just pay an ebayer to give me an unlock code, in the hope that it might unlock it, despite what I've read. Most people say I must go back to a stock ROM before unlocking.
Ugh. Awful Cyanogenmod.

hellopaul said:
Unfortunately that firmware you linked to is one of the many corrupt .zip files out there, and will not decompress at all.
I've got another firmware downloading (very very slowly) from Rapidgator. It will probably also be corrupt.
I've called a couple of local phone unlocking shops, and they don't have a clue what Cyanagenmod is, and whether it will affect the unlockability of the phone. I'll just pay an ebayer to give me an unlock code, in the hope that it might unlock it, despite what I've read. Most people say I must go back to a stock ROM before unlocking.
Ugh. Awful Cyanogenmod.
Click to expand...
Click to collapse
The archives are not corrupt. Something is wrong at your end.
And again, CM has nothing to do with your issues. If you were on the stock rom you would just have had the same problem.

If I was on a stock ROM I wouldn't have to go through all this, and could presumably just unlock my phone very easily, as outlined on many sites, such as giffgaff (I cannot post links in this forum yet).
I cannot get that ROM to unzip, using 7-zip, WinRAR, Mac OS X Finder, Mac OS X Terminal. I've downloaded it at least 3 times, and it's always corrupt. Mac OS X Terminal reports "bad zipfile offset (local header sig): 0".
Uh?? Update: I've just tried 7-zip again...and it's decompressed it! How utterly bizarre.
I just tried it with Odin and it did not work - the usual result:
<OSM> I9505XXUEMK8_I9505O2UEMK1_I9505XXUEMK8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)​
Then I have to turn off the phone, and use Philz Touch to bring it back to life.

hellopaul said:
If I was on a stock ROM I wouldn't have to go through all this, and could presumably just unlock my phone very easily, as outlined on many sites, such as giffgaff (I cannot post links in this forum yet).
I cannot get that ROM to unzip, using 7-zip, WinRAR, Mac OS X Finder, Mac OS X Terminal. I've downloaded it at least 3 times, and it's always corrupt. Mac OS X Terminal reports "bad zipfile offset (local header sig): 0".
Uh?? Update: I've just tried 7-zip again...and it's decompressed it! How utterly bizarre.
I just tried it with Odin and it did not work - the usual result:
<OSM> I9505XXUEMK8_I9505O2UEMK1_I9505XXUEMK8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)​
Then I have to turn off the phone, and use Philz Touch to bring it back to life.
Click to expand...
Click to collapse
Yes ofcourse it fails. You are not following my instructions.
You are flashing a 4.3 rom which is IMPOSSIBLE for you. Your bootloader is at least a 4.4.2 version, probably even a 5.0.1 version. So you can only flash those stock roms.

Lennyz1988 said:
Yes ofcourse it fails. You are not following my instructions.
You are flashing a 4.3 rom which is IMPOSSIBLE for you. Your bootloader is at least a 4.4.2 version, probably even a 5.0.1 version. So you can only flash those stock roms.
Click to expand...
Click to collapse
Sorry if I'm not following you. How can you tell what version the firmware file is? The site I downloaded it from claimed it was 5.0.1.
My phone's Android version is 5.0.2
I've been putting the firmware file into Odin's AP slot.
I haven't done anything with the BL (presumably bootloader) slot.
Isn't there a way I can completely wipe the phone, then install whatever firmware I want, regardless of what was previously installed?

alright let's try something else.
Flash this rom with Philz. Perform a full wipe first form within the recovery.
http://forum.xda-developers.com/showthread.php?t=2283194
It's a 4.4.2.
Then flash a 4.2.2. modem and then try the things you want to do.

So I guessed that I should copy the .zip file of that WanamLite Rom onto the SD card, which I did.
I then did:
Recovery mode reboot, and booted into the Philz thing.
Wipe Data/Factory Reset.
Install Zip > Choose zip from /storage/sdcard1, and located the .zip file...
Installing...
Finding update package...
Installing update...
Welcom to WanamLite XXUGNH7 3.1
Formatting system...
System mounted!
data mounted!
Cleaning cache...
Installing system...
Symlinking...
Setting permissions...
set_metadata: some changes failed
E:Error in /storage/sdcard1/GT-I9505_WanamLite.XXUGNH7.V3.1.NO-WIPE.zip
(Status 7)
Installation aborted.
press any key to continue.​
So now I'm wondering how to get around a Status 7 error. Searching that forum thread about Wanamlite gives no help - at least not in a language a human can understand. Someone suggested:
"after spending several hours on this ... i made it
How to flash this ROM on old NON-Knox bootloader:
1. flash XXUEMJ5 modem via odin to prevent lags and call problems
2. flash a TWRP recovery to bypass the "status code 7"-error while flashing this ROM
3. flash this ROM
4. install your prefered recovery"​
I have absolutely no idea what any of that that means.
I have rebooted the phone, and it will only boot into the Philz thing - presumably because there is no operational firmware installed at all.

Partial success:
I followed the instructions given here: https://www.youtube.com/watch?v=np_nlFALMbQ
...to install firmware via PhilZ Touch, and I can successfully install Cyanogenmod (argh!) or WanamLite (yeah!). But I still cannot access the service menu in WanamLite. At least typing *#0011# does get some kind of menu up, but not the ServiceMode main menu.
And at least I now have a fully operational phone (with WanamLite), but still locked to O2.
Lennyz1988 suggested I "flash a 4.2.2. modem" - might doing that unlock the ServiceMode menu? Are those at all related? To flash the modem (presumably using Odin) which slot do I put it in? CSC?
I tried installing the O2 UK firmware using the exact same technique, using both the ROMs I downloaded, but neither would work. It failed at the very start, saying [bad]. I then reinstalled WanamLite successfully.

It wasn't just Lenny who mentioned flashing the 4.2.2 modem. I mentioned it as well. In fact, in the thread on the topic - which you really should be reading - the last few pages are peppered with posts from me telling people that you have to downgrade the modem (at minimum) before you can use either unlock method. For the record, I know downgrading works, because I had to do it myself after losing a SIM unlock that was done through the service menu. I ended up using RegionLock Away and couldn't be happier.
With that said, you cannot use a custom ROM of any kind to perform the unlock. I tried accessing the service menu on Imperium ROM, which is based on stock, and failed. You must be completely stock, which means you need to install a stock ROM to your device, using Odin. Download a new copy of the ROM, and if necessary use a totally different computer. Just one question however. If flashing the ROM through Odin doesn't work this time, will you then blame WanamLite for it?

Thank you for all your help with this, Strephon and Lennyz1988.
So, I tried flashing the modem (I put this file: I9505ZHUFNB3_MODEM.tar into Odin's CP slot - it seemed to work). I rebooted and tried to get to the service menu, but as Strephon predicted, there was no service menu.
So, again using Odin, I tried to put this firmware (I think it might be 4.2.2) on the phone:
I9505XXUEMK8_I9505O2UEMK1_I9505XXUEMK8_HOME.tar.md5
...and, predictably, it failed.
So then I tried doing them both at the same time, with the modem file in the CP and the firmware in the AP slot. But it failed again:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUEMK8_I9505O2UEMK1_I9505XXUEMK8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1005)..
<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> sbl2.mbn
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> aboot.mbn
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)​
I also tried to re-install the various other stock ROMs I'd downloaded (and re-downloaded, on a different computer), with no success.
So, I got back in touch with O2 - they'd previously said they wouldn't unlock the phone because they say the phone and number need to have been used together for 12 months. I only bought the phone about 6 weeks ago. But after much pleading (and £15) they've agreed to send me an unlock code! So when this arrives, I'll try it out (the phone is currently still running WanamLite) and see if it works. If not, to save my sanity, I'll just cut my losses and sell/give away the bloody phone as "locked (forever) to O2, with WanamLite or Cyanogenmod".
And no - I don't blame WanamLite (or Cyanogenmod now) for the stock ROM installations working - I can only assume that there's a problem with the ROMs. I can install WanamLite and Cyanogenmod fine, and it just so happens that they're not downloaded from some dark, dodgy server, unlike most of the supposedly stock ROMs. It's just really annoying that the phone's previous owner thought it was a good idea to install Cyanogenmod in the first place, without first unlocking the phone.

It's only annoying because the phone wasn't unlocked beforehand, meaning you have to put the stock ROM on the device in the first place to be able to unlock it using those methods. I can understand that. However, you still have the issue of why Odin keeps on failing when you try running it. That's one that perplexes me as I've had no issues with Odin whatsoever.

Well, my problems are over! O2 have already emailed me an unlocking code which WORKED! I now have an unlocked phone. I'm still interested in tweaking it, so may well install a more interesting firmware in future.
Thanks for your help and suggestions!

I9505 Softbricked, Cannot be flashed with odin :(

Hello,
I have problems with my s4 I9505 while I try to unbrick it
After a ota update from android 4.4.2 to 5.X (Orginal Firmware from Samsung) it cannot boot and enter Recovery and now I try to flash Firmware with odin but my phone turning screen off during odin says System.img.ext4 but the phone seens still working because it is showing in odin as connected but it doesn't continue flashing
I also see a new stuff in Download Mode Like Write Protection Enabled and eMMC Burst Mode Enabled

MichalPlays said:
Hello,
I have problems with my s4 I9505 while I try to unbrick it
After a ota update from android 4.4.2 to 5.X (Orginal Firmware from Samsung) it cannot boot and enter Recovery and now I try to flash Firmware with odin but my phone turning screen off during odin says System.img.ext4 but the phone seens still working because it is showing in odin as connected but it doesn't continue flashing
I also see a new stuff in Download Mode Like Write Protection Enabled and eMMC Burst Mode Enabled
Click to expand...
Click to collapse
Which firmware were you trying to flash through Odin? Is it KK or Lollipop?

Post the Odin log here.

Mandark52 said:
Which firmware were you trying to flash through Odin? Is it KK or Lollipop?
Click to expand...
Click to collapse
I tryed to flash Lollipop 5.0.1 (Orginal Firmware) and before brick I had Cyanogenmod Lollipop with Old Samsung Lollipop Modem and all worked fine until this **** ota update :/

Lennyz1988 said:
Post the Odin log here.
Click to expand...
Click to collapse
Ok, I will post it at 4:30p.m. (German Time Zone)

Lennyz1988 said:
Post the Odin log here.
Click to expand...
Click to collapse
ODIN LOG:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUHOJ2_I9505OXAHOJ2_I9505XXUHOJ2_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> aboot.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> tz.mbn
<ID:0/007> boot.img
<ID:0/007> recovery.img
<ID:0/007> system.img.ext4
(Device Freeze,after 2h battery empty)
<ID:0/007> Removed!!
<OSM> All threads completed. (succeed 0 / failed 1)

MichalPlays said:
ODIN LOG:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUHOJ2_I9505OXAHOJ2_I9505XXUHOJ2_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> aboot.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> tz.mbn
<ID:0/007> boot.img
<ID:0/007> recovery.img
<ID:0/007> system.img.ext4
(Device Freeze,after 2h battery empty)
<ID:0/007> Removed!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Use a different usb port/different usb cable. That will solve it.

Lennyz1988 said:
Use a different usb port/different usb cable. That will solve it.
Click to expand...
Click to collapse
Nope I tryed now this already :/
I tested also the battery with my other s4 and it worked fine.
There is a pict. that showing where I put the firmware file and what option I select
hmm, what is this CSC and Phone slots at odin?
sry 4 my bad english

Maybe try a newer version of Odin?

MichalPlays said:
Nope I tryed now this already :/
I tested also the battery with my other s4 and it worked fine.
There is a pict. that showing where I put the firmware file and what option I select
hmm, what is this CSC and Phone slots at odin?
sry 4 my bad english
Click to expand...
Click to collapse
Then try a different pc. the log doesn't show anything strange that would let me doubt my suggestion.

Lennyz1988 said:
Then try a different pc. the log doesn't show anything strange that would let me doubt my suggestion.
Click to expand...
Click to collapse
At all my pc's one with win7 and another with windows xp - sp3 it are the same, maybe I need to flash something other and them the firmware :/

@MichalPlays Try using Odin 307.

downgrade Samsung s4 [GT-I9505] from Lolipop 5.0.1 to kitkat 4.4.2
Please read the entire post and don’t skip any steps, note that we cannot be blamed in case something goes wrong and you brick the phone.
1)-Make sure that your phone version is GT-I9505 (if you don't know how to check ; remove your battery then you will find)
2)-Download[/B] " SAMSUNG USB Driver for Mobile Phones" and setup, if you dont have it already
-Download Odin3-v3.09
-Download "PDA" ; "[email protected]" [1.52 GB]
-Download "BL" ; "Bootloader_GNK2.tar" [2.12 MB]
-Download "CP"; "Modem_GNK2_FULL.tar" [61.46 MB]
3)- your phone must be Charged 70% or more, and Rooted, if you have Samsung Kies; reboot your pc then end Kies from CPU (Ctrl + Alt + Supp).
4)-extract Odin and Start a program as an administrator then put only the PDA file which you've already downloaded and extracted before "([email protected])"
-Disable « Auto Reboot » and « Re-Partition »
-Enable « F. Reset Time » only
-Reboot your phone on Download Mode ( Power off the Phone completely, Press and hold Volume Down, Home and Power buttons, all at the same time.
Release the buttons only when the ‘Warning!!’ message appears.
Next, press Volume Up button to confirm that you wish to enter Download Mode.
Your device will now show a green Android with the ‘Downloading… Do not turn off target’ text listed under it.).
-Connect your device with your PC and check "Added Message" and « ID:COM » in Odin
-Start
5)-Once you have "PASS" Plug out your Phone, and Reboot again in "Download Mode",
-Reset Odin
-Enable « Auto Reboot »and « F. Reset Time » only
-Put « Bootloader_GNK2.tar » on "BL"
-Put « Modem_GNK2_FULL.tar » on "CP
-Plug in your Phone and check "Added Message" and « ID:COM » if it doesn't work; restart Odin.
-Start to Downgrade
6)-Once the Downgrade done, plug out your phone and Hard Reset ;
(Power off your phone completely. Boot it in Recovery Mode. Select the ‘wipe data/ factory reset’ option. Confirm process by selecting the ‘Yes — delete all user data’ option. Press Power to confirm process. Reboot the phone when the Hard Reset/ Factory Reset is completed).
7)-Enjoy...

MichalPlays said:
At all my pc's one with win7 and another with windows xp - sp3 it are the same, maybe I need to flash something other and them the firmware :/
Click to expand...
Click to collapse
Ok then we can probably rule that out.
Are you using the original cable? Did you try different cables?

Lennyz1988 said:
Ok then we can probably rule that out.
Are you using the original cable? Did you try different cables?
Click to expand...
Click to collapse
I use always Original Cable and tested with cable from s4, s3, s3neo and htc one x plus and all doesn't work I tryed now the tutorial from this one guy this all was the same :/
btw. can I flash and enter a costum recovery without android on it ??

MichalPlays said:
I use always Original Cable and tested with cable from s4, s3, s3neo and htc one x plus and all doesn't work I tryed now the tutorial from this one guy this all was the same :/
btw. can I flash and enter a costum recovery without android on it ??
Click to expand...
Click to collapse
Yeah you can do that. Flash the latest TWRP. Uncheck auto-reboot before flashing with Odin.

Lennyz1988 said:
Yeah you can do that. Flash the latest TWRP. Uncheck auto-reboot before flashing with Odin.
Click to expand...
Click to collapse
oh, ok I will try this becasue I have this cyanogenmod .rar file on sd card and have also there an nandroid backup