TheTrustedComputer (Ryan Calculator) | FIX PLEASE! ZTE Source N9511 Encryption Unsuccessful message [READ DESCRIPTION FIRST] @TheTrustedComputer | Uploaded 9 years ago | Updated 2 hours ago
Things I tried the following:
-Factory resetted phone from stock recovery
-Wiped cache from stock recovery
-Flashed stock ROM(1) from stock recovery
-Booted phone into FTM(2) mode for adb to operate
-Unlocked OEM(3) bootloader
-Ran adb reboot-bootloader to fastboot
-Booted phone into CWM(4)/PhilZ(5) recovery and formatted
-Wiped Dalvik from CWM/PhilZ
-Flashed via CWM and PhilZ, fastboot, and adb sideload
-Prior to the brick, the phone was rooted

Acronyms you may not know:
1. Read-only memory
2. Field test mode
3. Original equipment manufacturer
4. ClockWorkMod
5. PhilZ Touch Recovery by Phil3759

Nothing seem to work for me, even with the proper ZTE and Google drivers installed. Neither fastboot nor the custom recovery ROMs can flash the stock ROM to the phone's internal memory. Erasing it will simply not work on fastboot. It sort of does format the phone using recovery ROMs, but insignificant from what I see; it still displays the "Encryption Unsuccessful" message after rebooting.

When I try to erase or flash any data to the phone using fastboot, it will not do anything. It will just stop at "writing 'partition'", "erasing 'partition'" and hangs there. I can use Ctrl+C to abort execution, however, and experiment with other fastboot commands. "fastboot oem unlock" and "fastboot boot recovery.img" ran fine without any problems.

Onto the recovery menu. I can reformat (but really doesn't I think) the phone using said options on CWM and PhilZ, but here is the catch: when I try to install stock ROM, it will fail saying "some symlinks failed" with a status of 7. I am pretty sure this is not an assert-related issue because what am I installing is the correct ROM for the phone. Yet "Encryption Unsuccessful" shows up without a single sign of the phone being restored.

Oh by the way, CWM has slightly glitchy graphics when booted (screen jumps when selecting a menu). CWM members knew about this bug and was patched on some phones. On the other hand, PhilZ is more stable and user-friendly; it does not jump screens despite being built off from CWM. Unfortunately, PhilZ is no longer being developed by the author and therefore abandoned.

If anyone can fix the problem for me, and if my phone successfully boots up to Android, I will award you a huge Internet cookie; I have been figuring it out myself for months now. Please answer me; do not ask silly questions. You will be ignored otherwise. Thank you.

UPDATE #1: Since my sister on my dad's plan owns the same phone as me, I tried to make a backup of her current state of her working phone. Upon completion, I took the SD card from her phone out and inserted it to my phone. By using fastboot to boot into either ClockWorkMod or PhilZ recovery to restore it, fails on restoring /system. Mounting /data won't work either, sadly. Gosh, how many unsuccessful attempts I've made!