Database Users

FAIL Flashing stock 4.2.2

Ive been desperately trying to return to stock to unroot my phone for 2 days to no avail.
Holding the power button takes me to the Samsung bootloop.
I used Odin 1.85 to flash a HOME.tar.md5 file getting this message:
<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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
In download mode it says the following:
ODIN MODE
Product Name:GT-i19505
Current binary: Custom
System status: Custom
Knox Kernel lock: 0x0
Knox warranty void: 0x1
CSB-CONFIG-LSB: 0x30 (have no idea what this is)
Write protection: Enable
eMMC Burst mode: enabled
START [224, 1440]
Any ideas?

poninaine said:
Ive been desperately trying to return to stock to unroot my phone for 2 days to no avail.
Holding the power button takes me to the Samsung bootloop.
I used Odin 1.85 to flash a HOME.tar.md5 file getting this message:
<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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
In download mode it says the following:
ODIN MODE
Product Name:GT-i19505
Current binary: Custom
System status: Custom
Knox Kernel lock: 0x0
Knox warranty void: 0x1
CSB-CONFIG-LSB: 0x30 (have no idea what this is)
Write protection: Enable
eMMC Burst mode: enabled
START [224, 1440]
Any ideas?
Click to expand...
Click to collapse
are you putting it in download mode
http://galaxys4root.com/galaxy-s4-tutorials/how-to-unroot-galaxy-s4-and-remove-root-completely/

jaythenut said:
are you putting it in download mode
http://galaxys4root.com/galaxy-s4-tutorials/how-to-unroot-galaxy-s4-and-remove-root-completely/
Click to expand...
Click to collapse
Yes, I specifically wrote down what it said on the top left side in download mode,too.

poninaine said:
Yes, I specifically wrote down what it said on the top left side in download mode,too.
Click to expand...
Click to collapse
Did you:
Use the cable that came with your device.
Use the usb ports in the back of your computer. Don't use a hub.
Try on a different computer.
Get firmware from sammobile.com
These are all things that you should check. Also, I've had Odin fail a number of times and the for whatever reason decide to work. It can be finicky.

jd1639 said:
Did you:
Use the cable that came with your device.
Use the usb ports in the back of your computer. Don't use a hub.
Try on a different computer.
Get firmware from sammobile.com
These are all things that you should check. Also, I've had Odin fail a number of times and the for whatever reason decide to work. It can be finicky.
Click to expand...
Click to collapse
I also found certain versions of Odin didn't work with some ROMS. When I tried using a 3.1x version of Odin to root my I9505G, it didn't setup properly, but using the 3.07 version did.

jd1639 said:
Did you:
Use the cable that came with your device.
Use the usb ports in the back of your computer. Don't use a hub.
Try on a different computer.
Get firmware from sammobile.com
These are all things that you should check. Also, I've had Odin fail a number of times and the for whatever reason decide to work. It can be finicky.
Click to expand...
Click to collapse
Yes I have tried all of those things. I also downloaded all the Odin versions and tried them. Unfortunately all of them failed. Is there any idea of what the failure in the original post means?

poninaine said:
Yes I have tried all of those things. I also downloaded all the Odin versions and tried them. Unfortunately all of them failed. Is there any idea of what the failure in the original post means?
Click to expand...
Click to collapse
In the last fail the box on the bottom left side said "Leave CS" what does this mean?

poninaine said:
Yes I have tried all of those things. I also downloaded all the Odin versions and tried them. Unfortunately all of them failed. Is there any idea of what the failure in the original post means?
Click to expand...
Click to collapse
Do you know what firmware you were on? And what country and carrier are you.

jd1639 said:
Do you know what firmware you were on? And what country and carrier are you.
Click to expand...
Click to collapse
You mean now or before the root? And my country is Estonia which has no stock .tar file anywhere on the internet. I read somewhere that you can just use a random countrys one and change the csc later so I decided to do that.

poninaine said:
You mean now or before the root? And my country is Estonia which has no stock .tar file anywhere on the internet. I read somewhere that you can just use a random countrys one and change the csc later so I decided to do that.
Click to expand...
Click to collapse
Yes, before root.

I even tried re-partition. Still failed instantly.

jd1639 said:
Yes, before root.
Click to expand...
Click to collapse
Before root I was on the stock Android 4.2.2. The first time I flashed anything it was the new leaked 4.3 which worked just fine.
Then I flashed CM 10.1 and it worked but the problems started when I wanted to get back to stock.

