Database Users

[Q] Need help unbricking my phone.

I have searched and used as much google fu as I know how, so if I've missed the obvious I'm sorry.
Phone: Att Galaxy S4 SGH-I337
Running: I think stock 4.2.2 that was rooted.
Problem: currently will only get to the att logo then moves no further. Odin always fails to get me back to stock.
Cause of problem: Mostly likely me. I was attempting to unroot my phone using ODIN following a tutorial on galaxys4root.com.
Things I have tried: 6 different USB cords, 4 PCs 1 mac, Odin 3.07 and Odin 1.85, Several different sources for stock roms.
Notes: When I try to use the power button volume button method of booting to recovery it just goes to the odin download screen. This has been happening for a day or so that I've noticed.
Output from odin: <OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)​
Output from phone: Odin Mode
Produc Name: SGH-I337
Current Binary: Samsung Offical
System Status: Custom
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
START [224, 1440]
SW REV. CHECK FAIL : fused : 2, Binary : 1​
the output is pretty much the same regardless of odin computer or cable.
Any help would be greatly appreciated.
Thanks

#1. did you have usb debugging enabled before booting into download mode?
#2. do you know what firmware version was on the device when you got it (MDB, MDL, MF3)?
#3. booting into recovery is volume up + home + power. when your device vibrates, release just the power button. not sure if this is what you've been doing or if this will even benefit you right now.

Can you get into recovery? Were you stock beforehand or did you have a custom rom? If you can get into recovery do a factory reset. I'm guessing you got the mf3 update and that's why odin is not working.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

xBeerdroiDx
1. It was enabled the last time I was able to boot up.
2. Sadly no.
3. Tried a million on a thousand times. Every way which way i could think. The blue text pops up for a fraction of a second then it dumps off into odin mode.
jd1639
Can't get to recovery. Stock rooted. wasn't even aware i got the update. noobed it up.

Idk what else you can do. Try to see if kies will do an emergency restore. After that I'm out of ideas.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

Try an older version of odin like 1.85 get into download mode then try to flash a custom recovery?
Sent from my SAMSUNG-SGH-I337 using xda premium

Are you releasing all the buttons as soon as you see the blue text come up--like immediately
@BD could OP have lost recovery and maybe dd the twrp recovery image. assuming adb recognizes phone

rugmankc said:
Are you releasing all the buttons as soon as you see the blue text come up--like immediately
@BD could OP have lost recovery and maybe dd the twrp recovery image. assuming adb recognizes phone
Click to expand...
Click to collapse
Immediately, promise, the text flash up for less than time that it would take to read it. just long enough for you to see something blue. I haven't been able to get it into recovery mode. Up until recently it wasn't a problem.

do you have adb access to phone to see if phone is recognized thru windows command terminal

Rabidbot, you got some serious fire power here helping you. I hope you're successful. Good luck to you.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

rugmankc said:
do you have adb access to phone to see if phone is recognized thru windows command terminal
Click to expand...
Click to collapse
Working on trying to figure that out now.
UPDATE It isn't coming up in the list of attached devices.

ok, i don't know if phone can be recognized in your situation. It has to have had usb debugging enabled.

rugmankc said:
Are you releasing all the buttons as soon as you see the blue text come up--like immediately
@BD could OP have lost recovery and maybe dd the twrp recovery image. assuming adb recognizes phone
Click to expand...
Click to collapse
I would be curious to know if adb in fact does recognize the phone. If so, the OP might be more successful flashing stock recovery and seeing if a factory reset clears it up. Sound like that partition is borked?

xBeerdroiDx said:
I would be curious to know if adb in fact does recognize the phone. If so, the OP might be more successful flashing stock recovery and seeing if a factory reset clears it up. Sound like that partition is borked?
Click to expand...
Click to collapse
Agreed--

xBeerdroiDx said:
I would be curious to know if adb in fact does recognize the phone. If so, the OP might be more successful flashing stock recovery and seeing if a factory reset clears it up. Sound like that partition is borked?
Click to expand...
Click to collapse
Doesn't seem to be recognized.

rabidbot said:
SW REV. CHECK FAIL : fused : 2, Binary : 1
Click to expand...
Click to collapse
I believe you were on MF3 when it died.
Fused:2 means the qfuse was blown by the mf3 update
Binary:1 means the software you're attempting to flash matches a qfuse level 1 (mdl and lower)
I think it's either a samsung warranty replacement or wait for mf3 on kies.
Sent from my SAMSUNG-SGH-I337 using xda premium

