Database Info

[ROM] 08/09 MacLite v0.8 Froyo Sense modular - DualGovernor - odexed - no buggy A2SD+

Updated to version *** MacLite v0.8 baremetal - modular *** - clean and lean, fastloading fully odexed Froyo Sense ROM without unnecessary bloat. Factory Reset save, unlike almost every other custom ROM out there and battery optimized as never before . This ROM implements a new CPU governor implementation based on screen on/off status that should theoretically be more responsive and more power efficient. Your feedback would be greatly appreciated. More info here: [INITSCRIPT] screenstate_scaling - switch CPU freq governor on screen state
Note: v0.8 includes now undervolting and some fixes and updates to v0.7/v1.0. If you still use an older release please update to v0.8 to benefit not only from the battery improvements .
Version 1.0 added. This is a full ROM, unlike the modular version, that includes all the improvements of 0.7 and adds the AppsBundle package from posting #2. This is for all people who have problems with installing the modules, and it gives you something similar to a full featured official ROM, with all applications updated to the latest versions. Download link at the bottom. Development however continues with the modular MacLite version.
--
Dear all,
I'm a member in these forums for quite some time, on the reading side most of that . But I think I could at least give a bit back to all the great folks here in the forum. Here comes the latest MacLite build so far. I've simplified and modified quite a number of things, still leaving the ROM as original as possible, while adding hopefully valuable features and performance improvements. This ROM takes ideas and contributions from many different cooked versions and information + help in the forums. Full credit goes to all of the original authors and their particular contributions. Too many to remember and not to forget anyone. Thank you all!
{
"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"
}
MacLite is based on Paul's official Modaco FroYo "original" ROM (not R8), but is re-rooted and updated to Superuser 2.3.5 + latest busybox 1.17.1. This version goes a step further, to bare metal . If you know nlite for WinXP, it's that what this is for Froyo Sense. Stripped to the core, fully odexed, as a basis for individual configurations.
The following changes and features were included:
- Automatic full wipe during installation to prevent any problems, make a backup first!
- APN fix (should find and set your APN automatically out of the box)
- Kernel tuning (Auto-Task Killer with lowmem-optimum settings)
- Kernel tuning (vm settings)
- Perflock disabler
- Interactive and Powersave Schedulers
- Implementation of FloHimself's screen on/off governor, if on, ondemand with slightly reduced max CPU freq. (800MHz for more battery juice), if off powersave with 245MHz only. Thanks! NO SetCPU required anymore and DO NOT USE IT!
- Untervolting enabled with conservative settings. Thanks iscaela
- Changed media_profiles.xml for better quality
- Terminfo
- Wifi fix for streaming in sleepmode
- Bluetooth fixes for connectivity/pairing
- New framework-res.apk with B&W Battery Indicator/Percentage
Removed space and battery wasting applications/widgets are (see posting #2 below on how to restore):
- AppSharing
- DCSStock
- Facebook
- FriendStream (broken since Twitters change to OAuth)
- FriendStreamWidget (broken since Twitters change to OAuth)
- Flickr
- Footprints
- FootprintsWidgets
- GenieWidget
- Google Search
- Google Talk
- HtcFacebook
- htcmailwidgets (do not work with the new Email client, use app instead of widget)
- install_flash_player (latest Flash player included instead)
- Learn More
- Maps (replaced, see below)
- NewsReader
- NewsReaderWidget
- PDFViewer
- Quickoffice
- Sim Toolkit
- SocialNetworkProvider
- Stocks
- StockWidget
- Teeter
- Twitter (broken since Twitters change to OAuth)
- TwitterWidget (broken since Twitters change to OAuth)
- VoiceSearch
If someone knows in where the default Picture Frame, not HTC photo frame, is hidden, please let me know. That is still something redundant.
The following were previously added applications in /data/apps, they are removed from the baremetal ROM now and are listed again as space-saving fully odexed apps in the second posting in this thread:
- 3GWatchdog
- adbWireless
- Gallery3D
- Maps (latest brut version 4.4.0 added to /system/app again )
- MarketEnabler
- SpareParts
- Y5Battery
The default Mail.apk application was previously replaced by Improved Email. In v0.8 I added the default mail client back as Improved Email has problems with Exchange accounts and push mail updates.
The only app additions to the baremetal system are the odexed SuperUser 2.3.6.1 (update) as well as the final Adobe Flash Player.
Previously in the data/local partition, and thus not surviving a factory reset, the following configurations are now part of the system again (and will be made upgradeable in posting 2)
- AdBlock (hosts)
- DNS settings (resolv.conf, set to Google DNS) and
- APN configuration (apns-conf.xml)
Added goodies, the stock HTC wallpapers are replaced by the fantastic background pictures from NeoPhyTe's ROM, thanks for that! I made them still a bit smaller saving even more precious space.
142 MB free without SD card and buggy A2SD+ implementations .
This ROM is one of the few that is fully odexed, meaning it will have a lot of free space without a SD-EXT partition and should run a bit faster than all the deodexed ones. It does *not* include A2SD+ as this reportedly causes SD card corruptions with Froyo for EXTx and FAT32 partitions when connecting to a PC.
It also does not include a lot of things that nobody really needs but are nowadays included in almost every ROM. To name a few: Wifi 802.11n (uses more battery), OpenVPN, CIFS, EXT4, CFQ scheduler, bash (does a normal user really need these?!).
There is intentionally no configuration tool, the idea is KISS (keep it simple and stupid) which is easy and usable for most normal users.
This is a very clean lean build as a baseline ROM for individual additions; hopefully stable and speedy, your feedback is welcome. If you have SD card corruption issues, please give it a shot and feedback if it solves the FAT32 corruption.
Simple Installation:
For rooted devices only, flash with Amon-RA or ClockworkMod Recovery. Do not create a swap or EXTn partition (whole SD card formatted as FAT32 only). No wipe necessary, this will be done automatically. Backup your data first.
Please follow these detailed steps:
1) Start phone in recovery mode with Amon-RA
2) Partition the SD, no swap, no EXTn, all FAT32
3) Wipe data, cache, Dalvik
4) Switch to USB mode
5) Copy all the packages to the flashcard (or v1.0 only for full install)
6) Flash them all, starting with MacLite_vX.X.zip
7) Reboot and go through the normal setup wizard
8) Voila
Please make sure you update to a Froyo radio too. Some people report high battery drain with the latest 5.23 version with 3G. I therefore recommend using 32.44.00.32U_5.09.05.30_2.
Have fun!
Mac
...and, if this one still screws your SD card, buy a different brand
Download:
I don't intend to create a new release with pointless fixes every other day, although they have 0.x numbers the downloads are stable working releases that should keep you going for a while
v0.8 http://www.multiupload.com/9U8PV07Y3B Modular Version
v1.0 http://www.multiupload.com/BVNXRU9EBI Full Version (MacLite v0.7 + integrated AppsBundle) - v1.0 is not yet updated to v0.8 base which is newer!
To update a previous version (v0.6 or v0.7) please flash v0.8 over your existing setup, but make a backup first!

