After i've installed ezgingerbread on my G1 (radio 2.22.28.25 SPL 1.33.0013d), I have problem restoring my nandroid backup of Gingerfroyo (Restore the rom, but lost all settings).
If i install Gingerfroyo rom again , I can't download apk larger than 2 MB from market.
How can I solve this problem?
Thanks and excuse me for my english.
ezGingerbread doesn't touch the partitions, it takes the standard layout of the 1.33.0013(d) SPL. I am not sure if GingerFroyo touches the partition map, I've never installed it.
If your market downloads are not working, probably removing the folder ".android_secure" from your /sdcard will help you.
If i delete .android_secure, it recreate again. The market have the same problem.
I can't download .Apk larger than 2 MB from market.
Gingerfroyo don't touch the partitions.
00040000 00020000 misc
00500000 00020000 recovery
00280000 00020000 boot
05b00000 00020000 system
01b00000 00020000 cache
05bc0000 00020000 userdata
If that didn't work, do you have an ext partition? Is your cache bind mounted to /sd-ext? Can you post the output of the
df -h
command? I suspect your cache is not bind mounted.
Sent from my Gingerbread on Dream using XDA App
Filesystem Size Used Available Use% Mounted on
tmpfs 55.0M 0 55.0M 0% /dev
tmpfs 55.0M 0 55.0M 0% /mnt/asec
/dev/block/mtdblock3 91.0M 70.5M 20.5M 78% /system
/dev/block/mtdblock5 91.8M 37.8M 54.0M 41% /data
/dev/block/loop0 2.5M 2.5M 0 100% /system/xbin
/dev/block/mtdblock4 27.0M 13.7M 13.3M 51% /cache
/dev/block/vold/179:2
457.4M 34.2M 398.8M 8% /sd-ext
/dev/block/vold/179:2
457.4M 34.2M 398.8M 8% /data/data
/dev/block/vold/179:1
3.1G 416.0M 2.7G 13% /mnt/sdcard
/dev/block/vold/179:1
3.1G 416.0M 2.7G 13% /mnt/secure/asec
Code:
Filesystem Size Used Available Use% Mounted on
tmpfs 55.0M 0 55.0M 0% /dev
tmpfs 55.0M 0 55.0M 0% /mnt/asec
/dev/block/mtdblock3 91.0M 70.5M 20.5M 78% /system
/dev/block/mtdblock5 91.8M 37.8M 54.0M 41% /data
/dev/block/loop0 2.5M 2.5M 0 100% /system/xbin
/dev/block/mtdblock4 27.0M 13.7M 13.3M 51% /cache
/dev/block/vold/179:2 457.4M 34.2M 398.8M 8% /sd-ext
/dev/block/vold/179:2 457.4M 34.2M 398.8M 8% /data/data
/dev/block/vold/179:1 3.1G 416.0M 2.7G 13% /mnt/sdcard
/dev/block/vold/179:1 3.1G 416.0M 2.7G 13% /mnt/secure/asec
Thanks for help
I have re-flashed the rom and the problkem seems to be solved. Thanks for help.
P.S: add rotary lockscreen to ADS_magpie?
gorneman said:
Thanks for help.
Click to expand...
Click to collapse
Prego.
gorneman said:
P.S: add rotary lockscreen to ADS_magpie?
Click to expand...
Click to collapse
Sorry, I tried it already some time ago, but there are too many dependencies to other parts of the CM sources. At the moment I don't think that I will invest the time to port it to ADS_Magpie, but we will see.
Ok.. so I was having issues with not being able to install apps after I did a factory reset on my phone and reinstalled v20q rebuild and a custom kernel.
Some things from the market automatically downloaded, but others failed saying "Not enough disk space".
So I attached my phone to the PC, and deleted some unimportant files (Like soutcraft demo I never used, I removed the spiderman/gameloft stuff.. and other stuff that I knew was not important. I DID NOT remove system files.
So in the end.. I had about a gig spare space on my internal SD card. BUT after rebooting it still says "not enough disk space".
So I tried to boot into CWM... but it no longer boots in. I can't install Astro as not enough disk space. how the heck can I find out what's going on?
Which partition is it referring to not enough space? (And why won't CWM work?)
If i goto settings > applications > Manage Applications > Storage > It tells me I am only using 302MB of 1.2GB .. so defo plenty. It must be a different partition?
The /system partition is probably full, not the entire internal SD-card. I ran across the same problem when I installed adaway and tried to install the hosts file. So I deleted a couple of .apk's from /system/app. Why the system partition is so small I don't know.
Might that explain why CWM isn't starting as well?
Just a quick thought: on my old phone, when this error occurred, I had to wipe cache partition. It wouldn't hurt to try - as you cannot access CWM, maybe there's a way to do this using ADB.
wiredback said:
Just a quick thought: on my old phone, when this error occurred, I had to wipe cache partition. It wouldn't hurt to try - as you cannot access CWM, maybe there's a way to do this using ADB.
Click to expand...
Click to collapse
I've tried a factory reset. It wouldn't do the reset.
I've tried formatting the internal SD Card. It did that, but made no difference.
As you say, I am unable to get into CWM, so I would need some help with ADB if I'm to sort this :-(
I had that once too.
Did you change to EXT4 ?
Hmm.. not that I remember. I remember it saying that it was 'converting to ext3' when I put flashed "V20Q rebuild" on again, but I thought it was ext3 anyway. I'm not sure anything I have put on has ext4...
Only other thing I put on was the V20Q tweak pack, followed by spica's HP RC12 kernel (was trying it out).
Only thing I can do at present is seemingly to get in Android, and hook it up to the PC. It's useable, but without apps I'm a bit screwed, and even more screwed without access to CWM.
Can I reflash CWM perhaps?
(Side Note: I have flashed V20Q rebuild, gueste kernel, flik123's tweak pack and spica's HP kernel before without issue... I think this might be relating to the internal partition space. How the hell do I get access to it).
It's a bit of a pain that you can't get in CWM else you could try the backtoext3 tool by Paul, and reflash
I did that and it worked.
But with my problem, CWM still worked... Strange.
try reflashing CWM, and then go in CWM and format your /system and do a full wipe.
And reflash the ROM.
Try the BackToExt3 tool too (if Reflashing CWM worked):
http://android.modaco.com/topic/336...3-for-converting-your-device-er-back-to-ext3/
IT WILL WIPE YOUR DATA
BTW : Only use the backtoext3.zip mod of course if you use a EXT3 ROM
If that all dind't work try to hard reset to factory settings with NVFlash:
http://android.modaco.com/topic/335...k-rom-release-v10b-dated-1300166062-15032011/
Flashing at your own risk of course.
Hope this helps you somewhat i'm just suggesting some things for you to try.
I would firstly try to flash CWM again using ROM Manager or (if this is not possible) manually (I think there is a thread in Development section how to do this).
Secondly, I would flash original ROM using Smartflash.
I'm unable to run that from work, so I'll give it a shot when I get home.
Restalling CWM did nothing. Still a blank screen after the 2nd LG logo (Where the CWM logo and options would normally be).
Hmm.. how can I get access to the system partition, and then how do I delete stuff? (I'm a newb at linux stuff)
In fact, interal and external CWM bat files seems to copy but doesn't work on reboot :-( ARGGHH.
Hmm.. seems I can do a 'pull' and managed to pull everything out of /system/ LOL!!!
Someone help me here.. I assume I need to delete something in /system/ (or another directory???) to make room on the partition?
As info I have been looking around and used the 'df' command to get this:
# df system
df system
Filesystem Size Used Free Blksize
system 338M 327M 11M 1024
# df root
df root
Filesystem Size Used Free Blksize
root 0K 0K 0K 4096
# df
df
Filesystem Size Used Free Blksize
/dev 185M 64K 185M 4096
/mnt/asec 185M 0K 185M 4096
/mnt/obb 185M 0K 185M 4096
/system 338M 327M 11M 1024 <---- is this the issue here 11M free ?
/data 1G 136M 1G 4096
/mnt/extasec 185M 0K 185M 4096
/lgdrm 2M 2M 398K 2048
/mnt/sdcard 5G 2M 5G 4096
/mnt/secure/asec 5G 2M 5G 4096
/mnt/sdcard/_ExternalSD 7G 2G 4G 32768
/mnt/extsecure/extasec 7G 2G 4G 32768
"Pulled" some files off as backups, and deleted a few apk's to try and make space on system, but CWM will still not boot.
I have tried deleting the dalvik-cache, and no difference. I've tried reinstalling CWM.. but no difference :-(
What is going on :-(
EDIT: Even after removing these APK's which must have given me at least 20mb extra.. I STILL cannot download anything else from the market. Something is wrong here. please help XDA
Have you tried the Smartflash or NVflash method
To hard reset your phone we recommended ?
Not yet. Spent all night trying to make space on the system area, but it still told me no space, and CWM wouldn't boot.
Which do you recommened I try first? Actually I will follow Rusty's post here and see what happens (with NVFlash) . http://forum.xda-developers.com/showthread.php?t=1229407&highlight=smart+flash
I am not worried about the data in the slightest, only recovering the phone.
@Scougar: the df output looks a bit strange for me. I was expecting to see something like this:
# df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 215564 32 215532 0% /dev
tmpfs 215564 0 215564 0% /mnt/asec
tmpfs 215564 0 215564 0% /mnt/obb
tmpfs 215564 0 215564 0% /mnt/asec
tmpfs 215564 0 215564 0% /mnt/extasec
/dev/block/mmcblk0p1 347067 198348 130799 60% /system
/dev/block/mmcblk0p8 1548144 271128 1198376 18% /data
/dev/block/mmcblk0p2 63461 4154 56031 7% /cache
/dev/block/mmcblk0p6 2472 2074 398 84% /lgdrm
(some other less relevant entries deleted to make the output more readable).
Please note that I can see actual devices (partitions) how much they are filled and where they are mounted. In your output I'm missing things like e.g. cache partition.
The above output I got on adb but the same thing appeared in terminal emulator on my phone (currently WIUI).
You can also use "mount" command to see what is mounted where.
mipr said:
@Scougar: the df output looks a bit strange for me. I was expecting to see something like this:
# df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 215564 32 215532 0% /dev
tmpfs 215564 0 215564 0% /mnt/asec
tmpfs 215564 0 215564 0% /mnt/obb
tmpfs 215564 0 215564 0% /mnt/asec
tmpfs 215564 0 215564 0% /mnt/extasec
/dev/block/mmcblk0p1 347067 198348 130799 60% /system
/dev/block/mmcblk0p8 1548144 271128 1198376 18% /data
/dev/block/mmcblk0p2 63461 4154 56031 7% /cache
/dev/block/mmcblk0p6 2472 2074 398 84% /lgdrm
(some other less relevant entries deleted to make the output more readable).
Please note that I can see actual devices (partitions) how much they are filled and where they are mounted. In your output I'm missing things like e.g. cache partition.
The above output I got on adb but the same thing appeared in terminal emulator on my phone (currently WIUI).
You can also use "mount" command to see what is mounted where.
Click to expand...
Click to collapse
OK, I'll redo the df tonight when I get in (I can't do it from work), and see what I get. Maybe you have a different version of ADB to me ? (I am using the version as supplied by Rusty in his CWM script thread - linked to from the Q&A).
I'm trying to go through the sequence of events that lead up to this:
1) Booted into CWM (I did all the below WITHOUT rebooting until I had finished installing ZIPS - fatal flaw?)
2) Wiped dalvik cache
3) wiped data/Factory reset
4) Installed the Rebuilt V20Q ROM
5) Installed the V20Q Tweak pack (From Flix123)
6) Installed Spica's latest HP kernel (RC12 a few days ago).
I then rebooted.
None of the above I believe would have changed to ext4, only ext3 (Although I really don't understand ext versions at present). Perhaps by me doing too much at once, and not rebooting after I installed the V20Q ROM is what did it?
I'm using the latest adb downloaded from google. But this should not matter because with adb you are running commands from your phone, not from your computer, i.e. after "adb shell" you are effectively on your phone and the "df" is one of the commands on your phone. You may try "df -a" which should list all your file systems. You may also try "df --help" to see all command options. Additionally the "mount" command (without any params) should list all your mounted devices/partitions along with their filesystems, e.g. on my phone I get following:
/dev/block/mmcblk0p1 on /system type ext4 (rw,noatime,barrier=1,data=ordered)
/dev/block/mmcblk0p8 on /data type ext4 (rw,nosuid,nodev,noatime,barrier=1,data=ordered)
/dev/block/mmcblk0p2 on /cache type ext4 (rw,nosuid,nodev,noatime,barrier=1,data=ordered)
/dev/block/mmcblk0p6 on /lgdrm type ext3 (rw,nosuid,nodev,noatime,data=writeback)
As you can see my "system" partition is ext4, as well as "data" and "cache" partitions.
mipr said:
I'm using the latest adb downloaded from google. But this should not matter because with adb you are running commands from your phone, not from your computer, i.e. after "adb shell" you are effectively on your phone and the "df" is one of the commands on your phone. You may try "df -a" which should list all your file systems. You may also try "df --help" to see all command options. Additionally the "mount" command (without any params) should list all your mounted devices/partitions along with their filesystems, e.g. on my phone I get following:
/dev/block/mmcblk0p1 on /system type ext4 (rw,noatime,barrier=1,data=ordered)
/dev/block/mmcblk0p8 on /data type ext4 (rw,nosuid,nodev,noatime,barrier=1,data=ordered)
/dev/block/mmcblk0p2 on /cache type ext4 (rw,nosuid,nodev,noatime,barrier=1,data=ordered)
/dev/block/mmcblk0p6 on /lgdrm type ext3 (rw,nosuid,nodev,noatime,data=writeback)
As you can see my "system" partition is ext4, as well as "data" and "cache" partitions.
Click to expand...
Click to collapse
Cool, thanks. I'll give those a go tonight
Here is the result of the mount command:- (I do not know how to interprete the output, advice here gladly received)
# mount
mount
rootfs / rootfs ro,noatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /mnt/asec tmpfs rw,noatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,noatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p1 /system ext3 ro,nodev,noatime,errors=continue,data=ordered
0 0
/dev/block/mmcblk0p8 /data ext3 rw,nosuid,nodev,noatime,errors=continue,data=ord
ered 0 0
tmpfs /mnt/extasec tmpfs rw,nodev,noatime,mode=755,gid=1000 0 0
/dev/block/mmcblk0p6 /lgdrm ext3 rw,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/vold/179:9 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,ui
d=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=
iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:9 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noati
me,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocha
rset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/vold/179:17 /mnt/sdcard/_ExternalSD vfat rw,dirsync,nosuid,nodev,noex
ec,noatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp4
37,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:17 /mnt/extsecure/extasec vfat rw,dirsync,nosuid,nodev,noexe
c,noatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp43
7,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/_ExternalSD/.android_secure tmpfs ro,relatime,size=0k,mode=000
0 0
#