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

[RECOVERY]TWRP_3.1.0_unofficial_ALCATEL_U5_&_TCL_5044_all_va riants

******TWRP 3.1 FOR TCL 5044 all variants******
---------------------------------------------------------------------------
DISCLAIMER : this is an unnoficial build created by myself Tested and confirmed working, i used magisk V18 as test.zip and is now rooted with magisk, there will be bugs comment here any issues you find & i will fix them asap,
UPDATE : 26th Jan 2019 : WORKING
* SD card mount now added
*OTG fixed
* terminal now works within TWRP no more child process exited error,
* sideload is functional
NOT WORKING : MTP
---------------------------------------------------------------------------
CHIP VERSION
---------------------------------------------------------------------------
Compatible chip type: FSTYPE
MEDIATEK : MT6737M EMMC
MEDIATEK : MT6735M EMMC
---------------------------------------------------------------------------
NOTICE : take a firmware backup before flashing
Anything to your device though this recovery is
Confirmed working you should always back your original firmware up, This recovery does NOT come with a Scatter.file included to stop bricking with incompatible device partitions, should you require it please ask in the comments.
--------------------------------------------------------------------------
0. make sure OEM unlock is ON in the developer options before doing anything.
1. Unzip the recovery from the .zip.
2. Open SP Flash tool.
3.set your DA AGENT to all in one MTK DA.
4.load your scatter.file into the Flash tool.
5.wait for your scatter to load your files.
6.unselect all files for flash but recovery.
7.load twrp_3.1 into recovery slot.
7.1 if you have 5044T flash my patched boot.img below also.
8.MAKE SURE DOWNLOAD ONLY is set DO NOT use format all + download.
9. Click start download.
10. Remove battery from phone.
11. Connect to pc with usb cord.
12. wait for flash to complete.
13. Unplug & insert your battery.
14. Hold power & volume up until the first screen appears and release, TWRP will now load.
15. Swipe to allow modifications.
16. Tap wipe.
17. Tap format & type yes then press ok
18. Reboot recovery once complete,
19. You can now root your device or flash what you need to.
20. Hit the thanks button here on XDA i spent hours upon hours building this for everyone once you reboot after formatting the data partition it will take roughly 5 minutes for your 5044 to boot.
---------------------------------------------------------------------------
If you need help please dont be afraid to ask here im here to help, if it does not boot on your device your board is different in which case you will need to attach your boot.img & recovery.img in a post so i can download and create a compatible twrp for your device.
_____________________________________________
LINKS :
TWRP 3.1.0 updated 26th Jan 2019
https://drive.google.com/file/d/1hi19OtPeVqSpe3c6VyRu8XusBcCpmai0/view?usp=drivesdk
PATCHED BOOT.IMG (no dm-verity) 5044T ONLY
https://drive.google.com/file/d/1SR99R4Bo-VoZnd4T9rQebt5tczaHNQxT/view?usp=drivesdk

Pics of twrp

NEW UPDATED TWRP 3.2.3-0 here for OPTUS X SPIRIT ( 5044T MT6737M - MT6735M ) everything is confirmed working in the latest build including MTP
TWRP 3.2.3-0
https://forum.xda-developers.com/android/development/twrp-t3903337

Alcatel Versa
First off... Great work and an awesome easy to follow tutorial. Now for the million dollar question... I have an Alcatel 5044c. It's the Cricket version and it's called the Versa. It has Android 7.0. Is this compatible?

Illbeurhuckleberry6666 said:
First off... Great work and an awesome easy to follow tutorial. Now for the million dollar question... I have an Alcatel 5044c. It's the Cricket version and it's called the Versa. It has Android 7.0. Is this compatible?
Click to expand...
Click to collapse
Hey mate,
No not for this recovery your kernel will be different,
If you 5044C is mediatek you can upload me your recovery.img and i can most certainly make you twrp for your 5044C
android version your currently on wont matter TWRP version 3.x.x supports from android 6-9

Matty1993 said:
Hey mate,
No not for this recovery your kernel will be different,
If you 5044C is mediatek you can upload me your recovery.img and i can most certainly make you twrp for your 5044C
android version your currently on wont matter TWRP version 3.x.x supports from android 6-9
Click to expand...
Click to collapse
Hi,
Since others are asking:
Does this support the Alcatel 5044Y?
Is this the latest release?
/Martin

5044c boot.img and recovery.img
Need scatter and flash files please
GH

[Guide][Installation][Fix]Switching from stock ROM to custom ROMs + Installing stock ROM after a brick or other Failures ( Mi A2 Lite - Daisy)

