Database Develop

Low on space...

I just installed CyanogenMod 6.1.1 with Darktremor Apps2SD and wildmonks .35.10 kernel.
When it 1st booted it said that i'm low on space. If I look at internal storage I only have 4mb left When I apply the "a2sd cachesd" it reboots and after that I have 51mb left internal storage.
Any solution on this one?
PS: Yes, I did full wipe
EDIT:
Just did full wipe again and installed MIUI stock ROM and same issue, 19mb internal storage left...
EDIT2:
Reïnstalled CyanogenMod (app2sd) with all my apps,.. 45mb internal storage left It's not a disaster, but before I had 180mb internal memory, so there must be something wrong...

I have found something similar here, but no solution
http://forum.xda-developers.com/archive/index.php/t-787288.html

ZeppeMan said:
I have found something similar here, but no solution
http://forum.xda-developers.com/archive/index.php/t-787288.html
Click to expand...
Click to collapse
Hi,
Have you try to flash your the bootloader ? (then wipe data/cache and install new rom)

My bootloader is unlocked. Radio/SPL flashed to latest. Wiped many times, did a factory reset. Didn't help...
It looks like it doesn't wipe everything... But what can be the problem then?

ZeppeMan said:
My bootloader is unlocked. Radio/SPL flashed to latest. Wiped many times, did a factory reset. Didn't help...
It looks like it doesn't wipe everything... But what can be the problem then?
Click to expand...
Click to collapse
Have you tried with a new/different SD ?

Can you post the output of a2sd check to verify that DT is set up and functioning correctly?

a2sd is working because my apps are all on my ext3 partition, checked it in Titanium Backup. If it was not working then I hadn't enough internal memory (only 4mb) to install all my apps
Tried another SD card too, same result, it's something with /data I think not wiping correctly or something.

ZeppeMan said:
a2sd is working because my apps are all on my ext3 partition, checked it in Titanium Backup. If it was not working then I hadn't enough internal memory (only 4mb) to install all my apps
Tried another SD card too, same result, it's something with /data I think not wiping correctly or something.
Click to expand...
Click to collapse
Have you try to manually delete all files in /data ?

fautpasycraindre said:
Have you try to manually delete all files in /data ?
Click to expand...
Click to collapse
Also tried wiping through adb, same result...

fautpasycraindre said:
Have you try to manually delete all files in /data ?
Click to expand...
Click to collapse
or even just looking at the contents of that directory with ls -al /data? Should indicate all the files there, along with the size of files and directories - will also verify that all of your symlinks are in place and functioning.

This is what I get in Terminal app after applying "ls -al /data" command.
$ export PATH=/data/local/bin:$PATH
$su
# ls -al /data
drwxrwx--x 1 system system 2048 Jan 26 13:24 .
drwxr-xr-x 14 root root 0 Jan 26 13:24 ..
-rw-rw-rw- 1 root root 2 Jan 26 13:02 .dalvikcache
-rw-rw-rw- 1 root root 83 Jan 26 13:02 a2sdmnt.tmp
lrwxrwxrwx 1 root root 11 Jan 26 13:24 app -> /sd-ext/app
lrwxrwxrwx 1 root root 19 Jan 26 13:24 app-private -> /sd-ext/app-private
drwx------ 1 system system 2048 Jan 26 12:58 backup
lrwxrwxrwx 1 root root 20 Jan 26 13:24 dalvik-cache -> /sd-ext/dalvik-cache
drwxrwx--x 1 system system 2048 Jan 26 13:20 data
drwxr-x--- 1 root log 2048 Jan 26 12:57 dontpanic
-rw-r--r-- 1 root root 6073 Jan 26 13:24 dta2sd.lg1
-rw-r--r-- 1 root root 2966 Jan 26 13:24 dta2sd.lg2
-rw-r--r-- 1 root root 6073 Jan 26 13:24 dta2sd.log
-rw-rw-rw- 1 root root 376 Jan 26 12:56 dtinstall.log
drwxr-xr-x 1 root root 2048 Jan 26 12:56 jit
drwxrwx--x 1 shell shell 2048 Jan 26 12:57 local
drwxrwx--- 1 root root 2048 Jan 26 12:57 lost+found
drwxrwx--t 1 system misc 2048 Jan 26 15:29 misc
drwx------ 1 root root 2048 Jan 26 13:24 property
drwxrwxr-x 1 system system 2048 Jan 26 15:29 system
#

