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

Blade A3 Prime (Visible)

Search This thread

lopestom

Senior Member
Nov 7, 2012
743
498
Archland - Narnia
mewe.com
I'm trying these now

UPDATE: None of these worked either unfortunately and yielded the same issue once at the TWRP splash screen
The ideal thing to know if it really works is to have the device in stock ROM without passwords or personal settings. It's better not to have magisk at the moment because I don't know how much one gets in the way either.
I can't ask anyone to want to lose settings and data right now. Even more that I'm not sure of the functionality, but without confirming everything I ask, we can also keep running in circles.

Time now to see if anyone can try to install the test TWRP file in the ideal condition.


Code:
09-20 17:34:20.554   566   566 W libc    : Unable to set property "ro.crypto.state" to "encrypted": error code: 0xb
09-20 17:34:20.556   566   566 W libc    : Unable to set property "ro.crypto.type" to "file": error code: 0xb

Can you please post here any photo starting TWRP?
 
  • Like
Reactions: Jerry12798

Jerry12798

Senior Member
The ideal thing to know if it really works is to have the device in stock ROM without passwords or personal settings. It's better not to have magisk at the moment because I don't know how much one gets in the way either.
I can't ask anyone to want to lose settings and data right now. Even more that I'm not sure of the functionality, but without confirming everything I ask, we can also keep running in circles.

Time now to see if anyone can try to install the test TWRP file in the ideal condition.


Code:
09-20 17:34:20.554   566   566 W libc    : Unable to set property "ro.crypto.state" to "encrypted": error code: 0xb
09-20 17:34:20.556   566   566 W libc    : Unable to set property "ro.crypto.type" to "file": error code: 0xb

Can you please post here any photo starting TWRP?
Ok well I'm willing to do that to help I just didn't know if it was necessary. I'll flash stock with SPFT then try the commands again. I'll go ahead and attach a photo of TWRP trying to start as per your request
 

Attachments

  • 20210920_155314.jpg
    20210920_155314.jpg
    1.4 MB · Views: 83
  • Love
Reactions: lopestom
Here I will make a complete guide to root the ZTE Blade A3 Prime with all the required files attached for ease of access. It is REQUIRED to CREATE a FULL NANDroid Backup before even reading this guide. If you fail to do so then you will loose the ability to connect to cell phone towers to make calls, send/receive texts, and use your mobile data from your plan. Even if this is a WiFi Only device for you some apps may not work that use your IMEI as sort of identification or otherwise needs the IMEI as it the IMEI will show as Null, N/A, or Not Available. You can fix this by simply flashing your NVDATA file in SPFT from the NANDroid Backup you made.



1) Flash Stock Yahoo Firmware [Z5157Y-Stock-ROM.zip Attached Below]

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 [Z5157Y-vbmeta.img Attached Below]
fastboot --disable-verity --disable-verification flash vbmeta <PATH-TO-VBMETA-FILE-HERE>

11) Flash Modded Boot Image [Z5157Y-Root.img Attached Below]
fastboot --disable-verity --disable-verification flash boot <PATH-TO-BOOT-IMAGE-FILE-HERE>




~ I like to flash stock firmware by using the Format All + Download Option in SPFT (Smart Phone Flash Tool) just to ensure nothing from the previous firmware is left behind.

~ If you encounter bootloops and need to flash back to stock with SPFT then you may have some issues. This can easily be fixed with the steps below.
1) Open SPFT
2) Take Out Your Battery
3) Open MT6761_Android_scatter.txt in SPFT by Selecting Choose beside Scatter-loading File and navigating to Z5157Y-Stock-ROM
4) Select in the Dropdown Box the Format All + Download Option (Dropdown Box is below the Authentication File Option)
5) Plug Charger Cord in PC (Do NOT Plug in Phone Yet)
6) Click Download (It has a Green Downward Arrow above it)
7) Reinsert Battery & Place Back Case on Phone
8) Hold Volume Down & Plug in Charger Cord to Phone
9) Keep Holding Volume Down until Red Line Appears at Bottom of SPFT
10) Once You See the Red Line & Release Volume Down the Line will Turn Yellow
11) Wait for OK Message to be Displayed
12) Reboot Device

After this you should be back on the stock Yahoo firmware and can either stay here or try rooting again.

Where can I find the Z5157Y-Stock-ROM.zip? It's not attached in this post?
 

tcs100

Member
Oct 14, 2021
7
0
Those two posts are for something else we were trying to get working.

The instructional video link is here. I'd suggest watching the video at least once to get some idea of what it involves. Essentially after WwR generates a watered down version of the scatter file you will use it in SPFT to get three files off the phone and those are used to whip up the actual phone 's image using WwR. It's not difficult just time consuming.

