If you can get into Download Mode there is always a solution. I recommend you to download the original 4.3 MetroPCS GS4 M919NUVUEMK5 firmware from SamMobile, it's under SGH-M919N and flash it thru Odin. You will get the stock MetroPCS 4.3
i did that yesterday,
now i tried to flash the M919NUVUEMK5_M919NTMBEMK5_M919NUVUEMK5_HOME.tar.md5 and it only goes this far then fails now. ooops hehe
<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> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
-------------------------------------------------------------
i noticed in download mode it says eMac burst mode enabled??????
And I also notice underneath that in red it says 'start (224/1440) sw. Rev. Check fail, fused 4, binary 1'
i read this just now
"a Qfuse gets blown while the bootloader is updated, you cannot go back to a previous build, even if forcefully flashed."
this line
SW REV. CHECK FAIL : fused:2, Binary: 1
states that your binary is flagged for a fuse counter set to 1 but your fuse counter is currently set to 2 so the verification fails.
In fact, from what I saw in the bootloader assembly, it works like this:
- Upon updating, the current (old) bootloader will verify the signature of the new bootloader binaries
- If the counter matches the one of the current device, the check passes and the bootloader gets written.
- If the counter is lower than the one of the current device, the check fails and the update process is halted, if the counter is higher than the one of the current handset, Qfuses are blown to match the ones of the new binary and the new binary is written.
although i dont really understand it
i did just read this
"run debrick image on a micro SD card. From there, I was able to restore the bootloader."
how did you update yours to 4.4? while avoiding all this problem?
Upvote
0