App2Sd Causes phone to not boot. HELP!!! - Desire Q&A, Help & Troubleshooting

Hi I just rooted my phone using a method from another website ( not sure if i can post the website as that is xda-developers policy.. )
It rooted fine and it loaded back and i could use my phone.
Then I try to install app sd, i follow a guide to the letter, and once it rebooted it just gets stuck at the htc white screen. I've been waiting for 10 minutes and nothing loads. Is it bricked? I can still go into bootloader or whatever but how do i get it back? Is it the SD card?
I'm using a 8GB sdhc card Kingston Class 4. If it has to do with anything. What do i do? I really need to use the phone!!!

What rom did you install?
Does the rom you have not already have Apps2SD integrated? (check thread title of rom and change log notes to find out)
Are you able to get into Recovery Mode?
If you did not flash a Froyo only (not Sense UI) rom, did you forget to partition your SD card before rebooting?
Sent from my HTC Desire using XDA App

i install whatever rom that came with the package of rooting from android.modaco.com. I don't knwo what it is but i'm guessing its some 2.1 rom.
No i think the roms was used jsut for rom, so i dont' think app2 sd is integrated. I am able to get into recovery mode, but don't know what to do it from there.
I actually partition the sd card and did the ext2 to et 3 and after it finished i rebooted and it just get stuck on this screen. What i did now is install a custom rom on it and it boots. However I want to load back just the htc rom that came with the root package and add Apps 2 SD

On MoDaCo, there should be an option to download a custom 2.1 based rom that already includes A2SD in the downloads section. Try downloading that rom, in Recovery Mode, do a full wipe, flash the rom, and while still in Recovery Mode, partition your SD card with 0 MB swap, ext2 size of 512 MB, rest to FAT32. Then convert ext2 to ext3.
If you still have the same issue, report back here bud.
Just make sure it is a 2.1 based rom that you are attempting to flash with A2SD. If it is a 2.2 Froyo based rom without Sense, then you do not partition your SD card at all as it is setup differently.

does your sd card have an ext partition? if your using an apps2sd with a dalvik cache script, your fone wont boot without a ext partiton because your fone has nowhere to put the dalvik cache lol

Thank to the two of you for your help. I was planning to use 2.1 as I only wanted a2Sd because i ran out of space very easily installing apps and games.
Anyways i wipe and install the official froyo sense one from adamg from here in the desire forums. Now i'm confused, he saids he has google's app2 sd, legacy app2 sd, and davlik cache app2 sd..
Can u guys explain the differences? What is app 2 sd+ ??
I understand google's one is the one that comes with froyo that it only works if the developers of the games and apps code it in, or else it wont' move to the sd card. Legacy is the one which uses the ext3 partition ( which i still have btw.. ) but i don't know how to use that one even though its already preinstalled. I have no idea about davlik cache except that i had to clear it before i install app2sd.. and i'm in the blind for a2sd+ ...
Thanks

I read somewhere minimum class of sd should be 6 for apps2sd. Also had a freeze once, i panicked then took battery out, went into recovery and just re-installed ROM and it worked after that.

@Supergluey basically, a2sd just moves the apps, while a2sd+ also moves the dalvik cache.
The Froyo implementation is pretty lame (only moves apps if allowed by creator) and is best ignored.
If your rom comes with the legacy a2sd (not Froyo native) then you can partition your sd card in Recovery Mode by setting a 0 MB swap size, an ext2 size (dedicated for apps) of 512 MB, and remaining space to the FAT32 file system (mass storage space).
You then convert ext2 to ext3 while still in Recovery Mode.
Explanation about how Dalvik cache works: when Android OS starts up, the DalvikVM looks through all of your applications (.apk files) and frameworks, and builds a tree of dependencies. It uses this dependency tree to optimise the bytecode for every application and stores it in the Dalvik cache. The applications are then run using the optimised bytecode. This is why when you install a new ROM, sometimes it takes a very long time to boot for the first time. Any time an application (or framework library) changes, it's re-optimised and the cache is updated.
Sent from my HTC Desire using XDA App

