Develop Bugs

[Q] AT&T SGH-I747 Soft Brick Need Help!!!

I need help recovering my GS3, i tried using CF auto root to root my phone and i guess it didnt work because my phone doesnt boot past the samsung screen. I didnt have any custom recovery installed so i dont believe and thing was backed up. I am able to get into download mode and recovery mode. I tried flashing stock firmware using kies but it encounters a error saying its a problem with my phone, I tried using odin but it also gives me an error when flashing firmware saying
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_ATT_I747UCDLK3.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> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1
What do I do to fix my phone?

FuTuRisTiC Zo3 said:
I need help recovering my GS3, i tried using CF auto root to root my phone and i guess it didnt work because my phone doesnt boot past the samsung screen. I didnt have any custom recovery installed so i dont believe and thing was backed up. I am able to get into download mode and recovery mode. I tried flashing stock firmware using kies but it encounters a error saying its a problem with my phone, I tried using odin but it also gives me an error when flashing firmware saying
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_ATT_I747UCDLK3.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> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1
What do I do to fix my phone?
Click to expand...
Click to collapse
Ok I Installed Insecure Boot img via odin3 and my phone rebooted but now instead of it booting at the 1 second samsung screen it goes past it to the galaxy s 3 screen and just sits there. i also installed twrp, it let me mount everything but i cant u adb to push anything and it says i have no os installed. i dont know what moves to make anymore someone please help me out!!!

What version of Android did you have on your phone when it last worked, stock or custom ROM?

dawgdoc said:
What version of Android did you have on your phone when it last worked, stock or custom ROM?
Click to expand...
Click to collapse
its was a stock android rom i believe im not sure what version though.

Are you still able to get it into download mode?
Press and hold volume down + home + power at the same time

lemngo02 said:
Are you still able to get it into download mode?
Press and hold volume down + home + power at the same time
Click to expand...
Click to collapse
yes im able to go into download and recovery mode

lemngo02 said:
Are you still able to get it into download mode?
Press and hold volume down + home + power at the same time
Click to expand...
Click to collapse
oops didnt fully read your 1st post

lemngo02 said:
oops didnt fully read your 1st post
Click to expand...
Click to collapse
thats koo but the problem is i dont think my phone is rooted, i cant adb push using twrp cause my device wont show up when i adb devices

If you had the 4.3 bootloader on your phone, you cannot use Odin to flash a stock ROM.
Were you running the stock AT&T 4.3 ROM?

FuTuRisTiC Zo3 said:
thats koo but the problem is i dont think my phone is rooted, i cant adb push using twrp cause my device wont show up when i adb devices
Click to expand...
Click to collapse
Based on your Odin printout in the first post you were flashing a modified 4.1.1 kernel to install root. This should be fine if you were on either the 4.1.1 or 4.1.2 stock ROM. If you were on the 4.3 stock ROM your root attempt is probably the source of the problem.
IMPORTANT How to proceed from here depends on if you were on 4.3 or an earlier version of stock.
Also, since this forum is for AT&T and Canadian variants; I see the title of the first post says i747 - is this correct? It matters.

dawgdoc said:
Based on your Odin printout in the first post you were flashing a modified 4.1.1 kernel to install root. This should be fine if you were on either the 4.1.1 or 4.1.2 stock ROM. If you were on the 4.3 stock ROM your root attempt is probably the source of the problem.
IMPORTANT How to proceed from here depends on if you were on 4.3 or an earlier version of stock.
Also, since this forum is for AT&T and Canadian variants; I see the title of the first post says i747 - is this correct? It matters.
Click to expand...
Click to collapse
ok, not to jack his thread, but what if you are on the 4.3 bootloader? i didnt do what he did, but i am stuck in a similar situation. I am on the 4.3 bootloader, but i do have a custom recovery installed. problem is i get an error when i try to wipe. Ive tried flashing stock 4.3 rom via sideload in stock recovery, and modified rom though twrp. both roms install fine, but dont boot, but they do freeze in different points so i know something is being flashed. ive also tried wiping in cwm and stock. im bout ready to flash anything to this phone. oh and a nandroid restore fails after boot img flashes.

