Related
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.
So I just traded my iPhone for a rooted MyTouch. It has the Cyanogen mod I believe. Well all of a sudden I could not access my SD card and when I tried to open it on my computer it said 'Wrong Format'. Wouldn't work on the phone either. So I formated Fat32 and thought I could start over.
It still shows my apps installed in the Marketplace, although they were on the SD and deleted. I can't uninstall them, but it thinks they are there, somewhere. Has anyone had this problem? I am relatively new to Android and rooting. I had a jailbroken iPhone before. Thanks!
kinda depends really. I would suggest first going thru recovery console if you are using amon recovery and partition sd card there. With most modified roms you have apps 2 sd so there are actually 3 partions. The biggest is fat32 for data like music, then ext2,3,4 for applications then a linux swap partition to help expand the ram on the phone and if you formated on PC or from settings on phone those partitions are gone. So I would do that first and then try to uninstall from market and reinstall again if not you may need to wipe and restart the device.
How do I get into recovery mode? I tried going to the terminal and using the flash_image recovery /sdcard/imgfile but it says I do not have permission?
Any ideas??
If your phone has been rooted right by the previous owner, you can access the recovery mode by first powering down, then pressing home and power at the same time.
Ahh! That worked! thanks!
I have a variation on this problem and lost my apps and Market, hope someone can help. Started with the SD card coming unmounted randomly, known issue with EVO I guess. Followed the recommendation of reformatting the SD by plugging it into a Windows PC and doing a FAT32 format. I backed up everything I could "see" from SD to C: drive. I am running a custom ROM with APPS2SD feature and Clockworkmod recovery. I'm very new to Linix and Android but, it looks like there is a Linix Ext3 partition that is made by APPS2SD on the SD card and that is where all my apps where, including android Market app. So, upon copying all the folders back to the re-formatted SD I had no apps and no android Market to able to re-download all my apps. I guess Market is like a licensed deal that you can't just get a .apk of and reload it. I do HAVE a current recovery backup that was on the FAT32 directory of the SD card but it appears the the Ext3 partition is not in that recovery file. I tried booting into recovery with Clockworkmod and reformatting the SD again, I tried a "Restore ext3.img" but Clockworkmod comes back with 'sd-ext.img not found" so I am guessing that the Linix Ext3 partition backup was stored IN the Ext3 partition of the SD(?) and the system and data stuff is stored in the FAT32 recovery file. Brilliant idea (not)! I tried a re-flash of the ROM, flashes OK but no apps. Anyway, the SD is properly partitioned now, the FAT32 stuff is back on, I don't know how to look in to the Est3 partition but, I know there is one program there cause I installed a file explorer by downloading and executing an .apk and there was an option to install it to SD. Going to factory reset and starting over again is not an option. Any ideas please?
SOLVED this issue:
apperantly the android market application is called "vendor.apk" and can be downloaded from various sites BUT WAIT, it's not that simple. Apperantly the vendor app has to be specific to your phone (hardware)? On a whim, I downoaded the previous version of my custom ROM (happedned to be Fresh ROM) .zip, I extracted the vendor.apk from the .zip and installed that. Then, I had an apk called MarketUpdater.apk, or something like that, that had installed in the phones system/app from the last Fresh ROM update. I ran this to update the vendor (android market) to the latest version, then I ran that. Did it work? NO, it crashed hen I tied to run market. I then did a re-boot. Did it it work? NO Upon attempting to reboot it got stuck in a loop and froze. Very scary. So, remove the battery and try again. I think I had to remove and re-install the SDcard somewhere in there to get it to a first time boot and, after a re-boot, whalla, come back with a working market. Market remembered all the apps that I purchased and I re-downloaded everything. Of course, I don't know for sure where they are stored right now (SD card or phone??)
And, my original problem of SD card constantly coming unmounted has been fixed.
Hi
for the last few hours I am trying to resolve the issue that I only today found out and after lots of testing, reflashing different roms I realized that this is a general issue and not related only to me or the rom I am using. So far tried only CM7 roms and NexusHD 3.0.
First it only happens if you have second partition on your sdcard. If you have only one fat32 partition everything works OK.
To see the issue try next:
-Enable USB Mass storage via default mount option in notification area. (issue is not present with 3rd party mount apps)
-On your computer open some folder on your SD card and remember its content
-Turn off USB Mass storage
-copy any file to that folder via any file manager app ib your phone
-Turn on USB Mass Storage and again open that folder to check for the new file (second mount lasts much longer then the first)
-File is not visible via USB mount until next phone reboot.
I have tried so far:
-HyperDroid 3 and Hyperdroid GBX v12
-Typhoon 3.6.4
-NexusHD 3.0 and 3.1a
-UltimateDroid 3.3
(all cLK)
Tried to use vold files from several other roms (MIUI and sense rom) but the issue is always there.
Also tried disabling USB debugging, changing USB ports, even PC's.
After some testing I realized that it only occurs if there is extra partition on sd. I tried ReiserFS and ext4 format, no difference. Only when I deleted all the partitions, created one and reformat it to fat32 mount was working fine.
I am currently using AdamG's a2sd modified by Seader for Hyperdroid, but while trying this on NexusHD I used Darktremor 2.7.5.2 and the issue is there.
Workaround for this is to use alternative apps for mounting. I am using Multi Mount SD-Card Lite.....
I have several people so far confirming this, on HyperDroid and Typhoon. All have partitions for a2sd.
I am not sure when this started happening. I will try tommorow some older roms but until then any information about this is helpfull. Please post if you have the issue and what rom you are on.
This is a log while mounting the USB for the second time. I see lots of vold, mount lines.
http://pastebin.com/XKUqpU56
update:
The cause of this issue is definitely a2sd. After I installed fresh rom (hyperdroid) with a2sd script removed from init.d folder USB mount doesn't have this issue.
So something is happening during mount or unmount process with active a2sd which breaks the ability of USB mount to update its file index which is sent to the computer.
This is happening with both Darktremor (tried 2.7.5.2 and 2.7.5.3. beta4) and AdamG's a2sd scripts.
update2:
this is another logcat
while mounting, checking Camera folder on a computer, unmounting, takes a picture, mounting again(this mount takes about 3 times longer then the first) and then checking the Camera folder again.
http://pastebin.com/HtqXzVx4
update3:
I found a way to stop this issue from happening. I have modified one line in vold.fstab file that is located in /system/etc
from
dev_mount sdcard /mnt/sdcard auto /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1
to
dev_mount sdcard /mnt/sdcard 1 /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1
As soon as I change 1 to auto again and reboot issue is back.
This way only the first partition (fat32) is mounted and the issue is gone. I dont know if this change can cause any other issues, but so far only thing I noticed that is different is that when you turn USB Mass storage on while connecting the phone to a linux computer it only mounts first partition and no sdext one. For me this is not important, but as I said I am not sure if this change could have an impact on stability to any part of the system or phone functionality.
So to summ up:
- there is an issue of phone doesnt updating file index after first mount and you can't see any new files on your PC that are created in the meanwhile until phone reboot (for example new pictures taken with Camera)
-this only happens if you have extra partition on sdcard (for a2sd) and installed a2sd script (so far tried only Darktremors and AdamG's, but I guess that they all basically are doing the same thing). If you remove one of this elements the issue is gone
-after changing line in /system/etc/vold.fstab
"dev_mount sdcard /mnt/sdcard auto /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1 "..........from auto to 1
so the system will mount first and not automaticaly the first available partition, the issue is gone but someone with more knowledge then me could say what kind of issues this change might produce.
(Some time ago while applying this change in hyperdroid release at that time lots of people had issues with getting an corrupt SD card error. Not sure why it happened because it worked fine on my phone)
I have that issue also and i'm using NDT MIUI...now have to use the eMAgldr 1.13 USB Mount Storage to move or copy the file.
I have just installed Ultimate Droid 3.3 to check this issue and it is also there. UD is a 2.3.3 rom with tytung r9 kernel. So the issue is not so new
I need to test even older roms to find out if this ever worked right.
Is there anyone with some old rom installed on it? Nand or SD.
clyder said:
tytung r9 kernel.
Click to expand...
Click to collapse
Yup just try updating your kernel to be able to support ext2-4 partitions
its a big mistake that almost everybody does...
Dakargr said:
Yup just try updating your kernel to be able to support ext2-4 partitions
its a big mistake that almost everybody does...
Click to expand...
Click to collapse
You havent read my post. There is no problem with functionality of sdext partition. But the presense of sdext partitions is one of the conditions for this issue.
I am using Hyperdroid with kernel that is based on tytung r12. After I realized the issue I thought that it is related to that rom and after that with my sd card or something 3rd from my side. But that is not the case.
I have tried about 5 different roms, vold files from 5 more and the issue is always there. Issue is present only where there is a second partion on SD card.
Oldest rom I tried is UD 3.3. I havent found much older cLK roms to test, and now dont have time to convert older roms to test. I will do so later. I want to see if this thing ever worked right and in what point it stopped.
Also you havent mentioned if you tested the issue or not.
I think I don't have any USB Mass storage issue.
My SD card has FAT32 and Ext3 partitions but I don't use Apps2SD. (i.e. Ext3 partition is empty.)
I will try your steps when I go home. (I didn't bring my mini USB cable in hand.)
I rarely copy files using file manager apps.
If you can use USB Mass Storage, it seems there's no reason to use file manager apps.
tytung said:
I think I don't have any USB Mass storage issue.
My SD card has FAT32 and Ext3 partitions but I don't use Apps2SD. (i.e. Ext3 partition is empty.)
I will try your steps when I go home. (I didn't bring my mini USB cable in hand.)
I rarely copy files using file manager apps.
If you can use USB Mass Storage, it seems there's no reason to use file manager apps.
Click to expand...
Click to collapse
Thanx for replying. I havent tried with ext3. Only reiserFs and ext4 and the behavior was the same. Only when I removed the ext partition it was gone.
The issue is like phone is sending the same directory listing to a computer in both first and all other mounts until reboot.
One also good way to test is by taking photos from a camera. Look at the DCIM/Camera folder with USB mass storage. Turn storage off. Take another picture. Use Mass storage again and the new pic wont be visible through USB mass storage on your computer.
So far I tried only on windows and not linux. Maybe the behavior is different. I will make more tests later.
At one point I thought that my windows system made that issue, so I tried to change USB ports, also tried hooking phone to another computer and the new files wasn't present.
Also it came to me that a2sd can cause this, but on your rom I tried Darktremor a2sd, while on others it was AdamG's one. Issue was exactly the same.
I havent tried any sense rom, because I would need to reflash different partition layout and was too lazy to do that yesterday.
Point of this thread was to check other people experiences with this to try to realize if this is all general HD2 issue, or perhaps only on AOSP roms. So far not much reports
Can any of your older kernel (<r9) work with newer roms(2.3.4+). I dont care about wifi, phone or anything. It is enough if I can just boot the phone to test this.
update:
I just tried USB mount in Ubuntu and the behavior is the same. Also since I can see ext partition when do a USB mount in linux I realized that the same issues goes with files on ext. New files are not visible to the computer until phone reboot.
clyder said:
Thanx for replying. I havent tried with ext3. Only reiserFs and ext4 and the behavior was the same. Only when I removed the ext partition it was gone.
The issue is like phone is sending the same directory listing to a computer in both first and all other mounts until reboot.
One also good way to test is by taking photos from a camera. Look at the DCIM/Camera folder with USB mass storage. Turn storage off. Take another picture. Use Mass storage again and the new pic wont be visible through USB mass storage on your computer.
So far I tried only on windows and not linux. Maybe the behavior is different. I will make more tests later.
At one point I thought that my windows system made that issue, so I tried to change USB ports, also tried hooking phone to another computer and the new files wasn't present.
Also it came to me that a2sd can cause this, but on your rom I tried Darktremor a2sd, while on others it was AdamG's one. Issue was exactly the same.
I havent tried any sense rom, because I would need to reflash different partition layout and was too lazy to do that yesterday.
Point of this thread was to check other people experiences with this to try to realize if this is all general HD2 issue, or perhaps only on AOSP roms. So far not much reports
Can any of your older kernel (<r9) work with newer roms(2.3.4+). I dont care about wifi, phone or anything. It is enough if I can just boot the phone to test this.
Click to expand...
Click to collapse
This problem appears only after dismounting SD storage you don't remove the cable from the phone.
It is normal before mounting it again to disconnect the USB cable!
Denkov said:
This problem appears only after dismounting SD storage you don't remove the cable from the phone.
It is normal before mounting it again to disconnect the USB cable!
Click to expand...
Click to collapse
This is not the case here. I tried disconnecting my phone, also tried connecting it to another PC and again I can't see any new files until phone reboot.
Have you actualy tested this or just guessing? Do you have ext partition on your SD card? What rom are you using?
clyder said:
This is not the case here. I tried disconnecting my phone, also tried connecting it to another PC and again I can't see any new files until phone reboot.
Have you actualy tested this or just guessing? Do you have ext partition on your SD card? What rom are you using?
Click to expand...
Click to collapse
I have second partition ext3.
I mount SD card, check screen shot folder, unmounted the card, remove the cable, take a screenshot, mount it again and the new image was there.
When I try to do same thing second time it did't work! Maybe you are right - there is issue with th SD card mount and I think the card is not dismounted properly!
tytung said:
I think I don't have any USB Mass storage issue.
My SD card has FAT32 and Ext3 partitions but I don't use Apps2SD. (i.e. Ext3 partition is empty.)
I will try your steps when I go home. (I didn't bring my mini USB cable in hand.)
I rarely copy files using file manager apps.
If you can use USB Mass Storage, it seems there's no reason to use file manager apps.
Click to expand...
Click to collapse
I have tried it.
Mount -> check the content of a folder in the SD card.
Unmount -> Copy a file to that folder using ES File Explorer. (Second testing is Root Explorer. Has the same result.)
Mount -> new file is there.
Win7 x64
NexusHD2-Gingerbread V3.1a NAND
tytung said:
I have tried it.
Mount -> check the content of a folder in the SD card.
Unmount -> Copy a file to that folder using ES File Explorer. (Second testing is Root Explorer. Has the same result.)
Mount -> new file is there.
Win7 x64
NexusHD2-Gingerbread V3.1a NAND
Click to expand...
Click to collapse
You said before that you dont have a2sd installed. Did you tested this without a2sd also? Maybe that is the key. All my tests so far included the presence of some kind of a2sd script.
Also I am on cLK, and two other guys that confirmed it are also on cLK. I dont know about denkov.
I will do more tests later but the issue is definitely related to ext. Because of some incompatibility of a2sd scripts with some part of android system or for some other reason.
I have just tried the combination of NexusHD 3.1a/cLK/AdamG's a2sd script/ext4
issue remains here
clyder said:
You said before that you dont have a2sd installed. Did you tested this without a2sd also? Maybe that is the key. All my tests so far included the presence of some kind of a2sd script.
Also I am on cLK, and two other guys that confirmed it are also on cLK. I dont know about denkov.
I will do more tests later but the issue is definitely related to ext. Because of some incompatibility of a2sd scripts with some part of android system or for some other reason.
Click to expand...
Click to collapse
I am on MAGLDR.
And I don't use any a2sd as I said before.
So my testing is without a2sd.
I think a2sd scripts may be the suspect.
tytung said:
I am on MAGLDR.
And I don't use any a2sd as I said before.
So my testing is without a2sd.
I think a2sd scripts may be the suspect.
Click to expand...
Click to collapse
They are definitely the cause. I have tried both Darktremor's and AdamG's script.
All of the people who confirmed this to me was using a2sd.
edit:
Just did a fresh install of hyperdroid with a2sd script removed from init.d and usb mount issue is gone.
So something is happening while mounting or remounting USB with active a2sd script which breaks the file list updating when mounting it the second time.
I have found a way to stop the issue from happening. Updated first post....if anyone is actually reading this thread...
clyder said:
update3:
I found a way to stop this issue from happening. I have modified one line in vold.fstab file that is located in /system/etc
from
dev_mount sdcard /mnt/sdcard auto /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1
to
dev_mount sdcard /mnt/sdcard 1 /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1
As soon as I change 1 to auto again and reboot issue is back.
This way only the first partition (fat32) is mounted and the issue is gone. I dont know if this change can cause any other issues, but so far only thing I noticed that is different is that when you turn USB Mass storage on while connecting the phone to a linux computer it only mounts first partition and no sdext one. For me this is not important, but as I said I am not sure if this change could have an impact on stability to any part of the system or phone functionality.
So to summ up:
- there is an issue of phone doesnt updating file index after first mount and you can't see any new files on your PC that are created in the meanwhile until phone reboot (for example new pictures taken with Camera)
-this only happens if you have extra partition on sdcard (for a2sd) and installed a2sd script (so far tried only Darktremors and AdamG's, but I guess that they all basically are doing the same thing). If you remove one of this elements the issue is gone
-after changing line in /system/etc/vold.fstab
"dev_mount sdcard /mnt/sdcard auto /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1 "..........from auto to 1
so the system will mount first and not automaticaly the first available partition, the issue is gone but someone with more knowledge then me could say what kind of issues this change might produce.
Click to expand...
Click to collapse
Good job! I will try!
Hi,
I have a nook that I rooted and put a custom rom on back about a year and a half ago. I flashed the ROM to the internal EMMC and CWM 3.2.0.1 was flashed as recovery. If it makes any difference it was a CM9 ROM
Now here's where I'm at. I can run ROMs off the sd-card but they are not stable at all. I get a whole bunch of force closes and such.
When I try and flash a new ROM to the internal EMMC it says it completes, but nothing changes. It is still the previous ROM. When I try and format the /data and /system partitions with the EMMC recovery, it doesn't complete. It says there is an error. When I format with TWRP off an sd card, it says it completes but once again, the rom is not wiped.
I've tried the 8 reboot error method, and it never gets to the stock recovery screen. It keeps booting to the EMMC ROM.
I've tried repartioning the EMMC with leapinlar's zip files. It says it successfully completes, but once again nothing changes.
Ideally I'd like to get the emmc back to stock and try and run a rom off the sdcard.
I've read the threads that I thought were applicable to my issues, but nothing seemed to work. I'm completely out of ideas. Anyone have similar issues or can provide some guidance?
Thanks.
The problem you are having running a ROM from SD is the brand and speed of SD you are using. It needs to be SanDisk class 4.
The reason the 8 failed boot does not work is you replaced the stock recovery with CWM. It needs the stock recovery to be able to complete. See my NC tips thread linked in my signature and read item A12. Assuming you can get it to flash, I have a stock recovery zip there.
I don't understand why the ROMs are not flashing. You say it gives errors when you try to wipe with CWM. What do the errors say? You used the internal CWM and TWRP on SD, but none worked. Try my bootable CWM SD to see if that helps.
I don't understand why my partition zips did not work. I know the newest TWRP will not flash them without giving an error 2 message. Try my bootable CWM SD.
Sent from my Nook HD+ running CM10.1 on Hybrid SD
Thanks for the advice...
I've been using a Patriot class 10 micro sd to run the roms/attempt to flash new roms. Its worked fine before, but I'll try and pickup another one from someplace.
When I try and format /system and /data from the emmc CWM it says "Error formatting /system" or "error formatting /data" after working away for about 5 minutes
Here's what i did:
Created CWM 6.0.1.2 Bootable SD
- Flashed NookColor-emmc-stockrecovery.zip
- Message said successfull.
- tried to restart and old CWM recovery 3.2.0.1 was still installed
Booted into CWM 6.0.1.2 Bootable SD Recovery
- mounted /system and /data
- attempted to format
- Message "Done." for both
- attempted to flash stock 1.4.3 that you have modified for CWM
- install from sdcard complete
- reboot
- Old CynanogenMod bootscreen and old rom still installed.
Using same CWM 6.0.1.2 Bootable Sd Recovery
-flashed NookColor-emmc-repair-partitions-1-4-5-6-7-8.zip and NookColor-emmc-format-partitions-5-6-7.zip
-said success
-attempted to flash stock 1.4.3
- nothing changed. Old rom still installed
One more thing I noticed:
Everytime I login to the currently flashed rom, any changes I make are never saved. For example, if i install an apk or uninstall an app, the next time i can successfully boot into the emmc ROM, those changes are reversed to the previous version. Could it be that the current rom is being stored somewhere and being reflashed when it tries to bootup?
I hate to say this, but it sounds like your internal embedded card has become read only. I have had this happen to SDs but not to emmc. The apps act like they are writing and if you leave the folder and come back, they are not there. It is like they are writing to a ramdisk instead of your SD. You might try booting to a ROM on SD and see if you can write to any of the internal partitions like /cache or /rom and see if they stick. If not, you may only be able to run off SD and maybe not even then. You might have to change your dalvik cache setting on SD so it uses /data instead of /cache.
Sent from my Galaxy Tab running Tapatalk
I tried copying a file to the emmc partition from twrp and it didn't persist after reboot... so it looks like the emmc is set to read only. I don't supposed I can change that using adb and/or software solutions right? It's a hardware issue?
Any guidance on how to change davlik cache to use /data instead of /cache? I'll be happy to get any sort of stable rom running off any SD card.
I was hoping to repurpose the nook as in in car tablet to tether a data connection to my phone and play music and such.
Thanks for your help. I appreciate you taking the time.
canjoe said:
I tried copying a file to the emmc partition from twrp and it didn't persist after reboot... so it looks like the emmc is set to read only. I don't supposed I can change that using adb and/or software solutions right? It's a hardware issue?
Any guidance on how to change davlik cache to use /data instead of /cache? I'll be happy to get any sort of stable rom running off any SD card.
I was hoping to repurpose the nook as in in car tablet to tether a data connection to my phone and play music and such.
Thanks for your help. I appreciate you taking the time.
Click to expand...
Click to collapse
I don't know of anything that can revive it. I never could revive my SD that that happened to.
To make your ROM on SD use /data for all of the dalvik cache, create a file in /data named local.prop. In that file put this line:
dalvik.vm.dexopt-data-only=1
Next time it boots the system file portion of dalvik cache will be on /data along with the installed app portion.
Sent from my stock Nook HD+ using XDA Premium
I now have a stable version of CM 7.2 running off the SD card. I put the davlik cache on the data partition and everything seems to be running pretty smooth.
I'll keep messing around seeing if there is anything to revive the internal emmc, but at least I can use the nook off the SD card again.
Thanks for helping me troubleshoot and figure this out. Cheers.
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!