Database Develop

[Q] Can't install protected (app-private) apps

Hi
First things first:
PDA: I9000XWJM6
PHONE: I9000XXJM3
CSC: I9000OXAJM1
Rooted, CFLagFix applied if that matters.
I flashed it recently to the mentioned ROM. After flash, I've got strange problem when I'm trying to install any protected apps (ones which go to app-private folder, I'm guessing they're all protected?). When I'm trying to install them, they report success in installing, but there is default icon used in applications' menu, and instead of name I can see only the beginning part of application's package. When I'm trying to launch, launcher force closes
Anyway, I tried to debug this problem. So here is what I've got, the example app is QR Contacts. First, relevant part of logcat file is attached.
As far as I can understand, it all starts with PackageManager unable to move some files to app-private, and all following warning and errors happens because file hadn't been moved, so it's not where it supposed to be
But, then again: I adb shell'ed, and as root (and as system user) I CAN copy some files to this destination. Furthermore, here are my persmissions for this folder:
Code:
# ls -l
drwxrwx--x system root 2010-09-16 16:44 gps
drwxrwx--t system misc 2010-09-15 12:08 misc
drwxrwx--x wifi wifi 2010-09-13 00:34 wifi
drwxrwx--x shell shell 2010-09-12 23:14 local
drwxrwx--x system system 2010-09-16 16:49 data
drwxrwx--x system system 2010-09-16 16:23 app-private
drwxrwx--x system system 2010-09-16 16:49 app
drwx------ root root 2010-09-15 22:56 property
drwxrwxrwx root root 2010-09-13 02:31 log
drwxrwxrwx root root 2010-09-15 22:54 dump
drwxrwx--x system system 2010-09-16 16:49 dalvik-cache
drwxrwx--- root root 2010-09-12 21:57 lost+found
drwxrwxrwx system system 2010-09-16 14:03 anr
drwxrwxr-x system system 2010-09-16 17:14 system
drwx------ system system 2010-09-12 21:58 backup
drwxrwxrwx system system 2010-09-16 16:45 cflf
drwxr-xr-x system system 2010-09-15 23:16 tombstones
As You can see, the same permissions are used for app folder - and normal apps can be installed without problems. So, what about free space then?
Code:
# busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 162.7M 0 162.7M 0% /dev
df: /mnt/.lfs: Function not implemented
tmpfs 4.0M 0 4.0M 0% /sqlite_stmt_journals
/dev/block/stl9 275.8M 269.1M 6.7M 98% /system
/dev/block/mmcblk0p2 1.9G 1.6G 250.5M 87% /data
/dev/block/stl10 127.2M 95.4M 31.8M 75% /dbdata
/dev/block/stl11 30.1M 2.2M 27.9M 7% /cache
/dev/block/stl3 5.9M 4.0M 1.9M 68% /efs
/dev/loop0 1.6G 447.9M 1.2G 27% /data/cflf/mount
/dev/loop0 1.6G 447.9M 1.2G 27% /data/app-private
/dev/loop0 1.6G 447.9M 1.2G 27% /data/app
/dev/loop0 1.6G 447.9M 1.2G 27% /data/dalvik-cache
/dev/loop0 1.6G 447.9M 1.2G 27% /data/data
/dev/loop0 1.6G 447.9M 1.2G 27% /data/system
/dev/loop1 93.9M 12.7M 81.2M 14% /dbdata/cflf/mount
/dev/loop1 93.9M 12.7M 81.2M 14% /dbdata/databases
/dev/block//vold/179:1
13.4G 1.7G 11.7G 13% /sdcard
/dev/block//vold/179:9
14.9G 13.8G 1.1G 93% /sdcard/sd
Clearly, I do have enough space, or so it appears.
So, right now I'm clueless. Googled for couple hours, searched this forum and found nothing. Does anyone have idea what's causing this problem?

Same problem here, any solutions?