FuTuRisTiC Zo3 said:
its was a stock android rom i believe im not sure what version though.
Click to expand...
Click to collapse
From your message, you likely were on stock 4.3. Since you are able to get into recovery and download modes, you may try a restore via custom recovery. Please see the thread below on how to install custom recovery and do a stock restore ...
<http://forum.xda-developers.com/showthread.php?t=2658486>

fastludeh22 said:
ok, not to jack his thread, but what if you are on the 4.3 bootloader? I am on the 4.3 bootloader, but i do have a custom recovery installed.
Click to expand...
Click to collapse
I would then link you to the same thread Larry2999 provided.

dawgdoc said:
I would then link you to the same thread Larry2999 provided.
Click to expand...
Click to collapse
thanks. i had found that thread right after i posted. lets hope. its halfway downloaded. if that doesnt work,ill be posting a thread about the weird way i ended up here and detailed report of what i did and what ive tried...

dawgdoc said:
Based on your Odin printout in the first post you were flashing a modified 4.1.1 kernel to install root. This should be fine if you were on either the 4.1.1 or 4.1.2 stock ROM. If you were on the 4.3 stock ROM your root attempt is probably the source of the problem.
IMPORTANT How to proceed from here depends on if you were on 4.3 or an earlier version of stock.
Also, since this forum is for AT&T and Canadian variants; I see the title of the first post says i747 - is this correct? It matters.
Click to expand...
Click to collapse
audit13 said:
If you had the 4.3 bootloader on your phone, you cannot use Odin to flash a stock ROM.
Were you running the stock AT&T 4.3 ROM?
Click to expand...
Click to collapse
Yes the phone is AT&T and more than likely it was on 4.3 now what do i do

never mind folks i got it up and running my only option was to use the sd card so i found my adapter and fixed it. im on 4.1.2 now its updating software now im guessing to 4.3. thank you guys for all the help

FuTuRisTiC Zo3 said:
Yes the phone is AT&T and more than likely it was on 4.3 now what do i do
Click to expand...
Click to collapse
Before doing anything else, boot into recovery. If you are on a stock recovery the very first line will tell you that the system recovery is 3e
If you have one of the custom recoveries it will be different. If you have one of the custom recoveries, TWRP or CWM, you can use the link Larry299 posted earlier in this thread to restore your phone. If you are on the stock recovery and the 4.3 bootloader I don't know what to suggest.

dawgdoc said:
Before doing anything else, boot into recovery. If you are on a stock recovery the very first line will tell you that the system recovery is 3e
If you have one of the custom recoveries it will be different. If you have one of the custom recoveries, TWRP or CWM, you can use the link Larry299 posted earlier in this thread to restore your phone. If you are on the stock recovery and the 4.3 bootloader I don't know what to suggest.
Click to expand...
Click to collapse
I got everything back to normal im rooted on 4.1.2 and have a pending up date, is it safe for me to update via software updater or do i have to do something else

FuTuRisTiC Zo3 said:
I got everything back to normal im rooted on 4.1.2 and have a pending up date, is it safe for me to update via software updater or do i have to do something else
Click to expand...
Click to collapse
There is a chance that being rooted will prevent you from using the OTA official update. I've seen reports of people being able to update to the official 4.3 while rooted, but I've also seen reports of people not being able to update.
Before you make that update, bear in mind that the official 4.3 bootloader, its name ends in MJB, is the one that will prevent you from ever going back to an older bootloader. Some of the devs and the more experienced on here have no problem with that. Others do consider it an issue. An alternative is to install the leaked 4.3 bootloader, it's name ends in MJ2. That bootloader will allow you to downgrade to the 4.1.1 or 4.1.2 bootloaders, or so I have read. There is information about this in the development and the general forums for our device.
To muddy the waters more; if you intend to sim unlock your device without gettings codes from your carrier you need to do it from the 4.1.1 official ROM. A point you can not return to from the official 4.3 ROM, or so I've read.