Add-On Packages
=============
These add-ons restore functionality from the official Froyo Sense release back to MacLite if you need / want them and provide essential 3rd party add-ons and tools. They reside in /system/app and will not take up additional space. Please install these on top of MacLite by flashing the zip package in Recovery mode with Amon-RA or ClockworkMod Recovery.
Official ROM
Productivity:
GMail_signed_odexed.zip (852.38 KB) v2.2.1 - included in v0.7
HTCMail_signed_odexed.zip (2.48 MB) v2.2 - Official HTC Mail + Widget - default in v0.8
ImprovedEmail_signed_odexed.zip (759.31 KB) v2.2 - default Mail in v0.7 - choose only one, HTCMail or this! (has push issues for me with Exchange)
PDFViewer_signed_odexed.zip (1.7 MB) v1.00.1045.218634
QuickOffice_signed_odexed.zip (2.66 MB) v3.2.50-HTC
Social Networking:
SocialNetworkProvider_signed_odexed.zip (56.94 KB) - Install this first!
Facebook_signed_odexed.zip (1.63 MB) v1.3.2
Flickr_signed_odexed.zip (136.01 KB) v1.0
Friendstream_signed_odexed.zip (309.17 KB) v1.0
Plurk_signed_odexed.zip (290.58 KB) v1.00
HTCTwitter_signed_odexed.zip (699.56 KB) v2.0 (Peep)
GoogleTalk_signed_odexed.zip (610.96 KB) v1.3
Note: Due to changes in the authorization to OAuth currently the Twitter application and FriendStream do *NOT* work, you cannot login. This is not an issue with this ROM but a general problem with Twitter, Android and HTC. Please have a look below under Add-Ons for a working non-HTC Twitter version. Update: Seems Twitter reactivated logins for Peep.
Tools:
AppSharing_signed_odexed.zip (186.06 KB) v1.0
VoiceSearch_signed_odexed.zip (968.45 KB) v2.0.1
GoogleSearch_signed_odexed.zip (517.38 KB) v1.1.1.53565 (updated)
SIM ToolKit (50.36 KB) v2.2 - for our Pinoy friends
Misc:
Footprints_signed_odexed.zip (2.2 MB) v1.10
Original Froyo Statusbar (framework-res.apk)(2.62 MB) v2.2
News & Info:
GenieWidget_signed_odexed.zip (586.7 KB) v1.2.02-RC2 (GenieWidget)
NewsReader_signed_odexed.zip (636.13 KB) v1.0
Stocks_signed_odexed.zip (699.88 KB) v2.00
Games:
Teeter_signed_odexed.zip (1.49 MB) v1.00
All-in-One Bundle:
This is a single installation of all the listed packages and will result in an almost "official" (and updated) ROM from an apps point of view, but keeps all the improvements and modifications. Only missing are the pointless "Learn More", the "SIM Toolkit" and the original Froyo statusbar (see above if needed).
AppsBundle_v1.3_signed_odexed.zip (15.25 MB)
I've tested the All-in-one bundle with Amon-RA Recovery. Please let me know if there are eventually any issues with the single update packages.
Bug Fix:
This is only needed for MacLite v0.6 and restores the incidentally deleted calendar functionality.
CalendarFix_MacLite_v0.6.zip (908.64 KB) v2.2
Add-Ons
Connectivity
OpenVPN (module, binary, settings) v0.4.6
Productivity
BarcodeScanner_signed_odexed.zip (343.21 KB) v3.4
Gallery3D_signed_odexed.zip (501.94 KB) v1.1.30682
Social Networking
Twitter_signed_odexed.zip (1.54 MB) v1.0.2 Twitter for Android, works with new OAuth authentication.
Tools
3GWatchdog_signed_odexed.zip (119.53 KB) v0.20.1
DSPManager_signed_odexed.zip (25.18 KB) v1.0
MarketEnabler_signed_odexed.zip (86.7 KB) v3.0.8
SpareParts_signed_odexed.zip (19.49 KB) v1.5
Y5Battery_signed_odexed.zip (38.13 KB) v1.6.0
Development
adbWireless_signed_odexed.zip (90.29 KB) v1.2
powertop+libncurses.so (131.13 KB) v1.11 - Use powertop with terminal emulator or "adb shell" to analyze key power consumers
Experimental
These are some modifications "under the hood". If you don't know what they might be for, ignore them .
InteractivGov_signed.zip (2.84 KB) Set governors to Interactive / Powersave regime (thanks FloHimself)
OndemandGov_signed.zip (2.84 KB) Set governors to Ondemand / Powersave regime (default since v0.7)
Wifi_NoSleep_bg_signed.zip (115.91 KB) Wifi streaming fix for standby mode with 802.11 b/g (thanks Myshkinbob) (default since v0.7)
Wifi_NoSleep_bgn_signed.zip (115.91 KB) Wifi streaming fix for standby mode with 802.11 b/g/n (thanks Myshkinbob)
Wifi_Sleep_orig_signed.zip (115.91 KB) Original Froyo Wifi module (backup in case you want to revert back to original)
Best way to install and avoid eventual problems:
1) copy the ROM and all update (or update bundle) zips to your SD card
2) reboot into recovery
3) flash the main ROM and all updates
4) reboot and go through the setup wizard that should configure all apps automatically
5) done
If you add anything later, please get a file manager (e.g. Astro), browse to /system/app and run HtcSetupWizard.apk manually *after* you installed the update zips. That should also do the necessary configurations as at first boot. Not sure if this is really required, just in case of problems you could give it a shot.
...or even simpler, do a factory reset (wipe data & cache) after installing all add-ons you like.
DO THIS ONLY IN RECOVERY MODE AFTER INSTALLING ALL THE 1st TIME

Curious. Are the widgets for Facebook, Friendstream etc removed as well or just the apps?

Apps and widgets are gone altogether. As clean as it gets.

M'kayyy

your ROM is based on PINKY'S DESIRE 1.3?

kmetek said:
your ROM is based on PINKY'S DESIRE 1.3?
Click to expand...
Click to collapse
It's based on Paul's clean official odexed version, but adds the changes from Pinky 1.3. So you have also the cool config system.

In my opinion You should try to prepare some updates, that will help people in removing useless google/htc stuff from Desire, than making another custom rom.

