How To Guide [GUIDE][REALME 8i][NARZO 50] Unlock Bootloader Flash TWRP and Root [RMX3151][RMX3286]

[JhaeZI]

So I unlocked the bootloader of my realme 8i, and i faced an issue where i kept on getting stuck on this loop where it refuses to boot, fortunately i was able to solve this problem by clearing the data, and now i just finished on the rooting process and now my phone is stuck in an endless bootloop where it refuses to boot at all, im wondering if i should clear my data aswell by using the python commandline i used to unlock the bootloader by clearing its data?

 

[SubwayChamp]

So I unlocked the bootloader of my realme 8i, and i faced an issue where i kept on getting stuck on this loop where it refuses to boot, fortunately i was able to solve this problem by clearing the data, and now i just finished on the rooting process and now my phone is stuck in an endless bootloop where it refuses to boot at all, im wondering if i should clear my data aswell by using the python commandline i used to unlock the bootloader by clearing its data?

If you can reach fastboot then you can command fastboot -w, if you know how to use mtkclient then you can command python mtk e userdata but you probably need to flash a blank vbmeta, in order to bypass the AVB.

 

[JhaeZI]

If you can reach fastboot then you can command fastboot -w, if you know how to use mtkclient then you can command python mtk e userdata but you probably need to flash a blank vbmeta, in order to bypass the AVB.

how do i flash a blank vbmeta?

 

[SubwayChamp]

how do i flash a blank vbmeta?

Use the one that is inside the mtk-client zip, in case you didn't know about it, follow the instructions you'll find in the link I provided.

 

[realme8iandrey]

Guys please help, my phone wont turn on: after installing lk.bin, it vibrated once with black screen, and after when i trying to turn it on, it want, just black screen. I tryed to connect it to pc, and it defined as "android phone". I tryed to follow guide again but mtk-client didnt recognizes phone. I also tryed to reboot phone with adb but adb dont recognizes phone too. Please help me

 

[HadesBar]

Guys please help, my phone wont turn on: after installing lk.bin, it vibrated once with black screen, and after when i trying to turn it on, it want, just black screen. I tryed to connect it to pc, and it defined as "android phone". I tryed to follow guide again but mtk-client didnt recognizes phone. I also tryed to reboot phone with adb but adb dont recognizes phone too. Please help me

Try doing https://forum.xda-developers.com/t/guide-unbrick-realme-8i-narzo-50-unbrick-free-without-auth-rmx3151-rmx3286.4370619/unread

 

[realme8iandrey]

Try doing https://forum.xda-developers.com/t/guide-unbrick-realme-8i-narzo-50-unbrick-free-without-auth-rmx3151-rmx3286.4370619/unread

Doesnt work at brom.bat stage. It didnt recognizes my phone

 

[babai93]

Request for patched boot.img for firmware version RMX3151_11_C.19 (Realme 8i)

 

[Treeager]

If you can reach fastboot then you can command fastboot -w, if you know how to use mtkclient then you can command python mtk e userdata but you probably need to flash a blank vbmeta, in order to bypass the AVB.

Every time I boot.

dm-verify corruption

your device is corrupt.
It can't be trusted and may not work properly.
Press power button to continue.
Or, device will power off in 5s

How to get access to fastboot by vol- and power? I can go in TWRP by adb reboot recovery and in TWRP fastboot by adb reboot fastboot, but if something goes wrong and i can't use adb I don't know what to do. Vol- and power (or adb reboot bootloader) shows

the serial is not match
fastboot_unlock_verify fail

 

[SubwayChamp]

Every time I boot.

dm-verify corruption

your device is corrupt.
It can't be trusted and may not work properly.
Press power button to continue.
Or, device will power off in 5s

The message, firstly, is OK, because this is just a warning, but, if your device can´t boot, then this means that you altered some partition, without properly unlock the bootloader.

How to get access to fastboot by vol- and power? I can go in TWRP by adb reboot recovery and in TWRP fastboot by adb reboot fastboot, but if something goes wrong and i can't use adb I don't know what to do. Vol- and power (or adb reboot bootloader) shows

the serial is not match
fastboot_unlock_verify fail

Realme devices enter to fastboot mode using volumen+ and PWR buttons, or supposedly this is the method that is designed to work, but, it happens that some devices, and in some builds this method simply, doesn´t work.

Using TWRP to reboot to fastboot using adb reboot fastboot will send device to fastbootd, not to fastboot; the command to send device to fastboot is adb reboot bootloader.