MasDroid said:
@Supergluey basically, a2sd just moves the apps, while a2sd+ also moves the dalvik cache.
The Froyo implementation is pretty lame (only moves apps if allowed by creator) and is best ignored.
If your rom comes with the legacy a2sd (not Froyo native) then you can partition your sd card in Recovery Mode by setting a 0 MB swap size, an ext2 size (dedicated for apps) of 512 MB, and remaining space to the FAT32 file system (mass storage space).
You then convert ext2 to ext3 while still in Recovery Mode.
Explanation about how Dalvik cache works: when Android OS starts up, the DalvikVM looks through all of your applications (.apk files) and frameworks, and builds a tree of dependencies. It uses this dependency tree to optimise the bytecode for every application and stores it in the Dalvik cache. The applications are then run using the optimised bytecode. This is why when you install a new ROM, sometimes it takes a very long time to boot for the first time. Any time an application (or framework library) changes, it's re-optimised and the cache is updated.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Thanks MasDroid. I get the differences now. But i have a problem. So like my last post I install the official froyo rom that is posted on here by AdamG. I loved it cause its based off some hong kong test rom and i'm in HK However, he added more features to it such as the apps to sd (not the froyo one ) and davlik cache app to sd.
I formatted my 8GB with the swap file , fat 32 and ext 2 converted to ext 3 respectively to the sizes you stated. However whenever i install apps it still goes to the internal memory! I tried different partitions and it still doesn't' work! I tried wiping everything and re-flashing the rom and it doesn't' work. I also tried forcing it to install to external but all apps just fails to install. I tried reformat and remove all partitions and re partition again once through recovery mode and another through the android sdk and using adb. Is it the sd card problem?
When i first rooted my phone, with defrost and then later changing to devillian. It worked. Apps were installed on sd card but i changed roms because i found out it was dragging the internal memory as well. So i would still gt the "I have no space" message. What can I be doing wrong?

ruisinho said:
I read somewhere minimum class of sd should be 6 for apps2sd.
Click to expand...
Click to collapse
Definitely not true.
I use Apps2SD on my 16gb Sandisk Class 2 card and never have any lag whatsoever.
Regards,
Dave

foxmeister said:
Definitely not true.
I use Apps2SD on my 16gb Sandisk Class 2 card and never have any lag whatsoever.
Click to expand...
Click to collapse
+1
16 gig Sandisk class 2, absolutely no difference or lag comparing to internal memory

Related

[Q] Can't make apps move to SD card

Heya,
Today I flashed a fresh Defrost 6.1a (Which is said to support A2SD+), Flashed Gapps. So far so good.
I took my 8GB SD card and partitioned it in Ubuntu using Gpareted. I set the FAT32 partition first, then a ext3 partition (512MB) second.
Ubuntu read both with accurate sizes.
I put the card back into the phone and looked "SD card & phone storage", it no said my SD card is only 6.89GB, but the Internal phone storage was still low.
I decided to check a little more with Titanium Backup, which surprisingly said that my ext3 partition is only 256MB and is half full (talking about a fresh ROM here).
Can someone point me to where I did wrong?
Maybe format using ext4?
Put the ext partition first?
Reflash ROM after partitioning?
TNX
I have never got A2SD working either. I think you need to install a script or something. Here is a post about A2SD. Also, Android 2.2+ supports moving apps to SD anyway.
If you want more space to install apps, you can install one of AlphaRev's HBoot templates which can increase the /data partition, that's if you have S-Off.
I couldn't be bothered farting around with A2SD and so I did that instead.
CoreOxide said:
Maybe format using ext4?
Click to expand...
Click to collapse
No, it will not make it work and will only increase your memory card's wear.
CoreOxide said:
Reflash ROM after partitioning?
Click to expand...
Click to collapse
So you flashed the a2sd enabled ROM on the device which didn't have memory card prepared? I always thought such enterprises would end in a boot loop. Flash it again if this is the case.
GoogleJelly said:
Also, Android 2.2+ supports moving apps to SD anyway.
Click to expand...
Click to collapse
It is not teh same thing!
erklat said:
How do you inspect if a2sd is working? Coz I think u r doing it wrong. Install Quick system info and check what it says under a2sd storage and if it slowly decreases when you install apps, which means it is working. You don't have to set default install location anywhere, the script does that for you.
What you are referring to here, is Froyo's built-in a2sd which requires the app to be optimized for app2sd, that's why only some of your apps seem to be on the SD card. Furthermore, it will transfer the apps to FAT32 partition, that you don't want for it to do since Android first loads apps which need to be loaded at startup, and afterwards it mounts the SD card, which will lead to some apps failing to start after boot.
a2sd tricks the phone into thinking that ext partition is it's internal memory. Froyo app2sd != a2sd script, don't confuse those two, they are not the same.
Click to expand...
Click to collapse
Sent from my HTC Desire using Tapatalk

