• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

Blade A3 Prime (Visible)

Search This thread

tlopez51

Senior Member
Jan 25, 2011
157
67
So I was able to get SPFT working with that tutorial. Thank you. I attempted a readback of boot.img using your instructions. I am receiving an error:

ERROR : STATUS_BROM_CMD_SEND_DA_FAIL (-1073348605) , MSP ERROE CODE : 0x00.

no hint is given

Terminal gives this relevant output (unsure how to format correctly on this forum?)

--------------------------------------

Total wait time = -1614741745.000000
USB port is obtained. path name(/dev/ttyACM0), port name(/dev/ttyACM0)
USB port detected: /dev/ttyACM0
BROM connected
Downloading & Connecting to DA...
connect DA end stage: 2, enable DRAM in 1st DA: 0
Failed to Connect DA: STATUS_BROM_CMD_SEND_DA_FAIL(-1073348605)
Disconnect!
BROM Exception! ( ERROR : STATUS_BROM_CMD_SEND_DA_FAIL (-1073348605) , MSP ERROE CODE : 0x00.


[HINT]:
)((ConnectDA,../../../flashtool/Conn/Connection.cpp,146))
Connecting to BROM...
Scanning USB port...
Search usb, timeout set as 3600000 ms

--------------------------------------

In addition, when I plug the battery-less phone into the pc, the phone power cycles showing a dotted, red battery icon with a warning sign. SPFT throws that error after about 15 seconds. I tried both user and sudo.

I put the battery in, and plugged USB in without turning the phone on and attempted a readback as well. No dice there. Nothing happened after 5 minutes of waiting.

**EDIT**
I did some googling, and found https://forum.xda-developers.com/t/...send_da_fail-0xc0060003.3707811/post-74617876

This post suggested I hold the volume down key and then plug in the usb. I now receive a different error:

---------------------------------------
Total wait time = -1614743845.000000
USB port is obtained. path name(/dev/ttyACM0), port name(/dev/ttyACM0)
USB port detected: /dev/ttyACM0
BROM connected
Downloading & Connecting to DA...
connect DA end stage: 2, enable DRAM in 1st DA: 0
Failed to Connect DA: STATUS_PRELOADER_INVALID(-1073545212)
Disconnect!
BROM Exception! ( ERROR : STATUS_PRELOADER_INVALID (-1073545212) , MSP ERROE CODE : 0x00.

The Preloader file format is invalid!
[HINT]:
Please retry another official load.)((ConnectDA,../../../flashtool/Conn/Connection.cpp,146))
----------------------------------------------------------------

I tried googling all these issues, and couldn't figure out what to do next.

What's the next step?
I am late responding on this one as I got onboard later in the game and struggled to sort out all of the errors I've gotten using SPFT. I too am on Linux most of the time and for some other applications on Windows. Each has their vices. However, I believe the error you are getting has to do with the USB port on the pc side. I could be it mat not supply enough power or power on the USB line is not stable and clean, and so on. I've run into this before and re-connecting to another USB port has cleared this up. I'd spent many hours chasing my tail on this one and it was that simple. Some have even suggested getting a separate USB hub and that seems to work too. Hope that works out.
 
Last edited:

tlopez51

Senior Member
Jan 25, 2011
157
67
A word of caution!
Before venturing on to root your Blade A3 Prime you must make a FULL NANDroid backup for each phone you are wanting to root. If you FAIL to do this and on the reboot the device gets stuck in an endless bootloop then the only recovery method is to do a Format All + Download in SPFT. Doing so has the potential to wipe clean the IMEI info which is stored in the nvdata file and your phone will no longer work on any cellular network!

Presently there aren't any utilities capable of restoring the IMEI on this device as it is a read only file system which as a result makes rooting problematic on the stock firmware. You can more easily get root on this phone by loading a GSI image but you will not be able to re-write the IMEI even though you are root because of the encryption used to hide it.
 
Last edited:

tlopez51

