softbricked at&t galaxy s5 - AT&T Samsung Galaxy S 5

my sisters s5 was in the process of updating and failed. it's now stuck in a boot loop saying a custom rom installed and there hasn't been. only on mine anywyays im getting these error messages when i go to flash the stock firmware and im not sure what they mean or what im doing wrong.

jondabomb541 said:
my sisters s5 was in the process of updating and failed. it's now stuck in a boot loop saying a custom rom installed and there hasn't been. only on mine anywyays im getting these error messages when i go to flash the stock firmware and im not sure what they mean or what im doing wrong.
Click to expand...
Click to collapse
this is the phone screen

jondabomb541 said:
this is the phone screen
Click to expand...
Click to collapse
What stock firmware did you try to flash?

shortydoggg said:
What stock firmware did you try to flash?
Click to expand...
Click to collapse
G900AUCU1ANCE_G900AATT1ANCE_ATT\G900AUCU1ANCE_G900AATT1ANCE_G900AUCU1ANCE_HOME.tar.md5

jondabomb541 said:
G900AUCU1ANCE_G900AATT1ANCE_ATT\G900AUCU1ANCE_G900AATT1ANCE_G900AUCU1ANCE_HOME.tar.md5
Click to expand...
Click to collapse
That's the wrong file to flash to that phone.
I suggest you try the OI5 part of this guide, first since she wants the update.
http://forum.xda-developers.com/showthread.php?t=2785185

shortydoggg said:
That's the wrong file to flash to that phone.
I suggest you try the OI5 part of this guide, first since she wants the update.
http://forum.xda-developers.com/showthread.php?t=2785185
Click to expand...
Click to collapse
<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..
<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..
<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..
<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..
<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> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
<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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<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> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
It gets stuck right here, which is normal but it's been here for an hour. should i try a different file?

I'd say start over, but this time do not flash the BL file. Do the AP, CP, and CSC files only.

Related

Little problem with ezbase

I try to update my android software back to froyo (2.2) using the ezbase, but the installiation freezes at:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> EZbase-PDA-XWJS3.tar.md5 is valid.
<OSM> EZbase-PHONE-XXJVE.tar.md5 is valid.
<OSM> EZbase-CSC-XXJV1.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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
whta i´m gonna do now??
huuuh, i already got it
lmao, just fyi, what I did last time that happened to me was to just pull the cable out, restart back to download mode, and things should be working like normal

messed up my phone, need help.