Mystenes said:
In my opinion You should try to prepare some updates, that will help people in removing useless google/htc stuff from Desire, than making another custom rom.
Click to expand...
Click to collapse
I made this ROM as almost every other existing one is deodexed and/or bloated. There is no lean original version. Updates are therefore not really suitable if one doesn't have a good basis to work up on.
I'll see what is the best way for the next version, I still have some changes in mind like a switchable 802.11n. All which are part of a stable baseline. Anything in addition to that would then be possible as updates and addons.

Updated to v0.2. Please see the first posting for details.

mmaacc said:
[UPDATE: This is likely the fastest smallest odexed 2.2 ROM available without carrying a deodexed SD penalty or corruption risk, v0.2 is out, incorporating changes from Pinky Desire 1.6]
Click to expand...
Click to collapse
I'm sorry, but the SD problems continue with this ROM. The Odexed does not solved the problems.
Try my tests detailed here http://forum.xda-developers.com/showthread.php?t=748793
Regards

simemu said:
I'm sorry, but the SD problems continue with this ROM. The Odexed does not solved the problems.
Try my tests detailed here http://forum.xda-developers.com/showthread.php?t=748793
Regards
Click to expand...
Click to collapse
If you still have an EXTx partition that would explain it, please repartition your card with FAT32 only and remove any old extra partitions.
If the corruption happens on the FAT32 part (I only had problems with EXTx and A2SD+) then this is a different issue. I understand you do not have the "read only" corruption error, your problem is that your phone can not access the SD card when it is mounted under Windows (and not properly dismounted), which is the correct behavior.

