Hi all, my first post here.
I recently bought this phone thinking it was customizable. Every tutorial I have tried has failed and required a re-flash to stock ROM using MIFlash.
I have tried custom ROMs, GSI ROMs, 64 bit, 32 bit, etc. I tried using Magisk 21.0 to root, it appears to work, but I believe the boot.img patching isn't currently working on this particular phone.
Most tutorials I have tried are very simple and use TWRP to flash the OS img file, then reboot and enjoy. Some suggest flashing vbmeta.img to prevent boot loop, but, boot loop happens anyway. I have TWRP installed and working, so far, that is all I have had success with.
Can this phone still be customized at all?
Update: I achieved root on the stock ROM. If anyone is interested I'll post the exact instructions.
stvmnn said:
Hi all, my first post here.
I recently bought this phone thinking it was customizable. Every tutorial I have tried has failed and required a re-flash to stock ROM using MIFlash.
I have tried custom ROMs, GSI ROMs, 64 bit, 32 bit, etc. I tried using Magisk 21.0 to root, it appears to work, but I believe the boot.img patching isn't currently working on this particular phone.
Most tutorials I have tried are very simple and use TWRP to flash the OS img file, then reboot and enjoy. Some suggest flashing vbmeta.img to prevent boot loop, but, boot loop happens anyway. I have TWRP installed and working, so far, that is all I have had success with.
Can this phone still be customized at all?
Update: I achieved root on the stock ROM. If anyone is interested I'll post the exact instructions.
Click to expand...
Click to collapse
Hi.
I´m interested. I´m not able to root the MI 8A MIUI 11 global 11.0.2.0 QCPMIXM. I achieved install TWRP . But I can´t install MAGISK . It don´t show me any error, but it isn´t installed. I ´ve tried many versions 20.0, 20.1, 20.2, 20.3 20.4 21.0 and 21.1. neither of them are successfull with TWRP.
Neither with magisk manager apk 7.5.1 and above. These are installed but then I download magisk 20.4 version, but this isn´t installed.
how did you it? please.
Yajirobai said:
Hi.
I´m interested. I´m not able to root the MI 8A MIUI 11 global 11.0.2.0 QCPMIXM. I achieved install TWRP . But I can´t install MAGISK . It don´t show me any error, but it isn´t installed. I ´ve tried many versions 20.0, 20.1, 20.2, 20.3 20.4 21.0 and 21.1. neither of them are successfull with TWRP.
Neither with magisk manager apk 7.5.1 and above. These are installed but then I download magisk 20.4 version, but this isn´t installed.
how did you it? please.
Click to expand...
Click to collapse
Your bootloader needs to be unlocked and USB debugging enabled first of course. TWRP Recovery should be installed.
To do this, you need the adb and fastboot binaries installed on a PC/Laptop. I use Ubuntu and installing these is trivial via apt package manager:
Debian based:
Code:
sudo apt install adb fastboot
RedHat based:
Code:
yum install adb fastboot
If you use Windows, the install and use of these binaries is a little different. I don't use Windows so you'll have to do a quick search to find out how to install and use these binaries. The commands listed below will work no matter what OS you use.
Connect your phone to your PC/Laptop via it's USB cable and reboot it to TWRP Recovery:
Power off the phone, then power on while holding the volume up button until you see the TWRP logo. Log into TWRP to decrypt.
Next, you need to pull the current boot.img from your ROM to patch it for root access:
Code:
adb shell dd if=/dev/block/by-name/boot of=/sdcard/boot.img
There should be a boot.img on your phone's internal storage, copy it to your PC/Laptop. From TWRP, reboot your phone to fastboot.
Now, we'll use this most excellent, free resource to patch the boot.img file which will give root access:
https://patcher.yaalex.xyz/
Check the 'Include Magisk' checkbox on the website before submitting image.
Important: After you upload your boot.img file to the website, be patient. This could take 10 minutes or more to complete, just wait until you get a prompt to download the patched image. You will be provided a patched_boot.img file from the website once it is finished.
Finally, all you need to do is flash the patched_boot.img to your phone:
Code:
fastboot flash boot patched_boot.img
Boot your phone to the ROM:
Code:
fastboot reboot
Install Magisk Manager if you haven't already, and enable Magisk Hide in the settings. Magisk Manager should report root access is available and SafetyNet test should pass.
I typed all this up from memory so if you run into trouble or are confused by any step, let me know and I will gladly clarify/fix the steps.
I hope this helps others achieve root on this phone. Let me know how it goes and happy de-bloating!
Rollback instructions:
If your phone fails to boot don't panic. You can restore your original boot.img if needed to regain access. Reboot your phone to fastboot:
Boot phone while holding the down volume button until you see the fastboot logo.
Next, flash the original boot.img to the boot partition:
Code:
fastboot flash boot boot.img
Now just reboot to ROM and all should be restored:
Code:
fastboot reboot
stvmnn said:
Hi all, my first post here.
I recently bought this phone thinking it was customizable. Every tutorial I have tried has failed and required a re-flash to stock ROM using MIFlash.
I have tried custom ROMs, GSI ROMs, 64 bit, 32 bit, etc. I tried using Magisk 21.0 to root, it appears to work, but I believe the boot.img patching isn't currently working on this particular phone.
Most tutorials I have tried are very simple and use TWRP to flash the OS img file, then reboot and enjoy. Some suggest flashing vbmeta.img to prevent boot loop, but, boot loop happens anyway. I have TWRP installed and working, so far, that is all I have had success with.
Can this phone still be customized at all?
Update: I achieved root on the stock ROM. If anyone is interested I'll post the exact instructions.
Click to expand...
Click to collapse
Iirc redmi 8a is an ab device, and yes this device is as customisable as any other Qualcomm. What gsi image are you flashing?
Actually he is not way off ..... i am NOT able to find a Custom Non MIUI ROM with full VoLTE support. VoLTE fix for GSI's ( if at all it worked ! ) does not work for Havoc. twrp root is all good. I want a NON MIUI ROM that can regional variants ( Europe and Asia ) and supports VoLTE
Related
Hello,
i'm trying to root a Sharp B10 (SH-A01) with Magisk.
It would be nice if i could do this without unlocking because i want to keep the stock rom anyway.
First problem is that i can't find a custom recovery (TWRP, CWM) for this device from where i could install Magisk.
Then i found out that Magisk gives the possibility to root a device through the Magisk Manager App by patching the boot.img.
But the second problem is that i can't find the boot.img either. I spotted the boot partition on the device and tried to pull with adb but i would need an already rooted device to give the needed permissions.
Is there anything else I could do to get this thing rooted besides compiling my own TWRP for the device?
thanks a lot,
paul
Hello, i search the same.
paulquappe said:
Hello,
i'm trying to root a Sharp B10 (SH-A01) with Magisk.
It would be nice if i could do this without unlocking because i want to keep the stock rom anyway.
First problem is that i can't find a custom recovery (TWRP, CWM) for this device from where i could install Magisk.
Then i found out that Magisk gives the possibility to root a device through the Magisk Manager App by patching the boot.img.
But the second problem is that i can't find the boot.img either. I spotted the boot partition on the device and tried to pull with adb but i would need an already rooted device to give the needed permissions.
Is there anything else I could do to get this thing rooted besides compiling my own TWRP for the device?
thanks a lot,
paul
Click to expand...
Click to collapse
Neither Magisk nor TWRP is needed to root Android: Chainfire's SuperSu does the job. You flash its ZIP via stock recovery "adb sideload"
jwoegerbauer said:
Neither Magisk nor TWRP is needed to root Android: Chainfire's SuperSu does the job. You flash its ZIP via stock recovery "adb sideload"
Click to expand...
Click to collapse
Hi,
thanks for your answer.
I already managed to root this device. I got the boot.img with Wwr_MTK & SP flash tool (windows tools...), patched it with the magisk app and than flashed the patched boot.img
1. Unlock your bootloader enter in download mode Vol+ + Vol- + USB conected to pc (Keep in mind that by doing this you will lose your files, it is advisable to make a backup of your photos, music, etc.)
2. Once you start your cell phone install magisk manager, Choosing the boot.img file of your rom into the app (Tip: Only!!! If your model is SM-A015M Android 11 I leave you my own modified boot.img to flash:
File on MEGA
mega.nz
Otherwise, you can download the firmware (3.79 gb) and extract the boot.img from the firmware of your model SM-A015 M / F ... Android 10, Android 11... etc. And No need for pc
https://samfrew.com/model/SM-A015M/
3. The image will begin to flash
4. When it restarts you will have Root on the cell phone!
------------------------------------------------------------------------------------------------------------------------------------------------
Extra: If you need the custom recovery I give you the link with my TWRP which is installed through the Odin program on a PC (this step does not delete your files)
File on MEGA
mega.nz
Keep in mind that to install TWRP you must deactivate the DM-VERITY & FORCEENCRYPT DISABLER I leave it in a link:
Zackptg5 - Android
zackptg5.com
This is a module that can be installed via magisk, which is necessary to decrypt the system ... so once TWRP is installed, it is advisable to uninstall it via Magisk to avoid R / W errors
Was searching in preparation of my K30 arriving, and found an unofficial version of TWRP is now available.
https://www.google.com/amp/s/unofficialtwrp.com/unofficial-twrp-3-3-1-xiaomi-redmi-k30/amp/
Note: I've not tried it myself, as I don't have the phone yet.
It's a none working TWRP ripped from a dev who was working on it. don't even test it guys. Devs at .eu made one that actually works.
https://xiaomi.eu/community/threads/twrp.53906/page-8
ddaggebi said:
It's a none working TWRP ripped from a dev who was working on it. don't even test it guys. Devs at .eu made one that actually works.
https://xiaomi.eu/community/threads/twrp.53906/page-8
Click to expand...
Click to collapse
please give instalation guide also
ddaggebi said:
It's a none working TWRP ripped from a dev who was working on it. don't even test it guys. Devs at .eu made one that actually works.
https://xiaomi.eu/community/threads/twrp.53906/page-8
Click to expand...
Click to collapse
Thanks for the info @ddaggebi
I used the K30 TWRP from https://xiaomi.eu/community/threads/twrp.53906/page-8#post-528914 to fastboot boot to TWRP and dump stock boot, recovery and misc (using e.g. `dd=/dev/block/bootdevice/by-name/boot of=/tmp/boot.img`). Then I patched the boot.img with Magisk Manager Canary. :good:
Any idea why that TWRP recovery installer .bat overwrites the misc partition? Temp booting the .img directly with fastboot boot seemed to work fine without their patched misc, so I'm sticking with that for now.
Again, be sure to fastboot boot recovery and then dump your ROM's misc first if you plan on flashing the recovery using that batch script, since you might need to flash it back along with the ROM's recovery for OTAs to succeed.
I can understand rooting here but is twrp installed permanently here? I mean to flash any rom do we always need fastboot command to boot twrp or its staying always and working normally??
Hard_Rock83 said:
I can understand rooting here but is twrp installed permanently here? I mean to flash any rom do we always need fastboot command to boot twrp or its staying always and working normally??
Click to expand...
Click to collapse
Yes. But some features are limited for now.
btw I installed eu rom in case stock rom replaces TWRP to stock recovery.
osm0sis said:
I used the K30 TWRP from https://xiaomi.eu/community/threads/twrp.53906/page-8#post-528914 to fastboot boot to TWRP and dump stock boot, recovery and misc. Then I patched the boot.img with Magisk Manager Canary. :good:
Any idea why that TWRP recovery installer .bat overwrites the misc partition? Temp booting the .img directly with fastboot boot seemed to work fine without their patched misc, so I'm sticking with that for now.
Also here is the latest Magisk Canary (20308) patched stock boot.img to simplify rooting for those just getting started on this device. Simply fastboot flash boot it..
Click to expand...
Click to collapse
Ok so the question is can we reboot to recovery normally or we need to manually type fastboot command to boot to recovery..
I am still searching for twrp , which can normally appears while rebooting to recovery
LR.Team twrp-3.4.0-0209 will be installed by default when you install Eu rom.
I can reboot into recovery as normal (by pressing "vol up" & "power" button). To install root, I can simply go to "Advanced" -> "Install Root" or by using boot.img method. One thing which I can't do is deleting (or changing file name) to system file to remove some of the unwanted app.
It works very well
https://xiaomi.eu/community/threads/twrp.53906/page-8#post-528914
I had a boot loop trying to install a module.I am in build 11.0.11 without twrp.I used the command adb wait ... to remove modules via adb but the problem didn't solve.After that I reinstalled the stock rom and the phone reboots. But when I tried to reinstall magisk using the patched img via adb I had bootloop again so I reinstalled again the rom. What can I do to solve the problem?
You are probably flashing the wrong boot.img for the firmware you are on perhaps?
Make sure it is the patched.img from here you flash https://forum.xda-developers.com/mi-a3/how-to/guide-how-to-root-mi-a3-magisk-t3958509/post82207833
Credits: @Sapper Morton
Thanks for the answer, but it isn't the boot.img, the specific module (sony music!) was the problem..
At last I installed twrp using the q- base twrp.img and I disabled this module via twrp and the magisk manager for recovery....The phone booted normally with the others modules to work fine...
Good evening dear members, I ask for your kind advice, as I have done something wrong to my Oneplus 5t.
I upgraded my Oneplus 5t with "lineage for microG" 19.1 (from lineage 18).
I had installed TWRP 3.5.0_9 (phone encrypted).
It booted fine the first time into system.
The problem arose after I tried to install Magisk 21.4 from TWRP.
Now the phone only boots in recovery, but it doesn't enter TWRP's menu. It stays on the first TWRP screen (where it shows the version number).
The good thing (I hope) is that I can enter fastboot mode.
I tried flashing TWRP again from fastboot to no avail.
I tried flashing boot.img from fastboot (taken from the original firmware), but still no luck.
Is there a way to install the original firmware from fastboot?
I think starting from scratch would be a step into the right direction.
Please give any suggestion which I fill follow to the letter.
Thank you, thank you, thank you!
You have to be decrypted or flash DMverity for A12. I assume You mean Magisk 24.1 the current version is 24.3
Hi. This is what I did:
I downloaded and installed original firmware through fastboot (fastboot was still on).
I also installed original recovery through fastboot.
After that my oneplus 5t was in stock condition, apart from the bootloader, which was unlocked.
After that I managed to install TWRP through fastboot, and then lineage 19.
The thing is that TWRP doesn't support lineage 19, for one reason or another. Or it could be the other way around (lineage 19 doesn't support TWRP). In any case I had a phone which would only go in fastboot mode.
At least I knew what to do, as I did it already: reinstall stock firmware and recovery.
Long story short, I installed LOS recovery and lineage 19, and everything works fine.
Thanks everyone, and especially thaidroid, for the support.
Have a nice day.
miclombardo said:
Good evening dear members, I ask for your kind advice, as I have done something wrong to my Oneplus 5t.
I upgraded my Oneplus 5t with "lineage for microG" 19.1 (from lineage 18).
I had installed TWRP 3.5.0_9 (phone encrypted).
It booted fine the first time into system.
The problem arose after I tried to install Magisk 21.4 from TWRP.
Now the phone only boots in recovery, but it doesn't enter TWRP's menu. It stays on the first TWRP screen (where it shows the version number).
The good thing (I hope) is that I can enter fastboot mode.
I tried flashing TWRP again from fastboot to no avail.
I tried flashing boot.img from fastboot (taken from the original firmware), but still no luck.
Is there a way to install the original firmware from fastboot?
I think starting from scratch would be a step into the right direction.
Please give any suggestion which I fill follow to the letter.
Thank you, thank you, thank you!
Click to expand...
Click to collapse
Its not working cus you need to format data in recovery and then reboot it.
kirknado18 said:
Its not working cus you need to format data in recovery and then reboot it.
Click to expand...
Click to collapse
It wont boot cus your encrypted formatting data will allow op5t to boot.
latest lineage + magisk = stuck on boot logo, I tried an older version of lineage + magisk (known to work), same thing.. what did I do?
paradoxiumwind said:
latest lineage + magisk = stuck on boot logo, I tried an older version of lineage + magisk (known to work), same thing.. what did I do?
Click to expand...
Click to collapse
What recovery are you on? TWRP?
I use the one posted alongside each version: https://download.lineageos.org/dumpling
can you help?
I need to root so I can titanium backup everything. but I can't root. I suspect I might need to fully format and wipe and start again, I tried wiping data and doing a fresh install, but after sideloading magisk it just fails to boot every time now.
Does it boot regularly BEFORE installing magisk? I am trying to define the source of the problem.
I have installed lineage 19 and magisk, and I confirm you that it's possible
Yes. It boots fine if I just install lineage then nevermindthegapps. problem only occurs if I flash magisk. I tried installing the .apk and patching the .boot image manually in it and then fastboot flashing that, but same thing.
oh - one possible thing that it may be - is that I had a couple of modules loaded (I think a gcam fix mod and something similar) in magisk, and I read somewhere about people having them stuck 'installed' despite demoving all traces of magisk app. whether that is the problem I don't know.
This is very strange. That's what I did:
Sideload lineage recovery
Sideload lineage 19
Download magisk apk
Patched boot image from lineage 19.zip
Sideload the patched boot image
And that's it it all worked
May I suggest you to start all over again?
is wiping system data sufficient or do I need to format it? I'd rather not lose my appdata- but I can't rescue it without root / titanium backup :/
Try first without formatting, and see how it goes
I wiped system/cache, installed lineage-19.1-20220719-nightly-dumpling-signed.zip / mindthegapps, phone booted up fine - rebooted fine.
ok, good. Now download latest magisk app and patch the boot img.
do I click patch vbmeta in image?
Yes.
First extract the file called boot.img from lineage.zip you just installed.
Then in magisk select "patch vbmeta in image".
Magisk should produce a file named something like " magisk_pached-24300_f41h3.img".
That patched file should be sideloaded.
Installation is explained really well by topjohnwu
it wouldn't flash without selecting vbmeta, so tried with, flashed it, now i'm sitting looking at the boot logo.
hi guys i'm trying to unlock the bootloader and install a custom recovery and custom rom i've never done it if anyone can help me and all the necessary files thanks a lot
Well first downgrade to rui 2.0 and then using deep testing apk unlock the bootlorder and then flash custom recovery (ofox better) . Install your custom rom of your choice then ur good to go
Pranav060 said:
Bene, prima eseguire il downgrade a rui 2.0 e quindi utilizzare l'apk di deep testing per sbloccare il bootlorder e quindi eseguire il flashing del ripristino personalizzato (ofox migliore). Installa la tua rom personalizzata di tua scelta, quindi sei a posto
Click to expand...
Click to collapse
unfortunately I can't find the realme ui 2.0 downgrade file when I install what is written in the guides it tells me verification failed and I can't downgrade
andrea34334343 said:
unfortunately I can't find the realme ui 2.0 downgrade file when I install what is written in the guides it tells me verification failed and I can't downgrade
Click to expand...
Click to collapse
I have this version of realme ui 3
Hi, maybe my experience will be useful to you. I have Realme 7 pro with android 12 rmx2170_11_f.24. I was doing root to my device. What I was doing? First I downloaded deeptest rui3.apk. When I get confirmation from manufacturer I start deep test in app. Then I use ADB to send command for unlock bootloader. I completed this task. Then I downloaded and flash TWRP 3.6.2_12 (because it's can work with android 12. I tried 3.5.2_10 it's not worked). Also you need vbmeta file from rmx2170_11_f.24 to don't make your phone brick. First flash vbmeta then recovery. After recovery you need to install Magisk from TWRP to keep TWRP working after reboot. But, when I tryed install Magisk I was getting TWRP error 1: cannot write /system. How I fix it? I reboot device and install Magisk 25.2 via Android. Then you need patch boot.img from rmx2170_11_f.24 via Magisk and you get Magisk patched boot.img. Then you need flash TWRP again and reboot to recovery. In TWRP you need chose flash img button and flash Magisk patched boot.img to boot partition. Doing this you keep TWRP working and then you can flash custom ROM's to your phone.
Mod edit: 4pda link removed.
here you can get f24 ROM ( you need vbmeta and boot.img from this ROM). ROM is ~2 Gb size. Maybe you need registration on website to download. Also get TWRP 3.6.2. I'll pin deep test rui3.apk and Magisk 25.2 for you here. You can rename Magisk.zip to Magisk.apk and install via Android. I gaved you roadmap how to make this. Hope you can do it. By the way, hello from Ukraine)
s_svyrydenko said:
Hi, maybe my experience will be useful to you. I have Realme 7 pro with android 12 rmx2170_11_f.24. I was doing root to my device. What I was doing? First I downloaded deeptest rui3.apk. When I get confirmation from manufacturer I start deep test in app. Then I use ADB to send command for unlock bootloader. I completed this task. Then I downloaded and flash TWRP 3.6.2_12 (because it's can work with android 12. I tried 3.5.2_10 it's not worked). Also you need vbmeta file from rmx2170_11_f.24 to don't make your phone brick. First flash vbmeta then recovery. After recovery you need to install Magisk from TWRP to keep TWRP working after reboot. But, when I tryed install Magisk I was getting TWRP error 1: cannot write /system. How I fix it? I reboot device and install Magisk 25.2 via Android. Then you need patch boot.img from rmx2170_11_f.24 via Magisk and you get Magisk patched boot.img. Then you need flash TWRP again and reboot to recovery. In TWRP you need chose flash img button and flash Magisk patched boot.img to boot partition. Doing this you keep TWRP working and then you can flash custom ROM's to your phone.
Mod edit: 4pda link removed.
here you can get f24 ROM ( you need vbmeta and boot.img from this ROM). ROM is ~2 Gb size. Maybe you need registration on website to download. Also get TWRP 3.6.2. I'll pin deep test rui3.apk and Magisk 25.2 for you here. You can rename Magisk.zip to Magisk.apk and install via Android. I gaved you roadmap how to make this. Hope you can do it. By the way, hello from Ukraine)
View attachment 5867277 View attachment 5867279
Click to expand...
Click to collapse
Thanks for helping me out and passing me the necessary files
{Mod edit: Quoted post has been deleted. Oswald Boelcke, Senior Moderator}
You wrote in the wrong trend write in a new post
s_svyrydenko said:
Hi, maybe my experience will be useful to you. I have Realme 7 pro with android 12 rmx2170_11_f.24. I was doing root to my device. What I was doing? First I downloaded deeptest rui3.apk. When I get confirmation from manufacturer I start deep test in app. Then I use ADB to send command for unlock bootloader. I completed this task. Then I downloaded and flash TWRP 3.6.2_12 (because it's can work with android 12. I tried 3.5.2_10 it's not worked). Also you need vbmeta file from rmx2170_11_f.24 to don't make your phone brick. First flash vbmeta then recovery. After recovery you need to install Magisk from TWRP to keep TWRP working after reboot. But, when I tryed install Magisk I was getting TWRP error 1: cannot write /system. How I fix it? I reboot device and install Magisk 25.2 via Android. Then you need patch boot.img from rmx2170_11_f.24 via Magisk and you get Magisk patched boot.img. Then you need flash TWRP again and reboot to recovery. In TWRP you need chose flash img button and flash Magisk patched boot.img to boot partition. Doing this you keep TWRP working and then you can flash custom ROM's to your phone.
Mod edit: 4pda link removed.
here you can get f24 ROM ( you need vbmeta and boot.img from this ROM). ROM is ~2 Gb size. Maybe you need registration on website to download. Also get TWRP 3.6.2. I'll pin deep test rui3.apk and Magisk 25.2 for you here. You can rename Magisk.zip to Magisk.apk and install via Android. I gaved you roadmap how to make this. Hope you can do it. By the way, hello from Ukraine)
View attachment 5867277 View attachment 5867279
Click to expand...
Click to collapse
Please provide twrp link.
UNOFFICIAL TWRP RMX2170 TRIAL FOR ANDROID 12
give me
boot img .vbmeta and .persist img