[Q] HELP I have Soft Bricked my SGS4 I337 - Android Q&A, Help & Troubleshooting

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

Related

Problem updating firmware 4.1.1 to 4.3

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

[Q] HELP: attempted to UNROOT,(soft)bricked my S4, doesnt boot shows Firmware E

WHAT:
I need some help fixing my Galaxy S4 SCH-i545, i have seemed to have (soft)bricked it, as i can still use the Volume (up/down), Home, and Power buttons to get into the ODIN Download Mode.
______
HOW:
Tried to UNROOT galaxy S4 via this method provided by galaxy4root wesbite titled "how to unroot galaxy s4 and remove root completely"
I mistakenly did not do the initial step prior to Step 1 of, "Also, Triangle Away app should support Galaxy S4 soon so you can reset your . binary counter. Run Triangle Away app BEFORE starting unrooting process." Not sure if this should have caused any problems as from what i know Triangle Away only reset the binary counter.
_______
I know i followed the other steps exactly as stated in the link, made sure i downloaded the correct firmware for my Galaxy,"Verizon Galaxy S4 SCH-i545 VRUAMDK (Android 4.2.2)", reinstalled the Samsung Driver, tried all USB ports (front and back).
When i get into ODIN Download Mode, I realized that my download screen has an extra line at the bottom:
ODIN MODE
PRODUCT NAME: SCH-I545
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0X0
KNOX WARRANTY VOID: 0X0
CSB-CONFIG-LSB: 0X30
WRITE PROTECTION: Enable
eMMC BURST MODE: enabled
As aforementioned I followed the galaxys4root method using ODIN3 Ver.1.85 with firmware (Android 4.2.2) files linked above, but I also tried to use the newer version of ODIN3 Ver.3.09 with this tar.md5 file foudn if you just download I545VRUEMK2_I545VZWEMK2_VZW.zip or androidfilehost website
After all that I still get this error no matter how i try flash any of the two files in ODIN i still get this error:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_I545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low_ship_MULTI_CERT.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> 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> 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>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
After this, my Galaxy S4 screen shows this (with top line and bottom two lines in red font):
ODIN MODE
PRODUCT NAME: SCH-I545
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0X0
KNOX WARRANTY VOID: 0X0
CSB-CONFIG-LSB: 0X30
WRITE PROTECTION: Enable
eMMC BURST MODE: Enable
START [224, 1440]
SW REV. CHECK FAIL : FUSED : 6 , BINARY : 5
Jessooca said:
Reflash the stock firmware in Odin, then boot into recovery and do a factory reset.
Update this after you do.
*If you need the .pit file here's a link to the 16GB...
Click to expand...
Click to collapse
Thanks!
But i have never used a .pit file before, so I am assuming on ODIN just upload the .pit file the to the corresponding PIT section under "Re-Partition".
Question, do I keep ONLY "Auto Reboot" and "F. Reset Time" AND "RE-PARTITION"check and the rest blank?
Jessooca said:
yep in the pit area at the top of odin add it then add the stock .md5 or tar file in the "pda" section and all 3 checked are fine. As loading the pit file will check the repartition box.
Click to expand...
Click to collapse
So i did that exactly, and ended up failing.
I got this:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUEMK2_I545VZWEMK2_I545VRUEMK2_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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Jessooca said:
Go into recovery do a factory reset, then pull the battery, go into download mode and reflash the stock firmware via Odin without the pit file and uncheck repartition.
You'll be good to go then.
Click to expand...
Click to collapse
i might have not mentioned this earlier, sorry about that. But the only two screens i can load on my S4 are the ODIN Download Mode and this error screen and an error screen that says “Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again“...
so i cant get into recovery mode
*********UPDATE: i tried to enter recovery mode and it just booted my S4 normally, all my data is still there, nothing was wiped. Just as it was prior to me doing anything to it...weird..
so how the PIT file helped, yet it still showed it failed in the Message on ODIN.
Jessooca said:
Make sure If you're on android 4.4 you only use the 4.4 md5 file or it will fail... do this:
Add your tar or md5 to Odin, then add THIS pit (different one then I gave you earlier)
...
Make sure all 3 are checked (including repartition)
Now let me know how it goes, IF that doesn't work this time then .....
Download this: ....
Then flash it in Odin.
take the time to download that and flash it instead of the one you're using. Also use the pit file Surge has included in that zip and make sure repartition IS checked.
Get back to me later after you're done! As long as you can get into Odin we can fix it.
---------- Post added at 07:10 PM ---------- Previous post was at 07:04 PM ----------
So holding down Volume UP & HOME then pressing power until you see a "blue line" pop up at the top then let go of power only {keep holding Volume UP & Home}... You should boot into stock recovery
Click to expand...
Click to collapse
you are a goddess at this! serisouly, thank you!
all of this helped incredibly! i got it to work and all is good. thanks again!

