Tried the root method here.
And got the error:
Code:
image size too large!! W:1080, H:1920
display image fail
SECURE FAIL: KERNEL
I panicked, but figured it'd be alright if I just flashed the stock firmware. I re-downloaded the unmodified stock firmware and not I am getting the error
Code:
sw rev check fail fused 3 > binary 2
Odin fails to flash stock at all. It seems to flash it if it's the modified one (the attempt to remove the bootloader) but it then doesn't boot.
If I try to boot phone after flashing stock and failing it says "Firmware upgrade encountered an issue. Please select revoery mode in kies & try again."
What can I do? I want to try re downloading/flashing the PIT file but i can't seem to find a download for that anywhere. Could anyone link me or maybe create a backup pit from their phones I could use?
I have no idea what to do...
Same Issue
I flashed Cyanogenmod and it was working smoothly until I would attempt to load certain apps like Tribal wars or if I was in Game of war, the text would lag after I type a single line of wording then it would jerk up and cause the app to crash. Also, after a few reboots I noticed it automatically uninstalled half of my total apps and I had to redownload them all. I would like to reverse what I did so I installed the stock firmware for my SPH-L520 with this method.
My phone's specs mentioned on Odin Download Mode..
PRODUCT NAME: SPH-L520
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
KNOX KERNAL LOCK: 0x0
KNOX WARRENTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
BOOTLOADER AP SWREV: 4
WRITE PROTECTION: ENABLE
I would get the following error after attempting to flash stock firmware..
What it says on Odin3 v3.07..
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L520VPUAMK2_L520SPTAMK2_L520VPUAMK2_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> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
What it says on my phone...
SW REV CHECK FAIL : Fused 4 > Binary 2
Anyone mind shedding some light on this?
Related
I am not new to the rooting scene, however I have a problem that I can't seem to figure out. I've been reading now for the past 2 days, tried several things and still can't get this resolved. I've never had any issues in the past with odin and rooting samsung phones before, including ones with locked bootloaders. However, I've met my match. I tried following the tutorial listed on this site for rooting the samsung note 3 from tmobile. I watched the video and followed along with the files listed here
http://forum.xda-developers.com/note-3-tmobile/#root
My problem is as follows: I tried rooting with odin, installed kies for the usb support but halfway through the root process I get the big RED FAILED! phone's progress bar stops and it hangs. I though this was strange and never encountered this before. I then tried repeating the same process and same results, however this time around I am only able to bring the phone into "odin" mode "download" and not the original stock rom.
At first I was getting the original "the firmware encountered an upgrade issue" and couldn't bypass this unless I opted for download mode. I've tried the same steps to "unbrick" via oden with stock tmobile firmware for this phone and yet it yields the same results, big exclamation failed on odin. I then tried the process with the .pit file to partition that I found online somewhere and that fails too. My note starts up now, but stuck at the samsung galaxy note 3 screen. I've tried several versions of odin, switching usb cables, usb ports and I am unable to root this phone or even get it unbricked! i've read extensively here and can't seem to find a solution to my problem. Can someone PLEASE point me in the right directions?? BTW, I am using a mac with VMWARE, i've never encountered any issues with vmware in the past while running windows 8.
Phone says the following:
Once in download mode my phone says the following:
ODIN MODE
PRODUCT NAME: SW-N900T
CURRENT BINARY: CUSTOM
SYSTEM STATUS: OFFICIAL
KNOX KERNEL LOCK: 0X0
KNOX WARRANTY VOID: 0X0
QUALCOM SECUREBOOT: ENAMBLE
RP SWREV: S2, T2, A2, A3 P2
WRITE PROTECTION: ENABLE
UOC START
and I get these results from ODIN:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900TUVUCNB4_N900TTMBCNB4_N900TUVUCNB4_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> 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> 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)
Please someone help me, I am desperate and I can't think of what to do next.
http://forum.xda-developers.com/showthread.php?t=2677032
TWEAKED N3
BACARDILIMON said:
http://forum.xda-developers.com/showthread.php?t=2677032
TWEAKED N3
Click to expand...
Click to collapse
I can't seem to do this on 2 versions of windows installed on vmware for my mac. Everytime I try odin fails! Is there a way you can help me do this with heimdall on my mac?
Hi Folks,
I've messed up my S4 mini. I'm going to try to remember what i have done..
First of all, I started with rooting my phone with Odin. After that I've installed Slimbean. Yesterday I thought I saw heaven in this Deodexed rooted rom: http://www.s4miniarchive.com/2014/04/deodexed-and-rooted-stock-for-galaxy-s4-mini.html But it went wrong.
I've copied that rom to my ext SD card and installed this zip with the install .zip function in the CWM Recovery interface. After installing I've rebooted. At the first screen my phone hangs.
After this I've tried to recover my phone with ODIN by using a stock rom I9195XXUBML4_I9195TNLBML1_I9195XXUBML4_HOME.tar.md5 But it hangs at the end of the proces. Below the transscript:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9195XXUBML4_I9195TNLBML1_I9195XXUBML4_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> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> NON-HLOS.bin
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> FAIL! (Ext4)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
When I'm trying to boot now I got the Annoying message stating: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
Unfortunately the recoverymode in Kies doesn't see my phone.
Does anyone out here know a possible workaround?
Hope I can find help here!
Thanks a lot!
Arno (from The Netherlands)
wich firmware you where on begining?
whats your download screen looks like, does it have the word knox on it?
fburgos said:
wich firmware you where on begining?
whats your download screen looks like, does it have the word knox on it?
Click to expand...
Click to collapse
I don't know on which firmware my phone started.
My screen contains the following information:
ODIN MODE
PRODUCT NAME: GT-I9195
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
BOOTLOADER AP SWREV: 1
WRITE PROTECTION: Enable
Am I screwed?
47273 said:
I don't know on which firmware my phone started.
My screen contains the following information:
ODIN MODE
PRODUCT NAME: GT-I9195
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
BOOTLOADER AP SWREV: 1
WRITE PROTECTION: Enable
Am I screwed?
Click to expand...
Click to collapse
No you are not.
Based on your "screen" the computer should detect it . Kies is :silly:, if not try different ports of pc, or other pc. You also can try making a "samsung jig" if all fail (Google it = instructions).
Load the correct latest firmware depending on you back sticker (under the battery) with odin.
Best of luck.
vasiboss said:
No you are not.
Based on your "screen" the computer should detect it . Kies is :silly:, if not try different ports of pc, or other pc. You also can try making a "samsung jig" if all fail (Google it = instructions).
Load the correct latest firmware depending on you back sticker (under the battery) with odin.
Best of luck.
Click to expand...
Click to collapse
It worked! I am back on a offical Samsung ROM and for now thats good enough.
Thanks a lot for your help!
My phone randomly stopped working the other day. When its off, it'll start up on its own (without the power button being touched) but only get past the "samsung" screen a couple times and then shut back off. I tried flashing the stock firmware via odin but it fails every time (I've used versions 1.86, 3.04 and 3.09). As of now, my phone is totally useless. All I can do is put it into download mode. Any ideas?
This is what odin says every time
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCALG1_I747ATTALG1_I747UCALG1_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)
Phone Screen:
ODIN MODE
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 0
BOOTLOADER AP SWREV: 3
SW REV CHECK FAIL : Fused 3 > Binary 0
Odon is failing because you are trying to downgrade the firmware. After 4.3 you cannot do this anymore. It looks like you probably updated to 4.4.2 via ota. Correct? If so there is no firmware you can flash as att refuses to release it.
Take your battery out and put it back in. If it tries to turn on by itself your power switch is bad and needs replacing.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Our daughter deleted all of the pics on my wife's phone. She tried to use Dr. Fone, but someone told us that it failed because her phone wasn't rooted. So I tried to root it from this post on cnet:
It failed during the root. Now it says "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again. Which I tried and also failed.
After a lot of heart ache and hours working on it, i have what a friend told me was the right tar file. I have attached the error in Odin.
When I run the tar file in Odin here is what the output screen shows:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<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> 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)
Then my phone screen show this:
SW REV CHECK FAIL : Fused 3 > Binary 0
Not really my area of expertise at all. Any help would be appreciated!!
Thanks,
Brian
You cannot flash that tar file onto your phone. It is failing because that file is trying to downgrade the bootloader.
I recommend not flashing anymore files until you know the bootloader version of your phone.
I recommend you flash the latest Philz Touch custom recovery using desktop Odin from here:https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Use Philz to flash the latest CM11 and Gapps. Then install the Samsung Phone Info app from the play store to verify your bootloader.
Once you know your bootloader, let us know the version.
Ok, about 2 weeks ago I flashed back to stock from a rooted stock rom using Odin and then took all of the OTA updates. I believe I took the BOB7 OTA as well. I then used the newest 5.1.1 root method to root. This also replaced my stock recovery with TWRP. Yesterday, I was going to return to sprint to do their new upgrade plan so I needed to get back to stock. I did exactly what I did 2 weeks ago to flash back to stock and now it won't work at all. Odin Reads:
<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/003> Added!!
<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> 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> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
My phone screen has this:
PRODUCT NAME: SM-N910P
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
REACTIVATION LOCK: OFF
KNOX WARRANTY VOID: 0x1
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T3, A1, A4, P1
SECURE DOWNLOAD: ENABLE
UDC Start
SW REV CHECK FAIL : [aboot] Fused 4 > Binary 1
[1] eMMC write fail : ABOOT
I then tried to redo the root method for 5.1.1 and erased my data and dalvick(sp?) cache inside of TWRP and doing this caused my phone to be stuck in a bootloop. Even though the flash failed multiple times in Odin, I was still able to get back into the system with no problems. Is there I a way I can flash EVERYTHING new including the recovery and system. I need my phone back to stock ASAP. I would greatly appreciate any help at all. Thanks!
Please close thread. I was flashing the wrong stock ROM. I needed to be flashing COG5