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..
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?
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
Hey guys
This is a new update 2013.
In this update I will try to clarify the most “complicated things” with this app link 2sd
donot forget to read faq's and read the steps carefully before asking
and dont worry about your internal memory" you donot need to use titanium backup to move data"
-----------------------------------------------------------------------------------------
updated: FAQ'S to solve problems of some members:
look to FAQ's at the bottom
-----------------------------------------------------------------------------------------
The thread will contain :
1. What is link2sd and how should we benefit from it.
2. Link2sd requirement s.
3. What not to do.
4. What to do in regular basis
-----------------------------------------------------------------------------------------
{
"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"
}
1. What is link2sd and how should we benifit from it.
Link2sd is an app that using a partition on the sd card to link all your apps to it, in other words it is convincing the phone that it has a larger memory so you can install hundreds of apps.
when you are linking your app files by “creating link” it won’t take any space from the device memory so you can by creating a second partition install apps as much as you want without concerning about memory.
The benifit from link2sd :
*More apps to install
*using apps while you are in storage mode “usb mode”.
---------------------------------------------------------------------------------------
2.Link2sd requirments:
Here will be many sections, if you already done or don’t need what is in any section skip it to the next one.
Note: your phone must be rooted.
Note: section A is only for stock roms.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Update section A is obsolete but iam keeping it here if any one wanna to root or convert the system to ext4, so donot waste your time in section A.
If
If you are not rooted yet, follow this toturial [Tutorial]How To Root and Unroot Samsung Galaxy Ace official Gingerbread 2.3 updgrade by gganon
Then go to android market update super user and update the binary “if necessary I will upload the ScreenShots later”
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Remember you donot need this, skip it donot waste your time and go to section B.
A. “Here you have to get CF-Root on your device
Or activated superuser “ check it by using for example root explorer, titanuim backup etc...”
install CF-Root by ketut.kumajaya
first install CF-Root-S5830-v3.7-b84.zip (12.55 MB)
By flashing it by recovery
install super user from market Link
then install ext4 as any usual apk
and open it
after that go to CWM and select flash kernel
and flash thisB84.zip.”
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
B. If you have any a2sd scrpits or a2sd gui you have to delete it.
Iam not sure about the method, once i get it gonna post it.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
C. Partition your sd-card:
Simplest way is to use "MiniTool Partition Wizard Home Edition" from http://www.partitionwizard.com/download.html
This tool is compatible with Windows 2000/XP/Vista & Windows 7
requirements: USB SD Card reader.
pull SD card from phone, insert into USB SD Card reader. Windows should report new drive and content of the drive should be visible.
• step 1: delete old partitions on SD card
Note: this partition manager QUEUES the operations. So nothing is deleted and changed UNTIL you click "APPLY" and then confirm by clicking "OK".
WARNING!
Make sure you are deleting partition on SD card! (not your hard drive for example)
This step deletes everything on SD card, so backup files first!
Dont be afraid, just read everything and think twice before selecting correct drive.
Do you see three gray icons on the bottom? Under each of them the capacity of each drive is listed, and SD CARD has slightly different icon.
Hard drives on the screenshot have 465.8GB and 74.5GB, and on the bottom, the SD card, with 3.8GB capacity.
• step 2: create FAT or FAT32 partition “ note that this partition is for storing your media, etc..”
select "Create As": PRIMARY
Select "File System:" FAT when you have 2GB or smaller card.
Select "File System:" FAT32 when you have 4GB or greater card.
• step 3: select the 2nd partition and select "Create As": PRIMARY
NOTE:
Stock roms with stock kernel will support fat32
Stock roms with custom kernels “ like CF-Root” may support both fat32/ext4 “check their threads”
Cm7/cm9 roms will support ext4
Here Is a NOTE:
For a wired reason, in both cm7/cm9 roms if formatted your 2nd partition with ext4 format, link2sd wont create mount script, unless you have selected ext3 “although the format was converted to ext4”
• step 4: finish
finally, click "apply" button on top left corner.
partitions will be created and card will be formatted.
Reattach your sd card to your phone and turn it on.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
D. Now use root explorer and copy the attached file to system/app
Give it the permissions rw-r-r.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
E. open it, then there will be a popup window, select fat32, ext3,ext4 “as you have formatted your 2nd partition”
Here Is a NOTE:
For a wired reason, in both cm7/cm9 roms if formatted your 2nd partition with ext4 format, link2sd wont create mount script, unless you have selected ext3 “although the format was converted to ext4”
then reboot
after reboot open link2sd
click filter and select user
then menu, multi select , select all, or select the apps you wanna to link
menu actions, create link,
tick all the options
leave it, it's gonna take about halfan hour linking your apps to the new partition
after completion you will see
at the bottom of your app " linked > sd"
then
click menu, settings auto link,
tick them all
-----------------------------------------------------------------------------------------
3. What not to do:
Please everyone avoid to do anything mentioned down there, am telling you after experience.
1. Do not ever wipe dalvick cache by cwm or any recovery
Even a developer thread told you to wipe, don’t even think to wipe dalvick cache through recovery
You will get troubles.
if you by mistake thinking that you are genuis and wiped the dalvik cache from recovery, or you have red in a thread to do so
Whenever you boot up, you will get memory full, so open link2sd :
Menu>more>link dalvik chache, reboot, then repeat it untill you see all your
apps
then link library files and reboot for two time at least
2. In the newer version of link2sd if you wiped dalvick cache, there is a new option which is “link application files” select this option then reboot.
-----------------------------------------------------------------------------------------
4.Everey couple of days:
1. relink library files
2. relink dalvick cache
3. cleanup 2nd partition
4. cleanup dalvick cache
5. cleanup app chache
6. select all apps and create link.
7. relink application files “NEW ver.”
NOTE:
When there is an update available for link2sd, update it first then update the other apps
-----------------------------------------------------------------------------------------
FAQ's:
1. I think i cant use link2sd because i have a2sd
well iam using themyth ace which is a modified stock rom with a2sd script
but link2sd is working fine with no problems
REMMEMBER
if you have a fresh flashed rom, it might work so don't enable d2sd script form twaeks app " which provided by ROM's developers"
Click to expand...
Click to collapse
2. I have this error message
mount script cannot be created
mount: invalid argument
try using differrent partition types such as ext4
if the problem still there
*try ext3
*reinstall linksd
*reboot
try these steps with ex3,ext4,fat32
Click to expand...
Click to collapse
3. I have this error
" mount: mounting/dev/block/vold/179:2 on /data/sdext2 failed: device or resource busy.
"
try full wipe
Click to expand...
Click to collapse
4. I have tried all these solutions no clu?
try differrent ROM
Click to expand...
Click to collapse
5. Q:
Originally Posted by D3molitionMan
Hi, followed you original post to the point where, your asking to copy a file,
D. Now use root explorer and copy the attached file to system/app
Give it the permissions rw-r-r.
I can't seem to find the file you are referring to, please could you help me out also i'm not sure how to set permissions correctly.
Thanks in advance
D3molitionMan
This step is merely to install the link2sd app as a system app instead of a user app.
The attached file is link2sd.apk given at the end of the post, look it up.
You are supposed to use any root explorer and paste this app in the directory system/app and then change the app's permissions to rw-r-r-.
Before pasting the app change the mode to read-write instead of read-only. There should be a button or an option in the settings in your explorer to do that.
Look for r/w or r/o symbols.
example of rw-r-r- permissions=>
http://forum.xda-developers.com/show...1&postcount=11
Then reboot and the app will be installed.
Thanks “ayush29k”
Click to expand...
Click to collapse
6. what is the difference if I can move apps to sd from system?
The diff. is that when you move app to sd there are many problems, which are:
1. Not all the app moves to sd, there will some parts from it in internal memory.
2. If you wanna to use your mass storage all apps will be unavailable till you disconnect from pc.
3. Some apps which requires syncing like facebook whenever you restart your phone your synced contacts will be gone.
Click to expand...
Click to collapse
7. use titanium backup to move data to SD….
Link2sd is much better try then judge
Click to expand...
Click to collapse
8. will my data cover the internal memory overtime?
No, unless your second partition is full
Click to expand...
Click to collapse
Updated on 9/25:
If you cannot link your apps:
press on the first icon from the left and select
"ON INTERNAL"
then link those Apps, after that
chose "On SD Card"
then link them"
Couldn't take a screen shot
Click to expand...
Click to collapse
for those guys who PM me:
punitthereddevil said:
Hi there...M using link2sd for 4mths now...and I found that the data of tha apps is still being stored on the internal memory...for example Facebook...it creates a lot of data...n nearly 25mb s occupied in d int memory...I have 2 clear it from the app manager...n every time I do it,all d settings in the app are reset...its irritating to login everytime I open fb...and due to low space in internal,m unable to download larger apps from the market...can u tell me how to get around this...?
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
i didn't get you!
but if you linked the app via link2sd all apps, the data supposed to be linked as well
rahulnandwani said:
I have heard that apps dont work with fat32 but with ext2 on stock firmware kernal ....
Is it true
Sent from my GT-S5830i using xda premium
---------- Post added at 02:57 PM ---------- Previous post was at 02:53 PM ----------
Also can i use the same tutorial for galaxy ace s5830I
Sent from my GT-S5830i using xda premium
---------- Post added at 03:37 PM ---------- Previous post was at 02:57 PM ----------
http://forum.xda-developers.com/showthread.php?t=1795410
I have used for app2sd how can i disable it because i uninstalled it too but the preffered location is still even after factory reset
Sent from my GT-S5830i using xda premium
Sent from my GT-S5830i using xda premium
Click to expand...
Click to collapse
1. didn't face any problem, actually i dont think so either.
2. yes you can! on any device
3. hmmm have no idea, why not using link2sd instead?
---------------------------------------------------------------------------------------
Now for those who are talking about updating superuser or superSU
yes it can be updated, and linked, it will appear in updated list in link2sd app.
-------------------------------------------------------------------------------------------
am sorry for not following this thred, that's because am a normal user, all my answers will
be based on "if i have faced that problem or not"
so am sorry again!
Thats all
Thank for every body who thanked
And thanks for ketut.kumajaya for the cf-root.
partitioning source : Link
NO THANKS ???
Press thanks if helped it will take just one sec :laugh::good::fingers-crossed: and rate the thread
Any q’s are welcomed
This week i will add FAQ’s
Please guys keep this thread active.
I will prefer link2sd app
regards,
•ƒγяύs ργяσ™•
pyronia said:
I will prefer link2sd app
regards,
•ƒγяύs ργяσ™•
Click to expand...
Click to collapse
it is for link2sd
eraser0 said:
it is for link2sd
Click to expand...
Click to collapse
Haha...sorry, didnt see it earlier...
regards,
•ƒγяύs ργяσ™•
basically this is a tutorial for newbies of how to partition your sd and use link2sd. It will help new users, nice!
Basically link2sd is better than s2e. Why? Because it lets you decide which apps to move on sd-ext and secondly does not move the app's data on sd cause that slows down the phone. This is also stated on s2e instructions so if any of you use s2e DON'T MOVE DATA TO SD-EXT.
From personal experience and lots of testing you shouldn't move the following apps on sd-ext:
1. Launchers
2. Widgets (but moving widget's themes on sd-ext is ok)
3. Apps that run in the background such as Google Maps, Go SMS, Go Keyboard, etc...
4. Themes for theme chooser
If you move any of these on sd-ext won't mess up your ACE but it will slow it down or give you more lag.
Is fat32 faster then ext2/3/4 partition?
Sent from my GT-S5830 using xda premium
itasoulas said:
basically this is a tutorial for newbies of how to partition your sd and use link2sd. It will help new users, nice!
Basically link2sd is better than s2e. Why? Because it lets you decide which apps to move on sd-ext and secondly does not move the app's data on sd cause that slows down the phone. This is also stated on s2e instructions so if any of you use s2e DON'T MOVE DATA TO SD-EXT.
From personal experience and lots of testing you shouldn't move the following apps on sd-ext:
1. Launchers
2. Widgets (but moving widget's themes on sd-ext is ok)
3. Apps that run in the background such as Google Maps, Go SMS, Go Keyboard, etc...
4. Themes for theme chooser
If you move any of these on sd-ext won't mess up your ACE but it will slow it down or give you more lag.
Click to expand...
Click to collapse
YUP may be it is for newbies
but it is better than a2sd
yup you are right about ur moving launchers etc..
but we wanna more memory
about widgets ia have beutiful widgets linked and no problem
gengi said:
Is fat32 faster then ext2/3/4 partition?
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
not because of speed
the reason is that you may experience some problems with ext2/3/4
so it is safer and easier to use fat32
Eror make partitions ext4 on SDcard whit link2SDK. ..
Sent from my GT-S5830 using XDA Premium App
de.rach29 said:
Eror make partitions ext4 on SDcard whit link2SDK. ..
Sent from my GT-S5830 using XDA Premium App
Click to expand...
Click to collapse
Link2sd its not to create partitions.
Sent from my GT-S5830 using xda premium
Or here's an EASIER method,
1. Create partition with CWM
2. Use S2E to move everything to that partition
Completely empty internal storage with 100+ apps installed with NO RISKS OF BRICKING PHONE or doing ANYTHING wrong.
hi. newbie here.. i follow the instruction and made it... thank for useful info tut... can i use freeze funtion menu to freeze the sys app like email , map , etc that i dont use tosave the ram beside delete it?. regard
kolej said:
hi. newbie here.. i follow the instruction and made it... thank for useful info tut... can i use freeze funtion menu to freeze the sys app like email , map , etc that i dont use tosave the ram beside delete it?. regard
Click to expand...
Click to collapse
yes you can delete it
by using root explorer
go to system/ app
mount rw
select and delete
but make sure you back it up
about freezing i dont know
actually i didn't try it
Cwm make partitions SDcar ext3, not ext4 ,I must Cheng ext4 Mini partition via windows. .thank 4 u reply. ..
Sent from my GT-S5830 using XDA Premium App
Thanks for a good guide(my first post)
Thanks alot helped bu I would also prefere the app
BTW:This realy makes a 32GB SD come to work
Oops a lost noob
Hi
i get lost by "important
now you have to move link to sd by root explorer
to system, apps"
Which files from which directory must i copy to sytem/app dir?
Thanks
gustafari69 said:
Hi
i get lost by "important
now you have to move link to sd by root explorer
to system, apps"
Which files from which directory must i copy to sytem/app dir?
Thanks
Click to expand...
Click to collapse
check it @ data/app
am gonna update the post later today or tommorrow
I now that...link2sd not make partition...but make partition via mini tool..make sconnd partition ext4 but why link2sd don't recognize parttion ext4 on sd but recognize
Ext3...
Sent from my GT-S5830 using XDA Premium App
de.rach29 said:
I now that...link2sd not make partition...but make partition via mini tool..make sconnd partition ext4 but why link2sd don't recognize parttion ext4 on sd but recognize
Ext3...
Sent from my GT-S5830 using XDA Premium App
Click to expand...
Click to collapse
i have told you to do it as fat32
because some systems get interrupt with ext4
but all systems recognizes fat32
eraser0 said:
D. Now use root explorer and copy the attached file to system/app
Give it the permissions rw-r-r.
Click to expand...
Click to collapse
Which attached file???
aditya_7298 said:
Which attached file???
Click to expand...
Click to collapse
done, file uploaded
Original throad
http://www.miui.com/thread-1141052-1-1.html
developer :__wky
{
"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"
}
【when flash choose NO 】use magldr，CLK dont have data support couse the builder dont include PPP
whats working
phone message，music voice，rotation，promission，software，GPRS，camera album…
not working
wifi ,bluetooth,.........
link
http://pan.baidu.com/share/link?shareid=383751&uk=2822129531
http://d-h.st/p7l
partation:370/5
I'm not a developer, i just ask the original builder to let me post here fro asking some help
So partition size would be 300mb +/-
zexmunze said:
So partition size would be 300mb +/-
Click to expand...
Click to collapse
370/5 I use
will give this a shot! though almost no more space would be for those using 512mb version.
translated Thread
http://translate.google.com.hk/tran...u=http://www.miui.com/thread-1141052-2-1.html
tnx
can someone reupload this rom on dev host,tried several times to download but corrupted or dl breaks
zexmunze said:
can someone reupload this rom on dev host,tried several times to download but corrupted or dl breaks
Click to expand...
Click to collapse
am uploading, please wait a lil while
Hope that you devs will bw able to produce data on ext version.
Wish all the luck!
Sent from my PIXELDROID HD2 using Tapatalk 2
new dev host link
http://d-h.st/p7l
tried 350mb partition got stuck @ gogogo
now it's booting @ 370mb partition but got stuck @ Desire HD boot screen
tried 380mb/5cache still @ boot screen
Stuck at the HTC Desire HD bootscreen too
370/5 partition and still desire bootscreen
CLK??
Does it run on clk cuz i dont use 3g?
Is it for T-Mobild HD2?
can't use this on EU HD2?
jpg3927 said:
Is it for T-Mobild HD2?
can't use this on EU HD2?
Click to expand...
Click to collapse
Can be use on EU
Thanks
Sent from my Galaxy Nexus using xda premium
has anyone got this rom to boot yet
couldn't boot it. is it normal for an initrd.gz to be 165K?
Edit: i got it to work. finally
Magldr, 370mb/5cache partitionned via hd2 toolkit
using adb shell, i mkdir /sd-ext ; and mount -t ext4 /dev/block/mmcblk0p2 /sd-ext. count in your head to 30 while jumping around.
Rom boots (after hanging forever on DHD bootanimation.)
Someone should tell us how to make it auto mount sd-ext (or tell me at least ) and upload a fix or something. I'm sorry but i'm too lazy to think about learning it.
Greetings
Edit2: i also copied framework folder back to system, although it should be installed on sd-ext partition. it probably didn't affect anything.
Edit3(bug reports): 1-Sound works, but volume is too low. with headset, sound is great
2-video in camera closes.
3-Recording app doesn't work, couldn't test microphone yet.
4-wifi,bluetooth
5-gps status states that the phone "doesn't have a compass sensor"
6-Camera works. In whatsapp, it freezes the application after taking a shot to share.
Edit4: freaking fast. and i thought 4.2.2 was fast. thanks
gilbert32 said:
couldn't boot it. is it normal for an initrd.gz to be 165K?
Edit: i got it to work. finally
Magldr, 370mb/5cache partitionned via hd2 toolkit
using adb shell, i mkdir /sd-ext ; and mount -t ext4 /dev/block/mmcblck0p2 /sd-ext. count in your head to 30 while jumping around.
Rom boots (after hanging forever on DHD bootanimation.)
Someone should tell us how to make it auto mount sd-ext (or tell me at least ) and upload a fix or something. I'm sorry but i'm too lazy to think about learning it.
Greetings
Edit2: i also copied framework folder back to system, although it should be installed on sd-ext partition. it probably didn't affect anything.
Edit3(bug reports): 1-Sound works, but volume is too low. Camera works. In whatsapp, it freezes the application after taking a shot to share.
2-video in camera closes.
3-Still to come
Edit4: freaking fast. and i thought 4.2.2 was fast. thanks
Click to expand...
Click to collapse
Thank you, when you installed the ROM I suppose you chose Tmo?
I want to but unfortunately can't try this now, I need my phone for alarms. Will try it tomorrow inshallah.
gilbert32 said:
couldn't boot it. is it normal for an initrd.gz to be 165K?
Edit: i got it to work. finally
Magldr, 370mb/5cache partitionned via hd2 toolkit
using adb shell, i mkdir /sd-ext ; and mount -t ext4 /dev/block/mmcblck0p2 /sd-ext. count in your head to 30 while jumping around.
Rom boots (after hanging forever on DHD bootanimation.)
Someone should tell us how to make it auto mount sd-ext (or tell me at least ) and upload a fix or something. I'm sorry but i'm too lazy to think about learning it.
Greetings
Edit2: i also copied framework folder back to system, although it should be installed on sd-ext partition. it probably didn't affect anything.
Edit3(bug reports): 1-Sound works, but volume is too low. Camera works. In whatsapp, it freezes the application after taking a shot to share.
2-video in camera closes.
3-Still to come
Edit4: freaking fast. and i thought 4.2.2 was fast. thanks
Click to expand...
Click to collapse
Never using adb shell before.any tutorial to install using this methode?thanks
Sent from my PIXELDROID HD2 using xda premium
gilbert32 said:
couldn't boot it. is it normal for an initrd.gz to be 165K?
Edit: i got it to work. finally
Magldr, 370mb/5cache partitionned via hd2 toolkit
using adb shell, i mkdir /sd-ext ; and mount -t ext4 /dev/block/mmcblck0p2 /sd-ext. count in your head to 30 while jumping around.
Rom boots (after hanging forever on DHD bootanimation.)
Someone should tell us how to make it auto mount sd-ext (or tell me at least ) and upload a fix or something. I'm sorry but i'm too lazy to think about learning it.
Greetings
Edit2: i also copied framework folder back to system, although it should be installed on sd-ext partition. it probably didn't affect anything.
Edit3(bug reports): 1-Sound works, but volume is too low. Camera works. In whatsapp, it freezes the application after taking a shot to share.
2-video in camera closes.
3-Still to come
Edit4: freaking fast. and i thought 4.2.2 was fast. thanks
Click to expand...
Click to collapse
mmm can u explain when to mount ext partation? I have a 512 HD2 too and i cant make it boot like Tver's hd2
Thank you, when you installed the ROM I suppose you chose Tmo?
Click to expand...
Click to collapse
i chose eu as i have the eu hd2.I think 300mb system partition should be enough for eu hd2.
Never using adb shell before.any tutorial to install using this methode?thanks
Click to expand...
Click to collapse
use search button to find out how to use it
mmm can u explain when to mount ext partation? I have a 512 HD2 too and i cant make it boot like Tver's hd2
Click to expand...
Click to collapse
i installed to eu hd2 using 370mb system partition. after showing the DHD bootanimation, phone got stuck at it. i connected to pc and used adb logcat to find out that framework files arn't loaded/cant be found. so then i mounted the sdext.
in simple, mount it after ~ 5 seconds after bootanimation ends.
More bugs in my first post. cant really reply further as i'm at school right now.
Note: you should repeat the process of mounting ext partition every time you reboot.
now something weird happened. i tried flashing dataonext initrd patcher v2. rom no longer boots (i expected that) BUT after reflashing the rom with wiping data/system/.... and installing to eu hd2, it doesn't work too! did what i say work with anyone or it's unhelpful? because i think there's something missing
I got it working again finally. after doing everything i did before (mount ext part on sd-ext, and copy everything from the framework folder in /sd-ext/sys-parts/framework to /system/framework), i used again adb to cd /system/etc/init.d and sh 40a2sd then sh 05mountext(in this order). mountext failed (resource busy) so i tried umount /sd-ext which failed for the same reason. previous errors stopped and rom booted up fine again. Fast again hopefully someone works on the rom and the installer