if you can download the .apk file you can install it from your SD card
even if you can not download them from Android Market because you are listed in an area of no valid

[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.

Boot loop, problems with recovery

Hello,
I recently unlocked my bootloader and went to install a custom rom with Clockwork Recovery. It got stuck on the HTC boot screen (using an M7), and it would not move. I hard booted the device, and it corrupted my data.
Now, when going into CWM, the device reboots. I have tried reflashing CWM to no avail, so I then tried flashing TWRP. TWRP cannot mount any partition other than system. Problematically, I cannot get adb to recognize my device when in recovery (on multiple computers) but can get fastboot to detect it.
I cannot get a new image onto my phone via usb to fix it, and I cannot use the following guide (edit, cannot post links yet) to fix my corrupted data as a result. Also, I cannot get the device to show up as mountable storage in windows (I have yet to try Linux) to transfer files to it.
What are my options here?

Update:
I was able to update my "unknown" driver to the HTC diver in windows, and now can see my phone with adb devices.
So, I tried the data corruption fix by loading mkfs.ext4 to it and running :
/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^extra_isize -m 0 /dev/block/mmcblk0p37
this completed, but now I still cant mount /data/ for some reason.
this is what I get:
ls -l
drwxr-xr-x 2 root root 0 May 10 20:12 cache
drwxr-xr-x 2 root root 0 Jan 1 1970 data
-rw-r--r-- 1 root root 6586 Jan 1 1970 default.prop
drwxr-xr-x 12 root root 3440 May 10 20:12 dev
drwxr-xr-x 2 root root 0 May 10 20:12 etc
-rwxr-x--- 1 root root 105268 Jan 1 1970 init
-rwxr-x--- 1 root root 1670 Jan 1 1970 init.rc
drwxr-xr-x 3 root root 0 Jan 1 1970 license
dr-xr-xr-x 157 root root 0 Jan 1 1970 proc
drwxr-xr-x 5 root root 0 Jan 1 1970 res
drwx------ 2 root root 0 Aug 15 2013 root
drwxr-x--- 2 root root 0 Jan 1 1970 sbin
drwxr-xr-x 2 root root 0 May 10 20:12 sdcard
drwxr-xr-x 2 root root 0 Jan 1 1970 supersu
dr-xr-xr-x 24 root root 0 May 10 20:12 sys
drwxr-xr-x 3 root root 0 Jan 1 1970 system
drwxrwxr-x 2 root shell 0 May 10 20:17 tmp
-rw-r--r-- 1 root root 272 Jan 1 1970 ueventd.goldfish.rc
-rw-r--r-- 1 root root 5075 Jan 1 1970 ueventd.rc
drwxrwxrwx 2 root root 0 May 10 20:12 usb-otg
~ # ←[6nmount data
mount data
mount: mounting /data on ext4 failed: No such file or directory
~ # ←[6nmount /data
mount /data
mount: mounting /data on ext4 failed: No such file or directory
~ # ←[6nexit
exit
Now what?

Hey Wulf,
Sorry I'm still at work but this happened to me once as well. You wiped the OS completely from the phone and somehow corrupted the recovery.
I resolved it by relocking the bootloader and flashing a stock RUU. After it booted stock I unlocked the bootloader again reflashed the custom rom.

wulfsburg said:
What are my options here?
Click to expand...
Click to collapse
my bad, useless contribution / preaching.

nkk71 said:
re-EDIT: you start by reading (a little or a lot)... by reading you will learn... by learning you will acquire knowledge... and by knowledge you will be hopefully to get a lot farther than where you are now.
Click to expand...
Click to collapse
By posting useless crap like this you become a douche bag, when you become a douche bag people disregard your opinion, when people disregard your opinion you become useless to a forum community, when you become useless to a forum community you get eaten by a bear. Don't get eaten by a bear, stop posting useless crap

nicowagner said:
By posting useless crap like this you become a douche bag, when you become a douche bag people disregard your opinion, when people disregard your opinion you become useless to a forum community, when you become useless to a forum community you get eaten by a bear. Don't get eaten by a bear, stop posting useless crap
Click to expand...
Click to collapse
Have removed my post.
Thanks for pointing it out.

How I fixed my bricked Nexus 5 (corrupted userdata, bootlooping)

Hi everyone,
First of all - apologies if this is in the wrong forum. First time I post something, so not too sure if this is the right place.
I've been struggling with my Nexus 5 for the past 3 days after I attempted a factory reset. After trying everything I could find, I managed to combine some strategies from different threads, and got some help from a friend who is a linux specialist. As it has been REALLY HARD for me to fix this, I thought I would post the solution in case anyone is seeing the same issue.
Summary of my issue:
I attempted a factory reset to cleanup the phone. That was really all I intended to do.
The factory reset got stuck on "erasing". After 30 minutes waiting, I forced the phone to reboot. Then everything went downhill.
My Nexus 5 started bootlooping. It wouldn't even get in recovery mode.
I've flashed ClockWorkMod Recovery, and tried to format everything and start again. The processes to wipe partitions would fail.
Flashing stock also failed, as things would hang on "erasing cache".
I found references on multiple threads about things to try - from flashing other ROMs, to formatting the file system manually, and basically trying every step of a flashing a stock installation manually.
The bottom line is everything would hang because the system could not mount the /data partition.
When I tried to use "e2fsck" to check /userdata partition, it would give me an error about the file system being corrupted, and suggesting to use a different superblock.
Some threads here in XDA suggested to use CWM and TWRP to format the partition, as that would usually fix the problem. It didn't work in my case.
The system would basically hang when trying to format /data, with any method I tried.
When using the "dmesg" command, I would also see lots of errors with superblocks when trying to mount "/data".
I considered it could be a hardware issue, but I was not seeing problems with the other partitions (/cache, /system, /recovery, and so on).
Solution:
I fixed the problem by removing the partition, recreating it with "ext2" file system, then upgrading to "ext4" manually, and finally flashing the system images again WITHOUT flashing userdata.
Every time I flash "userdata", the partition just gets corrupted.
This is the step by step on how I did it:
1) Start the phone on bootloader by holding power button + volume down. Flash CWM recovery through fastboot.
Download CWM recovery from here: https://clockworkmod.com/rommanager
I'm using windows, so I opened a command prompt on the "Android SDK\platform-tools" folder.
run: "fastboot flash recovery <CWM_Recovery_Folder>\recovery-clockwork-6.0.4.5-hammerhead.img"
2) Reboot in recovery mode, so that it would load ADB. In the command prompt I ran "adb shell" so I could use the linux tools
Use "parted /dev/block/mmcblk0" to open the parted tool for the mmc block.
Use command "print" to list all partitions. You should see something like this:
Number Start End Size File system Name Flags
1 524kB 67.6MB 67.1MB fat16 modem
2 67.6MB 68.7MB 1049kB sbl1
3 68.7MB 69.2MB 524kB rpm
4 69.2MB 69.7MB 524kB tz
5 69.7MB 70.3MB 524kB sdi
6 70.3MB 70.8MB 524kB aboot
7 70.8MB 72.9MB 2097kB pad
8 72.9MB 73.9MB 1049kB sbl1b
9 73.9MB 74.4MB 524kB tzb
10 74.4MB 75.0MB 524kB rpmb
11 75.0MB 75.5MB 524kB abootb
12 75.5MB 78.6MB 3146kB modemst1
13 78.6MB 81.8MB 3146kB modemst2
14 81.8MB 82.3MB 524kB metadata
15 82.3MB 99.1MB 16.8MB misc
16 99.1MB 116MB 16.8MB ext4 persist
17 116MB 119MB 3146kB imgdata
18 119MB 142MB 23.1MB laf
19 142MB 165MB 23.1MB boot
20 165MB 188MB 23.1MB recovery
21 188MB 191MB 3146kB fsg
22 191MB 192MB 524kB fsc
23 192MB 192MB 524kB ssd
24 192MB 193MB 524kB DDR
25 193MB 1267MB 1074MB ext4 system
26 1267MB 1298MB 31.5MB crypto
27 1298MB 2032MB 734MB ext4 cache
28 2032MB 31.3GB 29.2GB ext4 userdata
29 31.3GB 31.3GB 5632B grow
Click to expand...
Click to collapse
3) Remove the existing data partition by running command "rm 28" .
4) Recreate the partition and the file system with "mkpartfs". I didn't use all parameters at once, but just informed the proper values as requested by the tool:
(parted) mkpartfs
mkpartfs
mkpartfs
Partition name? []? userdate
userdate
userdate
File system type? [ext2]? ext2
ext2
ext2
Start? 2032MB
2032MB
2032MB
End? 31.3GB
31.3GB
31.3GB
Click to expand...
Click to collapse
5) The partition should now be recreated as "ext2" file system. I've set the partition name with:
(parted) name 28 userdata
name 28 userdata
name 28 userdata
Click to expand...
Click to collapse
If you print again, you should see the new partition as ext2 file system:
(...)
28 2032MB 31.3GB 29.2GB ext2 userdata
(...)
Click to expand...
Click to collapse
6) Upgrade the FS from ext2 to ext4 by using make_ext4fs:
make_ext4fs -l 29236371456 -b 4096 -g 32768 -i 8192 -I 256 -j 32768 -L msdos -a /data /dev/block/mmcblk0p28
Now here is the interesting part. When I tried to run "flash-all" from the google stock image, this is what I would see when it ran the format script on the userdata partition:
OKAY [ 13.186s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 29236371456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7137786
Block groups: 218
Reserved block group size: 1024
Created filesystem with 11/1785856 inodes and 156120/7137786 blocks
sending 'userdata' (139109 KB)...
writing 'userdata'...
OKAY [ 16.625s]
finished. total time: 29.811s
Click to expand...
Click to collapse
When I manually ran the make_ext4fs, the only difference was I added a label "msdos" and this was the result:
Creating filesystem with parameters:
Size: 29236371456
Block size: 4096
Blocks per group: 32768
Inodes per group: 48
Inode size: 256
Journal blocks: 32768
Label: msdos
Blocks: 7137786
Block groups: 218
Reserved block group size: 1024
Click to expand...
Click to collapse
Almost the same thing, but with a difference in "Inodes per group": stock script shows 8192, and running manually it shows 48.
I have no idea why is that. Honestly I know very little about linux and its file systems, so I don't know what that means.
After I did this, I was FINALLY able to mount the "/data" partition.
8) Checked the file system with e2fsck. It now worked fine:
~ # e2fsck /dev/block/mmcblk0p28
e2fsck /dev/block/mmcblk0p28
e2fsck 1.41.14 (22-Dec-2010)
msdos: clean, 11/10464 files, 45158/7137786 blocks
~ #
9) Manually flash google stock system, cache, boot, and bootloader.
I was using this image: hammerhead-ktu84p-factory-35ea0277.tgz
I uncompressed this to a folder, and also uncompressed the image-hammerhead-ktu84p.zip.
So I ran:
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash boot boot.img
After this, I rebooted the system and it loaded, after loooooong 3 days reading through everything I could on XDA!
These were some of the threads that helped me in one way or another to get to this solution:
http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
http://forum.xda-developers.com/google-nexus-5/help/help-nexus-5-bricked-clearing-cache-t2564509
http://forum.xda-developers.com/google-nexus-5/help/stuck-erasing-doing-factory-reset-t2530342
http://forum.xda-developers.com/google-nexus-5/orig-development/nexus-5-f2fs-t2668486
http://forum.xda-developers.com/goo...o-repairing-corrupted-data-partition-t2577447
http://forum.xda-developers.com/showthread.php?t=1441928
http://forum.xda-developers.com/google-nexus-5/help/help-nexus-5-bricked-clearing-cache-t2564509
http://forum.xda-developers.com/google-nexus-5/help/help-stuck-bootloop-t2515338
http://forum.xda-developers.com/google-nexus-5/help/stuck-google-logo-recovery-mode-t2898337
I really hope no one else had the same "luck" as I did, since this problem has been a nightmare.
But in case you unfortunately do... hope this helps!

