[Solved] Elephone P8 Max Root - Android General

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

Related

How To flash [ SYSTEM.IMG ] using TWRP

Hii.. All , I'm using A Lyf wind mobile , I have my my orginginel ( system.img ) file I don't have PC Computer . , I'm using TWRP 3.0 .. Somebody help me how to flash a System.img using TWRP
_ THANKS _
vinay durva said:
Hii.. All , I'm using A Lyf wind mobile , I have my my orginginel ( system.img ) file I don't have PC Computer . , I'm using TWRP 3.0 .. Somebody help me how to flash a System.img using TWRP
_ THANKS _
Click to expand...
Click to collapse
TWRP can flash .img files without having to do anything special.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
TWRP can flash .img files without having to do anything special.
Click to expand...
Click to collapse
Sir .. I was tried , there was only 2 options in TWRP 1st one recovery & 2cond one boot .. Which 1 ican select ,, I need to flash system.img
vinay durva said:
Sir .. I was tried , there was only 2 options in TWRP 1st one recovery & 2cond one boot .. Which 1 ican select ,, I need to flash system.img
Click to expand...
Click to collapse
I dont think you've booted into TWRP yet, I think you're looking at bootloader, select recovery and see if it boots to TWRP.
TWRP has more than just 2 options, are you sure you have TWRP? What version is it? Does it look like this?
http://cloud.tapatalk.com/s/58a730280544c/Screenshot_2017-02-17-12-15-48.png?
If that's what you have, select Install then find your .img and flash it.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
I dont think you've booted into TWRP yet, I think you're looking at bootloader, select recovery and see if it boots to TWRP.
TWRP has more than just 2 options, are you sure you have TWRP? What version is it? Does it look like this?
http://cloud.tapatalk.com/s/58a730280544c/Screenshot_2017-02-17-12-15-48.png?
If that's what you have, select Install then find your .img and flash it.
Click to expand...
Click to collapse
Yes sir I'm Booting Into TWRP , Then > install > install images >. I found 2 options 1st one BOOT 2cond RECOVERY , but I won't to flash SYSTEM.img
vinay durva said:
Yes sir I'm Booting Into TWRP , Then > install > install images >. I found 2 options 1st one BOOT 2cond RECOVERY , but I won't to flash SYSTEM.img
Click to expand...
Click to collapse
I remember now that TWRP doesn't flash system.img correctly, system.img isn't a standard .img, you need PC and use fastboot.
Sent from my SM-S903VL using Tapatalk
Thanks Sir.. Any Another way to flash system , i don't have A PC
vinay durva said:
Thanks Sir.. Any Another way to flash system , i don't have A PC
Click to expand...
Click to collapse
I wouldn't try it without PC
Sent from my SM-S903VL using Tapatalk
vinay durva said:
Thanks Sir.. Any Another way to flash system , i don't have A PC
Click to expand...
Click to collapse
I know it is too late, but you can enter in Advaced > Terminal and then run this command:
dd if=/sdcard/system.img of=/dev/block/bootdevice/by-name/system
If your mobile phone doesnt have by-name symlinks you will need to enter the correct partition.
Aex12 said:
I know it is too late, but you can enter in Advaced > Terminal and then run this command:
dd if=/sdcard/system.img of=/dev/block/bootdevice/by-name/system
If your mobile phone doesnt have by-name symlinks you will need to enter the correct partition.
Click to expand...
Click to collapse
hi aex, I have the same problem but I dont have the folder
/bootdevice/by-name............
can you help me?
it will not work.
try to make a folder and "mount -o loop file in it.
and it will be not mounted also if you specify file system type.
(if it work probably you can use the file)
so ,i don't know how fastboot write in partition or probably
in to file system.
however if you do a dd of your current system partition in a file , after will be correctly mounted , or rewrited correctly in the original partition if you need.
then probably you cannot use fastboot system.img directly in twrp shell (using dd)
this is my experience (e2303 sony / pexorom 3.0 twrp 3.1.1)
if you are searching a fast way to know system partition device block
cat /etc/fstab
and look for system
or just mount system in twrp , then in a terminal do a
df -h
and search for system
for e2303 was /dev/block/mmcblk0p30
(example)
twrp have busybox and light kernel.
so , is linux.
for better support try to ask
tonystark88
u need to use simg2img
(sparse file format compression)
system partition device name can be different on other phones.
done.
img can be write by twrp whitout pc/fastboot.
c'ya
giuseppe
just go to file manager and search for system partition, and on first part type your system.img location and 2 part type just system location
I did this Steps on my Huawei P8. Sim2Img reported a non sparse image, so i moved directly to the DD steps. But after writing the image to the partition, the /system Partition cannot get mountet...
What the hell iam doing wrong ????
I extracted the system.img from an update.app Firmware file.
Its the same Firmware file i flashed before with the dload method.
I want to install TWRP on my Phone with an faulty USB Port. So i have no PC / ADB. I Installed the Firmware via the official Dload Method from Huawai. Then i used this crappy Kingroot to get root and installed TWRP. Now i wanted to flash the stock system partition to get rid of Kingroot for Safetynet.
But why i cant just flash the systempartition ?
Or is there another way to gain root for 15 seconds without traces ?
chr2002 said:
I did this Steps on my Huawei P8. Sim2Img reported a non sparse image, so i moved directly to the DD steps. But after writing the image to the partition, the /system Partition cannot get mountet...
What the hell iam doing wrong ????
I extracted the system.img from an update.app Firmware file.
Its the same Firmware file i flashed before with the dload method.
I want to install TWRP on my Phone with an faulty USB Port. So i have no PC / ADB. I Installed the Firmware via the official Dload Method from Huawai. Then i used this crappy Kingroot to get root and installed TWRP. Now i wanted to flash the stock system partition to get rid of Kingroot for Safetynet.
But why i cant just flash the systempartition ?
Or is there another way to gain root for 15 seconds without traces ?
Click to expand...
Click to collapse
Why not just use the settings in Kingroot to remove root? Or convert from Kingroot to SuperSu then use SuperSu app settings to remove root?
You don't have to flash the stock system to remove root.
Sent from my LGL84VL using Tapatalk
Kingroots uninstall leaves traces in /system/xbin and Safetynet wont work. Why i did not try Supersu ? :-/
But i managed to flash the system.img without problems.
First i tryed an extracted system.img from the Huawei Firmware extractor and Sim2img reported an invalid sparse image. So i thought it must be a raw image.....And this was my mistake. It is a useless image for TWRP.
So i created a flashable zip (TWRP cant flash this, too and the /system partition is not mountable after flashing / installing this zip.
BUT, the system.img INSIDE this zip is a spase image, which sim2img can handle. It gave me a nice raw image which i just dd´d to /system and BINGO, my phone starts up normally
The Short Version :
- Create a FLASHABLE ZIP with the Huawei Firmware Extractor
- use SIM2IMG in TWRP Terminal to get a RAW Image.
- dd´it to the /system partition
System img
You use the restore in twrp to flash your system img, you just until the other boxes
Edit: Sorry wrong thread
Lenovo K5 Pro ROM img
After flashing img file (using TWRP 3.3.1) the phone (Lenovo k5 pro) starts in bootloader mode. Everyone can help?
Help u
Hi u can download a deodexed rom because ais doesn't support some stock roms for ex ch Samsung roms. then decompile it.then decompile it with rar or zarchiver or etc. Then install android image studio (ais) from google
Then open it and tap unpack/mount and select system.img or system.img.ext4 file in decompiled rom . After mounting, copy all files to a directory for ex emulated/0/system/system or another. Attention if you copy it in another directory, rename it as (system) now copy the boot.img from decompiled rom into emulated/0/system .then download this file
https://forum.xda-developers.com/an...oid-o-beta-redesigned-emoji-set-t3608280/amp/
Extract meta-inf file into emulated/0/system using winrar or zarchiver or etc. Now you need to have a system folder,boot.img file and a Meta-inf in diractory emulated/0/system. Now compress system,boot.img and meta-inf into one archive and after completing, turn of your device and boot it into twrp recovery and wipe data and cache without wipping internal storage then select install. Then tap select storage and select internal storage.then go to the file and select it and turn off zip singuature verification and install it after installing tis rom, install root zip file and wipe cache/dalvik art and then reboot your device. It may take between 5-25 minutes to boot. Enjoy your new rom
#issues
Sometimes your device maybe take bootloop so you need to install your stock boot.img file and after installing your root zip file choose wipe cache/dalvik art and then reboot your system.
#Alert
1.Don't install the recovery.img file which exists in the decompiled rom because it takes your device into recovery mod and not boot anymore and after you need to install the stock rom using PC
2.your device maybe take bootloop in this method so do it with your own risk
---------- Post added at 07:58 AM ---------- Previous post was at 07:53 AM ----------
ShmuelCohen said:
After flashing img file (using TWRP 3.3.1) the phone (Lenovo k5 pro) starts in bootloader mode. Everyone can help?
Click to expand...
Click to collapse
Reboot your device and install twrp official app and open it and select flash image from a directory and select your own twrp and reboot your device [root]
Connect your phone to a PC and install stock rom using ADB or another app which was made for your smartphone [no root]

Root Honor 8 Lite OREO

NOTE:I shall not be responsible for any damage cause to your phone by this procedure.
As OREO on Honor 8 Lite brings treble support so rooting it is an issue for everyone.
I am here to guide you how to root Honor 8 Lite.
Requirements:
1.Unlocked Bootloader
2.Oreo Updated
3.Current running firmware (mine PRA-LA1C185B366)
4.Huawei Update Extractor (Download Below)
5.Magisk Manager latest apk.
6.Internet Connection.
7.Fastboot installed.
Procedure:
1.Extract RAMDISK.img from your downloaded firmware (or you can dump it using TWRP).
2.Transfer extracted RAMDISK.img to your phone.
3.Now open installed Magisk Manager and click install.
4.Now choose patch boot image and select the extracted RAMDISK.img.
5.It will take 5 min to download zip file and patch RAMDISK.img.
6.Patched RAMDISK.img usually stored in "sdcard/Download/patched-boot.img" or magisk manager will also guide you where the patched boot image stored.
7.Transfer the patched-boot.img to your pc.
8.Now boot your phone in bootloader mode.
9.Flash the patched-boot.img using this command"fastboot flash ramdisk (path of patched-boot).img" without qoutes.
10.After successful flashing reboot your phone either by holding power button or by using fastboot command.
BOOM your phone is rooted now start playing with magisk modules.

[GUIDE] How to root Android Pie build (Temporarily Guide)

Since TWRP is unbootable under this build, you have to use patched boot trick to root this phone.
However, only Magisk 17.1 is usable on this build, Magisk 17.2 - 18.0 can't be installed properly.
So I made a custom update channel that fixed to Magisk 17.1 to assist me.
This guide requires unlocked bootloader - still, I won't introduce how to unlock it here, please Google for it.
Click to expand...
Click to collapse
Here's how to root:
1. Extract the D1C-0-6120-00CN-boot.img from my homebrew firmware written in previous guide, or extract the boot.img from the OTA package.
(Later versions will also provide the patched boot image)
2. Copy this boot.img to Download directory.
3. Install latest Magisk Manager from https://github.com/topjohnwu/Magisk/releases
Remember to allow all the permission after installed.
4. Choose "Left Hamburger Menu" - "Settings" - "Update Channel" - "Custom", and type following URL:
Code:
https://dwz.cn/5I3anBD4
5. Back to Magisk Manager main interface, refresh it and check if latest version changed to 17.1.
Tap "Install" - "Install" - "Patch Boot Image", "Left Hamburger Menu" - "Download" - the boot img you copied.
And wait for the patching procedure complete.
6. Copy patched_boot.img from the Download directory of internal storage to PC.
7. Reboot your phone to fastboot mode and execute following commands:
Code:
.\fastboot reboot-bootloader
.\fastboot boot D:\patched_boot.img
8. Open Magisk Manager, reinstall Magisk 17.1 directly.
9. Reboot your phone and all done.
Is this procedure familiar? Yes, it's the same method used on Nokia 7 Plus. But I wrote this guide to tell you few details that you need to notice.
Hope TWRP can be compiled for D1C-6120.
If you have already unlocked the bootloader then just flash the official TWRP for Nokia 6 and flash the Magisk v17.1 or 17.3 via TWRP normally. And TWRP 3.2.3.0 works well on Android P. I tested it and it works fine.
taicracker said:
If you have already unlocked the bootloader then just flash the official TWRP for Nokia 6 and flash the Magisk v17.1 or 17.3 via TWRP normally. And TWRP 3.2.3.0 works well on Android P. I tested it and it works fine.
Click to expand...
Click to collapse
OK, thanks for the info.
hikari_calyx said:
OK, thanks for the info.
Click to expand...
Click to collapse
I hope you can build TWRP for Android P variant of Chinese and it works on non-unlockbootloader. Like you used to do with Oreo? .Thanks
This did not work with TA-1021 while i have pi installed with twrp and patched boot with magisk 16.1 but it do not work not even root access just keep recovery unchanged(twrp).
It says deviceid locked ple if i patch boot with 17.1 what to do! google pay and banking apps dont work.
hikari_calyx said:
OK, thanks for the info.
Click to expand...
Click to collapse
Can we use official TWRP recovery (3.2.3 made for PLE)
On pie 612H CN - OF YOUR HOMEBREW
and also on 612H ww ??
Please tell
---------- Post added at 06:12 AM ---------- Previous post was at 06:05 AM ----------
taicracker said:
If you have already unlocked the bootloader then just flash the official TWRP for Nokia 6 and flash the Magisk v17.1 or 17.3 via TWRP normally. And TWRP 3.2.3.0 works well on Android P. I tested it and it works fine.
Click to expand...
Click to collapse
Can we install this TWRP recovery on Chinese firmware (or ww firmware of ta-1003)or it can be flashed only on PLE versions
hikari_calyx said:
OK, thanks for the info.
Click to expand...
Click to collapse
Can I install D1C-612H-WW over 612H-CN using OST ??
OST show that the image is broken
hikari_calyx said:
Here's how to root:
1. Extract the D1C-0-6120-00CN-boot.img from my homebrew firmware written in previous guide, or extract the boot.img from the OTA package.
(Later versions will also provide the patched boot image)
2. Copy this boot.img to Download directory.
3. Install latest Magisk Manager from https://github.com/topjohnwu/Magisk/releases
Remember to allow all the permission after installed.
4. Choose "Left Hamburger Menu" - "Settings" - "Update Channel" - "Custom", and type following URL:
Code:
https://dwz.cn/5I3anBD4
5. Back to Magisk Manager main interface, refresh it and check if latest version changed to 17.1.
Tap "Install" - "Install" - "Patch Boot Image", "Left Hamburger Menu" - "Download" - the boot img you copied.
And wait for the patching procedure complete.
6. Copy patched_boot.img from the Download directory of internal storage to PC.
7. Reboot your phone to fastboot mode and execute following commands:
Code:
.\fastboot reboot-bootloader
.\fastboot boot D:\patched_boot.img
8. Open Magisk Manager, reinstall Magisk 17.1 directly.
9. Reboot your phone and all done.
Is this procedure familiar? Yes, it's the same method used on Nokia 7 Plus. But I wrote this guide to tell you few details that you need to notice.
Hope TWRP can be compiled for D1C-6120.
Click to expand...
Click to collapse
On rebooting Android root gone????
dont work for me
edit: worsk now over ND1-612C-0-00WW , but for firm official for n5 (612h-0-00WW ) not works, ist patched the xploit for magisk 17 and up
hikari_calyx said:
Here's how to root:
1. Extract the D1C-0-6120-00CN-boot.img from my homebrew firmware.
9. Reboot your phone and all done.
Is this procedure familiar? Yes, it's the same method used on Nokia 7 Plus. But I wrote this guide to tell you few details that you need to notice.
Hope TWRP can be compiled for D1C-6120.
Click to expand...
Click to collapse
Please help I have working 1003 ww pi installed on Ta-1021 and initially rooted using Chinese twrp with magisk later I tried to install update of twrp recovery got crashed and could not enter recovery tried to flash with Qualcomm tools can enter into Edl phone detected but frimware files doesn't flash some errors. Now result is I can operate my phone magisk 16.1 installed but useless. Banking apps don't work. Factory reset don't work. *#*#874#*#* says file not found (may be because I don't have recovery). Ost la as usual don't work. Please help!
Please help me i am on oreo version .. and i have flashed twrp recovery on my nokia 6 (TA - 1021) ..
THE Problem is when i reboot to recovery it's not booting in twrp but it's booting on custome recovery ..
I need pc everytime , if i want to boot it on twrp .
I have to run command every time to boot in on twrp recovery ..
Is there any way to directly boot it on twrp recovery not in custom recovery ? Please help me
@hikari_calyx Does fastboot boot work for you on pie? For me, it does not. Almost shat my pants thinking my TWRP doesn't work but it does in fact work, just fastboot booting it does not work.
Finally got the official pie update on my TA-1033. (unlocked bootloader)
The standard versions of TWRP 3.2.3.0 / Magisk 17.3 / Magisk Manager 6.0.1 worked perfectly.
As above, "fastboot boot" doesn't work, but "fastboot flash" etc. does.
Happy days.
Not working for me please can you tell the procedure step by step as i tried your steps but didn't happen anything please
---------- Post added at 06:29 PM ---------- Previous post was at 06:26 PM ----------
taicracker said:
If you have already unlocked the bootloader then just flash the official TWRP for Nokia 6 and flash the Magisk v17.1 or 17.3 via TWRP normally. And TWRP 3.2.3.0 works well on Android P. I tested it and it works fine.
Click to expand...
Click to collapse
Not working i have unlocked bootloader but i tried to flash twrp and it's not booting on it any other solution please let me know .
Can you help me please my device is showing me this on my recovery , what's an issue please reply as soon as possible i can't even apply update through sd card or adb it's not detecting everytime it entered to this menu .. please help me
hikari_calyx said:
Here's how to root:
1. Extract the D1C-0-6120-00CN-boot.img from my homebrew firmware written in previous guide, or extract the boot.img from the OTA package.
(Later versions will also provide the patched boot image)
2. Copy this boot.img to Download directory.
3. Install latest Magisk Manager from https://github.com/topjohnwu/Magisk/releases
Remember to allow all the permission after installed.
4. Choose "Left Hamburger Menu" - "Settings" - "Update Channel" - "Custom", and type following URL:
Code:
https://dwz.cn/5I3anBD4
5. Back to Magisk Manager main interface, refresh it and check if latest version changed to 17.1.
Tap "Install" - "Install" - "Patch Boot Image", "Left Hamburger Menu" - "Download" - the boot img you copied.
And wait for the patching procedure complete.
6. Copy patched_boot.img from the Download directory of internal storage to PC.
7. Reboot your phone to fastboot mode and execute following commands:
Code:
.\fastboot reboot-bootloader
.\fastboot boot D:\patched_boot.img
8. Open Magisk Manager, reinstall Magisk 17.1 directly.
9. Reboot your phone and all done.
Is this procedure familiar? Yes, it's the same method used on Nokia 7 Plus. But I wrote this guide to tell you few details that you need to notice.
Hope TWRP can be compiled for D1C-6120.
Click to expand...
Click to collapse
You gave wrong code for booting patched boot.img
It should be as
FASTBOOT FLASH BOOT PATCED_BOOT.IMG
It will permanently root the android pie
You gave the FASTBOOT code only for booting
vineet09i said:
Here's how to root:
1. Extract the D1C-0-6120-00CN-boot.img from my homebrew firmware written in previous guide, or extract the boot.img from the OTA package.
(Later versions will also provide the patched boot image)
2. Copy this boot.img to Download directory.
3. Install latest Magisk Manager from https://github.com/topjohnwu/Magisk/releases
Remember to allow all the permission after installed.
4. Choose "Left Hamburger Menu" - "Settings" - "Update Channel" - "Custom", and type following URL:
5. Back to Magisk Manager main interface, refresh it and check if latest version changed to 17.1.
Tap "Install" - "Install" - "Patch Boot Image", "Left Hamburger Menu" - "Download" - the boot img you copied.
And wait for the patching procedure complete.
6. Copy patched_boot.img from the Download directory of internal storage to PC.
7. Reboot your phone to fastboot mode and execute following commands:
You gave wrong code for booting patched boot.img
It should be as
FASTBOOT FLASH BOOT PATCED_BOOT.IMG
It will permanently root the android pie
You gave the FASTBOOT code only for booting
Click to expand...
Click to collapse
Hey can i use patched boot image on my official update of pie or which version is able to use of magisk?
Emmykay223 said:
Hey can i use patched boot image on my official update of pie or which version is able to use of magisk?
Click to expand...
Click to collapse
You can use the same procedure as hilarious calyx have said in the post
But the FASTBOOT command should be as
FASTBOOT flash boot patched_boot.img
It will permanently root your android
Magisk 17.1 is working
Or you can also flash official twrp available at twrp website and from there you can directly flash magisk 17.1 zip
vineet09i said:
You can use the same procedure as hilarious calyx have said in the post
But the FASTBOOT command should be as
FASTBOOT flash boot patched_boot.img
It will permanently root your android
Magisk 17.1 is working
Or you can also flash official twrp available at twrp website and from there you can directly flash magisk 17.1 zip
Click to expand...
Click to collapse
Yes but twrp is not booting on my pie build because it is showing "failed to find device for partition system" and i am unable to apply update through sd card or through adb i don't know why so i am thinking to follow this steps hope it will work.
vineet09i said:
You can use the same procedure as hilarious calyx have said in the post
But the FASTBOOT command should be as
FASTBOOT flash boot patched_boot.img
It will permanently root your android
Magisk 17.1 is working
Or you can also flash official twrp available at twrp website and from there you can directly flash magisk 17.1 zip
Click to expand...
Click to collapse
Why any module is not installing by magisk it's showing me unable to extract, i followed each and every steps as mentioned above and rooted my Nokia 6 again but it's not installing any module what's the reason behind it?

