Database Info

[Solved] Elephone P8 Max Root

Hello, this is my first post
Don't let me waste time...
Requirements
1.Stock boot.img for your phone model (its best its for your Build Number / Variant ) . You can extract from the stock rom / firmware of your device OR backup from your device using a box e.g Miracle box, CM2, etc
2.Download Latest Magisk Manager
Steps on how to root an Elephone P8 Max using Magisk Manager and patched boot.img
Step 1: Patching the stock boot.img
1.Install MagiskManager apk on your android device
2.Copy the stock boot.img of your device to your phone's internal storage or SD card
3.Launch Magisk Manager app
4.If prompted to install Magisk, select NO THANKS
5.If you are using a samsung device and wish to flash using Odin, then select Options > Settings > Update Settings > Patched Boot Output Format > img.tar )
6.Select Install > Install > Patch Boot Image File >
7.Navigate to the location of the stock boot.img you copied earlier on, then Select it
8.Magisk Manager should begin downloading the magisk zip file used for patching
9.Once download is complete, MagiskManager will automatically patch the boot file and store it under SDcard/MagiskManager/patched_boot.img[.tar]
Step 2: Flashing the patched boot.img
You have a variety of options to flash the patched boot.img depending on you
1.Sp Flashtool
2.Fastboot
3.Miracle Box
1. For Sp Flashtool copy the patched boot.img with mt6755 scatter file and make sure to rename patched boot.img to boot.img before flashing
2.For fastboot copy the patched boot.img to your fastboot folder and press shift right click on a free space in the fastboot folder, you would see open command here. Click on it and boot your Elephone P8 Max to fastboot with power+volume up and use volume down to select fastboot and connect your Elephone P8 Max. Your PC type fastboot devices to check if the system as seen it. Now type fastboot flash boot patched_boot.img
You are done.
3.For miracle box rename the file from .img to .bin before flash.
In case you lazy..:laugh:
I have the patched_boot.img here
https://drive.google.com/file/d/17jjlC_znGMEA6HY0H0l4XP6LaBIv7n_t/view?usp=drivesdk
Enjoy..use root checker to confirm
Anyone who can support for custom recovery

TWRP for Elephone p8 Max
I need the newest TWRP for Elephone p8 Max. Can anybody help?
Thanks

Iamkratos said:
Hello, this is my first post
You have a variety of options to flash the patched boot.img depending on you
2.Fastboot
Click to expand...
Click to collapse
Hi I tried fastboot.
fastboot oem unlock OK
fastboot flash recovery patched_boot.img
works, but after switch off an boot into recovery, just normal android 7 starts, no twrp.
When boot finished, touching on display does not work anymore.
Any hinds?
Elephone P8_Max
Android 7.0
Build-Number:
Elephone_P8_Max_20171221
Thanks for any help.

aaaalbi2 said:
Hi I tried fastboot.
fastboot oem unlock OK
fastboot flash recovery patched_boot.img
works, but after switch off an boot into recovery, just normal android 7 starts, no twrp.
When boot finished, touching on display does not work anymore.
Any hinds?
Elephone P8_Max
Android 7.0
Build-Number:
Elephone_P8_Max_20171221
Thanks for any help.
Click to expand...
Click to collapse
Because you flash boot.img as recovery
That why your phone is getting that fault
You are suppose to flash boot
Fastboot flash boot patched_boot.img OK
Or use sp flashtool or miracle box
I included the scatter file

I have the twrp but it doesn't touch only if you use otg with Mouse

Alternative scatter file for MT6750
Hi lmkratos,
thank you very much!
This worked like a charm but I had to use a different scatter file (attached here) as the P8 Max has a MT6750 (not MT6755) and the PMT didn't match so spflash refused to flash boot ("PMT changed for the ROM").
If you happen to be on Linux: spflash works perfectly but take care to stop ModemManager (WAN modems) before flashing as it interferes, so
"service ModemManager stop".

rec Please send it, thank you
Iamkratos said:
I have the twrp but it doesn't touch only if you use otg with Mouse
Click to expand...
Click to collapse
rec Please send it, thank you
---------- Post added at 04:18 AM ---------- Previous post was at 04:16 AM ----------
Iamkratos said:
I have the twrp but it doesn't touch only if you use otg with Mouse
Click to expand...
Click to collapse
twrp Please upload, thank you

Guide to Install GApps and Magisk on Custom ROMs for Nokia 7.2

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

Development Orange Fox for M12 U2 & U3

