hey guys, just thinking about the situation when Zuk will close the doors. is there any way to re-use an existing unlocker image from a different serial number? or any way to patch the serial into an existing image?
I used hex-editting capable note pad plus.
You can easily change the serial no. since it was shown as ASCII. But I have no idea how to change or what to replace in the image part. So I chaged the serial no., saved the file and loaded to the phone. It did not take it.
I also shared my image file here so that anyone could try it but no succes story.
The reason I did it was I need to unlock two Zuk phones and Zuk allows only one image request per account per 30 days. I end up have two Zuk accounts.
You are wiring the image via ADB. As I recalled, it did not load it (write it) at all. It did not destory my bootlaoder though. If it is a correct image you would get the confimation message within 5 sec.
You could edit the file but it will not work. You can check any message in this thread.
The site is down sometime.
Try this way again.
Appernetly, you have to be login to the passport.zuk.com while you are requesting the code.
goto https://passport.zuk.com/wauthen3/preLogin and create the account using your email. Get email confirmation and login to that account.
Open the new tab and goto http://developer.zuk.com/bootloader_2 and request the unlock code using the email that you registered with the passport.zuk.com.
Unsuccessfully tried to flash the my Zuk 2 Pro Z2121 and seem to have hard bricked the phone. After pouring through videos, websites, and forums, I am at a total loss. Sorry if the answer is already in this thread, but I just can't seem to find the solution.
Phone is completely unresponsive, but seems stuck in edl 9008 mode. No screen activity. Will not boot. No LED or vibration. Power button seems to briefly disconnect the 9008 port before automatically reconnecting to the PC. Only indicator is through the PC. QFIL, MiFlash, and Windows Device Manager sees the disconnect & reconnect. ADB does not see the device from the command prompt.
What I've Done
Been messing around with this for awhile, trying everything, so I may miss something here. I'll try to work backwards from most recent efforts to earliest.
Flash Z2121_CN_OPEN_USER_Q01002.1_M_ZUI_1.9.104_ST_160617_qpst\prog_ufs_firehose_8996_ddr.elf with MiFlash 2016.03.30.0 (64-bit). Operation completed successfully, but no change. Trying the same thing with QFIL 18.104.22.168 results in ownload Fail: FireHose Fail: FHLoader Fail: Process fail". MiFlash 2017.4.25.0 quickly generates errors. With 2 out of 3 not working, I wonder whether MiFlash 2016.03.30.0 is actually succeeding?
Using MiFlash 2016.03.30.0, flashing Zui 2.5.462 after using deep flash cable is what seemed to HARD BRICK the phone. It's at after this point that I put Win 10 in developer mode. Note that I was having difficulty flashing at all until I read that time is a factor, suggesting that the port only remains "open" briefly. While MiFlash indicated the operation was successful, the phone did not reboot and became unresponsive. Seems like it is locked in 9008 mode. Device Manager shows Qualcomm HS-USB QDLoader 9008 (COM5), currently a permanent state.
Failing to flash over and over I followed the SDfuse method. BRICKed! Phone would reboot showing the Zuk logo and wouldn't turn off. Once the battery died I was able to move on to the above with a deep flash cable.
Flashed Zui 2.5.462 using MiFlash 2017.4.25.0 without putting PC in Developer mode to no effect. Wouldn't take, didn't affect the operation of the loaded OS & ROM. Didn't follow all the steps of the tutorial properly, but the phone was fine, just no update.
Sources QFIL ROM Flashing Guide and QFIL ROM & Unbrick Guide were sources for moving through the above. Not exclusively though. I've read through this forum, videos, etc..
To have the latest version of Zui and Android 7.0 with ota support. However, I am ready to lower my expectations to simply having a functioning phone and having not through money out the window.