Hi,
I would say google these terms to get a better idea of what you need to do to fix your phone:
START [224, 1440]
SW REV. CHECK FAIL : fused : 2, Binary : 1
I am pretty sure it sounds like you somehow flashed the new MF3 update and now it is not possible to Odin an AMDL image onto phone now due to blown Qfuse in the MF3 update. Here is example of what the above terms mean:
http://forum.xda-developers.com/showpost.php?p=43484436&postcount=370
Possible fix? (Not quite the same situation as you are in, but if you try to use Kies to restore your phone, I bet you will be in this same position maybe?)
http://forum.xda-developers.com/showthread.php?t=2360859
Sorry I couldn't provide a definite, quick fix, but I hope this helps point you in the right direction at least!

rabidbot said:
Working on trying to figure that out now.
UPDATE It isn't coming up in the list of attached devices.
Click to expand...
Click to collapse
ok based on other's comments, you may not have a quick solution. i missed the part about "fuse" -- sorry
did you have adb working before as in are your drivers installed. if no drivers, dl kies to get drivers. then uninstall it and try again
sounds like you are familiar with running adb commands?

Klown80 said:
Hi,
I would say google these terms to get a better idea of what you need to do to fix your phone:
START [224, 1440]
SW REV. CHECK FAIL : fused : 2, Binary : 1
I am pretty sure it sounds like you somehow flashed the new MF3 update and now it is not possible to Odin an AMDL image onto phone now due to blown Qfuse in the MF3 update. Here is example of what the above terms mean:
http://forum.xda-developers.com/showpost.php?p=43484436&postcount=370
Possible fix? (Not quite the same situation as you are in, but if you try to use Kies to restore your phone, I bet you will be in this same position maybe?)
http://forum.xda-developers.com/showthread.php?t=2360859
Sorry I couldn't provide a definite, quick fix, but I hope this helps point you in the right direction at least!
Click to expand...
Click to collapse
This is the output from odin. It was successful but my phone still doesn't boot past the att logo.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MF3_BTL_FIX.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<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> rpm.mbn
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> tz.mbn
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!​

rugmankc said:
ok based on other's comments, you may not have a quick solution. i missed the part about "fuse" -- sorry
did you have adb working before as in are your drivers installed. if no drivers, dl kies to get drivers. then uninstall it and try again
sounds like you are familiar with running adb commands?
Click to expand...
Click to collapse
I got the Drives are installed and have worked before. still nothing in the device list.

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

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

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

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

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

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

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

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

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

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

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

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

did anyone tried this ??

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

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

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

[Q] Soft brick at&t note 3?

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

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

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

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

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

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

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

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

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

Need pit file?

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

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

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

firstsx said:
how can there be a newer version, it was never updated to kitkat?
sammobile only lists that version and i'm quite certain it was 4.3
so if i don't flash the bootloader, what do i flash?
can i not use these files?
AP_N900AUCUBMJ5.zip
BL_N900AUCUBMJ5.zip
CP_N900AUCUBMJ5.zip
HLTE_USA_ATT_32G.pit
Click to expand...
Click to collapse
Hi mate,
if you are stuck, maybe you can try this.
http://forum.xda-developers.com/showthread.php?t=2701062
it's a way to unbrick your software.
and update to kitkat.
maybe your problem is the firmware in the sammobile were before the firmware you have install on your device via OTA update.
Yours firmware came throw out via OTA update and with some reason you can't see any latest firmware USA N900A in sammobile.
try the method in the link and reply if you have been successful.
cumps

Markudsc said:
Hi mate,
if you are stuck, maybe you can try this.
http://forum.xda-developers.com/showthread.php?t=2701062
it's a way to unbrick your software.
and update to kitkat.
maybe your problem is the firmware in the sammobile were before the firmware you have install on your device via OTA update.
Yours firmware came throw out via OTA update and with some reason you can't see any latest firmware USA N900A in sammobile.
try the method in the link and reply if you have been successful.
cumps
Click to expand...
Click to collapse
can i use this method
http://forum.xda-developers.com/showthread.php?t=2559715
it seems pretty much the same, except yours includes updating to kitkat.
if i do kitkat, can i still keep root?
will this trip knox?

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

[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

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.