I just bought a used Note 4 DE and I'm having issues getting it straight. Firstly let me say that the previous owner did inform me that he had a flashing issue himself at one point but he sent the phone back to Samsung and they reflashed his phone back to a DE but In doing so, Samsung flashed 5.0.1 onto the device. I was trying to get to a point where I could back up the aboot so I flashed v2.8.7.0 of TWRP. For some reason The phone got stuck in a boot loop after I flashed TWRP and I couldn't do anything but boot into download mode. Heres where I think I messed up because I then used odin to try and flash N910VVRU2BOG5_StockRestore.tar.md5 which is the safe upgrade found in this thread http://ift.tt/1KYjedJ Odin makes it all the way though the flashing process then at the very last minute fails. This is what Odin says:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin engine v(ID:3.1100)..
<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> NON-HLOS.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> boot.img
<ID:0/007> cache.img.ext4
<ID:0/007> modem.bin
<ID:0/007> recovery.img
<ID:0/007> rpm.mbn
<ID:0/007> sbl1.mbn
<ID:0/007> sdi.mbn
<ID:0/007> system.img.ext4
<ID:0/007> tz.mbn
<ID:0/007> RQT_CLOSE !!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Then right underneath where it says Mode: Developer on the phones screen in download mode I get this message:
SW REV CHECK FAIL: (tz) fused 2 > Binary 1
And underneath that I get a message that says:
Software Update Failed
Your device didn't update successfully. Use Verizon Software Repair Assistant on a computer to repair your device and complete the update.
I've searched XDA, Google and numerous threads were people bring up similar errors but I can't find any threads where someone as had a happy resolution wit these errors especially wit a DE Note 4. Can someone please tell me how to at least get back to the initial set up screen for the device? I can get into download mode and my device still says Developer where the Mode is labeled on the download screen so I am hoping I can get back up and running with the right help. Thanks.
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin engine v(ID:3.1100)..
<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> NON-HLOS.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> boot.img
<ID:0/007> cache.img.ext4
<ID:0/007> modem.bin
<ID:0/007> recovery.img
<ID:0/007> rpm.mbn
<ID:0/007> sbl1.mbn
<ID:0/007> sdi.mbn
<ID:0/007> system.img.ext4
<ID:0/007> tz.mbn
<ID:0/007> RQT_CLOSE !!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Then right underneath where it says Mode: Developer on the phones screen in download mode I get this message:
SW REV CHECK FAIL: (tz) fused 2 > Binary 1
And underneath that I get a message that says:
Software Update Failed
Your device didn't update successfully. Use Verizon Software Repair Assistant on a computer to repair your device and complete the update.
I've searched XDA, Google and numerous threads were people bring up similar errors but I can't find any threads where someone as had a happy resolution wit these errors especially wit a DE Note 4. Can someone please tell me how to at least get back to the initial set up screen for the device? I can get into download mode and my device still says Developer where the Mode is labeled on the download screen so I am hoping I can get back up and running with the right help. Thanks.
from xda-developers http://ift.tt/1TgpZ3I
via IFTTT
No comments:
Post a Comment