Database Users

Data isn't working after Factory Reset!

Hey there guys, I have the i337M Galaxy S4 (since then it has been changed to i9505), but I recently had enough of flashing roms and chose to go back to stock touchwiz firmware. I downloaded the right firmware for my device, and I tried flashing it with odin. When the flashing was done, the odin onscreen said "pass!", however, when my phone rebooted, it was still on the old rom, and nothing has changed. I tried a different computer, a different cable, everything, and I am very sure it's an issue with the phone.
I don't know why it does this, but now I have seen when after it reboots, it reboots into stock recovery, and there is a green bar that moves with the green android above it, but once the green bar reachs halfway, the phone reboots and it remains the same, as if there was no stock rom flashed onto it. I flashed a custom rom (CM11) through custom recovery, and then I used odin to flash stock rom. It seemed to work, but the bootscreen got stuck on the samsung logo(the samsung logo was just pulsing).
This is what it says on ODIN (When I flash the Official 4.3 Samsung update for I337M):
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUEMK6_I337MOYAEMK6_I337MVLUEMK6_HOME.tar.md 5 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> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> NON-HLOS.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> aboot.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Funny thing is, I restored a backup I had, and the data works fine with that (rooted touchwiz backup). However, as soon as I try to factory restore it through the phone, it completes, but data stops working. The same issue happens with ODIN as described above if I am on the restored ROM.
Please help me!

victoriousbig said:
Hey there guys, I have the i337M Galaxy S4 (since then it has been changed to i9505), but I recently had enough of flashing roms and chose to go back to stock touchwiz firmware. I downloaded the right firmware for my device, and I tried flashing it with odin. When the flashing was done, the odin onscreen said "pass!", however, when my phone rebooted, it was still on the old rom, and nothing has changed. I tried a different computer, a different cable, everything, and I am very sure it's an issue with the phone.
I don't know why it does this, but now I have seen when after it reboots, it reboots into stock recovery, and there is a green bar that moves with the green android above it, but once the green bar reachs halfway, the phone reboots and it remains the same, as if there was no stock rom flashed onto it. I flashed a custom rom (CM11) through custom recovery, and then I used odin to flash stock rom. It seemed to work, but the bootscreen got stuck on the samsung logo(the samsung logo was just pulsing).
This is what it says on ODIN:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUEMK6_I337MOYAEMK6_I337MVLUEMK6_HOME.tar.md 5 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> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> NON-HLOS.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> aboot.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Funny thing is, I restored a backup I had, and the data works fine with that (rooted touchwiz backup). However, as soon as I try to factory restore it through the phone, it completes, but data stops working. The same issue happens with ODIN as described above if I am on the restored ROM.
Please help me!
Click to expand...
Click to collapse
are your apn settings intact?

aandrichaci said:
are your apn settings intact?
Click to expand...
Click to collapse
Yes they are

aandrichaci said:
are your apn settings intact?
Click to expand...
Click to collapse
Ok so it turned out to be that the APN settings were messed up lol, but I still don't understand why they get wiped after each factory reset, AND why when I try flashing with ODIN, nothing changes...

victoriousbig said:
Ok so it turned out to be that the APN settings were messed up lol, but I still don't understand why they get wiped after each factory reset, AND why when I try flashing with ODIN, nothing changes...
Click to expand...
Click to collapse
So did that fix the issue?

MrKhozam said:
So did that fix the issue?
Click to expand...
Click to collapse
It fixes the issue, but I would like to know why the APN settings get wiped after a factory restore? Just curious lol, I know they can be put in manually, but before this they would automatically be there. It's a minor frustration

victoriousbig said:
It fixes the issue, but I would like to know why the APN settings get wiped after a factory restore? Just curious lol, I know they can be put in manually, but before this they would automatically be there. It's a minor frustration
Click to expand...
Click to collapse
It seems to be a carrier-specific issue. Might have something to do with frequency. I know that when I sold my old S3, which was an original factory unlocked phone from T-Mobile, detected my APN settings fine on the Bell network here in Canada. However, when I put in a Wind SIM (same frequency as T-Mobile), I needed to re-configure the APN settings. Which is a bit ironic, if anything.

[Q] soft bricked i9505, odin keeps failing

