I'm using mate 9 with Magisk for a while. Here is the steps how I flash my phone.
Notice: Only verified Mate 9 MHA-L29C636B188 (Pass SafetyNet Check).
Magisk: Thanks to @topjohnwu
Huawei Firmware Finder: Thanks to (Team MT)
TWRP 3.1.0-1: Thanks to @Tkkg1994
Prepare:
A. Flash official ROM. (Ex: MHA-L29C636B188) (Refer to : [Guide] Mate 9 Flash Update Package and Rebrand)
B. Download Magisk and related file. (Link)
Download:
A. Download Huawei Firmware Finder PC Tool (Link)
B. Run "FimrwareFinderRewrite.exe" and select "Common Base".
C. Select phone brand (Ex: MHA-L29C636) and click "Find".
D. Select 1A. Firmware (Ex: MHA-L29C636B188) "Filelist" and download the second and third link file.
E. Put 1B. bootimg_data_decrypt_xxx.zip and 2D. files(___data___.zip and ___hw___.zip) into phone SDCard.
Unlock:
A. Phone power off, press vol-down and usb cable to enter fastboot mode.
B. fastboot oem unlock xxxxxx (xxxxxx is your unlock code)
Flash:
A. Enter Fastboot again using "fastboot flash recovery MHA_xxxx-3.1.0-1-hi3660.img" to flash TWRP Recovery.
B. Phone power off, press vol-up and power to enter TWRP.
C. TWRP select "Keep Read Only" (Everytime enter TWRP select this.)
D. Wipe => Format Data => yes
E. Install => Select 2E. bootimg_data_decrypt_xxx.zip file.
F. Install => Select 2E. xxxx__data__xxxx.zip file.
G. Install => Select 2E. xxxx__hw__xxxx.zip file (Ignore errors).
H. Reboot => System => Do Not Install.
Magisk:
A. Download "SafetyNet Test" application in Google Play Store.
B. Run SafetyNet Test, only CTS profile match fail.
C. Put 1B. Magisk-vxxxx.zip and Huawei-Prop-Fix-xxxx.zip into SDCard.
D. Phone power off, press vol-up and power to enter TWRP again.
E. Install => Select Magisk-vxxxx.zip
F. Install => Select Huawei-Prop-Fix-xxxx.zip
G. First boot SafetyNet Test can't pass.
H. After second boot SafetyNet Test pass.
I. If SafetyNet Test failure in the future, disable all modules in Magisk, reboot SafetyNet pass then enable modules.
Update: Huawei-Prop-Fix-v1.2_2017091101.zip (Be sure Magisk has busybox, recommend v14.0) [Link]
Keep UP Good Work.
Sure will try.
Thanks,
goldybewon
MHA-L29
Please note that you need to be on a firmware released on or after 12th of April 2017. If it's before that date you'll fail at flashing Magisk.
And you should probably add a notice that this is for decryption.
If coming from SuperSU or PHH you'll have to flash back stock boot image before flashing.
If you're already decrypted there's no need to format data again.
If you want to stay encrypted, flash this instead: https://mega.nz/#!o4ESgABJ!DyUxQSKo8skyfv05sSuU7FjMmsyeckAO0KD_1dDIctw
I have tried several times flashing magisk with C185B181 and I gave up it fails hiding the root! Ante0 tried to help me but I gave up
Iloudsan said:
I have tried several times flashing magisk with C185B181 and I gave up it fails hiding the root! Ante0 tried to help me but I gave up
Click to expand...
Click to collapse
Try flashing the module linked in OP, the Huawei fix. It seems to work for me. USB debugging is staying on, I just had to go to the service menu and enable logging again. After rebooting several times it's still passing
Before, after it became buggy for me again, I had to enable USB debugging after rebooting/using adb. And yesterday I had to enable logging to get it running.
ante0 said:
Try flashing the module linked in OP, the Huawei fix. It seems to work for me. USB debugging is staying on, I just had to go to the service menu and enable logging again. After rebooting several times it's still passing
Before, after it became buggy for me again, I had to enable USB debugging after rebooting/using adb. And yesterday I had to enable logging to get it running.
Click to expand...
Click to collapse
Thanks I'll give it a try tonight
ante0 said:
Try flashing the module linked in OP, the Huawei fix. It seems to work for me. USB debugging is staying on, I just had to go to the service menu and enable logging again. After rebooting several times it's still passing
Click to expand...
Click to collapse
Fix property script enable persist adb, that's the point to pass safetynet. I didn't enable logging and it passed as well.
It's working now thanks guys!!!!
Is it possible to install xposed too?
Iloudsan said:
Thanks I'll give it a try tonight
Click to expand...
Click to collapse
I got it running but the apps takes really long time to load and freeze a lot is this normal
Iloudsan said:
I got it running but the apps takes really long time to load and freeze a lot is this normal
Click to expand...
Click to collapse
Do you mean the magisk manager?
It shouldn't take long at all. Or it doesn't for me at least.
mankindtw said:
Fix property script enable persist adb, that's the point to pass safetynet. I didn't enable logging and it passed as well.
Click to expand...
Click to collapse
I think it's because usb debugging kept disabling for me.
Not sure why it would stop logging, I couldn't even get a logcat...
Oh well, it works now!
By the way, did you make the module? if so you should post it in the Magisk section of XDA. More people are having trouble with Magisk on other Huawei devices (P10, P9, Honor etc.) , and it might help them too.
ante0 said:
Oh well, it works now!
By the way, did you make the module? if so you should post it in the Magisk section of XDA. More people are having trouble with Magisk on other Huawei devices (P10, P9, Honor etc.) , and it might help them too.
Click to expand...
Click to collapse
Yes, I made the module and already post in Magisk 13.6 thread. I don't want to open a new thread in Magisk.
Because I don't have other devices to test if they fail on SafetyNet test.
Hello
So is it possible to install magisk on rooted with PHsuperuser MHA-L29C185b181 .
what is the best method flash it with TWRP or with Magisk Manager
thankd in advance
reg
repoman728 said:
Hello
So is it possible to install magisk on rooted with PHsuperuser MHA-L29C185b181 .
what is the best method flash it with TWRP or with Magisk Manager
thankd in advance
reg
Click to expand...
Click to collapse
Use twrp, and restore stock B181 boot image first.
Just tested on MHA-L09C185B180 with Magisk v14.
Working perfectly fine
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Followed the post as instructed and it works just fine! Installed Magisk on my Mate 9 MHA-L29C567B190. Cheers!!
Hey guys, can I install xposed using magisk without safetynet getting tripped?
Confirmed Mate 9 Pro is working
for those who are interested I followed the instructions to a t however substituted and used update_data_public.zip & update_all_hw.zip files from MATE 9 PRO Firmware LON-L29C636B229.
I also used twrp-3.1.0-1-hi3660 which may be the same but i found mine on a mate 9 pro thread.
It was actually seamless installation and ive had my mate 9 pro rooted with supersu before but never magisk because I couldn't quite get it working but this method worked perfectly.
Like I said I just followed instructions but substituted those two .zip files and used all other files in the instructions.
I will attach a couple screen shots if I can figure out how on here. Man this thing is snappy as Ive ever seen it.... great job on the directions and this thread.... I have seen no lag as far as the magisk apk its all very very fast with no hiccups so far.
pri10 said:
Hey guys, can I install xposed using magisk without safetynet getting tripped?
Click to expand...
Click to collapse
Nope.
Also seems to work on my P10 Plus
Maybe this is old news I just thought id share it in case no one has tested it yet.
model is VKY-L29 and i just substituted those two firmware finder files from B162 of the p10 plus fw
also i used a different twrp obviously but this method has my recent huawei devices running magisk for the first time at least for me its great thing ive never been able to figure out how to do it until this method. thanks
Update 1B. link:
Huawei-Prop-Fix-v1.2_2017091101.zip keeps persist.sys.root.status property zero.
Related
Alright.
I had this problem for a while and I figured out how to flash the update without the need to factory reset or change the update script of the update file.
Even if you get the user/release-keys error message. EXAMPLE:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You have to be using the latest lollipop release before updating. That means you have to be on YOG7DAS2K1 before attempting.
This worked out for me. But it might not work for you. I do not believe it can destroy your phone and switch some satellites off, but still, not responsible if it did so.
Requirments:
You have to have TWRP now or you at least have ROOT and any flashing app like flashify.
Download COS 13 update file. here https://www.androidfilehost.com/?fid=24459283995316311
Download the latest CyanogenMod Recovery https://download.cyanogenmod.org/?device=bacon
Download the cm-12.1-YOG7DAS2K1 full ROM [url]https://www.androidfilehost.com/?fid=24369303960686198[/URL]
Guide:
Make sure the update cyanogen recovery option is checked in developer options.
Flash CyanogenMod Recovery downloaded before.
Reboot into it.
Use the update function in CyanogenMod Recovery and choose cm-12.1-YOG7DAS2K1 as the update file. It might take a while.
Now reboot to your phone. When booted and running, reboot to recovery.
Now you are running COS recovery. Update with the incremental.
That is it.
I hope this works out for you.
EXTRA: How to ROOT and have TWRP as a recovery:
Requirements:
A laptop.
Download TWRP and adb drivers on the laptop and the SuperSU and TWRP on your phone
Download Oneplus One TWRP Recovery [url]https://dl.twrp.me/bacon/twrp-3.0.2-0-bacon.img.html[/URL]
Get any adb divers. This one suffice [url]http://forum.xda-developers.com/google-nexus-5/development/adb-fb-apx-driver-universal-naked-t2513339[/URL]
Download the latest SuperSu [url]https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip[/URL]
Guide:
Reboot into bootloader: you can do this in many ways. A simple google search will show you how. Easiest way is to turn the phone off and hold the volume up and power long enough for the phone to boot into bootloader.
Connect your phone to your laptop
Run the adb: I assume you are using windows of course. First put the TWRP .img file in this folder. Hold shift and right click in the folder downloaded above. A 'Open command window here' option will be there. Click it and write in the window
Code:
fastboot boot twrp-3.0.2-0-bacon.img
. A hint: you can just write twrp and hit TAB, it will complete the filename. Or you can rename the downloaded file to just twrp.img
Check your phone, you will be running TWRP temporarily. You now have the option to ROOT only by flashing the SuperSU file downloaded on your phone. If you reboot now you will lose TWRP and get back to the official COS Recovery. If you want TWRP for good flash the TWRP file downloaded on your phone before.
I hope this is easy. It actually is. just follow it step by step.
If you could provide us the guide to root and come back to twrp I would be extremely happy
bisio971 said:
If you could provide us the guide to root and come back to twrp I would be extremely happy
Click to expand...
Click to collapse
fastboot flash latest twrp and flash SuperSU BETA
THANK the post if I deserve
bisio971 said:
If you could provide us the guide to root and come back to twrp I would be extremely happy
Click to expand...
Click to collapse
if you need a guide to root, this means you are not rooted, and if you are not rooted most probably you already have stock recovery, which means you can just install the OTA update without any issues.
bisio971 said:
If you could provide us the guide to root and come back to twrp I would be extremely happy
Click to expand...
Click to collapse
Added as requested. I hope you find it easy.
y2kkingboy said:
Added as requested. I hope you find it easy.
Click to expand...
Click to collapse
Thank you, you made my life easier, but when I tried to run the twrp through fastboot I got an error and I got the solution writing "fastboot boot twrp.img" (after renaming the file).
bisio971 said:
Thank you, you made my life easier, but when I tried to run the twrp through fastboot I got an error and I got the solution writing "fastboot boot twrp.img" (after renaming the file).
Click to expand...
Click to collapse
Yeah. I mad a mistake there. Thank you and glad it helped.
If I do this what happens to my data?? I'm on cm 12. 1.1, rooted & running twrp.
---------- Post added at 12:20 AM ---------- Previous post was at 12:18 AM ----------
Link for cos13 that works with this method?
thinleytsering9 said:
If I do this what happens to my data?? I'm on cm 12. 1.1, rooted & running twrp.
---------- Post added at 12:20 AM ---------- Previous post was at 12:18 AM ----------
Link for cos13 that works with this method?
Click to expand...
Click to collapse
As I stated before you have to be on COS 12.1 YOG7DAS2K1. This method should not format your phone or remove any data as there is no factory reset step.
As for the link they are all over the place now. I used the official one. I'll link it for your convenience.
can anyone please pull the stock recovery from COS 13, not 12. I kinda screwed up while updating and now stuck in bootloop.
Update: The issue is resolved. The issue was because of SuperSu 2.46. Installing the latest TWRP and SuperSu 2.66 fixed it. Marshmallow is now rooted!
Thank you very much! After going back to stock and still not receiving the update for more than a week (well at least it felt like a week, Lol) I decided to flash a full COS 13 zip floating around. Instantly liked the new ROM but it had root/symlink issues only to be resolved when flashing a custom kernel it seems. Not what I really wanted so then I stumbled onto your thread and this technique worked 100%! I was on DAS2K1 (flashed thru a custom recovery) already and had several failed attempts flashing just the incremental outright (thru stock recovery)., but by flashing DAS2K1 thru stock recovery first as you suggest then the incremental seems to do the trick.
I did it all the steps, but my phone doesn't not start. After optimizing aplications I have bootloop at "cyanogen modready".
L.E. I think the problem was one of old aplications. After a clean install everything works.
This is the best thing Oneplus one i ever experience.COS13 give my Oneplus one a new breathe of life .This update better than crap lolipop.No Bug for me until now,only google play service need to update twice in play store,its auto reboot itself twice and wholla,super speed UX.The best thing i ever have.I apply update from CM-12-0-YNG1TAS17L Build LRX22G using this method and it works flawlessly
I don't need to factory reset or wipe cache .
I flash full stock ROM cm-12.1-YOG7DAS2K1 and apply update through CyanogenMod Recovery only and nothing else.
Now my oneplus one is rooted and TWRP install using ADB and its fly.All rooted apps is working together with Adaway.
Thanks Cyanogen team for make this 2 years old flagship killer a beast .
Only thing not satisfied is gone signal and wifi status (connectivity indicator ).I need to swipe down to see my transfer data working (what a bummer ).
Thanks so much for this magical guide (y2kkingboy) Yours truly Oneplus one diehard fan.
I was already on cm-12.1-YOG7DAS2K1, however rooted. So even if I had been offered the OTA it would have failed.
Your guide got me updated, first time with no problems.
6.0.1 is such an improvement on 5.1.1, I tried a couple of other 6.0 roms, however this has by far been the most stable and bug free.
Cheers for the tutorial!
u can also add a trick i saw online i.e to remove lines of code from assets to - in updater file
#sychrome# said:
u can also add a trick i saw online i.e to remove lines of code from assets to - in updater file
Click to expand...
Click to collapse
Can you provide more info? i've always had trouble updating when rooted.
InsaneNutter said:
Can you provide more info? i've always had trouble updating when rooted.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2522762
u can also add a trick i saw online i.e to remove lines of code from assets to - in updater file
Click to expand...
Click to collapse
Can you provide more info? i've always had trouble updating when rooted.
Click to expand...
Click to collapse
I had tried this before and it did not work for me. Kept getting an error saying "the signature file was not a complete file" and therefore it didn't flash. But it may have been editing error on my part. This method works just fine and no need to give up your data either.
Having tried many other ways, I got it done with this instruction.
Thank you!
marxu said:
Having tried many other ways, I got it done with this instruction.
Thank you!
Click to expand...
Click to collapse
Glad I helped.
Do not work with Nougat 7.1.1 / 32.4.A.0.160 (Bootloop)
New TWRP (You dont need otg and mouse anymore!):
https://www.androidfilehost.com/?fid=745425885120733410 (thanks to andralex8!)
GUIDE UPDATED, TESTED AND SIMPLIFIED 15.2.2017 (thanks to munjeni)
Tested with Saudi Arabia, Germany and Nordic (.378) firmwares
I managed to get my Xperia Z4 Tablet (SGP771) LTE model to have root, TWRP-recovery*, munjenis DRM fix and Adaway working with Nougat firmware (Saudi Arabia). I will share steps that I have done with my own tablet. If this guide brick your device or something goes wrong, I am not responsible for loss of your device. Use this guide only with your own RISK!
This tutorial is not for beginners. You need to have working adb installed yout pc, unlocked tablet, sonys special driver for fastboot. and TA backup (example TA-21062016.img). Use only this tutorial with Sony USB-cable.
*To get TWRP working, you need: OTG-cable and a mouse with wire or wireless mouse with a dongle.
0. Download Nougat 32.3.A.0.376 (Saudi Arabia) firmware with Xperiafirm 32.3.A.0376. to your PC
1. Flash Nougat 32.3.A.0.376 (Saudi Arabia) with Flashtool 0.9.23.2.
2. Boot your device and enable Developer settings from setting
3. Enable USB debugging setting from Developer settings
4. Download Supersu and Magisk to your device:
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip
http://tiny.cc/latestmagisk
5. Shutdown your device
6. Download munjenis DRM fix and serajr script package v2 to your pc:
http://munjeni.myiphost.com/ta_poc.rar
https://forum.xda-developers.com/showpost.php?p=70959962&postcount=65
7. Decompress files from munjeni and serajir to same folder.
8. Extract kernel.sin from your nougat firmware ftf (You can use 7zip to do this). Copy it to same folder with DRM fix. Rename kernel.sin to kernelX.sin
9. Copy your TA backup to same folder with DRM fix and rename it TA.img
10. Open Cmd with admistrator persimmions and use DOUBLECLICKME_NOUGAT.bat (search cmd rght mouseclick use admistrator).
11. Follow munjenis tool tutorial: You can choose if you want Sony Ric off. I left it on but turned dm verity off.
12. Download TWRP: https://drive.google.com/drive/folders/0B0j3VJ1Xp5N8cnhQamtxRWVtRmc
13. Press vol up and connect your device to pc to use fastboot. Use command: fastboot flash boot new_boot.img
14. After that use command: fastboot flash recovery TWRP-3.0.2-0-20160604.img
15. Disconnect your device and put otg-cable to tablets usb and connect mouse to otg-cable.
16. Press vol down + power to boot to TWRP. Touchscreen is not workin but you can use your mouse to navigate in TWRP!
17. Allow TWRP to make changes to your device and flash Supersu 2.79 and Magisk 11.1.
18 Boot your device and install magisk manager from the play store.
19. Enable from magisk manager settings: busybox, magisk hide and systemless hosts and Install Adaway (Will not work without Magisk, strange).
I have not managed to get my CTS profile approved but that is not major issue if not playing with Pokemon go (You can use magisk to detect this).
Note1 : Change LTE to 1 priority from mobile setting. Default for SA firmware is GSM
Note2: If you have already tried rootkernel to get drm working; do a full wipe and reflash firmware with flashtool. Rootkernel messes something. Tablet do not boot if you have used rootkernel and after that try to use munjenis DRM fix.
Note3: Magisk 11.1 wont work with Xperia Z4 Tablet without Supersu. So flash Supersu first and Magisk 11.1 after that
Note4: You cannot boot to TWRP by using root and reboot to recovery apps. You need to boot to the recovery with keycommand voldown+power
I hope this guide helps some fellow flashers
Special thanks for
munjeni
serajr
Chainfire
Androplus
topjohnwu
Teamwin
Androxyde
mrRobinson
If I forgot someone I am truly sorry!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just tried unable to boot to recovery
sahilg009 said:
Just tried unable to boot to recovery
Click to expand...
Click to collapse
Did you do a full wipe? Try to fastboot flash boot new_boot.img after flashing recovery!
Tried wiping now flashing kernel gives me a no sim card error
sahilg009 said:
Tried wiping now flashing kernel gives me a no sim card error
Click to expand...
Click to collapse
Check this out:
https://forum.xda-developers.com/showpost.php?p=70972513&postcount=115
halfvast said:
Check this out:
https://forum.xda-developers.com/showpost.php?p=70972513&postcount=115
Click to expand...
Click to collapse
Even tried that still giving me signal problem
sahilg009 said:
Even tried that still giving me signal problem
Click to expand...
Click to collapse
Strange, I Did not encourter this problem because I could boot to TWRP and do adb trick there. Do you use orginal Sony usb to flash in fastboot? I had once a problem with Samsung Phone (S7) to flash recovery because the usb was not the one that came with my Phone.
Yeah
Try redownload TWRP image and flash it. If not working do a clean flash and try again or wait for Androplus kernel
Tried it all nothing worked still no sim error
sahilg009 said:
Tried it all nothing worked still no sim error
Click to expand...
Click to collapse
I found out munjeni is fixing his tool:
https://forum.xda-developers.com/showpost.php?p=70993277&postcount=173
I used previous version, which is not availble right now.
He says further in his thread he is going to release tomorrow a new version.
I used this version:
http://www.filedropper.com/tapoc
halfvast said:
I found out munjeni is fixing his tool:
https://forum.xda-developers.com/showpost.php?p=70993277&postcount=173
I used previous version, which is not availble right now.
He says further in his thread he is going to release tomorrow a new version.
I used this version:
http://www.filedropper.com/tapoc
Click to expand...
Click to collapse
Couldnt I just do the root and recovery method you have given on the wifi version as im not too bothered about drm fix for now as it looks abit complicated at the moment for me. It would be much more simple for me to flash recovery then super su. I just wanna know if this is possible?
Thanks
I am not sure. You need atleast a correct TWRP. You can try if You dare with your own RISK
But I doubt that it wont work..
halfvast said:
I am not sure. You need atleast a correct TWRP. You can try if You dare with your own RISK
But I doubt that it wont work..
Click to expand...
Click to collapse
Ok then dont think id like to try incase it doesnt boot so I think I might just wait for andro to do his stuff.
I have updated the guide and tested it today (13.2.2017) and it is working again
Guide updated and simplificed 15.2.2017. Thanks to munjeni!
halfvast said:
Guide updated and simplificed 15.2.2017. Thanks to munjeni!
Click to expand...
Click to collapse
Step 8 says Extract kernel.sin from your nougat firmware copy it to same folder with DRM fix. Rename kernel.sin to kernelX.sin. Do I have to extract that from the ftf or my Nougat firmware im currently using? Also does the ftf have to be that region?
RJASSI21 said:
Step 8 says Extract kernel.sin from your nougat firmware copy it to same folder with DRM fix. Rename kernel.sin to kernelX.sin. Do I have to extract that from the ftf or my Nougat firmware im currently using? Also does the ftf have to be that region?
Click to expand...
Click to collapse
You need to extract it from ftf-image. I used 7zip. My device was Nee with stock. I used DE with Marshmallow and I am currently using Saudi Arabia. So I dont think it will matter, which kernel you use with your device. But I would use same kernel version with rom. So If you are using Saudi Arabia rom use Saudi Arabia kernel. For Russia rom use Russia kernel, and so on
I will add tft-image extract to tutorial!
DRM fix doesn't work. XReality (among other things I assume) are ever disabled.
On Marshmallow DRM fix was working fine (was using XReality engine despite the unlocked bootloader)
For me it is working!
Firstly, I do not take any responsability in case anything happens to your device or your files. You decided to follow this guide at your own risk.
THIS WORKED FOR ME FOR MAGISK v14.3
ALSO WORKS ON MAGISK v14.5
I highly not recommend to use this guide for a different device other than the Xperia Z2 D6503.
All that aside, I managed to install magisk on my Stock Xperia Z2 and still keep ctsProfile and basicIntegrity: true.
HIGHLY RECOMMEND TO BACK EVERYTHING UP BEFORE PROCEEDING
You will need:
(OPTIONAL)Marshmallow FTF Firmware Here
(OPTIONAL)Flashtool Here
Magisk Manager Here
Rootkernel_v4.31_Windows_Linux.zip Here
ADB and Fastboot Here
Advanced Stock Kernel Here
TWRP Sirius Here
(OPTIONAL BUT HIGHLY RECOMMENDED) Use flashtool to flash the modified version of the stock ROM from above. It worked on this version but I can't really guarantee it will work on others. Can't really guarantee it will work on this either.(after you select the file there are 2 versions. pick the modified one).
1) Extract the Rootkernel_v4.31_Windows_Linux.zip and extract from the advanced stock kernel the boot.img (Rename it from boot.img to Old_boot.img)
2) Open cmd and use cd to reach the folder in which you extracted rootkernel.
Use the command "rootkernel Old_boot.img New_boot.img"
Say Yes to everything except installing TWRP.
3) Install Magisk Manager on your phone and copy "New_boot.img" to the phone.
4) Go to Magisk Manager settings , scroll to Update Channel and select Beta
5) Select install Magisk and select modify boot image. Select "New_boot.img" from the folder you copied it to
6) Extract adb to a folder
7) After patching the boot image at step 6, copy "patched_boot.img" from internal storage/MagiskManager to the folder in which you extracted adb
8) Copy TWRP to the adb folder and rename it to TWRP.img
9) Open cmd and use cd to navigate to the folder in which you copied adb. Type in the console "fastboot flash boot New_boot.img". Turn off your phone and then hold Volume Up whil plugging it into your pc(booting it into fastboot).
10) While still in fastboot, type "fastboot flash recovery TWRP.img"
11) Disconnect your phone from the pc. Wait a few seconds and then boot into TWRP (hold power button and Volume Down). A notification will pop up and select to "Keep System Readonly" (I think something like that). Reboot into system.
If everything worked as intended, a safetynet check will reveal everything in green, allowing you to both have root access and also run apps like Netflix and Android Pay
NOTE: Magisk Modules should be flashed via TWRP. For some reason, Magisk Manager is unable to install them.
EDIT: I tried to install xposed systemlessly but Safetynet was triggered. Don't think I can figure this out.
DahakePL tried with elite kernel and it didn't work. Writing this just in case anyone tries.
This worked for me but I can't guarantee it will work for you. (Photos at the end)
Did this guide help you? If you need any help, I will do my best to answer your questions.
I am not a developer and I do not really understand why or how everything works. I came across this method that worked for me and I thought I'd share it since I couldn't find a guide for my xperia phone when I needed it.
IN CASE SAFETY NET IS TRIGGERED, the only way to restore to everything in green is to reflash the stock rom (you don't have to format everything).
Did it work out for you? Just leave a reply saying that so I can figure out if everything works.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
.
Thank you man
Great job
Hi there and great job. Many thanks for this.
I've a question, "(OPTIONAL BUT HIGHLY RECOMMENDED) Use flashtool to flash the modified version of the stock ROM from above (after you select the file there are 2 versions. pick the modified one)." - what if another .291 stock firmware is used (eg downloaded from Xperifirm)?
fribriz said:
Hi there and great job. Many thanks for this.
I've a question, "(OPTIONAL BUT HIGHLY RECOMMENDED) Use flashtool to flash the modified version of the stock ROM from above (after you select the file there are 2 versions. pick the modified one)." - what if another .291 stock firmware is used (eg downloaded from Xperifirm)?
Click to expand...
Click to collapse
Well, this worked on this exact version. If you don't use it, i can't guarantee it will work.
Well, can't either way
But it worked on that one. I believe you don't have to reinstall your stuff if you already have the stock rom. You can just flash it over without deleting anything
Works fine thank you
Adriano-A3 said:
Thank you man
Great job
Click to expand...
Click to collapse
Awesome
I'm actually surprised.
Doesn't work on elite kernel, just tested, no root and no safetynet
DahakePL said:
Doesn't work on elite kernel, just tested, no root and no safetynet
Click to expand...
Click to collapse
Have you tried with the advanced kernel I linked?
Also, you have to be running stock
Xperia z2
IceGordol said:
Have you tried with the advanced kernel I linked?
Also, you have to be running stock
Xperia z2
Click to expand...
Click to collapse
I'm using the advanced stock kernel method and it works 100%
But I tried elite kernel and it doesn't work at all, just in case someone else wanted to know or something :highfive:
DahakePL said:
I'm using the advanced stock kernel method and it works 100%
But I tried elite kernel and it doesn't work at all, just in case someone else wanted to know or something :highfive:
Click to expand...
Click to collapse
Modified the post in order to specify this. Also credited you. Thanks for this addition.
Where is modified FTF?
Sent from my D6503 using Tapatalk
Why do I need to flash TWRP? It is already included into advanced stock kernel.
After flash magisk, can't mount otg drive in twrp
Sent from my D6503 using Tapatalk
I am running a phone with KK 4.4.4 rooted and xposed installed. What should I do first to use it?
If I want to keep few apks data?
May I install Cyberian Camera MOd after it?
Thanks you! Working finally!
609125 said:
Thanks you! Working finally!
Click to expand...
Click to collapse
How u make it working? I got no clue about step 2... rootkernel old_boot.img new_boot.img? I really have no idea about the instructions...
---------- Post added at 04:10 PM ---------- Previous post was at 04:03 PM ----------
DahakePL said:
I'm using the advanced stock kernel method and it works 100%
But I tried elite kernel and it doesn't work at all, just in case someone else wanted to know or something :highfive:
Click to expand...
Click to collapse
Guys, I once rooted my Z2 with SuperSU in locked bootloader condition (already unroot it). Im interested with magisk and want to try it. Is it possible for me even my device is bootloader locked? Thank you
IceGordol said:
9) Open cmd and use cd to navigate to the folder in which you copied adb. Type in the console "fastboot flash boot New_boot.img". Turn off your phone and then hold Volume Up whil plugging it into your pc(booting it into fastboot).
Click to expand...
Click to collapse
Perfect for me. Thank you very much!
But your step 9 is wrong. should be "fastboot flash boot patched_boot.img"
My ROM is Marshmallow_Stock_575_ROM_Ultraslim
must remove SuperSU (root) before installing, use UPDATE-unSU-signed.zip
Can't get this to work at all. I'm on Customised UK stock ROM.
No matter what I do, I get bootloops once Magisk is installed. If I use the Magisk Uninstaller from TWRP the phone works fine again.
EDIT: I should have said, I've tried with Magisk 16.0 and 16.7 Beta. No luck with either. I've also tried patching the advanced stock kernel boot.img and I've tried installing via TWRP with Bootloader-SonyELF. No luck again, just the same bootloop!
UPDATE: I managed to fix this by using the latest version of the RootKernel patching tool (v5.23) instead of v4.31 and following the rest of the instructions using the boot.img from advanced stock kernel with Magisk 16.7 installed successfully.
Work fine with Magisk 18
okay after two soft brick, red blinking light and the device wont turn on, i finally succeed installing this. the first issue i'm getting is adb command not found when running the "fastboot flash boot patched_boot.img", so i tried to use TWRP to install the img, which refuse saying it need bootbridge, so i install through the recommend option in magisk manager (installing directly) which cause the first brick
the first brick is restored by using flash tool
the second brick can't be restored by flash tool due to the usb debugging is off causing flash tool to said "device connected but using old drivers", luckily xperia companion software (now called emma) restored it succesfully
and i finally figured what causing the soft brick, since emma said the bootloader is locked and magisk can't be used with locked bootloader and that bricked the device.
anyway finally unlocked the bootloader since emma needed it to unbrick the device. and after unlocking the bootloader and follow again the procedure here i finally succeed installing magisk on my z2
TLDR: YOU NEED UNLOCKED BOOTLOADER TO FOLLOW THIS PROCEDURE. to check easily if your bootloader is locked or not is just by running Emma (xperia updater replacement) or use "fastboot oem device-info".
finally can try magisk, since many apps detect supersu now and refuse to work with it. i didn't unlocked the bootloader the first time since supersu can work with locked bootloader >_>
IMPORTANT
I havent made this rom and im not responsible of any problem with it. Its just a tutorial.
The best Gsi fully working, Blissos Rom (unnoficial) on N20U Snapdragon:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Full credits to Nazim, autor of this GSI rom
ABOUT
An open-source operating system based on Android with customizations, options and added security features.
LINKS
Telegram: https://t.me/naz_dev/46
Download: https://sourceforge.net/projects/gsi-projects/files/v402.1/BlissOS-15.3/
WHAT WORKS
Almost everything is working:
NFC
FINGERPRINT
SPEN
BLUETOOTH
RIL
CAMERA (not the best quality)
ETC...
WHAT NOT WORKS
LOCATION
Anything else report it
INSTRUCTIONS
1. Unlocked Bootloader
2. TWRP installed (https://forum.xda-developers.com/t/...r-galaxy-note-20-ultra-5g-snapdragon.4210985/)
3. Once you have the TWRP installed, you need to donwload the GSI, extract the .img file and transfer it to the phone via TWRP connection.
4. Flash the image file on system.
5. Wipe factory reset.
6. Reboot.
7. Setting up your phone, I recommend you to skip the security (fingerprint and pin), and VERY IMPORTANT, skip the google log in account.
8. Once you are ready, go to settings > apps > google play services > uninstall upgrades.
9. Log in google and READY!.
10. I recommend you to go to PHH settings, force fps to 96hz and then to 120hz. On samsung settings, enable extended brightness. To enable Bluetooth, go to misc settings, then activate "Force-disable A2DP offload".
11. Now you can add security methods, including fingerprint.
ENJOY!
its important to mention that other GSI roms work well: PHH AOSP, Pixel Experience (problem with 120hz), OctaviOS. All of them have little important problems (battery, ril...), and its important to remark that the battery life is AMAZING in this rom (between 8-9h with half birghtness and bluetooth).
HOPE WILL HELP TO EVERYONE TIRED OF ONE UI
IF ANYONE CAN HELP WITH ROOT, CAMERA (PORT SAMSUNG ONE) AND LOCATION IT WOULD BE AMAZING
This is amazing, when I get tired of stock one ui, will definitely try this
CRDROID
is also working amazing, its a newer release, its more smooth but there is a problem with the fingerprint and safetynet (im not able to pass it). Location problem solved and its performing a little better in general
Link: https://sourceforge.net/projects/gsi-projects/files/v411/crDroid-8.3/
FerJavi said:
CRDROID
is also working amazing, its a newer release, its more smooth but there is a problem with the fingerprint and safetynet (im not able to pass it). Location problem solved and its performing a little better in general
Click to expand...
Click to collapse
Do you mind sharing the link to CRDROID?
Suntaina said:
Do you mind sharing the link to CRDROID?
Click to expand...
Click to collapse
Shared, edited post
I spent a few days messing with a few of these GSI builds. I'd fixed most of the problems i was having except for calls. I could not place a call nomatter what i did.
As soon as i would dial. it'd immediately hang up. Which firmware vendor.img are you guys using?
My most successful combo was Android 11 firmware with an Android 10 vendor... but still no calling.
flippage said:
I spent a few days messing with a few of these GSI builds. I'd fixed most of the problems i was having except for calls. I could not place a call nomatter what i did.
As soon as i would dial. it'd immediately hang up. Which firmware vendor.img are you guys using?
My most successful combo was Android 11 firmware with an Android 10 vendor... but still no calling.
Click to expand...
Click to collapse
Hi dude, I was able to get calls working with crdroid A12 with a12 vendor. The problem with it was safetynet, and i was unable to root gsi to get safetynet fix. After a few days using bliss os the calls stopped working (as u said).
flippage said:
I spent a few days messing with a few of these GSI builds. I'd fixed most of the problems i was having except for calls. I could not place a call nomatter what i did.
As soon as i would dial. it'd immediately hang up. Which firmware vendor.img are you guys using?
My most successful combo was Android 11 firmware with an Android 10 vendor... but still no calling.
Click to expand...
Click to collapse
Did u managed to root gsi? i tried A11 but i had a problem with landscape mode (black stripes appeared on my screen).
Maybe we can create a telegram group to share all this things
UPDATE:
I've managed to install magisk, location is also working, ril is working, ALL IS WORKING. I installed Gcam and photos are good, not amazing, but good enough.
There is a new rom, AncientOs, is the rom Im using now, but PE+ is working also amazing.
SCREENSHOOTS:
ROOT WITH MAGISK:
1. Latest Odin flashable update is required (at least this is the best worked for me).
2. Transfer the AP file to the device, and install
MAGISK
3. Go to Install, then select patch image (recommended), then select the AP file you have transfered to the phone.
4. After the process, transfer the magisk patched image to the PC, use WINRAR or 7ZIP to extract the files, IMPORTANT the file you need is only boot.img.
5. After you have done this, transfer the boot.img file to the phone, and after installing the rom, flash the boot.img file via TWRP as boot image.
6. Boot and Enjoy, root is done, pass safetynet if you need by using magisk fix.
GCAM FILES
So I'm waiting Exynos variant.
FerJavi said:
UPDATE:
I've managed to install magisk, location is also working, ril is working, ALL IS WORKING. I installed Gcam and photos are good, not amazing, but good enough.
There is a new rom, AncientOs, is the rom Im using now, but PE+ is working also amazing.
SCREENSHOOTS:
View attachment 5592089
ROOT WITH MAGISK:
1. Latest Odin flashable update is required (at least this is the best worked for me).
2. Transfer the AP file to the device, and install
MAGISK
3. Go to Install, then select patch image (recommended), then select the AP file you have transfered to the phone.
4. After the process, transfer the magisk patched image to the PC, use WINRAR or 7ZIP to extract the files, IMPORTANT the file you need is only boot.img.
5. After you have done this, transfer the boot.img file to the phone, and after installing the rom, flash the boot.img file via TWRP as boot image.
6. Boot and Enjoy, root is done, pass safetynet if you need by using magisk fix.
GCAM FILES
Click to expand...
Click to collapse
Grea job dude, when my note 20 ultra doesn’t get anymore updates, I will definitely try this or perhaps very soon lol.
Do you know if we could get esim to work? I know some dude on this forum made it work earlier, rooted on android 11, this model.
Suntaina said:
Grea job dude, when my note 20 ultra doesn’t get anymore updates, I will definitely try this or perhaps very soon lol.
Do you know if we could get esim to work? I know some dude on this forum made it work earlier, rooted on android 11, this model.
Click to expand...
Click to collapse
I´ll check it
Nettwerk said:
So I'm waiting Exynos variant.
Click to expand...
Click to collapse
At the moment, exynos chips are supported, so you only need to have TWRP (that supports flashing images, I think the one available can do it).
What is link for Exynos variant ROM?
FerJavi said:
UPDATE:
I've managed to install magisk, location is also working, ril is working, ALL IS WORKING. I installed Gcam and photos are good, not amazing, but good enough.
There is a new rom, AncientOs, is the rom Im using now, but PE+ is working also amazing.
SCREENSHOOTS:
View attachment 5592089
ROOT WITH MAGISK:
1. Latest Odin flashable update is required (at least this is the best worked for me).
2. Transfer the AP file to the device, and install
MAGISK
3. Go to Install, then select patch image (recommended), then select the AP file you have transfered to the phone.
4. After the process, transfer the magisk patched image to the PC, use WINRAR or 7ZIP to extract the files, IMPORTANT the file you need is only boot.img.
5. After you have done this, transfer the boot.img file to the phone, and after installing the rom, flash the boot.img file via TWRP as boot image.
6. Boot and Enjoy, root is done, pass safetynet if you need by using magisk fix.
GCAM FILES
Click to expand...
Click to collapse
After I extract the boot.img from inside the patched AP file and flash it i can not boot. It messes up something related to vbmeta i think. Still gonna mess with it because if it works for you I'm sure its just something I'm doing wrong.
Also, you said you have gotten calls working? When i try to place a call it immediately tells me call ended. From what i've gathered so far it's something to do with no VoLTE. I'm on AT&T which has no 3G network anymore so if that's how you're able to place calls that won't work for me.
flippage said:
After I extract the boot.img from inside the patched AP file and flash it i can not boot. It messes up something related to vbmeta i think. Still gonna mess with it because if it works for you I'm sure its just something I'm doing wrong.
Click to expand...
Click to collapse
I suposse you have flashed vbmeta disabled to flash twrp, if not, try that. Another option could be flashing vbmeta from the magisk patched AP file... Or have you tried the "multidisabler" command from twrp terminal?
Nettwerk said:
What is link for Exynos variant ROM?
Click to expand...
Click to collapse
https://sourceforge.net/projects/an...4_bgN-vndklite-Steel-20220417.img.xz/download
Try this one
FerJavi said:
I suposse you have flashed vbmeta disabled to flash twrp, if not, try that. Another option could be flashing vbmeta from the magisk patched AP file... Or have you tried the "multidisabler" command from twrp terminal?
Click to expand...
Click to collapse
Tried those and still no-go. No matter what as soon as i modify the boot.img to anything other than the original file from the firmware (FVC5) I fail to boot and get sent back into TWRP.
Link for ancient os snapdragon plz
FerJavi said:
At the moment, exynos chips are supported, so you only need to have TWRP (that supports flashing images, I think the one available can do it).
Click to expand...
Click to collapse
Can u plz give the link of ancient os for snapdragon
Are you using the vndklite version? I've been using the regular builds, I wonder if that has anything to do with my magisk issues...
Hi!!
This is my first contact with Android. I have compiled the TWRP for SM-N980F is fully working. I hope we find a custom rom to be able to install it.... I'm going to try to develop one. Let's see how it goes.
TWRP NOTE20
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Shiresp said:
Hi!!
This is my first contact with Android. I have compiled the TWRP for SM-N980F is fully working. I hope we find a custom rom to be able to install it.... I'm going to try to develop one. Let's see how it goes.
TWRP NOTE20
View attachment 5588669
Click to expand...
Click to collapse
Thanks for your effort. Please let us know, 10 days later, are there any bugs or it works as planned? Are there any special steps we shoul do to install it?
sheebee said:
Thanks for your effort. Please let us know, 10 days later, are there any bugs or it works as planned? Are there any special steps we shoul do to install it?
Click to expand...
Click to collapse
Hi Sheebee,
I haven't found any bug usung the recovery.
And about the install steps, they are the usual to install twrp.
1. Unlock bootloader.
2. Flash with Odin in AP side the twrp file.
3. Reboot in recovery Mode.
---‐-------------------
4. If you want install magisk or rom. Install it
5. Reboot settings power off.
6. Automatically turn on in recovery Mode.
7. Wipe data.
8. Reboot settings and system.
And thats all.
Sorry for no show the steps.
Byeeee
Thanks Shiresp, may the force be with you! Let us know if you find appropriate ROM.
Shiresp said:
Hi!!
This is my first contact with Android. I have compiled the TWRP for SM-N980F is fully working. I hope we find a custom rom to be able to install it.... I'm going to try to develop one. Let's see how it goes.
TWRP NOTE20
View attachment 5588669
Click to expand...
Click to collapse
Where u got sources from ?
installed smoothly until i tried to boot to system and found that my device no longer boots to system lol now having a hard time finding the stock firmware for the usa model
i think you should try installing GSI ' s to your device
deathbypvp said:
installed smoothly until i tried to boot to system and found that my device no longer boots to system lol now having a hard time finding the stock firmware for the usa model
Click to expand...
Click to collapse
It's just for n980F model. Im using a european model and works properly
Ivan2005 said:
Where u got sources from ?
Click to expand...
Click to collapse
Twrp??? From github.. c1s model....
Shiresp said:
It's just for n980F model. Im using a european model and works properly
Click to expand...
Click to collapse
idk what region model my device was but its a n980f and it just boots to the custom recovery
I have a eu version sm-n980f/ds, android 12. Twrp is installed but you can not boot the system. it remains in twrp recovery
deathbypvp said:
idk what region model my device was but its a n980f and it just boots to the custom recovery
Click to expand...
Click to collapse
When twrp boots, after that you try reboot -> system???
edsoedso said:
I have a eu version sm-n980f/ds, android 12. Twrp is installed but you can not boot the system. it remains in twrp recovery
Click to expand...
Click to collapse
I'll do it with 4 n980F and work. After twrp boot, reboot -> system
Shiresp said:
I'll do it with 4 n980F and work. After twrp boot, reboot -> system
Click to expand...
Click to collapse
I have already rooted phone but have not installed recovery. I tried to install it through magisk but unsuccessfully. Could you please be more specific in steps you follow to install it through odin? Thank you
edsoedso said:
I have already rooted phone but have not installed recovery. I tried to install it through magisk but unsuccessfully. Could you please be more specific in steps you follow to install it through odin? Thank you
Click to expand...
Click to collapse
1. In Odin uncheck auto reboot.
2. In AP side select twrp file.
3. Flash the file.
4. Press In the device volume down and power, when phone rebooting and before logo press volume up and power. When warning about custom firmware installed, release power button.
5. Into twrp flash samsung disabler 3.0 and flash magisk.
6. Option reboot -> power off.
7. Device rebooting again in twrp automatically.
8. Factory data, no factory reset.
9. Option reboot -> system
10. Device will reboot normally. But this first power on system is normal that it takes a few minutes to start the phone completely.
That's the steps I follow with all twrp I have installed.
BYE!!!
Shiresp said:
1. In Odin uncheck auto reboot.
2. In AP side select twrp file.
3. Flash the file.
4. Press In the device volume down and power, when phone rebooting and before logo press volume up and power. When warning about custom firmware installed, release power button.
5. Into twrp flash samsung disabler 3.0 and flash magisk.
6. Option reboot -> power off.
7. Device rebooting again in twrp automatically.
8. Factory data, no factory reset.
9. Option reboot -> system
10. Device will reboot normally. But this first power on system is normal that it takes a few minutes to start the phone completely.
That's the steps I follow with all twrp I have installed.
BYE!!!
Click to expand...
Click to collapse
Thank you for your prompt reply. What should I do under number 8, wipe data? Thank you!
edsoedso said:
Thank you for your prompt reply. What should I do under number 8, wipe data? Thank you!
Click to expand...
Click to collapse
Jajajaj, that's right wipe data... sorry I was typing from memory.
Shiresp said:
Jajajaj, that's right wipe data... sorry I was typing from memory.
Click to expand...
Click to collapse
Thanks a lot! Really appreciate.
Shiresp said:
Twrp??? From github.. c1s model....
Click to expand...
Click to collapse
The tree was still WIP for official release, that's the reason for which it wasn't on XDA yet. I also see you didn't post any links to sources, neither credits whatsoever.
I opened a thread for Official TWRP here, with more instructions, FAQ and everything needed.
Regards
corsicanu said:
The tree was still WIP for official release, that's the reason for which it wasn't on XDA yet. I also see you didn't post any links to sources, neither credits whatsoever.
I opened a thread for Official TWRP here, with more instructions, FAQ and everything needed.
Regards
Click to expand...
Click to collapse
sorry,
I assumed that the sources we all knew are from github. Without the work of those people developing in the repositories, the compilation of the recovery would be impossible.
I have only compiled the recovery because I needed it personally for 4 n980f.