I am having a huge booting issue with my Samsung Galaxy S3. Its a brand new one and I tried rooting it but it gave me this error:
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<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)
I can get to download mode, but not recovery nor does it boot into the Android OS. I tried putting back the stock OS and it gave me this error:
<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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've tried follow a bunch of these threads, but I can't seem to resolve my issue yet. I probably have that 4.3 bootloader which screwed everything up. Can someone help me resolve my issue? I literally got this phone today from AT&T. Thank you.

Can't return back to stock ROM

Hello, could please someone help me with this terrible problem? I have Galaxy S4 mini (i9195 LTE version). I flashed clockwork recovery, make a root and install CyanogenMod 11 (everything works fine). But I need to complaint this device back to the shop, because it has problems with random restarts (and I was thinking than maybe a flashing of custom ROM can help, but no). But when I connect device to the PC with Odin (3.09, but I tried 3.07 and others), select original ROM (which I downloaded from sammobile) and click Start, process fails after few seconds (I tried all of USB ports on my laptop and I tried same steps on my second PC), but with no success
Here is the log from ODIN:
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9195XXUBML4_I9195TMZBML1_I9195XXUBML4_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> sbl2.mbn
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> aboot.mbn
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On the screen of my phone I see this:
ODIN MODE
Model: gt-i9195
Current binary: custom
System status: official
Knox kernel lock: 0x0
Know warranty void: 0x1
CSB-config-LSB: 0x30
Bootloader ap swrev: 2
Write protection: enable
SW REV CHECK FAIL: Fused 2 > Binary 1
And I am trying to flash this ROM:
Model: GT-I9195
Model name: GALAXY S4 mini LTE
Country: Germany (T-Mobile)
Version: Android 4.2.2
Changelist: 2340422
Build date: Fri, 20 Dec 2013 16:46:00 +0000
Product Code: TMZ
PDA: I9195XXUBML4
CSC: I9195TMZBML1
MODEM: I9195XXUBML4
Can someone tell me why I can't return back to stock ROM?

jerrry said:
[SNIP]
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)[/CODE]
[SNIP]
Click to expand...
Click to collapse
See that "Auth" there? Have you allowed access to your phone via USB? First thing that comes to mind for me.

Because you have latest knox bootloader. Do you see that line ""bootloader ap swrev : 2"" in your download mode.....that indicates it.
So this means you cannot downgrade to jellybean roms. Do not try to downgrade because repeated failures of odin might brick your device.
The mbn files odin flashes are all related to bootloader and corrupted bootloader = hard brick.
If you are desperate for jellybean flash the brazil ububne2 for I9195. Only that JB works. Good luck.

ericlnu: Thank you for reply. Did you mean USB debugging in phone settings menu? But I can't boot into system because the last flash causes FAIL message and I can only access to bootloader or download mode.
sasank360: Thank you very much for your support. I didn't know that. So you mean than I need to download Brazil ROM for i9195 (ububne2), which will only works? (and after that I can update to 4.4.2)? Or what Can I do after flashing ububne2 ROM if I need back original stock ROM from my operator?

jerrry said:
ericlnu: Thank you for reply. Did you mean USB debugging in phone settings menu? But I can't boot into system because the last flash causes FAIL message and I can only access to bootloader or download mode.
sasank360: Thank you very much for your support. I didn't know that. So you mean than I need to download Brazil ROM for i9195 (ububne2), which will only works? (and after that I can update to 4.4.2)? Or what Can I do after flashing ububne2 ROM if I need back original stock ROM from my operator?
Click to expand...
Click to collapse
You cannot go back any further. Jellybean ububne2 is the latest jb rom and only that works. Ofcourse you can flash any stock kitkat firmware if you wish. Good luck.