Great guide. Might become handy for other users. It should be stickied

Why would you force reboot while factory resetting in the first place lol
Sent from my Nexus 5

Good guide but a bricked phone is rendered useless, hence the name 'bricked.' If your phone can still power on, it is not bricked. You said your self you got it out of a bootloop. That's essentially all you had, a bootloop, and you were able to figure out what was wrong with it.
Just a heads up so we don't throw that term around loosely since a lot of people do so.
You can't bring a phone back from a brick. I think JTAG is an option but its for Samsung phones only. (Feel free to correct me if I'm wrong.)

dicecuber said:
Why would you force reboot while factory resetting in the first place lol
Sent from my Nexus 5
Click to expand...
Click to collapse
Yeap, I know it sounds stupid but the factory reset was hanging, lol.
I tried multiple times and it would hang every time. I left it running for more than 3h once and nothing happened.

jayRokk said:
Good guide but a bricked phone is rendered useless, hence the name 'bricked.' If your phone can still power on, it is not bricked. You said your self you got it out of a bootloop. That's essentially all you had, a bootloop, and you were able to figure out what was wrong with it.
Just a heads up so we don't throw that term around loosely since a lot of people do so.
You can't bring a phone back from a brick. I think JTAG is an option but its for Samsung phones only. (Feel free to correct me if I'm wrong.)
Click to expand...
Click to collapse
Thanks for clarifying! I thought bricked also meant "the phone is about to go useless, but there is a tiny hope", lol.
Is there a way to correct the thread name?
You're right - it was only bootlooping.