As a side note, you dont need to reboot to TWRP, in order to go to fastboot mode, you always can reboot to fastboot mode, from the device on using ADB commands, if you are wondering how; connect the device to the PC through an USB cable, then open a terminal and command adb reboot bootloader, inmediately when you see that the command was sent to the device, disconnect the USB cable, and quickly, reconnect it. The fastboot mode screen is identical to the recovery screen.

 

[Treeager]

adb reboot fastboot

boots in fastbootd.

adb reboot bootloader

shows

the serial is not match
fastboot_unlock_verify fail

for a split second and boots normally. It's the same thing for vol- and power. vol+ and power simply just boots the phone. Is there a way to boot in fastbootd or recovery with mtk client or to make normal fastboot work?

 

[SubwayChamp]

adb reboot fastboot

boots in fastbootd.

Yes, this is what I said.

adb reboot bootloader

shows

the serial is not match
fastboot_unlock_verify fail

for a split second and boots normally.

Not only commanding, follow exactly what I pointed out, it is a timing thing, be sure that the command was sent to device, and the device started to reboot, but reconnect the cable quickly.

It's the same thing for vol- and power. vol+ and power simply just boots the phone. Is there a way to boot in fastbootd or recovery with mtk client or to make normal fastboot work?

Volume- and PWR buttons send device to recovery mode.
Volume+ and PWR buttons send device to fastboot mode, BUT as I said you previously, it´s very unstable.

Mtk-client has nothing to do with those things, anyway, it´s funny, to reboot to fastboot you should get the device first in download mode, and then?, it´s non-sense.

You have the "normal" fastboot reboot method as described previously, again, just commanding won´t work.

 

[LoJK3y]

I'm currently stuck in a bootloop with my narzo 50

I used the following guides in order:

1. https://forum.xda-developers.com/t/...-flash-twrp-and-root-rmx3151-rmx3286.4369399/
2. https://forum.xda-developers.com/t/...ock-bootloader-install-twrp-and-root.4483507/
3. https://forum.xda-developers.com/t/...ck-free-without-auth-rmx3151-rmx3286.4370619/

While I was following guide(1), I ran into a bootloop after the step where you unlock the bootloader. It took a while, but I managed to boot into android, showing the "OEM unlock" setting in developer options greyed out. The bootloader was unlocked, so I proceeded to the next step ("2. ROOTING YOUR DEVICE:"). When I was at the step where you disconnect and reboot the phone I got stuck in a boot loop where it displays the realme logo and small white text on the left hand side that says "Orange State Your device has been unlocked and can't be trusted Your device will boot in 5 seconds", then the screen goes black for a few seconds and the cycle repeats. I could, however kind of enter fastboot by pressing the volume down and power buttons at the same time, but it would display some text really fast and then the realme logo with the white text would appear again and the cycle repeats. Then I found guide(2).

Since the bootloader was already unlocked, I decided to skip to step 2 of guide(2), "Installing TWRP". However, when I entered the "fastboot reboot recovery" command in my pc, the phone would display "dm verity corruption your device is corrupted" and then it would display "Orange State Your device has been unlocked and can't be trusted Your device will boot in 5 seconds", and the cycle continues. After this, I found guide(3).

I followed guide(3), but I still coudn't access recovery, so I used the "python mtk e metadata,userdata,md_udc" command and redo everything in the guide. I used a decrypted oppo stock rom .ofp instead of the one in the guide specifically the Realme_Narzo_50_RMX3286_EX_11_A.49_220213_RFT one from the oppstockrom site.

Currently, I can still access fastboot mode with a black screen and text at the center that says "fastboot_unlock_verify ok". The phone still responds to commands using the adb platform tools such as " fastboot reboot recovery" but it still gets stuck in a bootloop, where the realme logo will appear and text that says "recovery mode" on the bottom left of the screen then said text on the bottom left of the screen will disappear and it wil be on the realme logo for a few minutes then the screen goes black and the cycle repeats. The only way to get out of this cycle to get into fastboot mode is by waiting for the screen to go black and entering brom mode and using mtkclient, then using the "python mtk reset" command and pressing the volume down and power buttons at the same time.

This is the first time I've tried to do anything like this and I don't really know what to do at this point. Any help would be greatly appriciated.

Also, every time I enter a command in mtkclient I get the following:

but the process will still succeed. Is the "Error on patching da1 version check" a serious issue?

