[UTILITY][10-18-2011] APK Manager for Mac OS X, Intel only, v1.2.1 - AT&T Samsung Galaxy Note I717

[UTILITY][10-18-2011] APK Manager for Mac OS X, Intel only, v1.2.1
This is from the more general Android Development section of XDA. I thought that some of you here may like it to work on mods for our NOTE's apps.
Original Thread: http://forum.xda-developers.com/showthread.php?t=1285130
s0niqu3 said:
{
"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"
}
So almost everyone here should be pretty familiar with android, and that means you've probably heard of (and maybe even used yourself) the windows tool APK Manager by fellow XDA member Daneshm90.
Earlier this year I started to port the current windows 4.9 version to mac using the outdated linux script for a base. And I had some early success at the time with simply using macports to install sox, optipng, etc. And then my computer crashed (double drive failure back in July) and I gave up for the time being. Recently though I was excited to find that someone else tried to do the same thing, XDA member MAD Industries released a very basic port for mac.
Sadly though, a quick diff of his script and the outdated linux version shows that its not much of a port at all. In fact there were only 9 changes, purely for MAD Industries to add his credit lines, and disable the options to optimize png images, and ogg files.
And so a couple of weeks ago I started working (once again) on my own port of APK Manager for Mac OS X.
Since I used the MAD Industries version originally for my base, I have kept his credit in the readme.txt, though to be honest, I've undone every single change he made, and changed virtually every line in the original linux script. And on top of that, I've written over 1700 new lines of code to not only bring this current to the windows feature set, but exceed it in many ways.
I've built in 32/64-bit architecture checking, and compiled and include the required missing binaries to re-enable optimizing png images and ogg files. I'm also including a .terminal file for easily configuring the default display, and a copy of my NEW favorite fixed-width font, Bitstream Vera Sans Mono.
And now some notes, and requests:
PLEASE note: this is currently INTEL only, but it supports both 32-bit and 64-bit all-in-one with architecture checking built-in to the script.
PLEASE note: if your computer is running OS X 10.7.X, "Lion" then it does not include a java runtime by default, please download it here first: http://support.apple.com/kb/DL1421
PLEASE note: due to the length of some of the strings used in the menus, etc., in order to not need to scroll your terminal window, you must adjust your default columns and rows settings. You can set this automatically by using the include "JocelynCustom.terminal" file, and you can also find simple instructions to set this yourself in the README.txt
PLEASE read the included readme for installation and very basic (for right now) usage instructions. I welcome any and all feedback on improvements for the readme file.
PLEASE report any and all bugs or generally wonky behavior, preferrably by posting here in this thread, or by posting a comment back on my blog.
LASTLY, please if you re-post this anywhere else, including blogs, other forums, etc. I would greatly appreciate if you would at least give me credit, and link back to my blog (http://girlintroverted.wordpress.com/) or at the very least, link back here to this post.
IMPORTANT: Starting with v0.9.7/RC1 I'm including an applescript setup applet. I've also changed some directory names, removed some old files, added new files and changed location of some files. Please backup your existing APKManager directory, then unzip and setup the new version. Once you verify that it works, then you can copy the CONTENTS of the following old directories, to the new ones.
place-apk-here-for-modding -> place-here-for-modding
place-apk-here-for-signing -> place-here-for-signing
place-here-to-batch-optimize -> place-here-to-batch-optimize
place-ogg-here -> place-ogg-here
projects -> projects
DO NOT COPY OVER THE CONTENTS OF THE "other" directory or the root directory unless you absolutely know what you're doing.
Download current version v1.2.1 here: http://www.mediafire.com/?29bosvufiiv66vl
Click to expand...
Click to collapse

Related

Ever wanted to know how you can use low-res (176*220) titles on your QVGA phone?

If you have a QVGA Smartphone like the HTC Vox / s710, you know well enough that most existing games and other graphics-based Smartphone apps (Windows Mobile 6 Standard) out there only use a postage-stamp sized screen area. An example of this is PDAMill’s Flux Challenge, which, being designed for the traditional low-res (176*220) Smartphone resolution, only uses part of the available QVGA screen estate:
{
"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"
}
There were no widely known solutions for the problem. Some developers announced support for QVGA devices (for example, that of Cell Doom – see announcement HERE), but the most (including PDAMill) didn’t.
Fortunately, an excellent White Russian coder has come up with a generic solution, which not only makes it possible to run MANY (but not all!) games at full screen, but, in cases, also lets for using real (!) QVGA resolution with some titles (for example, emulators).
Downloading, installing
Go to this MoDaCo thread and download the ZIP file attached to the first post. You’ll need to register as a forum user if you aren’t able to access it. If you don’t want to bother with it, I’ve also uploaded the file to my database back-end; it’s HERE.
After this, just unZIP it and start GxQvga Patcher.exe. Should you encounter an error message complaining about the lack of the .NET Framework 2, you will need to download it HERE (note that some stated it only requires 1.1. I haven’t checked whether they’re right. The latter is accessible HERE.)
Using
This patcher app runs on the desktop, NOT on the Smartphone. This means you must transfer the main EXE file of the game / emulator / app you’d like to make use of the QVGA screen to your desktop computer first. To do this, use for example Total Commander with the CE file system patch (see THIS for an explanation of installing it) or, if you don’t want to bother, just the “Explore” button of ActiveSync.
Transfer the main EXE files (but nothing else) of the apps / games you’d like to patch to the directory of where the above-mentioned, just decompressed GxQvga Patcher.exe resides.
Now, start GxQvga Patcher.exe. It will present you a dialog:
In there, click “Select exe file to patch...". Now, select the EXE file you’d like to patch:
After letting it go on, you’ll be presented a message telling you the patching was successful:
Now, all you need to do is:
Copy the patched EXE file back to your MS Smartphone, making sure you overwrite the original EXE file
Go to the QVGA subdirectory on your desktop (just under the directory where GxQvga Patcher.exe resides), and copy XG.dll to the same directory on your smartphone
Start the game / app to see whether it worked; answer Yes to the message.
If the game / app still only uses 176*220 (and not the full screen), exit it and go to the SCALE (NOT the previous QVGA!) subdirectory on your desktop, and copy XG.dll to the same directory on your smartphone and copy XG.dll to the smartphone, making sure you overwrite the previously copied QVGA XG.dll. Now, start the game on your Smartphone. Hope it’ll use the full screen. If it still doesn’t do this, then, nothing can help, I’m afraid.
Examples of the before-after cases
PocketHobbitSP2003 (as of the current, Alpha 11 version) doesn’t support QVGA devices. As can be seen in the following screenshot, without patching, it only uses a stamp-size screen area in Portrait mode on QVGA devices:
http://www.winmobiletech.com/062007C64Emus/c64EmuDefaultStamp.bmp.png
After the patch and using the QVGA DLL, it becomes much bigger and, what is even more important, makes use of the full horizontal screen reoslution – that is, 240 pixels, resulting in MUCH more readable text:
http://www.winmobiletech.com/062007C64Emus/PatchedSEQVGAP.bmp.png
Incidentally, with the SCALE DLL, it also fills in the entire screen horizontally, BUT only upscaling the original, 176*132 rendition resulting in a MUCH inferiour real resolution & readability:
http://www.winmobiletech.com/062007C64Emus/PatchedSPVersionScaleDLLQVGAPortrait.bmp.png
This is why I’ve emphasized you MUST give a try to the QVGA DLL first and only give a try to the SCALE one when the former doesn’t deliver any results.
Recommended link
This MoDaCo thread discusses the converter at length. A MUST!

Ever wanted to know how you can use low-res (176*220) titles on your QVGA phone?

If you have a QVGA Smartphone like the HTC Vox / s710, you know well enough that most existing games and other graphics-based Smartphone apps (Windows Mobile 6 Standard) out there only use a postage-stamp sized screen area. An example of this is PDAMill’s Flux Challenge, which, being designed for the traditional low-res (176*220) Smartphone resolution, only uses part of the available QVGA screen estate:
{
"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"
}
There were no widely known solutions for the problem. Some developers announced support for QVGA devices (for example, that of Cell Doom – see announcement HERE), but the most (including PDAMill) didn’t.
Fortunately, an excellent White Russian coder has come up with a generic solution, which not only makes it possible to run MANY (but not all!) games at full screen, but, in cases, also lets for using real (!) QVGA resolution with some titles (for example, emulators).
Downloading, installing
Go to this MoDaCo thread and download the ZIP file attached to the first post. You’ll need to register as a forum user if you aren’t able to access it. If you don’t want to bother with it, I’ve also uploaded the file to my database back-end; it’s HERE.
After this, just unZIP it and start GxQvga Patcher.exe. Should you encounter an error message complaining about the lack of the .NET Framework 2, you will need to download it HERE (note that some stated it only requires 1.1. I haven’t checked whether they’re right. The latter is accessible HERE.)
Using
This patcher app runs on the desktop, NOT on the Smartphone. This means you must transfer the main EXE file of the game / emulator / app you’d like to make use of the QVGA screen to your desktop computer first. To do this, use for example Total Commander with the CE file system patch (see THIS for an explanation of installing it) or, if you don’t want to bother, just the “Explore” button of ActiveSync.
Transfer the main EXE files (but nothing else) of the apps / games you’d like to patch to the directory of where the above-mentioned, just decompressed GxQvga Patcher.exe resides.
Now, start GxQvga Patcher.exe. It will present you a dialog:
In there, click “Select exe file to patch...". Now, select the EXE file you’d like to patch:
After letting it go on, you’ll be presented a message telling you the patching was successful:
Now, all you need to do is:
Copy the patched EXE file back to your MS Smartphone, making sure you overwrite the original EXE file
Go to the QVGA subdirectory on your desktop (just under the directory where GxQvga Patcher.exe resides), and copy XG.dll to the same directory on your smartphone
Start the game / app to see whether it worked; answer Yes to the message.
If the game / app still only uses 176*220 (and not the full screen), exit it and go to the SCALE (NOT the previous QVGA!) subdirectory on your desktop, and copy XG.dll to the same directory on your smartphone and copy XG.dll to the smartphone, making sure you overwrite the previously copied QVGA XG.dll. Now, start the game on your Smartphone. Hope it’ll use the full screen. If it still doesn’t do this, then, nothing can help, I’m afraid.
Examples of the before-after cases
PocketHobbitSP2003 (as of the current, Alpha 11 version) doesn’t support QVGA devices. As can be seen in the following screenshot, without patching, it only uses a stamp-size screen area in Portrait mode on QVGA devices:
http://www.winmobiletech.com/062007C64Emus/c64EmuDefaultStamp.bmp.png
After the patch and using the QVGA DLL, it becomes much bigger and, what is even more important, makes use of the full horizontal screen reoslution – that is, 240 pixels, resulting in MUCH more readable text:
http://www.winmobiletech.com/062007C64Emus/PatchedSEQVGAP.bmp.png
Incidentally, with the SCALE DLL, it also fills in the entire screen horizontally, BUT only upscaling the original, 176*132 rendition resulting in a MUCH inferiour real resolution & readability:
http://www.winmobiletech.com/062007C64Emus/PatchedSPVersionScaleDLLQVGAPortrait.bmp.png
This is why I’ve emphasized you MUST give a try to the QVGA DLL first and only give a try to the SCALE one when the former doesn’t deliver any results.
Recommended link
This MoDaCo thread discusses the converter at length. A MUST!

[DEV] [REF] Splash Updater Utility - Modify source to add a GUI to any script!

Background
Here is a program a whipped up as a learning experience.
My goal was to demonstrate a way add a GUI to any batch script as a standalone EXE.
I did some research and found a small program developed by Dion Nicolaas called Wizard's Apprentice. This program uses a well-described and portable API to create a good user interface for most script languages (e.g. Perl, PHP, VB or batch). This is an old (2006) but effective program and I am sure there may be newer and/or better programs that could have been used.
Armed with...
close to zero experience with batch
the manual for Wizard's Apprentice
benjamminzIS's code from here
Bat To Exe Converter 1.6.0
a nifty website called google
and LOTS of trial and error
...I was able to make this program.
This project demonstrates that almost anyone can add a GUI to almost any script…and really that means the options are limitless. I am not going to write a guide on how to do this but I am releasing all my source code/files for anyone interested.
I encourage anyone to modify, repackage, repurpose or even continue developing this program as your own.
I require no credit and it is my hope that this program will be used as a base (or reference) that will stimulate more meaningful development.
All I ask is that if you are experienced with batch scripting that you do not make fun of my scripts (at least not to my face), which should be functional but are surely not the most advanced or efficient.
​Overview
This program will allow you to choose a 540 x 960 image file (e.g. jpg, png, bmp), convert it to a flashable format (.img), optionally save the converted file and/or flash the file to your phone.
All things considered this program is nothing to be too excited about except that it can be used as a base to add a GUI to other scripts.
This is and always will be a beta release and I plan to only release (at most) a couple of updates to fix any critical issues that are found.
I personally tested this on my device and found it to work perfectly but do your own research and please only use it at your own risk.
​Requirements
S-OFF w/ JB_HBOOT or ENG HBOOT
Windows PC (only)
USB Debugging Enabled
USB Cord
Common Sense
Download Links
--->suu_beta.exe<---
--->suu_dev_source.zip<---​​Screenshots
{
"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"
}
​Credits
Dion Nicolaas for creating Wizapp (wizapp.sourceforge.net)
Fabrice Bellard for creating FFmpeg (ffmpeg.org)
Pau Oliva/pof for creating NBIMG (code.google.com/p/htc-flasher)
benjamminzIS for his code (forum.xda-developers.com/showthread)
google for answering all of my questions, once I asked in the correct format (google.com)
reserved ....
i might have to S-OFF soon :/
dude, super sweet... I wish I had known about that tool in 06! haha...
benjamminzIS said:
dude, super sweet... I wish I had known about that tool in 06! haha...
Click to expand...
Click to collapse
Ben, thanks for code!
You know batch better than me, you could do much more with wizzapp than I have...it's a cool tool...very straight forward.
Sent from my HTC_Amaze_4G using Tapatalk 2
I am curious to hear some feedback from those (few) that downloaded this. Feedback?
Hey man.
I am very impressed by what you were able to do here. I have been trying to edit your source to make a GUI for my batch file but I cant get it to work right. The code looks nothing like normal batch to me.
What are you looking to do?
The the manual for Wizard's Apprentice is really helpful BUT it took me a lot of trial and error...it is not standard batch but pretty straightforward.
Works great!Super easyyyyyyyyyy!Thanks aloooooooooot!:good::good:
I have a batch script that roots the republic wireless defy xt. It is outdated now with the most recent update to the phone but I still wanted to test it with wizard apprentice.
Sent from my XT557 using Tapatalk 2
If you want send me the scripts and I will take a look.
Sent from my Nexus 7 using Tapatalk HD
krook6023 said:
If you want send me the scripts and I will take a look.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
That would be awesome if you could look at it for me and give me some pointers. I will pm you with the source.

HALF-ASSED ONEPLUS ONE TOOLKIT v1.0 BETA in Python - OSX, Linux, and Windows!

UPDATED!!!!!! 12/30/2014
i present to you the latest pre-release from vvn's secret underground laboratory.......
THE HALF-ASSED ONE PLUS ONE TOOLKIT v1.3.2 BETA!
{
"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"
}
STILL IN BETA TESTING. tested most functions on my macbook pro (running OSX mountain lion) and they all seem to be working. haven't tested the newer functions like flashing the newer stock ROM images (XNPH38R and XNPH44S) but theoretically they should work if the others do.
USE AT YOUR OWN RISK. i'm not responsible for anything that might happen to your device as a result of using the toolkit. i assume if you are able to make it far enough to install python, the android SDK, and run the script, then you've got a pretty good idea of what you're doing already. if you need help, send me a message.
requirements: python 2.7, android SDK, opotoolkit.py, opointro.py, pyadb.py
NOW ON GITHUB!!!!
to install and run using git:
git clone https://github.com/eudemonics/1plus1toolkit.git 1plus1toolkit
cd 1plus1toolkit
python opotoolkit.py
*you might need to run as root, and make sure to have USB debugging enabled*
GITHUB project link: https://github.com/eudemonics/1plus1toolkit
installation:
download and install python 2.7: https://www.python.org/downloads/
download and install android SDK: https://developer.android.com/sdk/
it should work with the adb and fastboot binaries provided in the ZIP, but if not, you should install the android SDK. i recommend even MORE that you create an environmental path variable to the android SDK so you can run the commands from any directory.
setting up an environmental path variable (optional - recommended):
if you're on windows you can go to my pastebin, find the only powershell script on there, and steal/adapt the code to create your own environment path variable. but it's much easier to configure in system properties - i'm not on windows right now so these may not be exact instructions, but you should be able to right click on "my computer", select "properties", go to the "environment" tab in system settings, and add the environment path there. linux and OSX users just need to add the android SDK directory to their ~/.bash_profile or ~/.bashsrc or wherever environment paths are defined. if you still don't understand environmental path variables or symbolic links, i highly recommend google (or startpage.com, the private version).
if you don't want to go to the trouble of creating the environmental path variables, and you want to use the android SDK on your computer, then just extract all the files from the ZIP into your android SDK directory.
how to run the toolkit:
plug phone to computer via USB, turn on android debugging.
open command prompt or terminal window to scripts directory. start toolkit by entering:
"python opotoolkit.py"
if everything is installed and in the right places, you should see a menu like the attached screenshot.
i'll continue working on it and adding more when i can so keep checking this space, as well as the pastebin links (i'll add to github eventually). everything's open source; use, share, steal whatever you want from the code. some credit would be nice, though.
not gonna ask for donations - if you'd like to donate, please do so by purchasing my EP:
buy it here: http://dreamcorp.bandcamp.com
or search for it on itunes, google play, amazon, spotify, last.fm, cdbaby, blah blah blah.
there are also links in the description for my music video
https://www.youtube.com/watch?v=2i-F4jiKtGg
RESERVED
THIS IS NOW ON GITHUB!
get the latest version from here:
https://github.com/eudemonics/1plus1toolkit
sorry i rarely ever log on to xda-developers, email or facebook me if you have any problems!
Reserved again
***space reserved***
create an app or another to unlock root
Hello everyone is there any good developer can create an app or another to unlock root permissions to OnePlus One? Me with the Oppo N1, I used only app. Unfortunately I have no problems to the PC, and with the usual methods can not. I would be very grateful.
cassyjack said:
Hello everyone is there any good developer can create an app or another to unlock root permissions to OnePlus One? Me with the Oppo N1, I used only app. Unfortunately I have no problems to the PC, and with the usual methods can not. I would be very grateful.
Click to expand...
Click to collapse
What was the point in bumping a thread that hasn't had a reply for over 3+ months?
cassyjack said:
Hello everyone is there any good developer can create an app or another to unlock root permissions to OnePlus One? Me with the Oppo N1, I used only app. Unfortunately I have no problems to the PC, and with the usual methods can not. I would be very grateful.
Click to expand...
Click to collapse
hi, you should be able to root with SuperSU (latest version 2.40) using my toolkit. let me know if you have any problems, since i haven't tested flashing the latest SuperSU yet.
zephiK said:
What was the point in bumping a thread that hasn't had a reply for over 3+ months?
Click to expand...
Click to collapse
my apologies - this is why i named it the half-assed oneplus one toolkit
Lol