it's an sgh-i537
I'm not experienced in this sort of stuff, but I think my phone is considered "soft bricked"
I can boot it into recovery mode/download mode, but when I go into download mode, odin wont recognize it.
on top of that, when/if I am able to get it to recognize my phone, to my understanding I need to know what MF# I'm running- and I have absolutely no clue what that is. A bit of reading leads me to believe it means Manifest or something like that, but I still have no clue what one I have.
please help an idiot.
magapower said:
it's an sgh-i537
I'm not experienced in this sort of stuff, but I think my phone is considered "soft bricked"
I can boot it into recovery mode/download mode, but when I go into download mode, odin wont recognize it.
on top of that, when/if I am able to get it to recognize my phone, to my understanding I need to know what MF# I'm running- and I have absolutely no clue what that is. A bit of reading leads me to believe it means Manifest or something like that, but I still have no clue what one I have.
please help an idiot.
Click to expand...
Click to collapse
What you're referring to as MF# is actually the last three characters in the firmware build number, which we use to differentiate between different firmware builds. To fix your phone, you have to use Odin v3.09 to restore a stock firmware. Download this file and extract all 4 files within. You have to use all 4 files in Odin, it'll look like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(I know the picture has Odin v3.07 but I've always had success with 3.09). The process will take some time, you must be patient and let it do its thing. When you do this, your phone will automatically reboot on its own a couple times, and one of those times will be to the stock android recovery. This is completely normal. I say this because I've seen so many people freak out when their phone starts doing stuff on its own. Just let Odin go, it knows what it's doing.
I finally got odin to recognize my phone, and I used files you linked to and the top left box turned red and said "Fail!"
In the Messages box...
<ID>:0/003>Initialization..
<ID>:0/003>Set PIT file..
<ID>:0/003>DO NOT TURN OFF TARGET!!
<ID>:0/003>Complete(write) operation failed.
<OSM> All Threads completed. (succeed 0 / failed 1)
<ID>:0/003> Removed!!
<ID>:0/003>Added!!
I would just post a picture, but I'm a new user.
edit:
tried using odin 3.07 and just the AP file, I noticed it added something in the messages...
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_I537UCUBML2_2244695_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> Get PIT for mapping..
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
I'm looking at that "There is no PIT partition... thoughts on that?
What android you had after softbrick ... because that file ML2 Firmware is Jellybean if your system kitkat you can't go back to Jellybean or if your System lollipop you can't go back to Kitkat make sure what android is you current system puls check your usb cable.. notes.. if you used to be on lollipop and software brick there's no Lollipop file Odin flash file available on xda only available jellybean and kitkat.. you need to take your phone to best buy you will see Samsung section just tell them I want to flash my phone they will help you ....
Sent from my SAMSUNG-SGH-I537 using XDA Free mobile app
---------- Post added at 10:06 AM ---------- Previous post was at 10:03 AM ----------
Check your usb cable and flash kitkat 4.4.2 Odin files if is failing take your phone to best buy and flash lollipop
Sent from my SAMSUNG-SGH-I537 using XDA Free mobile app
I believe It was 4.2.2 Jellybean. (with AT&T)
I tried to update it to lollipop when this started.
I'm still looking into the whole PIT thing, and even found a download for a PIT file for the i537 but haven't done anything with it yet because stuff I've read say thats more for the development stuff and could really mess up your phone.
magapower said:
I believe It was 4.2.2 Jellybean. (with AT&T)
I tried to update it to lollipop when this started.
I'm still looking into the whole PIT thing, and even found a download for a PIT file for the i537 but haven't done anything with it yet because stuff I've read say thats more for the development stuff and could really mess up your phone.
Click to expand...
Click to collapse
You are flashing the wrong Odin file. You need to flash the files that @thisisapoorusernamechoice linked to. You should be flashing all 4 files at once otherwise you're going to end up with a phone that doesn't work properly.
Devo7v said:
You are flashing the wrong Odin file. You need to flash the files that @thisisapoorusernamechoice linked to. You should be flashing all 4 files at once otherwise you're going to end up with a phone that doesn't work properly.
Click to expand...
Click to collapse
I have been flashing with all 4. on various different Odin versions with different firmware versions.
magapower said:
I have been flashing with all 4. on various different Odin versions with different firmware versions.
Click to expand...
Click to collapse
As was mentioned before, it looks like you're flashing the wrong files. You've flashed ML2 firmware which is why it fails to flash all 4 files. You need to be flashing all 4 NE3 files.
alright, a little headway... I tried all 4 files on odin 3.10 and got further...
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_I537UCUBML2_2244695_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_I537UCUBML2_2244695_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CP_I537UCUBML2_2244695_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_ATT_I537ATTBML2_2244695_REV06_user_low_ship_MULTI_CERT.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> 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
at the moment my phone is still plugged in and odin is just hanging on aboot.
thoughts?
magapower said:
alright, a little headway... I tried all 4 files on odin 3.10 and got further...
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_I537UCUBML2_2244695_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_I537UCUBML2_2244695_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CP_I537UCUBML2_2244695_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_ATT_I537ATTBML2_2244695_REV06_user_low_ship_MULTI_CERT.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> 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
at the moment my phone is still plugged in and odin is just hanging on aboot.
thoughts?
Click to expand...
Click to collapse
Stop using ML2 and use the NE3 files I linked to
thisisapoorusernamechoice said:
Stop using ML2 and use the NE3 files I linked to
Click to expand...
Click to collapse
I tried them, with odin 3.04, 3.06, 3.07, 3.09 and 3.10 and it kept failing right away.
also now the other files aren't getting as far as they did before.
also minor development- for the first time, when I tried to go into download mode, it popped up the "Firmware upgrade encounter an issue. please select recovery mode in kies and try again" screen.
aaaand now even the files that looked like they might work aren't doing ****.
magapower said:
I tried them, with odin 3.04, 3.06, 3.07, 3.09 and 3.10 and it kept failing right away.
also now the other files aren't getting as far as they did before.
also minor development- for the first time, when I tried to go into download mode, it popped up the "Firmware upgrade encounter an issue. please select recovery mode in kies and try again" screen.
aaaand now even the files that looked like they might work aren't doing ****.
Click to expand...
Click to collapse
You're flashing the wrong files. The only way you're going to get this to work is if you flash the NE3 files. You have to make them work. Try downloading it again and check the MD5 to make sure you didn't get a corrupted download.
alright, just put it to rest, I am using the files I was linked to, I did check the md5.
I tried all the following just a few minutes ago
Odin 3.10 (yes running as admin)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_I537UCUCNE3_987011_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_I537UCUCNE3_987011_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CP_I537UCUCNE3_987011_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_ATT_I537ATTCNE3_987011_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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
Odin 3.09 (yes running admin)
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_I537UCUCNE3_987011_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_I537UCUCNE3_987011_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CP_I537UCUCNE3_987011_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_ATT_I537ATTCNE3_987011_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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
Odin 3.07 (yes running admin)
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_I537UCUCNE3_987011_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_I537UCUCNE3_987011_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CP_I537UCUCNE3_987011_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_ATT_I537ATTCNE3_987011_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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
Odin 3.06 (yes running admin)
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_I537UCUCNE3_987011_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_I537UCUCNE3_987011_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CP_I537UCUCNE3_987011_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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
Odin 3.04 (yes running in admin)
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_I537UCUCNE3_987011_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> AP_I537UCUCNE3_987011_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> CP_I537UCUCNE3_987011_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> CSC_ATT_I537ATTCNE3_987011_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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
I'm wondering if I should try harder using Kies? I can't get kies to connect to my phone (it just hangs on the connecting screen), and when I try to manually input my phone (where you put in the model and S/N), it gives me the message saying that my phone can't be verified.
update to this:
after leaving the phone alone for a week, I decided to give it another go and was somewhat successful I think. This is what happened.
<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> BL_I537UCUCNE3_987011_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_I537UCUCNE3_987011_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CP_I537UCUCNE3_987011_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_ATT_I537ATTCNE3_987011_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> 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> persdata.img.ext4
<ID:0/003> system.img.ext4
<ID:0/003> modem.bin
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> NON-HLOS.bin
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> cache.img.ext4
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
now instead of automatically booting to the "connect to keis" screen, it goes to the Samsung S4 active screen and just hangs there.
I can still enter download mode.
Doesn't seem like I can ever recovery mode though. any thoughts on how to progress?
Thanks.

S6 Edge Not Downgrading

Hi! I have the S6 Edge AT&T. I currently have it on the latest firmware 5.1.1 and when I try to flash the stock rom/firmware I always get an error message. Why is that?
<ID:0/004> 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..
<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..
<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..
<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> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can't downgrade bro you're stuck on 5.1.1 I'm afraid
Sent from my SAMSUNG-SM-G925A using Tapatalk
Once you're on 5.1.1 you can not downgrade. Sucks, we'll be stuck on it for a while. I upgraded for Samsung Pay and sacrificed my root.
What if it did not finishing installing all the way. can you down grade then
nope. bootloader is the first thing flashed. that is whats keeping you from downgrading. Your stuck. Just like us.
updates?
Any updates? :/

Got locked out. S6 AT&T 64gb SM-G920A - Bricked

Tried to flash with a wrong .tar file im pretty sure. Now the phone will not get past the message telling me to restore it with smart switch. (from what i can tell smart switch doesnt currently work with the att version of this s6).
tried using these files:
AP_G920AUCU1AOE2_CL4823236_QB4834510_REV02_user_low_ship.tar.md5
BL_G920AUCU1AOE2_CL4823236_QB4834510_REV02_user_low_ship.tar.md5
CP_G920AUCU1AOE2_CL4823236_QB4834510_REV02_user_low_ship.tar.md5
CSC_ATT_G920AATT1AOE2_CL4823236_QB4834510_REV02_user_low_ship.tar.md5
ODin v3.10.7 gives me this:
<ID:0/003> 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..
<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..
<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..
<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/003> Odin engine v(ID:3.1100)..
<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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
also, i am on a retina mbp with vmware running odin on both windows and mac sides attempting this.
turns out these files corrected my issue:
couldnt post link directly so i had to make it all weird: remove spaces (clearly lol)
download1334.
mediafire .
com
/
uiye5aii38zg
/c9xr4ti8x7xwq5x/G920AUCU3BOI2_User_Binary.zip

Please help!!! My phone is not working right now! Please help!

I tried to root my phone today and I failed and my phone is not working right now. Does anybody know how to fix it? Can someone please help me? Please!!! Thank you so much.
hxsports said:
I tried to root my phone today and I failed and my phone is not working right now. Does anybody know how to fix it? Can someone please help me? Please!!! Thank you so much.
Click to expand...
Click to collapse
My phone current is look like this. And I tried Odin flash and the process is failed.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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/004> Odin engine v(ID:3.1401)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 332 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> abl.elf
<ID:0/004> xbl.elf
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
hxsports said:
My phone current is look like this. And I tried Odin flash and the process is failed.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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/004> Odin engine v(ID:3.1401)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 332 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> abl.elf
<ID:0/004> xbl.elf
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
My phone stuck in Download mode right now and it shows
partition vbmeta
Reason vbmeta: Error verifying vbmeta image:
0_0INDIVLDUMT_EDRHS_IMTHSGAUEMSAC
if your phone won't boot because of verified boot, either flash back to stock or flash vbmeta_disabled.tar
if you tried to patch your boot.img this wouldn't really be a problem because magisk patches vbmeta for you when you patch.
if you tried to flash a magisk zip you should have followed instructions for twrp which requires flashing vbmeta_disable.tar in Odin. in other words you couldn't have followed instructions.
hxsports said:
I tried to root my phone today and I failed and my phone is not working right now. Does anybody know how to fix it? Can someone please help me? Please!!! Thank you so much.
Click to expand...
Click to collapse
bootloader is locked!! You got a US phone version, you can not Root neither install a custom Rom or TWRP.
Download the last official Rom for your phone, and flash it through Odin. Then your phone will work again.
3mel said:
if your phone won't boot because of verified boot, either flash back to stock or flash vbmeta_disabled.tar
if you tried to patch your boot.img this wouldn't really be a problem because magisk patches vbmeta for you when you patch.
if you tried to flash a magisk zip you should have followed instructions for twrp which requires flashing vbmeta_disable.tar in Odin. in other words you couldn't have followed instructions.
Click to expand...
Click to collapse
I can't flash anything into it because it say OEM lock and
hxsports said:
I can't flash anything into it because it say OEM lock and
Click to expand...
Click to collapse
flash the correct stock firmware for your phone and nothing else. if you have an American FE there's NOTHING ELSE that will work on it.
3mel said:
flash the correct stock firmware for your phone and nothing else. if you have an American FE there's NOTHING ELSE that will work on it.
Click to expand...
Click to collapse
Correct. There are sites, from where you may download the last available firmware for your phone!
Download it and flash it correctly with Odin, and it will work.
Download SM-G781U1 / Galaxy S20 Fan Edition 5G SM-G781U1 XAA in Samfw - Samsung firmware download
SM-G781U1 / Galaxy S20 Fan Edition 5G SM-G781U1 XAA samsung firmware download all model, lastest, fast update, completely free and fast speed in Samfw.com ✅
samfw.com
Download the latest one for US version for this phone, currently they jumped to bootloader v.7
Carreful, I gave you a link for S20 FE 5G !! If you got S20 FE 4G, download the adequate one.

Categories

Resources