jeudi 28 juillet 2016

Need some help here, please... flash attempt may have bricked SM-930U

I installed the Samsung USB drivers and Odin (v3.11.1). I then placed the phone in download mode, launched Odin, and connected the USB cable. I was greeted on the phone's display with:

Quote:

ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-G930U
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
FAP LOCK: ON
WARRANTY VOID: 0X0
QUALCOM SECUREBOOT: ENABLE
AP SWREV: B2(2,1,1,1,1) K1 S1
SECURE DOWNLOAD : EBABLE
The ID:COM indicator on the Odin screen turned blue. I navigated to the unzipped PDA/AP file (extracted from the updato.com zip). I made sure that only the Auto Reboot and F. Reset Time options were check marked. I then clicked the start button.

Below is the progressive log from the Odin screen:

Quote:

<ID:0/008> 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..
<ID:0/008> Odin engine v(ID:3.1101)..
<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> SingleDownload.
<ID:0/008> boot.img
<ID:0/008> NAND Write Start!!
<ID:0/008> recovery.img
<ID:0/008> system.img.ext4
<ID:0/008> FAIL! (Ext4)
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
After the fail, I noticed that the following lines had appended to the phone's download mode screen in bright red:

Quote:

Volume Size is too big 1152000 < 1300480
ODIN Invalid ext4 image
What did I do wrong? Is it recoverable? I can't seem to power the phone off now. Please help. Thanks.


from xda-developers http://ift.tt/2aAGmJG
via IFTTT

Aucun commentaire:

Enregistrer un commentaire