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

[Solved] Need help with SHV-E300L - Cannot load most roms - stuck with bad rom

Hi,
So I'm a bit of a noob with regards to roms and kernels and all that stuff and I've found myself with a bit of a problem.
I ordered a Samsung Galaxy S4 (i9500) from Korea and received it a few days ago. The phone worked fine but was Android 4.2.2. There was no updates available OTA or in Kies so I decided to try flash my own rom.
I went about doing this and discovered that CWM recovery was already on the phone...it must have been added by the supplier, however the CWM version was in Korean.
I downloaded a rom, the first one I found, called Ozcran Rom. It's Android 4.4.2. On my phone it's very unstable, it keeps rebooting and it cannot recognize my sim card but it kind of works. I've tried to change the rom to many other ones but they all either fail to install or if I can install them they load but get no further than the boot animation.
Because the CWM was in Korean and because I'm a fool I never made a backup of the original. I've since been able to update CWM to an english version and figured out how to make a backup of the (barely working) Ozcran rom but I'm not having any luck installing a rom that actually works.
I've tried loading roms with both CWM and Odin but usually Odin fails. Odin was able to update CWM recovery for me but it seems to fail everytime I try to install a rom.
I've attached a screenshot of the About screen (when it's working with Ozcran Rom). When the phone is in download mode (in korean) it says Product Name: SHV-E300L, Current Binary: Custom, System status: Custom.
Can someone please help with this?

nicenormalfiend said:
Hi,
So I'm a bit of a noob with regards to roms and kernels and all that stuff and I've found myself with a bit of a problem.
I ordered a Samsung Galaxy S4 (i9500) from Korea and received it a few days ago. The phone worked fine but was Android 4.2.2. There was no updates available OTA or in Kies so I decided to try flash my own rom.
I went about doing this and discovered that CWM recovery was already on the phone...it must have been added by the supplier, however the CWM version was in Korean.
I downloaded a rom, the first one I found, called Ozcran Rom. It's Android 4.4.2. On my phone it's very unstable, it keeps rebooting and it cannot recognize my sim card but it kind of works. I've tried to change the rom to many other ones but they all either fail to install or if I can install them they load but get no further than the boot animation.
Because the CWM was in Korean and because I'm a fool I never made a backup of the original. I've since been able to update CWM to an english version and figured out how to make a backup of the (barely working) Ozcran rom but I'm not having any luck installing a rom that actually works.
I've tried loading roms with both CWM and Odin but usually Odin fails. Odin was able to update CWM recovery for me but it seems to fail everytime I try to install a rom.
I've attached a screenshot of the About screen (when it's working with Ozcran Rom). When the phone is in download mode (in korean) it says Product Name: SHV-E300L, Current Binary: Custom, System status: Custom.
Can someone please help with this?
Click to expand...
Click to collapse
can you tell us what odin says when it fails? give us a picture please, most odin fails are because of wrong firmware for wrong devices. also did you get your stock rom from here http://www.sammobile.com/firmwares/2/ ? most recommended place.

Hi.
One of the stock roms I tried was from sammobile yes.
I've attached an image of Odin when it fails and I've pasted the content of the message box here:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9500XXUGNH4_I9500OJKGNI1_I9500JKUGNH1_HOME.tar.md5 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> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

nicenormalfiend said:
Hi.
One of the stock roms I tried was from sammobile yes.
I've attached an image of Odin when it fails and I've pasted the content of the message box here:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9500XXUGNH4_I9500OJKGNI1_I9500JKUGNH1_HOME.tar.md5 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> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
you say its a i9500 but you said its a SHV-E300L in download mode, try flashing one of those stock roms from sammobile might have to deal with Korean language for awhile unless Samsung Korean phones come with english. You are sure its a i9500? take out the battery and tell me the model number where the battery is supposed to go.

Trozzul said:
you say its a i9500 but you said its a SHV-E300L in download mode, try flashing one of those stock roms from sammobile might have to deal with Korean language for awhile unless Samsung Korean phones come with english. You are sure its a i9500? take out the battery and tell me the model number where the battery is supposed to go.
Click to expand...
Click to collapse
I thought perhaps SHV-E300L was the model number of the i9500 in Korea.
Under the batter the model number says GT-i9500. Is the SHV-E300L supposed to be different from the i9500?
I'll try downloading firmware from sammobile for the SHV-E300L...

