Intro:
---------------------
Extended TWRP is based on official Team Win Recovery Project, but modified** to address some special methods & features found on The HD2,
a device which has 3 different android loaders (cLK, MAGLDR and Haret) and various Android Rom configurations (DataOnExt, NativeSD, SD, Nand).
** If you are just looking for an unmodified TWRP for the HD2, check here.
I take no credit for this. All the creative hard work was already done!
Credits to:
agrabren, Dees_Troy, ViViDboarder, and AssassinsLament - core twrp 2 development team.
Toastcfh – for his underappreciated dedication to the community.
s0up and kevank - for their hard work on the web side of things.
shift, onicrom, netarchy, kevank, myndwire, bigbiff, dkelle4, shinzul, spiicytuna, and eyeballer - the rest of Team Win.
Amon_RA - for his great Recovery.
Koush - for his dedication to the community and ClockworkMod.
Akmzero, arif-ali, Evil_DevNull, gus6464, Jesusice, _jmz_, NxtGenCowboy, ohshaith55, Pyrostic, [R], and Rootzwiki - for all the help with devices and testing.
Team's supporters and the Android Community.
However, if you think that this extended version is full of unnecessary cr*p or that something is not working as expected anymore,
Credits to:
me
Notice:
---------------------
For me, this thread is about learning while having fun. It would be ideal if it leads to something that is really useful.
So, as you may have already understood, This Is Not a release thread. If you have the time and interest to help in any way, please do. Cause together we can make sure that this project will benefit all of us.
The attached recovery image is provided for people who can't compile it from source, but want to either help in debugging or just experiment.
Have in mind that before attaching it here, it was only tested on one HTC-HD2(Eu) powered by (black) cLK bootloader.
The performance on devices powered by MAGLDR bootloader or running the good-old WM6.X should be considered untested.
In order to exploit the full potentials of this software, Black cLK bootloader is strongly recommended!
As usual, use at your own risk. TeamWin or kokotas is not responsible for anything bad that may occur from using Extended TWRP.
ReadMe
Features:
---------------------
**************Mainline**************
* Ability to save custom recovery settings
* Touchscreen driven with real buttons and drag-to-scroll
* XML-based GUI that allows full customization of the layout – true theming!
* Settings are saved to the sdcard and persist through reboots
* Ability to choose which partitions to back up and which to restore
* Ability to choose to compress backups – now with pigz (multi-core processor support for faster compression times)
* Ability to backup large partitions (size>1.5GB) by splitting the backup archive.
* Basic file manager (copy, move, delete, and chmod any file)
* OpenRecoveryScript scripting engine
* On-screen keyboard in recovery! -- supports long press, backspace repeat, and swipe left deletes everything left of the cursor
* ADB sideload functionality from AOSP
* Pseudo-terminal emulator
* Decryption support
* Ability to set a timeout for auto-turning off the screen
* exFAT support for sdcard's 1st partition
* Manual screen rotation
**************Extended**************
* Proper detection of bootloader(cLK/MAGLDR/haret)
* Support for cLK's extra boot partitions
* Tweaked off-mode charging for cLK (device can wake up by pressing any key)
* Direct rebooting to selected boot partition for cLK bootloader
* Direct rebooting with selected kernel from NativeSD folder for MAGLDR bootloader
* Ability to communicate with cLK in order to change partitions' size if needed
* Built-in NativeSD manager(Backup - Restore - Delete - Fix Permissions - Wipe Data - Wipe Dalvik-Cache - [cLK]Kernel-Restore)
* Option to skip any NativeSD Rom during sd-ext's partition backup
* Option to adjust backup/restore process for DataOnExt method
*
* Nilfs2 support for sdcard's ext(2nd/3rd primary) partition
* NTFS support for sdcard's 1st primary partition
* Option for converting file system [ext2 - ext3 - ext4 - nilfs2] of sdcard's ext partition (without losing any data if there is enough space on the /sdcard)
* Option for adding a 3rd primary partition(mmcblk0p3 as /sdext2)
* Option to skip dalvik-cache during backup
* Ability to restore backups that were made using a CWM Recovery
* Ability to check SD Card's filesystem(s)
* Ability to run shell scripts from your SD Card (script location: /sdcard/TWRP/scripts)
* Ability to "run" recovery (AROMA based) apps with one click (app location: /sdcard/TWRP/app)
* Ability to select current theme (example of theme file location /sdcard/TWRP/theme/MyTheme/ui.zip)
* Ability to check the size of the backup to be restored
* Ability to take screenshot (screenshots location: /sdcard/TWRP/screenshots)
* Configurable haptic feedback
* Configurable system tweaks (cpu gov, cpu freq, i/o sched, drop_caches)
Source:
---------------------
Extended-Team-Win-Recovery-Project
Looks:
---------------------
Screenshots
Compatible themes:
TWRP's Default Style Blue Theme for v2.5.0.5
Dark_Avenger's Holo Dark Theme for v2.6.3.0
Download:
---------------------
HD2_EXTENDED_TWRP_2.6.3.4.zip
md5: 5af088d200a00e0a3efb27860a5168c6
Info: You need to have a recovery partition at least 9 MB to fit the img
HD2_EXTENDED_SD_TWRP_2.6.3.4.zip
Info: Extract to the root of your SD Card
Frequent issues:
---------------------
If you report an issue without a log and/or without details, that's not very helpful in tracking down that issue, so, eventually, don't expect any assistance cause I am not a medium.
If you get a "status 2" error when installing a recovery-update-package(zip) that used to work with your old recovery, change the update-binary inside the zip file with a newer one (API 3).
DON'T FORGET to check the syntax in the updater-script and verify that format() and mount() commands have the correct amount of arguments, otherwise you'll end up having other errors like "status 7".
i.e. if you use the update-binary included in the attached file below, format takes 2: format("MTD", "boot").
If you occasionally can't boot into recovery, try increasing the size of its partition >= 10MB.
Installation:
---------------------
[Basic stuff before installing]
Make sure you have adb and fastboot working (required files here). Please don't ask here questions about this - a simple web search will be enough to help you.
Make sure that the size of the 'recovery' partition is enough for the image to fit.
Make sure the name of the recovery *.img file is the one you use in the commands or in flash.cfg
[Flashing occasions]
[cLK/MAGLDR]
Flashing the zip file from existing Recovery
Download zip file to your computer and copy to /sdcard.
Reboot phone into recovery.
Select to install the zip file from your /sdcard.
Reboot Phone into recovery as normal.
[cLK/MAGLDR]
Flashing the *.img file while booted in Android or in Recovery
Download the recovery file to your computer.
If it is a zip file, extract the *.img.
(Win) Open the folder you have the recovery, do a [Shift+RightClick] and select "Open command window here".
(Lnx) Open the folder you have the recovery, RigthClick and select "Open in Terminal".
Execute the commands:
Code:
adb push recovery.img /sdcard/recovery.img
adb shell erase_image recovery
adb shell flash_image recovery /sdcard/recovery.img
Reboot Phone into recovery as normal.
[cLK]
Flashing the *.img file while in fastboot mode(cLK menu)
Download the recovery file to your computer.
If it is a zip file, extract the *.img.
(Win) Open the folder you have the recovery, do a [Shift+RightClick] and select "Open command window here".
(Lnx) Open the folder you have the recovery, RigthClick and select "Open in Terminal".
Reboot phone into cLK menu (fastboot mode).
If needed, change the size of the 'recovery' partition on the fly (under SETTINGS/RESIZE PARTITIONS).
Execute the commands:
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot oem boot-recovery
[MAGLDR]
Flashing the *.img file while in USB Flasher mode(using DAF.exe)
Code:
[B][COLOR="Red"]WARNING!!![/COLOR] This way of flashing will erase your current Rom on NAND too!
You will probably want to do this
[COLOR="Red"]ONLY IF[/COLOR] you need to increase the size of the 'recovery' partition![/B]
Download the recovery file to your computer.
If it is a zip file, extract the *.img.
Open the folder you have the recovery and place DAF.exe and flash.cfg in that same folder.
Edit flash.cfg according to required recovery partition size:
Make sure the .img file has the name that flash.cfg specifies!!
i.e. If the *.img file is named recovery.img and min-required-size = 8MB then the flash.cfg could be:
Code:
misc ya 1M
[U]recovery rrecov|ro|nospr 8M recovery.img[/U]
boot yboot|ro 5M
system ya 150M
cache ya 2M
userdata ya|asize|hr allsize
Check out the info about flash.cfg.
Connect the device to the computer via usb, enter MAGLDR and select USB Flasher option.
Right click on DAF.exe and select Run as Administrator.
Click [NEXT] when asked and wait to finish.
Post-Installation:
---------------------
Make sure you delete /sdcard/TWRP/.twrps.
If you're using a theme, update your theme file or temporarily switch to the default theme.
A big Thank-You for supporting/testing the ExtendedTWRP to:
---------------------
Dark_Avenger
NYLimited
DarrenNewsgroup
Nixda99
MarkAtHome
Robbie P
Timeline
Commit History
HD2_Extended_TWRP_2.6.3.4 @ 2013.11.24
Compiled tytung's jellybean kernel with CONFIG_YAFFS_XATTR=y
and replaced existing recovery kernel.
Attempt to fix curtain.jpg loading bug.
HD2_Extended_TWRP_2.6.3.3 @ 2013.11.20
Reverted to 2.x kernel (more stable and smaller size).
HD2_Extended_TWRP_2.6.3.2 @ 2013.11.20
Ported latest mainline commits.
Compiled without ntfs and exFat support (since no existing HD2 Rom really requires any of them).
Switched to 3.x kernel (github.com/TeamNightmare/android_kernel_htc_leo).
HD2_Extended_TWRP_2.6.3.0 @ 2013.09.19
Ported latest mainline commits (update to v2.6.3.0).
Disabled the ability to encrypt the backup of the data partition. Rolled back to old twrpTar code in an attempt to temporarily fix some backup/restore errors.
(The backups made by previous versions might not be good).
HD2_Extended_TWRP_2.6.1.2 @ 2013.09.09
Fix crashing when installing a recovery-package.
Added "bootloader=haret" to startup.txt for haret's case.
HD2_Extended_TWRP_2.6.1.1 @ 2013.09.06
Reverted a commit that messed up the rotation feature.
Attempt to improve bootloader detection.
HD2_Extended_TWRP_2.6.1.0 @ 2013.08.31
Ported latest mainline commits (update to v2.6.1.0).
HD2_Extended_TWRP_2.6.0.0 @ 2013.07.16
Ported (most of the) latest mainline commits (update to v2.6).
Ported Vojtech Bocek's screen rotation.
Old themes are not compatible!
Instead of one ui.xml file, the new theme requires two files portrait.xml and landscape.xml and the appropriate images.
Misc code cleanups/fixes.
HD2_Extended_TWRP_2.5.0.5 @ 2013.05.10
Try to fix libtar bug (present when creating sd-ext's backup).
Reboot options for "recovery" and "bootloader" will be available for cLK only.
Revised nativeSD manager.
HD2_Extended_TWRP_2.5.0.4 @ 2013.05.08
Made partitionlist's selection persist.
Added ability to load selected theme's curtain.jpg.
Fixed slider-touch.png, changed list's header separator color to red and reordered header info in built-in theme.
Revised how twrp handles 'userdata' partition when DataOnExt mode is.
Cause there is a chance 'DalvikOnNand' method is used.
Cleaned up unused code and added a flag for HD2-specific stuff so if anyone would try to build Extended TWRP for another device it would be easier.
HD2_Extended_TWRP_2.5.0.3 @ 2013.05.06
Added "View file" under filemanager options (it's more or less like 'cat /file').
Small fix to off-mode charging.
Attempt to fix progress bar issue.
Changed built-in theme. The new one is based on Dark_Avenger's Holo Dark.
Changed some log messages.
HD2_Extended_TWRP_2.5.0.2 @ 2013.04.22
Changed behavior of "Reset Defaults". Device will reboot after that.
Changed handling of extra boot partitions for cLK.
Now you can backup/restore/wipe any of those partitions just like the default ones!
(In the end this means that you can backup/restore EVERYTHING at once)
Changed versioning way (last digit will be used for the extended revision).
Changed screenshot function:
If the system is busy (perhaps doing something (?) to the sdcard) no screenshot will be taken if you press the top logo.
Otherwise, in order to notify the user that a screenshot was successfully taken the keys backlight will blink.
Reorganized/rewrote some of the code (backup/restore/wipe) around "partitionlist".
Removed sfdisk.
Recompiled tytung_jellybean_r2 kernel with increased MSM_MAX_PARTITIONS to 20 (this will fix the detection of cLK's extra boot partitions).
Misc fixes that I don't remember now...
HD2_Extended_TWRP_2.5.0.0_r1 @ 2013.04.17
Ported latest mainline commits (update to v2.5).
Fixed battery_thread().
Added ability to auto delete logs from cache to free up some space when needed (see Dark_Avenger's post).
Switched kernel to tytung_jellybean_r2.
Misc fixes.
Compiled img with TW_INCLUDE_CRYPTO = true & TW_INCLUDE_JB_CRYPTO = true.
Increased required min size to 9MB.
HD2_Extended_TWRP_2.4.4.0_r7 @ 2013.04.05
Attempt to fix /sdcard mounting issues in case of slow cards(thanks to Darren for helping).
Fixed restoring a tar that was made with a previous version that used busybox tar.
HD2_Extended_TWRP_2.4.4.0_r6 @ 2013.04.03
Attempt to fix archive extraction during restore.
Added separate option for excluding dalvik-cache from a NativeSD Rom's backup under NativeSD Manager Settings.
HD2_Extended_TWRP_2.4.4.0_r5 @ 2013.04.02
Attempt to fix timezone dst settings.
Revised extractTarFork() function.
HD2_Extended_TWRP_2.4.4.0_r4 @ 2013.03.31
3rd attempt to fix sdcard partitioning.
Added option for magldr users to select which NativeSD Rom to reboot to(jskenderi's idea).
Fixed cpu governor selection not getting applied at boot.
Removed "read_ahead_kb" tweaks from init.rc.
Revised LoadValues() function.
HD2_Extended_TWRP_2.4.4.0_r3 @ 2013.03.22
2nd attempt to fix sdcard partitioning.
Changed "Enable MD5 verification" to "Skip MD5 verification" - The default behavior is to verify md5s.
Fixed a bug regarding backing up with "Exclude NativeSD Roms..." option enabled.
HD2_Extended_TWRP_2.4.4.0_r2 @ 2013.03.20
First attempt to fix sdcard partitioning.
Ported latest mainline md5sum fix.
Fixed NativeSD dalvik wipe.
Replaced the option for the preboot scrict with an option to force TWRP to handle boot partition as 'mtd'.
Only MAGLDR users will be able to see it AND in case your "boot" is raw (rboot was used in flash.cfg), enable it!
HD2_Extended_TWRP_2.4.4.0_r1 @ 2013.03.14
Ported latest mainline commits.
Updated/fixed clkpartmgr (needs cLK v1.5.2.0 to work correctly) - partition size is passed in blocks.
Revised storage partitioning method.
Enabled ntfs and exFat formats for card's 1st primary partition.
Switched to libtar for archive handling.
Switched to libblkid for filesystem detection.
Added more options for haptic feedback.
Added option under "Settings" for the preboot scrict that sets the filesystem for "boot" partition before recovery loads recovery.fstab.
If your bootloader is MAGLDR and "boot" is raw, disable it. IN ANY OTHER CASE leave it enabled.
If you don't know what I'm talking about, leave it enabled.
Kernel is compiled with defaults: gov = performance, i/o scheduler = deadline, cpu freq = (245 - 998)MHz
SD Card read_ahead_kb set to 2048, NAND's partitions read_ahead_kb set to 128
Added system tweaks options (cpu gov, i/o scheduler, cpu max/min freq, available memory boost).
If we want to have a theme setting persisted there is a new function <action function="save"> instead of <action function="set">.
HD2_Extended_TWRP_2.4.3.0_r3 @ 2013.03.04
Reverted the way TWRP handles 'boot' partition's file-system.
Backup/restore for MAGLDR should work now.
Ported the dim effect before screen turns off from mainline.
Misc small changes in code.
HD2_Extended_TWRP_2.4.3.0_r2 @ 2013.03.02
Reverted fileselector to clear by default the data variable.
HD2_Extended_TWRP_2.4.3.0_r1 @ 2013.03.01
Ported mainline commits (update to 2.4.3.0).
One of them fixes the fileselector bug.
1st attempt to fix UI's bug (hot-rebooting after theme changing).
HD2_Extended_TWRP_2.4.2.0_r2 @ 2013.02.27
Fixed screen timeout not being loaded at boot (instead it was always 60 sec).
Added haptic feedback and an option to enable it under "Settings".
Fixed screenshot feature.
HD2_Extended_TWRP_2.4.2.0_r1 @ 2013.02.25
Added option for the root checking stuff. If you don't want TWRP messing with your system you have the option to disable it under "Settings".
Added option to select the clock-time format.
Cleaned up blanktimer.
HD2_Extended_TWRP_2.4.1.0_r3 @ 2013.02.24
Ported latest mainline commits.
Some of them were already in Extended TWRP(button highlight and 24h clock)
One of them added a "Screen" button under "Settings" which gives you the option to
(a)set the timeout for auto-turning-off the screen and
(b)set the level of screen brightness.
Created separate thread for monitoring battery capacity and usb status.
Led will work as normal. I've also set it to blink the amber led if battery < 10%.
Tweaked offmode-charging (this is for cLK users that don't use cLK's built-in offmode charging mode).
Fast charging is enabled in kernel and 'Powersave' settings will be used.
Also added the ability to wake up the device while offmode-charging by pressing ANY key.
Removed unused/duplicate options from "Settings".
When you skip dalvik-cache during a backup, a file named .nodalvikcache will be created in the backup folder with the size of dalvik-cache stored inside.
This will be used whenever you restore that backup in order to add that size to the calculations for minimum partition's size.
In case the '.nodalvikcache' file doesn't exist there is an option to set the increment(%) for the size of the partition to which a backup that doesn't contain dalvik-cache will be restored. Default value is 40%.
Changed the way TWRP handles 'boot' partition's file-system. It doesn't depend anymore on which bootloader we have (cause MAGLDR supports both yaffs2 and raw mtd).
Code:
Dropped the logic:
If cLK => mtd
else => yaffs2
Now it really checks the file-system.I think
Added the ability to restore a backup made with cLK as bootloader on MAGLDR.
...
HD2_Extended_TWRP_2.4.1.0_r2 @ 2013.02.11
Moved option for backing up nand's userdata to BACKUP page.
Instead of Data show DataOnExt or DataOnNand accordingly.
Added option under "SETTINGS" page to let TWRP check if a partition's size is enough for its backup to be restored before tar throws an error caused of insufficient space.
MAGLDR users: if the selected part of your backup is larger than the actual size of the partition, this part will be excluded from the restore process.
cLK users: Update to v1.5.1.9 and size mismatches will be no problem, since TWRP and cLK will automatically resize any partition that needs resizing.
Show progressbar during NativeSD backup.
Updated clkpartmgr (the args passed to it have changed too).
HD2_Extended_TWRP_2.4.1.0_r1 @ 2013.02.06
Port mainline commit(TWFuncc::Get_Folder_Size and MD5 checking).
Added function for finding a file on storage using the file's name and used it in OpenRecoveryScript.
Add clkpartmgr to TWRP.
HD2_Extended_TWRP_2.4.0.0_r8 @ 2013.02.01
When restoring a backup with DataOnExt show 'data' instead of 'sd-ext' under Restore page.
Always reset Use_unyaffs_To_Restore to false.
Fix Recreate_DataOnExt_Folder().
HD2_Extended_TWRP_2.4.0.0_r7 @ 2013.02.01
Created separate thread for updating time clock in order to avoid having it frozen.
Fix for sd-ext button disappearing after wiping.
Recreate folder for DataOnExt after wiping sd-ext.
Port last mailine commits.
HD2_Extended_TWRP_2.4.0.0_r6 @ 2013.01.31
Fixed backup part selection when there are split archives.
Corrected free space calculation in FS-converting and NativeSD-backup.
Time format changed to hh:mm:ss. (Sometimes seconds get frozen but it's nothing to worry about)
Misc NativeSD Manager fixes.
HD2_Extended_TWRP_2.4.0.0_r5 @ 2013.01.30
Added ability to select theme.
You must place the theme file(ui.zip) in a folder under /sdcard/TWRP/theme (eg /sdcard/TWRP/theme/Holo_Dark/ui.zip)
Added ability to select and load a recovery package like Aroma-File-Manager or NativeSD-Recovery.
You must place the files (*.zip) under /sdcard/TWRP/app.
Fixed NativeSD backup(tar arguments error).
Moved Update_Size() from Mount() function to Wipe().
HD2_Extended_TWRP_2.4.0.0_r4 @ 2013.01.29
Fixed a mounting issue:
Update_Size() function was called inside Mount().
However inside Update_Size() there was a call for Mount() and UnMount(!?) causing a mess.
Lets see if this could fix the problem with DataOnExt too.
HD2_Extended_TWRP_2.4.0.0_r3 @ 2013.01.29
Ported mainline commits till 29th of Jan.
Fixed boot partition's flag so that it can be wiped
Settings file (.twrps) is now read once at boot.
The TWRP folder structure on /sdcard will be auto-generated.
HD2_Extended_TWRP_2.4.0.0_r2 @ 2013.01.27
Updated to twrp2.4.
Ported all mainline commits till 26th of Jan.
Rewrote most of the extended functions.
Added option to format all main partitions except for /sdcard.
Added new feature in file manager: the size of the selected file or folder will be shown in the operation page.
HD2_Extended_TWRP_2.3.3.0_rev12 @ 2013.01.16
One&only purpose: Attempt to fix all issues for MAGLDR users.
Extensive logging is present in this rev.
HD2_Extended_TWRP_2.3.3.0_rev11 @ 2013.01.15
Second attempt to fix weird sdcard issues.
Added more logging output to help find the problem.
HD2_Extended_TWRP_2.3.3.0_rev10 @ 2013.01.14
Probably fixed the error during "Fix-Permissions" when DataOnExt is used.
Reverted changes in fstab as an attempt to fix weird sdcard issues.
HD2_Extended_TWRP_2.3.3.0_rev9 @ 2013.01.13
Another attempt to fix partitions' sizes for the backup process.
Added option (under "Backup" page) for the user to select if the NativeSD roms will be excluded or not from the sd-ext backup.
Added ability to run shell scripts that you might have on your sdcard (/sdcard/TWRP/scripts).
Added back the missing "Reload Theme" button under "Advanced" page.
HD2_Extended_TWRP_2.3.3.0_rev8 @ 2013.01.06
Changed the path where TWRP will save any taken screenshot to "/sdcard/TWRP/screenshots/".
The name of the png file will have this format "TWRPScr-001.png". The increment will be done automatically.
Unfortunately I haven't fixed the quality yet.
Added an option under "Settings" to "Enable path-checking for DataOnExt".
If enabled the path that will be used for the DataOnExt mode will be checked before any errors occur. Hopefully this will help non-experienced users to use DataOnExt function.
Added ability to automatically skip any NativeSD Rom folder from your sd-ext backup.
If you want to backup a NativeSD Rom do it from the NativeSD Manager.
Probably fixed the way TWRP calculates the partition sizes according to our extended settings(skip dalvik-cache - dataonext - skip nativesd roms).
So now the sizes (shown under "Backup" and) used during backup-process should be correct.
HD2_Extended_TWRP_2.3.3.0_rev7 @ 2013.01.04
Removed the second parsing of recovery.fstab (the one after "postrecoveryboot.sh" run). Instead the script "prerecoveryboot.sh" will run before TWRP parses the recovery.fstab file.
This should also eliminate any weird errors you've been seeing in the logs.
Attempt to resolve problems relevant to "Fix Permissions" when DataOnExt mode is ON.
Added a second step/check in UnMount() in case it fails the first time. Just like I did for the Mount() in previous rev.
Added option to skip saving "dalvik-cache" during backup (under "Backup" menu) in order to minimize the size of the backup file. After-all dalvik-cache is recreated. It will be like you've wiped it when you restore that backup.
Changed the way Backup & Restore work for DataOnExt:
If you have DataOnExt checked and you go ahead and start a backup process then
a (hidden) file called .dataonext will be created in the backup folder.
The path for your /data mount point will be stored inside that file.
Do not delete that file cause you'll have to recreate it manually!
Regardless of the settings you might have(DataOnExt checked or unchecked) if you go ahead and start a restore process of a backup with DataOnExt
(so it has the .dataonext file inside - if not it's easy to manually create it)
the option for "Setup recovery for DataOnExt" will be checked and
the path (DataOnExt button) will be reset to the path you had when the backup was done.
If you were using the entire /sd-ext for /data (original DataOnExt) when you made your backup then
when you restore that backup, the sd-ext will be formatted.
If you were using a subdir of /sd-ext for /data (modified DataOnExt like "/sdext/NexusHD2-JellyBean/data") when you made your backup then
when you restore that backup, the sd-ext will not be formatted - instead only that subdir will be deleted.
Ported Tasssadar's "clicked" effect to all buttons as feedback.
Been experimenting and added some code to be able to take a screenshot (will be saved as /sdcard/TWRPScr.png).
It is done by touching the top LOGO. To enable it, there is a relevant checkbox under "Settings".
It doesn't work as expected yet! The pics taken are crap but it's a wip...
HD2_Extended_TWRP_2.3.3.0_rev6 @ 2013.01.02
Fixed a problem when restoring an sd-ext backup that was made with CWM Recovery.
Added an option to run some filesystem checks on the sd-card under "Partition SD Card" button inside "Advanced".
Enabled power key to lock the screen.
HD2_Extended_TWRP_2.3.3.0_rev5 @ 2012.12.30
1st attempt to fix mounting problem(s) related to ext partition.
TWRP is now able to restore backups that were made using a CWM Recovery.
All you have to do is copy the entire backup folder (i.e. 2012-08-20.09.12.38) from /sdcard/clockworkmod/backup to /sdcard/TWRP/BACKUPS/htcleo
HD2_Extended_TWRP_2.3.3.0_rev4 @ 2012.12.28
1st attempt to fix TWRP's failure on file-system check when a partition has a label.
Changed how TWRP handles the ext partition(s) size while parsing recovery.fstab.
HD2_Extended_TWRP_2.3.3.0_rev3 @ 2012.12.27
3rd attempt to fix the .android_secure bug.
Added an SD version for testing.
HD2_Extended_TWRP_2.3.3.0_rev2 @ 2012.12.26
2nd attempt to fix the .android_secure bug.
1st attempt to fix the crash of sd card's partitioning when adding 2nd ext partition.
Reverted the logo to the default one.
New settings for fs-check and DataOnExt will be saved and not lost after a reset.
Switched the type of release from just an img-file to a flashable-zip with a script to check recovery's partition size before updating.
HD2_Extended_TWRP_2.3.3.0_rev1 @ 2012.12.24
Ported commits from mainline 2.3.3.0.
Changed how the DataOnExt will be handled.
Under "Settings" you'll find a checkbox with which you can "tell" recovery that you're using DataOnExt or not.
In case you're using a modified DataOnExt method you can set the actual path of your /data (i.e. /sd-ext/%RomName%/data) by hitting DataOnExt button.
Probably fixed the .android-secure bug.
Reverted the backup path(BACKUPS/htcleo/).
So you have to create an intermediate folder named "htcleo" under BACKUPS and move your backups inside.
Reverted the max size for splitting archive to 1.5GB.
1st attempt for saving the contents of your ext partition when you change the fs type (will need enough free space on your sdcard for this to work).
Added option to set the number of mounts that will trigger a filesystem check under "Settings".
Added option to wipe Data, Boot and (cLK)sBoot under "wipe" Menu.
Added necessary code for selecting fs type (vfat / ntfs) for /sdcard but since I can't make it function properly I've disabled it in the UI. (Also in case it will work using the ntfsprogs binaries, the size of the recovery will increase to ~ 8MB)
HD2_TWRP_2.3.2.X @ 2012.12.14
Detection of bootloader
Nilfs2 support for sdcard's ext partition
Option for converting file system(formatting) of sdcard's ext partition: [ext2 - ext3 - ext4 - nilfs2]
In-built NativeSD manager
Option for adding a 2nd ext partition(mmcblk0p3)
(cLK)Direct rebooting to selected boot partition
Option to adjust the backup process for DataOnExt case
1st attempt for archive splitting(also lowered the max size to 512MB)
1st attempt for MAGLDR boot restoring
Info
How to report a problem
Provide the log file.
In order to get it connect your device to pc via usb and run in terminal:
Code:
adb pull /tmp/recovery.log
If that fails for some strange reason then you could also try:
Code:
adb pull /cache/recovery/log
Or you could just use the "Copy Log" button under "Advanced" and have the log copied to the root of your card.
Give a short description of what triggered the problem.
If you don't have your device's setup in your signature, post that info too. For example:
Code:
HD2 ver.: EU
SDCard: Sandisk 32GB(c4)
SDCard's Partition Table: mmcblk0p1 [vfat,30GB], mmcblk0p2 [ext4,2GB]
Bootloader: cLK 1.5.1.6
NAND's Partition Table: recovery 8MB, misc 2MB, boot 4MB. userdata auto-size, system 200 MB, cache 2MB
Rom: HyperDroid 6.1 - NAND
Since this is a WIP, you could also use github to report any issue.
Theme related
Information on Official TWRP Theming.
Extended TWRP gives you the ability to choose between many themes.
When booting, it checks for a theme zip file on your card:
/sdcard/TWRP/theme is the location where you must create a folder named after the theme you will use and place the ui.zip inside it (i.e. /sdcard/TWRP/theme/Holo_Dark/ui.zip).
If none found then it will use the built-in theme.
For those who prefer the blue-ish TWRP default theme, I will be attaching it to this post every time something changes, so that you can use it as any external theme.
Since version 2.6.0.0, the theming engine of the Extended TWRP differs from the official.
Instead of one ui.xml file, the new theme requires two files portrait.xml and landscape.xml with the appropriate images.
Thanks for your work. Will try and report back.
Holo Dark theme for version 2.6.3.4 (portrait only).
Nice! will give this a shot
thanks.
Dark_Avenger said:
Updated Holo Dark theme for version 2.4.0.0 rev2
Click to expand...
Click to collapse
How is your theme applied? do you extract it and put it in a folder somewhere?
Re: [DEV][27/Jan/2013]Extended TWRP|v2.4.0.0.r2
Create a folder "/sdcard/TWRP/theme" and place the ui.zip there without unzipping it.
Sent from my HTC HD2 using Tapatalk 2
Re: [DEV][27/Jan/2013]Extended TWRP|v2.4.0.0.r2
v2.4.0.0r2 is not mounting my sd-ext at all, when I checkmark it manually, it vanishes after a short while.
Obviously, fix permissions don't work. Backups menu reports 0 size.
My log: http://ompldr.org/vaDk5aw/recovery.log
System setup:
Boot loader: Black cLK 1.5.1.6
Radio: 2.15.50.14
ROM: NexusHD2-JellyBean-1.3a
SD card: SanDisk class 4 30GB fat32 mmcblk0p1 and 2GB ext4 mmcblk0p2
Internal partitions: system 390M, user data auto, recovery 8M, rest cLK default.
TWRP v2.3.3.0rev7 was the last extended recovery that worked perfectly for me.
Thanks kokotas. =)
Sent with love from me to you via HTC HD2 with Tapatalk 2
sunitknandi said:
v2.4.0.0r2 is not mounting my sd-ext at all, when I checkmark it manually, it vanishes after a short while.
Obviously, fix permissions don't work. Backups menu reports 0 size.
My log: http://ompldr.org/vaDk5aw/recovery.log
System setup:
Boot loader: Black cLK 1.5.1.6
Radio: 2.15.50.14
ROM: NexusHD2-JellyBean-1.3a
SD card: SanDisk class 4 30GB fat32 mmcblk0p1 and 2GB ext4 mmcblk0p2
Internal partitions: system 390M, user data auto, recovery 8M, rest cLK default.
TWRP v2.3.3.0rev7 was the last extended recovery that worked perfectly for me.
Thanks kokotas. =)
Sent with love from me to you via HTC HD2 with Tapatalk 2
Click to expand...
Click to collapse
Did you try to run "Check SD Card" from "Advanced" menu?
Re: [DEV][27/Jan/2013]Extended TWRP|v2.4.0.0.r2
Dark_Avenger said:
Did you try to run "Check SD Card" from "Advanced" menu?
Click to expand...
Click to collapse
Yeah that works fine.
The recovery doesn't seem to function properly with DataOnEXT enabled.
In normal mode, all seems OK.
Log:
http://ompldr.org/vaDlubQ
Sent with love from me to you via HTC HD2 with Tapatalk 2
Re: [DEV][27/Jan/2013]Extended TWRP|v2.4.0.0.r2
Did you set the path properly in DataOnExt page?
Sent from my HTC HD2 using Tapatalk 2
sunitknandi said:
Yeah that works fine.
The recovery doesn't seem to function properly with DataOnEXT enabled.
In normal mode, all seems OK.
Log:
http://ompldr.org/vaDlubQ
Sent with love from me to you via HTC HD2 with Tapatalk 2
Click to expand...
Click to collapse
same here.
sd-ext is not getting mounted if DataOnEXT option enabled.
mounting via shell workes
if DataOnEXT option disabled sd-ext gets mounted vie GUI
Hi guys,
I don't currently use a Rom with the DataOnExt feature, so I can't really test this.
I'll try one tomorrow in order to be able to see what's the problem.
[EDIT]I found a nasty loop in Mount() function which I removed in r4. Try to see if this one solves this problem.[/EDIT]
Also I'd suggest that you either manually delete the /sdcard/TWRP/.twrps file or select to "Restore Defaults" after updating TWRP.
I've seen some really strange issues (like 'buttons disappearing') if I don't remove the previous settings file.
At last, I have ported the latest commits from official TWRP and fixed a couple of things in the r2.
But I didn't check out the problem you reported. Nevertheless I will upload the compiled files to keep things moving...
Regards!
PS:@Dark_Avenger
Just a suggestion: Keep using the 5th post for any updates of your theme so that it will be found easier. I already linked that post in the 3rd one.
kokotas said:
Hi guys,
I don't currently use a Rom with the DataOnExt feature, so I can't really test this.
I'll try one tomorrow in order to be able to see what's the problem.
Also I'd suggest that you either manually delete the /sdcard/TWRP/.twrps file or select to "Restore Defaults" after updating TWRP.
I've seen some really strange issues (like 'buttons disappearing') if I don't remove the previous settings file.
At last, I have ported the latest commits from official TWRP and fixed a couple of things in the r2.
But I didn't check out the problem you reported. Nevertheless I will upload the compiled files to keep things moving...
Regards!
Click to expand...
Click to collapse
FYI
deleting settings file did not help
issue still present in .rev3
kokotas said:
Hi guys,
I don't currently use a Rom with the DataOnExt feature, so I can't really test this.
I'll try one tomorrow in order to be able to see what's the problem.
[EDIT]I found a nasty loop in Mount() function which I removed in r4. Try to see if this one solves this problem.[/EDIT]
Also I'd suggest that you either manually delete the /sdcard/TWRP/.twrps file or select to "Restore Defaults" after updating TWRP.
I've seen some really strange issues (like 'buttons disappearing') if I don't remove the previous settings file.
At last, I have ported the latest commits from official TWRP and fixed a couple of things in the r2.
But I didn't check out the problem you reported. Nevertheless I will upload the compiled files to keep things moving...
Regards!
PS:@Dark_Avenger
Just a suggestion: Keep using the 5th post for any updates of your theme so that it will be found easier. I already linked that post in the 3rd one.
Click to expand...
Click to collapse
kokotas,
thanks for suggestion. I will use the 5th post to keep the Holo Dark theme in sync with the current extended version.
Without having a DataOnExt rom, I think that the problem with mounting the "sd-ext" is still there. You could reproduce it without a DataOnExt rom. Check the "DataOnExt" checkbox in "Settings" and try to mount the "sd-ext" from "Mount" page. The checkbox is selected for a second and then immediately deselected.
[EDIT]Deleting the .twrp settings file fixed it.[/EDIT]
Best
Dark_Avenger said:
kokotas,
thanks for suggestion. I will use the 5th post to keep the Holo Dark theme in sync with the current extended version.
Without having a DataOnExt rom, I think that the problem with mounting the "sd-ext" is still there. You could reproduce it without a DataOnExt rom. Check the "DataOnExt" checkbox in "Settings" and try to mount the "sd-ext" from "Mount" page. The checkbox is selected for a second and then immediately deselected.
Best
Click to expand...
Click to collapse
for me sd-ext mounting issue is fixed in .rev4
ratelutz said:
for me sd-ext mounting issue is fixed in .rev4
Click to expand...
Click to collapse
Yes... I can't reproduce it too after deleting the settings file ".twrp".
Re: [DEV][29/Jan/2013]Extended TWRP|v2.4.0.0.r4
kokotas said:
HD2_Extended_TWRP_2.4.0.0_r4 @ 2013.01.29
Click to expand...
Click to collapse
Looks like I am getting to the party a little late, sorry. Will be catching up soon as time permits.
---
If at first you don't succeed, skydiving is probably not for you... (via Tapatalk)
Re: [DEV][29/Jan/2013]Extended TWRP|v2.4.0.0.r4
kokotas said:
HD2_Extended_TWRP_2.4.0.0_r4 @ 2013.01.29
Click to expand...
Click to collapse
It certainly is better and probably functional now! You know, I used to have 'fun' with circular links and here you go introducing circular mounts!
Okay, let's see. I had some odd things happen after I flashed r4. I did delete the structure and started clean.
Sd-ext was found immediately. However, the xml path was not. I tried to use file explorer to look at the partition but it came up blank.
I tried to calculate partition sizes and it sat there for a long time before returning to the twrp splash screen and restarting. No boot - never saw Magldr.
I loaded Aroma fm which worked fine.
Back to twrp and checked the card. All went fine.
Not sure what else I may have touched but all of the sudden the correct path was populated and verified.
Not enough time to do a full backup but it was very close.
Should you want the log it is on dev-host: recovery.log - 230.13 KB <= Deleted
---
If at first you don't succeed, skydiving is probably not for you... (via Tapatalk)
Related
Development continues here: http://forum.xda-developers.com/showthread.php?t=881837
Universal lagfix kernel project.
This project is aimed at multiple audiences.
If you think you're an end user read on.
For lagfix and kernel developers check the second post.
Download, changelog, bugs and other links can be found at the third post.
Credits
ChainFire for the original cf-root initramfs
hardcore for the speedup hacks
nikademus for the compiled jfs utils
neldar for BackLightNotification
newmail for some kernel modules
RyanZA for OCLF and for being helpful
supercurio for Voodoo
ykk_five for being helpful (and for the memory tweaks)
z4ziggy for z4mod
and for everyone else I might have missed. (like myself - I'm an egoist you know... and for all the people that helped the guys I credited above. And for the people who helped the guys that helped the guys credited above. And for XDA of course.)
If you only care about points
OhmygodIcanget2kpointsatquadranttoobadI'vealreadysoldSGSbecauseitonlyhas300MBraminsteadof512asadvertisedandboughtadesirebecauseilikehowitcrapsatmultitouch.
For the rest of the people
What is this about?
This project has multiple aims:
A JPM based kernel with ext4, jfs, tun and BLN support
An init script which supports multiple lagfix schemes
Init.d support (without early script support)
A modified ClockWorkMod that
Has better support for some features of the SGS-I9000
Includes support for rooting the device
Includes support for switching the lagfix schemes
Has some tweaking options
Various additions that might help the other lagfix/kernel developers
How does this work?
Simply flash the kernel to any JPM/JP6 based, unlagfixed ROM. By default it won't apply any lagfix scheme, so you might use it as a simple ROM, with built in ClockworkMod + rooting support. If you have a complete ROM package (with dbdata.rfs and an older csc file (it won't work with some of the newer csc files) ) you can also flash it with the other parts, just replace the zImage in the PDA.tar with the one supplied. The ROM was tested with the original JP6 and JPM ROMs, and with my Multinational 3.0 ROM.
How can I use the extra features?
Reboot your phone to recovery mode. Under "Advanced ULK", there are some new options:
Reboot to download: switches to download mode
Run 2e recovery: Switches to 2e recovery
Install superuser: installs busybox and superuser to the phone
Lagfix options: switch between various lagfix schemes
Tweak options: switch between various startup tweaks
BLN options: Turns BackLightNotification on or off
Reset permissions: Resets permissions to the same state as init does
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 and cache), whether you want to use an extra loop device or not, and whether you want to bind some directories from /data to /dbdata.
There are also 8 included pre-defined schemes:
OCLF: /data stays at rfs, but has an ext2 loop device on top of it
Voodoo: /data is ext4, all others are kept at rfs
JFS Voodoo: /data is jfs, all others are still rfs
No-RFS Standard: /data is rfs+ext2, all other partitions are ext4
No-RFS Advanced: all partitions are ext4
No-RFS Advanced JFS: all partitions are jfs
No-RFS Overkill: turns on all options: everything is ext4+ext2 and /data/data is bound to /dbdata
No-RFS Overkill JFS: turns on all options: everything is jfs+ext2 and /data/data is bound to /dbdata
(If using the overkill scheme using the bind option is dangerous if using too much apps, so you should disable it in the advanced menu.)
Although I used the names OCLF and Voodoo, the ROM is not compatible with any of them, it's just a naming convention I used. Hope RyanZA and supercurio won't mind
Which one should I use?
You decide. OCLF or Voodoo might seem simple but they are actually working great (but for those you can actually use the originals, they are probably much more stable), while NO-RFS Overkill might seem cool, it is clearly an overkill.
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.
Is this ROM safe
alpha 0.2 means no. Switching between lagfix schemes might break, and data loss (mostly database corruption) can happen if you're using a lot of loop devices. And this kernel isn't thorougly tested anyway.
How to switch to another kernel/ROM
After disabling the lagfix everything should be fine (except for the possible data corruption). 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. I'll try to collect them and answers to them at post #3
Internal workings.
In this post I'll try to describe how this works, and how it might be useful for other people.
The Kernel uses both the pre-init trick and the bootlogos trick to load up, and do it's stuff. In the pre-init phase it does the following:
initializes the devices
checks the actual state of the partitions, and decides which lagfix scheme is active
checks the config (resides in /system/etc/lagfix.conf), and if they differ runs the converter application
if they don't differ then it starts to mount the devices, and let's init run.
if during the mounting a fatal error occurs, it prints the log, waits for a couple of seconds and reboots the device.
It does the filesystem checks by mounting and checking whether mounting succeded or not. To defend against samsung's init's reformatting, it simply removes the fat.format command.
In the post-init phase it removes some files (mainly the symlinks to busybox, so they won't interfere with the busybox installed on the system). It also reinstalls fat.format, because it might be needed later.
The lagfixer is built inside clockworkmod, which has the following advantages:
Can use nandroid backup
Can use the framebuffer to show the progress (this makes it much easier to debug problems)
Besides the lagfixer there is also a "graphsh" application, which will run a specified command and prints its output to the framebuffer (the reasons for this are the same: it's much easier to debug this way than to check a log file copied to the sdcard). If a fatal error occurs this command is run so the end-user can see some logs. (all of this is still pre-init). The only problem with using the framebuffer is that core android won't boot up properly if the framebuffer was initialized beforehand (it switches to QVGA with overlapped screens... it's actually quite fun to try using android that way). That's why I always reboot after using either 'graphsh' or 'lagfixer', except for recovery modes, because CWM is using the same framebuffer anyway.
The initramfs is "ro.debuggable=1" so if anything happens one can connect to the phone in adb root mode, to check for errors. Adb is enabled by default in both CWM and base android mode. I don't know the drawbacks of using debuggable=1.
CWM was modified in order to be able to handle the various lagfix schemes. If it tries to mount, unmount or format /data,/dbdata or /cache, it asks for the lagfixer to do the actual mount, unmount or format. Therefore if one saves or restores a backup it will always see and use the actual files, and not the loop device file.
There were some other minor modifications, like binding the home button too to the enter key, using /mnt/sdcard instead of /sdcard, and the ability to back up the efs partition too. (/efs won't be restored however).
There is also a small modification in how the updates work. If there is an update, the init will always run samsung's 2e recovery, if not it will use CWM (you can use CWM's menu to run an update using CWM if desired). This is to maximize compatibility with updates.
About the compiled files:
I had a hard time getting the binaries to work, even when compiling in static mode. All of the binaries are either compiled by me using bionic (AOSP), or used from other sources (but they seem to be using bionic too). The main advantage is that the recovery binary is actually only around 700k, but has a working busybox implementation, a working recovery and some other small stuff. The main problem is with the other binaries (mainly with e2fsprogs). If I could cut from the size the whole initramfs might fit into an official kernel, so it could be used by anyone.
Links
Da kernel 0.3 + BLN 2.2: http://forum.xda-developers.com/showpost.php?p=9157498&postcount=738
Da kernel 0.3: http://android.sztupy.hu/dl/Universal_lagfix_kernel_JPM_0.3.tar
Da kernel 0.2: http://android.sztupy.hu/dl/Universal_lagfix_kernel_JPM_0.2.tar
Da kernel 0.1: http://android.sztupy.hu/dl/Universal_lagfix_kernel_JPM_0.1.tar
Source of the modified CWM: http://github.com/sztupy/android_bootable_recovery
Source of vendor/samsung/galaxys: http://github.com/sztupy/android_vendor_samsung_galaxys
Kernel sources I'm using: http://github.com/sztupy/universal_lagfix_kernel
Bionic port of jfsutils: http://github.com/sztupy/android_external_jfsutils
The contents of the initramfs: http://github.com/sztupy/universal_lagfix_kernel_initramfs
Changelog
Version 0.3
- before the lagfix gets applied there are now multiple options to chose from:
-- backup+restore (the original way)
-- backup, but don't restore (this eventualy results in a factory reset)
-- no backup (this also results in a factory reset)
-- go to recovery mode (to debug)
-- erase config file (to get back to the old options)
- the screen glitch in the first screen is now gone (because the kernel got smaller)
- jfsutils are ported to bionic (takes less space)
- there is a new option that will do the same restore permissions run, as the init script does
- I also added a few fixes to the CWM fix_permissions script, although I don't tested them yet (so it might brick the phone)
- Added two more rooting option:
-- the old one simply copyes busybox, superuser and su to the phone and adds symlinks to busybox
-- the new ones will also remove some old toolbox commands, so if you use the shell a lot, they won't interfere. The first mode only removes the base utils, like ls,mkdir,rm or ln
-- the second mode removes every toolbox command that has an equivalent busybox command (like mount, lsmod, rmmod, etc.)
- Adeed an option to get back to 2e recovery from CWM
Remarks
It seems that formatting dbdata as rfs only works, if you use the 512 PIT file (more exacty it only works if you have used the 512 PIT file the last time you've ticked re-partition in odin). This is probably due to the fact thet the 512 and 803 pit files reserve different space for the dbdata and for the system partition (the 803 pit file reserves 40 units less for the dbdata than the 512 pit file)
Version 0.2
- efs is not backed up automatically during lagfixing (but it's still backed up during ordinary backups)
- added jfs support and some more lagfix schemes using jfs
- added backlightnotification support, with the option to turn it on and off
- added startup script tweaks support, with options to turn them on and off
- removed ext2 support for the base mounts (might be put back into later)
- bind now only binds /data/data (should use less space)
- some minor bugfixes relating
Remarks
- If Updating from 0.1 to 0.2: If binds were turned on you have to turn them off before updating. After the update has finished you can turn them back on if desired.
Known bugs
After the lagfix conversion is done the phone reboots and the lagfix conversion starts over again
This means that the conversion took place, but the result is not the same as was desired. You should reboot into recovery mode and remove the config file.
After rebooting I have a lot of FC's - After switching lagfix schemes I have a lot of FC's
This is probably because of a database corruption. Try loading an earllier backup.
Can't download anything from market
Some configurations might have this problem, I'm still trying to find out why this happens.
Can't download some apps, like angry birds from the market
Retry, it should work after a while. If it still fails remove the external sd.
Shutdown fails on some configurations
Until I find a way to hook onto the shutdown script this might happen on more complex configurations (like the NO-RFS overkill)
Can't get back to rfs on /dbdata
Reverting the lagfix on /dbdata only works if you used the 512 pit file the last time you checked re-partition in odin.
I for one am excited
Dan
Can't wait to see this.
I am waiting too ++++
Lol 100% teasing ^^
gingerbread?
shahadat said:
gingerbread?
Click to expand...
Click to collapse
would be a bit early
Fantastic
Testing now on a very stripped JP6...
very interresting i think i will give it a try hehehe
any feedback?
Would it be unsavory to say that I got a little motion in my pants after reading that first post?
Nah, I think we all did
Sounds great! And I'll wait for a few more version points on that alpha before I try it... but I'm tempted!
wonderful,i'll try it
Sztupy is this kernel and method usable with your multilingual rom v3.0?
Thanks
kurudisease said:
Sztupy is this kernel and method usable with your multilingual rom v3.0?
Thanks
Click to expand...
Click to collapse
check first post. Tested with JPM, JP6 and Multinational 3.0
Test drive
I just used it, I had no issue. Everything worked fine and there is no lag at all, still too soon to say it's faster than voodoo though(which I was very happy with). All data is still there and no problem! Im using JP6 with NO-RFS Extended. Quadrant score is ~1900 for anyone that want to know .
looks great! gonna try this
ist it possible to add in that also??
Startup script speed tweaks
http://forum.xda-developers.com/showthread.php?t=813309
I applied the no-rfs advanced fix and everything worked fine. No issues so far.
Thanks!
{
"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"
}
V4.31.44.12
v4.32.44.12 applied with theme from he_stheone64.
Important note:
I create the Desire Series together with freak, and also got a lot of help from many technical experts, so, please thank them as well if you like the build.
This thread is for discussing the SD builds only.
All the releases, Please check: http://forum.xda-developers.com/showthread.php?t=962600.
Please discuss the SD builds at: http://forum.xda-developers.com/showthread.php?p=9979611#post9979611
Before flash or install new builds:
1. DON'T expect it will work out of box.
2. DON'T expect it will be as light and fast as Gingerbread.
3. DON'T expect that some legacy problem will disappear
4. Reboot your phone at lease twice after flashing or installing, after 1st boot into setting screen, long press the right button to recall the boot menu, reboot. Can not use /Update_DL method to install app before 3rd reboot.
5. For this version, due to the base has been changed throughly, can not use previous data.img or ext4, remove existing data.img and set data_img=1 to let system generate one for you, or set format_ext4=1 to format your ext4 if you are using ext4
6. DON'T set any config for 1st installation except data_img=1(for data.img) or format_ext4=1(for ext4 user). if your have tmous phone, no need the config.txt.
7. For SD or magldr, if 1st installation failed, must delete the system.ext2 file under /Desire_DL to let system convert it again.
8. Use Windows notepad create a file named config.txt, save it under /Desire_DL, only need to put the necessary config inside it, say:
data_img=1.
Important Release Note
This build is another endeavor by freak and me to improve the performance of our build, now, besides our existing optimization methods: squashfs, ext4, etc, this build has been added in the following features to improve it performance furthermore:
1. Re-Engineering Sense:
All the apps and framework were re-compiled and reduced the size to get the lowest RAM consuming and Highest performance.
2. Merged DesireZ and DesireHD into one.
Merged the advantage features from both DesireZ and DesireHD into one build.
3. RAMfs
by default, one 16M RAMfs will be created for app and market cache.
once set ram_data=1, additional 1 RAMfs will be created for most accessed dalvik cache.
4. Re-write the SuperInit
fixed a lot of bugs inside and optimize it again, once set ram_data=1, the boot time should be within 1min, in next version, the boot time will be reduced again.
5. Added a lot of usable functions into SuperInit
- extend the backup/restore to be able to backup &restore to different build.s
- added more repair_mode, to be able to repair the nand system and reset the system.
6. Use own kernel Source: http://www.linux4freak.com/gitweb
- freak kernel v1.2 to perfect fit our builds.
--hence, 2 parameters were added to best control the kernel
---vdd_mode= xxx //for under/over volting cpu, [-150,-125,-100,-75,-50,-25,+25,+50]
---sched_mode= xxx // "cfq" or "bfq"
I dare to say, the performance of this build is unbeatable.
New Features for SuperInit v4.4
-- Buildin with IMG/EXT4/RAM support
--- by default will create a 16M RAMfs and use it as app_cache and cache.
--- once set the ram_data=1, will move the dalvik-cache of framwork into RAM
--- to roll back to normal status, use the ram_data=11
-- Optimize the nand_data, which will also be able to move the dalvik-cache of framwork into Nand.
-- add new backup_img=2 to back apps from data, which is used for changing the build, the backup_img=1 will back up the whole data, once restore to a new base, will incur the UID inconsistent issue. should use restore_img=2 to restore.
-- add more function for repair_mode
-- repair_mode=1 will rescue the data partition.
-- repair_mode=2 can use the MAGLDR load system to repair the Nand system and mount the Nand system to /mnt/rescue
-- repair_mode=3 will reset the system, all the modified app, framework, lib, fonts that caused the issue will be removed, system will be reset to the origin without losing data and settings.
-- Auto detect the phone modal(EU or TMOUS)
--- for EU modal, will auto enable the data.img if the 2nd partition can not be found.
--- for TMOUS, if doesn't have 2nd partition and set the data_img=1, will auto bypass all the relative code to reduce the boot time.
-- Auto detect the boot mode and set the best config (SD/MAGLDR/NAND)
-- Auto partitioning the SDCard if set the format_ext4=9
DOWNLOAD
DL Desire v4.31.44.12
Light themed with power notification and battery percentage.
DL Desire v4.32.44.12
Themed with he_stheone64.
How to ask for help:
1. First, make sure you ask at the proper place, this thread is only for ask the question related to the NAND, please ask questions related to SD or MAGLDR at http://forum.xda-developers.com/showthread.php?t=881937
2. Please indicate the following information when asking for help:
a. your phone modal: EU or TMOUS modal.
b. your loading mode: NAND, SD or MAGLDR
c. Please post the content of init.log(this file is on the root of your sdcard).
3. Please be patient and polite.
4. We(myself and freak) will only answer question that follows the above rules, thanks!!!
Naming convention
1. the 1st digit is for the build base, say DesireZ v4.xxx, is for the v4.0 base which based on the HTC RUU 1.85.
2. the 2nd field is for the subversion, normally, x.0 means the first relase which should based on a totally new base, and from x.0 till x.3, there will be a lot fix and testing, if you want a stable version, DON'T use it, and the build will be stabilized after x.4.
3. the 3rd field is for the init version, currently, our init is at v42, which is also not a stable version.
4. the 4th field will be used for the kernel, currently, freak is working on it, and will have the 1st kernel soon.
Bugfix & Enhancement
Bugfix & Enhancement (7 Mar 2011)
PLEASE don't PM me asking for help, you can always post in my SD or nand thread and there are a lot of people willing to help you more promptly.
I can't reply so many PMs everyday, sorry !
- Upgrade to v4.32.45.13 and v4.31.45.13
changelog:
--- bugfixes initrd
--- bugfixes init, removed some debug info
--- modified vdd_mode: now, if the value for undervolting is "more" than -50, only frequency below 576000 are reduced by this value, others only -50.
--- new kernel v1.3 (only change is aufs support inside kernel, this is for testing Jim's Squashfs Cache idea late.)
--- mobile/wifi data.
- - all the stock framework-res.apk:1.72, 1.83, 1.84, 1.85.
- How to change wifi mac address by Terabite7
- Install EVO Keyboard from ehsan76
- More kernel update package
- full Arabic support by jaguaralani and
this
- Optional update for full Arabic support View attachment update.newfeature.Arabic.zip (for both SD&Nand version)
Cautioin: you will lost the boot animation after this update.
- Compulsory update to v2.3 for v2.2 to extend the config.txt and enable Force using the ext4.
View attachment back.update.ext4.1501201103.zip (for both Nand version only)
you need to extract the DLZUPDATE to the root your of SDCARD, and have attached the .data folder with a pre-made config.txt. the data_img and data_ext can not be activated(set to 1) at the same time.
Reboot your mobile twice to activate the data2ext4, after that, you can put your app under /DLZUPDATE/AndroidApps/, to automatically install the app into ext4.
Q&A
1. why cannot I get as high score as freak on v3.3
PLEASE read here
2. about ext2/ext3/ext4: (ownhere)
I will provide the feature for format the partition2 to ext4 with block size of 4096 in next update.
3. what's the recommended config for data to sd(data.img)
A:
4. what's the recommended config for data to ext4.
A.
Note1. for 1st installation or if encounter ext4 performance issue, please set the format_ext4=1, it will take some time to format the 2nd partition, after booting into system, please manually change the format_ext4 to 0, otherwise, system will format the ext4 every time when reboot. After re-formatting , lot problems related to ext4 will be eliminated.
Note2. the "nand_data" is for making use of the nand data partition, if your SD card is fast enough, no need to use it. for 1st installation, it is always necessary to set it to 0, after that, you can try to set it to 1 to check. (nand data partition will be mounted to /system/data_internal)
Note3. once set the sd_boost to 1, for ext4, it will be mounted to loop driver without journal, should improve some performance, but may not so stable, you can try.
5. How to enable ClockworkMod .
Thanks nightcraw, please check.
6. Can you make RAM, DHD or Android 2.3 builds .
NO.
1) I don't have time, making current builds perfect already occupied all my free time.
2) There are already enough choices, why bother.
3) My principle is : I will not touch it unless I can make it special, outstanding, and perfect.
7. Can you make a unsquashfs build .
Why?
1) squashfs can save a lot of space.
2) it can also improve the performance(read less from low speed sdcard and restore it using high speed CPU )
3) key system files are protected from being malicious modified.
4) you don't lose any flexibility of customize the system as much as you want, by just deleting the existing file and replace with you own file.
8. can I upgrade to v2.4 from v2.2 or v2.3 without losing my data.
upgrading from v2.2 to v2.3 is possible which I have provided the update package.
upgrading to v2.4 directly is no so straightforward, thus, suggest you flash the v2.4 instead, the data on ext4 should be kept, but it is always advised to format the ext4 using the format_ext4 parameter before installation, after that, you can put all your apps apk to the folder of /DLZUPDATE/AndroidApps, it will be automatically installed to the ext4 or data.img. Fast and clean.
How to install config the v3 based builds.
How to config SuperInit v4.4(advance user)
the config.txt is now under Desire_DL folder, Normall, no need to config it, system can auto-detect the status and set the config correctly.
You can use windows Notepad to create a text file and save it as config.txt to /Desire_DL, or just refer to this sample View attachment config.txt
The below config are for advanced user only.
For Nand:
=================
format_ext4=1 //will format the 2nd partition with ext4 (recommended for 1st install, if you have 2nd partition, it must be 1 for 1st time installation.)
format_ext4=9 //which will auto-partition your SDCard to 3 partitions, and auto-format to ext4.
// the 2nd partition is for data partition which size is according to the data_size, default is 512M.
//the 3rd partition is for system optimization, system will auto-create it.
swap_mode=1 //will create a vfat swap file to improve the system performance if don't have 3rd partition.
swap_mode=2 //will move the about 160M squashed.sqsh file from system to data partition to release the system space.
but you must manually delete the squashed.sqsh file under /system, and keep the swap_mode unchanged.
swap_mode=3 //will create some cache space in nand part, if encounter the slow response during market download and install, can choose this.
nand_data=1 // will make use of the nand parition to optimize the system performance.
For Nand&SD
=================
ram_data=1 //move the dalvik-cache of framwork into RAM, it can improve the system performance a lot
ram_data=11 //roll back to normal status
ram_data=0 //by default, system will create a 16M RAMfs to optimize the performance, can use this to disable it.
ram_size=xxx //by default, system will create a 16M RAMfs to optimize the performance, can use this to change the size.
sd_boost=1 //may improve the SD performnace for both data.img and 2nd partition, it is very much depend on the SD situation.
vdd_mode= xxx //for under/over volting cpu, [-150,-125,-100,-75,-50,-25,+25,+50]
sched_mode= xxx // "cfq" or "bfq"
Other config:
=================
data_size=xxx //when create data.img or 2nd partition, will use the size of xxxM.
gps_zone=xxx // your gps zone country code.
ppp_mode= 0 //will be RMNET mode, 1 for PPP. normally, no need to config it, system will auto set it.
backup_img=1 //will back the data part to backup.gz file under /Desire_DL
restore_img=1 //will restore the data part from backup.gz
backup_img=2 //will back the app from /data to backupapp.gz file under /Desire_DL
restore_img=2 //will restore the data part from backupapp.gz
This is used for restore the app to another build.
repair_mode=1 //will rescue the data partition without losing any app or settings.
repair_mode=2 //will use the MAGLDR load system and repair the Nand system, after that mount the Nand system to /mnt/rescue for further action.
repair_mode=3 //will reset the system, all the modified app in system, framework, lib, fonts that caused the issue will be removed, system will be reset to the origin status without losing data and settings.
How to play with V3.3 final.
there are a lot of possible combinations to play with this rom, most cool part is that you can boot it from Nand, Magldr or SD with the same data.img or ext4 partition, you cannot even differentiate where it is from after booting into the system.
for performance, there are also a lot of combinations to try, I have ever tested some as below, others, need somebody provide the figure.
0. Load from Nand:
1. Load from Nand, ext4: 1860
2. Load from Nand , ext4, with sd_boost: 1180
3. Load from Nand, data.img:
4. Load from Nand, data.img, with sd_boost:
5. Load from Nand with Squashed from data partition(swap_mode=2):
6. Load from Nand with 3rd swap partition:
7. Load from Nand with a VFAT swap file(swap_mode=1):
of course, 5,6,7 can also mix with ext4 or data.img and sd_boost.
8. Load from Magldr, ext4: 1960
9. Load from Magldr, data.image: 2100
10. Load from Magldr, datat.image, sd_boot: 1580
11. Load from SD, ext4:
12. Load from SD, ext4, sd_boost:
13. Load from SD, data.img:
14. Load from SD, data.img, sd_boost:
The sd_boost seems need to do some adjustment as I put all the focus on the normal configuration before.
please make it so u can use root uninstaller to remove system apps like u can with mdj cyanogen.
Thank you
this looks good...
upload it already dude
LOL
M..
Hi! Finally you are on Nand thread.
You are from the future time zone.....
Anyway. thanks for posting, will try after you have uploaded.
Wooo, can't wait to try.
if I want install MDJ's kernel? it's really?
botan1q said:
if I want install MDJ's kernel? it's really?
Click to expand...
Click to collapse
Yes, which version do you want? I current use the 10OC
the power consuming is little much, but very stable.
shree.cse said:
Hi! Finally you are on Nand thread.
Click to expand...
Click to collapse
the thread at SD part can not upload attachment. have to move home.
TMOUS Installation...
Welcome to the world of NAND
Please also suggest how to install it on TMOUS HD2 without using the SD Card at all.
Thanks in advance
Ehsan
Dandiest, Glad to see you on the NAND threads sorry for the how. I will request my thread me removed since you are over here now.
dandiest said:
Yes, which version do you want? I current use the 10OC
Click to expand...
Click to collapse
I want 10.4OC But it is impossible now
kendav911 said:
Dandiest, Glad to see you on the NAND threads sorry for the how. I will request my thread me removed since you are over here now.
Click to expand...
Click to collapse
thanks, maybe we can discuss if you can help me maintain all the threads
Will help as I can. I am in the US so maybe it can get coverage a little longer and keep you from having to stop your development to answer questions.
dandiest said:
thanks, maybe we can discuss if you can help me maintain all the threads
Click to expand...
Click to collapse
Hey all,
Wanted to post CM7 here for everyone to enjoy.
Neopeek has been working hard to get this build up and running, he's been doing great work!
Neopeek's Original Post - if you wish to see Neopeek's original post about the CM7 topic.
Also, since now I am using his new ClockWordMod method - CWM Recovery thread
As is stated in the title, this is mainly for devs/testers. Lots of things are broken, and there will be frequent updates.
There are two methods to using this build:
1) ClockWorkMod (requires 3 separate ext2 partitions)
2) Loop'd system.ext2 image (like XDAndroid) [In progress]
The benefit of #1 is a dedicated system/data partition, and *partial* USB mass storage support.
The benefit of #2 is, it's easier .
I still have to work to get #2 up, but I wanted to post #1 ASAP. Lots of work to flesh out the post to, be patient!
I've been holding off on releasing this CWM version of CM7, because I'm still having a lot of bugs with it. Still needs quite a bit of work, but it's getting late for me tonight - I am going to release it, let me know if you guys make improvements, I'd love to incorporate them!
Main issues seem to be related to my durn CDMA device. Need to break into some logs to see what's goin on, it may be a little while! I think GSM folk will be fine. Let me know!
Downloads
Download #1
How-to
Method #1 (ClockWorkMod)
****WARNING****
If you setup dedicated partitions using this method, normal XDAndroid builds will think that you want to use dedicated partitions. I had to modify the init to get it to work correctly (I basically broke the partition detection in the init). It's not pretty, but I don't know of a better way to resolve that issue - let me know what ideas you guys have!
Setup:
You will need to create three (3) ext2 partitions on your SD card. This is not extremely simple, but by no means impossible .
If you're using Windows, I like the Mini Partition Tool. If you're in Linux, I usually use gparted.
This takes a little bit of planning - but in total, I would say you need a minimum of 450mb of space for all three ext2 partitions. So work out how much free space is left (if you want a bigger data partiton, or system partition account for it!) and make that the first partition - FAT32. Make sure all the partitions are "primary", not "logical"! See the partition layout below:
1 - FAT32 Primary (remainder of card)
2 - ext2 Primary (at least 150mb, system partition)
3 - ext2 Primary (at least 250mb, data partition - I wouldn't go over 1gb here)
4 - ext2 Primary (at least 50mb, cache partition)
Don't worry about putting anything in these ext2 partitions, everything is populated by Android and CWM. The FAT32 partition is used to kick off Android, while system, data and cache are all ext2 partitions. Reason for this is, hopefully if things go haywire we can blast out cache, not data . Also, it should be easier to update using this method than previously.
Extract the file. Look at the folder it created (npkboot). Copy the entire npkboot folder to the root of your SD (for now this is required - the init assumes there's a /sdcard/npkboot/tmp folder). There will also be an update.zip, in this case update-cm-7.0.0-neopeek.zip. Put this at the root of your SD card (this makes finding it in the menu much easier!)
Copy the appropriate startup.txt from the STARTUPS folder.
Find haret.exe in th npkboot folder. Run it, and watch the boot process carefully! It will ask you to hold the vol down button to enter recovery, and you have 10 seconds to do so.
Assuming you manage to do this correctly (I had some trouble at first ) you should see an icon like a hat. Wait for the menu.
Buttons:
End key - back (back button seems to do this as well...)
Send key - enter
Vol up - up
Vol down - down (menu button seems to do this as well...)
If this is the first install, go to "install zip from sdcard". Then "choose zip from sdcard" This will install the system image to the system partition from the update.zip.
If you need to wipe the data partition, you can do that under "mounts and storage". You shouldn't need to do this unless you're going from gb -> froyo or visa-versa. Froyo -> froyo should 'just work', as always YMMV.
There are A LOT of options in replimenu. The only ones I have used are install, format /data, /system or /cache and Reboot. According to Neopeek, there are several things that should not be used:
Neopeek said:
* Don't use "factory wipe" in CWM (you have been warned )
* Don't use "format sdcard" unless you know what you do (you have been warned )
* Don't use "partition sdcard" unless you know what you do (you have been warned )
Click to expand...
Click to collapse
Once you've installed Android, go back to the main menu and "reboot system now" There are some bugs, for example "reboot recovery" and "power off" all just reboot the phone to WinMo.
Boot haret again, but this time don't hold the vol down to enter recovery - boot as normal!
#2: Much simpler method, similar to XDAndroid builds.
Extract the file to your desktop. Go into the CM7 folder, look for the STARTUPS folder - grab the appropriate startup.txt, move it to where haret.exe is.
Copy everything in the CM7 folder to the root of your SD card - if you want to run it from a folder, create a rel_path=CM7 statement in your startup.txt after the set cmdline (if you want a different folder, change the CM7.)
Grab the ts-calibration file attached to this post (for RHOD), or go to this post for a list of ts-calib's. You can also create your own on boot, but may have to revert to an older kernel to do so.
Run haret.exe!
****Not Working****
CDMA seems broken - still! I did some testing with hyc's RIL and it's still busted, so there's something in the system image messing with it - Airplane mode was checked, and I could not uncheck it.
In addition, phone.apk seems like a forceclosefest. Neopeek did point this out in his original thread...
Mobile data - broken (Fixed soon)
Wifi - broken (Fixed soon)
System needs optimization for RHOD - was originally build with DIAM in mind - so it's a little slow.
Failed wakes seem pretty bad - sometimes it is quite difficult to wake the phone.
Boot animation seems to be not present - I'm looking into fixing it, probably graphics libs if anything that's broke it.
Dev Content
This new method should be great for anyone who wants to make their own updates - you can easily peek into the system image and make changes at will, then just install the new system image! You can even rolll updates instead of an entire system image if you wish.
The script language in ClockWorkMod is called "Edify", see this thread to learn about the syntax. This is related to the META-INF folder you see in the update zip.
There's a few differences in the rootfs', the main being the init. There's also some additional files it looks like neopeek added for Recovery specifically.
This is amazing work. Props to all involved.
Does anyone have any feedback on this build?
arrrghhh said:
Long story short, you need a ext2 partition and a fat32 partition - ext2 needs to be between 400-600mb, fat32 can just take the remainder of the card's space.
Click to expand...
Click to collapse
Is there a reason for the 600mb upper limit? If I use 1 gb, will it cause problems or will it not use it and just waste card space?
PM message
Arrrgh,
Disregard the PM I sent you.
I read the instruction and like you said, its not simple. So I will wait until you upload the easy to run load.
Thanks
Ltilt2 said:
Arrrgh,
Disregard the PM I sent you.
I read the instruction and like you said, its not simple. So I will wait until you upload the easy to run load.
Thanks
Click to expand...
Click to collapse
Sorry, I need access to a Linux box to do the 'easy' build... I will when I get home tonight from work, promise .
vinceweis said:
Is there a reason for the 600mb upper limit? If I use 1 gb, will it cause problems or will it not use it and just waste card space?
Click to expand...
Click to collapse
You can make it as big as you want I guess... I'm not sure how neopeek sets up the data partition to be honest, I'd have to ask him.
Edit - in lieu of the post below, I adjusted the first post to say it needs to be at least 400mb .
vinceweis said:
Is there a reason for the 600mb upper limit? If I use 1 gb, will it cause problems or will it not use it and just waste card space?
Click to expand...
Click to collapse
I have 700 mb and is working well,you can use as much as you want
Ltilt2 said:
Arrrgh,
Disregard the PM I sent you.
I read the instruction and like you said, its not simple. So I will wait until you upload the easy to run load.
Thanks
Click to expand...
Click to collapse
Is easy just use mini tool partition wizard,delete the main partition on the sd-card
and do two,one fat32 primary and one ext2 primary,then extract the archive and put the proper startups in npkinstall and in root
from the phone run install.exe
and after the reboot use haret.exe
I wonder if CDMA data is working with this...that is my biggest issue with GB right now...
HELICOPTER88 said:
I have 700 mb and is working well,you can use as much as you want
Is easy just use mini tool partition wizard,delete the main partition on the sd-card
and do two,one fat32 primary and one ext2 primary,then extract the archive and put the proper startups in npkinstall and in root
from the phone run install.exe
and after the reboot use haret.exe
Click to expand...
Click to collapse
yeah easy for you to say, that sounds complicated.
I will wait for the other one.
Do you know the ETA?
i have
- downloaded the file cm7new.tar.gz
- made primary fat32 and ext2 partitions
- extracted the file cm7new.tar.gz to the root of the fat32 partition
- got a lot of linux folders
but i am missing
- npkinstall folder
- startup.txt
- install.exe
- haret.exe
- startup folder
Where are these files?
Tippfehler said:
i have
- downloaded the file cm7new.tar.gz
- made primary fat32 and ext2 partitions
- extracted the file cm7new.tar.gz to the root of the fat32 partition
- got a lot of linux folders
but i am missing
- npkinstall folder
- startup.txt
- install.exe
- haret.exe
- startup folder
Where are these files?
Click to expand...
Click to collapse
Still need to upload, sorry!
Tippfehler said:
i have
- downloaded the file cm7new.tar.gz
- made primary fat32 and ext2 partitions
- extracted the file cm7new.tar.gz to the root of the fat32 partition
- got a lot of linux folders
but i am missing
- npkinstall folder
- startup.txt
- install.exe
- haret.exe
- startup folder
Where are these files?
Click to expand...
Click to collapse
I was looking at that too when extracted the files and didn't see what you are also missing.
Sorry about the confusion guys, I probably shouldn't have put the download link up before I was done .
I just fixed it, so #1 is good to go! I'll get #2 up later, thanks.
Another noob question, but the rootfs, kernels, oc, etc from the xdandroid builds will work the same on these?
(...solved...)
it's necessary create a swap partition?
What works in this build?
fishingmedic said:
Another noob question, but the rootfs, kernels, oc, etc from the xdandroid builds will work the same on these?
Click to expand...
Click to collapse
The rootfs is more or less collapsed in these.
Kernels are straight from XDAndroid repo.
OC is the same, startup.txt is fairly similar .
Quincux said:
it's necessary create a swap partition?
What works in this build?
Click to expand...
Click to collapse
Swap is not necessary.
Most things that work in XDAndroid work in here. Lots of other things are broken here tho .
Okay, downloaded and installed without problems.
First impressions:
Absolutely great build in terms of response!
No delays in menus, etc.
Also, this looks like the first build that may have little or no clock delay, so no need for clocksync !!! (to be confirmed since I did not use it very long, die to issues below)
However...
1) No WIFI
2) No Mobile data (2G/3G)
3) camera not working (could be just blackstone)
- maybe other issues, decided to wait for more feedback before continuing, without market access there's little point...
Device: Blackstone
Kernel: extensive testing with provided one (1276), later switched to 1277, to fix audiostuttering, no wifi or mobile data in either...
As a reference, used many NeoPeek / XDAndroid builds, generally got WIFI/Mobile data working until now...
Love to hear if someone else (blackstone?) got WIFI/2G/3G working...
Oh, well, as I understood, this was an early "developer" release, still plenty of room for improvements!
Cheers,
Robbert
last updated: 2011-Oct-29 [DISCONTINUED]
ROM version described: 3.0.8
If you wish to use the data in this FAQ in any way, you are free to do so without any need for links\attribution, except for people mentioned in the FAQ itself - please mention them where applicable.
I'd like to thank Lee for the wonderful ROM, fred_be9300 for the initial FAQ, and anderl78 for... lots of help.
Also thanks to alpharev and others who are quoted or otherwise mentioned on this page.
Thread management
[DISCONTINUED]
======
1. What is the difference between A2SD+ and data++ versions of LeeDrOiD V3.x.x Bravo GB?
With Desire's stock ROM, little ROM is available for user apps as the \data partition is very small (147 MB).
With A2SD+ ROM, somewhat more is available, as dalvik cache and apps are moved to sd-ext. However, some data is still written to the \data partition, so no matter what, the "Internal memory" will decrease.
Data++ version gives you yet more internal memory for app installation than A2SD+ version, however, it is a little trickier to both flash and customize. As it does not move dalvik cache to SD, unlike A2SD+, dalvik cache still occupies a considerable amount of internal storage. This makes the system marginally quicker than A2SD+, at the expense of available internal memory and placing a cap on the total volume of installable apps (which is still considerably higher than in the A2SD+ version). Furthermore, it can be moved to sd-ext as well, freeing more memory still (see subsection "Things to know if using Data++" below, item 5).
To actually free more memory for user apps, data++ version moves a number of system files from \system partition to sd-ext. This in turn allows to redistribute the partitions of the phone memory:
- system partition is reduced to 90-100mb at the expense of files moved to sd-ext and\or deleted
- cache partition, originally 40 mb and empty most of the time, is reduced to 5mb
- data partition (the one shown as "internal memory" and available for your user apps\dalvik) is increased at the expense of the two mentioned above
This partitioning is determined by the hboot you use. So, in order to enjoy the benefits of data++, you will have to flash the required hboot first. There are currently several hboots that are compatible with LeeDroid Bravo GB. However, to obtain the maximum benefit you have to flash Oxygen hboot (revision 1), second best is Oxygen-r2. More details on flashing \ updating can be found in the respective section.
You can get an overview of different ROM variants looking at the picture Bravo ROM allocation.jpg by clicking the preview at the end of this post. The picture may be not very precise and perhaps even partially erroneous, but it will give you a graphical overview and it is correct in general.
Last point: data++ is NOT the same as Data2Ext. Simplified explanation: Data2Ext will increase the size of "internal memory" as percieved by your system to the size of your sd-ext (it may also usually require two ext partitions instead of one, etc, etc). Data++ will NOT increase your internal memory to the size of sd-ext; it will only free some NAND memory by moving some system files to sd-ext and re-allocating the freed space to \data by using oxygen hboot.
Things to know if using Data++:
1. As cache partition has been reduced to 5 mb in data++ version-compatible hboot:
- a ramdisk is used instead of it for caching downloads from the market. However, RAM is not used when not needed, so you should not worry about your RAM being squandered.
- to update the radio, you have to use fastboot ('fastboot flash radio radio.img'. Radio.img is to be extracted from the radio update.zip beforehand) or update radio using stock hboot prior to flashing modified hboot.
2. Since location of some system files has changed in data++ relative to stock ROM, flashing UOT kitchen mods and themes can be tricky. More on this below in the respective section.
3. Having sd-ext on sdcard may negatively affect the read\write performance of the fat32 partition (this one goes for A2SD+ as well, though).
4. There are two most suitable hboots for data++: oxygen r1 and oxygen r2. The difference between them is that r1 has a 90mb system partition while r2 has a 100mb one. As LeeDroid Bravo GB 3.0.7 has a system partition exceeding 90mb, you have two options:
- prudent option for people who have hands.sys and head.sys drivers installed on their system:
-- use oxygen r1, as it leaves more space in data partition hence more space for your apps
-- modify LeeDroid Bravo GB rom.zip in any of the below ways to reduce the size of \system folder:
--- open the rom.zip in either WinRAR, 7ZIP, Total Commander with an archive-reading plugin will also work, other methods have not been mentioned but might also work; do NOT unpack rom.zip, just open it
--- remove bootanimation (rom.zip\resource\customize\bootanimation.zip) and boot sound (should be somewhere near it) by pressing the del key inside the chosen app (WinRAR\7ZIP\TC)
--- and\or remove unnecessary stuff like wallpapers and jpegs and whatever you believe is ok from rom.zip\system\customize\resource
--- copy the modified rom.zip to sd card for flashing, keeping in mind you will have to turn off signature verification (as we've changed the rom.zip and the embedded signature is now no good) in the recovery prior to flashing (e.g in Amon-Ra it's Other\Toggle Signature Verification)
- strange option for people who are lazy and\or do not have hands.sys and head.sys drivers installed (what would they be doing flashing hboots and roms then is another question, particularly data++ roms):
-- use oxygen r2, as it has a 100mb system partition and no modification have to be made to rom.zip prior to flashing - but your data partition will be about 10mb smaller than with oxygen r1
5. Even if you install data++ version, which has dalvik in internal memory, you can move dalvik cache to sd-ext to free space for your apps at the cost of a small performance decrease. To learn more, see post by anderl78: http://forum.xda-developers.com/showpost.php?p=14297694&postcount=4751
6. If you want to go back from Data++ rom to a2sd+\stock rom, be it by flashing or restoring a nandroid, you will have to flash stock hboot first!
2. Requirments for flashing (i.e. before you flash, you need)
a. General requirements
- Rooted HTC Desire
- SD card partitioned into two partitions - FAT32 and EXT3 (EXT4 supported, haven't tried it but people confirm it works)
- hboot 0.93.x - some have reported successfully flashing with older hboots, but it usually took multiple attempts, so it's easier to S-OFF
- Desire should be fully charged, just in case
- It is always better to flash critical stuff using a notebook or UPS-connected PC for obvious reasons
To partition your card, you can use:
- your recovery
- ROM Manager app
- GPARTED (linux software for partitioning, also can be run on any PC using a boot-cd, site: http://gparted.sourceforge.net/livecd.php)
- minitool partition wizard (freeware windows partitioning program, site: http://www.partitionwizard.com/download.html)
- any other reasonably advanced partitioning program (such as Acronis Disk Director)
Keep in mind:
- both partitions should be primary (how to check if your partition is primary?)
- FAT32 should go first, EXT3\4 should go second (EXT4 claimed to be supported, not tested by author of this post)
- if partitioning via recovery\ROM manager, specify swap size as zero
- do not label the partitions
- reasonable size range for ext partition is 1-2gb
- if you are not experienced in partitioning, back up your sd card data (if you need it), for there are many ways to lose it when partitioning and only a few not to. You can just copy your sdcard data to a folder, then copy it back to fat32 partition if necessary.
- the last, but NOT the least: method of partitioning should be irrelevant, however, best results seem to be obtained by using GPARTED \ minitools partition wizard. Gparted is the surest way, but least convenient; minitool Partition Wizard is very easy to use and requires no reboots.
b. Requirements specific to Data++
- S-OFF
- Oxygen hboot downloaded and ready to flash
- Stock hboot in case you want to go back
Obtaining S-OFF is described here: http://alpharev.nl/ OR in detail http://forum.xda-developers.com/showthread.php?t=805811
Brief explanation (sapienti sat): download S-OFF CD http://alpharev.nl/alpharev.iso, burn it and reboot (or mount it as bootcd in a virtual machine and reboot), connect rooted HTC Desire, cross your fingers and follow instructions.
Flashing hboot is described here: http://alpharev.nl/ OR http://androidtricks.net/fastboot-custom-hboot-partition-table-htc-desire-52 OR http://forum.xda-developers.com/showpost.php?p=14259861&postcount=3683 OR read this post by anderl78 with detailed instructions of flashing it via fastboot.
Flashing hboot via PBIMG is in my opinion easier and is the only way I ever tried. Flashing via fastboot requires having ADB installed.
All necessary files can be found in the last section: "7. One-stop download reference".
3. Flashing guide
1. Make a Titanium backup of apps (optional but reasonable)
2. Make a Nandroid backup
3. Copy both backups (titanium and nandroid) to a PC for ultimate safety (optional but reasonable)
4. Have the following files on your SD card in the root folder:
- Lee's ROM (make sure to have modified the updater script if it's 3.0.8.2 Data++)
- Ext3 alignment patch
- [optional] radio if you update it from sd
- [optional] any other zips you may want to flash (kitchen mods, backlight mod)
- [optional] hboot files (stock and chosen oxygen) if you want to install Data++ using the PBIMG way
5. Flash recommended radio (32.56.00.32U_5.17.05.08), reboot to old rom to check in Settings\About phone\Software Information\Baseband version
6. Make sure you have an EXT3 partition as described in the Requirments section above (EXT4 claimed to be supported, not tested by author of this post)
7. [data++] Flash necessary oxygen hboot (r1 or r2) if you are flashing the data++ version
8. [optional but highly recommended] Perform a full wipe (can usually be omitted if updating from most prior sub-versions of this rom e.g. 3.0.x where x<8 but better to do this, you do have titanium backup anyhow). Still, you can always try flashing without wiping, and if it doesn't work or works but is buggy, you can reflash again with wiping.
9. [data++] Toggle signature verification to off if you are using oxygen-r1 hboot and have modified the rom.zip to reduce system partition
10. Flash rom.zip
11. Reboot and wait for the ROM to first-boot, which may take quite some time (up to 10-15-20 minutes is a safe bet; if you worry your battery will run low, nothing keeps you from connecting the charger)
12. If everything is OK, reboot back to recovery and flash optional mods if you have them (you can flash them right after flashing rom.zip prior to first-booting, but if the rom fails to boot it will be hard to determine the reason - maybe it's the rom, maybe it's the mod - so easier to flash after first-boot)
13. If you have problems flashing the rom \ first-booting, read the following section.
14. [optional] restore Titanium backup if you have one, but make sure you do not restore any red items. To totally make sure, you can choose to restore only user apps+data, and set up system settings by hand, if you like to be on the safe side.
Note: DO NOT flash EXT3 Alignment Patch as described on Lee's official page (step 3 of his flashing guide). With all due respect to Lee, flashing this patch has resulted in non-mountable sd-ext partition for many users. So do not flash it unless the rom won't start, as described in the following section.
The ext3 aligtnment patch has the following purpose, however, ROM works fine for virtually all who go without it and the opposite is not true. So the guidelines are:
- if it works without it, don't flash it;
- if it doesn't work without it, try flashing it
- if you you've flashed it first and the rom doesn't boot, use any partitioning software to delete the ext partition, then re-create it and flash without the alignment patch.
4. Troubleshooting ROM installation
Usually, failing to flash\boot the rom has the following causes:
1. Incorrect card partitioning - perhaps number one among other reasons.
To check for it, reboot to recovery (if you can't reboot by key combination, pull the battery). Try mounting sd-ext in recovery.
If it fails, this is indeed a problem.
Solutions:
- flash EXT3 Alignment Patch (http://leedroid.ftp.rshost.eu/Bravo_Addons/alignment-ext3.zip), then try reinstalling rom by repeating steps starting with step 10 of the above flashing guide.
- delete sd-ext partition in any partition manager such as Gparted \ minitool Partition Wizard and recreate it again, then try reinstalling rom by repeating steps starting with step 10 of the above flashing guide.
- if above fails, repartitioning the whole card (fat32 backup may be necessary if you have needed data on it), then try reinstalling rom by repeating steps starting with step 10 of the above flashing guide.
- if all above fails, ask the gurus such as anderl78 or mod-author, and don't forget to press the THANKS button once they have solved your problem
2. hboot - rom incompatibility, such as:
- flashing data++ rom on a device which is S-ON and\or has stock hboot (Solution: if so, S-OFF your device and flash correct hboot)
- flashing unmodified data++ rom with oxygen-r1 hboot (Solution: either modify rom or flash oxygen-r2 hboot)
- flashing a2sd+ rom on oxygen hboot (Solution: flash stock hboot)
- flashing rom on old hboot (<0.93): may take several tries, though I'd suggest S-OFFing as an easier alternative
3. Corrupt ROM file
- If flashing 3.0.8.2 Data++, modify the updater script as described here
- You may want to check MD5 signature for the rom file just in case
- If you have modified data++ rom to use oxygen-r1 hboot - make sure you did it without extracting stuff with consequent recompressing; make sure you haven't deleted anything not meant to be deleted
- If you tried integrating kitchen mods into rom.zip file - try flashing a vanilla rom, this way you'll determine the cause (maybe you modified rom.zip incorrectly, corrupting it)
4. Unrooted phone
Solution: Learn to RTFM and root your phone
You can read up here: http://forum.xda-developers.com/showthread.php?t=696189
5. Attempt to flash modified ROM without toggling signature verification to disabled
If you have modified your ROM, you have to toggle signature verification off; e.g in Amon-Ra it's in the menu Other\Toggle Signature Verification.
6. Other causes
If your problem does not fall under the above list, ask the gurus such as anderl78 or ROM-author in the MAIN THREAD, and don't forget to press the THANK button once they have solved your problem
5. Customizing guide
5.1. Kitchen customization - battery icon, etc.
To customize your phone by changing the appearance of top bar icons, notification panel, fonts, battery icon and the like you can use the UOT kitchen: http://uot.dakra.lt/kitchen/.
Just cook the file you need as described here http://forum.xda-developers.com/showthread.php?t=990829, then flash it from recovery.
Data++ customization
Now if you have installed data++ version, things may be somewhat complicated. This is due to the fact that in the data++ version, some system files are partially on sd-ext:
/system/app goes to /sd-ext/app_s
/system/framework goes to /sd-ext/framework_s
/system/media goes to /sd-ext/media_s
/system/fonts goes to /sd-ext/fonts_s
You can actually check it yourself by opening the rom.zip file.
As the files which are changed by the kitchen mod you have cooked are usually among the ones relocated, the mod has to be a little different from the standard.
There are several ways to do this:
1. When cooking the mod in the kitchen, set the "Kitchen\File Upload\Flashing for Data++ ROM option" to ON.
This worked for most users.
2. [OR] edit cooked file manually, replacing file paths as described below:
Open the theme's zip file (e.g. one from UOT) and edit \META-INF\com\google\android\updater-script file, changing paths of files that had been moved to sd-ext in the data++ rom. After that you can flash it from recovery as usual, having toggled signature verification to Disbled.
For instance, with the data++ version of 3.0.6 I used the following lines (could be different with 3.0.7 official data++, but enought to get the picture, and you can always figure out the paths and which of them to alter from rom.zip):
Code:
ui_print("Applying UOT framework");
run_program("/sbin/busybox", "mount", "/sd-ext");
package_extract_dir("framework", "/sd-ext/framework_s");
package_extract_dir("app", "/sd-ext/app_s");
run_program("/sbin/busybox", "umount", "/sd-ext");
whereas original was like this:
Code:
ui_print("Applying UOT framework");
run_program("/sbin/busybox", "mount", "/system");
package_extract_dir("framework", "/system/framework");
package_extract_dir("app", "/system/app");
run_program("/sbin/busybox", "umount", "/system");
So it's the "spot 10 differences" game. Just check the official data++ rom.zip for files moved to sd-ext, then check what files are changed in the theme\mod zip, and alter the update script accordingly. Remember not to extract files and recompress them, but rather to open the archive and edit the script from the archive.
3. [OR] integrate the cooked file into rom.zip. To do this:
1) Browse through your cooked mod and see what modded files are in there. Usually its SystemUI.apk and framework-res.apk.
2) Extract these files to any folder.
3) Now open you rom.zip using WinRAR, 7ZIP, Total Commander with an archive-browsing plugin or any other decent software.
4) Locate the files you found in (1) and replace them by dragging the files extracted in (2) over them. E.g.:
You have extracted from the kitchen mod.zip:
framework-res.apk from the app\ folder
SystemUI.apk from the framework\ folder
to some temporary folder on your pc.
In data++ rom.zip, you'll most likely find
framework-res.apk in rom.zip\sd-ext\framework_s\
SystemUI.apk in rom.zip\sd-ext\app_s\
So, for each instance, you drag the respective file from temporary folder to the archive, and confirm if the program you're using asks if you want to replace the files. In any case, ignore the META-INF\ folder.
The resulting modified rom.zip should be flashed with Signature Verification toggled to Disabled in recovery, as we have modified it.
Troubleshooting:
Check if you have selected the right source files in the kitchen. In the UOT kitchen, on the FILE UPLOAD tab, under the heading "Select your rom from kitchen's list, or upload your own files", make sure you use "Kitchen's list", and select "LeeDrOiD 3.0.7 A2SD, ROM" from the dropdown. Alternatively, you can upload the actual files from the rom.zip.
If it still isn't working, then, most likely, you have incorrectly followed the above guide.
With all due respect, go to the main thread and bug people there - they will be very amused by yet another repetition of the "how do I flash the UOT kitchen mod on data++" topic... but will help you anyhow, as they are indeed nearly saints.
5.2. Adding notification panel widgets
The question of how to add widgets into the notification panel seems to appear every now and then in the main thread. There are many ways to do that. However, not all of them are easy\are easily customizable as the way I am describing below.
I solved it for myself by using the free Widgetsoid app.
It allows to make any number of highly customizable widgets, and can also place any of them in the notification bar.
The way to setup is first:
1. Install widgetsoid
2. Run it from the apps menu for initial settings:
ADVANCED tab:
- Flash led setting is METHOD 2
- Select desirable Brightness levels if you're going to use it (suggest using Seekbar first to get the hang of which levels are good for you, then using custom levels to set them up)
- I'd suggest setting "Widget focusable" to OFF, haptic feedback to ON
- Service in backgroud ON
NOTIFICATION tab:
- Hide notification icon to ON
- Open popup to OFF
Other settings you can change to your taste.
Then, to create your widget:
- Create a widget on your desktop, i usually use Widgetsoid Switcher 4x1 widget
- On network, Screen, Sound, Other, Shortcut tabs -- select which widgets are needed
- by clicking on a specific widget item in the preview you can move it to any place you want
- Go to theme tab, set it up to look as you want
- go to advanced tab, suggest following settings:
-- Modifiable - YES, you can turn it off later after you're sure you got what you wanted
-- Modifiable icon - up to you, I set it to off. What it does is show a small icon in top right corener which you can click to bring up widget editing screen; it works the same way without the icon, so it looks cleaner. It affects only the widgets placed on desktop, it won't be visible\usable in the notification panel widget
-- Notification - ON if you want to see the widget in the notification bar - so you want it ON
-- Widget invisible - as you want. If you check it, widget won't take place on your desktop, it'll only be visible in Notifications panel. Can't undo that later, so decide on the spot. You can always make another widget, though, if you later want to have one on the desktop and had made the previous one invisible.
-- Click Apply tab
It will ask you if you want to edit global prefs - no need to do that, so answer NO. The widget should appear in notification panel.
Some notes things:
- depending on notification panel style (transparent\white\other) you may want to change the color of your widget's icons so they are clearly visible (Widgetsoid app\Notification tab\Choose icon color). In transparent panel of 3.0.6-r2 it doesn't seem to work; as I remember, it worked with a white panel.
- In some cases, you may get a popup with the widget after you tap a widget item in notification panel after initial setup. If that happens, got to widgetsoid app, go to Notification tab, check state of "Open Popup" checkbox. If ON, set to off. If OFF but you still get the popup, check it to ON, then set it back to OFF, this solves the issue. It appears, you'll have to do that each time you add a widget to notification panel.
- If you made your widget visible only in notification panel and want to edit it, you can go to Widgetsoid app, go to Widgets tab, select widget you want to edit, tap the pencil button, edit as needed, tap apply tab.
- If you choose the widget to be Invisible on your dektop when you set it up initially, there is no way to uncheck this option if later you change your mind and want to see it on you dektop as well as in the notification panel. The only way you can do that is by recreating the widget.
- You can put more than one widget panel in the notification panel.
- If you use task killers (why would you want to?), make sure widgetsoid service is on the exceptions list.
VOILA, LeeDroid GB3.x.x with a notification tab switches in an easily customizable way!
PS you can watch it, if I am not mistaken, starting with 14:00 of the official widgetsoid video guide at http://www.youtube.com/watch?v=6pyf7U1cByI
6. Troubleshooting other issues:
There's not much issues I know of with this rom, unlike the HD ports. They may be user-specific, but I'm listing them here just in case.
- Lockscreen not appearing on power-on, i.e. after on button is pressed, phone starts direct to desktop.
Problem surfaced after several months of use. Fixed by reboot.
- When I want to select which calendars to be synced, I can only select [x] of my [x+n] calendars.
Fixed by clearing all data in the Settings>Applications section from processes containing the word Calendar.
7. One-stop download reference:
ROM links
ROM itself: see middle of this post
EXT 3 Alignment patch
Recommended radio 32.56.00.32U_5.17.05.08, MD5 03cd7972412bec4b4ed6f2699e4c9af0
S-OFF links
Site: http://alpharev.nl/
Live-CD used to S-OFF, MD5 3ca4c4803fe1eb309c980420788ad3f
HBOOT links
Site: http://alpharev.nl/
Bravo oxygen r1 (with 90mb system partition, alpharev took it down after releasing r2 for some reason):
- fastboot flashing: link courtesy of anderl78, OR backup link to same file, MD5 0ac1bd252276a7e81c24d601569746e1 (if you use the second link and want to check MD5, unpack .img first, then check MD5)
- PB99IMG flashing, MD5 4f19784ae373fbfd8c2e5de6d32696a0
Bravo oxygen r2 (with 100mb system partition):
- fastboot flashing, MD5 532e39f7b0e8cf9aff07d4556fe6d841
- PB99IMG flashing
Stock hboot:
- fastboot flashing, MD5 7bd5234711364880de1fa982dcf3a2d6
- PB99IMG flashing
Mods and fixes
- All mods courtesy of anderl78, so if you like them, I'd suggest pushing a THANKS button on the respective post by anderl78
- Nandroid prior to flashing is a reasonable policy
- Some mods may require toggling signature verification to "disabled" prior to flashing
Hardkey backlight always off (good for those who like to read at night), backup link
Bluetooth autoconnect
No-sense patches for A2SD+ and Data++ versions: for LD3.0.7 and for LD3.0.8
Camera tweak (media_profiles updated, reducing jpeg compression)
Unlimited browser tabs tweak
3G\EDGE\MMS not working:
- reset your APN to default (goto Settings\Wireless and Networks\Mobile networks\Access Point Names\ press MENU key on your device, choose RESET TO DEFAULT)
- if unsuccessful, enter APN details manually (your operator should know) OR see this post for how-to on importing a large APN preset list
Black HTC Home widget (flip-clock+weather), works for 3.0.x and 2.5.0
Various performance improvements
Autobrightness tweak for 3.0.8
Juwe11's Ramscript for Leedroid
Leedroid 3.0.8.2 data++ updater-script fix
Database defrag mod (frees internal memory, speeds up operation a bit, slows down boot a bit)
Tools
[url="http://www.paehl.de/cms/fastmd5_deutsch]Software to check MD5[/url]
GPARTED - linux software for partitioning, also can be run on any PC using a boot-cd
- site: http://gparted.sourceforge.net/livecd.php
- how-to: http://www.youtube.com/watch?v=sVK-tJe8pXE
MiniTool Partition Wizard - freeware windows partitioning program, site: http://www.partitionwizard.com/download.html
DISCLAIMER: whatever you do, you do on your own initiative and the results of your actions are your responsibility.
Hello s300pmu1!
respect, very good FAQ-Thread!
oxygen_r1 hboot (bravo_alphaspl-oxygen.img) http://db.tt/eNlzMrS
md5: 0ac1bd252276a7e81c24d601569746e1
hi,
indeed very well done.
I would suggest that this thread url is pasted to the OP Lee's thread. would be easer for everyone's as an howTO
awesome thread .. resolves most of the issues that crop up related to data++
Thx a lot. Seems to be complete and clear !!!
hi,
Is there a easy way to check if my sd-ext3 is set as primary? Im using Win7 and i try booting into Gpart via a usb drive, but it doesnt seem to detect my sd.
My sd-ext3 have been partitioned using RA when i flashed LeeDroid 2.4.0.
kobezt08 said:
hi,
Is there a easy way to check if my sd-ext3 is set as primary? Im using Win7 and i try booting into Gpart via a usb drive, but it doesnt seem to detect my sd.
My sd-ext3 have been partitioned using RA when i flashed LeeDroid 2.4.0.
Click to expand...
Click to collapse
Firtsly, if you partitioned using ROM manager \ Recovery, your partitions should be primary, because the writers of that software are not saboteurs
So you need to check it only if you partitioned the disk yourself using partitioning software and are no longer sure if you did it right (one can always forget).
If you're using Windows, it's very easy:
If you don't have a card reader or do not want to open your desire to get the card out of it:
1. Connect phone to PC with USB and boot into recovery
2. Enter USB-MS mode and wait for the PC to see your flash card
If you have a card reader and don't mind opening it to get the card out:
1. Open Desire, remove card
2. Connect card reader to your PC, stick the card into it, wait for the PC to see it
THEN:
3. In windows, press WinKey+R to get the Run dialog
4. Type DISKPART, wait for a prompt to appear (it could take some time)
5. type LIST and hit ENTER
6. It will show you a bunch of disks that are on your system. You have to find in the list the one which is your flash card (by the size) and mark its number.
7. Type SELECT DISK <disk number here> and hit ENTER
8. Type LIST PARTITION and hit ENTER
9. It will show you partitions and their types
10. After you're done, just close the windows with the mouse
ALTERNATIVELY, for the GUI-minded:
3. In windows, press WinKey+R to get the Run dialog
4. Type dikmgmt.msc and hit ENTER
5. Wait for it to initialize, locate your flash card in the bottom half of the screen, using scroll bar if necessary
6. It should show two partitions, xx.xxGB FAT32 / Healthy (Primary Partition) and x.xxGB / Healthy (Primary Partition)
7. When done, close the window.
OR, if you have acronis Disk Director, you can:
3. Launch it
4. Find your flash card
5. In the top half, partition types are specified
6. In the bottom half, you can check the color of the partition against the legend (primary is yellow, at least in version 10)
s300pmu1 said:
Firtsly, if you partitioned using ROM manager \ Recovery, your partitions should be primary, because the writers of that software are not saboteurs
So you need to check it only if you partitioned the disk yourself using partitioning software and are no longer sure if you did it right (one can always forget).
If you're using Windows, it's very easy:
If you don't have a card reader or do not want to open your desire to get the card out of it:
1. Connect phone to PC with USB and boot into recovery
2. Enter USB-MS mode and wait for the PC to see your flash card
If you have a card reader and don't mind opening it to get the card out:
1. Open Desire, remove card
2. Connect card reader to your PC, stick the card into it, wait for the PC to see it
THEN:
3. In windows, press WinKey+R to get the Run dialog
4. Type DISKPART, wait for a prompt to appear (it could take some time)
5. type LIST and hit ENTER
6. It will show you a bunch of disks that are on your system. You have to find in the list the one which is your flash card (by the size) and mark its number.
7. Type SELECT DISK <disk number here> and hit ENTER
8. Type LIST PARTITION and hit ENTER
9. It will show you partitions and their types
10. After you're done, just close the windows with the mouse
ALTERNATIVELY, for the GUI-minded:
3. In windows, press WinKey+R to get the Run dialog
4. Type dikmgmt.msc and hit ENTER
5. Wait for it to initialize, locate your flash card in the bottom half of the screen, using scroll bar if necessary
6. It should show two partitions, xx.xxGB FAT32 / Healthy (Primary Partition) and x.xxGB / Healthy (Primary Partition)
7. When done, close the window.
OR, if you have acronis Disk Director, you can:
3. Launch it
4. Find your flash card
5. In the top half, partition types are specified
6. In the bottom half, you can check the color of the partition against the legend (primary is yellow, at least in version 10)
Click to expand...
Click to collapse
Thank you so much for the detailed stepped.
I tried using the the steps with DiskPart as well as Disk Mgmt. But I can only see one primary partition on my 8GB SD, that is the FAT32 Primary with around 6GB+ size. I could not see the ext partition which I have partitioned to be 1GB.
Does this mean my ext3 is not primary? or Win7 just cant detect ext3 since it suppose to be for Linux?
Does this mean my ext3 is not primary? or Win7 just cant detect ext3 since it suppose to be for Linux?
Click to expand...
Click to collapse
It means, most likely, that something is wrong.
Win7 can detect sd-ext, though it will not be able to work with it.
Still, it will display the ext partition in both diskpart and diskmgmt.msc, and also show if it is primary.
How did you connect the flash card to your PC?
If you just connect your booted Desire to PC in "Disk Drive" mode, it will never show the sd-ext partition. You have to do it as described, from recovery or by using a card reader.
If you still can not see the sd-ext partition (BTW, what size is your card?), try partitioning it using recommended software (you can start with minitools partition wizard as it is much easier than Gparted and yields the same results).
first, I'm sorry I can't post my question in the main thread (not enough
posts ).
Question :
i have Leedroid 3.0.7 A2SD+ installed, everything seems fine, but I can see my internal storage free space going down and down (now only 5 mb) and at the same time the SD card (A2SD ext3 partition) still has 284 Mb free.
Anyone knows where the problem could be ?
Anyone knows where the problem could be ?
Click to expand...
Click to collapse
Yup. See the first post of this thread:
However, some data is still written to the \data partition, so no matter what, the "Internal memory" will decrease.
Click to expand...
Click to collapse
To get more memory, you will have to use Data++ version.
Or somehow integrate data2ext which will give you even more space (which is, however, rather complicated, and I assume, less stable).
s300pmu1 said:
Yup. See the first post of this thread:
To get more memory, you will have to use Data++ version.
Or somehow integrate data2ext which will give you even more space (which is, however, rather complicated, and I assume, less stable).
Click to expand...
Click to collapse
Hey guys,
Everybody just keeps saying that, but there must be a limit to data accumulation, isn't?
Even with data++, if it is just normal to lose 5mb each day without new installs or updates, well...
I'd address this question to anderl78\lee.
They are better equipped to answer it ^)
Just don't forget that apps do store data (e.g. gmail stores incoming mails somewhere, and this somewhere is most likely the \data partition).
TomLeeDesire said:
Even with data++, if it is just normal to lose 5mb each day without new installs or updates, well...
Click to expand...
Click to collapse
What, you're losing 5 MB of internal memory EACH DAY? That's insane! I'm about to switch from A2SD to DATA++ because my internal memory is dangerously low but should I now?
I'd address this question to anderl78\lee.
They are better equipped to answer it ^)
Just don't forget that apps do store data (e.g. gmail stores incoming mails somewhere, and this somewhere is most likely the \data partition).
Click to expand...
Click to collapse
Hello! I looked into the Rom configuration but could not find a problem that would cause this space consumption. Apps are saved in sd-ext, app-data is saved in nand Memory (internal).
Dalvik-cache is on ext or internal, depends in the Rom, is ok too.
In data++ is a little error, app-private (buyed apps) is not on sd-ext, its completely on internal memory. To change this, flash my dalvik2nand.zip ;-) (see link in OP) - perhaps its that? But this is only in data++ and not in a2SD+ ROM... I don't think this is the reason...
I looked into the space available here on my phone for a few days now, and I have to say nearly no space is gone... 116mb free to 115mb free in 3 days... Absolutely ok what I think. (data++ with the above dalvik2nand "extension" )
I think, the described problem is related to some apps, which are storing a lot of data in internal memory. If somebody have this problem, I recommend to see into "manage applications" sorted by needed space, or use "diskusage" from market to look, what app(s) are causing this.
One other thing I have seen is Titanium backup. After a flash I restored my apps with tb as usual. I wondered why some apps last so long to restore and suddenly i got a low space warning message. Looked into the apps and see for example xda-app using 90MB for data! Wiped all, restored nothing with tb, installed all from market and the problem is gone...
I hope this helps somebody... ;-)
Sent from my HTC Desire using XDA App
Ghisy said:
What, you're losing 5 MB of internal memory EACH DAY? That's insane! I'm about to switch from A2SD to DATA++ because my internal memory is dangerously low but should I now?
Click to expand...
Click to collapse
See my post above, you could use data++ without fear! ;-)
Sent from my HTC Desire using XDA App
Ghisy said:
What, you're losing 5 MB of internal memory EACH DAY? That's insane! I'm about to switch from A2SD to DATA++ because my internal memory is dangerously low but should I now?
Click to expand...
Click to collapse
Hey don't panic.
I am a happy data++ user.
Those 5mb were just a way to speak about this subject coming back every time.
I just can't stop installing and uninstalling apps so I have no real number to give you.
I also use a cache cleaner that frees some internal every day.
I just thought there would be a max data an app can store that would avoid explosion...
Thanks for your replies guys. I went ahead and updated to DATA++. I've checked apps sizes in the "manage applications" menu and they don't seem out of the ordinary.
I guess that's what you get when you have 130+ apps installed!
anderl78 said:
See my post above, you could use data++ without fear! ;-)
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
It may be something wrong with the A2SD version.. When I was using that I was constantly losing memory, I switched to the data++ version and no longer have the problem.. the memory always stays the same (give or take a few mb for app caches etc..).
Something seems weird with the A2SD version for sure.. (well that's what I think anyway lol)
himeshladva said:
It may be something wrong with the A2SD version.. When I was using that I was constantly losing memory, I switched to the data++ version and no longer have the problem.. the memory always stays the same (give or take a few mb for app caches etc..).
Something seems weird with the A2SD version for sure.. (well that's what I think anyway lol)
Click to expand...
Click to collapse
I can't believe it, cause a2sd+ Rom and data ++ Rom are using the same a2sd-script, the difference is, in easy words, only that the dalvik-cache is not moved to sd-ext in data ++ Rom. But I'm not the Rom-cook, perhaps I'm totaly wrong... I have only looked a bit into scripts and a few other things perhaps related to this - I'm not a real expert in this... Let's see, if lee provide us with more infos and perhaps a solution in his next build!
Sent from my HTC Desire using XDA App
CYANOGEN MOD BETA 1 FEATURES
Phone
WiFi
GPS (first time slow, next time very fast)
Data connections (GPRS)
Sensors (all)
2D/3D
MP4/3GP movie play (camera hardware button doesn't work yet)
Camera in photo (up to 5MP) and movie recording mode (we are working on new driver)
Bluetooth
ADB/UMS
Autobrightness
it's already rooted
Note1: There is a new parameter to startup.txt (vmalloc=256M), so if You are installing it manually also read README.
Note2: To change clock color go to SpicaGen Mod settings in settings menu.
FROYO BETA 3 FEATURES
-Phone
-WiFi
-GPS (because of another way of loading phone is a bit slower now)
-Data connections (GPRS)
-Sensors (all)
-2D/3D
-MP4/3GP movie play (camera hardware button doesn't work yet)
-Camera in photo (up to 5MP) and movie recording mode (it's still not 480p, but works)
-Bluetooth
-ADB/UMS
-Autobrightness
-It's already rooted
Note1: There is a bug when calling via BT or speaker, when screen goes off, only way to turn it on is finish call.
FROYO BETA 2 FEATURES
- Android 2.2 Froyo compiled from sources with some O2 optimizatios
- Phone
- WiFi
- GPS
- Data connections (GPRS)
- Sensors (all)
- 2D/3D
- MP4/3GP movie play (camera hardware button doesn't work yet)
- Camera in photo (up to 5MP) and movie recording mode (it's still not 480p, but works)
- ADB/UMS
- it's already rooted
LATEST NEWS & DEVELOPMENT
30.11.2011: CyanogenMod beta 1, update 1. Headset detection (3,5mm jack) update + today's kernel update (incomming call screen appearing fix) in one package. Download here.
30.11.2011: Kernel update. Kernel update contains incomming call screen appearing fix. Now it's instant. Download here.
28.11.2011: CyanogenMod beta 1. Introducing CM beta 1 (based on SpicagenMod 4 from voku). It's very fast, has IMEI working on beta2 phone image, has JIT enabled, I/O speed is increased. For both Americas there is an update script in case of phone not working.
16.11.2011: Froyo beta3, update 1 fix. Update contains kernel which fixes App2SD problem. Download here.
07.11.2011: Froyo beta3, update 1. Update contains following: sensors lib fixes, charging battery fixes, compass calibration caused discharging even when connected to usb, memory bug fix, reserved memory change (GUI should be smoother now), WiFi should connect now faster. Remember to reboot after update, because modules changed. Download here.
18.10.2011: Froyo beta3. Introducing working Bluetooth, autobrightness, phone working for all (IMEI is ok now, signal is much better), boot logo, , some other fixes like: proximity bug when calling, WiFi should obtain DNS addresses and sleep well now, reserved memory for 3D is increased - it should not cause white squares - result is less memory for system, that's why additional swap partition is created and used. Download:
Automatic install package - full install package for external SD. Experimental (not tested, but should work) install for Internal Storage - before using read included README file and make backup. Automatic installer requires 1160MB of SD space.
Beta2 to beta3 update - update from official beta2 (SD card install only).
20.09.2011: Automatic installer is ready for download. Check main site. Quick howto is available inside archive. It assumes that Your My Storage wasn't touched (so it is mmcblk1p5). You have to use 2GB SD card or bigger. If You already have two partitions eg. from first beta installer (vfat and ext2/3/4), it should only format ext2/3/4 partition and install android. Otherwise it will try to shrink existing fat32 and create new one with ext4.
17.09.2011: Froyo beta2 is ready for download (please check project site for link)! It contains new kernel (2.6.32.9) and many bugs fixed (ie. You don't need call light anymore).
MANUALS & GUIDES (BETA 2)
Note1: Pink screen at boot
It's normal because of no logo compiled in. If it's too long (longer than 30s) tap the screen. If this not helps, You probably set wrong partition in startup.txt.
Note2: WiFi
- There is a bug with WiFi. If it's on and phone go sleep, after wake there is a chance it would not work again. Only fix is to reboot. We suggest to turn off WiFi before suspending phone.
- Sometimes phone cannot connect to router (it connects, but no DNS addresses). Workaround: in build.prop uncomment following entries:
Code:
#net.dns1=8.8.4.4
#net.dns2=8.8.8.8
to:
Code:
net.dns1=8.8.4.4
net.dns2=8.8.8.8
Note3: Black screen after call
There is a bug in a phone call. When call is finished, screen stays black. Workaround is to swipe through proximity sensor
Note4: Automatic installer
Requires:
- untouched My Storage with automatic installer content
- ext4.tar.gz from manual install package
- at least 2GB SD card (class 6 at least will be enough) with one FAT32 partition or with 2 partitions (FAT32 + ext2/3/4)
Note 5: Manual install
Example: if You have two partitions on SD card (first vfat, second ext4) You should set in startup.txt following: root=/dev/mmcblk0p2. Full file example for this (do not change anything other, only root device):
Code:
Set ramsize 180*1024*1024
Set mtype 1626
Set ramaddr 0x50000000
Set kernelcrc 1
Set CMDLINE "rootdelay=2 root=/dev/mmcblk0p2 init=/init console=ttySAC2,115200"
setbitp 0x7F008808 5 1
pfw 0x7f005800 4 0x3
pfw 0x7f005804 4 0x805
pfw 0x7f005808 4 0x7
pfw 0x7f00580c 4 0x0
pfw 0x7f005828 4 0x11
pfw 0x7f00582c 4 0x80
boot
Note 6: Internal Storage Installation
If You want install on My Storage (Internal Storage):
mmcblk1p5 - by default is My Storage partition (this partition is mounted by default by Android as /storage)
mmcblk1p6 - by default is hidden partition
You have to resize mmcblk1p5, then create mmcblk1p7 (this will be root device in startup.txt) and format it with ext4.
Just a question: install android needs a hardreset my current WM settings?
I asked that because I have a lot of configurations at now (SPB Mobile Shell, Pocket Breeze, Pocket Weather etc.) and I really don't want to lose them or need to do all again.
Thanks.
hiroshi.rio said:
Just a question: install android needs a hardreset my current WM settings?
I asked that because I have a lot of configurations at now (SPB Mobile Shell, Pocket Breeze, Pocket Weather etc.) and I really don't want to lose them or need to do all again.
Thanks.
Click to expand...
Click to collapse
no need to hard reset,android has nothinf to do with wm except running haret ,Theoretically
no need to hard reset,android has nothinf to do with wm except running haret ,Theoretically
Click to expand...
Click to collapse
Thanks for your answer.
I'm a little affraid because I read here (http://forum.xda-developers.com/showthread.php?t=1066313) that I need to create a partition at 'My Storage'. So I think this operation will automatically hardreset my device.
the installation is the same as the beta 1??
Is the Zimage missing???
not anymore. zimage is up.
i m sorry. Where can find the updates? 2011-09-17
no link
There is no link.
Where can we find the package?
Modaco thread.
http://www.modaco.com/topic/346446-froyo-beta-2-for-omnia-2/
Project Download Page
http://o2droid.phj.hu/index_en.php
lalinde89 said:
the installation is the same as the beta 1??
Click to expand...
Click to collapse
Currently you'll have to do it manually, with Ubuntu.
damn. when i tried to partition the 2GB My Storage into 1000mb FAT32 and remaining 959mb ext4 (in ubuntu), i got an error when applying in gparted.
And now, all 2GB appears unallocated, and ubuntu cant mount anything. So im stuck. Tried creating a partition under Disk Utility, but it just hangs and doesn't do anything. At the same time, using windows 7, im stuck with 1000mb of FAT32 and 959mb that appears unallocated. Cant do anything to extend or delete the partitions (using disk management). All options are greyed out.
So now winmo can only effectively recognise 1GB of My storage. I effectively reduced my storage in half.
Anyone know what to do?
l3ong91 said:
Currently you'll have to do it manually, with Ubuntu.
Click to expand...
Click to collapse
I have extracted the ext4.tar to my ext4 partition on omnia 2 (i8000 8gb) as i always do.
Copied the startup and zimage to my root and changed the startup to reflect my partition. This works perfectly for beta 1
But all i got with beta 2 was a pink screen, so i waited for 10 minutes and nothing...
So i downloaded the debug zimage to see what's going on.
I can see it's "jumping to kernel" and then a cursor is blinking for a few seconds and then the screen goes all black.
Any idea what's going wrong?
exactly the same problem than fran_nic....
i'll tell you if i find a solution....
vpnair said:
damn. when i tried to partition the 2GB My Storage into 1000mb FAT32 and remaining 959mb ext4 (in ubuntu), i got an error when applying in gparted.
And now, all 2GB appears unallocated, and ubuntu cant mount anything. So im stuck. Tried creating a partition under Disk Utility, but it just hangs and doesn't do anything. At the same time, using windows 7, im stuck with 1000mb of FAT32 and 959mb that appears unallocated. Cant do anything to extend or delete the partitions (using disk management). All options are greyed out.
So now winmo can only effectively recognise 1GB of My storage. I effectively reduced my storage in half.
Anyone know what to do?
Click to expand...
Click to collapse
If gparted is not working for you, then try to re-format or delete all the existing partition on your My Storage using Minitool PArtition Wizard (Do it on Windows instead of Ubuntu).
---------- Post added at 07:46 PM ---------- Previous post was at 07:43 PM ----------
fran_nic said:
I have extracted the ext4.tar to my ext4 partition on omnia 2 (i8000 8gb) as i always do.
Copied the startup and zimage to my root and changed the startup to reflect my partition. This works perfectly for beta 1
But all i got with beta 2 was a pink screen, so i waited for 10 minutes and nothing...
So i downloaded the debug zimage to see what's going on.
I can see it's "jumping to kernel" and then a cursor is blinking for a few seconds and then the screen goes all black.
Any idea what's going wrong?
Click to expand...
Click to collapse
Did you do the extracting in Ubuntu? And did you set the destination to the correct partition?
First boot it will took some times for the pink screen to disappear, for me it's around 1-2 minutes, before the shiny Android logo pops out.
ok i have found a solution.
re-format sd card with g-parted under ubuntu.
-unmount device
- completly erased partitions.
- create new partition in fat32 in primary mode 7go
- create new parttion in ext4 in extended mode 1go
- extract . tar files in ext partition.
my first install was a 2go ext4 parttion , it seems to be the pb, i've read somewhere that if ext 4 partitions are more than 1.5 go = troubles.
hope i have help you....
l3ong91 said:
If gparted is now working for you, then try to re-format or delete all the existing partition on your My Storage using Minitool PArtition Wizard (Do it on Windows instead of Ubuntu).
---------- Post added at 07:46 PM ---------- Previous post was at 07:43 PM ----------
Did you do the extracting in Ubuntu? And did you set the destination to the correct partition?
First boot it will took some times for the pink screen to disappear, for me it's around 1-2 minutes, before the shiny Android logo pops out.
Click to expand...
Click to collapse
Yes i did the extracting in ubuntu. I checked my previous startup to be sure i had the correct partition cause it always worked.
fran_nic said:
Yes i did the extracting in ubuntu. I checked my previous startup to be sure i had the correct partition cause it always worked.
Click to expand...
Click to collapse
Then make sure you set to the correct partition in the startup.txt, coz for this 2nd version of beta is different from the froyo beta 1.
For your reference:
mmcblk(X)p(Y)
For (X): Root of partition
mmcblk0: SD Card (If you want to extract the ext4.tar.gz to SD Card)
mmcblk1: My Storage (If you want to extract the ext4.tar.gz to My Storage)
For (Y): Specific partition number
You need to find out what is the partition number of the newly created partition.
ie. if it's 2, then it will be mmcblk(X)p2
In this beta, it's normally p5,p6 or p7.
Hope this helps you understand better and good luck.
Thanks for your advise l3ong91.
Problem was... windows would see My Storage while ubuntu would not. Minitool was able to resize my partition so i could use all of it. BUT still ubuntu would not recognise. After a lot of work, i found the problem was in my micro usb cable. It was faulty. So i replaced that and voila! ubuntu mounted My Storage. I was then able to create the partitions. Unpack the ext4, set startup.txt to My Storage (mine was mmcblk1p2 after following youtubeguide by JerryTech11).... Then had to redownload zImage (as i download my version early on and it was 2.2mb while the current link is to 2.4mb). And android is now running! Hoping battery lasts a day with moderate use. If so my omnia 2 is once again my favourite device.
l3ong91 said:
Then make sure you set to the correct partition in the startup.txt, coz for this 2nd version of beta is different from the froyo beta 1.
For your reference:
mmcblk(X)p(Y)
For (X): Root of partition
mmcblk0: SD Card (If you want to extract the ext4.tar.gz to SD Card)
mmcblk1: My Storage (If you want to extract the ext4.tar.gz to My Storage)
For (Y): Specific partition number
You need to find out what is the partition number of the newly created partition.
ie. if it's 2, then it will be mmcblk(X)p2
In this beta, it's normally p5,p6 or p7.
Hope this helps you understand better and good luck.
Click to expand...
Click to collapse
Thanks for your reply.In beta 1 mystorage was seen as mmcblk0.
That was my problem.
I changed it to 1 and it boots perfectly.
Thank you very much for helping me out here.