Axon 7 A2017U b19N BRICKED FOR NO REASON!

[Ghostface009]

Alright, so I don't know what happened, my axon 7 got bricked for no reason at all
I unlocked the bootloader using Axon7Toolkit v1.1.0 method here > https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108 it got unlocked and whenever I boot I get bootloader verifying, the screen that says "software corruption failed, please lock the bootloader"
I asked Bkores about it in zte community he said it was all normal
everything was good until I decided to flash twrp 3.1.0.0 official image using fastboot flash recovery command on bootloader, twrp was flashed successfully everything was fine till that moment
I reboot to twrp, twrp's working fine, i reboot the device using twrp, the bootloader verifying screen appears, I wait 5 seconds...NOTHING! No bootanimation, nothing just stuck on the bootloader verifying screen, can't use the volume buttons to navigate (unless I use it before the 5 sec. period to reboot to recovery, fastboot, etc)
I reboot to twrp, try to perform factory reset I see "can't mount /data device or resource is busy"
since I am very familiar with this error (due to my older experience with older devices ) I thought this was "lulzworthy" and I only needed to wipe data by advanced wipe (without changing the file system, kept it ext4)
data is usable now, I reboot to system...same issue...
I tried deleting cache, dalvik and internal, same thing, nothing changed
why is this happening and how to fixit? I am downloading the b19 bootstack and b19 system for flashing them, but that'll take a lot of time and maybe it's not a system issue at all can someone help?

 

[amphi66]

That "Software corruption failed" message is NOT normal, but you should get a warning about "unable to check for corruption".

Had a similar issue after an unsuccessful attempt to flash TWRP 3.1. EDL was the answer. See HERE

I went through the process and even did not lose any data, to my surprise. Decided to stay with TWRP 3.0.4-1 .. .. ..

Good luck

 

[StickMonster]

I think you need to flash an su/root or the no-verity zip.

 

[gpz1100]

^^Ding ding ding. I mentioned in one of the other threads, there really needs to be a sticky about this.

The phone is not bricked, it's just not meeting certain security standards that the stock rom is checking for, so it halts before it even begins to boot. Flashing supersu patches the dm-verity check. Or if you don't want root, flash the no-verity zip.

 

[Ghostface009]

That "Software corruption failed" message is NOT normal, but you should get a warning about "unable to check for corruption".

Had a similar issue after an unsuccessful attempt to flash TWRP 3.1. EDL was the answer. See HERE

I went through the process and even did not lose any data, to my surprise. Decided to stay with TWRP 3.0.4-1 .. .. ..

Good luck

Not really it was just the verity check >_> and yes it was "Unable to check for corruption"

I think you need to flash an su/root or the no-verity zip.

Yep

^^Ding ding ding. I mentioned in one of the other threads, there really needs to be a sticky about this.

The phone is not bricked, it's just not meeting certain security standards that the stock rom is checking for, so it halts before it even begins to boot. Flashing supersu patches the dm-verity check. Or if you don't want root, flash the no-verity zip.

IT MUST BE A STICKY since I rushed downloading twrp from twrp.me and flashed it via Axon7tool thinking everything was fine, being unaware of verity check >_> but now flashed no verity zip and booted successfully
This is my first Arm64 device and things are a bit confusing for me, sorry for this post I should've searched about the twrp post >_>