Update: I did guide(3) again from scratch and successfully flashed the firmware I previously used, then I did the "python mtk w lk lk.bin" command from guide(2) and entered fastboot mode. I then used the adb platformtools and typed the command "fastboot reboot recovery". After that, the phone would do the same thing as before where it would display "recovery mode", but instead of disappearing, the text is replaced with "dm-verity corruption" and some other text which says it will power off in 5 seconds or press the power key to boot. However, regardless of whether I choose to let it power off in a few seconds or press the power key to continue, the screen will just go black and the same thing happens again. If I try to go into fastboot mode by pressing the volume down and power keys, the screen eventually goes black and go into the screen where it says "recovery mode". It does, however, still go into brom mode and respond to commands from mtkclient. It will still display the "Error on patching da1 version check" whenever I run a command for it in mtkclient.

 

[SubwayChamp]

I'm currently stuck in a bootloop with my narzo 50

I used the following guides in order:

1. https://forum.xda-developers.com/t/...-flash-twrp-and-root-rmx3151-rmx3286.4369399/
2. https://forum.xda-developers.com/t/...ock-bootloader-install-twrp-and-root.4483507/
3. https://forum.xda-developers.com/t/...ck-free-without-auth-rmx3151-rmx3286.4370619/

While I was following guide(1), I ran into a bootloop after the step where you unlock the bootloader. It took a while, but I managed to boot into android, showing the "OEM unlock" setting in developer options greyed out. The bootloader was unlocked, so I proceeded to the next step ("2. ROOTING YOUR DEVICE:"). When I was at the step where you disconnect and reboot the phone I got stuck in a boot loop where it displays the realme logo and small white text on the left hand side that says "Orange State Your device has been unlocked and can't be trusted Your device will boot in 5 seconds", then the screen goes black for a few seconds and the cycle repeats. I could, however kind of enter fastboot by pressing the volume down and power buttons at the same time, but it would display some text really fast and then the realme logo with the white text would appear again and the cycle repeats. Then I found guide(2).

Since the bootloader was already unlocked, I decided to skip to step 2 of guide(2), "Installing TWRP". However, when I entered the "fastboot reboot recovery" command in my pc, the phone would display "dm verity corruption your device is corrupted" and then it would display "Orange State Your device has been unlocked and can't be trusted Your device will boot in 5 seconds", and the cycle continues. After this, I found guide(3).

I followed guide(3), but I still coudn't access recovery, so I used the "python mtk e metadata,userdata,md_udc" command and redo everything in the guide. I used a decrypted oppo stock rom .ofp instead of the one in the guide specifically the Realme_Narzo_50_RMX3286_EX_11_A.49_220213_RFT one from the oppstockrom site.

Currently, I can still access fastboot mode with a black screen and text at the center that says "fastboot_unlock_verify ok". The phone still responds to commands using the adb platform tools such as " fastboot reboot recovery" but it still gets stuck in a bootloop, where the realme logo will appear and text that says "recovery mode" on the bottom left of the screen then said text on the bottom left of the screen will disappear and it wil be on the realme logo for a few minutes then the screen goes black and the cycle repeats. The only way to get out of this cycle to get into fastboot mode is by waiting for the screen to go black and entering brom mode and using mtkclient, then using the "python mtk reset" command and pressing the volume down and power buttons at the same time.

This is the first time I've tried to do anything like this and I don't really know what to do at this point. Any help would be greatly appriciated.

Also, every time I enter a command in mtkclient I get the following:

but the process will still succeed. Is the "Error on patching da1 version check" a serious issue?

Update: I did guide(3) again from scratch and successfully flashed the firmware I previously used, then I did the "python mtk w lk lk.bin" command from guide(2) and entered fastboot mode. I then used the adb platformtools and typed the command "fastboot reboot recovery". After that, the phone would do the same thing as before where it would display "recovery mode", but instead of disappearing, the text is replaced with "dm-verity corruption" and some other text which says it will power off in 5 seconds or press the power key to boot. However, regardless of whether I choose to let it power off in a few seconds or press the power key to continue, the screen will just go black and the same thing happens again. If I try to go into fastboot mode by pressing the volume down and power keys, the screen eventually goes black and go into the screen where it says "recovery mode". It does, however, still go into brom mode and respond to commands from mtkclient. It will still display the "Error on patching da1 version check" whenever I run a command for it in mtkclient.

The warning screen says to press the power on, you just have to press it for one or two seconds, not keep it for minutes, or it will do the cyclical reboot. This warning is because you didn´t unlock or relock the bootloader in some part of the process.

 

[LoJK3y]

The warning screen says to press the power on, you just have to press it for one or two seconds, not keep it for minutes, or it will do the cyclical reboot. This warning is because you didn´t unlock or relock the bootloader in some part of the process.

Update:

As of writing this reply, it has been stuck on the realme logo screen for about 1 hour and 20 minutes after pressing the power button for two seconds when the "dm-verity corruption" prompt came up. It's currently plugged in charging, should I just let its battery drain and try something in brom mode like running the "python mtk da seccfg unlock" command in mtkclient?