poninaine said:
I even tried re-partition. Still failed instantly.
Click to expand...
Click to collapse
I'm pretty sure it's the firmware version you're flashing that's the problem. If you know what it was before you rooted I'd look for the same version.

I have a similar problem
Hello there,
I have a similar problem but in odin it is a success but then i get stuck at boot.
To flash the file as a success, remove your device then flash again. By looking at your info, it says you have samsung knox which is a bummer (i'm in the same boat), you'll have to flash the same stock firmware as you did last time
Let me know how you get on mate

LimitedStreak said:
Hello there,
I have a similar problem but in odin it is a success but then i get stuck at boot.
To flash the file as a success, remove your device then flash again. By looking at your info, it says you have samsung knox which is a bummer (i'm in the same boat), you'll have to flash the same stock firmware as you did last time
Let me know how you get on mate
Click to expand...
Click to collapse
If Odin is successful but you get stuck at boot, do a factory reset in the stock recovery and it'll get you past the boot loop.

Would that delete my internal sd card folders etc?
---------- Post added at 10:12 PM ---------- Previous post was at 10:04 PM ----------
jd1639 said:
If Odin is successful but you get stuck at boot, do a factory reset in the stock recovery and it'll get you past the boot loop.
Click to expand...
Click to collapse
Would that delete my internal sd cards folders, prictures etc?
What if I flash another recovery then try wiping?

LimitedStreak said:
Hello there,
I have a similar problem but in odin it is a success but then i get stuck at boot.
To flash the file as a success, remove your device then flash again. By looking at your info, it says you have samsung knox which is a bummer (i'm in the same boat), you'll have to flash the same stock firmware as you did last time
Let me know how you get on mate
Click to expand...
Click to collapse
What do you mean I have Samsung Knox? I dont know how to find the same stock firmware as I dont know what I exactly need. As in if I need the exact same as it was when I bought it then I probably wont have no luck because my countrys csc firmware is nowhere for download.

I just realised - Im probably a huge idiot - I just checked the store site from where I bought my phone and it says the OS version is 4.2 not 4.2.2. Im going to try that but does every site only has 4.2.2!

[Q] SM-N9005 bricked, help needed!

I managed not only brick one, but two SM-N9005, trying to do the Root de la Vega (yes, I used the right files).
After entering download mode, Odin failed after a short time (blue status bar was 2mm long).
Now the phone only says: Firmware upgrade encountered an issues. Please select recovery mode in Kies & try again.
But:
- Kies recovery fails
- I can't go into recovery mode, only download mode.
- Can't install stock ROM with Odin, fails as well.
- Can't CF-Auto-Root, Odin fails.
Note: Reactivation lock is OFF.
Any ideas?

k3000 said:
I managed not only brick one, but two SM-N9005, trying to do the Root de la Vega (yes, I used the right files).
After entering download mode, Odin failed after a short time (blue status bar was 2mm long).
Now the phone only says: Firmware upgrade encountered an issues. Please select recovery mode in Kies & try again.
But:
- Kies recovery fails
- I can't go into recovery mode, only download mode.
- Can't install stock ROM with Odin, fails as well.
- Can't CF-Auto-Root, Odin fails.
Note: Reactivation lock is OFF.
Any ideas?
Click to expand...
Click to collapse
try a different odin

jaythenut said:
try a different odin
Click to expand...
Click to collapse
Tried that, did not help. Thanks for the input. Used v1.85 mainly, though.

k3000 said:
Tried that, did not help. Thanks for the input. Used v1.85 mainly, though.
Click to expand...
Click to collapse
Try 3. what ever the number is i think it's better

jaythenut said:
Try 3. what ever the number is i think it's better
Click to expand...
Click to collapse
Odin3v185
That's the one I used.

k3000 said:
Odin3v185
That's the one I used.
Click to expand...
Click to collapse
No not that one v 3.07

jaythenut said:
No not that one v 3.07
Click to expand...
Click to collapse
Just tried it again with ODIN v3.07 and got the same error message in ODIN
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

This is getting really frustrating...
I tried different ODINs running on XP, Win 7 and Win 8.
I ran ODIN as Admin or Standard user and I used different USB ports and cables.
Nothing seems to help.
For example, trying to flash stock ROM gives me this error in ODIN:
<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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

What's the error on the phone?
Example:
ODIN MODE
PRODUCTION NAME: SM-N9005
CURRENT BINARY: Samsung
SYSTEM STATUS: Official
REACTIVIATION LOCK: OFF
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
QUALCOM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1 T1 R1 A2 P1
WRITE PROTECTION: ENABLE.....

toker_X1 said:
What's the error on the phone?
Example:
ODIN MODE
PRODUCTION NAME: SM-N9005
CURRENT BINARY: Samsung
SYSTEM STATUS: Official
REACTIVIATION LOCK: OFF
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
QUALCOM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1 T1 R1 A2 P1
WRITE PROTECTION: ENABLE.....
Click to expand...
Click to collapse
There is no error message on the display... that's exactly the text I see as well.
The only things that happens on the display the moment ODIN displays "FAIL", the blue progress bar freezes... I'd day it doesn't get further than 1-2%.

Normally there should be a red line with the error code/message.
All I can suggest is you try flashing stock rom using the several files (Kernel, PDA, CSC) method if you already havent done so already.

toker_X1 said:
Normally there should be a red line with the error code/message.
All I can suggest is you try flashing stock rom using the several files (Kernel, PDA, CSC) method if you already havent done so already.
Click to expand...
Click to collapse
Would you kindly be able to provide a link to the procedure you are referring to?
I have attached a picture of my bricked screen... I either see this one or the download screen.

k3000 said:
Would you kindly be able to provide a link to the procedure you are referring to?
I have attached a picture of my bricked screen... I either see this one or the download screen.
Click to expand...
Click to collapse
Why didn't you use ODIN 3.09 like guide here on XDA says?
Have you tried with that version?

k3000 said:
Would you kindly be able to provide a link to the procedure you are referring to?
I have attached a picture of my bricked screen... I either see this one or the download screen.
Click to expand...
Click to collapse
Thats not 'Download Mode', thats phone firmware recovery mode.
Can you get to 'Download Mode'? - ie. Green Andriod Robot screen? (Pull out the battery, Vol Down, Home and Power)
When I soft brinked my phone, I eventually got it working by doing this..
1) Boot into 'Download Mode'
2) Using Odin 3.09 flash Stock Kernel (my kernel file was 'KERNEL-BTU-N9005XXUBMJ3-1381515654.tar'), this enabled boot to 'Recovery Mode' where is was not working before.
3) Using Odin 3.09 flash CSC (my CSC file was 'N9005OXABMJ3_CSC.tar.md5')
4) Boot into 'Recovery Mode' and wipe all (System, Data, Cache etc..)
5) Using Odin 3.09 flash Stock Firmware (my file was 'N9005XXUBMJ3_N9005OXABMJ1_N9005XXUBMJ2_HOME.tar.md5') - this will fail.
6) Using Kies 3 Beta - Perform a 'Emergency Firmware Recovery', recovery code is required - this got be back to normal
Hope this helps.

