Has anyone managed to root their device by patching their boot image and not installing a custom recovery (TWRP)?
I am referring to the method described on the Magisk website:
https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
mmedei9 said:
Has anyone managed to root their device by patching their boot image and not installing a custom recovery (TWRP)?
I am referring to the method described on the Magisk website:
https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
Click to expand...
Click to collapse
I think this would work with the xiaomi.eu rom. And I say it because when I install Magisk through TWRP, it works without the need to close AVB2.0 etc etc. Just install Magisk, reboot and you're good to go.
You need TWRP in order to flash the Xiaomi.eu rom though. Except if you flash all the partitions of the rom one by one through fastboot. And then flash the rooted boot.img.
Side note: I have not managed to root ANY rom (Chinese/global) on the Chinese device while keeping encryption. It always leads to bootloop, except if you disable forceencrypt, which of course leads to loss of encryption.
polfrank said:
Side note: I have not managed to root ANY rom (Chinese/global) on the Chinese device while keeping encryption. It always leads to bootloop, except if you disable forceencrypt, which of course leads to loss of encryption.
Click to expand...
Click to collapse
Do you suspect that the reason rooting via patching boot doesn't work is the encryption then? I'd be willing to disable encryption to obtain root with stock recovery
mmedei9 said:
Do you suspect that the reason rooting via patching boot doesn't work is the encryption then? I'd be willing to disable encryption to obtain root with stock recovery
Click to expand...
Click to collapse
Not exactly. I suspect that it is the reason for bootloop when trying to install Magisk on the Chinese device. Because Magisk does not work on the Chinese device, even if you flash and close avb2.0, you get bootloop.
In global device + global rom, you can disable avb2.0 through TWRP after flashing Magisk, and then reboot normally to get a perfectly rooted phone while keeping encryption.
But if you flash the rooted boot.img through fastboot, how are you going to close avb2.0?
polfrank said:
Not exactly. I suspect that it is the reason for bootloop when trying to install Magisk on the Chinese device. Because Magisk does not work on the Chinese device, even if you flash and close avb2.0, you get bootloop.
In global device + global rom, you can disable avb2.0 through TWRP after flashing Magisk, and then reboot normally to get a perfectly rooted phone while keeping encryption.
But if you flash the rooted boot.img through fastboot, how are you going to close avb2.0?
Click to expand...
Click to collapse
Of the handful of tutorials on the forums, which would you recommend for flashing TWRP and rooting the device?
Would it require me flashing the global rom in the place of my global (EEA) rom?
polfrank said:
I think this would work with the xiaomi.eu rom. And I say it because when I install Magisk through TWRP, it works without the need to close AVB2.0 etc etc. Just install Magisk, reboot and you're good to go.
You need TWRP in order to flash the Xiaomi.eu rom though. Except if you flash all the partitions of the rom one by one through fastboot. And then flash the rooted boot.img.
Side note: I have not managed to root ANY rom (Chinese/global) on the Chinese device while keeping encryption. It always leads to bootloop, except if you disable forceencrypt, which of course leads to loss of encryption.
Click to expand...
Click to collapse
Attention because there will be no more updates for the redmi note 8 pro concerning the rom xiaomi.eu! (announcement on their site ...)
I flashed patched boot image without disabling avb and now I'm stuck in bootloop.
Is it necessary to disable avb before flashing patched image through fastboot?
Introduction
This is a LineageOS Recovery compiled from the source tree of LineageOS 17.1 for Redmi Note 9S / 9 Pro.[/STRIKE] While the recovery has been usable for quite some time now, since it is not possible for TWRP to support any device launched with Android 10 for now.
I am aware that there is a TWRP port for this device, but since the source code is not accessible (as for as I can tell, maybe I just did not look hard enough for the source code), I can only advice against using it. The official TWRP open-sourced under GPLv3 does not even support devices launched with Android 10 yet, so there's clearly something going on here. I do not fix compatibility issues between my ROM and that TWRP port.
Instructions (Installing Recovery)
1. Download recovery-XXXX.zip (extract to get recovery.img and vbmeta.img)
2. Reboot to bootloader (`adb reboot bootloader`)
3. Run `fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img`
4. Run `fastboot flash recovery recovery.img`
5. Run `fastboot reboot recovery` to enter LineageOS Recovery
Instructions (Installing Magisk)
You have to use the official Magisk, version 20.4 or later. Installing an older Magisk will make the system unbootable.
1. Download Magisk >= 20.4, put onto computer
2. Reboot to LineageOS recovery, select `Mount /system` (you may see some errors, but they can be safely ignored)
3. Select `Apply update from ADB`
4. Run `adb sideload Magisk-xxx.zip`
5. You will see a signature verification error, select `Yes` to bypass the check
6. Reboot to system to enjoy your Magisk installation.
Caveats
1. Since it's not TWRP, you cannot decrypt your /data in recovery for now, which means no data backup or recovery, and you cannot install on-device flashable zips through this recovery.
2. Since it's not TWRP, it cannot prevent your OS from overwriting recovery automatically. If you use official ROM, you may need to manually re-flash the recovery every time. I'm not sure whether this can be bypassed with some Magisk module.
3. Don't expect to be able to flash anything into /system (e.g. OpenGAPPS or magisk) on stock ROMs
4. When trying to install OpenGAPPS on custom roms, it will get stuck at the end of the flashing process. This does not affect the functionality of the installed system and gapps, and a force-reboot into system will work just fine.
5. You need to always click "Mount /system" before flashing any mods into the system (i.e. Magisk, OpenGapps, etc., ROMs themselves are not affected), otherwise they will fail to install. (Clicking the option does not actually mount /system; it just sets up necessary mappings from the super partition to each of the dynamic partitions so that the installation scripts will work)
Downloads
LineageOS Recovery (with vbmeta included inzide the zip) (17.1, 2020-05-05): https://github.com/Xiaomi-Curtana/a.../recovery-2020-05-05/los-recovery-curtana.zip
Source Code
Device Tree: https://github.com/Xiaomi-Curtana/android_device_redmi_curtana
Kernel: https://github.com/Xiaomi-Curtana/android_kernel_redmi_sm7125
This is amazing !!! :laugh::laugh::laugh:
I'm very very grateful, but what's the advantage over stock recovery if we can't flash zips inside the phone memory? Or if we can't take a data backup?
Just asking trying not to be rude
cimdrap said:
I'm very very grateful, but what's the advantage over stock recovery if we can't flash zips inside the phone memory? Or if we can't take a data backup?
Just asking trying not to be rude
Click to expand...
Click to collapse
Stock recovery can't flash custom rom, gapps or magisk
cimdrap said:
I'm very very grateful, but what's the advantage over stock recovery if we can't flash zips inside the phone memory? Or if we can't take a data backup?
Just asking trying not to be rude
Click to expand...
Click to collapse
With LOS recovery you can adb sideload roms like EvolutionX
After reboot to recovery. It stuck at LOS recovery menu screen not response to Vol up/down button.
Then about 10 seconds phone reboot to normal stage.
When I reboot to recovery again it became stock recovery screen no LOS recovery.
ps000000 said:
After reboot to recovery. It stuck at LOS recovery menu screen not response to Vol up/down button.
Then about 10 seconds phone reboot to normal stage.
When I reboot to recovery again it became stock recovery screen no LOS recovery.
Click to expand...
Click to collapse
You sure you read all the steps? And didn't just flash straight away
A greatest thanks to dev and tester to make this work. Thank you for all your hard work to make this work. More great things is coming soon!
Is it work on Pro Max?
ahmetrasittopal said:
Is it work on Pro Max?
Click to expand...
Click to collapse
No
QuantumShqipe said:
You sure you read all the steps? And didn't just flash straight away
Click to expand...
Click to collapse
Success now (BAD USB CABLE Haha).:laugh:
Can I install this recovery and work as twrp? then installing the xiaomi.eu rom? Thank you
Yuluga said:
Can I install this recovery and work as twrp? then installing the xiaomi.eu rom? Thank you
Click to expand...
Click to collapse
No
TheMalachite said:
No
Click to expand...
Click to collapse
so what is this recovery? to install the lineage rom?
Yuluga said:
so what is this recovery? to install the lineage rom?
Click to expand...
Click to collapse
No, it's for flash custom rom + flash gapps and magisk on custom rom only
TheMalachite said:
No, it's for flash custom rom + flash gapps and magisk on custom rom only[/QUOTE
Your responds is confusing. Recent post ask if you can flash roms with this recovery and you said no. And then the person ask you so whats this recovery for, you said to flash roms and gapps ect.
Soo can we flash roms and gapps and zips YES or NO?
Thanks.
Click to expand...
Click to collapse
Gearswar said:
TheMalachite said:
No, it's for flash custom rom + flash gapps and magisk on custom rom only[/QUOTE
Your responds is confusing. Recent post ask if you can flash roms with this recovery and you said no. And then the person ask you so whats this recovery for, you said to flash roms and gapps ect.
Soo can we flash roms and gapps and zips YES or NO?
Thanks.
Click to expand...
Click to collapse
Is Xiaomi.eu is a custom ROM ? No that's a MIUI port with more customization and debloated
Click to expand...
Click to collapse
Lame question
Do we need to unlock bootloader?
Or does it come unlocked by default
RickyGoldsmith said:
Lame question
Do we need to unlock bootloader?
Or does it come unlocked by default
Click to expand...
Click to collapse
You unlock it via mi unlock tool... https://en.miui.com/unlock/
Takes 7 days
Hi,
i have a problem, my micro SD Card cant be mountet.
i have flasht LRTWRP now.
Have anyone a tip for me? What can i do ?
big thx
I'm flashing TWRP version from official TWRP website for poco F3. Successfully flash temporary and make it permanent using flash this TWRP version.
Boot up to stock miui (im not flashing custom rom yet), work fine. I want to flash magisk, but TWRP wong detect storage or the magisk zip. Anyone can help?
Official TWRP doesn't support Android 12's Encryption yet, that's why /data partition appears empty.
You need to use unofficial TWRP "skkk": https://dl.akr-developers.com/?dir=skkk/TWRP/A12
cyanGalaxy said:
Official TWRP doesn't support Android 12's Encryption yet, that's why /data partition appears empty.
You need to use unofficial TWRP "skkk": https://dl.akr-developers.com/?dir=skkk/TWRP/A12
Click to expand...
Click to collapse
Thank you. I will try this version.
Edit: It works. Thank you sir!!
I successfully unlocked my bootloader, then I tried flashing the twrp by following munchy's tutorial from YouTube (as someone recommended here). I also used the twrp recovery file he provided in the description, by using the latest platform tools from the official website. It was going pretty good. I even got the TeamWin logo, and also loaded up the twrp interface, and was able to navigate through it. But the problem was my internal storage wasn't showing up. So I booted back to my system normally to see If I can find a solution. Then I think I tried again after restarting to see if it fixes itself, but the same problem was persisting. The next time when I tried again, I used the latest twrp version which I downloaded from the official twrp website.
But since my 3rd attempt, I am not able to see any TeamWin recovery come up on my phone, when I connect I do the "fastboot boot (twrp filename)" command in cmd. When I do the command, nothing shows up. The device remains in the Fastboot mode, or just turns off. When I switch it back on, It turns on normally and boots into the phone without any issues, and I can use it. I've tried switching back to the original twrp version munchy used in the above linked video, but same result.
What did I do wrong here? How do I make my phone get into the twrp recovery when I enter the fastboot boot (twrp filename) command thru my PC? How do I make my Internal Storage available to view int he TWRP recovery so I can install it from my Downloads folder? I am on MIUI 14.0.4 If that helps. My end goal is to install Magisk.
Any tips/guides/suggestions are appreciated.
Installing TWRP and root does not erase your data.
Remove security from the lock screen. (decryption).Normally the latest TWRP decrypts the data.
Install Platform tools ,put the TWRP in the folder and run the commands from the folder.
TWRP SKK, Use A12 if your system is in A12/A13 if system A13.
Rename it to twrp.img
CMD
fastboot boot twrp.img
Powershell
./fastboot boot twrp.img
Once booted, go to Advanced -> Press "Flash current TWRP"
If offered, both slots.
NOSS8 said:
Installing TWRP and root does not erase your data.
Remove security from the lock screen. (decryption).Normally the latest TWRP decrypts the data.
Install Platform tools ,put the TWRP in the folder and run the commands from the folder.
TWRP SKK, Use A12 if your system is in A12/A13 if system A13.
Rename it to twrp.img
CMD
fastboot boot twrp.img
Powershell
./fastboot boot twrp.img
Once booted, go to Advanced -> Press "Flash current TWRP"
If offered, both slots.
Click to expand...
Click to collapse
Thank you. I had put backed the screen lock after the first 2 attempts because someone said to to that on a YT video after they faced the same problem. Now I tried again by removing the screen lock and the latest twrp for my device also boots up just fine. Now the problem Is I still can't access my internal storage .
Still having removed the screen security?
Which rom(fullname)?
Which TWRP?
Try to mount storage.
NOSS8 said:
Still having removed the screen security?
Which rom(fullname)?
Which TWRP?
Click to expand...
Click to collapse
Yes, I removed the screen security, though I can enter TWRP, I can't read the internal storage. MIUI 14.0.4.
I just watched a YT video where the dude does the following:
-TWRP Recovery
- Wipe
- Format Data
- Types 'yes'
then
-TWRP Recovery
- Reboot
- Recovery
- Do not Install
After coming back to recovery after rebooting, he gets a pop up, which at the swipe says "Swipe to allow for modifications" which he swipes, then now after checking the Internal Storage, It's readable now. Is this a possible solution?
Twrp A13, obviously if you don't want to keep the data.
Twrp/wipe format data type yes/reboot TWRP.
If error red lines, reboot TWRP and repeat the operation.
Sideload roms or use OTG.
NOSS8 said:
Twrp A13, obviously if you don't want to keep the data.
Twrp/wipe format data type yes/reboot TWRP.
If error red lines, reboot TWRP and repeat the operation.
Sideload roms or use OTG.
Click to expand...
Click to collapse
what's twrp A13? Also, I just unlocked my bootloader a few hours ago, so my phone has already done a factory reset and i don't have anything to lose except the Magisk APK and .img file in my phone.
But I have a question, will doing the format data just do a factory reset, or will I lose my ROM? Because I'm not trying to install a custom ROM, I just want to Install Magisk as the end goal with my current ROM.
MIUI 14 Android 13 so use this TWRP
plugged the phone into the PC when it is on the TWRP, you will have access to the internal storage. (works on my 12 pro aves twrp A13 Skk).
twrp-3.7.0_12-v7.5_A13-alioth-skkk.img
I'm using the latest one I could find on the TWRP website for my device. Not aware If it supports Android 13 though as it isn't mentioned on the website. Just asking my prev question, will doing the format data from TWRP just do a factory reset, or do I lose the ROM and will have to install a custom ROM?
second question I forgot to ask in my prev post, after i do the format data and put the Magisk APK and twrp img file again on my device, will my device stay decrypted as I formatted the data, or will the problem persist?
sorry If i sound dumb
zoinksy said:
I'm using the latest one I could find on the TWRP website for my device. Not aware If it supports Android 13 though as it isn't mentioned on the website. Just asking my prev question, will doing the format data from TWRP just do a factory reset, or do I lose the ROM and will have to install a custom ROM?
second question I forgot to ask in my prev post, after i do the format data and put the Magisk APK and twrp img file again on my device, will my device stay decrypted as I formatted the data, or will the problem persist?
sorry If i sound dumb
Click to expand...
Click to collapse
Use this TWRP(officiel).
twrp-3.7.0_12-v7.5_A13-alioth-skkk.img
thank you, this is the one I was looking for. Sorry to bother you again, now I installed the Magisk V26.1 apk from TWRP. And when I boot back to system and try opening the magisk manager, this happens. It says downloading, forever. I think I shouldn't have directly downloaded the latest version. So probably have to downgrade it a bit. For that, what will I have to do?
Can I just hold the Magisk icon, and uninstall it simply like any other app? Or do I have to do it from the TWRP? Also, Is it necessary for me to uninstall it before downgrading, or can I just download the apk of older magisk version and flash it from twrp just like I did previously?
It was on my first post.
Installation
The Magic Mask for Android
topjohnwu.github.io
TWRP + Root
Hi all. Hope you are good and safe from Covid-19. If you like TWRP as your recovery and want to keep root access as well, I am going to show you how to do that. Because if you take the stock boot.img and patch it via magisk, you will lose TWRP...
forum.xda-developers.com
Try OrangeFox. I never had problems with it. Been using it for half a year and constantly flash new ROM builds as a tester
Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40 (alioth) build releases | OrangeFox Recovery Downloads
Orangefox recovery for Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40 (alioth)
orangefox.download
cyanGalaxy said:
Try OrangeFox. I never had problems with it. Been using it for half a year and constantly flash new ROM builds as a tester
Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40 (alioth) build releases | OrangeFox Recovery Downloads
Orangefox recovery for Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40 (alioth)
orangefox.download
Click to expand...
Click to collapse
Sure, but currently only in A12.
NOSS8 said:
Sure, but currently only in A12.
Click to expand...
Click to collapse
I use ArrowOS 13
cyanGalaxy said:
I use ArrowOS 13
Click to expand...
Click to collapse
I don't doubt it, the Twrp A12 also works for certain operations on an A13 system but for certain Miui roms some bootloop.
NOSS8 said:
I don't doubt it, the Twrp A12 also works for certain operations on an A13 system but for certain Miui roms some bootloop.
Click to expand...
Click to collapse
Hm ok.
Welp for me on AOSP, it works nicely. I flash a new build (or two) every week. Backup/Restore works as should. UI is nice and modern, imo better than TWRP. That's why I'm recommending it.
Haven't heard anyone saying that they can't view Phone storage on OrangeFox.
Hi,
@NOSS8 , I'd like to ask : I've only some hours to wait to unlock the BL. But one question, as it's yet the stock rom (FW V13.0.11.0, A12), wich twrp should I use ? I want to install a A13 rom (that supposes FW V 14.xxx !)
So :
- fastboot boot twrp (but wich one ?? A12 or 13 ?? ; skkk ? Or ?) (+ "flash current twrp" OR "install it in ramdisk"?)
- reboot recovery
- flash FW V14.xxx
- flash rom
- format data
- reboot system
- flash magisk (last version ? Seems to be 'big' changes ?)
- flash what I need (V4A, DFE (??), ....)
What do you think ?
Thanks a lot ! Main question is about what version of twrp.. Help will be very appreciated !
néonaloj said:
Hi,
@NOSS8 , I'd like to ask : I've only some hours to wait to unlock the BL. But one question, as it's yet the stock rom (FW V13.0.11.0, A12), wich twrp should I use ? I want to install a A13 rom (that supposes FW V 14.xxx !)
So :
- fastboot boot twrp (but wich one ?? A12 or 13 ?? ; skkk ? Or ?) (+ "flash current twrp" OR "install it in ramdisk"?)
- reboot recovery
- flash FW V14.xxx
- flash rom
- format data
- reboot system
- flash magisk (last version ? Seems to be 'big' changes ?)
- flash what I need (V4A, DFE (??), ....)
What do you think ?
Thanks a lot ! Main question is about what version of twrp.. Help will be very appreciated !
Click to expand...
Click to collapse
Instead, use Miflash with a Fastboot rom, you can extract the boot img for root.(don't re lock the bootloader).
You can root without TWRP, but according to this thread, if you root you lose the TWRP and vice versa, I don't know if this is still relevant.(I don't have this device).
If you need ,install the TWRP A13 after flashing the A13.
See this thread for instructions
[Recovery] [13] [12] TWRP & OrangeFox
Since recoveries play a crucial role in flashing firmwares, custom ROMs and offline updates, it is of importance to have access to them. This post is about sources and instructions to working versions of recoveries for Alioth. Platform Tools (aka...
forum.xda-developers.com
***Note:
Use the TWRP SKKK.
Advantage with Miflash, the Fastboot roms contain all the imgs.
EDIT:
omitted link
TWRP + Root
Hi all. Hope you are good and safe from Covid-19. If you like TWRP as your recovery and want to keep root access as well, I am going to show you how to do that. Because if you take the stock boot.img and patch it via magisk, you will lose TWRP...
forum.xda-developers.com
NOSS8 said:
Instead, use Miflash with a Fastboot rom, you can extract the boot img for root.(don't re lock the bootloader).
You can root without TWRP, but according to this thread, if you root you lose the TWRP and vice versa, I don't know if this is still relevant.(I don't have this device).
If you need install the TWRP A13 after flashing the A13.
See this thread for instructions
[Recovery] [13] [12] TWRP & OrangeFox
Since recoveries play a crucial role in flashing firmwares, custom ROMs and offline updates, it is of importance to have access to them. This post is about sources and instructions to working versions of recoveries for Alioth. Platform Tools (aka...
forum.xda-developers.com
***Note:
Use the TWRP SKKK.
Advantage with Miflash, the Fastboot roms contain all the imgs.
Click to expand...
Click to collapse
I'm very greatfull for your quick reply ! Thanks
The device is too a Poco f3, sorry.. This doesn't need to flash magisk for twrp to stick (I had another one I've broken)
But I don't understand what's the advantage to first flash a fastboot rom..? As you say to flash twrp would loose root and vice versa... (I've read the thread you're talking about ofox)
So I wanted to go trough +- the way I mentionned, as A13 as well as ofox 'seems' to work (but I'm carefull with that twrp on stock MIUI A12, and I never used ofox..)
So you do think it's a bad idea ?? The rom I want to flash is crdroid.
I'm more lost now ...
Thanks again !