hello everyone
i rooted my s4 a while back, then unrooted by flashing XSA-I9505XXUEMK9-20131212101727 through odin
then i decided to root it again, it worked but this time the wifi stopped working so i flashed XSA-I9505XXUEMK9-20131212101727 (same firmware) again, except everytime i do it, odin gives me a fail
i used a pit file to flash with XSA-I9505XXUEMK9-20131212101727 (same firmware again), except during the middle of this process, the connection between my cable and phone broke
tried pit + XSA-I9505XXUEMK9-20131212101727 (same thing) on odin 3.09 after the first attempt, it gives me a fail and this
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUEMK9_I9505XSAEMK3_I9505XXUEMK9_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> 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> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004> tz.mbn
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> NON-HLOS.bin
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
right now, when i try to boot my phone, it gives me "firmware upgrade encountered an issue. please select recovery mode in kies and try again", though i can't do anything in kies
all i can access is download mode, recovery mode doesn't work either (it never did, even when my phone was fine)
please help

chilifourloko said:
hello everyone
i rooted my s4 a while back, then unrooted by flashing XSA-I9505XXUEMK9-20131212101727 through odin
then i decided to root it again, it worked but this time the wifi stopped working so i flashed XSA-I9505XXUEMK9-20131212101727 (same firmware) again, except everytime i do it, odin gives me a fail
i used a pit file to flash with XSA-I9505XXUEMK9-20131212101727 (same firmware again), except during the middle of this process, the connection between my cable and phone broke
tried pit + XSA-I9505XXUEMK9-20131212101727 (same thing) on odin 3.09 after the first attempt, it gives me a fail and this
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUEMK9_I9505XSAEMK3_I9505XXUEMK9_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> 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> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004> tz.mbn
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> NON-HLOS.bin
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
right now, when i try to boot my phone, it gives me "firmware upgrade encountered an issue. please select recovery mode in kies and try again", though i can't do anything in kies
all i can access is download mode, recovery mode doesn't work either (it never did, even when my phone was fine)
please help
Click to expand...
Click to collapse
Although this message your phone is in download mode
change usb port and try again
try different port

Fixed it somehow........
actually disregard all that, i flashed the pit file by itself in odin 3.09 and everything works again O_O
i'm missing an app which is weird...

i still can't reflash XSA-I9505XXUEMK9-20131212101727 through odin though, it still gives me a fail, which ends up ruining everything again, so i reflash the pit and now this happens
i did a factory reset, now samsung keyboard keeps crashing and the menu and back button do nothing
wth is happening ._.

chilifourloko said:
i still can't reflash XSA-I9505XXUEMK9-20131212101727 through odin though, it still gives me a fail, which ends up ruining everything again, so i reflash the pit and now this happens
i did a factory reset, now samsung keyboard keeps crashing and the menu and back button do nothing
wth is happening ._.
Click to expand...
Click to collapse
maybe wrong or corrupt firmware file try another

pda4g said:
maybe wrong or corrupt firmware file try another
Click to expand...
Click to collapse
which firmware should i use
does it matter ?

chilifourloko said:
which firmware should i use
does it matter ?
Click to expand...
Click to collapse
download firmware for your country
Your file may be damaged
download new

pda4g said:
download firmware for your country
Your file may be damaged
download new
Click to expand...
Click to collapse
redownloaded firmware, stopped antivirus and all kies processes, changed usb ports to one of the back ones, reflashed firmware from ~80 percent battery aaaaaaaaaaaaand...
IT WORKS !!!!!!!!!!!!!!!!!!!!!!!!!!!!
HALLELUJAH

chilifourloko said:
redownloaded firmware, stopped antivirus and all kies processes, changed usb ports to one of the back ones, reflashed firmware from ~80 percent battery aaaaaaaaaaaaand...
IT WORKS !!!!!!!!!!!!!!!!!!!!!!!!!!!!
HALLELUJAH
Click to expand...
Click to collapse
ok Good luck!

Want to root on 4.2.2 MDL