toker_X1 said:
Thats not 'Download Mode', thats phone firmware recovery mode.
Can you get to 'Download Mode'? - ie. Green Andriod Robot screen? (Pull out the battery, Vol Down, Home and Power)
When I soft brinked my phone, I eventually got it working by doing this..
1) Boot into 'Download Mode'
2) Using Odin 3.09 flash Stock Kernel (my kernel file was 'KERNEL-BTU-N9005XXUBMJ3-1381515654.tar'), this enabled boot to 'Recovery Mode' where is was not working before.
3) Using Odin 3.09 flash CSC (my CSC file was 'N9005OXABMJ3_CSC.tar.md5')
4) Boot into 'Recovery Mode' and wipe all (System, Data, Cache etc..)
5) Using Odin 3.09 flash Stock Firmware (my file was 'N9005XXUBMJ3_N9005OXABMJ1_N9005XXUBMJ2_HOME.tar.md5') - this will fail.
6) Using Kies 3 Beta - Perform a 'Emergency Firmware Recovery', recovery code is required - this got be back to normal
Hope this helps.
Click to expand...
Click to collapse
Just tried... I get stuck at 2) again trying to flash the Kernel.

k3000 said:
Just tried... I get stuck at 2) again trying to flash the Kernel.
Click to expand...
Click to collapse
try stock firmware from www.samfirmwares.com with odin v3.09

k3000 said:
Just tried... I get stuck at 2) again trying to flash the Kernel.
Click to expand...
Click to collapse
Uhm, probably a dumb question, but did you use the CSC file as well? Didn't see that in the SS.

nabilsweet007 said:
try stock firmware from www.samfirmwares.com with odin v3.09
Click to expand...
Click to collapse
Unfortunately, no progress. Fails at the very same stage all where all my other efforts have failed, too.
Note: I am using the standard USB 3.0 cable which came with the Note 3. I have tried about 5 different USB 2.0 I have at home. Windows would not recognize a USB device being connected, but the Note 3 itself starts to charge the battery.