Galaxy S6: Bricked After Trying To Install Xposed

Pretty sure i bricked this to no repair.
So got my Sprint s6 edge few months ago and rooted it a week after. Sadly i dont know what i used rom wise to root it since its been a month+. Sadly i reformated pc awhile back so can't see the files i used.
Got bored and wanted to try and install xposed to add some new features to my phone. So just tried and i'm prety sure i bricked it hard...
what i followed
gs6.wonderhowto.com/how-to/install-xposed-framework-your-samsung-galaxy-s6-s6-edge-0163918/
It said make a recovery so i did by following
gs6.wonderhowto.com/how-to/install-custom-recovery-your-galaxy-s6-s6-edge-0161619/
I did what he did and after it asked for a reboot i rebooted and it got stuck on samsung boot logo saying "Recovery not SEANDROID Enforcing" in top left corner.
So i googled how to remove root and how to get past this screen and many suggested stock rom. I tried that and odin (v3.09) wont get past "Write NAND!"
I let it set for 20 minutes and nothing happened so i googled and everyone claimed trying different usb hubs and cables so i did that. I've tried every usb hub on my pc(8) and all 3 cables i had. So then tried different version v3.10.7 of odin and it fails with following
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<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> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And in top right under Odin mode it reads
Product Name: SM-G295P
Current binary: Custom
System Status: Custom
FRP Lock: OFF
Secure Download: Enabled
Knox warranty void: 1 (0x0301)
RP SWREV: B:3 K:2 S:2
SW REV. CHECK FAIL. DEVICE: 3, BINARY: 1
So now i'm just lost and scared at what to do. I googled "SW REV. CHECK FAIL. DEVICE: 3, BINARY: 1" And my findings are just to use stock rom...but thats what i did in first place. So now i'm stuck with a phone that is continuously rebooting itself to the samsung boot logo....
G925PVPU1AOCF_G925PSPT1AOCF_G925PVPU1AOCF_HOME.tar.md5 is the rom im trying to flash with and i believe it is stock because got it off this forum from a post claiming it was the new stock updated rom.
Can someone please help? I can skype or teamspeak or ventrilo or just use this forum to help me but i'm beyond confused on what to do now...
edit- phone is continuously rebooting itself to the samsung boot logo...but i managed to make it stop by making phone sit in download mode...
edit2- i can not go into recovery or safe mode. All i can do is wtach my phone go to the boot logo "Samsung Galaxy S6 Edge" screen then to black screen back to boot screen. And i can put it into download mode.... Thats it...The brick is real...
edit 3- 40 views and not one help lol, seems i'll be craigslist shopping soon.
You tripped the Knox counter, that is for sure. Since you can enter download mode that means it is still possible to install the stock firmware. Did you use the correct firmware for your model?
Snowby123 said:
You tripped the Knox counter, that is for sure. Since you can enter download mode that means it is still possible to install the stock firmware. Did you use the correct firmware for your model?
Click to expand...
Click to collapse
I'm pretty sure
SPR-G925PVPU1AOCF-20150415164450
forum.xda-developers.com/sprint-galaxy-s6-edge/general/sm-g925p-firmware-available-t3084414
Is the stock rom i used to try and fix that recovery screwup.
i tried G925PVPU3BOJ7_G925PSPT3BOJ7_G925PVPU3BOJ7_HOME.tar which is a 5.1.1 stock rom and still same results!!!
Try performing a log cat. That is a low skill technique of diagnosing problems in android during a boot loop.
Snowby123 said:
Try performing a log cat. That is a low skill technique of diagnosing problems in android during a boot loop.
Click to expand...
Click to collapse
I dont know how or what a log cat is.
Edit- just turned device back on and plugged itno computer and now blue screen saying An error occured while updating the device software. use emergency function in the smart switch pc software. Yet the smart switch software says unsupported device.
randomly got it to work after 2 hours of leaving it alone i can now start to install the stock firmware but it stops
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin engine v(ID:3.1100)..
<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> sboot.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> cm.bin
<ID:0/007> boot.img
<ID:0/007> recovery.img
<ID:0/007> system.img
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/007> Removed!!
i dk if phone not charged enough or what
edit---
It fails on same part, but progress bar is sometimes farther. Tried it 3 times in total, just going to put phone on charger(wall outlet) for a few hours then try again
also sorry for double posting...

