Database Develop

Can't get Apps2sd to work (help please)

I have been searching the forums for 2 hours trying to figure this out and I cannot find out how. I tried following the tutorials on the forums here on how to partition the SD card but none of the settings that were listed are not on my recovery. But I still tried it anyways. Here is the list of options on my recovery
Reboot system now
Nandroid v2.2 backup
Nandroid v2.2 restore
Apply sdcard:update.zip
Apply sdcard:choose zip
Wipe data/factory reset
Wipe SD:ext partition
Wipe SD:dalvik-cache
Part SD:fat32+ext2+swap
Part SDnly fat32
Repair ext filesystem
Convert ext2 to ext3
Fix apk uid mismatches
Fix rotate
USB Mass storage on
USB Mass storage off
The bottom says "Build : RA-heroc-v1.2.3".
Upon reading the tutorials, I decided to try something different. So I wiped ext partion, parted sd fat32 ext2 and swap, then converted ext2 to ext3. Applied PureHero 2.1 and I enabled Apps2SD, move apps to sd, move dalvik cache to sd, enable JIT, and changed dalvik heap to 24mb. It rebooted and none of the applications I downloaded and installed were transferred to the SD.
Before this I applied a rom before wiping and parting and changed the same settings and it wasn't working then either.
I tried using the cmd and located to my android-sdk-windows and tried finding what version of apps2sd I had but it kept aborting. I tried repairing and it kept aborting, I even tried installing and it kept aborting.
I am at a loss here and I am trying to get all of this working.
It is a 2gb card and it is only showing 1.34gb available so I have no idea how to give me the full 2gb like it was before I tried partitioning.
Before I posted this, I applied the program at http://forum.xda-developers.com/showthread.php?t=715116 and that didn't work as well.
Please help.

I'm not sure if it makes a difference, but I would try to upgrade to RA-heroc-v1.6.x, it might be your recovery not partitioning correctly or something. Once you have upgraded, go ahead and wipe everything (data, dalvik, and ext). Flash your ROM. Before you move your dalvik to the sd card you want to make sure you have at least a class 4 sd card. Once your phone is booted up check your internal memory and you should have 90+M out of 159 or so. If you have that then I am pretty sure your ap2sd is working. You can also check to make sure it is working through adb. I don't use the option in recovery to move the apps to sd. Hope this helps, and I hope my information is correct, lol. I still consider myself a noob.

Ok ill do some research on how to update and see what I find. If that don't work then ill come back and keep you updated.
Thanks
EDIT: I have tried updating my Recovery using FlashRec and it isn't backing up my recovery or finding the recovery at all. I am on ubuntu so maybe that might be the problem, idk. Is there any other way I can update my recovery? I have 1.6.2 downloaded and just need to apply it.

puppetmstr said:
Is there any other way I can update my recovery? I have 1.6.2 downloaded and just need to apply it.
Click to expand...
Click to collapse
The instructions are here http://forum.xda-developers.com/showthread.php?t=581521#1
I used the adb method last night no problem.
Note: the first thing it tells you to type is "mount -a"
After which your phone might spit out some sort of error message. Don't worry about it, it doesn't affect anything. That's what people said, and it didn't affect me.

c00ller said:
The instructions are here http://forum.xda-developers.com/showthread.php?t=581521#1
I used the adb method last night no problem.
Note: the first thing it tells you to type is "mount -a"
After which your phone might spit out some sort of error message. Don't worry about it, it doesn't affect anything. That's what people said, and it didn't affect me.
Click to expand...
Click to collapse
Well this is confusing lol. I went into recovery, went into USB mode getting ready to update my recovery option and a screen popped up in ubuntu with the folders app, app-private, dalvik-cache, and lost+found. Apparently I had apps2sd working the entire time... But I nandroid last night back to ZenEXP. Idk if it still works in Pure Hero.
But now that I have apps2sd working, I can flash a new rom and still have my applications right?
EDIT: In Windows 7, it doesn't show the partition anymore for the apps2sd. So im just gonna go ahead and update recovery then repartition everything.

Please update with whether or not your apps still work after flashing a new ROM, I want to know if it works like that.