What was the csc of the phone before you tried the first flash?
Sent from my SM-N9005

SUCCESS!!
I went to the basement and dug out an old Win XP laptop, approx. 2002 vintage, which has not been used since probably 2005.
Plugged in my Note 3 with the USB 3.0 cable (of course at USB 1.0 speeds), re-ran Root de la Vega from scratch and voilà, it worked!
LESSON LEARNED: Do not use VMWARE FUSION/MAC to root. IT WILL BRICK YOUR PHONE.

[HELP] i9505 Stuck in Boot (serious problem)

Hi all,
Two weeks ago I dropped my Samsung GT - I9505 S4 ( T -Mobile NL ). The screen was damaged (black), but the phone still worked. I could hear the startup sound and also incoming mail and whatsapp messages. So the phone was alive, but the screen was dead.
So i ordered a new screen and replaced it myself. This was no problem at all. The screen replacement was a succes. The S4 logo came up. I was happy the screen replacement worked. But now i had this problem, the phone was stuck in the bootlogo!
I tried to enter the recovery mode, it didn't work (Volume Up + Home + Power).
Then i tried to enter the download mode (Volume Down + Home + Power). This worked.
Then i tried to install the official firmware. I chose to install the newest firmware (I9505XXUEMKF 4.3). I downloaded it at sammobile model=GT-I9505&pcode=TNL#firmware
I used Odin 1.85, 3.07 and 3.09 on Windows 7 and Windows 8 with all the Samsung USB drivers installed. And also i used the Pit file CSB signed Fusion3 EUR 0325 V2.
The phone is still stuck in the boot screen. After a clean install and pass from odin, the s4 says: "Recovery booting". Recovery mode still not accessible.
When i flash my S4 with the latest CW-Autoroot or Philz Touch, the Phone says:
Recovery booting ....
Recovery is not enforcing seandroid
Warrenty Bit Set : Recovery
Download screen info:
ODIN MODE
Product Name: GT-I9505
Current Binary: Samsung Official
System Status: Custom
Knox Kernel Lock: 0x0
Knox Warranty Void: 0x1
CSB-CONFIG-LSB: 0x30
Write Protection: Enable
eMMC BURST MODE enabled
Any help would be appreciated! I am willing to pay for the right solution.

1. Download a suitable kernel in tar.md5 format -> HERE
2. Download ODIN 3.09
3. Once installed, boot your phone in Download mode by pressing Vol Down+Home+Power together until you see a warning dialog. Press Vol UP to get into download mode.
4. Make sure ODIN is running, and NO KIES processes are running.
5. Connect your phone with USB cable to your PC.
6. In ODIN, you should see a COM port with yellow background.
7. Click the PDA/AP button ONLY.
8. Select the kernel file you downloaded.
9. Press Start and nothing else.
10. If everything went as expected, your phone should reboot after a while with a working Recovery.
11. Try now to install the firmware MKF u downloaded before (without selecting .pit file)
12. Tell me how it works :highfive:

I just followed your steps, one by one.
I have all the versions of Odin, so i used the Odin 3.09 this time, like you said.
I putt my phone in download mode and installed the kernel i downloaded from your link. Odin status: pass.
Status Phone:
Start [224,1440]
BAR [240, 1440]
END [840, 1440]
Odin Status:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.07.9-jfltetmo.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> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
S4 is still stuck in boot logo.
When i try to get in to recovery mode (By holding Volume up, Home + Power), this message comes up:
Recovery booting ....
Recovery is not enforcing seandroid
Warrenty Bit Set : Recovery
Everytime i get stuck with the Boot logo, Recovery booting.. or Recovery is not enforcing seandroid.

<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUEMKF_I9505TNLEMJ6_I9505XXUEMKF_HOME.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> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004> tz.mbn
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> NON-HLOS.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
Stuck in:
Recovery Booting....

you need a full wipe before flashing stock or custom rom, if you do not do as you get into the boot loop

Nininho1995 said:
you need a full wipe before flashing stock or custom rom, if you do not do as you get into the boot loop
Click to expand...
Click to collapse
How can i do that? How can i do a full wipe? Remember i cannot get into recovery mode at all.
Please help?

do you have a stock rom?
do you have a stock recovery?
do you have a stock kernel?

