Related
Just wondering if anyone else have seen GAPPS for tegra. I have downloaded the signed UPDATE and it works beautifully.
Really appreciate the XDA community for all the help.
http://www.megaupload.com/?d=KMXRDDR3
Thanks. I'll give it a try...
So far, no joy. I installed it, wiped cache, and now get FC's. I will try to work around it, but will probably have to go back to backup.
Good find, though.
flashed fine on cm6. lost sound though. not sure if that is because of this or because of something else. will report back after more research.
i even tried with the newer update 3316 and it works fine. The only problem i had was i updated to the newer market and it started crashing. i flashed 3316 and installed gapps and no problems.
One thing i have done differently though is to put the FRF91 key in the build props before install the GAPPS. It took couple of tries for the market to work properly.
Isn't this the original gapps that we've had for a month, now? I see the Htc stuff in there, which kind of tipped me off.
I actually pulled the Htc stuff and some other things out, back when I used it for TnT Lite.
Well the date signature seems to be recent so i guess it's possible.
roebeet said:
Isn't this the original gapps that we've had for a month, now? I see the Htc stuff in there, which kind of tipped me off.
I actually pulled the Htc stuff and some other things out, back when I used it for TnT Lite.
Click to expand...
Click to collapse
Not sure... but here is a link - they are all listed at the bottom of the page.
http://wiki.cyanogenmod.com/index.php?title=Latest_Version
The file name gives it away. 20101020 obviously means 20th October. So yeah, not new
umar.ranjha said:
i even tried with the newer update 3316 and it works fine. The only problem i had was i updated to the newer market and it started crashing. i flashed 3316 and installed gapps and no problems.
One thing i have done differently though is to put the FRF91 key in the build props before install the GAPPS. It took couple of tries for the market to work properly.
Click to expand...
Click to collapse
3316 + GAPPS work great! thanx!
didn't install the new Market but was able to do Market fix (w/o TI Backup)...
I'm sorry to sound like a noob, but I've searched and searched, and haven't been able to find an explanation. When I go to my phone info section (About phone), my phone is listed as a Galaxy Nexus, despite the fact that my phone is a Galaxy S3 (d2vzw). I'm not sure when this changed and I don't remember exactly what it used to say, but I know this was not it. I can't figure out if it was the ROM or the kernel that changed it (though I have my doubts it was the kernel).
I am using the AOKP rom and the KT747 kernel.
The only reason I noticed this is because I've been using the goomanager app to let me know when there have been updates to my ROM and to my surprise one day, I was notified that there was an update (even though I wasn't expecting one). I downloaded it (without even paying attention to the file name) and tried flashing it a few times, but it kept failing no matter what I did. I started to wonder if the recovery was the issue, so I took that opportunity to move from clockworkmod to TWRP. That did not change the outcome. I then decided to check the file itself by googling its file name and I was shocked to learn that it was for the Galaxy Nexus... not for the GS3! I finally went into About phone and noticed my phone was listed as a Galaxy Nexus.
As it stands now, I'm not sure if the reason it's listed wrong is because of me trying to flash the wrong ROM, or if it was like that beforehand. What I do know is that because it's listed wrong, goomanager keeps telling me there's an update to my ROM (and keeps pointing me to that original file I tried flashing).
I only recently flashed a different kernel than what came with the phone and I believe this was after the name was already wrong, so I doubt that's to blame. To be safe, I tried installing a different kernel (I think it was called "Lean" kernel), but that ended up preventing my phone from ever booting (seriously, I waited about an hour and even tried rebooting, but it never actually booted), so I ended up reflashing the KT747 kernel and it's working again.
Any idea as to why this is happening? Is there a way to fix this? Other than the fact that goomanager keeps looking for the wrong updates, is it bad for my phone?
Thanks in advance!
You can modify the build.prop to make your phone think its anything. So the ROM has a nexus written in the build.prop. are you using an unofficial build or the official one for our phone?
Also it really doesn't matter that it is listed as a nexus. Just disable goo manager updates. And then you will ha e to manually check for d2vzw updates. There is nothing to worry about. As far as lean kernel not booting. Be sure to use the right kernel (aosp or stock) and if your using the 4.2 version of AOKP you need the new 4.2 kernel, which I am personally unfamiliar with lean if it has a 4.2 kernel
Sent from my SCH-I535 using Tapatalk 2
faehsemc said:
You can modify the build.prop to make your phone think its anything. So the ROM has a nexus written in the build.prop. are you using an unofficial build or the official one for our phone?
Click to expand...
Click to collapse
I'm using the official Milestone build released on 2012-10-29. I know it wasn't changed in the builds prior to that because goomanager was always able to point me to the next, correct update. If they did change the build.prop for that release, what would have been the point?
faehsemc said:
Also it really doesn't matter that it is listed as a nexus. Just disable goo manager updates. And then you will ha e to manually check for d2vzw updates.
Click to expand...
Click to collapse
Well, you're right except that it kind of does matter if goomanager is no longer able to find the right updates. I know I can disable the checks, but I don't want to have to remember to check manually.
faehsemc said:
As far as lean kernel not booting. Be sure to use the right kernel (aosp or stock) and if your using the 4.2 version of AOKP you need the new 4.2 kernel, which I am personally unfamiliar with lean if it has a 4.2 kernel
Click to expand...
Click to collapse
I thought I had checked to make sure it was an aosp version and not touchwiz, but now I don't remember. The Milestone build of AOKP I'm on is 4.1.2.
I wanna say getting google wallet working you have to edit the device in the build.prop? Or is that on TW roms?
x714x said:
I wanna say getting google wallet working you have to edit the device in the build.prop? Or is that on TW roms?
Click to expand...
Click to collapse
Oh wow, I think you just answered my question. Thank you. I do have Google Wallet on my phone, but I installed it using an app called Wallet Installer, so I didn't actually change it myself.
JerseyMike4 said:
Oh wow, I think you just answered my question. Thank you. I do have Google Wallet on my phone, but I installed it using an app called Wallet Installer, so I didn't actually change it myself.
Click to expand...
Click to collapse
Ya then thats why it changed
Right after my last post, I opened the Wallet Installer app and saw that there's a button to restore build.prop, so I pressed it and my phone rebooted. Afterwards, it was back to normal. What's odd is that Google Wallet appears to still work properly (I think; all I've ever done is add a credit card). I guess it only needs to change it for it to install.
Hi everyone, really sorry if someone has asked this before, but I looked through the forums and couldn't find much pertaining to my problem.
I installed LiquidSmooth 4.2.1 for my I535 Galaxy S3 on Verizon, and it loaded, but I noticed my appstore was gone, preventing me from installing Titanium to get all my apps back.
I googled it and that told me to install Gaaps. So I reflashed the stock ROM, and then installed Gaaps. When I did, every Google related app crashed simultaneously, making the phone near unusable. I figured I'd just reflash the stock image again, and that seemed to fix the problem. Is there anything else I should do, in case something goes wrong?
I have a feeling I might have used the wrong Gaaps? Is there a certain place I'm supposed to look as mentioned here? In that same thread, it looks like the dev doesn't even want to answer where to get the gaaps.
Again, I'm sorry if the answer is obvious, but I am having a little trouble here.
why are you trying to install an inferior dated version?
go here
http://forum.xda-developers.com/showthread.php?t=2148261
and do the latest build.
the google apps are right under the download button in the OP.
ddurandSGS3 said:
why are you trying to install an inferior dated version?
go here
http://forum.xda-developers.com/showthread.php?t=2148261
and do the latest build.
the google apps are right under the download button in the OP.
Click to expand...
Click to collapse
I saw that one, and noticed i535 wasn't one of the options listed. Do I just use d2vzw?
levelxplane said:
I saw that one, and noticed i535 wasn't one of the options listed. Do I just use d2vzw?
Click to expand...
Click to collapse
yes.
Always make sure to flash a Gapps package when flashing a ROM, unless otherwise specified. Also, when flashing a Gapps package make sure that you flash a gapps package that is compatible with whichever variant phone you are using, in your case d2vzw as well as compatible with the ROM, i.e. if flashing a 4.2.2 ROM make sure you flash the compatible gapps package. Doing an extra 10 minutes of research can save you hours of headaches.
levelxplane said:
Hi everyone, really sorry if someone has asked this before, but I looked through the forums and couldn't find much pertaining to my problem.
I installed LiquidSmooth 4.2.1 for my I535 Galaxy S3 on Verizon, and it loaded, but I noticed my appstore was gone, preventing me from installing Titanium to get all my apps back.
I googled it and that told me to install Gaaps. So I reflashed the stock ROM, and then installed Gaaps. When I did, every Google related app crashed simultaneously, making the phone near unusable. I figured I'd just reflash the stock image again, and that seemed to fix the problem. Is there anything else I should do, in case something goes wrong?
I have a feeling I might have used the wrong Gaaps? Is there a certain place I'm supposed to look as mentioned here? In that same thread, it looks like the dev doesn't even want to answer where to get the gaaps.
Again, I'm sorry if the answer is obvious, but I am having a little trouble here.
Click to expand...
Click to collapse
If you flash another AOSP ROM the newest Gapps is from 3/1/2013
---------- Post added at 06:41 AM ---------- Previous post was at 06:36 AM ----------
mcdevil58 said:
If you flash another AOSP ROM the newest Gapps is from 3/1/2013
Click to expand...
Click to collapse
http://goo.im/gapps/gapps-jb-20130301-signed.zip
Setup Wizard Unfortunately Failed
I just installed the LiquidSmooth Rom and Gapps zips. I reboot phone and i get the "Unfortunately Setup Wizard has stopped" any help?
I am kinda new at this so some guidance will be appreciated.
liquid 4.2.2
why not try liquid 4.2.2
why not
brandoncarlson33 said:
why not try liquid 4.2.2
Click to expand...
Click to collapse
I second that recommendation. So smooth. Almost nothing wrong with it. (There has to be something, just not found it yet).
awesome
kevcuas said:
I second that recommendation. So smooth. Almost nothing wrong with it. (There has to be something, just not found it yet).
Click to expand...
Click to collapse
liquid smooth 2.1 stable is the bomb no issues except the sound icon but who cares other than that its prefect
Hey guys,
So here is a straight from source build of Android L, 5.0. I have not done anything beside build it from source and flash it. I have not done extensive testing on it.
So anyways, here is the link:
http://d-h.st/zi0
I have not included gapps or anything else. They will be coming soon. This build is primarily to play around with. I would not consider this a daily driver.
Issues:
Probably a ton, seeing as I have only checked if it boots.
I am not responsible for any issues this may cause or anything else that may happen to your tablet as a result of this.
I also have a ton of schoolwork and other things that keep popping up, so my support may be iffy. Please bear with me or go back to 4.4.4.
Here is a screenshot for proof:
https://www.dropbox.com/s/lnmhdapeemskggi/1743495_10153594576754572_4551962379003400239_n.jpg?dl=0
Future Plans for this Rom:
GApps are not yet possible on Lollipop as far as I can work out, due to the fact that baksmali and smali do not appear to play nicely with ART odex files. I will be rebuild the rom to be odexed and then including a gapps package.
XDA:DevDB Information
[Android 5.0] Straight from source ROM, ROM for the Nexus 7
Contributors
MidnightNinja
Version Information
Status: Testing
Created 2014-11-05
Last Updated 2014-11-04
Tried to adb side load and am getting No OS error. Will restore and try again on device
Sent from my A0001 using XDA Free mobile app
cchant said:
Tried to adb side load and am getting No OS error. Will restore and try again on device
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Hmm..let me know if you still have issues, because I was able to sideload on my device
Awesome!!
When first booted you need to erase it because it is encrypted. But after that it works (for now) like a charm. Wifi working, sound working.
The only problem so far is that after I installed the Play Store it didn't want to open but the Amazon app store works fine.
Niekhout02 said:
When first booted you need to erase it because it is encrypted. But after that it works (for now) like a charm. Wifi working, sound working.
The only problem so far is that after I installed the Play Store it didn't want to open but the Amazon app store works fine.
Click to expand...
Click to collapse
I am missing alot of the google stuff, which is probably why none of that works
That will come shortly, I just need to redo a lot of my vendor files and such to get gapps to be built in.
It worked even though it said no OS
first boot takes awhile but it works!
Confirmed it works.
Sideloading gapps for cyanogenmod 11 and hoping they auto update does not work. Worth a shot though. Time to reflash.
Woah, thanks a lot
Btw, how do I sideload gapps? (especially play store)
Since I think it won't be just installing apk, isn't it?
Working great! I think performance is even better than kitkat
Wi-Fi also working (maybe bluetooth, nfc and gps too)
StardustGeass said:
Woah, thanks a lot
Btw, how do I sideload gapps? (especially play store)
Since I think it won't be just installing apk, isn't it?
Click to expand...
Click to collapse
Flashing GApps is the solution. Sadly, there isn't a package for Lollipop GApps yet.
tatazeuz said:
Flashing GApps is the solution. Sadly, there isn't a package for Lollipop GApps yet.
Click to expand...
Click to collapse
I am currently working on the gapps, right now i have fixed my own build process and am getting a nexus 9 dump to try and fix it up.
MidnightNinja said:
I am currently working on the gapps, right now i have fixed my own build process and am getting a nexus 9 dump to try and fix it up.
Click to expand...
Click to collapse
Yay!
Works great, now waiting for gapps
thanks
Gapps mostly work fine if you edit updater.script
I've only had issue with the keyboard crashing so I'd suggest removing it from the gapps package before flashing.
Woah
I can't wait for the final version, this one, using 4.4.4 binaries, is crazy smooth. Google outdid theirselves on the optimization department.
Awesome work, think im gonna givebthis a try atbwork tomorrow.
What does work and what doesn't
basuraunak said:
What does work and what doesn't
Click to expand...
Click to collapse
So far, everything seems to be working. Have to check camera yet though.
I cant seem to get much else to go with it, but I will share my findings.
I can get TWRP to install,but then I get a bootloop.
If you use the Nexus Root Toolkit v 1.9.3 and "Root" with custom recovery checked. It freezes after trying to temporarily boot the modified boot image.
Hard reset the tablet and boot normally. The toolkit should reboot your tablet back into the bootloader and into TWRP, but this is only good for one boot.
If you mount /system and run a fix permissions, then it stays installed, but never gets past the boot screen.
It boots far enough to get into ADB.
Not sure what to try next though...
I was thinking if we could get a flashable zip without the stock recovery, then we may be able to keep TWRP, but I am not familiarwith building the flashable zips.
Wait, So how do you flash the google play services after you lose TWRP?! I don't understand..
If the following table is correct then I have a GT-N8013. I'm running KitKat 4.4.2 on it: (N8010XXUDNE4_N8010BTUDNF1_BTU_N8013.tar.md5).
How close can one get to the latest version of Android and still have a working GT-N8013?
GT-N8000 - Wifi+3G+calling
GT-N8005 - Wifi+3G
GT-N8010 - Wifi (Except USA)
GT-N8013 - Wifi (Only USA)
GT-N8020 - Wifi+LTE
KK 4.4.2 is the last release from Samsung .
Android then see your models custom rom section .
JJEgan said:
KK 4.4.2 is the last release from Samsung .
Android then see your models custom rom section .
Click to expand...
Click to collapse
I've just picked up a used 10.1 (first edition) and am hoping to get it onto 5.1.1 or 6.01.
I see a custom CM ROM from Cyanogen, that states it's 6.0 official, but when I go to the site the release is really old for the 8013, and I'm not sure if it's been grouped in with the more recent beta group that is linked in the thread or if it's not.
I also see an older Cyanogen thread for 12, but that's pre 6.0 and appears to be somewhat abandoned.
My Note 3 is on phronesis 6.0.1, and I would like to get the Note 10.1 to as close to that as possible, without dealing with any major bugs.
Thank you for your assistance.
Some progress.
I managed to update mine to Marshmallow 6.0.1 (cm-13.0-20160523-UNOFFICIAL-n8013.zip) via CWM v6.0.3.6 but Google Apps keeps crashing.
I've tried both open_gapps-arm-6.0-nano-20160721.zip (Open GApps) and gapps-600-base-20151107-1-signed.zip. Both take hours to install and just keep crashing whenever you try to do anything.
Anyone have any luck getting cm-13.0-20160523-UNOFFICIAL-n8013.zip / and GApps.zip working?
Basil Rathbone said:
I managed to update mine to Marshmallow 6.0.1 (cm-13.0-20160523-UNOFFICIAL-n8013.zip) via CWM v6.0.3.6 but Google Apps keeps crashing.
I've tried both open_gapps-arm-6.0-nano-20160721.zip (Open GApps) and gapps-600-base-20151107-1-signed.zip. Both take hours to install and just keep crashing whenever you try to do anything.
Anyone have any luck getting cm-13.0-20160523-UNOFFICIAL-n8013.zip / and GApps.zip working?
Click to expand...
Click to collapse
I had it crashing initially too, with CM-13.
I reinstalled the ROM, root, twrp, everything. I also made sure to install the latest "Stock" Gapps, before rebooting once the ROM was in place. Since then I have not had any issues.
I did however have some issues using the nano package. Hope that helps.
Still no joy
I still can't get CM-13 to work. I use CWM. I made sure I was using the latest CWM 6.0.4.6.
I booted into CWM, factory reset and cleared cache. Flashed cm-13.0-20160523-UNOFFICIAL-n8013.zip.
I then factory reset and cleared cache again and flashed gapps-600-base-20151107-1-signed.zip.
I then factory reset and cleared cache again and rebooted.
No joy.
What actual gApps and CM-13 did you use? Maybe I need to use the same version of TWRP as you used?
I'm stumped.
--------------------------------------------------------------------------------
bladebarrier said:
I had it crashing initially too, with CM-13.
I reinstalled the ROM, root, twrp, everything. I also made sure to install the latest "Stock" Gapps, before rebooting once the ROM was in place. Since then I have not had any issues.
I did however have some issues using the nano package. Hope that helps.
Click to expand...
Click to collapse
Basil Rathbone said:
I still can't get CM-13 to work. I use CWM. I made sure I was using the latest CWM 6.0.4.6.
I booted into CWM, factory reset and cleared cache. Flashed cm-13.0-20160523-UNOFFICIAL-n8013.zip.
I then factory reset and cleared cache again and flashed gapps-600-base-20151107-1-signed.zip.
I then factory reset and cleared cache again and rebooted.
No joy.
What actual gApps and CM-13 did you use? Maybe I need to use the same version of TWRP as you used?
I'm stumped.
--------------------------------------------------------------------------------
Click to expand...
Click to collapse
I used the ARM 6.0 Stock version for CM 13. http://wiki.cyanogenmod.org/w/Google_Apps#Downloads
I ended up swapping to the 2014 model because I got a good deal on a Verizon version (which is locked but oh well), so I don't recall the TWRP that I ran. It sounds like that sometimes gives people issues.
I do recall that using the nano version of gapps was not working for me. Could be a coincidence, but I had constant crashes when I tried using it.
This is the thread I used to grab the ROM and TWRP: http://forum.xda-developers.com/galaxy-note-10-1/development/rom-lollipop-t3269375
It helps to read the installation notes properly
The problem(s) I was having were resolved by using twrp-2.8.7.0-gt-n8013 instead of N8013-CWM-Touch-6.04.6. I also used open_gapps-arm-6.0-stock-20160803 instead of nano but I really think it was TWRP that made everything work.
I'm now running cm-13.0-20160523-UNOFFICIAL-n8013 without any problems.
I consider this thread closed.
Basil Rathbone said:
If the following table is correct then I have a GT-N8013. I'm running KitKat 4.4.2 on it: (N8010XXUDNE4_N8010BTUDNF1_BTU_N8013.tar.md5).
How close can one get to the latest version of Android and still have a working GT-N8013?
GT-N8000 - Wifi+3G+calling
GT-N8005 - Wifi+3G
GT-N8010 - Wifi (Except USA)
GT-N8013 - Wifi (Only USA)
GT-N8020 - Wifi+LTE
Click to expand...
Click to collapse
How did you get KitKat on n8013. It was never released and no one successfully flashed 4.4 n8010 to n8013. Odin keeps giving an error. Please I've been trying for years now since it's been 2 years since update was released and doesn't look like it'll ever release (**** yoi Samsung with your update **** and regions)
Anyone have any luck? I've had this tablet since 2013 and I stopped using it because it has always been such a laggy sluggish experience. I thought I would try putting an AOSP ROM on it to see if that helped. Everything is so old for this device that it's nearly impossible to find the old files, ROMs, recoverys, etc. I can't even get TWRP or CWM to work on it. Maybe it's not worth the trouble anymore.
MrAwesome75 said:
Anyone have any luck? I've had this tablet since 2013 and I stopped using it because it has always been such a laggy sluggish experience. I thought I would try putting an AOSP ROM on it to see if that helped. Everything is so old for this device that it's nearly impossible to find the old files, ROMs, recoverys, etc. I can't even get TWRP or CWM to work on it. Maybe it's not worth the trouble anymore.
Click to expand...
Click to collapse
Well official only kitkat if you are international (Samsung decided not to release a lot of device updates in the us for kit kat including the s3, galaxy light, and this one). However I think you can get CM 13.1, idk about anything more recent but there is a (slightly) active community for it still left. Its a shame that this flagship tablet was neglected. I hope it doesn't happen with future Samsung ones but I've avoided buying any. I still use mine on jellybean for basic internet browsing and games
zMrAwesome75 said:
Quote:
Anyone have any luck? I've had this tablet since 2013 and I stopped using it because it has always been such a laggy sluggish experience. I thought I would try putting an AOSP ROM on it to see if that helped. Everything is so old for this device that it's nearly impossible to find the old files, ROMs, recoverys, etc. I can't even get TWRP or CWM to work on it. Maybe it's not worth the trouble anymore.
Click to expand...
Click to collapse
Not sure if you're still looking but I just installed Android Nougat v7.1.2 using the instructions provided here:
https://forum.xda-developers.com/showthread.php?t=2185119
I have a N8010 that topped out at 4.1.2. I flashed to a N8013 kernel/rom about 2 years ago which maxed out at 4.2.2 . I just recently found that link to the LineageOS build (Formerly Cyanogenmod) when I was contemplating buying a new tablet. The tablet was getting a bit sluggish so I decided to go ahead and blast it out and see what happened. I was VERY pleasantly surprised! Had some issues getting the Recovery flashed but once I did, it was pretty smooth from there. I had backed up all the apps so once I got it booted and restored all the apps, I was surprised how responsive it is. Oh, and you can say goodbye to all those SD card issues that the Note 10.1 had since this version of Android integrates the external SD with the internal SD so everything gets installed on the external card. No need for apps like folder mount, etc.
I highly recommend it. The only issue is that you lose the integrated S-Pen functionality but you can reinstall some of those apps from the play store and bring back a lot of those features. Some 3rd party apps actually work better.
Good luck!
7.1.2 on GT-N80013
I am currently running an unoffical build I picked up here on xda it is an unofficial Lineage OS build. I haven't currently found any bugs... camera works, bluetooth works, wifi works... at least for me. The build number is 14.1-20170810-unnofficial-n8013
Hannover2k said:
Not sure if you're still looking but I just installed Android Nougat v7.1.2 using the instructions provided here:
https://forum.xda-developers.com/showthread.php?t=2185119
I have a N8010 that topped out at 4.1.2. I flashed to a N8013 kernel/rom about 2 years ago which maxed out at 4.2.2 . I just recently found that link to the LineageOS build (Formerly Cyanogenmod) when I was contemplating buying a new tablet. The tablet was getting a bit sluggish so I decided to go ahead and blast it out and see what happened. I was VERY pleasantly surprised! Had some issues getting the Recovery flashed but once I did, it was pretty smooth from there. I had backed up all the apps so once I got it booted and restored all the apps, I was surprised how responsive it is. Oh, and you can say goodbye to all those SD card issues that the Note 10.1 had since this version of Android integrates the external SD with the internal SD so everything gets installed on the external card. No need for apps like folder mount, etc.
I highly recommend it. The only issue is that you lose the integrated S-Pen functionality but you can reinstall some of those apps from the play store and bring back a lot of those features. Some 3rd party apps actually work better.
Good luck!
Click to expand...
Click to collapse
I'd appreciate a link to the rom you installed. Thx.
I'm interested as well I'm still running original os. Also wondering if the rom update works well on these tablets since they are older. As Android matures the os gets bigger which can impact performance on older CPUs.
cloves said:
I'm interested as well I'm still running original os. Also wondering if the rom update works well on these tablets since they are older. As Android matures the os gets bigger which can impact performance on older CPUs.
Click to expand...
Click to collapse
I recently installed Lineage OS 14 and it is working great.
Tablet is stable, everything works, great battery life.
All devices work gps, etc...
The s-pen will not work like it did stock but there are apps you can get that seem to work better
Squid and Sketch for drawing....squid seems cool if you write with stylus
Install Magisk instead of supersu.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445