A long time ago I sent my phone in for repairs (screen). I factory reset it and lost root. I don't even remember how I rooted it, it was an automated tool. After it came back from repairs, it still had 4.2.2 and MDL (it was a repair shop not Samsung).
Whenever I reset/turn phone off and back on, I get an error about com.android something, but only then, it works normally after. Due to this error, my phone tries to upgrade but fails (thankfully). I want to root my phone but I'm afraid it will fail because of that error. What exactly should I do next? I asked in another thread and I was told Motochopper was the best tool to root on 4.2.2. I just want to get rid of this error then root, that's it, what should I do next?

Moto chopper should work. I'm guessing towelroot would too. https://towelroot.com
Sent from my Nexus 5 using XDA Free mobile app

But do you think I can just use it the way my phone is now? Someone told me to do a Factory Reset with Odin, but I have no idea how to do that. All the tutorials I find mention downloading something (apart from Odin itself), why would I need to do that if I'm just resetting?
This is the error I get "com.android.phone has stopped working".
I think I've already tried factory resetting with the physical buttons method and I still keep getting that.

SRCP said:
But do you think I can just use it the way my phone is now? Someone told me to do a Factory Reset with Odin, but I have no idea how to do that. All the tutorials I find mention downloading something (apart from Odin itself), why would I need to do that if I'm just resetting?
This is the error I get "com.android.phone has stopped working".
I think I've already tried factory resetting with the physical buttons method and I still keep getting that.
Click to expand...
Click to collapse
Odin flashes the factory firmware, it does a lot more than a factory reset. You need to download the mdl firmware and flash that in Odin. You can get it at sammobile.com. It's a zip file, you need to extract it using 7-zip or win rar. After it's extracted you end up with a .tar.md5 file. That's what you use in Odin.
If you do flash it, the phone will want to update via the ota. You should make sure it doesn't do that by rooting it and freezing out deleting the update apps. There are three files and I don't remember their names
Edit, read this http://forum.xda-developers.com/showthread.php?p=42320391
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Odin flashes the factory firmware, it does a lot more than a factory reset. You need to download the mdl firmware and flash that in Odin. You can get it at sammobile.com. It's a zip file, you need to extract it using 7-zip or win rar. After it's extracted you end up with a .tar.md5 file. That's what you use in Odin.
If you do flash it, the phone will want to update via the ota. You should make sure it doesn't do that by rooting it and freezing out deleting the update apps. There are three files and I don't remember their names
Edit, read this http://forum.xda-developers.com/showthread.php?p=42320391
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thank you. Last question. Do you think I should flash first or try to root right away?

SRCP said:
Thank you. Last question. Do you think I should flash first or try to root right away?
Click to expand...
Click to collapse
Rooting isn't going to do you any good at this point. Flash first
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Rooting isn't going to do you any good at this point. Flash first
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks.

jd1639 said:
Rooting isn't going to do you any good at this point. Flash first
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Odin failed.
<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> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> tz.mbn
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!
What next? I'm trying to find more info.

SRCP said:
Odin failed.
<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> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> tz.mbn
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!
What next? I'm trying to find more info.
Click to expand...
Click to collapse
This looks bad. The blue bar on phone moved a bit then stopped and it's stuck there. I tried Odin again and now I get this:
<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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!

Try a different port on the PC. Use one that is attached to the motherboard. Usually the USB ports on the back of the PC. Then try again

RockRatt said:
Try a different port on the PC. Use one that is attached to the motherboard. Usually the USB ports on the back of the PC. Then try again
Click to expand...
Click to collapse
I restarted the phone and now I'm on the "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". I did have it connected to a rear usb port, let me change it.

RockRatt said:
Try a different port on the PC. Use one that is attached to the motherboard. Usually the USB ports on the back of the PC. Then try again
Click to expand...
Click to collapse
It worked. Tried a different cable and port. I have all my apps, is that normal? I thought this did a factory reset.

Thanks guys. It worked, I'm rooted .

[Q] Need help with Recovery Problems.

