Is this how A2SD supposed to work?
I have MCR R8 with old school A2SD installed, and have a 512MB ext2 partition on my SD card. Lately I have been getting the "low on space" warning all the time when I install new apps, and have to uninstall some apps in order to put some new apps on.
Upon checking, all my apps are only using about 70MB of my ext2 partition, and there is still 400MB+ space left there. On the other hand, there is only about 20MB left on my phone storage, causing the "low on space" warning popping up whenever I put new apps onto my phone. I've noticed that when a new app is installed, only part of it goes to my ext2 partition, while the remaining goes to my phone storage.
For example, this is some partial output of "adb shell df -h" before and after Google Earth is installed:
Before:
/dev/block/mtdblock5 147.6M 126.3M 21.3M 86% /data
/dev/block/mtdblock4 40.0M 22.4M 17.6M 56% /cache
tmpfs 8.0M 0 8.0M 0% /app-cache
/dev/block/mmcblk0p2 457.4M 67.4M 365.6M 16% /system/sd
Click to expand...
Click to collapse
After:
/dev/block/mtdblock5 147.6M 141.4M 6.3M 96% /data
/dev/block/mtdblock4 40.0M 22.4M 17.6M 56% /cache
tmpfs 8.0M 0 8.0M 0% /app-cache
/dev/block/mmcblk0p2 457.4M 72.8M 360.2M 17% /system/sd
Click to expand...
Click to collapse
i.e. only about 5MB of Google Earth installation went to the SD card, while the other 15MB was installed on the phone storage.
I'm up to the point that I always have to remove apps in order to installed new ones... which is kind of frustrating...
Additional information (is this how a properly installed A2SD supposed to look?):
C:\AndroidSDK\android-sdk-windows\tools>adb shell ls -l /data
drwxrwxr-x 1 1000 1000 2048 Aug 8 19:06 ←[1;34manr←[0m
lrwxrwxrwx 1 0 0 14 Aug 18 14:47 ←[1;36mapp←[0m -> ←[1;34m/system/sd/app←[0m
lrwxrwxrwx 1 0 0 22 Aug 5 14:51 ←[1;36mapp-private←[0m -> ←[1;34m/system/sd/app-private←[0m
drwxr-xr-x 1 0 0 2048 Aug 5 14:47 ←[1;34mase←[0m
drwx------ 1 1000 1000 2048 Aug 5 14:53 ←[1;34mbackup←[0m
drwxrwx--x 1 1000 1000 2048 Aug 25 12:43 ←[1;34mdalvik-cache←[0m
drwxrwx--x 1 1000 1000 2048 Aug 25 12:43 ←[1;34mdata←[0m
drwxr-x--- 1 0 1007 2048 Aug 5 14:51 ←[1;34mdontpanic←[0m
lrwxrwxrwx 1 0 0 11 Aug 5 14:51 ←[1;36mdrm←[0m -> ←[1;34m/data/local←[0m
drwxr-xr-x 1 0 0 2048 Aug 5 14:47 ←[1;34metc←[0m
drwxrwx--x 1 2000 2000 2048 Aug 18 14:38 ←[1;34mlocal←[0m
drwxrwx--- 1 0 0 2048 Aug 5 14:51 ←[1;34mlost+found←[0m
drwxrwx--t 1 1000 9998 2048 Aug 25 17:14 ←[1;34mmisc←[0m
drwx------ 1 0 0 2048 Aug 25 12:17 ←[1;34mproperty←[0m
drwxrwxr-x 1 1000 1000 2048 Aug 25 18:24 ←[1;34msystem←[0m
Click to expand...
Click to collapse
How many apps have you got installed? A simple cache clear could sort your issues as I had the same on Pays rom.
Sent from my HTC Desire using XDA App
cache or dalvik-cache?
I tried "wipe cache" using Amon-RA and it didn't help. Going to try "wipe dalvik-cache" next...
EDIT: ok, wiping dalvik cache didn't help either
Is it normal that when you install Google Earth, 15MB goes to phone storage and 5 MB goes to ext partition?
anyone????
tsekh501 said:
Is it normal that when you install Google Earth, 15MB goes to phone storage and 5 MB goes to ext partition?
Click to expand...
Click to collapse
yes...its one of the app´s...some app´s still need this
Depending on the ROM you're using, if it has bulitin aufs capability, you can modify the script i posted a while ago (in the aufs writeable /system thread) to overlay /data/data and /data/app with the writeable partition. Then you really don't need a2sd/app2sd or any 'move to sdcard' froyo support as your apps magically have lots more storage to write to.
I'm currently using this on CM6 and have been installing huge apps like Fennec and Asphalt with no issues.
Hi,
I've moved to Oxygen 2.3 recently because I wanted always to get rid of Low space messages. I created partition on SD card (1GB ext3), but I am still getting Low space message.
Why android is putting still some apps do /data/data ? Furthermore, is it safe to move dalvik cache? I know there are some tutorials, but they are quite old, that's why I'm asking it..
mount:
Code:
/data/data/berserker.android.apps.sshdroid/home # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 202.9M 32.0K 202.9M 0% /dev
tmpfs 202.9M 0 202.9M 0% /mnt/asec
tmpfs 202.9M 0 202.9M 0% /mnt/obb
/dev/block/mtdblock3 250.0M 95.6M 154.4M 38% /system
/dev/block/mtdblock5 147.6M 132.9M 14.7M 90% /data
/dev/block/mtdblock4 40.0M 1.1M 38.9M 3% /cache
/dev/block/mmcblk0p2 902.0M 89.2M 767.1M 10% /sd-ext
/dev/block/vold/179:1
2.8G 2.5G 298.4M 90% /mnt/sdcard
/dev/block/vold/179:1
2.8G 2.5G 298.4M 90% /mnt/secure/asec
/dev/block/dm-0 4.1M 2.5M 1.6M 62% /mnt/asec/com.google.android.apps.docs-1
/dev/block/dm-1 4.1M 2.4M 1.7M 58% /mnt/asec/com.metago.astro-1
/dev/block/dm-2 3.1M 1.7M 1.3M 56% /mnt/asec/ro.hex.installers.mc-1
/dev/block/dm-3 2.0M 52.0K 2.0M 2% /mnt/asec/net.maicas.android.batterys-1
/dev/block/dm-4 3.1M 2.0M 1.1M 65% /mnt/asec/com.estrongs.android.pop-1
/dev/block/dm-5 5.1M 3.2M 1.8M 64% /mnt/asec/com.facebook.katana-1
Quick system info pro:
storage: free/total
SD card storage: 298MB/2.79GB
A2SD storage: 767MB/0.88GB
Internal storage: 14.71MB/148MB
System storage: 154MB/250MB
System cache: 298MB/2.79GB
ls -l /data
Code:
/data # ls -l
total 23
drwxrwxr-x 1 1000 1000 2048 Oct 10 19:46 anr
lrwxrwxrwx 1 0 0 11 Oct 10 17:01 app -> /sd-ext/app
lrwxrwxrwx 1 0 0 19 Oct 10 17:01 app-private -> /sd-ext/app-private
drwx------ 1 1000 1000 2048 Oct 11 11:55 backup
drwxrwx--x 1 1000 1000 2048 Oct 11 16:53 dalvik-cache
drwxrwx--x 1 1000 1000 2048 Oct 11 16:25 data
drwxr-x--- 1 0 1007 2048 Oct 10 17:01 dontpanic
drwxrwx--x 1 2000 2000 2048 Oct 10 17:01 local
drwxrwx--- 1 0 0 2048 Oct 10 17:01 lost+found
drwxrwx--t 1 1000 9998 2048 Oct 11 16:28 misc
drwx------ 1 0 0 2048 Oct 10 20:52 property
drwx------ 1 1000 1000 2048 Oct 10 17:02 secure
drwxrwxr-x 1 1000 1000 2048 Oct 11 18:16 system
Directory sizes:
Code:
/data # du -sc * | sort -n -r | head -n 10
131631 total
72847 dalvik-cache
58353 data
295 system
73 anr
35 misc
13 backup
4 secure
4 property
4 local
/data/data is never moved unless you use the latest (beta?) Dark tremor a2sd.
Dalvik-cache is safe to move and most a2sd solutions do this. Not sure what a2sd solution oxygen comes with though
Sent from my HTC Desire using XDA App
Please use the Q&A Forum for questions Thanks
Moving to Q&A
rootSU said:
Not sure what a2sd solution oxygen comes with though
Click to expand...
Click to collapse
That what you wrote
For starters, change your hboot to oxygen. This way your internal memory will run almost the same way as without sd-ext partition.
erklat said:
That what you wrote
For starters, change your hboot to oxygen. This way your internal memory will run almost the same way as without sd-ext partition.
Click to expand...
Click to collapse
Ok, I will change the HBOOT. Can you please tell me what version from the AlphaRev.nl download table is suitable for my phone ? The first one ? Thank you very much.
Bravo Stock 250M 40M 147M 7bd5234711364880de1fa982dcf3a2d6 bravo_alphaspl.img PB99IMG_stock
Oxygenr2. Make nandroid backup, wipe everything you flash hboot and then make a nandroid restore. Your low space issues should be gone.
I've had BusyBox Free on my Nexus for many months... only there to keep me on the latest version. Well, yesterday it told me about 1.20.2 so I let it install that but it was a big mistake.
The memory is locked at read only now. I can even see last files written to it were...
busybox-stericson
toolbox-stericson
It crashes if I don't quickly put it in airplane mode, for example. I can push and delete files via adb, but that's only fake because once the buffer fills with backlogged changes, the phone crashes. In fastboot, erasing userdata, etc. doesn't really erase anything. Locking/Relocking the bootloader doesn't reallly take effect either, and neither does reflashing recovery. Formatting the internal memory doesn't have an effect, and while restoring a recovery backup goes through the motions, it complains at the end about the memory being read only.
I wrote the BusyBox Free developer an email last night but didn't get a response yet.
I don't know how this is possible.
BusyBox doesn't change anything to read only, except for /system, which is suppose to be read only anyways.
Besides this point, anything Busybox would have done, in regards to remounting partitions to rw, ro, or whatever a reboot would reset these to their defaults.
I suspect something else is going on. Maybe an applet or something of the like has been replaced that is causing this issue, but I have never heard of my installer causing an issue like this.
also, those files you are talking about being written, are written to you SDCard or internal storage which is not a part of your phones system memory.
Stericson said:
... those files you are talking about being written, are written to you SDCard or internal storage which is not a part of your phones system memory.
Click to expand...
Click to collapse
The Galaxy Nexus lumps all its memory in one 32GB pool (internal with SD) which is normally great compared to all my other Android devices. Regardless, writes to any of the filesystems don't appear to get committed from a buffer.
Anyways, thanks for the response. I'm gonna' have to do some more research and hope there's nothing wrong at the hardware layer (eg. write-enable/disable trace on chip). Physically, my phone is pampered and in mint condition.
I would say that's pretty dang good response time from the dev, and on the forum, even.
:good:
consultant.ben said:
I would say that's pretty dang good response time from the dev, and on the forum, even.
Click to expand...
Click to collapse
I agree, Ben. I have to remember this is more of a volunteer effort here, unlike at work where I'm a product engineer with certain response time criteria.
Hmmm, even with the memory being all internal I don't change any of the write permissions on the external storage...
Did you replace any applets?
Did you use smart install or normal install?
Maybe some applet got replaced that otherwise shouldnt have been...
If you run a logcat, do you notice any weird errors....if so, what are they stating?
Also, when your phone crashes, can you give us the actual logcat of the crash?
Also, I try to respond as quick as possible, but I have so little time to dedicate to my own personal applications nowadays
I didn't replace any applets, and have never used your applet manager. Also, normally I wait for your smart install to scan, but I remember I did something abnormal that day and impatiently hit install (ie. normal install) while it was doing its smart scan. It reported successfully installing 1.20.2 though.
Per your request... adb logcat -d -v time > logfile.txt
I put that file on my website at http://ErichMoraga.com/logcat.txt
I pulled the SIM card so I wouldn't have to put it into airplane mode, and got the logcat once the OS loaded after a crash. At first I thought this part was curious...
07-08 12:18:01.234 I/SystemServer( 186): Mount Service
07-08 12:18:01.234 D/MountService( 186): got storage path: /mnt/sdcard description: Internal Storage primary: true removable: false emulated: true mtpReserve: 100 allowMassStorage: false maxFileSize: 0
07-08 12:18:01.234 D/MountService( 186): using emulated external storage
But then I searched on the Internet and noticed other people had that too. This logcat didn't appear to catch the actual crash (I don't see how it could if I'm having a read only memory problem).
I understand we both don't have much free time, being technical people. Normally I'm analyzing logs for customers, so it's frustrating 'shooting my own device. I do appreciate any insight anyone has, and am concerned this could happen to other people too.
Well, I bought myself another Nexus so I'd have something to keep me going. I also disassembled my faulty one to inspect the module with the 32GB Sandisk memory, but couldn't see anything wrong with it. If I can find a replacement, I can easily swap modules I suppose...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What about the output of adb shell ls -l --color=never /system/bin? Maybe one of the necessary programs (e.g. mount) is missing or has a dead link.
-Snags
Snags697 said:
What about the output of adb shell ls -l --color=never /system/bin? Maybe one of the necessary programs (e.g. mount) is missing or has a dead link.
Click to expand...
Click to collapse
Thanks for the response, Snags. I uploaded output to that here...
http://ErichMoraga.com/color.txt
I haven't scoured that for yet for missing programs, dead links, etc. Mount seems to be there...
lrwxrwxrwx 1 0 0 19 Jul 5 2012 mount -> /system/bin/busybox
Since there's so much BusyBox redirection going on there, it still supports my theory that the BusyBox installation was the root cause of the read only memory issue.
I'm sure there is a way to debug the Nexus in real-time. I'll have to find out the command for that (ie. dump threads, etc. as they occur to my PC via USB). A reliable way to crash the phone is to wait about 5 seconds into the scan at... Settings > Storage
I also noticed other people have similar problems not being able to write any of their memory...
http://forum.xda-developers.com/showthread.php?t=1756111
I'm a Linux guy and just learning Android. My first impression would be to double-check with a known writable directory. If you can't write in the /data/local directory (adb push anyfile /data/local/), check the mount status of everything: adb shell toolbox mount should do that with the native toolbox instead of busybox. Each entry should list either "rw" or "ro" amidst the gibberish. If /data is "ro", remounting from a root prompt (toolbox mount -o remount,rw ... /data) (Note: no space before rw, and replace ... with whatever was listed before /data in the list of mounted filesystems above) may give you write access to /data/local.
Then again, I think this is pointless, because if fastboot can't write to the internal SD (like the link you posted), something hardware-related or partition-related must be going on. Maybe the partition table got fried. Fastboot is only willing to write whole partitions that are genuine, I think. So if the partitions are messed up, it may prevent fastboot from doing anything. To see the partition table, you'd need root (there's a hole in the bucket...) and from a root prompt, run: parted /dev/block/mmcblk0 then from the (parted) prompt, type print. Quit or exit should get you out of there. Compare the output to "Need a copy of a stock GSM Nexus partition table" (Google it, I can't post links yet).
Of course, if you don't have root, this all doesn't help.
-Snags
Well, Snags, let's just say great minds think alike :good:
Also, I have root, and bought another Nexus that should arrive this week to play with that I'll flash with a nandroid backup from a couple weeks ago. The mount output looked fine...
rootfs on / type rootfs (ro,noatime)
tmpfs on /dev type tmpfs (rw,nosuid,noatime,mode=755)
devpts on /dev/pts type devpts (rw,noatime,mode=600)
proc on /proc type proc (rw,noatime)
sysfs on /sys type sysfs (rw,noatime)
none on /acct type cgroup (rw,noatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,noatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,noatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,noatime,cpu)
/dev/block/platform/omap/omap_hsmmc.0/by-name/system on /system type ext4 (rw,noatime,barrier=1,data=ordered,noauto_da_alloc)
/dev/block/platform/omap/omap_hsmmc.0/by-name/userdata on /data type ext4 (rw,nosuid,nodev,noatime,errors=panic,barrier=0,nomblk_io_submit,data=ordered,noauto_da_alloc)
/dev/block/platform/omap/omap_hsmmc.0/by-name/cache on /cache type ext4 (rw,nosuid,nodev,noatime,errors=panic,barrier=0,nomblk_io_submit,data=ordered,noauto_da_alloc)
/dev/block/platform/omap/omap_hsmmc.0/by-name/efs on /factory type ext4 (ro,noatime,barrier=1,data=ordered,noauto_da_alloc)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,noatime)
/dev/block/platform/omap/omap_hsmmc.0/by-name/userdata on /mnt/sdcard type ext4 (rw,nosuid,nodev,noatime,errors=panic,barrier=0,nomblk_io_submit,data=ordered,noauto_da_alloc)
/sbin # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: MMC SEM32G (sd/mmc)
Disk /dev/block/mmcblk0: 31.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 524kB 4194kB 3670kB sbl
3 4194kB 25.2MB 21.0MB ext4 efs
4 25.2MB 33.6MB 8389kB param
5 33.6MB 37.7MB 4194kB misc
6 37.7MB 41.9MB 4194kB dgs
7 41.9MB 50.3MB 8389kB boot
8 50.3MB 62.8MB 12.5MB recovery
13 62.8MB 62.9MB 65.5kB metadata
9 62.9MB 79.7MB 16.8MB radio
10 79.7MB 765MB 686MB ext4 system
11 765MB 1218MB 453MB ext4 cache
12 1218MB 31.9GB 30.7GB ext4 userdata
I've also included some other stuff...
</etc/fstab>
/dev/block/platform/omap/omap_hsmmc.0/by-name/cache /cache ext4 rw
/dev/block/platform/omap/omap_hsmmc.0/by-name/userdata /data ext4 rw
/dev/block/platform/omap/omap_hsmmc.0/by-name/system /system ext4 rw
</etc/recovery.fstab>
# mount point fstype device
# there is no actual sdcard in this thing...
#/sdcard vfat /dev/block/sda1
/system ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/system
/cache ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/cache
/data ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/userdata
/misc emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/misc
/boot emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/boot
/recovery emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/recovery
/sbl emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/sbl
/xloader emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/xloader
/radio emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/radio
Bear in mind I have a Verizon CDMA phone, so the partition table is different than GSM's (32GB vs. 16GB). Oddly enough, I couldn't locate the CDMA version online. Here is one of the the GSM versions I found...
Model: MMC VYL00M (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 524kB 4194kB 3670kB sbl
3 4194kB 25.2MB 21.0MB ext4 efs
4 25.2MB 33.6MB 8389kB param
5 33.6MB 37.7MB 4194kB misc
6 37.7MB 41.9MB 4194kB dgs
7 41.9MB 50.3MB 8389kB boot
8 50.3MB 62.8MB 12.5MB recovery
13 62.8MB 62.9MB 65.5kB metadata
9 62.9MB 79.7MB 16.8MB radio
10 79.7MB 765MB 686MB ext4 system
11 765MB 1218MB 453MB cache
12 1218MB 15.8GB 14.5GB userdata
The only differences were the specification of ext4 in mine under 11 & 12, as well as the size in 12. I also noticed Koush documented the recovery.fstab to have "auto" for /data instead of ext4 like mine. Worst case, I can run some comparisons between my 2 phones when the new one arrives. It won't be hard to push the correct changes if found.
Yet another person has the same problem as me... [writing to the memory card isn't actually committed, effectively making it read-only]
http://forum.xda-developers.com/showthread.php?p=28707474
My new phone will arrive Monday so I'll be able to perform more comparative analysis then. That said, since parted can't even make effective changes (I already tried), this may be a tricky fix.
If you don't mind the fact that it'll result in a full wipe including internal storage, you could try:
Open up any Google official ROM and extract the userdata img file.
Go into fastboot and flash that img. Reboot. Let it go through the full reboot process.
If something went wonky with how the partition is configured, that should set it straight. If it's a hardware problem you are still boned.
ErichMoraga said:
Yet another person has the same problem as me... [writing to the memory card isn't actually committed, effectively making it read-only]
http://forum.xda-developers.com/showthread.php?p=28707474
My new phone will arrive Monday so I'll be able to perform more comparative analysis then. That said, since parted can't even make effective changes (I already tried), this may be a tricky fix.
Click to expand...
Click to collapse
So yes, it seems i have a pretty similar problem with mine : nothing can be written anymore on the internal memory, whatever i can try : in recovery, in windows or with a file manager in the phone. Plus it is in bootloops constantly.
But i haven't touch at Busybox at all ; i mean it comes with Trinity kernel i use, so i don't bother to install or update it....Problem appeared just after this procedure :
- Downloaded a new Rom
- Rebooted to recoverry (TWRP)
- Made a Nand
- Wiped cache/dalvik/data
-Flashed new Rom/ gapps
-Rebooted...in the old configuration, just as if i've done nothing ! O_O......then i knew something was getting really bad....
As i said in the other thread (http://forum.xda-developers.com/showthread.php?t=1756334&page=2) i've just sent it to Samsung for repair under warranty...so i'll tell you in about 2/3 weeks when they'll return it, if they accept it, becaused even if I relocked the bootloader, it is still rooted.....but as it is surely a hardware problem, the warranty should work.
Anyway, i read somewhere that people had experienced this kind of issue after a "bad nandroid", or EMMC (?)....i'm not sure of what it means though....
Yeah, I'm leaning towards the hardware side too. It looks like the SANDISK NAND that Samsung used in the Nexus is a bit unstable. Also, I ran...
fastboot flash userdata userdata.img
sending 'userdata' (139193 KB)...
OKAY [ 15.448s]
writing 'userdata'...
OKAY [ 9.876s]
finished. total time: 25.325s
Not surprisingly the data was unchanged when I booted up. I might call Samsung later today to get the ball rolling.
ErichMoraga said:
Yeah, I'm leaning towards the hardware side too. It looks like the SANDISK NAND that Samsung used in the Nexus is a bit unstable. Also, I ran...
fastboot flash userdata userdata.img
sending 'userdata' (139193 KB)...
OKAY [ 15.448s]
writing 'userdata'...
OKAY [ 9.876s]
finished. total time: 25.325s
Not surprisingly the data was unchanged when I booted up. I might call Samsung later today to get the ball rolling.
Click to expand...
Click to collapse
Yeah, that's not surprising me...let's them repair their **** after all....
Samsung was pretty quick with the repair. There was a status update yesterday...
"The unit has left the technician. SOLUTION: Replaced Component - PRL Updated - S/W Updated - Passed"
I assume they replaced the module that holds the SIM slot and SANDISK chip. I'm sure I'll receive the phone soon, although I've been using a backup i515 I bought on eBay earlier.
Good day fellow xda-developers!
I am currently have a problem with my galaxy ace 2 ( GT-I8160). My brother by accident and through Odin erased some partition files! He ticked Nand erased all and since then the mobile shows the first screen writting Samsung Galaxy Ace 2 GT-I8160 and then reboots.
More specific:
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found..
I:Cannot load volume /misc
I:Can't partition non mmcblk device: /devices/sd i2/mmc_host/mmc0/mmc0
I have tried many Official roms by sammobile but no luck, i tried from here an official rom given with PDA,CSC and pit but still nothing.
I have even tried to flash through CWM many custom roms but still nothing. Some off them showed to be done correctly but still then it showed the first screen and then restarted.
Has anyone any idea how to fix it? Can someone provide me with a CWM back up to try to flash it?
@matlowpap, you PMed me:
matlowpap said:
Do you have any CWM back up to send me to try flash through there? I want to see if it will flash the missing partitions..
Click to expand...
Click to collapse
Not sure if flashing CWM backup will help here, since even flashing an official ROM didn't help. Probably your best bet is to try recovering deleted partitions via parted. Have you tried to repart internal sdcard via CWM ReParted? If no, then first connect the phone to PC via adb and run:
Code:
parted /dev/block/mmcblk0
print
If even this is not working, it's likely to be a hardware fault. Otherwise this command will print partition list. Compare output with this one
Code:
Model: MMC SEM04G (sd/mmc)
Disk /dev/block/mmcblk0: 3959MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
10 524kB 1573kB 1049kB PIT
6 1573kB 3146kB 1573kB CSPSA FS
7 4194kB 14.7MB 10.5MB ext4 EFS
2 14.7MB 31.5MB 16.8MB ext4 Modem FS
14 32.5MB 34.6MB 2097kB SBL
16 34.6MB 36.7MB 2097kB SBL_2
1 36.7MB 53.5MB 16.8MB PARAM
12 53.5MB 55.6MB 2097kB IPL Modem
13 55.6MB 72.4MB 16.8MB Modem
15 72.4MB 89.1MB 16.8MB Kernel
17 89.1MB 106MB 16.8MB ext4 Kernel2
3 106MB 726MB 620MB ext4 SYSTEM
5 726MB 1972MB 1246MB ext4 DATAFS
4 1972MB 1982MB 10.0MB ext4 CACHEFS
9 1982MB 2602MB 620MB ext4 HIDDEN
8 2602MB 2702MB 100MB fat32 UMS
11 2702MB 3949MB 1247MB
to find out what partitions to restore. Note that CWM reparted doesn't touch any of "vital" partitions, and will recreate only System, data, cache and UMS. If some other partitions are missing, you have to create them via parted utility.
P.s. Be sure to read that topic in link above before flashing anything.
ChronoMonochrome said:
@matlowpap, you PMed me:
Not sure if flashing CWM backup will help here, since even flashing an official ROM didn't help. Probably your best bet is to try recovering deleted partitions via parted. Have you tried to repart internal sdcard via CWM ReParted? If no, then first connect the phone to PC via adb and run:
Code:
parted /dev/block/mmcblk0
print
If even this is not working, it's likely to be a hardware fault. Otherwise this command will print partition list. Compare output with this one
Code:
Model: MMC SEM04G (sd/mmc)
Disk /dev/block/mmcblk0: 3959MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
10 524kB 1573kB 1049kB PIT
6 1573kB 3146kB 1573kB CSPSA FS
7 4194kB 14.7MB 10.5MB ext4 EFS
2 14.7MB 31.5MB 16.8MB ext4 Modem FS
14 32.5MB 34.6MB 2097kB SBL
16 34.6MB 36.7MB 2097kB SBL_2
1 36.7MB 53.5MB 16.8MB PARAM
12 53.5MB 55.6MB 2097kB IPL Modem
13 55.6MB 72.4MB 16.8MB Modem
15 72.4MB 89.1MB 16.8MB Kernel
17 89.1MB 106MB 16.8MB ext4 Kernel2
3 106MB 726MB 620MB ext4 SYSTEM
5 726MB 1972MB 1246MB ext4 DATAFS
4 1972MB 1982MB 10.0MB ext4 CACHEFS
9 1982MB 2602MB 620MB ext4 HIDDEN
8 2602MB 2702MB 100MB fat32 UMS
11 2702MB 3949MB 1247MB
to find out what partitions to restore. Note that CWM reparted doesn't touch any of "vital" partitions, and will recreate only System, data, cache and UMS. If some other partitions are missing, you have to create them via parted utility.
P.s. Be sure to read that topic in link above before flashing anything.
Click to expand...
Click to collapse
I will try as soon as I can your method but please can you upload a CWM back up too.
I want to be sure that it is not working.
matlowpap said:
I will try as soon as I can your method but please can you upload a CWM back up too.
I want to be sure that it is not working.
Click to expand...
Click to collapse
I don't have neither enough internet traffic to upload nand backup nor high enough upload speed. Of course you can ask someone else to upload CWM backup, but it would be senseless, as restoring nand backup won't create those deleted partitions.