How To Guide [ROOT] [PSYCHE] Root Xiaomi 12x with Magisk

How To Guide [ROOT] [PSYCHE] Root Xiaomi 12x with Magisk - Xiaomi 12X

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sources used: link
1. First unlock your bootloader. This thread does not cover this. I suggest you do not try to tamper with the 1week~ time gate you will encounter else it may get longer should you fail.
2. Enable Developer mode and adb from Developer settings again.
3 Download the appropriate Fastboot files for your device . See the About section in your phone's settings to know what you are currently running.
4. Download latest Magisk-vXX.Y.apk and install it on your device. Magisk developer only provides files from Github, do not download it from anywhere else.
5. Extract(Install 7-zip if needed) the fastboot .tgz archive and copy the boot.img from it to your phone's sdcard through adb (or other means):
Code:
adb push psyche_eea_global_images_V13.0.3.0.SLDEUXM/images/boot.img /sdcard/
6. Open up Magisk on your phone, press Install and use the patch option to navigate to the boot.img you just copied. Select that, next next next.
7. Read the output to see where the patched boot.img got saved. Pull that.
Code:
adb pull /sdcard/Download/magisk_patched-24300_D2K9V.img
8. Reboot phone to fastboot.
Code:
adb reboot fastboot
9. Flash the modified boot image
Code:
fastboot flash boot recoveryxy.img
10. Flash dtbo (found inside rom zip)
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
10. Say your prayers and reboot, your device should now have functional root with Magisk
Code:
fastboot reboot

This did not work for me. Seemingly flashed okay, but phone is now bootlooping.

weggy101 said:
This did not work for me. Seemingly flashed okay, but phone is now bootlooping.
Click to expand...
Click to collapse
im sorry forgot step 10. flash vbmeta image. updated guide.

nofx161 said:
im sorry forgot step 10. flash vbmeta image. updated guide.
Click to expand...
Click to collapse
Still gets stuck in a bootloop. Just for fun I downloaded the tgz archive from another source, same situation.
If anyone else gets stuck, here's how to get out of it:
1) Reboot into RECOVERY mode. Select the option for help. It should show a picture of the phone and a USB cable.
2) Follow the onscreen URL for the MiPhoneAssistant Tool
3) I was not able to download via the tool, so I loaded the image in manually with the 2nd option. For my Chinese phone, it was a ~380 MB ZIP file called V13.0.5.0.SLDCNXM, downloaded from:
https://hugeota.d.miui.com/V13.0.5.0.SLDCNXM/miui-blockota-psyche-V13.0.4.0.SLDCNXM-V13.0.5.0.SLDCNXM-ffe7c45215-12.0.zip
4) After finishing, it just boots up to a black screen. Reboot into FASTBOOT mode.
5) From here you can reflash your ROM and be back in business.

I think it worked here, I patched the boot.img from the EEA ROM I'm running (V13.0.3.0.SLDEUXM_20220528.0000.00_12.0_eea) and the Magisk App says it's installed. The only problem is that I'm not able to edit files and/or paste new ones in the root/system folder.
I'm trying to edit build.prop but it says there's not enough space to complete the operation (using SolidExplorer), I tried to disable my nav buttons with FNG too, but that also won't work.

hey you can use my boot image which is rooted with magisk 25.0
magisk_patched-25000_WA0wW.img
drive.google.com
also the original boot if you messed up
boot.img
drive.google.com

Did anyone solved CTS profile ?

Completed successfully. The steps were really straightforward and easy to execute. The only question I had was about flashing the second slot. These instructions contain the command to flash the active slot only, but the 12x has a and b. I went ahead and flashed the second slot anyway even though it's inactive right now. Also, as was noted in the 12 thread, I was confused why Power-Vol Down boots to "fastboot" while adb reboot fastboot boots to "fastbootd". I don't know, just went with fastbootd and all was fine. Thank you @nofx161 for the instructions.
I haven't really done any testing yet but will report back if I find anything interesting.

bjs339 said:
Completed successfully. The steps were really straightforward and easy to execute. The only question I had was about flashing the second slot. These instructions contain the command to flash the active slot only, but the 12x has a and b. I went ahead and flashed the second slot anyway even though it's inactive right now. Also, as was noted in the 12 thread, I was confused why Power-Vol Down boots to "fastboot" while adb reboot fastboot boots to "fastbootd". I don't know, just went with fastbootd and all was fine. Thank you @nofx161 for the instructions.
I haven't really done any testing yet but will report back if I find anything interesting.
Click to expand...
Click to collapse
What ROM do you use? Stock or xiaomi EU or which one? Which modules have you tried? Thanks!

I'm on the stock rom and really haven't done much with it yet, so not much to report at this point.

An alternative way for installing magisk is to install twrp ( https://forum.xda-developers.com/t/shared-recovery-psyche-twrp-by-skkk.4461461/ ) and then choose "install twrp" from the advanced menu in twrp. Then restart system and tap on the magisk button. The magisk manager will be loaded from web and your good to go with root.

shortek said:
Did anyone solved CTS profile ?
Click to expand...
Click to collapse
Working on it. I've followed the instructions here: https://forum.xda-developers.com/t/working-safetynet-with-pixel-6-pro-android-12.4354149/ except that I'm using the Shamiko magisk module instead of the Magisk Deny List per guidance here: https://forum.xda-developers.com/t/chase-app-always-detects-root.4099627/page-9. I have two banking apps working, but not Chase and can't add a credit card to my Google Wallet yet. I tested with YASNAC and it says it passes Safety Net, so we'll see if I can get it figured out. It sounds like the Chase app is a constant struggle, and I'm not too concerned about that, but I'd really like to be able to use Google Pay.

bjs339 said:
Working on it. I've followed the instructions here: https://forum.xda-developers.com/t/working-safetynet-with-pixel-6-pro-android-12.4354149/ except that I'm using the Shamiko magisk module instead of the Magisk Deny List per guidance here: https://forum.xda-developers.com/t/chase-app-always-detects-root.4099627/page-9. I have two banking apps working, but not Chase and can't add a credit card to my Google Wallet yet. I tested with YASNAC and it says it passes Safety Net, so we'll see if I can get it figured out. It sounds like the Chase app is a constant struggle, and I'm not too concerned about that, but I'd really like to be able to use Google Pay.
Click to expand...
Click to collapse
Got it! This Safety Net mod fixed Google Pay: https://forum.xda-developers.com/t/...tynet-fix-2-3-1.4217823/page-91#post-87198517

bjs339 said:
Got it! This Safety Net mod fixed Google Pay: https://forum.xda-developers.com/t/...tynet-fix-2-3-1.4217823/page-91#post-87198517
Click to expand...
Click to collapse
Do you have Widevine Level 1 with this method? So we could use streaming services on high quality while being rooted. (can be checked by app DRM info).

HikL said:
Do you have Widevine Level 1 with this method? So we could use streaming services on high quality while being rooted. (can be checked by app DRM info).
Click to expand...
Click to collapse
Looks like it if I'm reading that right.

bjs339 said:
View attachment 5699583
Looks like it if I'm reading that right.
Click to expand...
Click to collapse
Great news! Thank you!

Hello. Please help me. I did everything as in instructions except one thing and it reboots in MIUI Recovery 5.0 as in this photo https://prnt.sc/Oyjs9lxGVFX8 (not my photo). The only thing that I didn't follow is instead of installing my current MIUI version official boot.img which updated tonight 13.04 Global, I used 13.02 Global because I couldn't find fastboot version of 13.04.
edit: now it started just constant bootloop without going into recovery mode, they just uploaded 13.04 fastboot version and I'm downloading it in with high hopes. I hope that if I patch the boot.img with Magisk in emulation on PC nothing bad will happen.
edit2: Sadly I was unable to do it with PC emulator, I'd appreciate if anyone patched it for me, attached file.
boot.img
drive.google.com

kiknalex said:
Hello. Please help me. I did everything as in instructions except one thing and it reboots in MIUI Recovery 5.0 as in this photo https://prnt.sc/Oyjs9lxGVFX8 (not my photo). The only thing that I didn't follow is instead of installing my current MIUI version official boot.img which updated tonight 13.04 Global, I used 13.02 Global because I couldn't find fastboot version of 13.04.
edit: now it started just constant bootloop without going into recovery mode, they just uploaded 13.04 fastboot version and I'm downloading it in with high hopes. I hope that if I patch the boot.img with Magisk in emulation on PC nothing bad will happen.
edit2: Sadly I was unable to do it with PC emulator, I'd appreciate if anyone patched it for me, attached file.
Click to expand...
Click to collapse
I patched boot.img with another phone (huawei or smth) repeated all steps and now it's just stuck in fastboot bootloop...
I tried this
Still gets stuck in a bootloop. Just for fun I downloaded the tgz archive from another source, same situation.
If anyone else gets stuck, here's how to get out of it:
1) Reboot into RECOVERY mode. Select the option for help. It should show a picture of the phone and a USB cable.
2) Follow the onscreen URL for the MiPhoneAssistant Tool
3) I was not able to download via the tool, so I loaded the image in manually with the 2nd option. For my Chinese phone, it was a ~380 MB ZIP file called V13.0.5.0.SLDCNXM, downloaded from:
https://hugeota.d.miui.com/V13.0.5....SLDCNXM-V13.0.5.0.SLDCNXM-ffe7c45215-12.0.zip
4) After finishing, it just boots up to a black screen. Reboot into FASTBOOT mode.
5) From here you can reflash your ROM and be back in business.
But my Mi PC Suite doesn't detect phone when I plug cable, although the icon on phone shows that it's plugged in. Please help me...
Edit: issue was fixed in this thread
Please Help Me. Xiaomi 12x. Bricked Phone after trying to root. Stuck in fastboot bootloop.
Hello. I've followed instructions as in this thread https://forum.xda-developers.com/t/root-psyche-root-xiaomi-12x-with-magisk.4455293/ only 1 thing I did wrong is downloading 13.02 boot.img file instead of 13.04 boot.img which wasn't available...
forum.xda-developers.com