Also, I forgot to mention that before running the "fastboot reboot recovery" command I ran the "fastboot flashing unlock" and the phone gave me a prompt to press the volume up key to proceed with the unlock, then it showed me a screen that gave me the option to boot into recovery, fastboot, and one other option that I can't remember, however the phone did not respond to any key inputs, that was when I ran the "fastboot reboot recovery" command.

Update:

After about 4 hours on the realme logo screen, the device's battery drained, apparently it wasn't charging even though it was plugged in.

Update:

The phone is back in the bootloop where it tries to boot into recovery and then the "dm-verity corruption" warning comes up that also says the phone has been unlocked and can't be trusted with the option to proceed to boot by pressing the power button, it will get stuck on the realme logo then the screen goes black and it repeats. Currently, I just let its battery drain and turn off.

 

[Treeager]

Update:

As of writing this reply, it has been stuck on the realme logo screen for about 1 hour and 20 minutes after pressing the power button for two seconds when the "dm-verity corruption" prompt came up. It's currently plugged in charging, should I just let its battery drain and try something in brom mode like running the "python mtk da seccfg unlock" command in mtkclient?

Also, I forgot to mention that before running the "fastboot reboot recovery" command I ran the "fastboot flashing unlock" and the phone gave me a prompt to press the volume up key to proceed with the unlock, then it showed me a screen that gave me the option to boot into recovery, fastboot, and one other option that I can't remember, however the phone did not respond to any key inputs, that was when I ran the "fastboot reboot recovery" command.

Update:

After about 4 hours on the realme logo screen, the device's battery drained, apparently it wasn't charging even though it was plugged in.

Update:

The phone is back in the bootloop where it tries to boot into recovery and then the "dm-verity corruption" warning comes up that also says the phone has been unlocked and can't be trusted with the option to proceed to boot by pressing the power button, it will get stuck on the realme logo then the screen goes black and it repeats. Currently, I just let its battery drain and turn off.

Can u boot to fastboot? If yes maybe try to flash twrp (if ur goal is to install custom rom). Btw u can join the telegram group and get help and responses faster

 

[SubwayChamp]

Update:

As of writing this reply, it has been stuck on the realme logo screen for about 1 hour and 20 minutes after pressing the power button for two seconds when the "dm-verity corruption" prompt came up. It's currently plugged in charging, should I just let its battery drain and try something in brom mode like running the "python mtk da seccfg unlock" command in mtkclient?

Also, I forgot to mention that before running the "fastboot reboot recovery" command I ran the "fastboot flashing unlock" and the phone gave me a prompt to press the volume up key to proceed with the unlock, then it showed me a screen that gave me the option to boot into recovery, fastboot, and one other option that I can't remember, however the phone did not respond to any key inputs, that was when I ran the "fastboot reboot recovery" command.

Update:

After about 4 hours on the realme logo screen, the device's battery drained, apparently it wasn't charging even though it was plugged in.

Update:

The phone is back in the bootloop where it tries to boot into recovery and then the "dm-verity corruption" warning comes up that also says the phone has been unlocked and can't be trusted with the option to proceed to boot by pressing the power button, it will get stuck on the realme logo then the screen goes black and it repeats. Currently, I just let its battery drain and turn off.

Sorry for late reply.

Again, the warning screen is because not unlocking bootloader, either not entirely or correctly, when you do the official unlocking process has to be through the official Realme app, in-depth test, if there´s not one available for your model, then the fastboot thing won´t do a complete unlocking, lefting critical partition untouched. If you unlock through mtk client, then you also have to erase partitions like userdata, reboot and check, if not enough, erase md_udc, reboot and check, if not enough, erase metadata, and check again, if the issue still persist, then flash the blank vbmeta that you´ll find inside the mtk-client-main.zip.

 

[LoJK3y]

Sorry for late reply.

Again, the warning screen is because not unlocking bootloader, either not entirely or correctly, when you do the official unlocking process has to be through the official Realme app, in-depth test, if there´s not one available for your model, then the fastboot thing won´t do a complete unlocking, lefting critical partition untouched. If you unlock through mtk client, then you also have to erase partitions like userdata, reboot and check, if not enough, erase md_udc, reboot and check, if not enough, erase metadata, and check again, if the issue still persist, then flash the blank vbmeta that you´ll find inside the mtk-client-main.zip.

I see, thanks.

 

[basarbd]

can someone help me with boot image and vbmeta of a56? (narzo 50)

 

[Aleplus]

This method will work with Realmi 8i with firmware Realmi UI 4.0?