Does Official TWRP contain a disable AVB file?
The official TWRP site has the twrp.img, where you boot from it with fastboot and a twrp.zip which installs TWRP on the phone.(not sure what the steps to install are: can someone please explain the steps?)
Does the zip file have something that disables encryption/Android Verified Boot?
If you understand it better under this name, does the zip have a dm-verity-disable-forceEncryption file?
If the zip doesn't have it, do i flash it manually?
I don't want do get this phone into a bootloop.
Thanks in advance!
Related
Hey guys,
seems Magisk 16.1 is now working on the S9 but in order to flash it without custom recovery I'd need the boot.img file? Anyone has it?
According to Magisk, this would be the process then:
Install Magisk Manager.
Press install.
Select "Patch Boot Image File".
Select the stock boot image you've previously saved on your device.
Wait.
Flash the patched boot image to your device. (ODIN)
Done.
Thanks!
Hi, I flashed TWRP to be able to install magisk on my friend's Honor 7x (BND-L21 C432) and now that magisk is flashed and configured I want to go back to the stock recovery. I've downloaded the update.zip with the Firmware Finder app, and I've extracted the recovery_ramdisk.img from the UPDATE.APP file.
But once flashed (with fastboot) I can't access it, it gives me ERROR MODE, like if the img was invalid.
Any help?
Thanks!
Did you download and flashed the correct build file? Which recovery you flashed?
shashank1320 said:
Did you download and flashed the correct build file? Which recovery you flashed?
Click to expand...
Click to collapse
I was using correct version, but I wasn't using HuaweiUpdateExtractor. After using it to get the img it worked well.
Thanks!
eXtremeDevil said:
Hi, I flashed TWRP to be able to install magisk on my friend's Honor 7x (BND-L21 C432) and now that magisk is flashed and configured I want to go back to the stock recovery. I've downloaded the update.zip with the Firmware Finder app, and I've extracted the recovery_ramdisk.img from the UPDATE.APP file.
But once flashed (with fastboot) I can't access it, it gives me ERROR MODE, like if the img was invalid.
Any help?
Thanks!
Click to expand...
Click to collapse
this install zip, should restore the recovery-from-boot.p file, the file that causes stock recovery to be replaced. I have not confirmed on this device but it is a generic solution that should work.
mrmazak said:
this install zip, should restore the recovery-from-boot.p file, the file that causes stock recovery to be replaced. I have not confirmed on this device but it is a generic solution that should work.
Click to expand...
Click to collapse
Thanks anyway, I was able to *correctly* extract the img file
What does that file exactly? Is there a backup of the recovery on the phone?? I assuming we're talking about normal recovery, not the second eRecovery thing, right?
eXtremeDevil said:
Thanks anyway, I was able to *correctly* extract the img file
What does that file exactly? Is there a backup of the recovery on the phone?? I assuming we're talking about normal recovery, not the second eRecovery thing, right?
Click to expand...
Click to collapse
Stock Android has a feature to make a recovery image from the boot.img. By checking the contents of the recovery partition and comparing a checksum. When the sum does not match, the file "recovery_from_boot.p" takes over and builds it's own recovery image.
When you install twrp and "swipe to allow system modification" that file gets renamed to end with ".bak"
This zip file verifies the recovery script is on the phone e, and if it is, it will remove the .bak extension . That makes the system .restore (make) stock recovery on the next boot up
Thanks for the info!
Hi forum readers,
I think about buying an A32 4G (SM-A325FZKGEUB). In two threads here it was mentioned that rooting was successful. But how about twrp? I found an article on unofficialtwrp.com with description and download of an unofficial twrp and vbmeta.img with another tool for also unencrypting the data partition.
1) With all previous phones I only used xda stuff. What do you think, is it safe to use unofficial twrp?
2) If that twrp fails, I think it is possible to get the original recovery back using Odin. Correct?
3) Is it safe to use the vbmeta.inf and tool to unencrypt the data? I don't need Knox and also not Safety Net. Would it be possible to revert to factory status using Odin?
4) Ist necessary to unlock the bootloader for only flashing the Magisk-patched boot image? How about encrypted data?
Many Greetings
Florian
To root you need bootloader unlocked, if it isn't your phone will fail to flash and it will boot on EDM. If twrp fails you can always flash a .tar as AP containing only recovery.img
@ZModder, thank you for your hint. I was already successfully unlocking and installing Magisk 23. Because of your hint I dared to flash TWRP from the above mentioned web site. It didn't boot. But I could successfully return to original recovery. So waiting for a real device specific TWRP.
fbalder18 said:
@ZModder, thank you for your hint. I was already successfully unlocking and installing Magisk 23. Because of your hint I dared to flash TWRP from the above mentioned web site. It didn't boot. But I could successfully return to original recovery. So waiting for a real device specific TWRP.
Click to expand...
Click to collapse
how did you install Magisk? could you tell?
kkintr0 said:
how did you install Magisk? could you tell?
Click to expand...
Click to collapse
1st: Download appropriate firmware for your region and version of Samsung.
2nd: Unlock your bootloader. This will wipe your data.
3rd. Download magisk manager from github.
4th. Open Magisk and check what Ramdisk says.
4th: Extract your downloader firmware. There should be AP.... File. Open it via 7zip. Inside there you should have boot.img.lz4. Extract that file. If Ramdisk Says NO. Do the same with recovery file.
5th: Zip your boot file to tar format and place it on your phone.
6th: Open Magisk. and Press first Install Button.
7th: Press Select and Patch File. Magisk should create a new file inside Downloads folder. Called magisk..patched...etc Insert that file inside your pc. Do the same with recovery file if needed.
8th. Get into Download mode. You can do this by first turning off your phone and pressing both volume keys as you insert your usb cable.
9th: Open Odin File. If you have recovery file uncheck autoreboot. Place your patched file inside AP section.
10th: Reboot your phone and wipe your data.
11th: Volia!
Hey guys, has someone ever installed Magisk v24 by using this Guide:
I have shortened it in the way that I think it's right, NOT TESTED YET
Can anyone with the knowledge about this "proof read it"?
############################################
Get a copy of the boot.img.
You should be able to extract the file you need from official firmware packages or your custom ROM zip.
Next, we need to know whether your device has a separate vbmeta partition.
If your official firmware package contains vbmeta.img, then yes, your device has a separate vbmeta partition
You can also check by connecting your device to a PC and run the command:
adb shell ls -l /dev/block/by-name
If you find vbmeta, vbmeta_a, or vbmeta_b, then yes, your device has a separate vbmeta partition
Otherwise, your device does not have a separate vbmeta partition.
Quick recap, at this point, you should have known and prepared:
Whether your device has boot ramdisk
Whether your device has a separate vbmeta partition
A boot.img or recovery.img based on (1)
Let’s continue to Patching Images.
Patching Images
Copy the boot image to your device
Press the Install button in the Magisk card
Choose “Select and Patch a File” in method, and select the boot image
Start the installation, and copy the patched image to your PC using ADB:
Code:
adb pull /sdcard/Download/magisk_patched_[random_strings].img
Flash the patched boot image to your device.
For most devices, reboot into fastboot mode and flash with command:
Flash the patched boot image to your device.
For most devices, reboot into fastboot mode and flash with command:
Code:
fastboot flash boot /path/to/magisk_patched.img
(Optional) If your device has a separate vbmeta partition, you can patch the vbmeta partition with command:
Code:
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
Reboot and voila!
UninstallationThe easiest way to uninstall Magisk is directly through the Magisk app. If you insist on using custom recoveries, rename the Magisk APK to uninstall.zip and flash it like any other ordinary flashable zip.
Best, dj
derjango said:
Hey ...
Click to expand...
Click to collapse
Why people look for troubles ?
That guide is for people who don't have custom recovery
it's a long process and some people will make mistakes
renaming to zip and flash in recovery is the easiest way
also with patching img way you will not have a magisk folder in data/adb and magisk will tell you that the install is not complete and probably will need couple of reboots to work ...
To be honest, my trouble is, that the Magisk App does not work properly and I'm searching the reason for that.
It says:
Magsik:
Installed: N/A
Zygisk: No
Ramdisk: No
In the bottomline Superuser is inactive as well as Modules.
How can I fix this?
I've installed Magisk.zip via TWRP, Root Checker tells me that Root is not installed properly
Best, dj
/edit
got it, I had to install it after booting into rom, not directly after flash ROM
derjango said:
In the bottomline Superuser is inactive as well as Modules.
/edit
got it, I had to install it after booting into rom, not directly after flash ROM
Click to expand...
Click to collapse
Hey brother, I've been searching high and low for this problem and got excited seeing your post.
Care to elaborate on how you managed to solve the inactive SU & Modules sections problem?
loopypalm said:
Why people look for troubles ?
That guide is for people who don't have custom recovery
it's a long process and some people will make mistakes
renaming to zip and flash in recovery is the easiest way
also with patching img way you will not have a magisk folder in data/adb and magisk will tell you that the install is not complete and probably will need couple of reboots to work ...
Click to expand...
Click to collapse
I tried doing that with lineage but it stopped internet working
Nebster7 said:
I tried doing that with lineage but it stopped internet working
Click to expand...
Click to collapse
i used .ZIP method on over than 200 rom (including lineage builds) and never had such problem
maybe in new magisk builds ? or miui based rom ?
Done it now using boot_a and boot_b method https://www.getdroidtips.com/how-to-root-poco-x4-pro-5g/
Nebster7 said:
Done it now using boot_a and boot_b method https://www.getdroidtips.com/how-to-root-poco-x4-pro-5g/
Click to expand...
Click to collapse
so you look on how to root "Poco X4 Pro 5G" on "redmi note 8" forums ?
hello all, i have an moto g8 xt2045-1 rav, with android 11 Is there no guide to root? magisk I have read that they lose touch ability. thanks
Not sure where you got that info, but I am writing this on a rooted XT2045-2 (i think the only difference to yours is color).
TL;DR: get the boot.img, patch it on the phone using the magisk app, and flash it on the device.
If you have unlocked the bootloader you can skip the following:
- Before you start reconsider if you really want to unlock the bootloader.
- Please note that unlocking the bootloader can and will cause you to lose the warranty on the device.
Here is a website that explains how to unlock the bootloader.
Once you have done that, you need the magisk zip file which you can find online.
From here I will assume that you know how to get into the bootloader.
I personally was unable to get TWRP on android 11, but in case you have it or any other custom recovery, and it works, you can try installing the zip.
If you cannot get a custom recovery, you will have to get the boot.img file for your device.
There are a few ways you could do that, those being finding the stock rom on lolinet and the official LMSA pc app.
I personally like the LMSA method more, as it automatically detects and downloads the correct stock rom.
What you are looking for is the boot.img file.
In case you get the zip from lolinet just extract it and skip the following steps.
In case you are using LMSA, get into the rescue and just download the file, you don't want to rescue the device.
Once you have gotten the zip, extract it and get the boot.img file.
On the device, boot into the system normally and install the magisk app like any other apk.
Transfer the boot.img file to the device, then open magisk and click on install magisk.
Select "choose and patch an image" and select the boot.im that you transfered earlier.
Once that is done you will see the path to the modified magisk-boot.img file (it will have a different name) which you have to get onto the pc.
Once you have the modified boot image and the bootloader is unlocked, go into the bootloader and flash the modified boot image on the device. (fastboot flash boot boot.img*)
*change boot.img to the actual file name
Feel free to ask questions, I tried to make it as detailed as possible.