Indeed mate !B09 ?
Just out today : http://www.ztedevice.com/support/detail?id=FA568879D9C14D719385E6F8CFB6A514
@g0dzstar : Did you update and in which country did it apply for you pls ?
Can you give the changelogs perhaps ?
Thnx
Last edited:
Indeed mate !B09 ?
Will update and test. Thnx :good:Hello,
Just to mention that TWRP 3.2.0-0 has been released and available for our Axon 7: https://twrp.me/site/update/2017/12/01/twrp-3.2.0-0-released.html
Download page for Axon 7: https://twrp.me/zte/zteaxon7.html
I'll always use my adapted B15 with TWRP 3.1.1.0 in it. Does the same. Had no problem so far.Now that a new version of TWRP is out, I'll ask again: What is the point of having the Universal Bootloader flash that old TWRP version? Is it necessary for something? Does it really need to even flash TWRP, given that you'll flash it from TWRP, probably a new version? This just complicates things for everyone as it is.
What would be nice is that the Universal Bootloader failed if it detected that your TWRP is anything older than 3.1.1 (or 3.2) prompting you to update if possible.
@Unjustified Dev I'd only like to know. Hope you read this
Im gonna check that too.Good to mention. Perhaps you open a topic about thatHello all,
ATTENTION: I used new TWRP 3.2.0-0 to backup, all is OK. But I got problem using it to restore : there is no progression messages, and the animated progression bar remains empty. I waited for > 30 minutes then gave up. Fortunately by constantly pressing Power off button I succeeded to power off then restart the phone, then within the 5 seconds where you can choose normal boot, recovery, fastboot etc... I can enter recovery (TWRP). Then I reflash the old good TWRP 3.1.1-0, rebooto recovery, and fortunately it can handle the backup maded by TWRP 3.2.0-0 ! By the way, the cheksum (digest) used by TWRP 3.2.0-0 is sha2 instead of md5 as used by TWRP 3.1.1-0.
Currently I did not recommend using TWRP 3.2.0-0.
Better open up a topic perhaps? Hope you get it working. Question though : on 3110, did those steps work ok?@raystef66
Thank you for your report on TWRP 3.2.0-0. My phone needs password after entering TWRP since I set security with finger print (which requires setting PIN password).. The decrypting phase is OK, and all partitions are mounted by TWRP. But at start of restore, I got my problem as described. Maybe another user which password-protected phone could try to check again?
You don't need to select pin on startup to use a pattern and the fingerprint. Just saying.@raystef66
Thank you for your report on TWRP 3.2.0-0. My phone needs password after entering TWRP since I set security with finger print (which requires setting PIN password).. The decrypting phase is OK, and all partitions are mounted by TWRP. But at start of restore, I got my problem as described. Maybe another user which password-protected phone could try to check again?
Thnx @joaste ! Good find :good: Very short after the other...By the way, just saw that twrp 3.2.1 is out.
BootstackShould I first flash the bootstack or stock rom?
And magisk instead of supersu?
Coming from a custom rom.