Database Info

[Q] Can anyone help? SD card (internal)

So I updated to the leaked Samsung 2.2 Froyo. I am trying to move apps to the sd card and I am getting an error. "Failed to move application. Not enough memory".
I have seen demos/reviews with this function working. I am also making sure I try it with apps that are compatible with the feature.
Anyone have a clue as to whats going on here.
Other than that, I love being a new Android user, ported over from the apple world. Captivate made my 3g look foolish.
Thanks in advance for any help guys.

stjalsma said:
So I updated to the leaked Samsung 2.2 Froyo. I am trying to move apps to the sd card and I am getting an error. "Failed to move application. Not enough memory".
I have seen demos/reviews with this function working. I am also making sure I try it with apps that are compatible with the feature.
Anyone have a clue as to whats going on here.
Other than that, I love being a new Android user, ported over from the apple world. Captivate made my 3g look foolish.
Thanks in advance for any help guys.
Click to expand...
Click to collapse
When installing a program it will pop up, this is Apps2SD, do you want to move. Or you can see it in manage applications, select application > Move to SD is highlighted
You have to be careful with it because that silly media scanner will run and disable you sd functions. Example. You have a program that starts up when your phone starts you will get a FC because the media scanner is running.
Good to have you by the way.

I'm getting the same message, but it was working before.
I flashed a ROM and enabled lag fix. However, when I went back to stock, I forgot to disable the lag fix.
I'm back to the leaked 2.2, but I still can't move apps to the SD card. There is plenty of memory free.
Is there any way around this?
Thanks!

gospeedgo said:
I'm getting the same message, but it was working before.
I flashed a ROM and enabled lag fix. However, when I went back to stock, I forgot to disable the lag fix.
I'm back to the leaked 2.2, but I still can't move apps to the SD card. There is plenty of memory free.
Is there any way around this?
Thanks!
Click to expand...
Click to collapse
Have you tried doing a master reset to remove the the lag fix or gotten the app from the market app2sd?

I tried a master clear using Odin, but I haven't tried a master reset. How is that done?

gospeedgo said:
I tried a master clear using Odin, but I haven't tried a master reset. How is that done?
Click to expand...
Click to collapse
If you did a master clear with odin then it is pretty much the same thing

Oh, and when I use the app, I get the same message.

gospeedgo said:
Oh, and when I use the app, I get the same message.
Click to expand...
Click to collapse
Ok I know a dumb question but do you have enough rom on your SD card? Try the apps2sd app from the market

No worries, I know you have to ask.
My SD card has 12.83GB free.
I did try using the apps2sd, but I get the same message, that there isn't enough memory.

I would say that there is an issue with the leaked rom. I would try a custom rom and see if it happens, if it is still an issue I would copy the stuff off your card and reformat it to see if that is an issue

I actually got the message the first time I tried a custom ROM. When I went back to 2.2 the problem went away, but I hadn't tried the lag fix.
When I tried another customer ROM today, I got the message again, but this time a tried the lag fix.
I forgot to disable it when I went back to stock, then to 2.2.
I did reformat the internal SD card, didn't help. That's why I turned to the forums. I'm all out of ideas.

OMG I am stupid lol. The apps to SD is for moving the APPS to an EXTERNAL sd card not the internal sd

LOL, no worries.
I don't want to waste my time, but would it be worth a try to:
1. Flash back to stock.
2. Install Clockwork recovery
3. Install customer ROM again.
4. Enable lag fix.
5. Disable lag fix.
6. Flash back to stock.
7. Master clear
8. Install 2.2 again?

gospeedgo said:
LOL, no worries.
I don't want to waste my time, but would it be worth a try to:
1. Flash back to stock.
2. Install Clockwork recovery
3. Install customer ROM again.
4. Enable lag fix.
5. Disable lag fix.
6. Flash back to stock.
7. Master clear
8. Install 2.2 again?
Click to expand...
Click to collapse
Only if you have enough room on your external sd (micro sd plugged into the phone)

I don't currently have one installed.
It must be a file system issue. Is there anyway to rebuild the stock file system? Or is that supposed to happen when I flash back to stock?
By the way, thanks for your help on this.

gospeedgo said:
I don't currently have one installed.
It must be a file system issue. Is there anyway to rebuild the stock file system? Or is that supposed to happen when I flash back to stock?
By the way, thanks for your help on this.
Click to expand...
Click to collapse
No prob, but here is the deal. This only works for external SD card in 2.2 2.1 didnt have this option at all. So unless you insert an external SD card it is not gonna work.