There's soft-brick and hard-brick.
Wysłane z mojego Nexus 5

rm 28
3) Remove the existing data partition by running command "rm 28": im getting a error on this step .
need help..

How did the phone become bricked? What was the phone doing before trying to unbrick?

audit13 said:
How did the phone become bricked? What was the phone doing before trying to unbrick?
Click to expand...
Click to collapse
dont know how it got bricked..in morning when i wake up its suddenly start showing the boot only for hours. I've tried flashig it.evertime got flash write failure for bootloader and other images except boot.img .i've checked for emmc its fine and showing the device partion.
I'm using nexus 5 16gb device.pls anyone help

I assume the bootloader is unlocked since you are able to flash the boot.img. Try this: re-lock the bootloader, reboot to fastboot and see if the bootloader remains locked. If the bootloader unlocks itself, this is an indication that the memory chip is damaged. Also try flashing the older stock ROM available.

audit13 said:
I assume the bootloader is unlocked since you are able to flash the boot.img. Try this: re-lock the bootloader, reboot to fastboot and see if the bootloader remains locked. If the bootloader unlocks itself, this is an indication that the memory chip is damaged. Also try flashing the older stock ROM available.
Click to expand...
Click to collapse
havn't tried to lock the bootloader but tried all these after reading too many posts but dont't what the issue is?...pls have a look into this..
_____________________________________________
C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data>adb shell
~ # list users
/sbin/sh: list: not found
~ # df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 949780 128 949652 0% /dev
tmpfs 949780 0 949780 0% /storage
tmpfs 949780 0 949780 0% /mnt/secure
tmpfs 949780 0 949780 0% /mnt/fuse
~ # cat /proc/partitions
major minor #blocks name
179 0 15388672 mmcblk0
179 1 65536 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 512 mmcblk0p3
179 4 512 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 2048 mmcblk0p7
179 8 1024 mmcblk0p8
179 9 512 mmcblk0p9
179 10 512 mmcblk0p10
179 11 512 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 3072 mmcblk0p13
179 14 512 mmcblk0p14
179 15 16384 mmcblk0p15
179 16 16384 mmcblk0p16
179 17 3072 mmcblk0p17
179 18 22528 mmcblk0p18
179 19 22528 mmcblk0p19
179 20 22528 mmcblk0p20
179 21 3072 mmcblk0p21
179 22 512 mmcblk0p22
179 23 512 mmcblk0p23
179 24 512 mmcblk0p24
179 25 1048576 mmcblk0p25
179 26 30720 mmcblk0p26
179 27 716800 mmcblk0p27
179 28 13404138 mmcblk0p28
179 29 5 mmcblk0p29
179 32 4096 mmcblk0rpmb
~ # mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /storage type tmpfs (rw,seclabel,relatime,mode=050,gid=1028)
tmpfs on /mnt/secure type tmpfs (rw,seclabel,relatime,mode=700)
tmpfs on /mnt/fuse type tmpfs (rw,seclabel,relatime,mode=775,gid=1000)
~ # mount -o,rw /system
~ # mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /storage type tmpfs (rw,seclabel,relatime,mode=050,gid=1028)
tmpfs on /mnt/secure type tmpfs (rw,seclabel,relatime,mode=700)
tmpfs on /mnt/fuse type tmpfs (rw,seclabel,relatime,mode=775,gid=1000)
/dev/block/platform/msm_sdcc.1/by-name/system on /system type ext4 (rw,seclabel,
relatime,data=ordered)
~ # moutn -o,rw /cah←[J
/sbin/sh: moutn: not found
~ # mount -o,rw /cache
mount: mounting /dev/block/platform/msm_sdcc.1/by-name/cache on /cache failed: I
nvalid argument
~ # mount -o,rw /data
mount: mounting /dev/block/platform/msm_sdcc.1/by-name/userdata on /data failed:
Invalid argument
~ # mount -o,rw /sdcard
mount: can't find /sdcard in /etc/fstab
~ # ls -l
drwxr-xr-x 2 root root 0 Jan 1 09:39 boot
drwxr-xr-x 2 root root 0 Jan 1 09:39 cache
-rwxr-x--- 1 root root 288392 Jan 1 00:00 charger
drwxr-xr-x 3 root root 0 Jan 1 09:39 data
drwxr-xr-x 2 root root 0 Jan 1 09:39 datadata
-rw-r--r-- 1 root root 3976 Jan 1 00:00 default.prop
drwxr-xr-x 10 root root 4480 Jan 1 09:39 dev
drwxr-xr-x 2 root root 0 Jan 1 09:39 emmc
drwxr-xr-x 2 root root 0 Jan 1 09:39 etc
drwxr-xr-x 2 root root 0 Jan 1 09:39 external_sd
-rw-r--r-- 1 root root 9375 Jan 1 00:00 file_contexts
-rw-r----- 1 root root 953 Jan 1 00:00 fstab.goldfish
-rw-r----- 1 root root 2653 Jan 1 00:00 fstab.hammerhead
-rwxr-x--- 1 root root 179556 Jan 1 00:00 init
-rwxr-x--- 1 root root 2708 Jan 1 00:00 init.rc
drwxr-xr-x 2 root root 0 Jan 1 09:39 internal_sd
drwxrwxr-x 5 root system 0 Jan 1 09:39 mnt
dr-xr-xr-x 127 root root 0 Jan 1 00:00 proc
-rw-r--r-- 1 root root 2161 Jan 1 00:00 property_contexts
drwxr-xr-x 2 root root 0 Jan 1 09:39 recovery
drwxr-xr-x 3 root root 0 Jan 1 00:00 res
drwx------ 2 root root 0 Dec 1 2013 root
drwxr-x--- 2 root root 0 Jan 1 00:00 sbin
drwxr-xr-x 2 root root 0 Jan 1 09:39 sd-ext
lrwxrwxrwx 1 root root 11 Jan 1 09:39 sdcard -> /data/media
-rw-r--r-- 1 root root 711 Jan 1 00:00 seapp_contexts
-rw-r--r-- 1 root root 74942 Jan 1 00:00 sepolicy
d---r-x--- 2 root sdcard_r 40 Jan 1 09:39 storage
dr-xr-xr-x 12 root root 0 Jan 1 09:39 sys
drwxr-xr-x 14 root root 4096 Jan 1 00:00 system
drwxrwxr-x 2 root shell 0 Jan 1 09:39 tmp
-rw-r--r-- 1 root root 272 Jan 1 00:00 ueventd.goldfish.rc
-rw-r--r-- 1 root root 2204 Jan 1 00:00 ueventd.hammerhead.rc
-rw-r--r-- 1 root root 5897 Jan 1 00:00 ueventd.rc
~ # cat recovery.fstab
cat: can't open 'recovery.fstab': No such file or directory
~ # cat recovery.fstab.bak
cat: can't open 'recovery.fstab.bak': No such file or directory
~ # system /bin
/sbin/sh: system: not found
~ # system/bin
/sbin/sh: system/bin: Permission denied
~ # e2fsck
Usage: e2fsck [-panyrcdfvtDFV] [-b superblock] [-B blocksize]
[-I inode_buffer_blocks] [-P process_inode_size]
[-l|-L bad_blocks_file] [-C fd] [-j external_journal]
[-E extended-options] device
Emergency help:
-p Automatic repair (no questions)
-n Make no changes to the filesystem
-y Assume "yes" to all questions
-c Check for bad blocks and add them to the badblock list
-f Force checking even if filesystem is marked clean
-v Be verbose
-b superblock Use alternative superblock
-B blocksize Force blocksize when looking for superblock
-j external_journal Set location of the external journal
-l bad_blocks_file Add to badblocks list
-L bad_blocks_file Set badblocks list
~ # -p
/sbin/sh: -p: not found
~ # p
/sbin/sh: p: not found
~ # e2fsck -p
Usage: e2fsck [-panyrcdfvtDFV] [-b superblock] [-B blocksize]
[-I inode_buffer_blocks] [-P process_inode_size]
[-l|-L bad_blocks_file] [-C fd] [-j external_journal]
[-E extended-options] device
Emergency help:
-p Automatic repair (no questions)
-n Make no changes to the filesystem
-y Assume "yes" to all questions
-c Check for bad blocks and add them to the badblock list
-f Force checking even if filesystem is marked clean
-v Be verbose
-b superblock Use alternative superblock
-B blocksize Force blocksize when looking for superblock
-j external_journal Set location of the external journal
-l bad_blocks_file Add to badblocks list
-L bad_blocks_file Set badblocks list
~ # c
/sbin/sh: c: not found
~ # e2fsckc
/sbin/sh: e2fsckc: not found
~ # e2fsck c
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: No such file or directory while trying to open c
Possibly non-existent device?
~ # e2fsck -c
Usage: e2fsck [-panyrcdfvtDFV] [-b superblock] [-B blocksize]
[-I inode_buffer_blocks] [-P process_inode_size]
[-l|-L bad_blocks_file] [-C fd] [-j external_journal]
[-E extended-options] device
Emergency help:
-p Automatic repair (no questions)
-n Make no changes to the filesystem
-y Assume "yes" to all questions
-c Check for bad blocks and add them to the badblock list
-f Force checking even if filesystem is marked clean
-v Be verbose
-b superblock Use alternative superblock
-B blocksize Force blocksize when looking for superblock
-j external_journal Set location of the external journal
-l bad_blocks_file Add to badblocks list
-L bad_blocks_file Set badblocks list
~ # e2fsck -y /dev/block/platform/msm_sdcc.1/by-name/persist
e2fsck 1.41.14 (22-Dec-2010)
/dev/block/platform/msm_sdcc.1/by-name/persist: recovering journal
Superblock needs_recovery flag is clear, but journal has data.
Run journal anyway? yes
e2fsck: unable to set superblock flags on /dev/block/platform/msm_sdcc.1/by-name
/persist
~ # cat /proc/partitions
major minor #blocks name
179 0 15388672 mmcblk0
179 1 65536 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 512 mmcblk0p3
179 4 512 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 2048 mmcblk0p7
179 8 1024 mmcblk0p8
179 9 512 mmcblk0p9
179 10 512 mmcblk0p10
179 11 512 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 3072 mmcblk0p13
179 14 512 mmcblk0p14
179 15 16384 mmcblk0p15
179 16 16384 mmcblk0p16
179 17 3072 mmcblk0p17
179 18 22528 mmcblk0p18
179 19 22528 mmcblk0p19
179 20 22528 mmcblk0p20
179 21 3072 mmcblk0p21
179 22 512 mmcblk0p22
179 23 512 mmcblk0p23
179 24 512 mmcblk0p24
179 25 1048576 mmcblk0p25
179 26 30720 mmcblk0p26
179 27 716800 mmcblk0p27
179 28 13404138 mmcblk0p28
179 29 5 mmcblk0p29
179 32 4096 mmcblk0rpmb
~ # df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 949780 128 949652 0% /dev
tmpfs 949780 0 949780 0% /storage
tmpfs 949780 0 949780 0% /mnt/secure
tmpfs 949780 0 949780 0% /mnt/fuse
/dev/block/platform/msm_sdcc.1/by-name/system
1033516 1020920 12596 99% /system
~ #
C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data>fastboot dev
ices
034dd8de828dd06c fastboot
C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data>fastboot for
mat system
Creating filesystem with parameters:
Size: 1073741824
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 4096
Label:
Blocks: 262144
Block groups: 8
Reserved block group size: 63
Created filesystem with 11/65536 inodes and 8536/262144 blocks
target reported max download size of 1073741824 bytes
erasing 'system'...
OKAY [ 0.187s]
sending 'system' (18800 KB)...
OKAY [ 0.813s]
writing 'system'...
FAILED (remote: flash write failure)
finished. total time: 1.188s
C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data>fastboot for
mat cache
Creating filesystem with parameters:
Size: 734003200
Block size: 4096
Blocks per group: 32768
Inodes per group: 7472
Inode size: 256
Journal blocks: 2800
Label:
Blocks: 179200
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/44832 inodes and 5813/179200 blocks
target reported max download size of 1073741824 bytes
erasing 'cache'...
FAILED (remote: failed to erase partition)
finished. total time: 0.219s
C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data>fastboot for
mat bootloader
Formatting is not supported for file system with type ''.
_______________________________________________________

Try the suggestion about relocking there bootloader and checking to see if it stays locked. If it doesn't stay locked, I would replace the motherboard.

When trying to delete partition 28, I get:
Error: Input/output error during write on /dev/block/mmcblk0
Anybody else got this and found a way to solve it?

audit13 said:
I assume the bootloader is unlocked since you are able to flash the boot.img. Try this: re-lock the bootloader, reboot to fastboot and see if the bootloader remains locked. If the bootloader unlocks itself, this is an indication that the memory chip is damaged. Also try flashing the older stock ROM available.
Click to expand...
Click to collapse
Thanks, I've been reading for quite some time looking for a solution to fix my Nexus 5 (I bought it brick just to fix it), and it does exactly what you mention here in your post. It recognize fastboot, it lock the bootloader but when the phone reboot, it display bootloader unlock. It doesn't let me flash the recovery img. by computer.
Thanks

The motherboard's flash memory is defective which means you'll need to replace the motherboard to have functional phone.

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.