messed up my phone, need help.

magapower · Jul 25, 2015 8 0 0

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.

thisisapoorusernamechoice · Jul 25, 2015 at 3:15 PM

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.

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:

(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.

magapower · Jul 26, 2015

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?

tet1 · May 9, 2013 143 30 0

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

magapower · Jul 25, 2015 8 0 0

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.

Devo7v · Jul 26, 2015 at 3:29 PM

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.

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.

magapower · Jul 25, 2015 8 0 0

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.

I have been flashing with all 4. on various different Odin versions with different firmware versions.

Devo7v · Jul 26, 2015 at 10:49 PM

magapower said:
I have been flashing with all 4. on various different Odin versions with different firmware versions.

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.

magapower · Jul 25, 2015 8 0 0

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?

thisisapoorusernamechoice · Jul 27, 2015 at 3:04 AM

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?

Stop using ML2 and use the NE3 files I linked to

magapower · Jul 25, 2015 8 0 0

thisisapoorusernamechoice said:
Stop using ML2 and use the NE3 files I linked to

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 ****.

Devo7v · Jul 27, 2015 at 11:43 AM

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 ****.

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.

magapower · Jul 25, 2015 8 0 0

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)

Odin 3.09 (yes running admin)

Odin 3.07 (yes running admin)

Odin 3.06 (yes running admin)

Odin 3.04 (yes running in admin)

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.

magapower · Jul 25, 2015 8 0 0

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.

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.

Top Devices

New Devices

Topics

Search

messed up my phone, need help.

magapower

Member

thisisapoorusernamechoice

Senior Member

magapower

Member

tet1

Senior Member

magapower

Member

Devo7v

Senior Member

magapower

Member

Devo7v

Senior Member

magapower

Member

thisisapoorusernamechoice

Senior Member

magapower

Member

Devo7v

Senior Member

magapower

Member

magapower

Member

New posts