I've been rooting and stuff since 2012. I got a S4 AT&T I337. I rooted with Geohots app. I don't know what its called, but you just tap "make it rain" and then you install SuperSu. All that worked fine, it rooted and I took off the bloatware with TBK. And after that I tried installing TWRP. I downloaded the TWRP app and chose the right phone and model I have and flashed the TWRP recovery. Then I rebooted and It booted into download mode and I got a message in red at the top saying "stuck in odin mode". I then took the battery out and booted into download mode by holding volume Down and power and then pressed down to restart the phone. The phone works fine it's just when I boot into recovery mode It boots into this download mode thing with a message in red saying 'Stuck in odin Mode'
I installed safestrap and now when I restart the phone from the Device options. Power Off, airplane mode and restart. it gives me the option to continue and boot normally or go into recovery mode. But at the top off safestrap in says safestrap Disabled I don't know what that means.
What did I do wrong? How can I fix this? And did I make a big mistake?
I have a I337 NI1 running 4.4.2 Stock. I just got this phone off ebay so I know for a fact it probaly hasn't been messed with.
I also tired uning triangle away but that didn't fix my problem. I'm thing about just getting a Stock NI1 odin .tar and doing an emerency flash.

Do you have an i337 our an i337m? I'm not clear on that. Twrp won't work on the i337
Sent from my Nexus 5 using XDA Free mobile app

I got the normal S4

You're most likely gonna have to use the Odin to stock thread in the general section. Sounds like you meant 1337 on NI1 baseband, which can't use twrp. You're right to use safestrap but it sounds like you might have mucked your phone up a bit.

I tried that but it didn't work out to well. odin almost finished but I got an error at the very very end of the flash. But I can still get into download mode. I'm thinking about flashing the MLD since the NI1 didn't work out.

How bad do you think I messed my phone up? what would you do to fix it? This is my first time working with the s4. Every other phone I had and rooted and messed with worked fine. But this s4 is something different. Do you think you can tell me the do's and don'ts on the s4. Thanks! I need to get it fixed by Friday.
Odin log file
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUFNB1_TWRootable_Full_Odin.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!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004> tz.mbn
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> persdata.img.ext4
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
It took less than 10 seconds to get this.

TylerMarshall256 said:
How bad do you think I messed my phone up? what would you do to fix it? This is my first time working with the s4. Every other phone I had and rooted and messed with worked fine. But this s4 is something different. Do you think you can tell me the do's and don'ts on the s4. Thanks! I need to get it fixed by Friday.
Odin log file
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUFNB1_TWRootable_Full_Odin.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!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004> tz.mbn
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> persdata.img.ext4
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
It took less than 10 seconds to get this.
Click to expand...
Click to collapse
Try different usb ports (use the ones in the back of the pc) and cables. Odin can be finicky. You're flashing the right file
Sent from my Nexus 9 using XDA Free mobile app

Murasakiii said:
You're most likely gonna have to use the Odin to stock thread in the general section. Sounds like you meant 1337 on NI1 baseband, which can't use twrp. You're right to use safestrap but it sounds like you might have mucked your phone up a bit.
Click to expand...
Click to collapse
jd1639 said:
Try different usb ports (use the ones in the back of the pc) and cables. Odin can be finicky. You're flashing the right file
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
That's what I figured it was. I'm on a little Acer laptop right now. I'm about to go use my cousins desktop. I hear those are better than laptops. I'll keep you updated man just stick with me.

ALRIGHT! All I did was go to my cousins house, install the USB driver! NOT KIES! And use his factory USB cable and it fixed it just FINE!!

Help Accidentally Wiped Stock Rom

I have an SCH-i545 S4. It was running Jelly Bean 4.3 at the time rooted using Super SU and still have TWRP recovery.
I was trying to install the new lollipop update manually and forgot to switch from stock to a ROM slot in TWRP recovery and wiped the stock ROM.
I try to use Odin to flash stock firmware and revert to unrooted, but I get the following error: (I am able to get phone into download Odin mode)
<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> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
Using Odin 3.09 and trying to flash :
ALL_I545VRUEMK2_I545VZWEMK2_1937946_REV06_user_low_ship_MULTI_CERT.tar
Not sure if I'm using the wrong stock firmware and Odin version.
Let me know what I'm doing wrong thank you!

You can't flash older firmwares.
Odin 3.09 worked fine for me in the past, buy it doesn't hurt to try a different version.
Also, use the back USB ports if you have a pc.
Try different USB cables and windows versions too. Odin is quite picky.
My setup was Windows 7 x64 Pro with Odin 3.09. Using the back USB and original cable I never had an issue flashing stuff with Odin.