Thank you. I flashed ububne2 ROM to my Galaxy S4 mini and finally, ODIN didn't fails (and phone si working). But when I try to flash latest KitKat ROM (from my operator or any Jelly Bean ROM for my region), ODIN again fails with flashing. Ububne2 is right now the one and only ROM which I can flash to my device.

jerrry said:
Thank you. I flashed ububne2 ROM to my Galaxy S4 mini and finally, ODIN didn't fails (and phone si working). But when I try to flash latest KitKat ROM (from my operator or any Jelly Bean ROM for my region), ODIN again fails with flashing. Ububne2 is right now the one and only ROM which I can flash to my device.
Click to expand...
Click to collapse
Try the knox free kk rom. worked fine for me. knox tripped and running cm11.

kev23m: You mean any unnoficial ROM? This is not sollution for me (I already tried CM11 ROM), but due to random restarts (which is probably hw problem) I need return back stock ROM and complaint device with my seller/shop (as a part of warranty issue).

jerrry said:
kev23m: You mean any unnoficial ROM? This is not sollution for me (I already tried CM11 ROM), but due to random restarts (which is probably hw problem) I need return back stock ROM and complaint device with my seller/shop (as a part of warranty issue).
Click to expand...
Click to collapse
It is the stock rom , knox bootloader removed so people can update without knox. Thanks to SilviuMik
Click Here

oh, I see. But this ROM is only for Galaxy S4 Mini Duos, I have classic LTE version (i9195).

jerrry said:
oh, I see. But this ROM is only for Galaxy S4 Mini Duos, I have classic LTE version (i9195).
Click to expand...
Click to collapse
oops. I think i read somewhere he got a request for 9195 too, maybe he has prepared it. Just do a search and see.
See this

S3 keeps rebooting into recovery

So this is just a quick question. I've never had a phone reboot into recovery mode before, I've just had them either straight up hardbricked, stuck on logos, not booting, or only booting into Download Mode. From going through other threads (I used the search bar before asking this question. *shock&awe*), I'm gonna assume this is also considered a soft brick.
I'm not sure what was done to the phone because I upgraded to an S5 and passed this S3 down to my little brother who tried to flash another ROM. It was working fine on one of the stable versions of SlimKit before I got the S5 if that matters.
So my questions:
Is this considered a soft brick?
Would flashing stock everything resolve this issue? (reverting back to Stock everything, then reflashing custom ROMs)
Is there a simpler way to resolve this issue to avoid going back completely to stock?
Thanks for looking everyone.

Yes, anytime you can get to download mode or recovery its considered a soft brick. A hard brick will not boot anything at all.
Flashing stock firmware will be the best option imo. But you could just try flashing a rom. You will likely have to factory reset in either case.
If i had to guess, he probably formatted /system and then the rom failed to flash, leaving it with no OS.
Sent from my SAMSUNG-SGH-T999 using Tapatalk

I haven't tried to do anything with it until he gets home, but best bet would be the following? Let me know if something's off or if I should do something another way:
Download stock firmware on the SD card
Factory reset
Flash stock firmware
Flash custom ROM
Reboot
At any point would the phone get unrooted? I'm gonna just make sure everything's set to go when the little bro gets home.

You cannot flash stock firmware from SD. Here is what you should do:
1) download stock firmware to your computer
2) factory reset, wipe cache and dalvik
3) flash stock firmware with Odin and make sure the device boots and works fine
4) flash custom recovery
5) flash custom ROM
6) reboot
Edit: also make sure you flash the correct firmware. For example if the device was ever updated to 4.3 then only flash that 4.3 build, any other that is lower will fail. And yes you will lose root when you flash back to stock but it doesn't mean much at all. You can gain root easily

I keep getting this issue in ODIN when I attempt to flash a stock firmware. Any ideas?
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_TMO_T999UVUENC2.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> sbl2.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!

Ate you sure you have a T999, not a T999L.
Also, if kies is on your computer, uninstall it.

It's a S3 from T-Mobile directly, so I think it's a T999. I have Kies 3 for my S5 installed, so I'll go ahead and uninstall to try again. Will report back.