Will try this rom, it has all of the things I want. (Odexed, removed useless apps (ecxept facebook) and it's fast) Thanks.

Stock framework-res
Thanks for a great ROM. Works great.
Is it possible to upload stock framework-res with circle battery?
Thanks.

mmaacc said:
If you still have an EXTx partition that would explain it, please repartition your card with FAT32 only and remove any old extra partitions.
If the corruption happens on the FAT32 part (I only had problems with EXTx and A2SD+) then this is a different issue. I understand you do not have the "read only" corruption error, your problem is that your phone can not access the SD card when it is mounted under Windows (and not properly dismounted), which is the correct behavior.
Click to expand...
Click to collapse
The problem occurs with the FAT32 partition and it is descripted in my post and it only occurs when A2SD is activated and exists and EXT2/3 partition.
If A2SD is not active, that problem does not occur.
I also tried the tests with the CyanogenMod before installing the A2SD and it worked fine, but the problem begins when the A2SD is installed.

simemu said:
The problem occurs with the FAT32 partition and it is descripted in my post and it only occurs when A2SD is activated and exists and EXT2/3 partition.
If A2SD is not active, that problem does not occur.
I also tried the tests with the CyanogenMod before installing the A2SD and it worked fine, but the problem begins when the A2SD is installed.
Click to expand...
Click to collapse
Yes, I understand that.
If you look at my other thread you find that there is another problem with A2SD+, resulting in the "read only" corruption on the EXTn partition. That is different from your issue and in my opinion far more serious as it renders the phone partly useless. And to be honest, I did not have that FAT32 problem nor was looking into it. However I can understand how to reproduce it. You changed the phone from disk drive to charge only without unmounting it in Windows. And what probably happened is that A2SD+ somehow stays in the way of doing the switch by itself. Solution: unmount the drive first in Windows as every other card or USB stick (not sure if that really helps ).
I'm going to build another version that has the ext4 support and anything related to A2SD+ completely removed, hopefully that solves the FAT32 problem too besides the already fixed "read only" thing.

Sweet Jesus yes. Something that strips out all the useless, pointless crap like Facebook, Twitter, etc. Let people get that crap off the market if they want it, but give us a clean first boot.
Awesome.

mmaacc said:
Yes, I understand that.
If you look at my other thread you find that there is another problem with A2SD+, resulting in the "read only" corruption on the EXTn partition. That is different from your issue and in my opinion far more serious as it renders the phone partly useless. And to be honest, I did not have that FAT32 problem nor was looking into it. However I can understand how to reproduce it. You changed the phone from disk drive to charge only without unmounting it in Windows. And what probably happened is that A2SD+ somehow stays in the way of doing the switch by itself. Solution: unmount the drive first in Windows as every other card or USB stick (not sure if that really helps ).
I'm going to build another version that has the ext4 support and anything related to A2SD+ completely removed, hopefully that solves the FAT32 problem too besides the already fixed "read only" thing.
Click to expand...
Click to collapse
Unmounting the drive in Windows was my first try, but the problem is the same.
The problem is not in Windows, it is in the phone. It seems the phone does not update the system files after the first PC connection, but it does it in the next power off.
Talking about the "read only" problem, I had that problem only once, but I could solved it checking the drive with Windows and I thought it was by the same problem.
Could you explain me how can I do to reproduce the "read only" problem with a deodexed ROM?
Regards

I've made a brand new test build, this time it's really down to the very basics to figure out the corruption issue.
And it comes with a changed name as there is no Pinky in it .
MacLite v0.3 is based on Paul's official Modaco FroYo, but is re-rooted and updated to latest Superuser 2.3.2.2 +
latest busybox 1.17.1. In addition it has only included bash, /data/apps (for easy removal/update) + custom boot
screen/sound removed capability (none included).
Removed space and battery wasting applications/widgets:
AppSharing
FriendStream
Stocks
Twitter
Facebook
Flickr
Footprints
Maps (replaced, see below)
PDFViewer
Quickoffice
SocialNetworkProvider
Teeter
VoiceSearch
Added applications (in /data/apps):
3GWatchdog
Gallery3D
Maps (latest brut version)
MarketEnabler
Y5Battery
B&W Battery Indicator (Framework)
131MB free. Odexed.
Again, this is a test build that misses a lot of additional functionality and further cleanup. If you have SD card
corruption issues, please give it a shot and feedback if it solves the FAT32 corruption. Changes can then be
implemented in a more complete version.
It uses default settings and governor, so battery life, speed and behavior should be identical to the official
release.
Thanks!
Mac
...if this one still screws your SD card, buy a different brand
Download:
http://www.multiupload.com/I71XY7WQQZ
@simemu
The read only corruption only affects EXTx partitions, and if this happens it basically screws up your whole Android OS. It's not possible to be caused or repaired by Windows itself. Windows is technically incapable to access EXT partitions, nor could it check or repair them.
I assume it is really some problem of incompatibility between A2SD+, which acts as a kind of file system driver, and the external machine. Problems were reported with Windows, Linux and Mac connections. So it must really be a problem within the phone.
To reproduce it you need an EXTx partition with applications installed to it. Then connect it to your PC and try to transfer some data to your SD card. It will give you the "read only" error and the only way to fix is is to take the card out and plug it in a PC/laptop and repartition/format it externally. Pretty messy.
But there is hope. Please give this new test build a try and report back .

How can I remove the apps I don't want? Remove them from the zip file?
Sent from my HTC Desire using XDA App

[ROM] Avaritia HD v0.7 (Udate: 20 jan )

_~~~ Avaritia HD ~~~__
...when a DESIRE grows inordinately strong it becomes AVARICE ...
I tested almost all Desire HD ROMs with data2sd (!).... and i didn't like any of those. The reason is that the data2sd solution is done in a bad "patchwork" way. The reason is this: A Desire HD rom needs about 350mb for the system partition (nand). But the Desire has only 250mb for system available. To make HD Rom work all the devs move system stuff to the SD. This is needed if you provide an app2sd ROM because app2sd still needs some space of the internal data partition. But this is different on a data2sd ROM. In that case you only need 1mb of the internal nand. All other ROMs STILL move system stuff to the sd for their data2sd version although there is much free space on the internal now. Thats why i decided to make my own ROM .... optimized for data2sd only. This way all the 350mb of system is installed to the nand. This way i make good use of all the free memory that you get on data2sd and thats why i wont provide an app2sd version of this ROM. Instead of making data2sd for a ROM i made a ROM for data2sd.
Apart from that i tried to improve data2sd in general and the included script has advantages you don't get on other Desire HD roms. Other HD Roms use a "loop" device for data2sd. I find that a bit risky and thats why i didnt make that default but provide this as an OPTIONAL addon. The life-of-the-edge mod is not more risky than other data2sd Roms .... the difference is that I tell you about the risk and give you to choice if you want to use it....
This ROM is still work in progress and i still won't provide a full feature list (but i think you won't miss a thing because all "usual" features are included). Instead i give you a feature list of features that won't find in any other data2sd HD-ROM.
Features: (that make this ROM unique - at least for some time )
- partition alignment with zips.
- optimized layout for data2sd (system apps on NAND)
- ReiserFS, btrfs, JFS support + recovery
- "deadline" scheduler instead of cfq/bfq which is better for a microSD
I'll add some explanations for the features in future.
Requirements:
-A second Partition in Ext2/3/4 format (same as for app2sd - min 512 but 1024 mb highly recommended max is 2048 mb)
-FULL WIPE (if you come from any other rom or a version before 0.6)
-Default nand partition layout (if you dont know what this means dont care about it .... youll have it then )
Apart from the ext2/3/4 partition this ROM also supports other filesystems (btrfs, Reiserfs, jfs). See 2nd post for "mods" to align, format you partion in the desired filesystem. And for recovery.
Download
Avaritia HD v0.7 alpha (ftp - thanks c0urier)
Avaritia HD v0.6 alpha (ftp - thanks c0urier)
Avaritia HD v0.5 alpha (ftp - thanks c0urier)
WARNING: btrfs is still experimental, jfs is made for IBM servers with battery backed hdds, and the developer of reiserfs killed his wife ... so be careful with those.
Additional info: EXT3 is recommended. Akso see /sdcard/Avaritia/ for the config file.
Pictures
{
"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"
}
Changelog (newest)
v0.7
- reverted rebase - Base is now RUU_Ace_HTC_WWE_1.32.405.6
- Cgroup errors on bfs fixed (through rebase)
Note: HTC using cgroup to speed up interactivity on CFS is not the way forward when
a sheduler MADE for interactivity (BFS) - CFS + cgroups is intended for large servers
and not for a phone.
- Dpad to wake / volume keys works now and included (see mods to "unflash")
- Power Notification widget included as default (see mods to unflash)
- Add custom Wallpaper to the default skin
- Fixed bootanimation (2 frames were too bright + made it a bit slower)
- Bluelight "fun" on boot
- Updated apks
- Some tweaks (mostly adopted from ownhere - thx ownhere)
- Some fixes.
For a complete changelog see the attached full-changelog.txt file
Known Issues and Recommendations
-As for all data to sd solution you may have slowdowns in some situations like market downloads if you have a slow microSD. Any data2sd solution is about space in the first place. But compared to other data2sd ROMs this ROM is faster.
-If you use any other filesystem you need the custom recover from 2nd post.
-FAKE quadrant scores if you use "life-on-the-edge". This does not show the real performance. This skips data base synchronization. It improves the performance (but not as much as bench suggests) at the risk of data safety.
- 720p not working. (see here)
Further Plans
Many....
Thanks
- Coutts99 for the Kernel
- ownhere for tools an help
- Sibere for data2sd/ext
- snq- : vdd, powermenu, camera etc
- woti23 for his unrestless benching
- supercurio and Unhelpful from #project-voodoo
- IEF from #alpharev
- c0urier for hosting
- all devs @ xda
GPL: kernel is an exact git-clone from coutts99 kernel till commit http://git.couttstech.com/?p=coutts...it;h=73857c9910ea276eca798f6cc6a10f424a5eace9 ... no changes to source only different .config .
Also make sure you check coutts thread:http://forum.xda-developers.com/showthread.php?t=849002
All credit for the Kernel to him

[ROM] Avaritia HD v0.1 alpha [ data2ext4 | data2btrfs]
Additional stuff:
Recovery
Clockwork 2.5.0.7 and 2.5.1.8 with support for wipe, install, Nandroid backup and restore for reiserfs, jfs, btrfs ... and ext2,3,4 of course
Custom recoveries
Alignment zip
This will format (WIPE !!!) you sd-ext in the desired format. In addition it will align the sd-ext partition to the "erase block size" of your sd-card ( 1 MiB alignment like gparted - Infos here. Zips do that for you ... ).
ALL alignment zips
Kernel
BFS kernel is here (default)
CFS Kernel is here
Mods:
- dpad to unlock (in ROM as default) + uninstall
- Power notification widget (in ROM as default) + uninstall
- The modified skin (in ROM as default) + original
- a custom splash1.img (see picture)
ALL mods
Splash1:

Looks great, will test it

----- place ------
EDIT: LOL. I was to slow for a placeholder. NVM i dont think i need it anyway... it's not a tutorial or something .....

melethron said:
----- place ------
EDIT: LOL. I was to slow for a placeholder. NVM i dont think i need it anyway... it's not a tutorial or something .....
Click to expand...
Click to collapse
hehe, sorry
what is the benefits of data2btrfs?