Nininho1995 said:
do you have a stock rom?
do you have a stock recovery?
do you have a stock kernel?
Click to expand...
Click to collapse
Yes, i have everything stock. Installed from sammobile . com.

ok then'll try a pre rooted rom to flash from djembey. it is not good that you do not get into recovery. then you reflashing the latest philz revovery touch.
so everything should work, take the best pre rooted XXUEML6 because this is the latest.

Nininho1995 said:
ok then'll try a pre rooted rom to flash from djembey. it is not good that you do not get into recovery. then you reflashing the latest philz revovery touch.
so everything should work, take the best pre rooted XXUEML6 because this is the latest.
Click to expand...
Click to collapse
Thanks. I will give it a try.
Is this the file i need? Pre-Rooted ROM (Odex): Downloads: <<< MEGA >>> See below.
http://forum.xda-developers.com/showthread.php?t=2250824
Model: GT-I9505 (4.3)
PDA: XXUEML6
PHONE: XXUEML6
CSC: OXXEMK3 (27 codes) (NOTE: KIES will NOT recognize this FW due to CSC mismatch..)
Kernel: 3.4.0-2082040 (19.12)
KNOX WARRANTY VOID - 0x1
Build Date: 19.12.2013
Changelist: 2082040
Original Stock ROM: Download: <<< Samsung-Updates.com >>>
Pre-Rooted ROM (Odex): Downloads: <<< MEGA >>>
Latest KNOX Bootloader INCLUDED - Completely IRREVERSIBLE back to 4.2.2!!!

DannyPRK said:
Thanks. I will give it a try.
Is this the file i need? Pre-Rooted ROM (Odex): Downloads: <<< MEGA >>> See below.
http://forum.xda-developers.com/showthread.php?t=2250824
Model: GT-I9505 (4.3)
PDA: XXUEML6
PHONE: XXUEML6
CSC: OXXEMK3 (27 codes) (NOTE: KIES will NOT recognize this FW due to CSC mismatch..)
Kernel: 3.4.0-2082040 (19.12)
KNOX WARRANTY VOID - 0x1
Build Date: 19.12.2013
Changelist: 2082040
Original Stock ROM: Download: <<< Samsung-Updates.com >>>
Pre-Rooted ROM (Odex): Downloads: <<< MEGA >>>
Latest KNOX Bootloader INCLUDED - Completely IRREVERSIBLE back to 4.2.2!!!
Click to expand...
Click to collapse
Yes man this is the right one.

DannyPRK said:
Everytime i get stuck with the Boot logo, Recovery booting.. or Recovery is not enforcing seandroid.
Click to expand...
Click to collapse
- Turn off ur phone
- Use the combination (Vol up + Home button + Power button)
- When u see the letters of Samsung S4 in white... drop the Power button
- If u dont do it by this way u will be stucked in the boot logo
- This will go directly to your CUSTOM RECOVERY

Nothing works guys.
I really can't get into recovery mode at all.
When the phone is not flashed with the philz revovery touch, it keeps stuck on the samsung logo or Recovery booting....
When the phone is flashed with philz revovery touch i get:
Recovery booting....
Recovery is not enforcing seandroid
Warrenty Bit Set : Recovery
Are there more options?

Joku1981 said:
- Turn off ur phone
- Use the combination (Vol up + Home button + Power button)
- When u see the letters of Samsung S4 in white... drop the Power button
- If u dont do it by this way u will be stucked in the boot logo
- This will go directly to your CUSTOM RECOVERY
Click to expand...
Click to collapse
I did this like 1000 times. I'ts getting really frustrating. Could it be that the something is broken?

DannyPRK said:
I did this like 1000 times. I'ts getting really frustrating. Could it be that the something is broken?
Click to expand...
Click to collapse
1- Install the firmware u had (without .pit file). The stock firmware have STOCK recovery that have to work (If u cant go to STOCK recovery follow the step 2)
2- Flash this file with ODIN: HERE
3- Do the same process of post #12

Joku1981 said:
1- Install the firmware u had (without .pit file). The stock firmware have STOCK recovery that have to work (If u cant go to STOCK recovery follow the step 2)
2- Flash this file with ODIN: HERE
3- Do the same process of post #12
Click to expand...
Click to collapse
Just did this. Now i tried it with the I9505XXUEMJ7 (Non brandend NL).
Guess what? Recovery booting....
Is my phone dead?

So basically it comes to this:
- When flashed stock firmware:
Recovery booting....
- When flashed custom firmware:
Recovery booting....
- When flashed stock firmware + philz_touch, openrecovery-twrp or even with recovery-clockwork-touch :
Recovery booting....
Recovery is not enforcing seandroid
Warrenty Bit Set : Recovery

