Database Users

[Info] List of Samsung Galaxy S2 GT-I9100 devices and partitions

To run this commands you need a rooted device with BusyBox and parted. Using stock partition layout. You can change the partition layout to get more or less than 2GB of size for the data partition:
[MOD][GUIDE]Partition your internal memory for better App management (Pit Files)
List of devices by name:
[email protected]:/sdcard # ls -l /dev/block/platform/dw_mmc/by-name/
lrwxrwxrwx 1 root root 20 May 12 21:24 CACHE -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 May 12 21:24 DATAFS -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 20 May 12 21:24 EFS -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 May 12 21:24 FACTORYFS -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 May 12 21:24 HIDDEN -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 May 12 21:24 KERNEL -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 May 12 21:24 MODEM -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 May 12 21:24 PARAM -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 May 12 21:24 RECOVERY -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 May 12 21:24 SBL1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 May 12 21:24 SBL2 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 May 12 21:24 UMS -> /dev/block/mmcblk0p11
Click to expand...
Click to collapse
List of fdisk for all given partitions:
Command (needs Superuser or equivalent and Busybox):
su
find /dev/block/platform/dw_mmc/ -name 'mmc*' -exec fdisk -l {} \; > /sdcard/list_of_sgs2_partitions.txt
Click to expand...
Click to collapse
Code:
Disk ./mmcblk0boot0: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0boot0 doesn't contain a valid partition table
Disk ./mmcblk0boot1: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0boot1 doesn't contain a valid partition table
Disk ./mmcblk0p12: 536 MB, 536870912 bytes
4 heads, 16 sectors/track, 16384 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p12 doesn't contain a valid partition table
Disk ./mmcblk0p11: 12.3 GB, 12356419584 bytes
4 heads, 16 sectors/track, 377088 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
./mmcblk0p11p4 1 1 0 0 Empty
Partition 4 does not end on cylinder boundary
Disk ./mmcblk0p10: 2147 MB, 2147483648 bytes
4 heads, 16 sectors/track, 65536 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p10 doesn't contain a valid partition table
Disk ./mmcblk0p9: 536 MB, 536870912 bytes
4 heads, 16 sectors/track, 16384 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p9 doesn't contain a valid partition table
Disk ./mmcblk0p8: 16 MB, 16777216 bytes
4 heads, 16 sectors/track, 512 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p8 doesn't contain a valid partition table
Disk ./mmcblk0p7: 104 MB, 104857600 bytes
4 heads, 16 sectors/track, 3200 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p7 doesn't contain a valid partition table
Disk ./mmcblk0p6: 8 MB, 8388608 bytes
4 heads, 16 sectors/track, 256 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p6 doesn't contain a valid partition table
Disk ./mmcblk0p5: 8 MB, 8388608 bytes
4 heads, 16 sectors/track, 256 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p5 doesn't contain a valid partition table
Disk ./mmcblk0p4: 8 MB, 8388608 bytes
4 heads, 16 sectors/track, 256 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p4 doesn't contain a valid partition table
Disk ./mmcblk0p3: 1 MB, 1310720 bytes
4 heads, 16 sectors/track, 40 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p3 doesn't contain a valid partition table
Disk ./mmcblk0p2: 1 MB, 1310720 bytes
4 heads, 16 sectors/track, 40 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p2 doesn't contain a valid partition table
Disk ./mmcblk0p1: 20 MB, 20971520 bytes
4 heads, 16 sectors/track, 640 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p1 doesn't contain a valid partition table
Disk ./mmcblk0: 15.7 GB, 15758000128 bytes
1 heads, 16 sectors/track, 1923584 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
./mmcblk0p1 1 1923456 15387647+ ee EFI GPT
Partition 1 does not end on cylinder boundary
Mounted filesystems:
Code:
[email protected]:/ # df
df
Filesystem Size Used Free Blksize
/dev 415M 32K 415M 4096
/mnt/asec 415M 0K 415M 4096
/mnt/obb 415M 0K 415M 4096
/system 503M 429M 74M 4096
/cache 98M 4M 94M 4096
/efs 19M 8M 11M 4096
/data 1G 666M 1G 4096
/mnt/.lfs: Function not implemented
/mnt/sdcard 11G 2G 9G 32768
/mnt/sdcard/external_sd 29G 24G 5G 32768
/mnt/sdcard/external_sd 29G 24G 5G 32768
temporal fstab:
Code:
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mmcblk0p9 on /system type ext4 (ro,noatime,barrier=1,data=ordered)
/dev/block/mmcblk0p7 on /cache type ext4 (rw,nosuid,nodev,noatime,barrier=1,data=ordered)
/dev/block/mmcblk0p1 on /efs type ext4 (rw,nosuid,nodev,noatime,barrier=1,data=ordered)
/dev/block/mmcblk0p10 on /data type ext4 (rw,nosuid,nodev,noatime,barrier=1,data=ordered,noauto_da_alloc)
/dev/block/mmcblk0p4 on /mnt/.lfs type j4fs (rw,relatime)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,relatime)
/dev/block/vold/259:3 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/external_sd type tmpfs (rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,size=0k,mode=755,gid=1000)
tmpfs on /mnt/sdcard/usbStorage type tmpfs (rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,size=0k,mode=755,gid=1000)
/dev/block/vold/179:25 on /mnt/sdcard/external_sd type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:25 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/external_sd/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
/dev/block/dm-0 on /mnt/asec/org.ais.archidroid-1 type vfat (ro,dirsync,nosuid,nodev,noatime,nodiratime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
AdamOutler said:
Hey guys. I'm doing some work to figure out how to recover Galaxy Nexus devices which are hard-bricked.. ie.. they have a bad or no bootloader installed.
the boot sequence
1. IROM - the Internal ROM which cannot be rewritten on the device. This loads the XLoader.
2. XLoader/MLO - This completes the initialization of the processor and memory, and loads up the relatively huge U-Boot ( Samsung modified this and calls it SBL)
3. UBoot/SBL - This "Bootloader" is almost a complete operating system. The U-Boot initializes the screen, provides Odin mode, Fastboot Mode as well as loading the kernel/recovery and provides a UART debugging mode (Yet to be unlocked).
4. Kernel - Once we reach this point, it's all clear.. the kernel is linux which loads android and all sorts of other things.
The Problem
People are bricking their devices at stage 2 and 3 of this boot sequence... This leaves them unable to boot Fastboot or Odin. The device is 100% interchangable with a brick. These devices are ending up hard bricked.
The solution
We must come up with a way to undo the hard brick. Here are some things i'm looking at to use the native hardware to recover itself.
When you plug in the device (when off), you will immediately notice a Texas Instruments D010 device gets enumerated. This is a debug mode for the processor.
Code:
Bus 001 Device 023: ID 0451:d010 Texas Instruments, Inc.
We've started looking at some bootloader output here: http://forum.xda-developers.com/showthread.php?t=1461986
You can find information about the OMAP4 bootloaders here: http://omapedia.org/wiki/Bootloader_Project
Help
I need help locating drivers to initialize the 0451:d010 device and make it readable from within Linux or Windows.. Generally Linux is easier to find appropriate drivers.
I could use some help collecting more reading materials and resources.
I think together as a community we can take care of this problem.
Click to expand...
Click to collapse
AdamOutler said:
There's more to the boot then the OP mentioned... there's 6 partitions involved, not 4.
irom = hard coded
IBL/PBL = initial bootloader and primitive bootloader
SBL = Secondadary Bootloader finds linux
param = contains paramaters to run the phone and required for boot.
SBL2 = download mode (included in SBL)
PIT = Partiton Information Table
Don't touch any of these files.
If you touch the param.ifs, the phone can still boot, however you will see a black screen if something goes wrong.
Code:
BOOT 00000000 0000 0003FFFF 0001
PIT 00040000 0001 0003FFFF 0001
EFS 00080000 0002 009FFFFF 0028
SBL 00A80000 002A 0013FFFF 0005
SBL2 00BC0000 002F 0013FFFF 0005
PARAM 00D00000 0034 004FFFFF 0014
KERNEL 01200000 0048 0077FFFF 001E
RECOVERY 01980000 0066 0077FFFF 001E
FACTORYFS 02100000 0084 11E7FFFF 047A
DBDATAFS 13F80000 04FE 085FFFFF 0218
CACHE 1C580000 0716 022FFFFF 008C
MODEM 1E880000 07A2 00C7FFFF 0032
07D4 1F500000
Click to expand...
Click to collapse
Aditional links:
* Definitive guide to Bricking *
[Guide] Types of Android backups
[REF] GT-I9100 PIT v Flash Analysis
[GUIDE] ROOT/UNROOT Stock ICS Firmware without flashing unsecure kernel
[GUIDE] Making Dump Files Out of Android Device Partitions

/sdcard
This is nice, thank.
But where is from block device the sdcard. How working the "vold"?
How can I partition sdcard with fdisk or with parted?

gyurman said:
This is nice, thank.
But where is from block device the sdcard. How working the "vold"?
How can I partition sdcard with fdisk or with parted?
Click to expand...
Click to collapse
Partition the sdcard from clockworkmod recovery

Thanks, but I want use parted, or fdisk. But what mmcblk0? use sdcard? mmcblk0p11?

Someone please. Need nvflashable ROM

Please if someone have, upload your backedup mmcblk0_start with partition configuration data from mmcblk0p8, my tablet has only 7 partitions although My flash.cfg makes 8 partitions and last one is mmcblk0p8 with size FFFF... But after flashing it I get always same thing- when i boot into ubuntu and check my partitions I get only last one mmcblk0p7 who is data, so I can't flash second boot image and make dualboot+recovery. On picasso.init.rc i get just some words and digits, so I can not do anything with it, I tryed all EUU's, but get the same. So please if you can, upload it, if it wery hard then jus system.img it will be better than nothing. Thanks and sorry for bad English.

There is no such partition. It is only defined this way in nvflash flash.cfg but whole space is taken by the user data parition, which takes as much space as it can get (depending on emmc size) and this last one is not actually created.

yaworski said:
There is no such partition. It is only defined this way in nvflash flash.cfg but whole space is taken by the user data parition, which takes as much space as it can get (depending on emmc size) and this last one is not actually created.
Click to expand...
Click to collapse
So what I need to do that I can flash second boot image, and why mmcblk0p7 in nvflash .cfg is about just 7 or more megabytes? And http://projects.pappkartong.se/a500/ do you read it, in that table is write 8 partitions and mmcblk0p8 is data, then it is strange. Thanks for reply. Sorry for bad english.

Tautvaldas said:
Please if someone have, upload your backedup mmcblk0_start with partition configuration data from mmcblk0p8, my tablet has only 7 partitions although My flash.cfg makes 8 partitions and last one is mmcblk0p8 with size FFFF... But after flashing it I get always same thing- when i boot into ubuntu and check my partitions I get only last one mmcblk0p7 who is data, so I can't flash second boot image and make dualboot+recovery. On picasso.init.rc i get just some words and digits, so I can not do anything with it, I tryed all EUU's, but get the same. So please if you can, upload it, if it wery hard then jus system.img it will be better than nothing. Thanks and sorry for bad English.
Click to expand...
Click to collapse
If you don't have a mmcblk0p8 I would be interested to see what /proc/partitions and /proc/mounts looks like.
With mmcblk0p8:
Code:
$ cat /proc/partitions
major minor #blocks name
179 0 31259648 mmcblk0
179 1 5120 mmcblk0p1
179 2 8192 mmcblk0p2
179 3 614400 mmcblk0p3
179 4 1253376 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 102400 mmcblk0p6
179 7 10240 mmcblk0p7
179 8 29253632 mmcblk0p8
$
$ cat /proc/mounts
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,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
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p3 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p8 /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p4 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p6 /system/vendor ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
$
The partition table parsed from raw dump of /dev/block/mmcblk:
Code:
nvtegrapart: #0 [BCT ] start=0 size=6144 (6)
nvtegrapart: #1 [PT ] start=2048 size=1024 (1)
nvtegrapart: #2 [EBT ] start=3072 size=8192 (8)
nvtegrapart: #3 [GP1 ] start=11264 size=2048 (2)
nvtegrapart: #4 [SOS ] start=13312 size=10240 (10)
nvtegrapart: #5 [LNX ] start=23552 size=16384 (16)
nvtegrapart: #6 [APP ] start=39936 size=1228800 (1200)
nvtegrapart: #7 [CAC ] start=1268736 size=2506752 (2448)
nvtegrapart: #8 [MSC ] start=3775488 size=8192 (8)
nvtegrapart: #9 [FLX ] start=3783680 size=204800 (200)
nvtegrapart: #10 [AKB ] start=3988480 size=20480 (20)
nvtegrapart: #11 [UDA ] start=4008960 size=58507264 (57136)
nvtegrapart: #12 [GPT ] start=62516224 size=1024 (1)

Try the thread called rollback from ics leak, it has a rooted 3.2 image so uh, good luck with that
Sent from my A501 using xda app-developers app

Wery strange now, I got mmcblk0p8, but when I flash second boot image then my data is gone (can't boot into tegraowners 170 ROM) it says that can't use data partition and need data reset, after that it is same thing again. In root 3.2.1 is same as EUUs, same,.cfg, maybe I'm doing something wrong. Sorry for bad english. Now I have a501 stock ROM in my a500 and I will try flash second boot again. And thanks for replies.

Taks for help, it seems working now, maybe I should check what ROM I am using next time thanks. Sorry for bad english.

Haha i don't know who your referring to but uh if it worked , your welcome
Sent from my A501 using xda app-developers app

[Q] Nook Color partitioning messed up

Hi,
I've tried to install CM10.1 but I ran into some glitches: 10.1 is some how installed but every time I boot up it says "Android is upgrading" followed by a pop up once I unlock saying "Unfortunately, ConfigUpdater has stopped". This happens every time I boot up.
On the device is a multiboot installed I no longer need. In order to get rid of it, I installed newest CWMR, searched multiple partition recovery packages but none of them worked. I always became "can't open /sdcard/*.zip (bad)". Downloading again (from the device as from my Mac) also didn't work.
When connecting it via adb, partition scheme looks as follows:
adb shell busybox fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 7944 MB, 7944011776 bytes
255 heads, 63 sectors/track, 965 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 9 72261 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p2 10 18 72292+ c Win95 FAT32 (LBA)
/dev/block/mmcblk0p3 19 56 305235 83 Linux
/dev/block/mmcblk0p4 57 965 7301542+ 5 Extended
/dev/block/mmcblk0p5 57 114 465853+ 83 Linux
/dev/block/mmcblk0p6 115 370 2056288+ 83 Linux
/dev/block/mmcblk0p7 371 415 361431 83 Linux
/dev/block/mmcblk0p8 775 965 1534207+ c Win95 FAT32 (LBA)
/dev/block/mmcblk0p9 416 671 2056288+ 83 Linux
/dev/block/mmcblk0p10 672 716 361431 83 Linux
/dev/block/mmcblk0p11 717 774 465822 83 Linux
Partition table entries are not in disk order
I compared this with a partition scheme I found here and it looks like there are some differences.
One more thing: When trying to mount /emmc/ via CWMR it says "can't mount /emmc/", not sure but likely this has to do with this.
As there is absolutely no data I would need on the device, I am fine to do what ever is needed in order to straighten this. I'm also used to Linux so able to execute shell commands. I know adb and like to use it.
What would be the best way to get this device back to operational? I don't find my SD-card adapter so I won't be able to prepare SD cards until I will buy a new one next week.
Thanks!
Sven

antagonist01 said:
Hi,
I've tried to install CM10.1 but I ran into some glitches: 10.1 is some how installed but every time I boot up it says "Android is upgrading" followed by a pop up once I unlock saying "Unfortunately, ConfigUpdater has stopped". This happens every time I boot up.
On the device is a multiboot installed I no longer need. In order to get rid of it, I installed newest CWMR, searched multiple partition recovery packages but none of them worked. I always became "can't open /sdcard/*.zip (bad)". Downloading again (from the device as from my Mac) also didn't work.
When connecting it via adb, partition scheme looks as follows:
adb shell busybox fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 7944 MB, 7944011776 bytes
255 heads, 63 sectors/track, 965 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 9 72261 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p2 10 18 72292+ c Win95 FAT32 (LBA)
/dev/block/mmcblk0p3 19 56 305235 83 Linux
/dev/block/mmcblk0p4 57 965 7301542+ 5 Extended
/dev/block/mmcblk0p5 57 114 465853+ 83 Linux
/dev/block/mmcblk0p6 115 370 2056288+ 83 Linux
/dev/block/mmcblk0p7 371 415 361431 83 Linux
/dev/block/mmcblk0p8 775 965 1534207+ c Win95 FAT32 (LBA)
/dev/block/mmcblk0p9 416 671 2056288+ 83 Linux
/dev/block/mmcblk0p10 672 716 361431 83 Linux
/dev/block/mmcblk0p11 717 774 465822 83 Linux
Partition table entries are not in disk order
I compared this with a partition scheme I found here and it looks like there are some differences.
One more thing: When trying to mount /emmc/ via CWMR it says "can't mount /emmc/", not sure but likely this has to do with this.
As there is absolutely no data I would need on the device, I am fine to do what ever is needed in order to straighten this. I'm also used to Linux so able to execute shell commands. I know adb and like to use it.
What would be the best way to get this device back to operational? I don't find my SD-card adapter so I won't be able to prepare SD cards until I will buy a new one next week.
Thanks!
Sven
Click to expand...
Click to collapse
You still have your old dual boot partition scheme on emmc. Since you cannot seem to get CWM to flash a repair zip, you need to do it manually with ADB and fdisk. P1 through p7 are set up correctly. You need to delete p8, p9, p10 and p11. Then recreate p8 as fat32 to fill the rest of the disk.
Sent from my Nook HD+ running CM10.1 on emmc.

Thanks for the quick reply!
I did as you mentioned. Recreation of partition went fine so I booted into recovery in order to create the filesystem. I used "wipe data/factory reset" which ended without error.
But after the reboot data seems to be still unavailable:
[email protected]:/data # mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,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 /storage tmpfs rw,relatime,mode=050,gid=1028 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/fuse tmpfs rw,relatime,mode=775,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p2 /rom vfat rw,noatime,nodiratime,uid=1000,gid=1000,fmask=0117,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
/dev/block/mmcblk0p5 /system ext4 ro,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p6 /data ext4 rw,nosuid,nodev,noatime,user_xattr,acl,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p7 /cache ext4 rw,nosuid,nodev,noatime,user_xattr,acl,barrier=1,data=ordered 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/179:49 /storage/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:49 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /storage/sdcard1/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
[email protected]:/data # mount /dev/block/mmcblk0p8 tt/
Usage: mount [-r] [-w] [-o options] [-t type] device directory
mkfs.vfat /dev/block/mmcblk0p8
mkfs.vfat: lseek: Value too large for defined data type
I thought mkfs.vfat would make a FAT32 file system? This confuses me...
Any ideas are highly appreciated...
Thanks in advance!
Sven

antagonist01 said:
Thanks for the quick reply!
I did as you mentioned. Recreation of partition went fine so I booted into recovery in order to create the filesystem. I used "wipe data/factory reset" which ended without error.
But after the reboot data seems to be still unavailable:
[email protected]:/data # mount /dev/block/mmcblk0p8 tt/
Usage: mount [-r] [-w] [-o options] [-t type] device directory
mkfs.vfat /dev/block/mmcblk0p8
mkfs.vfat: lseek: Value too large for defined data type
I thought mkfs.vfat would make a FAT32 file system? This confuses me...
Any ideas are highly appreciated...
Thanks in advance!
Sven
Click to expand...
Click to collapse
I don't understand that mount command you did above, so don't know about the mkfs.vfat command either.
The mount command should be:
mount -t vfat /dev/block/mmcblk0p8 /emmc
Since you now have CWM working, go to my NC partition repair thread linked in my signature and flash my 5678 format zip.
Edit: You say data is not available, yet it is mounted in your list as p6. I guess I am not sure what you mean.
Sent from my Nook HD+ running CM10.1 on emmc.

leapinlar said:
I don't understand that mount command you did above, so don't know about the mkfs.vfat command either.
The mount command should be:
mount -t vfat /dev/block/mmcblk0p8 /emmc
Since you now have CWM working, go to my NC partition repair thread linked in my signature and flash my 45678 format zip.
Edit: You say data is not available, yet it is mounted in your list as p6. I guess I am not sure what you mean.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
I tried mounting it manually followed by the try to create the FS manually. Also mount -t vfat /dev/block/mmcblk0p8 /emmc gives mem an error.
Anyhow: I downloaded the files from your thread but had no success:
The NookColor-emmc-format-partitions-5-6-7-8.zip gives me
E:Error in /sdcard/Download/new/NookColor-emmc-format-partitions-5-6-7-8.zip
(Status ())
Installation aborted
When trying NookColor-emmc-repair-partitions-1-4-5-6-7-8.zip screen flickers and it returns to CWMR start screen.
I meanwhile believe CWMR is somehow corrupt. I will search for a manual how to flash via ADB...
Thanks!
Sven

antagonist01 said:
I tried mounting it manually followed by the try to create the FS manually. Also mount -t vfat /dev/block/mmcblk0p8 /emmc gives mem an error.
Anyhow: I downloaded the files from your thread but had no success:
The NookColor-emmc-format-partitions-5-6-7-8.zip gives me
E:Error in /sdcard/Download/new/NookColor-emmc-format-partitions-5-6-7-8.zip
(Status ())
Installation aborted
When trying NookColor-emmc-repair-partitions-1-4-5-6-7-8.zip screen flickers and it returns to CWMR start screen.
I meanwhile believe CWMR is somehow corrupt. I will search for a manual how to flash via ADB...
Thanks!
Sven
Click to expand...
Click to collapse
You cannot flash by ADB. What version of CWM are you using?
Does the fdisk command say that p8 was created properly? And you changed p8 to fat with fdisk, right? You did tell it to write (w) after making those changes?
Sent from my Nook HD+ running CM10.1 on emmc.

leapinlar said:
You cannot flash by ADB. What version of CWM are you using?
Does the fdisk command say that p8 was created properly? You did tell it to write (w) after making those changes, right?
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
OK, that explains my unsuccessful search. I thought it would be possible as I usually do this with my Nexus7 as well...
I wrote the partition table and it also is there:
[email protected]:/ # fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 7944 MB, 7944011776 bytes
255 heads, 63 sectors/track, 965 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 9 72261 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p2 10 18 72292+ c Win95 FAT32 (LBA)
/dev/block/mmcblk0p3 19 56 305235 83 Linux
/dev/block/mmcblk0p4 57 965 7301542+ 5 Extended
/dev/block/mmcblk0p5 57 114 465853+ 83 Linux
/dev/block/mmcblk0p6 115 370 2056288+ 83 Linux
/dev/block/mmcblk0p7 371 415 361431 83 Linux
/dev/block/mmcblk0p8 416 965 4417843+ c Win95 FAT32 (LBA)
[email protected]:/ #
Here the history of what I did:
[email protected]:/ # fdisk /dev/block/mmcblk0
Command (m for help): p
Disk /dev/block/mmcblk0: 7944 MB, 7944011776 bytes
255 heads, 63 sectors/track, 965 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 9 72261 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p2 10 18 72292+ c Win95 FAT32 (LBA)
/dev/block/mmcblk0p3 19 56 305235 83 Linux
/dev/block/mmcblk0p4 57 965 7301542+ 5 Extended
/dev/block/mmcblk0p5 57 114 465853+ 83 Linux
/dev/block/mmcblk0p6 115 370 2056288+ 83 Linux
/dev/block/mmcblk0p7 371 415 361431 83 Linux
/dev/block/mmcblk0p8 775 965 1534207+ c Win95 FAT32 (LBA)
/dev/block/mmcblk0p9 416 671 2056288+ 83 Linux
/dev/block/mmcblk0p10 672 716 361431 83 Linux
/dev/block/mmcblk0p11 717 774 465822 83 Linux
Partition table entries are not in disk order
Command (m for help): d
Partition number (1-11): 11
Command (m for help): d
Partition number (1-10): 10
Command (m for help): d
Partition number (1-9): 9
Command (m for help): d
Partition number (1-8): 8
Command (m for help): n
First cylinder (416-965, default 416):
Using default value 416
Last cylinder or +size or +sizeM or +sizeK (416-965, default 965):
Using default value 965
Command (m for help): t
Partition number (1-8): 8
Hex code (type L to list codes): c
Changed system type of partition 8 to c (Win95 FAT32 (LBA))
Command (m for help): p
Disk /dev/block/mmcblk0: 7944 MB, 7944011776 bytes
255 heads, 63 sectors/track, 965 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 9 72261 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p2 10 18 72292+ c Win95 FAT32 (LBA)
/dev/block/mmcblk0p3 19 56 305235 83 Linux
/dev/block/mmcblk0p4 57 965 7301542+ 5 Extended
/dev/block/mmcblk0p5 57 114 465853+ 83 Linux
/dev/block/mmcblk0p6 115 370 2056288+ 83 Linux
/dev/block/mmcblk0p7 371 415 361431 83 Linux
/dev/block/mmcblk0p8 416 965 4417843+ c Win95 FAT32 (LBA)
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table
fdisk: WARNING: rereading partition table failed, kernel still uses old table: Device or resource busy
Is it possible to replace the actual recovery with a new one? Or would I need a recovery on SD Card?
CWRM is 6.0.3.1 by the way...
Thanks!
Sven

antagonist01 said:
OK, that explains my unsuccessful search. I thought it would be possible as I usually do this with my Nexus7 as well...
I wrote the partition table and it also is there:
Disk /dev/block/mmcblk0: 7944 MB, 7944011776 bytes
255 heads, 63 sectors/track, 965 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 9 72261 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p2 10 18 72292+ c Win95 FAT32 (LBA)
/dev/block/mmcblk0p3 19 56 305235 83 Linux
/dev/block/mmcblk0p4 57 965 7301542+ 5 Extended
/dev/block/mmcblk0p5 57 114 465853+ 83 Linux
/dev/block/mmcblk0p6 115 370 2056288+ 83 Linux
/dev/block/mmcblk0p7 371 415 361431 83 Linux
/dev/block/mmcblk0p8 416 965 4417843+ c Win95 FAT32 (LBA)
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table
fdisk: WARNING: rereading partition table failed, kernel still uses old table: Device or resource busy
Is it possible to replace the actual recovery with a new one? Or would I need a recovery on SD Card?
CWRM is 6.0.3.1 by the way...
Thanks!
Sven
Click to expand...
Click to collapse
Ok, the partition table looks right.
And that 6.0.3.1 CWM is the problem. My old zips do not work on that version. You somehow need to get an older version like 5.5.0.4 on there. You could try flashing the emmc version zip from my NC Tips thread linked in my signature. But it might fail to install too since it is also an old zip.
Sent from my Nook HD+ running CM10.1 on emmc.

Now it makes sense! I meanwhile called my neighbor and got an micro SD card reader borrowed. I saw you have a rescue image linked in your thread as well. Once the card is backed up, I will flash this in order to fix the Nook.
About the threads: Awesome help pages! They really describe everything in a perfect way! The only thing I could think of as minor improvement is md5sums for the links.
I will report back once I'm finished with the SD card.
Thanks a lot for your help!
Sven

Alright, worked like a charm! I've dd'ed the image to a SD card, copied the packages to it and booted into it. From there everything was easily done.
Thank you leapinlar for your quick help and the great manuals!
Sven

[TWRP][ONEPLUS3][TESTING] TWRP 3.0.2-1 | Testing | Help of OP3 Users Required

Straight Into the Topic.
This is based on Omni 6.0 Sources. My OWN FORK/REPO
Please Test, If woking/no please comment in comment section
Downloads:
twrp-3.0.2-1-oneplus3.img
twrp-3.0.2-0-oneplus3.img
Hope You Will Test It!
Source: https://github.com/HostZero/android_device_oneplus_oneplus3/tree/android-6.0
XDA:DevDB Information
[TWRP][ONEPLUS3][TESTING] TWRP 3.0.2-1 | Testing | Help of OP3 Users Required, Tool/Utility for the OnePlus 3
Contributors
HostZero
Version Information
Status: Testing
Created 2016-06-16
Last Updated 2016-06-19

HostZero said:
Straight Into the Topic.
This is based on Omni 6.0 Sources. My OWN FORK/REPO
Please Test, If woking/no please comment in comment section
Downloads:
twrp-3.0.2-0-oneplus3.img
Hope You Will Test It!
Source: https://github.com/HostZero/android_device_oneplus_oneplus3/tree/android-6.0
XDA:DevDB Information
[TWRP][ONEPLUS3][TESTING] TWRP 3.0.2-0 | Testing | Help of OP3 Users Required, Tool/Utility for the OnePlus 3
Contributors
HostZero
Version Information
Status: Testing
Created 2016-06-16
Last Updated 2016-06-16
Click to expand...
Click to collapse
How is this different from the one made by Grarak?

CircuitBug said:
How is this different from the one made by Grarak?
Click to expand...
Click to collapse
Sir, I don't even know the Grarak, made a TWRP. I am here to make official twrp for OP3 , so if booting and other features are fine. I will talk to my superiors to make it OFFICIAL. I hope you will test Recovery Now.
- HostZero

HostZero said:
Sir, I don't even know the Grarak, made a TWRP. I am here to make official twrp for OP3 , so if booting and other features are fine. I will talk to my superiors to make it OFFICIAL. I hope you will test Recovery Now.
- HostZero
Click to expand...
Click to collapse
My phone will arrive today, and I'll gladly test this for you. Any specific checks you need to be carried out?

CircuitBug said:
My phone will arrive today, and I'll gladly test this for you. Any specific checks you need to be carried out?
Click to expand...
Click to collapse
Thabkyou for the positive and quick replies.
I need Backup/Restore, CPU Temp.
And Major, Is it booting?
That's it sir.
- HostZero

I used your toolkit and everything worked well. I'm rooted and running Xposed on my OP3.

My device tree already has TWRP flags inside with decryption working.

And as an addition, Dees Troy will prolly be merging Grarak's sources for Official TWRP. He has tested everything on his phone himself, so
Sent from my OnePlus2 using XDA Labs

both storages in TWRP recovery shows 0 MB, any helps? thanks.

Naman Bhalla said:
And as an addition, Dees Troy will prolly be merging Grarak's sources for Official TWRP. He has tested everything on his phone himself, so
Sent from my OnePlus2 using XDA Labs
Click to expand...
Click to collapse
So its best that I forget TWRP for OnePlus3.

works very well thank you to you
backup not working
Installed there is not

HostZero said:
So its best that I forget TWRP for OnePlus3.
Click to expand...
Click to collapse
LoL
I should get my phone today. Still need more tests?
Is encryption supported already?
Gesendet von meinem OnePlus One

jejemc said:
works very well thank you to you
backup not working
Installed there is not
Click to expand...
Click to collapse
I found the bug, but has raised because of partition details I have provided. Please provide me new block/partition details so I can fix backup install etc issues.

Could I use it with oxygen?
Gesendet von meinem ONEPLUS A3003 mit Tapatalk

HostZero said:
I found the bug, but has raised because of partition details I have provided. Please provide me new block/partition details so I can fix backup install etc issues.
Click to expand...
Click to collapse
Hello what file? I do not see or take it thank you

Hi, Flashed it and its running.
There is a mouse cursor in the middle of the screen.
Backup is not working as I cant select any location where to backup too.
Edit. It seems that I can't mount the data partition to flash supersu.zip

Signor Rossi said:
Hi, Flashed it and its running.
There is a mouse cursor in the middle of the screen.
Backup is not working as I cant select any location where to backup too.
Edit. It seems that I can't mount the data partition to flash supersu.zip
Click to expand...
Click to collapse
Please your a senior member so you ksut be know about block details please provide me your device block info.

HostZero said:
Please your a senior member so you ksut be know about block details please provide me your device block info.
Click to expand...
Click to collapse
Not 100% sure if this is what you are looking for ?
Code:
[email protected]:/ $ cat /proc/partitions
major minor #blocks name
7 0 32768 loop0
8 0 56582144 sda
8 1 8 sda1
8 2 32768 sda2
8 3 262144 sda3
8 4 1024 sda4
8 5 512 sda5
8 6 128 sda6
8 7 128 sda7
8 8 512 sda8
8 9 10240 sda9
8 10 10240 sda10
8 11 1024 sda11
8 12 8096 sda12
8 13 16192 sda13
8 14 512 sda14
8 15 56238572 sda15
8 16 4096 sdb
8 17 4052 sdb1
8 32 4096 sdc
8 33 4052 sdc1
8 80 1572864 sdf
8 81 2048 sdf1
8 82 2048 sdf2
8 83 4 sdf3
8 84 512 sdf4
8 64 4194304 sde
8 65 512 sde1
8 66 512 sde2
8 67 2048 sde3
8 68 2048 sde4
8 69 512 sde5
8 70 512 sde6
8 71 2048 sde7
8 72 16 sde8
8 73 512 sde9
8 74 512 sde10
8 75 97280 sde11
8 76 16384 sde12
8 77 1024 sde13
8 78 32768 sde14
8 79 8192 sde15
259 0 8192 sde16
259 1 16384 sde17
259 2 65536 sde18
259 3 65536 sde19
259 4 3080192 sde20
259 5 65536 sde21
259 6 4 sde22
259 7 1024 sde23
259 8 512 sde24
259 9 512 sde25
259 10 256 sde26
259 11 256 sde27
259 12 256 sde28
259 13 256 sde29
259 14 256 sde30
259 15 256 sde31
259 16 4 sde32
259 17 33424 sde33
259 18 2048 sde34
8 48 131072 sdd
8 49 32 sdd1
8 50 4 sdd2
8 51 1024 sdd3
254 0 56238556 dm-0
[email protected]:/ $
Code:
[email protected]:/ $ mount
rootfs / rootfs ro,seclabel,size=2846160k,nr_inodes=711540 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=2921120k,nr_inodes=730280,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
debugfs /sys/kernel/debug debugfs rw,seclabel,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,size=2921120k,nr_inodes=730280,mode=750,gid=1000 0 0
tmpfs /mnt tmpfs rw,seclabel,relatime,size=2921120k,nr_inodes=730280,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
pstore /sys/fs/pstore pstore rw,seclabel,relatime 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
/dev/block/bootdevice/by-name/system /system ext4 ro,seclabel,noatime,discard,data=ordered 0 0
/dev/block/bootdevice/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/bootdevice/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/bootdevice/by-name/dsp /dsp ext4 ro,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/bootdevice/by-name/modem /firmware vfat ro,context=u:object_r:firmware_file:s0,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/bootdevice/by-name/bluetooth /bt_firmware vfat ro,context=u:object_r:bt_firmware_file:s0,relatime,uid=1002,gid=3002,fmask=0333,dmask=0222,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
tmpfs /storage tmpfs rw,seclabel,relatime,size=2921120k,nr_inodes=730280,mode=755,gid=1000 0 0
/dev/block/dm-0 /data ext4 rw,seclabel,nosuid,nodev,relatime,discard,noauto_da_alloc,data=ordered 0 0
/dev/block/loop0 /su ext4 rw,seclabel,noatime,data=ordered 0 0
/dev/fuse /mnt/runtime/default/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other,reserved_mem=50MB 0 0
/dev/fuse /storage/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other,reserved_mem=50MB 0 0
/dev/fuse /mnt/runtime/read/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other,reserved_mem=50MB 0 0
/dev/fuse /mnt/runtime/write/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other,reserved_mem=50MB 0 0
[email protected]:/ $
Code:
[email protected]:/ # df
Filesystem Size Used Free Blksize
/ 2.7G 4.8M 2.7G 4096
/dev 2.8G 124.0K 2.8G 4096
/sys/fs/cgroup 2.8G 12.0K 2.8G 4096
/mnt 2.8G 0.0K 2.8G 4096
/mnt/runtime/default/emulated 52.6G 22.8G 29.8G 4096
/mnt/runtime/read/emulated 52.6G 22.8G 29.8G 4096
/mnt/runtime/write/emulated 52.6G 22.8G 29.8G 4096
/system 2.8G 2.4G 417.4M 4096
/cache 248.0M 1.1M 246.9M 4096
/persist 27.5M 420.0K 27.1M 4096
/dsp 11.7M 4.1M 7.6M 4096
/firmware 95.0M 81.2M 13.8M 16384
/bt_firmware 1023.7M 112.0K 1023.6M 16384
/storage 2.8G 0.0K 2.8G 4096
/storage/emulated 52.6G 22.8G 29.8G 4096
/data 52.7G 22.8G 29.9G 4096
/su 27.5M 1004.0K 26.5M 4096
[email protected]:/ #

Delete
---------- Post added at 05:45 PM ---------- Previous post was at 05:43 PM ----------
Grarak said:
My device tree already has TWRP flags inside with decryption working.
Click to expand...
Click to collapse
Garak, I installed your recovery and was able to back up successfully.
No problems so far.
Thanks!

phonepersonality said:
Delete
---------- Post added at 05:45 PM ---------- Previous post was at 05:43 PM ----------
Garak, I installed your recovery and was able to back up successfully.
No problems so far.
Thanks!
Click to expand...
Click to collapse
You are in the wrong thread dude
Gesendet von meinem OnePlus One

Michael Kors Access Bradshaw [MKT500X Series] [1st Gen Fossil]

This is my first foray into Wear OS. I seem to always end up with some locked down devices. It Always teaches me a thing or two though! Because all is not lost it seems. I've been trying to compile what I can see from the device into one spot. Information on this series of watches is spread out all over the place. Let me explain what I've found out about The MK Access Bradshaw, that makes me think there is a light at the end of the tunnel. If you have experience with these watches or the Fossil Q sister series, please share. Links to the Fossil Q firmware would be amazing at this point.
Code:
----------------------------------------------
Michael Kors Access Bradshaw Device Info
----------------------------------------------
MODEL: MKT5006
CHIPSET: SD Wear 2100
RAM: 512 MB
STORAGE: 4 GB
SCREEN: 1.4 inch
RESOLUTION: 320x290 pixels (309 ppi)
WEAR OS: 2.6
BUILD: fossil/gar/gar
8.0.0/OWD6.180205.022/53356216
user/release-keys
----------------------------------------------
1. FASTBOOT MODE
[adb reboot bootloader]
----------------------------------------------
PRODUCT_NAME - gar
VARIANT - PFW2
PHASE - SA
BOOTLOADER VERSION - GAR.EINSTEIN_0.083.00
BASEBAND VERSION - N/A
HW_CONFIG - 1
SERIAL NUMBER - XXXXXXXXX (9 Digits)
** A Direct Pin Connection is Needed
to utilize the Fastboot Protocol.
** Fastboot appears active and functional
and only missing a physical connection
** A Pin Connection can be made.
Now, when we finally make it into the recovery mode, we are presented with standard Android Oreo Recovery options. Including the Recovery Logs. It is in these logs I have found A LOT of Information. They have the Log Daemon configured to 'eng'. But I noticed that simply using the 'adb reboot recovery' command, would start recovery mode but never show the recovery menu before rebooting back to the system.
The recovery menu only ever appears for me when I boot into recovery mode from fastboot mode.
Code:
----------------------------------------------
2. RECOVERY MODE
[Boot to Recovery from Bootloader]
----------------------------------------------
* The Recovery Log displays the Recovery FSTAB
* Build.Prop Contents Can also been seen.
* ro.logd.kernel=eng
It is very verbose. But without actual access to the cache partition there is no way to copy & paste, or pull the logs from the watch. My "last_log" entry is from when I updated the device from WearOS 2.2 to version 2.6. In that log, so much of the nitty gritty partition details are revealed, here are a few I've wrote down so far:
Code:
/cache/recovery/last_log:
-----------------------------
0 /system ext4 /dev/block/platform/soc/7824900.sdhci/by-name/system 0
1 /cache ext4 /dev/block/platform/soc/7824900.sdhci/by-name/cache 0
2 /data ext4 /dev/block/platform/soc/7824900.sdhci/by-name/userdata -16384
3 /sdcard vfat /dev/block/mmcblk1p1 0
4 /boot emmc /dev/block/platform/soc/7824900.sdhci/by-name/boot 0
5 /recovery emmc /dev/block/platform/soc/7824900.sdhci/by-name/recovery 0
6 /misc emmc /dev/block/platform/soc/7824900.sdhci/by-name/misc 0
7 /oem ext4 /dev/block/platform/soc/7824900.sdhci/by-name/oem 0
8 /tmp ramdisk ramdisk 0
ro.sys.fw.use_trim_settings=true
ro.sys.fw.trim_enable_memory=1073741824
ro.sys.fw.trim_empty_percent=100
ro.sys.fw.trim_cache_percent=100
ro.sys.fw.empty_app_percent=50
ro.sys.umsdirtyratio=20
ro.boot.hardware=gar
ro.boot.baseband=apq
ro.boot.console=null
ro.boot.ceibootmode=0
ro.boot.bootdevice=7824900.sdhci
ro.board.platform=msm8909
ro.build.host=abfarm648
ro.product.cpu.abi=armeabi-v7a
ro.boot.verifiedbootstate=green
ro.boot.authorized_kernel=true
ro.logd.kernel=eng
ro.bootimage.build.date=Thu Aug 9 00:39:05 UTC 2018
[11.364486]Verifying update package...
I:comment is 1476 bytes; signature is 1458 bytes from end.
I:signature (offset: 10127db, length: 5ac):
That log continues on with all of the signature, but on the watch screen it is quite a few pages long. But continues on during the whole verification process. And it really does say in so many words what it is doing and when. The log explains exactly what data it is putting where, and where the developers forgot to set expected values that the system must choose a default for.
What I need to do now is go through the log with an OCR App that can take pictures of the screen and extract the text. I believe the two most recent log files on my watch could explain just how to get at the bootloader & kernel. They definitely tell you where to go find the eFuse. Because even though it has Green Verified Boot Status, the boot log shows a few things for verified boot were never actually implemented. I'm working on getting these logs now.
Enable Developer Options:
Settings > System > About > Tap Build Number until it unlocks.
Connecting to ADB:
1.) Enable Developer Options
2.) Disable Bluetooth
3.) Connect Device to Wi-Fi
4.) Settings > Dev Options > ADB Debugging
5.) Settings > Dev Options > Debug Over Wi-Fi
6.) From a command line, start the adb server and then use this command with the watch's wifi ip address: "adb connect <ip_address>:5555"
7.) Run command "adb devices" and hit the yes button on the watch face to accept the connection.
Replacement 1st Gen Fossil Watch Chargers (2016-2017 Watches):
1.) 1st Party Marc Jacob's MJT0001/MKT0001
2.) 3rd Party Soarking Fossil Charger
Once I find a repair manual or schematic to this thing, I think I'm going to work on creating a cable to connect to the board for fastboot access.
MEMINFO
Code:
MemTotal: 455000 kB
MemFree: 8228 kB
MemAvailable: 179528 kB
Buffers: 2216 kB
Cached: 179400 kB
SwapCached: 7136 kB
Active: 153580 kB
Inactive: 154504 kB
Active(anon): 63348 kB
Inactive(anon): 64340 kB
Active(file): 90232 kB
Inactive(file): 90164 kB
Unevictable: 256 kB
Mlocked: 256 kB
SwapTotal: 338936 kB
SwapFree: 222520 kB
Dirty: 0 kB
Writeback: 0 kB
AnonPages: 125548 kB
Mapped: 78400 kB
Shmem: 1216 kB
Slab: 41732 kB
SReclaimable: 13440 kB
SUnreclaim: 28292 kB
KernelStack: 8544 kB
PageTables: 20392 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 566436 kB
Committed_AS: 26409868 kB
VmallocTotal: 499712 kB
VmallocUsed: 95544 kB
VmallocChunk: 291668 kB
MOUNTS
Code:
rootfs / rootfs ro,seclabel,size=205932k,nr_inodes=51483 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=221356k,nr_inodes=55339,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime,gid=3009,hidepid=2 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,seclabel,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt tmpfs rw,seclabel,relatime,size=221356k,nr_inodes=55339,mode=755,gid=1000 0 0
none /config configfs rw,relatime 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
pstore /sys/fs/pstore pstore rw,seclabel,relatime 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
/dev/block/platform/soc/7824900.sdhci/by-name/system /system ext4 ro,seclabel,relatime,discard 0 0
/dev/block/platform/soc/7824900.sdhci/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/platform/soc/7824900.sdhci/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/platform/soc/7824900.sdhci/by-name/modem /firmware vfat ro,context=u:object_r:firmware_file:s0,relatime,uid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/platform/soc/7824900.sdhci/by-name/oem /oem ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/platform/soc/7824900.sdhci/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,errors=panic,data=ordered 0 0
tmpfs /storage tmpfs rw,seclabel,relatime,size=221356k,nr_inodes=55339,mode=755,gid=1000 0 0
/data/media /mnt/runtime/default/emulated sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=1015,multiuser,mask=6,derive_gid 0 0
/data/media /storage/emulated sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=1015,multiuser,mask=6,derive_gid 0 0
/data/media /mnt/runtime/read/emulated sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,multiuser,mask=23,derive_gid 0 0
/data/media /mnt/runtime/write/emulated sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,multiuser,mask=7,derive_gid 0 0
PARTITIONS
Code:
major - minor - #blocks name
-------------------------------------
254 - 0 - 262144 zram0
179 - 0 - 3817472 mmcblk0
179 - 1 - 65536 mmcblk0p1
179 - 2 - 512 mmcblk0p2
179 - 3 - 512 mmcblk0p3
179 - 4 - 512 mmcblk0p4
179 - 5 - 512 mmcblk0p5
179 - 6 - 768 mmcblk0p6
179 - 7 - 768 mmcblk0p7
179 - 8 - 1024 mmcblk0p8
179 - 9 - 1536 mmcblk0p9
179 - 10 - 1536 mmcblk0p10
179 - 11 - 1536 mmcblk0p11
179 - 12 - 1 mmcblk0p12
179 - 13 - 1024 mmcblk0p13
179 - 14 - 8 mmcblk0p14
179 - 15 - 10240 mmcblk0p15
179 - 16 - 32 mmcblk0p16
179 - 17 - 16 mmcblk0p17
179 - 18 - 32768 mmcblk0p18
179 - 19 - 32768 mmcblk0p19
179 - 20 - 512 mmcblk0p20
179 - 21 - 1024 mmcblk0p21
179 - 22 - 1024 mmcblk0p22
179 - 23 - 32768 mmcblk0p23
179 - 24 - 32768 mmcblk0p24
179 - 25 - 1024 mmcblk0p25
179 - 26 - 512 mmcblk0p26
179 - 27 - 512 mmcblk0p27
179 - 28 - 16384 mmcblk0p28
179 - 29 - 256 mmcblk0p29
179 - 30 - 256 mmcblk0p30
179 - 31 - 256 mmcblk0p31
259 - 0 - 256 mmcblk0p32
259 - 1 - 65536 mmcblk0p33
259 - 2 - 655360 mmcblk0p34
259 - 3 - 2310127 mmcblk0p35
179 - 32 - 4096 mmcblk0rpmb
DF Utility
Code:
Filesystem 1K-blocks Used Available Use% Mounted on
---------------------------------------------------------------------------
rootfs 205932 3460 202472 2% /
tmpfs 221356 532 220824 1% /dev
tmpfs 221356 0 221356 0% /mnt
/dev/block/mmcblk0p34 645056 630224 0 100% /system
/dev/block/mmcblk0p33 60400 1632 57460 3% /cache
/dev/block/mmcblk0p1 65488 22240 43248 34% /firmware
/dev/block/mmcblk0p28 12016 64 11628 1% /oem
/dev/block/mmcblk0p35 2237680 690400 1530896 32% /data
/data/media 2237680 690400 1530896 32% /storage/emulated

Since making this thread, this update no longer seems to be available. I think I am also leaving XDA, my words here have caused me too much trouble.