ZeppeMan said:
This is what I get in Terminal app after applying "ls -al /data" command.
Code:
[I]$ export PATH=/data/local/bin:$PATH
$su
# ls -al /data
drwxrwx--x 1 system system 2048 Jan 26 13:24 .
drwxr-xr-x 14 root root 0 Jan 26 13:24 ..
-rw-rw-rw- 1 root root 2 Jan 26 13:02 .dalvikcache
-rw-rw-rw- 1 root root 83 Jan 26 13:02 a2sdmnt.tmp
lrwxrwxrwx 1 root root 11 Jan 26 13:24 app -> /sd-ext/app
lrwxrwxrwx 1 root root 19 Jan 26 13:24 app-private -> /sd-ext/app-private
drwx------ 1 system system 2048 Jan 26 12:58 backup
lrwxrwxrwx 1 root root 20 Jan 26 13:24 dalvik-cache -> /sd-ext/dalvik-cache
drwxrwx--x 1 system system 2048 Jan 26 13:20 data
drwxr-x--- 1 root log 2048 Jan 26 12:57 dontpanic
-rw-r--r-- 1 root root 6073 Jan 26 13:24 dta2sd.lg1
-rw-r--r-- 1 root root 2966 Jan 26 13:24 dta2sd.lg2
-rw-r--r-- 1 root root 6073 Jan 26 13:24 dta2sd.log
-rw-rw-rw- 1 root root 376 Jan 26 12:56 dtinstall.log
drwxr-xr-x 1 root root 2048 Jan 26 12:56 jit
drwxrwx--x 1 shell shell 2048 Jan 26 12:57 local
drwxrwx--- 1 root root 2048 Jan 26 12:57 lost+found
drwxrwx--t 1 system misc 2048 Jan 26 15:29 misc
drwx------ 1 root root 2048 Jan 26 13:24 property
drwxrwxr-x 1 system system 2048 Jan 26 15:29 system
#[/I]
Click to expand...
Click to collapse
Everything looks fine there, for the most part.
How many apps do you have installed? Keep in mind that each app will still have some amount of storage in /data/data - it can add up if you have 180+ apps installed.

For the moment I have like 25 apps installed. So, not that much..

I hate to keep hassling you for further information... but could you post the output of df -h please, to show the breakdown of storage usage on your file system?

Code:
$ export PATH=/data/local/bin:$PATH
$df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 203.3M 0 203.3M 0% /dev
tmpfs 203.3M 0 203.3M 0% /mnt/asec
/dev/block/mtdblock3 145.0M 107.2M 37.8M 74% /system
/dev/block/mtdblock5 196.3M 149.3M 46.9M 76% /data
/dev/block/mtdblock4 95.0M 2.9M 92.1M 3% /cache
/dev/block/mmcblk0p2 914.7M 105.2M 760.7M 12% /sd-ext
/dev/block/vold/179:1
6.4G 90.9M 6.4G 1% /mnt/sdcard
df: /mnt/secure/asec: Permission denied
/dev/block/dm-0 7.1M 5.9M 1.2M 83% /mnt/asec/net.hexage.radiant.lite-1
/dev/block/dm-1 2.0M 464.0K 1.6M 22% /mnt/asec/com.skitapps.bubblebuster-1
/dev/block/dm-2 16.2M 14.1M 2.1M 87% /mnt/asec/com.rovio.angrybirds-1
/dev/block/dm-3 7.1M 5.4M 1.7M 76% /mnt/asec/com.qualcomm.qx.neocore-1
$
Np, I want this to be fixed.. So ask all things you need

