Hey all,
Decided to downgrade from Modaco 2.3 to 2.2 as it was a little faster. Thought I would sort out the App2SD side of things too. I copied all of my SD card data off, then followed this guide:
http://android.modaco.com/content/htc-hero-hero-modaco-com/293461/how-to-partition-sdcard/
Once done I copied the SD contents back on and then downgraded to the 2.2 ROM. All back up and running but not sure if the apps have moved over as I expected them to do, is there a way to check? Otherwise what do I need to do to move them over to the SD?
Thanks
Russ
you don't need a2sd on hero.. it was only needed on g1 because of the low memory of 85 mb for apps..
hi roakes, there is already a thread that covers this:
http://forum.xda-developers.com/showthread.php?t=564932
you should have posted this in Q&A NOT Dev!!
The following post does not belong to me. I forgot who post it so all credits go to him/her:
To confirm whether A2SD is working properly from a terminal / ADB Shell type:
busybox df -h
You should see something along these lines below:
/dev/block/mccblk0p2 532.9M 67.1M 438.7M 13% /system/sd
The key is that you see one of the entries as /system/sd
This means that the phone is picked up your Ext2 partition.
Next if you see the above you can check that you setup the symlinks properly.
To do this type these cmds:
cd /data/app
pwd
The terminal returns /system/sd/app which means that the apps are now being saved onto the Ext2 Partition since the /system/sd = your Ext2 partition.
If it returns /data/app then the apps are still being installed onto the phone's internal rom.
Hope this helps, let me know if not.
Click to expand...
Click to collapse
Filesystem Size Used Available Use% Mounted on
tmpfs 96.2M 0 96.2M 0% /dev
/dev/block/mtdblock4 130.0M 1.3M 128.7M 1% /cache
That's what I am getting hmmmm doesnt look promising, but the partitions seem ok...
Number Start End Size Type File system Flags
1 512B 7425MB 7425MB primary fat32 lba
2 7425MB 7937MB 512MB primary ext3
3 7937MB 7969MB 32.0MB primary linux-swap(v1)
roakes said:
Filesystem Size Used Available Use% Mounted on
tmpfs 96.2M 0 96.2M 0% /dev
/dev/block/mtdblock4 130.0M 1.3M 128.7M 1% /cache
That's what I am getting hmmmm doesnt look promising, but the partitions seem ok...
Number Start End Size Type File system Flags
1 512B 7425MB 7425MB primary fat32 lba
2 7425MB 7937MB 512MB primary ext3
3 7937MB 7969MB 32.0MB primary linux-swap(v1)
Click to expand...
Click to collapse
Can anyone verify that this looks right?
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\DamianV>adb shell
* daemon not running. starting it now *
* daemon started successfully *
# busybox df -h
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 96.2M 0 96.2M 0% /dev
tmpfs 4.0M 0 4.0M 0% /sqlite_stmt_journals
/dev/block/mtdblock3 170.0M 149.9M 20.1M 88% /system
/dev/block/mtdblock5 165.8M 22.5M 143.3M 14% /data
/dev/block/mtdblock4 130.0M 1.1M 128.9M 1% /cache
/dev/block/mmcblk0p2 446.9M 8.0M 415.0M 2% /system/sd
/dev/block//vold/179:1
3.3G 94.5M 3.2G 3% /sdcard
#
roakes said:
Filesystem Size Used Available Use% Mounted on
tmpfs 96.2M 0 96.2M 0% /dev
/dev/block/mtdblock4 130.0M 1.3M 128.7M 1% /cache
That's what I am getting hmmmm doesnt look promising, but the partitions seem ok...
Number Start End Size Type File system Flags
1 512B 7425MB 7425MB primary fat32 lba
2 7425MB 7937MB 512MB primary ext3
3 7937MB 7969MB 32.0MB primary linux-swap(v1)
Click to expand...
Click to collapse
Can anyone verify that this looks right?
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\>adb shell
* daemon not running. starting it now *
* daemon started successfully *
# busybox df -h
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 96.2M 0 96.2M 0% /dev
tmpfs 4.0M 0 4.0M 0% /sqlite_stmt_journals
/dev/block/mtdblock3 170.0M 149.9M 20.1M 88% /system
/dev/block/mtdblock5 165.8M 22.5M 143.3M 14% /data
/dev/block/mtdblock4 130.0M 1.1M 128.9M 1% /cache
/dev/block/mmcblk0p2 446.9M 8.0M 415.0M 2% /system/sd
/dev/block//vold/179:1
3.3G 94.5M 3.2G 3% /sdcard
#
If you type:
cd /data/app
pwd
and it becomes this: /system/sd/app
Then it should be correct.
hi,
i am not sure what i am doing wrong here, I am using pinky's ROM and I have the default and used ROM manager to partition the SD card to a 512 MB ext3 and the remainder 14 GB as FAT32.
I have set the EXT4 module is enabled and App2SD is set to external.
But I still cant get the apps to install to SD, using the method above to check it. The Ext3 partition is being seen, but the symlinks are correct.
Any ideas?
Heres a dump from my CMD prompt
C:\android\tools>adb shell
sh-3.2# busybox df -h
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 207.6M 0 207.6M 0% /dev
tmpfs 207.6M 0 207.6M 0% /mnt/asec
/dev/block/mtdblock3 250.0M 181.6M 68.4M 73% /system
/dev/block/mtdblock5 147.6M 12.0M 135.6M 8% /data
/dev/block/mtdblock4 40.0M 1.1M 38.9M 3% /cache
tmpfs 8.0M 0 8.0M 0% /app-cache
/dev/block/mtdblock5 147.6M 12.0M 135.6M 8% /system/mnt/data
/dev/block/mmcblk0p2 457.4M 70.1M 362.9M 16% /system/sd
/dev/block/vold/179:1
14.6G 158.4M 14.5G 1% /mnt/sdcard
/dev/block/vold/179:1
14.6G 158.4M 14.5G 1% /mnt/secure/asec
sh-3.2# cd /data/app
cd /data/app
sh-3.2# pwd
pwd
/data/app
I'm running 2.03 and my browser started crashing so I did a reboot. Now I keep looping between the ViewSonic screen and gtablet screen. I've tried several restores through ClockWorkMod and it still doesn't work. I thought I could try to do the upgrade.zip off of a sd card but how do I get the system to recongize it and not the internal memory?
Stupid question : Have you done a user data wipe/system data wipe from CW?
If cw is not seeing the internal sd and the updates located on the internal sd are not working with full users data wipe, then a nvflash push from pc will have to be done to vanilla tnt, then do an update to get clockwork back, then tnt lite 2.0 with clockwork?
You might need to do a re-partition of your SD card (or rather, of the internal SD card memory) from clockwork mod. That has gotten other people out of a boot loop. This most likely has something to do with partitions getting corrupted, which seems to occasionally happen when you are flashing ROMs. You might want to search the forum for SD card partition and boot loop, I know several people have had the same issue.
There is also the APX mode as a backup mechanism if that fails. Search forum for that one too - it's basically a backup to the normal CW or other recovery that lets you flash a fresh ROM even if all else has failed. But I don't think you need to go there if your recovery is still working fine.
arrow21 said:
Stupid question : Have you done a user data wipe/system data wipe from CW?
Click to expand...
Click to collapse
Yes, tried nearly everything I can in Clock and nothing changes the loop. I thought in the worst case you could always find a way to get the system back to it's original state but no luck so far.
another option is this
http://forum.xda-developers.com/showpost.php?p=9439414&postcount=7
I have never done the partiton of my sdcard... so I guess that might work also.
arrow21 said:
another option is this
http://forum.xda-developers.com/showpost.php?p=9439414&postcount=7
I have never done the partition of my sdcard... so I guess that might work also.
Click to expand...
Click to collapse
HELP!!! I think my data partition just go hosed, all I tried to do was restore a backup since I was getting a lot of FC, all trying to access my data folder according to logcat....what do I do, will redoing the partition of my sdcard fix the errors below. How do I repartition and what settings do I use? I was trying to do the restore since I too got stuck in reboot loop. I have the logcat ouput if any dev is interested in seeing it.
Trying to restore backup in clockworkmod I get this:
ClockworkMod Recovery v2.5.1.1-bekit-0.8
Checking MD5 sums...
Erasing boot before restore
Restoring system...
Restoring data...
E:Can't mount /dev/block/mmcblk3p2
(Invalid argument)
Error mounting /data/!
Skipping format...
E:Can't mount /dev/block/mmcblk3p2
(Invalid argument)
Can't mount /data/!
rcgabriel said:
You might need to do a re-partition of your SD card (or rather, of the internal SD card memory) from clockwork mod. That has gotten other people out of a boot loop. This most likely has something to do with partitions getting corrupted, which seems to occasionally happen when you are flashing ROMs. You might want to search the forum for SD card partition and boot loop, I know several people have had the same issue.
There is also the APX mode as a backup mechanism if that fails. Search forum for that one too - it's basically a backup to the normal CW or other recovery that lets you flash a fresh ROM even if all else has failed. But I don't think you need to go there if your recovery is still working fine.
Click to expand...
Click to collapse
rc, thanks for the help. Honestly partitioning is something I've never fully understood so I wasn't even sure how to do that. I went into CW and then advanced settings and chose to partition the sd card. The only problem is I didn't know what settings to use so I just used the first ones to pop up. After doing that I did a reboot and things worked fine.
I was going to go back and try a CW restore and see if I could get everything back but now it can't find the restore file. I assume that happened when I tried to reformat the card.
scmobileman said:
I was going to go back and try a CW restore and see if I could get everything back but now it can't find the restore file. I assume that happened when I tried to reformat the card.
Click to expand...
Click to collapse
The restore files were are stored on the internal sdcard, so when you formatted, you wiped them out...is my guess. You could have used adb to save them off before hand and then put them back after format.
For the benefit of others, here is how I fixed this:
-Boot into clockworkmod
-Used adb to copy off all sdcard files (including backup files to use in restore)
-Use CW to partition the sdcard (2048mb ext, 256mb swap)
-Tried to copy backup files back...see issues below
-Restore backup files
-Back to working tab
Two issues I had, one is that for the life of me, I could not get the backup files back onto the sdcard. adb must not like windows because it had issues copying the files back unless you copy them to the root of the device. Even then I tried to shell into the device and move the files to the sdcard, but then CW would not see the files, when I reboot the device and try again, the files were gone. I tried to just copy the update.zip file, again CW didn't see the file, and reboot caused it to disappear as well. I managed to mount the tab in USB mode and copy the files to the sdcard using windows. Afterwards CW didn't see the files either.
I figured the system image was good, rebooted to start from scratch, and the setup program ran. I tried to tap the screen bu nothing would happen. Issue two from the log, is that it the setup wizard ignores touch evens if there is no phone interface...reboot again, back into CW, and this time it saw my backup files, restore, then good to go.
My next step would have been to delete the setupwizard apk, wipe data, boot into android, copy backup files, reboot, restore, but not needed finally.
Have other people run into the above issue where you copy files to the sdcard uin adb while within CW, and the files don't stick. How do you get around this?
raydog.. thank you thank you thank you
thanks
raydog, your post helped greatly. thank you.
Life in LA said:
raydog, your post helped greatly. thank you.
Click to expand...
Click to collapse
Thanks, sad to say I am back in a reboot loop, so I have to do this all over again...uggg
I have shut my tablet off by holding down the power button and bypassing the shutdown screen, wonder if this corrupted the data partition.
I had the reboot problem when trying to load 2.0.0
My fix: Loaded original vanilla via sdcard (took two load tries) then retried 2.0.0 via sdcard and it worked.
please help to make my data read write
raydog153 said:
Have other people run into the above issue where you copy files to the sdcard uin adb while within CW, and the files don't stick. How do you get around this?
Click to expand...
Click to collapse
1|[email protected]:/sbin # su
[email protected]:/sbin # is
sh: is: not found
127|[email protected]:/sbin # cat /proc/mounts
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/FACTORYFS /system ext4 ro,seclabel,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/EFS /efs ext4 rw,seclabel,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/DATAFS /data ext4 ro,seclabel,nosuid,nodev,noatime,user_xattr,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/CACHE /cache ext4 rw,seclabel,nosuid,nodev,noatime,user_xattr,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
[email protected]:/sbin # mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/FACTORYFS /system ext4 ro,seclabel,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/EFS /efs ext4 rw,seclabel,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/DATAFS /data ext4 ro,seclabel,nosuid,nodev,noatime,user_xattr,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/CACHE /cache ext4 rw,seclabel,nosuid,nodev,noatime,user_xattr,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
[email protected]:/sbin # fs
sh: fs: not found
127|[email protected]:/sbin # df
Filesystem Size Used Free Blksize
/dev 407.7M 32.0K 407.6M 4096
/sys/fs/cgroup 407.7M 12.0K 407.7M 4096
/mnt/asec 407.7M 0.0K 407.7M 4096
/mnt/obb 407.7M 0.0K 407.7M 4096
/system 1.3G 443.6M 934.3M 4096
/efs 19.7M 8.1M 11.5M 4096
/data 11.9G 5.5G 6.3G 4096
/cache 689.0M 129.8M 559.1M 4096
/mnt/shell/emulated 11.9G 5.5G 6.3G 4096
[email protected]:/sbin # cat /proc/partitions
major minor #blocks name
179 0 15388672 mmcblk0
179 1 20480 mmcblk0p1
179 2 2048 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 8192 mmcblk0p6
179 7 716800 mmcblk0p7
259 0 20480 mmcblk0p8
259 1 1433600 mmcblk0p9
259 2 12640239 mmcblk0p10
259 3 524288 mmcblk0p11
179 16 2048 mmcblk0boot1
179 8 2048 mmcblk0boot0
[email protected]:/sbin # format 259
sh: format: not found
127|[email protected]:/sbin # del
sh: del: not found
127|[email protected]:/sbin # mount /efs rw
Usage: mount [-r] [-w] [-o options] [-t type] device directory
1|[email protected]:/sbin # mount -o rw,remount /efs
[email protected]:/sbin # mount -o rw,remount /dev
[email protected]:/sbin # mount -o rw,remount /sys/fs/cgroup
[email protected]:/sbin # mount -o rw,remount /mnt/asec
[email protected]:/sbin # mount -o rw,remount /mnt/obb
[email protected]:/sbin # mount -o rw,remount /system
[email protected]:/sbin # mount -o rw,remount /syste
Usage: mount [-r] [-w] [-o options] [-t type] device directory
1|[email protected]:/sbin # mount -o rw,remount /efs
[email protected]:/sbin # mount -o rw,remount /data
mount: Read-only file system
255|[email protected]:/sbin # mount -o rw,remount /data
mount: Read-only file system
255|[email protected]:/sbin # mount -o rw,remount /cache
[email protected]:/sbin # mount -o rw,remount /mnt/shell/emulated
[email protected]:/sbin # mount -o rw,remount /data
mount: Read-only file system
255|[email protected]:/sbin # mount -o rw,remount /data
mount: Read-only file system
255|[email protected]:/sbin # mount -o rw
Usage: mount [-r] [-w] [-o options] [-t type] device directory
1|[email protected]:/sbin # mount -o rw, del /data
Usage: mount [-r] [-w] [-o options] [-t type] device directory
1|[email protected]:/sbin # mount -o rw,del /data
Usage: mount [-r] [-w] [-o options] [-t type] device directory
1|[email protected]:/sbin # help
sh: help: not found
127|[email protected]:/sbin # Read-only file system
sh: Read-only: not found
127|[email protected]:/sbin # rw
sh: rw: not found
127|[email protected]:/sbin # mount -o rw,remount /data
mount: Read-only file system
255|[email protected]:/sbin # mount -o rw,remount /data
mount: Read-only file system
255|[email protected]:/sbin #
this is my partition table and errors for p3100.
please help me how to make it read write.
please mailm e the steps.
[email protected]
thanks in advance
Hello,
I am flashing roms since nearly two years and I got my first big problem 2 days ago.
My GT-i9100 (DBT Germany) was running stable under cm-12.1-20150611-UNOFFICIAL-i9100.zip brought by Lysergic Acid.
When I tried to log on WLAN on Tuesday morning, my rom crashed with a few percent of energy remaining. I charged my battery and started the phone again. I had a message "No Service" and a barred circle. Pin Code was being asked, as well as my lock screen Pin Code.
I thought it was a mobile network operator issue, and that it would be temporary. Didn't care about it, I was able to log in my WLAN network. Then I saw an update (06/17) on xda, that I downloaded and flashed following the installation instructions. I noticed still the "No service" message and the circle barred. I looked at my telephone settings an saw Unknown Baseband, No Signal, Unknown Imei. When I called *#6#, there was a popup with only the Text IMEI no number.
Finally I did sthg really stupid (I didn't google Unknown Baseband Unknown Imei at this time), because I thought wrongly that the issue is a rom, modem or csc issue. Then I decided to flash back to a stable jelly bean version.
Thus, I had to flash the partition with Stock i9100 pit, because I was using a preload modified area partition before.
Then I made my great mistake, that's what I think now, I think I corrupted my /efs folder. I installed a stock firmware from sammobile on my SII (still no service, unknown baseband), then rooted the phone again, and installed
ASNET MIUI v5 (4.8.10) everything is working except this my mobile network unknown baseband, unknown Imei, etc
I tried to look on my external harddrive, if I had any backups from my phone, did not have any /efs backup. :crying:
With root explorer I am able to to see the /efs folder no file is missing I think, but it is certainly corrupt. I am joining a .tar file of this folder here. https mega.nz/#!4IZijDTK!2eZ1lhC01bTEcbzwP7OVe8tePiIm5GNQ_dwpZRZHF0k
~ $ mount
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mmcblk0p9 on /system type ext4 (ro,relatime,barrier=1,data=ordered)
/dev/block/mmcblk0p7 on /cache type ext4 (rw,nosuid,nodev,noatime,errors=panic,barrier=1,journal_async_commit,data=ordered)
/dev/block/mmcblk0p1 on /efs type ext4 (rw,nosuid,nodev,noatime,errors=panic,barrier=1,journal_async_commit,data=writeback)
/dev/block/mmcblk0p12 on /preload type ext4 (ro,nosuid,nodev,noatime,barrier=1,data=ordered)
/dev/block/mmcblk0p10 on /data type ext4 (rw,nosuid,nodev,noatime,errors=panic,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard)
/dev/block/mmcblk0p4 on /mnt/.lfs type j4fs (rw,relatime)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,relatime)
/dev/block/vold/259:3 on /storage/sdcard0 type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro,discard)
~ $ su
[email protected]:/ # #
[email protected]:/ #
[email protected]:/ # df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 422816 76 422740 0% /dev
tmpfs 422816 0 422816 0% /mnt/asec
tmpfs 422816 0 422816 0% /mnt/obb
/dev/block/mmcblk0p9 516040 453384 62656 88% /system
/dev/block/mmcblk0p7 100784 4160 96624 4% /cache
/dev/block/mmcblk0p1 20144 10492 9652 52% /efs
/dev/block/mmcblk0p12
516040 77688 438352 15% /preload
/dev/block/mmcblk0p10
2064208 306208 1758000 15% /data
df: /mnt/.lfs: Function not implemented
/dev/block/vold/259:3
12063840 445792 11618048 4% /storage/sdcard0
1|[email protected]:/ # mount /efs
mount: can't read '/etc/fstab': No such file or directory
1|[email protected]:/ # mount /data
mount: can't read '/etc/fstab': No such file or directory
1|[email protected]:/ # mount /preload
mount: can't read '/etc/fstab': No such file or directory
1|[email protected]:/ # mount /cache
mount: can't read '/etc/fstab': No such file or directory
1|[email protected]:/ # mount /system
mount: can't read '/etc/fstab': No such file or directory
I still have the IMEi on the back of my phone.
Is there a way to fix this or is it impossible?