OK, now I'm the stupid one. I didn't even think of putting my SD card back in! I always take it out when I flash back to stock because the media scanner takes so long.
Anyway, I put it back in, now I can move to SD.
So, my next question is, where does it put it on that SD card? I looked, and I don't see anything other than my music.

gospeedgo said:
OK, now I'm the stupid one. I didn't even think of putting my SD card back in! I always take it out when I flash back to stock because the media scanner takes so long.
Anyway, I put it back in, now I can move to SD.
So, my next question is, where does it put it on that SD card? I looked, and I don't see anything other than my music.
Click to expand...
Click to collapse
To tell the truth I dont remember really, I have not needed to move anything to my external sd in a long time, what are you using to look at your SD card?

Root explorer. It's not really that important, it's mostly just curiosity.

[Q] unable to open zip in TWRP

Hi, I've been trying to hunt down an answer to my problem with no avail, hopefully someone here can help. I've a rooted Huawei y300 0100 back on factory stock again.
My problem is this after I rooted (went fine first time doing this) installed TWRP created backups, Flashed Fusion x rom no problems at all, found a few bugs thought I would try another ROM, restored my stock from twrp saved backups all good I thought...
Upon re entering recovery everything is fine, factory wipe etc then when it comes to installing any ROM I get the message E: cannot open zip. This happens on any ROM I try, so I know its not the file, file can also be opened on PC and phone explorer.I've formatted the external SD card and re-downloaded ROMs still nowt.
I would just use the stock again and run a new launcher and delete the bloat myself but I can't get Orbit working at all now I'm rooted and back on factory stock when it was working fine on fusionx and orbit/Pandora are pretty much what I did all this for
Any ideas would be appriecated as I'm pretty noobish at this.
Would installing cwm over the top of twrp work?
Do I need to do a special kind of wipe in case of file corruption?

Solved, after some fiddling got flashing working again. What worked for me was to redownload the file direct to internal SD and flashing from there. Downloading anywhere else ie PC or ext SD and copying across still gave same error. Not sure why but I've flashed 3 ROMs today without issue this way. Hope this helps anyone else who encounters this.

petehippy said:
Solved, after some fiddling got flashing working again. What worked for me was to redownload the file direct to internal SD and flashing from there. Downloading anywhere else ie PC or ext SD and copying across still gave same error. Not sure why but I've flashed 3 ROMs today without issue this way. Hope this helps anyone else who encounters this.
Click to expand...
Click to collapse
Hey Pete, did you flash rom from Int. Sd card or ext. sd card?? Getting the same problem flashing DN3 for note 2 on TWRP 2.7.2.0.

Yay!
petehippy said:
Solved, after some fiddling got flashing working again. What worked for me was to redownload the file direct to internal SD and flashing from there. Downloading anywhere else ie PC or ext SD and copying across still gave same error. Not sure why but I've flashed 3 ROMs today without issue this way. Hope this helps anyone else who encounters this.
Click to expand...
Click to collapse
ABSOLUTELY confirmed. I was trying it for days. After finding this post, direct downloading to sdcard worked for me.

petehippy said:
Solved, after some fiddling got flashing working again. What worked for me was to redownload the file direct to internal SD and flashing from there. Downloading anywhere else ie PC or ext SD and copying across still gave same error. Not sure why but I've flashed 3 ROMs today without issue this way. Hope this helps anyone else who encounters this.
Click to expand...
Click to collapse
yeeah... thank you bro

I also had problems with "unable to open zip file" and "bad" errors, seemed to be fixed by formatting a spare 4gb MicroSD to FAT and making sure it was the first thing copied to the SD card. I was using PHILZ recovery, but I'd assume that TWRP will work just as well. I have a suspicion it may have something to do with file fragmentation or maybe allocation block size. Before this I checked MD5SUMs on a few MicroSD cards and they were all perfect, so it wasn't a download or copy corruption, the bootloader just has an issue with the file or filesystem for some reason.

Can confirm. Was having trouble installing Boeffla 3.0 kernal on gnabo 4.4.2 (v8). ( samsung galaxy note 10.1 n801x / n8013 )
Deleted the zips I downloaded, then re-downloaded straight to zip. installed like a boss!
Thanks!

This is a most underrated thread.
Just had the same issue with my old Galaxy S3. Needed to copy the zip directly to internal storage via mtp in twrp.
In newer twrp version it shows zip file corrupt instead of unable to open zip.

[Q] Need help fast, sdcard problem [J]

