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

Blade A3 Prime (Visible)

Search This thread

areallydumbperson

Senior Member
Jun 1, 2021
202
1
22
Sony Xperia L1
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.
Man I’m impressed u managed to compile twrp
 

lopestom

Senior Member
Nov 7, 2012
741
498
Archland - Narnia
mewe.com
Man I’m impressed u managed to compile twrp
Thanks. It's not that hard.... But let's see if the file will work. Then we will see if the path has been correctly placed. Now it's up to anyone here with a Blade A3 Prime with the yahoo ROM to test.
 

Attachments

  • Screenshot_20210918_221226.png
    Screenshot_20210918_221226.png
    139 KB · Views: 10
  • Screenshot_20210918_221523.png
    Screenshot_20210918_221523.png
    130.4 KB · Views: 9
  • Screenshot_20210918_230919.png
    Screenshot_20210918_230919.png
    147.6 KB · Views: 9

Jerry12798

Senior Member
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.
Ok I'm about to try this. So I just need to use the step as in thread #402 to get this flashed?
 

Jerry12798

Senior Member
sorry guys i fell asleep anyways i have the image ready

first backup your boot image because this twrp image if it works most likely wont boot into system because of how the script i used works

now

boot into bootloader mode
execute these commands:

fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img
fastboot flash boot ZTE_TWRP.img
fastboot reboot recovery

if it get stuck on the twrp splash screen then reboot back into bootloader mode and execute

fastboot format userdata

now fastboot reboot recovery

it should boot and now since this is still experimental PLEASE TELL ME WHAT PARTITIONS MOUNT AND DONT MOUNT BECAUSE I MAY NEED TO EDIT THE FSTAB TWRP USES
I tried using your steps with @lopestom's TWRP image and am getting stuck at the splash screen so I tried formatting userdata as per your suggestion and it's saying system can't find the file specified
 

Jerry12798

Senior Member
Thanks. It's not that hard.... But let's see if the file will work. Then we will see if the path has been correctly placed. Now it's up to anyone here with a Blade A3 Prime with the yahoo ROM to test.
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
 

lopestom

Senior Member
Nov 7, 2012
741
498
Archland - Narnia
mewe.com
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.
 
Last edited:
  • Like
Reactions: Jerry12798

Jerry12798

Senior Member
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.
 
  • Like
Reactions: lopestom

areallydumbperson

Senior Member
Jun 1, 2021
202
1
22
Sony Xperia L1
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
 
  • Like
Reactions: Jerry12798

areallydumbperson

Senior Member
Jun 1, 2021
202
1
22
Sony Xperia L1
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.
BTW Im curious on why customized vbmeta is needed
 

Jerry12798

Senior Member
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
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?
 

lopestom

Senior Member
Nov 7, 2012
741
498
Archland - Narnia
mewe.com
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.
Can you try it?:
Code:
fastboot boot boot_a.img

or try:
Code:
fastboot flash boot_a boot_a.img
fastboot flash boot_b boot_a.img

Let me know about. I still don't think it will work. But I don't want to give up hope or possible confirmations of mistakes and successes.

Cheers
 
  • Like
Reactions: Jerry12798

Jerry12798

Senior Member
Its gonns be a last resort because it erases userdata
So don't run it yet?

Here is the logcat report while on TWRP splash screen:

Code:
09-20 17:34:19.526   566   566 E ashmem  : Failed to dlopen() libashmemd_client.so: dlopen failed: library "libashmemd_client.so" not found
09-20 17:34:19.526   566   566 I ARMAssembler: generated scanline__00000077:03010101_00008001_00000000 [ 91 ipp] (112 ins) at [0xafb6f1f0:0xafb6f3b0] in 88154 ns
09-20 17:34:19.543   566   566 I ARMAssembler: generated scanline__00000077:03545401_00000A01_00000000 [ 37 ipp] (58 ins) at [0xafb6f3c0:0xafb6f4a8] in 91154 ns
09-20 17:34:19.548   566   566 I ARMAssembler: generated scanline__00000077:03545401_00000A08_00000000 [ 37 ipp] (59 ins) at [0xafb6f4b0:0xafb6f59c] in 76692 ns
09-20 17:34:20.219   566   566 W /system/bin/recovery: [libfs_mgr]Warning: unknown flag: resize
09-20 17:34:20.229   566   566 I chatty  : uid=0(root) /system/bin/recovery identical 2 lines
09-20 17:34:20.231   566   566 W /system/bin/recovery: [libfs_mgr]Warning: unknown flag: resize
09-20 17:34:20.364   566   566 E /system/bin/recovery: DM_DEV_CREATE failed for [product_a]: Device or resource busy
09-20 17:34:20.364   566   566 E /system/bin/recovery: [libfs_mgr]Could not create logical partition: product_a
09-20 17:34:20.365   566   566 W /system/bin/recovery: DM_DEV_STATUS failed for system: No such device or address
09-20 17:34:20.365   566   566 W /system/bin/recovery: DM_DEV_STATUS failed for vendor: No such device or address
09-20 17:34:20.365   566   566 W /system/bin/recovery: DM_DEV_STATUS failed for product: No such device or address
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
09-20 17:34:20.556   566   566 I /system/bin/recovery: fscrypt_initialize_systemwide_keys
09-20 17:34:21.557   566   566 W ServiceManagement: Waited for hwservicemanager.ready for a second, waiting another...
09-20 17:34:21.590   576   576 E ServiceManager: failed to open binder driver /dev/binder
09-20 17:34:21.607   575   575 E hw-ProcessState: Binder driver protocol(8) does not match user space protocol(7)!
09-20 17:34:21.607   575   575 E hw-ProcessState: Binder ioctl to set max threads failed: Bad file descriptor
09-20 17:34:21.607   575   575 E hw-ProcessState: Binder driver could not be opened.  Terminating.
09-20 17:34:21.608   577   577 I [email protected]/: [email protected]/default: Hal starting main loop...
09-20 17:34:21.608   577   577 I [email protected]/: [email protected]/default Hal is starting up...
09-20 17:34:21.608   577   577 E hw-ProcessState: Binder driver protocol(8) does not match user space protocol(7)!
09-20 17:34:21.608   577   577 E hw-ProcessState: Binder ioctl to set max threads failed: Bad file descriptor
09-20 17:34:21.608   577   577 E hw-ProcessState: Binder driver could not be opened.  Terminating.
09-20 17:34:21.608   577   577 F HidlSupport: Failed to setup binder polling: -9 (Unknown error -9)
09-20 17:34:21.608   575   575 E SELinux : avc:  denied  { add } for interface=android.hidl.manager::IServiceManager sid=u:r:recovery:s0 pid=575 scontext=u:r:recovery:s0 tcontext=u:object_r:hidl_manager_hwservice:s0 tclass=hwservice_manager permissive=1
09-20 17:34:21.608   577   577 F libc    : Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 577 (android.hardwar), pid 577 (android.hardwar)
09-20 17:34:21.609   575   575 E SELinux : avc:  denied  { add } for interface=android.hidl.base::IBase sid=u:r:recovery:s0 pid=575 scontext=u:r:recovery:s0 tcontext=u:object_r:hidl_base_hwservice:s0 tclass=hwservice_manager permissive=1
09-20 17:34:21.609   579   579 F libc    : failed to exec crash_dump helper: No such file or directory
09-20 17:34:21.609   575   575 E SELinux : avc:  denied  { add } for interface=android.hidl.token::ITokenManager sid=u:r:recovery:s0 pid=575 scontext=u:r:recovery:s0 tcontext=u:object_r:hidl_token_hwservice:s0 tclass=hwservice_manager permissive=1
09-20 17:34:21.610   575   575 E hw-ProcessState: Binder ioctl to become context manager failed: Bad file descriptor
09-20 17:34:21.610   577   577 F libc    : crash_dump helper failed to exec
09-20 17:34:21.610   566   566 E hw-ProcessState: Binder driver protocol(8) does not match user space protocol(7)!
09-20 17:34:21.610   575   575 F HidlSupport: Failed to setup binder polling: -9 (Unknown error -9)
09-20 17:34:21.610   566   566 E hw-ProcessState: Binder ioctl to set max threads failed: Bad file descriptor
09-20 17:34:21.610   566   566 E hw-ProcessState: Binder driver could not be opened.  Terminating.
09-20 17:34:21.611   575   575 F libc    : Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 575 (hwservicemanage), pid 575 (hwservicemanage)
09-20 17:34:21.611   566   566 E cutils-trace: Error opening trace file: No such file or directory (2)
09-20 17:34:21.611   566   566 E ServiceManagement: getService: defaultServiceManager()->getTransport returns Status(EX_TRANSACTION_FAILED): '-9 Bad file descriptor: '
09-20 17:34:21.611   566   566 F /system/bin/recovery: Keymaster.cpp:124] Check failed: serviceManager Could not retrieve ServiceManager
09-20 17:34:21.611   566   566 F libc    : Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 566 (recovery), pid 566 (recovery)
09-20 17:34:21.612   582   582 F libc    : failed to exec crash_dump helper: No such file or directory
09-20 17:34:21.613   575   575 F libc    : crash_dump helper failed to exec
09-20 17:34:21.614   583   583 F libc    : failed to exec crash_dump helper: No such file or directory
09-20 17:34:21.616   566   566 F libc    : crash_dump helper failed to exec
09-20 17:34:22.255   584   584 W libc    : Unable to set property "ro.twrp.boot" to "1": error code: 0xb
09-20 17:34:22.255   584   584 W libc    : Unable to set property "ro.twrp.version" to "3.5.2_10-- by jasonmerc": error code: 0xb
 