It would be great to get both the Visible and Yahoo for second backups though I am more interested in the Visible. I know I may be asking a lot but if you run into any difficulties let me know.

If successful at creating an image it would be best to zip it and put it on the cloud like mediafire or something similar and link it here for all to have access.

Update: You can put the three dump files and WwR initially generated scatter file on the cloud and I can generate the images. Generally try to make those available in a separate zip download. Don't put them in with the zipped images. Keep everything separate as the Visible and Yahoo files are different.

Thanks.
I am trying to create a backup for my Visible A3 Prime, build number Z5157VV1.0.0B11. I created the scatter file with Wwr per Hovatek's video but when i try to do a EMMC_BOOT1 Readback with SPFT, I get;

ERROR: STATUS_PRELOADER_INVALID
THE PRELOADER FILE FORMAT IS INVALID!
PLEASE TRY ANOTHER OFFICIAL LOAD

From the scatter file I am using Start address 0x0 and length 0x80000. I'm wondering if the newer Visible phones use a different scatter file. I've tried it holding down the volume down button and without.
 

areallydumbperson

Senior Member
Jun 1, 2021
205
1
22
Sony Xperia L1
I am trying to create a backup for my Visible A3 Prime, build number Z5157VV1.0.0B11. I created the scatter file with Wwr per Hovatek's video but when i try to do a EMMC_BOOT1 Readback with SPFT, I get;

ERROR: STATUS_PRELOADER_INVALID
THE PRELOADER FILE FORMAT IS INVALID!
PLEASE TRY ANOTHER OFFICIAL LOAD

From the scatter file I am using Start address 0x0 and length 0x80000. I'm wondering if the newer Visible phones use a different scatter file. I've tried it holding down the volume down button and without.
Don’t put a
I am trying to create a backup for my Visible A3 Prime, build number Z5157VV1.0.0B11. I created the scatter file with Wwr per Hovatek's video but when i try to do a EMMC_BOOT1 Readback with SPFT, I get;

ERROR: STATUS_PRELOADER_INVALID
THE PRELOADER FILE FORMAT IS INVALID!
PLEASE TRY ANOTHER OFFICIAL LOAD

From the scatter file I am using Start address 0x0 and length 0x80000. I'm wondering if the newer Visible phones use a different scatter file. I've tried it holding down the volume down button and without.
don’t put a size it’ll automatically fill in for u in sp tool
 

tlopez51

Senior Member
Jan 25, 2011
161
67
I tried reading back EMMC_BOOT1 without putting a length value and got the same error. I've tried two different computers and two different data cables. I'll try to wade through the log files.

Has anyone successfully backed up using the hovatek video procedure?
WwR creates an empty scatter file with partition_size: 0x80000 but it should be partition_size: 0x40000 instead. Edit the WwR created empty scatter file and change from partition_size: 0x80000 to partition_size: 0x40000 and see if that works. I think this is how I got it to work and do believe Hovatek may also have mentioned it in the video but don't recall for certain.

The final scatter file should look similar to the below once you have successfully created a full ROM backup. Note the below example is not the complete contents of the actual scatter file that is generated in the end but serves to show the proper partition size and is the same for the Visible and Yahoo phone variants.

#
#########################################__WwR_MTK_2.50__###################################################
- general: MTK_PLATFORM_CFG
info:
- config_version: V1.1.2
platform: MT6761
project: k61v1_32_bsp_hdp
storage: EMMC
boot_channel: MSDC_0
block_size: 0x20000
############################################################################################################
#
# Layout Setting
#
############################################################################################################
- partition_index: SYS0
partition_name: preloader
file_name: preloader_k61v1_32_bsp_hdp.bin
is_download: true
type: SV5_BL_BIN
linear_start_addr: 0x0
physical_start_addr: 0x0
partition_size: 0x40000
region: EMMC_BOOT_1
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: BOOTLOADERS
is_upgradable: true
empty_boot_needed: false
reserve: 0x00
 

lopestom

Senior Member
Nov 7, 2012
743
498
Archland - Narnia
mewe.com
############################################################################################################
Can you try?


20210920_155314-jpg.5414769
 

tlopez51

Senior Member
Jan 25, 2011
161
67
Copy of untouched Visible Initial Rom Dump created with WwR 2.50 which should allow you to get a full image dump of your phone using WwR while also following Hovatek's proceedure.
 

Attachments

  • vs_rom_dump.zip
    133.1 KB · Views: 3

Top Liked Posts

  • There are no posts matching your filters.
  • 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.
    1
    I know it was recognized during the TWRP splash screen because to reboot normally I just used adb reboot. I'll run logcat now. Why exactly does this bug happen? Your saying I should run fastboot -w?
    Its gonns be a last resort because it erases userdata
  • 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