Senior Member
Jan 25, 2011
157
67
Good News is here after all!
The newly released Magisk f822ca5b (23001) in the Canary branch provides us with some major fixes and as a result it is now able to root the Blade A3 Prime. Just a few short words of caution before rushing in to root this device.

Read thread #282 first!
Remember you should always have a FULL NANDroid backup for your device in case you run into trouble and then have to resort to a Format All + Download in SPFT to recover but then you run the bigger risk of erasing the IMEI info. Note that you can safely bring back the IMEI for your device using SPFT only if you have a backup of the nvdata file from the FULL NANDroid backup. You have been warned!

What I know is verified and works:
  1. Unlock the Bootloader in Developers options and turn ON USB debugging.
  2. Install Magisk and patch a copy of the boot-visible-oss-nomagisk.img attached below. Next copy the Magisk patched boot-oss-nomagisk.img to your Desktop.
  3. Do a adb reboot bootloader using a terminal emulator (cmd prompt for windows) on the pc. Watch for any pop ups asking for permissions on the phone.
  4. Make sure you are in => FASTBOOT mode . . . (lower left corner of the screen on device) once the phone has rebooted to the bootloader then on the pc type fastboot flashing unlock followed by a fastboot flashing unlock critical. Press enter plus VOL UP after you type each command on the phone to accept.
  5. Next flash the Magisk patched boot-visible-oss-nomagisk.img (attached): fastboot --disable-verity --disable-verification flash boot <PATH-TO-BOOT-IMAGE-FILE-HERE>
  6. Flash vbmeta_Mod-MT6761-10.img to vbmeta (attached): fastboot --disable-verity --disable-verification --skip-reboot flash vbmeta <PATH-TO-BOOT-IMAGE-FILE-HERE>
  7. Lastly do a fastboot reboot.
 

Attachments

  • vbmeta_Mod-MT6761-10.img
    4 KB · Views: 34
  • Screenshot_20210512_170316.png
    Screenshot_20210512_170316.png
    144.8 KB · Views: 29
  • Screenshot_20210512_170406.png
    Screenshot_20210512_170406.png
    107.4 KB · Views: 30
  • boot-visible-oss-nomagisk.img
    17.4 MB · Views: 13
Last edited:
  • Like
Reactions: luridphantom

tlopez51

Senior Member
Jan 25, 2011
157
67
Read thread #282 and #283 first!
Attached is a Magisk patched boot-visible-oss-nomagisk.img that you can flash along with vbmeta_Mod-MT6761-10.img to get you root on the Visible variant in the event you do not know how to use Magisk or may want to shorten the root process to one less step. Remember you need to unlock the bootloader in the Developer section on your phone and to do a fastboot flashing unlock and fastboot flashing unlock critical while the device is booted to the bootloader in => FASTBOOT mode . . . and before you can flash any file.

Note: Do not use the attached file to root the Yahoo variant !
 

Attachments

  • magisk_patched-23001_CiVIi.img
    17.6 MB · Views: 3
Last edited:

itsfitts

Member
Jun 20, 2020
8
1
Motorola Edge (2021)
I hate to be this guy, but I installed the zte software and drivers that are given when selecting system update usb mode, and I cannot get fastboot to recognize the device. Adb works fine, but when entering fastboot mode with "adb reboot bootloader " any fastboot command such as "fastboot flashing unlock" reports waiting for device. I did update drivers and tried uninstalling/reinstalling them. Can someone advise me what I'm doing wrong please?

Bootloader unlock is enabled in dev settings btw

Edited for: typo
 

drewmol

New member
Dec 11, 2018
2
1
New here, hello. Thanks for all the hard work! I just tried the above (flashing magisk_patched-23001_7pq6C.img and vbmeta_Mod-MT6761-10.img) in fastboot and got to bootloop (Visable stock).
In the process of formatAll+download back to visable variant stock from this thread.

For those with issues with SPTF I've had some success (on Windows) by holding the volume down button and unplugging/replugging the device or restarting the download/readback operations so if your struggling try that. Also using a usb port with enough power (or just a different one).
 

