Hello, I was trying to edit things in my mobile hotspot so I could tether for free, I restarted my phone and cant get passed the logo. I put it in ODIN Mode and am trying to flash my phone but am not having any success.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900PVPUBMI3_N900PSPTBMI3_N900PVPUBMI3_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> Firmware update start..
<ID:0/006> sbl1.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> aboot.mbn
<ID:0/006> FAIL! (Auth)
My screen now says Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
Any suggestions ?
You did not get drop call on the MI3 modem? why not use the MJ4 file?
See here for the MJ4 full stock. http://forum.xda-developers.com/showthread.php?t=2549035 What version of Odin are you using? I have found that the v1.85 and v3.09 works best. See here for more Odin versions https://www.dropbox.com/s/wzwji1gufyav83g/Odin_v3.09_v3.07_v3.06_v3.04_v1.85_v1.83.zip If you still choose to use the MI3 tar make sure that you are using the PDA or AP slot and that "re-partition" is off.
---------- Post added at 11:54 PM ---------- Previous post was at 11:46 PM ----------
wingkandy said:
Hello, I was trying to edit things in my mobile hotspot so I could tether for free, I restarted my phone and cant get passed the logo. I put it in ODIN Mode and am trying to flash my phone but am not having any success.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900PVPUBMI3_N900PSPTBMI3_N900PVPUBMI3_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> Firmware update start..
<ID:0/006> sbl1.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> aboot.mbn
<ID:0/006> FAIL! (Auth)
My screen now says Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
Any suggestions ?
Click to expand...
Click to collapse
What firmware where you before trying to flash the MI3 firmware?
I was running 4.3 before attempting to flash. I was using 3.07 Odin, I'll try downloading your suggestions. Thank you for the links
slow_one said:
You did not get drop call on the MI3 modem? why not use the MJ4 file?
See here for the MJ4 full stock. http://forum.xda-developers.com/showthread.php?t=2549035 What version of Odin are you using? I have found that the v1.85 and v3.09 works best. See here for more Odin versions https://www.dropbox.com/s/wzwji1gufyav83g/Odin_v3.09_v3.07_v3.06_v3.04_v1.85_v1.83.zip If you still choose to use the MI3 tar make sure that you are using the PDA or AP slot and that "re-partition" is off.
---------- Post added at 11:54 PM ---------- Previous post was at 11:46 PM ----------
What firmware where you before trying to flash the MI3 firmware?
Click to expand...
Click to collapse
The tar you are using has a old bootloader that is why it fails. .. download the mj4 tar and flash in Odin and it will pass unless you updated to a kit kat bootloader .... Then it won't ...
Sent from my SM-N900P using Xparent BlueTapatalk 2
Thank you so much for your help! You saved my butt. My phone is in working order
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'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.
Hello I have a Galaxy s6 edge from videotron SM-G925W8 I've try to rooted it today , but now I'm cought in a bootloop , I've try to flash it back with the original Videotron firmware but Odin give me this error at the beggening
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G925W8VLU1AOCG_G925W8OYA1AOCG_G925W8VLU1AOCG_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1005)..
<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> sboot.bin
<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)
Does anyone know what should be my next step ?
imanu said:
Hello I have a Galaxy s6 edge from videotron SM-G925W8 I've try to rooted it today , but now I'm cought in a bootloop , I've try to flash it back with the original Videotron firmware but Odin give me this error at the beggening
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G925W8VLU1AOCG_G925W8OYA1AOCG_G925W8VLU1AOCG_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1005)..
<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> sboot.bin
<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)
Does anyone know what should be my next step ?
Click to expand...
Click to collapse
Did you try wiping the cache partition?
Snowby123 said:
Did you try wiping the cache partition?
Click to expand...
Click to collapse
yes and its not working
http://forum.xda-developers.com/galaxy-s6-edge/help/5-1-1-manual-update-stuck-g925f-t3173112
This thread describes a similar issue.
The user tried flashing the stock firmware through Odin; it bricked the phone.
If you read through it you will see how the issue was resolved.
Thanks , but its for G925F version ? what do I need to do since its not the same version?
Now that is another conundrum I wasn't prepared for. I know that half of the tutorial on that thread is compatible with your phone; half is exclusive to G925F.
---------- Post added 13th August 2015 at 12:06 AM ---------- Previous post was 12th August 2015 at 11:50 PM ----------
I found another thread that explains how to troubleshoot a failed Odin attempt.
It is written for the Galaxy S2, but sounds generalized for all Samsung Galaxies.
http://forum.xda-developers.com/galaxy-s2/general/guide-t2345831
If you have access to download mode, you're ok but in order to reduce to a minimum the things that might go wrong, you should:
1- Use odin 3.10.6
2- verify the integrity of the firmware downloaded on sammobile. It should be roughly 3,402,561 kb in size
3- make sure you have Samsung Android drivers installed
4- If all above fails, switch USB cable, and then USB port
If you still have an issue, try downloading the odin flashable TWRP and try to flash it, if it passes, try wiping everything on the phone in TWRP and try the process again
As a last resort, you can try to see if KIES emergency firmware installation will work. If after doing all this you're not back up and running, you're screwed but i doubt you will have failed all of the above.
at first.. you need a custom kernel to root 5.1.1 because of the new system write protection..the second i think you are on reactivation look..look in my twrp thread for more
You got error on sboot.bin due to your flashing bootloader version lower than your device bootloader try to get the latest firmware or flash a custom firmware
If you need further assistance contact me via pm
Sent from my SM-G925F using XDA Free mobile app
Hi xda,
Recently I rooted my phone (sm-g925w8 Rogers) using the modified kernel method. Then I tried installing TWRP using the TWRP manager app however this failed and caused my phone to enter a bootloop. Of course, I can't enter recovery and whenever I try flashing a stock firmware it gives me the following error message:
<ID:0/006> Removed!!
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G925W8VLU1AOCG_G925W8OYA1AOCG_G925W8VLU1AOCG_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1005)..
<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> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any help would be greatly appreciated!
rpaterno said:
Hi xda,
Recently I rooted my phone (sm-g925w8 Rogers) using the modified kernel method. Then I tried installing TWRP using the TWRP manager app however this failed and caused my phone to enter a bootloop. Of course, I can't enter recovery and whenever I try flashing a stock firmware it gives me the following error message:
<ID:0/006> Removed!!
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G925W8VLU1AOCG_G925W8OYA1AOCG_G925W8VLU1AOCG_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1005)..
<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> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any help would be greatly appreciated!
Click to expand...
Click to collapse
Hello,
I have reported this thread to move to right Q&A so the experts there might be able to assist you.
-Vatsal
How about you try to format+downloading the any compatible "Full Rom"
Preferred Stock Rom
NVRAM already back up
............
Ready with your SP Flasht tool best ver 5.xxxxxx
Stock Rom by meant of SP Flashtool
Make sure you have Vcom+USB driver in your PC
Even though it is in a boot loop
Just get your self ready...ie: Rom scatter uploaded into SP Flash
When ever loop cycle end JUSt PLUG IN YOUR EVERREADY unit
Hopefully it will be detected.
---------- Post added at 02:10 PM ---------- Previous post was at 02:07 PM ----------
I did that to my daughter's phone that is Lenovo S850
Using splash tool
Stock rom
Lucky me.....I back up NVram + Imie
Just revive from semi bricked phone
rpaterno said:
Hi xda,
Recently I rooted my phone (sm-g925w8 Rogers) using the modified kernel method. Then I tried installing TWRP using the TWRP manager app however this failed and caused my phone to enter a bootloop. Of course, I can't enter recovery and whenever I try flashing a stock firmware it gives me the following error message:
<ID:0/006> Removed!!
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G925W8VLU1AOCG_G925W8OYA1AOCG_G925W8VLU1AOCG_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1005)..
<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> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any help would be greatly appreciated!
Click to expand...
Click to collapse
Try smart switch emergency recovery
Also do u have the same firmware as ur bootloader if not this can cause odin to fail
U could also try flashing just the stock recovery img with odin
I just had this problem now i download samsung smart switch.
1. Install smart switch
2. Click more you will find emergency software recovery.
3. Then it click device initialization.
4. Enter your phone model no that starts with sm.
5. Then ur sn no that is in the box.
6. Enter both and it will start searching and show the steps and u will get the official os for your phone.
Pls note data will be erased.
I'm having trouble with flashing the stock rom for the Samsung Galaxy S3 on Odin, as I get a fail everytime I try to flash the rom onto my device.
This comes up everytime I try to flash:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGOK1_I9300NZCGOK1_I9300XXUGOK1_HOME.tar.md 5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The model number is a GT-i9300, and no stock roms so far have succeeded.
I have used Odin 3.07 and Odin 3.09, my samsung drivers are up to date and Odin still fails to flash the rom.
I've also tried different usb cables, along with trying out different ports, none of them have worked.
On the S3 it's currently running TWRP version 3.0.2-1, it also asks me whether or not I keep it "System Read only" whenever I go in recovery mode. And each time I always choose the option of keeping it read only. I don't know if these has anything to do with Odin failing to flash the rom but might as well mention it. I was also running CyanogenMod13 for roughly a month before the brick happened.
Any help would be appreciated !
Reply
Kiddzu said:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGOK1_I9300NZCGOK1_I9300XXUGOK1_HOME.tar.md 5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
Click to expand...
Click to collapse
Hi, after NAND Write Start!! and this double !! means it start to WRITE on your Device Flash Memory when this fails it means that the cable dont transfer correct data / Cable Connection OK but wrong cable cannot write correctly on your device
I recommend you to use Original cable when flashing or a other cable but look for the compatibility to devices:good:
as far as I know it cant be a other opportunity to fix this because in the Download Mode of the s3 is the only way to Flash Original Firmware when this fails i dont now how to continue and i cannot help you more than that
And sry for my bad as fu** English