Orange Fox for m12 u3 and u3
Built by Roger F
modified by physwizz
Download tar file.
Extract recovery.img from tar file
Method 1.
If you have already installed recovery and decrypted.
1. Boot to recovery.
2. Install recovery.img
3. Choose recovery partition
4. Reboot to recovery
Method 2.
1. Download firmware
2. Extract ap file.
3. Patch with magisk
4. Flash with Odin
5. Download recovery.img
6. Install TWRP app
7. Install TWRP
8. Choose file to flash.(don't select device)
9. Select recovery.img.
10. Reboot to recovery.
Go to part B
Method 3.
1. Download recovery tar
2. Download vbmeta disabled tar
Exynos 850 Resources
t.me
3. Connect phone to PC
4. Go to Download mode
5. Flash recovery tar into ap with Odin
6. Flash vbmeta disabled tar into userdata with Odin
Part B
7. Reboot to recovery.
8. Wipe, format data, type YES.
9. Advanced, terminal.
10.Type multidisabler (twice).
11.Reboot to recovery
Reboot and setup phone completely
12. Flash Magisk for root(only for method 3)
13. Backup boot, data, super and dtbo
@physwizz

In general, things are like this, I run Odin with administrator rights, I throw twrp and vbmeta, I run it, and at the vbmeta firmware stage, a failure occurs and an inscription in red in the loader, ( SW REV. CHECK FAIL(VBMETA) DEVICE: 0x3, BINARY: 0x0

physwizz said:
Afaneh TWRP modified by physwizz
For baseband u3
Download tar file.
Extract recovery.img from tar file
Method 1.
If you have already installed recovery and decrypted.
1. Boot to recovery.
2. Install recovery.img
3. Choose recovery partition
4. Reboot to recovery
Method 2.
1. Download firmware
2. Extract ap file.
3. Patch with magisk
4. Flash with Odin
5. Download recovery.img
6. Install TWRP app
7. Install TWRP
8. Choose file to flash.(don't select device)
9. Select recovery.img.
10. Reboot to recovery.
Go to part B
Method 3.
1. Download recovery tar
2. Download vbmeta disabled tar
Exynos 850 Resources
t.me
3. Connect phone to PC
4. Go to Download mode
5. Flash recovery tar into ap with Odin
6. Flash vbmeta disabled tar into userdata with Odin
Part B
7. Reboot to recovery.
8. Wipe, format data, type YES.
9. Advanced, terminal.
10.Type multidisabler (twice).
11.Reboot to recovery
12. Flash Magisk for root(only for method 3)
13. Backup boot, data, super and dtbo
@physwizz
Click to expand...
Click to collapse
So, everything went, it worked, I found another vbmeta file from samsung sm-a217f and installed it, I'll attach a working file for m12 below

thank you so much for your work

KEMLEP said:
So, everything went, it worked, I found another vbmeta file from samsung sm-a217f and installed it, I'll attach a working file for m12 below
Click to expand...
Click to collapse
You don't need vbmeta.tar if you root using the patched ap file.

I can't believe only 1 person has installed it

I noticed an unpleasant bug in orange fox on m12, when it is blocked, the swipe does not work, I swipe with my finger, and it does not work, I have to restart

and another inscription pops up in the logo "E: A render request has failed"

KEMLEP said:
and another inscription pops up in the logo "E: A render request has failed"
Click to expand...
Click to collapse
I'll post a different one soon

physwizz said:
I'll post a different one soon
Click to expand...
Click to collapse
thank you very much, I'm waiting with impatience

So it's just the only one with the m12 model, the rest with the A12, although I saw a little man with the Indian version of the F12

KEMLEP said:
thank you very much, I'm waiting with impatience
Click to expand...
Click to collapse
Done
TWRP for m12 U3 and U2
TWRP for m12 u3 (See post#2 for u2 version) Built by Afaneh mod physwizz Download tar file. Extract recovery.img from tar file Method 1. If you have already installed recovery and decrypted. 1. Boot to recovery. 2. Install recovery.img 3...
forum.xda-developers.com

Thank you, everything works, but for some reason the swipe unlock does not work, I move my finger and it stands still and does not move, and so if you turn off the screen time, then everything works, thank you again, may God give you strength and reward you all the best for your labors

KEMLEP said:
Thank you, everything works, but for some reason the swipe unlock does not work, I move my finger and it stands still and does not move, and so if you turn off the screen time, then everything works, thank you again, may God give you strength and reward you all the best for your labors
Click to expand...
Click to collapse
Thanks.
Try swiping 6 times

Question How to root derkpest os in op9?

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

Question phone wont boot after installing twrp or gsi (a125w, originally an a125u)

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.