• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Unabe to transfer apps to SD

R

robinta

Well-Known Member
Hi All,

For no apparent reason my phone started acting up today.

All the apps that are trandferred to SD card are showing as not installed when selected. I should say I`m rooted on Redux 1.2 with the apps2sd script installed. I`ve tried to restore apps and data through a zipped Titanium Backup but the program just `sticks` and doesnt restore any apps. I ran chkdsk on the sd card and it restored some truncated links but said the card was ok.

I also tried moving an app from SD to phone and then back but it said `unable to move file`. I suspect a possible problem on the partioned SD card. Anyone have any ideas ?
 
I'd agree that the problem lies with the SD card. You could try backing up the card, reformatting it in the phone and then restoring all the files (make sure you include hidden and system files too.)

If that doesn't work you may need a new sd card. Even if it does work you might need a new card as this could be indiciative of impending failure.
 
Thanks, lunatic. I was unfortunately thinking along the same lines but I looked in System Panel and it showed the SD cards as read-only. I went into root explored and changed it to read-write and it is now letting me restore the "missing" apps. Hopefully this will mean its ok, but how the sd became read only I dont know ?
 
Did you use a card reader to copy files? Some of them have a little switch to set the device to read only and I believe if you set it accidentally and do not cleanly unmount the partition it can remain flagged.
 
Woah what?

All the apps should be on the internal / phone memory anyway if you're using the a2sd script. By manually moving them to sd "move to sd" you're splitting the application over 3 locations rather than 2, i.e /sd-ext, /sdcard and /data

Please leave all apps on "internal" or "move to phone" and then see if the issue persists.
 
I moved all the apps back to the phone memory. Which seems ok, however before the incident i was showing c. 95mb of memory available for apps, which then dropped to 65mb. With all the apps in internal memory its now 37.
 
136..

Last night the sd card showed as corrupted. I eventually managed to retrieve the files from both partitions with a freeware package. I then reformatted and transferred everything back and ran a nandroid restore. The phone seems to be working fine but i think i might need to fork out for a new card.
 
It could just be that the file system was corruopt. See how it goes for now. The memory amount seems about right for that amount of apps with a standard hboot (250 MB system).

As Redux is Gingerbread, the reason memory increases when you "Move to SD" via manage applications is that it also moves the application libs for those that have them.

If you are not s-off, I would consider doing it because if you have the stock hboot, you are wasting 100MB of space in /system that you could you to increase your /data partition size.
 
I know it gives more space but I would not be happy recommending moving apps to FAT32 manually as I mentioned before, you are further splitting the application into a 3rd location which is just more to go wrong IMHO.

Although I'm not telling you not to ;)

Personally I would go for an alternative hboot myself.

Download "Quick system info" from the market please. How big is your system (well how much space is taken up?)
 
So basically the ROM is 82MB? yeah sounds about right.

If you have a look at the table half way down this page:

AlphaRev 1.8

You will see the oxygen Hboot. This would give you internal memory of 332MB Instead of the 147 you have now.

If you went custom MTD, you could have 85, 3 leaving you 349MB. Although this si a little more advanced.....
 
your not flashing a radio, just a different hboot. See suroots faq on fastboot/adb. If your not comfortable with fastboot, you can use android flasher from the root tools page.
 
A bad hboot flash could also be a big problem, so it's important to check you have a good copy, i.e. check the md5 sum matches the one on the alpharev site before you flash it.

As long as you do that you should be fine though.
 
Hadron said:
A bad hboot flash could also be a big problem, so it's important to check you have a good copy, i.e. check the md5 sum matches the one on the alpharev site before you flash it.

As long as you do that you should be fine though.
Click to expand...

and don't drop usb connection / lose power throughout the operation (all 5 seconds of it)
 
You must log in or register to reply here.
Back
Top Bottom