Related
Android System app Installer
I present you an window application to install System app in a very useful way...
Benefits:
1. No need to reboot your phone after installing system app
2. Simple User Interface easy to use
3. Small and fast
4.You can restore to previous app
5. Delete/Uninstall System app
6. Install Normal apps in single click
Requirements:
1. Any windows PC
2. ROOT
Screenshots:
Instructions:
1. Extract using any zip extractor (winzip, winrar, 7zip)
2. Open SystemAppInstaller.jar
3. Connect your phone to PC (make sure USB Debugging in ON)
4. Browse App to install
5.Click Install
6. To restore select again app (if not selected) and click restore
7. To uninstall apps click on uninstall> it will list all apps in system/app> type a name (eg:LuckyPatcher_2.9.5.apk) and press enter
8. Press 'Y' to delete more apps or 'N' to exits
Link:
System app Installer (v5)
Changelog on post#2
Hit thanks if you like my work
Changelog:
29/05/2013 (v1) -- Initial release
30/05/2013 (v2) -- Added Uninstall app option and small bug fixes
31/05/2013 (v3) -- Changed UI, Now you can install or restore more than one app at a time
09/06/2013 (v4) -- Option added to install apk as Normal or System app
04/09/2013 (v5) -- Redefined UI
Bat execution of file inside app no cmd dialog will open
Log window added and save log option
Lot of Bug fixes
Hit thanks if you like my work
[/SIZE]
Nice work bro..
Can you add a feature to uninstall a system app as well...??
karthiks.840 said:
Nice work bro..
Can you add a feature to uninstall a system app as well...??
Click to expand...
Click to collapse
Sure started working on it :silly:
System apk Installer [Updated] 30/05/2013
Updated to v2
-- Small bug fixes and added uninstall app support on request
System app Installer v3 [UPDATED]31/05/2013
v3 Uploaded
31/05/2013 --
1. Changed UI
2. Now you can install or restore more than one app at a time (batch app install)
Good job!
System app Installer v4 [UPDATED] 09/06/2013
Updated to v4......
09/06/2013 -- Option added to install apk as Normal or System app
See Screenshot on OP
awsme good work
thanks for this nice tool :good:
but I only can install one apk,
after this I get errors if I try a new one,
only works when I unplug my device and start from beginning with choice of apk and the plug the Handy again to pc
is this normal or do I something wrong
greetins
hara
04/09/2013 (v5) -- Redefined UI
Bat execution of file inside app no cmd dialog will open
Log window added and save log option
Lot of Bug fixes
New gapps are available.
Changelog:
update several libs
native google camera support (no need to flash the compatibility fix nor the addons photosphere package anymore)
update GoogleTTS
include GoogleEars in AIO package again
Note: YouTube remains the same. If you want to keep TRDS do not update over PlayStore. Our YouTube update will follow on next weekly.
Downloads: www.slimroms.net
OTA Updates
A useful tool to help ROM developers provide OTA updates to their users. It's free to use and you can build from source or use the APKs provided.
Screenshots
Holo
{
"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"
}
Material
More on the screenshots tab
Features
OTA Updates for your ROM
Addition file listings for your ROM
Background checking for updates
Flashing automatically using OpenRecoveryScript (found in settings)
Holo light and dark theme (4.0-4.4.4)
Material light and dark Theme (5.0+)
Self host your files and manifest or integrate with RomHut.com
OTA App updates on Google Play Store to save you time, effort and energy
Requirements
Root - not essential, but you will most likely have this anyway
A place to store a static manifest xmls. Dropbox will work fine, and any web server, or RomHut.
Some build.prop entries
Download
You can download the APKs here: http://ultimarom.com/downloads/ota-updates/
You can find the source here: https://github.com/MatthewBooth/OTAUpdates
Changelog
v2.5.3
10th August 2015
Fixed the Addons page crashing. This only affected RomHut users... but the fix will affect users who's developers manually host their ROMs. I'm knee deep in the middle of work and a rewrite that will resolve these kinds of issues for good.
Fixed the OpenREcoveryScript InstallAfterFlash generation so that it generates properly and will install files as intended
Stripped whitespace from the OTA Urls just in case developers put some in there (they shouldn't, but it's happening :| )
v2.5.2
11th July 2015
Fixed download location bug
v2.5.1
29th June 2015
Fixed a serious FC when a ROM didn't have a default theme set in the build.prop (so, most people).
v2.5
29th June 2015
Fixed downloading from HTTP only links for manual users
Added the parsing of the download link's host and showing it in the available update activity screen
Fixed my own donation links always showing Coinbase!
Added the choosing of download location by developers (see the XDA thread instructions for this)
Added the ability for developers to choose the default theme (also see the XDA thread for this)
Changed the available update activity page to show the full download file title without stripping spaces
Fixed some more NullPointerExceptions for various methods
Used version name rather than filename for available update activity
Fixed the generation of ORS (@nicholaschum)
Added Pro/Donate button to the settings. This does nothing (Currently) just a donate button, but in future this will add some nice things for those who buy it and support development.
Added showing the current storage location in preferences to show users where downloads will go. Later this will be changed to allow users to change the download location
Code:
[COLOR="#ff4444"]v2.4.5[/COLOR]
[COLOR="#ff4444"]14th June 2015[/COLOR][LIST]
[*] Fixed the downloading location bug. Sorry about that.
[*] Moved the open recovery script information above the settings
[*] Removed some unused code and optimised others
[*] Fixed InstallAfterFlash location
[*] moved About/Info into settings[/LIST]
[COLOR="#ff4444"]v2.4.4[/COLOR]
[COLOR="#ff4444"]13th June 2015[/COLOR][LIST]
[*] Fixed some null pointer exceptions that had been showing in Google Play Developer console
[*] Fixed BitCoin always being chosen as developer donation, if available[/LIST][COLOR="#ff4444"]v2.4.3[/COLOR]
[COLOR="#ff4444"]11th June 2015[/COLOR][LIST]
[*] Change the way the file directories are created
[*] Hopefully stop this IllegalStateException that's showing in the crash
reports.
[*] Fix NPE on download progress bar in MainActivity
[*] OTA Dir path correction
[*] Fix NPE in AvailableActivity when setting up progress bars and text
color
[*] Catch NPE related to Google Play Services and ads
[*] Check for null values when checking for connectivity
[*] Fixed another NPE with the Addons List view[/LIST]
[COLOR="#ff4444"]v2.4[/COLOR]
[COLOR="#ff4444"]26th May 2015[/COLOR][LIST]
[*] Added first run message to inform about new features
[*] Fixed Open Recovery Script on non-AOSP ROMs. Should now work properly
[*] Added "install after ROM functionality" - Put zips inside "/sdcard/OTAUpdates/InstallAfterFlash/" and they will be automatically flashed after an update, if using Open Recovery Script
[*] Added delete confirmation on addons
[*] Change default download directories. Now they go into /sdcard/OTAUpdates
[*] Translations for Italian and Russian
[*] Added AOSP makefile functionality for AOSP ROMs built form source
[*] Open Recovery Script is now on by default[/LIST]
[COLOR="#ff4444"]2.3.1 - 15th March 2015[/COLOR][LIST]
[*] Updated to target/be compatible with Android 5.1
[*] Show a warning dialog when trying to download an addon on a mobile network
[*] Show a button on the network warning dialogs to take you to settings and adjust if need be
[*] Card layout in the About activity
[*] Changelog viewing (for this app) in the About activity
[*] Removed lots of unnecessary and unused images from the Holo-based themes
[*] Fixed links in the Addons description markdown not being able to be clicked
[/LIST]
[COLOR="#ff4444"]2.3 13th March 2015[/COLOR][LIST]
[*] Fixed cancel button not updating to install when the download finishes
[*] Important licence changes (to ensure the app cannot be taken and resold by someone -it stays free)
[*] Added ignore release option (found in the notification for a new release. Can be undone in settings)
[*] Added notification shortcut to the download page
[*] More robust update checking code
[*] Font changes in about page - more legible
[*] Added BitCoin donations (for ROM developers and the me)
[*] Removed some debugging code showing for end users
[*] Theme tweaks to Material theming, more true to proper Material light and dark.
[*] Fixed layout height being broken on the update available card
[*] Better method of rechecking for an update
[*] Advertisements added. A small evil, but you can disable them freely in the app settings. Please consider keeping them for me.
[*] XML parsing is more robust and should result in fewer FC's or errors
[*] Ongoing notification for downloading now takes you to the download page
[* Added Addons (can be added manually via a new XML, or automatically on RomHut
[/LIST]
[COLOR="#ff4444"]9th January 2015[/COLOR][LIST]
[*] Fixed with MD5 returning false if you use uppercase MD5 string in the XML
[*] Fixed OpenRecoveryScript not installing if used (looking for the file in a folder with 0 in it.)
[*] Added Dutch translation
[*] Added Portuguese (Brazil) translation
[*] Added German translation
[*] Added Spanish translation
[/LIST]
[COLOR="#ff4444"]8th January 2015[/COLOR][LIST]
[*] Fixed issue with ROMs not seeing updates
[*] Fixed background service not switching off
[*] Background service will now correctly check for an update on boot (if on)
[*] Theme no longer changes to dark after accessing the settings
[*] New material icons
[*] New changelog parsing (using Btpass HTML to parse [URL="http://daringfireball.net/projects/markdown/syntax4"]Markdown[/URL] in changelogs)
[*] Changed priority of notification to be viewable on the lockscreen
[*] New notification controls (change the sound and toggle vibrate)
[*] Integration with major hosting provider ([URL="http://romhut.com"]RomHut.com[/URL])
[*] Tapping a notification now takes you to the update page
[*] General cleaning of the code and making more efficient
[/LIST]
[COLOR="#ff4444"]5th December 2014[/COLOR]
[LIST]
[*] Material UI for 5.0+ devices
[*] More robust checking of version numbers
[*] Removed location chooser - Better to store on the internal storage and limit the chance of an error with using an external SD Card
[*] Fixed MD5 checking
[*] Default checking on boot time is 12 hours rather than 3 days
[/LIST]
[COLOR="#ff4444"]19th July[/COLOR]
[LIST]
[*]Initial release
[/LIST]
XDA:DevDB Information
OTA Updates - Give your users Over-The-Air updates direct to their device, App for all devices (see above for details)
Contributors
Kryten2k35
Source Code: https://github.com/MatthewBooth/OTAUpdates
Version Information
Status: Stable
Current Stable Version: 2.5.3
Stable Release Date: 2015-08-10
Created 2014-07-19
Last Updated 2015-08-10
Reserved
Issues
To help me track issues, please use waffle.io
.
What's new?
New in v2.3 - Addons!
As of v2.3 you can provide additional ROM files via an addons page. If you have no addons provided, the page is hidden. To provide this, you can follow the instructions here. If you use RomHut to provide your updates, you need only use the upload feature of the website for Addons and the rest will show automatically, without you having to do anything.
How-to use
There are two ways you can use this in your ROM. Manually, or automatically with romhut.com. Romhut is highly recommended, as it will host your files for you, automate the process somewhat and it's free for users and developers.
RomHut
You should head over the Github instructions if free ROM hosting and automated OTA updates are your thing: https://github.com/Kryten2k35/OTAUpdates/blob/stable/Romhut.md
Manually
Equally, there are some Github instructions on how to do this manually also: https://github.com/Kryten2k35/OTAUpdates/blob/stable/Manually.md
Reserved
Notes
Direct or HTTP links
Direct links must be exactly that, direct. They cannot include any kind of gateway or web page that requires you to click a button or there will be errors in any download. Generally, if you can just paste the link into an address bar and it starts to download, it's direct. Not everyone has access to to this kind of service, especially for ROMs as it can be bandwidth intensive, but for those that do, this is there for them.
This is why, alternatively, you can use HTTP links. In this case, the user's web browser will be opened instead.
No Icon
In the download link there is a "no Icon" option. This is an apk that does not have a launcher icon, for developers who wish to integrate the apk into the settings app, for instance. In which case, you need to know that the packagename is com.ota.updates and the classname is com.ota.updates.activities.MainActivity
Planned Features
Possibly GCM notifications
Credits
Roman Nurik - Android Asset Studio Framework
Jeff Gilfelt - Android Action Bar Style Generator
ficeto - Shell tools
StackOverflow - Many, many people
Usage
Anyone is free to use this project in their ROM. I only request that you keep the app about page in-tact leaving my credits in there. You don't have to, but it'd be nice if you did.
If you could shoot me a mention in your ROM thread, that'd be cool as well.
Contributions
If you feel like you can contribute to this project, don't hesitate to fork and send me some pull requests.
Any issues I should no about? I am going to assume no news is good news
Kryten2k35 said:
Any issues I should no about? I am going to assume no news is good news
Click to expand...
Click to collapse
No news IS good news, the manifest check is good, I have yet to check anything else (download link, etc...). Thanks for sharing, good work.
What i am doing wrong?
this is my link to manifest https://www.dropbox.com/s/d4ghncsf1eadnhr/update_manifest.xml
this is lines i have add in buld.prop
Code:
ro.ota.romname=ARTROM
ro.ota.version=3.5
ro.ota.codename=stable
ro.ota.device=m7
ro.ota.manifest=https://www.dropbox.com/s/d4ghncsf1eadnhr/update_manifest.xml
It's checking few seconds and says no updates.
also tryed last line
Code:
ro.ota.manifest=https://dl-web.dropbox.com/get/update_manifest.xml?_subject_uid=125764646&w=AADm0MlpSblydhht8LYX5_R84NIgT3S7dJOCYPnADxeHyw
artur0588 said:
What i am doing wrong?
this is my link to manifest https://www.dropbox.com/s/d4ghncsf1eadnhr/update_manifest.xml
this is lines i have add in buld.prop
Code:
ro.ota.romname=ARTROM
ro.ota.version=3.5
ro.ota.codename=stable
ro.ota.device=m7
ro.ota.manifest=https://www.dropbox.com/s/d4ghncsf1eadnhr/update_manifest.xml
It's checking few seconds and says no updates.
also tryed last line
Code:
ro.ota.manifest=https://dl-web.dropbox.com/get/update_manifest.xml?_subject_uid=125764646&w=AADm0MlpSblydhht8LYX5_R84NIgT3S7dJOCYPnADxeHyw
Click to expand...
Click to collapse
Maybe this line instead: https://www.dropbox.com/s/d4ghncsf1eadnhr/update_manifest.xml?dl=1
Notice it says "?dl=1" at the end. I have to admit I have no experience using Dropbox for this (I use my webserver), but I know you can get direct links this way.
Kryten2k35 said:
Maybe this line instead: https://www.dropbox.com/s/d4ghncsf1eadnhr/update_manifest.xml?dl=1
Notice it says "?dl=1" at the end. I have to admit I have no experience using Dropbox for this (I use my webserver), but I know you can get direct links this way.
Click to expand...
Click to collapse
Now it says update available but downloading small 15.1kb zip file with rom name.
I found what is wrong, now all fine.
Any way to implement that in system like stock ota, or replace? CM like, don't know if s possible.
dkionline said:
Any way to implement that in system like stock ota, or replace? CM like, don't know if s possible.
Click to expand...
Click to collapse
I'm not sure what you mean. This is supposed to be a system app and you as a ROM developer can provide your own OTA updates with it, if you have the right tools.
I mean implement in settings app, you wrote about no icon in 3 post, will that work on sony?
Absolutely
https://github.com/UltimaAOSP/platf...blob/kk-4.4/res/xml/settings_headers.xml#L196
Code:
<!-- UltimaControl Settings -->
<header
android:title="@string/ultima_settings"
android:icon="@drawable/ic_ultima_settings">
<intent android:targetPackage="com.ultima.settings"
android:targetClass="com.ultima.settings.SettingsActivity" />
</header>
That's how you'd do it. Obviously you should replace the strings and drawable with your own. The target package and class in the OP's It goes in the xml's for settings. I'vfe never had a Sony device so I don't know the exact layout, but for me that's in /Settings.apk/res/xml/settings_headers.xml
i tried now, but its complicated. Are there more lines to write in other file? It stops in compilingtime.
You probably need to match the strings, of course, and add a drawable/image of your choosing.
Everything seems working fine. The only md5 check always failed.
How can i release 2 or more OTA step by step?
For example i pushed first OTA with some additional and improvements. Then i want push 2nd OTA after some time. How to make users receive 1st OTA then 2nd OTA step by step?
The only way would be to have multiple manifests.
Say v1.0 has http://www.example.com/update/manifest_1.0.xml
Then v1.1 has http://www.example.com/update/manifest_1.1.xml
And v1.2 has http://www.example.com/update/manifest_1.2.xml
That way, anyone on v1.0 would update to 1.1, then 1.2. However, that's pretty inefficient, but it works.
You can also simply integrate v1.1 into the v1.2 update, that way anyone getting the v1.2 update also gets the v1.1 update as well. That's what I'd do.
Or, you can have a record of previous updates, and run an assert check in your installer script for an update checking the user is on the right version and directing them to a website to download the other updates.
I could bare this in mind and perhaps add some stuff to the xml about previous updates, but I don't want it to get too messy.
Kryten2k35 said:
The only way would be to have multiple manifests.
Say v1.0 has http://www.example.com/update/manifest_1.0.xml
Then v1.1 has http://www.example.com/update/manifest_1.1.xml
And v1.2 has http://www.example.com/update/manifest_1.2.xml
That way, anyone on v1.0 would update to 1.1, then 1.2. However, that's pretty inefficient, but it works.
You can also simply integrate v1.1 into the v1.2 update, that way anyone getting the v1.2 update also gets the v1.1 update as well. That's what I'd do.
Or, you can have a record of previous updates, and run an assert check in your installer script for an update checking the user is on the right version and directing them to a website to download the other updates.
I could bare this in mind and perhaps add some stuff to the xml about previous updates, but I don't want it to get too messy.
Click to expand...
Click to collapse
Thanks for reply. I also think about integrate previous update in each next, just think that each next OTA size increase.
Some of my OTA's are just full ROM downloads anyway, which is like 800MB+. Sometimes you just need to do this, I've found. This is why there's a setting to limit which data connection is being used. Not everyone has unlimited mobile data
That means for every Update or full rom a new xml. Correct me if im wrong.
The best method would be a check of higher number. U provide folder link in build.prop and it checks automatic if 1.1->1.2 by xml name.
I had tested in 1 xml with small zip by changing build nr, but it doesn't show anything -.-.
Detach3
Introduction
This Magisk module is for detaching apps from the Google Play Store.
It removes your defined packages from the 'Manage apps and device" section and disables them from auto-updates.
Installation
Flash module in Magisk Manager only.
Not necessary to reboot after flashing this module.
This module is designed to flash as many times as you like.
It is configured with a *configuration file. You can create one before flashing this module to define your package(s) or the default one will be used instead, which detaches YouTube by default.
Add your package name(s) you would like to detach to the configuration file, with each package name on a new line.
You can add more package names to your configuration file or the default one at any time, then simply just flash module again to apply it. Again, no need to reboot or any other user interaction needed.
Read the log that Magisk Manager displays when flashing the module, it displays the detached package(s) for confirmation.
*Configuration file: /storage/emulated/0/Android/detach.cfg
Reattach
https://forum.xda-developers.com/t/module-detach3-detach-market-links.3447494/post-84951411
Scheduler
https://forum.xda-developers.com/t/module-detach3-detach-market-links.3447494/post-84981039
Uninstallation
Uninstall with Magisk and reboot.
Troubleshooting
Follow uninstallation method. After reboot open playstore, navigate to the 'Manage apps and device' section so it can populate and then re-flash the module.
Still have an issue? Post your problem in detail and upload your Magisk installer log, found in your Download directory after saving it ( Shown here ).
Changelog
Spoiler: Click to expand
v3.00
- Initial release
v3.01
- Disabled Fallback broadcast
v3.02
- Disable auto-update for detached apps
- Disable playstore running in background
- Added uninstall script to revert changes
v3.03
- Updated sqlite3 binary
- Added support for x86 and x64
v3.04
- Added package check for configuration file
- Minor alterations
v3.05
- Recompiled sqlite3 binaries
- Improved device platform check
- Added database check
- Added the default detach.cfg file
- Minor alterations
v3.06
- Improved installer checks
- Fixed inflating uninstall script error
- Tidied installer script
- Added reattach feature*
* Comment out package name(s) in detach.cfg to reattach.
v3.07
- Fixed minor install.sh error on Android 11
- Improved some installer logic
- Added scheduler feature*
*Termux and Termux:API apks need to be installed beforehand for scheduler
v3.08
- Fixed playstore update log error on some devices
- Fixed script not applying package names with the same string of characters
- Fixed minor installer check for checking packages
- Fixed termux-api binary check
- Disabled package checks on some devices
- Added option to open playstore with scheduler notification
- Added option to open configuration file with scheduler notification
- Added option to flash module with scheduler notification
v3.10 - Note: Disable scheduler and uninstall previous version before installing this version.
- Removed package check (Some users have had issues, reboots etc.)
- Removed scheduler (Not needed for now)
- Removed unnecessary coding
- Added new method to prevent detached apps repopulating
- Added disabling of Play store trackers
- Other minor alterations in installer script
- Cleaned up installer script for new method
v3.11
- Added ignore GET_USAGE_STATS in AppOps
v3.12
- Updated sqlite binaries
- Removed disabling of fallback receiver
- Added disabling of alarm manager background service
v3.13
- Updated sqlite binaries
- Added ignore RUN_ANY_IN_BACKGROUND in AppOps
- Added ignore RUN_IN_BACKGROUND in AppOps
- Disabled App Discovery Service
Frequenly Asked Questions
Spoiler: Click to expand
Q. Can I use the old detach.txt?
A. No, I decided to ditch it. It now uses a new method explained in the installation section.
Q. Where is the boot script installed?
A. No boot script is needed for detaching, everything is done while flashing the module.
Q. Does this break safetynet?
A. No, it doesn't conflict with safetynet at all.
Q. Why shouldn't I re-enable Play Protect?
A. It will interfere with the module's purpose.
Q. Will having Play Protect disabled, open me up to vulnerabilities?
A. No, the playstore scans their market apk's after developers upload them.
Q. I usually install after-market apks (modified ones) and I think play protects me from this?
A. You should scan your unknown apk with Total Virus.
Q. How do you find a package name?
A. Magisk Manager lists your apps with the package name underneath each one, in the Magisk Hide list.
Q. What Magisk version is needed?
A. The module template is designed for Magisk v20.4+
Q. Do I need to uninstall previous version before updating?
A. No, unless stated. Just flash updated version.
Q. Do auto-updates still work for all my other apps that aren't detached?
A. Yes, auto-update and other notifications etc still work.
Download
See attached below -- detach-3.xx.zip
Previous versions
Detach Market Links for Theme Ready Apps *
Introduction
This Mod is for detaching apps from the Google Play Store that are included in the Theme Ready Apps zip and/or aroma installer from Team Black Out for CMTE and Substratum theme engines.
*Now also includes majority of all themed apps by Team Black Out by using an optional txt file.
The purpose is that updates will not show in your update list and also in update notifications from the Google Play Store.
This allows you to auto-update or the ability to use the update all button without the worry of updating Theme Ready Apps which will break your themes for those apps updated.
The Google apps that are detached if you're not using the optional txt file are Gmail, Google App, Google Plus, Hangouts, YouTube and Gboard (Google Keyboard).
Installation
Flash Mod in recovery, no need to wipe anything but if using SuperSU systemless mode or Magisk, flash this mod afterwards.
No need to flash again in-between ROM updates if using SuperSU systemless mode or Magisk or if your ROM supports addon.d scripts.
To detach more themed apps, place the detach.txt file either on root of your sdcard or internal storage and remove the comment from the apps you wish to detach and then flash Detach.zip
You can also use the optional detach.txt file to just selectively detach Theme Ready Apps.
If you don't use the supplied detach.txt file, only Theme Ready Apps will be detached.
To add your own custom packages (apps), read here > https://forum.xda-developers.com/showpost.php?p=72194332&postcount=147
Uninstallation
Rename detach.txt on sdcard to detach.remove, flash Detach.zip again and reboot.
This will remove all files related to installation, including the txt and custom file and restores all market links.
Note
If not using SuperSU or Magisk, you need to have init.d support.
The configured script doesn't execute until after 60 seconds when boot has completed, this also includes the remove script too.
This Mod has been tested by myself on Android 6 and 7.
You still have the ability to update your Theme Ready Apps via Google Play Store but you'll need to use the search function instead.
Changelog
v1.0
- Initial release
v1.1
- Changed detach method
v1.2
- Disabled service for database
v1.3
- Bug fixes
v1.4
- Added static sqlite binary
v2.0
- Added themed apps to detach with configuration txt file (optional)
v2.1
- Cleaned up installation script
- Added mod removal option
v2.2
- Magisk compatible (systemless installation)
- SuperSU systemless mode compatible (systemless installation)
- Fixed init.d detection
- Fixed market links reappearing
- Updated detach.txt (added Wallpapers, Pixel Launcher, Capture (GoPro))
v2.3
- Updated script and detach.txt (added Gboard, Clock, Camera, Google Connectivity Services, Google VR Services, Google Play Services)
v2.4
- Updated script and detach.txt (added Google Carrier Services and the ability to add custom packages)
v2.5
- Fixed market links reappearing
v2.6
- Main script updated for removal process
- Disabled code for a playstore service that no longer needs to be disabled
- Removed Contacts, Phone and Photos from default install
Thanks @hinxnz, I'll try the newest one.
Report 1.3: My theme ready gapps were detached except Google Calendar. I installed Black Google Calendar from TBO. Is there something I can do for this?
sunanulh said:
Thanks @hinxnz, I'll try the newest one.
Report 1.3: My theme ready gapps were detached except Google Calendar. I installed Black Google Calendar from TBO. Is there something I can do for this?
Click to expand...
Click to collapse
I was thinking about adding more themed apps to detach but would have to either use a config file on sdcard for example or probably better to make an aroma version but I would need all the package names first.
hinxnz said:
I was thinking about adding more themed apps to detach but would have to either use a config file on sdcard for example or probably better to make an aroma version but I would need all the package names first.
Click to expand...
Click to collapse
I think a "fulfilled" config file is simpler. So the users have just to add/remove '#' symbol.
For the name of the apps, maybe you can ask to TBO.
Cheers
hinxnz said:
I updated mod, see if it works for you now & I made a thread for it too > http://forum.xda-developers.com/and...detach-market-links-theme-ready-apps-t3447494
Click to expand...
Click to collapse
It's still not working on Stock rooted N. Thanks for trying.
Glad I saw your post that you put this thread up!
I downloaded 1.3 and flashed it and rebooted and waited for two minutes, but YouTube is still showing an update.
cmo220 said:
It's still not working on Stock rooted N. Thanks for trying.
Click to expand...
Click to collapse
Could you call script manually with Terminal Emulator and post output
RED ZMAN said:
Glad I saw your post that you put this thread up!
I downloaded 1.3 and flashed it and rebooted and waited for two minutes, but YouTube is still showing an update.
Click to expand...
Click to collapse
But the first version still works for you?
YouTube hasn't been updated for awhile AFAIK, what version is showing an update?
Are the other theme ready apps showing in your 'My apps & games' list?
Do you have any apps in your 'Wishlist', found in side menu?
hinxnz said:
Could you call script manually with Terminal Emulator and post output
But the first version still works for you?
YouTube hasn't been updated for awhile AFAIK, what version is showing an update?
Are the other theme ready apps showing in your 'My apps & games' list?
Do you have any apps in your 'Wishlist', found in side menu?
Click to expand...
Click to collapse
I couldn't get a /su.d folder so I put it in /system/su.d, which was already there and working. Here is the output.
angler:/ $ su
angler:/ # /su.d/99-detach.sh
sush: /su.d/99-detach.sh: not found
127|angler:/ # /system/su.d/99-detach.sh
angler:/ # Component {com.android.vending/com.google.android.finsky.services.DailyHygiene$DailyHygieneService} new state: disabled
CANNOT LINK EXECUTABLE "sqlite3": cannot locate symbol "u_setDataDirectory_55" referenced by "/system/xbin/sqlite3"...
Aborted
CANNOT LINK EXECUTABLE "sqlite3": cannot locate symbol "u_setDataDirectory_55" referenced by "/system/xbin/sqlite3"...
Aborted
And a bunch more of the same error.
The first version? I've deleted the previous versions .zips.
I've installed 1.0, 1.2, and 1.3.
Youtube has been showing this way for about a week, even after reboots.
11.32.53 is what's showing on Google Play, I've got 11.29.55 installed from TBO Theme Ready Apps v 21.
com.google.android.youtube
Showing up in the My apps & games list as installed...
Gmail
Google App
Google+
Google Photos
Hangouts
Wishlist, yes, I've got several.
RED ZMAN said:
The first version? I've deleted the previous versions .zips.
I've installed 1.0, 1.2, and 1.3.
Youtube has been showing this way for about a week, even after reboots.
11.32.53 is what's showing on Google Play, I've got 11.29.55 installed from TBO Theme Ready Apps v 21.
com.google.android.youtube
Showing up in the My apps & games list as installed...
Gmail
Google App
Google+
Google Photos
Hangouts
Wishlist, yes, I've got several.
Click to expand...
Click to collapse
Could you call script in Terminal Emulator and post output too.
For example:
Code:
su
/system/su.d/99-detach.sh
I don't think I've used terminal emulator except for twice since the G1, so I'm not sure if I did this right.
[email protected]:/ $
[email protected]:/ $ su
system/su.d/99-detach.sh <
sush: /system/su.d/99-detach.sh: not found127|[email protected]:/ #
hinxnz said:
Could you call script in Terminal Emulator and post output too.
For example:
Code:
su
/system/su.d/99-detach.sh
Click to expand...
Click to collapse
Is there any reason you are using a dynamically linked sqlite in your zip? the error the user is getting is because of that I believe. Idk I would try to use a static sqlite binary. Ill attach one so you/someone can have, but in case anyone is curious how to quickly compile sqlite3 statically ill post it in the spoiler tags below.
oh and just to note, I forgot to rename it from sqlite3 to sqlite before uploading
Im not going to explain the lines though, pretty straight forward imho
/opt/androideabi is my ndk toolchain prefix
Code:
mkdir sqlite3-static
cd sqlite3-static
wget https://sqlite.org/2016/sqlite-amalgamation-3140100.zip
unzip sqlite-amalgamation-3140100
cd sqlite-amalgamation-3140100
export PATH=$PATH:/opt/androideabi/bin
cp $(ANDROID_BUILD_TOP)/bionic/libdl/libdl.c .
cp /opt/androideabi/sysroot/usr/include/android/dlext.h .
cp /opt/androideabi/sysroot/usr/include/dlfcn.h .
arm-linux-androideabi-gcc -static -I./ -L./ -ldl *.c -o ../sqlite3
cd ../
file ./sqlite3
Surge1223 said:
Is there any reason you are using a dynamically linked sqlite in your zip? the error the user is getting is because of that I believe. Idk I would try to use a static sqlite binary. Ill attach one so you/someone can have, but in case anyone is curious how to quickly compile sqlite3 statically ill post it in the spoiler tags below.
oh and just to note, I forgot to rename it from sqlite3 to sqlite before uploading
Im not going to explain the lines though, pretty straight forward imho
/opt/androideabi is my ndk toolchain prefix
Code:
mkdir sqlite3-static
cd sqlite3-static
wget https://sqlite.org/2016/sqlite-amalgamation-3140100.zip
unzip sqlite-amalgamation-3140100
cd sqlite-amalgamation-3140100
export PATH=$PATH:/opt/androideabi/bin
cp $(ANDROID_BUILD_TOP)/bionic/libdl/libdl.c .
cp /opt/androideabi/sysroot/usr/include/android/dlext.h .
cp /opt/androideabi/sysroot/usr/include/dlfcn.h .
arm-linux-androideabi-gcc -static -I./ -L./ -ldl *.c -o ../sqlite3
cd ../
file ./sqlite3
Click to expand...
Click to collapse
Thank you Surge! :highfive:
Surge1223 said:
Is there any reason you are using a dynamically linked sqlite in your zip? the error the user is getting is because of that I believe. Idk I would try to use a static sqlite binary. Ill attach one so you/someone can have, but in case anyone is curious how to quickly compile sqlite3 statically ill post it in the spoiler tags below.
oh and just to note, I forgot to rename it from sqlite3 to sqlite before uploading
Im not going to explain the lines though, pretty straight forward imho
/opt/androideabi is my ndk toolchain prefix
Code:
mkdir sqlite3-static
cd sqlite3-static
wget https://sqlite.org/2016/sqlite-amalgamation-3140100.zip
unzip sqlite-amalgamation-3140100
cd sqlite-amalgamation-3140100
export PATH=$PATH:/opt/androideabi/bin
cp $(ANDROID_BUILD_TOP)/bionic/libdl/libdl.c .
cp /opt/androideabi/sysroot/usr/include/android/dlext.h .
cp /opt/androideabi/sysroot/usr/include/dlfcn.h .
arm-linux-androideabi-gcc -static -I./ -L./ -ldl *.c -o ../sqlite3
cd ../
file ./sqlite3
Click to expand...
Click to collapse
Cheers, thanks and yeah that's definitely the reason
Super idea, this would of been good a few months ago when google pushed their framework update and it broke some apps that i kept from updating,,, @Shaftamle google keyboard is the main on one, thank you
3GotoM ym morf tneS
Version 1.4 works for me now on 7.0. Thanks everyone!
Installed version 2.0 earlier today and seems to be working perfectly. Nothing showing needing updated.
Thanks!
How to add Black Google Calendar and Black Keep in the list?
sunanulh said:
How to add Black Google Calendar and Black Keep in the list?
Click to expand...
Click to collapse
Just remove the comments from those two as well as the other theme apps you flash.
Here's an example, theme ready apps, calendar and keep will be detached.
Code:
Contacts
Gmail
Google App
Google Plus
Hangouts
Phone
Photos
YouTube
#Inbox
#Duo
#Dropbox
#PushBullet
Calendar
Keep
#Telegram
#Swiftkey
#Translate
I have tried installing your script... And no matter how I go about... I cannot get the script to populate the su.d directory like it should...
And... Since I don't understand your flashable... I can't pull what I want out of it...
Could you explain how to install said script without recovery?
Thanks
Features:
- Fully rewritten su binary!!!
- In-app su binary Updater!!!
- SuperPower access prompt (no countdown timer!)
- SuperPower access logging (date and time only!)
- SuperPower access notifications (Faster, with guaranteed security!)
- Deep process detection (all apps and processes!)
- Works with non-standard shell locations
- Always runs in ghost mode
- Supports SuperSU/Magisk
SuperPower Premium's current extra features include:
- Full Command Logging (input/output/error)
- Per app notification/logging settings
- Pin protection for Superuser prompt
- App list and preferences backup/restore
Download:
SuperPower on Google Play Store:
https://play.google.com/store/apps/details?id=wkroot.superpower
SuperPower Premium on Google Play Store:
https://play.google.com/store/apps/details?id=wkroot.manager.premium
If you have rooted your device through SuperSU or Magisk, the fastest/easiest/recommended way to installing SuperPower's su binary is to download and install the attached SuperPower-v30.5.apk, which has the "su binary Updater" feature.
If Magisk is your root, you can use both SuperPower and Magisk at the same time, if you use the SuperPower-v30.5.apk to install the SuperPower's su binary!!!
Note: the TWRP zip is attached at the bottom of this post!
Donation via PayPal:
https://www.paypal.com/cgi-bin/webs...ss=BQJLWCA5L8WMG¤cy_code=BRL&source=url
Developer's journey
Since 2016, I have been working on ChainsDD's Superuser's su binary, fixing several bugs and security issues, to make them work on my devices. The result of that work is a fully rewritten/full-featured su binary and root access manager app: SuperPower - Root Access Manager!
SuperPower is highly compatible with SuperSU. Also, it uses the SuperSU's tools to ensure its working on SELinux-enabled devices.
Special thanks:
@zinxv, @ChainsDD and @Koush, for have built Superuser/su binary;
@Chainfire for have built SuperSU.
Wanderson Kalil, author of SuperPower.
Changelogs
v5.7 - 2023-03-03
- Fixed --mount-master inherinting SuperPower instead of init mount namespace
- Fixed Termux stuck on prompt
- Added Support for SuperSU/Magisk
v5.6 - 2022-11-09
- Added support for Android 11/12
v5.5 - 2020-11-09
- Removed unused receiver causing crashes at app's opening
- Fixed bug of "Settings" screen not opening in Multiuser mode
v5.4 - 2020-11-06
- Fixed a performance regression on the "apps" screen
- Fixed a bug introduced in v5.3
v5.3 - 2020-10-30
- Improved support for Android 11
- Fixed SuperPower's Prompt/Notifications not being shown on Android 10 due to code incompatibilities
v5.2 - 2020-09-25
- Fixed app not opening on some devices
v5.1 - 2020-09-16
- Fixed a crash on the "Info" screen
v5.0 - 2020-08-14
- Removed the su binary Updater feature (Google Play Store requirement!)
- Improved "Root" setting
v4.8 - 2020-07-18
- Made some improvements into the Settings/Preferences screen
- The su binary Updater is now only available to the device's owner
- The su binary is now deleted immediately after SuperPower has been uninstalled
- Fixed a crash after an app has been installed
v4.7 - 2020-07-12
- Fixed an in-app crash introduced in v4.6
v4.6 - 2020-07-10
- If SuperPower app is not installed, the SuperPower's su binary is automatically removed from the device as part of app uninstall!!!
V4.4 - 04/07/2020
- Updated su binary version to match SuperPower version
v4.3 - 2020-07-03
- added new permission to support Android 11
- added option to switch the Settings screen
- added suppport for Scoped Storage: removed backup/restore of apps/preferences feature and related permissions
v4.2 - 2020-06-26
- Added Uninstall/Unroot button to the su binary Updater feature so you can remove SuperPower's su binary from your device (Google Play Store Requirement!)
v4.0 - 2020-06-13
- Finally republished on Google Play Store again!!!
v4.0 - 2020-05-15
- Fixed Language Switcher not working on Oreo (8.0+) devices
- Added Language Switcher feature
- Improved translations
- Fixed a bug in the Settings screen on some devices
v3.7 - 2020-05-04
- SuperPower: updated Privacy and Secutity Policy
- su: all apps and processes that call the su binary are now forced to run in their own mount namespace (on failure, fallback to private mount namespace!)
- su: removed --id/--mount-master/--mount-namespace (Google Play Policy compliance!)
- SuperPower: removed option to disable mount namespace (Google Play Policy compliance!)
2020-04-27 - v3.6
- Fixed a crash in the "Information" tab
2020-04-16 - v3.4
- Initial public release
reserved!
After 14 days of release, Yesterday - 2020-04-29 - I received an email from Google Play stating that SuperPower v3.6 has been removed from Play Store due to a policy violation! Keep reading to understand the situation!
In v3.6, all the apps and processes that call the SuperPower's su binary run in private mount namespace by default, with an option/parameter to run in the master mount namespace (--mount-master), and another one to run in different mount namespaces (--mount-namespace).
However, allowing apps and processes that call the su binary to execute in mount namespaces other than their own mount namespace should be considered a security vulnerability, not a feature, as it disables an important Android security feature. Therefore, the --mount-master/--mount-namespace options are now out of the SuperPower's su binary's command-line.
From v3.7 onwards, all the apps and processes that invoke SuperPower's su binary - including SuperPower - will execute in their own mount namespace (on failure, the su binary fallback to running in private mount namespace).
Root app developers should be aware that this is the default behavior on Android 4.2.2, where su binary runs in non-daemon mode.
Thus, all of these changes make SuperPower the most secure Root Access Manager app available into the world.
Wanderson Kalil, author of SuperPower - Root Access Manager.
RESERVED!
reserved
Thanks for the work!
Will you share the app here? Still not available at play store.
Running in ghost mode is similar to Magisk hide?
And how is the installation procedure for people with/without Magisk installed.
Regards,
Enviado de meu HD1903 usando o Tapatalk
lucfig said:
Thanks for the work!
Will you share the app here? Still not available at play store.
Running in ghost mode is similar to Magisk hide?
And how is the installation procedure for people with/without Magisk installed.
Regards,
Enviado de meu HD1903 usando o Tapatalk
Click to expand...
Click to collapse
The entire Magisk's system is kept on your device, only the Magisk's su binary is replaced (this is only when you updates the su binary through the SuperPower's su binary Updater!).
Enviado de meu SM-J120H usando o Tapatalk
Greetings & thanks for sharing your work. A few questions...
I am on Android 10 currently rooted with Magisk. I have downloaded the app from Play as well as updater apk (there are 2, what's the difference?)
I open updater & there's no option to update binaries. Any suggestions on what to try & which updater apk is correct for OP8 rooted with Magisk?
I understood that SU binaries would be updated from the app, does the tarp zip need to be flashed?
It would be great to have a Magisk Module for this.
Thanks in advance
are you still updating this? does it play well with a11 or 12?
SuperPower v5.6:
The 2 main reason for this version of SuperPower are:
1: I lost SuperPower's keystore (file needed to publish apps on Play Store)!
2: Android 11 have code execution restrictions that prevents SuperPower's prompt/notifications/logging from working!
3: Added su binary Updater feature to SuperPower.apk, you can now replace MAGISKSU BY SuperPower's su binary!
Important note: Android 12 fully break SuperPower su's binary from working:
Setting LD_LIBRARY_PATH from su binary is no longer possible/allowed by Android 12, meaning it's not possible to do a login shell (call /system/bin/sh) from SuperPower's su binary. There is no fix for that, and we can't bypass that system protection/restriction.
Update: the above restriction is already fixed: since we cannot call setenv("LD_LIBRARY_PATH", "/system/lib", 1) from su binary on Android 12, the solution is to inherit the environment of the caller process for a new process image and call execve().
Update 2: we need to set /system/lib64 first instead of /system/lib so the linker link the binaries through the correct libc.so.
Note 2: DON'T DELETE THIS POST: I'm the author of SuperPower - Root Access Manager!!!