Database Users

[Q] secure chek fail : recovery, can´t flash anything

Hi guys I'm having problems trying to root my note 3, in fact i can't flash anything with odin.
It is a n900w8 from Telcel, with 4.4.2 stock rom.
I tried flashing to root it and tried to flash a custom recovery and nothing.
this is what odin shows:
<ID:0/009> recovery.img
<ID:0/009> NAND Write Start!!
<ID:0/009> FAIL! (Auth)
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and in the phone it shows in red letters : Secure check fail : recovery
I already checked the reactivation lock, and it isn´t checked.
Do you have an idea of what could it be?
If you need another info pleas tell me, i would appreciate any help thanks

1. Reinstall the Samsung's drivers.
2. Try other USB cable/port.
3. Take a look if you are flashing the latest firmware for your device. Latest is: HERE.

Joku1981 said:
1. Reinstall the Samsung's drivers.
2. Try other USB cable/port.
3. Take a look if you are flashing the latest firmware for your device. Latest is: .
Click to expand...
Click to collapse
thanks for the answer but i didn´t work , I can flash that rom but only that. I tried to flash the root and the same error.

[HELP] Cant boot in recovery mode

I just flashed 5.0.1 leaked firmware and im trying to flash twrp but i cant boot on recovery. What can i do to solve this ? Help plz..
p.s.: Everything else works fine

sonnax said:
I just flashed 5.0.1 leaked firmware and im trying to flash twrp but i cant boot on recovery. What can i do to solve this ? Help plz..
p.s.: Everything else works fine
Click to expand...
Click to collapse
try flashing recovery through odin

smth i had missed.. when i flashed recovery it failed and this is what it shows
Code:
<ID:0/004> recovery.img
<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)

sonnax said:
smth i had missed.. when i flashed recovery it failed and this is what it shows
Code:
<ID:0/004> recovery.img
<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
Hi
Did you try to flash rom again?

Yep 2 more times
-EDIT-
Might it be the fault of the twrp version im using? (openrecovery-twrp-2.8.4.0-klte.tar)

sonnax said:
Yep 2 more times
-EDIT-
Might it be the fault of the twrp version im using? (openrecovery-twrp-2.8.4.0-klte.tar)
Click to expand...
Click to collapse
Is possible....also remember is a leaked rom..

MAX 404 said:
Is possible....also remember is a leaked rom..
Click to expand...
Click to collapse
yep but none reported this difficulty.
-SOLVED-
Installed CWM and dissabled a couple of security settings. Not sure wich of these 2 did the trick. Thanks anyways

sonnax said:
yep but none reported this difficulty.
-SOLVED-
Installed CWM and dissabled a couple of security settings. Not sure wich of these 2 did the trick. Thanks anyways
Click to expand...
Click to collapse
Great news...
What security settings you disable?

[Q] ODIN Fails when trying to go back to stock

So i download my stock firmware off samsfirmware and tried to go back using odin but i always get Successful 0 Failed 1, can anyone help me please,?

LukeyyPalmerHD said:
So i download my stock firmware off samsfirmware and tried to go back using odin but i always get Successful 0 Failed 1, can anyone help me please,?
Click to expand...
Click to collapse
Hi mate ,
Please more info , what phone , what stock rom you had , what custom rom you had ( if so) , what stock rom are you trying to flash, what odin are you using , full odin log......

MAX 404 said:
Hi mate ,
Please more info , what phone , what stock rom you had , what custom rom you had ( if so) , what stock rom are you trying to flash, what odin are you using , full odin log......
Click to expand...
Click to collapse
Hi!
I have a Galaxy S4 i9505 - I bought the phone on a tesco contract so i am assuming the ROM would be the 02 one as they own tesco and i get the option between O2 PAY Monthly, 02 Pay As You GO and TESCO.
I'm trying to flash the 02 ROM (I9505XXUBMF8_I9505O2UBMG1_I9505XXUBMF8_HOME.tar)
I have tried using ODIN v1.85 and v3.09 but neither work
Log:
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<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>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