Jerry12798

Senior Member
Can you try it?:
Code:
fastboot boot boot_a.img

or try:
Code:
fastboot flash boot_a boot_a.img
fastboot flash boot_b boot_a.img

Let me know about. I still don't think it will work. But I don't want to give up hope or possible confirmations of mistakes and successes.

Cheers
I'm trying these now

UPDATE: None of these worked either unfortunately and yielded the same issue once at the TWRP splash screen
 
Last edited:
  • Sad
Reactions: lopestom

areallydumbperson

Senior Member
Jun 1, 2021
202
1
22
Sony Xperia L1
So don't run it yet?

Here is the logcat report while on TWRP splash screen:

Code:
09-20 17:34:19.526   566   566 E ashmem  : Failed to dlopen() libashmemd_client.so: dlopen failed: library "libashmemd_client.so" not found
09-20 17:34:19.526   566   566 I ARMAssembler: generated scanline__00000077:03010101_00008001_00000000 [ 91 ipp] (112 ins) at [0xafb6f1f0:0xafb6f3b0] in 88154 ns
09-20 17:34:19.543   566   566 I ARMAssembler: generated scanline__00000077:03545401_00000A01_00000000 [ 37 ipp] (58 ins) at [0xafb6f3c0:0xafb6f4a8] in 91154 ns
09-20 17:34:19.548   566   566 I ARMAssembler: generated scanline__00000077:03545401_00000A08_00000000 [ 37 ipp] (59 ins) at [0xafb6f4b0:0xafb6f59c] in 76692 ns
09-20 17:34:20.219   566   566 W /system/bin/recovery: [libfs_mgr]Warning: unknown flag: resize
09-20 17:34:20.229   566   566 I chatty  : uid=0(root) /system/bin/recovery identical 2 lines
09-20 17:34:20.231   566   566 W /system/bin/recovery: [libfs_mgr]Warning: unknown flag: resize
09-20 17:34:20.364   566   566 E /system/bin/recovery: DM_DEV_CREATE failed for [product_a]: Device or resource busy
09-20 17:34:20.364   566   566 E /system/bin/recovery: [libfs_mgr]Could not create logical partition: product_a
09-20 17:34:20.365   566   566 W /system/bin/recovery: DM_DEV_STATUS failed for system: No such device or address
09-20 17:34:20.365   566   566 W /system/bin/recovery: DM_DEV_STATUS failed for vendor: No such device or address
09-20 17:34:20.365   566   566 W /system/bin/recovery: DM_DEV_STATUS failed for product: No such device or address
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
09-20 17:34:20.556   566   566 I /system/bin/recovery: fscrypt_initialize_systemwide_keys
09-20 17:34:21.557   566   566 W ServiceManagement: Waited for hwservicemanager.ready for a second, waiting another...
09-20 17:34:21.590   576   576 E ServiceManager: failed to open binder driver /dev/binder
09-20 17:34:21.607   575   575 E hw-ProcessState: Binder driver protocol(8) does not match user space protocol(7)!
09-20 17:34:21.607   575   575 E hw-ProcessState: Binder ioctl to set max threads failed: Bad file descriptor
09-20 17:34:21.607   575   575 E hw-ProcessState: Binder driver could not be opened.  Terminating.
09-20 17:34:21.608   577   577 I [email protected]/: [email protected]/default: Hal starting main loop...
09-20 17:34:21.608   577   577 I [email protected]/: [email protected]/default Hal is starting up...
09-20 17:34:21.608   577   577 E hw-ProcessState: Binder driver protocol(8) does not match user space protocol(7)!
09-20 17:34:21.608   577   577 E hw-ProcessState: Binder ioctl to set max threads failed: Bad file descriptor
09-20 17:34:21.608   577   577 E hw-ProcessState: Binder driver could not be opened.  Terminating.
09-20 17:34:21.608   577   577 F HidlSupport: Failed to setup binder polling: -9 (Unknown error -9)
09-20 17:34:21.608   575   575 E SELinux : avc:  denied  { add } for interface=android.hidl.manager::IServiceManager sid=u:r:recovery:s0 pid=575 scontext=u:r:recovery:s0 tcontext=u:object_r:hidl_manager_hwservice:s0 tclass=hwservice_manager permissive=1
09-20 17:34:21.608   577   577 F libc    : Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 577 (android.hardwar), pid 577 (android.hardwar)
09-20 17:34:21.609   575   575 E SELinux : avc:  denied  { add } for interface=android.hidl.base::IBase sid=u:r:recovery:s0 pid=575 scontext=u:r:recovery:s0 tcontext=u:object_r:hidl_base_hwservice:s0 tclass=hwservice_manager permissive=1
09-20 17:34:21.609   579   579 F libc    : failed to exec crash_dump helper: No such file or directory
09-20 17:34:21.609   575   575 E SELinux : avc:  denied  { add } for interface=android.hidl.token::ITokenManager sid=u:r:recovery:s0 pid=575 scontext=u:r:recovery:s0 tcontext=u:object_r:hidl_token_hwservice:s0 tclass=hwservice_manager permissive=1
09-20 17:34:21.610   575   575 E hw-ProcessState: Binder ioctl to become context manager failed: Bad file descriptor
09-20 17:34:21.610   577   577 F libc    : crash_dump helper failed to exec
09-20 17:34:21.610   566   566 E hw-ProcessState: Binder driver protocol(8) does not match user space protocol(7)!
09-20 17:34:21.610   575   575 F HidlSupport: Failed to setup binder polling: -9 (Unknown error -9)
09-20 17:34:21.610   566   566 E hw-ProcessState: Binder ioctl to set max threads failed: Bad file descriptor
09-20 17:34:21.610   566   566 E hw-ProcessState: Binder driver could not be opened.  Terminating.
09-20 17:34:21.611   575   575 F libc    : Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 575 (hwservicemanage), pid 575 (hwservicemanage)
09-20 17:34:21.611   566   566 E cutils-trace: Error opening trace file: No such file or directory (2)
09-20 17:34:21.611   566   566 E ServiceManagement: getService: defaultServiceManager()->getTransport returns Status(EX_TRANSACTION_FAILED): '-9 Bad file descriptor: '
09-20 17:34:21.611   566   566 F /system/bin/recovery: Keymaster.cpp:124] Check failed: serviceManager Could not retrieve ServiceManager
09-20 17:34:21.611   566   566 F libc    : Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 566 (recovery), pid 566 (recovery)
09-20 17:34:21.612   582   582 F libc    : failed to exec crash_dump helper: No such file or directory
09-20 17:34:21.613   575   575 F libc    : crash_dump helper failed to exec
09-20 17:34:21.614   583   583 F libc    : failed to exec crash_dump helper: No such file or directory
09-20 17:34:21.616   566   566 F libc    : crash_dump helper failed to exec
09-20 17:34:22.255   584   584 W libc    : Unable to set property "ro.twrp.boot" to "1": error code: 0xb
09-20 17:34:22.255   584   584 W libc    : Unable to set property "ro.twrp.version" to "3.5.2_10-- by jasonmerc": error code: 0xb
That is alot of errors for logcat on twrp
 
  • Wow
Reactions: Jerry12798

Top Liked Posts

  • There are no posts matching your filters.
  • 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