So I went from Hyper RLS16 MJ7 to MK2 using odin, then used VZW OTA to go to NC5. Rooted, Installed Safestrap, then installed Hyperdrive RLS17 (on stock slot per sbreens instructions). For some reason I was having some weird Quirks and decided to try to flash NC5 in odin again using surges file, It started to flash (full wipe method with PIT file) and failed, so now I have the problem where it starts to flash, fails, the I jut re-partition and am able to get back into download mode, but Its gets up to ABOOT in odin, then fails. Here is the messages in odin:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_VZW_I545VRUFNC5_I545VZWFNC5_1151670_REV06_user _low_ship_MULTI_CERT.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> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<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> persdata.img.ext4
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
If anyone has any ideas, please let me know, I have tried going back to MK2, but I am assuming its locked out because it fails instantly.
Let me know if there is more info needed.
Verizon SCH-I545 Galaxy S4 NC5 baseband.
i think Riff Jtag box will help you
bradbb2009 said:
So I went from Hyper RLS16 MJ7 to MK2 using odin, then used VZW OTA to go to NC5. Rooted, Installed Safestrap, then installed Hyperdrive RLS17 (on stock slot per sbreens instructions). For some reason I was having some weird Quirks and decided to try to flash NC5 in odin again using surges file, It started to flash (full wipe method with PIT file) and failed, so now I have the problem where it starts to flash, fails, the I jut re-partition and am able to get back into download mode, but Its gets up to ABOOT in odin, then fails. Here is the messages in odin:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_VZW_I545VRUFNC5_I545VZWFNC5_1151670_REV06_user _low_ship_MULTI_CERT.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> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<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> persdata.img.ext4
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
If anyone has any ideas, please let me know, I have tried going back to MK2, but I am assuming its locked out because it fails instantly.
Let me know if there is more info needed.
Verizon SCH-I545 Galaxy S4 NC5 baseband.
Click to expand...
Click to collapse
bradbb2009 said:
So I went from Hyper RLS16 MJ7 to MK2 using odin, then used VZW OTA to go to NC5. Rooted, Installed Safestrap, then installed Hyperdrive RLS17 (on stock slot per sbreens instructions). For some reason I was having some weird Quirks and decided to try to flash NC5 in odin again using surges file, It started to flash (full wipe method with PIT file) and failed, so now I have the problem where it starts to flash, fails, the I jut re-partition and am able to get back into download mode, but Its gets up to ABOOT in odin, then fails. Here is the messages in odin:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_VZW_I545VRUFNC5_I545VZWFNC5_1151670_REV06_user _low_ship_MULTI_CERT.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> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<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> persdata.img.ext4
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
If anyone has any ideas, please let me know, I have tried going back to MK2, but I am assuming its locked out because it fails instantly.
Let me know if there is more info needed.
Verizon SCH-I545 Galaxy S4 NC5 baseband.
Click to expand...
Click to collapse
I can't find the fix, but if I remember right @Surge1223 has posted a fix for the "persdata.img.ext4" failing.
In the meantime, what message is displayed on your phone when the flash fails?
---------- Post added at 07:30 PM ---------- Previous post was at 07:28 PM ----------
avsamuel87 said:
i think Riff Jtag box will help you
Click to expand...
Click to collapse
Not needed. This is not a hard brick. (What is it with the number of RIFF JTAG posts answering softbrick questions these days? Riffbox owners looking to drum up business?)
k1mu said:
I can't find the fix, but if I remember right @Surge1223 has posted a fix for the "persdata.img.ext4" failing.
In the meantime, what message is displayed on your phone when the flash fails?
---------- Post added at 07:30 PM ---------- Previous post was at 07:28 PM ----------
Not needed. This is not a hard brick. (What is it with the number of RIFF JTAG posts answering softbrick questions these days? Riffbox owners looking to drum up business?)
Click to expand...
Click to collapse
There is no message on the phone it just freezes when downloading and odin fails.
bradbb2009 said:
So I went from Hyper RLS16 MJ7 to MK2 using odin, then used VZW OTA to go to NC5. Rooted, Installed Safestrap, then installed Hyperdrive RLS17 (on stock slot per sbreens instructions). For some reason I was having some weird Quirks and decided to try to flash NC5 in odin again using surges file, It started to flash (full wipe method with PIT file) and failed, so now I have the problem where it starts to flash, fails, the I jut re-partition and am able to get back into download mode, but Its gets up to ABOOT in odin, then fails. Here is the messages in odin:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_VZW_I545VRUFNC5_I545VZWFNC5_1151670_REV06_user _low_ship_MULTI_CERT.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> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<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> persdata.img.ext4
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
If anyone has any ideas, please let me know, I have tried going back to MK2, but I am assuming its locked out because it fails instantly.
Let me know if there is more info needed.
Verizon SCH-I545 Galaxy S4 NC5 baseband.
Click to expand...
Click to collapse
MK2 wont work, and it doesnt fail at aboot, it fails at persdata. Use Heimdall and flash just the system.img.ext4, you can extract the NC5 system.img.ext4 from the ALL_VZW_I545VRUFNC5_I545VZWFNC5_1151670_REV06_user _low_ship_MULTI_CERT.tar.md5 file by renaming it to ALL_VZW_I545VRUFNC5_I545VZWFNC5_1151670_REV06_user _low_ship_MULTI_CERT.tar and then extracting system.img.ext4 from it. You can find a guide on how to use Heimdall via google or xda search if you aren’t familiar with how to use it.
So when I go into Heimdall, I try to flash the system, and it fails the confirmation,
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading SYSTEM
0%
100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: SYSTEM upload failed!
Ending session...
Releasing device interface...
and the phone says SECURE CHECK FAIL : system.
any ideas?
bradbb2009 said:
So when I go into Heimdall, I try to flash the system, and it fails the confirmation,
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading SYSTEM
0%
100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: SYSTEM upload failed!
Ending session...
Releasing device interface...
and the phone says SECURE CHECK FAIL : system.
any ideas?
Click to expand...
Click to collapse
Use a different usb port and uninstall then reinstall the drivers for your phone. Other than that, try flashing cache, hidden, and persdata and see if any of those fail.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Tried new USB port, I can successfully do everything but system, everything else completes without a hitch.
I download and the device reboots, I go back into download mode, flash each piece like that.....once I get to system it fails.
When I get into recovery, it says unable to mount /system, I assume it is because I cant download it. I have tried to wipe/factory reset and n reboot im stuck at SGS4 splash screen.
Sorry Im taking long to respond my fiances dad is up and trying to do this in between activities...
I really appreciate the help here though.
bradbb2009 said:
Tried new USB port, I can successfully do everything but system, everything else completes without a hitch.
I download and the device reboots, I go back into download mode, flash each piece like that.....once I get to system it fails.
When I get into recovery, it says unable to mount /system, I assume it is because I cant download it. I have tried to wipe/factory reset and n reboot im stuck at SGS4 splash screen.
Sorry Im taking long to respond my fiances dad is up and trying to do this in between activities...
I really appreciate the help here though.
Click to expand...
Click to collapse
The "Secure Check Fail" that you're getting means that the digital signature of what you're trying to install is not verifying.
That either means that you're getting data corruption when transferring over the USB connection, or you're trying to flash older software.
In the latter case, your phone will give additional information with the system revision and rev of what's being flashed.
If all you're getting is "Secure Check Fail", then you've got a bad USB cable, flaky USB port, etc.
I have tried 3 different USB cables, 3 ports on one PC and 2 on another. I can successfully flash all other files except System, and with that I have downloaded multiple times and extracted multiple times to avoid corruption as a possibility, this is the last file I need to get my phone back working, and its killing me i cant figure it out. is there any other way to get it into the phone? I see you can do recovery with the sdcard, is that even a possibility? I'm just a little lost at this point.
the one other thing that is odd is my device shows up as MSM8960 in Heimdall driver configuration, could that point somewhere?
bradbb2009 said:
I have tried 3 different USB cables, 3 ports on one PC and 2 on another. I can successfully flash all other files except System, and with that I have downloaded multiple times and extracted multiple times to avoid corruption as a possibility, this is the last file I need to get my phone back working, and its killing me i cant figure it out. is there any other way to get it into the phone? I see you can do recovery with the sdcard, is that even a possibility? I'm just a little lost at this point.
the one other thing that is odd is my device shows up as MSM8960 in Heimdall driver configuration, could that point somewhere?
Click to expand...
Click to collapse
SOLVED!
So after doing everything under the sun to make this work I came across this post,
http://forum.xda-developers.com/showpost.php?p=53674568&postcount=2
Basically I had Samsung drivers 1.5.14.0 installed when trying to use odin, it worked with the MK2 flash without a problem, well apparently flashing NC5 required at least 1.5.27.0 installed which I found during a google search. Link- 1.5.27.0 Driver Download
Now, this does not explain why Heimdall would not flash my system.img.ext4, I switched the drivers over using Zadig and I could flash everything else, but system gave the headache. Maybe the driver isn't up to snuff? I am running 8 also (although I could not get it to work on 7 either.)
AGAIN, the only thing that changed was the driver revision, I was still using the same port and cable as just before the driver install and failure.
Related
HI,
I have Samsung S3 i tried to upgrade it to the latest firmware via Odin and while it was in processing my laptop froze so i restarted it and now when i get my phone into download mode i get those information:
Product name:
Custom Binary Download: NO
Current Binary: Samsung Official
System Status: Custom
as u can see the product name is "empty"
I really need your help! please...
Thanks
Have you tried to reflash with odin?
Sent from my GT-I9300 using Tapatalk 2
The main thing is you can get into download mode still, like previous post said reflash on a reliable laptop
Reflash with odin. If still problem, remove/replace. battery and Reflash. I think it ll work...
Sent from my GT-I9300 using Tapatalk 2
Thanks alot for your help i will try now and give u the results...
still the same:crying::crying::crying:
this is what i get
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006>
<ID:0/006> Re-Partition operation failed.
<ID:0/006> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
Start odin, put your rom on pda, leave everything unchanged, make sure that repartition button is not enabled, start your phone in download mode, and wait until you see in odin message "added" , than click start. I wish you luck.
Sent from my GT-I9300 using Tapatalk 2
delta1987 said:
still the same:crying::crying::crying:
this is what i get
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006>
<ID:0/006> Re-Partition operation failed.
<ID:0/006> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
Click to expand...
Click to collapse
how you flash with odin?
please see this
http://forum.xda-developers.com/showthread.php?t=1671969
re-partition box should be empty and try changing usb port. do not use usb 3.0 port if you have. good luck.
ok so i tried it with Re-partition checked off and i got this
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXBLFB_I9300OJVBLF3_I9300XXLFB_HOME.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>
<ID:0/006> There is no PIT partition.
<ID:0/006> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
I'm a bit of a Noob but here's what I would try - go to sammobile.com and find the latest official ROM for your phone/area. Download it to laptop. Start Odin. Put phone into Download mode then connect it. Click PDA and find the download file and flash it.
The official file should have all you need, but if you did this previous with PIT clicked you will need to ask someone more experienced than me - I haven't had any experience with that.
Another thing you might try is DL Revolution ROM (search for ARHD 9) and follow the Superwipe instructions to get rid of all the previous possible crap. I noticed when I used it there was all kinds of format-type stuff happening as the ROM installed.
If flashing with repartition failed after first try and now your nand is improperly partitioned or not partitioned at all, than you must now thick repartition while flashing by Odin because in other case it will not even start nand write.
But to make it properly you need Rom with separate parts (3 file firmware: PDA, PHONE, CSC) and proper .pit file for mapping new partition structure to flash it.
I can give you a link for such firmware but only for XEO region. If you need another one you must find it yourself.
Rom:
https://hotfile.com/dl/158814567/30ec3bc/GT-I9300_XEO_I9300XXALEF_I9300OXFALEA_I9300XXLEF.rar.html
Proper pit for above firmware:
https://hotfile.com/dl/162097667/e5b3f90/mx.zip.html
Flash with those probably will be successful, but if your nand partition information was erased than there is a risk of data loss on efs partition. But this will be your future problem.
i9.0.1.3k galaxy imperator
I think op need to use a proper pit file along with some stock odin rom to resolve this issue
《spilled from dragon jellybean rom》
And run ODIN as administrator.
My first NAND write failed win W7.
I retried it it worked (but as an Admin)
I still have the same problem even when i run odin as an administrator
still got that pit partition error!!
delta1987 said:
ok so i tried it with Re-partition checked off and i got this
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXBLFB_I9300OJVBLF3_I9300XXLFB_HOME.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>
<ID:0/006> There is no PIT partition.
<ID:0/006> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
you sir have corrupted the PIT mapping...now I believe you will have to flash the 3 file method..get the correct pit file.. I believe mx.pit is the latest...check repartition....
PM SirKunon..he is more experienced in these things..
And never check Repartition again..
I'm trying to brick my phone using ODIN 3.07 and file name, VRUDMI1_Root_de_la_vega_jfltevzw.tar.md5 but it kept failing at Fail (AUTH). I've since downloaded the factory image for VRUDMI1 (which is what my phone is) from the link found in this thread.
After rebooting the phone and again trying to flash it via Odin 3.07 I'm now getting this error message:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUDMI1_I545VZWDMI1_I545VRUDMI1_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> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
At this point, what else can I do to recover the phone into working operation?
sage55 said:
I'm trying to brick my phone using ODIN 3.07 and file name, VRUDMI1_Root_de_la_vega_jfltevzw.tar.md5 but it kept failing at Fail (AUTH). I've since downloaded the factory image for VRUDMI1 (which is what my phone is) from the link found in this thread.
After rebooting the phone and again trying to flash it via Odin 3.07 I'm now getting this error message:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUDMI1_I545VZWDMI1_I545VRUDMI1_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> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
At this point, what else can I do to recover the phone into working operation?
Click to expand...
Click to collapse
I would start by redownloading the file you're flashing to make sure your current one isn't corrupt. May even wanna try unistalling odin and reinstalling. And you're sure that you are flashing the same version you are already on?
sage55 said:
I'm trying to brick my phone using ODIN 3.07 and file name, VRUDMI1_Root_de_la_vega_jfltevzw.tar.md5 but it kept failing at Fail (AUTH). I've since downloaded the factory image for VRUDMI1 (which is what my phone is) from the link found in this thread.
After rebooting the phone and again trying to flash it via Odin 3.07 I'm now getting this error message:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUDMI1_I545VZWDMI1_I545VRUDMI1_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> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
At this point, what else can I do to recover the phone into working operation?
Click to expand...
Click to collapse
This is a VERY frequently asked question. You're probably flashing the wrong software (i.e. older than what's on your phone). There's a bit more detail on the cause of the "FAIL!" displayed on your phone that could be used to verify the cause.
You're trying to flash a no-wipe image as well. Using a full wipe factory image may work better.
bjoostema said:
I would start by redownloading the file you're flashing to make sure your current one isn't corrupt. May even wanna try unistalling odin and reinstalling. And you're sure that you are flashing the same version you are already on?
Click to expand...
Click to collapse
Uninstall and re-install odin? What are you talking about? Odin was in a zip file that I simply had to extract then run. There was no install process nor would their be an uninstall process...
As for the files I've tried thus far and their MD5 as per Md5Checker:
File: rootdelavegajfltevzw.7z
MD5: BC497A23D75752D2C5AAD8D7D8E39B00
Note: Root for MI1 build.
File: SCH-I545_VZW_3_20131015092810_3pa3eg8qji.zip
MD5: 8335DA10191B0E2CE84A701B8E5249B4
Note: No-wipe factory restore for MI1 build.
File: SCH-I545_VZW_1_20130613171315_24s13crny1_fac.zip
MD5: 622956872FA0083188BEAB3A78A21B1C
Note: Factory restore for M7J build (I seen in another thread where this fixed previously bricked phones)
All three have failed, all at different points.
sage55 said:
Uninstall and re-install odin? What are you talking about? Odin was in a zip file that I simply had to extract then run. There was no install process nor would their be an uninstall process...
As for the files I've tried thus far and their MD5 as per Md5Checker:
File: rootdelavegajfltevzw.7z
MD5: BC497A23D75752D2C5AAD8D7D8E39B00
Note: Root for MI1 build.
File: SCH-I545_VZW_3_20131015092810_3pa3eg8qji.zip
MD5: 8335DA10191B0E2CE84A701B8E5249B4
Note: No-wipe factory restore for MI1 build.
File: SCH-I545_VZW_1_20130613171315_24s13crny1_fac.zip
MD5: 622956872FA0083188BEAB3A78A21B1C
Note: Factory restore for M7J build (I seen in another thread where this fixed previously bricked phones)
All three have failed, all at different points.
Click to expand...
Click to collapse
OK, you're doing the right things but it's failing. The next thing to try is to make sure you're using a known good OEM (Samsung) USB cable. Also, try a different port on your PC. Some people have had better success with using the ports on the back of their PCs.
When I run the Root image for MI1 the error in odin is above and the error on the phone in tiny red text is:
SECURE CHECK FAIL: CACHE
The MJ7 file seems to go the furthest but still fails:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> COMBINATION_I545VRUAME7_I545VZWAME7_690088_REV06_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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On the phone in super tiny text and red is:
START [224,1440]
SW REV. CHECK FAIL; FUSED; 5. BINARY; 3
For the No-Wipe MI1 file I Odin has this error:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUDMI1_I545VZWDMI1_I545VRUDMI1_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> 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)
<OSM> All threads completed. (succeed 0 / failed 1)
and the phone shows the following error:
SW REV. CHECK FAIL; FUSED; 5. BINARY; 4
Just got the phone this afternoon and am using the white Samsung USB cord that came with the phone. I've tried using the USB ports on the back of my desktop computer (windows 8.1) as well as on my laptop (Windows 7).
sage55 said:
When I run the Root image for MI1 the error in odin is above and the error on the phone in tiny red text is:
SECURE CHECK FAIL: CACHE
START [224,1440]
SW REV. CHECK FAIL; FUSED; 5. BINARY; 3
Click to expand...
Click to collapse
That is not good news.
Each time VZ updates their software for these phones, they update a value in a fuse.
That started as 1 with MDK, went to 2 with ME7, 3 with MI1, and 4 with MJ7. At least that's what I think the revisions did to the qfuse.
So it's seeing that you're trying to flash a binary with revision 3 (BINARY:3) but it remembers a flash with revision 5.
Now, there's nothing out there that I know of for the i545 that's rev 5 - the next update after MJ7 will be rev 5. So, your phone is probably not going to be recoverable until VZ and Samsung release another software update for the I545. Something corrupted the fuse storing the update level.
You can verify this by flashing MJ7 - it'll probably say FUSED:5, BINARY: 4.
Sorry for the bad news.
k1mu said:
You can verify this by flashing MJ7 - it'll probably say FUSED:5, BINARY: 4.
Sorry for the bad news.
Click to expand...
Click to collapse
The MJ7 file errors with "SW REV. CHECK FAIL; FUSED; 5. BINARY; 3"
The MI1 No-wipe file errors with SW REV. CHECK FAIL; FUSED; 5. BINARY; 4"
Fused value for ME7 was 3. So for MJ7 the fused value should be 5. The binary values are one behind because you're using no wipe odin tars. The dev edition binary values are set to 1. Use the full odin tar instead.
Sent from my SCH-I545 using XDA Premium 4 mobile app
is there a way to edit so called fuse value and binary value in MI1 to read that same value as MJ7 when flashing ?
Surge1223 said:
Fused value for ME7 was 3. So for MJ7 the fused value should be 5. The binary values are one behind because you're using no wipe odin tars. The dev edition binary values are set to 1. Use the full odin tar instead.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You are absolutely correct and somehow I managed to download ME7 thinking it was MJ7. I've downloaded MJ7 from here and so far I've gone much further in the flashing process. Crossing fingers.
The correct, MJ7 file did in fact work and the phone is back to life running Android 4.3!
Thanks for all the help guys!
delete
Surge1223 said:
Fused value for ME7 was 3. So for MJ7 the fused value should be 5. The binary values are one behind because you're using no wipe odin tars. The dev edition binary values are set to 1. Use the full odin tar instead.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks. That also explains one of the other major differences in the no-wipe tar files, which is something I didn't know.
---------- Post added at 09:13 AM ---------- Previous post was at 08:48 AM ----------
enfurnic said:
is there a way to edit so called fuse value and binary value in MI1 to read that same value as MJ7 when flashing ?
Click to expand...
Click to collapse
No, the value in the binary can't be altered without invalidating the signature.
The "fuse" is an efuse that can't currently be reverted. From what I know of how it's implemented, it's simply not possible at all to restore.
Hi all,
I have a Samsung galaxy S3 GT-I9300. 2 days ago it crashed and won't boot anymore. The reason was can't mount /cache, can't mount system ... on recovery mode. I tried only the wipe cache option and it did nothing.
I started looking at the forum to understand how to fix it. I deciced first to make a backup of my data if possible so I downloaded Odin v3.07 and philz_touch_6.07.9-i9300.tar.md5. I read in another thread that we can manage to copy data from the phone using philz tools.
The problem here is that flashing philz tools with Odin fails all the time. Now I can only access the download mode. At boot, I have a "Firmware upgrade encountered an Issue..." I tried with Kies recovery but it failed too.
In my sdcard, I have no folder clockwordmode ! In download mode
PRODUCT NAME : GT-I9300
CUSTOM BINARY DOWNLOAD : Yes (3)
CURRENT BINARY : Custom
SYSTEM STATUS : Ofiicial
I am bit lost as there seem to be a lot of options in other threads. I don'y know where to start or what to do ? is it the PIT files to restore ? the firmware, the kernel ? the whole OS ?
Many thanks
Don't use pit file. pit is Last resort!!!! Get stock firmware from sammobile.com and flash it through Odin. Forget kies. Read about Odin before flashing.
You'll need to flash with a *.pit file, and the ROM downloaded from sammobile in order to restore your device. Use the *.pit file as the absolute last option to restore your phone. It will repartition your phone, and any power loss of either the machine you are flashing from, or your phone will render it a permanent brick.
Thank you
I am downloading the latest firmware from sammobile (1.1 GB) and Odin 3.09. There are specific instructions for Odin on sammobile website so I don't think i'm goint to mess it up. I will let you know if it did work for me.
I tried to flash the image from sammobile but it failed. There is no log I can read to understand why
Here is the name of image I downloaded I9300XXUGML2_I9300FTMGML2_I9300BVUGML1_HOME.tar
Concerning Odin, its the 3.09 GS3 by l0gan
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGML2_I9300FTMGML2_I9300BVUGML1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<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> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Shall I try with an older image (this one is the latest) ? or retry by messing the PIT ?
Nand write fail = motherboard replacement.
Keep trying to flash and don't give up but please leave pit till the end. Yes try three part recovery firmware and older firmware "not ics" SDS on ics firmware and you don't want that. But at the end of the day nand write fail means hardware failure.
Hi again,
I succeeded to flash one image from 2013. Odin says PASS!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXELL1_I9300FTMELL1_I9300BVELK1_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> system.img
<ID:0/006> NAND Write Start!!
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> cache.img
<ID:0/006> hidden.img
<ID:0/006> modem.bin
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/006> Removed!!
<ID:0/006> Removed!!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
However, I still have the "Firmware upgrade encountered an issue" at boot I removed the phone when I saw the message Removed in Odin. I am not sure whether it didn't let the process finish well or I did right. Any ideas or suggestions ?
I succeeded to reinstall the latest firmware and I got back the samsung logo at boot. However It still doesn't go any further and no recovery mode ... Is there a way to check the status of the system ?
Omg its alive!! Odin said pass! Just keep flashing that firmware till you get recovery and then factory reset.
Try the rescue firmware in general thread, follow the instructions exactly.
Sent from my GT-I9300 using Tapatalk
Hello
An update of my case. After struggling 2 days with NAND write fail and trying lots of firmwares... I succeeded to install CMW recovery tool. From that, I installed Cyanogenmod 10.0.2. I struggled to make it boot too as it looped on cyanogen logo many times.
Now I must confess that I am afraid of rebooting the phone as I thought it was dead :angel:
Hope it helps someone else :highfive:
Great feed back for others. and go's to show never give up flashing with Odin. Odin is a pain in the ....
Congrats :thumbup:
Hey guys, long time lurker here, and finally made an account to get some help :/
It seems like I softbricked my phone today, and I have been unsuccessful at trying to recover it through Odin.
I was trying to install the GS4 GPE (KK 4.4.3) when I accidentally wiped my System (with my cache, data, and dalvik) and then turned my phone off. My phone wouldn't go past the "Samsung Custom" screen, so I tried to boot it into Download mode for a full recovery via Odin. I've been following the thread by Surge regarding using Odin with NC5, and it keeps failing on me
When I try to boot it normally now, it comes up to a screen that says "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again".
If I try to do a Full Wipe using Surge's guide on Odin and NC5, it gives me this:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_VZW_I545VRUFNC5_I545VZWFNC5_1151670_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> 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!!
Click to expand...
Click to collapse
I've tried this multiple times, and it either stops at NAND Write Start into a Complete(write) operation failed, or it just gives me that response after Get PIT for mapping.
What I know for sure:
- I am on NC5, rooted and safestrap 3.72
Any ideas? Maybe my only option is to cancel my contract and get a new phone? Any help would be appreciated.
EDIT 1: I tried Odin again for the hell of it and seems like it got little further before failing. I got to sbl1.mbn and sbl2.mbn before hitting "Complete(Write) Operation failed"
<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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> sbl2.mbn
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
wnsdlek said:
Hey guys, long time lurker here, and finally made an account to get some help :/
It seems like I softbricked my phone today, and I have been unsuccessful at trying to recover it through Odin.
I was trying to install the GS4 GPE (KK 4.4.3) when I accidentally wiped my System (with my cache, data, and dalvik) and then turned my phone off. My phone wouldn't go past the "Samsung Custom" screen, so I tried to boot it into Download mode for a full recovery via Odin. I've been following the thread by Surge regarding using Odin with NC5, and it keeps failing on me
When I try to boot it normally now, it comes up to a screen that says "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again".
If I try to do a Full Wipe using Surge's guide on Odin and NC5, it gives me this:
I've tried this multiple times, and it either stops at NAND Write Start into a Complete(write) operation failed, or it just gives me that response after Get PIT for mapping.
What I know for sure:
- I am on NC5, rooted and safestrap 3.72
Any ideas? Maybe my only option is to cancel my contract and get a new phone? Any help would be appreciated.
EDIT 1: I tried Odin again for the hell of it and seems like it got little further before failing. I got to sbl1.mbn and sbl2.mbn before hitting "Complete(Write) Operation failed"
Click to expand...
Click to collapse
Try booting into download mode and plugging the phone in to your computer and running "Emergency Firmware Recovery" and "Firmware Upgrade and Initialisation" in Kies under the "Tools" tab. They will both fail, that is okay. Just follow the steps for both as far as it will let you. I have been in your exact situation (not turning my phone off after wiping, but the yellow triangle and firmware error message) a couple times and for some reason this seems to reset the phone or something, allowing you to run the odin program. Also, make sure you are using Odin 3.10. Im not sure the GPE Rom you are trying to flash is even compatible with NC5, I have not seen one on the threads that is except for one that Gigilie ported and I think that one was a 4.4.4 port, though I could be wrong. What is the link to the thread you were trying to flash? Let me know how it goes.
I made the mistake of rooting my phone with KingUser Root. Not Kingo, but the one you can "root" without a PC. At any rate, when the latest Pokemon Go update came out I was unable to play. I tried unrooting with the King software, but it failed. So I tried a method I found online to installe SuperSU over King and then attempted to unroot it with its proprietary software...only to have my phone soft brick and at first it would only boot to the Verizon Splash screen...
So, I downloaded ODIN, downloaded the appropriate files or so I thought and attempted to flash to recover it. Now it won't boot past "Software Updated Failed: please run VZW Software Update Repair Assistant" and that doesn't work either... any tips as to what I can do? I can still use download mode, but recovery mode won't load.
It's the 16 GB VZW SCH-I545 version.
It got stuck here:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUAME7_I545VZWAME7_I545VRUAME7_HOME.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> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sbl2.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl3.mbn
<ID:0/006> rpm.mbn
<ID:0/006> aboot.mbn
<ID:0/006> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
For me also
Any help ?