This guide is general guide for the installation of custom ROMs. I will also include guide to install stock ROM on devices which have been bricked or for solving various problem which you may encounter in custom ROMs. There are other guides for the same purpose but most of them are outdated and many of you seem to ignore old guide despite the fact that those guides can be helpful.
This is guide is only relevant for installation of custom ROMs which were released up to the date of posting this guide or up to android version 11. Recovering a bricked device can be done in the same way as to this one but installation instruction for devices with android version greater than 11 may differ.
DISCLAMER
Code:
I am NOT responsible for bricked devices,
thermonuclear war or for you getting fired because your alarm app failed.
Make sure the bootloader is unlocked and never lock the bootloader
How to unlock bootloader ?
>See in this thread.
Hard Brick, Soft brick, Problems in custom rom due to bad base, installation of base for switching to custom roms: windows linux
Installation of stock ROM through fastboot : The reply below
Migration from stock base to custom ROM : CLEAN FLASH
Migration between different version of same custom ROM : DIRTY FLASH
FOR SPECIFIC THREADS
Oragne Fox For Daisy
TWRP For Daisy
Magisk
CREDITS:
LInkBoi for his previous guide and TWRP
DarthJabba9 for Orange Fox Recovery
Every pros in daisy telegram groups.

EDL FLASHING (For windows only)​
EDL flashing can be helpful when flashing every partition of device is needed either for clean stock base or after brick or after some failure.
EDL flashing can be the final resort when everything else fails.
PREREQUISITES
1) A good USB cable, your phone
2) A PC with either windows or linux
3) Fastboot drivers from google and edl drivers from qualcomm
4) Platform tools from google
5)Fastboot rom. This should be full rom in .tgz format.
6)Xiaomi flash tool (LATEST VERSION AVAILABLE)
Install the adb and fastboot drivers from google. If you are on windows 10 or greater then you can also use "windows update > optional updates" to update adb and fastboot drivers + edl drivers. For the installation of drivers always use trusted sources and don't turn of driver signature enforcement if you can.
Extract the platform tools in a convenient folder, we will be doing our operations from this folder for fastboot and adb opeartions. Extract the fastboot ROM and place that in convenient folder as well. And for xiaomi flash tool extract the zip and launch XiaoMiFlash.exe .
If you can access fastboot in you phone then the phone can be booted into edl mode through fastboot else you have to take out back cover and short the testpoint pins to make the device boot into edl mode (see the attached image ).
If you can access fastboot. Boot into fastboot and type the following command in terminal.
To check if device is connected properly and drivers are properly installed
If no devices is shown then connect device properly with good usb cable and check the drivers.
Code:
fastboot devices
To boot phone into edl mode. This is only possible if the bootloader is unlocked else testpoint-edl is the only option
Code:
fastboot oem edl
The device should be shown as COM device in device manager ( Windows ). If not then either drivers aren't installed properly or your phone isn't in edl mode.
Now click on refresh button in xiaomi flash tool. Your device should be recognized as com device. Set the path to the images folder ( extracted fastboot rom ). Select CLEAN ALL option . If everything is good then click
on FLASH. The flashing process should start now. After the process completes keep pressing power button to boot device into the currently installed ROM.
Just install the rom and setup once even if you're going to flash custom rom next. This reduces various problems which may come in custom ROMs.
If any error occurs then try the following:
Make sure you are using latest flash tool.
Good fastboot rom (shouldn't be corrupted )
Good USB cable and try different ports of the PC.
The flashing should be done immediately after booting to edl. If not then take out battery and reconnect it if you have back cover open(In case of hard brick). Or keep pressing power button and volume down to boot into fastboot and boot to edl mode again from the above instructions(If fastboot is accessible)
For booting to edl using testpoint:
> Take out backcover
> Disconnect battery
> Short the pins
> Flash
> Connect battery after flashing is complete
> Keep pressing power button to boot into system.

qdl flashing ( linux only )​
For very detailed guide github -> bkerler edl
Thanks to DEFXZ and LinkBoi for suggesting this alternative.
Make sure you have platform tools, fastboot rom and other prerequisites to detect device properly.
clone the repository in convenient place
Code:
git clone https://git.linaro.org/landing-teams/working/qualcomm/qdl.git --depth=1
change to qdl directory
Code:
cd qdl
Build qdl tool
Code:
make
Finally flash the rom
Code:
./qdl --storage emmc --include /path/to/stock/images /path/to/stock/images/prog_emmc_firehose_8953_ddr.mbn /path/to/stock/images/rawprogram0.xml /path/to/stock/images/patch0.xml
The paths are the paths to various files inside the images folder which will be obtained after fastboot rom is extracted.
For further informations:
Original github link
qdl discussion in XDA

FASTBOOT FLASHING​
PREREQUISITES
FASTBOOT DRIVERS
PLATFORM TOOLS
FASTBOOT ROM
GOOD USB CABLE
PC WITH WORKING USB PORT
See this for meeting prerequisites.
Install fastboot drivers, connect device to PC via USB.
Extract platform tools into a convenient folder.
Extract fastboot ROM into a convenient folder.
Go to platform tools folder ( this will contain files and executable like fastboot.exe) and open powershell or any terminal window there
[ shift + right click and select open (powershell) window here ]
Type this command to see everything worked correctly.
Code:
fastboot devices
If not then check every step properly.
Now execute the script to flash the ROM.
Execute flash_all.bat script for windows PC.
Execute flash_all.sh script for linux PC.
If platform tools cannot be accessed system wide then.
Code:
./fastboot devices
will provide fastboot devices information.
For flashing drag and drop flash_all.bat or flash_all.sh file into the terminal.
Code:
'/media/user001/user/daisy/stock_roms/daisy_global_images_V10.0.18.0.PDLMIXM_9.0/flash_all.sh'
It will look something like this in linux and similar in windows.
If any error occurs the search for particular error. Most of the times the error is due to corrupted fastboot ROM or bad connection between phone and PC.

FINALLY! FLASHING CUSTOM ROM​
STEP 0
Flash(if not flashed already) the stock base recommended by particular ROM, if the ROM doesn't recommend a specific stock base flash 10.0.18.0 from the above instructions.
PREREQUISITES
TWRP or ORANGE FOX RECOVERY
Fastboot drivers and platform tools (details above )
The ROM which you want to flash, choose from here
GAPPS package if rom is vanilla and you want to install it.
Magisk if you want to root.
As you may have known by experience, our device doesn't have recovery partition so, flashing recovery through fastboot isn't possible. For flashing recovery first we need to boot recovery image and then only we can flash it.
If you want to use twrp:
Download both twrp*.zip and twrp*.img and place it in a convenient place.
If you want to use orange fox recovery:
Download orangeFox*.zip and extract it.
Keep both the .zip and .img file in convenient place.
If you have sdcard then copy ROM file, gapps, magisk, twrp or orange fox files into sdcard.
If not then there will be further instructions.
Now, connect the phone to the PC via USB and enable usb debugging. And open terminal in the platform tools folder as in above instructions.
Check device connectivity:
Code:
adb devices
Reboot into fastboot:
Code:
adb reboot bootloader
Check device connectivity:
Code:
fastboot devices
Lets check if the bootloader is unlocked:
Code:
fastboot oem device-info
If bootloader isn't unlocked you won't be able to flash custom recovery into the device. So, first unlock the bootloader. This should be allowed in the developers option of your phone first. This will factory reset the device.
Code:
fastboot oem unlock
Now if everything is good then it's time to boot into custom recovery:
Code:
fastboot boot recovery.img
recover.img is name of image of whichever custom recovery you want to use.
Code:
fastboot boot '/media/user001/storage (1)/daisy/twrp/twrp-3.5.2_9-2-daisy-unofficial.img'
It's like this in my case. You can drag and drop after typing fastboot boot
The phone should now boot into custom recovery. If it ask for decryption then your lockscreen password should work there.
if you want to flash recovery only then find the recovery.zip you want and flash it.
The steps further is also valid for moving between different custom roms. The term used for such process is CLEAN FLASH.
For Flashing custom ROMS :
SOMETIMES FLASHING INSTRUCTIONS MAY DIFFER SO, BE SURE TO CROSS CHECK FOR INSTRUCTION IN ROM SPECIFIC XDA THREAD OR TELEGRAM GROUP
The following action will wipe userdata if not wiped already. Be sure to backup data before these steps. Also if you encounter any future problems full backup from custom recovery may be able to solve most of the problems. So, be sure to keep full backup(including every partition) of your device.
Go to main menu > wipe > select all except internal storage and microSD.
Swipe right to perform wipe.
Install custom recovery by flashing recovery.zip
(This is done in case adb push doesn't work below and sdcard isn't available for flashing)
Again go to main menu > wipe > format data
Type yes and press enter.
If you don't have files in your sdcard then:
push rom file + gapps + other files into your device through adb push.
The command will be something like this:
Code:
adb push '/media/user001/storage (1)/daisy/posp/potato_daisy-11-20210919-dumaloo.v4.2.3+20.Community.zip' /sdcard
If adb push fails to work then you can reboot recovery and simply copy the files through file explorer.
Reboot to recovery only if you had installed recovery after wiping system else the device will soft brick
Now flash the rom.zip by selecting the file and swiping right.
Flash custom recovery if the ROM doesn't contain recovery
We have to change current slot even if we don't want to flash anymore things.
Latest recoveries changes slot automatically So, go to main menu > reboot > recovery
Now flash files which you want to flash i.e. gapps and magisk.
Again, Don't flash gapps if the ROM is of Gapps variant
Most of the roms now have implemented FBE (File Based Encryption ). So, you need to format data before rebooting to system. Again, check for specific ROM installation instruction if that is required or not. If you keep data from previous ROM that won't be considered a clean flash so, for proper clean flash format data before rebooting to system.
reboot system

MOVING BETWEEN DIFFERENT VERSION OF SAME CUSTOM ROM
Dirty flash or OTA ​
Most of the newer ROMs have seamless update ( even the unofficial ones ). The OTA update is simple. Just go to updater ( in settings > system or native app, depends upon the rom). If your ROM is of vanilla version then make sure gapps and/or magisk which you have installed, your ROM and custom recovery all support addon.d survival script. If they don't then you may have to flash everything again after update process is complete.
If custom recovery itself doesn't support update then you may need to choose different recovery or dirty flash ROM from the recovery. Don't worry most of the roms and both the recoveries for daisy support OTA and addon.d survival.
DIRTY FLASH​The process of flashing a ROM on top of existing one keeping the /data partition intact is known as dirty flashing. Such flashing must be done only on different builds of same ROM and it isn't recommended to flash build of lower version on top of higher version.
The steps for dirty flashing:
Download the update package.
Reboot to recovery
Enter password for decryption if encrypted.
Flash the update.zip package.
Reboot recovery, if recovery/rom doesn't support survival of recovery then flash recovery before rebooting to recovery.
If gapps and/or magisk survival isn't supported then flash gapps and magisk, make sure gapps is of the same type which was flashed before.
reboot system

Hi @user-001 thanks for this.
I'm on a stock A2 lite thats never had anything done to it , am i right in thinking i follow the clean flash section ?
You mention in there
We have to change current slot even if we don't want to flash anymore things.
Click to expand...
Click to collapse
I'm not fully sure what that involves could you break it down the steps a little for me.
I've downloaded all the files and am set up but i'm unsure on the Flashing fastbbot section where you say to use these files..
Execute flash_all.bat script for windows PC.
Click to expand...
Click to collapse
Is this a section i can bypass ? if not where can i get them from ?
Cheers

steve.loveday said:
Hi @user-001 thanks for this.
I'm on a stock A2 lite thats never had anything done to it , am i right in thinking i follow the clean flash section ?
You mention in there
I'm not fully sure what that involves could you break it down the steps a little for me.
I've downloaded all the files and am set up but i'm unsure on the Flashing fastbbot section where you say to use these files..
Is this a section i can bypass ? if not where can i get them from ?
Cheers
Click to expand...
Click to collapse
1) Yes you should follow clean flash instructions.
2)Changing of slot is done in custom recovery. Precisely in the reboot menu. But newer recoveries automatically switch the slot after flashing the rom , just be sure to reboot to recovery after flashing the recovery zip file.
3) the flash_all.bat script will be inside the extracted rom(fastboot rom) folder. You can use xiaomiflash too for flashing through fastboot.