Hi all, I just installed Alien Rom 4.1, did everything correctly, I'm sure, and now I can't use apps that require memory. For example, everytime I try to download something it says I have no SD card, I tried fixing permissions and giving permission via Root Browser, nothing worked. Help?

deviance1337 said:
Hi all, I just installed Alien Rom 4.1, did everything correctly, I'm sure, and now I can't use apps that require memory. For example, everytime I try to download something it says I have no SD card, I tried fixing permissions and giving permission via Root Browser, nothing worked. Help?
Click to expand...
Click to collapse
I think it's problem in vold.fstab,because sd card and ext_sd(internal) are replaced... sd is ext,ext is sd ,lol. Hope u understand.

2010matej said:
I think it's problem in vold.fstab,because sd card and ext_sd(internal) are replaced... sd is ext,ext is sd ,lol. Hope u understand.
Click to expand...
Click to collapse
I understand, yes. This was my thought at first, however I tried to download an app to change them and there was nothing new, it stayed the same. Also, no one is complaining about this on the thread, so I must have screwed something up. Any way to fix it?

I still have this problem, bump? ...

installing apps to sd card working?

so, I've noticed that on my j7 metal (j710mn) stock MM in the app manager there is an option to install apps to the external SD card, but it doesn't seem to work - at least not for every app. tried to move some games to the SD card, and the only one that worked was odd world - strangers wrath, and only after I moved it's obb folder to the SD card manually. is there any tip or thick to make it work on other apps or is this not working?

You have to format the SD as internal memory.
Then it should work.

Boulliebeest said:
You have to format the SD as internal memory.
Then it should work.
Click to expand...
Click to collapse
there's no option to do that on the stock ROM, is there?

khaotik said:
there's no option to do that on the stock ROM, is there?
Click to expand...
Click to collapse
Look here:
https://www.androidpit.com/how-to-format-microsd-cards-as-internal-storage
It is working for a bunch of people, but it all depends on how well Samsung altered the core Android OS.
I tried it on my SM-T800 (MM), didn't work.
Also the same on my SM-J730F (N).

Boulliebeest said:
Look here:
https://www.androidpit.com/how-to-format-microsd-cards-as-internal-storage
It is working for a bunch of people, but it all depends on how well Samsung altered the core Android OS.
I tried it on my SM-T800 (MM), didn't work.
Also the same on my SM-J730F (N).
Click to expand...
Click to collapse
oh, this is great, thanks! I'll try that ASAP

Boulliebeest said:
Look here:
https://www.androidpit.com/how-to-format-microsd-cards-as-internal-storage
It is working for a bunch of people, but it all depends on how well Samsung altered the core Android OS.
I tried it on my SM-T800 (MM), didn't work.
Also the same on my SM-J730F (N).
Click to expand...
Click to collapse
yeah, it was a no-go. thanks for the help anyways

Should work after rooting then.
However, I didn't manage to root my phone following the guide posted somewhere else on xda.
Phone for stuck in a boot loop

sd card corrupted

I just wanted to post this here in case it might help someone.
If you have ever had the SD card corrupted issue after installing a ROM or an update the first thing you should check is the kernel. I have found that every time I've had this issue I could still see the SD card in TWRP you couldn't figure out what was going on. I have since learned that the issue usually stems from the kernel. So take and reflash your current kernel or try a new kernel. Hope this helps someone good day

I reformatted my card to FAT32 which solved those issues for me. Be sure to backup anything before doing that as it reformatting will erase the card obviously.

AngryManMLS said:
I reformatted my card to FAT32 which solved those issues for me. Be sure to backup anything before doing that as it reformatting will erase the card obviously.
Click to expand...
Click to collapse
Why format the SD card if just flashing another kernel will fix the issue lol

shadavis08 said:
Why format the SD card if just flashing another kernel will fix the issue lol
Click to expand...
Click to collapse
I could think of a reason, that being (and this is an Android-wide rule) the kernel dictates support for file formats.
If you're using a kernel that has better features than a stock one on a ROM (let's say Gamma vs the stock LineageOS kernel in this case) the better kernel might not support the file-system format the stock one does. It comes down to support for what file-systems a kernel dev chooses to implement.
At least personally, I'd rather move 64GB off my microSD card, format it and move it all back on if it means I get to keep using a better kernel.

Your thought process is flawed. Since the source of the issue is the stock kernel. Geesh

Thinking that it's easier to remove everything and then put it back rather than, simply flashing a different kernel than the stock kernel, first to see if that is the issue, by the way is flawed.

shadavis08 said:
Your thought process is flawed. Since the source of the issue is the stock kernel. Geesh
Click to expand...
Click to collapse
shadavis08 said:
Thinking that it's easier to remove everything and then put it back rather than, simply flashing a different kernel than the stock kernel, first to see if that is the issue, by the way is flawed.
Click to expand...
Click to collapse
I'm not entirely sure what makes my thought process flawed. If the issue is the stock kernel, then the stock kernel likely doesn't support the format the SD card is using, in which case, like you said, swapping kernels would fix that.
I don't disagree with you there.
I also wouldn't call moving everything off, formatting and moving everything back on is a flawed process either.
If I have to choose between massive screen retention using a stock kernel on the V20, or little to no screen retention and better performance by using a custom kernel like Gamma, Gamma is going to win every-time. Even if I have to spend 20 minutes moving stuff off, formatting my SD card and moving it all back on.
It might not be a process that's worth it for some people, but it's by no means flawed.
Your "flash a different kernel to see if that's the issue first" is like me saying I'll plug my desktops Windows 10-formatted SSD into my Windows 7-formatted laptop and see if it'll work.
It could, but I run the risk of it not working properly, which is something you want to avoid in most cases.
And I did say
At least personally
Click to expand...
Click to collapse
which, again, doesn't make my process flawed.

Redline said:
I'm not entirely sure what makes my thought process flawed. If the issue is the stock kernel, then the stock kernel likely doesn't support the format the SD card is using, in which case, like you said, swapping kernels would fix that.
I don't disagree with you there.
I also wouldn't call moving everything off, formatting and moving everything back on is a flawed process either.
If I have to choose between massive screen retention using a stock kernel on the V20, or little to no screen retention and better performance by using a custom kernel like Gamma, Gamma is going to win every-time. Even if I have to spend 20 minutes moving stuff off, formatting my SD card and moving it all back on.
It might not be a process that's worth it for some people, but it's by no means flawed.
Your "flash a different kernel to see if that's the issue first" is like me saying I'll plug my desktops Windows-formatted SSD into my Linux-formatted laptop and see if it'll work.
It could, but I run the risk of it not working properly, which is something you want to avoid in most cases.
And I did say
which, again, doesn't make my process flawed.
Click to expand...
Click to collapse
Wow really dude? I was giving some advice for people that could potentially keep them from losing all their data on the SD card. By simply flashing a different kernel before just wiping a card when the android system throws up an error saying sd card corrupted. You are only here to argue and I would like you to stop. Thank you for over thinking the situation and good day.

shadavis08 said:
You are only here to argue and I would like you to stop. Thank you for over thinking the situation and good day.
Click to expand...
Click to collapse
That's precisely the opposite of the reason why I'm here.
I was here to point out the benefits and potential downsides to doing it either way, but okay.

I don't get t flash kernels on my variant but if ever i saw a corrupt sd card message i'm wondering whether just deleting the android folder (on the card say on a PC) and then re-inserting the card would be enough.
You could simulate this just by pulling the card without un-mounting it and then reinserting and android thinks the card is corrupt

I don't know. I don't have a computer to test with lol

One Twelve said:
I don't get t flash kernels on my variant but if ever i saw a corrupt sd card message i'm wondering whether just deleting the android folder (on the card say on a PC) and then re-inserting the card would be enough.
Click to expand...
Click to collapse
This shouldn't be the case. I say shouldn't because I'm not sure how Android does it exactly, but telling you the SD card is corrupt either means it is, or it can't read the file system itself, not the files.
Deleting the Android folder probably won't do anything, that folder just has data for apps and such that want to store things on the SD card.
I'd imagine you could achieve the same thing with internal storage if you formatted it weirdly from TWRP or something.

Redline said:
This shouldn't be the case. I say shouldn't because I'm not sure how Android does it exactly, but telling you the SD card is corrupt either means it is, or it can't read the file system itself, not the files.
Deleting the Android folder probably won't do anything, that folder just has data for apps and such that want to store things on the SD card.
I'd imagine you could achieve the same thing with internal storage if you formatted it weirdly from TWRP or something.
Click to expand...
Click to collapse
My mistake not Android folder but lost.dir folder needs to be deleted

Back on nougat this happened to me twice on the same card. Formatted once and it happened again and this was back before I tried any custom ROMs or Kernels. Was purely stock rooted with SuperSU so it was definitely something screwy with LGs kernels
Kinda fuzzy but I think it happened first on 10J for TMobile and then again on 10K for my H918

I've not had any problems with my sandisk extreme 128GB for over a year now. On N.
I don't take the card out and swap it about, its been in all this time.