c00ller said:
Please update with whether or not your apps still work after flashing a new ROM, I want to know if it works like that.
Click to expand...
Click to collapse
I cant update the recovery at all. I have tried both ways and it fails.
I tried adb and as soon as i try to use the command "mount -a" it says "no such device". I tried using "mount /sdcard" and it says "Device or resource is busy".
On the Fastboot + adb I can load into fastboot. But when i type "fastboot boot recovery-RA-heroc-v1.6.2-blue.img" it says "cannot load fastboot boot 'recovery-RA-heroc-v1.6.2-blue.img'".
I tried pressing the trackball on fastboot usb and the screen goes black for a second, then i hear a connect noise in the speakers then it shows fastboot for a split second then fastboot usb again.
Also in Fastbot +adb when I use the command "adb shell mount /sdcard" it says "device not found".
EDIT: im also starting to think my adb shell is broken or something lol.

Ok nevermind I got it working. I typed mount /sdcard and it said it was busy but then i used the command "flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2-blue.img" then Rebooted into recovery and it says 1.6.2 and its blue. I just hope I did it the right way and didnt **** anything up...
EDIT: Ok well I partitioned it with 64mb swap, 1024mb ext2, converted to ext3, and loaded up PureHero 2.1. How do I know if it is working? I have my DConfig options set to move dalvik and apps to sd, with JIT enabled. Do I just install an app and see if the internal memory lowers or stays the same? How do I access the apps folder through USB mode?

This is how to tell if you have A2SD working
http://forum.xda-developers.com/showpost.php?p=6848245&postcount=80

[Q] Clockwork recovery sees different files than are actually on SD

Hi folks,
I am having a weird problem on my A855. When I boot into CWM recovery, I cant see the contents of my SD card. I see something totally different, something that looks like files from an old SD card. I've formatted the SD card and copied only the ZIPs that i want to use to update. When I boot to clockwork recovery I dont see them but some phantom files!
Strangely, if use the partitions menu and mount USB while in recovery, I see the correct files. Or, also while in recovery, if I adb shell, mount sdcard, list files, I also see what's actually on there.
I've already wiped boot, system, data, cache, reflashed CWM, but it still sees those old files. I've never seen this before and I've updated 6 or so different phones to Cyanogenmod.
I was able to adb push update.zip to /data/ and recovery --update_package=DATA:ROM.zip to get CM on the phone but it's a less than optimal solution.
On a related note, on my Sensation, when trying to update via ROM Manager I get a "file not found" error upon booting to recovery but at least there I can see the SD files and manually update.
Any info would be appreciated.

help, problem with internal storage

Hi at all, I've a problem with my samsung galaxy note n7000, I have the latest 4.1.2 original samsung touchwiz , I've only rooted it,
the problem is that the android os doesn't mount the internal sd card, and get me a notification that say "blank usb memory or not supported file system", I tried to reboot custom recovery(philz recovery) and wipe data and cache, format sd card but nothing works, can anyone help me????

Did you format it to fat32? In recovery did you try formating the external storage?

diaboliko.hacker said:
Hi at all, I've a problem with my samsung galaxy note n7000, I have the latest 4.1.2 original samsung touchwiz , I've only rooted it,
the problem is that the android os doesn't mount the internal sd card, and get me a notification that say "blank usb memory or not supported file system", I tried to reboot custom recovery(philz recovery) and wipe data and cache, format sd card but nothing works, can anyone help me????
Click to expand...
Click to collapse
*bump
I'm facing the same problem right now. It occurred after I did a hard reset. In the best case scenario, this is just a partition table corruption, but in the worst, a physically damaged card.
On Linux, I have fixed partition tables with a nifty tool called gpart (not gparted). There is a similar utility available for Linux, Windows, Mac etc. called TestDisk. Unfortunately, these tools are not available on Android. However, there is something called aparted available on Play Store that supposedly fixes filesystems.
I have installed it, but it wants to install some browser addons too. I've tried to repair the filesystem that it shows as empty, but no luck so far. I will shortly check its online manual, but I hope we can get something like gpart on Android.