b3ndik said:
hehe, sorry
what is the benefits of data2btrfs?
Click to expand...
Click to collapse
Check the thread. In short btrfs is a copy on write filesystem. And overwriting is the slowest operation for a microSD. Btrfs has some options to optimize the ssd devices. Especially slow cards profit from it (for good cards it may be worse). Apart from that it doesn't need journaling to be safe because of COW. This decreases the overhead on writes.
Overall data2sd feels smoother on btrfs than on ext4 (at least for a class 2 microSD). Check the thread for more info and note that BTRFS is a BETA FILESYSTEM.

I just gave you another post directly below your original one All you have to do is edit it and use it.

Nice to see you choose the right ROM
I'm following your progress of your btrfs work a time now, and played around with it, too. I flash it to my device, lets see how it is

Please make the same with the desireZ rom

PaY87 said:
Nice to see you choose the right ROM
I'm following your progress of your btrfs work a time now, and played around with it, too. I flash it to my device, lets see how it is
Click to expand...
Click to collapse
Coutts99 recommended it and after i looked at it found it rather easy to check the structure. Not much symlinks etc. Very clean and AFAIK the ROM that is closest to stock. Still needed to adjust many things (zipalign etc).
rolfd said:
I just gave you another post directly below your original one All you have to do is edit it and use it.
Click to expand...
Click to collapse
Thx for that
animehq said:
Please make the same with the desireZ rom
Click to expand...
Click to collapse
Atm i first focus on btrfs and this rom. I also need to get familiar with cooking first. Maybe in the future, but don't wait for it. Sorry

We will wait for pays next release.
With btrfs
but good work by melethron.
PaY87 said:
Nice to see you choose the right ROM
I'm following your progress of your btrfs work a time now, and played around with it, too. I flash it to my device, lets see how it is
Click to expand...
Click to collapse
Sent from my HTC Desire using XDA App

animehq said:
Please make the same with the desireZ rom
Click to expand...
Click to collapse
If this btrfs works good, then of course i will release such version dont worry hehe
@melethron
Congrats on the rom btw

WHAT software can i make a data2btrfs in my sd card???

gn123099 said:
WHAT software can i make a data2btrfs in my sd card???
Click to expand...
Click to collapse
The best way if you are not already on a linux based system, is to grab a livecd and use gparted. Normally I would recommend Ubuntu, but Ubuntu 10.10 LiveCD got problems with btrfs + gparted. So you could try fedora or opensuse e.g.
Of course you can also use the gparted live cd or usb version.
I never tried them, but should be the same:
http://gparted.sourceforge.net/livecd.php
With gparted format your sd card to FAT32 (first partion) and then 1024MB to btrfs (second partition).
Copy the ROM to your FAT32 partition and flash it through the recovery. I recommend AmonRAs latest recovery!
Don't forget to wipe before you flash! Don't worry if you get error messages when trying wiping the sd-ext, just ignore that.
Regards

I flashed the rom in btrfs mode. Installation without problems.
Its nice to see so much space on the phone.
The only thing is that the device really seems slower now.
Of course this is not your fault, you give us a great solution for more storage, but you can feel the difference.
I will let the phone do some caching and will use it a hole day tomorrow. (Navigation included). Lets see maybe things will settle down a little.
Maybe it could be improved with a optimized kernel.
I got a class 6 sd card by the way.

PaY87 said:
The best way if you are not already on a linux based system, is to grab a livecd and use gparted. Normally I would recommend Ubuntu, but Ubuntu 10.10 LiveCD got problems with btrfs + gparted. So you could try fedora or opensuse e.g.
Click to expand...
Click to collapse
Pays, i normally use either UltimateLinux build for the meerkat or plain lynx. Are any of these distros have issue with btrfs too ?
Thanks
BL

I'll be testing this as soon as I can as I'm skeptical of Btrfs. Only way to check and test the actual Btrfs usability and performance with our device and ROMs is to use it with one. I'll try it with a class 2 SD first, then class 4 and 6 that I own. Thanks.
EDIT: Yeah, your "my data2btrfs" link talks about "advantages" where no. 1/2/4 are all speculation yet. There's no studies or widespread reliable, repeatable, and conclusive testing showing either. Basically, this is experimental.
EDIT2: Sorry can't help further. I bricked my device. Carry on.
------------------------------
- Sent via HTC Desire -

I'm giving this ROM a shot, currently downloading and partitioning it. You used coutt's btrfs_test kernel right?

Dragooon123 said:
I'm giving this ROM a shot, currently downloading and partitioning it. You used coutt's btrfs_test kernel right?
Click to expand...
Click to collapse
Read first post again...

Lol, missed it. Sorry .

[Recovey] TWRP 2.6.0.0

