For some bizarre reason, Wileyfox has been rejecting sending me latest fastboot and recovery images... Until today.
I really hope and expect more future collaboration between their technical support assets and us, starting by myself, to provide as much info and solutions as possible to you all, the community.
For those that didn't receive the update yet, I've requested the links to the Wileyfox nougat support team, so here you can download the incremental, recovery and fastboot images of the latest upgrade TOS163B.
RECOVERY IMAGE (2GB) (works neat in TWRP as well as in Cyanogen Recovery / does not necessarily require open bootloader) - MD5
FASTBOOT IMAGE (2GB) (requires open bootloader) - MD5
INCREMENTAL UPDATE THREAD (from TOS118C to TOS163B / from aa4d5d86bc to 8eec3af77b)
They have also attached some documentation I left in the attachments, in case someone is interested or needs detailed instructions on how-to upgrade their devices.
Many thanks Ramvir for sending everything in!
Thank you, just updated my Swift 2X and flashed the recovery image in TWRP, then flashed magisk and it seems to be working well so far!
Yeah thanks linuxct for your work and contribution.
Because there is (not yet) a debloater for this version, is it than reguired to flash magisk or is superSU enough??
I think you can still use the most recent debloater, it worked for me. Magisk is still needed. I'm still on Magisk v12 and SuperSU 2.79 because I could not get other combinations to work.
Hello. cloud.mail.ru/public/JEWW/bMe4rXfbg/Wileyfox%20Swift%202%20series/Fastboot/
Cloud with official roms for marmite
Related
Hello,
I'm the proud owner of a KIW-L21 (Europe Honor 5x), but with all the bloatware and the lack of privacy in the default rom, I'm a little sad.
To fix this, as you could have guessed I'll need to root the phone (install AFwall + Xposed + XPrivacy, right?).
I plan to unlock the smartphone as soon as emui . huawei . com starts to work for me.
Anyway, I'd be happy to test custom recoveries, kernels/roms if you want help from a L21 user.
My first stop would be custom recovery, so who should I work with in order to bring TWRP for the KIW-L21 (and not the L24) to a working state? or do you think the L24 recovery would be working for the L21?
Thank you in advance.
I've installed twrp l24 and there was a fictional mouse in the middle of a screen, hard to explain. I was wondering if you could flash twrp 3.0 directly without installing l24 version and see what happens? https://twrp.me/devices/huaweihonor5x.html
For that you would need to flash supersu zip through the bootloader (if you prefer app version of twrp) or install .img file from bootloader
A lot of people said that xposed doesn't work; this was for l24 version, don't know if it will work on l21.
We have some threads that may interest you -
http://forum.xda-developers.com/honor-5x/development
Thanks for the link.
For information, the emui huawei com unlock procedure described here (http://forum.xda-developers.com/honor-5x/development/root-kiw-l24-usa-kiwi-t3305190 steps 1 through 7) also works for the KIW-L21.
Next step is the recovery.
For information, flashing twrp following the procedure described here (http://forum.xda-developers.com/honor-5x/development/root-kiw-l24-usa-kiwi-t3305190 steps 8 through 11) also works for the KIW-L21.
Please expect a lots of glitches with the interface, but with a lot of patience, you can flash your zips (for example SuperSU described in the steps 11 to 13).
Next step is the privacy tools' installation: Installation of AFWall+ + AdAway + Xposed framework
I just got my Moto G4 Plus and want to root it. Does somebody have a good guide for rooting it?
I found this guide on youtube, can I just follow this?: https://www.youtube.com/watch?v=g3bhXe3msxU&t=3s
What stock OS are you running on your device, Marshmallow or Nougat?
echo92 said:
What stock OS are you running on your device, Marshmallow or Nougat?
Click to expand...
Click to collapse
I just updated to Android 6.0.1 Marshmallow
If you're on Marshmallow (6.0.1), then the guide you linked should work, you may wish to keep the stock kernel (and not flash ElementalX). Also, instead of phh superuser, you could choose to flash SuperSU or magisk.
Here's a guide for rooting on Marshmallow 6.0.1 as well https://forum.xda-developers.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772 You may wish to use a newer build of SuperSU than mentioned in the guide - the latest build currently is 2.82 SR1.
echo92 said:
If you're on Marshmallow (6.0.1), then the guide you linked should work, you may wish to keep the stock kernel (and not flash ElementalX). Also, instead of phh superuser, you could choose to flash SuperSU or magisk.
Here's a guide for rooting on Marshmallow 6.0.1 as well https://forum.xda-developers.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772 You may wish to use a newer build of SuperSU than mentioned in the guide - the latest build currently is 2.82 SR1.
Click to expand...
Click to collapse
I found a video that showed how to unlock bootloader, and uses SuperSU when rooting. Can I use this guide insted, or is it to old you think?: https://www.youtube.com/watch?v=dK2uacpjGwc&t=119s
Thank you so much for all the help btw
skismas said:
I found a video that showed how to unlock bootloader, and uses SuperSU when rooting. Can I use this guide insted, or is it to old you think?: https://www.youtube.com/watch?v=dK2uacpjGwc&t=119s
Thank you so much for all the help btw
Click to expand...
Click to collapse
Looking through that video, I think it should work for 6.0.1 - as an aside for anyone reading this, the root procedure for Nougat is different. Though the resources linked in the video may work (I have not tested them), you may, as I mentioned above, wish to flash newer versions of TWRP and SuperSU than that linked in the video:
TWRP - (official): https://dl.twrp.me/athene/
I personally use shreps' TWRP: https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337
SuperSU v2.82: https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703 Ideally, you'll want to use v2.79 SR3 or newer as they're systemless root.
EDIT: this guide linked to in the video has a nice description of some of the steps you'll need: https://forum.xda-developers.com/moto-g4-plus/how-to/guide-newbie-resource-thread-t3386584
One thing I'd add to those guides is before you flash SuperSU, make a backup of all of the partitions in TWRP (on the TWRP main menu, you'll see 'Backup'). If SuperSU fails to root or causes instabilty, you'll have a backup to fall back to.
Additionally, when flashing TWRP, you'll see the 'Image not signed or corrupted' warning, that's normal. As long as [OKAY] comes up in fastboot after flashing and you reboot to recovery afterwards (so TWRP is set as your recovery), then TWRP should stick.
You may also receive OTA messages - do not accept these whilst rooted and with TWRP. if you wish to turn them off, have a look here: https://forum.xda-developers.com/showpost.php?p=72373828&postcount=12
Don't FLASH TWRP, just BOOT it up, do whatever you need to do and... keep your stock bootloader. The TWRP is useful mostly for CM/Lineage ROM's, for stock it's just a headache waiting to happen.
echo92 said:
Looking through that video, I think it should work for 6.0.1 - as an aside for anyone reading this, the root procedure for Nougat is different. Though the resources linked in the video may work (I have not tested them), you may, as I mentioned above, wish to flash newer versions of TWRP and SuperSU than that linked in the video:
TWRP - (official): https://dl.twrp.me/athene/
I personally use shreps' TWRP: https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337
SuperSU v2.82: https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703 Ideally, you'll want to use v2.79 SR3 or newer as they're systemless root.
EDIT: this guide linked to in the video has a nice description of some of the steps you'll need: https://forum.xda-developers.com/moto-g4-plus/how-to/guide-newbie-resource-thread-t3386584
One thing I'd add to those guides is before you flash SuperSU, make a backup of all of the partitions in TWRP (on the TWRP main menu, you'll see 'Backup'). If SuperSU fails to root or causes instabilty, you'll have a backup to fall back to.
Additionally, when flashing TWRP, you'll see the 'Image not signed or corrupted' warning, that's normal. As long as [OKAY] comes up in fastboot after flashing and you reboot to recovery afterwards (so TWRP is set as your recovery), then TWRP should stick.
You may also receive OTA messages - do not accept these whilst rooted and with TWRP. if you wish to turn them off, have a look here: https://forum.xda-developers.com/showpost.php?p=72373828&postcount=12
Click to expand...
Click to collapse
I managed to root my phone without bricking it! I think......
SuperSU was not on the phone when I rebooted the phone like in the video. I had to download it through play store. But since it says its rooted on root checker, and I could grant it permission, im pretty sure I done it right.
Thanks for the help I really appreciate it
I want to root my phone due to its huge benefits but also at the same time I want to keep my OTAs
Is it possible even if I will install them manually (but the data remains with no wipe) ?
And if so, how can I do this and whats the best way?
Thanks in advance and sorry if the language was bad <3
Tsunaimy said:
I want to root my phone due to its huge benefits but also at the same time I want to keep my OTAs
Is it possible even if I will install them manually (but the data remains with no wipe) ?
And if so, how can I do this and whats the best way?
Thanks in advance and sorry if the language was bad <3
Click to expand...
Click to collapse
Yes it's possible with a little workaround, to temporarily switch to stock Recovery (from TWRP, if you had it installed) and to stock Boot (from the one patched by Magisk) during the OTA upgrade - OTA will fail if it finds not the stock images of Recovery and Boot
After the upgrade you just flash the new Boot patched by Magisk (and flash TWRP if you will)
Or you flash TWRP and flash Magisk from TWRP
Below is a post how I recently upgraded from QFJEUXM 12.0.2 to 12.0.3. Btw, I downloaded zip and initiated OTA manually because I didn't want to wait more days to be pushed for OTA, but that's just a small detail not important for the way how to do it:
https://forum.xda-developers.com/showpost.php?p=83791185&postcount=93
Ofc, all my data, apps, settings, and Magisk modules were preserved
Generally, in the Redmi K20/Mi 9T Guides section on XDA you can find (at least two) threads about how-to root, i.e. install Magisk
Those threads describe the way to install Magisk by installing Magisk Manager, patching the Boot image, then flashing it from Fastboot (I prefer that way).
In that case TWRP is not needed (but it can be also installled)
Threads and guides are maybe old (since MIUI 11) but it doesn't matter, it's always the same method (essentially the same as in my post I gave you the link above, its part about returning back to Magisk after the OTA upgrade)
If you follow those guides you must pay attention that you patch the boot.img for exactly that (new) stock MIUI you do have and that you now use new Magisk (not some old versions as in the guides)
Alternatively, you flash TWRP by Fastboot, then flash Magisk zip from TWRP and then you install Magisk Manager
All those methods are described in other threads and posts.
Anyway, you must first unlock the Bootloader, again there is thread with a guide, or just google for how to unlock Bootloader on Xiaomi
Btw, some custom TWRP versions and Orange Fox do have Advanced options for upgrading MIUI and to keep Magisk, but when I did it that way for upgrading from QFJEUXM 11.0.5 to 12.0.2, it made me Factory reset and I lost all my files on Internal memory (it was generally an issue for the others who upgraded from MIUI 11 to MIUI 12 by flashing OTA through custom recovery)
Hence now for upgrading to 12.0.3 I didn't want to risk and did it as above
zgfg said:
Yes it's possible with a little workaround, to temporarily switch to stock Recovery (from TWRP, if you had it installed) and to stock Boot (from the one patched by Magisk) during the OTA upgrade - OTA will fail if it finds not the stock images of Recovery and Boot
After the upgrade you just flash the new Boot patched by Magisk (and flash TWRP if you will)
Or you flash TWRP and flash Magisk from TWRP
Below is a post how I recently upgraded from QFJEUXM 12.0.2 to 12.0.3. Btw, I downloaded zip and initiated OTA manually because I didn't want to wait more days to be pushed for OTA, but that's just a small detail not important for the way how to do it:
https://forum.xda-developers.com/showpost.php?p=83791185&postcount=93
Ofc, all my data, apps, settings, and Magisk modules were preserved
Generally, in the Redmi K20/Mi 9T Guides section on XDA you can find (at least two) threads about how-to root, i.e. install Magisk
Those threads describe the way to install Magisk by installing Magisk Manager, patching the Boot image, then flashing it from Fastboot (I prefer that way).
In that case TWRP is not needed (but it can be also installled)
Threads and guides are maybe old (since MIUI 11) but it doesn't matter, it's always the same method (essentially the same as in my post I gave you the link above, its part about returning back to Magisk after the OTA upgrade)
If you follow those guides you must pay attention that you patch the boot.img for exactly that (new) stock MIUI you do have and that you now use new Magisk (not some old versions as in the guides)
Alternatively, you flash TWRP by Fastboot, then flash Magisk zip from TWRP and then you install Magisk Manager
All those methods are described in other threads and posts.
Anyway, you must first unlock the Bootloader, again there is thread with a guide, or just google for how to unlock Bootloader on Xiaomi
Btw, some custom TWRP versions and Orange Fox do have Advanced options for upgrading MIUI and to keep Magisk, but when I did it that way for upgrading from QFJEUXM 11.0.5 to 12.0.2, it made me Factory reset and I lost all my files on Internal memory (it was generally an issue for the others who upgraded from MIUI 11 to MIUI 12 by flashing OTA through custom recovery)
Hence now for upgrading to 12.0.3 I didn't want to risk and did it as above
Click to expand...
Click to collapse
I really appreciate your reply but I kinda don't know much info to understand most of what u said
My last time with root was about 3 years ago with king root on Mi A1 and I didn't care about updates then
so it's my very first time with magisk and TWRP and that stuff
Could u tell me what is the best method of u mentioned to keep my files and everything with no delete and also makes me able to upgrade Official ROM with no deletes
After this i'll start digging to learn but I want to know what should I dig for
Thanks bro
Tsunaimy said:
I really appreciate your reply but I kinda don't know much info to understand most of what u said
My last time with root was about 3 years ago with king root on Mi A1 and I didn't care about updates then
so it's my very first time with magisk and TWRP and that stuff
Could u tell me what is the best method of u mentioned to keep my files and everything with no delete and also makes me able to upgrade Official ROM with no deletes
After this i'll start digging to learn but I want to know what should I dig for
Thanks bro
Click to expand...
Click to collapse
Unlocking Bootloader usually takes to wait 7 days=168 hours, hence you have enough time to read?
Unlocking Bootloader:
https://c.mi.com/thread-1857937-1-1.html
Unlocking Bootloader: and Installing TWRP, OP post #1:
https://forum.xda-developers.com/mi-9t/how-to/guide-unlock-bootloader-flash-xiaomi-eu-t3952443
- for step 6, installing TWRP, use TWRP I'm giving you below
- instead of 7, execute this command:
>> fastboot oem reboot-recovery
- step 7, don't Format Data (unless you really go to install custom ROM, otherwise you don't need to)
- stop here for installing TWRP
Suggesting you to use this TWRP, 3.4.0.2 from OP post #1:
https://forum.xda-developers.com/mi-9t/how-to/recovery-unofficial-twrp-3-4-0-1-t4135159
- every time you boot to TWRP, you must type in your Android screen unlock pin, TWRP needs to be able to read/write to Data and Internal memory
Learn about using ADB and Fastboot:
https://www.makeuseof.com/tag/use-adb-fastboot-android/
- you can't do things with ADB that require root, but you can read
- similarly, fastboot commands mostly require unlocked Bootloader, but you can read
- google yourself
About installing Magisk, read in these threads:
https://forum.xda-developers.com/mi-9t/how-to/guide-easiest-to-root-twrp-t4000209
https://forum.xda-developers.com/mi-9t/how-to/root-k20-indian-rom-v10-3-6-0-twrp-t3958566
- if you have time, go through the whole threads, you will see variations
- don't worry if talking about MIUI 11, same applies for MIUI 12, you will just need to download your MIUI 12 recovery/zip firmware, will give you link below
- I'll give you below the link for the latest Magisk
MIUI firmwares, download, etc:
https://androidfilebox.com/tips/how-to-install-miui-recovery-rom/
https://androidfilebox.com/tips/how-to-install-miui-fastboot-rom/
https://xiaomiflashtool.com/tutorial/use-xiaomi-flash-tool
https://xiaomifirmwareupdater.com/miui/davinci/
https://codeexercise.com/xiaomi-all-android-mobile-secret-code-list/amp/
Various methods to extract stock Recovery, Boot, Persist and Persistbak partitions:
https://forum.xda-developers.com/mi-9t/how-to/root-k20-indian-rom-v10-3-6-0-twrp-t3958566
Magisk documentation and download:
https://github.com/topjohnwu/Magisk/blob/master/README.MD
- read the docs
- I would suggest you to use Canary (don't worry, Stable is far behind), hence you will only need to download Magisk Manager Canary (then follow XDA guides I gave you above)
zgfg said:
Unlocking Bootloader usually takes to wait 7 days=168 hours, hence you have enough time to read
Unlocking Bootloader:
https://c.mi.com/thread-1857937-1-1.html
Unlocking Bootloader: and Installing TWRP, OP post #1:
https://forum.xda-developers.com/mi-9t/how-to/guide-unlock-bootloader-flash-xiaomi-eu-t3952443
- for step 6, installing TWRP, use TWRP I'm giving you below
- instead of 7, execute this command:
>> fastboot oem reboot-recovery
- step 7, don't Format Data (unless you really go to install custom ROM, otherwise you don't need to)
- stop here for installing TWRP
Suggesting you to use this TWRP, 3.4.0.2 from OP post #1:
https://forum.xda-developers.com/mi-9t/how-to/recovery-unofficial-twrp-3-4-0-1-t4135159
- every time you boot to TWRP, you must type in your Android screen unlock pin, TWRP needs to be able to read/write to Data and Internal memory
Learn about using ADB and Fastboot:
https://www.makeuseof.com/tag/use-adb-fastboot-android/
- you can't do things with ADB that require root, but you can read
- similarly, fastboot commands mostly require unlocked Bootloader, but you can read
- google yourself
About installing Magisk, read in these threads:
https://forum.xda-developers.com/mi-9t/how-to/guide-easiest-to-root-twrp-t4000209
https://forum.xda-developers.com/mi-9t/how-to/root-k20-indian-rom-v10-3-6-0-twrp-t3958566
- if you have time, go through the whole threads, you will see variations
- don't worry if talking about MIUI 11, same applies for MIUI 12, you will just need to download your MIUI 12 recovery/zip firmware, will give you link below
- I'll give you below the link for the latest Magisk
MIUI firmwares, download, etc:
https://androidfilebox.com/tips/how-to-install-miui-recovery-rom/
https://androidfilebox.com/tips/how-to-install-miui-fastboot-rom/
https://xiaomiflashtool.com/tutorial/use-xiaomi-flash-tool
https://xiaomifirmwareupdater.com/miui/davinci/
https://codeexercise.com/xiaomi-all-android-mobile-secret-code-list/amp/
Various methods to extract stock Recovery, Boot, Persist and Persistbak partitions:
https://forum.xda-developers.com/mi-9t/how-to/root-k20-indian-rom-v10-3-6-0-twrp-t3958566
Magisk documentation and download:
https://github.com/topjohnwu/Magisk/blob/master/README.MD
- read the docs
- I would suggest you to use Canary (don't worry, Stable is far behind), hence you will only need to download Magisk Manager Canary (then follow XDA guides I gave you above)
Click to expand...
Click to collapse
bro I can`t really thank u enough for the effort
as I got it:
1- Unlock bootloader
2- Install TWRP (the version u provided)
3- Install Magisk (last link u provided) right?
Is there any step of those that is risky or unsafe that may brick the phone ?
PS: On mi unlock application it says all phone data will be erased !
what should I do ?
By unlocking Xiaomi phone you won't lose anything but previous user data stored in phone, unlike ASUS phone losts OTA permanentry.
So make a backup, also I recommend you first picking your secondaly phone, not your daily using one.
Tsunaimy said:
bro I can`t really thank u enough for the effort
as I got it:
1- Unlock bootloader
2- Install TWRP (the version u provided)
3- Install Magisk (last link u provided) right?
Is there any step of those that is risky or unsafe that may brick the phone ?
PS: On mi unlock application it says all phone data will be erased !
what should I do ?
Click to expand...
Click to collapse
As described, TWRP is optional, not needed for Magisk/root but it would be useful to have, so yes, install TWRP
Instructions for unlocking Bootloader say to do Backup. Copy photos and files from Internal memory to PC.
Export contacts to CVS file and also copy to PC.
Backup to Google your Google accounts, contacts, WhatsApp, etc.
Use Settings, Additional settings, Backup, and cooy to PC.
You can also use Settings, MIUI account to backup things
Installations of Magisk and TWRP will not erase data. Generally, they are not risky unless you make really stupid mistake like flashing TWRP img file to System partition instead of to Recovery partition and so - that's why you have instructions how to use Fastboot command to flash TWRP
It's more risky if you go to use e.g. MiFlash (you don't need for TWRP and Magisk), then people can screw up things and need authorized EDL support
Ramdisk from Huawei official firmware is required in order to patch Magisk and acquire root privelages in Openkirin LineageOS builds. Can't apply patches to rom from TWRP because TWRP doesn't support custom rom decryption in this case.
Since other people may be running into a similar issue I figured I would write down my process and share it for the reference of others. I do not plan to support this thread, I just wanted to share what I did that worked for me to remove some of the legwork for research.
Disclaimer:
This isn't, by any means, a recommended method to achieve this end.
Essentially, I ran into the predicament that Huawei and alternative sneaky Russian sites for hosting the firmware files for Huawei Devices are down as of writing this.
Namely:
Online firmware database ⋆ TEAM MT Developers
< PREVIOUS FIND MODEL NEXT > Дата изменения Полное название Файлы обновления Размер Тип G g v f 2021.11.09 MED-LGRP2-OVS 10.1.0.195 filelist 0 OTA 1458 104 519745 3 2021.11.08 patch01 filelist 0 OTA 1458 104 525603 1 2021.11.08 TAS-LGRP1-CHN 11.0.0.170 filelist 0 OTA 1458 104 525098 1 2021.11.08...
pro-teammt.ru
So I could no longer use the site to download the official firmware for my Honor 7X and extract the ramdisk from it in order to patch Magisk to that ramdisk image.
Well, against the wishes of the openkirin project, I installed a modified version of TWRP customer recovery in order to manually dump the ramdisk image already present inside of the Huawei (which, in my mind, should have been the same one from the OEM that would have been extracted from an official Huawei update). The TWRP recovery version that I used came from the P10 Lite TWRP test build 0.5 from the thread I listed below. Hacky as all hell, but it worked for what I needed.
To get the ramdisk you need to go into TWRP and do backup --> ramdisk. It will drop it in your phone. Likely underneath /sdcard/TWRP.
Dump command to send to Linux(what I'm using, should be same on windows):
adb pull /sdcard/TWRP TWRP
The ramdisk dumped itself as a `.win` filetype, so I simply renamed the file extension to `.img` so that Magisk would recognize it and apply the appropriate patch.
With this dumped ramdisk image I added it to my phone and used Magisk to patch magisk to that dumped ramdisk, which I then transferred back to my computer.
I then booted the phone into bootloader mode:
adb reboot bootloader
and then flashed the newly modified Magisk ramdisk:
fastboot flash ramdisk magisk_patched-23000_9FXew.img
Upon rebooting my Huawei:
fastboot reboot
was able to verify with Magisk that I now had both TWRP custom recovery without issue and access to root privelages inside of LineageOS (which is good and ignores the need for TWRP to be able to decrypt custom rom contents)
Since TWRP cannot decrypt the contents of a custom rom in this case, being able to use TWRP to dump the ramdisk was an essential step even though Openkirin does not support TWRP. I would have otherwise had no option for acquiring that factory ramdisk because Huawei took them all offline.
This is all mostly just to get ahold of the ramdisk without needing to use huawei official firmware and patch it for Magisk, which there are already guides for on XDA and on Openkirin's support site. There's probably some steps of this I left out. Best of luck to others.
Resources Used that explain some steps I left out (Like installing TWRP to recovery_ramdisk, etc etc):
[Openkirin Magisk Guide](https://openkirin.net/user_guide/how-to-install-magisk/)
[Openkirin Rom Installation Instructions](https://openkirin.net/user_guide/openkirin-rom-installation-instructions/)
[Converting a TWRP Backup into a Flashable zip](https://forum.xda-developers.com/t/tutorial-create-flashable-zip-from-cwm-twrp-backup-mtk.2746044/)
[Huawei P10 Lite TWRP test build 0.5](https://forum.xda-developers.com/t/recovery-emui-8-x-huawei-p10-lite-unofficial-twrp-3-2-1-0-28-04-2018.3783447/page-2)
Hi,
is anyone running latest B20 Oreo rom on an A2017U phone with Magisk v25?
When I patch boot image and flash it via EDL the phone doesn't boot it, I have to restore original boot.img to be able to boot android again.
Also, fastboot is not available in the stock EDL images, any idea how to get fastboot back?
Thanks
Hi,
For first, I flashed some ROMs earlier in my life but it was like 5 years ago. I'm not expert in that field. That being said... I'm running B02 Oreo ROM on A2017G but i had the same problem. I managed somehow to find somewhere (can't remember which site) that "Magisk 16.4 should work because 16.0 version had some problems". So I tried 16.4 and it worked for me. Unfortunately data partition, although it shouldn't after root, stays encrypted (in TWRP).
Also, if You boot to system and open Magisk manager it will show You that update is available. After updating to the latest app version it will say that your version of Magisk is not supported now and You should update it (meaning, flashing latest zip). I didn't try it but assuming that earlier it didn't want to boot with the latest version on "Magisk-v25.1.zip" it won't at this time too.
It's so hard to find any information about this phone this day's... I would love if someone knew how to disable this encryption. I tried I think every solution and nothings seems to work :/
I hope I'm not late and my post will help You