diaboliko.hacker said:
Hi at all, I've a problem with my samsung galaxy note n7000, I have the latest 4.1.2 original samsung touchwiz , I've only rooted it,
the problem is that the android os doesn't mount the internal sd card, and get me a notification that say "blank usb memory or not supported file system", I tried to reboot custom recovery(philz recovery) and wipe data and cache, format sd card but nothing works, can anyone help me????
Click to expand...
Click to collapse
Hi, I have been able to get the Internal SDCard (/storage/sdcard0) mounted again, albeit with loss of data. Look at my recent post http://forum.xda-developers.com/showpost.php?p=48595569&postcount=24
and the one from which I got the hint
http://forum.xda-developers.com/showpost.php?p=35726016&postcount=6
The step by step procedure is here: http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
but if you have only one partition damaged, you could just check it with e2fsck and then, if necessary, recreate it with mkfs.exfat or the other method in the referred post.
EDIT: link to parted and other files: http://forum.xda-developers.com/showpost.php?p=38598228&postcount=4
http://www.droidforums.net/forum/htc-droid-eris/78650-internal-storage-partitions-screwed-up.html
I don't know if you can recover your original data - I had tried formatting the partition, by mistake, to ext4 with mke2fs. You could avoid this, and see if you can back up your partition with dd before re-formatting it to fat32.

solved, I download latest frimware, and flash it throught odin and all are fixed

[Q] GT-P1000 Stuck in bootloop

Hello All,
Long time lurker, first time poster (and, as usual, asking for help)
I have a Samsung Galaxy Tab GT-P1000, stock, rooted. Was installing an app yesterday from the play store, when the device rebooted and now it seems to be stuck in a boot loop.
At first I was afraid that it was the dreaded internal SD card corruption issue mentioned here: http://forum.xda-developers.com/showthread.php?t=1463756
However, when connecting with adb, I was unable to locate any references to the error mentioned in the post above :
Code:
<3>[ 4.802004] mmc0: error -110 whilst initialising MMC card
(Also tried the alternative option to list contents of /dev/block and was able to see several references to mmcblk)
Having said that, I haven't yet tried a wipe data/factory reset from the stock recovery because I am not sure if this will wipe my internal SD card contents. I do want to try to save/ copy out my pics etc. if there is a way to do this at all prior to wiping it. (And yes, I am kicking myself hard for not having backed this stuff up.)
I guess what I am asking for is:
a) Is there a way to recover from this without a complete device wipe?
b) If I do need to wipe from recovery, will I lose media/user data on the interal sd card?; and
c) If so, is there a way to retrieve all this data to a PC prior to wiping?
I have also attached the adb logcat file recorded during the bootloop.
Thanks All!!

Resolved
I guess this forum is not quite as alive as some of the others, which makes sense considering the age of this device.
In any case here is a quick summary of what I went thru to successfully get the device working again. (and I still have all my pics/videos )
a) Answer to my first question below - After a loooot of googling, I couldn't figure out a way to recover without a wipe.
b) Answer to my second question - You will NOT lose data on your internal SD card when you do a wipe from (stock) recovery.
c) Answer to third question - There may be, but I was unable to figure it out. I'm fairly certain you can mount the internal SD manually from ADB if you have root and attempt to pull your files to your PC, but my device didn't have a rooted kernel, so I couldn't quite get this done.
Anyway, my other issue was that my Stock recovery was unresponsive as well. On selecting the wipe option for example, the screen would clear itself of all text and just display the Android w/ Exclamation background. I attempted to flash CWM recovery based on the steps in this thread: http://forum.xda-developers.com/showthread.php?t=2430190
However, I ended up with a corrupt screen when attempting to access this new recovery. (Don't know - May be because of improper rooting?)
I was able to successfully restore the device by flashing the stock recovery and ROM based on this thread http://forum.xda-developers.com/showthread.php?t=1133590 ,following the instructions for un-softbricking .
When I booted into recovery and attempted to wipe/factory reset, I got an error.
Code:
rfs format failed on /dev/block/stl10
There was an additional step I had to take, which is clarified further below in the same thread. http://forum.xda-developers.com/showthread.php?p=27979493#post27979493 , which is to flash dbdata as well.
Doing this let me successfully wipe the device, which in turn let me finally get out of the damn bootloop.
Anyway, I hope all this helps someone. Thanks for being a great resource as usual XDA! :good:
Dagrat3One said:
Hello All,
Long time lurker, first time poster (and, as usual, asking for help)
I have a Samsung Galaxy Tab GT-P1000, stock, rooted. Was installing an app yesterday from the play store, when the device rebooted and now it seems to be stuck in a boot loop.
At first I was afraid that it was the dreaded internal SD card corruption issue mentioned here: http://forum.xda-developers.com/showthread.php?t=1463756
However, when connecting with adb, I was unable to locate any references to the error mentioned in the post above :
Code:
<3>[ 4.802004] mmc0: error -110 whilst initialising MMC card
(Also tried the alternative option to list contents of /dev/block and was able to see several references to mmcblk)
Having said that, I haven't yet tried a wipe data/factory reset from the stock recovery because I am not sure if this will wipe my internal SD card contents. I do want to try to save/ copy out my pics etc. if there is a way to do this at all prior to wiping it. (And yes, I am kicking myself hard for not having backed this stuff up.)
I guess what I am asking for is:
a) Is there a way to recover from this without a complete device wipe?
b) If I do need to wipe from recovery, will I lose media/user data on the interal sd card?; and
c) If so, is there a way to retrieve all this data to a PC prior to wiping?
I have also attached the adb logcat file recorded during the bootloop.
Thanks All!!
Click to expand...
Click to collapse