Hi all.
I made the newest TWRP for our P920/925s.
{
"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"
}
Seems everything working except USB Mount.​
Tasssadar said:
CHANGELOG for 2.6.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!
-Can encrypt a backup to prevent theft of private data from your backup files
-Updated graphics / icon courtesy of shift
-Updated exFAT to latest commits
-Fixed a problem with Samsung TouchWiz decryption
-Update SuperSU binary
-Fixed saving of backup partitions list
-Fixed saving of last used zip install folder
-Fixed backup of datadata on devices that use a separate partition for datadata
-Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
-Fixed some problems with partitioning a SD card
-Various other bug fixes and tweaks
Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.
Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.
CHANGELOG for 2.5.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.5.0.0 as your custom theme will likely not be compatible with the new changes!
-Added scrollable partition lists for mount, backup, restore, wipe, and storage selection
-Add new SliderValue GUI element for selecting brightness and screen timeout (thanks to Tassadar)
-Re-work AOSP and TWRP code to improve license compatibility between GPL and Apache
-Added official theme for 1080x1920 portrait devices (HTC One m7, HTC DNA, HTC Butterfly, Oppo Find 5, Sony Xperia Z, etc)
-Fixed a problem with directory permissions on split archive backups (backups usually restored with no app data)
-Fixed a problem with md5 verification of backups
-Added a search function to libtar (thanks to kokotas)
-Improve handling of XML errors (fix permissions)
-Fixed handling of subpartitions
-Improvements to recovery.fstab flags
-Fixed a problem with decryption not being able to locate the decryption key in some situations
CHANGELOG for 2.4.4.0:
-Added another libtar hardlink workaround to fix restore of some backups (usually related to Ubuntu Touch)
-More fixes for the file selector
-Switched from using busybox md5sum to a direct C function call
-Fixed capturing the exit status of tar based backups/restore - TWRP will display that there was an error if there was one again
-Update exFAT to latest commits
-Added a build flag to disable using the ioctl for screen blanking
CHANGELOG for 2.4.3.0:
-Fixed 2 bugs related to restore, one dealing with mknod failures (by bigbiff) and one dealing with restoring hardlinks (by Dees_Troy)
NOTE: If your backups weren't restoring correctly in earlier 2.4.x versions they should restore correctly now. Hopefully you didn't delete those backups. If you're still having problems, run the restore, go to advanced and copy log, then give us the log. Complaints without logs will be rightfully ignored.
-Added a scroll bar to file selectors and listboxes courtesy of Tassadar
-Added libblkid for more accurate detection of file systems and can now detect exFAT properly thanks to bigbiff
-Added a screen dim effect 2 seconds before screen off on some devices
-Finally fixed file selector crash (one of the joys of working with multi-threaded software)
-Fixed loading of screen timeout setting during startup
-Improvements and bugfixes to screen timeout code
-Fixed persistence of the 24 hour / military time setting
CHANGELOG for 2.4.2.0:
-Add screen timeout - screen will turn off automatically after 60 seconds, saves battery and prevents screen burn-in especially on AMOLED devices
-Add a brightness setting (requires device specific setup and only some devices have been added)
-Add a root checker and offer to install SuperSU if the device isn't already rooted
-Add a write buffer to libtar backups, significant improvements to speeds when backing up to exFAT target, minor improvements for other file systems
-Check and offer to fix root permissions if broken
-Add an option for a 24 hour clock display instead of AM/PM (aka military time)
-Move stock recovery reflash check to occur during the reboot cycle
-Add support for some MTK6xxx devices
-Change libtar to vfork to help prevent memory problems
-Add a "clicked" effect to most buttons, file selector, and listbox
-Improve timezone listbox to be more like file selector (per pixel kinetic scrolling, etc)
-Remove some no longer used settings (Forced MD5 sum on zips, size checking on image backups)
-Other minor bugfixes and improvements
CHANGELOG for 2.4.1.0:
-Fixed a problem with mkdosfs that formatted sdcards to 2GB
-Fixed handoff between vfat and exFAT on devices where blkid didn't detect vfat (fixes some issues with mounting sdcards)
-Fixed problems with changing working directory on MD5 creation/checking that may have prevented unmounting
-Backups will now store a copy of the backup log after the backup is completed (only if backup is successful)
CHANGELOG for 2.4.0.0:
-Using libtar instead of busybox's tar for better control over tar file creation and breaking the 2GB barrier that busybox imposes (thanks to bigbiff)
-Support for exFAT formatted sdcards (also thanks to bigbiff)
-Support for decrypting Samsung TouchWiz encrypted devices including internal and external storage (special thanks to a3955269 for figuring it out)
-Improvements to OpenRecoveryScript including displaying a proper GUI while the script is running
-Added wipe cache and dalvik after ADB Sideload
-Replaced many system calls with their native C counterparts
-Fixed bugs in file manager where it would display an empty list after moving or deleting a folder
-Fixed AOSP recovery commands to run after decryption on encrypted devices
-Improvements for building TWRP in CM10.1
-Other minor bugfixes and improvements
NOTE: 2.4.0.0 is, as always, still compatible with your older backups!.
Click to expand...
Click to collapse
Installation:
Download recovery image from here: https://dl.dropboxusercontent.com/u/78302442/LG%20P920%20P925/twrp2.6.img
Copy the image to your SD card.
Type in Terminal Emulator:
HTML:
su
dd if=/sdcard/twrp2.6.img of=/dev/block/mmcblk0p6 bs=4096
Done.​

Thank you very much:good::good::laugh:

COmpatible with su760?

thank u very much

bartdotnet said:
COmpatible with su760?
Click to expand...
Click to collapse
Not sure but I think no.

....update my twrp
Jelly Cream ICS p925 (acurav4)

Thank you so much for your work... Two questions ;
Is this update compatible with wkpark's bootloader? and would my backups from 2.2.3 get unrecognizable?
Sent from my LG-P920 using xda premium

arsen4oo said:
Hi all.
I made the newest TWRP for our P920/925s.
Seems everything working except USB Mount.
Installation:
Download recovery image from here: https://dl.dropboxusercontent.com/u/78302442/LG P920 P925/twrp2.6.img
Copy the image to your SD card.
Type in Terminal Emulator:
HTML:
su
dd if=/sdcard/twrp2.6.img of=/dev/block/mmcblk0p6 bs=4096
Done.​
Click to expand...
Click to collapse
Good job :thumbup:
Jelly Cream ICS p925(acurav4)

boltthrower56 said:
Thank you so much for your work... Two questions ;
Is this update compatible with wkpark's bootloader? and would my backups from 2.2.3 get unrecognizable?
Sent from my LG-P920 using xda premium
Click to expand...
Click to collapse
1. Yes.
2. Probably no.

Good job

Hello I need your support i Installed the TWRP 2.6.0.0 but Now the phone is not turned on I only see the LG Logo Please give me advice Thanks

awesom3: dynamic partition table resizing ~ twrp 2.8.0.0