luridphantom

Senior Member
Apr 4, 2021
123
19
@tlopez51 do we need to actually flash your magisk patched image to boot or can we use fastboot boot first? just curious if you've tried it since the images all boot unrooted for me. trying to be cautious because i'm not sure how to get a nandroid backup without recovery
 

luridphantom

Senior Member
Apr 4, 2021
123
19
update: am using a backed up copy of my boot.img to keep restoring my phone through spft because no matter what i try, even with magisk canary, my visible zte a3 prime keeps bootlooping itself after the vbmeta/boot flash
 

Jerry12798

Senior Member
update: am using a backed up copy of my boot.img to keep restoring my phone through spft because no matter what i try, even with magisk canary, my visible zte a3 prime keeps bootlooping itself after the vbmeta/boot flash
We're in the same boat.. me and a few others are experiencing the same issue. Not sure what the issue is either

Basically as soon as I posted this I actually booted with root. I've assisted the others that was attempting this with me but they've not had success yet. A few is still bootlooping and another says she isn't bootlooping but can't boot into Android.

I'm now going to attempt trying that GSI. I didn't make a backup before I attempted rooting this device unfortunately.. now I've erased the IMEI and not am not completely sure how I could regain it.
 
Last edited:

luridphantom

Senior Member
Apr 4, 2021
123
19
We're in the same boat.. me and a few others are experiencing the same issue. Not sure what the issue is either

Basically as soon as I posted this I actually booted with root. I've assisted the others that was attempting this with me but they've not had success yet. A few is still bootlooping and another says she isn't bootlooping but can't boot into Android.

I'm now going to attempt trying that GSI. I didn't make a backup before I attempted rooting this device unfortunately.. now I've erased the IMEI and not am not completely sure how I could regain it.
what's your steps to root your device? i've already unlocked my bootloader but am not sure which build/device everyone is using. my phone is the visible variant

for restoring the imei, i'm not sure if it will 100% work but hovatek forum has a guide for any format + download restores. i've been super careful to only use download only when i reflash my boot img after bootloops
 

Jerry12798

Senior Member
what's your steps to root your device? i've already unlocked my bootloader but am not sure which build/device everyone is using. my phone is the visible variant

for restoring the imei, i'm not sure if it will 100% work but hovatek forum has a guide for any format + download restores. i've been super careful to only use download only when i reflash my boot img after bootloops
My device is originally the Visible variant (Z5157V). I just flash to the stock Yahoo variant (Z5157Y) and then do the steps below. I'm using the modified magisk image @tlopez51 sent when flashing boot.

1) Enable Developer Options

2) Enable OEM Unlock & USB Debugging in Developer Options

3) Boot to Bootloader
adb reboot bootloader

4) Ensure Device is Recognized by PC
fastboot devices

5) Proceed with Unlocking
(Press Volume Up After Each Command to Confirm)
fastboot flashing unlock
fastboot flashing unlock_critical

6) Reboot Device
fastboot reboot

7) Enable USB Debugging Again
(OEM Unlock Should be Grayed Out & Enabled)

8) Boot to Bootloader
adb reboot bootloader

9) Flash VBmeta
fastboot --disable-verity --disable-verification flash vbmeta <PATH-TO-VBMETA-FILE-HERE>

10) Flash Modded Boot Image
fastboot --disable-verity --disable-verification flash boot <PATH-TO-BOOT-IMAGE-FILE-HERE>
 
Last edited:
  • Like
Reactions: luridphantom

luridphantom

Senior Member
Apr 4, 2021
123
19
oh you had to flash the yahoo variant first, thats pretty much the only step i didn't take. the oss boot file from tlopez doesn't work with the visible variant for some reason

guess i need to readback my entire rom first before i flash the yahoo build and root my device. were the others who were bootlooping using visible or yahoo?
 

Jerry12798