ZeppeMan said:
Code:
$ export PATH=/data/local/bin:$PATH
$df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 203.3M 0 203.3M 0% /dev
tmpfs 203.3M 0 203.3M 0% /mnt/asec
/dev/block/mtdblock3 145.0M 107.2M 37.8M 74% /system
[B]/dev/block/mtdblock5 196.3M 149.3M 46.9M 76% /data[/B]
/dev/block/mtdblock4 95.0M 2.9M 92.1M 3% /cache
/dev/block/mmcblk0p2 914.7M 105.2M 760.7M 12% /sd-ext
/dev/block/vold/179:1
$
Np, I want this to be fixed.. So ask all things you need
Click to expand...
Click to collapse
Your /data is really high ! It should not be that big! Could you check the size of folders "app", "data" and "backup" ? (or list 1st level folder size in /data if it's ok for you)

Can you give me the command or where I can find it? Sorry, don't know to much of these things..
EDIT:
In Astro app, when I go into /data it says it's empty..

ZeppeMan said:
Can you give me the command or where I can find it? Sorry, don't know to much of these things..
EDIT:
In Astro app, when I go into /data it says it's empty..
Click to expand...
Click to collapse
Command is :
Code:
du -m -d 1 /data
du = disk usage
-m = size in megabytes
-d 1 = depth=1
About Astro, it's the same for some file manager as you need explicit root access. That's why before exectue "du" command, you may have to type "su" to get root privilege.

This what I get..
Code:
$ export PATH=/data/local/bin:$PATH
$su
# du -m -d 1 /data
0牋牋牋 /data/property
0牋牋牋 /data/backup
0牋牋牋 /data/dontpanic
1牋牋牋 /data/jit
0牋牋牋 /data/misc
5牋牋牋 /data/data
0牋牋牋 /data/local
0牋牋牋 /data/system
0牋牋牋 /data/lost+found
7牋牋牋 /data
#
In Terminal app the chinese signs can't be seen, it's just empty space.
Like this..
Code:
$ export PATH=/data/local/bin:$PATH
$su
# du -m -d 1 /data
0 /data/property
0 /data/backup
0 /data/dontpanic
1 /data/jit
0 /data/misc
5 /data/data
0 /data/local
0 /data/system
0 /data/lost+found
7 /data
#

Ok so you have 14 MB used on your /data folders.
Now try with "-a" option (du -m -d 1 -a /data) to list all files in /data folder, as it might come from files in /data folder
-a = List all (not only folder)

[Q] Invalid Magic (TouchPadBuntu)

Hi,
I have upgraded my moboot to 3.0.5 and upgraded the Cyanogenmod to CM9. Also, i have decided to install TouchPadBuntu to test it. Followed the instructions with some modifications, and everything went fine, but when i try to boot on it via moboot, it gives the error:
Loading '/boot/uImage.TouchPadBuntu'... OK
Checking uImage... Invalid Magic
BOOT FAILED!
Also, ClockRecovery doesn't works too, it returns some numbers (hex codes) on the boot screen.
Someone can give some light?

I'm dealing with same problem, but with Arch Linux.
I think the problem is in /boot free space...
Can you list your files in /boot and your free space in there?
ls -l /boot
df -h /boot

Hi, i have attached the errors... one is TouchPadBuntu error, and the other is Cyanogenmod error that is appearing sometimes yes, sometimes no...
http://img19.imageshack.us/img19/5138/imagem0000m.jpg
http://img828.imageshack.us/img828/4153/imagem0001.jpg
Also, here is my /boot
Code:
[email protected]:/# ls -l /boot
-rw-r--r-- 1 root root 1430215 Jul 30 2011 System.map-2.6.35-palm-tenderloin
drwxr-xr-x 2 root root 4096 Oct 14 02:59 bin
-rw-r--r-- 1 root root 490764 Jul 30 2011 boot-genesis.tar.gz
-rw-r--r-- 1 root root 119371 Jul 30 2011 boot-images.tar.gz
-rw-r--r-- 1 root root 115392 Jul 30 2011 boot.bin
-rw-r--r-- 1 root root 75277 Jul 30 2011 config-2.6.35-palm-tenderloin
drwxr-xr-x 2 root root 4096 Oct 14 02:59 dev
drwxr-xr-x 3 root root 4096 Oct 14 02:59 etc
-rwxr-xr-x 1 root root 1131 Jul 30 2011 genesis-update.xml
-rwxr-xr-x 1 root root 2224 Jul 30 2011 image-update.xml
drwxr-xr-x 2 root root 4096 Oct 14 02:59 lib
drwx------ 2 root root 16384 Oct 14 02:56 lost+found
-rw-r--r-- 1 root root 11 Oct 14 03:51 moboot.default
-rw-r--r-- 1 luna luna 0 Feb 9 01:57 moboot.next
-rw-rw-rw- 1 root root 30313 Feb 8 00:58 moboot.splash.CyanogenMod.tga
-rw-r--r-- 1 luna 10000 14046 Sep 8 2001 moboot.splash.webOS.tga
-rw-r--r-- 1 root root 4 Feb 8 01:51 moboot.verbose.TouchPadBuntu
drwxr-xr-x 2 root root 4096 Oct 14 02:59 proc
drwxr-xr-x 2 root root 4096 Oct 14 02:59 realroot
drwxr-xr-x 2 root root 4096 Oct 14 02:59 sbin
drwxr-xr-x 2 root root 4096 Oct 14 02:59 sys
lrwxrwxrwx 1 root root 13 Feb 8 01:51 uImage -> uImage.moboot
-rw-r--r-- 1 root root 3333228 Jul 30 2011 uImage-2.6.35-palm-tenderloin
-rw-r--r-- 1 root root 5006686 Feb 8 00:57 uImage.ClockworkMod
-rw-r--r-- 1 root root 4136681 Feb 8 00:58 uImage.CyanogenMod
-rw-r--r-- 1 root root 1106 Feb 8 02:53 uImage.TouchPadBuntu
-rw-r--r-- 1 root root 64508 Feb 8 01:50 uImage.moboot
lrwxrwxrwx 1 root root 29 Oct 14 02:58 uImage.webOS -> uImage-2.6.35-palm-tenderloin
-rw-r--r-- 1 root root 84 Jul 30 2011 updatefs-info
drwxr-xr-x 5 root root 4096 Oct 14 02:59 usr
[email protected]:/# df -h /boot
Filesystem Size Used Available Use% Mounted on
/dev/root 31.0M 22.1M 8.9M 71% /boot

Hi folks,
I have corrected my problem downloading uImage.TouchPadUbuntu again via CURL direclty to /boot. To do this i have to use mount -O rw,remount /boot and execute the curl command here.
After this, i rebooted the touchpad and now have ubuntu on it. But using touchscreen as mouse is sucking a lot, and response of my touch on virtual keyboard too... but fine to test!

I also solved my problem, I think the problem was pretty like yours!
My solution post.

Reboot loop after upgrading from CM 10.0 stable to CM 10.1 nightly

Hi
I was running CM 10 stable and on friday I installed CM 10.1 nightly 20130111. I installed after factorty reset, cache and dalvik cache wipe. After rebooting I saw a message that android is upgrading along with "optimising" 96 apps. After finishing optimisation it went to home screen and instantly message "Unfortunatley, the process com.android.phone has stopped" popped up. when I hit ok, it popped up again and again and then phone rebooted.
Now it is stuck in reboot loop.
Please help.
Thanks

transact said:
Hi
I was running CM 10 stable and on friday I installed CM 10.1 nightly 20130111. I installed after factorty reset, cache and dalvik cache wipe. After rebooting I saw a message that android is upgrading along with "optimising" 96 apps. After finishing optimisation it went to home screen and instantly message "Unfortunatley, the process com.android.phone has stopped" popped up. when I hit ok, it popped up again and again and then phone rebooted.
Now it is stuck in reboot loop.
Please help.
Thanks
Click to expand...
Click to collapse
Have you tried wiping data again from recovery and then boot?

ishangoyal said:
Have you tried wiping data again from recovery and then boot?
Click to expand...
Click to collapse
Yeah, multiple times.
I tried to flash stock firmware back but I think system is read only now.
When I flashed stockfirmware from samfirmware also with odin and pit file, I was able to go to stock recovery but phone never booted to stock firmware. Then I flashed semaphore . this time I could see semaphore logo and then cyanogenmod animation. Seeing cyanogen animation was a surprise as it should have been wiped when i flashed stockfirmare.
I went to recovery mode again did factory reset, cache wipe, dalvik cache. Then mounted usb and copied latest nightly of 10.1 and gapps to customroms folder on my sdcard.
After copying I rebooted into recovery mode again and selected install from zip on sdcard but to my surprise the new files I copied were not there but the files I deleted were still there.
It seems like phone didn't allow me to alter content of sdcard. To test I mounted the usb storage again and created some dummy files like default.txt, default.ini and default.zip in root of sdcard and deleted some files from my backup files of fuellog folder. After unmounting and going through files on phone I discovered that new files are not there and old files are still present.
Another thing is that I have factory reset multiple times, wiped cache partition and cleared dalvik cache as well but every time I mount usb from recovery I have .android_secure folder filled with my previous apps from CM 10.0, which I think shouldn't be there after factory reset.
So I guess it is something to do with permissions. I have done 'fix permissions' multiple times but that also didn't helped.
One more thing I noticed is that after I flash CM10.1 from old file still in my sdcard, on first boot I get com.phone.android error but then on second boot I saw option to complete action using apex, nova or trebuchet laucnher behing the com.android.phone error. I think I shouldn't see that message as it is suppose to be new install with factory reset.
after I click ok on the error message, the phone reboots again but this time it stuck on cyanogen animation. it never goes past animation on 3rd boot.
I have really no idea what is happening.
Is there a way to reset everything through adb? or reset file permissions? I could access my device using adb but had no idea what I could do or not do.
File system view when phone is booting and stuck at cyanogen animation
Code:
drwxr-xr-x root root 2013-01-15 10:29 acct
-rw-r--r-- root root 614 2013-01-15 10:29 boot.txt
drwxrwx--x system cache 2013-01-15 10:29 cache
-rwxr-x--- root root 264080 2013-01-15 10:29 charger
dr-x------ root root 2013-01-15 10:29 config
lrwxrwxrwx root root 2013-01-15 10:29 d -> /sys/kernel/debug
drwxrwx--x system system 2013-01-11 17:08 data
drwxrwx--x system system 2013-01-15 10:29 datadata
-rw-r--r-- root root 163 2013-01-15 10:29 default.prop
drwxr-xr-x root root 2013-01-15 10:29 dev
drwxr-xr-x radio radio 2013-01-14 21:30 efs
lrwxrwxrwx root root 2013-01-15 10:29 emmc -> /storage/sdcard1
lrwxrwxrwx root root 2013-01-15 10:29 etc -> /system/etc
-rw-r----- root root 568 2013-01-15 10:29 fstab.aries
-rwxr-x--- root root 109484 2013-01-15 10:29 init
-rwxr-x--- root root 555 2013-01-15 10:29 init.aries.gps.rc
-rwxr-x--- root root 5375 2013-01-15 10:29 init.aries.rc
-rwxr-x--- root root 3899 2013-01-15 10:29 init.aries.usb.rc
-rwxr-x--- root root 1238 2013-01-15 10:29 init.cm.rc
-rwxr-x--- root root 2487 2013-01-15 10:29 init.goldfish.rc
-rwxr-x--- root root 18768 2013-01-15 10:29 init.rc
-rwxr-x--- root root 1795 2013-01-15 10:29 init.trace.rc
-rwxr-x--- root root 3915 2013-01-15 10:29 init.usb.rc
-rw-r--r-- root root 340 2013-01-15 10:29 lpm.rc
drwxr-xr-x root root 2013-01-14 22:02 lvm
drwxrwxr-x root system 2013-01-15 10:29 mnt
dr-xr-xr-x root root 1970-01-01 10:00 proc
drwxr-xr-x root root 2013-01-14 21:28 radio
drwxr-xr-x root root 2013-01-15 10:29 res
drwxr-x--- root root 2013-01-15 10:29 sbin
lrwxrwxrwx root root 2013-01-15 10:29 sdcard -> /storage/sdcard0
d---r-x--- root sdcard_r 2013-01-15 10:29 storage
drwxr-xr-x root root 2013-01-15 10:29 sys
drwxr-xr-x root root 2013-01-11 17:01 system
-rw-r--r-- root root 1489 2013-01-15 10:29 ueventd.aries.rc
-rw-r--r-- root root 272 2013-01-15 10:29 ueventd.goldfish.rc
-rw-r--r-- root root 5220 2013-01-15 10:29 ueventd.rc
lrwxrwxrwx root root 2013-01-15 10:29 vendor -> /system/vendor
file system view when in recovery
Code:
drwxr-xr-x 18 root root 0 Jan 15 00:12 .
drwxr-xr-x 18 root root 0 Jan 15 00:12 ..
drwxr-xr-x 3 root root 0 Jan 15 00:12 acct
-rw-r--r-- 1 root root 586 Jan 15 00:12 boot.txt
drwxrwx--x 1 system cache 4096 Jan 14 23:29 cache
-rwxr-x--- 1 root root 264080 Jan 15 00:12 charger
dr-x------ 2 root root 0 Jan 15 00:12 config
lrwxrwxrwx 1 root root 17 Jan 15 00:12 d -> /sys/kernel/debug
drwxrwx--x 12 system system 0 Jan 15 00:12 data
-rw-r--r-- 1 root root 2887 Jan 15 00:12 default.prop
drwxr-xr-x 13 root root 3040 Jan 15 00:12 dev
drwxr-xr-x 2 root root 0 Jan 15 00:12 efs
d--------- 2 system system 0 Jan 15 00:12 emmc
drwxr-xr-x 2 root root 0 Jan 15 00:12 etc
-rw-r----- 1 root root 568 Jan 15 00:12 fstab.aries
-rwxr-x--- 1 root root 109484 Jan 15 00:12 init
-rwxr-x--- 1 root root 10349 Jan 15 00:12 init.rc
-rw-r--r-- 1 root root 340 Jan 15 00:12 lpm.rc
drwxr-xr-x 4 root root 0 Jan 14 11:02 lvm
dr-xr-xr-x 73 root root 0 Jan 1 1970 proc
drwxr-xr-x 3 root root 0 Jan 15 00:12 res
drwxr-x--- 2 root root 0 Jan 15 00:12 sbin
d--------- 2 system system 0 Jan 15 00:12 sdcard
drwxr-xr-x 12 root root 0 Jan 15 00:12 sys
drwxr-xr-x 3 root root 0 Jan 15 00:12 system
drwxr-xr-x 2 root root 0 Jan 15 00:12 tmp
-rw-r--r-- 1 root root 1489 Jan 15 00:12 ueventd.aries.rc
-rw-r--r-- 1 root root 272 Jan 15 00:12 ueventd.goldfish.rc
-rw-r--r-- 1 root root 5220 Jan 15 00:12 ueventd.rc
-rw-r--r-- 1 root root 3899 Jan 15 00:12 usb.rc
lrwxrwxrwx 1 root root 14 Jan 15 00:12 vendor -> /system/vendor
I hope they give some kind of clue.
please help.
thanks

transact said:
Yeah, multiple times.
I hope they give some kind of clue.
please help.
thanks
Click to expand...
Click to collapse
That's a really weird and detailed explanation .. however I am unable to explain the behaviour of your phone.. what I can suggest is formating the sd card too (if you have backup of data that is) and format /system too manually along with wiping data, cache and dalvik cache.. after that flash CM10.1 nightly twice.. don't flash gapps atm.. after that reboot recovery.. wipe data, cache again (not /system this time) and flash nightly again.. fix permissions and then reboot..
I know repetition like this doesn't make much sense but nor does your problem..
Hope this will help.

if you are comeing from cm10.0 ant flashing cm10.1 it is recommend to wipe /system befor flashing

No logcat output

I'm porting Ubuntu Touch on an y991 (Elephone Vowney Lite).
I managed to boot the system and run its apps. Now I need to debug RIL, wireles, camera etc., but I cannot get any logcat output.
I tried both /system/bin/logcat both /android/system/bin/logcat from an adb root shell. It just returns to prompt. No error, no log. Logs exist:
Code:
ls -l /dev/log*
srw-rw-rw- 1 root root 0 Jan 1 01:00 /dev/log
crw-rw-rw- 1 root root 10, 59 Jan 1 01:00 /dev/log_events
crw-rw-rw- 1 root root 10, 60 Jan 1 01:00 /dev/log_main
crw-rw-rw- 1 root root 10, 58 Jan 1 01:00 /dev/log_radio
crw-rw-rw- 1 root root 10, 57 Jan 1 01:00 /dev/log_system

I was about to suggest that you ask the ubport's guys ..... but mayyybe you know them already https://forums.ubports.com/user/4javier

Watch shutting down before finish boot

Hello guys,
first of all, sorry for my bad english
now i have some strange problems too, and i need your help.
A year ago i flashed a moddet rom, but a bug has caused that the watch reboots when booting in the cradle.
finally my watch restart over and over for a whole night.
Afterwards she started to turn off randomly. Now i replaced the battery with a new one and flashed the newest stock rom and TWRP.
While in TWRP the watch keeps on and charge correctly until 100%.
When i try to boot normaly it boots up, says "Android is starting - X of 45 Apps" when all 45 Apps are done it says "Finish boot".
after that it says "Is shuting down" and switch off immediately .
After starting again, it shows the colorful loadingscreen and switch off again.
This is reproducible:
5 times shut down during colorful loadingscreen
"Updating Android" - shut down
and so on.
This is constantly repeated
I tried different stock roms, but have the same issue everytime.
Is that a Kernel or another softwareproblem? because in TWRP the Watch stay on the whole time. But right before starting the Android Mainscreen it shuts off.
Edit: one thing i recognize today:
The watch dont turn on automatically when i place it on the cradle
greetings
Stephan

Try to completely wipe the system and then flash new one from TWRP.
I mean wipe the system partition from ADB

i wiped the partition with
adb shell
rm -rf /system/*
and flashed the Rom via TWRP.
But same issue

I do not know if it is a error:
i tried to sidoload superSU in TWRP and get the error:
Failed to mount /system (no such device)
In TWRP im unable to Mount system. Its not selectable
i cant find the SYSTEM partition:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell cat /proc/mounts
rootfs / rootfs rw,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
tmpfs /tmp tmpfs rw,seclabel,relatime 0 0
pstore /sys/fs/pstore pstore rw,relatime 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
/dev/block/mmcblk0p21 /data ext4 rw,seclabel,relatime,data=ordered 0 0
/dev/block/mmcblk0p21 /sdcard ext4 rw,seclabel,relatime,data=ordered 0 0
/dev/block/mmcblk0p20 /cache ext4 rw,seclabel,relatime,data=ordered 0 0
only in the mappings i can find system
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell ls -al /dev/block/platform/msm_sdcc.1/by-name
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
drwxr-xr-x 2 root root 480 Jan 1 00:00 .
drwxr-xr-x 4 root root 560 Jan 1 00:00 ..
lrwxrwxrwx 1 root root 21 Jan 1 00:00 DDR -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 20 Jan 1 00:00 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 Jan 1 00:00 abootb -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 Jan 1 00:00 boot -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 Jan 1 00:00 cache -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 Jan 1 00:00 grow -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 Jan 1 00:00 imgdata -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 Jan 1 00:00 laf -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 Jan 1 00:00 metadata -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 Jan 1 00:00 misc -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 Jan 1 00:00 persist -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 Jan 1 00:00 recovery -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 20 Jan 1 00:00 rpm -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 Jan 1 00:00 rpmb -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 Jan 1 00:00 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 Jan 1 00:00 sbl1b -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 Jan 1 00:00 sdi -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 Jan 1 00:00 ssd -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 Jan 1 00:00 system -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 20 Jan 1 00:00 tz -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 Jan 1 00:00 tzb -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 Jan 1 00:00 userdata -> /dev/block/mmcblk0p21

Which TWRP are you using?

robimarko said:
Which TWRP are you using?
Click to expand...
Click to collapse
twrp-3.1.0-0-lenok

Thats the issue,officiall TWRP was not working on 3.0.2 so it is probably not working on 3.1.
I use an unofficall image,if I am not mistaken this should be it
http://www.mediafire.com/download/rhfr5ps2c8ssxx5/twrp-3.0.0-0-lenok+squashfs.img
And it works

this works thanks! Mounting works
Now i will try to sideload the rom (M1D65H) again, hopefully my watch will boot
btw: M1D65H etc is the versionnr? Or does it have to fit my watch?

ARRRGH!
Still the same problem:crying:

Maybe stupid question but have you tried to wipe cache and format everything except recovery from TWRP?

robimarko said:
Maybe stupid question but have you tried to wipe cache and format everything except recovery from TWRP?
Click to expand...
Click to collapse
i make a factory reset (wipes Data, cache and dalvik) via TWRP.
if i try to wipe System with TWRP it says: Unable to wipe /system -- unknown file system "auto"
Is there another way to format everything? With adb there is no command like wipe or format

Yes,through TWRP.
In Wipe,through advanced

robimarko said:
Yes,through TWRP.
In Wipe,through advanced
Click to expand...
Click to collapse
Its unable to wipe /system

Now i have flashed the old 5.1.1 and have the same problem. Maybe a hardware problem?

Hm,I doubt it since it does not reebot in TWRP.

And not during the Android update or Upgrade process. Only when it tries to load the homescreen i think. Is there a kind of safemode like in windows?

No ideas anymore?

Blueforcer I am having the exact same issues. Since my watch is on the new read only system OS I have not been able to get my watch to boot. I am able to use fastboot and adb but once it loads it just stays on the startup screen for a few minutes and then shuts down.
Does anyone know if there is a way to wipe the entire contents and reload from a working watch? I have tried multiple boot/recovery, but believe the issue stems from inside the systems folders.
Thoughts?

hello all.
It appears I am suffering from the same or similar issues. My watch wont boot fully. It boots, and then on completion it immediately says "switching off".
I have reset it. And tried to wipe system. And im now at the same point where the system folder wont wipe properly. It errors saying "unknown filesystem 'auto'".
This to me looks like a software bug. In either twrp or the rom itself. The issue started for me when the battery ran too low. My rom was fully stock. Nothing changed.
Where can we report this to LG? My watch is well out of warranty so I am holding no hope for a fix. Seems my watch got bricked by this update to me.
EDIT: UPDATE!! Its fixed!! For now!
I used this recovery and used advanced wipe to wipe the system folder. Which resulted in no error about the filesystem. And I then sideloaded the twrp flashable factory zip.
I hope you guys can fix too!

Well it seems I'm still in the same boat. Although it's not happening immediately after bootup, my watch is still randomly shutting itself down.
Got enough time while it's booted to get a logcat, but can't see what is doing it.