I'm not sure about that model number question. All I know is i9500 sounds international so maybe that says its international but runs on shv e300l firmware.

Trozzul said:
I'm not sure about that model number question. All I know is i9500 sounds international so maybe that says its international but runs on shv e300l firmware.
Click to expand...
Click to collapse
Ok, thanks for the lead. I'll give the SHV-E300L firmware a go

Trozzul said:
I'm not sure about that model number question. All I know is i9500 sounds international so maybe that says its international but runs on shv e300l firmware.
Click to expand...
Click to collapse
Amazing, the firmware for SHV-E300L works perfectly. Thank you so much!

nicenormalfiend said:
Amazing, the firmware for SHV-E300L works perfectly. Thank you so much!
Click to expand...
Click to collapse
Enjoy i hope you are able to get non-korean languages if you need it. if you have any other questions please be sure to ask!

я
мне тоже дайти
nicenormalfiend said:
ok, thanks for the lead. I'll give the shv-e300l firmware a go
Click to expand...
Click to collapse

Need help flashing stock rom, already attempted and failed on GS5

Hello everyone,
I'm trying to flash a stock rom on a Verizon GS5. I say trying because so far it hasn't been working, unless I'm doing something wrong, which I think I am. When I got the phone, it had a Sprint rom flashed to the GS5. The original Verizon IMEI under the battery is clean and verified good with Verizon. There is nothing physically or cosmetically wrong with the phone, it powers on sometimes and randomly restarts. When it does turn on, the Sprint Spark logo comes up, the phone boots up normally and then randomly shuts off, taking a long time to be able to power back on. The only way that it says on is by putting it on Download Mode.
When in download mode, it shows as a G900P,
As far as my understanding goes, shouldn't it be a G900V?
I attempted to flash a stock Verizon rom I downloaded and tried to flash it with Odin 3.04 but it fails each and every time. I have installed the Samsung drivers that I got from the website, I restarted the computer, I restarted the phone but Odin give me a fail error.
Then I tried a newer version of Odin 4.43 but I'm not sure I'm using that one correctly but it's not working for me either.
I left the phone in Download Mode and it has been on for about 30 mins (the longest so far without it restarting on me).
Is there something that I'm missing here? Something else I could try to fix this?
Any ideas? Suggestions?
Any help would be greatly appreciated!!

..

-> It's a Verizon Galaxy S5 Phone I got from eBay
-> It's flashed with the Sprint rom version of the GS5
-> The phone restarts on and off, randomly, unless it is in Download Mode
-> I want to flash it back to the original Verizon GS5 rom.
-> I attempted to flash the phone with Odin 3.09 and rom SM-G900V_VZW_1_20140331185350
-> I get an error message when using Odin 3.09, it FAILS
-> The progress bar in the GS5 phone advances a small amount but that's it.
-> I attempted to use Odin 4.43 with the same rom file but that also fails and I get an error message.
-> I researched on Google before signing up and asking for help.
-> I have read many Threads and Posts on several Forums, and I have also tried many tutorials without any luck.
-> I researched how to use Odin, there is lot's of pictures, easy explanations but that's not it.
-> I found a GS5 stock rom, file name mentioned above.
-> Samsung drivers are installed, phone is recognized by Odin.
1.) Am I using the correct rom?
2.) Which version of Odin should I use?

..

SewerDweller said:
Hello everyone,
Any ideas? Suggestions?
Any help would be greatly appreciated!!
Click to expand...
Click to collapse
Download this version of Odin and extract the folder in the zip.
Make sure you have downloaded the correct firmware, extract the MD5 / tar file from inside the firmware.zip file you downloaded and put it in the Odin 3.07 folder
Start Odin.exe, put your phone in download mode and connect to your PC, if you have Kies installed make sure it is not running, Odin and Kies don't mix.
Once you have the Blue ID.COM indicated, click on PDA, find the MD5 / .tar file wait for teh file check Odin runs then click Start, wait for Odin to finish and your phone reboots.
Guide for Odin use here it is from the S3 but the use of Odin is the same for the S5

