I got samsung I337 fully working phone and it had only one problem that it did not let us to select network mode and i tried to reflash the phone but stuck at " Firmware upgrade encountered an issue and flashing always failed.
In Download Mode it shows these things
Odin Mode
Product name: SGH-I337
Current Binary: Samsung Official
System Status: Custom
Knox Kernel Lock: 0x0
Knox Warrenty Void: 0x0
CSB-CONFIG-LSB:0X30
Waite Protection: Enable
eMMC Burst MODE enabled
So then i tried the odin method and downloaded both the 1337DB and DL file and tried running them in Odin. Odin fails and shows this in the messages:
I already tried with NCB1 firmware but its gives error at system file with pit and without pit.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_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> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
this occurs whether i check the boxes or not and if i add a pit file or not. Then on my phone it says in red, " SW REV. CHECK FAIL: fused:4, Binary 1".
Need perfect solution for it please help.
Following. I have the same situation.
kuljindersaini said:
I got samsung I337 fully working phone and it had only one problem that it did not let us to select network mode and i tried to reflash the phone but stuck at " Firmware upgrade encountered an issue and flashing always failed.
In Download Mode it shows these things
Odin Mode
Product name: SGH-I337
Current Binary: Samsung Official
System Status: Custom
Knox Kernel Lock: 0x0
Knox Warrenty Void: 0x0
CSB-CONFIG-LSB:0X30
Waite Protection: Enable
eMMC Burst MODE enabled
So then i tried the odin method and downloaded both the 1337DB and DL file and tried running them in Odin. Odin fails and shows this in the messages:
I already tried with NCB1 firmware but its gives error at system file with pit and without pit.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_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> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
this occurs whether i check the boxes or not and if i add a pit file or not. Then on my phone it says in red, " SW REV. CHECK FAIL: fused:4, Binary 1".
Need perfect solution for it please help.
Click to expand...
Click to collapse
If I understand you, U've tried two different firmware and they fail at different lengths.
Okay try flashing any custom recovery, I'd prefer Twrp. Try booting to recovery. If it boots lemme know.
It is not possible to install TWRP on the AT&T i337 S4.
Are you sure? I'm pretty sure there's a twrp recovery for the i337 except u are not keen with the search button. Im not sure if I'm allowed to post links, so I'd suggest you search through google u are sure to get one.
Oh, I'm familiar with the search function. I've been searching special topic forums ever since forums were created years ago. Newer bootloaders for the i337 are locked down solid. I think I would pee myself for joy if someone came up with a way to load a custom recovery for the i337 with the OK3 build. From what I get, there's nothing you can do once you have NB1 or newer.
OK if that's the case, get a mk3 rom, unpack the tar and remove the aboot file, (if it's a 4file repair fw, just don't add the aboot.) decompress the mk3.tar with 7zip remove the aboot repack it and flash via Odin.
Related
Hey Guys I have a Verizon S4 I am attempting to help a friend with he completely bricked it. Now only accessible option is ODIN Mode. I have tried 4 different versions of ODIN and 6 different tar files including the full wipe and everytime ODIN fails. I'm completely lost I personally have a L720 Sprint S4 and things are a little different but I cannot figure out anything to get this phone booted.
This is all I see.
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: ENABLE
Okay so Im assuming this phone either had the OTA Update and is on a Knox Bootloader. Like I said I don't care how I have to go about getting this phone booted any suggestions would help. I have bricked my L720 before and never had problems like this.
Thanks in Advance.
Would anyone be willing to help me? This is my Odin Log, no matter what I try to flash. This is what happens.
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> COMBINATION_I545VRUAME7_I545VZWAME7_690088_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> sbl1.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> sbl2.mbn
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/008> Removed!!
<ID:0/008> Added!!
GramKrackr said:
Would anyone be willing to help me? This is my Odin Log, no matter what I try to flash. This is what happens.
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> COMBINATION_I545VRUAME7_I545VZWAME7_690088_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> sbl1.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> sbl2.mbn
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/008> Removed!!
<ID:0/008> Added!!
Click to expand...
Click to collapse
are you trying to load stock ME7 on the device? if so and the device had a different version on it such as MJ7 you cannot go backwards and the odin flash will fail, try flashing stock MJ7 on the device and see if that helps
GramKrackr said:
Hey Guys I have a Verizon S4 I am attempting to help a friend with he completely bricked it. Now only accessible option is ODIN Mode. I have tried 4 different versions of ODIN and 6 different tar files including the full wipe and everytime ODIN fails. I'm completely lost I personally have a L720 Sprint S4 and things are a little different but I cannot figure out anything to get this phone booted.
This is all I see.
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: ENABLE
Okay so Im assuming this phone either had the OTA Update and is on a Knox Bootloader. Like I said I don't care how I have to go about getting this phone booted any suggestions would help. I have bricked my L720 before and never had problems like this.
Thanks in Advance.
Click to expand...
Click to collapse
If I'm not mistaken, the "Knox Warranty Void" flag showed up in MJ7, so you need to flash MJ7. Your log shows you flashing ME7, which is not going to work. The bootloader will not allow you to downgrade.
No-wipe and full-wipe images for MJ7 are available in the Android Development forum.
Hey guys i have a rooted Samsung Galaxy S4, 16GB, SGH-I337, with the safestrap custom recovery. and 2 days ago i tried to do a factory reset so i could have enough space to install a custom rom. Through my carelessness , i seem to have wiped the OS off of the device. Now if you try to turn the device on its stuck on the "Samsung custom" boot screen with the unlock icon in the middle. The device can go into download mode but fails to go into recovery mode.
Every time i try to go into recovery it displays the following:
Odin Mode
Product name: SGH-I337
Current Binary: Samsung Official
System Status: Custom
Knox Kernel Lock: 0x0
Knox Warrenty Void: 0x0
CSB-CONFIG-LSB:0X30
Waite Protection: Enable
eMMC Burst MODE enabled
Then the phone-computer caution emblem comes up in the middle of the screen and says, " Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". So ive tried Upgrade and Initialization and the Emergency Recovery feature but both failed. They both return a pop up message saying that " Firmware emergency recovery stopped due to GALAXY S4(SGH-I337) error. If the problem persists, please contact the Samsung service centre.". So then i tried the odin method and downloaded both the 1337DB and DL file and tried running them in Odin. Odin fails and shows this in the messages: <ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_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> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
this occurs whether i check the boxes or not and if i add a pit file or not. Then on my phone it says in red, " SW REV. CHECK FAIL: fused:4, Binary 1".
Everything that i have tried has resulted to a fail from Kies to Odin so right now im just about ready to give up and get a new phone. Is my Galaxy S4 still saveable and if so how would i go about saving it? thanks
(oh and sorry for the long question i just wanted to describe exactly what i was going through so you guys have all the information you need in order to develop a solution to my problem, if their is one.)
anyone please?
Looks like you have a knox enabled rom... have you tried mf3 or mk2. I think that of you didn't have at least mf3 that would have worked. I could be wrong on that part but if you cannot use your phone I wpuld try flashing one of those roms.
I337 stock, unlocked, rooted
Hi, I was trying to upgrade my Samsung Galaxy S3 i9300 ; firmware version 4.1.1 to 4.3
On my first attempt I used:
* I9300XXUGMK6_I9300OXXGML1_I9300XXUGMK6_HOME.tar
* Odin 3.07
I turned my phone off, then I went to Download Mode (power + volume down + home buttons), opened the Odin 3.09, opened the tar file on the PDA, ticked F Reset and Auto Reboot and start!
After this odin finished as:
Complete(write) operation failed! ...
On the download screen this is the following information:
Product Name: SGH-I747
Custom Binary Download: Yes (8 counts)
Current Binary: Custom
System Status: Custom
Qualcomm Secureboot: Enable
Unsupport Dev_Type
As you can see the product name is different now. But it is an i9300 as i confirmed on settings before upgrading (and on the battery slot).
I have tried with 2 or 3 differents firmwares and it keeps giving the same error.
Phone will not show Samsung Logo right now, it shows: Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again. Kies does not detect the phone, but the pc and odin does.
Please help.
If it's really a i9300 then it should just be a matter of flashing the right file.
Please try this german 4.3 ROM: http://goo.gl/aJMX7K
If it doesn't work find a threepart-firmware for i9300 (with PIT-file included) and flash it.
Still presenting the issue
Benko111 said:
If it's really a i9300 then it should just be a matter of flashing the right file.
Please try this german 4.3 ROM: LINK ABOVE..
If it doesn't work find a threepart-firmware for i9300 (with PIT-file included) and flash it.
Click to expand...
Click to collapse
Hi, thanks for your response! This was my destiny:
<ID:0/ 004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGMK6_I9300DBTGMK2_ I9300XXUGMK6_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> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot. img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On device:
Product name: sgh-i747 (Probably this is what is causing this issue, but it is a i9300)
Unsupport dev_type
I'll still look for more softwares !
re
Ovejox said:
Hi, thanks for your response! This was my destiny:
<ID:0/ 004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGMK6_I9300DBTGMK2_ I9300XXUGMK6_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> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot. img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On device:
Product name: sgh-i747 (Probably this is what is causing this issue, but it is a i9300)
Unsupport dev_type
I'll still look for more softwares !
Click to expand...
Click to collapse
Hi. Try chimera tools and flash rom.
I'm beginning to suspect you are on commission for chimera...
It looks like the op flashed a firmware for the i747, try the rescue firmware from general forum else a repair centre.
Sent from my GT-I9300 using Tapatalk
That would definitely be my next step as well. Try the 3-part rescue firmware with PIT.
What do you mean on device it says SGH-i747? Where on device, when it trys to boot? That's from the incorrectly flashed firmware but
should normally be overwritten by the correct firmware without problem.
Again, if you're positiv it really is a i9300 the rescue firmware should do:
http://direct.xda-developers.com/showpost.php?p=30087735
You do need to ensure you get the correct firmware and to do this you need Kies to work.
Uninstal Kies then download Kies and install again, download the 4.3 version, then start Kies go to tools and select the Firmware Upgrade and Installation, follow the instructions, hopefully for you it will see the phone, following the process should wipe the phone and install the correct firmware for it, once this is done the phone should boot up, after that you should have a working phone.
Seems very odd your phone shows i9300 in the About Phone and under the battery but not when you go into download mode it shows the US / Canada phone model.SGH-i747
Helo there XDA. I joined the site today because I have a difficult problem that I am working on.
I have the Verizon Galaxy S4 phone running Lollipop 5.0.1, build number I545VRUGOC1.
I have tried to root my phone using motochopper, towelroot, KingRoot, and many others with no luck. I have also tried to flash custom pre-rooted I545VRUGOC1 firmwares. Also no luck.
This is the consistent error that Odin throws me every time:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SCH-I545_MD2_423399_Kernel.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> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
After many attempts at installing custom firmwares, flashing roms, using rooting tools, etc, my phone now says:
Software Update Failed
With the information:
Code:
ODIN MODE
PRODUCT NAME: SCH-I545
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
REACTIVATION LOCK: OFF
CSB-CONFIG-LSB: 0x30
SECURE DOWNLOAD: ENABLE
WRITE PROTECTION: Enable
eMMC BURST MODE enabled
START [224, 1440]
SYS REV CHECK FAIL[K] : No Version
SECURE MAGICODE CHECK FAIL : boot
I just need to root my galaxy s4. I do not care whether my phone is lollipop, kitkat, whatever. If downgrading is what must be done to root then that is fine I just need to know what is going on.
Thanks,
Eveno
You could have saved all that time by doing a simple search first. There is no downgrading or rooting once you're on the factory OC1.
i have galaxy s3 the international model
right now it stucks on the logo. i can get into download mod, but not into recovery.
i've tried to flash stock version. i used first the one file method . didn't work, then i tried the 4 files method
with bootloader etc... but it failed again.
i changed cables, usb ports, nothing!
here's the odin log.
___________________
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXEMG4_I9300ITVEML2_I9300XXEMG4_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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
could it be an hardware issue. or theres still chance
thanks..
Check if it says "Custom" on "Current Binary"
This is probably a cause of half SDS(Sudden Death Syndrome),basically your device is dead
Dinkec27 said:
Check if it says "Custom" on "Current Binary"
This is probably a cause of half SDS(Sudden Death Syndrome),basically your device is dead[/Q
in download mode it says:
custom binary download: no
currnet binary: samsung official
system status: official
so maybe its not??
Click to expand...
Click to collapse
I think your device is dead
tyler6389 said:
I think your device is dead
Click to expand...
Click to collapse
i think too, but is there any last options i could try.. like flash it with pit files???