I tried to install the distro, and followed the procedure but failed on the op7tpro.
I managed to root via magisk patched image, but yea, flashing the twrp leaves /system_root and /vendor unmountable. The decryption tool installs via twrp just fine, just doesnt recognize the magisk root, but i think it doesnt work, as after every reboot twrp show in the log a line in red saying "E: unable to decrypt stuff". After flashing the nethunter image for the op7 the op7tpro seem bricked and system startup wont work anymore, but a loader loophole.
So i dont know if i could just try another recovery bootloader or if the hole nethunter image wont work. Thanks for any help.
Decrypting OOS doesn't work.
adb push zip /cache and try flashing.
Otherwise if might simply not work for this device.
Related
Hello, i'm new here.
I wanna know if there is some way to root my Galaxy J6 with magisk.
Last time i've tried i bricked my phone, but fix it.
So i flashed twrp recovery and flashed something like RMM State Lock to keep it on the custom recovery, then i couldn't reset the phone. I had an error saying "Cannot mount /data?".
So after a while, i saw something to do like "Format Data", so, if i reinstall twrp, then do format data, am i still able to
boot Android without that reset error? And do magisk?
J600FN
("SORRY FOR BAD ENGLISH")
Same problem for me, Did you find a solution?
I can't root my galaxy J6
Help please.
Hello,
It is possible that TWRP can't load the /data partition due to DM-verity still enabled. You need to flash the zip file linked below to fix it.
Please download the Oreo (also works on Pie) DM-verity forced encryption disabler on here : https://qc3.androidfilehost.com/dl/...65586/J6+_oreo_forced_encryption_disabler.zip and restart your phone.
Hi all,
I have read about how to install Twrp, with method described for flashing roms, but i need twrp only for flashing mods eventually and nothing more, and i need to receive ota.
Which is the simpliest and secure way?
Boot.img method or fastboot slot a/b?
Hope i was clear enough and thanks all in advance.
In theory, you could:
- fastboot flash boot twrp.img (do NOT allow system modifications)
- fastboot continue or fastboot reboot (it is being mentioned that continue command is to be used on A3, though not sure why)
- do the magic in twrp
- fastboot flash boot stock_boot.img
- fastboot continue or fastboot reboot
- use the phone and install OTA when it arrives
However, I can't imagine what kind of mods do you want to install in TWRP. Any system modification will prevent OTA installation (even mounting system partition as R/W) and also can prevent booting up the phone (dm-verity). Most mods these days are systemless via Magisk. TWRP on Mi A3 is useful mainly for making (and possibly restoring) backups, installing custom ROMs and troubleshooting. For everything else you have Magisk.
_mysiak_ said:
In theory, you could:
- fastboot flash boot twrp.img (do NOT allow system modifications)
- fastboot continue or fastboot reboot (it is being mentioned that continue command is to be used on A3, though not sure why)
- do the magic in twrp
- fastboot flash boot stock_boot.img
- fastboot continue or fastboot reboot
- use the phone and install OTA when it arrives
However, I can't imagine what kind of mods do you want to install in TWRP. Any system modification will prevent OTA installation (even mounting system partition as R/W) and also can prevent booting up the phone (dm-verity). Most mods these days are systemless via Magisk. TWRP on Mi A3 is useful mainly for making (and possibly restoring) backups, installing custom ROMs and troubleshooting. For everything else you have Magisk.
Click to expand...
Click to collapse
Thanks for reply, really appreciated. Twrp grant you to mount system (for example with fonts) and then umount without issue with ota if you restore boot image, in theory.
Thanks again, maybe i use magisk but i use banks app and i don't want root
HTCDevil said:
Thanks for reply, really appreciated. Twrp grant you to mount system (for example with fonts) and then umount without issue with ota if you restore boot image, in theory.
Thanks again, maybe i use magisk but i use banks app and i don't want root
Click to expand...
Click to collapse
Nope, won't work. OTA update engine checks system partition metadata hash, if it doesn't match, it won't continue with the installation. Just mounting system partion as R/W will change its metadata. With banking apps you'll have more luck with Magisk than without for a simple reason, unlocked bootloader will fail the Safetynet test. Magisk can hide bootloader status, root and itself. Only a very few apps can detect Magisk (mostly with controversial "undocumented" methods).
Btw. fonts replacement is a perfect task for Magisk, there are already modules ready for this.
_mysiak_ said:
Nope, won't work. OTA update engine checks system partition metadata hash, if it doesn't match, it won't continue with the installation. Just mounting system partion as R/W will change its metadata. With banking apps you'll have more luck with Magisk than without for a simple reason, unlocked bootloader will fail the Safetynet test. Magisk can hide bootloader status, root and itself. Only a very few apps can detect Magisk (mostly with controversial "undocumented" methods).
Btw. fonts replacement is a perfect task for Magisk, there are already modules ready for this.
Click to expand...
Click to collapse
Thank you again, you are right, probably magisk is more secure than if you haven't it once bootloader is unlocked
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
Hello,
I installed TWRP and rooted my Phone with Magisk afterwards.
Now my phone always boots into TWRP instead of starting my Android.
I already removed Magisk and tried flashing the xiaomi.eu ROM but that doenst help.
I also tried formatting my /data partition but that fails with the Message "Unable to decrypt FBE". When i try to format data i get the error "unable to wipe '/data' -- unknown file system 'auto' unable to format to remove encryption.
I hope I haven't bricked my phone completely and someone can help me
raphi59 said:
Hello,
I installed TWRP and rooted my Phone with Magisk afterwards.
Now my phone always boots into TWRP instead of starting my Android.
I already removed Magisk and tried flashing the xiaomi.eu ROM but that doenst help.
I also tried formatting my /data partition but that fails with the Message "Unable to decrypt FBE". When i try to format data i get the error "unable to wipe '/data' -- unknown file system 'auto' unable to format to remove encryption.
I hope I haven't bricked my phone completely and someone can help me
Click to expand...
Click to collapse
Tray xiaomi MI Tool V2
[email protected] said:
Tray xiaomi MI Tool V2
Click to expand...
Click to collapse
The Program fails with exit code 1: Mismatching Image and Device, do you know how i can solve this?
Enter in fastboot mode
Select the phone is bricked
Got it working!
If anyone else has this Problem on his MI 10T, this is what i did:
1. Download the TWRP from here --> https://forum.xda-developers.com/t/...r-mi-10t-mi-10t-pro-redmi-k30s-ultra.4187427/
2. Boot TWRP from Fastboot --> fastboot boot <twrp.img>
3. Use OTG pendrive to install xiaomi.eu ROM (I used Version 12.0.7) - without any wipe.
4. After the installation completed successfully, wipe your cache, data and do a full wipe in stock recovery
5. Reboot your System (optionally install twrp) and happy with your working System :^)
I've followed all the guides to unlock the bootloader, install TWRP and then decrypt and install Magisk to root the device. However what I really want to do is install a custom system.img that I built from the AOSP source following the GSI instructions. When I use TWRP to write that to the system partition the reboot fails with something that looks like a vbmeta error. I have to use ODIN to flash the stock ROMs to get it back.
What am I missing? I can do the same thing on a Pixel and using fastboot it boots fine. I'm sure it has something to do with AVB. I've tried using TWRP to install the decrypt zip after installing the image but that doesnt help. Any help is appreciated.
hypermoose said:
I've followed all the guides to unlock the bootloader, install TWRP and then decrypt and install Magisk to root the device. However what I really want to do is install a custom system.img that I built from the AOSP source following the GSI instructions. When I use TWRP to write that to the system partition the reboot fails with something that looks like a vbmeta error. I have to use ODIN to flash the stock ROMs to get it back.
What am I missing? I can do the same thing on a Pixel and using fastboot it boots fine. I'm sure it has something to do with AVB. I've tried using TWRP to install the decrypt zip after installing the image but that doesnt help. Any help is appreciated.
Click to expand...
Click to collapse
I think this [ t.me/tabs6twrp ] might be the best we can do. I would love to be proven wrong.