Database Develop

[Q] Where can I find fsck.vfat for I9000?

Hi,
I can't find fsck.vfat in order to repair a corrupt internal SD card.
How come it's not that popular (if it exists at all)?
Thanks,
Yaron.

I found there is a build in one patched by samsung, if it was not added by custom firmware.
# /system/bin/fsck_msdos -ny /dev/block/vold/179:1
/system/bin/fsck_msdos -ny /dev/block/vold/179:1
patched by [email protected] 2011/01/21
** /dev/block/vold/179:1
Boot sector contents:
bytes per sector:.............512
sectors per cluster:..........64
number of reserved sectors:...32
number of FATs:...............2
number of sectors are in FAT:.3440 (1720 KB)
cluster mask (bit):...........32
FAT entries:..................440320
first cluster offset..........6784
cluster size(bytes):..........32768
number of sectors:............28180416
hidden sectors:...............0
number of clusters:...........440213
oem name:.....................android { 0x61 0x6e 0x64 0x72 0x6f 0x69 0x64 0x20}
volume serial number:.........466b-16f7
volume label:.................NO NAME { 0x4f 0x20 0x4e 0x41 0x4d 0x45 0x20 0x20 0x20 0x20 0x46}
file system string id:........FAT32 { 0x41 0x54 0x33 0x32 0x20 0x20 0x20 0xfa}
** Phase 1 - Read and Compare FATs
Attempting to allocate 1720 KB for FAT
Attempting to allocate 1720 KB for FAT
** Phase 2 - Check Cluster Chains
** Phase 3 - Checking Directories
** Phase 4 - Checking for Lost Files
FSNext block (3) is correct, NumClusters (440213)
11950 files, 4180320 free (130635 clusters)

[Q] Hardware Watchdog Crash

