How To Guide What worked for me: Working lockscreen after unlocking + rooting

[mcfizzlestag]

It took me a few tries, but i successfully followed the guide.
I already had the broken lock screens on a rooted device. Couple steps i took to set up for the guide:

-Moved the update update (3.18) to internal storage.
-Used System Update in Settings (3 dots, local update). This will install the OS to the other slot and switch over
-enabled USB debugging, adb reboot bootloader
-fastboot flashing lock_critical
-Confirm the lock and hold the volume down button as the phone restarts to get back to bootloader
-fastboot flashing lock
-Confirm the lock and let the phone reboot
-Skip passwords in setup as recommended
-Reset/wipe phone in settings
-Reboot and Skip password set up again.
-confirm developper options OEM unlock enabled
-Follow the OPs guide

as mentioned by others, need to be in bootloader to unlock. and hold down volume key as the phone restarts after each lock confirmation. I also skipped the boot confirmation after the second lock and went straight into the flashing steps

I would recommend that people follow this Thread for rooting. The others will break your lockscreen

 

[yoonhx]

Here are steps that I have found out for myself that will work, for both rooting and unrooting/locking bootloader(to remove the message on boot).

Decided to unroot & lock the bootloader since there was honestly nothing much I could do with android 13 and there isn't any stock roms available for this device, yet.

So here are the steps below.

For rooted devices, ensure you are on the latest firmware (3.18), stock.
Otherwise, do the above @mcfizzlestag by going to your System Update in settings(3 dots, local update) and push the .zip file.

After that, enable USB Debugging & OEM Unlocking(if you havent) in developer options and type
adb reboot bootloader

In fastboot, key in the following -
fastboot flashing unlock_critical (device will reboot, go back to fastboot and key in the next line)
fastboot flashing unlock

For both unlocks, it will prompt you on your screen to use the volume keys to select and confirm.
Just follow as shown.

After reboot, skip all password setups and boot back into boot loader.

Use fastboot enhance as shared by TS and load into fastbootd mode and enter the following commands

fastboot flash init_boot_a (check which partition you are in, if _a, use a, else use _b) filename.img
fastboot flash system system.img
fastboot flash vendor vendor.img

Reboot and you can do your basic setup.

========================================================================

As for unrooting and getting your lock screen to work again follow the steps below.

Boot into bootloader, enter fastbootd mode and key in the following -

fastboot flash _initboot_a (check which partition you are in, if _a, use a, else use _b) filename.img
(your stock init_boot file, not magisk patched)
fastboot flash system system.img
fastboot flash vendor.img


Reboot into bootloader and key in -

fastboot flashing lock_critical (device will reboot, go back to fastboot and key in the next line)
fastboot flashing lock

For both unlocks, it will prompt you on your screen to use the volume keys to select and confirm.
Just follow as shown.

Reboot and setup your device, do not set any password yet.
Enable developer options, and untick OEM Unlocking.

Reboot device and enjoy your password/fingerprint/face protected device again.


Hope my struggles will make rooting/unrooting your device more convenient altogether.

 

[Stusick]

Just got my set today and started tinkering, managed to get it unlocked and rooted and lockscreen is working (both fingerprint and pin)

Here is a summary of what I did, maybe not all steps are needed, but this is what worked for me on the first try

PREPARATION
==========
Update zip file were from the 3.18 firmware on the redmagic.gg site https://help.redmagic.gg/hc/en-us/sections/360005986031-Global-ROMs-and-Updates
Extracted the payload.bin from the update zip file
All img files were dumped from payload.bin using Payload-Dumper-Go https://github.com/ssut/payload-dumper-go/releases


STEP ONE
==========
- Booted up my new device and updated to latest firmware (3.18) - SKIPPED all pin and fingerprint setups
- Rebooted
- Enabled developer settings
- Enabled bootloader unlocking in developer settings
- Powered off again

