Database Users

HELP PLEASE!!! firmware error

OK so this is what i did. so i tried to root my s4, and in odin it said fail. so i took out the battery. and try to turn it on now it has the phone YELLOW triangle and a monitor. it says "firumware upgrade encountered an issue. Please select recovery mod in kies & try again.
what i have tried so far was download the sprint stock and odin it back. i used qbking77 . com the stock i used is linked on that website. which then links me to stockroms.net. so during the process of doing going back to stock it said fail. i read some where that in the id:com on odin, it should say 0:[COM6] and i read some where else that it does have to say com6 it could say com3. i dont know if that matters. and i also read on the forum they say to use another stock rom? is that also if so where can i get one besides from stockroms.net please someone help me..
this is what it says when i try to odin to stock:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUAMDC_L720SPTAMDC_L720VPUAMDC_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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Added!!

Sounds like a bad rom download. Download the rim again or get it from a sticky on xda.
Also it doesn't matter what com port Odin puts the phone on as long as it sees it.
Sent from my SPH-L720 using xda app-developers app

tordsrv 1892
im still fairly new at the whole rooting scene. could you possible link me to the stock rom? oh btw idk if this would matter but i think i had the MF9..
i just want to go back stock for now and get this phone to work.. than i will try again.. thank you in advance!
my uncle also said there is a odin file not the program. but an odin file that you use with odin program. is this true for the s4? if so could you link me to it also!

i just tried it again. and im getting this error now..
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUAMDC_L720SPTAMDC_L720VPUAMDC_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> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)

I have read that that download fron QBKing is bad. As a poster above me said, download the rom from XDA instead and redo the process. Also, be sure to use the usb cable that came with your phone as others can cause the same issue. Also....if it fails again, try a different usb port. Good luck
Sent from my SPH-L720 using Tapatalk 4 Beta

could someone link me to the right post that has the sprint stock rom? thank you

texassoljaz said:
could someone link me to the right post that has the sprint stock rom? thank you
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2382188
Last post
Sent from my SPH-L720 using xda premium

and ubuings
ok so.. i downloaded this stock firmware
http://forum.xda-developers.com/showthread.php?t=2258107
and it actually goes futher but than it said i dont have a pit file.. im sorry this is my first time and it is so hard to understand everything.

<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MF9FirmwareAIO.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
could someone tell me wht it says no PIT partition? i have tried so many different stocks for the sprint phone.
im sure mines was the MF9. but i also tried the MDL and MDC.

texassoljaz said:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MF9FirmwareAIO.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
could someone tell me wht it says no PIT partition? i have tried so many different stocks for the sprint phone.
im sure mines was the MF9. but i also tried the MDL and MDC.
Click to expand...
Click to collapse
Bot trying to scare you here but if you google the pit error people are being told its a faulty motherboard
Sent from my SPH-L720 using xda premium

same thing happen to my boys gs2 when i was flashing a recovery for him... same ishh.. all i had to do is use odin to unroot and flash a stock rom via odin.. its worked for me.. all the phone would do is go into download mode.. thats it.. no recovery and it wouldnt boot.. stuck in download mode.. i plugged it in to my pc.. odin noticed the phone i flashed stock unrooted rom.. phone rebooted at the end and everything was fine..one crazy thing was after that happen i tried to root again and flash a custom recovery and it happen again.. so i had to fix it again.. i just could not root that phone after that.. had to keep it stock.. my buddy was just happy to have his phone he didnt care about root after that!!

texassoljaz said:
OK so this is what i did. so i tried to root my s4, and in odin it said fail. so i took out the battery. and try to turn it on now it has the phone YELLOW triangle and a monitor. it says "firumware upgrade encountered an issue. Please select recovery mod in kies & try again.
what i have tried so far was download the sprint stock and odin it back. i used qbking77 . com the stock i used is linked on that website. which then links me to stockroms.net. so during the process of doing going back to stock it said fail. i read some where that in the id:com on odin, it should say 0:[COM6] and i read some where else that it does have to say com6 it could say com3. i dont know if that matters. and i also read on the forum they say to use another stock rom? is that also if so where can i get one besides from stockroms.net please someone help me..
this is what it says when i try to odin to stock:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUAMDC_L720SPTAMDC_L720VPUAMDC_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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Added!!
Click to expand...
Click to collapse
Its not really a bad download, had this issue once before when I soft bricked my s4 and I needed to restore it back to stock. You need to delete the .md5 extension and leave it with the .tar extension and that should work! Good luck!
Sent from my SPH-L720 using xda app-developers app