【Reproduced】XZ2/XZ2P/XZ2C/XZ3 TWRP for Android 10

Reprinted to China xpeira Forum: GFan Author: machao44.Just reproduced, irresponsible
Original Link:
http://bbs.gfan.com/android-9634387-1-1.html
http://bbs.gfan.com/android-9634397-1-1.html
http://bbs.gfan.com/android-9634405-1-1.html
Bugs:Unable to read external SD card
Flash steps:
1.Flash firmware, do not start the device
2.Open the adb folder
xz2:
fastboot flash boot twrp-xz2.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
xz2p:
fastboot flash boot twrp-xz2p.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
xz2c:
fastboot flash boot twrp-xz2c.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
xz3:
fastboot flash boot twrp-xz3.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
3.Press and hold the volume down and power buttons to enter twrp, connect to the phone and enable MTP mode.
4.Drag boot_X-FLASH-ALL-B6B5.sin in the firmware to UnSIN.exe to decrypt it, and then rename it to kernel.img.
5.Put kernel.img in the startup folder, and then compress it to boot.zip (please note that the correct method is to select the META-INF folder and kernel.img for compression)
6.Copy boot.zip, twrp-installer-xz3-3.3.x.zip, Magisk-v20.3.zip, fstab.zip to the phone storage, and then refresh. (Xz3 only needs to copy boot.zip, twrp-installer-xz3-3.3.x.zip, Magisk-v20.3.zip)
7.Carry out
Download Link:https://drive.google.com/drive/folders/1e2sWOLhhiYmDyd-aN7sx1iLplPtIAVNf
It does not work for me, the first time I get to the home screen, after 5 minutes it restarted and it does not happen from the Xperia animation, I used XZ2 Android 10. Your input is greatly appreciated
anjelz2012 said:
It does not work for me, the first time I get to the home screen, after 5 minutes it restarted and it does not happen from the Xperia animation, I used XZ2 Android 10. Your input is greatly appreciated
Click to expand...
Click to collapse
Maybe you should try again. Step 6 is that I did n’t write clearly. The correct flashing steps are: Flashing in order
1. Flashing boot.zip 2. Flashing twrp-installer-xz3-3.3.x.zip 3. Flashing Magisk-v20.3.zip 4. Flashing fstab.zip
---------- Post added at 12:03 ---------- Previous post was at 11:56 ----------
L1e" said:
Reprinted to China xpeira Forum: GFan Author: machao44.Just reproduced, irresponsible
Original Link:
http://bbs.gfan.com/android-9634387-1-1.html
http://bbs.gfan.com/android-9634397-1-1.html
http://bbs.gfan.com/android-9634405-1-1.html
Bugs:Unable to read external SD card
Flash steps:
1.Flash firmware, do not start the device
2.Open the adb folder
xz2:
xz2p:
xz2c:
xz3:
3.Press and hold the volume down and power buttons to enter twrp, connect to the phone and enable MTP mode.
4.Drag boot_X-FLASH-ALL-B6B5.sin in the firmware to UnSIN.exe to decrypt it, and then rename it to kernel.img.
5.Put kernel.img in the startup folder, and then compress it to boot.zip (please note that the correct method is to select the META-INF folder and kernel.img for compression)
6.Copy boot.zip, twrp-installer-xz3-3.3.x.zip, Magisk-v20.3.zip, fstab.zip to the phone storage, and then refresh. (Xz3 only needs to copy boot.zip, twrp-installer-xz3-3.3.x.zip, Magisk-v20.3.zip)
7.Carry out
Click to expand...
Click to collapse
The correct way to step 6 is to refresh boot.zip, twrp-installer-xz3-3.3.x.zip, Magisk-v20.3.zip, fstab.zip in turn
I followed him in that order and he always got the same result
anjelz2012 said:
I followed him in that order and he always got the same result
Click to expand...
Click to collapse
Have you tried flash the firmware?Because after flashing the firmware according to the original text, do not start the phone
L1e" said:
Have you tried flash the firmware?Because after flashing the firmware according to the original text, do not start the phone
Click to expand...
Click to collapse
The process I have followed is as follows:
1.- Flash firmware 52.1.A.0.532 (android 10) and I don't start it
2.- I connect in fastboot mode to the pc and execute:
fastboot flash boot twrp-xz2.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
3.- I enter Twrp mode
4.- Prepare the boot.zip file (META-INF + kernel.img using 7zip)
5.- Copy: boot.zip, twrp-installer-xz3-3.3.x.zip, Magisk-v20.3.zip, fstab.zip in the phone storage
6.- Flashing in the following order:
*boot.zip
twrp-installer-xz3-3.3.x.zip
Magisk-V20
fstab.zip
7.- I restart my mobile and it doesn't work for me.
When it shows the lock screen after rebooting, it turns off and does not pass the Xperia animation
:cyclops::cyclops:
anjelz2012 said:
The process I have followed is as follows:
1.- Flash firmware 52.1.A.0.532 (android 10) and I don't start it
2.- I connect in fastboot mode to the pc and execute:
fastboot flash boot twrp-xz2.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
3.- I enter Twrp mode
4.- Prepare the boot.zip file (META-INF + kernel.img using 7zip)
5.- Copy: boot.zip, twrp-installer-xz3-3.3.x.zip, Magisk-v20.3.zip, fstab.zip in the phone storage
6.- Flashing in the following order:
*boot.zip
twrp-installer-xz3-3.3.x.zip
Magisk-V20
fstab.zip
7.- I restart my mobile and it doesn't work for me.
When it shows the lock screen after rebooting, it turns off and does not pass the Xperia animation
:cyclops::cyclops:
Click to expand...
Click to collapse
Sorry, it took a long time to reply to you. Through trial and error, I found no problems. I don't know what went wrong.
anjelz2012 said:
The process I have followed is as follows:
1.- Flash firmware 52.1.A.0.532 (android 10) and I don't start it
2.- I connect in fastboot mode to the pc and execute:
fastboot flash boot twrp-xz2.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
3.- I enter Twrp mode
4.- Prepare the boot.zip file (META-INF + kernel.img using 7zip)
5.- Copy: boot.zip, twrp-installer-xz3-3.3.x.zip, Magisk-v20.3.zip, fstab.zip in the phone storage
6.- Flashing in the following order:
*boot.zip
twrp-installer-xz3-3.3.x.zip
Magisk-V20
fstab.zip
7.- I restart my mobile and it doesn't work for me.
When it shows the lock screen after rebooting, it turns off and does not pass the Xperia animation
:cyclops::cyclops:
Click to expand...
Click to collapse
I think maybe your step 4 was wrong,
put Kernel.img into boot folder,then compression the folder,you will get boot.zip ,flash it.
Did anyone try this? Got success?
Tia
serajr said:
Did anyone try this? Got success?
Tia
Click to expand...
Click to collapse
I tried again and yes, this time it worked! Although it is somewhat unstable, because it causes forced reboots and forced encryption does not work!
anjelz2012 said:
I tried again and yes, this time it worked! Although it is somewhat unstable, because it causes forced reboots and forced encryption does not work!
Click to expand...
Click to collapse
Thanks bro! I didn't even get the 3rd step to work (entering twrp with combo keys after flashing it).
I'll try it once again tomorrow, after a fresh firmware installation! Maybe that's why things didn't work here.
I've just installed it with latest firmware, it works great
An advice, keep TWRP in chinese or it doesn't flash anything and get stucked
I was stuck on booting the first TWRP in the adb folder, with the screen screaming with a notification of a corrupt device & it will reboot.
I am thus assuming this TWRP pack is for the stock rom, not a custom one.
Works almost perfectly, thanks for sharing
---------- Post added at 12:05 AM ---------- Previous post was at 12:04 AM ----------
adwinp said:
I was stuck on booting the first TWRP in the adb folder, with the screen screaming with a notification of a corrupt device & it will reboot.
I am thus assuming this TWRP pack is for the stock rom, not a custom one.
Click to expand...
Click to collapse
Step One: Flash Firmware....
Beetle84 said:
Works almost perfectly, thanks for sharing
Step One: Flash Firmware....
Click to expand...
Click to collapse
I read that - it should probably be specified that only stock firmware is supported (in contrast to custom).
adwinp said:
I read that - it should probably be specified that only stock firmware is supported (in contrast to custom).
Click to expand...
Click to collapse
Generally, when someone says firmware, they mean stock. Custom roms are usually not called firmware
adwinp said:
I was stuck on booting the first TWRP in the adb folder, with the screen screaming with a notification of a corrupt device & it will reboot.
I am thus assuming this TWRP pack is for the stock rom, not a custom one.
Click to expand...
Click to collapse
I made progress
My twrp build for custom 10.0 works now.
Decryption is left in my to-do list, before I move to adapt changes for a stock twrp.
MartinX3 said:
[...] before I move to adapt changes for a stock twrp.
Click to expand...
Click to collapse
Just another amazing news from you... THANK YOU SO MUCH! Looking forward to it!!
The one provided from OP does work, I gotta say, but it makes use of unencrypted /data partition hack (fstab.zip), which is not - imho - a good choice.
serajr said:
Just another amazing news from you... THANK YOU SO MUCH! Looking forward to it!!
The one provided from OP does work, I gotta say, but it makes use of unencrypted /data partition hack (fstab.zip), which is not - imho - a good choice.
Click to expand...
Click to collapse
Thank you
Yeah, this TWRP is the same chinese TWRP like for stock 9.0 in the past

Question can't install magisk

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

Categories

Resources