This started out as a little side project on the OmniROM threads, and it's about time some things are clarified, and what exactly done, is explained.
Currently, only a modified version of TWRP 2.7 recovery is available, and we *might* support other recoveries soon
We have moved ahead of the TWRP 2.7.0.0 originally available in orig-development, to 2.7.1.0, and eventually to 2.8.0.0 too. Enjoy!
What is aw3som3?
Developers have long tried to sqeeze in ROMs into legacy devices with low internal memory, and one of the ways to do this was by using custom tailored mtd_parts, which gave the kernel a partition table to use, with resized partitions. This was widely used on many devices like the HTC G1, MT3G, Hero, Evo4G, Desire, etc.
While that was a viable option for the HTC Pico, a small "problem" that popped up was that different phones have different NAND Devices, with different partition tables and pagesizes. Incase the modified custom mtd_parts even accidentally touched the boot partition, or has been offset'ed out of the available space, a partition would be lost.
As a solution, dynamically obtain 32 mB from userdata partition, and 48 mB from the cache partition, and hax the partition table as soon as the information is got from ATAG. This should make this method work on *almost* all Pico's out there, which have partition layouts as misc:recovery:boot:system:cache:userdata:devlog and partitions in the order misc:rec..cache:devlog:userdata.
Click to expand...
Click to collapse
I've changed the partition table layout, without modifying the actual mtdblock<n>, thus no further fstab/ramdisk editing is required.
table: 0->misc::1->recovery::2->boot::3->system::4->cache::5->userdata::6->devlog
original layout : recovery:boot:system:cache:devlog:userdata:misc
new layout : recovery:boot:misc:devlog:userdata:cache:system
To developers:
In case you want to modify any of the partition size defines, there are three defines, CACHE_SIZE_LEAVE, USERDATA_SIZE_LEAVE, and DEVLOG_SIZE_LEAVE. This, will leave that much mB as defined, and take the rest, put it in system partition. The default defines are: 8, 4 and 1 respectively.
You may clone this repo, and follow the following steps:
download and compile kernel from android-4.4-recovery branch from https://github.com/thewisenerd/android_kernel_htc_pico
put compiled zImage (arch/arm/boot/zImage) in root directory (i.e. cloned directory)
run the following command to repack recovery ./repack.sh
output recovery would be in output/recovery.img
Downloads:
TWRP 2.8.0.0: http://forum.xda-developers.com/showpost.php?p=56168368&postcount=125
[*] TWRP 2.8.0.0: http://forum.xda-developers.com/showpost.php?p=55685051&postcount=108(26 sep 2014)
[*] Modified TWRP 2.8.0.0: http://forum.xda-developers.com/showpost.php?p=55430289&postcount=106(14 sep 2014)
[*] Modified TWRP 2.8.0.0: http://forum.xda-developers.com/showpost.php?p=55375649&postcount=104(11 sep 2014)
[*] Modified TWRP 2.7.1.0: http://forum.xda-developers.com/showpost.php?p=55246774&postcount=97 (05 sep 2014)
[*] Modified TWRP 2.7.0.0: http://forum.xda-developers.com/showpost.php?p=54709263&postcount=69 (09 Aug 2014)
[*] Modified TWRP 2.7.0.0: http://forum.xda-developers.com/showpost.php?p=54688800&postcount=65 (08 Aug 2014)
[*] Modified TWRP 2.7.0.0: http://forum.xda-developers.com/showpost.php?p=54484381&postcount=58 (30 Jul 2014)
[*] Modified TWRP 2.7.0.0 (resized): http://forum.xda-developers.com/showpost.php?p=53704940&postcount=6
[*] Modified TWRP 2.7.0.0: http://d-h.st/I4L
Kernel: You may use CodyKernel or the kernel provided by your ROM's developer that supports aw3som3.
Q: How to use?
A:
Wipe the system, data and cache partition.
fastboot flash the given recovery.img.
wipe the system, data and cache partitions, again. preferably use flash_erase on the partitions.
flash your preferred ROM
flash the given kernel, *with* aw3som3
you're good to go!
Sources
you can get the patches here:
PS#1: 0001-aw3som3-hax-the-partition-table.patch
PS#2: 0002-aw3som3-set-msm_nand_data.parts-later.patch
PS#3: 0003-aw3som3-rearrange-and-relay-the-partition-table.patch
thewisenerd said:
I've moved all the partition re-laying, resizing, etc, to a separate file, in drivers/misc, which should help keep clean the nand_partitions.c file, and we would have to worry only about one file, and related code. It also means that awesom3 is reduced to one patch
Click to expand...
Click to collapse
PS#1 (26Sep'14):
0001-awesom3-hax-the-partition-table.patch
0002-awesom3-allow-a-128-mB-userdata.patch
XDA:DevDB Information
awesom3, Tool/Utility for the HTC Pico (Explorer)
Contributors
thewisenerd
Version Information
Status: Stable
Created 2014-10-21
Last Updated 2014-10-21

Reserved
Questions&Answers
Q: Does this work?
A: Yes, it does
Q: Will it work on my phone?
A: no. it will blast into pieces. jk.
Yes, it should. The main reason that partitions are dynamically resized, is to avoid having to create tailor-made hex values for every type of NAND device that different picos have.
Q: why the name awesom3?
A: A couple of reasons, actually. I was using the awesome D.E. in my distro a few days before I wrote this patch. I liked that UI, mainly because it was cluster-free, and the maximum available space was always used.
Another, was a couple of twn_oc_helper scripts which I had written before this. I had decided to get rid of the scripts, once and for all, due to various reasons (you can read them here), and the working dir for those scripts was named awesom3. The name just stuck by, and voila!
misc
- setting timezone
1. settings-> Time Zone -> set timezone (closest) and offset.