I have a Sony Xperia TX. It randomly crashes and it reads - Phone crashed please wait for the crash reports to be saved.
it also say Hardware Watchdog crash stored on internel sdcard.
I am posting my crash reports from the CrashDump folder.
rdlog_init() created temp log file: /hhVMYg
[E] Could not open VT /dev/tty0: "No such file or directory"
Framebuffer initialized: 720x1280, 16bpp, 1.8MB
Setting backlight [/sys/class/leds/lcd-backlight_1/brightness] intensity to 255 (masked to 255)
Setting backlight [/sys/class/leds/lcd-backlight_2/brightness] intensity to 255 (masked to 255)
[E] Failed to open /sys/class/timed_output/vibrator/enable: No such file or directory
RamdumpV3 app. Version: 1.0.A.0.57
Loading configuration from conf.xml
adding 1 mount point(s)
Mount of /dev/block/by-name/SDCard on /YMogkv with file system ext4 returned: SUCCESS
DUMP /YMogkv /dev/block/by-name/SDCard 179:15 ext4 READY
Cleaning up permission problems for CrashDump
Unable to open RTC device
No rtc time
Creating /YMogkv/CrashDump/Crash-YMD-HMS-19000100-000000 directory
[W] Failed to create /YMogkv/CrashDump/Crash-YMD-HMS-19000100-000000, retrying... No such device
Creating /YMogkv/CrashDump/Crash-YMD-HMS-19000100-000000_0 directory
ramdump log created at "/YMogkv/CrashDump/Crash-YMD-HMS-19000100-000000_0/ramdump.log"
Updating /YMogkv/CrashDump/crashinfo
opened memory device node /dev/mem (3) in O_RDWR | O_SYNC mode
Verify config
Reading cmdline file /proc/cmdline:
* Found: startup=6a58c
* Found: warmboot=6a594
* Found: androidboot.serialno= CB5A1JYRHT
RestartReason=0xabadbabe, restartReasonType=1
No buildinfo found, fallback to crash-notes.
Storing kernel log to: /YMogkv/CrashDump/Crash-YMD-HMS-19000100-000000_0/ramdump_system.log
Searching linux area 12 (0x80200000, 0x8d00000) for magic 0xCAFEBABE.
[W] Default build id checksum! Early kernel crash?
Found build info in crash notes: 7.0.A.3.193\hayabusa\userdebug
Found crash notes for crashing CPU! Crashing process:
[W] Skipping ram console search, crash type is 1
RESTART_REASON: 0xABADBABE (Hardware watchdog)
Creating /YMogkv/CrashDump/Crash-YMD-HMS-19000100-000000_0/ramdumpinfo
HWWD but can't read /proc/rdtags/addr_scm_regsave from rdtags: errno=2 <No such file or directory>
HWWD using hardcoded physical addr 0x2a03f658
CPU registers dump addr (phy) 0x00000000={0xea000006, 0xea000060, 0xea000063, ...}
HWWD found but no TZBSP_DUMP_CTX_MAGIC (found 0xea000006 expected 0x44434151)
RDTAG_DIR not set for this platform! Skipping rdtags dump!
Creating /YMogkv/CrashDump/Crash-YMD-HMS-19000100-000000_0/productinfo
Creating dump file: /YMogkv/CrashDump/Crash-YMD-HMS-19000100-000000_0/tlcore
Platform: blue
Dump areas:
( 0) address=0x0006206c size=0x00000004 flags=0x00006000 name: WDT Reset... success!
( 1) address=0x09000000 size=0x00008000 flags=0x0000a000 name: MDSP Ram A... success!
( 2) address=0x09200000 size=0x00008000 flags=0x0000c000 name: MDSP Ram B... success!
( 3) address=0x09400000 size=0x0000f800 flags=0x0000e000 name: MDSP Ram C... success!
( 4) address=0x12000000 size=0x0002c000 flags=0x00010008 name: SPS RAM... success!
( 5) address=0x12040000 size=0x00004000 flags=0x00012000 name: SPS Buff RAM... success!
( 6) address=0x12800000 size=0x00008000 flags=0x00014000 name: SPS Pipe Mem... success!
( 7) address=0x28400000 size=0x00020000 flags=0x00016008 name: Lpass Memory... success!
( 8) address=0x2a000000 size=0x00010000 flags=0x00018008 name: System IMEM-A... success!
( 9) address=0x2a03f000 size=0x00001000 flags=0x0001c000 name: System IMEM-C... success!
(10) address=0x38000000 size=0x04000000 flags=0x00020008 name: SMI CS0... success!
(11) address=0x80000000 size=0x00200000 flags=0x00080088 name: EBI1_CH0_CS0(SMEM)... success!
(12) address=0x80200000 size=0x08d00000 flags=0x00080028 name: EBI1_CH0_CS0(LINUX)... success!
(13) address=0x88f00000 size=0x00100000 flags=0x00080008 name: EBI1_CH0_CS0(APPSBL)... success!
(14) address=0x89000000 size=0x04400000 flags=0x00080018 name: EBI1_CH0_CS0(Modem Q6 SW)... success!
(15) address=0x8d400000 size=0x00600000 flags=0x00080018 name: EBI1_CH0_CS0(Modem Q6 FW)... success!
(16) address=0x8da00000 size=0x01800000 flags=0x00080008 name: EBI1_CH0_CS0(LP_Audio_SS)... success!
(17) address=0x8f200000 size=0x00500000 flags=0x00080008 name: EBI1_CH0_CS0(WConnect_SS)... success!
(18) address=0x8f700000 size=0x00080000 flags=0x00080008 name: EBI1_CH0_CS0(TZ Image)... success!
(19) address=0x8f780000 size=0x00080000 flags=0x00080008 name: EBI1_CH0_CS0(Reserved)... success!
(20) address=0x8f800000 size=0x00300000 flags=0x00080008 name: EBI1_CH0_CS0(FS Cache)... success!
(21) address=0x8fb00000 size=0x00300000 flags=0x00080008 name: EBI1_CH0_CS0(RAM EFS)... success!
(22) address=0x8fe00000 size=0x00100000 flags=0x00080008 name: EBI1_CH0_CS0(SPS Image)... success!
(23) address=0x8ff00000 size=0x00100000 flags=0x00080008 name: EBI1_CH0_CS0(SBL3)... success!
(24) address=0x90000000 size=0x10000000 flags=0x00080028 name: EBI1_CH1_CS0(LINUX)... success!
(25) address=0xa0000000 size=0x10000000 flags=0x00100028 name: EBI1_CH0_CS1(LINUX)... success!
(26) address=0xb0000000 size=0x10000000 flags=0x00100028 name: EBI1_CH1_CS1(LINUX)... success!
(27) path=/dev/msm_etb_boot flags=0x00024008 name: ETB... Read from /dev/msm_etb_boot: 16384, written to dump: 1530
success!
(28) cmdlineParam=semcandroidboot.rpmcoderamcopy, address=0x00020000 size=0x00000000 flags=0x00002008 name: RPM Code RAM... Found cmdline specified dump area (semcandroidboot.rpmcoderamcopy)
Reading cmdline file /proc/cmdline:
* Found: semcandroidboot.rpmcoderamcopy=
cmdLine area [email protected],0x20000
addr = 0x88f00000 size = 147456 orgAddr = 0x20000
success!
(29) cmdlineParam=semcandroidboot.rpmregistercopy, address=0x0002e000 size=0x00000000 flags=0x00004000 name: RPM Registers... Found cmdline specified dump area (semcandroidboot.rpmregistercopy)
Reading cmdline file /proc/cmdline:
* Found: semcandroidboot.rpmregistercopy=
cmdLine area [email protected],0x2E000
addr = 0x88f24000 size = 104 orgAddr = 0x2e000
success!
(30) cmdlineParam=semcandroidboot.rpmmsgramcopy, address=0x00108000 size=0x00000000 flags=0x00008000 name: RPM Msg RAM... Found cmdline specified dump area (semcandroidboot.rpmmsgramcopy)
Reading cmdline file /proc/cmdline:
* Found: semcandroidboot.rpmmsgramcopy=
cmdLine area [email protected],0x108000
addr = 0x88f24100 size = 24575 orgAddr = 0x108000
success!
Updating /YMogkv/CrashDump/Crash-YMD-HMS-19000100-000000_0/ramdumpinfo
Ramdump finished in 154s
Ramdump done! type: 1, name: , result: RAMDUMP_RESULT_OK (00)
SD card free space: 8495 MB
Closing graphics and flushing log files
Setting backlight [/sys/class/leds/lcd-backlight_1/brightness] intensity to 0 (masked to 0)
Setting backlight [/sys/class/leds/lcd-backlight_2/brightness] intensity to 0 (masked to 0)
[E] Could not open VT /dev/tty0: "No such file or directory"
Can anyone help me fix this problem?