Ext3

Hi.
I'm in a dilemma here trying to.fimd out what is wrong. I formatted and partitioned my 4gb SD card to work with App2sd+ by making 3gb Fat32 Primary and First Partition and 1gb EXT3 Primary, however whenever apps are installed they tend to use the First partitioned instead of the reserved 1gb partition I had created.
Maybe I have done something wrong, since I am quite new to App2SD and how it works, but know the basics. I would appreciate your help.
Thank you
Sent from my HTC Desire using crappy XDA App.
You must flash a rom with a2sd+ support. It's different from the built in support for a2sd, which can be found in the stock froyo roms and above.
Flash Darktremor Apps2SD for Desire in recovery and then use A2SDGUI from the Market to change settings as you like. After that do not manually move apps around. They should me installed to the internal storage which then will be your sd-card.
I failed to metion that I am using Teppic's 'Pre-rooted Stock Froyo (2.29.405.5)' ROM with the optional addon 'App2SD+' so I presume it should work fine
However, I am thinking it has something to do with the app I have installed 'Move2SD Enabler' which I think is moving everything to the External Fat32 partition'.
Can someone confirm?
Deeco7 said:
I failed to metion that I am using Teppic's 'Pre-rooted Stock Froyo (2.29.405.5)' ROM with the optional addon 'App2SD+' so I presume it should work fine
However, I am thinking it has something to do with the app I have installed 'Move2SD Enabler' which I think is moving everything to the External Fat32 partition'.
Can someone confirm?
Click to expand...
Click to collapse
yes it could be, i wondering the same things about the app2sd with my first flash with custom's rom and ap2sd+ (i uninstalled this app).
to be shure that your sript ap2sd+ is working fine you can brouwse your phone and go to system/sd you should see 4 folders... app + app-private +lost-found and dalvik-cache (for the last folder it's assumed that your script got the little "+" which means that is moving the dalvik cache to your ext partition)
hope this would help you
Another idea to see if a2sd+ is working like it should is to download Quick System Info. When you launch it you should see a line with a2sd info. If it is there then a2sd+ is ok, and you can see how much of you ext3 1GB partition is used.
I used the rom manager to make the partitions, then I format them with MiniTool.Partition.Wizard.Professional.v5.2-REDT when needed, you can resize them as needed ... you can download it at rlslog.net
Wow... Is it really time for another "how does x type of app to sd solution work?"
It really is quite simple:
Froyo a2sd uses a folder on the fat32 and the system controls, where the apps is installed, and where they are moved to.
a2sd+/legacy a2sd uses the ext-partition by symlinking the folders /data/apps and /data/dalvik-cache to this partition. This solution is transparent to the system itself, so as far as the android system is aware the apps is installed internal. This means you can use widgets from apps on this partition, and it also means that your apps will allways be installed here, so you cannot move them to internal. You will also not see the extra space, your apps will just not take up as much space when installed.
If you like you have done move the apps to sd through the froyo settings, you actually just move them from the ext-partition to the folder on the fat32-partition.

[Q] a2sd problems on ICS

Hey,
I've been using ICS (beta 0.4.2.1 now, beta 0.3.9 previously) and none of the a2sd scripts seem to be working. I tried to use the one you have to activate through adb, and today when I updated to 0.4.2.1 I chose another one from the installer. My phone still reports 148 MB of internal storage...
I've had a thorough search of similar threads, but you know how difficult it is to find any meaningful information on this forum; can someone please point me in the right direction? Thank you!
I flashed ICS and installed the bundled a2sd script and it worked like the script on Insertcoin. That is the system still displayed the data partition size of my hboot but the SD ext4 partition was utilised for apps. If you have titanium backup you can see the data usage on the home screen.
I also flashed amarullz script. This script did change the reported internal memory to my SD card partition size. I did not use it long so I can't comment on how it runs on s class 4 SD card.
Sent from my HTC Desire using XDA
You did not understand how A2SD works. It moves all apps (with A2SD+ also dalvik-cache) you install automatically to an EXT-partition (some of their data still remain in internal memory). But it does not increase / decrease the size of internal memory.
If you want to change the size of internal memory, you have to use a script which moves the whole /data-partition to an EXT-partition. The size of this partition is then the size of your internal memory. The name of this scripts is DATA2SD / DATA2EXT.
Sent from my HTC Desire using Tapatalk
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
Did you ever get a fix for your problem?
I have something similar. Was running 0.3.9. and decided for a couple days ago to upgrade to a newer edition. Wiped data/factory reset, wiped cached and dalvik-cache, and installed the new version.
Used stock everything, activated a2sd and tried to start and install some apps from google play. Got a message that it was not sufficient space.
Did get titanium installed, and that reports the different "drives" correctly, but I still don't get it to work as it should. If I try to install from play, it says not sufficient space, even if I try to restore from titanium, still no luck.
Anyone got any ideas?
Start Terminal. Type:
su
a2sd install
yes (move dalvik-cache)
no (don't move appdata) (yes will make device slower)
yes (restart)
After reboot you have more space, but don't see it.
Start terminal
su
a2sd diskspace
gives the size of your sd-ext and how much is used
arsvendg said:
If I try to install from play, it says not sufficient space, even if I try to restore from titanium, still no luck.
Click to expand...
Click to collapse
Same problem here. I tried to wipe caches and even recreated the partitions but still no luck with the stock a2sd.
robla1000 said:
Start Terminal. Type:
su
a2sd install
yes (move dalvik-cache)
no (don't move appdata) (yes will make device slower)
yes (restart)
After reboot you have more space, but don't see it.
Start terminal
su
a2sd diskspace
gives the size of your sd-ext and how much is used
Click to expand...
Click to collapse
Just wondering. Isn't the whole idea with the as2d to move the appdata to the sd-card?
arsvendg said:
Just wondering. Isn't the whole idea with the as2d to move the appdata to the sd-card?
Click to expand...
Click to collapse
App and appdata are different things:
The App it's the "core" and are loaded in the RAM when you start them, so if you move them to sdcard you get a slowdown only on the boot of the app itself
The Appdata it's the data created and used by the program to run, likes databases and so; if you move it to the sdcard you get a slowdown 'cause the program continuosly try to access it.
someone correct me if I'm wrong, i'm still learning the stuff
Long story short: normal A2SD+ methods (like DarkTremor or m2sd) only move a part of /data, linking the files; you will NOT see the increased space but your Apps will occupy less memory.
Data2sd method like data2sd or Amarullz A2SDX will "swap" the ext space with the internal data memory, giving you a visible increase in your internal space.
TL;DR if you have a fast SD card you can go for the latter, else stick to m2sd wich is a new and good method to move application!
For partitioning, I suggest you to use 4ext touch recovery, you can install it on your phone from 4ext.net and flash your new recovery directly from your phone (you need to have S-OFF!); after you have your new recovery flashed:
make a backup of your SD card data (you have to format it)
Reboot in recovery
Go to "Tools"
"partition sd card ->"
"Remove all partitions and start from scratch"
Now you have to set, in order, you primary ext dimension, your secondary ext dimension and the swap dimension
I usually go for - 1st ext: 1024 -2nd ext: 0 - swap: 0
Select ext4 for your first ext partition
Now you are ready to use wathever a2sd method you want.
Hope this will help you!
Regards,
Ryther
Ahh I'm just going to leave this here.
All the ICS Devs have done a great job - Kudos to them.
But if you want a bugfree ROM which works well, for now - GIVE UP on ICS.
Go back to CM7 - it'll do you good.
Don't give up on ICS because SOME people have issues. I've ran an ICS build with a2sd working just fine no bugs whatsoever. I have not tried a data2ext script on an ICS build though so I don't know about that.

[Q] Internal Memory Full after Reboot; All Apps on SD

My HTC Desire was restarted due to low battery long after I restored some backups (app + data) with Titanium Backup. When I booted back into Android, it showed 1MB of free internal space! So thought it might be the 4 downloads I had, so I deleted all of them and Android then said it had 61MB of free internal space.
Then I rebooted but now I only have 216KB free space!!
This is the second time it's happened and I've tried everything including SD Maid and every single app is linked to the SD card's 2nd partition. This didn't happen when Installing apps from the Play store or from Easy Installer; and Avast finds no problems.
It keeps saying "Unfortunately Google Play Store has stopped" etc. and the phone is very slow including booting.
I'm not willing to re-flash everything again and manually install each app, especially as the first time re-flashing, Clockwork Recovery said it couldn't mount the SD card, then after formatting, Windows 7 wouldn't recognize it, then neither would (after formatting using gparted)!
I'm only using Link2SD on ICS for HTC Desire 0.4.4.4.1, default HBoot, Clockworkmod Recovery Touch 5.8.0.2, aGPS and default homescreen with no scripts.
This is extremely irritating, can anyone help please?
Using any scripts like A2SD?
Cool story bro. Please post more relevant information so peeps here can help you out. How about letting us know your hboot information, rom you are currently using, scripts etc. ;-)
I'm only using Link2SD on ICS for HTC Desire 0.4.4.4.1, default HBoot, Clockworkmod Recovery Touch 5.8.0.2, aGPS and default homescreen with no scripts.
DarkIceGB said:
I'm only using Link2SD on ICS for HTC Desire 0.4.4.4.1, default HBoot, Clockworkmod Recovery Touch 5.8.0.2, aGPS and default homescreen with no scripts.
Click to expand...
Click to collapse
try stock a2sd then enable it with terminal
Code:
su
a2sd install
y
y
y
Edit: also DL 5.1, i found 4.4.4.1 SUPER buggy.
Thanks for the help, I've tried the above and it's been booting for 10 minutes now, should I wait for it to finish or is it stuck?
Edit: After 30 minutes of booting, I took the battery out. It now won't go past booting (the animated 'X screen') and it takes ages to get past the 'HTC' screen to the boot screen.
Edit 2: I booted into recovery and cleared all caches and fixed permissions and after booting it doesn't say the memory is full! Thanks for your help!
What else did it move and is the data on the first partition of the SD card or the second and can I remove the SD card safely? Any idea how the internal memory was filled and why there were issues with the SD card or if they might appear again? It's a new Samsung Extreme Speed Class 10 16GB Micro SDHC card.
I can't move apps from the SD card to the SD card's second partition or to the internal memory. It says, "pkg: /mnt/asec/appnamehere/pkg.apk Failure [INSTALL_FAILED_INSUFFICIENT_STORAGE]".
The internal memory is empty, the SD card has 8GB of free space and the 2nd partition has 1GB free out of 2GB.
Just upgraded to 5.1 and it's the same as above. Any ideas?
Anyone have any idea?
What A2SD-option did you pick in Aroma Installer? I cannot see any Link2SD option there.
Sorry I meant I chose the built-in a2sd but I used this app called Link2SD as I have a second partition on my sd card for apps.
DarkIceGB said:
Sorry I meant I chose the built-in a2sd but I used this app called Link2SD as I have a second partition on my sd card for apps.
Click to expand...
Click to collapse
How have you partitioned your SD? Primary and secondary FAT32 or primary FAT32 and secondary EXT? I've never used Link2SD 'cause i prefer the script way, but i think it works the same way.
If you are using EXT for secondary, i recommend you the 4ext recovery, if you are S-OFF you can install it directly from the phone using the Updater form 4ext.net.
Then I suggest you to do:
A nandroid backup
A backup of your SD data
Repartition you SD using 4ext
Check partition allignment with 4ext
Do a full wipe
Restore your SD's backup
Restore your nandroid backup
Re-install 0.5.1 and select built-in a2sd
In rom use terminal like bortak stated, but say NO to moving appdata (slowed down my phone a lot)
Uninstall Link2SD
This will give you a standard installation for a2sd.
If I were in you, i would format everything (except SD card first partition) and start from scratch with the built-in a2sd method without Link2SD; you'll have to reinstall everything and lose every data (backup with TB if you can), but you are sure to run a rock solid method to "enlarge you space"
If you are on double FAT32... well, i cannot help you there
Bortak, correct me if i ever say stupids things i want to help out and you surely are a master in troubleshooting and point to my errors
I'm actually running BCM 3.0U0 + 3.0U1 update with m2sd (with apps and dalvik on ext), 100% V6 supercharged and ScrollingCache patched... i have to say, in my opinion, it finally surpassed Sandvold ICS!
Thanks a lot for the help, I've followed the steps and everything's working now!
I used 4ext recovery, which appears to be a lot better than clockworkmod, with more useful options. 4etx said that the partitions weren't aligned (which I previously set in clockworkmod) so I wiped everything and made fresh partitions which were perfectly aligned. I'm using 0.5.2 now with a full format.
I had/have fat32 then ext4.
I've noticed that most apps don't appear to be on the SD card though. Any advice?

[Q] Out of space with a2sd on LaidbackNikez JB Alpha9

Hi everyone,
I've installed today the last release of LaidbackNikez JB Rom after a full wipe.
I have a sd-ext partition of 512 Mo.
I followed the install instructions and run a2sd install yny, reboot, and when I restore my apps with TB I have an out of space error.
It seems that a2sd doesn't work.
Anyone have a solution for that ?
512MB is quite small, A2SD could be working as it should, and you may have literally just run out of space...
uninstall something to make room, then install an app like 'diskusage' to browse all your partitions (can do this for any rom), you may find your ext partition full as it contains apps and dalvik-cache
i would backup your sd card, and repartition your sd with a larger ext4 partition (1 to 2GB max depending on how many apps you have), using gparted or 4ext recovery only
Not Enough Space
eddiehk6 said:
512MB is quite small, A2SD could be working as it should, and you may have literally just run out of space...
uninstall something to make room, then install an app like 'diskusage' to browse all your partitions (can do this for any rom), you may find your ext partition full as it contains apps and dalvik-cache
i would backup your sd card, and repartition your sd with a larger ext4 partition (1 to 2GB max depending on how many apps you have), using gparted or 4ext recovery only
Click to expand...
Click to collapse
I have exactly the same problem. It has been working fine since ICS Beta Rom started with 10 till 18.1, both releases of JB Pre-Alpha 7 & 8. But after upgrading to Alpha 9, I can't restore my backups tooo... I get an error "Not enough space"
Have a Sandisk 16GB Class 4 card, that was working fine till now. Also tried a Tanscend 16GB Class10 card. Same issue. I just go to settings>>Apps, I can see them on the Internal Memory only.
I've discovered on my nexus one, with a2sd yny and a tiny cache partition, that app cache is stored in the data partition. along with app data of course. This is what has caused me to run out space even though I still had plenty of sd-ext remaining.
anyone experiencing this issue will need to run the df command from a terminal or install an app that tells them the usage of each partition. if you have a large enough sd-ext, rerunning a2sd with yyy (ie. moving app data to sd-ext) should solve your problems.

Categories

Resources