[Tutorial] Build Your Personal Magisk ROM

Figured some adventurous soul might have fun with this.....​
Anyone who follows our thread in the development section of this forum probably has figured out that I am a huge fan of @topjohnwu and Magisk.
Our team maintains a Magisk ROM there. So I decided that I would try to show anyone interested how to make their own personal Magisk ROM that they can flash over the stock ROM provided by ZTE.
I'm not big on disclaimers. You flashed a custom recovery, Right?
This may or may not work on LOS based ROMs. I am an audiophile from way back, and I'm not gonna flash and test any of it until someone says," sound is fixed 100% " Not, "I can kinda get by w/ this or that".
It's why I bought the phone.
Attached to this post you will find two templates. ROM.zip, and badboyz.zip (I'm feeling lazy, didn't feel like messing w/ the updater script). Download them both, and unzip onto your desktop. Most of the editing will be done in the badboyz.zip. We will deal with that first. Here is what the file structure should look like:
{
"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"
}
In the first folder, \common, there is a file named post-fs-data.sh. This is where you put your build.prop edits. I have left two examples to demonstrate proper syntax. Note that:
Code:
persist.adb.notify=0
As it would normally appear in build.prop becomes
Code:
persist.adb.notify 0
Feel free delete the demonstrative entries when you are finished with your edits.
You also will find a \system folder. If you have an app you would like to add to your ROM as a system app, or a system app that you have edited, i.e. SystemUI or Settings this is the place. Magisk will overlay the apk included in the stock ROM. You can also add edited files to /etc, /media, etc. just make sure to maintain the proper file stucture
Next we move on to the config file:
1) Call it what you want w/ no spaces (you'll need this later)
2) Call it what you want- This prints out on the twrp screen when flashing the module
3) This is where you debloat. I left two examples in the template (as seen in the ss). Anything you don't want to run, show up in the drawer,or on all applications, list it here keeping the proper folder structure.
Again, these entries can be deleted. They are there for demonstrative purposes.
The module.prop file is pretty self explanatory (tbd= to be determined)
Do notice that the module id matches the one from the config file........(where I said you'll need this later)
You can change both of these. Just make them match.
The rest- you can put your mom's facebook page, donation link for the red cross- whatever you want
So all that is left is to zip all those files up, and your ROM module is done.
Now let's make a flashable. That Rom.zip that you decompressed-
Inside there is a data folder. Leave the Magisk.apk and the PHH su apk there. You will need those. Anything else you have that you want to add throw it in there. Teeter.apk, Netflix whatever.
Then put your rom module (should be named badboyz.zip) into the magisk folder w/ the magisk.zip.
Now zip the whole shabang up and flash it over a bone stock ROM w/ a stock kernel.
Please follow THIS guy and donate what you can. Android will be a better place w/ him
Reserved
Mine
Super info, thank you. Can Masquerade be integrated to allow Substratum theming?
HERE is some detail I have found, but I don't understand exactly what to do.
Is there a working nougat kernel for a2017G knocking around which patches for Safety net? The ones i found only worked with A2017U, so WiFi and a few other things don't work
H0lmEd said:
Is there a working nougat kernel for a2017G knocking around which patches for Safety net? The ones i found only worked with A2017U, so WiFi and a few other things don't work
Click to expand...
Click to collapse
This should work for whatever ROM/kernel you are currently on.
Thank you for this amazing post
Themed stock ROM?
amphi66 said:
Super info, thank you. Can Masquerade be integrated to allow Substratum theming?
HERE is some detail I have found, but I don't understand exactly what to do.
Click to expand...
Click to collapse
Maybe a bit late: this https://xtremetricks.net/theme-stock-android/ seems to indicate stock ROM can be themed with substratum. If that is so, then you could include substratum in your personal magisk ROM.
Will this work on any android phone?
Sent from my ASUS_I01WD using Tapatalk

Categories

Resources