DannyPRK said:
So basically it comes to this:
- When flashed stock firmware:
Recovery booting....
- When flashed custom firmware:
Recovery booting....
- When flashed stock firmware + philz_touch, openrecovery-twrp or even with recovery-clockwork-touch :
Recovery booting....
Recovery is not enforcing seandroid
Warrenty Bit Set : Recovery
Click to expand...
Click to collapse
u have unbranded phone?

Joku1981 said:
u have unbranded phone?
Click to expand...
Click to collapse
I have T-mobile NL, but also with the T-mobile (I9505XXUEMKF) the recovery mode doesn't work, but Odin says Pass.
So i tried it also with NL Unbranded (I9505XXUEMJ7). I think this does not have any effect.
It's strange because before the screen replacement, the phone booted just fine (except i didn't have any screen). Now i have screen and no boot...
Edit:
What could be the problem?
- Bootloader?
- Some other error?

DannyPRK said:
I have T-mobile NL, but also with the T-mobile (I9505XXUEMKF) the recovery mode doesn't work, but Odin says Pass.
So i tried it also with NL Unbranded (I9505XXUEMJ7). I think this does not have any effect.
It's strange because before the screen replacement, the phone booted just fine (except i didn't have any screen). Now i have screen and no boot...
Edit:
What could be the problem?
- Bootloader?
- Some other error?
Click to expand...
Click to collapse
- Go to ODIN
- Untick REBOOT OPTION
- Flash again the MKF and the .pit file u downloaded before
- Click start and wait till finish
- When finish ur phone will be stucked but no worries
- Take off ur battery for 2 min
- Put it in again
- Turn on ur phone normally and let it boot for 10 min (no worries if u think its stucked)
- Tell me if booted correctly when u finish this process

Galaxy S5 "bootlocked" after attempted downgrade

Hello,
I am having some issues with my S5 G900A (AT&T). Any help I could get in order to get any functionality back out of my phone would be greatly appreciated.
I recently update via OTA to lollipop, but I wanted to get it rooted to try it out. The first thing I attempted to do was to revert the firmware back to 4.4.2 by using Odin. I used three different sources for the G900AUCU1ANCE model, the last of which I got from here, which I found from this post.
However, this did not work, and now I am forever stuck on the firmware update page.
When I ran the Odin program, the program failed and output the following:
<ID:0/007> Odin engine v(ID:3.1005)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> boot.img
<ID:0/007> NAND Write Start!!
<ID:0/007> recovery.img
<ID:0/007> persist.img.ext4
<ID:0/007> system.img.ext4
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
On the phone side, I get the following messages on the screen. The messages that appear after running Odin are bolded.
ODIN MODE
PRODUCT NAME: SM-G900A
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
REACTIVATION LOCK: OFF
KNOX WARRANTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLE (csb)
RP SWREV: S1, T2, R1, A3, P1
SECURE DOWNLOAD : ENABLE
UDC START
SYS REV CHECK FAIL : Refer 2 > Binary 1
SECURE CHECK FAIL : system
(Downloading... Do not turn off target!!)
Click to expand...
Click to collapse
At this point, if I restart by pulling out (the battery), and then turn it back on normally, then I get back to the 'Odin Mode' screen, but with the large message on the bottom: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
This message will appear when the following keypresses are used to turn the phone on:
Volume up + Lock
Volume down + Lock
Lock
Home + Lock
Volume up + Volume down + Lock
Volume up + Lock + Home
The following keypresses don't do anything
Volume up + Volume down
Volume up + Volume down + Home
Volume down + Home
Volume up + Home
Finally, if I do the following keypress:
Volume down + Lock + Home
I get the familiar warning screen:
Warning!!
A custom OS can cause critical problems in phone and installed applications.
If you want to download a custom OS, press the volume up key.
Otherwise press the volume down key to cancel.
Click to expand...
Click to collapse
If I press the volume down key, then I go back to the same Odin Mode screen with the "firmware upgrade encountered an issue" message from before. If I press the volume up key, then I get the Odin Mode screen (that always stays the same), but with "Downloading... Do not turn off target!!" as the message instead.
I also tried using Samsung Kies, though that method seems to be frowned upon by everyone. It clearly downloaded something and looked like it was installing something, but then it told me that I should run the emergency recovery process using an emergency recovery code. In the alert window, there was clearly a space where an emergency code was supposed to be, but there was no emergency code. Therefore, I was not able to get any farther using Kies.
I have read many posts mentioning that Odin can be very fickle, so I took the liberty of trying using two different USB cables and tried all 4 USB ports that are on my laptop, and I tried each of those three times. I also ensured that Kies and its background processes were not running when I utilized odin.
I also tried re-writing the PIT file, which I found from here, but when I did that, I got
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
In Odin and "SECURE CHECK FAIL : PIT" on my phone window.
After exhaustive googling, I am not too sure of what to do anymore, and would appreciate if someone could help.