Galaxy Tab E sm-t77p (Sprint) Smells like brick

I hope I am in the right section the structure of the forum seems to have changed on me or something.
I have gotten frustrated at this point and do not even remember the entire process that has got me this far.
I am not new to rooting as I have rooted maybe 10+ phones all using the xda forum. I just do not trust any other site. This does not mean I am claiming to be a pro. I just know how to follow directions and always try to have a backup before I even get started.
Anywho to the best of my recollection I started with this guide: [ROOT][Samsung Galaxy Tab E][sm-t377p/sm-t560nu]
When I started root I had Marsh 6.0.1
I don't think I ended up rooting using that exact method, or if i did the tablet wouldn't start up but it had twrp.
Somewhere in between my tablet had twrp and I used the backup that was given by @shawn1976 for the system, boot and modem.
The tablet worked but the wifi was refusing to turn on. I searched and searched and couldn't fix the problem and so I think at that point I decided to try and maybe flash the 6.0.1 that it had originally had on it and worse case scenario I would just end up where I started nothing lost.
Anyhow at this point I have TWRP 2.8.7.0 and it gives error that zip file is corrupt on the 6.0.1.
and using odin it just gives:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<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)
When I try to restore the @shawn1976 Backup now it doesn't show anything in the list below [ Select Partitions to Restore] list.
when i first started i took note of the OEM Unlocking steps and made sure it was on, but am wondering now after it got reflashed was I supposed to redo that step again before trying to reflash?
I have no backup and I'm wondering what to do at this point. I tried looking for a solution hoping I could avoid posting like a nub about my problems. Any help you guys could give me would be appreciated.
so brief description is:
Galaxy Tab E sm-t377p (sprint)
Tablet doesn't boot up just goes straight to recovery.
TWRP is 2.8.7.0
And no partitions show up for restore in twrp for what was supposed to be my backup @shawn1976's Backup )
is it fixable?
In download mode it says:
ODIN MODE
PRODUCT NAME: SM-T377P
CURRENT BINARY: Custom
FRP LOCK: OFF
WARRANTY VOID: 0x1 (2)
QUALCOM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, H1, R1, A2, P1
SECURE DOWNLOAD : ENABLE
S8Gonzo said:
In download mode it says:
ODIN MODE
PRODUCT NAME: SM-T377P
CURRENT BINARY: Custom
FRP LOCK: OFF
WARRANTY VOID: 0x1 (2)
QUALCOM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, H1, R1, A2, P1
SECURE DOWNLOAD : ENABLE
Click to expand...
Click to collapse
If you have the T377P use the firmware from SamMobile to unbrick your device.
https://www.sammobile.com/firmwares/database/SM-T377P/
I tried downloading it twice and twrp doesnt like it. It errors with [ zip file is corrupt] or just restarts twrp.
I'll try a 3rd download.
I have a twrp version 3 in my device which is running on android 5.1.1
I think the problem is with your recovery , 2.8.7.0 is too old to run new binaries maybe?
Try installing latest version of Philz for your device.
Happened with me before when i had a mtk kitkat device and when i tried to install a lollipop rom using an old twrp recovery.
Fixed it by upgrading to traditional cwm-philz
S8Gonzo said:
I tried downloading it twice and twrp doesnt like it. It errors with [ zip file is corrupt] or just restarts twrp.
I'll try a 3rd download.
Click to expand...
Click to collapse
That's because you need to unzip it and flash the md5 with odin not twrp.
ashyx said:
That's because you need to unzip it and flash the md5 with odin not twrp.
Click to expand...
Click to collapse
They were all giving me errors. The flash image with odin and the twrp backup. After a bunch of troubleshooting it turns out my microSD card was the problem. It started giving me errors in windows so i reformatted and put all the files back. Then I reflashed the twrp backup and its able to boot up.
The problem is back to wifi switch flipping off as soon as i turn on. Im guessing it doesnt like the modem flash.
I keep trying to download a diff version of stock rom but I can't keep connected. It's a poopy line i have.
anywho I tried to install the stock rom I did manage to download and I get:
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1100)..
<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> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I tried a few versions of odin, same result.
Please help me, i have a hard bricked SM-T377P, if you have one in hands you can help me to unbrick mine, it will take only 2 minutes! Here is my thread: https://forum.xda-developers.com/android/development/help-sm-t377p-hard-bricked-debrick-img-t3711889
Thankssssssss!
can I hide tethering with out root on this device

Samsung I337 AT&T" Firmware upgrade encountered an issue need solution

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.

Categories

Resources