Hi, guys.......new to the process....rooted my galaxy tab p1000 2.2 froyo with z4mod.
Then initially I installed cwm with ROM manager for galaxy tab T because there wasn't any specific model of cwm for p1000.
But but when I switched off and booted recovery, stock recovery always came......I could access cwm only through the ROM manager ("boot into recovery")....and that too if i choose any function it starts to load and when I press home twice it says "replacing stock with cwm" and that goes on forever...
So I installed cwm with Odin as I couldn't access functions like "install" in cwm without going into the loading phase.....but as the process in Odin finished, my tab started to boot and at "galaxy", the sceen got all pixalated and it went till " samsung " and the whole process looped........ Help!

NookHD+ can't mount emmc; can't fully boot from SD recovery

Perhaps someone can help. I've read a lot of the great content here but I've hit a wall.
A few weeks ago my ovation device was running cm11+cwm but began random rebooting. Clearing the cache+dalvik only helped briefly.
I tried an upgrade with a twrp 3.0.0.0 (using the amazing multiboot recovery SD), but it hung formatting the cache partition (I waited about an hour). Tried again, same thing.
I used adb shell to fix a blank file system type on the cache partition but was only successful in creating an ext2 partition there. I got cm13 booting but it trebuchet kept crashing. I tried twrp again and flashing a different image and tried a factory reset. Big mistake.
Now when I try to boot any recovery SD it doesn't boot all the way. Using adb shell, my dmesg shows that umount is hanging. No emmc partitions seem to be mounted. The partition data exists in dmesg but calls to parted hang. Mkfs.ext4 also hangs (naturally).
So I've lost the ability to fully boot recovery SDs (they are probably hanging when they try to mount the emmc partitions). As such I can't flash a recovery. I have a clockwork backup that has a system.ext.tar file in it, but I don't know how to use it at this point.
I can't mount /rom so I'm worried.
Is my emmc shot? Is there any way to tell?
Thanks!

Would a noEMMC SD be safe?
I guess what I was hoping to do was use adb to completely wipe and restore the device to a sane state, which would include repartitioning and formatting the emmc partitions. Is that possible? Maybe not at this point.
I guess another question would be: if my NookHd+ emmc is technically working but currently unrecoverable, is it possible for me to safely use a NOemmc SD card? There seem to be some warnings about those wrecking emmc but I can't find any technical explanation as to why.

Based on further diagnostics, my emmc is one of the faulty Samsung models and so I think the crashes and ultimate recovery failures were the failure of the emmc.
I've successfully installed 10.1 noEMMC on one microsd. Runs Okay but a lot of apps I am interested in don't work on android from this vintage.
I tried to install 4.4.4/CM11 noEMMC but it can't mount the necessary partitions as per the install process on the iamafanof Wordpress page. I also see SELinux errors in the twrp recovery log. Does anyone know how to overcome this mount issue that apparently impacts some people.

