A few months ago, I got a (Verizon) Samsung Galaxy S4 (it was "free" with contract). I successfully rooted it not long after.
Just a couple weeks ago, an update was released through the verizon network, so blindly I decided to use the update, only to find out afterwards that it removed my root. I tried the same method I used before to root it, only to find people saying that the newest OTA (Over The Air) update made rooting impossible.
After a fair amount of searching, I found a method which supposedly would work (http://forum.xda-developers.com/showthread.php?t=2487142). I used the method, however it did not work, and my phone was stuck in download mode.
After previous reading, I learned that the only way to manually exit download mode was to take out the battery. Though the root attempt had failed, it was obvious that something had occurred, so I was hesitant to use the brute force method of exiting download mode. However, without knowing an alternative, I removed the battery.
Now, whenever I try to turn on my phone, I merely get the message "Firmware update has encountered an issue. Please select recovery mode in Kies and try again."
If it helps, the text displayed in the upper corner with this message is:
ODIN MODE
PRODUCT NAME: SCH-I545
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: CUSTOM
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enabled
eMMC BURST MODE enabled
I have tried firmware upgrade and initialization in Kies3, but an error message is shown saying "SCH-I545 does not support initialization", When I tried Kies2, it just told me that the device was not responding.
I am still able to enter download mode.
When I try to flash an os using odin, I get these results:
<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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<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> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And in the corner of my phone screen, a red message appears which says:
START [224,1440]
SW REV. CHECK FAIL : fused : 6 , Binary : 5
If there is any more information you would need, please let me know.
Oddity3 said:
..... please let me know.
Click to expand...
Click to collapse
After some time spent on really deep and sophisticated analysis of your problem, I think that you will have a very good option of solving your problems described here
I don't have the Verizon version but maybe try reflashing stock file in odin
bdog2015 said:
I don't have the Verizon version but maybe try reflashing stock file in odin
Click to expand...
Click to collapse
There isn't solution for:
START [224,1440]
SW REV. CHECK FAIL : fused : 6 , Binary : 5
You can get it to repair to service center.
Related
Ok well let's start by letting everyone know, I have searched EVERYWHERE! for a fix and i CANNOT find one. This is really fustrating me. I am a noob to these forums but i do have little knowledge when it comes to this kind of stuff.
I recently rooted my Samsung S4 GT-i9505 and i wanted to unroot it back to it's original state, In the process of unrooting i don't know what i have done wrong but i get stuck on a screen "Firmware upgrade encountered.. blah blah, NOW i have tried all means to try and fix this by using Odin WITH the original firmware from which i downloaded from the samsung drivers website. Everytime i try too flash it, It always FAILS. There is a type of firmware i can use "I9505XXUAMDE_I9505TELAMD8_I9505DVUAMD8_HOME.tar.md5", But this particular one installs SU, Which i don't want, It also causes several features on my phone to stop working. Such a the clock and i can't even use my wifi.. I have tried several times, Over and over to try and fix it through Odin, But it will not budge, I can load the phone to download mode, But can't get past that. I am now stuck on the upgrade issue screen and i am literally stuck on things to do.. Any help will be appreciated as i am in desperate need to have my phone back too working order! I have tried Kies, Installing it uninstalling it, Disabling my firewall.. EVERYTHING.. I am trying to install the original firmware "I9505XXUBMG4_I9505XSABMG1_I9505DVUBMG1_HOME.tar.md5" But Odin will not let me!!
Thankyou in advance to anyone that can help.
These are the details on my screen atm..
ODIN MODE
Product name: GT-i9505
Current Binary: Samsung official
System status: Official
Knox Kernel Lock: 0x0
Knox Warranty Void: 0x1
CSB-CONFIG-LSB: 0x30
Write protection: Enable
Here is the error i get from Odin:
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> sbl2.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl3.mbn
<ID:0/007> rpm.mbn
<ID:0/007> aboot.mbn
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Hey guys I am having some serious difficulties with my verizon note 3. Last night my phone started boot looping so I decided to wipe and recover from my backup. I did the factory reset and all was well but safestrap would not recognize my backup so I attempted to install the stock Jasmine Rom (which I was using when the boot loop happened). Every time I tried to install I would get the E: unable to mount 'system' and 'systemorig'. I tried to wipe the system and it did not work, so I tried to format the internal memory which did not work. Today I tried to flash stock ROM using Odin 3.09. I also downloaded the "pit" file to attempt to repartition the drive and Odin is failing as well because of an authorization error I believe.
Here is the Odin information:
<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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<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> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On the Firmware upgrade screen on my phone it reads
ODIN MODE
Product Name: SM-N900V
Current Binary: Samsung Official
System Status: Official
Knox Kernel Lock: 0x0
Knox Warranty Void: 0x1
Qualcomm Secureboot: Enable (CSB)
RP SWREV: S1, T1, R1, A3, P1
Write Protection: Enable
UDC START
SW REV CHECK FAIL: [aboot]Fused 3 (greater than) Binary 1
Any help would be greatly appreciated. Have I successfully bricked my phone?
Sorry if this has been covered before but I could not find anything that has worked, and I have tried so many things that people say to do on forums that I may have caused more damage to my phone than there was in the first place :crying:
Since last night I have not had a phone and I need to get this thing working ASAP because I need it for work.
You're not running VMWare are you? I had a similar error when trying to use ODIN on a work VMWare machine - it always failed. Once I went home to my desktop - ODIN successfully flashed.
BigMcGuire said:
You're not running VMWare are you? I had a similar error when trying to use ODIN on a work VMWare machine - it always failed. Once I went home to my desktop - ODIN successfully flashed.
Click to expand...
Click to collapse
No I am not running VMWare, but trying it on a different computer isn't a bad idea. I'll try it on my other desktop as soon as I get ODIN and the drivers installed. Thanks for the idea
Edit: Tried on a different computer, downloaded a different stock .tar.md5 file, did not try to flash the 'pit' file (re-partition)(some other forum told me to do that), and made sure that only auto reboot and f. reset time were checked. Odin passed and I am currently back on stock firmware with a working phone! Thank you BigMcguire and the rest of the XDA forums that i looked through to help me fix this!
Hello.
I got a new Galaxy S4 (I9500) this October, and decided I would go ahead and install custom recovery on it. Me thinking I can get anything to work did not heed the warnings that this model does not support it go ahead and try anyway. After several failed attempts I find some software on the Play store that seems promising. Long story short, I no longer have a functioning recovery partition, and my phone will always try to boot into recovery mode unless I boot in Odin mode.
I have tried to follow several guides, most of which tell me the same thing:
Get Samsung drivers (not Kies)
Download Odin (one version or another)
Get the I9500 Firmware and install using Odin.
My phone is (from the sticker below the battery):
MODEL:GT-I9500
FCC ID: A3LGTI9500
SSN:-I9500GSMH
It is also factory unlocked.
I did notice however that the text in the top left when in Odin mode says it is a SGH-I337
The full text:
ODIN MODE
PRODUCT NAME: SGH-I337
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE: enabled
I have tried flashing both 4.4.2 (as it was delivered with) and 5.0.1, but I get the same error:
<ID:0/005> Odin engine v(ID:3.1100)..
<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> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The error that is displayed on the phone is:
SECURE MAGICCODE CHECK FAIL : boot
Any help would be greatly appreciated!
Edit: Added phone error
Hey ya'll, this past Saturday my Note 4 started a boot loop while using Baconreader. I was using stock ROM, unrooted, T-Mobile. I first deleted the cache partition, then did a factory reset, but neither worked.
I tried flashing with Odin v3.09, using ROMS from SamMobile:
4.4.4 ANK4
5.0.1 COD6
5.0.1 COG2
Each time I would get
<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)
And on the phone in download mode was:
Odin Mode (High Speed)
Product Name: SM-N910T
Current Binary: Samsung Official
System Status: Official
Reactivation Lock: Off
Knox Warranty Void: 0x0
Qualcomm Secureboot: Enable (CSB)
AP Swerv: S1, T1, R1, A2, P1
Secure Download: Enable
UDC Start
SW Rev Check Fail : [aboot]Fused 2 > Binary 1
[1]eMMC write fail: ABOOT
I then used the latest ROM from SamMobile, 6.0.1 EPE3, and everything worked. Odin flashed it and the installation was good. But as soon as it finished and booted for the first time the boot loop started again. I tried using KIES to do a emergency firmware restore but it would not pick up my Note 4 (Using a Samsung USB Cord) I tried it with and without Samsung USB Drivers installed. I'm starting to think it may be a hardware problem, honestly though I have no idea. I would like to get some other opinions before I send off for a new one. (No warranty over a year old) Thanks in advance, and sorry if the formatting is long, I figured it would be easier to read if everything was spaced out. Thanks in advance.
Hey guys please help me.
Long story short first: my stepsister wanted to get a new phone and gift this one to my stepdad. She apparently just factory resetted it with her google account on it but now when you start it up the FRP message pops up and the login doesn't work properly. This is the first time I even heard about FRP because I'm using a pretty old phone. I want to help because I'd consider myself good at computers and rooted my ex-smartphone years ago. Now I simply tried using this tutorial how to bypass it:
https://forum.xda-developers.com/general/general/bypass-frp-samsung-galaxy-s7-edge-t3765638
But that didn't work out because the ROM wasn't the right one for this device.
I spent the night downloading a previous stock ROM for it from a random website which took 12 hours
It was named DBT-G935FXXS1DQL1. Like I said stock ROM, I don't know if that's the right way. I wanted to downgrade it so I could use the bypass method from the tutorial.
But... That didn't work out either, Odin failed at this stage:
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> param.bin
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And on the smartphone this error message appeared in the download mode:
"SW REV. CHECK FAIL. DEVICE: 2, BINARY: 1"
Here are the informations I have from the recovery mode:
samsung/hero2ltexx/&hero2lte
7.0/NRD90M/G935FXXS2DRDI
user/release-keys
And this is standing in the download mode:
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT NAME: SM-G935F
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
FRP LOCK: ON
Secure Download: Enabled
WARRANTY VOID: 0 (0x0000)
RP SWREV: B:2 K:0 S:0
Please help me, I really have no clue about this flashing older firmwares and such.
Thank you in advance, Philipp
Hello, have you managed to solve this?
I have also similar problem
Samsung/hero21texx/hero2lte
8.0.0/R16NW/G935FXXU2EREM
No, I'm waiting for somebody who knows more.
e4zyphil said:
No, I'm waiting for somebody who knows more.
Click to expand...
Click to collapse
Me too, do you think this may work?
https://www.youtube.com/watch?v=KVYQyvJ7IVY
Balkrish999 said:
Me too, do you think this may work?
/watch?v=KVYQyvJ7IVY
Click to expand...
Click to collapse
this worked for me, thanks :good::good: