Related
Hey all, been spending the past couple days searching and reading various topics on this. My G1 if you rem the post went into the looping thing which I had to wipe to have it come back up. Now I used lucids script which relinked everything yes... including the looping reboot. So started from scratch again. Was times when I DID get it to show up but root, terminal were missing afterwords, Wipe/upgrade again. Now all I have done so far is JUST moved the apps, I havent touched the cache yet. Which at least now it shows my apps installed. Now I just need the config data back (Data) to complete the setup I had again.
How would you have the G1 go back to using the SD for the cache mapping. Would you move the cache (which isnt a good idea) back to the G1 then redo? I just wanna get everything back to 100% the partitions is fine and so since it does boot fine. I just dont wanna attempt to move the cache again only for phone to reboot and wind up missing its apps again and no root support till I wipe and start over again.
I want this all back since I had my G1 since it came out, Market cache is big, which yes I can manually restore that, but I rather do it all clean in one good move.
Anyways if anyone here knows how to relink a cache without it causing issues would be great. (Also the de cache is still on internal too) I did install the img from lucid tho for booting.
No one has any ideas or insight to this one? =/
It depends on what version of app2sd u are using or I should say it depends on the ROM. If you are upgrading to a ROM that uses Marcus's apps2sd u should be fine to follow instructions below. If u are using old apps2sd, then use Lucid's script to re-link to sd card after upgrade.
Copy all files from the sd card back to the phone, upgrade, then put them back on the sd card using apps2sd
Well can I copy the cache over to the internal and so, then move them back? The apps are linked fine to the SD atm, Im using Lucids. JF 1.51 US.
The cache, what is that exactly? Is that just the user data it creates after you run the program or what.
could someoe please help me out? ive been at this for about 3 hours now. i wasnt around any computer and wanted to flash JACHero 2.3, so i downloaded it on my phone, renamed it to update.zip, wiped, and flashed it. dont have a clue why, but it just started boot looping on me. so i just figured ild wait till i get home, and format my ext 3 partition, and try again. i did that, and ever since, whenever i type in "df" into terminal, i dont see /system/sd anywhere. isnt this supposed to mean my ext 3 dosent exist? tried everything i could think of, still didnt work. so i just decided to format my SD and start all over, but still the same thing. could anyone please tell me what im doing wrong? Thanks in advance.
ive always been using apps2sd since the app came out, so its nt my first time.
also tried going the ext2 way, but its all the same. and for some reason, when i format my ext3, there's like 23MB used? anyone know why that is?
It means either you don't have an ext2/3 partition(unlikely in this case) or that the ROM you're using is messed up a bit(bad flash maybe?). I'd try reflashing the ROM since that's most likely the culprit.
23MB used is likely overhead for the file system.
ive tried reflashing the Rom a couple of times, same result.
the Rom uses an auto- apps2sd script, so, it would need access to my ext3 partition. The problem is, my phone not recognising the partition.
ok so I did a search and I didn't find a specific answer to this...
I am running dc v2.7.2 and I had a notification pop up saying I am low on space, phone storage is getting low. How Do I fix this and make the notification go away? I am running a task manager and try to keep my memory freed up but I was running slacker and this popped up. It sends me to application manager when clicked. What does it want me to do?!
I tried a reboot and deleted a few worthless apps but it is still there.
Take a moment and really think about what the error message is saying. Its very obvious and does not require much of a attention span.
Take a moment and really think about what the error message is saying. Its very obvious and does not require much of a attention span.
Click to expand...
Click to collapse
Lol I love this place.
By the way OP, A2SD ftw.
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
Tipharet said:
Take a moment and really think about what the error message is saying. Its very obvious and does not require much of a attention span.
Click to expand...
Click to collapse
thanks... I understand the simplicity of the message. I can't clear the notification though. that is the issue. I have tried the deleting stuff but still there.
josh_131 said:
thanks... I understand the simplicity of the message. I can't clear the notification though. that is the issue. I have tried the deleting stuff but still there.
Click to expand...
Click to collapse
How much internal memory and ram do you have?
Try to download a cache cleaner from the market... Or wipe your dalvik cache in the recovery screen. It will take awhile to boot up, but should help.
Also if you dont use a2sd, try it out.. I install most of my apps on my sd and ones I use daily or hourly on my system. Just to keep heavy use off my sdcard.
Jus10o said:
How much internal memory and ram do you have?
Try to download a cache cleaner from the market... Or wipe your dalvik cache in the recovery screen. It will take awhile to boot up, but should help.
Also if you dont use a2sd, try it out.. I install most of my apps on my sd and ones I use daily or hourly on my system. Just to keep heavy use off my sdcard.
Click to expand...
Click to collapse
hmmm so there is another issue... from recovery I get an error everytime I try to wipe dalvik.
I try to run about 50-80M ram(almost never below40) and my internal memory shows available internal shows 15.01MB
josh_131 said:
hmmm so there is another issue... from recovery I get an error everytime I try to wipe dalvik.
I try to run about 50-80M ram(almost never below40) and my internal memory shows available internal shows 15.01MB
Click to expand...
Click to collapse
it tells me error : Run 'wipe dalvik' via adb!
but I tried adb and it didn't seem to work either...
josh_131 said:
hmmm so there is another issue... from recovery I get an error everytime I try to wipe dalvik.
I try to run about 50-80M ram(almost never below40) and my internal memory shows available internal shows 15.01MB
Click to expand...
Click to collapse
Try to flash this in recovery.. It wont delete or mess up your rom.
It should just wipe dalvik
View attachment _2__update1.zip
I would also delete apps that you dont use that are in your system/app
Type
adb remount
adb shell
cd /system/app
ls
It will show all your apps..
Type this to remove ones you dont use.. Maybe Stock.apk
rm Stock.apk
It is case sensitive.
Jus10o said:
Try to flash this in recovery.. It wont delete or mess up your rom.
It should just wipe dalvik
View attachment 310301
Click to expand...
Click to collapse
sweet... well I just booted to recovery to try to wipe dalvik and then failed.
got you message about the zip for wiping it... tried to reboot and now stuck in bootscreen! grrr
whew! battery pull got it up and going.... gonna try the above steps
Thanks for the help so far!
josh_131 said:
sweet... well I just booted to recovery to try to wipe dalvik and then failed.
got you message about the zip for wiping it... tried to reboot and now stuck in bootscreen! grrr
whew! battery pull got it up and going.... gonna try the above steps
Thanks for the help so far!
Click to expand...
Click to collapse
You can toggle usb mode in recovery. You can put it on your sdcard without ever having to boot up your phone.
I updated the script.. so get the new one.
View attachment _2__update1.zip
get the following error when running .zip
E:Synax error in update script
Installation aborted.
josh_131 said:
get the following error when running .zip
E:Synax error in update script
Installation aborted.
Click to expand...
Click to collapse
tried the updated script.... still get the same error.
josh_131 said:
tried the updated script.... still get the same error.
Click to expand...
Click to collapse
Uhh try this one..
I think the 2nd one I posted was same as first.
View attachment update.zip
josh_131 said:
hmmm so there is another issue... from recovery I get an error everytime I try to wipe dalvik.
I try to run about 50-80M ram(almost never below40) and my internal memory shows available internal shows 15.01MB
Click to expand...
Click to collapse
...15mb below 40 is the alert set. thats why.
how do i rectify this?
josh_131 said:
how do i rectify this?
Click to expand...
Click to collapse
I would partition your sd card.. And use a2sd. It moves most of your apps to your sd card, to save alot of memory.
Make a back up of all your stuff on your sdcard to a folder on your computer. Then use the recovery screen to partition your sdcard to ext3.
All of the main system apps your phone uses will stay on your internal but all of your downloaded apps from the market go to your sdcard.
well my phone won't reboot... I tried doing a wipe and nothing... guess I will try flashing a previous dc rom and see if that works but I think I may have a brick now
josh_131 said:
well my phone won't reboot... I tried doing a wipe and nothing... guess I will try flashing a previous dc rom and see if that works but I think I may have a brick now
Click to expand...
Click to collapse
If your phone turns on it's not bricked. What do you mean it won't boot? What is it doing?
flipzmode said:
If your phone turns on it's not bricked. What do you mean it won't boot? What is it doing?
Click to expand...
Click to collapse
You were correct it wasn't bricked. It was just stuck on the bootscreen. It would do the boot animation and just stick and not make it to the the home screen, just was looping the last .gif image...
I ended up doing a wipe and was able to get to come up. Lost all my info but I now have a working phone and realize I need to manage my memory a little better.
Thank you all for your help and suggestions. Greatly appreciated! I will be trying to partition my sd and hopefully that will alleviate my internal memory issue. We shall see.
The space error has nothing to do with /system/app or your RAM. It's internal storage, which is the /data filesystem.
You are running out of internal storage. You need to clear up space from /data, which can include clearing caches, uninstalling programs, using Apps2SD, etc.
Hi
During more than year of my "android on hd2 experience" I've had no problems at all. To be honest i became quite handy on this field.
recently I was using two roms daily HyperDroid-CM7 and testing NexusHD2-IceCreamSandwich Beta.
on NexusHD2 rom i install Data2SDInstaller.
and my problem started when I wanted to go back to HyperDroid.
boot animation stuck, of course i tried clk / magdlr different partition sizes always task29...without any effects. Now I tried NexusHD2 ICS 4.0.3 CM9 V1.0 , finally went through boot animation,when i saw Setup Wizard the messages appear immediately: "Unfortunetly, the process ....... has stopped" and when I click OK appears next and the next message , such as contacts, Email, calendar, etc. i thing all of the possible .. later message: Setup Wizard not responding.
And it happens on magdlr/300/5
I've read already about bad NAND blocks, and in recovery.log I did not detect any of them
I tried to run MTTY but I have a problem with drivers win7x64: - /
Does anyone know what's wrong with my HD2 and how to solve it.
you remembered to wipe the sd-ext partition and .android folder (cwm - wipe data / factory reset) right?
there are folders on both sd-ext and on the fat32 partition that will screw with new installs.
samsamuel said:
you remembered to wipe the sd-ext partition and .android folder (cwm - wipe data / factory reset) right?
there are folders on both sd-ext and on the fat32 partition that will screw with new installs.
Click to expand...
Click to collapse
Like he said, you need to wipe your sd card, ext and fat32. Both parts. This is majorly important since you used Apps 2SD!!
Another thing, I think your system size is way off. 200/5 for cLK if not 180/5 and for magldr probably like 200/44 but at least 10mb of cache..
I'm not too sure if this will help or not but this is my experience.
I have been on these forums for a while and using Hyperdroid for quite some time now as well. The reason why I do not have any posts on this account is because I switched over just today, my old account was imarte068.
When trying to update my Hyperdroid the other day through magdlr I encountered an issue. No matter the partition size or sd-card, it always managed to get stuck on boot. I got frustrated and attempted to re-flash countless times. After many attempts I gave up and just used an MIUI rom.
Several days later I devoted myself to solving the issue. After about an hour or so of trial and error I fixed it. I simply re-flashed the kernel after the installation of the rom. I am using magdlr therefore I do not know if the process will be the same for clk.
Hope I could be of help.
I thought it was a sdcard and i delete all partition and make it new.
I do always full wipe and dalvic...
QuRa said:
I thought it was a sdcard and i delete all partition and make it new.
I do always full wipe and dalvic...
Click to expand...
Click to collapse
Try re-flashing the kernel as I said in the post above.
Link to kernel here.
Hope I could be of help.
This may spur some argument, but in my experience task 29 is the key if you're having problems. many people say wipe with cwm the system boot davlik cache, etc but in my testing when I'm having a problem and need to solve it task 29 has been the answer almost everytime. Partition size is huge as well. Another thing if you were using apps2 SD on ics it was bugged. Without formatting your SD it is possible that it could bug your system.
Sent from my HD2 using xda premium
http://forum.xda-developers.com/showthread.php?t=1326217
In this thread you can find complete guide for install rom written by me. If that fails contact me for further solutions. Good Luck
kylew1212 said:
Like he said, you need to wipe your sd card, ext and fat32. Both parts. This is majorly important since you used Apps 2SD!!
Another thing, I think your system size is way off. 200/5 for cLK if not 180/5 and for magldr probably like 200/44 but at least 10mb of cache..
Click to expand...
Click to collapse
Im using 220 with 5mb cache. ICS running smooth without any problems. And no need to fully wipe sdcard. Would be stupid to delete the whole card just for flashing a new rom hehe. Its enough to wipe the (dalvik) cache and sd-ext partition via CWM.
For data2sd use the 'how to' from post #207 and the flashable file from post #174 in tytungs ics cm9 v1 thread. I think it removes old app2sd or data2sd scripts. Worked without any formatting of my sdcard.. works like a charm.
Btw.. ever tried to fix permissions? First thing you should try if you get FC.
Just do (re)install the rom like the guy in post #207 described but with the file from #174 (40ad2sdx-a2Recovery.zip)
And im using my hd2 now for more then one year. NEVER used task29.
Hf
Edit: btw for problems with your Usb? Driver on win7 machines try to install new version of WMDC (windows mobile device center)
Solved the problem for a friend
Sent from my NexusHD2
redplate said:
Im using 220 with 5mb cache. ICS running smooth without any problems. And no need to fully wipe sdcard. Would be stupid to delete the whole card just for flashing a new rom hehe. Its enough to wipe the (dalvik) cache and sd-ext partition via CWM.
For data2sd use the 'how to' from post #207 and the flashable file from post #174 in tytungs ics cm9 v1 thread. I think it removes old app2sd or data2sd scripts. Worked without any formatting of my sdcard.. works like a charm.
Btw.. ever tried to fix permissions? First thing you should try if you get FC.
Just do (re)install the rom like the guy in post #207 described but with the file from #174 (40ad2sdx-a2Recovery.zip)
And im using my hd2 now for more then one year. NEVER used task29.
Hf
Edit: btw for problems with your Usb? Driver on win7 machines try to install new version of WMDC (windows mobile device center)
Solved the problem for a friend
Sent from my NexusHD2
Click to expand...
Click to collapse
As I said people will disagree. I will say that in most cases you're right though, wiping the davlik cache is enough. I am just saying from my personal experience there are sometimes when it isn't (at least on my phone). I'm not trying to start an argument, I just want to help him.
Sent from my HD2 using xda premium
big thanks mates for advice.
So far I haven't had time for it but for sure tomorrow or on the weekend, I will deal with this and I will let you know how it goes.
In brief I run ICS all fine, but HyperDroid not starting.
Here is how i try:
________
Ok I was using WP7 and whats I made:
SD card: I delete all partition, I make only one Fat32 than in CWM I made ext partition.
Task29 > Clk 200/5 > recovery > install HyperDroid-CM7-v5.7.0 > And here phone stuck before boot animation, only white android robo > then as flamgodian advice I install kernel thins. > Same without boot animation.
Second try
Task29>clk 220/5>recovery>wipe(all possible)>install HyperDroid-CM7-v5.7.0>same robo>fix permision> install kernel this> I saw robo for 10s and phone self reboot after reboot > stuck :/
I have not seen even the boot animation.
Task29>clk 220/5>recovery>wipe(all possible)>install NexusHD2-ICS-CM9>Kernel>
He goes
__
I make like redplate(Big Thanks) write with installation 40ad2sdx, and everything runs great.
I will stay with ICS but it is strange why my phone doesn't like HyperDroid Rom.
And from here I would like to thank you all for advice.
I've been experiencing the dreaded "Low Internal Memory" problems on my HD2 running a MIUI GB ROM.
I was told this was because the included A2SD, well, sucks. I was advised to use Data2EXT instead. Since I wanted to start with a clean slate anyway, I decided it was time to completely wipe my HD2 and install everything anew. This is what I did:
Wiped the HD2 with Task29 (using the HD2 Toolkit)
Installed ClockworkModRecovery v1.3 150MB (I wasn't sure I actually used the 150MB version when I initially installed CWM Recovery)
Cleared data/cache with CWM Recovery
Reformatted the 1GB sd-ext partition on my SD Card (using MiniTool Partition Wizard)
Installed ROM with CWM Recovery (from zip)
Installed A2SDKiller scripts (from zip)
Rebooted phone into MIUI, but did not install anything.
Rebooted into CWM Recovery and installed the Data2SD Installer.
Rebooted into MIUI again
It seemed everything was fine. If I looked at my memory usage, instead of only 210 MB of total storage I had previously, I now had almost 1GB. I setup my Google account and started to install some apps. Somewhere along the line one of the apps hung the phone so I rebooted it again.
But when it was done rebooting, much to my surprise all installed apps were gone. In fact, the phone was behaving like it was the first time it was started (asking me for my Google credentials again, etc). At first I thought this was perhaps due to the hung app, so I did all the above steps again (including wiping the phone).
Again I installed a few apps, and this time I rebooted the phone to check if all was OK now. It wasn't. Again the phone behaved like it was the first time I booted into the new ROM and all installed apps were gone. I've tried about 5 times now and every single time with the same results.
So what could be wrong here?
just a thought (i havent checked, you can do that) but what type of ext did you create? ext2? ext3? ext4? perhaps data2sd (you called it data2ext in the title, data2sd in the post, , ,which is it? they're probably different) doesnt play nice with whichever one you created?
Hi, and thank you for your answer.
samsamuel said:
just a thought (i havent checked, you can do that) but what type of ext did you create? ext2? ext3? ext4?
Click to expand...
Click to collapse
Ext3.
perhaps data2sd (you called it data2ext in the title, data2sd in the post, , ,which is it? they're probably different) doesnt play nice with whichever one you created?
Click to expand...
Click to collapse
I'm pretty sure they are the same (since took the installation procedure from this forum post and they call it both Data2Ext and Data2SD).
I will check to see if the filesystem matters. Thanks!
I just checked and ext3 should be fine.
Zippy1970 said:
I just checked and ext3 should be fine.
Click to expand...
Click to collapse
Check to see see if there's any script left from old method in system/etc/init.d
This is a complete guess but worth a try
EDIT: this is the script that the A2SD killer removes from system/etc/init.d
delete("/system/etc/init.d/40a2sd");
delete("/system/etc/init.d/03stuff2sd");
delete("/system/etc/init.d/10apps2sd");
delete("/system/etc/init.d/04apps2sd");
delete("/system/etc/init.d/01data2whatever");
delete("/system/etc/init.d/98zipalign");
delete("/system/etc/init.d/02cachedalvikcache");
So make sure that has been removed then try flash the new zip file
Sent from my GT-I9100 using xda premium
wis1152 said:
Check to see see if there's any script left from old method in system/etc/init.d
So make sure that has been removed then try flash the new zip file
Click to expand...
Click to collapse
Yes, all those files have been deleted.
It seems to be working now. I wanted to test if changing the Ext3 partition to Ext2 would make any difference so I fired up MiniTool Partition Wizard again. I wiped the partition and formatted it as Ext2.
Or so I thought.
The partition still said it was Ext3. Then it hit me. I had forgotten that you actually have to "Apply" the changes, which I hadn't done before. So I clicked Apply and it wiped the partition and actually formatted it as Ext2.
I then redid the whole thing (install ROM & A2SDKiller scripts, reboot into ROM, reboot into CWM Recovery and installed Data2SD). And now it seems to be working fine.
Not sure which of the two actions on the Ext partition caused it to start working: the wipe or the change to Ext2.
I spoke too soon. I thought it was working since a reset didn't clear all my installed apps. But if I look at the total storage space, it's back to 216MB total. So it looks like Data2Ext isn't running...
*SIGH*
I'm just about to give up on Data2Ext. First of all, I thought I had figured out what was wrong. For some odd reason, whenever I tried to write to my 16GB microSD card on my computer using an SD adapter, it would crash every now and then. Also, partitioning through MiniTool Partition Wizard often resulted in a "Bad Disk" error. I tried this with 3 different 16GB microSD cards. All experienced the same problems when using an SD card adapter (it wasn't a broken SD adapter because I've tried several).
I then dug up an old external microSD USB card reader I had laying around. Using that, I was able to write to the microSD cards just fine and I didn't experience any problems partitioning either.
Speaking about partitioning, it took me a while to figure out that:
Partitioning through ClockWorkMod Recovery doesn't work properly. The FAT32 partition becomes incredibly slow, and the Ext partition is not recognized by Data2Ext
Ext3/Ext4 partitions don't work with Data2Ext. At least, not on my phone
Ext2 partitions only work if they are set as the primary partition
You must name the partition sd-ext or it will not work
Just a FYI for anyone finding this thread in the future.
Anyway, once I figured that out, I was finally able to get Data2Ext working. Sort of. Let me try to explain.
Previously after I had installed Data2Ext and setup some apps, a reboot of my phone would bring it back to a factory reset state. So all installed apps were gone, just like any settings I had altered. Oddly enough, if I looked at the sd-ext partition I could see the data was still there. It simply wasn't used by the phone. But after I had partitioned the sd-ext partition as Ext2, all was fine. A reboot didn't reset the phone back to factory settings.
So I happily reinstalled all my apps, restored my SMS as well as my WhatsApp backup and thought all was fine now. But I did notice the phone wasn't very stable. Every now and then it would become unresponsive for 10-20 seconds. Sometimes I got an error message that a certain app had become unresponsive and I was offered a choice to either shutdown the app or to wait. And sometimes, the phone would spontaneously reset itself.
Today the phone again became unresponsive. Oddly enough, long-pressing the power button did bring up the shutdown window. So I tapped "Shutdown". Next, the phone hung on "Shutting Down". It didn't come back to live. So I removed the battery lid and pressed the reset button.
After it had rebooted, I was greeted with a factory reset phone again. I was about to throw the phone through the window! But when I did another reboot, all my apps were back again as well as my settings. Except for the settings of my individual widgets. Those had all disappeared for some reason. Also, I got quite a few error messages that some apps had stopped unexpectedly. I rebooted again and again the phone behaved as if it were factory reset. But yet another reboot brought everything back...
I now suspect it has something to do with the phone not being able to mount sd-ext every now and then. Either way, my problems aren't solved yet so any tips are much appreciated.
Zippy1970 said:
*SIGH*
I'm just about to give up on Data2Ext. First of all, I thought I had figured out what was wrong. For some odd reason, whenever I tried to write to my 16GB microSD card on my computer using an SD adapter, it would crash every now and then. Also, partitioning through MiniTool Partition Wizard often resulted in a "Bad Disk" error. I tried this with 3 different 16GB microSD cards. All experienced the same problems when using an SD card adapter (it wasn't a broken SD adapter because I've tried several).
I then dug up an old external microSD USB card reader I had laying around. Using that, I was able to write to the microSD cards just fine and I didn't experience any problems partitioning either.
Speaking about partitioning, it took me a while to figure out that:
Partitioning through ClockWorkMod Recovery doesn't work properly. The FAT32 partition becomes incredibly slow, and the Ext partition is not recognized by Data2Ext
Ext3/Ext4 partitions don't work with Data2Ext. At least, not on my phone
Ext2 partitions only work if they are set as the primary partition
You must name the partition sd-ext or it will not work
Just a FYI for anyone finding this thread in the future.
Anyway, once I figured that out, I was finally able to get Data2Ext working. Sort of. Let me try to explain.
Previously after I had installed Data2Ext and setup some apps, a reboot of my phone would bring it back to a factory reset state. So all installed apps were gone, just like any settings I had altered. Oddly enough, if I looked at the sd-ext partition I could see the data was still there. It simply wasn't used by the phone. But after I had partitioned the sd-ext partition as Ext2, all was fine. A reboot didn't reset the phone back to factory settings.
So I happily reinstalled all my apps, restored my SMS as well as my WhatsApp backup and thought all was fine now. But I did notice the phone wasn't very stable. Every now and then it would become unresponsive for 10-20 seconds. Sometimes I got an error message that a certain app had become unresponsive and I was offered a choice to either shutdown the app or to wait. And sometimes, the phone would spontaneously reset itself.
Today the phone again became unresponsive. Oddly enough, long-pressing the power button did bring up the shutdown window. So I tapped "Shutdown". Next, the phone hung on "Shutting Down". It didn't come back to live. So I removed the battery lid and pressed the reset button.
After it had rebooted, I was greeted with a factory reset phone again. I was about to throw the phone through the window! But when I did another reboot, all my apps were back again as well as my settings. Except for the settings of my individual widgets. Those had all disappeared for some reason. Also, I got quite a few error messages that some apps had stopped unexpectedly. I rebooted again and again the phone behaved as if it were factory reset. But yet another reboot brought everything back...
I now suspect it has something to do with the phone not being able to mount sd-ext every now and then. Either way, my problems aren't solved yet so any tips are much appreciated.
Click to expand...
Click to collapse
I have similiar problem before, The ext partition always failed. Now I used Extended TWRP to create the ext partition, it is stable now.
http://forum.xda-developers.com/showthread.php?t=2120297
I can't get Data2Ext to work. I'm either getting tons of force close errors, or it's not seeing the sd-ext partition at all. I tried with Ext2/Ext3/Ext4 partitions (Ext3 didn't seem to work at all). With or without a swap partition. Nothing worked.
I also tried Data2ExtV2 and even DataOnExt. The result was always a ton of force close errors and a very unstable phone.
So anyone any ideas? It sucks only having 200MB of internal storage.
Hmmmm... That's odd. I just wiped my phone again (Task29), reinstalled MAGLDR, CWM Recovery (150MB) and my ROM without Data2Ext or anything and I'm getting the same force close errors and it's telling me I don't have enough internal storage to install apps.
So apparently there's something else going on with my phone?
What ROM are you using?
Try increasing system partition size!
Sent from my NexusHD2 using xda premium
shanman-2 said:
What ROM are you using?
Try increasing system partition size!
Sent from my NexusHD2 using xda premium
Click to expand...
Click to collapse
Actually, I found out it was because I used the wrong cache size this last time. So it's not the cause of all the other problems, but most certainly the cause of the problems this last time I flashed the ROM.
Ok, I've given up on Data2Ext. I can't get it to work. No matter what I try it's incredibly unstable and slow - if it works at all.
1. Make a backup of your SDCard.
2. Download EXTRecovery here.
3. Unzip it and place the 4EXTRecovery folder in the root of your SDCard.
4. Start MAGLDR, choose option 10, then 1, then 3 and select the folder (4EXT~), then boot from SD in the MAGLDR main menu.
5. In the 4EXTRecovery go to Advanced -> Partition SD Card -> Remove all partitions and start from scratch.
6. 1st sd-ext partition: 1024MB, skip 2nd sd-ext partition, SWAP partition is OPTIONAL, I recommend 256MB.
7. Press Yes and pick: "EXT4".
8. When it's finished, choose: "Print partitiontable" to check if it's actually there.
9. If it's there, go back to the main menu and press: "Install from SDCard".
10. Locate your ROM and install it.
Goodluck.
EDIT: Oh, I just read you've given up on it.. all this work for nothing, lol.
Ohwell, maybe I'm lucky and someone else stumbles upon this and can use it.
EDIT 2: Use DataOnEXT and have a /system size of about 285MB, 300-350MB if you have Bad Blocks!
EDIT 3: Try it with: "Jellybean 4.1.2" by Tytung, definitely works!