Good. That's what I hate about those programs, they depend a lot on the state of Windows and your deviceYes using Miflash
A few reboots of phone and laptop and it flashed.
Good. That's what I hate about those programs, they depend a lot on the state of Windows and your deviceYes using Miflash
A few reboots of phone and laptop and it flashed.
i don't know anything about DFU or debricking, this is a guide to install TWRP on a nice healthy Nougat.hey i have in windows 10 handset dfu mode i cant get usb drivers to work
I've had a new problem with this method, after updating to B02. MiFlash seems to flash the fastboot image but it doesn't work. I assume that your phone just booted to the system when axon7toolkit said it didn't find fastboot... that's what happens in my phoneI managed to flash correctly using miflash. But when I tried to install twrp using axon7tool, it says that my fastboot device is not connected. Any advice?
Look, I've done it 4 times already, no problems whatsoever. A lot of people have also tried. But the only thing you have to be aware of is that the method in the OP probably won't work if you're on Nougat B02. If that's the case you'll have to forget Fastboot for now and flash the recovery directly with axon7tool, which I don't like because axon7tool is too finicky and may or may not work@Choose an username...
As far as I know the partition layout on the A2017G is different from the one on the A2017U.
Is this still considered safe? I would do it only to get fastboot running as I am already unlocked.
Thanks for the clarification.Look, I've done it 4 times already, no problems whatsoever. A lot of people have also tried. But the only thing you have to be aware of is that the method in the OP probably won't work if you're on Nougat B02. If that's the case you'll have to forget Fastboot for now and flash the recovery directly with axon7tool, which I don't like because axon7tool is too finicky and may or may not work
This method will not unlock your bootloader (i think), it is just to get Fastboot. But you won't get it on B02
Well I flashed the fastboot package like an hour ago, and I couldn't access fastboot. Pity that I did a full reinstall. I might still have fastboot if i didn'tThanks for the clarification.
In regards to B02, fastboot partition is not touched by tje update, so maybe you can still have fastboot after upgrading to B02 when applied at B01. I agree with you that it would be a bit risky to apply it on B02.
That's very unfortunate...Well I flashed the fastboot package like an hour ago, and I couldn't access fastboot. Pity that I did a full reinstall. I might still have fastboot if i didn't
I don't know if it's risky though. Maybe backing up then restoring the fastboot partition would do the trick?
well saidThat's very unfortunate...
I'm not sure if this will solve it. It's a pitty that ZTE does everything to prevent us from doing what XDA users are supposed to do, fastbooting the s*** out of our devices.![]()
What version of the ROM do you currently have?Flashed with Miflash, but still no Fastboot![]()
Unfortunately, it seems that this is no longer working on V1.2.0B021.2.0B02 stock
You would have to downgrade to V1.2.0B01This method will not unlock your bootloader (i think), it is just to get Fastboot. But you won't get it on B02
[..]
apply_patch_check("EMMC:/dev/block/bootdevice/by-name/aboot:755496:0ff4ba5f5c81bc3a61e6a36992fd06dfea2f1c08:763772:5e2c84f772691ae91f258228910c3f6dbeb21950", "0ff4ba5f5c81bc3a61e6a36992fd06dfea2f1c08", "5e2c84f772691ae91f258228910c3f6dbeb21950") || abort("E3005: \"EMMC:/dev/block/bootdevice/by-name/aboot:755496:0ff4ba5f5c81bc3a61e6a36992fd06dfea2f1c08:763772:5e2c84f772691ae91f258228910c3f6dbeb21950\" has unexpected contents
[..]
ui_print("Patching emmc_appsboot.mbn image...");
apply_patch("EMMC:/dev/block/bootdevice/by-name/aboot:755496:0ff4ba5f5c81bc3a61e6a36992fd06dfea2f1c08:763772:5e2c84f772691ae91f258228910c3f6dbeb21950",
"-", 5e2c84f772691ae91f258228910c3f6dbeb21950, 763772,
0ff4ba5f5c81bc3a61e6a36992fd06dfea2f1c08,
package_extract_file("patch/emmc_appsboot.mbn.p")) ||
abort("E3008: Failed to apply patch to EMMC:/dev/block/bootdevice/by-name/aboot:755496:0ff4ba5f5c81bc3a61e6a36992fd06dfea2f1c08:763772:5e2c84f772691ae91f258228910c3f6dbeb21950");
[..]
Read the OP correctly, I added a method to get TWRP on your phone. You won't get Fastboot though1.2.0B02 stock
One could maybe fix it by flashing a different aboot image (like the one used to unlock the bootloader on MM).Read the OP correctly, I added a method to get TWRP on your phone. You won't get Fastboot though
Sorry that message was for the other guyOne could maybe fix it by flashing a different aboot image (like the one used to unlock the bootloader on MM).
Sure no problem.Sorry that message was for the other guy
I have 0 knowledge on coding. No idea how you can fix this. If someone fixes whatever there is to fix I'll update the guide