spontaneous bricking?

[callmejoe9]

using a note 2 today and it just decided to reboot on its own, and then never got passed the splash screen. i have twrp recovery installed. booted into recovery and couldnt do anything. couldn't mount anything, wipe anything, restore anything. all storage showed 0MB. kept giving errors that it couldn't mount any partitions (cache, system, etc.) something with error 16.

i tried flashing a stock rom with odin. that failed. just seems like it is totally corrupted and nothing can be written to it.

how does something like that happen just randomly???? any way back from the dead?

 

[audit13]

Is the phone an AT&T Note 2? Where did you find the stock ROM for Odin?

 

[callmejoe9]

Is the phone an AT&T Note 2? Where did you find the stock ROM for Odin?

yes AT&T note 2.

the stock rom i got from a link on this forum. i tried this one first, I317-UCUCNJ2-Stock.tar.md5, then this one I317-UCUCNE5-Stock.tar.md5

also tried re-partitioning after with this pit file, i317.pit

i tried using Odin v1.85 and Odin 3.07

 

[audit13]

What is the error message in the Odin log?

Tried using different usb cables and usb ports with Odin?

 

[callmejoe9]

What is the error message in the Odin log?

Tried using different usb cables and usb ports with Odin?

just tried it, same result. odin log? you mean the message output? here it is for when i tried with and without PIT file

[B]No pit file[/B]
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I317-UCUCNE5-Stock.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> boot.img
<ID:0/008> NAND Write Start!! 
<ID:0/008> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)

[B]With pit file[/B]
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I317-UCUCNE5-Stock.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..

 

[audit13]

Without the pit file, it's failing with the boot.img file and this may be fixed by using an oem Samsung cable or different usb 2.0 port. It could also be that the bootloader in the rom is not for the phone or the phone's current bootloader is newer than the bootloader being fished.

 

[callmejoe9]

Without the pit file, it's failing with the boot.img file and this may be fixed by using an oem Samsung cable or different usb 2.0 port. It could also be that the bootloader in the rom is not for the phone or the phone's current bootloader is newer than the bootloader being fished.

tried different cables and ports and another ROM, I317UCAMA4.. still fails.

i think it's a lost cause.

 

[audit13]

I'm sure you are correct but this phone shows up as an sgh-i317 in download mode?

Where did you get the ROMs? AT&T never released an Odin-flashable ROM after 4.1.2.

 

[callmejoe9]

I'm sure you are correct but this phone shows up as an sgh-i317 in download mode?

Where did you get the ROMs? AT&T never released an Odin-flashable ROM after 4.1.2.

yes it shows as sgh-i317 when in download mode

roms were gotten from wherever one gets roms i guess