LukeyyPalmerHD said:
Hi!
I have a Galaxy S4 i9505 - I bought the phone on a tesco contract so i am assuming the ROM would be the 02 one as they own tesco and i get the option between O2 PAY Monthly, 02 Pay As You GO and TESCO.
I'm trying to flash the 02 ROM (I9505XXUBMF8_I9505O2UBMG1_I9505XXUBMF8_HOME.tar)
I have tried using ODIN v1.85 and v3.09 but neither work
Log:
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<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>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Hi mate ,
When i mention what stock rom i mean version number not from who ( carrier) aboot.mbn is the bootloader , if you try to flash a older bootloader than the one you have it will give you an error ( odin will not let you downgrade) , is that the latest stock rom for your phone/ carrier?
Just in case check that:
Odin troubleshooting: If Odin accidentally gives you "fail" try the following:
- Repeat procedure.
- Make sure that all actions of Kies are disabled from task manager.
- Change usb port.
- Try another usb cable (make sure it is the original).
- Try another Odin version.
- Uninstall and re-install driver.
- Use pit file.
- Try another computer.
http://forum.xda-developers.com/showthread.php?t=2265477

MAX 404 said:
Hi mate ,
When i mention what stock rom i mean version number not from who ( carrier) aboot.mbn is the bootloader , if you try to flash a older bootloader than the one you have it will give you an error ( odin will not let you downgrade) , is that the latest stock rom for your phone/ carrier?
Just in case check that:
Odin troubleshooting: If Odin accidentally gives you "fail" try the following:
- Repeat procedure.
- Make sure that all actions of Kies are disabled from task manager.
- Change usb port.
- Try another usb cable (make sure it is the original).
- Try another Odin version.
- Uninstall and re-install driver.
- Use pit file.
- Try another computer.
http://forum.xda-developers.com/showthread.php?t=2265477
Click to expand...
Click to collapse
I'm using the 4.2.2 ROM because im on 4.2.2, if i use 4.4.2 will it work?

LukeyyPalmerHD said:
I'm using the 4.2.2 ROM because im on 4.2.2, if i use 4.4.2 will it work?
Click to expand...
Click to collapse
Hi
You can use a stock 4.2.2 as long as you have a 4.2.2 bootloader that should be no problem , yes you can always upgrade (4.4.2)

MAX 404 said:
Hi
You can use a stock 4.2.2 as long as you have a 4.2.2 bootloader that should be no problem , yes you can always upgrade (4.4.2)
Click to expand...
Click to collapse
Hi, thanks for all the help, managed to fix it all and now im on lollipop

LukeyyPalmerHD said:
Hi, thanks for all the help, managed to fix it all and now im on lollipop
Click to expand...
Click to collapse
Great news mate!

ODIN is unable to flash stock firmware for Galaxy S4 SC-04E

Hi,
I need some assistance. I have an S4 (SC-04E) and it has TWRP custom recovery loaded in it. My colleague accidentally clicked wipe system from TWRP and it wasn't able to boot at all. So I thought I'd flash the stock firmware in order to resolve the problem. However, when I flash stock firmware on ODIN, it fails and gives me an error:
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> aboot.mbn
<ID:0/012> NAND Write Start!!
<ID:0/012> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
How do I resolve this? The original firmware was 5.0.1 and I tried flashing both 4.4.4 as well as 5.0.1, but both have failed. I googled the error and I was unable to get relevant results. I downloaded the stock firmware from sammobile. Any idea what I can do for this issue?

Your phone doesn't boot because your friend wiped the Operating System from it. The recovery should boot and flashing any custom ROM through it should make it work again.
Regarding your Odin problem, make sure you have done the following:
Used a different USB cable
Used a different USB port
Used a different Odin version
Tried another Windows
Tried a completely different PC.
All of the above can affect the outcome of flashing with Odin.

Soft Bricked S4

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

What is the model # in download mode?

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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