Senior Member
oh you had to flash the yahoo variant first, thats pretty much the only step i didn't take. the oss boot file from tlopez doesn't work with the visible variant for some reason

guess i need to readback my entire rom first before i flash the yahoo build and root my device. were the others who were bootlooping using visible or yahoo?
They was GABB and Visible. We just flash to stock Yahoo and after that it all went good aside from some lost IMEIs. No one is bootlooping anymore. I'd presume you'd just need to have the NANDroid backup beforehand so you can get IMEI and other things back once you flash to stock Yahoo or after you flash the patched boot image
 

Jerry12798

Senior Member
seems like its a choice between losing my IMEIs vs root since for some reason the visible builds are unrootable
Well if you properly backed up before rooting you should be able to recover the IMEI. I've yet to find anyway to get the IMEI back without having the data from the NANDroid backup. Unfortunately since I didn't backup myself, I too am not able to use cellular on my device. Hopefully someone will soon have a method to recover or rewrite our IMEIs
 
Update: MediaTek Man @lopestom sent me instructions for how to properly flash GSI's on Android 10 devices. This was the message he sent to me directly, in response to the instructions I posted before:

Maybe he need try flashing in the system_a partition for test.
When have vbmeta mod flashed so may be not need flash that again. Only if have error flashing GSI.img so try reflashing vbmeta too.


I wrote this for me and other users A10 a time ago:

1. You need know the difference about fastboot and FASTBOOTD in your device!!
Your device has bootloader mode: recovery - fastboot - reboot (system)
Stock recovery has very options: reboot system - reboot to bootloader - wipe - Enter fastboot - ...
reboot to bootloader => normal fastboot
Enter fastboot => FASTBOOTD
FASTBOOTD => some options

2. Device in fastboot
fastboot --disable-verification flash vbmeta vbmeta.img

3. fastboot -w

4. fastboot reboot fastboot
(you MUST be at the FASTBOOTD menu now. If not, you will not be able to flash the GSI successfully)

5. fastboot erase system
or
fastboot delete-logical-partition system

6. fastboot delete-logical-partition product
- deletes the product partition, allowing a larger system partition

I not need resize-logical-partition product. But if you want:
You will need a larger system partition to flash a GSI. There are 2 ways to achieve this
6A. fastboot resize-logical-partition product 509344768
6B. fastboot resize-logical-partition system 3089272064 or 3889272064
resizes product and system partitions. This gives you about 3GB of system partitions. You can adjust or arrive at your own numbers if you want different sizes.

7. fastboot --disable-verity --disable-verification flash system GSI.img

8. fastboot -w
for confirm great & fast start GSI

9. fastboot reboot bootloader
9A. fastboot erase userdata
for confirm and boot clean

10. Reboot to system
fastboot reboot
Enjoy
!

EDIT: He also sent me something else called Treble Toolkit, that's a nice GUI for doing a lot of Treble related stuff. Maybe this can help us too:

Thank you for sharing my work!
 

tlopez51

Senior Member
Jan 25, 2011
157
67
I hate to be this guy, but I installed the zte software and drivers that are given when selecting system update usb mode, and I cannot get fastboot to recognize the device. Adb works fine, but when entering fastboot mode with "adb reboot bootloader " any fastboot command such as "fastboot flashing unlock" reports waiting for device. I did update drivers and tried uninstalling/reinstalling them. Can someone advise me what I'm doing wrong please?

Bootloader unlock is enabled in dev settings btw

Edited for: typo

The phone needs to be in bootloader mode to use the fastboot commands such as "fastboot flashing unlock".
At the => FASTBOOT mode screen on the phone do a fastboot flashing unlock. Press VOL UP on the phone to accept.
 

tlopez51

Senior Member
Jan 25, 2011
157
67
New here, hello. Thanks for all the hard work! I just tried the above (flashing magisk_patched-23001_7pq6C.img and vbmeta_Mod-MT6761-10.img) in fastboot and got to bootloop (Visable stock).
In the process of formatAll+download back to visable variant stock from this thread.