user-001 said:
1) Yes you should follow clean flash instructions.
2)Changing of slot is done in custom recovery. Precisely in the reboot menu. But newer recoveries automatically switch the slot after flashing the rom , just be sure to reboot to recovery after flashing the recovery zip file.
3) the flash_all.bat script will be inside the extracted rom(fastboot rom) folder. You can use xiaomiflash too for flashing through fastboot.
Click to expand...
Click to collapse
Hi thanks for the reply,
I'm getting confused with all the various guides all seem to want you to do it a different way.
As i'm wanting Lineage thier instructions are...
Installation:
Download the latest build from here
Download LinkBoi00's version of TWRP here
Reboot to bootloader (adb reboot bootloader)
Fastboot into TWRP recovery (fastboot boot twrp*.img)
Do a factory reset in TWRP
Flash the latest build of Lineage OS
Boot into your new phone
Click to expand...
Click to collapse
Theres no mention of the edl or fastboot flashing and also the fastbot rom i downloaded doesnt have the flash_all.bat script in the zip file.
So do i follow thier instructions or these ones ?
Cheers

steve.loveday said:
Theres no mention of the edl or fastboot flashing and also the fastbot rom i downloaded doesnt have the flash_all.bat script in the zip file.
So do i follow thier instructions or these ones ?
Cheers
Click to expand...
Click to collapse
This guide deals with how to do something rather than what to do, meaning you should always do what particular rom suggests but the way to do this is mentioned here.
edl or fastboot flashing comes under clean flashing with new base, most of the time you aren't required to do this.
The script should be clean_all.bat or something similar just don't execute script with lock in the name(it will lock the bootloader)
And if you're already on the recommended base you don't have to flash the fastboot rom.