GDReaper said:
You can't flash older firmwares.
Odin 3.09 worked fine for me in the past, buy it doesn't hurt to try a different version.
Also, use the back USB ports if you have a pc.
Try different USB cables and windows versions too. Odin is quite picky.
My setup was Windows 7 x64 Pro with Odin 3.09. Using the back USB and original cable I never had an issue flashing stuff with Odin.
Click to expand...
Click to collapse
So I should be flashing the latest lollipop firmware vs. the older kit kat or jellybean?

odin is failing when flashing aboot.mbn because the rom has a bootloader that is older than the bootloader on the phone.
Flashing a stock LP or kk should work if the phone was running a stock 4.3 rom.

audit13 said:
odin is failing when flashing aboot.mbn because the rom has a bootloader that is older than the bootloader on the phone.
Flashing a stock LP or kk should work if the phone was running a stock 4.3 rom.
Click to expand...
Click to collapse
Alright I tried what you said and started to flash the following file: I545VRUGOC1_I545VZWGOC1_VZW
Here is the data from Odin 3.09 and the process failed again:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUGOC1_I545VZWGOC1_I545VRUGOC1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl1.mbn
<ID:0/006> sbl2.mbn
<ID:0/006> sbl3.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any suggestions? Working with Windows 10 and original samsung cord.

Strange. Boot into recovery and look at the second or third line for the recovery version on the phone.

audit13 said:
Strange. Boot into recovery and look at the second or third line for the recovery version on the phone.
Click to expand...
Click to collapse
So booting into download gives the following:
Odin Mode
Product name: SCH-I545
Current Binary: Samsung Official
System Status: Custom
Reactivation Lock: Off
CSB-CONFIG-LSB: 0x30
Secure Download: Enabled
Write Protection: Enabled
eMMC Burst Mode enabled

Can the phone be booted into recovery?

audit13 said:
Can the phone be booted into recovery?
Click to expand...
Click to collapse
Trying... Maybe not anymore???... Giving me the software update fail screen

Sounds reasonable since recovery is probably gone.
This is the verizon version of the phone? Have you tried using the original USB cable as previously suggested, a different USB port, or operating system?

audit13 said:
Sounds reasonable since recovery is probably gone.
This is the verizon version of the phone? Have you tried using the original USB cable as previously suggested, a different USB port, or operating system?
Click to expand...
Click to collapse
Just got his while trying this OS on a different USB port.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SCH-I545_MDK_562219_Stock_Restore.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sbl1.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl2.mbn
<ID:0/006> sbl3.mbn
<ID:0/006> rpm.mbn
<ID:0/006> aboot.mbn
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

angelfury126 said:
Just got his while trying this OS on a different USB port.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SCH-I545_MDK_562219_Stock_Restore.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sbl1.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl2.mbn
<ID:0/006> sbl3.mbn
<ID:0/006> rpm.mbn
<ID:0/006> aboot.mbn
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Just got it to PASS!!!! YES!!!. Plugged into the back usb ports.
Now the problem is it won't boot up... Thoughts?

It is completely dead? Did you get the firmware from sammobile.com?

audit13 said:
It is completely dead? Did you get the firmware from sammobile.com?
Click to expand...
Click to collapse
Don't think so. I'll download and try again.

All official firmware is on sammobile.com.
The phone will go to download mode?

audit13 said:
All official firmware is on sammobile.com.
The phone will go to download mode?
Click to expand...
Click to collapse
Yes.

angelfury126 said:
Just got it to PASS!!!! YES!!!. Plugged into the back usb ports.
Now the problem is it won't boot up... Thoughts?
Click to expand...
Click to collapse
I told you right from the beginning to use the back USB ports.
Anyway, did you wipe before flashing the firmware? Cuz Odin will not do it for you.

have you tried flashing different versions of the rom?
When flashing, did you try unchecking everything except f.reset time? When it finishes flashing, power off the phone by removing the USB cable and then the battery. Replace the battery and boot directly to recovery to perform a factory wipe, then reboot to the rom.

audit13 said:
power off the phone by removing the USB cable and then the battery.
Click to expand...
Click to collapse
Or you can just hold the power button for a couple of seconds until it turns off

That will work too but I find removing the battery to be easier for me.