If you're on the screen with the bootloader unlock stuff, and you've already selected the correct option to unlock, then just hold the volume-down button. If that doesn't work, just hold the power-button until it restarts.
It's just the fastboot screen that in-depth test apk helped me get into, so I haven't been able to access adb commands to unlock the bootloader.
You don't need to, I'm pretty sure. You just need the volume-buttons from what I remember. Besides, I'm near-certain that you use "adb" and not "fastboot". My memory could be failing me, though. It might be worth a try, however.
So I got it finally working! The problem was that my adb usb drivers weren't properly installed.
Right.., so I followed the guide to install TWRP but when i boot into recovery, the default realme UI recovery shows up. Everything was "okay" too.
I dont know why is that, few monts ago I downloaded 50GB file and it was working, but this time i used cloudflare warp to get another 5gb.
It's near impossible to brick an MTK device. Just use SP FLash-tools to re-flash the stock firmware.I am an idiot and when trying to root my phone i bricked it, when i was trying itmy phone booted to realme ui recovery and it said there's a system error and to do online update but it coudnt find any wifi, can anybody help me? I'm so stressed that is permamently bricked
No worries. Ask as much as you want.I'm really sorry for spamming in this topic but how should I root my device? everytime when i'm patching boot.img I cant run system again, I tried to change extenstion of magisk.apk to zip and install it using pbrp but then settings app is crashing everytime i try to launch it
I'm using rom from mega, I did everything like you said, like on youtube videos on internet etc. but it again got a bootloop. Here's how I did itNo worries. Ask as much as you want.
You install the magisk apk, find the boot.img for your phone's current ROM, and then patch it with the magisk app. Then, you put the patched boot image into the ADB platform-tools, and start the flashing process afterwards. Like this:
adb reboot bootloader
fastboot flash boot x.img (where "x" is the name of the patched boot image you got from Magisk)
If you're using a custom ROM, extract its zip file, and then move it to your phone. If you're using the ROM I uploaded to the MEGA, you should be able to find it somewhere in the folder. You're looking for the "boot.img" file.
You did pretty much everything right. It seems that the boot image is either not the correct one, or the stock ROM is unrootable, for whatever reason. Would you consider flashing a custom ROM? I can recommend crDroid 7.8 with confidence.
I tried root on dotos and it was working fine, and I'm trying to root coloros cause its prettiest os I've ever seen, but imo it have to be rootable, no one there said that he has problem with rooting, and I can root it in pbrp but settings app doesnt working
BlissOS was kinda buggy for me. Caused my phone to crash. I recommend doing a full wipe of all partitions (excluding external storage and internal storage [you can wipe intyernal if you want, but not recommended if you don't have an SD Card]), and then flashing a different ROM. CrDroid, EvolutionX, and Nusantara are pretty good.
Wait. Was your model originally an RMX2151, or originally an RMX2155?Thanks, it's very strange, I flashed other ROM (evolution, OctaviOS), and it refuses to boot normally, it redirects me either to fastboot or recovery, I flashed the vbmeta image, Magisk but nothing.
Trying to flash the ROM through SP Flash tool gave error 00a0001 and installing the stock recovery and flashing an update for 2151 didn't work, so by now I'm bricked. I guess my device model switched to 2155, if I can get a recovery update ROM for 2155, maybe can fix it.
Yes. According to the person who sent me these instructions: It does unlock the bootloader, which allows you to flash Magisk, TWRP, and ROMs. I haven't tried it myself, and this method has only recently become public due to my post - meaning that we need to wait for a brave soul to risk their Realme 7 for further development. Let's hope somebody tries this out soon. I'd be absolutely ecstatic if we could get one or two more people to confirm that it works.