4EXT Recovery Classic v2.2.7 RC5 | STAY @EXT4 | Convert FS | Rom -> Backupname | ..
{
"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"
}
Quick note about themes:
Available themes as of Oct/18:
Themes by [URL="https://forum.xda-developers.com/member.php?u="]GuestK00388[/URL]
Themes by Apaquette420
Themes by Whiskey103
Themes by Amresh
Themes by Apaquette420
Themes by CWhitney24
Themes by DaMyth
Themes by Blindndumb
To uninstall any "flashed theme" and to revert to your own custom settings you had before flashing, just use this Theme Uninstaller in recovery.
It will clear any theme you might have flashed and revert to your own custom settings you had before flashing that theme!
THANKS:
All credits and my deepest respect go to Koush for his extremely great code!
Without him 4EXT Recovery wouldn't have been possible!
Biggest thanks possible go to Sebastiaan15 for his brilliant ideas and who spent whole weeks testing my buggy code with his Desire
Without you I could never have made it!!!
So BIG THANKS to SEBASTIAAN15 and KOUSH for his hard work with CWMR !!!
Many credits to the Desire S community ( especially to loveboatcaptain - LBC Mod Android Development and Marylandcookie ) for testing, very nice ideas, feature suggestions and helping to get the code running on the Desire S!
Special big thanks to RAVENNA from android-hilfe.de board for hours of testing for the Desire!
BIG Thanks to Hussainmushahid who helped me a lot spending much of time with solving a bug I could not reproduce on my device.
And many thanks to all users who reported and helped to identify problems ( can't any longer list all of you here since the list has grown too large )!
Even more thanks to people who 've bought me some beer YOU ROCK!! ZEEKIZ, A USER, PHILOS64, STEVEATHOME, PREACHER65, BEN_PYETT, ULTRA DROID, PTR_HAMILTON, BEANBEAN50, SEBASTIAAN15 and LOVEBOATCAPTAIN
v2.2.6 RC4 Released: Oct/01
Rare Superuser problem when tar backups were enabled (disabled by default) was fixed.
Converting partitions between ext3 and ext4 without data loss now correctly calculates the space needed to successfully complete the operation
New option: check and optionally repair the file system on your sdcard (fat32)
Removed duplicate format cache option inside the format menu (wipe cache does the same)
When formatting fat32 it will now save your 4ext.prop settings and restore them afterwards
Changed partitioning of the sdcard to not use LBA mode for new fat32 partitions as requested by Ghiki
Added new size option (128mb) to the partitioning menu per request
Parted is no longer used to format fat32 in the partition menu-> This solves a bug where sometimes the creation of the fat32 file system failed and produces better quality results
4EXT Recovery themes should now stay when formatting /system or flashing new roms
New option: format /sdcard fat32
New 4EXT Recovery Control API because I'm forced to drop "extendedcommand" (see App for the reason why)enables file names and directories to include spaces for installations
calculates needed space to complete a full or advanced backup at the beginning of the backup.
This ensures that you are not left with a non working backup.
Size for recovery greatly reduced
New 4EXT Recovery Control Features
Please see www.4ext.net for more.
Fix permissions
Calculate real values for the space needed to create a new full or advanced backup
Advanced Backups: While you are selecting / deselecting partitions, it will display and update the currently needed space to complete that custom backup set.
As an example, the following would be possible to do in just one session: Restore a backup, set to create a backup / advanced backup before the restore,
format all partitions with a file system of your choice before the restore process starts,
flash additional zip files afterwards, fix permissions and select to stay inside recovery or to reboot automatically once all actions are complete.
Features: Use 4EXT Recovery Control or Recovery Updater for complete Changelogs and Known issues!
not all features may be relevant for all devices
Displays additional information:
Identifies your current rom and displays its name
Current filesystems on your partitions
Free space remaining of all of your volumes
Current battery charge level
Backup | Restore:
Correctly calculates free space needed to complete a backup ( version > 2.2.6 RC4 )
Tar backups (can be switched on or off)
Complete CWMR5 compatibility
All Backups you create will be named after your currently installed Rom for easier identification.
Never unwillingly get "downgraded" to EXT3 again
Always restores backups using the file systems you HAD on your partitions at the time of creation!-> all partitions formatted with ext4 at that time, will be restored to ext4. The same is true for ext3.
You can manually change any existing Backup to ext4 or ext3-> so that after a restore, all partitions and up with the file system you wanted!
Advanced Backup: backup only a single partition
Convert any of your partitions to EXT4 or EXT3 without data loss.
Formatting:
When you wipe or format it will always use the same file system you currently have.-> but you can change that
When you format ext4 it will always create an aligned file system
Correctly identifies unformatted sd-ext partitions-> if it finds one it displays a warning and suggests you may format them by visiting the 4EXT menu
Filesystem check and repair option in advanced menu
Partitioning:
Alignment check of your partitions
Full support for up to 2 sd-ext partitions + swap (Backup/restore/format/convert, fsck, et.c.)
(RE-) Partition your sdcard for sd-ext without removing your fat32 partition.
All partitions created with 4EXTRecovery will be perfectly aligned to 4k
Installing:
Integrated md5sum checking option
Themes:
Customize all colours used throughout recovery
Use your own icons, background images, progress bars.. more to come.
Assign different backgrounds to different menu categories (version >= 2.1.2)
Create a flashable zip for others to flash your theme.
Menus:
Most popular menu items rearranged
Format menu
Power Menu + option to reboot into bootloader
Less "No's" in confirmation dialogues
Changed Advanced Restore: first select what you want to restore, then select the backup-> Useful for restoring from "Advanced Backups"
4ext.prop:
Configuration file on your sdcard where you can set options to be used by 4EXTRecovery
Change all settings conveniently with 4EXT Recovery Control
Many more options to come
Share your settings / themes by packing your config into a flashable theme
Other stuff:
USB Storage Autostart (must be switched on)
Mount usb storage exposes all partitions on your sdcard to the os (not just fat32)-> you could even partition your sdcard from your PC while connected via USB
Switch haptic feedback on/off
You don't need to reboot recovery if you transferred a file to show up in the install menu.-> This bug affected only some users with either CWMR or previous versions of 4EXT.
Button backlights (Desire S, Desire HD and Incredible S only)
Download:
All downloads are now available through 4EXT Recovery Updater. It's free, no ads, no tracking, no nothing, don't worry
.. and of course via 4EXT Recovery Control
This ensures that your downloads are ok by automatically verifying md5sums and that known issues and changelogs are easily accessible
It also notifies you when there are any new critical bugs found
Recovery images will be uploaded for download soon too, but they can also be acquired easily by using Updater or Control.
You can for example just download a recovery.zip containing the image. The download will be automatically verified for correct md5sums!
4EXT Recovery Control
Free version: Recovery Updater
Fully featured version: 4EXT Recovery Control
For a list of its many features, visit www.4ext.net
Some examples :
Flash as many zip files you want in one go
Automatically calculate and display the md5sums of all zip files you are going to flash
Check your backups' health to ensure they will restore later when you need them, by verifying their md5sums!
Optionally, but highly not recommended:If md5sums don't match but you REALLY NEED that backup BADLY, you might want to restore it anyway.
You can you this app to fix the md5sums of a given backup to "forcefully" restore it!
Calculate real values for the space needed to create a new full or advanced backup
Advanced Backups: While you are selecting / deselecting partitions, it will display and update the currently needed space to complete that custom backup set.
Identifies and adds your romname so you don't need to type so much when chosing a meaningful name for your backup
As an example, the following is possible to do in just one session: Restore a backup, set to create a backup / advanced backup before the restore,
format all partitions with a file system of your choice before the restore process starts,
flash additional zip files afterwards, fix permissions and select to stay inside recovery or to reboot automatically once all actions are complete.
Much, much more! See www.4ext.net
Recovery theming
Uninstall and Install themes with live preview and the option to change their colours without the need to reboot into recovery.
Change all colours with live preview and a nice colour picker.
Working great on my dinc2 this is the one thing i missed since switching from the inspire and now i have it back. Thanks max!
Sent from my Incredible 2 using xda premium
oxlong27 said:
Working great on my dinc2 this is the one thing i missed since switching from the inspire and now i have it back. Thanks max!
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
Thank you very much for that!
And for jumping into the cold water for me
If it booted up fine it's alright and I can remove the warning. Everything else is just like on the IS.
---------- Post added at 01:09 AM ---------- Previous post was at 12:48 AM ----------
Added 2.1.1 Final, but that version is really old.
I'd try the latest first. It has been extensively tested and issues if any should only be minor.
Yep everything i tried is working as it should. Havent tested the formatting yet but im sure its fine everything else works. And as far as trying something thats untested, well thats what xda is about, if you dont get a soft brick here and there your not having any fun. But yes this works fine thanks again
Sent from my Incredible 2 using xda premium
I gave it a go and seems to be working just as it should. Was jealous of this recovery on the Incredible S forums because it let you create EXT4 file structures and now its here. Thanks!
Quick question, what's the advantage with EXT 4? I have heard that it's faster, but then several others say it's a waste of time. I do like this layout a lot more aswell.. The backgrounds are an awesome idea! Great job with this
Sent from my Incredible 2 using XDA App
You should add this to ROM manager.
jonathon2011 said:
Quick question, what's the advantage with EXT 4? I have heard that it's faster, but then several others say it's a waste of time. I do like this layout a lot more aswell.. The backgrounds are an awesome idea! Great job with this
Sent from my Incredible 2 using XDA App
Click to expand...
Click to collapse
Thank you very much
Yes, theoretically it's faster.. depending on usage it can be much faster.
On a phone the difference is less than on a computer though.
Deleting larger files is definitely much faster, also formatting.
Most newer mobiles get shipped with ext4 file system instead of ext3.
It's difficult to answer your question
You should try it out and check if you feel the phone is faster
shoman24v said:
You should add this to ROM manager.
Click to expand...
Click to collapse
I really can't imagine that I had a chance or that it would be possible
Also obviously I would like ppl to use my app.. it was a lot of work.
And yeah, also if it is the free version!
It's a big advantage for me as the developer and I hope for the users too.
That way I can send you news about critical bugs found in a new release (which happened with rc1 for example), I can make sure you get to see at least the Changelog when you install a new version and since it's just a button press, the chance is greatly increased that you also take a look at any known issues.
There are times when I release many updates in a short time. This really comes in handy.
At the moment there is only the preview, but I will release the free version today or tomorrow
Downloaded this morning and gave it a run. I like this recovery a lot.
I ended up making a backup, and then converted my file system to Ext 4 on data and Cache (system already is.)
This is a very nicely done recovery, I like that it is easy to navigate, and has a few more options when doing wipes.
The app is nice to.
Thanks for sharing this!!
PacerguyDon said:
Downloaded this morning and gave it a run. I like this recovery a lot.
I ended up making a backup, and then converted my file system to Ext 4 on data and Cache (system already is.)
This is a very nicely done recovery, I like that it is easy to navigate, and has a few more options when doing wipes.
The app is nice to.
Thanks for sharing this!!
Click to expand...
Click to collapse
Thank you very much
BTW Free version of the app is finally up
madmaxx82 said:
Thank you very much
BTW Free version of the app is finally up
Click to expand...
Click to collapse
I went ahead and bought the market version. Excellent job, Ive been waiting for a recovery like this.
I would have to say I like this recovery a lot. I like having the partion information and battery level in recovery. Also the option to convert partions is a plus. Already tried it on a couple different roms and currently running them all as ext4.
Great job and keep up the good work
Sent from my Incredible 2 using XDA App
After converting everything to ext4 cant get wifi tether to work anyone else have this issue? Boots 100 times faster though on cm7
edit fixed by updating to the latest nightly
Great recovery, got the market version. Super smooth on a few roms here.
Anyone with a sense rom should go without saying but make sure the kernel supports ext4. Drellisdees kernel does well
This Recovery looks great, I'll try it soon. A couple questions...
1. It replaces Clockworkmod 5.0.2.0?
2. Has anyone actually done any benchmarks to see if Ext4 is faster than whatever is on the stock phone?
I use Ext4 on my Ubunutu Linux box and I understand it improves performance and adds journaling, but is it actually faster on a phone. It would be cool to see boot times, application install and launch times, task switching, etc. So often people say even minor updates to ROMs are "much faster" and it's nonsense.
Thank you all very much
regarding ext4: yes it will be faster, but how much depends on usage and it's really difficult to say on a phone. But certainly it won't be slower.
Also since newer phones seem to ship with ext4 it might indicate something
Yes, when you flash any other recovery it replaces the previously installed one.
ph1nn said:
This Recovery looks great, I'll try it soon. A couple questions...
1. It replaces Clockworkmod 5.0.2.0?
2. Has anyone actually done any benchmarks to see if Ext4 is faster than whatever is on the stock phone?
I use Ext4 on my Ubunutu Linux box and I understand it improves performance and adds journaling, but is it actually faster on a phone. It would be cool to see boot times, application install and launch times, task switching, etc. So often people say even minor updates to ROMs are "much faster" and it's nonsense.
Click to expand...
Click to collapse
Well as far as benchmarks I haven't dug in too deeply. Unfortunately with quadrant file systems tend to fool it anyway but I haven't gotten linpack or similar
The biggest advantage I see are the same things that we both likely saw when linux changed to ext4 (ubuntu fan here too ) that being, things involving large amounts of data being moved at once have the biggest improvement. Obviously there are more instances of that on a computer than a phone . Boot times, it knocked a few seconds off my boot time on cm7 which is not slow to boot by any means already. I think it would be even more drastic with something as big as a sense 3.0 rom..everything else I don't know that its particularly faster after everything settles down but is most definitely not slower and is just as snappy as before. It does seem to be a bit quicker in terms of settling down more quickly after a reboot (not laggy for as long) and everything getting precached etc.
Just want to tell everyone, that there is a new known issue with tar backups!
It can happen if you have enabled tar backups that superuser stops working after you restored a tar backup.
To anyone not familiar with this: it is disabled by default! So don't worry if you didn't enable that setting!
I have updated known issues and also sent a notice about that.
To work around this, you can flash your rom again (no wipe needed) and it will be ok.
Nonetheless please deactivate tar backups for now.
It doesn't happen for everyone and always.
Difficult to track it down and I couldn't reproduce it on my device yet.
It is or was also known to happen with CWMR5 which introduced tar backups.
Maybe it's solved in the newest version I don't know however I have seen a lot of posts regarding that.
I'm working on this.
If someone runs into this problem, please send me a pm or a report telling me which version of superuser and which rom he was running.
Thank you very much and sorry about that.
Anyone entering the app gets a one time notice about it.
I've been using the tar backups since installing 4EXT last week. No problems on my end, but since I really don't need the tar backups anymore, I'll go ahead and disable that option and go with the default format.
Thanks for letting us know Madmaxx. And thanks again for the great recovery!!
Thank you
New versions of recovery and 4EXT Recovery Control.
Big changes
Related
STEAM KERNEL v2.9.9.0 (it's not 3.0.0.0 because that would mean stable)
Steam Kernel is the successor of ULTK, so you can expect it to be mostly the same, except for a few things.
But first the Credits: anzo,ChainFire,DocRambone,hardcore,koush,nikademus,neldar,newmail,patience,PFC,RyanZA,tariattila,XDA,ykk_fice,ZAGE,z4ziggy
What is this about?
This project is the successof of ULTK, with many new features. The main points are (the new features are in bold):
- Convert filesystems to ext2, ext4 or jfs (data, dbdata, cache and system)
- Use fake /efs to get a completely-rfs free ROM (only works if /system is set to be mounted as rw)
- Startup tweaks
- Even more boot-time settings (adb security settings, mounting options, bootanimation chooser)
- BackLightNotification 2.2
- Includes Steam Recovery (with many new features too, like touch based input, file manager, improved SGS compatibility, read more here)
- Includes possibility of filesystem encryption (read more here)
- Includes boot-time log viewer applications (with the option of watching the logs go instead of a bootanimation)
- Superuser install function
- Afterburner support (read more here and here)
- Many more I might have forgotten...
How does this work?
Simply flash the kernel to any non JPU/JPX based ROM. It might work with them too, but expect problems (mainly with the sd card and wifi). Steam kernel no longer includes 2e recovery, so you cannot flash it during initial flash (unless using Steam ROM).
How can I use the extra features?
All features can be enabled inside Steam Recovery. On a how-to on Steam Recovery check it's thread. Lagfixes and boot settings can be found inside the "Steam options" menu item.
What are the lagfix schemes?
They are ways on how to format and bind the various filesystems. You can chose how you want to format the partitions (data,dbdata,cache and system), whether you want to use an extra loop device or not, whether you want to encrypt the partition or not, and two other options, like fake /efs mode (which is a bit buggy in certain cases), and /system rfs reconvert mode
About inconsistent /system partitions
If you are using an ULTK kernel, which mounts system as "check", Steam Kernel tries to identify your partition and let you reformat it. If you know that you have a bad /system partition, but the autodetect couldn't figure it out, there is an option in the filesystem (lagfix) menu, that will tell Steam to convert your /system partition from one settings to another.
Which Lagfix scheme / config should I use?
You decide. Ext4 base is usually enough, but you can convert /system too. If you dare use the overkill options. Now that there is also the filesystem encryption support, you can actually use a mega-overkill scheme (encrpytion+loop device+ext)
What happens after I chose a lagfix scheme?
If the chosen one is different from the active one the kernel will reformat your device the next start. Before reformatting it will create a nandroid backup, reformats the device then restores the data from your backup. You can chose between some other options too before the reformat.
Is this ROM safe
As usual: no. There are a lot of places where the conversion can break (like not enough free space on the device while restoring /system), and steam is not yet good at handling these errors. The 3.0.0.0 milestone is however there so be prepared
What are the new features?
Steam Kernel uses Steam Recovery for configuration (plan on creating a native Android app for that is on the way), which has an extensive on-line help system, and touch screen interface. Try checking the new options, or ask!
How to switch to another kernel/ROM
There is an uninstall feature (in the about box) which will disable all lagfixes, removes steam config from the system and makes sztupy very sad. You can always flash another complete ROM package over this using Odin, you'll lose all your data however.
I've found a bug
And you'll find more of them. Please report them, so I can try and fix them.
Does this kernel cause corruption?
Yes, it corrupts your mind!
Okay this is great bout you still didn't put in feature X
I know, there are still a few features I'd like to add (like the journal free ext4), but I didn't
want to hold the current release any longer
You bet, we're already on CM/Gingerbread/2.2.1 and this only works for 2.2
Yep. But work is on the way to make it injectable to stock kernels without too much fuzz!
DL link: http://android.sztupy.hu/dl/Steam_Kernel_2.9.9.0.tar
(flash with Odin as PDA)
Source: https://github.com/SteamMOD
Sound good. Will try.
Good work sztupy.
WOW, I successor to ULTK. I bet this will be as path-breaking as ULTK.
ragin said:
WOW, I successor to ULTK. I bet this will be as path-breaking as ULTK.
Click to expand...
Click to collapse
I thought sztupy has moved on, but no, he was preparing for this big release!
Congratulations and thank You sztupy
Omfg youre pure awesomeness!!!
OMFG DUDE, you have done it again, cant wait to try this out, im on 2.2.1 right now but will try it as soon as its compatible, keep up the good work.. Im so happy with guys like you...
WOW what a Christmas present!!! Thanks alot!!! Will start testing now....
Looking good! Will try this as soon as it works with 2.2.1.
good to see u r still working for i9000
btw, looks like u have mis-spell my name
exelent m8,exelent job done
good start for 2.3 firmware
awesome the master is back , looking forward to a JPY compatible build
Ahh bravo! Well done I'm pretty sure no one expected this keep up the good work!
Sent from my GT-I9000 using XDA App
1617 in meaningless Quadrant. 1400's in latest hardcore kernels (with same config?). You did something right
tonyjansen said:
1617 in meaningless Quadrant. 1400's in latest hardcore kernels (with same config?). You did something right
Click to expand...
Click to collapse
what is the result of the mount command?
@sztupy thanks for your attempt to fix the RFS corruption on /system.
Master sztupy returns...
WOW!!!!!!!!!!!!!!!!!!!
Keep 'em coming!!!
Sent from my Samsung Galaxy S using tapatalk
created cwm flashable kernel ( thx hardcore and trasig )
Steam_Kernel_2.9.9.0_CWM.zip
pls clear dalvik after flashing.
tested it and it work just fine.
thx again sztupy
wow good work, hopefully we can have 2.2.1 compatibility soon with the release of the 2.2.1 sourcecode
WOW great work, the Recovery Mode is Awesome
I am trying it right now with original JPX and JFS Base.
One question!!! it tells me if I really want to formate /system because this can be undone. BUT if I flash it back with Odin to Original one with re-partition on it should be everything like original, should it ?
TweetyPeety said:
WOW great work, the Recovery Mode is Awesome
I am trying it right now with original JPX and JFS Base.
One question!!! it tells me if I really want to formate /system because this can be undone. BUT if I flash it back with Odin to Original one with re-partition on it should be everything like original, should it ?
Click to expand...
Click to collapse
if you reflash a full rom ( like jpu, low level package ) with repartition enable it will reformat your device in rfs.
Ok tried it and it doesn't work for me. It runs ok, but not really smooth. Live Wallpaper is really slow and I don't get connection to my mobile phone provider and WLAN doesn't work.
maybe not JPX ready, so I will try szutyps Steam Rom I have time today to try some stuff
{
"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"
}
3.2.1
This build is the exact copy of my RAFDROID HD EXT
the difference is that some parts of the system are "squashed" to give you the possibility to NOT USE any Ext partition for data.
I dont like squashedfs, but someone requested an hd build with some free space on nand (about 50mb) because some one not install a lot of apps and prefer to not use sd ext partition.
This build is mainly for EU HD2 (512mb) users.
If you are an HD 1024mb user really you dont need this, and you can use my main HD build
FEATURES
All the main features of RAFDROID HD EXT plus:
- odexed back to save dalvik cache space
- free user space after first boot: 101mb
- App2SD enabled if you use and SD with an EXT partition
CHANGELOG
Code:
3.2.1 - 3 MAR 11
Fixed Market FC
3.2- 3 MAR11
Some improvements and fixes to radio/audio driver,
this "should" fix phone freeze in some setups, also if I was not able to replicate the issues
Tweaked for more battery life on some sd cards usage
Updated hosts file with last one
3.1 - Initial release
=== INSTALL INSTRUCTIONS (CWR) - NEW USERS WITHOUT CWR INSTALLED OR WITH CWR BUT USING ANOTHER ROM ===
This process will erase everything on your nand. So, if you are already using a previous rom, backup everything!
Download PANASONIC SD FORMATTER and use it to format your card with FULL ERASE
You need to flash MAGDLR 1.13
You need to flash, via USB FLASHER magdlr option, this recovery partition layout, otherwise the build will not boot.
Download the FULL RAFDROID PACKAGE and copy the entire zip (not extracted!) on the SD CARD root.
Put the SD CARD in your phone and power it on and go in the MAGDLR menu (hold the power key while powering up)
Select BOOT AD RECOVERY
Click on INSTALL ZIP FROM SD CARD and then CHOOSE ZIP FROM SD CARD
Select the FULL_RAFDROID_HD*******.zip that you downloaded before.
Select "Yes - Install........" and wait for installation then Go back with power button and select REBOOT SYSTEM NOW
First boot can take up to 20 minutes. If you are stuck on white screen with HTC logo just wait. If you hear boot sound more than one time, you had a bootlop and something has gone wrong. Delete everything, reformat your SD card, read again the instructions and try again.
When you see the lockscreen, give at least 5 minutes to settle. Then do all your settings and then reboot again
Enjoy.
Remember: if you want to avoid Data Corruption always choose SHUT OFF and not reboot!
=== INSTALL INSTRUCTIONS (CWR) - UPGRADING FROM A PREVIOUS RAFDROID VERSION (2.2 or greater) WITH ALREADY CWR INSTALLED===
Since the data storage method is different, you cannot upgrade from a different RAFDROID HD version. You have to install fresh. Anyway you will keep your data and apps installed.
============ CONFIG.TXT ============Used some ideas and code bits from Dandiest's init script.
You can create a config.txt file on the root of your sdcard to configure some things at boot.
Actually you can configure the following options
gps_zone=[your country]
check http://www.pool.ntp.org/zone/@ for country codes (example: it for italy, us for usa.. and so on...)
ppp_mode=[1 or 0]
1 to enable PPP
0 to enable RMNET.
Default is 0
If wince=1 default ppp_mode will be 1
old_light_driver=[1 or 0]
0 to use the new light driver (working notification leds, button backlight control)
1 to use the old light driver (no notifications leds, buttons will go off after 10 seconds)
default is 0
auto_btn_backlight=[1 or 0]
1 to have the buttons backlight going off/on with the screen
0 to have the buttons backlight going off after 10 seconds from when the last button is pressed
default is 1
this work only if old_light_driver=0
wifi_mac_change=[1 or 0]
1 tells the system that you will need to change the wifi mac address to a custom one
0 tells the system that you will use the wifi mac address based on device hardware
custom_wifi_mac=yy:yy:yy:yy:yy:yy
here you have to write the wifi mac address you want.
This is needed, and will work, only if you specify wifi_mac_change=1
If you not write any mac address here, the default 00:11:22:33:44:55 will be used
Just an example on how a file could look:
Code:
gps_zone=it
ppp_mode=0
old_light_driver=0
auto_btn_backlight=1
The init script will also create an init.log file on your sd card at every boot. This will help you and me with debugging if something not works fine. If you have issues please always post your init.log file when reporting your problem.
============ KERNEL ============
You can refer to my kernel thread for updates, changelog, and comments
http://forum.xda-developers.com/showthread.php?t=940823
============ SQUASHED FILE SYSTEM ============
App, Framework and most of Lib folders, are squashed.
Anyway you can push or delete any file from those folder because any file is simlinked.
Example: if you want to use a different framework-res.apk, you can copy it in the /system/framework folder. At this point the simlink will be removed and your new file will be stored on nand, not in the squashed filesystem. This means that more "new files" you push in the squashed folders, less nand space you will have.
Anyway please note that I left only about 13mb free on "system". This means you will not able to push more then 13mb files. If you like to change a lot of things.. this build and squashfs is not for you.
============ DOWNLOADS ============
You need to flash, via USB FLASHER magdlr option, this recovery partition layout, otherwise the build will not boot.
Full Rafdroid HD 3.2 LIGHT SQ
http://hotfile.com/dl/108421743/5bfea5b/full_rafdroid_hd_3r2f1_light_sq.zip.html
MD5: 97018DD4D05FAAFBCC5F9329AEB03F28
SHA1: F6B6D67B90B96E02FCDA70D98836450B6FAE9917
CRC32: 150CCA2B
OLDER VERSIONS:
3.1 : http://www.multiupload.com/X8VBC6WKYV
============ DONATE ============
I made this version just for people that were asking, so if you think this helps you, a small donation for a coffe or a beer, is appreciated. Otherwise a click on the "thanks" button is appreciated too
============ CREDITS AND THANKS ============
Credit to all the people that made all this possible: Cotulla, DFT, darkstone, markinus, danijel, rajko and some one other I'm missing...
Big Thanks to Cass, ocm, darkstone, rajko, crawlingcity, atoore for their help in the last months and to be always available to help
Thanks to all the users who donated and helped me to keep going
Thanks to all the testers and users of my builds that with their reports helped me to solve bugs and issues.
Thanks also to Sergio76, imilka, cmylxgo for the nice talks and knowledge sharing
FAQ
Q: I have low quadrant score
A: This is normal. Nand is slower. Anyway during day usage you shold not notice big difference
Q: I have small freeze when installing apps
A: This happens with all Desire HD builds. I can't do nothing to avoid this
Q: I'm using App2SD but my internal memory keep decreasing at any app installed
A: Go in the application management and move the installed abb back in the phone. Some apps anyway keep some datas in internal mem.
Q: My phone sometimes freeze and I have to reboot.
A: Go in Settings -> Audio -> disable audible touch tones. this will solve the issue in most of the cases.
Q: Can you provide a different link or a mirror different from hotfile?
A: I'm sorry but the answer is "no". I pay hotfile every month and the downloads give me the possibility to pay it. I dont do this for money, but I also dont want to waste my money
Q: During/after boot a window appears with "System process not respoding". What I have to do?
A: This is caused from the new audio driver I used. The new audio driver has better phone stability and no robo voice. You have two choices: 1) Click on "wait" and all will be fine OR 2) download the "old_acdb_file.zip" and flash it via recovery. In this way you will not have the error anymore but you will start having robo voice on first call (you can avoid this disabling audible touch tones) and could happen that your phone freezes when receiving a call. It's your choiche. I preferred the "window error" one because for me is more important to have a working phone than an error window appearing at boot.
Q: I have robo voice when I make a call
A: To avoid this, disable "audible touch tones" from the "settings -> audio" menu. You will have no-more robo voice also if you reboot.
a) During the robo-voice call, enable the speaker, then disable it. You will have no more robo-voice until next reboot.
Q: I have very low audio during calls
A: During the call, enable the speaker, then disable it. You will have loud volume until next reboot.
Q: after boot I see only a white screen with a green htc logo
A: just wait. It can take fro 5 up to 20 minutes depending on your sd card. There are no issue. The build booted fine, it's just copying all the files to SD. This will happen only on first installation.
Q: I'm having high battery drain
A: Try reboot. Try disabling gps in location. As you can see from the screenshot I have 4mA with WIFI active! Also be careful. If during google account setup you choose to backup/restore all your data, the sync process will be dramatic heavy because it has to reinstall all your apps. It could need a couple of hours to settle. Also high battery drain could be caused by SD. try another one.
Q: It's really laggy!!!!
A: as all Desire HD builds this is BIG! This needs at least 10-15 minutes after boot to be usable. Then try to use it for 5-6 hours.. and do a couple of reboots.. you will see that the speed will improve. After 24 hours of use and 4-5 rebots this will be really fast.
Q: I have no GPS or the fix is really slow
A: Firs fixt can take up to 5 minutes. just wait.You can edit the config.txt gps_zone= to your country. See here for the right strings http://www.pool.ntp.org/zone/@ if this not solves, try use QuickGps from the market to download a-gps data.
Q: It not boots
A: partition again and format again your sd card. follow the guide linked in the first post. post your init.log. check that you flashed the custom recovery linked in the instructions.
Q: I have no data/3G/HSDPA
A: probably you have to set your apn manually. google it for tips on how to do and what settings are need for your carrier
Q: How do I remove BOOTSOUND / How do I change bootanim
A: bootsound and bootanim are located in /system/customize/resource
Just delete android_audio.mp3 if you dont want sound
Q: I have wake up lag
A: It's an issue that devs are trying to solve. It's not related to the build itself. In the Q&A Forum there is a thread about this problem.
Q: My screen stays off after call
a) Maybe this can help: http://forum.xda-developers.com/showthread.php?t=946012 ATM very few people have this issue, so I wonder is related to sd card.
Q: My contacts pictures are low res after sync!
A: this is a google problem, read here http://code.google.com/p/android/issues/detail?id=4147
Q: I have random reboots
A: Seems to be related to your phone, read here http://forum.xda-developers.com/showthread.php?t=941845 and here http://forum.xda-developers.com/showthread.php?t=898804
UPDATES:
Instructions:
1. Download your update and copy it to your sd card folder. Dont use MAGDLR mass storage mode because will corrupt your files. Use an sd card reader on your pc or usb mass storage mode in recovery menu
2. Boot into MAGDLR and choose BOOT AD RECOVERY
3. Make a backup! It will save your life if something goes wrong and you want to roll back! You are aware now!
4. Click on INSTALL ZIP FROM SD CARD
5. Click on CHOOSE ZIP FROM SD CARD
6. Select the update zip that you downloaded before
7. Select "Yes - Install........" and wait for installation
8. Go back with power button and select REBOOT SYSTEM NOW
Removed Apps for version 3.X -> http://www.multiupload.com/H5IPNFYBG4
old acdb file (read the faq if you dont know what this is) -> http://www.multiupload.com/AHV0UIKHZF
Stock Framework, only for version 3.X -> http://www.multiupload.com/TVDWWVDNL1
RAFDROID Framework, only for version 3.X -> http://www.multiupload.com/ZC4P6KSKWL
Replacing fonts with standard Desire HD one http://www.multiupload.com/N4VR74W8PK
Replacing fonts with Rafdroid one http://www.multiupload.com/E9UKQBEE4P
If you have issues with flash videos on website, you need an older flash version. Check this post. Thanks to Jayedamina http://forum.xda-developers.com/showpost.php?p=10584806&postcount=280
- maybe I need also this -
First! Nice!
waiting...
are there any advantages on HD2 TMOUS?
rafpigna said:
This build is mainly for EU HD2 (512mb) users.
If you are an HD 1024mb user really you dont need this, and you can use my main HD build
Click to expand...
Click to collapse
I gues not rizky_p
rizky_p said:
are there any advantages on HD2 TMOUS?
Click to expand...
Click to collapse
link is on-line
Thanks, will try
Going to try this tonight, looks good. Any one tried it yet?
Ston said:
Going to try this tonight, looks good. Any one tried it yet?
Click to expand...
Click to collapse
Yep, works a treat
Hello Raf thank you very much for giving us this opportunity, just wondering which files should we use to revert back to stock framework and standard fonts and how to install them.
Thanks again for all your efforts
I always had problem with data on ext partition due to easy file corruption, so I'm trying this...thanks!
thesniffer said:
Hello Raf thank you very much for giving us this opportunity, just wondering which files should we use to revert back to stock framework and standard fonts and how to install them.
Thanks again for all your efforts
Click to expand...
Click to collapse
You can use the update zips from my EXT build.
Very nice and smooth build
But one question: Has anyone tried to change the kernel to Rfp 1.6 or 1.5? I just tried and now the phone is stuck at "gogogo" ...
Intersting
rafpigna said:
You can use the update zips from my EXT build.
Click to expand...
Click to collapse
So via CWM Recovery as i supposed.
Thanks again for your kindness and keep up your valuable work
hi raf
i installed this one(only for proof of concept),works great and i think it is a little faster than the "normal" rafroid,i dont have any lag!!! but 101mb.....very poor...
back to rafroid HD "normal" with d2sd..... i love more space!!!
nice & good release
keep up the good work
cheers!
Notice: I'm shelving this, at least for now. The errors are too inconsistent and sporadic, and testing has proven to bee rather arduous. I won't delete the repos, but I'm not currently planning to support or look at this much for at least the near future. It's worked for some people, but USE AT YOUR OWN RISK only. I am not providing binaries for this, if you want to use it then you'll need to build it yourself and if you go to that much trouble I would hope you know what you're doing.
If an error occurs, I recommend rebooting into any version of FIREFIREFIRE that has the 'fastboot oem format' command and using that to fix your partition table. If you have no idea what that last sentence just said, I strongly suggest you do not use this tool.
-----
I briefly mentioned in a previous post that I was working on an app that would enable you to resize your data, cache, and sdcard partitions so that you can have some more app installation space. Now that I've gotten everything to a stable point, I'd like to go ahead and release my work to the general public for anyone who wants to give it a try. So, I'd like to present what I've named FireParted.
What is it?
FireParted is a basic partition manager for your Kindle Fire, released under the GNU General Public License v3.0. It provides you with a (hopefully) intuitive GUI for resizing your data, cache, and sdcard partitions. It does not support or affect any other partitions on your device.
{
"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"
}
How does it work?
To use FireParted you will first need the following:
ADB needs to be configured on your computer to connect to your Kindle Fire. This will not install or configure the ADB drivers for you, but KFU will.
You need to have a custom recovery installed (tested against TWRP, but ClockworkMod should also work)
You need to have Windows with the .NET 3.5 Framework installed (Win7 ships with this, XP and Vista users can use the link to the left if needed). I plan to support Mono, but it has not been tested yet (it does build in MonoDevelop, though, so that's a good sign).
(Optional, but recommended) FIREFIREFIRE v1.1 or later. This will give you access to the 'fastboot oem format' command should something horrible happen (power loss, your computer crashes mid-partition, etc).
Your device must be in recovery mode while running FireParted in order to repartition it. Note that you can make an archive of your /data partition from a normal OS boot.
(Optional) If you want to examine a data archive backup on your computer, I highly recommend 7-zip. It's lightweight, free, open source, and supports TAR and GZIP archives, which is what I'm using to create the backup.
Once you are sure that you have met the prerequisites, you can simply launch the FireParted executable to start the application. Again, before you can do any partitioning work, you will need to reboot your device into recovery. Next you should read the partition table of your device to get a baseline, and then backup your data partition (unless you want it to be formatted). The numeric controls on the left allow you to choose the partition sizes you want, and "Apply Changes" will perform the repartition for you. Then you can restore your data backup and reboot to test your new layout!
Can I get a quick feature rundown?
Sure. FireParted currently supports the following:
Repartitioning of the data, cache, and sdcard partitions, to allow for larger app installation space (for example).
Archiving and unarchiving of the data partition (to preserve data during a repartition). Can be used simply as a backup mechanism if desired (requires root).
Basic sanity checking - FireParted keeps track of how much space you have to split amongst the data/cache/sdcard partitions, and won't let you create a partition that doesn't fit. It also won't let you shrink a partition to be smaller than its current contents. Also limits the cache partition to a minimum of 64MB.
Where can I get it?
The source code is available on my GitHub.
CHANGELOG
Version 1.1 - 01/04/2012:
Fixed some math/parsing so that FireParted will be more intelligent when determining start/end points for partitions.
Version 1.0.1 - 01/04/2012:
Fixed a minor bug that would cause the GUI buttons to get stuck in a disabled state if an error occurred while reading the partition table.
Version 1.0 - 01/04/2012:
Initial release. Includes all of the planned basic features:
Repartitioning of the data, cache, and sdcard partitions, to allow for larger app installation space (for example).
Archiving and unarchiving of the data partition (to preserve data during a repartition). Can be used simply as a backup mechanism if desired (requires root).
Basic sanity checking - FireParted keeps track of how much space you have to split amongst the data/cache/sdcard partitions, and won't let you create a partition that doesn't fit. It also won't let you shrink a partition to be smaller than its current contents.
Planned features/Needs work
Figure out what the hell is causing the "cannot meet constraints" error on other Fires (but not mine )
Test and support Mono builds/execution on Windows
Test and support Mono builds/execution on Linux (possibly Mac as well)
Very nice will be using this in the near future.
This should be stickied. I could see this being a staple utility.
Awesome... no elaboration needed
Amazing! I assume I can also use this to claim more general storage space? Is their a minimum size I should avoid hitting?
Time to fire up a VM and give this a shot. Much appreciated!
very cool!
No words, you are our hero. I added in 3 minutes currently 1GB sd card space...
cl2eep said:
Amazing! I assume I can also use this to claim more general storage space? Is their a minimum size I should avoid hitting?
Click to expand...
Click to collapse
Sure, you can tweak the values in either direction. Really, however much you think you can manage with should work fine, I would think. When you read out your partition table the meters will let you know how much space you're currently using on each partition, so if you have a lot of free space on /data and don't intend to install a lot of large apps there's no reason you can't shrink it.
I do currently enforce (in code) a 64 MB minimum on the /cache partition. I chose 64 MB because the limit on apks in the Market is 50 MB (source), so 64 MB should in hopefully give you enough space to install anything from the Market.
Of course, another consideration might be OTA updates. A 64 MB cache partition would be too small for the 6.2.1 OTA update package to download, for example. It's possible this could be a sort of poor man's protection from unwanted OTA updates, but I can't make any guarantees
Not sure what happened, I followed the instruction and it got the the part where it tries to partition the sdcard and came up with an error about not meeting constraints ( i made sure I had plenty of free space). The program and phone froze up, I can only boot into recovery. When I run the program and check I no longer have partition 10 or 11.
I'm having bad luck with this device.
airmaxx23 said:
Not sure what happened, I followed the instruction and it got the the part where it tries to partition the sdcard and came up with an error about not meeting constraints ( i made sure I had plenty of free space). The program and phone froze up, I can only boot into recovery. When I run the program and check I no longer have partition 10 or 11.
I'm having bad luck with this device.
Click to expand...
Click to collapse
I had the same issue and tried to do it by hand. When I get into print the parted it says all of the partitions are there, but I can't get out of recovery
airmaxx23 said:
Not sure what happened, I followed the instruction and it got the the part where it tries to partition the sdcard and came up with an error about not meeting constraints ( i made sure I had plenty of free space). The program and phone froze up, I can only boot into recovery. When I run the program and check I no longer have partition 10 or 11.
I'm having bad luck with this device.
Click to expand...
Click to collapse
Can you post your current partition table?
dnathan13 said:
I had the same issue and tried to do it by hand. When I get into print the parted it says all of the partitions are there, but I can't get out of recovery
Click to expand...
Click to collapse
Are you stuck in the recovery bootmode, or does it simply fail to boot? Can you post your current partition table, too?
dnathan13 said:
I had the same issue and tried to do it by hand. When I get into print the parted it says all of the partitions are there, but I can't get out of recovery
Click to expand...
Click to collapse
I was able to create and setup partition 10 and 11 but I was only able to boot into recovery. I tried restoring a few backups, wiped data, cache, system, tried installing CM7 and always ended up only booting into recovery. As a last ditch effort I installed the stock 6.2.1 update.zip and it is back working again. I had to re-root and reinstall recovery but I've restored my backup and everything is back up and running fine. Now I'll be able to sleep tonight...
airmaxx23 said:
I was able to create and setup partition 10 and 11 but I was only able to boot into recovery. I tried restoring a few backups, wiped data, cache, system, tried installing CM7 and always ended up only booting into recovery. As a last ditch effort I installed the stock 6.2.1 update.zip and it is back working again. I had to re-root and reinstall recovery but I've restored my backup and everything is back up and running fine. Now I'll be able to sleep tonight...
Click to expand...
Click to collapse
I don't have that, do you have the thread?
Edit: found and I am all good now
So can I do this on my current ROM to add space for apps without losing data?
Well this thing bricked my KF. I'm having the same issues as the people from the previous posts. I installed 6.2.1 but now I'm stuck at the notorious "your Kindle has detected a problem" and nothing in CMD is working for me.
eldarerathis said:
Can you post your current partition table?
Click to expand...
Click to collapse
I don't have a copy of the partition table but the program tried to resize the media section and had an error then partition 10 and 11 were gone. I then used the steps in the last few posts of the manual partitioning guide to make partitions 10 and 11.
Matt V said:
Well this thing bricked my KF. I'm having the same issues as the people from the previous posts. I installed 6.2.1 but now I'm stuck at the notorious "your Kindle has detected a problem" and nothing in CMD is working for me.
Click to expand...
Click to collapse
As long as you can get into fastboot/recovery it should be fixable. FIREFIREFIRE v1.1 can 'fastboot oem format' to reset the device to its initial internal point, or in recovery you can examine the partition table and fix whatever is in a bad state.
airmaxx23 said:
I don't have a copy of the partition table but the program tried to resize the media section and had an error then partition 10 and 11 were gone. I then used the steps in the last few posts of the manual partitioning guide to make partitions 10 and 11.
Click to expand...
Click to collapse
Actually, would you be willing/able to post your layout as it is now? That could be helpful, too, even in its current working state.
Read my thread here for more information:
http://forum.xda-developers.com/showthread.php?t=1429661
Hello fellow I9000 users.
tl;dr - This fixes your low storage notification problems just by flashing it on CWM.
Disclaimer
First of all, I'd like to inform you that this post is a compilation of the work done by drafnel on the CyanogenMod forums, revthanki on the XDA-Developers forum, and as such I take little to no credit in it, as all I've done was ask for drafnel to help me in the cleanup code for me to put it in a flashable zip.
Sources:
http://forum.cyanogenmod.com/topic/39718-workaround-for-small-datadata-partition/
http://forum.xda-developers.com/showthread.php?t=1444333
Also, as you should know, you take full responsability should data loss or other kinds of damage occur.
Introduction
Lot's of people have encountered the problem where their /datadata partition fills up and then apps begin force closing. This is often confusing since there is usually a lot of space available on the internal 2GB storage partition. But these are two different partitions on cyanogenmod. The created the datadata partition on the fast internal memory so that apps would start up and run faster (i.e. less lag), but it is only about 170MB (which can't be helped).
One thing that can be done is to move the contents of /datadata onto the 2GB /data partition. That will solve the space problem, but then you have the lag problem. So, what we need is for the files that take up a lot of space to reside on the 2GB partition and the files that are accessed frequently by an app to reside an the fast 170MB partition. The files that are accessed often, or that affect app startup speed are the sqlite database files and the xml preferences files. These reside in the databases and shared_prefs sub-directories in each app directory. Drafnel has written a script to perform these operations.
Requirements
Samsung Galaxy S based phone (GT-I9000, Vibrant, Fascinate, Captivate, etc.)
Kernel that supports init.d scripts
How to use it?
As you would flash a ROM update or a Kernel:
Download the file to your sdcard.
Reboot your phone into CWM.
Choose 'install zip from sdcard', and choose the script from there.
It will run on boot everytime. It's pretty light so your total boot time shouldn't suffer. It will only do the operations if they are needed, and it will clean up after itself. No need to worry about broken links or stale resources.
What it actually does?
On every boot:
Runs a check to see if /data/data is still symlinked to /datadata/
Moves everything that isn't performance critical from /datadata/ to unlinked /data/data/
Cleans up old databases from uninstalled apps
Other stuff to watch out for
Titanium Backup users should tick the Preferences > Troubleshooting settings > Follow all symbolic links option
SlimICS users should follow this procedure
Changelog
11032012 - First working release.
LOL. I posted a request for exactly this script in the mintberry thread a few days ago!
Good work fella, Cheers.
OMG yeah! Was waiting for something like that . Will give it a try next time I'll encounter this problem .
Thanks mate.
Just flashed it. Cheers!
Sent from my GT-I9000 using xda premium
I had HUGE problems with Titanium Backup.
I lose all by backups some weeks ago because symlinked were corrupted after restore!
Njcki said:
I had HUGE problems with Titanium Backup.
I lose all by backups some weeks ago because symlinked were corrupted after restore!
Click to expand...
Click to collapse
According to this post, you can now force TB to follow all symbolic links for backup and restore.
what if i already moved all my apps data to sdcard? do i move it back to internal memory then flash the script, or just flash the script then move the data to internal memory? which is the correct way?
naTrium said:
According to this post, you can now force TB to follow all symbolic links for backup and restore.
Click to expand...
Click to collapse
Thanks! I'll try
AFAIK, if you have moved your apps to the SD card using the regular method (Apps2SD), the script will still work. This is because there's always leftover data on the phone, which then points to /.android_secure/ on the sdcard.
This script only changes the location of some data, but it's transparent to the phone.
If you don't feel safe about it, a full nandroid backup will restore the system to whatever setup you have now. (it also backs up what's mounted on the sdcard)
Well done! I knew I was never going to get round to this I'll close my old thread and redirect people here. Before I do so:
1) does the stock CM9 kernel support init.d scripts? If not stock kernel users will have to follow the manual method.
2) maybe it's worth putting a capitalised warning in your post to get people to set the option in Titanium Backup to follow all symbolic links
I flashed this script already but the low on space notification is still shown. It's definitely not working.
Do I have to create .nodatadata file inside /datadata and reboot now?
Sent from Ice-Cream flavored SGS GT-I9000 using Tapatalk
Free space in datadata folder,
Before flashing the script = 25mb
After flashing the script = 146mb
Definitely works without any lags.. one might experience lags on the first boot but after another reboot all gonna be super smooth like before!
Thanks a lot!!
It deleted some of my apps like Dolphin HD. I'm running CM9, with IcyGlitch Kernel. Oh well, restored.
Gr8 work
Many Thanks,
i have been waiting for this script ever since Darktremor Apps2SD (2010 !!! )
thank you!!!!!!!!!!!!!!
Great Job!
Excellent, it's very smooth like before, thanks a lot.
aha! that's the reason why all my apps suddenly began to lag like hell and some time after that force close. had only 1MB free space on /datadata partition lol. script works like a charm! thx
Sent from my GT-i9000 using xda premium
stfudude said:
I flashed this script already but the low on space notification is still shown. It's definitely not working.
Do I have to create .nodatadata file inside /datadata and reboot now?
Sent from Ice-Cream flavored SGS GT-I9000 using Tapatalk
Click to expand...
Click to collapse
I heard some kernels don't load init.d scripts on ICS, might be related to that.
finally......
before script 11mb and after got 168mb free space! thanks!
really nice stuff
{
"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"
}
This is CandySiX. Built straight from source with commits from a variety of different Sources/ROMS. We wanted to give the users a fun, fully customizable ROM. We aim to add more features as this project progresses.
Check us out on the web @The-Candy-Shop
@matthew0776 @mar5hal @gimmeitorilltell @Cuzz1369 @rc420head @Flashalot @Venomtester @Darknites @javelinanddart @calebcabob @NoSpamDan
ROM
DEVICES/KERNELS
Disclaimer: We here at The CandyShop are not responsible for any bricks you may obtain. Please follow the thread rules and steps and everything will be gravy. Remember, backing up before flashing is always recommended.
FEATURES
Choose from CMTE or OMS (RRO Layers is DEPRECATED)
Battery bar
LCD density options
Multi-window
Status bar customization
Quick setting customization
Quick setting pull down options
Force expand notifications
Time contextual headers in panel
Dark UI switch
Advanced power menu
Extra IME options
In-Call vibration options
Lockscreen customizations:
-Shortcuts
-Music visualizer
-WeatherAnimations:
-Power menu
-List view
-System
-ToastNavbar customization (CMTE only):
-SmartBar
-Fling
-Pulse Hardware Buttons settings:
-Slim Hardware key rebinding
-Long-press/double-tap actions
-Volume rockerOn the Go mode
Screenshot Crop & Share
Fully charged notification and toggle
CPU info overlay (Developer options)
Snap camera (Sultan's)
More to come, we are never done...
CHANGELOG
WARNING!
This is a Virtually Repartitioned ROM!
What this means is that you will need to take some special steps to flash this ROM. Don't worry, it's not that hard, and you will be able to return to stock with Odin at any time. The cool thing is that it will support a ton of app and app data storage and will behave like a more modern device.
The basic idea with virtual repartitioning is that the partitions are renumbered from the stock numbering, but not resized. So the most important parts of this are (as an FYI, you don't need to know this ):
-The 2GB /data partition becomes a most adequate 2GB /system partition for the ROM and GApps.
-The 12GB Internal SD partition becomes /data, so you have that space to install apps.
It is strongly recommended to use an External SD card to store the ROM/flashing files and for backups, etc., however it is not mandatory. If you do not have an External SD and you need to format the /data and /Internal storage partitions, you will have to copy the files you need from your PC again. Easy peasy, right?
FAQ/NOTES:
When formatting the device, first go to the Mount menu and make sure none of the partitions you want to format are mounted. If they are, formatting will fail.
Make sure you have NOT selected Mount USB Storage, and that the MTP button says "Enable MTP", which means it is DISABLED. If either of these are enabled, then formatting may fail.
The /system partition is formatted as EXT4.
The /data and /cache partitions can be formatted as either EXT4 or F2FS.
The Internal Storage should be formatted as EXT4 or F2FS.
The External SD card (if you have one) would be best formatted as FAT, which you can do in your computer. When the ROM boots, it will detect the card and offer you one of two different ways to use it, as "Internal storage" that will only work with your device for security (requires formatting and encryption by Android), or as "Portable storage" that will work in other devices.
CAUTION: With Internal, you will have to entirely format your card if you have issues and it can not be used in ANY other device. In fact, it will become invisible in file managers because it becomes an extension to the Internal SD card storage. Format the ExternalSD card to Internal Format at your own risk.
When formatting /data, the default behavior is that /data/media is not deleted. In order to wipe /data/media, you need to either go to TWRP > Wipe > Advanced wipe > Format data, or delete the folder manually through the file manager in TWRP.
TWRP > Wipe > Advanced wipe > Format data is also needed if you plan to use device encryption, because this step allows for a space at the end of /data to contain the encryption information. Without this, encryption will fail!
IMPORTANT: If you have flashed a modified PIT file, flash back the STOCK PIT. You can also return to stock by using Odin and a Factory Image.
If you are trying to get back to the stock partitioning:
Flash a stock TWRP recovery ZIP or IMG file, or use Odin to push a TAR recovery over. After doing this you need to reboot your device into Recovery to load up the newly flashed version, and format each of the partitions to their defaults (ext4, for the most part). If you encounter errors formatting, reboot back into Recovery and try again.
Check SamMobile.com for stock ROM packages. (There is a Stock ROM version in my AFH account which should be used for recovery purposes only.) Odin should also find the device if it's in download mode and you can flash a stock ROM back on it if you want.
If you are not sure you used the correct recovery or you just want to check the partition structure (I may ask for this), you can run each of these commands from an adb prompt, and save the output to a file for linking in the thread for help/analysis:
blkid
cat /proc/mounts
df
INSTALLATION STEPS:
Here is what you need to do; please follow the below steps carefully!
Connect your device to your computer and FULLY BACK UP YOUR FILES from both your Internal and External Storage!
While you are backing up your files, download the following files to your computer:
A custom TWRP recovery for virtually partitioned ROMs (see Post 2).
The ROM zip file (see Post 2).
A 6.0 Gapps package, pico recommended for now. (optional - see Post 2).
Copy all of these files to your device's External SD card. If you don't have an External SD card, then you will need to copy them over from your computer after formatting your internal storage.
MAKE A NANDROID BACKUP!
Using your EXISTING RECOVERY, format /system, /data, /cache and /Internal Storage.
Flash a VIRTUAL REPARTITIONED RECOVERY.
REBOOT to Recovery to use the new one.
Select Wipe > Advanced Wipe > System, then press the "Repair or change file system" button. Choose "Change File System" and select EXT4. Swipe to apply.
Press the back button and verify the Size: and Free: values at the top. The System partition should be 2GB. Press the Repair button and swipe to apply.
For good measure, now press the Resize button and swipe to apply.
Repeat steps 1-3 for the Data partition, choosing EXT4 or F2FS as the file system, then Repair and finally Resize.
Repeat steps 1-3 for the Cache partition, choosing EXT4 or F2FS as the file system, then Repair and finally Resize.
Reboot to Recovery and wipe /system again.
Flash the CandySiX zip
Flash Gapps (nano or pico Open GApps or BaNks ones, etc.). You may have to experiment a little.
Reboot and Enjoy
Please give first boot a good several minutes. If you get stuck at the boot animation for a long time, try removing your ExternalSD card and reboot without it.
IMPORTANT - PROBLEMS/ISSUES:
If you have issues, I need the following:
Logs from you (logcat, last_kmsg, dmesg) linked to on pastebin.com or hasteb.in, showing the failure.
A clear description of the steps that I need to take to exactly reproduce the problem.
State what flavor build you are on: CMTE, Layers, OMS, etc...
Please DO NOT complain about problems and offer nothing to help fix it. I reserve the right to ignore you for not following insructions...
NO ETA REQUESTS!
Special thanks to @gimmeitorilltell, @bryan2894, CyanogenMod, SlimRoms, Omni and all the rest who make their source open, we can't do this on our own.
XDA:DevDB Information
[ROM-DISCONTINUED][SGH-T989][6.0.1_r61][AOSP+CAF][CMTE+OMS][MM] CandySiX - Hercules, ROM for the T-Mobile Samsung Galaxy S II
Contributors
NoSpamDan, gimmeitorilltell
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x
Based On: AOSP
Version Information
Status: No Longer Updated
Current Stable Version: 3.2
Stable Release Date: 2016-02-11
Created 2016-01-01
Last Updated 2017-01-05
Downloads
Make sure you have FULLY READ and FULLY UNDERSTAND the OP (Post 1) above before following any steps!
RECOVERY
BaNks just announced they aren't supporting TWRP versions below 3.0.
@bryan2894 has a Flashable 3.X version you can flash here:
https://androidfilehost.com/?fid=24545065934258236
(My previous TWRP 2.8.7.0 for Virtual Partitioned ROMs: TWRP_2.8.7.0.VP_hercules_NSD.zip)
TWO ROM VERSIONS: Effective 26July2016, choose from CMTE or OMS/Substratum!
(You can NOT flash one on top of the other... If you decide to switch and try the other one, you MUST Clean Flash!)
DOWNLOAD CMTE (CM Theme Engine based) ROM:
CandySiX-celox-3.2-OFFICIAL-0903.zip
DOWNLOAD OMS/Substratum themed ROM (Substratum app required - Guide to using Substratum):
CandySiX-celox-3.2.S-OFFICIAL-0910.zip
GAPPS
"Normal" BaNks Dynamic GApps
Open GApps
Your best bet is to flash a Pico GApps package made for Android Marshmallow which doesn't have an included keyboard or any keyboard modifications. Watch out for GApps that replace Gallery too!
EXTRAS
- If you want to remove the built-in SuperSU, flash this in recovery after the ROM: SuperSU_Root_Remover.zip
Previous ROM versions for convenience (can be found on my AFH account unless they are OTAs).
DO NOT FLASH a CMTE ROM on top of an OMS or LAYERS version. You must CLEAN FLASH if switching theme engines!
OMS/Substratum-based:
CandySiX-celox-3.2.S-OFFICIAL-0902.zip
CandySiX-celox-3.2.S-OFFICIAL-0817.zip
CandySiX-celox-3.2.S-OFFICIAL-0808.zip
CandySiX-celox-3.2.S-OFFICIAL-0807.zip
CMTE-based:
CandySiX-celox-3.2-OFFICIAL-0817.zip
CandySiX-celox-3.2-OFFICIAL-0809.zip
CandySiX-celox-3.2-OFFICIAL-0807.zip
CandySiX-celox-3.1-OFFICIAL-0728.zip
Layers-based (deprecated):
CandySiX-celox-2.3-OFFICIAL-0514.zip
Previous GApps versions can be found on my AFH account here.
FAQ/Info
Due to several requests, here is some further information...
DISABLE HARDWARE CAPACITIVE KEYS AND LIGHTS
NOTE: This information is now outdated, as I've added ROM features for it. I'll leave it here, but hidden for now...
Several have asked about this. I am working on an in-ROM setting for each, but I simply haven't had the time. For now you can do it manually if you like.
If you decide to try/use the following instructions, please understand that you do this entirely at your own risk
Some people like to use the NavBar soft keys (on-screen). If this is you, below you will find some commands you can use to disable the built-in Hardware Keys and Hardware Key Lights.
***NOTE: Both the HW Keys switch and the HW Key Lights switch are a WIP and do not currently work properly!
Using adb or a terminal emulator app (or the built-in one that you can install in your app drawer by enabling Settings > Developer Options > Local terminal), issue the commands under the HW Keys option you want to apply.
For each item listed, copy/paste or type the commands, one line at a time, and EXACTLY as they are shown. Press ENTER after each command.
Open adb or the terminal emulator app and issue the following commands to start a shell with root access. Press ENTER after each command.
(Be sure to accept any Superuser root access propmpts you receive while doing this.)
Code:
adb shell
su root
Now issue one or a combination of the following:
To DISABLE Hardware Touch KEYS:
Code:
echo 0 > /sys/class/sec/sec_touchkey/keypad_enable
To ENABLE Hardware Touch KEYS:
Code:
echo 1 > /sys/class/sec/sec_touchkey/keypad_enable
You should be able to use the ScreenFilter app from the Play Store to disable the HW Key lights. You can even disable the Screen Filter notifications if you like (long-press on the notification, then select the "i" button), but beware this could trick you later.
Enjoy!
Let me know how this works out for you folks. I still need Mobile Data tested and please remember it's Alpha right now, so I need logs when things aren't working.
Thanks for your work. I'm excited for testing this rom.
juni12 said:
Thanks for your work. I'm excited for testing this rom.
Click to expand...
Click to collapse
It is a WIP right now, and there will be more Candy goodness added soon... Hopefully everything works for the Herc since I don't own one (but I have a Skyrocket and have actually flashed Herc ROMs on it )
Stand by... new build compiling now... seems something was missing for Mobile Data to work. I'll update the d/l link when ready.
EDIT: New build is up, and Mobile Data works. Happy New Year!
@NoSpamDan
candy6, thanks for the great work , u really rock man
Just a heads-up, make sure you grab this build or newer for now: CandySiX-alpha-hercules-OFFICIAL-0101-06.zip
(The previous "UNOFFICIAL" builds had broken vendor blobs and no mobile data.)
EDIT: I have updated Post 2 with a modified BanKs Dynamic GApps version that has the keyboard libraries removed. Temporarily fixes the AOSP keyboard FC. You can get Google Keyboard after setting up your account on the Play Store...
Gonna try this soon.
My assessments after set up.............this rom is rocking crazy fast than cm13 (no offense) even when browsing and using play store.
Issues for me:
1. One issue is the constant show of "sd card" info after reboot (am cool with that for now).
2. No navigation bar toggle (my captivative navigation is off and I use on screen navigation to get around everytime).
3. No DPI change option (Know will come with time as above but I hate the 240 default ,too big for me)
But with Xposed, I managed to fix all of the above with the exception of "sd card" constant nagging.
This rom rocks, will update if I find any issues.
Thanks.
edwin270 said:
My assessments after set up.............this rom is rocking crazy fast than cm13 (no offense) even when browsing and using play store.
Issues for me:
1. One issue is the constant show of "sd card" info after reboot (am cool with that for now).
2. No navigation bar toggle (my captivative navigation is off and I use on screen navigation to get around everytime).
3. No DPI change option (Know will come with time as above but I hate the 240 default ,too big for me)
But with Xposed, I managed to fix all of the above with the exception of "sd card" constant nagging.
This rom rocks, will update if I find any issues.
Thanks.
Click to expand...
Click to collapse
I would call those preferences, not issues...
1. Swipe away the notification unless you have not initially set up the card (you didn't quote the notification message you are getting).
2. Nav bar is in the next build... are your touch light buttons broken?
3. DPI may be forthcoming, not sure.
EDIT: Navbar does not appear to be present in the new build. Looking into it.
New build is up in Post 2: CandySiX-alpha-hercules-OFFICIAL-0102-16.zip
This one has Quick Settings Tile Customization, Status Bar mods, Battery mods... more features to come in the near future!
...
juni12 said:
About the first build if we talk about performance, you can put beta because the rom works super fast. For a fledgling rom it is excellent. It would alfa because it lacks certain configurations and features (such as screen capture, buttons Turn off lights ...) but it is significant that installs Facebook, which in other roms including lollipop did not occur. Thanks!
Click to expand...
Click to collapse
Depends what version you are runnig because Vol Dn. + Power has always been for screenshot, plus in my last build, there were Power menu customizations like Screen Shot for those who prefer that method. Look in Settings > Candy Interface.
CandySiX was maturing on the previous CyanogenMod base but the decision was made to switch to an AOSP base. Come CAF repos are needed and still some CM too, but things are speeding back into shape! Next build should have NavBar (I hope). Will be testing soon.
New build up in Post 2 with working Navigation Bar and some other things - CandySiX-alpha-hercules-OFFICIAL-0103-04.zip. Things will be slowing down here shortly once I return to work...
New build with more features is in Post 2: CandySiX-alpha-hercules-OFFICIAL-0105-05.zip
Sorry, no time to outline the changes but should have Quick Unlock, new boot animation and several other updates...
EDIT: Seems like there is no boot animation, but it indeed boots...
I'm looking into it, but in the interim you can flash the stock Google one:
http://forum.xda-developers.com/devdb/project/dl/?id=16024
Bootloop
NoSpamDan said:
New build with more features is in Post 2: CandySiX-alpha-hercules-OFFICIAL-0105-05.zip
EDIT: Seems like there is no boot animation, but it indeed boots...
I'm looking into it, but in the interim you can flash the stock Google one:
http://forum.xda-developers.com/devdb/project/dl/?id=16024
Click to expand...
Click to collapse
Flashed the bootanimation zip now stuck in bootloop..
Anyways awesome ROM!
Fast and stable
Thanks for this.. =)
2 issues though: a) phone reboots when using camera flash (perhaps on low battery)
b) external SD card is not mounted it only shows as a portable storage - no ext SD in gallery etc.
Lucky2say said:
Flashed the bootanimation zip now stuck in bootloop..
Anyways awesome ROM!
Fast and stable
Thanks for this.. =)
2 issues though: a) phone reboots when using camera flash (perhaps on low battery)
b) external SD card is not mounted it only shows as a portable storage - no ext SD in gallery etc.
Click to expand...
Click to collapse
Bootloop? Please explain further, because it's not the boot animation file. I personally flashed the boot animation zip found in the downloads section and it works perfectly.
If you get in bootloop or have a camera flash issue (if it wasn't because of low battery), plug the device into your PC and get a dmesg log while in an adb shell, or reboot to recovery and pull a /proc/last_kmsg log. Also log the issue with logcat and post the logs on pastebin, providing the links here please. I can't fix what I can't reproduce or see in a log.
If you formatted your external SD card as portable that is how it will be used... (not as internal). Try reformatting it within the ROM.
Cheers!
Cheers![/QUOTE]
Bootloop? Please explain further, because it's not the boot animation file. I personally flashed the boot animation zip found in the downloads section and it works perfectly.
Click to expand...
Click to collapse
My bad.. I may have done something wrong tweaking settings and stuff. I changed DPI, it got bootloop, I formatted external card using TWRP VP, it got bootloop, etc. I reflashed ROM, Gapps and bootanimation. Now it's working fine.
have a camera flash issue (if it wasn't because of low battery)
Click to expand...
Click to collapse
I've switched to google camera app and the problem is gone. (Even with low battery)
If you formatted your external SD card as portable that is how it will be used... (not as internal). Try reformatting it within the ROM.
Click to expand...
Click to collapse
Honestly, I didn't know that marshmallow has introduced the new portable function for External SD. I was looking for the old way of External SD mount (I don't know what to call it.) again it was my fault.
plug the device into your PC and get a dmesg log while in an adb shell, or reboot to recovery and pull a /proc/last_kmsg log. Also log the issue with logcat and post the logs on pastebin, providing the links here please. I can't fix what I can't reproduce or see in a log.
Click to expand...
Click to collapse
I didn't post the logs because the problems were caused by my side. I shouldn't have disabled some apps and flashed boot animation after using the rom.
As you might have figured out i'm a noob (guilty! I know I deserve to die! =P ), one more thing, there's no youtube, calender, calculator and browser apps included in the package/rom. Or is it just me?
This is a perfect rom.
Many Thanks!