[Razer Phone 2 Questions & Answers] Pernilex:
Here were my steps with Razer 2:

SUCCESS: Developer Mode USB Debugging

SUCCESS: (CMD) fastboot flashing unlock

SKIPPED BY MISTAKE: (CMD) fastboot flashing unlock_critical

SUCCESS: (CMD) fastboot flash recovery twrp.img

SOFTBRICKED: TWRP.img flashed on recovery partition alerted Google Security AI

So, I received the error in this picture:

View attachment 5880237

RAZER 2 SOFTBRICK ERROR

I did not unlock bootloader partition access, so when I use flash_all.bat, the script does not successfully create the hard drive partitions.

Strangely, it still tries to install system files on both A and B partitions (the Razer 2 uses A-B partitioning).

Of course, since creating the partitions failed, when the system.img flash reaches file 6/6 on partition B it has no partition to send the files to, so the script kicks me out.

Since the phone is softbricked, the phone does not show up on my drivers list either. The computer can flash the script, but it does not recognize the device is there at the same time:

fastboot devices: Visible

adb devices: not visible

It said Razer 2 in device manager prior to bricking, and changed to ADB interface while in bootloader mode after installing the correct USB Drives (Found on the Razer site). now it doesn't even show that the USB port is active.

I found a forum online that suggests using the CMD command to remove the error:adb reboot "dm-verity enforcing"

However, it failed and spit this error out:

View attachment 5880239

adb reboot "dm-verity enforcing" Failed. Error: no devices/emulators found

I'm wondering if it because the computer cannot see the phone in device manager.

Or maybe it's because I don't have the patch they are talking about on the XDA forum. I am still learning and not familiar with what patches are. I know some bug fixes are called patches but aside from that I don't know how to use them. This was the patch link they sent that they said you need for the command to work:

https://github.com/invisiblek/andro...mmit/e1f62399183b854144301ce85f3a33b53ebfdde7

I also tried:

CMD: fastboot flash boot boot.img

CMD: fastboot flash boot_a boot.img

fastboot flash boot_b boot.img

This did not erase the error either.

Apparently, some phones did away with the recovery partition post 2016 (my razer is Dec 2020).

They flashed the recovery partition inside of the boot Kernel in newer phones instead of having a separate recovery partition with its own Kernel.

I also discovered that my phone's firmware (Found directly on Razer 2 Site) does not have an existing recovery.img file to even dirty flash to erase the TWRP file.

So naturally I am assuming that there ISN'T a recovery partition to flash the img file onto in the first place. This also explains why I am able to still use recovery mode on the phone even though I bricked it by flashing TWRP and replacing the stock recovery.img.

So CMD: fastboot flash recovery recovery.img is useless (I already tried just in case)

So now I have this TWRP file floating on the hardrive somewhere and do not know how to get rid of it if these 3 methods don't work.

So if the TWRP.img was not successfully flashed onto an existing partition (and bypassed security successfully), then I would imagine that flashing the original boot.img would not help which is why it did nothing.

If anyone knows how to get my device to get recognized while in this error mode that would help. Then I can figure out how to use the patch to get the CMD command to work to wipe the boot error.

I used CMD: fastboot flashing get_unlock_ability, and it spit out a zero (Meaning it can't be). So I need to change that to a 1 somehow with some voodoo tech magic.