Go on ,please try to help us help you.
Rooted?
Bootloader unlocked? If so which kernel?
Stock ROM? If so which FW?
Custom ROM? If so which ROM and version.
What did you do to the phone prior to this happening?

gregbradley said:
Go on ,please try to help us help you.
Rooted?
Bootloader unlocked? If so which kernel?
Stock ROM? If so which FW?
Custom ROM? If so which ROM and version.
What did you do to the phone prior to this happening?
Click to expand...
Click to collapse
Not rooted
Bootlocker is not unlocked
The phone is out of the box and i did not change any ROM settings or Rooted it. Nothing has been changed.
I was surfing my gallery when this first happened.
after that it was like 2 to 3 times a day

Samsung Galaxy Gear Hardware Details

I've seen a few different things that stated our watches have an 800 MHz processor. I was looking for a reason to tinker, so heres what I came up with via root and Busybox:
total used free shared buffers
Mem: 420 392 27 0 13
-/+ buffers: 379 40
Swap: 0 0 0
[email protected]:/ #
Processor : ARMv7 Processor rev 8 (v7l)
processor : 0
BogoMIPS : 1592.52
Features : swp half thumb fastmult vfp edsp neon vfpv3 tls
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x2
CPU part : 0xc09
CPU revision : 8
Chip name : EXYNOS4212
Hardware : SMDK4x12
Revision : 0005
[email protected]:/ # busybox df -h
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 210.1M 76.0K 210.0M 0% /dev
tmpfs 210.1M 0 210.1M 0% /mnt/secure
tmpfs 210.1M 0 210.1M 0% /mnt/asec
tmpfs 210.1M 0 210.1M 0% /mnt/obb
/dev/block/mmcblk0p20
787.4M 388.0M 399.4M 49% /system
/dev/block/mmcblk0p3 19.7M 4.2M 15.5M 21% /efs
/dev/block/mmcblk0p19
315.0M 5.5M 309.5M 2% /cache
/dev/block/mmcblk0p21
2.4G 119.2M 2.3G 5% /data
/data/media 2.4G 119.2M 2.2G 5% /mnt/shell/emulated
I was surprised at the processor, doesn't seem too shabby!

Also, if anyone screws up their build.prop and needs the stock, or wants to tinker, its attached.

How did you root it?
Sent from my SM-N900V now Free

http://forum.xda-developers.com/showpost.php?p=46340266&postcount=21

[Q] Bricked or not bricked ? That is the question! --- Part 2

A bit more than a year ago I posted the following question:
http://forum.xda-developers.com/hp-touchpad/help/brick-bricked-question-t3015736
Basically I got possible boot stuff ( software/partition etc) corrupted as the TouchPas won't boot normally.
But do have some connectivity in the Palm (bootie) mode ( HOME-POWER-VOL.UP ) I can issue the following commands and boot into some minimal Linux system.
#1 Hold the HOME-POWER-VOL.UP buttons until the TouchPad enumerate on USB as:
Palm:
Product ID: 0x8070
Vendor ID: 0x0830 (Palm Inc.)
Version: 10.00
Speed: Up to 480 Mb/sec
Manufacturer: bootie
Location ID: 0xfd130000 / 4
Current Available (mA): 1000
Current Required (mA): 500
Extra Operating Current (mA): 0
#2 DFU-UTIL
$ dfu-util -d 0830:8070 -R -D tpdebrick-v004/moboot-dfu-v004
#3 FASTBOOT
$ fastboot flash bootmem /tpdebrick-v004/TPToolbox-Headless-v004
At this point the TouchPad enumerates as follow on the USB port:
CDC Composite Gadget:
Product ID: 0xa4aa
Vendor ID: 0x0525 (PLX Technology, Inc.)
Version: 3.27
Speed: Up to 480 Mb/sec
Manufacturer: Linux 2.6.35.7+ with msm72k_udc
Location ID: 0xfd130000 / 5
Current Available (mA): 500
Current Required (mA): 500
BSD Name: en4
#4 LOGIN THE LINUX SYSTEM
$ ssh -i tpdebrick-v004/ssh-key [email protected]
From there, is there anything I can do like DD-ing one of the boot partitions... copy software to restore TWRP or similar recovery software?