Bootloader is locked, not sure there is anything you can do

*Detection* said:
Bootloader is locked, not sure there is anything you can do
Click to expand...
Click to collapse
2 questions, which error message points out to you that the "bootloader is locked," and does this mean that I would need to take my phone to AT&T to get it serviced?

<ID:0/007> FAIL! (Auth)
Tells me the Secure Boot Key is failing to authenticate
--
From what I've read, AT&T S5s are bootloader locked, as are a few other carrier branded ones
What is actually wrong with the phone? Just that you want to downgrade to Kitkat and root?
Or is there actually something wrong with Lollipop?
It is a very well known fact that after upgrading from KK to LP, you should factory reset the phone, KK leaves behind rubbish files that cause all sorts of issues, resetting cures a lot of them

Oh I see, thanks!
Nothing really wrong with it, I just wanted to try rooting the phone.

Unfortunately the only known method to root Lollipop is via ODIN, but it's still a fairly new OS so never say never about the devs finding an exploit that can be used with a locked bootloader

You cant downgrade from lollipop to kitkat once you take the ota for lollipop, as you can see here. You need to get the oc4(lollipop) firmware files and flash that to unbrick, they are in the att s5 general section.
Sent from my twi5ted SM-G900A using Tapatalk

Thanks, I ended up taking it to best buy and having the guy there reset the firmware. Pretty sure he used something called SMART or something to do it

i9507 Could not do normal boot, Odin mode

Hi,
I wouldn't normally post unless I really need help and I do, I've been at this for days, I'm stressing out because I really need my phone for work and I can't fix it myself...
My phone is stuck in a loop where every time I turn it off/on it goes straight into download mode.
It's doing this because I foolishly (without knowing what I was doing) used a .pit file I downloaded off of the internet.
I installed Clockworkmod 11 on my i9507 with the jfltexx i9505 rom.
It worked flawlessly except the 3G would drop out every time I locked the screen. Only 2G would work.
To try and fix it I downloaded a I9505DVUAMD8_MODEM.tar because I'm on Australia's 3G Telstra network through ALDI (medion) mobile.
The problem I had was that when I tried to flash the new modem, Odin would say that it failed.
So without knowing what I was doing, I used CSB_signed_Fusion3_TDD_0906_V2.pit
Now my phone is stuck in a loop where it goes straight into download mode.
Can someone please tell me how to fix this, I'm stressing out because all of my work is on this phone.
Please help, I'd really appreciate it.

Just flash a stock rom for the I9507 and you will be fine.

Lennyz1988 said:
Just flash a stock rom for the I9507 and you will be fine.
Click to expand...
Click to collapse
This is a really noob question but would you be able to save me a heap of time and link me to one please? My head is going to explode soon...
Edit:
I found this, which has the stock optus rom but it's an extremely slow (10 hour) 1.7gb download. I don't think this is right...
http://www.mrcrab.net/viewstockrom/30638-gt-i9507.html

alex8337 said:
This is a really noob question but would you be able to save me a heap of time and link me to one please? My head is going to explode soon...
Edit:
I found this, which has the stock optus rom but it's an extremely slow (10 hour) 1.7gb download. I don't think this is right...
http://www.mrcrab.net/viewstockrom/30638-gt-i9507.html
Click to expand...
Click to collapse
http://samsung-updates.com/details/41041/Galaxy_S4_TD-LTE/GT-I9507/OPS/I9507XXUFOA1.html

Neither mirror in that link works.
The download starts but doesn't actually download anything... It just sits at 0% with '10 hours left'.
Edit: Now it's jumped up to 22 hours left...

alex8337 said:
Neither mirror in that link works.
The download starts but doesn't actually download anything... It just sits at 0% with '10 hours left'.
Edit: Now it's jumped up to 22 hours left...
Click to expand...
Click to collapse
You can also try to reflash the recovery and then reflash the custom rom you were on. That should also work.

