• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Stuck in recovery mode

  • Thread starter Thread starter Deleted User
  • Start date Start date
I just want be clear that I am not suggesting to root when I suggest this site but you may find Official firmware and other useful information specific to you device. For me I search "XDA Sprint Note 4"
Would that be any better than SamMobile?
 
can you provide the full detail from odin?
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_P580UEU1CRK2_CL14823999_QB20733081_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_P580UEU1CRK2_CL14823999_QB20733081_REV00_user_low_ship_meta.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_XAR_P580XAR1CRK3_CL14823999_QB20843994_REV00_user_low_ship.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> 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> sboot.bin.lz4
<ID:0/003> NAND Write Start!!
 
Windows 7 laptop
Does the laptop have USB 2.0 or USB 3.0 ports? It might have both. Try a different USB port or let it run and when it fails in Odin open device manager on the PC and see if drivers failed.

Odin versions being finicky on certain devices is correct, I would try Odin 3.09 it's one i've used alot.

It could be corrupted firmware or a incorrect Android version which one did you download?

I would be willing to download the firmware and we can match file sizes but again I would need to know which one to download.
 
Does the laptop have USB 2.0 or USB 3.0 ports? It might have both. Try a different USB port or let it run and when it fails in Odin open device manager on the PC and see if drivers failed.

Odin versions being finicky on certain devices is correct, I would try Odin 3.09 it's one i've used alot.

It could be corrupted firmware or a incorrect Android version which one did you download?

I would be willing to download the firmware and we can match file sizes but again I would need to know which one to download.
Already tried switching ports, didn't do anything.
Also I downloaded this: https://www.sammobile.com/samsung/g...are/SM-P580/XAR/download/P580UEU1CRK2/246257/
 
I tried it using a different version of odin and got stuck on <ID:0/003> NAND Write Start!!

Then it may not be due to Odin or that the new Odin is "finicky". Just trying to eliminate possible issues is of help. What your tablet previously rooted? The reason I ask is that bootloops seldom occur on stock OS.
 
Last edited:
what fail?

Just for reference but in the bottom the same place that you see DM'Verty fail. Look at your in yu recovery ti see if youfind a fail or error.
7.jpg
8.jpg
the
 
I have always benn successful un brick a Samsung I have owned with one exception and that was DM-Verity,DRK and EFS fail all together. Like a Mike Tyson uper cut TKO Hope you don't see any of those in you device recovery
 
Decided to try this on my windows 8 laptop, got this:
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 136 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> Complete(Write) operation failed.
 
Decided to try this on my windows 8 laptop, got this:
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 136 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> Complete(Write) operation failed.

I noticed that on your other PC the odin process got further, so I'm gonna tell you what I told someone else in a similar situation about 5 years ago which got them sorted...

This seems like a windows issue with drivers or .net.
  1. Go back to the windows 7 PC.
  2. Uninstall the samsung drivers and odin then reboot your PC.
  3. Update the windows ".net framework" https://dotnet.microsoft.com/download/dotnet-framework
  4. Reboot your PC.
  5. Install the latest Samsung drivers for your device then reboot PC.
  6. Install the latest Odin then reboot PC.
  7. Now try again to flash the firmware.
Sorry for all the "rebooting", but windows isn't modular like linux and is quite finicky about this.

Most importantly, I don't know if this will work, but it's worth a shot. This is all I got for you and probably my last post (I'm a linux and motorola user).

Good luck :)
 
I noticed that on your other PC the odin process got further, so I'm gonna tell you what I told someone else in a similar situation about 5 years ago which got them sorted...

This seems like a windows issue with drivers or .net.
  1. Go back to the windows 7 PC.
  2. Uninstall the samsung drivers and odin then reboot your PC.
  3. Update the windows ".net framework" https://dotnet.microsoft.com/download/dotnet-framework
  4. Reboot your PC.
  5. Install the latest Samsung drivers for your device then reboot PC.
  6. Install the latest Odin then reboot PC.
  7. Now try again to flash the firmware.
Sorry for all the "rebooting", but windows isn't modular like linux and is quite finicky about this.

Most importantly, I don't know if this will work, but it's worth a shot. This is all I got for you and probably my last post (I'm a linux and motorola user).

Good luck :)
Did it, currently stuck here:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 2715 M
<ID:0/003> SetupConnection..
 
Back
Top Bottom