Hi, I'm trying to restore my phone to stock using ODIN.
I have Odin 3.09 and have the latest Scamsung Kies installed (for the usb driver).
The file I am flashing is: http://www.androidfilehost.com/?fid=23203820527944861
The message log I get from Odin is:
Code:
<ID:0/003> 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/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)
Not really sure what I'm doing wrong. My phone was on the ME7 version (And running a SafeStrap rom) before I wanted to restore it today.
xMopx said:
Hi, I'm trying to restore my phone to stock using ODIN.
I have Odin 3.09 and have the latest Scamsung Kies installed (for the usb driver).
The file I am flashing is: http://www.androidfilehost.com/?fid=23203820527944861
The message log I get from Odin is:
Code:
<ID:0/003> 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/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)
Not really sure what I'm doing wrong. My phone was on the ME7 version (And running a SafeStrap rom) before I wanted to restore it today.
Click to expand...
Click to collapse
You can't flash backwards. Flash me7.
gnubian said:
You can't flash backwards. Flash me7.
Click to expand...
Click to collapse
That makes sense, I wasn't aware that I was using an older firmware file. I'm having trouble finding the ME7 file, could you point me to a copy? Thanks!
xMopx said:
That makes sense, I wasn't aware that I was using an older firmware file. I'm having trouble finding the ME7 file, could you point me to a copy? Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2357235
That will wipe everything, so make sure to back up your files if you haven't already. Good luck!
gnubian said:
http://forum.xda-developers.com/showthread.php?t=2357235
That will wipe everything, so make sure to back up your files if you haven't already. Good luck!
Click to expand...
Click to collapse
Thanks! But with that file I got this error:
Code:
<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)
Which from what I could find, meant I needed to repartition. So I grabbed the Pit file in this thread: http://forum.xda-developers.com/showthread.php?t=2290859
But got this:
Code:
<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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
Edit: I did have Safestrap recovery installed - do I need to flash a stock recovery or is it contained in that firmware file?
xMopx said:
Thanks! But with that file I got this error:
Code:
<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)
Which from what I could find, meant I needed to repartition. So I grabbed the Pit file in this thread: http://forum.xda-developers.com/showthread.php?t=2290859
But got this:
Code:
<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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
Edit: I did have Safestrap recovery installed - do I need to flash a stock recovery or is it contained in that firmware file?
Click to expand...
Click to collapse
Just go to the safestrap app in app drawer on stock slot and uninstall it.
gnubian said:
Just go to the safestrap app in app drawer on stock slot and uninstall it.
Click to expand...
Click to collapse
I can't do that anymore, a result of these failed flashes is that I can't boot the system currently.
xMopx said:
I can't do that anymore, a result of these failed flashes is that I can't boot the system currently.
Click to expand...
Click to collapse
What happens when you start the phone?
gnubian said:
What happens when you start the phone?
Click to expand...
Click to collapse
It says:
FIrmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
I tried using the Kies recovery, but it doesn't detect that the phone needs recovering (both on that screen and the download screen used for odin).
xMopx said:
It says:
FIrmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
I tried using the Kies recovery, but it doesn't detect that the phone needs recovering (both on that screen and the download screen used for odin).
Click to expand...
Click to collapse
Are you positive you were on me7 and not mj7? Because the error you got for me7 looks the same as the one for mdk...
gnubian said:
Are you positive you were on me7 and not mj7? Because the error you got for me7 looks the same as the one for mdk...
Click to expand...
Click to collapse
Positive. I had installed the rom/recovery before anything newer than me7 was released. And I remember when I upgraded from whatever it shipped with to ME7 because the upgrade window popped up and I tapped Install by accident. I had this installed: http://forum.xda-developers.com/showthread.php?t=2351840.
Edit: to confirm, I found my old post asking about the modules to get that rom to work on ME7: http://forum.xda-developers.com/showthread.php?p=46944438
Was waiting for someone else to chime in who may know more than me. Have you tried booting into recovery from being powered off?
gnubian said:
Was waiting for someone else to chime in who may know more than me. Have you tried booting into recovery from being powered off?
Click to expand...
Click to collapse
No problem, but yeah. After every failure I would battery-pull and go back into recovery.
Edit: Tried a different USB cable and a different computer today. No dice
xMopx said:
No problem, but yeah. After every failure I would battery-pull and go back into recovery.
Edit: Tried a different USB cable and a different computer today. No dice
Click to expand...
Click to collapse
So when you went to recovery it went to stock recovery I'm assuming? Or you got the error?
If it went to stock recovery did you try wiping everything before flashing in odin?
gnubian said:
So when you went to recovery it went to stock recovery I'm assuming? Or you got the error?
If it went to stock recovery did you try wiping everything before flashing in odin?
Click to expand...
Click to collapse
Err sorry, I meant download mode (Power+Voldown). If I try booting into recovery, I get the dead android: http://i.imgur.com/HRWVsvZ.jpg
xMopx said:
Err sorry, I meant download mode (Power+Voldown). If I try booting into recovery, I get the dead android: http://i.imgur.com/HRWVsvZ.jpg
Click to expand...
Click to collapse
Try finding a stock recovery tar for your build and just flashing that in odin.
gnubian said:
Try finding a stock recovery tar for your build and just flashing that in odin.
Click to expand...
Click to collapse
I had the thought of doing this, but wasn't able to find one.
xMopx said:
I had the thought of doing this, but wasn't able to find one.
Click to expand...
Click to collapse
I looked around a little and didn't fine one either. I'd try making a request thread, I'm sure someone knows how to make a tar of it you can use in odin.
gnubian said:
I looked around a little and didn't fine one either. I'd try making a request thread, I'm sure someone knows how to make a tar of it you can use in odin.
Click to expand...
Click to collapse
Isn't the recovery contained in the larger firmware files? What gain would flashing the stock recovery get?
I'm thinking I might just take the phone to a Verizon store and say, "Samsung kies told me it was going to update my phone, I took a shower and when I came back it was like this".
Edit: I untarred the firmware file, and it contained recovery.img. Can I flash that with odin?
xMopx said:
Isn't the recovery contained in the larger firmware files? What gain would flashing the stock recovery get?
I'm thinking I might just take the phone to a Verizon store and say, "Samsung kies told me it was going to update my phone, I took a shower and when I came back it was like this".
Edit: I untarred the firmware file, and it contained recovery.img. Can I flash that with odin?
Click to expand...
Click to collapse
I believe it has to be a tar. If you can get it on there and wipe data/factory reset it may get rid of safestrap and allow you to odin the full stock tar.
Related
Phone is 'bricked', and gets stuck on Samsung logo. How do I fix this? I'm trying to follow threads on how to get back to stock, but most of the links are dead - so if anyone can help, that would be great! When following some guides, I get the following error:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI500_VZW_EH03_GB_CM.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> param.lfs
<ID:0/003> Sbl.bin
<ID:0/003> boot.bin
<ID:0/003> recovery.bin
<ID:0/003> zImage
<ID:0/003> factoryfs.rfs
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!
Click to expand...
Click to collapse
lolreconlol said:
Phone is 'bricked', and gets stuck on Samsung logo. How do I fix this? I'm trying to follow threads on how to get back to stock, but most of the links are dead - so if anyone can help, that would be great! When following some guides, I get the following error:
Click to expand...
Click to collapse
If you're coming from ICS or CM7, you need pit file for re-partition.
jhssal said:
If you're coming from ICS or CM7, you need pit file for re-partition.
Click to expand...
Click to collapse
Ah! Thanks, worked that time.
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.
So my friend was trying to fix the wifi on his Note while on Sky Rom (4.3), but, for some reason he happened to have clicked a link to the wrong section and was in the n7100 (international) section. He used Odin to flash the MJ5 bootloader which is the international version. Now his phone will only bootloop with the N7100 boot screen appearing. We are not able to access recovery but we can get to download mode. Once we got to download mode I have tried flashing the PIT file, root66, and the official VRAMC3. Each attempt without a PIT file causes this
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I605VRAMC3_I605VZWAMC3_1098177_REV04_user_low_ship.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> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And any attempts with the PIT file causes this
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> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any help would be very much appreciated because I have run out of ideas at this point.
Jet5195 said:
So my friend was trying to fix the wifi on his Note while on Sky Rom (4.3), but, for some reason he happened to have clicked a link to the wrong section and was in the n7100 (international) section. He used Odin to flash the MJ5 bootloader which is the international version. Now his phone will only bootloop with the N7100 boot screen appearing. We are not able to access recovery but we can get to download mode. Once we got to download mode I have tried flashing the PIT file, root66, and the official VRAMC3. Each attempt without a PIT file causes this
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I605VRAMC3_I605VZWAMC3_1098177_REV04_user_low_ship.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> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And any attempts with the PIT file causes this
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> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any help would be very much appreciated because I have run out of ideas at this point.
Click to expand...
Click to collapse
I went through this last month and check these things:
- Try a different USB cord
- Try a different USB port
- Disable your antivirus
- May have to reboot your computer
When I softbricked a few weeks ago I went through this process for the first time, and I found I had to keep trying over and over but it finally ended up working.
Remember to unlock your bootloader after this process - which I did not and had to redo everything after rooting and flashing and getting the Verizon discovered unauthorized software etc.
Also, I wonder if this is part of the issue, while in download mode I get "PRODUCT NAME: GT-N7100" instead of sch-i605, could this be part of the issue?
And thanks for the ideas Darbylonia, I tried those and even different computers and still no luck.
Jet5195 said:
Also, I wonder if this is part of the issue, while in download mode I get "PRODUCT NAME: GT-N7100" instead of sch-i605, could this be part of the issue?
And thanks for the ideas Darbylonia, I tried those and even different computers and still no luck.
Click to expand...
Click to collapse
Did you try looking through the top stickied post about how to recover from a soft brick? I would go there and see if the info helps and post there. I do think it is strange about the product name but there's got to be a fix so keep on...
hi guys..
is there any wat to downgrade this version (i545VRUFNK1) to 4.3..?
t-mobile_mda said:
hi guys..
is there any wat to downgrade this version (i545VRUFNK1) to 4.3..?
Click to expand...
Click to collapse
yes downgraded..
first flash with this;
MK2_system_4downgrade
then flash,
MK2VZW-downgrade4rooting-AIOdin-gogolie
Bricked S4 SCH-I545
NEED HELP PLEASE!!!
I tried the Odlin3 approach for full wipe (with 3.09, 3.07, 3.10 version) but I get a fail as posted below. I'm completely stuck. I tried using Kies approach posted on another tread and the approach on http://forum.xda-developers.com/showthread.php?t=2751461. Both approaches failed. I've downloaded about 20GB of firmware and each fails. When I just try to power on the device it shows the SAMSUNG name and the "Unlocked" icon. Any suggestions?
<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> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
treaklet said:
NEED HELP PLEASE!!!
I tried the Odlin3 approach for full wipe (with 3.09, 3.07, 3.10 version) but I get a fail as posted below. I'm completely stuck. I tried using Kies approach posted on another tread and the approach on http://forum.xda-developers.com/showthread.php?t=2751461. Both approaches failed. I've downloaded about 20GB of firmware and each fails. When I just try to power on the device it shows the SAMSUNG name and the "Unlocked" icon. Any suggestions?
<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> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
When you boot into download mode what version does it say you are on? (it's the red lettering at the very top)
BladeRunner said:
When you boot into download mode what version does it say you are on? (it's the red lettering at the very top)
Click to expand...
Click to collapse
ODIN Mode.
BladeRunner said:
When you boot into download mode what version does it say you are on? (it's the red lettering at the very top)
Click to expand...
Click to collapse
Odin Mode
Ive been trying to fix my Samsung S3 GT- I9300, stuck on Samsung Logo, when i go to android system recovery, i get alot of errors,starting with cant mount efs then followed by alot of red colored errors,data factory reset , wipe partitions, wipe cache is giving errors also, when i go to download mode and tried flashing thru Odin with stock firmware from sammobile using only the PDA/AP
I9300XXUGNA5_I9300OLBGNB1_I9300DXUGNB1_HOME.tar
but gives me this error:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGNA5_I9300OLBGNB1_I9300DXUGNB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Help!, i dont know what to do next.
zansan said:
Ive been trying to fix my Samsung S3 GT- I9300, stuck on Samsung Logo, when i go to android system recovery, i get alot of errors,starting with cant mount efs then followed by alot of red colored errors,data factory reset , wipe partitions, wipe cache is giving errors also, when i go to download mode and tried flashing thru Odin with stock firmware from sammobile using only the PDA/AP
I9300XXUGNA5_I9300OLBGNB1_I9300DXUGNB1_HOME.tar
but gives me this error:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGNA5_I9300OLBGNB1_I9300DXUGNB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Help!, i dont know what to do next.
Click to expand...
Click to collapse
Try flashing the latest TWRP through Odin. Download it from their website 2.8.6.1 in .tar format and flash. Then flash the stock firmware.