ROMANTiC KiD said:
Its not really a bad download, had this issue once before when I soft bricked my s4 and I needed to restore it back to stock. You need to delete the .md5 extension and leave it with the .tar extension and that should work! Good luck!
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
I tried what you said than it went to this
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Complete(Write) operation failed.
<ID:0/007> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
but now i have a loading bar on my phone. so i dont know whats going to happen i will leave it for a while to see what happens.

texassoljaz said:
I tried what you said than it went to this
Added!!
Odin v.3 engine (ID:7)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Complete(Write) operation failed.
Added!!
All threads completed. (succeed 0 / failed 1)
but now i have a loading bar on my phone. so i dont know whats going to happen i will leave it for a while to see what happens.
Click to expand...
Click to collapse
Hmm weird. Redownload the file from qbking77 and delete the extension again. Also try it with a different version of odin for example the one that qbking uses v1.85 (which is also the one I use) and pull out battery and put the battery in and manually set it to download mode and try it one more time. Btw any chance did you get a pop up in your screen saying something about an error of some kind saying about a parameter before?
Edit: Also probably restart computer just in case also.
Sent from my SPH-L720 using xda app-developers app

ROMANTiC KiD said:
Its not really a bad download, had this issue once before when I soft bricked my s4 and I needed to restore it back to stock. You need to delete the .md5 extension and leave it with the .tar extension and that should work! Good luck!
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
ROMANTiC KiD said:
Hmm weird. Redownload the file from qbking77 and delete the extension again. Also try it with a different version of odin for example the one that qbking uses v1.85 (which is also the one I use) and pull out battery and put the battery in and manually set it to download mode and try it one more time. Btw any chance did you get a pop up in your screen saying something about an error of some kind saying about a parameter before?
Edit: Also probably restart computer just in case also.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
no i never never got a parameter error.. i also have window 8 do you think that will affect anything? i will try qbking than update you.. thanks for helping. greatly appreciated!

texassoljaz said:
no i never never got a parameter error.. i also have window 8 do you think that will affect anything? i will try qbking than update you.. thanks for helping. greatly appreciated!
Click to expand...
Click to collapse
Hmm... alrighty. Nah it shouldnt affect anything but you can also try with other computer as well or different version of windows. No problem hope you get it solved soon!
Sent from my SPH-L720 using xda app-developers app

so after trying it. i got a parameter error. what does this mean?

so i end up getting this far.. do you know how to fix this?
<ID:0/010> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUAMDC_L720SPTAMDC_L720VPUAMDC_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> aboot.mbn
<ID:0/010> NAND Write Start!!
<ID:0/010> tz.mbn
<ID:0/010> boot.img
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/010> Added!!

<ID:0/010> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUAMDC_L720SPTAMDC_L720VPUAMDC_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> aboot.mbn
<ID:0/010> NAND Write Start!!
<ID:0/010> tz.mbn
<ID:0/010> boot.img
<ID:0/010> recovery.img
<ID:0/010> system.img.ext4
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/010> Added!!
i dont get it. so i got it to start the green bar in on odin.. than all of a sudden it say fails. and one my phone the blue bar went half way

yessss!!!!! i got

[UNBRICK Guide][for Bootloader v1 jb only][I9195]How to unbrick your device