Check the sticker under the battery. T-Mobile doesnt sell the T999 anymore, only the T999L. Depends on how long ago you got it.

DocHoliday77 said:
Check the sticker under the battery. T-Mobile doesnt sell the T999 anymore, only the T999L. Depends on how long ago you got it.
Click to expand...
Click to collapse
I love you. Be back after getting the right firmware.

Just fyi in case you didnt know, there is an ota available for the T999L.
After flashing your firmware, go to settings , about device, and tap software update. It should update you to the latest build. (Still just 4.3, but i imagine its a bugfix/security update).
If you are up for putting in a little extra time, i can help you pull the ota (after downloading but before flashing it). If i can get a hold of this ota i can make an easier update method available for other members since no firmware has been released for it.
If you dont want to thats perfectly fine btw. Im sure someone else would get it soon.

Tried to Unroot now bricked

I had Cynagenmod 4.4.4 on my S4. I wanted to unroot it as the release is buggy. So I went to a link on how to unroot at S4 phones and followed the steps and now I cant get it to unroot and its now stuck in a boot loop. I have tried ODIN multiple times and this is what I get.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_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> Removed!!
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sbl2.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Please help. My phone is a paperweight right now.

Its also giving me a check fail on the phone itself.
Start [224,1140]
SW Rev. Check Fail: 4, Binary : 1

Snakedoktor said:
Its also giving me a check fail on the phone itself.
Start [224,1140]
SW Rev. Check Fail: 4, Binary : 1
Click to expand...
Click to collapse
Your trying to flash the wrong firmware? What was your phone BEFORE you rooted? 4.2.2? 4.3?

The Sickness said:
Your trying to flash the wrong firmware? What was your phone BEFORE you rooted? 4.2.2? 4.3?
Click to expand...
Click to collapse
It was December of last year. I dont honestly remember. I know I was at 4.4.4 when it was rooted. Just looked it up November of last year was 4.3

Snakedoktor said:
It was December of last year. I dont honestly remember. I know I ad 4.4.4 when it was rooted.
Click to expand...
Click to collapse
If you got it in Dec then it was 4.3. If it was 4.4.4 when you rooted meant you took a OTA?

The Sickness said:
If you got it in Dec then it was 4.3. If it was 4.4.4 when you rooted meant you took a OTA?
Click to expand...
Click to collapse
It was an update via cynogen mod that updated it to 4.4.4. It does look like it had 4.3 like you said. Did I download the wrong file?

Snakedoktor said:
It was an update via cynogen mod that updated it to 4.4.4. It does look like it had 4.3 like you said. Did I download the wrong file?
Click to expand...
Click to collapse
Yes you DL the wrong file. Im not too familar with Cynogen. So if it did update you to 4.4.4, you need to Odin the Official 4.4.4 Firmware

Cyanogen 4.4.4 won't require you to flash stock 4.4.4 because it does not update firmware If you had official 4.3 firmware when you flashed cm then you need to flash at least 4.3 firmware. That's why you are getting the error, you were trying to flash 4.2.2. You have the option of flashing 4.3 MK2, 4.4.2 NB4, or 4.4.4 NH7. You might as well flash NH7

One other thought: Just because the CM you are running has some bugs, perhaps another ROM would be a better experience than the bloated Samsung stock.
I'm very happy on Dirty Unicorns, but I've been thinking to try a very basic Slimkat or something like that, then theme it with Themer, and add any apps/functions needed.
Maybe something like that would work for you?
Marc

Unable to Odin stock OB7 or stock NK2.

I don't seem to be able to Odin stock OB7 or stock NK2. When I attempt to Odin either I get this on Odin:
<OSM> N910PVPU1BOB7_N910PSPT1BOB7_N910PVPU1BOB7_HOME.tar .md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.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> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and get this on the download screen:
UDC START
SW REV CHECK FAIL : [tz]Fused 3>Binary 1
[4]eMMC write fail: TZ
Right now I'm running HYBRID_OB7sbl_SPT_N910PVPU4COG5 unrooted. Any potential help with what I've done would be great. Thanks guys.