For those with issues with SPTF I've had some success (on Windows) by holding the volume down button and unplugging/replugging the device or restarting the download/readback operations so if your struggling try that. Also using a usb port with enough power (or just a different one).

Flashing the phone's oem boot.img with Magisk will not work as outlined in my instructions. Instead, flash the boot-oss-nomagisk.img that is attached in thread #283 or can use the already patched one attached in thread #284.
 
Last edited:
  • Like
Reactions: Jerry12798

tlopez51

Senior Member
Jan 25, 2011
157
67
@tlopez51 do we need to actually flash your magisk patched image to boot or can we use fastboot boot first? just curious if you've tried it since the images all boot unrooted for me. trying to be cautious because i'm not sure how to get a nandroid backup without recovery

Do not use a copy of the phone's boot.img to patch with Magisk as it will render the phone in an endless bootloop on reboot. Instead, as per instructions, either patch a copy of the boot-oss-nomagisk.img with Magisk or use the already patched one I had attached to thread #284.
 
Last edited:
  • Like
Reactions: Jerry12798

tlopez51

Senior Member
Jan 25, 2011
157
67
what's your steps to root your device? i've already unlocked my bootloader but am not sure which build/device everyone is using. my phone is the visible variant

for restoring the imei, i'm not sure if it will 100% work but hovatek forum has a guide for any format + download restores. i've been super careful to only use download only when i reflash my boot img after bootloops

I've looked at Hovatek for a recovery method but nothing on his site works on the ZTE Blade A3 Prime. Reason is the phone's file system is read only so any attempts to recover the IMEI by software will not work and being the IMEI is stored in a file once that file is erased the IMEI is gone and can only be restored from a backup.
 
Last edited:
  • Like
Reactions: Jerry12798

