Related
Hey guys here is the official Online Nandroid Backup app support thread!
Nandroid backups are usually performed in recovery mode. This means you would have to turn off your phone and reboot in recovery mode, which wastes a whole lot of time rebooting and a lot more time offline. With this tool you can do nandroid backups without switching off your device.
THIS APP REQUIRES A ROOTED DEVICE WITH BUSYBOX!
Features:
* Creates backups in the CMW 5 and 6 style or TWRP!
* Full support of the onandroid script.
* Create custom names for your backups.
* Choose what partitions get backed up.
The onandroid script was developed by Ameer Dawood. The original XDA post can be found at: http://forum.xda-developers.com/showthread.php?t=1620255
Important: This tool requires a rooted phone with busybox to work!
Screens:
Change Log:
Code:
Version 4.4.4
* Nandroid backups can now be uploaded without having to be zipped.
* Vibrate and LED notification for nandroid backup complete can now be turned off in the settings.
* Added upload only when charging option to Tasker plugin and scheduled backups.
* Fixed bug that prevented the tasker plugin from not working.
Version 4.3
* Removed ActionBarSherlock and replaced it with ActionBarCompat.
* Added support for Tasker!
* Scheduled backups can now be canceled from the notification bar. (Android 4.1+)
* Added elapsed time timer to nandroid backup so uses can see how long the backup has taken so far.
* Change log dialog will now show once the app as been updated.
Version 4.2.4
* Fixed user reported bugs.
* Added ability to set custom name of backup as build display id string.
* Time for scheduled backup is now displayed in 12 or 24 hour format depending on your system prefrences.
* Default partitions can now be set in default settings for seletive backups.
Version 4.2.3
* Improved backup process. App makes sure dedupe and patch are installed before starting a nandroid backup.
* Fixed bug that caused scheduled backup to run at boot and random times of the day." +
Version 4.2.2
* Fixed bug that caused scheduled backup to to not roll over to next month. <b>Please click on Manage Scheduled Backup and click set to set the next scheduled backup to the correct time!</b>
Version 4.2.1
* Fixed bug that caused the app to delete newly created nandroid backup when trying to enforce a backup retnetion policy of 1.
" +
Version 4.2
* App has graduated from beta!
* Added option to backup retention that lets user specify whether to enforce backup retention policy before or after nandroid backup has finished.
" +
Version 4.2_beta_3
* Fixed bug that cuased scheduled backup to show notification even if the auto backup is not running.
* Manual selection of device for device patch has been re added.
Version 4.2_beta_2
* Fixed bug that caused scheduled backups to trigger at wrong times after first scheduled backup. (Please remove current scheduled backup and set a new one for bug to be fixed on your device)
* Added option to scheduled backup to only backup if device is charging.
* Fixed FC bugs reported through the Google Play Store.
Version 4.2_beta
* Onandroid script now installs to and runs from app data instead of /system/bin.
* Users can now set a scheduled backup.
* Users can now set how many backups to retain on the device.
* Various UI tweaks and improvements.
* Dalvik cache and Google music files can now be exclued from the backup.
Version 4.1.4
* Slight UI improvments.
* Added on boot reciever to init the script auto update feature.
Version 4.1.3
* User can select which busybox the onandroid script uses.
* Fixed exit code 2 error on some devices.
Version 4.1.2
* Added tip about changing shell.
* Fixed some users reported UI issues on pre 3.0 devices.
Version 4.1.1
* The app now auto updates the backup script.
Version 4.1
* Users can now manually enter their save location.
Version 4.0.2:
* Removed Exclude dalvik and Google music options until those options are publicly supported by the backup script.
Version 4.0.1
* /storage/* is now included in selectable save paths.
* The app now uses its own busybox when running the script.
* Added link to Google+ community in settings.
* Fixed some layout issues on older devices running 2.x.
* Added more backup options.
Version 4.0
* The UI has been redesigned from the ground up.
* App no longer checks for necessary tools every run. Instead its checked when app is run for the first time.
* App now identifies device.
* Quick Backup mode added.
* User now sets default backup settings on first run of app.
* Nanroid Backup can now be stopped.
Version 3.0.7
* Users can select between ash and default shells.
* Fixed bug that prevented the onandroid.log from being read by the app.
Versions 3.0.4 & 3.0.5
* Fixed various bugs.
Version 3.0.3
* Added permission android.permission.ACCESS_SUPERUSER.
Version 3.0.2
* Added support for more partitoins in selective mode.
* Now using ash shell to fix problems so users were having running the script.
* Fixed typo.
Version 3.0.1
* FC bug fixed when going back from settings.
* Fixed small UI problem.
Version 3.0
* Now using actionbar Sherlock.
* Added support disable MD5 generation and compress backup. (TWRP only)
* UI has been improved.
* Added support for yaffs2 override.
Version 2.8.3
* Bug fixes.
Version 2.8.2
* Bug fixes.
Version 2.8.1
* Bug fixes.
Version 2.8
* Changed theme to dark theme.
* Fixed bug that prevented some devices from installing the onandroid script.
Version 2.7
* Added support for TWRP.
* My Backups removed infavor of Nandroid Manager.
Version 2.6.9
* Several small bug fixes.
* Fixed install loop for users who updated to version 7.0 of the script.
Version 2.6.8.1
* Bug fixes for users have install loop.
Version 2.6.8
* Fixed bug that prevented the onandroid script from being installed on some devices.
Version 2.6.7.2
* Fixed screen rotation bug.
Version 2.6.6
* Bug fixes.
Version 2.6.5
* If a backup witht the same name already exists the user is now given the choice wether or not they want to set a different name or overwrite the backup.
* Fixed white text on white background issue.
* Fixed crashed caused when dismissing a dialog.
* Various other bug fixes.
Version 2.6.4
* Improved logging of errors.
* Bug fixes.
* Backups listed in My Backups is now sorted by date.
Version 2.6.3
* Russian language updated.
* Various bug fixes.
Version 2.6.2
* My Backups has been readded to the app and enabled.
* Fixed bugs reported via play store.
Version 2.6.1
* Fixed issue with too many items in the action bar causing the itmes text to be truncated.
* My backups menu option has been removed untill this feature is ready.
* Device specific patch is now checked for when user runs the app for the first time.
Version 2.6_beta_4
* Directory chooser now is ordered alphabetically.
* Updated Russian translation.
* Clockworkmod location and specify sd-ext location can now be manually edited.
* Device specific patchs are now listed alphabetically.
* Checking of preconditions when app is first opened is now done asynchronous to prevent app from hanging on start.
* The directory chooser for selecting sd-ext can now browser directories such as /data.
" +
Version 2.6_beta_3
* Fixed serveral bugs submitted via the play store.
* Improved selection of clockworkmod folder.
* Path of clockworkmod folder can now be set in setting for My Backups.
Version 2.6_beta
* The app now fully supports all the featues added to version 6.0 of the onandroid script which include the following:
- Specify sd-ext path.
- Specify alternate backup media.
- Backup modes: normal, split, incremental, and specify partitions.
* Sening an app debug report has been improved now to include a debug log errors that occure.
* App now requires version 6.0 or higher of the onandroid script.
* My backups is now included in beta. It is still a work in progress but will give users a preview of whats to come. It includeds the following:
- Delete and rename backups.
- Compress to zip.
- Verify MD5.
Version 2.5.4
* Fixed bug that prevented patch from being installed!
* When a patch is installed a toast notification will show up verifying that the patch as been installed.
Version 2.5.2
* Added support for the 6.0 version of the script.
* Problems concerning the script will now be sent to Ameer.
Version 2.5.1
* Fixed looping of install onandroid script when app opens up.
* Added install onandroid menu option to settings menu to allow people to install the latest version of the onandroid script.
* Added option to settings under other to set wheahter app checks for new version of update script on start of app
Version 2.5
* Added German language.
* Various small bug fixes.
Version 2.4
* Fixed screen rotation and wakelock issues.
* Bug reports have now been split into the categories in the settings menu.
* Added ability to uninstall mkyaffs2image.
* User can now manually select the device specific patch to apply.
* The app now cleans up its cache data from downloading new onandroid scripts and device specific patches.
* Problems reading onandroid.log on some devices should now be fixed.
Version 2.3.1
* Fixed bug that prevented some devices from detecting whether or not a device specific patch existed for their device.
Version 2.3
* Fixed bug that prevented some users from downloading device specific patches!
* Script version is now shown on main screen.
* A messeage is now show in the main screen if a device specific patch is currently installed.
* mkyaffs2image is no longer auto installed. It can now be installed from the settings menu!
Version 2.2
* If mkyaffs2image is not found on device it will be installed.
* Added ability to apply device specific patches for devices where boot and recovery were not found!
* Added ability to remove the onandroid script from device through the settings menu.
* Added ability to remove device specific patch from device through settings menu.
Version 2.1
* Added ability to specify custom name for backup.
* Added option to set backup name based on phone timezone.
Version 2.0
* Added a settings menu.
* Added ability to view change log of new onandroid script before downloaing and installing the new script.
* When clicking the Start Backup button a dialog is now shown to confirm that the user want to start backing up.
* Code improvements.
Version 1.1.1
* Fixed bug that prevented newest version of onandroid from being installed.
* Fixed bug that prevented the new onandroid script to not be executable on some devices.
Version 1.1
* Added check to see if latest version of onandroid is installed and install latest version if current version is outdated.
* Added ability to install onandroid from app.
Version 1.0
* Initial release.
Download: https://play.google.com/store/apps/details?id=com.h3r3t1c.onnandbup
Removed!
New version in play store!
What?
Sent from my CINK SLIM using xda premium
HI!!
I have 3 questions:
1. How should I configure Online Nandroid backup for backing up to USB host drive?
The path to desired backup location is /mnt/sdcard/UsbOtgDrives/drive_1/clockworkmod/backup/
2. Will I be able to restore from USB host in CWM interface? I.e can it mount USB drive with NTFS?
3. I have probkem to running this. Getting error /system/bin/onandroid not found. A simple guide how to install this binary would be appreciated
I have tested this version, still the same problem: Partitions Not Detected
Another problem: When I start app, it asks me for root access, but at the next launch it doesn't ask me.
Sorry for my google english.
Sent from my HTC One S using xda premium
For me the op version works now. ?
Also in Combination with the NandroidManager, everything ok again.
---
ty for ur support and keep up ur work.
(I really like ur both apps)
greetz
SentFrom JB I9K
So OP you finally create a thread for your Online Nandroid Backup app...
This app did a great job!:good:
App still says no partitions found. However i found out if you hit start backup, it backs up all partitions just fine. So it seems to be more of a visual glitch.
Ok I think I may know what the problem. It may just be an issue of miscommunication.
So when you say "Partitions now detected" are talking about the text I boxed in red in the screenshot below:
{
"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"
}
If so this text is not meant to say that partitions were not detected! its meant to say if partitions are not detected check if a device specific patch exists!
bflmpsvz said:
HI!!
I have 3 questions:
1. How should I configure Online Nandroid backup for backing up to USB host drive?
The path to desired backup location is /mnt/sdcard/UsbOtgDrives/drive_1/clockworkmod/backup/
2. Will I be able to restore from USB host in CWM interface? I.e can it mount USB drive with NTFS?
3. I have probkem to running this. Getting error /system/bin/onandroid not found. A simple guide how to install this binary would be appreciated
Click to expand...
Click to collapse
I have never actually backed up my rom over usb host so I don't know if it would but you can try. In the backup options check Select Backup Location and put /mnt/sdcard/UsbOtgDrives/drive_1 as your backup location.
In CWM I don't think you will be able to restore over usb host but you should be able to transfer your backup over usb to your sdcard and restore that way.
The app should automatically install the onandroid backup script. When you open the app up are you asked for superuser permission?
Cyclu said:
I have tested this version, still the same problem: Partitions Not Detected
Another problem: When I start app, it asks me for root access, but at the next launch it doesn't ask me.
Sorry for my google english.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
See my post above this one concerning the partitions not detected. http://forum.xda-developers.com/showpost.php?p=41036936&postcount=9
The app may not be asking you again for superuser permission again because it may still have superuser permission from the first time or your superuser setting may be that it only asks you one time for superuser permission once and if you let it have superuser permission then it will automatically give superuser permission for every run after that. Does the app run correctly when superuser permission is not asked for?
H3R3T1C said:
I have never actually backed up my rom over usb host so I don't know if it would but you can try. In the backup options check Select Backup Location and put /mnt/sdcard/UsbOtgDrives/drive_1 as your backup location.
In CWM I don't think you will be able to restore over usb host but you should be able to transfer your backup over usb to your sdcard and restore that way.
The app should automatically install the onandroid backup script. When you open the app up are you asked for superuser permission?
Click to expand...
Click to collapse
I have installed script for my device. Now I used different mounter which mounted to /mnt/usbdisk/clockworkmod/backup/. But ONB checks for free space on SDcard instead USB even if I backup to USB ( I'm very low on space on SDcard, because this I need to backup on flashdrive. Could you please fix it?
bflmpsvz said:
I have installed script for my device. Now I used different mounter which mounted to /mnt/usbdisk/clockworkmod/backup/. But ONB checks for free space on SDcard instead USB even if I backup to USB ( I'm very low on space on SDcard, because this I need to backup on flashdrive. Could you please fix it?
Click to expand...
Click to collapse
Did you check Select Backup Location and put /mnt/usbdisk for the location in the backup options? (See screenshot im attaching for what i'm talking about. I boxed it in red)
Yes I put /mnt/usbdisk/clockworkmod/backup into Select backup location
I put /mnt/usbdisk into Specify sd-ext Path
I put /mnt/usbdisk/clockworkmod into Settings>Clockworkmod Folder Location
bflmpsvz said:
Yes I put /mnt/usbdisk/clockworkmod/backup into Select backup location
I put /mnt/usbdisk/clockworkmod into Settings>Clockworkmod Folder Location
Click to expand...
Click to collapse
No you must put only /mnt/usbdisk not the full path /mnt/usbdisk/clockworkmod/backup
H3R3T1C said:
No you must put only /mnt/usbdisk not the full path /mnt/usbdisk/clockworkmod/backup
Click to expand...
Click to collapse
Ah yes, I'll try. After checking Specify Ext SD card and filling in path ONB seems to run now :good:
H3R3T1C said:
Ok I think I may know what the problem. It may just be an issue of miscommunication.
So when you say "Partitions now detected" are talking about the text I boxed in red in the screenshot below:
If so this text is not meant to say that partitions were not detected! its meant to say if partitions are not detected check if a device specific patch exists!
Click to expand...
Click to collapse
Thats exactly what it shows. But if you hit start backup, it still backs up everything just fine. I see now its more of a question than a statement.
cmlusco said:
Thats exactly what it shows. But if you hit start backup, it still backs up everything just fine. I see now its more of a question than a statement.
Click to expand...
Click to collapse
Ok I'm going to change the text so it's less confusing. I'm publishing a new build to the play store now!
Did ONB backing up my MicroSD content..?
While I'm waiting ONB (Online Nandroid Backup) backing up my Stock ROM
I'm kinda confused when the log screen shows "backing up /sd-ext", my MicroSD contents being backed up or what..?
NOTE: The backup file size jump to 7GB, using BMM recovery about 3-4GB. Anything I missed..?
tridentcore said:
While I'm waiting ONB (Online Nandroid Backup) backing up my Stock ROM
I'm kinda confused when the log screen shows "backing up /sd-ext", my MicroSD contents being backed up or what..?
NOTE: The backup file size jump to 7GB, using BMM recovery about 3-4GB. Anything I missed..?
Click to expand...
Click to collapse
Have you checked if a device specific patch exists for your device.
I also see that it was not able to read sdcard free space correctly. Try updating your version of busybox with the busybox app from the play store.
H3R3T1C said:
See my post above this one concerning the partitions not detected. http://forum.xda-developers.com/showpost.php?p=41036936&postcount=9
The app may not be asking you again for superuser permission again because it may still have superuser permission from the first time or your superuser setting may be that it only asks you one time for superuser permission once and if you let it have superuser permission then it will automatically give superuser permission for every run after that. Does the app run correctly when superuser permission is not asked for?
Click to expand...
Click to collapse
I see what you mean about "partitions not detected" and the app correctly work even if superuser doesn't ask for permission. Thanks for latest version, thank to this, no more confusion about partitions not detected.
Sent from my HTC One S using xda premium
{
"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"
}
Mounts2SD - Storage & Memory Management
Mounts2SD started out as a simple sd-ext script which only difference between it an others like it, was that it did not use symlinks to create links between /data and /sd-ext. To day it has grown to be so much more. It now comes packed with an Application for controlling the script, viewing current states and more. The script itself has grown to become a large storage and management script with features that controlls SWAP, ZRAM, mount optimization, storage thresholds, different external and internal MMC configurations, cache and more. The content management is able to move a lot more different content between /data and /sd-ext, including the new internal storage, which on some devices, is placed in /data/media, and it also contains more than one option for storing system content on both /data and /sd-ext.
Mounts2SD is no longer just a script for devices with low storage capabilities. It can be used for a lot of things and is useful on almost any device, even those without external sdcard.
Links
The Source -> Go There
Documentation and Important Information -> Go There
Supported Languages
English
Danish
French (By @PerfectSlayer)
Dutch (By @Skippernl)
Portuguese (By @_MarcoMarinho_)
Italian (By @GMagician)
Hungarian (By @@steveboy25)
Upcoming Features
Since DevDB has future requests capabilities, I will keep a list here of planned/deciding features to avoid repeating requests.
Application Manager with fallowing options:
Convert/Revert regular applications to/from system applications
Status: Done
View and Clear Application Caches
Status: Pending
Manually kill the application
Status: Deciding (does not fit the Storage and Memory management category)
Downloads
Google Play
Install directly from Play Store
===========================
3.4.8 (6.0.20) APK (Nov 01, 2013)
[Default Mirror] SourceForge.net
This is the Application which can be installed directly on the phone
-------------------------------------------------
3.4.8 (6.0.20) Recovery ZIP (Nov 01, 2013)
[Default Mirror] SourceForge.net
This is the Recovery Package for when updating the ROM on an M2SD configured device
Older Downloads
2.2.0 (5.5.0) APK (Jan 26, 2013) (MD5: dd54ace01d9b17c72081a06cd1d072c7)
[Default Mirror] SourceForge.net
[Default Mirror] MediaFire.com
This is the Application which can be installed directly on the phone
-------------------------------------------------
2.2.0 (5.5.0) Ext4 ZIP (Jan 26, 2013) (MD5: 80c218ff53009c8a0ccde1927361def2)
[Default Mirror] SourceForge.net
[Default Mirror] MediaFire.com
This will provide you with an recovery ZIP for newer Ext4 devices
Does not have the file /proc/mtd
-------------------------------------------------
2.2.0 (5.5.0) MTD ZIP (Jan 26, 2013) (MD5: 4762d7d85c9cd934f97ba3ba36294fdd)
[Default Mirror] SourceForge.net
[Default Mirror] MediaFire.com
This will provide you with an recovery ZIP for older MTD devices
Will have the file /proc/mtd
Change Log
Version: 3.4.8
Added Hungarian translation by @steveboy25
Preferences: Fix nullPointerException issue
Upstart Script: Fix boot issues on a few devices
Older Change Log
Version: 3.4.6
Update RootFW
Script/App: Add busybox fail-safe
Tab Controller: Do not crash on IllegalStateException
Update Italian messages translation by @GMagician
Version: 3.4.4
Startup Script: Try default busybox as fallback if the runner selected one fails
Preferences: Fix another reported crash while loading configurations
EventHandler: Fix reported crash
Preferences: Fix reported crash while loading configurations
Fix internal busybox being restored on boot even thought it was removed
Upstart Script: Only unmount pre-mounted sd-ext if not on /data
Update Italian messages translation by @GMagician
Version: 3.4.2
Fix bug when sd-ext is not mounted
Fix typo which breaks IMMC configs on MTD devices
Fix reported nullPointerException crashes
RootFW: Fix nullPointerException crash on extensive loading
RootFW: Do not try to destroy a null property
Version: 3.4.1
Major rewrite
Complete rewrite of the entire application
Updated RootFW (Library)
Updated TaskManager (Library)
Added Debug File builder to the log tab
Added separate configure option for converted system applications
Minor typo fix in default locale by @GMagician
Italian translation updated to 3.3.2 by @GMagician
Version: 3.3.4
Fix sqlite3 installer to avoid boot loops
Replaced the binary and removed replacment of the libraries (They are kernel specific)
Handle old reversed mount from within the application
Is also handled by the script, but in case someone changes the configurations before rebooting after upgrading from the 2.x app, we need to have this handled before that
Version: 3.3.2
Fix reported crashes
Version: 3.3.0
Settings: Fix a few small bugs
Translated V3.2.0 new messages+some improvements by @GMagician
Add new App Manager
Used to convert apps into system apps and revert them back. No apps are moved to /system, but instead moved between /data/app and /data/app-system
Note that this feature is a paid feature. The downloads at XDA are unlocked, but installs and updates from Play Store is not
Settings: Add fallback installs for S-On devices
Uses the recovery as a fallback installer for the script and sqlite in case of HTC S-On protection
RootFW: Rebuild Instance Extender
Fixes a small issue where the shell was not always connected after boot on the first app launch
Version: 3.2.0
Add Italian translation by @GMagician
Preferences: Avoid using RootFW.Filesystem.statFstab if possible
RootFW.Filesystem.statMount is faster
Upstart Script: Fix a few shell bugs in environment setup
Possible boot loop cause
Settings: Cleanup script installer
Should fix the issue with the script not always getting installed
Settings: Add SQLite3 installer
New feature to install and/or fix the SQLite3 binary
RootFW: Do not use goldfish files on non-emulator devices
Avoid having wrong partitions located and recovery cleaned
Version: 3.1.8
Add Portuguese translation by @_MarcoMarinho_
Allow translating tab names for tablet layout
In tablet layout, there is text displayed for each tab. This should also be translated
Update English language file
Small corrections
Add missing tablet layout tab names strings
Add Danish translation
Settings: Allow translating upstart script info
Also display words like 'Versions', 'Bundled' and 'Installed' in Application Settings
Upstart Script: Fix not detecting folder suppport
Fix issue where the Application alerts about some Data folders not being moved
RootFW: Fix nullPointerException when no SWAPS are active
Issue where the Application would crash if no SWAP or ZRAM device was activated
RootFW: Fix hanging issues with Kutch SuperUser Daemon mode for Android 4.3
Bug in the SuperUser Daemon which would make some Shell types hang randomly
Version: 3.1.4
Added Dutch translation by @Skippernl
Upstart Script: Handle empty values better
Reset properties if their values are empty
Better log entry structure to better detect empty property values
RootFW: Fix write() not working
Bug in the write() method was causing empty values to be written to the property files
RootFW: Fix ArrayIndexOutOfBoundsException issue
Would sometimes cause a crash when getting stats on none existing directories
Version: 3.1.2
Update french locale and fix default one by @PerfectSlayer
Use the correct strings in the infobox
Display a log announcment instead of safe-mode information when there are warnings/errors in the log
RootFW - Fix java divide by zero Exception
Was causing crash when calculating usage percentage on partitions with 0 bytes used
Make better compatibility between different devices and ROM's
Revert Busybox binary
Create a more controlled environment to have the script executed in
Better variable export feature
Change temp dir /tmp ~> /mounts2sd-tmp
To fix issues where a ROM clears /tmp after boot
Generate more logging to help debug issues
Now generates both the regular /mounts2sd-tmp/log.txt and /data/local/mounts2sd.log which is not deleted on device shutdown
Click to expand...
Click to collapse
XDA:DevDB Information
Mounts2SD, a App for the No Device
Contributors
dk_zero-cool, PerfectSlayer, Skippernl, _MarcoMarinho_, GMagician
Version Information
Status: Stable
Current Stable Version: 3.4.8
Stable Release Date: 2013-11-01
Created 2013-09-04
Last Updated 2013-11-01
Reserved
Good job. And by the way u made small mistake. Stable version should be 3.1.8
Sent from my HTC Explorer A310e using Tapatalk 4
@rcane said:
Good job. And by the way u made small mistake. Stable version should be 3.1.8
Click to expand...
Click to collapse
Thanks, it has been corrected
When i try to install the script. Error popup that it failed to move 10mounts2sd.sh to system/etc/.
using galaxy note, jelly bean 4.1.3
jasonkhoo87 said:
When i try to install the script. Error popup that it failed to move 10mounts2sd.sh to system/etc/.
using galaxy note, jelly bean 4.1.3
Click to expand...
Click to collapse
Same problem here.
jasonkhoo87 said:
When i try to install the script. Error popup that it failed to move 10mounts2sd.sh to system/etc/.
using galaxy note, jelly bean 4.1.3
Click to expand...
Click to collapse
Okay, could you instead post this as an issue (top pane)?
Sent from my GT-I9300 using XDA Premium 4 mobile app
Says I need busybox and int. I should also say rooted sgh-i137 running skyrom 9.3
Sent from my SAMSUNG-SGH-I317 using Xparent Cyan Tapatalk 2
hmmmm....can't use this app on my Xperia Mini Pro (Carbon Rom v4.2.2)....i manage to install the scripts and after change a few in setup i reboot the phone then BAMMMMMMMM.....stuck on bootlogo....
iPusak Gaoq™ said:
hmmmm....can't use this app on my Xperia Mini Pro (Carbon Rom v4.2.2)....i manage to install the scripts and after change a few in setup i reboot the phone then BAMMMMMMMM.....stuck on bootlogo....
Click to expand...
Click to collapse
And I will gladly help you with this problem, but please use the Bug Report feature at the top of the Thread. It makes it much easier to keep track of current reports. Also, can you add a logcat entry of this issue as well?
dk_zero-cool said:
And I will gladly help you with this problem, but please use the Bug Report feature at the top of the Thread. It makes it much easier to keep track of current reports. Also, can you add a logcat entry of this issue as well?
Click to expand...
Click to collapse
Hope you have a copy of that paragraph so that can just paste.. probably need to use it often.
Sent from my OptimusBlack using xda app-developers app
Is it compatible with link2sd?
I'd like to move swap and cache on the second partition.
There's a separate q&a thread...just in case you weren't aware....
http://forum.xda-developers.com/showthread.php?t=1342387
romualdrichard said:
Is it compatible with link2sd?
I'd like to move swap and cache on the second partition.
Click to expand...
Click to collapse
Of cause not. Link2SD is not compatible with Mounts2SD or vise versa. You can't have two sd-ext scripts doing the same things and expect it to work.
using 4ext recovery and have sd-ext set up on sd card. rom boots fine. and i have the latest version of mounts2sd installed, under app settings i have the start up script installed, have green ck dot for applications, but still get insufficent avl, im very green when it comes to apps2sd and mounts2sd, the guides are not too helpful. any help here would be great. thx. jake
jaxenroth said:
using 4ext recovery and have sd-ext set up on sd card. rom boots fine. and i have the latest version of mounts2sd installed, under app settings i have the start up script installed, have green ck dot for applications, but still get insufficent avl, im very green when it comes to apps2sd and mounts2sd, the guides are not too helpful. any help here would be great. thx. jake
Click to expand...
Click to collapse
What does the size information say about your partitions? You can see this in the app. If cache or data is using to much space, it does not help much to have moved the APK's. And also, what about the Threshold, is that displaying more than what is left on data?
If dont check options that move data from /data/data into/sd ext/data/ whether to open the app to be faster?.
My memory card is 4gb class 4.
dejanxxxx said:
If dont check options that move data from /data/data into/sd ext/data/ whether to open the app to be faster?.
My memory card is 4gb class 4.
Click to expand...
Click to collapse
It all depends on the sdcard whether it slows down or not. I have a 16GB Kingston class4, and this card has faster read and write speed than the internal nand on the SGS3, so I actually gain speed by moving content to sd-ext.
The best cards when using sd-ext, is Kingston, Samsung and ScanDisk. The best class value is 2, 4 and 6 (High values is not good when using sd-ext). The worst is class10 (Don't know why). Also, lower readahead is mostly a good thing, but not if you do a lot of PC~>Phone transfers. So if you don't copy much from PC to Phone, I would lower it to 128KB.
Also, you could always try. If you think that your phone get's slower by moving /data/data, then you can just move it back.
dk_zero-cool said:
Kingston class4, so I actually gain speed by moving content to sd-ext.
The best cards when using sd-ext, is Kingston, Samsung and ScanDisk. The best class value is 2, 4 and 6 (High values is not good when using sd-ext). The worst is class10 (Don't know why). Also, lower readahead is mostly a good thing, but not if you do a lot of PC~>Phone transfers. So if you don't copy much from PC to Phone, I would lower it to 128KB.
Also, you could always try. If you think that your phone get's slower by moving /data/data, then you can just move it back.
Click to expand...
Click to collapse
Thanks, my card is Kingston, mean you say that be better that put lower readahead, on me when look on script for readahead is default 512kb, did leave thus?. Some say that be better that be a 2048kb readahead.
For copy from PC to phone, use air droid, I copy litlle much from PC to phone and conversely, and now how would you put in for readahead?
Ok, I do like you say for readahead,and leave on 512kb, it is deafult read.
Now I leave data/ data, on my internal memory,and only 47mb use.I have small internal memory 158mb free wheb flas ROM. On default is 512mb RAM.
dejanxxxx said:
Thanks, my card is Kingston, mean you say that be better that put lower readahead, on me when look on script for readahead is default 512kb, did leave thus?. Some say that be better that be a 2048kb readahead.
For copy from PC to phone, use air droid, I copy litlle much from PC to phone and conversely, and now how would you put in for readahead?
Ok, I do like you say for readahead,and leave on 512kb, it is deafult read.
Now I leave data/ data, on my internal memory,and only 47mb use.I have small internal memory 158mb free wheb flas ROM. On default is 512mb RAM.
Click to expand...
Click to collapse
Many people think that higher number means better performance, but they never take into account the scenarios. Large readahead is great for large file transfers and small readahead is good for many small reads and writes. So if you often copy multiple gb of music, movies etc to your phone, then yes, a large readahead would be better. If the system is constantly writing small amounts of data to the drive, then smaller readahead is better. The best would properly be around 4kb, but since you also use the first partition as a storage device, it is best to find a middle (Around 128kb, 256kb or 512kb depending of how much transfers you make).
It's like people who thinks that a large CPU is better in their computer, without thinking about whether or not their old HDD can actually keep up with that speed. Grater number does not mean better. A perfect balance is what you should go for.
Q&A for [MOD/APK] CLEANSER for CM12 v1.9 [multi-devices]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [MOD/APK] CLEANSER for CM12 v1.9 [multi-devices]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
hinxnz said:
Please request for an App if you don't see it in the list.
Click to expand...
Click to collapse
Play movies & TV APP
DomagojX said:
Play movies & TV APP
Click to expand...
Click to collapse
Yeah I was thinking of adding gapps removal, I only using pico gapps which is very minimal.
Do you have full gapps? Could you enter code below in terminal for me and post outcome.
The code just creates a list of your system apps.
Code:
ls /system/app /system/priv-app
I have micro gapps
here you go
Code:
acct
cache
charger
config
d
data
default.prop
dev
devlog
etc
file_contexts
firmware_q6
firmware_radio
fstab.pyramid
init
init.cm.rc
init.environ.rc
init.pyramid.rc
init.pyramid.usb.rc
init.rc
init.superuser.rc
init.trace.rc
init.usb.rc
init.zygote32.rc
mnt
proc
property_contexts
root
sbin
sdcard
seapp_contexts
selinux_version
sepolicy
service_contexts
storage
sys
system
tombstones
ueventd.pyramid.rc
ueventd.rc
usbdisk
vendor
BasicDreams
Bluetooth
Browser
CMFileManager
CMWallpapers
Calculator
Calendar
Camera2
CaptivePortalLogin
CertInstaller
ConfigUpdater
DeskClock
Development
DeviceSettings
DocumentsUI
DownloadProviderUi
Eleven
Email
Exchange2
FaceLock
Galaxy4
Gallery2
Gmail2
GoogleCalendarSyncAdapter
GoogleContactsSyncAdapter
GoogleTTS
HTMLViewer
HoloSpiralWallpaper
InCallUI
KeyChain
LatinIME
LiveWallpapers
LiveWallpapersPicker
LockClock
Maps
NoiseField
OpenWnn
PacProcessor
PackageInstaller
PhaseBeam
PhotoPhase
PhotoTable
PicoTts
PrintSpooler
Provision
SoundRecorder
Stk
Terminal
UserDictionaryProvider
Videos
VisualizationWallpapers
WAPPushManager
webview
AudioFX
BackupRestoreConfirmation
CMAccount
CMUpdater
CalendarProvider
CellBroadcastReceiver
Contacts
ContactsProvider
CyanogenSetupWizard
DefaultContainerService
Dialer
DownloadProvider
ExternalStorageProvider
FusedLocation
GmsCore
GoogleBackupTransport
GoogleFeedback
GoogleLoginService
GoogleOneTimeInitializer
GooglePartnerSetup
GoogleServicesFramework
InputDevices
MediaProvider
Mms
MmsService
OneTimeInitializer
Phonesky
ProxyHandler
Settings
SettingsProvider
SetupWizard
SharedStorageBackup
Shell
SystemUI
TeleService
Telecom
TelephonyProvider
ThemeChooser
ThemesProvider
Trebuchet
Velvet
VoiceDialer
VpnDialogs
WallpaperCropper
com.hinxnz.cleanser.apk
talkback
[email protected]:/ $
Persistent scripts
Hi,
How does the persistent app removal work? I ran the installer and it beautifully removed all the bloat from the ROM.
But on upgrades it seems that the bloat is added again and not automagically removed. Do i have to do something to make it run the cleanup scripts again?
I am using TWRP v2.8.6.0
-m4rcu5
m4rcu5.net said:
Hi,
How does the persistent app removal work? I ran the installer and it beautifully removed all the bloat from the ROM.
But on upgrades it seems that the bloat is added again and not automagically removed. Do i have to do something to make it run the cleanup scripts again?
I am using TWRP v2.8.6.0
-m4rcu5
Click to expand...
Click to collapse
With an addon.d and init.d script.
Did you upgrade ROM from CM12 to CM12.1 because in the backup script in the ROM.zip, it removes all addon.d scripts, I don't know why but I guess to avoid incompatibility issues.
Or on all ROM upgrades? Did you enable survival mode in the installer?
hinxnz said:
With an addon.d and init.d script.
Did you upgrade ROM from CM12 to CM12.1 because in the backup script in the ROM.zip, it removes all addon.d scripts, I don't know why but I guess to avoid incompatibility issues.
Or on all ROM upgrades? Did you enable survival mode in the installer?
Click to expand...
Click to collapse
I just did an CM12.1 snapshot update (clicked download in the updater, said yes to install, and then manually selected the zip to install in TWRP) but all the bloat re-appeared. I did have the cleanser zip installed.
So to de-bloat I did the following:
Rebooted into TWRP, installed the cleaner.zip, selected app-removal, ticket the "install persistent script", selected a whole bunch of apps (including the launcher), next, next, reboot. Installer exited with code 0.
Is there any way to recognize the cleaner init.d script when it should run?
m4rcu5.net said:
I just did an CM12.1 snapshot update (clicked download in the updater, said yes to install, and then manually selected the zip to install in TWRP) but all the bloat re-appeared. I did have the cleanser zip installed.
So to de-bloat I did the following:
Rebooted into TWRP, installed the cleaner.zip, selected app-removal, ticket the "install persistent script", selected a whole bunch of apps (including the launcher), next, next, reboot. Installer exited with code 0.
Is there any way to recognize the cleaner init.d script when it should run?
Click to expand...
Click to collapse
If the installer exited without finishing then it wouldn't work. Try turning off phone, removing battery for 5 secs if you can or how ever you reset device if you can't remove battery and try again, I can't think of a reason why it shouldn't work now. Try wiping cache then reboot recovery. You could upload recovery log if still getting the error.
hinxnz said:
If the installer exited without finishing then it wouldn't work. Try turning off phone, removing battery for 5 secs if you can or how ever you reset device if you can't remove battery and try again, I can't think of a reason why it shouldn't work now. Try wiping cache then reboot recovery. You could upload recovery log if still getting the error.
Click to expand...
Click to collapse
I just ran another test.
Wiped cache and dalvik.
Installed cleanser.zip, set up survival scripts, installer exited successfully.
Installed the latest snapshot.
Rebooted the phone into OS.
Android started upgrading the apps.
At this point the cleanser did nothing, the homescreen appeared and asked me if i would like to use trebuchet (one of the things I removed). Another reboot after that also triggered nothing.
The only way to get sanity restored is to launch recovery, run the cleanser.zip again and remove the apps.
What can I send to help find out why the cleaners did not run at step 4?
m4rcu5.net said:
I just ran another test.
Wiped cache and dalvik.
Installed cleanser.zip, set up survival scripts, installer exited successfully.
Installed the latest snapshot.
Rebooted the phone into OS.
Android started upgrading the apps.
At this point the cleanser did nothing, the homescreen appeared and asked me if i would like to use trebuchet (one of the things I removed). Another reboot after that also triggered nothing.
The only way to get sanity restored is to launch recovery, run the cleanser.zip again and remove the apps.
What can I send to help find out why the cleaners did not run at step 4?
Click to expand...
Click to collapse
It's because you installed rom straight after flashing mod and mod couldn't configure the scripts upon reboot.
Edit: PM sent with test version.
hinxnz said:
It's because you installed rom straight after flashing mod and mod couldn't configure the scripts upon reboot.
Click to expand...
Click to collapse
Another couple of tries later i still cannot get it to work
- On a working ROM, install cleanser via recovery.
- App Removal, tick Survival mode, tick a bunch of apps (including trebuchet en file manager), Remove now, It finishes without problems, reboot.
- Now I have a nice and clean ROM.
Next CM update;
- Download the update, hit update. System boots recovery, installs CM update and boots.
- You see android updating the Apps and dropping to lockscreen.
But after unlocking, all the cruft is still there.
It seems as if the init script is either not deployed, removed on update or fails.
m4rcu5.net said:
Another couple of tries later i still cannot get it to work
- On a working ROM, install cleanser via recovery.
- App Removal, tick Survival mode, tick a bunch of apps (including trebuchet en file manager), Remove now, It finishes without problems, reboot.
- Now I have a nice and clean ROM.
Next CM update;
- Download the update, hit update. System boots recovery, installs CM update and boots.
- You see android updating the Apps and dropping to lockscreen.
But after unlocking, all the cruft is still there.
It seems as if the init script is either not deployed, removed on update or fails.
Click to expand...
Click to collapse
Can you post outcome of this code in terminal:
Code:
ls /system/etc/init.d /system/addon.d
hinxnz said:
Can you post outcome of this code in terminal:
Code:
ls /system/etc/init.d /system/addon.d
Click to expand...
Click to collapse
Yes, sure:
Code:
~$ ls /system/etc/init.d /system/addon.d
00
00aae
00aaf
00aag
00aao
00aar
00aat
00aav
00aax
00aaz
00banner
90userinit
30-gapps.sh
31-faceunlock.sh
50-cm.sh
55-cleanser.sh
blacklist
~$ cat /system/addon.d/55-cleanser.sh
#!/sbin/sh
#
# /system/addon.d/55-cleanser.sh
#
. /tmp/backuptool.functions
list_files() {
cat <<EOF
etc/init.d/00
etc/init.d/00a
EOF
}
case "$1" in
backup)
list_files | while read FILE DUMMY; do
backup_file $S/$FILE
done
;;
restore)
list_files | while read FILE REPLACEMENT; do
R=""
[ -n "$REPLACEMENT" ] && R="$S/$REPLACEMENT"
[ -f "$C/$S/$FILE" ] && restore_file $S/$FILE $R
done
;;
pre-backup)
# Stub
;;
post-backup)
# Stub
;;
pre-restore)
# Stub
;;
post-restore)
# Stub
;;
esac
~$
m4rcu5.net said:
Yes, sure:
Code:
~$ ls /system/etc/init.d /system/addon.d
00
00aae
00aaf
00aag
00aao
00aar
00aat
00aav
00aax
00aaz
00banner
90userinit
30-gapps.sh
31-faceunlock.sh
50-cm.sh
55-cleanser.sh
blacklist
~$ cat /system/addon.d/55-cleanser.sh
#!/sbin/sh
#
# /system/addon.d/55-cleanser.sh
#
. /tmp/backuptool.functions
list_files() {
cat <<EOF
etc/init.d/00
etc/init.d/00a
EOF
}
case "$1" in
backup)
list_files | while read FILE DUMMY; do
backup_file $S/$FILE
done
;;
restore)
list_files | while read FILE REPLACEMENT; do
R=""
[ -n "$REPLACEMENT" ] && R="$S/$REPLACEMENT"
[ -f "$C/$S/$FILE" ] && restore_file $S/$FILE $R
done
;;
pre-backup)
# Stub
;;
post-backup)
# Stub
;;
pre-restore)
# Stub
;;
post-restore)
# Stub
;;
esac
~$
Click to expand...
Click to collapse
Yeah init.d scripts aren't applied, it probably a mount issue.
I'd say system is read only. I'll fix it when I have some time and maybe drop you a test version first.
hinxnz said:
Yeah init.d scripts aren't applied, it probably a mount issue.
I'd say system is read only. I'll fix it when I have some time and maybe drop you a test version first.
Click to expand...
Click to collapse
Cool,
I will be sticking around.
Let me know if you need more info!
hinxnz said:
Yeah init.d scripts aren't applied, it probably a mount issue.
I'd say system is read only. I'll fix it when I have some time and maybe drop you a test version first.
Click to expand...
Click to collapse
Hey, Did you have any chance building the new version?
m4rcu5.net said:
Hey, Did you have any chance building the new version?
Click to expand...
Click to collapse
Hey been busy, maybe able tonight, I'll pm you.
Edit: Hey there, did you manage to test the cleanser.zip v2.1 that I sent you?
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
Read Only to Read Write for android (RO2RW) Update 03.01.2023 : Stable Beta v 3.7.2.1The first truly working script, original and unique in its logic for all devices with a SUPER partition
Universal auto RO2RW | EROFS-2-RW | F2FS-2-RW by LeeGarChat
{
"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"
}
Spoiler: Screenshots
Short description:
Converts EROFS, EXT4(RO), F2FS Super partition to RW
Description:
A simple utility to convert your Super partition to RW mode (Read/Write) As well as the expansion and distribution of free space for each section, depending on how much space is available in the original Super section.
You can flash both via:
1. TWRP: by using controls in the script: (Volume control (+) to switch, Volume control (-) to select) in this case, the new super RW is flashed directly.
2. Magisk module: in this case you will need to go to the terminal and enter RO2RW, and a new RW-super.img will be prepared in the internal memory, you can choose both image output for FASTBOOT and RECOVERY.
For these two modes, the creation of the original super as a backup is supported, the file will also be output to the internal memory as bak-super.img
Spoiler: FAQ
Do I need to format the data after installation?- No, it is not necessary in normal cases, this script does not affect encryption in the data section. But in some cases, it is necessary to do the date format, it is not yet clear how this is related, for example on Asus devices.
Why do I need this script, for what and why; why do I, need it?- When your system partitions have read-only mode (RO), then you cannot integrate modifications directly into the firmware, (such as Viper4Android) as well as manually edit/delete files from system partitions. This script converts it in the case of F2FS and EROFS to EXT4, or forcibly in the case of EXT4 enables the "Read/Write" (RW) mode, and also expands partitions as much as possible.
What are systems partitions?What are system partitions?
- These are the sections that are located in the main container "super" (the script is focused only on devices with super), it includes system, product, vendor, etc., when mounting the system, the structure looks like this:
System <--- In TWRP it is mounted as /system_root
, in the system itself it is mounted as
Code:
/ <--- The main mount point for system
├── /product <--- The main mount point for product
├── /vendor <--- The main mount point for vendor
|
├── /system <--- Here are the main system files
│ │
│ ├── /system/vendor <--- Additional mount point for vendor
│ │
│ ├── /system/product <--- Additional mount point for product
And by analogy with product and system, all other partitions, or other mount points. This can be viewed in the fstab file located in vendor/etc/
Some files cannot be edited at the root, or even if they can be edited without RW, those modifications won't stick, because these are temporary files responsible for the operation of the kernel and the entire linux system, in this case android. For example, proc, or sys, if you open a clean image, or mount a system image, you will see that these folders are empty, and files appear there only after the system is started.
Is ROOT required?- If you want to prepare a new super partition inside the system, then you need it, the firmware via TWRP does not need root.
How does the script work in Magisk?- You need to install the archive via Magisk manager as a module, the script will tell you if you need to restart the device. Next, you need to launch the terminal and give it root rights with the command "su", Then enter the command "RO2RW" and the script will run, it will prepare an image of RW-super.img according to your choice and optionally backup the original super bak-super.img, these files will be located in internal memory, after which you need to them to a PC if it is a fastboot image, or flash it via TWRP as super img if the images are for recovery.
What does S=40% SE=10% and so on mean?- This is the distribution of free space in the super between the partitions 'System=S' 'Product=P' 'System_ext=SE' 'Vendor=V' 'Other sections are there they are= OT'
- For example: The whole system occupies a conditional 4.7 GB. The super partition always has a fixed size in the memory block on the device, for example, take the example with PocoF3, it has 8.5GB there
Code:
Super size 8.5-GB
{1111111111,111111111111,111111111,11111,11111111,111111111111111,000000000000000}
System System_ext Product Odm Vendor Others if any Unused memory
2.2/2.2G 0.5/0.5G 0.8/0.8G 7/7M 1.2/1.2G 1/1GB 3.8~G
- As you can see, there is unused space for the second slot in the section (In 99.99% of cases it is not needed for users with root), and we can use this space for expansion of the partitions, and for system, 40% of this free space will be distributed. For system_ext 10%, for other partitions, if there are any, conditional 10% will be divided between all of them
RO2RW worked correctly, and the system started, but I can't delete or change files, what is the reason?- Perhaps you have some Magisk module installed that prevents you from doing this, for example OverlayFS.
Also, the reason may be that your device is of the MTK family, in some models there is a restriction at the kernel level for changing system partitions, and therefore mounting in RW, you will not even be able to reinstall magisk on such devices from the system
In this case, you open the way only to modding via TWRP
Also, you need to use the latest version of a normal file manager, these are the ones I recommend:
Solid Explorer File Manager
Solid Explorer File Manager - Apps on Google Play
Organize, protect and share your files in a dual pane layout.
play.google.com
Root Explorer
Root Explorer - Apps on Google Play
The ultimate file manager for rooted devices. The original and still the best.
play.google.com
MT manager
下载 | MT管理器
MT管理器官网
mt2.cn
RO2RW worked correctly, the system started, but in any section, for example vendor, there is little free space available, 2-10mb, can it be expanded somehow?In- That's how it will not be possible to expand a lot, this is due to the limitation of space in the super itself. System partitions occupy a certain amount of space in it, in response to "What does S=40% SE=10% and so on mean?" there is an example of how it works inside. So, perhaps your firmware weighs a lot, and there is simply not enough space in the super itself, you can fix it if you know what you are doing, you need to remove any garbage, applications from the system partitions.
"/" is system, including "/system/
"/vendor" is a vendor, including "/system/vendor", with the rest of the sections in the same way by analogy. Some partitions have a different mount point, this can be viewed in your fstab, it is located along the path /vendor/etc/*fstab*.
So, you first need to delete something from the system partitions, after which, according to the configuration in RO2RW (it is available in config.txt inside the archive, or in the first choice when installing where "max expansion"), distribute the size according to percentages or a fixed size, i.e. flash ro2rw again, or generate rw-super one more time.
Will RW disappear after the OTA software update?- Yes, in this case, after OTA, you need to boot into the system first, the process will take place, re-mark super for new data, after that you can make a new super through the system or through TWRP:
1. OTA installation
2. Reboot into the system
3. Preparing a new super, or rebooting in TWRP
4. Installing a new super via fastboot, or firmware the archive inside TWRP
How to flash a file via fastboot?- You need to move the finished file from the phone to the PC, throw RW-super.img into the folder with fastboot/adb, switch to fastboot mode on the phone, and enter the command in the console on the PC "fastboot flash super RW-super.img".
Read more about using fastboot in the branch of your device.
What are the differences between the first 4 options and the rest when first selected in the script?- The first four expand the sections based on the maximum size of the super, the rest expand on a fixed scale for each section, for example, it is more logical for OnePlus to choose one of the first 4, since there are a lot of sections, about 8, and it will be very large size to expand each by the same 200 MB.
I cannot delete or modify files from /system/app or from /product/app or from any other specific directory, but at the same time in this directory or I can create a file, and at the same time in the neighboring directory I can change files, the system is RW, how to fix it?- This happens due to the non-direct mounting of specific folders, it is called overlay filesystem, more about it here: https://wiki.archlinux.org/title/Overlay_filesystem
It specifically mounts any folder read-only. At the moment, you can delete or change or add to this directory only via TWRP, having previously flashed RO2RW by selecting the LiteRW option.
Or go to the terminal and write the commands:
Code:
su
magisk --path
The last command will show the path to the magisk directory, you will need to follow the path:
"The path that the magisk --path command displayed"/.magisk/mirror/
There will be partitions that Magisk mounts directly; by going to them, you will be able to change files without obstacles from OverlayFS.
I have a device with 32GB of memory, I do not know which option to choose so that the memory does not suffer?- The super section occupies a fixed size in the device's memory and has already been marked up by the manufacturer, i.e. even if the system takes up a conditional 2 GB, super still takes up all its conditional 6 GB in memory, I wrote above about how memory is distributed in super.
Why does the script at some point ask to delete some applications?- This means that the firmware weighs a lot, and after conversion to RW, it does not fit into super, my script suggests deleting some system applications, for example, in Chinese miui there are such stupid advertising things as TikTok, MiShop, etc. Applications are removed from temporary partitions that are being prepared for conversion to super, from the installed system you do not delete anything, well, if you only interrupt the process, after installing a new super, naturally the applications will disappear.
So why should I redistribute something, I didn't understand. I don't care how the system distributes its "empty space" there, they are still not used by me for files, because it's still a system partition. Just need RW super in the same form as it is. That's all. Is it possible somehow without distribution?- No, you can't, because it won't be original anyway, it won't affect user memory, it won't affect the OTA process if the firmware is pumping FullOTA, only the process of light (incremental) updates that weigh from 2mb to 800mb on average will be prohibited, and the process will not become faster. And if you don't care, then don't you care that there is free memory in the system partitions? in any case, you can fix it through the config as you need and give 1% for all partitions, or 10 or less MB for all partitions.
If all the tests turn out to be successful, I will start adding more features to the script, so I'm waiting for the tests, and also please fill out the Google form if RO2RW worked correctly or incorrectly, by doing this you help the development, as well as other people to understand how it works on their device and their ROM
Do not PM me about the script and help without permission, write to the support group
DOWNLOAD - SourceForge
TG Group
Telegram support chat for quick feedback
Donate only TG link https://t.me/mfpupdate/47
Credits:
- Thanks to the first link in a Google search for" e2fsck --help" link for clarification on disabling RO
- Many thanks to my own tests with the super section and the official Google utilits lpdump/lpmake/lpunpack as well as the --help menu for it
- Many thanks to the first Google search result for explaining tune2fs and resize2fs
- Thanks to the Magisk team for the BusyBox and bootctl binary
- Thanks to the kory-vadim with UKA for the make_ext4fs bibary, and thanks help menu make_ext4fs
- Thanks to SKKK for the erofs.unpack binary
- Thanks all test users
Please take the survey for more RO2RW statistics
Google Forms: Sign-in
Access Google Forms with a personal Google account or Google Workspace account (for business use).
docs.google.com
Also, the entire list from the survey will be available on this table
RO2RW Support list
Ответы на форму (1) Отметка времени,You Device name: Example "Poco F3",You Device Code: Example "Alioth",ROM: Example "ArrowOS Official 12.11.22",Was the installation successful?,Attach a log file. Located on the path /sdcard/NEO.LOGS/,A brief description of wishes or problems,Which version RO2R...
docs.google.com
Changelog:
Stable Beta 3.7.0.0:
[MAGISK][TWRP][ARM32/64][A8+]Universal Read Only to Read Write for android (RO2RW) | Auto converting SUPER "system partitions" to read/write mode
Read Only to Read Write for android (RO2RW) Update 03.01.2023 : Stable Beta v 3.7.2.1 The first truly working script, original and unique in its logic for all devices with a SUPER partition Universal auto RO2RW | EROFS-2-RW | F2FS-2-RW by...
forum.xda-developers.com
- Fixed non-removable logs. (To delete old logs from versions 3.6.2.1 and below, go to the /data/media/0/NEO.LOGS directory and you can delete them, or in TWRP and delete them
- Changed configuration logic for RW_SIZE and RW_SIZE_MOD parameters
- Changed the logical chain of appearance of SELECT MENU when there was a request for mount2ext4 or continue without mounting
- The logic has been completely redesigned, when in case of unsuccessful mounting, all partitions were not mounted, now everything will be mounted, except for unsuccessful ones during installation, only EXT4 is affected
- Completely redesigned config.txt, a simple one will open it and be surprised
- Now added support for forced start of the script (FOR TWRP), just configure the config as you need, in case of any failure, the script will fall into an error, do not be afraid
- Added a parameter to the config to disable timeout for the volume keys, so that the script does not fall into an error when you do not press the button for a long time
Stable Beta 3.6.2.0:
- Added avbctl for arm32, thanks for providing binaries: brigudav and Bodya-Kolibass
Stable Beta 3.6.1.1:
- Fixed work in arm32
- fixed chcon
Stable Betav3.6.0.0
- Add with only arm32 linker devices support (Support arm32)
Stable Betav3.5
- Added support for OTG and MicroSD
- Added LiteRW for Recovery mode. Some firmware is enough LiteRW
- Added manual configurator inside the script during execution in a running system through the terminal
- Added display of main paths to directories
- Fixed work for encrypted date if it is not available
- Fixed work "check RW and free size"
- Improved LiteRW code compared to LiteRW 3.0
Stable Beta 3.4.2
- Added the ability to check for RW partitions, and for free space in them. Access is available in TWRP and Terminal via termux
- Added the ability to delete pre-delete system applications
- There is an opportunity to choose "Forced deactivation of verivication and verity, or prepare patched vbmeta for manual firmware
- Fixed the work of ignoring the mounting of partitions for checking in the case of ext4
- Fixed code optimization in half of the code, cut the code thanks to universal functions
- Fixed a bunch of issues
- Fixed work install.sh in TWRP, after separating from update-binary
- Fixed work config.txt
- Fixed bash shell operation
- Fixed the calculation of free space in the super section
- Still need Samsung testers for F2FS
Beta 3.3
- Added e2fsck,tune2fs,resize2fs binaries from termux libraries
- Added the ability to ignore additional checks for ext4 systems, because of which images will not be mounted, because of which it is possible to bypass one of the errors in the previous version. But in this case DFE will not be installed
- Another fix for working with F2FS images
- Added an additional method for cases when you need to mount system images to migrate files to a new image, if direct mounting fails, an image dump will be created and it will already be mounted
- Fixed English language in the script
- Added "SKIP" option for DFE, if you don't know what it is, then press SKIP
- Moved to the bash shell, taken from the termux library, now the sh shell built into recovery / android will not be used.
- Executable script is now separated from update-binary
- Other minor fixes
- now u can use commands: RO2RW,ro2rw
Stable Beta 3.2
- Fixed work for F2FS systems, for Samsung. But you need to do additional manipulations for this, for example, to flash a custom kernel according to tests with a Samsung user comes out exactly like this.
- Fixed the problem of detecting an active slot
- The output of files has become with an informative file name like super.sparse.fastboot.active.slot._a.img
- Also, no patches are applied inside the active system, now you need to flash the same vbmeta through the rrecovery, or fastboot, it will also be output as patched and original in the case of a backup
Stable Beta 3.1.1
- Fix modified fstab for F2FS
Stable beta 3.1
- Add dfe (legacy mode) as an additional option
- Fix 55 error and need 9+gb free space for all devices
- Many text inscriptions for users have been corrected and new ones have been added so that users do not swear and understand what is happening
Beta 3.0.4:
- A lot of fixes when converting images
- Fixed a problem when dm-verity sometimes did not turn off
Beta 3.0.3:
- Fixed installation in Magisk
Beta 3.0.2:
- Small fixes
Beta 3.0.1:
- Slightly tweaked the calculator, some problems may have been fixed
Beta 3.0
- Maybe fixed the issue for some OnePlus devices
- Maybe fixed issue for new Samsung devices
Alexey NoOne in MFP, DFЕ, RO2RW, for Android 10+
t.me
- Added the ability to make a backup of the original super inside the custom recovery (TWRP,OFox)
- The methods for converting images from versions 2.8 and 2.9 are combined, and it seems to me that F2FS support has been added, in theory it should work, but testing is needed
Spoiler: Older
Beta 2.9
- The procedure for converting to EXT4.img has been redesigned, there is no longer a need to mount the file system, except in cases where you need to free memory (remove) any garbage from images
Beta 2.8
- Fixed counting and comparison of large numbers for some devices
ZeReF ft in MFP, DFЕ, RO2RW, for Android 10+
t.me
ZeReF ft in MFP, DFЕ, RO2RW, for Android 10+
look at the size how to fix it
t.me
ZeReF ft in MFP, DFЕ, RO2RW, for Android 10+
t.me
Alexey NoOne in MFP, DFЕ, RO2RW, for Android 10+
t.me
- Added check for free memory before creating RW-super.img. will loop until there is enough free space
- Added an inscription about updating the script for magisk, if there was an update, then you do not need to restart the system, otherwise it will be said that you need to restart the system
Alexey NoOne in MFP, DFЕ, RO2RW, for Android 10+
t.me
- Added the ability to backup the original super partition, both in row for recovery and sparse for fastboot
Alexey NoOne in MFP, DFЕ, RO2RW, for Android 10+
t.me
- Added extensive log file with output folder /storage/emulated/0/NEO.LOGS a.k.a /sdcard/NEO.LOGS
Alexey NoOne in MFP, DFЕ, RO2RW, for Android 10+
t.me
Beta 2.7
- Fixed a critical issue when the script was interrupted halfway through and was restarted, in which case data from system partitions could be deleted
- Fix metadata read, moved to android-tools binary from termux pkg
Toni Moon in MFP, DFЕ, RO2RW, for Android 10+
Screenshot (20 nov 2022 23:19:06)
t.me
- Fix install for magisk with hide magisk app
Toni Moon in MFP, DFЕ, RO2RW, for Android 10+
t.me
- Fix calculate size for fixed size like 200-250mb
Thequellu in MFP, DFЕ, RO2RW, for Android 10+
Not work 150,200,250 for me
t.me
- Fixed a bug of different binary files in ROM, moved to a single busybox
Beta 2.6
- Added mode for Magisk.
Spoiler: DEMO MAGISK
Your browser is not able to display this video.
- Fixed some bugs that I don't remember anymore
Beta2.5:
-Fix awk calculate for any device
Sergiocubano1 in MFP, DFЕ, RO2RW, for Android 10+
t.me
Sergiocubano1 in MFP, DFЕ, RO2RW, for Android 10+
t.me
-add config.txt and added option to expand partitions in % or size Mb
Alexey NoOne in MFP, DFЕ, RO2RW, for Android 10+
t.me
Beta2.4:
-Fix problem with a-only devices or like system partition name when not sustem_a/_b
Alexey NoOne in MFP, DFЕ, RO2RW, for Android 10+
Like this https://t.me/PocoF3DFE/65768 ?
t.me
Beta2.3:
-fix problem when "need -(minus)xxxx Mb free size"
Cookies in MFP, DFЕ, RO2RW, for Android 10+
Why me got -3835
t.me
Beta2.2:
-Fix problem when partition have name main or same name
Ngô Túc Thanh in MFP, DFЕ, RO2RW, for Android 10+
t.me
Ngô Túc Thanh in MFP, DFЕ, RO2RW, for Android 10+
t.me
Beta2.1:
- Fix this problem with RW for partition into TWRP ( works )
bad habbit in MFP, DFЕ, RO2RW, for Android 10+
t.me
- nject a crutch for large ROMs to fix the problem ( works with later miui cn on poco f3 )
Deleted Account in MFP, DFЕ, RO2RW, for Android 10+
t.me
- Maybe Fix for A-only devices with super partition ( need test )
Alexey NoOne in MFP, DFЕ, RO2RW, for Android 10+
t.me
- Inject binary for disable DM-verity
Beta2:
-first release for test
Changelog:
Beta 3.0
- Maybe fixed the issue for some OnePlus devices
- Maybe fixed issue for new Samsung devices
Alexey NoOne in MFP, DFЕ, RO2RW, for Android 10+
t.me
- Added the ability to make a backup of the original super inside the custom recovery (TWRP,OFox)
- The methods for converting images from versions 2.8 and 2.9 are combined, and it seems to me that F2FS support has been added, in theory it should work, but testing is needed
Changelog:
Beta 3.0.4:
- A lot of fixes when converting images
- Fixed a problem when dm-verity sometimes did not turn off
Beta 3.0.3:
- Fixed installation in Magisk
Beta 3.0.2:
- Small fixes
Beta 3.0.1:
- Slightly tweaked the calculator, some problems may have been fixed
Just flash the zip in recovery?
TheGhost1951 said:
Just flash the zip in recovery?
Click to expand...
Click to collapse
Good luck getting all the the instructions it is never just flash zip with this stuff and the telegram thread or whatever is probably the hardest telegram thread to figure out in all of telegram. I have over 200 telegram threads I watch normally you'll have pinned messages with download and another pinned message with instructions a to z laid. Not this guy you'll have to figure out the puzzle that is his way of doing things
Techguy777 said:
Good luck getting all the the instructions it is never just flash zip with this stuff and the telegram thread or whatever is probably the hardest telegram thread to figure out in all of telegram. I have over 200 telegram threads I watch normally you'll have pinned messages with download and another pinned message with instructions a to z laid. Not this guy you'll have to figure out the puzzle that is his way of doing things
Click to expand...
Click to collapse
That is one of the reasons I trust lebigmac script, he is through and instructions are clear!
TheGhost1951 said:
That is one of the reasons I trust lebigmac script, he is through and instructions are clear!
Click to expand...
Click to collapse
I have been into xda now for about 6 or 7 years. I was edger to learn and even built 3 custom roms back in android 9. Every year or 2 now google makes changes that are huge changes and I still find myself having to learn things like day 1 at times. The new EROFS kernels and roms is brand new I have no idea how they work. F2FS is samsung and thats one of the reasons I was interested because I have a tab s8 plus. The problem is for this to work it makes a copy of your super partition your system. I was trying to figure all of that out and they get pissed you dont understand all of it already. Well I tried flashing it on poco f3 because I thought I was on a RO rom because of EROFS and it failed and I had 13gb of img files in a couple of folders. It requires a lot of free space and if people have there phone filled up and start flashing it will fill it all the way up depending on how big your system is compared to storage. That should be mentioned its not.
Techguy777 said:
Good luck getting all the the instructions it is never just flash zip with this stuff and the telegram thread or whatever is probably the hardest telegram thread to figure out in all of telegram. I have over 200 telegram threads I watch normally you'll have pinned messages with download and another pinned message with instructions a to z laid. Not this guy you'll have to figure out the puzzle that is his way of doing things
Click to expand...
Click to collapse
TheGhost1951 said:
Just flash the zip in recovery?
Click to expand...
Click to collapse
Techguy777 said:
I have been into xda now for about 6 or 7 years. I was edger to learn and even built 3 custom roms back in android 9. Every year or 2 now google makes changes that are huge changes and I still find myself having to learn things like day 1 at times. The new EROFS kernels and roms is brand new I have no idea how they work. F2FS is samsung and thats one of the reasons I was interested because I have a tab s8 plus. The problem is for this to work it makes a copy of your super partition your system. I was trying to figure all of that out and they get pissed you dont understand all of it already. Well I tried flashing it on poco f3 because I thought I was on a RO rom because of EROFS and it failed and I had 13gb of img files in a couple of folders. It requires a lot of free space and if people have there phone filled up and start flashing it will fill it all the way up depending on how big your system is compared to storage. That should be mentioned its not.
Click to expand...
Click to collapse
I have added a FAQ, if there are any more questions, I will expand the FAQ
TheGhost1951 said:
That is one of the reasons I trust lebigmac script, he is through and instructions are clear!
Click to expand...
Click to collapse
My script also does RW-Super.img, if you use it from the system. In any case, I started to do the design, because I started to do work on another forum. Now it is similar to that on 4 pda
LeeGarChat said:
My script also does RW-Super.img, if you use it from the system. In any case, I started to do the design, because I started to do work on another forum. Now it is similar to that on 4 pda
Click to expand...
Click to collapse
Not very clear " if you use it from the system". I have no clue what you are saying here.
TheGhost1951 said:
Not very clear " if you use it from the system". I have no clue what you are saying here.
Click to expand...
Click to collapse
If you use a script from Termux or another terminal in the running system (that is, not via TWRP), after installing as a Magisk module. I'll fix it now, I'm bad at English
Working
izsdeaman said:
View attachment 5781557Working
Click to expand...
Click to collapse
Need "mount -o rw,remount /parts"
LeeGarChat said:
Need "mount -o rw,remount /parts"
Click to expand...
Click to collapse
your script works perfectly, partitions are both readable and writable, i flashed another system.img after running the script so it doesn't have rw yet.
Update to Stable beta 3.1
- Add dfe (legacy mode) as an additional option
- Fix 55 error and need 9+gb free space for all devices
- Many text inscriptions for users have been corrected and new ones have been added so that users do not swear and understand what is happening
Stable Beta 3.1.1
- Fix modified fstab for F2FS
I have used your Script with TWRP at Xiaomi Redmi Note 10 Pro (#sweet) and it works perfectly, partitions are both readable and writable.
Many thx
I used your script with TWRP as well on OnePlus Pro 9 in combination with lebigmac's script because his script doesn't make all folders / files in the main root storage R/W. Your script helped make it possible.
My main concern: In TWRP, if I try to place any file I backed up from the system to a folder / file that is usually R/O, I get Error:1 in twrp for a simple copy and paste job. Any reason for this? Sorry I am not an expert in android file systems.
immortalwon said:
I used your script with TWRP as well on OnePlus Pro 9 in combination with lebigmac's script because his script doesn't make all folders / files in the main root storage R/W. Your script helped make it possible.
My main concern: In TWRP, if I try to place any file I backed up from the system to a folder / file that is usually R/O, I get Error:1 in twrp for a simple copy and paste job. Any reason for this? Sorry I am not an expert in android file systems.
Click to expand...
Click to collapse
Need after mount partitions "mount -o rw,remount /system_root" for system. "mount -o rw,remount /vendor" for vendor and etc partitions.
Go to advance menu, mount. Mount all parts.
Go to advance menu. Terminal and write this commands