unable to boot SD. sideload_2.2_update.npk issue? (black screen for >5min between on and boot)

I'm using the wonderfully organized files from amaces' box to image an sd card for BNVT400/hummingbird. After dd-ing the .img file, the Nook seems to try to boot from it. But, after 6 minutes of a black screen, it boots into stock normally. From the stock android I can see SD card contents -- it's mounted and has the files I expect it to.
Notably, before considering a custom ROM, I recently factory reset. Because the stock setup wizard failed with an internet connectivity issue (re: TLS<1.2), I followed B&N's instructions and updated with sideload_2.2_update.npk
Even after additional factory resets, the software version remains 2.2.1
I've read in a few places (e.g leapinlar;s tips) that SD boot isn't a sure thing. I've tried maybe 10 times across 2 days. With and without powering on via USB cable. (and via adb reboot and adb reboot bootloader). That's overkill right?
Is there something obvious I missed?
Thanks!
_________
Bash:
sudo dd if=sdcard-reco-hummingbird.img of=/dev/sdd bs=1M status=progress
# 933232640 bytes (933 MB, 890 MiB) copied, 58 s, 16.1 MB/s
# 900+0 records in
# 900+0 records out
# 943718400 bytes (944 MB, 900 MiB) copied, 81.4684 s, 11.6 MB/s
SD card is formatted w/ only partition as Fat32 with boot flag, and with first file MLO
Bash:
sudo fdisk -l /dev/sdd
# Disk /dev/sdd: 7.5 GiB, 8057257984 bytes, 15736832 sectors
# Disk model: MassStorageClass
# Units: sectors of 1 * 512 = 512 bytes
# Sector size (logical/physical): 512 bytes / 512 bytes
# I/O size (minimum/optimal): 512 bytes / 512 bytes
# Disklabel type: dos
# Disk identifier: 0x5387f638
#
# Device Boot Start End Sectors Size Id Type
# /dev/sdd1 * 59 1757963 1757905 858.4M c W95 FAT32 (LBA)
sudo mount /dev/sdd1 /mnt/usb -o uid=1000
stat -c "%y %n" /mnt/usb/*|sort
# 2013-06-10 15:49:44.000000000 -0400 /mnt/usb/MLO
# 2013-06-10 15:49:56.000000000 -0400 /mnt/usb/u-boot.bin
# 2014-01-19 18:22:28.000000000 -0500 /mnt/usb/ramdisk.cwm
# 2016-02-13 14:48:20.000000000 -0500 /mnt/usb/ramdisk.stock
# 2016-02-13 14:50:58.000000000 -0500 /mnt/usb/OLD
# 2016-04-03 13:35:56.000000000 -0400 /mnt/usb/kernel
# 2016-04-03 13:35:56.000000000 -0400 /mnt/usb/ramdisk
# 2016-04-03 13:35:56.000000000 -0400 /mnt/usb/uImage
# added zips to flash. but never get to use them :(
cp lnos_hummingbird-ota-NJH47F.181223.zip twrp-2.8.7.5-hummingbird.zip addonsu-14.1-arm.zip /mnt/usb/
eject /mnt/usb
As a sanity check: when the sd boot fails, I confirmed the files on the SD card are readable by the Nook. and that the Nook is in fact BNVT400/hummingbird.
Bash:
aft-mtp-cli ls
# selected storage 131073 SD Card
# 155 MLO
# 156 u-boot.bin
# 157 ramdisk.stock
# 158 ramdisk
# 159 kernel
# 160 ramdisk.cwm
# 161 OLD
# 164 lnos_hummingbird-ota-NJH47F.181223.zip
# 165 twrp-2.8.7.5-hummingbird.zip
# 166 uImage
# 167 addonsu-14.1-arm.zip
# 168 B&N Downloads
# 173 My Files
adb shell cat /proc/cpuinfo
# Processor : ARMv7 Processor rev 10 (v7l)
# processor : 0
# BogoMIPS : 789.24
# processor : 1
# BogoMIPS : 792.89
# Features : swp half thumb fastmult vfp edsp thumbee neon vfpv3
# CPU implementer : 0x41
# CPU architecture: 7
# CPU variant : 0x2
# CPU part : 0xc09
# CPU revision : 10
# Hardware : OMAP4 Hummingbird board
# Revision : 0006