STEP TWO
==========
- Pressing power button and down vol to enter fastboot
- Loaded fastboot enhanced program (https://github.com/libxzr/FastbootEnhance/releases)
- Selected device by double clicking it and press "fastbootd" mode button
- Waited for phone load to fastbootd mode (just look like normal bootloader but way smaller fonts)

STEP THREE
==========
- unlocked with command line in terminal:
- fastboot flashing unlock
- toggled to unlock with phone vol button
- fastboot flashing unlock_critical
- toggled to turn off device

STEP FOUR
==========
- Turned on and booted system to confirm it still loads
- Powered off again
- Pressing power button and down vol to enter fastboot
- Loaded fastboot enhanced
- Selected device and press "fastbootd" mode
- Waited for phone load to fastbootd mode (just look like normal bootloader but way smaller fonts)

STEP FIVE
==========
- Flashed magisk patched init_boot with:
- fastboot flash init_boot FILENAME.img
- Flashed system partition with:
- fastboot system system.img
- Flashed vendor partition with:
- fastboot vendor vendor.img
- Selected power off

STEP FIVE
==========
- Started phone and booted to system
- Did basic setup SKIPPED all pin and fingerprint setups
- Once setup completed entered Phone Settings - Password and Security
- Proceeded to set pin AND fingerprint for lockscreen

STEP SIX
==========
- Run the magisk stub app to complete Magisk installation


I suspect a reflash of the Vendor partition (and maybe also system parititon) AFTER flashing the patched init_boot image is what fixed this.

I already have the bootloader open. Should I start from step 5?
My screen lock is not working right now.

 

[yoonhx]

I already have the bootloader open. Should I start from step 5?
My screen lock is not working right now.

From step 4, booting into fastbootd first, then continuing to step 5 should pretty much resolve your issues.

 

[Boy_314]

What are the models that you guys are rooting? I recently ordered the 16GB/512GB Void US model from the redmagic store. Link here: https://na.redmagic.gg/products/redmagic-8-pro

I assume this one can be rooted the same way, but just wanted to sanity check.

 

[vernj123]

Just got my set today and started tinkering, managed to get it unlocked and rooted and lockscreen is working (both fingerprint and pin)

Here is a summary of what I did, maybe not all steps are needed, but this is what worked for me on the first try

PREPARATION
==========
Update zip file were from the 3.18 firmware on the redmagic.gg site https://help.redmagic.gg/hc/en-us/sections/360005986031-Global-ROMs-and-Updates
Extracted the payload.bin from the update zip file
All img files were dumped from payload.bin using Payload-Dumper-Go https://github.com/ssut/payload-dumper-go/releases


STEP ONE
==========
- Booted up my new device and updated to latest firmware (3.18) - SKIPPED all pin and fingerprint setups
- Rebooted
- Enabled developer settings
- Enabled bootloader unlocking in developer settings
- Powered off again

STEP TWO
==========
- Pressing power button and down vol to enter fastboot
- Loaded fastboot enhanced program (https://github.com/libxzr/FastbootEnhance/releases)
- Selected device by double clicking it and press "fastbootd" mode button
- Waited for phone load to fastbootd mode (just look like normal bootloader but way smaller fonts)

STEP THREE
==========
- unlocked with command line in terminal:
- fastboot flashing unlock
- toggled to unlock with phone vol button
- fastboot flashing unlock_critical
- toggled to turn off device

STEP FOUR
==========
- Turned on and booted system to confirm it still loads
- Powered off again
- Pressing power button and down vol to enter fastboot
- Loaded fastboot enhanced
- Selected device and press "fastbootd" mode
- Waited for phone load to fastbootd mode (just look like normal bootloader but way smaller fonts)

STEP FIVE
==========
- Flashed magisk patched init_boot with:
- fastboot flash init_boot FILENAME.img
- Flashed system partition with:
- fastboot system system.img
- Flashed vendor partition with:
- fastboot vendor vendor.img
- Selected power off

STEP FIVE
==========
- Started phone and booted to system
- Did basic setup SKIPPED all pin and fingerprint setups
- Once setup completed entered Phone Settings - Password and Security
- Proceeded to set pin AND fingerprint for lockscreen

STEP SIX
==========
- Run the magisk stub app to complete Magisk installation


I suspect a reflash of the Vendor partition (and maybe also system parititon) AFTER flashing the patched init_boot image is what fixed this.

For me I am stuck on Step 2. (Attempting to unlock bootloader) New EU model and updated via OTA to the latest 4.18 firmware. Did not set anything else up. When the phone loads into fastbootd mode I do see that everything has way smaller fonts but on the bottom of my screen I have two error messages
-ERROR Failed to load bitmap fastbootd (error -1)
-ERROR Failed to load bitmap een cant_find_OTG-en (error -01)

This is what Fastboot Enhanced shows as well. Any thoughts?

Thank you!

 

[Stusick]

- Flashed magisk patched init_boot with:
- fastboot flash init_boot FILENAME.img

Does this action need to be done via PowerShell?
init_boot received via Magick on the device

- Flashed system partition with:
- fastboot system system.img
- Flashed vendor partition with:
- fastboot vendor vendor.img

And this is already through Fastboot Enhance?

 

[izsdeaman]

doesn't work for me, i use rom cn 2.26


update : i did it successfully on cn rom 2.26 , lock screen and fingerprint both work , awesome

 

[MeTeC]

I did all the steps but now I have an issue with the Magisk app, it's getting stuck on the green screen whenever I launch it a second time after closing it normally, I have to force close the app to make it launch but even on the first launch it's slow to launch compared to when I'm unrooted, do you guys have the same issue ?

 

[kylegp]

Any idea how to get rid of the unlocked bootloader warning on boot up?

 

[Domainr7]

How to update to newly released firmware if RM8 is rooted?

 

[kylegp]

system partition with:
- fastboot system

How to update to newly released firmware if RM8 is rooted?

I'd also like to know.

 

[MrSec560]

Hello I need help. So I have a windows Vista computer with no wifi, when I enter in cmd fastboot flashing unlock nothing happens while I am in fastboot mode on redmagic... And when I open fastboot enhance it doesn't detect my device under serial number at all, can anyone help please?

 

[hasansinayan]

Thanks, I used these articles to root my redmagic 8 pro device without any problems. All locks are working as well. It's a mystery to be able to do it, but somehow I managed it. All I'm missing is twrp. There is one, but it is said that it does not work regularly. If anyone has installed twrp on the Redmagic 8 pro device, I would be very glad if he could give information about how, thank you again

 

[jaimele]

En twrp es tan fácil como coger el archivo ini_boot del nuevo firmware y parchearlo por magisk, este archivo lo pasa al pc para evitar pérdidas.
Después quitar la rom a actualizar por twrp y después flashear el archivo ini_boot parcheado por twrp

 

[jaimele]

He metido la actualización 4.28 EU y me sale archivo corrupto pero arranca el sistema y parcheado el 4.28 pero el sistema funciona no entiendo el porque el mensaje de error(solucionado)

 

[hasansinayan]

Sorry i didnt ses the previous message

 

[hasansinayan]

En twrp es tan fácil como coger el archivo ini_boot del nuevo firmware y parchearlo por magisk, este archivo lo pasa al pc para evitar pérdidas.
Después quitar la rom a actualizar por twrp y después flashear el archivo ini_boot parcheado por twrp

So first I install twrp, then with twrp I flash the patched boot file again and root it, did I understand correctly?

 

[jaimele]

So first I install twrp, then with twrp I flash the patched boot file again and root it, did I understand correctly?

en mi caso lo hice todo por comando ya que twrp al menos ami no me sale los archivos de la memoria interna...
Puedes hacerlo sin twrp tambien todo por comando y flashear el archivo ini_boot parcheado de magisk.
Aviso de que yo pude rotearlo con el archivo solo boot.img y funciona de maravilla y safetynet lo pasa con el parche que he metido

 

[ThienAn2023]

FAILED (remote: 'Unrecognized command flashing unlock').