Top Liked Posts

  • 1
    This is from the testing of ZTE_Z5157-BladeA3PrimeYahoo-TWRP-Test2.zip. Partially working after flashing the hacked boot_a.img and vbmeta files and then sending a --> [fastboot reboot fastboot] command allowed TRWP to get this far. Note on a reboot to android bluetooth no longer functions.

    Note also I had to do a complete wipe of the phone ie: "Download All + Format" in SPFT.
  • 1
    I'll try to flash the stuff to my phone now. Will flash TWRP to the boot slot now.

    EDIT: Flashed TWRP (to the boot slot) and vbmeta, it only creates bootloops. No luck.
    Okay guys. Let me explain:

    I don't have your device on hand for testing, let alone any A/B device (_a; _b).
    But at a future time I believe I will need to have a TWRP for the boot partition. I've been compiling the TWRP from Team Win sources for some time ago and it's neither hard nor easy. It depends a lot on the user experience on giving the correct information and how the device ROM was built.
    In the case with ZTE Blade/Yahoo, we clearly have the inclusion of company information and some particulars that make a big difference or will just be inconspicuous on something.

    The attached file contains version 3.5.2_10 boot_a.img which has been compiled from sources for anyone here to test.
    But I make a big WARNING! I cannot guarantee it will work.
    Backup everything you can before any test installation of the file!

    This is a second file I made. The first file (3.5.1_10) is with jasonmerc and I don't know the result. But I think it has a 99% chance of not starting. So I did this 3.5.2_10 to have a better chance of knowing.
    The TWRP3.5.2_10/boot_a.img file contains minimal information and file dependencies. Then anything can happen.

    Good luck and let me know the installation steps and the result.
    1
    I've tried flashing your image but get stuck at the TWRP splash screen so can't really see what is and isn't mounted. I've tried formatting userdata with the command in #402 but it didn't work so for now I just booted back into normal mode.. I was suprised none of my apps/data was gone when I booted back up since I did flash a new boot image
    Thanks Jerry... But let me know:
    1- What ROM in the device;

    2- Comands and files flashed;
    Unlocked device? with:
    Code:
    fastboot flashing unlock

    3- You can try formatting device with 3 options:
    i- removing google accounts, format data and the device reboot to stock recovery formating all;
    ii- you can reboot in the stock recovery and wipe cache & data;
    iii- using fastboot:
    Code:
    fastboot -w
    or
    Code:
    fastboot erase userdata

    4- You see the TWRP LOGO in the screen?
    Uow. I really thought it would have nothing but a black screen. That means I'm on the right path. It is now necessary to put more information and maybe more specific files. One piece at a time now.
    I'll leave the file in the post as a base. But I need more information and confirmations than what was done to try to install. Even if you confirm the commands, maybe using another modified vbmeta can help.

    Anyway in my spare time I will do more files if everything has been confirmed that TWRP does not start.


    Thnaks for testing the file.

    Thought itd be mka bootimage but youve compiled alot so i might be wrong
    mka bootimage => has boot.img file. BUT in the A10 boot partition has only kernel and "ramdisk". Not others necessary files. U need learning more about boot & recovery partitions: Boot operations and Devices with A/B updates & Recovery & Setting partitions (slots) & Images vs Non-A/B


    In short: The Recovery partition was never needed to boot the device. This was a second initialization (for safety) or mini loader.
    But on A10-A/B the Recovery partition doesn't really exist?! It is unified with the Boot partition. Anyway, read above and try to understand.
    1
    Thanks Jerry... But let me know:
    1- What ROM in the device;

    2- Comands and files flashed;
    Unlocked device? with:
    Code:
    fastboot flashing unlock

    3- You can try formatting device with 3 options:
    i- removing google accounts, format data and the device reboot to stock recovery formating all;
    ii- you can reboot in the stock recovery and wipe cache & data;
    iii- using fastboot:
    Code:
    fastboot -w
    or
    Code:
    fastboot erase userdata

    4- You see the TWRP LOGO in the screen?
    Uow. I really thought it would have nothing but a black screen. That means I'm on the right path. It is now necessary to put more information and maybe more specific files. One piece at a time now.
    I'll leave the file in the post as a base. But I need more information and confirmations than what was done to try to install. Even if you confirm the commands, maybe using another modified vbmeta can help.

    Anyway in my spare time I will do more files if everything has been confirmed that TWRP does not start.


    Thnaks for testing the file.


    mka bootimage => has boot.img file. BUT in the A10 boot partition has only kernel and "ramdisk". Not others necessary files. U need learning more about boot & recovery partitions: Boot operations and Devices with A/B updates & Recovery & Setting partitions (slots) & Images vs Non-A/B


    In short: The Recovery partition was never needed to boot the device. This was a second initialization (for safety) or mini loader.
    But on A10-A/B the Recovery partition doesn't really exist?! It is unified with the Boot partition. Anyway, read above and try to understand.
    I'm using the Yahoo firmware with Magisk Root.. I've been using it for a while running some things since achieving root on it. Yes it's unlocked. I don't want to remove my data.. I only did that as per post #402 suggestion to get past the TWRP splash screen if stuck. I tried fastboot format userdata and it failed.

    Yes when I boot to recovery I can see the TWRP logo but it just keeps flashing as if it was force closing and reopening. As I said I can reboot my device and use it regularly so it does seem things are pretty solid here and I personally think it's something simple.

    Here was my complete steps to flash TWRP:
    1) adb reboot bootloader
    2) fastboot --disable-verification --disable-verity flash vbmeta Z5157Y-vbmeta.img
    3) fastboot flash boot boot_a.img
    4) fastboot reboot recovery

    I used the vbmeta image I used when I had rooted my device which can be found in post #384. The boot_a image is of course the one I got from you in post #420.
    1
    I'm using the Yahoo firmware with Magisk Root.. I've been using it for a while running some things since achieving root on it. Yes it's unlocked. I don't want to remove my data.. I only did that as per post #402 suggestion to get past the TWRP splash screen if stuck. I tried fastboot format userdata and it failed.

    Yes when I boot to recovery I can see the TWRP logo but it just keeps flashing as if it was force closing and reopening. As I said I can reboot my device and use it regularly so it does seem things are pretty solid here and I personally think it's something simple.

    Here was my complete steps to flash TWRP:
    1) adb reboot bootloader
    2) fastboot --disable-verification --disable-verity flash vbmeta Z5157Y-vbmeta.img
    3) fastboot flash boot boot_a.img
    4) fastboot reboot recovery

    I used the vbmeta image I used when I had rooted my device which can be found in post #384. The boot_a image is of course the one I got from you in post #420.
    Twrp getting stuck is an infamous bug when the device is fbe so u need to disable it by fastboot format user data

    Edit i just read nvm but twrp splash is better than nothing btw is ur ohone recognised by ur pc i it is run adb logcat and pass on every log
    1
    BTW Im curious on why customized vbmeta is needed
    because the vbmeta stock have dm-verify/avb protection so need same permission in the TWRP file. The signing process can be done in the TWRP file. But obviously it's faster to know if TWRP starts with an "empty" vbmeta file or null of this protection.
  • 4
    No I haven't gotten root on the Visible firmware. I have root on the Yahoo firmware. We don't know what is causing the bootlooping when trying to flash the magisk boot image on the Visible firmware. I'll attach the steps below of what I did to get root on the Yahoo firmware.. keep in mind my device originally had the Visible firmware (Z5157V) on it.

    1) Flash Stock Yahoo Firmware (Z5157Y)

    2) Enable Developer Options

    3) Enable OEM Unlock & USB Debugging in Developer Options

    4) Boot to Bootloader
    adb reboot bootloader

    5) Ensure Device is Recognized by PC
    fastboot devices

    6) Proceed with Unlocking
    (Press Volume Up After Each Command to Confirm)
    fastboot flashing unlock
    fastboot flashing unlock_critical

    7) Reboot Device
    fastboot reboot

    8) Enable USB Debugging Again
    (OEM Unlock Should be Grayed Out & Enabled)

    9) Boot to Bootloader
    adb reboot bootloader

    10) Flash VBmeta (Obtained from thread #283)
    fastboot --disable-verity --disable-verification flash vbmeta <PATH-TO-VBMETA-FILE-HERE>

    11) Flash Modded Boot Image (Obtained from thread #284)
    fastboot --disable-verity --disable-verification flash boot <PATH-TO-BOOT-IMAGE-FILE-HERE>
    View attachment 5382835View attachment 5382837
    gonna borrow your steps and tweak it for any visible users:

    1) Enable Developer Options

    2) Enable OEM Unlock & USB Debugging in Developer Options

    3) Boot to Bootloader
    adb reboot bootloader

    4) Ensure Device is Recognized by PC
    fastboot devices

    5) Proceed with Unlocking
    (Press Volume Up After Each Command to Confirm)
    fastboot flashing unlock
    fastboot flashing unlock_critical

    6) Reboot Device
    fastboot reboot

    7) Enable USB Debugging Again
    (OEM Unlock Should be Grayed Out & Enabled)

    8) Boot to Bootloader
    adb reboot bootloader

    9) Flash VBmeta (Obtained from thread #283)
    fastboot --disable-verity --disable-verification flash vbmeta <PATH-TO-VBMETA-FILE-HERE>

    10) Flash Boot OSS unpatched Image (Obtained from thread #215) (SKIP THIS STEP IF YOU'RE CONFIDENT PATCHING WILL NOT BOOTLOOP YOUR DEVICE)
    fastboot --disable-verity --disable-verification flash boot <PATH-TO-BOOT-IMAGE-FILE-HERE>

    11) Reboot Device
    fastboot reboot

    12) If step 11 works without bootlooping, install magisk canary 23001 and patch boot file from step 10

    13) Boot to Bootloader
    adb reboot bootloader

    14) Flash magisk patched OSS boot image
    fastboot --disable-verity --disable-verification flash boot <PATH-TO-BOOT-IMAGE-FILE-HERE>

    15) Reboot Device
    fastboot reboot
    3
    I hope so too. Hope to understand this /super partition crap. I can't guarantee anything, but now that I'll have one, I can work much faster than solely doing it via messages like this and waiting for someone else to test.
    3
    Good news, won the bid. Wait a week or two and I'll be in the game for real
    2
    @tlopez51 I've been gone for a while, looks like a LOT happened in the span of 2 months. Would you be cool giving a TLDR summary of the progress? It looks like Magisk is finally working, that's great!
    Good to hear from you. Surely I would help in anyway to provide an update but I am not familiar with TLDR. Also, just like you I had dropped out after the last and final Magisk release but periodically would check in.

    Just recent there's been a spark of interest on this project and I see some folks have had some issues. Thanks to member luridphantom for keeping a watchful eye to help others while I slept at the wheel.

    Overall I think the most pressing problem is the result of wiping clean the IMEI to recover from the endless bootloop status. This would not be an issue at all if an oem rom backup was available to restore from. I myself have one such phone. You may recall I had jumped right into this project failing to take a snapshot of the oem rom due to that I was having some issues at the time but nevertheless took the risk. Unfortunately many did not heed to the warnings I too posted. As a result, I went ahead and revised my previous guides and hopefully any new comer will not fall into the same trap.

    Just an FYI.
    From all of my research the IMEI is not hard coded on this phone as far as I can tell but working to find out where it was kept it turns out is in the nvdata file which you will have from a backup. You can always flash this file back and it will restore the IEMI. In a pinch, you can flash the nvdata file from a working phone to another ZTE Blade A3 Prime where the IMEI was wiped clean to get data and calling features working again.

    As you may know, topjohnwu is no longer working on the Magisk project so I think we hit a wall on any new or further developments. Not sure we can push this project any further along.

    Let me know your thoughts.
    2
    Good to hear from you. Surely I would help in anyway to provide an update but I am not familiar with TLDR. Also, just like you I had dropped out after the last and final Magisk release but periodically would check in.

    Just recent there's been a spark of interest on this project and I see some folks have had some issues. Thanks to member luridphantom for keeping a watchful eye to help others while I slept at the wheel.

    Overall I think the most pressing problem is the result of wiping clean the IMEI to recover from the endless bootloop status. This would not be an issue at all if an oem rom backup was available to restore from. I myself have one such phone. You may recall I had jumped right into this project failing to take a snapshot of the oem rom due to that I was having some issues at the time but nevertheless took the risk. Unfortunately many did not heed to the warnings I too posted. As a result, I went ahead and revised my previous guides and hopefully any new comer will not fall into the same trap.

    Just an FYI.
    From all of my research the IMEI is not hard coded on this phone as far as I can tell but working to find out where it was kept it turns out is in the nvdata file which you will have from a backup. You can always flash this file back and it will restore the IEMI. In a pinch, you can flash the nvdata file from a working phone to another ZTE Blade A3 Prime where the IMEI was wiped clean to get data and calling features working again.

    As you may know, topjohnwu is no longer working on the Magisk project so I think we hit a wall on any new or further developments. Not sure we can push this project any further along.

    Let me know your thoughts.
    I was actually the one helping people here as well as others from the Discord but eh oh well lol. So there's no way to modify the nvdata file?
    So we cannot flash between variants then? Like visible should not flash yahoo? I'll update my AF post when I get a computer to access it on. I take it this somehow boot looped and wiped peoples devices. Which is weird, because I recall you doing it before and you had no issues.

    Be careful too with IMEI changing, in certain countries like the USA it's *basically* illegal to wipe or change the IMEI of your phone to something else, the only exception being to restore a lost one (that came with the device).

    I did not know Magisk support stopped. Did he say why? What will replace it? That's a shame since Magisk seemed to be the only way to get root access these days.
    Actually the only way I was able to get root was by first flashing the Yahoo stock firmware from your site.. I'm unable to get root on the Visible variant no matter what I try