Bro can I root op9 running derkpest rom it is safe to root and if safe then how to root tell the possible best way guys?
Patched boot.img with magisk, PS when you find derkpest Rom for op9?
iaio72 said:
Patched boot.img with magisk, PS when you find derkpest Rom for op9?
Click to expand...
Click to collapse
Hoo bro from a12 patched img doesn't work I've saw posts so does it work or flashing magisk zip in recovery which is best way to avoid bootloop
Venkata Prathap said:
Hoo bro from a12 patched img doesn't work I've saw posts so does it work or flashing magisk zip in recovery which is best way to avoid bootloop
Click to expand...
Click to collapse
For OOS:
1) Have Magisk Manager v23016 or above installed
2) Download the boot.img from here and put in phone’s Download folder
3) Open Magisk Manager and click top Install and patch boot.img
4) Move patched image to PC’s adb directory
5) Boot phone into fastboot mode and run the command:
fastboot boot magisk_patched_boot.img
6) Phone will boot into temporary root. Click top Install again but choose Direct Install (recommended) this time
7) Reboot when done and profit
For COS:
1) Have Magisk Manager v23016 or above installed
2) Download rooting files and extract on PC
3) Copy boot.img and vendor_boot.img to phone’s Download folder
4) Open Magisk Manager and click top Install and patch boot.img. When done, go back and repeat the process for vendor_boot.img
5) Move both patched images to adb directory on your pc along with vbmeta.img
6) Run this command:
fastboot –-disable-verity —disable-verification flash vbmeta vbmeta.img
********************Make sure it completes without errors before proceeding. If errors, update your ADB: https://developer.android.com/studio/releases/platform–tools
7) If no errors, run these commands:
fastboot flash vendor_boot vendor_boot_magisk.img
fastboot flash boot boot_magisk.img
8) If no errors, run
fastboot reboot
incesu said:
For OOS:
1) Have Magisk Manager v23016 or above installed
2) Download the boot.img from here and put in phone’s Download folder
3) Open Magisk Manager and click top Install and patch boot.img
4) Move patched image to PC’s adb directory
5) Boot phone into fastboot mode and run the command:
fastboot boot magisk_patched_boot.img
6) Phone will boot into temporary root. Click top Install again but choose Direct Install (recommended) this time
7) Reboot when done and profit
For COS:
1) Have Magisk Manager v23016 or above installed
2) Download rooting files and extract on PC
3) Copy boot.img and vendor_boot.img to phone’s Download folder
4) Open Magisk Manager and click top Install and patch boot.img. When done, go back and repeat the process for vendor_boot.img
5) Move both patched images to adb directory on your pc along with vbmeta.img
6) Run this command:
fastboot –-disable-verity —disable-verification flash vbmeta vbmeta.img
********************Make sure it completes without errors before proceeding. If errors, update your ADB: https://developer.android.com/studio/releases/platform–tools
7) If no errors, run these commands:
fastboot flash vendor_boot vendor_boot_magisk.img
fastboot flash boot boot_magisk.img
8) If no errors, run
fastboot reboot
Click to expand...
Click to collapse
for COS: you still only need boot.img and magisk. install magisk patch boot.img temporarily boot on magisk-patchedboot.img and direct install in magisk manager
Related
Systemless Root Magisk Beta 15.2 ( Thanks @topjohnwu for Magisk)
As it is systemless so it doesn’t change system file. It only changes in Boot image.
Whenever you got OTA just Reflash Stock Boot img and update your device to latest version.
This Boot.img is taken from latest version of XUI 3.0 Nougat version Build No. X603-H575A-N-IN-171227V175. So When it will update need to Patch again boot.img with updated version or this can also be used.
Warning:-
I am not responsible for bricked devices.
Your warranty will void now. Do it at your own Risk.
Follow Step as Mentioned Below:
1. Unlock Boot loader as mentioned on following link:
https://forum.xda-developers.com/android/development/unlock-bootloader-infinix-zero-5-t3715360
2. If you want to install TWRP recovery then follow:
https://forum.xda-developers.com/android/development/infinix-zero-5-x-603-twrp-recovery-t3712491
Now the step for Systemless root with unlocked bootloader and usb debugging on is must. (with stock recovery no need TWRP)
1. Download the Zip file on following link: https://drive.google.com/open?id=1vne0IdPrW1isGoCJbYTCl4GRG5mh6QF5
2. Extract zip file in a folder.
3. Press and ctrl+Shift and right click on mouse.
4. Now press option open cmd window here, in window 10 it may be open powershall window here just select it.
5. In cmd window follow the following command.
A. adb reboot bootloader (phone will reboot and light blank dark screen)
B. fastboot devices (it will show your device if connected well)
C. fastboot flash boot patched_boot.img (it will flash new boot img in your phone.
D. fastboot reboot (will reboot your phone)
E. Install magisk manager app from XDA lab or from attached here in zip just extract it.
Your phone is rooted now with stock recovery.
OTA Update Support: Just follow above cmd again and at point C. just change flash cmd to stock boot. (fastboot flash Stock boot.img) then reboot and update your system OTA.
Thanks.
Last Updated on 05/01/2018
I can't install any module
/data/adb/xxx.img mount failed
Failed
Installation failed
While I was trying to install GApps for Lineage OS 18.1 on my Nokia 7.2, I always lost my wi-fi. This is apparently due to flashing TWRP as boot image, which replaces the stock boot messing with wi-fi as the boot image has thee kernel.
Although, I did figure it out, it took me three days to get a proper solution from multiple sources. Here, I will explain how to install Lineage OS 18.1 on Nokia 7.2 with Gapps and Magisk. This can be applied to other ROMs as well. I am assuming you are on stock firmware.
Requirements:
Any custom ROM without GApps
vbmeta file
vendor image
Gapps zip file of your choice
platform-tools
twrp image
magisk file
payload dumper tool
Preperation:
The wifi stops working because we change the boot image. To prevent this, we must flash the boot image of the rom after we are done with our work with TWRP
For this, we ,ust get the boot image for the ROM. As this is not available readily, we must extract it from the ROM zip
Install latest python on your pc
Get the payload dumper tool from the link given below. Extract the contents into the root directory of python. It should be in C:\Users\USER-NAME\AppData\Local\Programs\Python\Python <version number>
Extract the ROM zip into any folder. Copy the payload.bin file and paste it in the folder where you put the payload dumper tool
Open a command prompt in the python root folder and type
Code:
python -m pip install -r requirements.txt
Then type
Code:
python payload_dumper.py payload.bin
After it finishes, go to the folder named Output inside the python folder. Here there will be a file named boot.bin. Rename this as lineage_boot.bin and paste it into the platform tools folder
Installation:
Download the twrp image, rename it to twrp.img and place it in the platform-tools folder. Connect your phone to the computer, switch on usb debugging on your phone.
Open command shell in the platform-tools folder and type
Code:
adb reboot bootloader
. In the bootloader, type
Code:
fastboot flash boot_b twrp.img
.
Next, type
Code:
fastboot --set-active=b
and then reboot to recovery using volume buttons and selecting using power button
In TWRP swipe to allow modifications. Copy your ROM and vendor image files to your SD Card. Now, click wipe, format data and type yes. Go back to home screen and the press install. Select your ROM file and install it. Sometimes it is required to flash vendor image. In that case flash that too. This step is required for Lineage OS 18.1
Now on the twrp home screen, tap on reboot. At the bottom, the current slot should be B. Tap slot A. THis changes the active slot to A. Now go back and tap on bootloader, this should boot you to the bootloader.
Take your vbmeta.img file and place it in the platform tools folder. Now, while in the bootloader mode, type,
Code:
fastboot flash vbmeta_a --disable-verity --disable-verification vbmeta.img
Next type
Code:
fastboot flash boot_a twrp.img
and boot to recovery using volume buttons
Now, press install in TWRP and select install and install the GApps file and reboot to bootloader
Next, in the bootloader type
Code:
fastboot flash boot_a lineage_boot.img
. Now start your phone. You should have lineage os with GApps
Installing Magisk:
Copy the lineage_boot.img into your phone. Download magisk.apk file from the link given below
Install the magisk app and open it. If it asks for additional setup select no. Beside the magisk option select install. Under options, if Recovery Mode is selected, deselect it and click next.
Now click on Select and patch a file under method. Select the lineage_boot.img
The patched image will be saved in downloads folder. Rename this file to lineage_magisk.img and copy it to the platform tools folder on your computer. Reboot your phone to bootloader mode
On your computer in the command window opened in the platform tools folder, type,
Code:
fastboot flash boot lineage_magisk.img
Reboot and you will have a rooted lineage os with GApps
Files:
Lineage OS 18.1 and vbmeta.img
TWRP
vendor
NikGApps
Payload Dumper tool
platform tools
Magisk
Guides that I Followed:
Extracting boot.img from ROM zip
Installing magisk using patched boot image
Credits:
Raghu varma for Lineage OS 18.1 port and twrp
Providers of the guides mentioned above
Hi @Ujwal2000 thanks for the guide.
I am using the stock android 10 rom and magisk patch method.
This also leads to non working wifi and magisk does not recognize that its installed.
Which steps of your guide apply to the stock rom?
i do not need gapps nor twrp I guess I only wanted to root the stock rom with magisk.
For stock, use this guide. They maintain a repository if patched boot images
Guide - How to root the Nokia 7.2 and Nokia 6.2 using Magisk
Nokia 7.2 and Nokia 6.2 come with an unlockable bootloader. The thing that compliments unlocked bootloader best is root access. So, this guide will help you in rooting the Nokia 7.2 or Nokia 6.2. You have a choice between Magisk patched boot images and TWRP recovery. I’d recommend going the...
www.techmesto.com
@Ujwal2000 , can you please look at my posting here? Thank you.
after fallowing the steps(except installing lineageOS with twrp flash everything was encrypted even tough i have the bootloader unlocked, managed to install it via adb sideload) the wifi doesnt work at all. When i try to turn it on is switches off on its own. Do anyone know a fix?
i had problem with latest version of python (3.10), version 3.7 was working for me
after the latest apdate 13.0.3 i lose my magisk
and when i want to install it using adb it gives me a boot loop and i shoold to flash the original boot.img
Nb : ramdisk yes
Uninstall it thn flash it using Twrp
twrp can't read internal storage
but when i use the memory card then i click install the recovery restart directly
also by using adb the installation fail in 3%
souhail39 said:
twrp can't read internal storage
but when i use the memory card then i click install the recovery restart directly
also by using adb the installation fail in 3%
Click to expand...
Click to collapse
First flash the original boot image into your phone and make sure your phone can boot after you flash the original boot image.
fastboot flash Magisk-patched-boot.img
Patched boot image can be made on another phone.
https://forum.xda-developers.com/t/4288121/post-85137963
pl1992aw said:
First flash the original boot image into your phone and make sure your phone can boot after you flash the original boot image.
fastboot flash Magisk-patched-boot.img
Patched boot image can be made on another phone.
https://forum.xda-developers.com/t/4288121/post-85137963
Click to expand...
Click to collapse
This is what i did
The original boot run finely but the patched one give me a boot loop
Miui 13 doesn't support yet unless you patch the boot img. Just revert to 12.5.9
souhail39 said:
This is what i did
The original boot run finely but the patched one give me a boot loop
Click to expand...
Click to collapse
The safe way is to not flash boot image with TWRP or Orangefox custom recoveries. Flash with fastboot mode with PC is better to prevent issue.
What version of Magisk?
If you are using the latest Magisk v24.X but it bootloop, you may report issue to Magisk author in his github.
If you used Magisk v23, it is said not working on Android 12, so will not work on MIUI 13.
1. Download stock MIUI rom.
2. Extract two files: boot.img and vbmeta.img.
3. Compress the two files to a TAR file, like: boot_and_vbmeta.tar
4. Copy the TAR file to the device.
5. Open magisk app.
6. Choose "Install magisk to file" and select the TAR file. It will create the file magisk_patched.tar
7. Copy the magisk_patched.tar file to the PC.
8. Extract magisk_patched.tar to get boot_patched.img and vbmeta_patched.img
9. Enter in fastboot in device.
10. Flash boot_patched.img and vbmeta_patched.img to the device:
Code:
fastboot flash boot boot_patched.img
fastboot flash vbmeta vbmeta_patched.img
VD171 said:
1. Download stock MIUI rom.
2. Extract two files: boot.img and vbmeta.img.
3. Compress the two files to a TAR file, like: boot_and_vbmeta.tar
4. Copy the TAR file to the device.
5. Open magisk app.
6. Choose "Install magisk to file" and select the TAR file. It will create the file magisk_patched.tar
7. Copy the magisk_patched.tar file to the PC.
8. Extract magisk_patched.tar to get boot_patched.img and vbmeta_patched.img
9. Enter in fastboot in device.
10. Flash boot_patched.img and vbmeta_patched.img to the device:
Code:
fastboot flash boot boot_patched.img
fastboot flash vbmeta vbmeta_patched.img
Click to expand...
Click to collapse
thx for your answer but always the same problem with patched img files
i've unlocked the bootloader of my phone, and it boots fine with stock recovery & oneui core 3.1, but whenever i install twrp or a gsi, my phone ceases to boot. any ideas?
tekkitheidiot said:
i've unlocked the bootloader of my phone, and it boots fine with stock recovery & oneui core 3.1, but whenever i install twrp or a gsi, my phone ceases to boot. any ideas?
Click to expand...
Click to collapse
Do u install TWRP through Odin?
C-Andy said:
Do u install TWRP through Odin?
Click to expand...
Click to collapse
The twrp must be built for a125w.
If you want I can modify the one you're trying but you need to send me your a125w stock recovery.img.lz4
physwizz said:
The twrp must be built for a125w.
If you want I can modify the one you're trying but you need to send me your a125w stock recovery.img.lz4
Click to expand...
Click to collapse
hello, ive been looking for a twrp that is compatible with sm-a125w because that is my model. how would i send you the stock recovery for this?
imdrew1234 said:
hello, ive been looking for a twrp that is compatible with sm-a125w because that is my model. how would i send you the stock recovery for this?
Click to expand...
Click to collapse
Just post it.
Attach files
physwizz said:
Just post it.
Attach files
Click to expand...
Click to collapse
here is the file. i included boot and vbmeta as well.
the link: https://drive.google.com/drive/folders/1L5491qUjTXUHKxXdLLlSOLBmwFY1rou-?usp=sharing
imdrew1234 said:
here is the file. i included boot and vbmeta as well.
the link: https://drive.google.com/drive/folders/1L5491qUjTXUHKxXdLLlSOLBmwFY1rou-?usp=sharing
Click to expand...
Click to collapse
Unzip to find the tar file.
Installing instructions in next post
Installing Custom Recoveries
A. Preparation.
1. Download firmware for your device
2. Extract ap file using Zarchiver and extract recovery.img from recovery.img.lz4 and compress it to recovery.tar
3. Patch the ap file with a magisk which will patch both boot.img and vbmeta.img (from magisk, choose install then select file to patch)
Exynos 850 Resources
t.me
Alternatively you can extract boot.img.lz4 and vbmeta.img.lz4 from the ap file and compress them into a new tar file and then patch that file.
note: if you don't want root then just extract the vbmeta.img and use zarchiver to add it to my twrp.tar file.
You can flash this new file from odin at step 5
For Exynos 850 android 11 use a21s patched magisk.
For Exynos 850 android 12 and most other devices use delta magisk
4. Unlock OEM in developer options
5. Attach phone to pc and reboot to download mode
6. flash patched ap file.
Or..
Extract boot.img and vbmeta.img and add them to the TWRP zip.
7. Download recovery.img or download twrp.tar and extract recovery.img using Zarchiver.
B.Installation
Method 1.
1. Connect to pc and boot into stock recovery
2. Factory reset
3. Reboot into download mode.
4. flash twrp.tar into the ap slot
5. reboot to recovery
6. Advanced, terminal. Type multidisabler (twice).
7.
Or flash samsung multidisabler zip
Or, for older phones flash dmverity zip
8. Reboot to recovery from main menu (not just reboot)
Backup boot, data, super and dtbo
9. Reboot to system
Method 2.
If you have already installed recovery and decrypted.
Extract recovery.img
1. Boot to recovery.
2. Install recovery.img
3. Choose recovery partition
4. Reboot to system then reboot to recovery
Backup boot, data, super and dtbo
(For Pitch-black just install the zip)
Method 3.
1. Install TWRP app
Extract recovery.img
2. Install TWRP
3. Choose file to flash.(don't select device)
4. Select recovery.img.
5. Reboot to recovery.
6. (You may need to change data partition to ext4 first if format ruins your system)
7. Reboot to recovery.
8. Wipe, format data, type YES.
9. Advanced, terminal.
10.Type multidisabler (twice).
Or flash samsung multidisabler zip
Or, for older phones flash dmverity zip
11.Reboot to recovery
12. Flash Magisk for root(only for method 3)
13. Backup boot, data, super and dtbo
Method 4
Using a second phone
Physwizz Collection
To flash TWRP from phone1 to phone2 Only if you have already installed recovery and decrypted. 1. Install this termux on phone1 2. Setup storage termux-setup-storage 3. Install this Heimdall Magisk module on phone1 Or install chroot Linux on termux and then install heimdall 4. Copy...
t.me
C. Recovery Problems
Most recovery issues can be solved by attending to the following issues.
1. Did you root using the full ap file patched Magisk .
(This contains the patched boot.img and vbmeta.img)
Exynos 850 users must use the special a217 magisk?
2. Did you then go all the way through the setup process?
3. Did you download the recovery to match your baseband?
See https://t.me/a127f_res/54 for Exynos 850 recoveries
4. Did you hold down power and volume up after Odin says pass?
5. Did you format data from stock recovery?
If you forgot to do this, just install stock recovery.img from TWRP and reboot.
6. Did you type multidisabler twice?
7. Did you reboot to recovery by choosing reboot from the menu and then choosing recovery?
8. To avoid touch issues go to settings and untick "allow time out"
D.To restore Stock Recovery
1. Attach phone to pc and reboot to download mode
2. flash patched ap file or stock recovery.tar
3. reboot
Or just flash stock recovery.img from twrp and reboot.
@physwizz
thank you so much ive been looking for this forever!
physwizz said:
Installing Custom Recoveries
A. Preparation.
1. Download firmware for your device
2. Extract ap file using Zarchiver and extract recovery.img from recovery.img.lz4 and compress it to recovery.tar
3. Patch the ap file with a magisk which will patch both boot.img and vbmeta.img (from magisk, choose install then select file to patch)
Exynos 850 Resources
t.me
Alternatively you can extract boot.img.lz4 and vbmeta.img.lz4 from the ap file and compress them into a new tar file and then patch that file.
note: if you don't want root then just extract the vbmeta.img and use zarchiver to add it to my twrp.tar file.
You can flash this new file from odin at step 5
For Exynos 850 android 11 use a21s patched magisk.
For Exynos 850 android 12 and most other devices use delta magisk
4. Unlock OEM in developer options
5. Attach phone to pc and reboot to download mode
6. flash patched ap file.
Or..
Extract boot.img and vbmeta.img and add them to the TWRP zip.
7. Download recovery.img or download twrp.tar and extract recovery.img using Zarchiver.
B.Installation
Method 1.
1. Connect to pc and boot into stock recovery
2. Factory reset
3. Reboot into download mode.
4. flash twrp.tar into the ap slot
5. reboot to recovery
6. Advanced, terminal. Type multidisabler (twice).
7.
Or flash samsung multidisabler zip
Or, for older phones flash dmverity zip
8. Reboot to recovery from main menu (not just reboot)
Backup boot, data, super and dtbo
9. Reboot to system
Method 2.
If you have already installed recovery and decrypted.
Extract recovery.img
1. Boot to recovery.
2. Install recovery.img
3. Choose recovery partition
4. Reboot to system then reboot to recovery
Backup boot, data, super and dtbo
(For Pitch-black just install the zip)
Method 3.
1. Install TWRP app
Extract recovery.img
2. Install TWRP
3. Choose file to flash.(don't select device)
4. Select recovery.img.
5. Reboot to recovery.
6. (You may need to change data partition to ext4 first if format ruins your system)
7. Reboot to recovery.
8. Wipe, format data, type YES.
9. Advanced, terminal.
10.Type multidisabler (twice).
Or flash samsung multidisabler zip
Or, for older phones flash dmverity zip
11.Reboot to recovery
12. Flash Magisk for root(only for method 3)
13. Backup boot, data, super and dtbo
Method 4
Using a second phone
Physwizz Collection
To flash TWRP from phone1 to phone2 Only if you have already installed recovery and decrypted. 1. Install this termux on phone1 2. Setup storage termux-setup-storage 3. Install this Heimdall Magisk module on phone1 Or install chroot Linux on termux and then install heimdall 4. Copy...
t.me
C. Recovery Problems
Most recovery issues can be solved by attending to the following issues.
1. Did you root using the full ap file patched Magisk .
(This contains the patched boot.img and vbmeta.img)
Exynos 850 users must use the special a217 magisk?
2. Did you then go all the way through the setup process?
3. Did you download the recovery to match your baseband?
See https://t.me/a127f_res/54 for Exynos 850 recoveries
4. Did you hold down power and volume up after Odin says pass?
5. Did you format data from stock recovery?
If you forgot to do this, just install stock recovery.img from TWRP and reboot.
6. Did you type multidisabler twice?
7. Did you reboot to recovery by choosing reboot from the menu and then choosing recovery?
8. To avoid touch issues go to settings and untick "allow time out"
D.To restore Stock Recovery
1. Attach phone to pc and reboot to download mode
2. flash patched ap file or stock recovery.tar
3. reboot
Or just flash stock recovery.img from twrp and reboot.
@physwizz
Click to expand...
Click to collapse
i was also wondering if you knew why i cant make modifications to /system partition. whenever i check it in mount on the main screen of twrp /system still doesn't show. I wanted to get the pixel experience rom but i cannot due to this issue im facing since the system partition does not show as a partition i can flash the custom rom to as a gsi.
imdrew1234 said:
i was also wondering if you knew why i cant make modifications to /system partition. whenever i check it in mount on the main screen of twrp /system still doesn't show. I wanted to get the pixel experience rom but i cannot due to this issue im facing since the system partition does not show as a partition i can flash the custom rom to as a gsi.
Click to expand...
Click to collapse
Do you see system.img as a partition?
physwizz said:
Do you see system.img as a partition?
Click to expand...
Click to collapse
i do. only data and system image. data doesn’t show as flashable and system image is already full plus not enough storage for the custom rom. i think that there is supposed to be a prompt from twrp when you load into it to allow modifications to the system partition but this prompt does not show on this twrp which is weird. i cannot find a solution to this issue.
i
imdrew1234 said:
i do. only data and system image. data doesn’t show as flashable and system image is already full plus not enough storage for the custom rom. i think that there is supposed to be a prompt from twrp when you load into it to allow modifications to the system partition but this prompt does not show on this twrp which is weird. i cannot find a solution to this issue.
Click to expand...
Click to collapse
If you want to install a gsi to system.img you can.
You may need to go to advanced terminal and type wipe system Or wipe SYSTEM_ROOT
physwizz said:
If you want to install a gsi to system.img you can.
You may need to go to advanced terminal and type wipe system Or wipe SYSTEM_ROOT
Click to expand...
Click to collapse
but what do i do if the system image is only 3.1gb and the rom is 3.48 gb? is there any way i can repartition it or something?
imdrew1234 said:
but what do i do if the system image is only 3.1gb and the rom is 3.48 gb? is there any way i can repartition it or something?
Click to expand...
Click to collapse
Choose a smaller gsi
physwizz said:
Choose a smaller gsi
Click to expand...
Click to collapse
i can’t seem to find any other custom roms for my model sm-a125w they are all for the sm-a125f model and i don’t want to brick my phone. do you think the f model roms would work on my model or have any rom suggestions?
physwizz said:
Choose a smaller gsi
Click to expand...
Click to collapse
whenever i try to wipe system_root it says inaccessible or not found in twrp terminal. i dont know whats going wrong here.
imdrew1234 said:
whenever i try to wipe system_root it says inaccessible or not found in twrp terminal. i dont know whats going wrong here.
Click to expand...
Click to collapse
Wipe system
tr
physwizz said:
Wipe system
Click to expand...
Click to collapse
tried that as well and same error occurs.
M04 twrp
MediaTek Helio P35 MT6765
Extra partitions added
No screen time out
Installation Instructions
Post 2
@physwizz
Device Tree
physwizz - Repositories
physwizz has 172 repositories available. Follow their code on GitHub.
github.com
Installing Custom Recoveries
A. Preparation.
1. Download firmware for your device
2. Extract ap file using Zarchiver and extract recovery.img from recovery.img.lz4 and compress it to recovery.tar
3. Patch the ap file with a magisk which will patch both boot.img and vbmeta.img (from magisk, choose install then select file to patch)
Exynos 850 Resources
t.me
Alternatively you can extract boot.img.lz4 and vbmeta.img.lz4 from the ap file and compress them into a new tar file and then patch that file.
note: if you don't want root then just extract the vbmeta.img and use zarchiver to add it to my twrp.tar file.
You can flash this new file from odin at step 5
For Exynos 850 android 11 use a21s patched magisk.
For Exynos 850 android 12 and most other devices use delta magisk
4. Unlock OEM in developer options
5. Attach phone to pc and reboot to download mode
6. flash patched ap file.
Or..
Extract boot.img and vbmeta.img and add them to the TWRP zip.
7. Download recovery.img or download twrp.tar and extract recovery.img using Zarchiver.
B.Installation
Note: some phones may need to be connected a pc or other device to boot to recovery
Method 1.
1. Connect to pc and boot into stock recovery
2. Factory reset
3. Reboot into download mode.
4. flash twrp tar file into the ap slot
5. reboot to recovery
6. Advanced, terminal. Type multidisabler (twice).
7.
Or flash samsung multidisabler zip
Or, for older phones flash dmverity zip
8. Reboot to recovery from main menu (not just reboot)
Backup boot, data, super and dtbo
9. Reboot to system
Method 2.
If you have already installed recovery and decrypted.
Extract recovery.img
1. Boot to recovery.
2. Install recovery.img
3. Choose recovery partition
4. Reboot to system then reboot to recovery
Backup boot, data, super and dtbo
(For Pitch-black just install the zip)
Method 3.
1. Install TWRP app
Extract recovery.img
2. Install TWRP
3. Choose file to flash.(don't select device)
4. Select recovery.img.
5. Reboot to recovery.
6. (You may need to change data partition to ext4 first if format ruins your system)
7. Reboot to recovery.
8. Wipe, format data, type YES.
9. Advanced, terminal.
10.Type multidisabler (twice).
Or flash samsung multidisabler zip
Or, for older phones flash dmverity zip
11.Reboot to recovery
12. Flash Magisk for root(only for method 3)
13. Backup boot, data, super and dtbo
Method 4
Using a second phone
Physwizz Collection
To flash TWRP from phone1 to phone2 Only if you have already installed recovery and decrypted. 1. Install this termux on phone1 2. Setup storage termux-setup-storage 3. Install this Heimdall Magisk module on phone1 Or install chroot Linux on termux and then install heimdall 4. Copy...
t.me
Method 5
If you have already installed recovery and decrypted.
install from system
1. extract recovery.img from tar file
2. open terminal app
3. navigate to folder containing recovery.img
4. type the following
dd if=/sdcard/recovery.img of=/dev/block/by-name/recovery
read t -5;reboot recovery
Method 6
If you have already installed recovery and decrypted.
Try bugjaeger mobile adb-usb otg app from playstore
C. Recovery Problems
Most recovery issues can be solved by attending to the following issues.
1. Did you root using the full ap file patched Magisk .
(This contains the patched boot.img and vbmeta.img)
Exynos 850 users must use the special a217 magisk?
2. Did you then go all the way through the setup process?
3. Did you download the recovery to match your baseband?
See https://t.me/a127f_res/54 for Exynos 850 recoveries
4. Did you hold down power and volume up after Odin says pass?
5. Did you format data from stock recovery?
If you forgot to do this, just install stock recovery.img from TWRP and reboot.
6. Did you type multidisabler twice?
If it doesn't work try this
Physwizz Collection
Decrypt. If multidisabler doesn't work try this method. 1. Copy /vendor/etc/fstab.**** over to another folder. 2. Edit it to remove the line containing the word "encryption" 3. Boot into twrp 4. Use twrp file manager to replace the fstab file with the edited one. 5. Format data (not just...
t.me
7. Did you reboot to recovery by choosing reboot from the menu and then choosing recovery?
8. To avoid touch issues go to settings and untick "allow time out"
9.For touch issues use a usb mouse
physwizz(Really Old Dev) in physwizz testing & discussion
If touch doesn't work on twrp, connect a usb mouse Everyone has an old mouse at home and the adapter costs less than a cup of coffee
t.me
D.To restore Stock Recovery
1. Attach phone to pc and reboot to download mode
2. flash patched ap file or stock recovery.tar
3. reboot
Or just flash stock recovery.img from twrp and reboot.
@physwizz
Let me know if it boots