Disclaimer:
I'm not liable to any demage to your device, including Knox. The information here is as good as I know, there is no guarantee.
(If you like to provide extra information or have a correction, I'll add it to the OP)
>>I'm searching for more full repair firmwares (Containing, PIT, Bootloader, etc. seperated), if anyone could send me the files for I9195 and I9192 etc. i'd upload them too, please help and help others.<<
There are several types of a brick:
Bootloop (usually possible to unbrick)
Stuck at splash screen (a bit harder but still usually possible)
Hardbrick (black screen and nothing works) (there is also a possible solution but it could also mean the end)
Full brick (black screen, nothing works, even the hardbrick method doesn't work. solution could be using a JTAG)
How to unbrick a bootloop and stuck at splash screen brick
Download one of the repair firmwares from here
I9195 Here
Thanks a lot for providing the I9195 files to: @b0g
PIT file:
https://drive.google.com/file/d/0Bx2R0nz6jh17bllKenctWnVsWkE/edit?usp=sharing
Other files:
https://drive.google.com/file/d/0Bx2R0nz6jh17aEVHMHkwLVRjWVE/edit?usp=sharing
###########################################################################################
- Unzip/unrar the files
- Install usb drivers and use the Odin program
- Put the files like the following:
(file names starting with: )
Bootloader (BL) > BOOTLOADER...
PDA (AP) > CODE...
PHONE (CP) > MODEM...
CSC > CSC...
PIT > CSB...
- Make sure your device has enough charge 40% is recommended
- Enter download mode (press volume down + home + power button in the booting process for around 20 seconds)
- connect your device (Odin should say "Added")
- Click start (do NOT disconnect your device or restart your computer in the flashing process, this could make things worse)
- Wait until the phone has fully reset and enter the recovery
- Do a "Factory reset" and "Wipe cache"
- Reboot
- Done
How to unbrick a Hardbricked phone
- Buy a USB-JIG online
- Make sure that the devices battery has charged (even if it doesn't show charging animation)
- Remove your battery
- Plug the USB-JIG inside your phone
- Wait 3 minutes and put the battery back inside
- Wait 40 seconds and the "download mode" screen should appear
- Follow the steps like in the "Bootloop and stuck at splashscreen guide" as above (note: you don't have to enter download mode because using the JIG it should enter it automatically)
Credits:
Me
@b0g

reserved

edited

I9195 mirror at Google drive added
Huge thanks go to @b0g for providing the files for I9195! :good:

hi.
i search a solution repair my s4 mini for hours. tried many ways on this forum and others, but nothing works. so i found this and use the data follow the steps above to ressurrect my phone of bootloop and stuck.
odin flashs correctly i think, but after the reset the phone stucks in "recovery booting..."
i checked autoreboot and re partitition, unchecked f reset time. the odin log says everthing ok:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9195XXUBML4_2340422_REV01_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> CODE_I9195XXUBML4_2340422_REV01_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> MODEM_I9195XXUBML4_2340422_REV01_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_OXA_I9195OXABML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<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> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sbl1.mbn
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> persist.img.ext4
<ID:0/003> persdata.img.ext4
<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> hidden.img.ext4
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
what can i do, please help?

skortax said:
hi.
i search a solution repair my s4 mini for hours. tried many ways on this forum and others, but nothing works. so i found this and use the data follow the steps above to ressurrect my phone of bootloop and stuck.
odin flashs correctly i think, but after the reset the phone stucks in "recovery booting..."
i checked autoreboot and re partitition, unchecked f reset time. the odin log says everthing ok:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9195XXUBML4_2340422_REV01_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> CODE_I9195XXUBML4_2340422_REV01_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> MODEM_I9195XXUBML4_2340422_REV01_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_OXA_I9195OXABML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<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> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sbl1.mbn
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> persist.img.ext4
<ID:0/003> persdata.img.ext4
<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> hidden.img.ext4
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
what can i do, please help?
Click to expand...
Click to collapse
try flashing twrp recovery and wipe all then (despite external sd)
also try flashing with f reset time enabled...

thanks for the quick help. flashed twrp and it boots in recovery, but full wipe doesnt run, so i wiped manually - unfortunately i get bluescreen and i am again at the beginning.
every method i tried ends with the same result: bluescreen, blackscreen, greenscreen and every other existing screen, in every possible loop or odin stuck during the flash process
i think the problem lies deeper and can only be solved with jtag, if it is not an hardware error. what do you think?

Hi I'm having a similar issue with my i9195 getting stuck on boot screen. I think mine has something todo with the new battery i got for it, as the new one only has 3 pins and the old has 4?
one way i found of being able to boot my phone was to take out the battery plug the charger in then put the battery back in once the green battery icon shows that it is charging hold the power until it vibrates and it should (it does for me) start up, i was also able to get into recovery using the above method by holding the home and volume up as normal.

Thanks for this, I will probably use it in near future.

Please someone has the i9192???

Aronuser said:
....
I9195 Here
Thanks a lot for providing the I9195 files to: @b0g
PIT file:
https://drive.google.com/file/d/0Bx2R0nz6jh17bllKenctWnVsWkE/edit?usp=sharing
Other files:
https://drive.google.com/file/d/0Bx2R0nz6jh17aEVHMHkwLVRjWVE/edit?usp=sharing
###########################################################################################
- Unzip/unrar the files
- Install usb drivers and use the Odin program
- Put the files like the following:
(file names starting with: )
Bootloader (BL) > BOOTLOADER...
PDA (AP) > CODE...
PHONE (CP) > MODEM...
CSC > CSC...
PIT > CSB...
- Make sure your device has enough charge 40% is recommended
- Enter download mode (press volume down + home + power button in the booting process for around 20 seconds)
- connect your device (Odin should say "Added")
- Click start (do NOT disconnect your device or restart your computer in the flashing process, this could make things worse)
- Wait until the phone has fully reset and enter the recovery
- Do a "Factory reset" and "Wipe cache"
- Reboot
- Done
.....
Click to expand...
Click to collapse
hi !
can i use this part for to try to downgrade a KK firmware to JB ???!!!
have to check "re-partition" ???

Loulou-13 said:
hi !
can i use this part for to try to downgrade a KK firmware to JB ???!!!
have to check "re-partition" ???
Click to expand...
Click to collapse
yes check re partition, ah and it's not sure yet if it's possible to downgrade from KK i wanna know myself please tell me the result if you know it

yes ,i think i will try it , but i'm "nervious" with re-partition and pit ! i'm a little afraid ...
i would have prefered an advise to a person"spécialist" who know Samsung very well ...... before testing with this flash .
but i know "re-partition" and Odin (I have already had olds Samsungs )
it's principaly the **** of **** of ****** of HELL "Knox" who scares me ...
The pit here is REALLY the good ???
There are devises who have good(s) method(s) for to downgrade , there are other that it's really impossible ..... but for the S4-mini ,nobody have done expérimenations about ,no tutorials ...etc ...
everybody flash as one file .tar now ...
EDIT !
maybe the master @arco68 can answer to this problem ???!!!

... no idea ?!

Hello, can you please help me? I have problems with random restarting of my i9195 S4 Mini (Vodafone). I tried to flash another official ROM, but this problem remains. When I try flash back original stock ROM (or any other ROM - with root or without root), the results are still same - FAIL message in ODIN after aboot.mbn file.
I tried this guide, but again, everything was ended with fail message (check the attached log).
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9195XXUBML4_2340422_REV01_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> CODE_I9195XXUBML4_2340422_REV01_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> MODEM_I9195XXUBML4_2340422_REV01_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_OXA_I9195OXABML4_2340422_REV01_user_low_ship_MULTI_CERT.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> 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)
Can you please help me and tell me what I can do if I want to put back any stock ROM? I am going crazy with the fail message which shows me in every try. Checked with Odin 3.09, 3.07, 1.83 and still no success.

jerrry said:
Hello, can you please help me? I have problems with random restarting of my i9195 S4 Mini (Vodafone). I tried to flash another official ROM, but this problem remains. When I try flash back original stock ROM (or any other ROM - with root or without root), the results are still same - FAIL message in ODIN after aboot.mbn file.
Can you please help me and tell me what I can do if I want to put back any stock ROM? I am going crazy with the fail message which shows me in every try. Checked with Odin 3.09, 3.07, 1.83 and still no success.
Click to expand...
Click to collapse
Can you tell what is the text in download mode screen? If the last 2 lines say BOOTLOADER SW REV : 2, then you have latest bootloader and IT IS IMPOSSIBLE TO DOWNGRADE.

sasank360 said:
Can you tell what is the text in download mode screen? If the last 2 lines say BOOTLOADER SW REV : 2, then you have latest bootloader and IT IS IMPOSSIBLE TO DOWNGRADE.
Click to expand...
Click to collapse
Thank you for reply. Yes, I have Bootloader AP SWREV: 2. But what can I do if I want to change actual ROM which is flashed in device? I would like to get back original Vodafone ROM (stock), but I can't do anything (flash same ROM which is now in device, flash Vodafone ROM, flash custom ROM).

jerrry said:
Hello, can you please help me? I have problems with random restarting of my i9195 S4 Mini (Vodafone). I tried to flash another official ROM, but this problem remains. When I try flash back original stock ROM (or any other ROM - with root or without root), the results are still same - FAIL message in ODIN after aboot.mbn file.
I tried this guide, but again, everything was ended with fail message (check the attached log).
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9195XXUBML4_2340422_REV01_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> CODE_I9195XXUBML4_2340422_REV01_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> MODEM_I9195XXUBML4_2340422_REV01_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_OXA_I9195OXABML4_2340422_REV01_user_low_ship_MULTI_CERT.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> 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)
Can you please help me and tell me what I can do if I want to put back any stock ROM? I am going crazy with the fail message which shows me in every try. Checked with Odin 3.09, 3.07, 1.83 and still no success.
Click to expand...
Click to collapse
I had the same issue (aboot.mbn failing and finally I managed to fix it by flashing I9195XXUCNE6_I9195OXACNE6_DBT with Odin 3.09. Downloaded the firmware from sammobile (http://www.sammobile.com/firmwares/3/?confirm=31540). Had to wipe data/cache after flashing the ROM. Not the ROM I wanted, but at least now I have a working S4 mini again.

jerrry said:
Thank you for reply. Yes, I have Bootloader AP SWREV: 2. But what can I do if I want to change actual ROM which is flashed in device? I would like to get back original Vodafone ROM (stock), but I can't do anything (flash same ROM which is now in device, flash Vodafone ROM, flash custom ROM).
Click to expand...
Click to collapse
skip the modem file and the bootloader file at flashing and you should be fine

Aronuser said:
skip the modem file and the bootloader file at flashing and you should be fine
Click to expand...
Click to collapse
How can I skip these files? Because in ODIN I am selecting just only one file.

My phone resisting odin flash

my phone is bricked, it will not flash stock rom via odin, i asked on the main forum what the log meant, i was told i needed a pit file, so i got one, and tried again, but it still fails, so here is the log, please tell me what to do.
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S5360XXMI1_S5360XEUMI1_S5360XXMG1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Complete(Write) operation failed.
<ID:0/007> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)

Try Adding the pit file+the stock rom in odin and flash them together, and see if that works

did you do the download mode
Power off phone
Press and hold Home + Volume down + Power on button
Press volume up to confirm and enter download mode

i did flash the pit and stock rom together in odin, and then tried separately, and yes of course i was in download mode!!!
still no good though...

Kobro said:
i did flash the pit and stock rom together in odin, and then tried separately, and yes of course i was in download mode!!!
still no good though...
Click to expand...
Click to collapse
Try to connect mobile using SS port. i.e. the USB port with different colour in a laptop. It is also known as US 3.0 port!

Kobro said:
my phone is bricked, it will not flash stock rom via odin, i asked on the main forum what the log meant, i was told i needed a pit file, so i got one, and tried again, but it still fails, so here is the log, please tell me what to do.
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S5360XXMI1_S5360XEUMI1_S5360XXMG1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Complete(Write) operation failed.
<ID:0/007> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
It failed because you have not split the firmware first - Galaxy y does not support single file flashing
You need to split the firmware into pda modem and csc - You can do this by using splitfus2 link in my signature
However I have already split pretty much all available firmware which you can find on my firmware thread - http://forum.xda-developers.com/showthread.php?t=2568853
The one that you want based on what your odin log says will be
http://d-h.st/hOn

[AT&T S7] Please help if you can. ODIN flashing stock error

EDIT: I HAVE SOLVED THE ISSUE. I am not sure how but I got into a different download mode and the flash worked. I also used different SM-930A Files and it worked but system status is still custom.
I want to put my phone back to stock after I have installed a custom ROM. I have an AT&T S7. I get this error while flashing the firmware using Odin
----------------------------------------------------------------------------------------------------------
<ID:0/005> 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/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
------------------------------------------------------------------------------------------------------
On the phone it says the following
"SW REV CHECK FAIL : [system]Fused 3 > Binary 1"
If you could tell me how to flash my phone back to stock without getting this error it would be very much appreciated.

I got the same error a while back. For me, it was because I was using Odin 3.11.1. Once I updated to Odin 3.12.3, the restore went smoothly. Someone correct me if that's not the way to fix this issue, but that is what worked for me.

lukemarcondes said:
I got the same error a while back. For me, it was because I was using Odin 3.11.1. Once I updated to Odin 3.12.3, the restore went smoothly. Someone correct me if that's not the way to fix this issue, but that is what worked for me.
Click to expand...
Click to collapse
I have resolved the issue. I have been trying for almost a month now to fix the phone and I finally did it. The device still says custom although I have flashed the official firmware on. Somehow I got into an alternative download mode that accepted the flash. I have no clue how I got it into the mode but it only said "downloading" and showed nothing in the top right corner. No white text.

ColbyTrip1 said:
I have resolved the issue. I have been trying for almost a month now to fix the phone and I finally did it. The device still says custom although I have flashed the official firmware on. Somehow I got into an alternative download mode that accepted the flash. I have no clue how I got it into the mode but it only said "downloading" and showed nothing in the top right corner. No white text.
Click to expand...
Click to collapse
I see. Glad you were able to fix it!

UnRoot Not Working (Save Me Please!!!)

So a few months back I followed PSouza's guide (https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039) to rooting the S7 Edge and everything worked perfectly. As of late, the phone has had many general performance issues and I decided today unrooting may be the best option for right now. So I cracked back open the thread and followed the instructions and low and behold, as always, something had to go wrong. For starters, Odin gives me a fail before it even really gets started (log below).
"<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.1203)..
<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> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<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!!"
The phone itself gives a SW Rev check fail after that (in the download mode).
So I thought to myself I'd just keep it in the meantime and just restart it and use it for now, but low and behold I now can't leave download mode. If I restart regularly, I'm brought back to a software update failed screen, and if I switch to recovery mode (? vol up + home + power) I've wiped the cache partition as another forum suggested, but then going to reboot system now... That restart brings me right back into recovery. I currently have the phone off charger in hopes the battery dies and something changes then.
I'm also downloading the very very latest firmware update for the S7 Edge in hopes that maybe Odin will like it a bit better than this one (VZW_G935VVRU2APE1.zip).
Any ideas? Any solution that gets me a working phone again, I'll definitely make a donation to your PayPal! Thanks in advance for any help!

To anyone reading this having the same issue, follow the instructions in this post (https://forum.xda-developers.com/showpost.php?p=71133959&postcount=27) worked like a charm.

zwroberts1 said:
To anyone reading this having the same issue, follow the instructions in this post (https://forum.xda-developers.com/showpost.php?p=71133959&postcount=27) worked like a charm.
Click to expand...
Click to collapse
Have you tried using smart switch? It is a PC app by Samsung which will automatically choose the correct firmware for you, flash it and also unroot your phone. It is the easiest way to do it.

TheSproker said:
Have you tried using smart switch? It is a PC app by Samsung which will automatically choose the correct firmware for you, flash it and also unroot your phone. It is the easiest way to do it.
Click to expand...
Click to collapse
The issue I was having was that Smart Switch wasn't recognizing my phone off the bat, and when I went to emergency recovery, it would say my serial number was incorrect so it wasn't useable for me.