Lennyz1988 said:
You can also try to reflash the recovery and then reflash the custom rom you were on. That should also work.
Click to expand...
Click to collapse
Noob again... Sorry. How do I do that? Reflash the recovery I mean.
I really appreciate your help. At least I don't feel like I'm about to burst into tears anymore.
Edit: I've got recovery-clockwork-touch-6.0.4.7-jfltexx.img on my desktop, I just don't know how to use it with Odin.

alex8337 said:
Noob again... Sorry. How do I do that? Reflash the recovery I mean.
I really appreciate your help. At least I don't feel like I'm about to burst into tears anymore.
Edit: I've got recovery-clockwork-touch-6.0.4.7-jfltexx.img on my desktop, I just don't know how to use it with Odin.
Click to expand...
Click to collapse
Put it in AP/PDA (depends on the Odin version). Uncheck auto-reboot and flash it in download mode.

Lennyz1988 said:
You can also try to reflash the recovery and then reflash the custom rom you were on. That should also work.
Click to expand...
Click to collapse
I don't understand what you mean by 'reflash recovery'?
I downloaded clockworkmod touch 6.0.4.7 but its a .img file and I don't know how to use it with Odin.
So I continued with what you told me to do the first time.
Lennyz1988 said:
Put it in AP/PDA (depends on the Odin version). Uncheck auto-reboot and flash it in download mode.
Click to expand...
Click to collapse
I9507XXUFOA1_I9507OPSFOA1_I9507XXUFOA1_HOME.tar.md5 with Odin 3.09, AP.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9507XXUFOA1_I9507OPSFOA1_I9507XXUFOA1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<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> sbl2.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> aboot.mbn
<ID:0/005> tz.mbn
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> FAIL! (Ext4)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I reset the phone a good 10min after and now it still boots into Odin mode but this is on the screen instead.
Odin mode
Product name: GT0i9507
Current binary: Samsung official
System status: Custom
Knox kernel lock: 0x0
Knox warranty void: 0x1
Csb-config-lsb: 0x30
Write protection: Enable
eMMC BURST MODE: Enabled
START [224, 1440]
ODIN : Invalid ext4 image
FIRMWARE UPGRADE ENCOUNTERED AN ISSSUE. PLEASE SELECT RECOVERY MODE IN KIES & TRY AGAIN.

You must flash the zip file,dont unpack the zip file,put the zip file in PA or PDA

ludoke said:
You must flash the zip file,dont unpack the zip file,put the zip file in PA or PDA
Click to expand...
Click to collapse
The zip file on its own doesn't show up when I click open in Odin though?
When I click AP/PDA and the Open box pops up, it doesn't show the zip file.
file name must be PDA File (*.tar, *.md5, *.smd, *.gz, *.tgz)
What am I supposed to do...

alex8337 said:
The zip file on its own doesn't show up when I click open in Odin though?
When I click AP/PDA and the Open box pops up, it doesn't show the zip file.
file name must be PDA File (*.tar, *.md5, *.smd, *.gz, *.tgz)
What am I supposed to do...
Click to expand...
Click to collapse
Open Odin ,connect your phone to pc via usb ,developers options enabled in ...settings ...about phone ..tap 6 or 7 times on build and enable usb ...foutopsporing in Dutch...also enable unknown sources .gO IN download mode ..search for how to do it. When phone is recognized in Odin
(If in the section ID COM is blue or yellow with a number it ,youre ready to go...
Tap on AP and it will ask for a file ...navigate on your pc to the location where you have stored the file,at first choose the Chainfire root file(,leave all the settings in Odin as the are) .it will appear in the AP section and hit Start ,wait until PASS appears in Odin...Disconnect phone from pc ,shut down Odin , Start the phone again in Download mode connect to pc and follow the same steps as with root,NOW UNCHECK automatic reboot in Odin,hit start and wait for Pass.
This should do the trick
---------- Post added at 01:10 PM ---------- Previous post was at 12:56 PM ----------
For root you need .tar file so unzip the zip file only once and flash that .tar file . For TWRP use the zip file,it contents the recovery.img NO need to unzip!!!
Sorry if i put you on the wrong leg.

I kept getting the same fail message in Odin.
I've fixed it now. I used Samsung Kies > Tools > Firmware upgrade and installation. It's taken the phone back to the stock Australian Optus rom. Not the original optus rom with baseband XXUAMH2 but a newer one running 4.2.2 with baseband XXUFOA1. Unfortunately I've lost all data on it but thankfully the phone still works. I was stressing out of my mind.
Thanks to everyone for helping, I appreciate your input