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.
Related
Hi,
I have a Verizon Samsung Galaxy Note II, (SCH-1605), and I have apparently soft-bricked / boot-looped my device.
I followed droidstyle's tutorial titled, "[GUIDE][VZW Edition]How to Root/Rom/Return to Stock the VZW Galaxy Note II!."
Installed Odin on my Win8 x64 desktop
Downloaded the proper pit and tar files from his tutorial
ran odin from the "downloading" screen
How can i fix my phone and/or reset it to factory condition?
What may have caused my phone to boot-loop?
P.S. (I still wish to root the phone and try some custom roms once it is operational)
try flashing root66 with no pit file.
Thank you for your response.
I tried flashing with "rooot66_VZW_stock_system.tar.md5," in both bootloader and PDA slots in Odin3 v1.85.
I ran at least one attempt of both with and without the pit file. The yellow highlighting is present.
The phone still seems to be in a boot-loop. Could it be that I'm using the wrong Samsung Drivers on my PC? They were plug-and-play as far as I could tell. I did run the OTA updates before I knew they had something to do with locking down the bootloader.
Below I will paste the various Odin logs...
Root66 in PDA w/ Pit file
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_VZW_stock_system.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> system.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
--
Root66 in PDA w/o Pit file
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_VZW_stock_system.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> system.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
--
Root66 in BOOTLOADER w/ PIT file
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_VZW_stock_system.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> system.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
--
Root66 in BOOTLOADER w/o PIT file
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_VZW_stock_system.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> system.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
--
Ok what you need to do is reflash root66 in pda with pit, power the device off, press and hold the volume up/home/power buttons and boot into recovery, then wipe data/factory reset, and reboot.
---------- Post added at 10:07 AM ---------- Previous post was at 10:05 AM ----------
and dont flash anything in bootloader...simply trying random techniques is a good way to turn your device into a paper weight.
taylorp0994 said:
Hi,
I have a Verizon Samsung Galaxy Note II, (SCH-1605), and I have apparently soft-bricked / boot-looped my device.
I followed droidstyle's tutorial titled, "[GUIDE][VZW Edition]How to Root/Rom/Return to Stock the VZW Galaxy Note II!."
Installed Odin on my Win8 x64 desktop
Downloaded the proper pit and tar files from his tutorial
ran odin from the "downloading" screen
How can i fix my phone and/or reset it to factory condition?
What may have caused my phone to boot-loop?
P.S. (I still wish to root the phone and try some custom roms once it is operational)
Click to expand...
Click to collapse
After flashing with Odin you must do a factory reset.
I also had this on my Galaxy S2 Plus.
Sent from my GT-I9105P using xda app-developers app
droidstyle said:
Ok what you need to do is reflash root66 in pda with pit, power the device off, press and hold the volume up/home/power buttons and boot into recovery, then wipe data/factory reset, and reboot.
---------- Post added at 10:07 AM ---------- Previous post was at 10:05 AM ----------
and dont flash anything in bootloader...simply trying random techniques is a good way to turn your device into a paper weight.
Click to expand...
Click to collapse
Thank you. I was previously unaware of the power/home/vol.up combination for factory reset. I re-flashed root66 in PDA w/ the PIT file, however this time it went to the android with a neutron-like animation inside signifying updates. It worked w/o running a reset, but I ran one anyways to ensure I know how it works.
Again, thank you for your support.
I rooted on VRUAME7 I am now trying to do a reset/restore. When I did a factory reset in the system, it rebooted and is now stuck on a yellow exclamation mark and says:
I tryed to put CWM on my phone. I didnt do my research so I had no idea I couldnt with ME7.. I have followed multiple forum guides that have the same exact problems as mine. also all ME7 specific. At this point... ODIN is non responsive.. and I am at the mercy of all yall haha
Odin Failed and says:
<ID:0/005> 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/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> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl2.mbn
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> aboot.mbn
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Phone says:
Start [224,1440]
SW REV. CHECK FAIL: FOUND: 3, Binary: 1
Once you're on ME7 you cannot Odin back to MDK. Find the ME7 Odin file and you'll be good.
Sent from my badass Galaxy S4 using Tapatalk
spc_hicks09 said:
Once you're on ME7 you cannot Odin back to MDK. Find the ME7 Odin file and you'll be good.
Sent from my badass Galaxy S4 using Tapatalk
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2301259
I have followed this one.. downloaded the ME7 file...
It still is not working. This is not the only ME7 file I have downloaded and they have all not worked.
I have used multiple cables on the phone and multiple versions of odin.
They are all doing the same thing... I have been at this for HOURS.
I am seriously stumped....
spjohnson08 said:
http://forum.xda-developers.com/showthread.php?t=2301259
I have followed this one.. downloaded the ME7 file...
It still is not working. This is not the only ME7 file I have downloaded and they have all not worked.
I have used multiple cables on the phone and multiple versions of odin.
They are all doing the same thing... I have been at this for HOURS.
I am seriously stumped....
Click to expand...
Click to collapse
I would verify the md5 to.make sure your not getting corrupted downloads. Its pretty common, but ya like hicks said you cant go backwards in firmware which is what you tried to do the first time around. It has to be an me7 image or ml1.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
spc_hicks09 said:
Once you're on ME7 you cannot Odin back to MDK. Find the ME7 Odin file and you'll be good.
Sent from my badass Galaxy S4 using Tapatalk
Click to expand...
Click to collapse
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> 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/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> sbl2.mbn
<ID:0/003> NAND Write Start!!
<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)
This is with the ME7 file...
hexitnow said:
I would verify the md5 to.make sure your not getting corrupted downloads. Its pretty common, but ya like hicks said you cant go backwards in firmware which is what you tried to do the first time around. It has to be an me7 image or ml1.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
Click to expand...
Click to collapse
I am now trying to use the ml1 file on http://forum.xda-developers.com/showthread.php?t=2301259
I didnt know I could do that...
How do I verify the Hash?
spjohnson08 said:
I am now trying to use the ml1 file on http://forum.xda-developers.com/showthread.php?t=2301259
I didnt know I could do that...
How do I verify the Hash?
Click to expand...
Click to collapse
Google md5 checker or md5 verifier. Its a straight forward process. The correct md5 should be posted in the thread.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
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.
I made the mistake of trading phones with a guy whose GS4 was rooted with SS recovery and there were no MSD in it when we traded. I brought it home, restarted it. And it began to get stuck on the "FIRMWARE UPGRADE ENCOUNTERED AN ISSUE. PLEASE SELECT RECOVERY MODE IN KIES & TRY AGAIN." which I know to not use Kies as it was useless to me when I had my first GS4 at time of launch. I am fairly new at this with a gs4. I have tried and tried with ODIN v3.07. I have been on here and looking through forums and I went to other forums besides xda with countless different trials. NONE have been even the slightest bit helpful...
I was wondering since it was stuck on the devilish yellow triangle screen. I can not even get past this to get the launcher... could ADB be the problem since I can't get it to even boot up to enable it?
before anyone asks, to which will waste both our time....
yes, i have used the stock vz firmware and placed it in the PDA section in ODIN
THIS IS WHAT I GET EVERY TIME.
<ID:0/003> 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/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> sbl2.mbn
<ID:0/003> NAND Write Start!!
<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)
ALL HELP IS MUCH APPRECIATED!!:good:
Are you sure you were on ME7? You might need to flash a newer firmware.
Sent from my NCC-1701 using Tapatalk.
Definitely need to flash newer firmware
degradedtree69 said:
I made the mistake of trading phones with a guy whose GS4 was rooted with SS recovery and there were no MSD in it when we traded. I brought it home, restarted it. And it began to get stuck on the "FIRMWARE UPGRADE ENCOUNTERED AN ISSUE. PLEASE SELECT RECOVERY MODE IN KIES & TRY AGAIN." which I know to not use Kies as it was useless to me when I had my first GS4 at time of launch. I am fairly new at this with a gs4. I have tried and tried with ODIN v3.07. I have been on here and looking through forums and I went to other forums besides xda with countless different trials. NONE have been even the slightest bit helpful...
I was wondering since it was stuck on the devilish yellow triangle screen. I can not even get past this to get the launcher... could ADB be the problem since I can't get it to even boot up to enable it?
before anyone asks, to which will waste both our time....
yes, i have used the stock vz firmware and placed it in the PDA section in ODIN
THIS IS WHAT I GET EVERY TIME.
<ID:0/003> 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/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> sbl2.mbn
<ID:0/003> NAND Write Start!!
<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)
ALL HELP IS MUCH APPRECIATED!!:good:
Click to expand...
Click to collapse
This has happened to me about four times with my phone. I was able to fix through a process of Kies and Odin. It seems that if you do all that you can in Kies, as far as attempting to re-install the stock firmware. Kies has the drivers you need in order for Odin to work. You will need to run through the Kies process (it will fail), but you will get the drivers you need. You will then need to boot into download mode and do the Odin flash process. This is all assuming you have the correct files for Odin. You will need to flash the stock build afterwards unless you have a backup and are able to access safestrap which i doubt you will have.
I attempted to root my phone through Odin pushing superuser and twrp onto it as tutorials told me to do, and my phone literally goes to the boot logo and then stops. I have tried a million times to flash a stock rom back onto it but it won't push through either Odin or TWRP without error messages. It lets me flash a cyanogenmod rom through TWRP but the screen just goes back when I boot it up. Is my phone done for? Can I fix this somehow?
If you aren't able to reflash the phone with Odin, most likely, you aren't using the correct firmware. Please post your model number, the name of the file you are using, which version of Odin, and what the error you are getting is.
es0tericcha0s said:
If you aren't able to reflash the phone with Odin, most likely, you aren't using the correct firmware. Please post your model number, the name of the file you are using, which version of Odin, and what the error you are getting is.
Click to expand...
Click to collapse
I have tried using both Odin3_v3.10.6 and Odin3 v3.12.3. The files I have attempted to flash are XSG-J700HXXU2BPF9-20160629164434, CAU-J700HXXU1APA3-20160106083224, SM-J700H_J700HXXU1AOK5_J700HOLB1AOK1_5.1.1-MYM, and J700FXXU1AOL2_J700FODD1AOL1_INS_(by_firmwarefile.com).
My phone's model number is J700H/DS. The error I am receiving is <ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> J700HXXU1APA3_J700HOXY1AOL1_J700HXXU1AOL1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin engine v(ID:3.1005)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> sboot.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> cm.bin
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
from Odin and
"sw. rev. check fail. device:2, binary:1" on my phone's screen
Thank you for your reply, I am actually incredibly stupid and left the DS out of my model number and was therefore getting the wrong firmwear. I fixed it.