First of all, thank you very much for the detailed guide. What you have done here took a lot of work to do but it will help a lot of people (including me) to understand, albeit rudimentarily, the structures and functions of the devices etc.
For all that, thanks again.
When I start using the guide, I will update this post with any questions, such as :
fastboot boot '/media/user001/storage (1)/daisy/twrp/twrp-3.5.2_9-2-daisy-unofficial.img'
why not doing below? (For those who, like me, are not very familiar with linux.)
1. > adb push <twrp.img> /sdcard or same adb push "C:\platform-tools\twrp-3.5.2_9-2-daisy-unofficial.img" /sdcard
( which means push <file> from "adb|platform-tools\ folder" (eg. C:\platform-tools\)
into the root of <internal storage> | /storage/emulated/0 )
2. Reboot from adb to fastboot:
> adb reboot bootloader
3. Boot the image from <internal storage>:
> fastboot boot /sdcard/twrp-3.5.2_9-2-daisy-unofficial.img
What is the "Red" pointed and "Yellow" addresses"?
fastboot boot '/media/user001/storage (1)/daisy/twrp/twrp-3.5.2_9-2-daisy-unofficial.img'

I followed your "EDL FLASHING" post (#2) and it worked exactly as you mention!
In short, I was comming from unsuccessful flashing... but this is out of topic.
For me, did not worked the first time (after restarts) but the other day worked perfect.
The point is, most of times, it's becase windowz drivers.
We have to point that windowz needs their time to take the drivers in place. So, be patient and leave windowz to (not forced) restart(s).

AntonyMan said:
What is the "Red" pointed and "Yellow" addresses"?
fastboot boot '/media/user001/storage (1)/daisy/twrp/twrp-3.5.2_9-2-daisy-unofficial.img'
Click to expand...
Click to collapse
That must be your terminal representing different type of character in different colors.
Or, Are you talking about something else ?

steve.loveday said:
Theres no mention of the edl or fastboot flashing and also the fastbot rom i downloaded doesnt have the flash_all.bat script in the zip file.
So do i follow thier instructions or these ones ?
Cheers
Click to expand...
Click to collapse
For future references, the extracted fastboot ROM should be like this and you need to execute flash_all.bat or flash_all.sh script depending upon your OS or terminal.

user-001 said:
That must be your terminal representing different type of character in different colors.
Or, Are you talking about something else ?
Click to expand...
Click to collapse
Of course I'm talking about something else. lol
I was talking about that 'strange' address. fastboot boot '/media/user001/storage (1)/daisy/twrp/twrp-3.5.2_9-2-daisy-unofficial.img' (explained in post #11)
There is not such a directories in my miA2Lite phone. Obviously, it's because you are on Linux or Mac (UNIX). On Windowz 'command prompt' syntax it's slightly different.
Thus, I typed fastboot boot "/sdcard/twrp-3.5.2_9-2-daisy-unofficial.img"
* /sdcard is the root of <internal storage> directory.
** On Windows, double quote the address, if it's include spaces.

AntonyMan said:
Of course I'm talking about something else. lol
I was talking about that 'strange' address. There is not such a directories in my miA2Lite phone.
Thus, I typed fastboot boot "/sdcard/twrp-3.5.2_9-2-daisy-unofficial.img"
* /sdcard is the root of <internal storage> directory.
** On Windows, double quote the address, if it's include spaces.
Click to expand...
Click to collapse
The twrp image was on my pc(linux) i was booting directly from pc's terminal. And if you use only adb(or fastboot) then the paths are pc's absolute paths.

Oukitel k15 pro

Hey does anyone know about a custom recovery for oukitel k15 pro? Or can I get away with using the stock recovery and a patched magisk file? If so does anyone have a up to date link.
Also would lineage work on this phone.
Thanks in advance

Lewickham2022 said:
Hey does anyone know about a custom recovery for oukitel k15 pro? Or can I get away with using the stock recovery and a patched magisk file? If so does anyone have a up to date link.
Also would lineage work on this phone.
Thanks in advance
Click to expand...
Click to collapse
There is no custom recovery. Oukitel haven't even posted the official Android 11 ROM on their Download Center website yet, even though I sent them a message about it a week or two ago.
I bought the phone, but haven't gotten it yet.
I wouldn' t do anything to modify the ROM without having the official ROM from Oukitel to unbrick the phone just in case something goes wrong with Magisk or something.
There are ways to extract the ROM with SP Flash Tool or maybe something else, so I would do that first.
For rooting I found this link for Oukitel wp12 with Android 11, I think I would try the same method with K15 Pro
Oukitel WP12 Magisk root bootloop
I'm trying to root an Oukitel WP12 with Magisk. I've downloaded the firmware from the vendor's link and flashed it successfully just like for other Oukitel phones (WP6, WP10). I could also create a magisk-patched boot image. I followed regular...
forum.xda-developers.com
Then, if that's not enough and we want a custom ROM like Lineage, for example, then we would have to use a GSI ROM like those from here
Generic System Image (GSI) list
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
and follow something like the fastboot method outlined here for wp5
GitHub - adil192/OukitelWP5TrebleTips: Sharing my experience with flashing a GSI on a friend's Oukitel WP5 (3GB model).
Sharing my experience with flashing a GSI on a friend's Oukitel WP5 (3GB model). - GitHub - adil192/OukitelWP5TrebleTips: Sharing my experience with flashing a GSI on a friend's Oukitel WP5...
github.com
Maybe there's a better link for GSI fastboot for Oukitel with Android 11
If you try anything, let me know. I'm waiting for my k15 pro to arrive, possibly next week.
I need it rooted, at least.

Let me know the outcome of rootin the k15 pro and if you succeed please tell me the steps. Also do you know if lineage will be compatible eventually?

Is there any news yet?

Lewickham2022 said:
Is there any news yet?
Click to expand...
Click to collapse
My phone came from AliExpress after 3.5 months, jeez. Got a refund, too, which I might return, never mind.
I dumped/backed up ROM partitions, except userdata because it's big and backup unnecessary, unless you want to keep your personal data in raw binary state for later, and rooted the phone.
You need MTK VCom drivers installed, e.g. from here:
Download MediaTek USB VCOM Drivers for Windows (32 & 64 bit)
Download MTK USB VCOM Drivers for Windows 10 to connect MediaTek phones even in a bricked state. Also, check the Installation guide.
www.ytechb.com
Use mtkclient:
mtkclient/README.md at main · bkerler/mtkclient
MTK reverse engineering and flash tool. Contribute to bkerler/mtkclient development by creating an account on GitHub.
github.com
I unlocked bootloader first. Remember UNLOCKING BOOTLOADER WIPES ALL DATA, returns to factory settings, back up all personal data to PC or SD card first!
To unlock bootloader, if you don't know, go to Settings, About Phone, tap 7 times on Build Number, You are Developer flashes on, go to System, Developer Options, OEM unlocking on, USB debugging on.
MTKCLIENT has a command to unlock the bootloader, it would surely work, I used Fastboot before I learned of mtkclient.
If using Fastboot, turn off phone. Hold Volume up and Power. Choose Fastboot. Connect phone.
You need Minimal Fastboot and ADB installed:
Download Minimal ADB and Fastboot Tool (all versions)
Download the latest version of Minimal ADB and Fastboot Tool which allow you to install and setup the ADB and Fastboot files on the computer.
androidmtk.com
Open CMD, type:
fastboot devices
if phone is listed, then type:
fastboot flashing unlock
fastboot reboot
Never re-lock the bootloader if your phone is rooted or GSI Lineage or other ROM other than original is installed. More than likely would brick the phone.
Everything is explained in mtkclient readme, line by line.
I used Windows 10, works on 11 too, there is a guide for Linux, and even a Ubuntu live image to use. Back up partitions first. Oukitel still haven't posted ROM, but can extract it from the phone, no problem.
Root is explained, need to get modified Magisk for MTK, and flash patched boot and empty vbmeta. It worked like a charm. There are guides on XDA on how to flash System GSI images to Android Super partition. Might try it later. One is here:
How to flash GSIs on devices with dynamic super partition
* Disclaimer * I am not responsible for bricked devices, dead SD cards, thermonuclear war, * or you getting fired because the alarm app failed. Please do some research * before flashing GSI! YOU are choosing to make these modifications, and if *...
forum.xda-developers.com
GSI Lineage images are here:
Andy Yan's personal builds // GSI - Browse /lineage-19.x at SourceForge.net
sourceforge.net
You couldn't add GAPPS, though, no TWRP, unless there is another way, doubt it. Could install replacement MicroG. Plenty other GSI images here:
Releases · phhusson/treble_experimentations
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Good luck.

MarkR7 said:
My phone came from AliExpress after 3.5 months, jeez. Got a refund, too, which I might return, never mind.
I dumped/backed up ROM partitions, except userdata because it's big and backup unnecessary, unless you want to keep your personal data in raw binary state for later, and rooted the phone.
You need MTK VCom drivers installed, e.g. from here:
Download MediaTek USB VCOM Drivers for Windows (32 & 64 bit)
Download MTK USB VCOM Drivers for Windows 10 to connect MediaTek phones even in a bricked state. Also, check the Installation guide.
www.ytechb.com
Use mtkclient:
mtkclient/README.md at main · bkerler/mtkclient
MTK reverse engineering and flash tool. Contribute to bkerler/mtkclient development by creating an account on GitHub.
github.com
I unlocked bootloader first. Remember UNLOCKING BOOTLOADER WIPES ALL DATA, returns to factory settings, back up all personal data to PC or SD card first!
To unlock bootloader, if you don't know, go to Settings, About Phone, tap 7 times on Build Number, You are Developer flashes on, go to System, Developer Options, OEM unlocking on, USB debugging on.
MTKCLIENT has a command to unlock the bootloader, it would surely work, I used Fastboot before I learned of mtkclient.
If using Fastboot, turn off phone. Hold Volume up and Power. Choose Fastboot. Connect phone.
You need Minimal Fastboot and ADB installed:
Download Minimal ADB and Fastboot Tool (all versions)
Download the latest version of Minimal ADB and Fastboot Tool which allow you to install and setup the ADB and Fastboot files on the computer.
androidmtk.com
Open CMD, type:
fastboot devices
if phone is listed, then type:
fastboot flashing unlock
fastboot reboot
Never re-lock the bootloader if your phone is rooted or GSI Lineage or other ROM other than original is installed. More than likely would brick the phone.
Everything is explained in mtkclient readme, line by line.
I used Windows 10, works on 11 too, there is a guide for Linux, and even a Ubuntu live image to use. Back up partitions first. Oukitel still haven't posted ROM, but can extract it from the phone, no problem.
Root is explained, need to get modified Magisk for MTK, and flash patched boot and empty vbmeta. It worked like a charm. There are guides on XDA on how to flash System GSI images to Android Super partition. Might try it later. One is here:
How to flash GSIs on devices with dynamic super partition
* Disclaimer * I am not responsible for bricked devices, dead SD cards, thermonuclear war, * or you getting fired because the alarm app failed. Please do some research * before flashing GSI! YOU are choosing to make these modifications, and if *...
forum.xda-developers.com
GSI Lineage images are here:
Andy Yan's personal builds // GSI - Browse /lineage-19.x at SourceForge.net
sourceforge.net
You couldn't add GAPPS, though, no TWRP, unless there is another way, doubt it. Could install replacement MicroG. Plenty other GSI images here:
Releases · phhusson/treble_experimentations
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Good luck.
Click to expand...
Click to collapse
Thanks for the reply. I had a few problems with micro g on MI A2. After flashing micro g in magisk is there a certain gapps I need to flash? Or can I just download Google services after flashing micro g

Lewickham2022 said:
Thanks for the reply. I had a few problems with micro g on MI A2. After flashing micro g in magisk is there a certain gapps I need to flash? Or can I just download Google services after flashing micro g
Click to expand...
Click to collapse
I was wrong about LineageOS not having GAPPS preinstalled. The link I gave you:
Andy Yan's personal builds // GSI - Browse /lineage-19.x at SourceForge.net
sourceforge.net
has this system image of LineageOS with GAPPS included, vndklite are read/write system images that I saw someone said were working on Oukitel phones with Android 11, and are generally probably best to use, so if you use that one, you don't need microG, which would have to be installed from F-Droid store or something like that:
https://sourceforge.net/projects/andyyan-gsi/files/lineage-19.x/lineage-19.1-20220410-UNOFFICIAL-arm64_bgS-vndklite.img.xz/download
G or g in the name of the system indicates that GAPPS are included.
I will try to flash that one myself sooner or later. It's based on Android 12, and if it doesn't work for some reason then we would have to drop to Lineage 18.1, but those aren't with GAPPS, so microG required:
Andy Yan's personal builds // GSI - Browse /lineage-18.x at SourceForge.net
sourceforge.net
There are other ROM with plenty of customizations that might be ok.
Corvus OS
Download Corvus OS for free. Corvus OS is another retarded ROM with many retarded Customization. First, it's inspired by Dirty Unicorns (thanks to Alex Cruz), but then we picked many other features too.
sourceforge.net
has GAPPS
Rest is here to choose from:
Generic System Image (GSI) list
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Funny, I'm using Xiaomi Mi A2 Lite now.

Lewickham2022 said:
Thanks for the reply. I had a few problems with micro g on MI A2. After flashing micro g in magisk is there a certain gapps I need to flash? Or can I just download Google services after flashing micro g
Click to expand...
Click to collapse
OK, it is possible to install Android 11 GSI system images on this phone. Android 12 images do not work, something to do with incompatible boot partition.
It's possible to try out GSI system images without flashing by installing this app:
GitHub - VegaBobo/DSU-Sideloader: A simple app made to help users easily install GSIs via DSU's Android feature.
A simple app made to help users easily install GSIs via DSU's Android feature. - GitHub - VegaBobo/DSU-Sideloader: A simple app made to help users easily install GSIs via DSU's Android feat...
github.com
Root is useful, but not necessary. Seems not to work, maybe needs flashed empty vbmeta_system and vbmeta_vendor like indicated below and I restored all to stock ROM except for boot.img with Magisk 24.3 and empty vbmeta.img
If you managed to make full backup of ROM with mtkclient, enable USB debugging, unlock bootloader, then to flash GSI images or Lineage 18.1 based on Android 11 (it works, but no image with gapps unless found somewhere else) you have to have installed Google Android USB driver from here
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
Unpack files, connect phone in recovery, power + volume up then power+ volume up fast click, choose fastboot, that gives you FastbootD (colorful menu), which is now used to flash system partitions. Connect phone, install driver with .inf file.
You also need Google platform tools
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Unpack anywhere if on Windows.
Run cmd, then "fastboot devices" to see if phone gets detected, should be there.
From here get product_gsi.img:
[Tutorial] Magisk on GSI on devices with dynamic partition
I hope you already know how to flash GSI on devices with dyamic partition already. If not then you can follow this guide: https://forum.xda-developers.com/t/how-to-flash-gsis-on-devices-with-dynamic-super-partition.4256667/#post-85271987 If...
forum.xda-developers.com
In mtk client is an empty vbmeta file - vbmeta.img.empty or similar, needs to be flashed to vbmeta, vbmeta_system, and vbmeta_vendor to disable verification of boot for magisk, and system and vendor for GSI system images. Can be done with mtkclient or normal fastboot ( power + volume down, choose fastboot, connect phone, run cmd, then "fastboot flash vbmeta vbmeta.img.empty (could be renamed to anything simple, name doesn't matter))
Then
fastboot flash vbmeta_system vbmeta_img.empty
Then
fastboot flash vbmeta_vendor vbmeta.img.empty
Same file to all three partitions, disables verification, worked for me. Can be done with GUI in mtkclient, same thing. Or commands in mtkclient
"python w vbmeta vbmeta.img.empty"
Etc.
Back to FastbootD -
"fastboot reboot fastboot" or power + volume up for recovery then click them again, choose fastboot.
Or probably "adb reboot fastboot" if phone is running system.
Run cmd, "fastboot devices" to be sure phone is detected, then
"fastboot flash product product_gsi.img"
This resizes dynamic system partition when flashing system images. This only modifies internal logical partitions within SUPER partition that contains Product, System, and Vendor. SUPER can be restored with mtkclient or just fastboot, I guess, I restored with mtkclient, works.
Then you can flash any system based on Android 11, stock phhusson GSI works. the system needs to be arm64, ab (for A/B partitions, indicated by letter B in name), vndklite, G or Gapps (if you want them), V is vanilla - no gapps, S is superuser but seems to have conflicts with magisk if you want that as root later. N is no superuser/root.
Eg.
"fastboot flash system Lineage-18.1-2021214-UNOFFICIAL-treble_arm64_bvS-vndklite.img" Rename this to 1.img or whatever, simpler to type
"fastboot flash system.1.img" or something like that.
"Invalid Sparse System Image At Magic Header" appears, but doesn't matter, starts flashing in 30 seconds or so, 10 or 11 chunks, maybe 2-3 minutes per system image.
Then
"fastboot reboot" go to recovery, power +volume up, click them again, choose wipe user data, wipe cache to get rid of old settings and apps from previous system.
"fastboot reboot recovery" should work too.
Seems that on custom ROMs Magisk 24.3 app gives option to directly patch boot image without need for flashing patched boot.img. Not sure about that. Just flashing patched boot.img in fastboot gives root, anyway.
If you just want newest Magisk then flash empty vbmeta and then patched boot Magisk generates. Those can be done in normal fastboot. Works fine.
Everything seems to work.

ROOT Sony Xperia XA2 H3113 on Iodé 3.4-2, lineage Os 19.1 or android 12 DONE !

( this tutorial is only for iodé os 3.4-20221215-pioneer on a Sony Xperia h3113 pioneer )
In this exploitation system, the boot.img is stocked in the payload of your zip install.
0. Before all,
I am not responsible if you make a mistake and brick your phone ( bad usb connexion, wrong or corrupted img ect.. ), I won't help you if it's the case after this tutorial.
You'll need to know how to use* " Minimal ADB and Fastboot" , and get the correct USB windows drivers for your phone ( *like unlock the bootloader with the sony code given with your IMEI activate the developper mode, usb debug & unlock the bootloader )
After typing adb reboot bootloader on the CMD of Minimal ADB Fastboot wait until the blue light appear on your Xperia XA2 pioneer.
Download Latest Minimal ADB and Fastboot Tool v1.4.3 (Dec 2018)
Minimal ADB and Fastboot Tool v1.4.3 is now available for download and install.If you are looking for the latest version of the Minimal ADB and Fastboot tool
rootmygalaxy.net
1. Root won't install with magisk in Lineage Os 19.1 or idoé os 3.4.20221215 if you don't change the original recovery file to TWRP recovery.
Download : https://eu.dl.twrp.me/pioneer/twrp-3.7.0_9-0-pioneer.img.html rename the *.img to twrp.img copy the *.zip in your phone
boot on TWRP with the administrator CMD ( you have copied in ) Minimal ADB Fastboot by typing : fastboot boot twrp.img
install TWRP with "Minimal ADB and Fastboot" by following the Advanced > Flash Current TWRP option, with the *.zip of TWRP on your phone.
Sony Xperia XA2
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
( the “Fix Recovery Bootloop” option is not needed anymore , pay attention to use "advanced" and not "install" in TWRP )
2. Download the *.zip of your system installation ( Lineage Os 19.1, iodé Os 3.4-2 - Android 12 ) and extract it on windows.
3. Use "payload dumper go" to get the boot.img, there's a tutorial on XDA here :
https://forum.xda-developers.com/t/...-payload-bin-using-payload-dumper-go.4468781/ )
NB : If you don't want to extract the boot.img with payload dumper go
just take this one only for Sony XA2 H3113 Pioneer ( 1 sim only )
Download boot.img on mega nz
4. Copy the boot.img in a folder of your XA2 H3113 pioneer phone.
5. Install Magisk, then patch the boot.img
( I've followed this video tutorial )
6. Copy the " magisk *** patched *.img" files of your H3113 download folder in the windows folder install of minimal ADB fastboot, and rename it to magisk.img
7.
In the administrator CMD of minimal ADB Fastboot on windows type :
. "adb reboot bootloader" enter
. "fastboot flash boot magisk.img" enter
It's alldone !

for h3123

hi not works more for me i am trying flashing twrp goes to bootloop

CyanRose said:
hi not works more for me i am trying flashing twrp goes to bootloop
Click to expand...
Click to collapse
This tutorial is for h3113, i don't know for h3213, I don't have one.

Also take care of the version of iodé os, I won't do update anymore ( I'll stay on 3.4-20221215). But Android 11 was faster on xperia H3113.
Iodé os didn't inform me before the update that it would change the core of the system and change the recovery ( unroot the phone ).
This update bring me only ****s like a slower system, unroot the phone and de-configurate all aps in the iodé ap ( an integrated firewall ).