It took me a while to get it to turn on but here's what I got from trying ag4751's suggestions.
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900VVRU1ANI2_G900VVZW1ANI2_G900VVRU1ANI2_HOME.tar.md5 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> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
It's the same thing that I was getting before, I'm sorry if I did not explain myself in detail at first.
I have used 2 versions of Odin 3.09 (which I used on my own and got the above message).
3.07 as suggested by ag4751.
I have used 2 different roms and both fail.
->G900V_VZW_1_20140331185350
->G900VVRU1ANI2-20140919141518
@fffft
To answer your question as to what tutorial I followed, I followed ag4751's tutorial/explanation on his reply. It's basic, just like all the other tutorials I googled.
1.) Put the phone in download mode
2.) Open Odin
3.) Select PDA
4.) Wait for the file check
5.) Click start
and then it fails.
That's what @ag4751 suggested, that's what I tried, that's what I tried before, that's what I'm trying now and all that is failing for some reason.

..

..

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

Help me root my phone, please.

Hello everyone.
I would really like to be able to remove remove unnecessary, bloatware and energy consuming apps for example google +, hangouts, dropbox,...and maybe even the play store.
I want to take full control of my phone so every piece of information is welcome.
I have a Samsung Galaxy S3 Neo phone with the following specifications:
Model number:
GT-I9301I
Android version:
4.4.2
Android security patch level:
2006-06-01
Baseband version:
I9301IXXUAPG1
Kernel version
3.4.0-6004186
[email protected] #1
Wed Jan 4 19:28:00 KST 2017
Build number:
KOT49H.I9301IXXSAQA1
SE for Android status
Enforcing
SEPF_GT-I9301I_4.4.2_0055
Wed Jun 29 20:36:25 2016
Security software version:
ASKS v1.2_161011

https://forum.xda-developers.com/ga...overy-t-r-p-samsung-galaxy-s3-neo-gt-t2906840
Hopefully its help you !! Cheer bro

I am not sure it's going to work and I really wouldn't like to make my phone useless.
Thanks for your reply though.
mitu725 said:
https://forum.xda-developers.com/ga...overy-t-r-p-samsung-galaxy-s3-neo-gt-t2906840
Hopefully its help you !! Cheer bro
Click to expand...
Click to collapse

Update
P.S. And I don't know if the build number is the same.
I got the impression that it matters and if you don't get the right tools for the exact phone specifications you render you phone useless.
meekss said:
I am not sure it's going to work and I really wouldn't like to make my phone useless.
Thanks for your reply though.
Click to expand...
Click to collapse

Need help with this as well
Basically the same situation as OP, same phone, same build number.
Samsung Galaxy S3 Neo
Model: GT-I9301I
Build: KOT49H.I9301IXXSAQA1
Prior to my rooting attempts I enabled debug mode, installed the USB drivers and made a full backup via MyPhoneExplorer.
I tried rooting it with CF-Auto-Root. Went to the site, selected the correct model and build (it was listed twice, tried both) and downloaded the Auto-Root package as well as the provided original boot and recovery images. When I try to flash the CFAR image.tar.md5 file, Odin initiates the transfer, however it fails to complete the task.
Here is the log:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1203)..
<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> recovery.img
<ID:0/003> cache.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The progress bar stops at around a quarter completed and my phone says "unsupported dev_type" in red letters, rebooting it results in a message that a firmware upgrade encountered a issue and it won't boot.
Thankfully it isn't bricked (yet) as I am able to use Odin to flash the original boot image successfully after which the phone boots normally again.
I tried several versions of Odin all with the same result, I even tried running it in Windows XP compatibility mode which interestingly doesn't make it fail but crash the application at the point where it normally would.
However, that's not helping me getting it rooted so any help would be much appreciated.

Here are the steps:
- install twrp via flashing it with Odin.
- after that make a full backup with twrp just in case
- flash supersu which will give you root (sometimes there is an option in twrp to flash supersu)

Best way to root s3 neo is SuperSU

I had the same version you have, so the solution is:
You'r version cannot be rooted. You have to change it.
Flash this version with Odin you will find on google or here : I9301IXXUANC6 : https://samfrew.com/download/Galaxy__S3__Neo+__/128t/ATO/I9301IXXUANC6/I9301IOXAUANC6/
Then flash recovery to TRWP or something else, then install SuperSu with TRWP recovery or others, and finally flash ROM if you want.
Have fun, tell me if it worked.