{
"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
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!
Hi all,
This is not squashed ROM for EU HD2 which contains all files from the stock RUU_Ace_HTC_WWE_1.72.405.3_R_Radio_12.28e.60.140f_26.04.02.17_M2_release_161342_signed. Yes of course some executables(akmd, reboot, vold), some libraries, some config files and kernel were replaced for Leo. The reason of why I do this is my wish to have Desire HD ROM on my EU HD2 which is closest to stock.
The ROM size is about 407M. I do not like squashed ROMs. We all have sdcards and I do not see any sense to make squashed ROM. Therefore this build uses the second partition of sdcard to store dalvik cache, data, system apps, framework. So size of this rom in NAND is 391Mb, and in sdcard is 16Mb. I recommend you to use 1024MB second partition, but not less.
My CWM installation script mounts the second partition of sdcard to /data, creates sysfiles directory and copies /system/etc/clockwidget, and /system/etc/slideshow and /system/etc/soundimage to this second partition into /data/sysfiles directory. After that the script creates symbolic links to these three directories in /system/etc direcory, and copies all other files of ROM to system partition in NAND. So we have 391Mb of files in NAND, and 16Mb of files in the second partition of sdcard.
The kernel mounts the second partition of sdcard to /data before the init.rc script will be run. Therefore android use this partition as internal storage, and we see free space of this partition as free phone storage in info.
The content:
- Full stock Desire HD RUU 1.72.405.3
- Last Gauner's kernel.
- Fixed mms.
- Fixed WiFi MAC.
- Fixed su.
- Fixed sql lib.
- Fixed first and external partition mounting.
- Percent battery.
- Rmnet is ON by default, if you would like to enable ppp you should create ppp file in /system directory and reboot your phone. To create the ppp file you should connect your phone to PC and run this command in a terminal:
adb shell touch /system/ppp
You should delete this file and reboot your phone if you would like to enable rmnet again:
adb shell rm -f /system/ppp
Not worked:
- 720p recording
- bluetooth MAC
Removed apps:
- Ereader. Use the attached archive if you would like to use ereader. Install it by CWM.
Link to ereader
"How to install" is in the readme file of the build. Please, read it! This ROM is only flashable using ClockworkMod. CWM v 1.2 is included into archive of this build. Note, system partition in NAND should be 399Mb.
CWM v 1.2 fix:
If you would like to use CWM backup and restore you should replace CWM initrd.gz file on this file. I fixed CWM to soppurting partition layout without userdata partition..
Update the previous version ROM:
If you would like to update the previous version you should not touch your sdcard. You should do this only: format NAND by task29, install magldr, flash new CWM partition layout, install new ROM.
Recommendations:
- I recommend to format NAND by task29 before install this ROM. After formatting will be done you should install magldr again. All tools are included into the archive.
- I recommend to calibrate G-Sensor. To do it go to Seetings->Display->G_Sensor calibration->, place your phone FACE-DOWN on level surface, press Calibrate button. After calibration will be finished press Ok button.
- If you would like to use the "backup second partition" feature in CWM, the second partition should be labeled as sd-ext.
- Sometimes magldr does copying of data with errors(lost data) in the "USB MassStg" mode, but you do not see these errors. Next you can see that the ROM installation was finished shortly. If it happens you should look into CWM log and you will see some errors of files extraction from archive. If you will copy this archive to sdcard again, but only by CWM or by other cardreader, you will not see these errors in CWM log. Therefore I recommend you to copy ROM zip to sdcard by CWM or by other cardreader.
- To get a CWM log you should do this:
a) Install the ROM
b) After the installation will be completed you should not reboot your phone! Go to "advanced" item of CWM menu.
c) Next select "Report Error" item. CWM will create the clockworkmod directory in root of sdcard.
d) Next copy the recovery.log file from the clockworkmod directory and attach this file to the thread. I will check it.
- The first loading(from the phone rebooting moment to appearance of the language choice screen) is long. Be patient, please.
- Please, setup only that you really need during the first boot. Desire ROM is syncing and configuring a lot of stuff during first boot if you have entered your google account. I recommend to setup all needed accounts after initial setup. And, please, let system sync and configure all stuff, next reboot your phone. After this work will be completed the ROM will be fast. I recommend:
a) disable the sync of accounts which are no needed for you, or change "Update schedule" of these accounts.
b) disable the "Back up my setting" for google account if it is no needed for you.
c) disable Automatic brightness and set Brightness to min value.
- Note, please, you can use CifsManager to mount cifs(samba(ms windows))/nfs network resources to your phone. This tool is available in the Market. It allows you to play music or watch movies from any shared resources which are available in your local network without copying this content to your phone. To use it your phone should be connected to local network by WiFi.
Currently I have 2Gb ext4 second partition on my Transcend 6-class sdcard. I can tell the system works properly and fast:
{
"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"
}
Performance:
Please, look at my video if you would like to see the performance of this ROM.
Download:
EFP v.2 HD2 Desire HD stock (last Gauner's kernel)
Kernels: (only if you would like to replace a kernel of your already installed ROM to other kernel)
Gauner's kernel with ext4
MDJ's 10.3 kernel
MDJ's 10.4OC kernel
Updates:
Desire HD stock toolbar
Desire HD custom toolbar with percent battery
How to install kernels, updates or fixs:
1. You should have already ClockworkMod(zImage and initrd.gz) on sdcard. If you use ROM-ZIP builds I think you have it already.
2. Copy the update.zip file from an update or a fixs archive to sdcard root.
3. Reboot your phone, hold Power button to access the magldr menu.
4. Next select the "Boot AD SD" item. ClockworkMod will be loaded and you will see ClockworkMod Recovery menu.
5. Select the "apply update from sdcard" item.
6. Select "Yes".
7. After flashing will be done select the "reboot system now" item.
what working and not working ???
It would be nice to have the readme of each build at least posted in the first post, so we don't have to download everything to see if we need it
I am always looking for a PURE/Stock Desire HD build, with no frils and no EXTRA apps, for a TMOUS HD2. But with no readme , i'll wait for someone first.
Greetings Santroph
Did it Include CM Mod setting?
Ok, thats what I get for beeing unpacient, downloaded it, before even reading the thread hehehe
So it is what it says, only CWM versions of the sayd rom....
I don't need it synce I don;t use CWM, but, some people might like it. Thanks anyway.
Greetings Santroph.
is this ext 2 ,ext 3 ,ext 4 same?
santroph said:
Ok, thats what I get for beeing unpacient, downloaded it, before even reading the thread hehehe
So it is what it says, only CWM versions of the sayd rom....
I don't need it synce I don;t use CWM, but, some people might like it. Thanks anyway.
Greetings Santroph.
Click to expand...
Click to collapse
Wel he did say that in the very first line of his post
But Until I get some sort of details on the builds and whats in it and whats not, I'll download MDJ's and let it sit on my sd card, cause I found CWM yesterday, and personally love it, especially with being able to take most NAND roms and convert them to CWM makes it ideal.
sathara said:
is this ext 2 ,ext 3 ,ext 4 same?
Click to expand...
Click to collapse
check www.google.com
AngelDeath said:
Wel he did say that in the very first line of his post
But Until I get some sort of details on the builds and whats in it and whats not, I'll download MDJ's and let it sit on my sd card, cause I found CWM yesterday, and personally love it, especially with being able to take most NAND roms and convert them to CWM makes it ideal.
Click to expand...
Click to collapse
same here.. I also find CWM yest..
does anyone have problems with root on gauner's kernel ? titanium backup can't get root permissions on my phone
wtf? i can`t choose CWMREC directory...
i dont get if its based on andrews work, so is it a2sd+ or data2sd? i think he mis explained
can someone confirm
hamdir said:
i dont get it its based on andrews work, so is it a2sd+ or data2sd?
Click to expand...
Click to collapse
a2sd+ as per the title
swordfish2009 said:
a2sd+ as per the title
Click to expand...
Click to collapse
the title says its based on andrews rom and the screen shots shows data2sd (768MB free)
so yea although i know the title says a2sd+ i need confirmation
What working?
What working and what not?
mms, volume, hd video???????
after i unlock phone its stuck at the htc logo
i have ext2 partition already
and i flashed the required partition size!
zheliapov said:
wtf? i can`t choose CWMREC directory...
Click to expand...
Click to collapse
From the "How to instal" in readme file:
...Copy the CwMRec directory from the 2_step directory to root of sdcard.
After copying will be finished disconnect USB cable.
Go to "Services->BootSettings->AD SD Dir" in the magldr menu and select the CWMREC directory....
1. Perhaps you forgot to disconnect a USB cable safely.
2. You copied the content of the CwMRec directory to root of sdcard, but not the CwMRec directory. In this case the CwMRec directory not exists on sdcard, the zImage and initrd.gz files are placed in root of sdcard. You should skip the step of selecting directory for boot from SD or select the <.> .
hamdir said:
i dont get if its based on andrews work, so is it a2sd+ or data2sd? i think he mis explained
can someone confirm
Click to expand...
Click to collapse
This is a2sd+.
In case of A2SD the internal storage does not include external partition, you will see only size of free space in NAND. But in case A2SD+ you will see free space of the external partition as size of intrenal storage.
rejdzu said:
does anyone have problems with root on gauner's kernel ? titanium backup can't get root permissions on my phone
Click to expand...
Click to collapse
I am using Gauner's kernel build currently and I do not have any issues with root.
something is awfully wrong
the gauner version keeps giving me a bootloop
I think you forgot to disconnect a USB cable safely. Or you copied the content of the CwMRec directory to root of sdcard, but not the CwMRec directory.
Click to expand...
Click to collapse
Not working... Any ideas?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3.2.1
This build is the exact copy of my RAFDROID HD EXT
the difference is that some parts of the system are "squashed" to give you the possibility to NOT USE any Ext partition for data.
I dont like squashedfs, but someone requested an hd build with some free space on nand (about 50mb) because some one not install a lot of apps and prefer to not use sd ext partition.
This build is mainly for EU HD2 (512mb) users.
If you are an HD 1024mb user really you dont need this, and you can use my main HD build
FEATURES
All the main features of RAFDROID HD EXT plus:
- odexed back to save dalvik cache space
- free user space after first boot: 101mb
- App2SD enabled if you use and SD with an EXT partition
CHANGELOG
Code:
3.2.1 - 3 MAR 11
Fixed Market FC
3.2- 3 MAR11
Some improvements and fixes to radio/audio driver,
this "should" fix phone freeze in some setups, also if I was not able to replicate the issues
Tweaked for more battery life on some sd cards usage
Updated hosts file with last one
3.1 - Initial release
=== INSTALL INSTRUCTIONS (CWR) - NEW USERS WITHOUT CWR INSTALLED OR WITH CWR BUT USING ANOTHER ROM ===
This process will erase everything on your nand. So, if you are already using a previous rom, backup everything!
Download PANASONIC SD FORMATTER and use it to format your card with FULL ERASE
You need to flash MAGDLR 1.13
You need to flash, via USB FLASHER magdlr option, this recovery partition layout, otherwise the build will not boot.
Download the FULL RAFDROID PACKAGE and copy the entire zip (not extracted!) on the SD CARD root.
Put the SD CARD in your phone and power it on and go in the MAGDLR menu (hold the power key while powering up)
Select BOOT AD RECOVERY
Click on INSTALL ZIP FROM SD CARD and then CHOOSE ZIP FROM SD CARD
Select the FULL_RAFDROID_HD*******.zip that you downloaded before.
Select "Yes - Install........" and wait for installation then Go back with power button and select REBOOT SYSTEM NOW
First boot can take up to 20 minutes. If you are stuck on white screen with HTC logo just wait. If you hear boot sound more than one time, you had a bootlop and something has gone wrong. Delete everything, reformat your SD card, read again the instructions and try again.
When you see the lockscreen, give at least 5 minutes to settle. Then do all your settings and then reboot again
Enjoy.
Remember: if you want to avoid Data Corruption always choose SHUT OFF and not reboot!
=== INSTALL INSTRUCTIONS (CWR) - UPGRADING FROM A PREVIOUS RAFDROID VERSION (2.2 or greater) WITH ALREADY CWR INSTALLED===
Since the data storage method is different, you cannot upgrade from a different RAFDROID HD version. You have to install fresh. Anyway you will keep your data and apps installed.
============ CONFIG.TXT ============Used some ideas and code bits from Dandiest's init script.
You can create a config.txt file on the root of your sdcard to configure some things at boot.
Actually you can configure the following options
gps_zone=[your country]
check http://www.pool.ntp.org/zone/@ for country codes (example: it for italy, us for usa.. and so on...)
ppp_mode=[1 or 0]
1 to enable PPP
0 to enable RMNET.
Default is 0
If wince=1 default ppp_mode will be 1
old_light_driver=[1 or 0]
0 to use the new light driver (working notification leds, button backlight control)
1 to use the old light driver (no notifications leds, buttons will go off after 10 seconds)
default is 0
auto_btn_backlight=[1 or 0]
1 to have the buttons backlight going off/on with the screen
0 to have the buttons backlight going off after 10 seconds from when the last button is pressed
default is 1
this work only if old_light_driver=0
wifi_mac_change=[1 or 0]
1 tells the system that you will need to change the wifi mac address to a custom one
0 tells the system that you will use the wifi mac address based on device hardware
custom_wifi_mac=yy:yy:yy:yy:yy:yy
here you have to write the wifi mac address you want.
This is needed, and will work, only if you specify wifi_mac_change=1
If you not write any mac address here, the default 00:11:22:33:44:55 will be used
Just an example on how a file could look:
Code:
gps_zone=it
ppp_mode=0
old_light_driver=0
auto_btn_backlight=1
The init script will also create an init.log file on your sd card at every boot. This will help you and me with debugging if something not works fine. If you have issues please always post your init.log file when reporting your problem.
============ KERNEL ============
You can refer to my kernel thread for updates, changelog, and comments
http://forum.xda-developers.com/showthread.php?t=940823
============ SQUASHED FILE SYSTEM ============
App, Framework and most of Lib folders, are squashed.
Anyway you can push or delete any file from those folder because any file is simlinked.
Example: if you want to use a different framework-res.apk, you can copy it in the /system/framework folder. At this point the simlink will be removed and your new file will be stored on nand, not in the squashed filesystem. This means that more "new files" you push in the squashed folders, less nand space you will have.
Anyway please note that I left only about 13mb free on "system". This means you will not able to push more then 13mb files. If you like to change a lot of things.. this build and squashfs is not for you.
============ DOWNLOADS ============
You need to flash, via USB FLASHER magdlr option, this recovery partition layout, otherwise the build will not boot.
Full Rafdroid HD 3.2 LIGHT SQ
http://hotfile.com/dl/108421743/5bfea5b/full_rafdroid_hd_3r2f1_light_sq.zip.html
MD5: 97018DD4D05FAAFBCC5F9329AEB03F28
SHA1: F6B6D67B90B96E02FCDA70D98836450B6FAE9917
CRC32: 150CCA2B
OLDER VERSIONS:
3.1 : http://www.multiupload.com/X8VBC6WKYV
============ DONATE ============
I made this version just for people that were asking, so if you think this helps you, a small donation for a coffe or a beer, is appreciated. Otherwise a click on the "thanks" button is appreciated too
============ CREDITS AND THANKS ============
Credit to all the people that made all this possible: Cotulla, DFT, darkstone, markinus, danijel, rajko and some one other I'm missing...
Big Thanks to Cass, ocm, darkstone, rajko, crawlingcity, atoore for their help in the last months and to be always available to help
Thanks to all the users who donated and helped me to keep going
Thanks to all the testers and users of my builds that with their reports helped me to solve bugs and issues.
Thanks also to Sergio76, imilka, cmylxgo for the nice talks and knowledge sharing
FAQ
Q: I have low quadrant score
A: This is normal. Nand is slower. Anyway during day usage you shold not notice big difference
Q: I have small freeze when installing apps
A: This happens with all Desire HD builds. I can't do nothing to avoid this
Q: I'm using App2SD but my internal memory keep decreasing at any app installed
A: Go in the application management and move the installed abb back in the phone. Some apps anyway keep some datas in internal mem.
Q: My phone sometimes freeze and I have to reboot.
A: Go in Settings -> Audio -> disable audible touch tones. this will solve the issue in most of the cases.
Q: Can you provide a different link or a mirror different from hotfile?
A: I'm sorry but the answer is "no". I pay hotfile every month and the downloads give me the possibility to pay it. I dont do this for money, but I also dont want to waste my money
Q: During/after boot a window appears with "System process not respoding". What I have to do?
A: This is caused from the new audio driver I used. The new audio driver has better phone stability and no robo voice. You have two choices: 1) Click on "wait" and all will be fine OR 2) download the "old_acdb_file.zip" and flash it via recovery. In this way you will not have the error anymore but you will start having robo voice on first call (you can avoid this disabling audible touch tones) and could happen that your phone freezes when receiving a call. It's your choiche. I preferred the "window error" one because for me is more important to have a working phone than an error window appearing at boot.
Q: I have robo voice when I make a call
A: To avoid this, disable "audible touch tones" from the "settings -> audio" menu. You will have no-more robo voice also if you reboot.
a) During the robo-voice call, enable the speaker, then disable it. You will have no more robo-voice until next reboot.
Q: I have very low audio during calls
A: During the call, enable the speaker, then disable it. You will have loud volume until next reboot.
Q: after boot I see only a white screen with a green htc logo
A: just wait. It can take fro 5 up to 20 minutes depending on your sd card. There are no issue. The build booted fine, it's just copying all the files to SD. This will happen only on first installation.
Q: I'm having high battery drain
A: Try reboot. Try disabling gps in location. As you can see from the screenshot I have 4mA with WIFI active! Also be careful. If during google account setup you choose to backup/restore all your data, the sync process will be dramatic heavy because it has to reinstall all your apps. It could need a couple of hours to settle. Also high battery drain could be caused by SD. try another one.
Q: It's really laggy!!!!
A: as all Desire HD builds this is BIG! This needs at least 10-15 minutes after boot to be usable. Then try to use it for 5-6 hours.. and do a couple of reboots.. you will see that the speed will improve. After 24 hours of use and 4-5 rebots this will be really fast.
Q: I have no GPS or the fix is really slow
A: Firs fixt can take up to 5 minutes. just wait.You can edit the config.txt gps_zone= to your country. See here for the right strings http://www.pool.ntp.org/zone/@ if this not solves, try use QuickGps from the market to download a-gps data.
Q: It not boots
A: partition again and format again your sd card. follow the guide linked in the first post. post your init.log. check that you flashed the custom recovery linked in the instructions.
Q: I have no data/3G/HSDPA
A: probably you have to set your apn manually. google it for tips on how to do and what settings are need for your carrier
Q: How do I remove BOOTSOUND / How do I change bootanim
A: bootsound and bootanim are located in /system/customize/resource
Just delete android_audio.mp3 if you dont want sound
Q: I have wake up lag
A: It's an issue that devs are trying to solve. It's not related to the build itself. In the Q&A Forum there is a thread about this problem.
Q: My screen stays off after call
a) Maybe this can help: http://forum.xda-developers.com/showthread.php?t=946012 ATM very few people have this issue, so I wonder is related to sd card.
Q: My contacts pictures are low res after sync!
A: this is a google problem, read here http://code.google.com/p/android/issues/detail?id=4147
Q: I have random reboots
A: Seems to be related to your phone, read here http://forum.xda-developers.com/showthread.php?t=941845 and here http://forum.xda-developers.com/showthread.php?t=898804
UPDATES:
Instructions:
1. Download your update and copy it to your sd card folder. Dont use MAGDLR mass storage mode because will corrupt your files. Use an sd card reader on your pc or usb mass storage mode in recovery menu
2. Boot into MAGDLR and choose BOOT AD RECOVERY
3. Make a backup! It will save your life if something goes wrong and you want to roll back! You are aware now!
4. Click on INSTALL ZIP FROM SD CARD
5. Click on CHOOSE ZIP FROM SD CARD
6. Select the update zip that you downloaded before
7. Select "Yes - Install........" and wait for installation
8. Go back with power button and select REBOOT SYSTEM NOW
Removed Apps for version 3.X -> http://www.multiupload.com/H5IPNFYBG4
old acdb file (read the faq if you dont know what this is) -> http://www.multiupload.com/AHV0UIKHZF
Stock Framework, only for version 3.X -> http://www.multiupload.com/TVDWWVDNL1
RAFDROID Framework, only for version 3.X -> http://www.multiupload.com/ZC4P6KSKWL
Replacing fonts with standard Desire HD one http://www.multiupload.com/N4VR74W8PK
Replacing fonts with Rafdroid one http://www.multiupload.com/E9UKQBEE4P
If you have issues with flash videos on website, you need an older flash version. Check this post. Thanks to Jayedamina http://forum.xda-developers.com/showpost.php?p=10584806&postcount=280
- maybe I need also this -
First! Nice!
waiting...
are there any advantages on HD2 TMOUS?
rafpigna said:
This build is mainly for EU HD2 (512mb) users.
If you are an HD 1024mb user really you dont need this, and you can use my main HD build
Click to expand...
Click to collapse
I gues not rizky_p
rizky_p said:
are there any advantages on HD2 TMOUS?
Click to expand...
Click to collapse
link is on-line
Thanks, will try
Going to try this tonight, looks good. Any one tried it yet?
Ston said:
Going to try this tonight, looks good. Any one tried it yet?
Click to expand...
Click to collapse
Yep, works a treat
Hello Raf thank you very much for giving us this opportunity, just wondering which files should we use to revert back to stock framework and standard fonts and how to install them.
Thanks again for all your efforts
I always had problem with data on ext partition due to easy file corruption, so I'm trying this...thanks!
thesniffer said:
Hello Raf thank you very much for giving us this opportunity, just wondering which files should we use to revert back to stock framework and standard fonts and how to install them.
Thanks again for all your efforts
Click to expand...
Click to collapse
You can use the update zips from my EXT build.
Very nice and smooth build
But one question: Has anyone tried to change the kernel to Rfp 1.6 or 1.5? I just tried and now the phone is stuck at "gogogo" ...
Intersting
rafpigna said:
You can use the update zips from my EXT build.
Click to expand...
Click to collapse
So via CWM Recovery as i supposed.
Thanks again for your kindness and keep up your valuable work
hi raf
i installed this one(only for proof of concept),works great and i think it is a little faster than the "normal" rafroid,i dont have any lag!!! but 101mb.....very poor...
back to rafroid HD "normal" with d2sd..... i love more space!!!
nice & good release
keep up the good work
cheers!
4EXT Recovery Classic v2.2.7 RC5 | STAY @EXT4 | Convert FS | Rom -> Backupname | ..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Quick note about themes:
Available themes as of Oct/18:
Themes by [URL="https://forum.xda-developers.com/member.php?u="]GuestK00388[/URL]
Themes by Apaquette420
Themes by Whiskey103
Themes by Amresh
Themes by Apaquette420
Themes by CWhitney24
Themes by DaMyth
Themes by Blindndumb
To uninstall any "flashed theme" and to revert to your own custom settings you had before flashing, just use this Theme Uninstaller in recovery.
It will clear any theme you might have flashed and revert to your own custom settings you had before flashing that theme!
THANKS:
All credits and my deepest respect go to Koush for his extremely great code!
Without him 4EXT Recovery wouldn't have been possible!
Biggest thanks possible go to Sebastiaan15 for his brilliant ideas and who spent whole weeks testing my buggy code with his Desire
Without you I could never have made it!!!
So BIG THANKS to SEBASTIAAN15 and KOUSH for his hard work with CWMR !!!
Many credits to the Desire S community ( especially to loveboatcaptain - LBC Mod Android Development and Marylandcookie ) for testing, very nice ideas, feature suggestions and helping to get the code running on the Desire S!
Special big thanks to RAVENNA from android-hilfe.de board for hours of testing for the Desire!
BIG Thanks to Hussainmushahid who helped me a lot spending much of time with solving a bug I could not reproduce on my device.
And many thanks to all users who reported and helped to identify problems ( can't any longer list all of you here since the list has grown too large )!
Even more thanks to people who 've bought me some beer YOU ROCK!! ZEEKIZ, A USER, PHILOS64, STEVEATHOME, PREACHER65, BEN_PYETT, ULTRA DROID, PTR_HAMILTON, BEANBEAN50, SEBASTIAAN15 and LOVEBOATCAPTAIN
v2.2.6 RC4 Released: Oct/01
Rare Superuser problem when tar backups were enabled (disabled by default) was fixed.
Converting partitions between ext3 and ext4 without data loss now correctly calculates the space needed to successfully complete the operation
New option: check and optionally repair the file system on your sdcard (fat32)
Removed duplicate format cache option inside the format menu (wipe cache does the same)
When formatting fat32 it will now save your 4ext.prop settings and restore them afterwards
Changed partitioning of the sdcard to not use LBA mode for new fat32 partitions as requested by Ghiki
Added new size option (128mb) to the partitioning menu per request
Parted is no longer used to format fat32 in the partition menu-> This solves a bug where sometimes the creation of the fat32 file system failed and produces better quality results
4EXT Recovery themes should now stay when formatting /system or flashing new roms
New option: format /sdcard fat32
New 4EXT Recovery Control API because I'm forced to drop "extendedcommand" (see App for the reason why)enables file names and directories to include spaces for installations
calculates needed space to complete a full or advanced backup at the beginning of the backup.
This ensures that you are not left with a non working backup.
Size for recovery greatly reduced
New 4EXT Recovery Control Features
Please see www.4ext.net for more.
Fix permissions
Calculate real values for the space needed to create a new full or advanced backup
Advanced Backups: While you are selecting / deselecting partitions, it will display and update the currently needed space to complete that custom backup set.
As an example, the following would be possible to do in just one session: Restore a backup, set to create a backup / advanced backup before the restore,
format all partitions with a file system of your choice before the restore process starts,
flash additional zip files afterwards, fix permissions and select to stay inside recovery or to reboot automatically once all actions are complete.
Features: Use 4EXT Recovery Control or Recovery Updater for complete Changelogs and Known issues!
not all features may be relevant for all devices
Displays additional information:
Identifies your current rom and displays its name
Current filesystems on your partitions
Free space remaining of all of your volumes
Current battery charge level
Backup | Restore:
Correctly calculates free space needed to complete a backup ( version > 2.2.6 RC4 )
Tar backups (can be switched on or off)
Complete CWMR5 compatibility
All Backups you create will be named after your currently installed Rom for easier identification.
Never unwillingly get "downgraded" to EXT3 again
Always restores backups using the file systems you HAD on your partitions at the time of creation!-> all partitions formatted with ext4 at that time, will be restored to ext4. The same is true for ext3.
You can manually change any existing Backup to ext4 or ext3-> so that after a restore, all partitions and up with the file system you wanted!
Advanced Backup: backup only a single partition
Convert any of your partitions to EXT4 or EXT3 without data loss.
Formatting:
When you wipe or format it will always use the same file system you currently have.-> but you can change that
When you format ext4 it will always create an aligned file system
Correctly identifies unformatted sd-ext partitions-> if it finds one it displays a warning and suggests you may format them by visiting the 4EXT menu
Filesystem check and repair option in advanced menu
Partitioning:
Alignment check of your partitions
Full support for up to 2 sd-ext partitions + swap (Backup/restore/format/convert, fsck, et.c.)
(RE-) Partition your sdcard for sd-ext without removing your fat32 partition.
All partitions created with 4EXTRecovery will be perfectly aligned to 4k
Installing:
Integrated md5sum checking option
Themes:
Customize all colours used throughout recovery
Use your own icons, background images, progress bars.. more to come.
Assign different backgrounds to different menu categories (version >= 2.1.2)
Create a flashable zip for others to flash your theme.
Menus:
Most popular menu items rearranged
Format menu
Power Menu + option to reboot into bootloader
Less "No's" in confirmation dialogues
Changed Advanced Restore: first select what you want to restore, then select the backup-> Useful for restoring from "Advanced Backups"
4ext.prop:
Configuration file on your sdcard where you can set options to be used by 4EXTRecovery
Change all settings conveniently with 4EXT Recovery Control
Many more options to come
Share your settings / themes by packing your config into a flashable theme
Other stuff:
USB Storage Autostart (must be switched on)
Mount usb storage exposes all partitions on your sdcard to the os (not just fat32)-> you could even partition your sdcard from your PC while connected via USB
Switch haptic feedback on/off
You don't need to reboot recovery if you transferred a file to show up in the install menu.-> This bug affected only some users with either CWMR or previous versions of 4EXT.
Button backlights (Desire S, Desire HD and Incredible S only)
Download:
All downloads are now available through 4EXT Recovery Updater. It's free, no ads, no tracking, no nothing, don't worry
.. and of course via 4EXT Recovery Control
This ensures that your downloads are ok by automatically verifying md5sums and that known issues and changelogs are easily accessible
It also notifies you when there are any new critical bugs found
Recovery images will be uploaded for download soon too, but they can also be acquired easily by using Updater or Control.
You can for example just download a recovery.zip containing the image. The download will be automatically verified for correct md5sums!
4EXT Recovery Control
Free version: Recovery Updater
Fully featured version: 4EXT Recovery Control
For a list of its many features, visit www.4ext.net
Some examples :
Flash as many zip files you want in one go
Automatically calculate and display the md5sums of all zip files you are going to flash
Check your backups' health to ensure they will restore later when you need them, by verifying their md5sums!
Optionally, but highly not recommended:If md5sums don't match but you REALLY NEED that backup BADLY, you might want to restore it anyway.
You can you this app to fix the md5sums of a given backup to "forcefully" restore it!
Calculate real values for the space needed to create a new full or advanced backup
Advanced Backups: While you are selecting / deselecting partitions, it will display and update the currently needed space to complete that custom backup set.
Identifies and adds your romname so you don't need to type so much when chosing a meaningful name for your backup
As an example, the following is possible to do in just one session: Restore a backup, set to create a backup / advanced backup before the restore,
format all partitions with a file system of your choice before the restore process starts,
flash additional zip files afterwards, fix permissions and select to stay inside recovery or to reboot automatically once all actions are complete.
Much, much more! See www.4ext.net
Recovery theming
Uninstall and Install themes with live preview and the option to change their colours without the need to reboot into recovery.
Change all colours with live preview and a nice colour picker.
Working great on my dinc2 this is the one thing i missed since switching from the inspire and now i have it back. Thanks max!
Sent from my Incredible 2 using xda premium
oxlong27 said:
Working great on my dinc2 this is the one thing i missed since switching from the inspire and now i have it back. Thanks max!
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
Thank you very much for that!
And for jumping into the cold water for me
If it booted up fine it's alright and I can remove the warning. Everything else is just like on the IS.
---------- Post added at 01:09 AM ---------- Previous post was at 12:48 AM ----------
Added 2.1.1 Final, but that version is really old.
I'd try the latest first. It has been extensively tested and issues if any should only be minor.
Yep everything i tried is working as it should. Havent tested the formatting yet but im sure its fine everything else works. And as far as trying something thats untested, well thats what xda is about, if you dont get a soft brick here and there your not having any fun. But yes this works fine thanks again
Sent from my Incredible 2 using xda premium
I gave it a go and seems to be working just as it should. Was jealous of this recovery on the Incredible S forums because it let you create EXT4 file structures and now its here. Thanks!
Quick question, what's the advantage with EXT 4? I have heard that it's faster, but then several others say it's a waste of time. I do like this layout a lot more aswell.. The backgrounds are an awesome idea! Great job with this
Sent from my Incredible 2 using XDA App
You should add this to ROM manager.
jonathon2011 said:
Quick question, what's the advantage with EXT 4? I have heard that it's faster, but then several others say it's a waste of time. I do like this layout a lot more aswell.. The backgrounds are an awesome idea! Great job with this
Sent from my Incredible 2 using XDA App
Click to expand...
Click to collapse
Thank you very much
Yes, theoretically it's faster.. depending on usage it can be much faster.
On a phone the difference is less than on a computer though.
Deleting larger files is definitely much faster, also formatting.
Most newer mobiles get shipped with ext4 file system instead of ext3.
It's difficult to answer your question
You should try it out and check if you feel the phone is faster
shoman24v said:
You should add this to ROM manager.
Click to expand...
Click to collapse
I really can't imagine that I had a chance or that it would be possible
Also obviously I would like ppl to use my app.. it was a lot of work.
And yeah, also if it is the free version!
It's a big advantage for me as the developer and I hope for the users too.
That way I can send you news about critical bugs found in a new release (which happened with rc1 for example), I can make sure you get to see at least the Changelog when you install a new version and since it's just a button press, the chance is greatly increased that you also take a look at any known issues.
There are times when I release many updates in a short time. This really comes in handy.
At the moment there is only the preview, but I will release the free version today or tomorrow
Downloaded this morning and gave it a run. I like this recovery a lot.
I ended up making a backup, and then converted my file system to Ext 4 on data and Cache (system already is.)
This is a very nicely done recovery, I like that it is easy to navigate, and has a few more options when doing wipes.
The app is nice to.
Thanks for sharing this!!
PacerguyDon said:
Downloaded this morning and gave it a run. I like this recovery a lot.
I ended up making a backup, and then converted my file system to Ext 4 on data and Cache (system already is.)
This is a very nicely done recovery, I like that it is easy to navigate, and has a few more options when doing wipes.
The app is nice to.
Thanks for sharing this!!
Click to expand...
Click to collapse
Thank you very much
BTW Free version of the app is finally up
madmaxx82 said:
Thank you very much
BTW Free version of the app is finally up
Click to expand...
Click to collapse
I went ahead and bought the market version. Excellent job, Ive been waiting for a recovery like this.
I would have to say I like this recovery a lot. I like having the partion information and battery level in recovery. Also the option to convert partions is a plus. Already tried it on a couple different roms and currently running them all as ext4.
Great job and keep up the good work
Sent from my Incredible 2 using XDA App
After converting everything to ext4 cant get wifi tether to work anyone else have this issue? Boots 100 times faster though on cm7
edit fixed by updating to the latest nightly
Great recovery, got the market version. Super smooth on a few roms here.
Anyone with a sense rom should go without saying but make sure the kernel supports ext4. Drellisdees kernel does well
This Recovery looks great, I'll try it soon. A couple questions...
1. It replaces Clockworkmod 5.0.2.0?
2. Has anyone actually done any benchmarks to see if Ext4 is faster than whatever is on the stock phone?
I use Ext4 on my Ubunutu Linux box and I understand it improves performance and adds journaling, but is it actually faster on a phone. It would be cool to see boot times, application install and launch times, task switching, etc. So often people say even minor updates to ROMs are "much faster" and it's nonsense.
Thank you all very much
regarding ext4: yes it will be faster, but how much depends on usage and it's really difficult to say on a phone. But certainly it won't be slower.
Also since newer phones seem to ship with ext4 it might indicate something
Yes, when you flash any other recovery it replaces the previously installed one.
ph1nn said:
This Recovery looks great, I'll try it soon. A couple questions...
1. It replaces Clockworkmod 5.0.2.0?
2. Has anyone actually done any benchmarks to see if Ext4 is faster than whatever is on the stock phone?
I use Ext4 on my Ubunutu Linux box and I understand it improves performance and adds journaling, but is it actually faster on a phone. It would be cool to see boot times, application install and launch times, task switching, etc. So often people say even minor updates to ROMs are "much faster" and it's nonsense.
Click to expand...
Click to collapse
Well as far as benchmarks I haven't dug in too deeply. Unfortunately with quadrant file systems tend to fool it anyway but I haven't gotten linpack or similar
The biggest advantage I see are the same things that we both likely saw when linux changed to ext4 (ubuntu fan here too ) that being, things involving large amounts of data being moved at once have the biggest improvement. Obviously there are more instances of that on a computer than a phone . Boot times, it knocked a few seconds off my boot time on cm7 which is not slow to boot by any means already. I think it would be even more drastic with something as big as a sense 3.0 rom..everything else I don't know that its particularly faster after everything settles down but is most definitely not slower and is just as snappy as before. It does seem to be a bit quicker in terms of settling down more quickly after a reboot (not laggy for as long) and everything getting precached etc.
Just want to tell everyone, that there is a new known issue with tar backups!
It can happen if you have enabled tar backups that superuser stops working after you restored a tar backup.
To anyone not familiar with this: it is disabled by default! So don't worry if you didn't enable that setting!
I have updated known issues and also sent a notice about that.
To work around this, you can flash your rom again (no wipe needed) and it will be ok.
Nonetheless please deactivate tar backups for now.
It doesn't happen for everyone and always.
Difficult to track it down and I couldn't reproduce it on my device yet.
It is or was also known to happen with CWMR5 which introduced tar backups.
Maybe it's solved in the newest version I don't know however I have seen a lot of posts regarding that.
I'm working on this.
If someone runs into this problem, please send me a pm or a report telling me which version of superuser and which rom he was running.
Thank you very much and sorry about that.
Anyone entering the app gets a one time notice about it.
I've been using the tar backups since installing 4EXT last week. No problems on my end, but since I really don't need the tar backups anymore, I'll go ahead and disable that option and go with the default format.
Thanks for letting us know Madmaxx. And thanks again for the great recovery!!
Thank you
New versions of recovery and 4EXT Recovery Control.
Big changes
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)