Hmmm.... First I would reflash the 13.0.4.0 boot.img to both slots using fastboot.
Copy boot.img to fastboot folder and type
"fastboot flash boot_a boot.img" and then "fastboot flash boot_b boot.img". Now it should boot again. Then you can patch your boot.img and flash it: Copy the patched boot.img to fastboot folder "fastboot flash boot patched_boot.img". Alternatively you can flash magisk via twrp. Therefore download twrp (search our thread), rename the file to twrp.img, copy the twrp.img to fastboot folder, boot the img with "fastboot boot twrp.img" and after twrp is booted go to advanced and tip "flash current twrp" now you have twrp installed. Now you can download the magisk.apk from github, copy it to your internal storage via your pc and flash it via twrp... Violla

Voodoojonny said:
Hmmm.... First I would reflash the 13.0.4.0 boot.img to both slots using fastboot.
Copy boot.img to fastboot folder and type
"fastboot flash boot_a boot.img" and then "fastboot flash boot_b boot.img". Now it should boot again. Then you can patch your boot.img and flash it: Copy the patched boot.img to fastboot folder "fastboot flash boot patched_boot.img". Alternatively you can flash magisk via twrp. Therefore download twrp (search our thread), rename the file to twrp.img, copy the twrp.img to fastboot folder, boot the img with "fastboot boot twrp.img" and after twrp is booted go to advanced and tip "flash current twrp" now you have twrp installed. Now you can download the magisk.apk from github, copy it to your internal storage via your pc and flash it via twrp... Violla
Click to expand...
Click to collapse
Thank you for your answer. I already fixed issue in another thread, will edit my comment.

Related

[ROOT] [MAGISK] How to root