Reserved
changelog
21Oct2014
- 128 mB userdata partition
- Fix wiping crash when block device is not present (credits to Ethan Yonker)
- mtp: fix log spam: findNode not finding a node is not an error (credits to that)
- Update reference to 24-hour clock (credits to Captain Throwback)
- display cpu temperature in twrp use TW_NO_CPU_TEMP := true to disable display use TW_CPU_CUSTOM_PATH := path to set custom path (credits to Jenkins)
- Add support for TrueType fonts (credits to Vojtech Bocek)
- Fix exfat-fuse handling (credits to Dees Troy)
- performance profile support (credits to Tom Hite)
- mtp: cleanup, fixes and performance improvements (credits to that)
- Update RECOVERY_VARIANT blocking to use project-path-for (credits to Matt Mower)
- Attempt to fix md5 issue with backups (credits to Captain Throwback)
- applypatch: add support for BML partitions (credits to Conn O'Griofa)
- atime is access time, let's just use mtime (credits to Jenkins)
- Remove extra slashes from zip path in openrecovery (credits to Matt Mower)
- Fixes for exfat-fuse (credits to Captain Throwback)
- recovery: Fix adb with linux 3.10 (credits to Benoit Goby)
- ADB sideload command not work (credits to Da Zhou)
- Check sehandle before fixing permissions (credits to Dees Troy)
- Attempt to automatically identify data/media devices (credits to Ethan Yonker)
older logs:
26sep'14
Fix handling of MTP fork/child process (upstream)
Include no strict aliasing for MTP (upstream)
Additional checks to prevent partitioning internal storage (upstream)
pico: use twrp.fstab (help unify recovery compilation with device tree)
removed UMS
updated MTP configs (Sachin Thomas)
aw3som3 -> awesom3
Click to expand...
Click to collapse
14sep'14
add mtp config
Click to expand...
Click to collapse
11sep'14
Add MTP support to recovery thanks mostly to bigbiff with a little help from Dees_Troy
Add command line capabilities - you can now execute various TWRP features via adb instead of the touchscreen
Add support for color in the console and give error, warning, and highlight lines different colors
Track backup and restore progress based on file sizes to provide a much more accurate indication of progress
Improve handling of /misc thanks to mdmower
Improve setting of time on Qualcomm devices thanks to [NUT]
Allow using images on slidervalue GUI objects thanks to Tassadar
Allow using variables and addition and subtraction in variables for easier theming
Add support for 1440x2560, 280x280, and 320x320 resolutions and update 240x240
Allow ui.xml file to include additional xml files to help break up the theme and make TWRP easier to maintain
Other minor fixes and improvements
Click to expand...
Click to collapse
05sep'14
updated sources to TWRP 2.7.1.0 (till 01 sep 2014)
removed TW_EXCLUDE_SUPERSU := true
removed TW_NO_EXFAT := true
Click to expand...
Click to collapse
09aug'14
use inverted logo
Click to expand...
Click to collapse
08aug'14
relay partition table
add graphic logo && text to differentiate between normal and awesom3 recovery
Click to expand...
Click to collapse
30jul'14
uses the normal pico_defconfig: !not! slimmered (this fixes *some* of the random reboots caused in recovery)
aw3som3: set msm_nand_data.parts later (0002-aw3som3-set-msm_nand_data.parts-later.patch)
Click to expand...
Click to collapse
27jun'14
resize the recovery
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse

here's mine.
it's working.
{
"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"
}
great work for this one @thewisenerd. :good:
i'm really excited for this aw3som3.
btw. what if we completely get the whole mtdblock5? we'll get a great space for /system.
it's time to use sd-ext completely.

Agaphetos said:
btw. what if we completely get the whole mtdblock5? we'll get a great space for /system.
it's time to use sd-ext completely.
Click to expand...
Click to collapse
That's a question to the users.
p.s. added that to OP

thewisenerd said:
That's a question to the users.
p.s. added that to OP
Click to expand...
Click to collapse
make a POLL for it. :good:

will you please tell me step by step procedure i am noob and don't know how to do all this stuff
I am currently using CM11 weekly 4 TWRP 2.7 recovery

the recovery has been resized, hopefully. get another beta here: http://www.solidfiles.com/d/e6d39a02c4/recovery.img
hopefully, we're just a few commits away from a complete partition table rewrite... I've decided to move devlog to the beginning, then, a 4 mB cache (you shouldn't need more), and the rest for the /system partition. What about /data? sd-ext becomes /data partition by default. I posted a poll on the FB group and most of the people are clearly fed up with internal memory being very low hence, already using sd-ext by default, why "waste" the data partition?
This would stay in beta till some more time.
a new build of twrp should be out any time soon... the kernel, slimmered down to 1.8 mB without affecting actual functionality, *and* adding back support for ext2/3 and exfat and ntfs.
the recovery's size has been slimmered too, by modifying its ramdisk compression. you might not be much interested in all that, but you should see the change in recovery size from this build itself.
and finally, here's the boot.img: http://d-h.st/5jK
proof that it works (otherwise which no one's going to download anyways):
as we are going to use complete /data partition + some moar of cache partition, 112 +

just pushed sources to git some time ago...
you can get the patches here: https://github.com/thewisenerd/android_kernel_htc_pico/commit/eaa7cd3d0d25b44ecbe026ea03dce796868adb35
slimmered recovery defconfig: https://github.com/thewisenerd/android_kernel_htc_pico/commit/1fbb5f37851d6ff4a1d40d91e71d39ac107cd8c4

Tried it on cm 11 works great thanks for the recovery and boot.img

noob question
pico hackr said:
Tried it on cm 11 works great thanks for the recovery and boot.img
Sent from my XT1033 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
how do I made this work bro?
I mean how many partitions should I have particularly their each sizes too
thanks in advance

Agaphetos said:
here's mine.
it's working.
Click to expand...
Click to collapse
instead of
Code:
http://dl-1.va.us.xda-developers.com/2/8/1/6/0/8/7/Screenshot_from_2014-06-24_202911.png?key=Kg2Fp7s86-Ky-H0UFugPJQ&ts=1403661729
use
Code:
http://forum.xda-developers.com/attachment.php?attachmentid=2816087
as your image link... that should fix image not showing.
memontalha said:
will you please tell me step by step procedure i am noob and don't know how to do all this stuff
I am currently using CM11 weekly 4 TWRP 2.7 recovery
Click to expand...
Click to collapse
theBstep said:
how do I made this work bro?
I mean how many partitions should I have particularly their each sizes too
thanks in advance
Click to expand...
Click to collapse
Its for this very reason that I wrote this patch. Users don't have to do anything, except what's written in OP.
This is out of beta now, (read: stable), and can be used.
For others: I'll be shifting to a "no userdata", "4 mB cache", and all for "system" policy soon. Hopefully, you can revert back those commits if you don't need. As a user, 150 mB has never been adequate since I had used 40int2ext, and so, I'll be making sd-ext for /data as default.
This would also involve refactoring the entire table, I've decided to move devlog a few places ahead and order it as boot:devlog:cache:system, which should, technically, make stuff easier (for me) if done in the kernel side.
Don't want that? Revert back those commits, simple as that.
p.s. after thinking about this for sometime, this would also involve editing fstabs, recoveries, etc, etc, so, we'll rather stick to the current partitioning, i.e. mtdblock3/4/5, and keep it as 1 mB userdata, rather than no userdata, so that all the mess of having to edit other stuff would be minimised.
welcome working pa's micro modular gapps (soon), which takes up about 135 mB of /system partition, which should fit, after we bring in some more space from userdata partition.

Perfect Setup Bro
Well it will be good if we use sd-ext as data default
Much System Space :laugh:
Regards : Bilal
Sent from my One M8 using XDA-FORUM, powered by appyet.com

well it's a nice work,but also make a guide on how to revert back to original partition table.

Jituv1996 said:
well it's a nice work,but also make a guide on how to revert back to original partition table.
Click to expand...
Click to collapse
Just flash a recovery and kernel that's not modded?

can i try using this recovery and boot.img with in2ext+??
will it work without any problem?
i dont wanna lose my partition

Hpsgill said:
can i try using this recovery and boot.img with in2ext+??
will it work without any problem?
i dont wanna lose my partition
Click to expand...
Click to collapse
it didnt worked for me I have to install fresh rom for using this mod .
btw thanks @thewisenerd for this aw3som3 mod ill be using it for weeklies

noobified
I tried and so far so good with cm weekly 5 :laugh: I flashed latest cody kernel by the way
the thing is how can I increase internal memory cus only system increased? do I need to add a partition again so that makes 4: fat32, sd-data, sd-cache and sd-ext

theBstep said:
I tried and so far so good with cm weekly 5 :laugh: I flashed latest cody kernel by the way
the thing is how can I increase internal memory cus only system increased? do I need to add a partition again so that makes 4: fat32, sd-data, sd-cache and sd-ext
Click to expand...
Click to collapse
nah, fat32, and sd-data would do
Its really messed up (all the "extra" partitions), considering we don't need to worry about the /cache partition.
The only partitions you need are a fat32 partition, and *one* ext2/3 partitions. Any more partitions, your headaches.
Also, I would suggest that mmcblk0p2 is directly mounted as /data, instead of using any scripts :angel:

hahaha okay as a matter of fact I followed your instructions to partition without card reader http://forum.xda-developers.com/showthread.php?t=2532212 which is really helpful
mmcblk0p2 mean I can modify it for increasing internal?

[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 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