Assuming there are others out there who find this useful, I have some updates.
I was determined to figure out why the CM11 NoEMMC was not working for me but CM10.2 noEMMC works fine. I get the error that many others get: unable to mount /boot, /data, /system.
I used adb shell to connect to the twrp 2.8.0.0 that runs when you boot the CM11 noEMMC SD boot/install image and compared the Linux system differences between that and the system you can see connected to the cwm 6.0.4.? That runs when you boot the CM10.2 noEMMC SD boot/instal image.
First things first: cm10 noEMMC remaps the internal emmc as /dev/block/emcblk1 and the external microsd card slot as blk0 (this is swapped from the norm and correct for a situation where you want to install to the SD as though it were the internal device).
CM11 noEMMC does not do this. I think that the author assumed that if your emmc is bricked then the system won't see your /dev/block/emmcblk0 at all so your external sdcard will take over that number. Clearly that's true for some, but it's not true for me.
I also began poking around the post boot script (in /sbin) to see how the cm11 noEMMC prepares the partitions on the Sd card and to see what Command it uses to create the data partition
Here's the kicker. I was able to mount my emmc rom partition and copy off all that data with an adb pull. I was able to initialize the cache partition (9) as a blank ext4 partition. I was even able to initialize the user partition (10) as ext4... Though I'm not sure that's right. I began mounting partitions and got greedy and tried to mount the whole partition map and it failed.
So, there's something wrong with (at least) one of my partitions. When recovery tries to mount the partitions, mount hangs and recovery fails to fully load. The noEMMC sd card got me around this because it doesn't try to mount any of the emmc partitions let alone all of them.
So, does anyone know if I can make new file systems on every partition and if by luck I'm able to get a twrp or cwm to fully load, will flashing a stock recovery put data on all those partitions?
Thanks

Sorry to resurrect this thread, But it exactly speaks to my issue. You mention that the blk0 and blk1 devices need to be switched for cm11 image to mount partitions properly. Does anyone know specifically where this might be done. Can files of the existing nov4 cm11 image be altered to reverse these two devices?

CalculonsTalent said:
Assuming there are others out there who find this useful, I have some updates.
I was determined to figure out why the CM11 NoEMMC was not working for me but CM10.2 noEMMC works fine. I get the error that many others get: unable to mount /boot, /data, /system.
I used adb shell to connect to the twrp 2.8.0.0 that runs when you boot the CM11 noEMMC SD boot/install image and compared the Linux system differences between that and the system you can see connected to the cwm 6.0.4.? That runs when you boot the CM10.2 noEMMC SD boot/instal image.
First things first: cm10 noEMMC remaps the internal emmc as /dev/block/emcblk1 and the external microsd card slot as blk0 (this is swapped from the norm and correct for a situation where you want to install to the SD as though it were the internal device).
CM11 noEMMC does not do this. I think that the author assumed that if your emmc is bricked then the system won't see your /dev/block/emmcblk0 at all so your external sdcard will take over that number. Clearly that's true for some, but it's not true for me.
I also began poking around the post boot script (in /sbin) to see how the cm11 noEMMC prepares the partitions on the Sd card and to see what Command it uses to create the data partition
Here's the kicker. I was able to mount my emmc rom partition and copy off all that data with an adb pull. I was able to initialize the cache partition (9) as a blank ext4 partition. I was even able to initialize the user partition (10) as ext4... Though I'm not sure that's right. I began mounting partitions and got greedy and tried to mount the whole partition map and it failed.
So, there's something wrong with (at least) one of my partitions. When recovery tries to mount the partitions, mount hangs and recovery fails to fully load. The noEMMC sd card got me around this because it doesn't try to mount any of the emmc partitions let alone all of them.
So, does anyone know if I can make new file systems on every partition and if by luck I'm able to get a twrp or cwm to fully load, will flashing a stock recovery put data on all those partitions?
Thanks
Click to expand...
Click to collapse
Could you please teach me how to mount EMMC partitions and retrieve data specially /factory partition with ADB?
I can only boot my Nook HD+ with with bootable SD card with TWRP or CWM.
Thanks.