Cant go back. Period.
Sent from my SM-N910P using Tapatalk

I have the same problem. Updated the phone with the latest from Sprint / Samsung, then tried to root and got into a boot loop. I can get into download mode and recovery. Trying to flash a ROM with CWM recovery fails too.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910PVPU1BOB7_N910PSPT1BOB7_N910PVPU1BOB7_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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Read frezzas stockish thread.
Sent from my SM-N910P using Tapatalk

It's failing because the bootloader is not authenticating. Since you flashed my custom rom odin package I'm surprised it's not letting you flash the official OB7 rom tar. Apparently there's more to this equation than just the bootloader or else you tried or successfully flashed the pre-rooted kernel before you tried to odin the OB7 rom tar. Try flashing my custom OB7/OG5 rom tar again THEN flash the official OB7 rom tar. You need to be bone stock before attempting the odin of OB7. If it still fails then give up because you can't win this battle. Just update to OG5 and don't worry about it.
I'll be honest, there's really no reason why you shouldn't just go ahead and wipe everything clean and flash my custom OB7/OG5 rom tar again or the official OG5 rom tar and let your bootloader update to OG5. I think 5.1.1 is by far the best version of Android to date. I see absolutely no reason to flash older software versions because 5.1.1 is much more responsive in every way and battery life is improved as well. Don't sweat this. If I had any trouble with my OB7 bootloader I'd update mine to OG5 in a second.

After blowing nearly an entire day....
To start off my phone was stock / rooted, I then installed the latest update via Kies (OE1, wanted the Stagefreight patch) and attempted to re-root my phone which I then found was stuck in a boot loop. I got lazy, updates had been going well on the Note 4 and I failed to come to XDA to see if there were any problems rooting it, turns out there is :crying: and I couldn't get Kies to recover it, and factory reset didn't work either. To recover I tried to use ODIN to flash OB7 and received the above results, I tried a few other stock ROMs and got the same problem.
At this point I was about ready to chuck my phone out the door until I noticed a comment saying that once you flash OE1 you can't go back and the only option is to flash an AOSP ROM such as Notirized. I downloaded Notorized, following the OP directions step by step and I now have my phone back! So far I like this ROM, so maybe this was fate
http://forum.xda-developers.com/not...-noterized-rom-super-speedy-reliable-t3099382
Thanks XDA! Now if I only had come here first and saved myself an entire day of grief! (Took away from my time playing Elite Dangerous! lol).

Thanks man. I appreciate the response and the explanation. I thought it was an issue with the bootloader, but I was confused about what I had done. I did wind up wiping everything clean and flashing your custom OB7/OG5 rom tar. Thanks for putting that together. I definitely should have updated everything sooner. I appreciate the advice on the OG5 bootloader as well. Have a great weekend.
tx_dbs_tx said:
It's failing because the bootloader is not authenticating. Since you flashed my custom rom odin package I'm surprised it's not letting you flash the official OB7 rom tar. Apparently there's more to this equation than just the bootloader or else you tried or successfully flashed the pre-rooted kernel before you tried to odin the OB7 rom tar. Try flashing my custom OB7/OG5 rom tar again THEN flash the official OB7 rom tar. You need to be bone stock before attempting the odin of OB7. If it still fails then give up because you can't win this battle. Just update to OG5 and don't worry about it.
I'll be honest, there's really no reason why you shouldn't just go ahead and wipe everything clean and flash my custom OB7/OG5 rom tar again or the official OG5 rom tar and let your bootloader update to OG5. I think 5.1.1 is by far the best version of Android to date. I see absolutely no reason to flash older software versions because 5.1.1 is much more responsive in every way and battery life is improved as well. Don't sweat this. If I had any trouble with my OB7 bootloader I'd update mine to OG5 in a second.
Click to expand...
Click to collapse