Just wanted to inform you, that rooting with Magisk works like a charm. Even without TWRP.
What you need:
Magisk Manager: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
boot.img from your ROM (prepatched boot.img for CN_V10.0.11.0 ROM here: https://filebase.philipp.technology/filebase/index.php?page=Entry&entryID=19)
Unlocked Bootloader
ADB and Fastboot on your PC (Simple ADB & Fastboot Installer: https://filebase.philipp.technology/filebase/index.php?page=Entry&entryID=5)
Installation:
Install MagiskManager.apk on your Smartphone
---SKIP IF YOU USE THE PREPATCHED BOOT.IMG---
Put the unpatched boot.img on your phone
Open MagiskManager and Click "Install"
Select "Patch boot.img" and choose the boot.img with your file manager
Copy the "patched_boot.img" file on your PC
---CONTINUE HERE---
Now connect your Mix 3 to the PC and boot in fastboot mode (over the command line: adb reboot bootloader)
Navigate with the command line to your folder, where you saved the patched_boot.img
Now flash the patched_boot.img file with fastboot: fastboot flash boot patched_boot.img
If the flash is successfull you can reboot the phone with fastboot reboot
Open the MagiskManager and verify that Magisk is installed and your phone is rooted.

Thanks so much! Will try this out! Nice work!

Thanks, after i root my mix 3 can i flash the xiaomi.eu rom on it too without problems ?

Normally you don't need root to flash Xiaomi.eu ROM, just TWRP. But there is no TWRP yet. You could try "Flash Fire", but I don't know if it would work. Never did that before. If you try it make sure, that you have USB Debugging enabled and know how to use common tools like MiFlash etc.
If you are unexperienced wait for TWRP.

PJF16 said:
Normally you don't need root to flash Xiaomi.eu ROM, just TWRP. But there is no TWRP yet. You could try "Flash Fire", but I don't know if it would work. Never did that before. If you try it make sure, that you have USB Debugging enabled and know how to use common tools like MiFlash etc.
If you are unexperienced wait for TWRP.
Click to expand...
Click to collapse
I used TWRP before and Rooted before too but i never used Flash Fire or Flashify. I don't know how hard it would be to use them.

Please report back your success and how it goes for you!

SacredSovL said:
I used TWRP before and Rooted before too but i never used Flash Fire or Flashify. I don't know how hard it would be to use them.
Click to expand...
Click to collapse
It's risky and something I won't be trying, I would wait for TWRP

Hi PJF16
How did you get the boot.img from your device without root? I'd love to make a unmodified copy before trying this out

I got it from the fastboot ROM which I also uploaded to the forum. See here: https://forum.xda-developers.com/mi-mix-3/development/xiaomi-mi-mix-3-fastboot-roms-t3869532

Tested and 100% working! Recommended

smiba said:
Tested and 100% working! Recommended
Click to expand...
Click to collapse
Did u flash xiaomi.eu rom or something else ?

PJF16 said:
Just wanted to inform you, that rooting with Magisk works like a charm. Even without TWRP.
What you need:
Magisk Manager: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
boot.img from your ROM (prepatched boot.img for CN_V10.0.11.0 ROM here: https://filebase.philipp.technology/filebase/index.php?page=Entry&entryID=19)
Unlocked Bootloader
ADB and Fastboot on your PC (Simple ADB & Fastboot Installer: https://filebase.philipp.technology/filebase/index.php?page=Entry&entryID=5)
Installation:
Install MagiskManager.apk on your Smartphone
---SKIP IF YOU USE THE PREPATCHED BOOT.IMG---
Put the unpatched boot.img on your phone
Open MagiskManager and Click "Install"
Select "Patch boot.img" and choose the boot.img with your file manager
Copy the "patched_boot.img" file on your PC
---CONTINUE HERE---
Now connect your Mix 3 to the PC and boot in fastboot mode (over the command line: adb reboot bootloader)
Navigate with the command line to your folder, where you saved the patched_boot.img
Now flash the patched_boot.img file with fastboot: fastboot flash boot patched_boot.img
If the flash is successfull you can reboot the phone with fastboot reboot
Open the MagiskManager and verify that Magisk is installed and your phone is rooted.
Click to expand...
Click to collapse
I feel like I'm missing something. I fastboot flash but it gets hung up in cmd. Should not take as long as it is trying to

souless poet said:
I feel like I'm missing something. I fastboot flash but it gets hung up in cmd. Should not take as long as it is trying to
Click to expand...
Click to collapse
Nevermind figured it out...duh.

Not working on 8.11.15 dev china rom...
Patched boot is much smaller than it should be and after flashing and fastboot reboot command, phone goes back to fastboot mode

It's normal that the patched boot.img is smaller.

PJF16 said:
It's normal that the patched boot.img is smaller.
Click to expand...
Click to collapse
I know that.
But this is quite smaller than usual and, anyway, it doesn't boot after flashing

Anyone have any issues with v4A magisk module? After I flashed it I lost the ability to turn on wifi. Wondering if anyone else has had that issue.

where can i find the pre patched boot img of 10.0.12.0?

Just use the one for 10.0.11.0.

nosidefcp said:
where can i find the pre patched boot img of 10.0.12.0?
Click to expand...
Click to collapse
Hi, here You can find patched boot for 10.0.12.0:
https://yadi.sk/d/aVlSEC_r7xj0VA

Open Beta 1 for OnePlus 8 Pro ROOT

Here is the patched boot img for OB1. I now have root again.
https://drive.google.com/file/d/1WBJ_0TLp_TFAMoN2ONmvWU4iMeeaHiY8/view?usp=sharing
Try this at your own risk. Worked great for me but I make no warranties if you blow up you phone.
Copy the above to you ADB folder
Type ABD reboot bootloader
Type fastboot boot OB1_patched.img
If the phone boots properly, go back into fastboot and type
Fastboot flash boot_a OB1_patched.img
Fastboot flash boot_b OB1_patched.img
Fastboot reboot.
You should be rooted on OB1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Deleted

@Mike02z My magisk is not installed properly with your patched boot img.
I came from oos 10 stable not rooted and followed all the steps you wrote, but when i launch magisk manager i see N/A on the status (See screenshot)
can sombody help me?
Thanks

I know this may sound silly but your bootloader is unlocked, correct? Bootloader must be unlocked.
I extracted the boot.img using payload dumper and Python. I then copied the boot.img to my device. I then ran Magisk and chose patch boot.img. selected it from my Download folder, patched it then copied it to my ADB/Fastboot directory. I booted the new patched image and it worked fine and showed I was rooted. I then flashed both slots, rebooted again and now I have permanent root.
Not sure why it's not working for you if you're unlocked.

Hiya!
Same thing here, bootloader unlocked, followed your instructions to the T and still no root. I downloaded the official canary_manager from github, could it be that? That the manager is the wrong one?
I also see your model is IN2025 but mine is IN2023 could that be it?

Mike02z said:
I know this may sound silly but your bootloader is unlocked, correct? Bootloader must be unlocked.
I extracted the boot.img using payload dumper and Python. I then copied the boot.img to my device. I then ran Magisk and chose patch boot.img. selected it from my Download folder, patched it then copied it to my ADB/Fastboot directory. I booted the new patched image and it worked fine and showed I was rooted. I then flashed both slots, rebooted again and now I have permanent root.
Not sure why it's not working for you if you're unlocked.
Click to expand...
Click to collapse
I had the same issue can you let me know what where you got your version of magisk manager are you using?
thanks

Ok I managed to get root with a bit of a workaround:
1. Download the patched boot.img from here to your phone
2. Open Magisk Manager Canary
3. Go to install - Patch image file - select the OB1_patched.img you downloaded
4. Redo step 3 only this time select the output file magisk_patched.img (the reason was that the magisk_patched.img file had a size of 0b, redoing the step with the new patched img solved it and it was back to 43MB)
5. Copy the magisk_patched.img to your adb folder on your PC or Mac
6. ADB reboot bootloader
7. Fastboot boot magisk_patched.img (do not skip this step so you know your phone will boot and you can check if you have root)
8. Fastboot flash boot_a magisk_patched.img
9. Fastboot flash boot_b magisk_patched.img
10. Fastboot reboot
This did it for me and I know have root on my phone so hope it helps

Shredz98 said:
Ok I managed to get root with a bit of a workaround:
1. Download the patched boot.img from here to your phone
2. Open Magisk Manager Canary
3. Go to install - Patch image file - select the OB1_patched.img you downloaded
4. Redo step 3 only this time select the output file magisk_patched.img (the reason was that the magisk_patched.img file had a size of 0b, redoing the step with the new patched img solved it and it was back to 43MB)
5. Copy the magisk_patched.img to your adb folder on your PC or Mac
6. ADB reboot bootloader
7. Fastboot boot magisk_patched.img (do not skip this step so you know your phone will boot and you can check if you have root)
8. Fastboot flash boot_a magisk_patched.img
9. Fastboot flash boot_b magisk_patched.img
10. Fastboot reboot
This did it for me and I know have root on my phone so hope it helps
Click to expand...
Click to collapse
that makes complete sense now, but what version of magisk manager are you using please?
thanks

bigAL99 said:
that makes complete sense now, but what version of magisk manager are you using please?
thanks
Click to expand...
Click to collapse
It worked flawlessly for me now, so hopefully you'll have the same luck!
The latest one off of his github canary release: fbaf2bde (297).

Shredz98 said:
It worked flawlessly for me now, so hopefully you'll have the same luck!
The latest one off of his github canary release: fbaf2bde (297).
Click to expand...
Click to collapse
i amy be completely stupid but I can't find this channel or this release :crying:

bigAL99 said:
i amy be completely stupid but I can't find this channel or this release :crying:
Click to expand...
Click to collapse
As I'm not fully clear on posting links here I've sent you the link to the official release via PM, hope it helps

Any idea how to keep root comming from 10.5.13?

RicardoDimm said:
Any idea how to keep root comming from 10.5.13?
Click to expand...
Click to collapse
I believe you'll have to do the steps, as the firmware and boot.img would've changed since you're upgrading to Android 11. I could be wrong though

bigAL99 said:
i amy be completely stupid but I can't find this channel or this release :crying:
Click to expand...
Click to collapse
You may download it here.
https://github.com/topjohnwu/magisk_files/blob/canary/app-debug.apk

thnx, for me it worked flawlessly :good:

works flaweless the way you explained it !
I now have root on OB1 , thanks m8

I never got it to boot after doing the inactive slot flash. Since then I have tried this - including the a and b flash, but still stuck on the OnePlus boot animation. Besides MSM, is there any way to get this to boot. I have same AA global device.

Is anyone able to patch boot.img and fastboot the patched image on IN2021. I downloaded the OB1 OTA and extracted boot.img. I am able to fastboot the extracted boot.img. Installed magisk canary and patched the boot.img and got the magisk_patched.img. For some reason when I boot the patched img file it goes to boot loop.

Hi all, can someone clarify if the steps highlighted are to be done before/after using local upgrade on the OB1 zip?

[email protected] said:
Is anyone able to patch boot.img and fastboot the patched image on IN2021. I downloaded the OB1 OTA and extracted boot.img. I am able to fastboot the extracted boot.img. Installed magisk canary and patched the boot.img and got the magisk_patched.img. For some reason when I boot the patched img file it goes to boot loop.
Click to expand...
Click to collapse
I don't think you need to patched the boot img as it is already patched as per OP post.

Updating your rooted Pixel 4a 5G on Windows

I'll try to make a step by step to update your Bramble (Pixel 4a 5G) with the latest updates assuming you're rooted (otherwise it would update normally). These steps worked for me. I know there are other ways. If you want to link to another way, please do.
Make sure you have the latest USB drivers: https://developer.android.com/studio/run/win-usb
and the latest platform tools: https://developer.android.com/studio/releases/platform-tools.html
NOTICE: The latest version (34) gave me this error when updating: "FAILED (Sparce file is too large or invalid)". When updating again with version 33 everything went fine.
Some Magisk modules may cause bootloops so it's best to disable them and to reboot before updating.
Unhide Magisk.
Download the latest Factory Image (look carefully to use the right one: Verizon or other) https://developers.google.com/android/images#bramble
Unzip this in your adb folder (I'm assuming you have this already set up as you're rooted already)
Edit the 'flash-all.bat' in Notepad and look for the "-w" in the last line. Remove the "-w" as this will wipe your phone
With your device plugged into the computer, open a command prompt in the adb folder. (pen the folder, hold down Shift and right click inside the folder, "Open Command window here")
Run this command to go into bootloader on your phone:
Code:
adb reboot bootloader
Now run the flash-all.bat from the command line
Code:
flash-all.bat
This can take a while, and sometimes it even fails the first time. Don't worry and try again.
In the extracted folder there is another zip file. Extract this too.
Now inside the extracted folder, look for boot.img
Your phone should be finished upgrading by now and booted normally
Copy the boot.img file to your phone (remember where you put it)
Open Magisk Manager (you should be on the Update Channel: Canary in the Settings)
Click on "install" (the top one)
Select "Select and Patch a file" and browse to your boot.img
Click "Let's go"
Magisk manager will now patch your boot.img to a rooted version and will tell you where it saved the file, and it's name
Now move this file to your adb folder and open the folder in the command line again
Go into bootloader again by running this code
Code:
adb reboot bootloader
When in bootloader mode run this code
Code:
fastboot flash boot magisk_patched_xxxxx.img [replace the filename with the one you have]
Reboot your updated and now rooted device!
Code:
fastboot reboot
Now can can turn back on your Magisk modules and hide it.

You can also update using the ota.
Download both the full factory image (fi) and ota
Extract boot.img from the fi, and patch on your phone using magisk - place in the same folder as the ota (on your pc)
Disable all modules in magisk. I also disable adaway (may not be necessary)
Reboot
Boot into recovery. Once the android is on the screen, hold power then press vol +
Select apply update from adb, then on the pc in a command window or powershell run
Code:
adb sideload xxx.zip (where xxx is the name of the ota image)
Once done, reboot into bootloader
Code:
adb reboot bootloader
Flash the patched boot
Code:
fastboot flash boot xxx.img (where xxx is the name of your patched boot img)
Reboot into system, give the phone a few mins. Enable all magisk modules, reboot, enable adaway, reboot. Done.

drdionysius said:
I'll try to make a step by step to update your Bramble (Pixel 4a 5G) with the latest updates assuming you're rooted (otherwise it would update normally). These steps worked for me. I know there are other ways. If you want to link to another way, please do.
Some Magisk modules may cause bootloops so it's best to disable them and te reboot before updating.
Download the latest Factory Image (look carefully to use the right one: Verizon or other) https://developers.google.com/android/ota#bramble
Unzip this in your adb folder (I'm assuming you have this already set up as you're rooted already)
Edit the 'flash-all.bat' in Notepad and look for the "-w" in the last line. Remove the "-w" as this will wipe your phone
With your device plugged into the computer, open a command prompt in the adb folder. (pen the folder, hold down Shift and right click inside the folder, "Open Command window here")
Run this command to go into bootloader on your phone:
Code:
adb reboot bootloader
Now run the flash-all.bat from the command line
Code:
flash-all.bat
This can take a while and sometimes it even fails the first time. Don't worry and try again.
Meanwhile you can download the latest factory image: https://developers.google.com/android/images#bramble
Extract the zip file and open the extracted folder. In there is another zip file. Extract this too.
Now inside the extracted folder look for boot.img
Your phone should be finished upgrading by now and booted normally
Copy the boot.img file to your phone (remember where you put it)
Open Magisk Manager (you should be on the Update Channel: Canary in the Settings)
Click on "install" (the top one)
Select "Select and Patch a file" and browse to your boot.img
Click "Let's go"
Magisk manager will now patch your boot.img to a rooted version and will tell you where it saved the file and it's name
Now move this file to your adb folder and open the folder in the command line again
Go into bootloader again by running this code
Code:
adb reboot bootloader
When in bootloader mode run this code
Code:
fastboot flash boot magisk_patched_xxxxx.img [replace the filename with the one you have]
Reboot your updated and rooted device!
Click to expand...
Click to collapse
Perfect, Thank you, would you please to do another guide of how to enable 5G and Volte

mx597turbo said:
You can also update using the ota.
Download both the full factory image (fi) and ota
Extract boot.img from the fi, and patch on your phone using magisk - place in the same folder as the ota (on your pc)
Disable all modules in magisk. I also disable adaway (may not be necessary)
Reboot
Boot into recovery. Once the android is on the screen, hold power then press vol +
Select apply update from adb, then on the pc in a command window or powershell run
Code:
adb sideload xxx.zip (where xxx is the name of the ota image)
Once done, reboot into bootloader
Code:
adb reboot bootloader
Flash the patched boot
Code:
fastboot flash boot xxx.img (where xxx is the name of your patched boot img)
Reboot into system, give the phone a few mins. Enable all magisk modules, reboot, enable adaway, reboot. Done.
Click to expand...
Click to collapse
This works perfectly! Thank you for sharing this method! Worked flawlessly on my bramble to get it to the February security update! Very amazing!

drdionysius said:
I'll try to make a step by step to update your Bramble (Pixel 4a 5G) with the latest updates assuming you're rooted (otherwise it would update normally). These steps worked for me. I know there are other ways. If you want to link to another way, please do.
Some Magisk modules may cause bootloops so it's best to disable them and te reboot before updating.
Download the latest Factory Image (look carefully to use the right one: Verizon or other) https://developers.google.com/android/ota#bramble
Unzip this in your adb folder (I'm assuming you have this already set up as you're rooted already)
Edit the 'flash-all.bat' in Notepad and look for the "-w" in the last line. Remove the "-w" as this will wipe your phone
With your device plugged into the computer, open a command prompt in the adb folder. (pen the folder, hold down Shift and right click inside the folder, "Open Command window here")
Run this command to go into bootloader on your phone:
Code:
adb reboot bootloader
Now run the flash-all.bat from the command line
Code:
flash-all.bat
This can take a while and sometimes it even fails the first time. Don't worry and try again.
Meanwhile you can download the latest factory image: https://developers.google.com/android/images#bramble
Extract the zip file and open the extracted folder. In there is another zip file. Extract this too.
Now inside the extracted folder look for boot.img
Your phone should be finished upgrading by now and booted normally
Copy the boot.img file to your phone (remember where you put it)
Open Magisk Manager (you should be on the Update Channel: Canary in the Settings)
Click on "install" (the top one)
Select "Select and Patch a file" and browse to your boot.img
Click "Let's go"
Magisk manager will now patch your boot.img to a rooted version and will tell you where it saved the file and it's name
Now move this file to your adb folder and open the folder in the command line again
Go into bootloader again by running this code
Code:
adb reboot bootloader
When in bootloader mode run this code
Code:
fastboot flash boot magisk_patched_xxxxx.img [replace the filename with the one you have]
Reboot your updated and rooted device!
Click to expand...
Click to collapse
checking product...
OKAY [ 0.069s]
checking version-bootloader...
OKAY [ 0.069s]
checking version-baseband...
OKAY [ 0.070s]
sending 'boot' (98304 KB)...
OKAY [ 0.409s]
writing 'boot'...
FAILED (remote: Failed to write to partition Not Found)
finished. total time: 0.929s
Press any key to exit...
hi I am trying to update to the Feb update and I get to "writing boot" but it always fails. What am I doing wrong? I am on stock with Magisk and Elemental X Kernal, that is pretty much it.
Thanks.
_______________________
I figured it out... I need to update my adb folder on my comp, thankssssss worked well.

kazemitsui said:
checking product...
OKAY [ 0.069s]
checking version-bootloader...
OKAY [ 0.069s]
checking version-baseband...
OKAY [ 0.070s]
sending 'boot' (98304 KB)...
OKAY [ 0.409s]
writing 'boot'...
FAILED (remote: Failed to write to partition Not Found)
finished. total time: 0.929s
Press any key to exit...
hi I am trying to update to the Feb update and I get to "writing boot" but it always fails. What am I doing wrong? I am on stock with Magisk and Elemental X Kernal, that is pretty much it.
Thanks.
Click to expand...
Click to collapse
Did you pick the right version?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

drdionysius said:
Did you pick the right version?
View attachment 5216649
Click to expand...
Click to collapse
Yea I figured it out, I needed to update my adb folder on my computer!

I'm having a problem myself with patching the boot.img through Magisk Manager. It says "installation failed".
-update-
Solved. I had to update Magisk Manager Canary.

mx597turbo said:
You can also update using the ota.
Download both the full factory image (fi) and ota
Extract boot.img from the fi, and patch on your phone using magisk - place in the same folder as the ota (on your pc)
Disable all modules in magisk. I also disable adaway (may not be necessary)
Reboot
Boot into recovery. Once the android is on the screen, hold power then press vol +
Select apply update from adb, then on the pc in a command window or powershell run
Code:
adb sideload xxx.zip (where xxx is the name of the ota image)
Once done, reboot into bootloader
Code:
adb reboot bootloader
Flash the patched boot
Code:
fastboot flash boot xxx.img (where xxx is the name of your patched boot img)
Reboot into system, give the phone a few mins. Enable all magisk modules, reboot, enable adaway, reboot. Done.
Click to expand...
Click to collapse
Hi ! Great Thank you is the best option without Twrp for update my Pixel 4a 5g.
Very simple, just a mistake with unautorized adb on my mac os but after Google it can resolve it and update quickly no do uninstall magisk but just uncheck mod same as Twrp.
Very Thank you have a good day
EDIT : NO !!! After re-check my mods the Pixel wont start ??? Or Re Start Or factory Reset ??? No no no it(s the second update do factory reset !!!! without Twrp is not good

ggkameleon said:
Hi ! Great Thank you is the best option without Twrp for update my Pixel 4a 5g.
Very simple, just a mistake with unautorized adb on my mac os but after Google it can resolve it and update quickly no do uninstall magisk but just uncheck mod same as Twrp.
Very Thank you have a good day
EDIT : NO !!! After re-check my mods the Pixel wont start ??? Or Re Start Or factory Reset ??? No no no it(s the second update do factory reset !!!! without Twrp is not good
Click to expand...
Click to collapse
I had the same problem, make sure to boot into safe mode, as this will automatically turn off all magisk modules. The clock mod caused this for me, so make sure to uninstall that.
Here is a video I found:
if the volume key to go into safe mode does not work, (it did not for me), as soon as you reach the os, before it shuts down, long press the power button and long press restart. Then click on ok to boot into safe mode. Hope this helps!

3dcantaloupe said:
I had the same problem, make sure to boot into safe mode, as this will automatically turn off all magisk modules. The clock mod caused this for me, so make sure to uninstall that.
Here is a video I found:
if the volume key to go into safe mode does not work, (it didd not for me), as soon as you reach the os, before it shuts down, long press the power button and long press restart. Then click on ok to boot into safe mode. Hope this helps!
Click to expand...
Click to collapse
Hi ! Thanks. I have the center clock too.
I do flash the stock boot img for restart it and test for remove mods but I can't.
I have flash again the Magisk boot img but again bootloop.
I have flash again the stock boot img and see your thread. Thanks

ggkameleon said:
Hi ! Thanks. I have the center clock too.
I do flash the stock boot img for restart it and test for remove mods but I can't.
I have flash again the Magisk boot img but again bootloop.
I have flash again the stock boot img and see your thread. Thanks
Click to expand...
Click to collapse
yes, when you go into safe mode, it disables your magisk modules so that you can boot with the magisk patched boot image! Make sure to boot into safe mode when you have the magisk boot image installed and not the stock image. If you have any more questions, feel free to ask me

3dcantaloupe said:
yes, when you go into safe mode, it disables your magisk modules so that you can boot with the magisk patched boot image! Make sure to boot into safe mode when you have the magisk boot image installed and not the stock image. If you have any more questions, feel free to ask me
Click to expand...
Click to collapse
Ok thanks but now I'm on stock boot img.
If I understand I flash again on fastboot the magisk boot img and restart on safe mod for uninstall magisk mods.
But how restart on safe mod.
Thanks

3dcantaloupe said:
yes, when you go into safe mode, it disables your magisk modules so that you can boot with the magisk patched boot image! Make sure to boot into safe mode when you have the magisk boot image installed and not the stock image. If you have any more questions, feel free to ask me
Click to expand...
Click to collapse
I'm curious, are you running the current March update?

ggkameleon said:
Ok thanks but now I'm on stock boot img.
If I understand I flash again on fastboot the magisk boot img and restart on safe mod for uninstall magisk mods.
But how restart on safe mod.
Thanks
Click to expand...
Click to collapse
Power off the phone
Turn it on
Once you see the Google boot logo, press and hold the Volume Down key
Keep holding the Volume Down key until the phone enters Safe Mode. You will see a watermark on the bottom-left that says "Safe Mode".

DJBhardwaj said:
Power off the phone
Turn it on
Once you see the Google boot logo, press and hold the Volume Down key
Keep holding the Volume Down key until the phone enters Safe Mode. You will see a watermark on the bottom-left that says "Safe Mode".
Click to expand...
Click to collapse
Ok thanks thank you.
I test it. Have a good day

3dcantaloupe said:
yes, when you go into safe mode, it disables your magisk modules so that you can boot with the magisk patched boot image! Make sure to boot into safe mode when you have the magisk boot image installed and not the stock image. If you have any more questions, feel free to ask me
Click to expand...
Click to collapse
Yesssss ! I don't know how can pass safedod but many times restart on "Restart or Factory Reset"
I have flash many times stock boot img and magisk boot img anf inaly restart on safe mod and restart with magisk install and work !!!!
it's more difficult as Twrp installed. I don't know why Google don't want Twrp

artlan said:
I'm curious, are you running the current March update?
Click to expand...
Click to collapse
yes, I am running RQ2A.210305.006

ggkameleon said:
Yesssss ! I don't know how can pass safedod but many times restart on "Restart or Factory Reset"
I have flash many times stock boot img and magisk boot img anf inaly restart on safe mod and restart with magisk install and work !!!!
it's more difficult as Twrp installed. I don't know why Google don't want Twrp
Click to expand...
Click to collapse
Not that they don't want twrp, but no one is taking the initiative to fork it over to our device yet. It will eventually make it I bet! Using the hardware buttons as DJBharadwaj stated did not work, and I had to instead I had to wait for the phone to boot, then I longpressed restart to boot into safe mode.

Hi ! And it's possible to flash the magisk mod Center Clock ? Or make bootloop ?

How To Guide Flash/Install TWRP on Realme GT Master Edition RMX3360 (Indian variant)

TWRP flashing guide for Realme GT Master edition RMX3360
Flash at your own risk. You might LOSE all data on your phone.
( I will be not responsible for any damage to your device )
Prerequisites :
Your Bootloader Should be Unlocked. Click Here For Instructions.
First Back up all of your data and files present on the phone because the phone might be erased from the process.
Install Minimal ADB and Fastboot tool from here: LINK
Get the A.09 vbmeta.img files for the Stock firmware. If you are using A.09 firmware then vbmeta.img is needed from A.09 firmware file. LINK
Get the TWRP image file and rename it to twrp.img . Unofficial TWRP Link
The process to disable verity/Verification (Important for Flashing TWRP Recovery):
Reboot the phone to fastboot (Vol Down + Power ).
Connect the phone to the computer using an USB data cable. Preferred to use the stock USB cable.
Search for Minimal adb and fastboot icon in the 'Windows search' and right-click for 'Locate file location' option.
Copy and Place that vbmeta.img in the Minimal adb and fastboot folder.
Hold Shift and Right-click in that directory and click on the options 'open cmd terminal there'.
Type fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img in the cmd terminal.
Reboot the phone again to fastboot mode.
Follow the further process.
The process to install TWRP :
Reboot the phone to fastboot (Vol Down + Power ).
Connect the phone to the computer using an USB data cable. Preferred to use the stock USB cable.
Search for Minimal adb and fastboot icon in the 'Windows search' and right-click for 'Locate file location' option.
Copy and Place that twrp.img in the Minimal adb and fastboot folder.
Hold Shift and Right-click in that directory and click on the options 'open cmd terminal there'.
Type fastboot boot twrp.img in the cmd terminal.
The phone will boot in TWRP recovery and after that go to Advanced > Flash Current TWRP.
Done you have installed TWRP in your device.
TWRP flashed now Enjoy Flashing Custom files and ZIPS.

pkm774 said:
TWRP flashing guide for Realme GT Master edition RMX3360
Flash at your own risk. You might LOSE all data on your phone.
( I will be not responsible for any damage to your device )
Prerequisites :
Your Bootloader Should be Unlocked. Click Here For Instructions.
First Back up all of your data and files present on the phone because the phone might be erased from the process.
Install Minimal ADB and Fastboot tool from here: LINK
Get the A.09 vbmeta.img files for the Stock firmware. If you are using A.09 firmware then vbmeta.img is needed from A.09 firmware file. LINK
Get the TWRP image file and rename it to twrp.img . Unofficial TWRP Link
The process to disable verity/Verification (Important for Flashing TWRP Recovery):
Reboot the phone to fastboot (Vol Down + Power ).
Connect the phone to the computer using an USB data cable. Preferred to use the stock USB cable.
Search for Minimal adb and fastboot icon in the 'Windows search' and right-click for 'Locate file location' option.
Copy and Place that vbmeta.img in the Minimal adb and fastboot folder.
Hold Shift and Right-click in that directory and click on the options 'open cmd terminal there'.
Type fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img in the cmd terminal.
Reboot the phone again to fastboot mode.
Follow the further process.
The process to install TWRP :
Reboot the phone to fastboot (Vol Down + Power ).
Connect the phone to the computer using an USB data cable. Preferred to use the stock USB cable.
Search for Minimal adb and fastboot icon in the 'Windows search' and right-click for 'Locate file location' option.
Copy and Place that twrp.img in the Minimal adb and fastboot folder.
Hold Shift and Right-click in that directory and click on the options 'open cmd terminal there'.
Type fastboot boot twrp.img in the cmd terminal.
The phone will boot in TWRP recovery and after that go to Advanced > Flash Current TWRP.
Done you have installed TWRP in your device.
TWRP flashed now Enjoy Flashing Custom files and ZIPS.
Click to expand...
Click to collapse
I am getting an error in the last step (Flash current TWRP): "failed to create ramdisk to flash". Any idea?

aprilfoo said:
I am getting an error in the last step (Flash current TWRP): "failed to create ramdisk to flash". Any idea?
Click to expand...
Click to collapse
Maybe more help for the issue i just mentioned above: in the temporary TWRP, the file ramdisk-files.txt contains a line for "mnt/vendor/persist", which does not exist, and thus the cpio command fails.

aprilfoo said:
Maybe more help for the issue i just mentioned above: in the temporary TWRP, the file ramdisk-files.txt contains a line for "mnt/vendor/persist", which does not exist, and thus the cpio command fails.
Click to expand...
Click to collapse
Screenshot can help better, try taking and sending it here.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

hello sir is it compatible with rmx3363 ?

Okay Stupid question: Has Realme officially released bootloader unlock tool? I know they have released kernel and drivers.

xeltos said:
Okay Stupid question: Has Realme officially released bootloader unlock tool? I know they have released kernel and drivers.
Click to expand...
Click to collapse
well yes for some phones but deeptest somehow works for others if your lucky test them all and see ^^

is this method work for latest Android 12 for installing twrp ?

pankaj9pankaj9334 said:
is this method work for latest Android 12 for installing twrp ?
Click to expand...
Click to collapse
Currently, A12 Twrp is under development by twrp team. So you have to wait.

ites working with rmx3363 finally i got twrp to work ^^ thanks

NextB said:
ites working with rmx3363 finally i got twrp to work ^^ thanks
Click to expand...
Click to collapse
Allright, you are the best.
Without any modification of twrp.img ?
On Android 11 Firmware ?

guizzzmo said:
Allright, you are the best.
Without any modification of twrp.img ?
On Android 11 Firmware ?
Click to expand...
Click to collapse
without any

NextB said:
without any
Click to expand...
Click to collapse
I can boot this twrp with fastboot boot twrp.img
but if i try to do Advanced > Flash Current TWRP
i have the same error than as @aprilfoo above

guizzzmo said:
I can boot this twrp with fastboot boot twrp.img
but if i try to do Advanced > Flash Current TWRP
i have the same error than as @aprilfoo above
Click to expand...
Click to collapse
Actually i found a workaround but i prefer not even to share it because of a bigger issue: the OP forgot to mention that: 'Installing Magisk is must if you are planning to press "Flash Current TWRP" when flashing alongside stock ROM'. I did not install Magisk and ended up with a completely dysfunctional phone and had to flash again the stock OS.
So i suggest to wait a bit more (some ROMs are in release candidate in the Telegram group)

aprilfoo said:
Actually i found a workaround but i prefer not even to share it because of a bigger issue: the OP forgot to mention that: 'Installing Magisk is must if you are planning to press "Flash Current TWRP" when flashing alongside stock ROM'. I did not install Magisk and ended up with a completely dysfunctional phone and had to flash again the stock OS.
So i suggest to wait a bit more (some ROMs are in release candidate in the Telegram group)
Click to expand...
Click to collapse
ok thanks for the reply. wich telegram group?

guizzzmo said:
ok thanks for the reply. wich telegram group?
Click to expand...
Click to collapse
@realmegtmasterupdates - telegram channel publications statistics Realme GT Master | UPDATES
telegram channel publications statistics of Realme GT Master | UPDATES telegram channel. All about Realme GT Master - RMX3366 ROMs, Kernels, Guides, Mods, NEWS, everything. Stay up-to-date with us! Official Group: @RealmeGTMaster Photography : @RMGTMasterPhotography Gaming : @RMGTMasterGaming...
telemetr.io

Use This
https://www.getdroidtips.com/twrp-recovery-realme-gt-master-edition/

Oh i see the problem, it's because the new partition slot A/B.
Ok i have magisk installed on stock rom but i think i will waiting. I stay on UI 2.0 with full root, magisk, lsposed, safetynet, and no bugs

How To Guide [ROOT] [FLASH STOCK]

DISCLAIMER:
Please post failures and successes. Keep it relevant, everything else to the DMs please. It makes it easier for others to Q&A. Everyone thanks you for your understanding.
***IF YOU ARE NEW BEWARE!!! BEFORE YOU CHANGE ANYTHING MAKE A BACKUP. LET THIS APPLY TO EVERYTHING. WHENEVER THE OPTION TO BACKUP IS AVAILABLE IT WOULD BE WISE TO DO SO. FAILURE TO BACKUP YOUR DEVICE WILL RESULT IN LOSS OF DATA***
ALL LINKS ALLOWED, APPROVED AND/OR UTILIZED BY XDA. SPECIAL THANKS TO ALL THE DEVS WHO CREATED THE TOOLS WITHOUT WHICH THIS WOULD NOT BE POSSIBLE. I DIDN'T BUILD ANY SOFTWARE MENTIONED IN THIS POST. IF YOU BRICK YOUR PHONE, DO NOT BLAME ME. I'M NOT TELLING YOU HOW TO DO IT, BUT NARRATING A GUIDE TO HOW I DID IT. YOU HAVE BEEN WARNED
REVVL V+ 5G TMOBILE VARIANT ANDROID 11
IT SHOULD BE NOTED THAT SOME PEOPLE ARE REPORTING LOSING WIFI AFTER ROOT, AS HAVE I. I HAVE NOT YET FIGURED OUT HOW TO FIX THIS. I'M THANKFUL FOR ANY ASSISTANCE. FLASHED STOCK BOOT_A DIDN'T FIX IT, ONLY FLASHING BACK TO STOCK ROM. ON ANOTHER IDENTICAL PHONE DIDN'T LOSE WIFI. YOUR GUESS IS AS GOOD AS MINE. LOOKING INTO IT, NO PROMISES
Without further ado, let's start at the unboxing.
1) PREP PHONE:
power on. navigate to settings>about phone and tap "build number" seven times to enable developer options.
navigate to settings>system>developer options and enable "USB Debugging" and "OEM unlock"
FIRST disconnect the device from your comp THEN power the device off.
2) DONWLOAD PYTHON & DRIVERS:
Python
BE SURE TO TICK THE BOX THAT SAYS ADD PYTHON TO PATH and install.
Download and install mediatek drivers from here:
Mediatek USB drivers
Download and install UsbDk from here:
UsbDk
Download MTK client from here:
MTK client
and extract to the desktop. Open the folder and move everything to
C:>Users>[username]>AppData>Local>Programs>Python>Python310
In the 310 directory press Alt + D to highlight your directory path and type CMD and hit enter. This opens a command prompt in the Python310 directory.
In cmd type this command without "":
"python setup.py install"
Go make a sandwich. Preferably turkey with mustard.
When you finish your sandwich, come back and type this command without "":
"python -m pip install -r requirements.txt"
Do not exit the command window.
3) BOOT INTO B ROM MODE:
This is kind of tricky when you don't know it. The screen will will be black. Sometimes, the device will not even vibrate. There's no sunbathing android, no "No Command", no fastboot, no download mode, no recovery- nothing, nada, zip, zilch, goose egg.
Make sure you unplug the device entirely from charger and pc BEFORE you power off. Now that you properly powered off, hold ONLY BOTH volume + - keys while you connect it to your PC. Try to be quick about it. DO NOT TOUCH THE POWER KEY. Continue to hold the volume keys until you know your device connected. When you hear your device connected jingle immediately let go. The screen will remain blacked out and unresponsive. It's normal.
Let's make sure we did it right. Enter the following command without ":
"python mtk e metadata,userdata,md_udc"
Disconnect and power on. If the device has been reset, then you have confirmation.
4) PREP PHONE AGAIN (STEP 1):
5) UNLOCK BOOTLOADER:
Enter the following command without ":
"python mtk da seccfg unlock"
~To relock the bootloader in the future use command "python mtk da seccfg lock". If you flash a custom recovery/ROM and want to return to stock, then you must unroot with magisk first, then flash stock ROM with SP flash tool at the end of this post~
Power on. On the splash screen you will see system type:
"Orange State
Your device is corrupted. Device has been unlocked and cannot be trusted. Press Power key to boot.
Will Reboot in 5 seconds."
This will happen each time you boot the device because your bootloader is now unlocked.
6) PREP PHONE AGAIN (STEP 1):
7) ENABLE ADB FASTBOOT COMMANDS:
Download sdk platform tools here:
sdk platform tools
Extract.
Navigate to the platform tools folder and type Alt+D to highlight directory and type CMD to open a cmd window in platform tools.
Connect device to pc and choose file transfer.
Enter the following command without ":
"adb devices"
A prompt will appear on your phone, click allow.
Enter the following command (again) without ":
"adb devices"
First you'll see a random, arbitrary number. Second time you should see your device serial number and "Authorized", "Allowed", or "Device".
Keep this cmd window open.
8) DOWNLOAD MAGISK AND PATCH BOOT IMG:
Download Magisk from here:
Magisk
Move it to your phone and install. You'll need to allow the installation from unknown sources.
Download firmware from here:
T-Mobile_REVVL_V%252B_5G.zip
Unzip and move boot_a to the downloads folder on your phone.
On your phone, open Magisk and click install and choose boot_a.
Make sure magisk_patched file is in your phone's download folder.
In your platform tools cmd window enter the following command without ":
"adb pull /sdcard/Download/magisk_patched_[numbers].img"
9) ENTER FASTBOOT MODE:
Disconnect device and power off. Hold Vol - and power to enter fastboot mode.
Connect device to PC.
10) ACHIEVE ROOT:
***NOTE: IN THIS STEP YOU MUST LOCATE THE PATCHED FILE ON YOUR PC AND COPY AS PATH. PASTE IT IN THE CMD WINDOW IN PLACE OF "[path to patched file]"***
In the platform tools cmd window enter the following command without ":
"fastboot flash boot [path to patched file]"
Now that you've achieved root, you can play around a little bit. But be careful what you go deleting if you get debloat happy like me and delete your NVRAM & wifi. Just in case you do, here's how to return to stock.
NVRAM backup. This video makes it look easy as pie. (It IS easy)
NVRAM Backup Tutorial
Now we have to bypass DA else SP flash tool will not be able to flash ROM.
Open cmd window and type the following without "":
"python -m pip install pyusb pyserial json5"
Then, update by entering the following command without "":
"python.exe -m pip install --upgrade pip"
Download LIBUSB:
LIBUSB
Run LIBUSB Win 32 filter installer and select Mediatek driver
Enter B ROM mode and connect to PC
Navigate to bypass tool and open "brom.bat"
Close cmd...
Run "flash_tool.exe" in sp flash folder
Options>options>connection tick UART
That's it. Now you can flash with sp flash without encountering error
Here is a helpful link that came from a senior mod:
mtk tool
Download SP Flash tool here:
SP Flash
Extract and launch flash_tool application
Download scatter mt6833 here:
MT6833_scatter.txt
Download bypass tool from here:
bypass tool
download rom2box:
rom2box
Download OTA and use a payload dumper to extract boot and scatter. You can also get DA, but it does nothing. You must bypass DA in order to flash ROM.
OTA
THIS SECTION IS FOR LATER REFERENCING, DISREGARD ANYTHING BELOW THIS
[A13 ota news https://www.t-mobile.com/support/devices/software-updates/t-mobile-revvl-v-plus-android-update]
[Twrp https://www.xda-developers.com/twrp-3-6-0-release-android-11-support/?_ga=2.195721068.1777813512.1675477697-1767133243.1662515191]
~fastboot set_active other
~fastboot flash recovery_a twrp file
~fastboot flash recovery_b twrp file
[Sprout https://dl.twrp.me/sprout/]
https://forum.xda-developers.com/t/guide-porting-twrp-without-source.3843473/
https://www.mediafire.com/download/sxq4cz8bddmr49
https://www.mediafire.com/file/irigs9iviy3sobw/T-Mobile_REVVL_V%2B_5G.zip/file
https://download1526.mediafire.com/ih0pus48i1kg/mwl6h20noutg005/revvplus.zip
[Patched boot_a pending verification https://forum.xda-developers.com/attachments/magisk_patched-25100_hiu69-img.5648347/]
[FLASH STOCK MODEM FILE]
My next guide will be how to use assurance wireless with ANY phone. I'm using assurance wireless on my Oneplus N200 (DE2118).

Hi. I read many posts of yours regarding the REVVL V+ 5G, I was encouraged by your progress, and took comfort that someone else had some of the same struggles that I did. I was able to unlock the bootloader, I was able to root the phone (using an img file posted by someone else here; I hadn't yet read your root recipe), but I was no longer able to connect to wifi. (is this familiar?) In trying to undo the mess, I ended up making my phone unbootable.
I wanted to install stock ROM from scratch. I read your instructions, but there's no scatter file in the ROM that you posted. So I'm confused.
I figured that I could install the stock ROM zip via TWRP; I googled and found a TWRP for "Sprout" (the codename of our device), but for the life of me I couldn't install it on my phone, no matter what I tried.
You're ahead of me here; perhaps you can get me on track. Right now, my phone isn't booting at all.
Thank you!

smuskat said:
Hi. I read many posts of yours regarding the REVVL V+ 5G, I was encouraged by your progress, and took comfort that someone else had some of the same struggles that I did. I was able to unlock the bootloader, I was able to root the phone (using an img file posted by someone else here; I hadn't yet read your root recipe), but I was no longer able to connect to wifi. (is this familiar?) In trying to undo the mess, I ended up making my phone unbootable.
I wanted to install stock ROM from scratch. I read your instructions, but there's no scatter file in the ROM that you posted. So I'm confused.
I figured that I could install the stock ROM zip via TWRP; I googled and found a TWRP for "Sprout" (the codename of our device), but for the life of me I couldn't install it on my phone, no matter what I tried.
You're ahead of me here; perhaps you can get me on track. Right now, my phone isn't booting at all.
Thank you!
Click to expand...
Click to collapse
Hey, I finished the guide. You can return to stock following the guide above. As you may have noticed I edited this message instead of posting again. It's okay, cause I brought good news, right? Cheers

R41N MuTT said:
i totally forgot, yeah, i will look up the proper method to install twrp. it's supposed to be easy. i thought i was going to have to port twrp-and i still might- so i'm looking into it. i need to flash twrp myself. there is supposed to be a way to use rom2box or spflash or twrp or something to make a flashable zip. i don't know if that's a thing. it seems to me somebody needs to build a preinstaller that automatically flashes each img. for you. like a 1 click. if we can get twrp on this, that's the next step. to make a flashable zip. or somehow one click installer. i imagine if i did, it would only work for this phone, but could be modified for similar devices. i know tcl has a software like that. they plug a phone up and click one button. on their end it's one folder and that program does the rest. that program is what i want to write. reverse engineer this shiz and get a complete understanding of it. i know good and well the folks at tcl aren't sitting on a cmd window using adb to flash dozens of duplicate images time and time again for each device they build. it's screw it together, plug it up, click a button and test. they already have all the files preloaded and they have a preinstaller that pretty much instantly flashes the software. damn, wouldn't it sure be nice to have? but i don't foresee anybody leaking it any time soon. maybe if you have the cheese
Click to expand...
Click to collapse
Download TWRP for sprout
Download TWRP Open Recovery for sprout
dl.twrp.me

smuskat said:
Download TWRP for sprout
Download TWRP Open Recovery for sprout
dl.twrp.me
Click to expand...
Click to collapse
Did you see this? https://www.xda-developers.com/twrp-3-6-0-release-android-11-support/

R41N MuTT said:
Did you see this? https://www.xda-developers.com/twrp-3-6-0-release-android-11-support/
Click to expand...
Click to collapse
I looked; our REVVL does not seem to be listed in the list of supported devices.
smuskat said:
I looked; our REVVL does not seem to be listed in the list of supported devices.
Click to expand...
Click to collapse
And may I ask for a clarification, please: You wrote above, "the firmware links i sent you- there should be at least 2 different ones, and an OTA... well, if you open the root folder and type 'scatter.txt' in the search bar it will pop up." In your post, I see 2 links to firmware; one is called https://www.mediafire.com/download/sxq4cz8bddmr49l, and one is called https://www.mediafire.com/file/irigs9iviy3sobw/T-Mobile_REVVL_V%2B_5G.zip/file. I downloaded both. I clicked on the downloaded file, and in the search bar, I searched for "scatter.txt", and got no results. What am i doing wrong? Thanks

smuskat said:
I looked; our REVVL does not seem to be listed in the list of supported devices.
Click to expand...
Click to collapse
It needs to be ported still. Unless it's already ported I'm working on it now. Nightmare. I'm trying to follow a guide on here about porting TWRP... Going slow...
OTA
https://r4---sn-npoldn76.gvt1.com/packages/data/ota-api/package/72d80093722599cd459bca02504f22cbf3421dd2.zip?mh=Rs&pl=21&cm2rm=sn-8qj-i5ozd7r,sn-i3bdr7s&req_id=37ad1f0feba7fd94&cmsv=e&ipbypass=yes&rm=sn-8qj-i5olz7l&redirect_counter=3&cms_redirect=yes&mip=117.4.250.39&mm=34&mn=sn-npoldn76&ms=ltu&mt=1672034446&mv=m&mvi=4
Firmware
T-Mobile REVVL V+ 5G
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Here is the link to the scatter.txt for mt6833 (revvl v+).
MT6833_Android_scatter.txt
Shared with Dropbox
www.dropbox.com
Tmobile just recently announced the release of the a13 update. It's supposed to be before the end of february.
Software Updates
Visit T-Mobile Support for help with phones & internet devices, plans & services, billing, and more!
www.t-mobile.com
Message edited at completion of guide. Irrelevant content removed.

After installing the modified boot img with fastboot my phone bricked and i cant fix it, it just crashes on boot and loops back whenever i try to normal boot.
If there's any help you can offer I'd appreciate it.

vinnie215215 said:
After installing the modified boot img with fastboot my phone bricked and i cant fix it, it just crashes on boot and loops back whenever i try to normal boot.
If there's any help you can offer I'd
Click to expand...
Click to collapse
Edited: guide complete. Try it now.

R41N MuTT said:
When your phone boots up do you see system font on the screen? It should prompt you to press power to boot normally, otherwise it will continue to reboot. It's because the bootloader is unlocked and you must press power to acknowledge this or else the phone will boot loop. Does this help? If not, get another phone and download magisk and try to patch boot_a again. You can use another device to do all those steps to get the file ready. Pull it, plug in your revvl v+ again and try flashing it. You can also try a different copy of the firmware, I linked 3. You can also flash stock boot_a and boot_b and that should get you going. I'm still figuring this device out. I advise you reach out to somebody who has a lot of experience flashing a/b partition scheme devices, namely mediatek. Project oppo. My only other suggestion is to flash the stock firmware using adb fastboot commands. In the forums you can find a guide to flashing a/b... So, just to be clear, recite to me exactly what you did up to the point it boot loops. And tell me is there system type on the screen when it boots?
Click to expand...
Click to collapse
So i Followed the guide exactly and everything seemed to work fine until i flashed the img modified by magisk. Fastboot said it moved and wrote successfully.
Then when i rebooted and hit the power button again to bypass the 'orange' warning instead of starting into a factory reset phone, it flashes the backlight and starts booting again.
Im also unable to get into recovery, fastboot mode is all that works now. I've tried to flash the stock boot_a img but not the boot_b, do you think that would help?
I'm gonna make a new img with my s9 and try that as you suggested.
Edit:
Well i might be handicapped.
I had 2 phones here, the V+ and the 6 pro.
Turns out i did youre walkthrough on the revvl 6 pro. It did unlock it, but obviously when i flashed the boot.img for the V+ it bricked. And i cant find the backup anywhere.
In short thanks for your time, I'm afraid all i did was waste it :\

vinnie215215 said:
So i Followed the guide exactly and everything seemed to work fine until i flashed the img modified by magisk. Fastboot said it moved and wrote successfully.
Then when i rebooted and hit the power button again to bypass the 'orange' warning instead of starting into a factory reset phone, it flashes the backlight and starts booting again.
Im also unable to get into recovery, fastboot mode is all that works now. I've tried to flash the stock boot_a img but not the boot_b, do you think that would help?
I'm gonna make a new img with my s9 and try that as you suggested.
Edit:
Well i might be handicapped.
I had 2 phones here, the V+ and the 6 pro.
Turns out i did youre walkthrough on the revvl 6 pro. It did unlock it, but obviously when i flashed the boot.img for the V+ it bricked. And i cant find the backup anywhere.
In short thanks for your time, I'm afraid all i did was waste it :\
Click to expand...
Click to collapse
Edited to remove irrelevant content. Guide complete. Try it again. If your phone will not hard reboot, try adb reboot bootloader. All activity should cease and your device should promptly enter fastboot.

i started messing with this phone on my own until ididn't have right stock firm. is alot steps get this phone rooted.

contevo said:
i started messing with this phone on my own until ididn't have right stock firm. is alot steps get this phone rooted.
Click to expand...
Click to collapse
I couldn't agree more. Lol. I'm actively editing the content to condense it. I'm also working on porting TWRP. I've done some other things to save a few steps, like patching boot_a and putting it on Dropbox so all you'll have to do is download it and flash it. When a13 OTA gets captured it'll get better

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i get this error when loading the scatter file ad i'm using the latest version
v5.1924

R41N MuTT said:
I couldn't agree more. Lol. I'm actively editing the content to condense it. I'm also working on porting TWRP. I've done some other things to save a few steps, like patching boot_a and putting it on Dropbox so all you'll have to do is download it and flash it. When a13 OTA gets captured it'll get better
Click to expand...
Click to collapse
can you help

pickymarker said:
can you help
Click to expand...
Click to collapse
Currently working on it. I've asked a couple ppl for help. Either they'll post here, or I'll update you. Stand by

okay

can it be done today

comm-ents said:
I am able to unlock the bootloader, then my phone just hangs at the boot screen, but I can can lock it again Now it just boots with the orange warning and it doesn't matter after that if it is locked or unlocked
The android version is still 11 with a security update from Dec 5, 2022.
I am just curious if there is a way to revert back to a previous version that might just work like the version listed for download. There could also be differences in the boot file that is in the firmware zip file from what is on my phone so patching and installing a different version won't work.
Maybe just waiting until the next version is releases would be the best option?
Click to expand...
Click to collapse
Perhaps that. In fact, that's what I'm waiting on- the a13 update. I intend to capture the OTA and follow the spflash walkthrough. Then I can update this how to where it'll work for everybody. I have 4 people right now with boot issues after root that go beyond WiFi, and they all 4 can't get spflash to work. It's bugging the crap out of me, I haven't been able to figure out what to do to fix it. I'm still waiting on some other folks I've reached out to, if they ever have the time...

Develop Bugs

welcome