I have a SC04E (Japanese NTT Docomo Galaxy S4) and I failed to flash Cyanogenmod and bricked my phone. When I try to put the original ROM from sammobile.com, I get this error on Odin:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> Enter CS for MD5..
<ID:0/004> Check MD5.. Do not unplug the cable..
<ID:0/004> Please wait..
<ID:0/004> Checking MD5 finished Sucessfully..
<ID:0/004> Leave CS..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> aboot.mbn
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
From that I think I need a PIT file to flash but I couldn't find any pit file on the web.
I really need a pit file for it or if there's any way I can fix this problem, please reply.
Thank you in advance.
taichiksto said:
I have a SC04E (Japanese NTT Docomo Galaxy S4) and I failed to flash Cyanogenmod and bricked my phone. When I try to put the original ROM from sammobile.com, I get this error on Odin:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> Enter CS for MD5..
<ID:0/004> Check MD5.. Do not unplug the cable..
<ID:0/004> Please wait..
<ID:0/004> Checking MD5 finished Sucessfully..
<ID:0/004> Leave CS..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> aboot.mbn
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
From that I think I need a PIT file to flash but I couldn't find any pit file on the web.
I really need a pit file for it or if there's any way I can fix this problem, please reply.
Thank you in advance.
Click to expand...
Click to collapse
You probably do not need a .pit file.
In 99% of the cases the error is resolved by the following:
- Different usb port
- Different usb cable.
Lennyz1988 said:
You probably do not need a .pit file.
In 99% of the cases the error is resolved by the following:
- Different usb port
- Different usb cable.
Click to expand...
Click to collapse
Thank you for your quick reply,
I have tried changing usb ports and checked all the cables I had and I even used different computer but I couldn't get it to work and always got the same message...
*sigh*
taichiksto said:
Thank you for your quick reply,
I have tried changing usb ports and checked all the cables I had and I even used different computer but I couldn't get it to work and always got the same message...
*sigh*
Click to expand...
Click to collapse
Are you trying to flash the latest firmware available? If you try to flash the latest firmware then it's still either one of these thing.
- Different usb cable
- Different usb port
Lennyz1988 said:
Are you trying to flash the latest firmware available? If you try to flash the latest firmware then it's still either one of these thing.
- Different usb cable
- Different usb port
Click to expand...
Click to collapse
I downloaded the latest firmware and there wasn't any errors but it gets stuck where the samsung logo appears. Is there any step that I missed?
it also says Recovery Mode on the carrier logo in blue and then reboots, next time without the message and shows samsung logo and shows the battery charging
nvm I redownloaded a latest rom and it fixed the issue
Related
Help, Phone Says " Firmare Upgrade encountered an issue, Please use Software Repair
Hey Guys,
I have no clue what happened, Phone is stuck in ODIN Mode,
I am in odin 3.09, downloaded the pit file and the latest MJE firmware and i get to this step.
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_N900VVRUBMJE_N900VVZWMJE_2106277_REV03_user_low_ship_MULTI_CERT.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> 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> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> aboot.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Please help a lost soul...
Justin
Install pit by itself. Restart in recovery and factory wipe. Then install firmware
If I helped hit thanks!!
I did the pit file, not it stays locked at Samsung Galaxy Note 3 screen.
2swizzle said:
Install pit by itself. Restart in recovery and factory wipe. Then install firmware
If I helped hit thanks!!
Click to expand...
Click to collapse
Pit File - HLTE_USA_VZW_32G.PIT
PDA - MI9/MJ7/MJE (none work)
I am running odin as an administrator. I just can't get this thing to download to the phone... am i doing something wrong..
I put the phone in download mode.
Ive Done :
Download the MJE Stock Firmware 1.3 GB and extract it once...
Download latest ODIN 3.09...
In your device go into Download mode(Vol Down+Home Button+Power Button) and again Volume Up for Download mode...
Right click ODIN and open as administrator...
Now connect your device to PC and check the status in ODIN as Connected... (COM 5)
Make sure that only Auto Reboot and F.Reset Time are checked in ODIN...
Click on AP and select the extracted file from MJE firmware...
After checking the MD5 file...Click on START and wait I get the following error
-<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_N900VVRUBMI9_N900VVZWMI9_1671014_REV03_user_low_ship_MULTI_CERT.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..
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/004> Added!!
<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> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
is there something I am missing?
Thanks in advance!
Looks like you are trying to install I9 in your second post. Unless you were on i9 to start with you cannot downgrade. At the top of your post you refer to MJE. That is probably the reason.
Sent from my SM-N900V using Tapatalk
ive tried them all.. still no luck... verizon is sending me a new phone... it should load through odin, it doesn't nothing..
Well the issue was I was running ODIN in my VMWare Windows 7 Virtual Machine. I got my new phone today from verizon, for ****s i hooked it up to my old Windows XP machine and it went with out a hitch. I unplugged it was 75% so they can have it showing ODIN MODE..
Thanks for all the help...
Hi all
Long time lurking and now hoping to pass some knowledge i have learned onto other but at the minute i have a problem myself.
I have a Note 3 running Baseband N9005XXUENB1 Build number KOT49H.N9005ZHUENB5 which given the keyboard settings i believe it is the Hng Kong firmware.
I want to use a stable UK firmware like the Vodafone one N9005XXUENB4_N9005VFGENA4_N9005XXUENB1_HOME.tar.md5 however everytime i try to flash using odin 3.09 it fails.
I am using an original USB cable and tried different USB ports.
Any ideas what is going wrong?
Can anyone suggest a version which will work?
daveherron said:
Hi all
Long time lurking and now hoping to pass some knowledge i have learned onto other but at the minute i have a problem myself.
I have a Note 3 running Baseband N9005XXUENB1 Build number KOT49H.N9005ZHUENB5 which given the keyboard settings i believe it is the Hng Kong firmware.
I want to use a stable UK firmware like the Vodafone one N9005XXUENB4_N9005VFGENA4_N9005XXUENB1_HOME.tar.md5 however everytime i try to flash using odin 3.09 it fails.
I am using an original USB cable and tried different USB ports.
Any ideas what is going wrong?
Can anyone suggest a version which will work?
Click to expand...
Click to collapse
Can we get an exact copy of the error you get on Odin please?
As the 16GB Hong Kong Note 3s have a different partition layout, you might have gotten that an error.
Sent from my fingers to your face using my Samsung Galaxy Note 3!
nicholaschum said:
Can we get an exact copy of the error you get on Odin please?
As the 16GB Hong Kong Note 3s have a different partition layout, you might have gotten that an error.
Sent from my fingers to your face using my Samsung Galaxy Note 3!
Click to expand...
Click to collapse
This is what i got from Odin
<ID:0/004> Added!!
<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> cache.img.ext4
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<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)
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENB4_N9005VFGENA4_N9005XXUENB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> 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
<ID:0/004> modem.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Size)
<OSM> All threads completed. (succeed 0 / failed 1)
Try a non-carrier rom, people seem to have trouble with these...
ultramag69 said:
Try a non-carrier rom, people seem to have trouble with these...
Click to expand...
Click to collapse
I cannot locate a non carrier rom
daveherron said:
I cannot locate a non carrier rom
Click to expand...
Click to collapse
:sly:
Sent from my N9005
Dejan Sathanas said:
:sly:
Sent from my N9005
Click to expand...
Click to collapse
Sorry don't understand you response?:sly:
You're trying to flash a vodafone rom... This is a carrier rom...
Look for the UK rom that has a csc with BTU as this is the open rom...
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!
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.
Hello.
I was trying to install another custom rom but this time it required new bootloader and modem so i was like okay.
I followed the instruction and selected modem as it said.
It did it's thing and then for some reason it failed and i unfortunately i closed odin and i don't have that log anymore.
And then i tried to flash stock rom but i get this...
<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..
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
Click to expand...
Click to collapse
So then i downloaded the pit file for I9505 and i get this...
<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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
Click to expand...
Click to collapse
So what the hell do i do at this point ?
And it says that is write protected...
Kies is also not helping...
Whoever solves this problem is my hero, thanks!!!
If you have a PC, use the back USB ports. This can make a difference.
Also try a different USB cable, odin version and eventually windows version. All those things can make a difference.
GDReaper said:
If you have a PC, use the back USB ports. This can make a difference.
Also try a different USB cable, odin version and eventually windows version. All those things can make a difference.
Click to expand...
Click to collapse
Ill try with different cable. This really is strange, it never happened before. Idk if modem upgrade would cause that....
veljo323 said:
Ill try with different cable. This really is strange, it never happened before. Idk if modem upgrade would cause that....
Click to expand...
Click to collapse
God damn it it's actually a cable, can't believe it! It was working perfectly. Thank you anyway .