Notice: I'm shelving this, at least for now. The errors are too inconsistent and sporadic, and testing has proven to bee rather arduous. I won't delete the repos, but I'm not currently planning to support or look at this much for at least the near future. It's worked for some people, but USE AT YOUR OWN RISK only. I am not providing binaries for this, if you want to use it then you'll need to build it yourself and if you go to that much trouble I would hope you know what you're doing.
If an error occurs, I recommend rebooting into any version of FIREFIREFIRE that has the 'fastboot oem format' command and using that to fix your partition table. If you have no idea what that last sentence just said, I strongly suggest you do not use this tool.
-----
I briefly mentioned in a previous post that I was working on an app that would enable you to resize your data, cache, and sdcard partitions so that you can have some more app installation space. Now that I've gotten everything to a stable point, I'd like to go ahead and release my work to the general public for anyone who wants to give it a try. So, I'd like to present what I've named FireParted.
What is it?
FireParted is a basic partition manager for your Kindle Fire, released under the GNU General Public License v3.0. It provides you with a (hopefully) intuitive GUI for resizing your data, cache, and sdcard partitions. It does not support or affect any other partitions on your device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How does it work?
To use FireParted you will first need the following:
ADB needs to be configured on your computer to connect to your Kindle Fire. This will not install or configure the ADB drivers for you, but KFU will.
You need to have a custom recovery installed (tested against TWRP, but ClockworkMod should also work)
You need to have Windows with the .NET 3.5 Framework installed (Win7 ships with this, XP and Vista users can use the link to the left if needed). I plan to support Mono, but it has not been tested yet (it does build in MonoDevelop, though, so that's a good sign).
(Optional, but recommended) FIREFIREFIRE v1.1 or later. This will give you access to the 'fastboot oem format' command should something horrible happen (power loss, your computer crashes mid-partition, etc).
Your device must be in recovery mode while running FireParted in order to repartition it. Note that you can make an archive of your /data partition from a normal OS boot.
(Optional) If you want to examine a data archive backup on your computer, I highly recommend 7-zip. It's lightweight, free, open source, and supports TAR and GZIP archives, which is what I'm using to create the backup.
Once you are sure that you have met the prerequisites, you can simply launch the FireParted executable to start the application. Again, before you can do any partitioning work, you will need to reboot your device into recovery. Next you should read the partition table of your device to get a baseline, and then backup your data partition (unless you want it to be formatted). The numeric controls on the left allow you to choose the partition sizes you want, and "Apply Changes" will perform the repartition for you. Then you can restore your data backup and reboot to test your new layout!
Can I get a quick feature rundown?
Sure. FireParted currently supports the following:
Repartitioning of the data, cache, and sdcard partitions, to allow for larger app installation space (for example).
Archiving and unarchiving of the data partition (to preserve data during a repartition). Can be used simply as a backup mechanism if desired (requires root).
Basic sanity checking - FireParted keeps track of how much space you have to split amongst the data/cache/sdcard partitions, and won't let you create a partition that doesn't fit. It also won't let you shrink a partition to be smaller than its current contents. Also limits the cache partition to a minimum of 64MB.
Where can I get it?
The source code is available on my GitHub.
CHANGELOG
Version 1.1 - 01/04/2012:
Fixed some math/parsing so that FireParted will be more intelligent when determining start/end points for partitions.
Version 1.0.1 - 01/04/2012:
Fixed a minor bug that would cause the GUI buttons to get stuck in a disabled state if an error occurred while reading the partition table.
Version 1.0 - 01/04/2012:
Initial release. Includes all of the planned basic features:
Repartitioning of the data, cache, and sdcard partitions, to allow for larger app installation space (for example).
Archiving and unarchiving of the data partition (to preserve data during a repartition). Can be used simply as a backup mechanism if desired (requires root).
Basic sanity checking - FireParted keeps track of how much space you have to split amongst the data/cache/sdcard partitions, and won't let you create a partition that doesn't fit. It also won't let you shrink a partition to be smaller than its current contents.
Planned features/Needs work
Figure out what the hell is causing the "cannot meet constraints" error on other Fires (but not mine )
Test and support Mono builds/execution on Windows
Test and support Mono builds/execution on Linux (possibly Mac as well)
Very nice will be using this in the near future.
This should be stickied. I could see this being a staple utility.
Awesome... no elaboration needed
Amazing! I assume I can also use this to claim more general storage space? Is their a minimum size I should avoid hitting?
Time to fire up a VM and give this a shot. Much appreciated!
very cool!
No words, you are our hero. I added in 3 minutes currently 1GB sd card space...
cl2eep said:
Amazing! I assume I can also use this to claim more general storage space? Is their a minimum size I should avoid hitting?
Click to expand...
Click to collapse
Sure, you can tweak the values in either direction. Really, however much you think you can manage with should work fine, I would think. When you read out your partition table the meters will let you know how much space you're currently using on each partition, so if you have a lot of free space on /data and don't intend to install a lot of large apps there's no reason you can't shrink it.
I do currently enforce (in code) a 64 MB minimum on the /cache partition. I chose 64 MB because the limit on apks in the Market is 50 MB (source), so 64 MB should in hopefully give you enough space to install anything from the Market.
Of course, another consideration might be OTA updates. A 64 MB cache partition would be too small for the 6.2.1 OTA update package to download, for example. It's possible this could be a sort of poor man's protection from unwanted OTA updates, but I can't make any guarantees
Not sure what happened, I followed the instruction and it got the the part where it tries to partition the sdcard and came up with an error about not meeting constraints ( i made sure I had plenty of free space). The program and phone froze up, I can only boot into recovery. When I run the program and check I no longer have partition 10 or 11.
I'm having bad luck with this device.
airmaxx23 said:
Not sure what happened, I followed the instruction and it got the the part where it tries to partition the sdcard and came up with an error about not meeting constraints ( i made sure I had plenty of free space). The program and phone froze up, I can only boot into recovery. When I run the program and check I no longer have partition 10 or 11.
I'm having bad luck with this device.
Click to expand...
Click to collapse
I had the same issue and tried to do it by hand. When I get into print the parted it says all of the partitions are there, but I can't get out of recovery
airmaxx23 said:
Not sure what happened, I followed the instruction and it got the the part where it tries to partition the sdcard and came up with an error about not meeting constraints ( i made sure I had plenty of free space). The program and phone froze up, I can only boot into recovery. When I run the program and check I no longer have partition 10 or 11.
I'm having bad luck with this device.
Click to expand...
Click to collapse
Can you post your current partition table?
dnathan13 said:
I had the same issue and tried to do it by hand. When I get into print the parted it says all of the partitions are there, but I can't get out of recovery
Click to expand...
Click to collapse
Are you stuck in the recovery bootmode, or does it simply fail to boot? Can you post your current partition table, too?
dnathan13 said:
I had the same issue and tried to do it by hand. When I get into print the parted it says all of the partitions are there, but I can't get out of recovery
Click to expand...
Click to collapse
I was able to create and setup partition 10 and 11 but I was only able to boot into recovery. I tried restoring a few backups, wiped data, cache, system, tried installing CM7 and always ended up only booting into recovery. As a last ditch effort I installed the stock 6.2.1 update.zip and it is back working again. I had to re-root and reinstall recovery but I've restored my backup and everything is back up and running fine. Now I'll be able to sleep tonight...
airmaxx23 said:
I was able to create and setup partition 10 and 11 but I was only able to boot into recovery. I tried restoring a few backups, wiped data, cache, system, tried installing CM7 and always ended up only booting into recovery. As a last ditch effort I installed the stock 6.2.1 update.zip and it is back working again. I had to re-root and reinstall recovery but I've restored my backup and everything is back up and running fine. Now I'll be able to sleep tonight...
Click to expand...
Click to collapse
I don't have that, do you have the thread?
Edit: found and I am all good now
So can I do this on my current ROM to add space for apps without losing data?
Well this thing bricked my KF. I'm having the same issues as the people from the previous posts. I installed 6.2.1 but now I'm stuck at the notorious "your Kindle has detected a problem" and nothing in CMD is working for me.
eldarerathis said:
Can you post your current partition table?
Click to expand...
Click to collapse
I don't have a copy of the partition table but the program tried to resize the media section and had an error then partition 10 and 11 were gone. I then used the steps in the last few posts of the manual partitioning guide to make partitions 10 and 11.
Matt V said:
Well this thing bricked my KF. I'm having the same issues as the people from the previous posts. I installed 6.2.1 but now I'm stuck at the notorious "your Kindle has detected a problem" and nothing in CMD is working for me.
Click to expand...
Click to collapse
As long as you can get into fastboot/recovery it should be fixable. FIREFIREFIRE v1.1 can 'fastboot oem format' to reset the device to its initial internal point, or in recovery you can examine the partition table and fix whatever is in a bad state.
airmaxx23 said:
I don't have a copy of the partition table but the program tried to resize the media section and had an error then partition 10 and 11 were gone. I then used the steps in the last few posts of the manual partitioning guide to make partitions 10 and 11.
Click to expand...
Click to collapse
Actually, would you be willing/able to post your layout as it is now? That could be helpful, too, even in its current working state.
Read my thread here for more information:
http://forum.xda-developers.com/showthread.php?t=1429661
Related
THIS IS NOW OUTDATED!!
It uses the old sqsh method WITH a rootfs. So if you're wanting to use the NoMoRootfs method, this won't work. Please use the already complete builds in the Kaiser/Vogue threads as they are working the best at this moment.
I hope to update this when I have some free time. Will include a how to for NAND also.
What's What:
zImage
Linux kernel which initializes hardware
initrd.gz
Initial ramdisk. Usually, startup scripts, device drivers (modules) and related files (e.g. Bluetooth firmware), as well as some basic system tools (shell etc.). This has grown and split into the rootfs.img.
rootfs.img
Contains the ril (how our phones communicate with the network) and other necessary files to get the system going.
haret.exe
Bootloader to reboot the device into Android
default.txt/startup.txt
Contains settings for the boot process, and special kernel configuration parameters
system.img/system.sqsh
Contains the Android core, default applications and some more system files and tools.
*.user.conf
Contained in conf folder. Sets compcache/swap parameters.
How it works
When you run Haret, it wipes Windows from memory so it's not running anymore, (although it keeps it on the actual phone storage) then it "reboots" the phone into android. So think of it like this... Windows is on the phone storage and Android is on the SD card. Haret shuts down Windows (keeping it on the phone storage) and then boots up the phone using the SD card in place of the phone storage. When you turn the phone off/reset it will boot back into Windows.
Haret looks at the default.txt/startup.txt for it's bootup parameters, it then loads the zImage which initializes all of the hardware (screen, keyboard, etc.) and initrd which contains the initial startup scripts. The rootfs is then called which creates the data.img and moves the system and data to partitions (if available). It looks in the system.sqsh for a file called ion.build, donut.build, tattoo.build, etc. which tells it what kind of system it is. This also tells it to run the ion.user.conf, donut.user.conf, tattoo.user.conf.
Setup:
Download this package.
If you can't run this then you'll have problems with other builds. If you can run this, things are on the right track.
Format your SD card to Fat32, if not already. Make sure there's NOTHING on your SD card.
Extract the android folder to your SD card.
Rename the default-*.txt file to either default.txt or startup.txt.
-default.txt will make it so you have to tap "Run" when you start haret.
-startup.txt will cause haret.exe to automatically run instead of having to tap Run.
Now when you run haret.exe you should see some scrolling text.
Don't touch anything and let it run.
You should soon be presented with a startup animation and then be ready to setup your new Android phone.
Advanced:
Partitioning SD
Installing Ubuntu (Live CD)
DOWNLOAD UBUNTU
You should now have an .iso image.
DOWNLOAD IMGBURN
Install ImgBurn
Select "Write image file to disc"
Click on the magifying glass/folder next to where it says "Please select a file..." and select the .iso file you just downloaded.
Uncheck Verify (underneath "destination")
Click on the picture on the bottom left to burn.
Once it's burned restart your computer with the disc in the drive.
You should then see the following image:
*If you boot into Windows you'll have to consult your motherboard manual on how to boot from a CD*
{
"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"
}
Select your language and then select Try Ubuntu
Installing Ubuntu (USB)(thanks sd73ta)
I haven't tested this but you can make a bootable USB drive with Ubuntu using UNetbootin
1 - download unetbootin
2 - insert a blank usb drive
3 - select ubuntu (the highest numerical) live version and run
4 - when its done reboot your pc
when it first boots look for instructions on how to enter setup usually F2 or Delete
5 - change your startup options so usb is before hdd
6 - save changes
Now it should boot to ubuntu
Partition your SD Card
Follow my vid:
Extract the android folder to the Fat32 Partition
Install Android to Partitions
Run Haret
Pay close attention to the scrolling text.
When you see "Press Voldn to run Android Installer" press the left softkey(the key just right of the green phone button)
It should now be placing the system.sqsh onto the first ext2 partition and creating a new data.img on the second.
To see if this actually worked, when you restart your phone into Windows you should see a folder called "backupsystem" with an installedsystem.sqsh file inside.
Swap/Compcache
*WARNING: Using a swap file/partition can decrease the life of your SD Card*
To use swap/compcache you'll need to edit your *.user.conf file which can be opened using any text editor. It should be easy to follow what everything in the file does, but if you can't figure it out SEARCH FIRST and then ask.
To utilize the swap partition you'll have to change
cc_backingswap_en=0 from 0 to 1
OR
linux_swap_en=0 from 0 to 1
Very Advanced (NAND)
NAND refers to the actual phone storage (where Windows resides). This wipes Windows from your phone and writes Android to the internal storage. It's not completely developed yet, but it's getting really far really fast.
There is already a thread HERE that discusses everything you need to know about running Android from NAND.
Upgrading to different builds
Simple Install(no partitions)
Most new builds will just be a system.sqsh file. If thats the case then you'll need to replace the system.sqsh file with the new one. It's also best to delete the data.img file.
If the new build contains a zImagexx-xx-xx or rootfsxx-xx-xx.img, then you'll need to replace those too. When you replace them, make sure to rename them to zImage and rootfs.img, unless theres a new default.txt where you don't have to rename them. Make sure you READ EVERYTHING the thread says about the build so you don't ask questions that have already been asked.
Advanced Install(partitions)
Almost the same as the Simple install but instead you'll just need to place the new system.sqsh file in the android folder and then pay attention to the scrolling text. You'll want to run the installer (Voldn) and when it asks to upgrade press Voldn. You can backup your data, and I would suggest wiping the data also to prevent any bugs.
Problems & Fixes
If your screen looks like it has random dots and things dont look quite right, open the "default.txt" and change board-htckaiser.panel_type=0 to 1, 2, or 3. This depends on your device and you should try each one to get the best result.
If you close the keyboard and the screen is now stuck in landscape, go to Settings > Sound & Display and uncheck Orientation.
If you just upgraded to a new build and are getting popups about things not responding (force closes) then you probably didn't get rid of the data.img file or wipe the data partition. If you have a blank data file/partition and are still getting errors, then look through the builds thread to see if others are having the same problems and if theres a solution.
If you can't get a data connection to work, go into Settings > Wireless Controls > Mobile Networks > Access Poin Names and if there is something present, select it and make sure all the settings are correct for your carrier according to THIS LIST. If there is nothing there, press the menu key (start button) and select New APN and enter the settings manually.
*More when I can think of them.*
FAQThere's a very nice FAQ HERE
loserskater said:
Resereved just in case... maybe FAQ/etc.
Click to expand...
Click to collapse
thx for making this loserskater! i found your post through the vogue general section and the file descriptions were exactly what i needed to know.
Hey loserskater! First off great post, I followed your instructions, and unfortunately although linux initiates the boot process it halts giving me the following error: Failed to allocate the storge;
This was using the basic setup I will now try the advance setup with live cd and let you know how it goes..
-b3ck
b3ck said:
Hey loserskater! First off great post, I followed your instructions, and unfortunately although linux initiates the boot process it halts giving me the following error: Failed to allocate the storge;
This was using the basic setup I will now try the advance setup with live cd and let you know how it goes..
-b3ck
Click to expand...
Click to collapse
Sorry, I had a couple files mismatched... updating the first post now. Just tested and its working fine now.
exellent thread, im gonna link to it in my sig!!!
loserskater said:
Sorry, I had a couple files mismatched... updating the first post now. Just tested and its working fine now.
Click to expand...
Click to collapse
Awesome thanks! Downloading now, I'll let you know how it goes =)
...
So far so good, I am looking at the ANDROID animation right now, so quick question since I am running this from an exe from the windows mobile os, is windows mobile still running in the background while I am using the ANDROID part, or does it completely shut down windows and load up the linux os, just wondering.. thanks.
...
Everything works great still can't get the 3G part working but I read somewhere that is because the tilt uses a different MHz than t-mobiles 3G, dunno if I can get it to work or not.. any ideas?
-b3ck
So what androids can I use with my HTC Tilt? yours works great, can I use just any of the ones I find on the 2 other forums you liked to in your post?
-b3ck
Great (and much needed) thread, loserskater - THANKS.
I have simple question: just how is the correct *.user.conf file selected? Is there a selection mechanism in system.img, or is there some other mechanism?
Thanks again for the partitioning walkthrough. And Ubuntu 9.10 is pretty darn nice, too!
b3ck said:
So far so good, I am looking at the ANDROID animation right now, so quick question since I am running this from an exe from the windows mobile os, is windows mobile still running in the background while I am using the ANDROID part, or does it completely shut down windows and load up the linux os, just wondering.. thanks.
Click to expand...
Click to collapse
When you run Haret, it wipes Windows from memory so it's not running anymore, (although it keeps it on the actual phone storage) then it "reboots" the phone into android. So think of it like this... Windows is on the phone storage and Android is on the SD card. Haret shuts down Windows (keeping it on the phone storage) and then boots up the phone using the SD card in place of the phone storage. When you turn the phone off/reset it will boot back into Windows. (added to first post)
b3ck said:
Everything works great still can't get the 3G part working but I read somewhere that is because the tilt uses a different MHz than t-mobiles 3G, dunno if I can get it to work or not.. any ideas?
Click to expand...
Click to collapse
Look in the second post under problems & fixes and make sure you're APN settings for your carrier are correct. I have 3G and I'm on AT&T.
b3ck said:
So what androids can I use with my HTC Tilt? yours works great, can I use just any of the ones I find on the 2 other forums you liked to in your post?
Click to expand...
Click to collapse
Look in Kaiser Rom development or the Vogue General forum for builds. Follow my upgrading procedure and you should be OK. If you're having problems with that build look through the thread and see if others are using different zImages, rootfs.img's, etc.
wanderso said:
Great (and much needed) thread, loserskater - THANKS.
I have simple question: just how is the correct *.user.conf file selected? Is there a selection mechanism in system.img, or is there some other mechanism?
Thanks again for the partitioning walkthrough. And Ubuntu 9.10 is pretty darn nice, too!
Click to expand...
Click to collapse
Look in the first post under How it works. (just added)
Yes Ubuntu is a very user friendly and popular version of linux. It was my primary OS for awhile and didn't have any problems with it. The best part is if you mess something up, you can just reinstall the OS and start over.
I use unetbootin instead of a live cd. this creates a live usb drive.
1 - download unetbootin
2 - insert a blank usb drive
3 - select ubuntu (the highest numerical) live version and run
4 - when its done reboot your pc
when it first boots look for instructions on how to enter setup usually F2 or Delete
5 - change your startup options so usb is before hdd
6 - save changes
Now it should boot to ubuntu
hope this helps. I havent done this in a while so if I missed something let me know and I'll fix it
Thanks for your help, very much appreciated!
Your the man!!!!!!!!
Thank you sir for this great tutorial!!!! it was the diff between me using android and me wanting to never try it again.
Thanks for great instructions!
I don't know what I did wrong, but the "Voldn" installer did not copy my system.img to the first partition. Only after I manually copied the content I was able to boot.
Question: how big the first partition should be? The system.img is only 74Mb, but all the related to the subject demos suggest to create a 256Mb ext2. Is not it a waste of space on a 2Gb sdcard?
zc2 said:
Thanks for great instructions!
I don't know what I did wrong, but the "Voldn" installer did not copy my system.img to the first partition. Only after I manually copied the content I was able to boot.
Question: how big the first partition should be? The system.img is only 74Mb, but all the related to the subject demos suggest to create a 256Mb ext2. Is not it a waste of space on a 2Gb sdcard?
Click to expand...
Click to collapse
You can use two 128 MB partitions to save space. You just don't want to get too small or you'll start having issues
I tried to install Android on my htc touch and it comes up with "Launch a script file. Default path is the same where the executable lives." What do I need to move and where to get it to work? Thanks
Thanks for the answer.
I made 128Mb and 269Mb. After I reboot my Tilt I found the Home and the Green Call button do not work anymore! And some other system settings were changed as well.
I had to run the instaler for three times before I finally got the system working.
This is great!
Could someone alternately host the Starting_Point file please? I have tried to download it multiple times and it doesn't complete ever.
Does anyone else have data access issues? I am unable to get any data with this build
vexersa said:
Does anyone else have data access issues? I am unable to get any data with this build
Click to expand...
Click to collapse
check the second post under problems and fixes (last one)
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?
In the last few days I've had a cascading series of issues with my Evo, and things keep popping up. Can anyone help me figure out what may be going on?
It began with my phone "losing" the SD card in the middle of daily use. Eventually I formatted the SD card and put my backed up files on it, and everything seemed fine.
I had been experimenting with Go Launcher, and wanted to return to Launcher Pro, so I flashed my themed update - built off of Myn's Warm TwoPointTwo themed Launcher Pro. I've flashed this a number of times with no issues, but this time - nothing happens.
So I DL Launcher pro from the Market, THEN flash Launcher Pro. All I get is the stock Launcher Pro, no matter what I do. So I go poking.
I find out that my /Data folder is completely empty - despite the fact that the themed update puts com.fede.launcher.apk into /Data/Data/App. But there's NOTHING in /Data, and no subfolders.
Finally, I reboot into recovery and run "fix apk ui mismatches", but the recovery hangs up right after saying it's done doing that. I have to pull the battery, and when I reboot, I get perma-stuck at the Whitescreen.
So I Battery out/in, and go into recovery, re-run fix apk ui mismatches, and this time it goes smoothly. Except that when it reboots, I get cascatding apk FCs immediately.
So I go to Nand, and every Nand I flash just gives me a whitescreen.
Finally, I load the PC36IMG.zip onto my sd card, but before I hit "update" (which UNROOTED my phone last time I did that, but at least restored it), I decide to reflash the Rom I've been using.
Reflash, reboot, everything looks peachy. Reflash all the other stuff I normally flash (which includes no new files that I haven't regularly used before, and no new Kernels), and then get to trying to use the phone normally.
Now here's the thing: all my recent data is still there. But on about half of the apps I try to run (including XDA, Gmail, Internet, and Dolphin HD) it begins to open and then immediately closes.
Does anyone have any idea what may be going on, and what I can do?
Thanks.
MDM
MadDogMaddux said:
In the last few days I've had a cascading series of issues with my Evo, and things keep popping up. Can anyone help me figure out what may be going on?
It began with my phone "losing" the SD card in the middle of daily use. Eventually I formatted the SD card and put my backed up files on it, and everything seemed fine.
I had been experimenting with Go Launcher, and wanted to return to Launcher Pro, so I flashed my themed update - built off of Myn's Warm TwoPointTwo themed Launcher Pro. I've flashed this a number of times with no issues, but this time - nothing happens.
So I DL Launcher pro from the Market, THEN flash Launcher Pro. All I get is the stock Launcher Pro, no matter what I do. So I go poking.
I find out that my /Data folder is completely empty - despite the fact that the themed update puts com.fede.launcher.apk into /Data/Data/App. But there's NOTHING in /Data, and no subfolders.
Finally, I reboot into recovery and run "fix apk ui mismatches", but the recovery hangs up right after saying it's done doing that. I have to pull the battery, and when I reboot, I get perma-stuck at the Whitescreen.
So I Battery out/in, and go into recovery, re-run fix apk ui mismatches, and this time it goes smoothly. Except that when it reboots, I get cascatding apk FCs immediately.
So I go to Nand, and every Nand I flash just gives me a whitescreen.
Finally, I load the PC36IMG.zip onto my sd card, but before I hit "update" (which UNROOTED my phone last time I did that, but at least restored it), I decide to reflash the Rom I've been using.
Reflash, reboot, everything looks peachy. Reflash all the other stuff I normally flash (which includes no new files that I haven't regularly used before, and no new Kernels), and then get to trying to use the phone normally.
Now here's the thing: all my recent data is still there. But on about half of the apps I try to run (including XDA, Gmail, Internet, and Dolphin HD) it begins to open and then immediately closes.
Does anyone have any idea what may be going on, and what I can do?
Thanks.
MDM
Click to expand...
Click to collapse
On the surface, two things come to mind : Virus and bad RAM. Make no mistake about it, I'm only speculating. If you don't mind, can you flash one of the stock roms and see if you have the same problems? You can download one from here: http://shipped-roms.com/shipped/Supersonic/ If you still have those issues using a stock rom, then it's safe to assume a hardware problem (bad RAM is my guess). If you find that those problem disappear with the stock rom then I would start from scratch when reinstalling RLS 5 and that includes reflashing the radios. I wouldn't leave anything to chance.
OK, I'm DLing one of the stock ROMs you linked to. I notice they're all .exe files. How do I go about this?
MadDogMaddux said:
OK, I'm DLing one of the stock ROMs you linked to. I notice they're all .exe files. How do I go about this?
Click to expand...
Click to collapse
Do NOT install or run the .exe after you finish downloading. I have not noticed that they were executables. Let me find another link for you for a 3.70 RUU zip.
Here you go: http://www.mediafire.com/?t7u904lm502vl7l
OK, that seems to let me run things normally. So I guess I'll assume that all the .zips on my SD card were corrupt and begin downloading/flashing new everything.
Weird, how Stock looks fresh and new since it's been so long since I've used it.
Thanks DJ!
Not sure if this is still part of the problem, or what.
I flashed the Warm TwoPointTwo themed Launcher Pro update, but it doesn't show up anywhere, and when I go to /Data, there's nothing in the folder at all.
MadDogMaddux said:
Not sure if this is still part of the problem, or what.
I flashed the Warm TwoPointTwo themed Launcher Pro update, but it doesn't show up anywhere, and when I go to /Data, there's nothing in the folder at all.
Click to expand...
Click to collapse
Have you tried using adb push instead?
If you're flashing it and it's not installing into the data/app folder then it's possible it's not actually being flashed properly.
I could send you a launcherpro apk that I use (the most recent one) but it has some lingering themeing effects in it.
You could use it for troubleshooting as far as installing goes. I have installed it myself many times. LMK.
Thing is, my /Data folder is completely empty. Is that right?
Additionally, it's an update that I've flashed before without issue - so why would it stop flashing correctly?
Come to think of it, I HAVE tried adb pushing it - it still shows up as empty in /data
MadDogMaddux said:
Thing is, my /Data folder is completely empty. Is that right?
Additionally, it's an update that I've flashed before without issue - so why would it stop flashing correctly?
Come to think of it, I HAVE tried adb pushing it - it still shows up as empty in /data
Click to expand...
Click to collapse
It sounds like you are looking in the wrong data folder. It's possible.
Can you take a screenshot of the directory you are looking in with some sort of visual indication of the directorys actual location in the structure?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is everything right above /data, at the same folder level as /system. /data is the next entry listed right below /d. Opening up the update.zip, it drops the .apk in /data/app
Sent from my little black box using XDA App
MadDogMaddux said:
This is everything right above /data, at the same folder level as /system. /data is the next entry listed right below /d. Opening up the update.zip, it drops the .apk in /data/app
Sent from my little black box using XDA App
Click to expand...
Click to collapse
Assuming that what you say is true (that your /data folder is empty) then the next logical explanation is that your data partition is jacked.
That in itself is amazing because if that is the case it's a wonder that your phone is even operating at all.
Have you tried formatting your partitions (boot, system, data) and reinstalling another rom (preferrably "stock like" rooted roms that don't use any type of sd scripts [a2sd])?
I haven't tried formatting Data, no....I assume I can do that from Recovery or HBoot?
Flashing the stock ROM that dougjamal linked me restored the functionality of my phone - and I think a2sd is optional on Warm, and I haven't set that up.
MadDogMaddux said:
I haven't tried formatting Data, no....I assume I can do that from Recovery or HBoot?
Flashing the stock ROM that dougjamal linked me restored the functionality of my phone - and I think a2sd is optional on Warm, and I haven't set that up.
Click to expand...
Click to collapse
Get a hold of calkulins "format all" zip and flash that.
If you flashed a stock rom and it restored your functionality then the possibility exists that the stock rom restored your data partition.
a2sd is not the only possible cause of your problems. Basically anything that moves system files to the sdcard has the potential of messing up your system which is why i don't use any of them anymore. The dalvik2cache script is another possibility. It doesn't move the files to the sdcard but it does move the dalvikcache out of its default location and app makers don't take into account all the modifications that can be done to the devices (really they shouldn't have to anyways) and so will always install extra files to their respective default locations.
If you need more space I suggest going the route of reallocating the partition amounts over moving everything to your sdcard.
MadDogMaddux said:
OK, that seems to let me run things normally. So I guess I'll assume that all the .zips on my SD card were corrupt and begin downloading/flashing new everything.
Weird, how Stock looks fresh and new since it's been so long since I've used it.
Thanks DJ!
Click to expand...
Click to collapse
You're very welcome, my friend. I'm glad you got it up and running. In regard to how the stock rom looks, lol, I can believe it. I would definitely feel the same way since I rooted and flashed Myn's RLS 3 days after purchasing my EVO...laughing...Anyway, take care and enjoy your day.
lovethyEVO said:
Get a hold of calkulins "format all" zip and flash that.
If you flashed a stock rom and it restored your functionality then the possibility exists that the stock rom restored your data partition.
a2sd is not the only possible cause of your problems. Basically anything that moves system files to the sdcard has the potential of messing up your system which is why i don't use any of them anymore. The dalvik2cache script is another possibility. It doesn't move the files to the sdcard but it does move the dalvikcache out of its default location and app makers don't take into account all the modifications that can be done to the devices (really they shouldn't have to anyways) and so will always install extra files to their respective default locations.
If you need more space I suggest going the route of reallocating the partition amounts over moving everything to your sdcard.
Click to expand...
Click to collapse
Cool, I've got Calk's Format_All on my lappy already, but I think i'll DL it again just to be safe.
OK, so I flashed Calk's Format All, and then reflashed the ROM that DougJamal had me flash previously listed in this thread.
Result?
MadDogMaddux said:
OK, so I flashed Calk's Format All, and then reflashed the ROM that DougJamal had me flash previously listed in this thread.
Result?
Click to expand...
Click to collapse
I just noticed your toolbar at the top of the image.
I am assuming (from memory) that you are using astro to view that folder.
If that is the case, astro is your first problem because it can't properly access and show the system files.
You would need to use root explorer to view the data folder. It is a paid app but you get what you pay for.
If you don't want to pay for it you can use terminal emulator and run these commands.
su<enter>
cd data<enter>
ls
After those commands you should have a list
backup, tombstones, system, agent, wimax, dalvik-cache, drm, property, etc.
You should see in that list "app".
Do the command
cd app<enter>
After that command you should see a whole bunch of "com.xxx" filenames. Those are your user installed apps.
Report your results.
LOL!!
Well, every now and again, it is good to be reminded that I'm a moron.
I didn't even think to question whether or not Astro could view that directory, as I remembered viewing it on my phone before.....now I'm realizing that I viewed /data with Ninjamorph. Here's my screenie.
Sent from my little black box using XDA App
MadDogMaddux said:
LOL!!
Well, every now and again, it is good to be reminded that I'm a moron.
I didn't even think to question whether or not Astro could view that directory, as I remembered viewing it on my phone before.....now I'm realizing that I viewed /data with Ninjamorph. Here's my screenie.
Sent from my little black box using XDA App
Click to expand...
Click to collapse
So we have established that your data folder does in fact exist.
What are your problems now?
I'm home early now so if you have gtalk pm me your gtalk name and I can try to help you more.
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
WARNING! THE BELOW PROCEDURE IS A ONE DIRTY HACK.
PLEASE READ CAREFULLY BEFORE PROCEEDING AND AS ALWAYS BACKUP YOUR FILES. IF YOU HAVE ANY DOUBT, YOU KNOW YOUR WAY OUT.
YOU ARE CHOOSING TO MAKE THE MODIFICATIONS. I WILL NOT BE HELD RESPONSIBLE FOR ANY LOSS OR CORRUPTION OF YOUR DATA AND ANY MISBEHAVING OF YOUR DEVICE.
ALSO PLEASE DON'T REPORT BUGS TO THE DEVELOPER OF THE APP BEING USED HERE. THE APP WAS NOT DESGINED TO BE USED THIS WAY AND MAY NOT WORK AS EXPECTED.
Hello, everyone, i was just fiddling with many tools that increase memory size, which basically is move the files to external sdcard one way or another.
Most of these solutions required to have a second partition, and so does Link2SD, but i liked Link2SD interface, and wanted to find a way to use it to create links without having to partition my sdcard at least in real, so i began testing commands in the terminal emulator and finally found a way to do so.
This does not require to format or touch the partitions, just a file is created on the sdcard which will hold all the apps. While this is nothing but a simple mounting of a somewhat virtual filesystem it works for me.
And the best part is the file size can be increased or decreased by simply typing two commands, so within few minutes you can make room for more apps or your other files.
The only limitation being the filesystem that can't handle < 4gb files.
But hey if you don't have that big sdcard, or don't need that much space for apps, then you are good, right?
If your sdcard is bigger than 8gb then you are good with a partition. but people with lesser size of sdcard have to choose between apps or their other files. and maybe this can somehow be helpful to them. .
Requirements:
*A non-partitoned external sdcard.
*Busybox symlinked, terminal emulator and root access
*Any kernel with init.d and ofcourse ext4 support
*Any rom should work, I'm using cm7.2. Just make sure other methods,scripts are not installed to avoid conflicts
*Basic knowledge of commands, and the terminal
*Oops, how could i forgot Link2SD.
Procedure:
*Backup your important files, while this method doesn't require formatting or touching partitions. I cannot guarantee anything, plus i can say that i warned you to backup your files, incase you screw up.
*Decide how much space you want for the *virtual* second partition file, although you can increase/decrease it later. It is good to allocate needed space beforehand.
After you got that going, it's time to get the hands dirty with the terminal emulator
*Open up the terminal emulator emulator and type
Code:
su
Grant it superuser access if you havent already, then you will drop to root shell "#"
We are now going to create a file, that we will use as our *virtual* second partition. Make sure you have enough needed free space for the creation of the file.
If you are familiar with how dd works, you can adjust the commands yourself.
busybox dd bs=16M count=n if=/dev/zero of=/sdcard/sdext.img
For starters, just divide the size required in mb by 16 and substitute the value of n in count.
WARNING! dd can be very dangerous , double check the command you typed, and yes, the commands are case sensitive
I will use 128mb as example: 128/16 would be 8, so i will type.
Code:
busybox dd bs=16M count=8 if=/dev/zero of=/sdcard/sdext.img
Wait for sometime, now that that will create a 128mb file named sdext.img in top folder of your sdcard.
Now we need to create a ext4 filesystem in our newly created sdext.img.
Just simply type and hit enter
Code:
mke2fs -T ext4 /sdcard/sdext.img
You will get something like, this
/sdcard/sdext.img is not a a block special device.
Proceed anyway?(y,n)
Click to expand...
Click to collapse
That is quite normal, just type "y" without quotes of course, and hit enter then wait for the creation to complete.
{
"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"
}
Journaling:
Journaling is mostly enabled by default, but it can be disabled at the creation but there's no need to, as we will be writing, when linking only. and it does not quite impact the read speed, plus it's safer to not disable. Unless you are planning to move apps data files and are going to use apps which perform heavvy I/O on their data files(the files that are in /data/data/appname), which most of the apps don't. you will be fine with journaling enabled. You can disable if you want but don't ask me how to.
That's it for the terminal part. now you can quit terminal emulator and install Link2SD if you haven't already.
Now if you open Link2SD then tap Menu, and select Storage info you will see that SD card 2nd part is not detected.
That will soon change.
The below should be pretty starightforward, and you probably have done it many times, so i won't go into details.
Download the attacted zip file put into top folder of your sdcard.
Reboot to CWM recovery. Make sure /system and sdcard are mounted.
Install the zip from the sdcard, and reboot to system.
After booting is completed, open Link2SD and check the Storage Info again. The second partition should be detected.
Wait! we are not done, yet.
First check that media scanner works, by opening gallery or camera.
Then test that the linking works, by selecting "User" filter on the Link2SD page and linking some common apps and opening them.
Now, reboot to make sure that the apps are not lost on reboot.
The above issues shouldn't hopefully happen, but we are testing it just to be sure. In any case if the above issue happens, please describe the problem clearly and don't forget to take a logcat.
After all this you can link other apps too provided that you won't come to hit me incase anything wrong happens.
Basic options works fine like creating and removing links, cleaning up, but i haven't tested them all.
Some things to consider.
You see the below screenshot.
NEVER EVER MAKE THE MISTAKE OF TAPPING "Recreate mount scripts".
It will try to detect primary second partition on the external sdcard, which we don't have and that could cause undesirable behavior.
If Link2SD is having trouble detecting the partition. dump a logcat here, and i will see what i can do.
Do not umount your sdcard.
Make sure apps like clean master don't clean itself by deleting the image file.
And it is possible to resize the image after creating it. Instructions to that will come later.
Request to linux ninjas: Please help by improving the init.d sh script used to make this work. it can be found in /system/etc/init.d/01mountsdextimg after installing.
As it currently stands it is a one big hairy mess.
Big thanks to developers of Link2SD, Android Terminal Emulator, Busybox, CWM and all others.
The countless sites on the internet where i learned most of the stuffs from.
(°_o) said:
Hello, everyone, i was..
.
Click to expand...
Click to collapse
Plz post the procedure Sir.....who r u waiting for....its like You show some sweets, and asking that you eat or not.
imElectronica said:
Plz post the procedure Sir.....who r u waiting for....its like You show some sweets, and asking that you eat or not.
Click to expand...
Click to collapse
I'm sorry, actually, i posted this right after it looked like it was working,
But then i rebooted, but the apps were lost after reboot, :0
After many hours of tweaking i finally managed to get it work somehow, but then the media scanner was broken.
So, i just let it be for yesterday, and today i managed to fix it too.
I will just edit the OP with procedure , just give me few more days hehe :cyclops:
imElectronica said:
Plz post the procedure Sir.....who r u waiting for....its like You show some sweets, and asking that you eat or not.
Click to expand...
Click to collapse
Updated the OP. Procedure is up.
(°_o) said:
Updated the OP. Procedure is up.
Click to expand...
Click to collapse
which rom u r using ?? and font ??
imElectronica said:
which rom u r using ?? and font ??
Click to expand...
Click to collapse
rom is cm7 and font is droid sans..
(°_o) said:
rom is cm7 and font is droid sans..
Click to expand...
Click to collapse
rom link plz...is there any bug
@op : after flashing zip file , Link2SD didnt detect second partition.
i'm using CM7.2rc4 based Reincarnation V6
kevin_tn said:
@op : after flashing zip file , Link2SD didnt detect second partition.
i'm using CM7.2rc4 based Reincarnation V6
Click to expand...
Click to collapse
did you follow the steps correctly?
and please upload a logcat
(°_o) said:
did you follow the steps correctly?
and please upload a logcat
Click to expand...
Click to collapse
sorry i can not take a logcat.
i'm using angpyshar kernel , and Pure Performance X script.
any conflicts ??
kevin_tn said:
sorry i can not take a logcat.
i'm using angpyshar kernel , and Pure Performance X script.
any conflicts ??
Click to expand...
Click to collapse
you can just open terminal emulator.. drop to root shell with su
and type
logcat > /sdcard/log.txt
it will keep going, just close the terminal emulator..
and upload the log.txt anywhere..
i cannot say anything for sure without logcat..