AOSP build issues - Xperia Z4/Z3+ Q&A, Help & Troubleshooting

Anyone have any insight into why my AOSP build isn't completing the boot process? Up to the end of the attached logcat, it seems to be the same as @ChrisJ951's previously posted logcat on a build that boots correctly.
I've rebuilt multiple times after doing a make clobber, repo sync, re-apply patches, etc., but nothing seems to work. Host is Fedora 21, openjdk 1.70_79...

What if you try to build without SELinux and double check proper fstab?
It worked here (no touch driver in first release) on my Tablet Z4.

DHGE said:
What if you try to build without SELinux and double check proper fstab?
It worked here (no touch driver in first release) on my Tablet Z4.
Click to expand...
Click to collapse
I'll give that a try although SELinux is running in permissive mode. It looks like the init process might not be completing the various init scripts correctly. The system boots as I can get an adb shell and the various partitions appear to be mounted correctly although the display only shows the Android logo and nothing more. The device gets very hot after a few minutes.
It's not the kernel either as I compiled a new one from source and it exhibits the same behaviour....
Code:
rootfs / rootfs ro,seclabel,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=1425884k,nr_inodes=356471,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,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,size=1425884k,nr_inodes=356471,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,size=1425884k,nr_inodes=356471,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,size=1425884k,nr_inodes=356471,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
tmpfs /tmp tmpfs rw,seclabel,nosuid,relatime,size=1425884k,nr_inodes=356471,mode=755 0 0
/dev/block/platform/soc.0/by-name/system /system ext4 ro,seclabel,relatime,discard,data=ordered 0 0
/dev/block/platform/soc.0/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/soc.0/by-name/modem /firmware vfat rw,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
and the output of ps -Z...
Code:
LABEL USER PID PPID NAME
u:r:init:s0 root 1 0 /init
u:r:kernel:s0 root 2 0 kthreadd
u:r:kernel:s0 root 3 2 ksoftirqd/0
u:r:kernel:s0 root 5 2 kworker/0:0H
u:r:kernel:s0 root 6 2 kworker/u16:0
u:r:kernel:s0 root 7 2 migration/0
u:r:kernel:s0 root 8 2 rcu_preempt
u:r:kernel:s0 root 9 2 rcu_bh
u:r:kernel:s0 root 10 2 rcu_sched
u:r:kernel:s0 root 11 2 migration/1
u:r:kernel:s0 root 12 2 ksoftirqd/1
u:r:kernel:s0 root 13 2 kworker/1:0
u:r:kernel:s0 root 14 2 kworker/1:0H
u:r:kernel:s0 root 15 2 migration/2
u:r:kernel:s0 root 16 2 ksoftirqd/2
u:r:kernel:s0 root 17 2 kworker/2:0
u:r:kernel:s0 root 18 2 kworker/2:0H
u:r:kernel:s0 root 19 2 migration/3
u:r:kernel:s0 root 20 2 ksoftirqd/3
u:r:kernel:s0 root 21 2 kworker/3:0
u:r:kernel:s0 root 22 2 kworker/3:0H
u:r:kernel:s0 root 23 2 migration/4
u:r:kernel:s0 root 24 2 ksoftirqd/4
u:r:kernel:s0 root 26 2 kworker/4:0H
u:r:kernel:s0 root 27 2 migration/5
u:r:kernel:s0 root 28 2 ksoftirqd/5
u:r:kernel:s0 root 30 2 kworker/5:0H
u:r:kernel:s0 root 31 2 khelper
u:r:kernel:s0 root 32 2 netns
u:r:kernel:s0 root 33 2 perf
u:r:kernel:s0 root 34 2 kworker/0:1
u:r:kernel:s0 root 35 2 kworker/1:1
u:r:kernel:s0 root 36 2 kworker/2:1
u:r:kernel:s0 root 37 2 kworker/3:1
u:r:kernel:s0 root 40 2 kworker/1:1H
u:r:kernel:s0 root 41 2 smd_channel_clo
u:r:kernel:s0 root 42 2 smsm_cb_wq
u:r:kernel:s0 root 43 2 kworker/u16:1
u:r:kernel:s0 root 44 2 deferwq
u:r:kernel:s0 root 45 2 kworker/u17:0
u:r:kernel:s0 root 46 2 rpm-smd
u:r:kernel:s0 root 47 2 kworker/u17:1
u:r:kernel:s0 root 48 2 irq/48-cpr
u:r:kernel:s0 root 49 2 irq/51-cpr
u:r:kernel:s0 root 50 2 mpm
u:r:kernel:s0 root 52 2 writeback
u:r:kernel:s0 root 53 2 bioset
u:r:kernel:s0 root 54 2 crypto
u:r:kernel:s0 root 55 2 kblockd
u:r:kernel:s0 root 56 2 khubd
u:r:kernel:s0 root 57 2 system
u:r:kernel:s0 root 58 2 ipa_power_mgmt
u:r:kernel:s0 root 59 2 sps_ipa_power_m
u:r:kernel:s0 root 60 2 ipawq14
u:r:kernel:s0 root 61 2 iparepwq14
u:r:kernel:s0 root 62 2 ipawq43
u:r:kernel:s0 root 63 2 iparepwq43
u:r:kernel:s0 root 64 2 ipawq13
u:r:kernel:s0 root 65 2 iparepwq13
u:r:kernel:s0 root 66 2 ipa_power_mgmt
u:r:kernel:s0 root 67 2 ipa_rm_wq
u:r:kernel:s0 root 68 2 ipa_interrupt_w
u:r:kernel:s0 root 69 2 irq/261-msm_iom
u:r:kernel:s0 root 70 2 irq/263-msm_iom
u:r:kernel:s0 root 71 2 irq/261-msm_iom
u:r:kernel:s0 root 72 2 irq/263-msm_iom
u:r:kernel:s0 root 73 2 irq/261-msm_iom
u:r:kernel:s0 root 74 2 irq/263-msm_iom
u:r:kernel:s0 root 75 2 irq/261-msm_iom
u:r:kernel:s0 root 76 2 irq/263-msm_iom
u:r:kernel:s0 root 77 2 irq/261-msm_iom
u:r:kernel:s0 root 78 2 irq/263-msm_iom
u:r:kernel:s0 root 79 2 irq/261-msm_iom
u:r:kernel:s0 root 80 2 irq/263-msm_iom
u:r:kernel:s0 root 81 2 irq/261-msm_iom
u:r:kernel:s0 root 82 2 irq/263-msm_iom
u:r:kernel:s0 root 83 2 irq/102-msm_iom
u:r:kernel:s0 root 84 2 irq/102-msm_iom
u:r:kernel:s0 root 85 2 irq/102-msm_iom
u:r:kernel:s0 root 86 2 irq/102-msm_iom
u:r:kernel:s0 root 87 2 irq/74-msm_iomm
u:r:kernel:s0 root 88 2 irq/75-msm_iomm
u:r:kernel:s0 root 89 2 irq/75-msm_iomm
u:r:kernel:s0 root 90 2 irq/75-msm_iomm
u:r:kernel:s0 root 91 2 irq/75-msm_iomm
u:r:kernel:s0 root 92 2 irq/273-msm_iom
u:r:kernel:s0 root 93 2 irq/273-msm_iom
u:r:kernel:s0 root 94 2 irq/272-msm_iom
u:r:kernel:s0 root 95 2 irq/97-msm_iomm
u:r:kernel:s0 root 96 2 irq/97-msm_iomm
u:r:kernel:s0 root 97 2 irq/97-msm_iomm
u:r:kernel:s0 root 98 2 irq/350-msm_iom
u:r:kernel:s0 root 99 2 irq/350-msm_iom
u:r:kernel:s0 root 100 2 irq/350-msm_iom
u:r:kernel:s0 root 101 2 irq/298-msm_iom
u:r:kernel:s0 root 102 2 irq/298-msm_iom
u:r:kernel:s0 root 103 2 irq/298-msm_iom
u:r:kernel:s0 root 104 2 irq/79-msm_iomm
u:r:kernel:s0 root 105 2 irq/78-msm_iomm
u:r:kernel:s0 root 106 2 irq/78-msm_iomm
u:r:kernel:s0 root 107 2 devfreq_wq
u:r:kernel:s0 root 108 2 cfg80211
u:r:kernel:s0 root 109 2 irq/15-bcl_vbat
u:r:kernel:s0 root 110 2 irq/460-bcl_iba
u:r:kernel:s0 root 133 2 kswapd0
u:r:kernel:s0 root 134 2 fsnotify_mark
u:r:kernel:s0 root 135 2 cifsiod
u:r:kernel:s0 root 155 2 ad_calc_wq
u:r:kernel:s0 root 156 2 rot_commit_work
u:r:kernel:s0 root 157 2 mdss_dsi_event
u:r:kernel:s0 root 158 2 hdmi_tx_workq
u:r:kernel:s0 root 159 2 unblanker
u:r:kernel:s0 root 160 2 apr_driver
u:r:kernel:s0 root 161 2 pil_vote_wq
u:r:kernel:s0 root 162 2 shm_svc
u:r:kernel:s0 root 163 2 qmi_hndl0000000
u:r:kernel:s0 root 164 2 msm_ipc_router
u:r:kernel:s0 root 165 2 k_hsuart
u:r:kernel:s0 root 166 2 msm_serial_hs_0
u:r:kernel:s0 root 167 2 msm_serial_hs_0
u:r:kernel:s0 root 168 2 hwrng
u:r:kernel:s0 root 169 2 diag_real_time_
u:r:kernel:s0 root 170 2 diag_modem_data
u:r:kernel:s0 root 171 2 diag_lpass_data
u:r:kernel:s0 root 172 2 diag_wcnss_data
u:r:kernel:s0 root 173 2 diag_sensors_da
u:r:kernel:s0 root 174 2 diag_wq
u:r:kernel:s0 root 175 2 DIAG_USB_diag
u:r:kernel:s0 root 176 2 diag_cntl_wq
u:r:kernel:s0 root 177 2 diag_dci_wq
u:r:kernel:s0 root 178 2 kgsl-3d0
u:r:kernel:s0 root 179 2 kgsl-events
u:r:kernel:s0 root 180 2 governor_msm_ad
u:r:kernel:s0 root 181 2 kgsl_devfreq_wq
u:r:kernel:s0 root 203 2 spi0
u:r:kernel:s0 root 204 2 usbnet
u:r:kernel:s0 root 205 2 sharedmem_qmi_w
u:r:kernel:s0 root 206 2 qmi_hndl0000000
u:r:kernel:s0 root 207 2 kworker/u16:3
u:r:kernel:s0 root 208 2 irq/212-msm_dwc
u:r:kernel:s0 root 209 2 k_gserial
u:r:kernel:s0 root 210 2 uether
u:r:kernel:s0 root 214 2 msm_cpp_workque
u:r:kernel:s0 root 215 2 irq/506-clearpa
u:r:kernel:s0 root 216 2 therm_core:noti
u:r:kernel:s0 root 217 2 therm_core:noti
u:r:kernel:s0 root 218 2 therm_core:noti
u:r:kernel:s0 root 219 2 therm_core:noti
u:r:kernel:s0 root 220 2 therm_core:noti
u:r:kernel:s0 root 221 2 therm_core:noti
u:r:kernel:s0 root 222 2 therm_core:noti
u:r:kernel:s0 root 223 2 therm_core:noti
u:r:kernel:s0 root 224 2 therm_core:noti
u:r:kernel:s0 root 225 2 therm_core:noti
u:r:kernel:s0 root 226 2 therm_core:noti
u:r:kernel:s0 root 227 2 therm_core:noti
u:r:kernel:s0 root 228 2 therm_core:noti
u:r:kernel:s0 root 229 2 therm_core:noti
u:r:kernel:s0 root 230 2 therm_core:noti
u:r:kernel:s0 root 231 2 therm_core:noti
u:r:kernel:s0 root 232 2 therm_core:noti
u:r:kernel:s0 root 233 2 irq/216-tsens_i
u:r:kernel:s0 root 234 2 therm_core:noti
u:r:kernel:s0 root 235 2 therm_core:noti
u:r:kernel:s0 root 236 2 therm_core:noti
u:r:kernel:s0 root 237 2 therm_core:noti
u:r:kernel:s0 root 238 2 therm_core:noti
u:r:kernel:s0 root 239 2 therm_core:noti
u:r:kernel:s0 root 240 2 therm_core:noti
u:r:kernel:s0 root 241 2 dm_bufio_cache
u:r:kernel:s0 root 242 2 cfinteractive
u:r:kernel:s0 root 243 2 irq/170-f982490
u:r:kernel:s0 root 244 2 kworker/5:3
u:r:kernel:s0 root 245 2 irq/253-f98a490
u:r:kernel:s0 root 246 2 irq/501-qpnp_wl
u:r:kernel:s0 root 247 2 binder
u:r:kernel:s0 root 248 2 usb_bam_wq
u:r:kernel:s0 root 249 2 irq/224-spdm_bw
u:r:kernel:s0 root 250 2 krfcommd
u:r:kernel:s0 root 251 2 irq/606-adsp
u:r:kernel:s0 root 252 2 irq/638-modem
u:r:kernel:s0 root 253 2 msm_vidc_worker
u:r:kernel:s0 root 254 2 pm_workerq_venu
u:r:kernel:s0 root 255 2 id-polling_wq
u:r:kernel:s0 root 256 2 kworker/u16:4
u:r:kernel:s0 root 257 2 mmcqd/0
u:r:kernel:s0 root 258 2 mmcqd/0rpmb
u:r:kernel:s0 root 259 2 kworker/5:4
u:r:kernel:s0 root 260 2 kworker/4:2
u:r:kernel:s0 root 261 2 therm_core:noti
u:r:kernel:s0 root 262 2 irq/464-chg-err
u:r:kernel:s0 root 263 2 irq/9-chg-taper
u:r:kernel:s0 root 264 2 irq/10-chg-tcc-
u:r:kernel:s0 root 265 2 irq/8-chg-rechg
u:r:kernel:s0 root 266 2 irq/468-chg-p2f
u:r:kernel:s0 root 267 2 irq/469-batt-ho
u:r:kernel:s0 root 268 2 irq/11-batt-war
u:r:kernel:s0 root 269 2 irq/13-batt-coo
u:r:kernel:s0 root 270 2 irq/12-batt-col
u:r:kernel:s0 root 271 2 irq/7-batt-miss
u:r:kernel:s0 root 272 2 irq/470-batt-lo
u:r:kernel:s0 root 273 2 irq/1-usbin-uv
u:r:kernel:s0 root 274 2 irq/2-usbin-ov
u:r:kernel:s0 root 275 2 irq/3-usbin-src
u:r:kernel:s0 root 276 2 irq/4-otg-fail
u:r:kernel:s0 root 277 2 irq/5-otg-oc
u:r:kernel:s0 root 278 2 irq/6-aicl-done
u:r:kernel:s0 root 279 2 irq/472-usbid-c
u:r:kernel:s0 root 280 2 irq/473-dcin-uv
u:r:kernel:s0 root 281 2 irq/475-power-o
u:r:kernel:s0 root 282 2 irq/476-temp-sh
u:r:kernel:s0 root 283 2 irq/477-safety-
u:r:kernel:s0 root 284 2 rq_stats
u:r:kernel:s0 root 285 2 sb-1
u:r:kernel:s0 root 286 2 irq/195-ngd_sli
u:r:kernel:s0 root 287 2 ngd_rx_thread1
u:r:kernel:s0 root 288 2 ngd_notify_sl1
u:r:kernel:s0 root 289 2 k_bam_data
u:r:kernel:s0 root 290 2 f_mtp
u:r:kernel:s0 root 291 2 file-storage
u:r:kernel:s0 root 292 2 msm-core:sampli
u:r:kernel:s0 root 293 2 msm_thermal:hot
u:r:kernel:s0 root 294 2 msm_thermal:fre
u:r:kernel:s0 root 295 2 msm_thermal:the
u:r:kernel:s0 root 296 2 therm_core:noti
u:r:kernel:s0 root 297 2 therm_core:noti
u:r:kernel:s0 root 298 2 therm_core:noti
u:r:kernel:s0 root 299 2 therm_core:noti
u:r:kernel:s0 root 300 2 therm_core:noti
u:r:kernel:s0 root 301 2 therm_core:noti
u:r:kernel:s0 root 302 2 therm_core:noti
u:r:kernel:s0 root 303 2 therm_core:noti
u:r:kernel:s0 root 304 2 therm_core:noti
u:r:kernel:s0 root 305 2 boost_sync/0
u:r:kernel:s0 root 306 2 boost_sync/1
u:r:kernel:s0 root 307 2 boost_sync/2
u:r:kernel:s0 root 308 2 boost_sync/3
u:r:kernel:s0 root 309 2 boost_sync/4
u:r:kernel:s0 root 310 2 boost_sync/5
u:r:kernel:s0 root 311 2 boost_sync/6
u:r:kernel:s0 root 312 2 boost_sync/7
u:r:kernel:s0 root 313 2 kworker/4:3
u:r:kernel:s0 root 314 2 ipa_A7_svc
u:r:kernel:s0 root 315 2 qmi_hndl0000000
u:r:kernel:s0 root 316 2 clnt_req
u:r:kernel:s0 root 317 2 kworker/u16:5
u:r:kernel:s0 root 318 2 clnt_resp
u:r:kernel:s0 root 319 2 clnt_req
u:r:kernel:s0 root 320 2 wl_event_handle
u:r:kernel:s0 root 321 2 dhd_watchdog_th
u:r:ueventd:s0 root 322 1 /sbin/ueventd
u:r:kernel:s0 root 324 2 kworker/0:1H
u:r:kernel:s0 root 325 2 jbd2/mmcblk0p43
u:r:kernel:s0 root 326 2 ext4-dio-unwrit
u:r:kernel:s0 root 330 2 jbd2/mmcblk0p42
u:r:kernel:s0 root 331 2 ext4-dio-unwrit
u:r:kernel:s0 root 346 2 IPCRTR
u:r:kernel:s0 root 347 2 kworker/0:2
u:r:kernel:s0 root 348 2 adsp_IPCRTR
u:r:kernel:s0 root 349 2 kworker/0:3
u:r:kernel:s0 root 350 2 msm_slim_qmi_cl
u:r:kernel:s0 root 351 2 qmi_hndl0000000
u:r:logd:s0 logd 352 1 /system/bin/logd
u:r:healthd:s0 root 353 1 /sbin/healthd
u:r:lmkd:s0 root 354 1 /system/bin/lmkd
u:r:servicemanager:s0 system 355 1 /system/bin/servicemanager
u:r:vold:s0 root 356 1 /system/bin/vold
u:r:kernel:s0 root 357 2 kworker/3:1H
u:r:surfaceflinger:s0 system 358 1 /system/bin/surfaceflinger
u:r:tad:s0 root 359 1 /system/vendor/bin/tad_static
u:r:init:s0 nobody 360 1 /system/vendor/bin/rmt_storage
u:r:init:s0 system 361 1 /system/vendor/bin/rfs_access
u:r:kernel:s0 root 362 2 migration/6
u:r:kernel:s0 root 363 2 ksoftirqd/6
u:r:kernel:s0 root 364 2 kworker/6:0
u:r:kernel:s0 root 365 2 kworker/6:0H
u:r:kernel:s0 root 366 2 migration/7
u:r:kernel:s0 root 367 2 ksoftirqd/7
u:r:kernel:s0 root 368 2 kworker/7:0
u:r:kernel:s0 root 369 2 kworker/7:0H
u:r:kernel:s0 root 371 2 kworker/7:2
u:r:kernel:s0 root 376 2 kauditd
u:r:kernel:s0 root 379 2 kworker/2:1H
u:r:kernel:s0 root 385 2 irq/449-wcd9xxx
u:r:kernel:s0 root 386 2 kworker/6:1
u:r:kernel:s0 root 401 2 mdss_fb0
u:r:bootanim:s0 graphics 409 1 /system/bin/bootanimation
u:r:kernel:s0 root 417 2 kworker/4:1H
u:r:kernel:s0 root 418 2 kworker/5:1H
u:r:kernel:s0 root 419 2 kworker/6:1H
u:r:kernel:s0 root 420 2 kworker/7:1H
u:r:shell:s0 shell 421 1 /system/bin/sh
u:r:init:s0 radio 422 1 /system/vendor/bin/qmuxd
u:r:init:s0 root 423 1 /system/vendor/bin/netmgrd
u:r:adbd:s0 shell 426 1 /sbin/adbd
u:r:kernel:s0 root 436 2 ipawq44
u:r:kernel:s0 root 437 2 iparepwq44
u:r:kernel:s0 root 480 2 kworker/u16:2
u:r:kernel:s0 root 481 2 kworker/7:1
u:r:kernel:s0 root 482 2 kworker/4:0
u:r:kernel:s0 root 483 2 kworker/5:0
u:r:kernel:s0 root 484 2 kworker/1:2
u:r:kernel:s0 root 485 2 kworker/0:0
u:r:shell:s0 shell 492 426 ps

dl12345 said:
Anyone have any insight into why my AOSP build isn't completing the boot process? Up to the end of the attached logcat, it seems to be the same as @ChrisJ951's previously posted logcat on a build that boots correctly.
I've rebuilt multiple times after doing a make clobber, repo sync, re-apply patches, etc., but nothing seems to work. Host is Fedora 21, openjdk 1.70_79...
Click to expand...
Click to collapse
delete /system/etc/thermalmanager.xml and should boot fine.
The thermalmanager.xml file is messed up and shuts down the phone around 45C (for reference the stock firmware does it around 85C)

ChrisJ951 said:
delete /system/etc/thermalmanager.xml and should boot fine.
The thermalmanager.xml file is messed up and shuts down the phone around 45C (for reference the stock firmware does it around 85C)
Click to expand...
Click to collapse
That didn't seem to do anything unfortunately. I have, however, partially solved the problem. It appears that, for some reason I've not yet identified, the "on nonencrypted" event is not being sent by the vold daemon and as a result, the "class_start main" is not being called in init.rc. This results in a partial boot. I put a temporary hack into init.kitakami.rc to explicitly call class_start main after the "setprop vold.post_fs_data_done 1"
Code:
# Touch
mkdir /dev/socket/tfsw 0770 system system
setprop vold.post_fs_data_done 1
class_start main
# Touch
mkdir /dev/socket/tfsw 0770 system system
setprop vold.post_fs_data_done 1
class_start main
After this, the system boots.

dl12345 said:
That didn't seem to do anything unfortunately. I have, however, partially solved the problem. It appears that, for some reason I've not yet identified, the "on nonencrypted" event is not being sent by the vold daemon and as a result, the "class_start main" is not being called in init.rc. This results in a partial boot. I put a temporary hack into init.kitakami.rc to explicitly call class_start main after the "setprop vold.post_fs_data_done 1"
Code:
# Touch
mkdir /dev/socket/tfsw 0770 system system
setprop vold.post_fs_data_done 1
class_start main
# Touch
mkdir /dev/socket/tfsw 0770 system system
setprop vold.post_fs_data_done 1
class_start main
After this, the system boots.
Click to expand...
Click to collapse
Unsure why that would happen. I didn't have that issue in any of the builds I did.
Also just to confirm, does your build support SIM card support?

Problem resolved. The build guide is incomplete. Flashing the cache partition is required.
Code:
fastboot flash cache cache.img
The "on nonencrypted" event in init.rc is invoked by do_mount_all() from system/core/init/builtins.c when all partitions in fstab are mounted successfully after the mount_all directive is given init.kitakami.rc.
Not flashing the cache partition caused the mount_all to fail and therefore the event was not generated and the class_start main not called.
I confirm no baseband.

Related

[Q] I think my internal memory is toast.

So this I9000 was given to me to try and repair for a friend. Basically phone had never been hacked, modded or anything. Was stock, not even rooted. One day the phone turned off and when turned on, it shows the GT screen, the Samsung screen, then the screen goes black and the lower buttons illuminate. That's it.
So i have tried to install multiple ROM's, repartitioning, odin, CWM all of it.
The last thing i have found is a thread where someone gave instructions on how to list your device memory from shell using parted. I have done just that but i do not see my internal memory there. If i put my 512MB sd card in it, it becomes visible, the external that is. But thats it.
In CWM i cannot mount data or emmc. Nor can i format them.
Here is the output from parted. Any ideas?
~ # cd /sbin
cd /sbin
/sbin # ls -al /dev/block
ls -al /dev/block
drwxr-xr-x 3 root root 700 Mar 29 21:55 .
drwxr-xr-x 11 root root 2880 Mar 29 21:55 ..
brw------- 1 root root 7, 0 Mar 29 21:55 loop0
brw------- 1 root root 7, 1 Mar 29 21:55 loop1
brw------- 1 root root 7, 2 Mar 29 21:55 loop2
brw------- 1 root root 7, 3 Mar 29 21:55 loop3
brw------- 1 root root 7, 4 Mar 29 21:55 loop4
brw------- 1 root root 7, 5 Mar 29 21:55 loop5
brw------- 1 root root 7, 6 Mar 29 21:55 loop6
brw------- 1 root root 7, 7 Mar 29 21:55 loop7
brw------- 1 root root 31, 0 Mar 29 21:55 mtdblock0
brw------- 1 root root 31, 1 Mar 29 21:55 mtdblock1
brw------- 1 root root 31, 2 Mar 29 21:55 mtdblock2
brw------- 1 root root 31, 3 Mar 29 21:55 mtdblock3
brw------- 1 root root 31, 4 Mar 29 21:55 mtdblock4
brw-rw---- 1 radio radio 31, 5 Mar 29 21:55 mtdblock5
brw------- 1 root root 31, 6 Mar 29 21:55 mtdblock6
brw------- 1 root root 31, 7 Mar 29 21:55 mtdblock7
drwxr-xr-x 3 root root 60 Mar 29 21:55 platform
brw------- 1 root root 1, 0 Mar 29 21:55 ram0
brw------- 1 root root 1, 1 Mar 29 21:55 ram1
brw------- 1 root root 1, 10 Mar 29 21:55 ram10
brw------- 1 root root 1, 11 Mar 29 21:55 ram11
brw------- 1 root root 1, 12 Mar 29 21:55 ram12
brw------- 1 root root 1, 13 Mar 29 21:55 ram13
brw------- 1 root root 1, 14 Mar 29 21:55 ram14
brw------- 1 root root 1, 15 Mar 29 21:55 ram15
brw------- 1 root root 1, 2 Mar 29 21:55 ram2
brw------- 1 root root 1, 3 Mar 29 21:55 ram3
brw------- 1 root root 1, 4 Mar 29 21:55 ram4
brw------- 1 root root 1, 5 Mar 29 21:55 ram5
brw------- 1 root root 1, 6 Mar 29 21:55 ram6
brw------- 1 root root 1, 7 Mar 29 21:55 ram7
brw------- 1 root root 1, 8 Mar 29 21:55 ram8
brw------- 1 root root 1, 9 Mar 29 21:55 ram9
Also, i tried using a CM7 rom last, so i am currently looping the Cm7 skateboard guy. I have the logcat of that available if you think it may help, but it just list a whole bunch of java failures and alike and then does it all over again.
I'm sure my GT-I9000 Galaxy S came with a 2 year Warranty. Would be well worth checking whether that phone was 1yr or 2yrs, as all 2yr warranties should still be valid, as they are all less than two years old still.
Hope you get it sorted.
---------- Post added at 12:04 PM ---------- Previous post was at 12:00 PM ----------
Just realised you are in Canada, does that mean this is a I9000M?... as I know they had major memory issues. There is a thread about it here somewhere. Not sure what the outcome was, but it was a known defect. Maybe you could convince Samsung to fix it for free (even if it is out of Warranty)?
Ya i have been getting snippits of info on the i9000m internal sd problem but can find any hard info on it.
Basically there was a huge batch of them with onboard memory that would fail when you upgraded to GB....or eventually on their own.
I had one, a friend of mine had one...
If it was still on warranty they would replace it outright for you but I'm guessing if you got it in Canada (Bell?) It's way past warranty.
You could try flashing an Claire or froyo ROM and see if you have any luck there. Chances are though that it's as good as dead.
Sent from my GT-I9000 using Tapatalk 2 Beta-4
Yes, its a Bell I9000M.
I dont see a date of manufacture on it though. I guess i will have to call Samsung to verify warranty then?
Date of manufacture should be on the battery. I got mine on release day and it still works great after being flashed dozens of times.
As far as I remember it was a later batch that had a corrupt boot loader. I was weary of flashing due to all the dying I9000M's and followed the discussions closely. The second GB update was supposed to have fixed it.
Sent from my GT - I9000M running Team Hacksung's ICS port.

SOLVED : neither CWM nor ODIN helps. bricked!

Hello mates,
I have a common but also weird case with note n7000.
after wiping data without abyss kernel, i stuck at boot screen then tried to flash GB with odin, it also stuck at last quarter, tried to flash ICS with odin but same as GB.
now i am able to flash kernels with ODIN and i am able to boot in recovery.
i go in to recovery, flash abyss 4.2 kernel and reboot in recovery then make all the wipes and even flash a custom rom but when i reboot the device, nothing happens. again stuck in boot screen and no further process.
i am really desperate about it now. as i bought it from ebay, i dont have the receipt of it. only the box, accs. and some papers(warranty and guide).
can anyone suggest me anything in this case? is there anything i can do or its done for good?
and in the case of superbrick, can anyone from germany tell me whether i can claim warrany without receipt(quittung, kassenbon, kaufbeleg) ?
any reply, any attempt of help will be highly appreciated.
thanks in advance
SOLUTION: i followed the link posted by Aluyi
http://forum.xda-developers.com/showthread.php?t=1667886
downloaded the rar file with many modified .pit files and flashed Rooted_Stock_Odex_N7000XXLC1(ICS XXLPY works also) with the downloaded .pit file (N7000_16GB_Q1_20110914-patched-standard) and IT DID WORK!
if u check the given link u will understand what was causing that problem.
after this process i did save the device from being bricked but sacrified 3 gb of internal sd. so it shows only 8.3 gb now.
try pc odin to flash.
mrbat said:
Hello mates,
I have a common but also weird case with note n7000.
after wiping data without abyss kernel, i stuck at boot screen then tried to flash GB with odin, it also stuck at last quarter, tried to flash ICS with odin but same as GB.
now i am able to flash kernels with ODIN and i am able to boot in recovery.
i go in to recovery, flash abyss 4.2 kernel and reboot in recovery then make all the wipes and even flash a custom rom but when i reboot the device, nothing happens. again stuck in boot screen and no further process.
i am really desperate about it now. as i bought it from ebay, i dont have the receipt of it. only the box, accs. and some papers(warranty and guide).
can anyone suggest me anything in this case? is there anything i can do or its done for good?
and in the case of superbrick, can anyone from germany tell me whether i can claim warrany without receipt(quittung, kassenbon, kaufbeleg) ?
any reply, any attempt of help will be highly appreciated.
thanks in advance
Click to expand...
Click to collapse
Try This Method;
1. Take Off The Phone And Wait A Minute Or Two,
2. Remove The Battery And Wait 5 Minutes,
3. Boot In Recovery And Do All 3 Wipes.
Alles Wird Gut, Happened To Me Yesterday, Please Do Holla Back If It Did Work Fine For You.
try pc odin to flash.
Click to expand...
Click to collapse
yea tried maybe 30 times. but as i mentioned above, it sticks at the last quarter of the installation.
Aluyi said:
Try This Method;
1. Take Off The Phone And Wait A Minute Or Two,
2. Remove The Battery And Wait 5 Minutes,
3. Boot In Recovery And Do All 3 Wipes.
Alles Wird Gut, Happened To Me Yesterday, Please Do Holla Back If It Did Work Fine For You.
Click to expand...
Click to collapse
i tried it. waited more than 5 minutes then booted in recovery, did wipes and still the same thing.
wiping cache and dalvik cache works normal but wiping data takes too long (around 4 mins)
Just wondering did u wiped system in recovery ?
sahilarora2003 said:
Just wondering did u wiped system in recovery ?
Click to expand...
Click to collapse
yes mate, i wiped everything in the "mounts and storage"
even sdcard and mmc. but still no success
mrbat said:
i tried it. waited more than 5 minutes then booted in recovery, did wipes and still the same thing.
wiping cache and dalvik cache works normal but wiping data takes too long (around 4 mins)
Click to expand...
Click to collapse
Maybe You Should Try This Method When No Other Method Helps You Out. http://forum.xda-developers.com/showthread.php?t=1667886&highlight=boot+loop.
What You Got To Lose Anyway? As It Stands Right Now You F..ked, So Give It A Try I´ll Do It.
Aluyi said:
Maybe You Should Try This Method When No Other Method Helps You Out. http://forum.xda-developers.com/showthread.php?t=1667886&highlight=boot+loop.
What You Got To Lose Anyway? As It Stands Right Now You F..ked, So Give It A Try I´ll Do It.
Click to expand...
Click to collapse
yea i got nothing to lose now, i surely will give a shot.
but here is the log file i got from CWM if anyone can get anything from it :
Code:
Starting recovery on Sat Jan 1 20:03:29 2000
framebuffer: fd 4 (800 x 1280)
ClockworkMod Recovery v5.8.1.5
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc /dev/block/mmcblk0p5 (null) 0
2 /efs ext4 /dev/block/mmcblk0p1 (null) 0
3 /cache ext4 /dev/block/mmcblk0p7 (null) 0
4 /system ext4 /dev/block/mmcblk0p9 (null) 0
5 /data ext4 /dev/block/mmcblk0p10 (null) 0
6 /sdcard vfat /dev/block/mmcblk1p1 (null) 0
7 /emmc vfat /dev/block/mmcblk0p11 (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
I:Processing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "recovery"
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=0
ro.factorytest=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=smdkc210
ro.revision=8
ro.emmc=0
dpm.allowpolicy=1
init.svc.recovery=running
init.svc.adbd=stopping
ro.build.product=smdkc210
ro.product.device=smdkc210
ro.radio.noril=yes
status.battery.state=Slow
status.battery.level=5
status.battery.level_raw=50
status.battery.level_scale=9
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
fd: 17
ev: 1 102 0
fd: 17
ev: 0 0 0
fd: 17
ev: 1 115 0
fd: 17
ev: 0 0 0
Starting recovery on Sat Jan 1 20:03:33 2000
framebuffer: fd 4 (800 x 1280)
ClockworkMod Recovery v5.8.1.5
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc /dev/block/mmcblk0p5 (null) 0
2 /efs ext4 /dev/block/mmcblk0p1 (null) 0
3 /cache ext4 /dev/block/mmcblk0p7 (null) 0
4 /system ext4 /dev/block/mmcblk0p9 (null) 0
5 /data ext4 /dev/block/mmcblk0p10 (null) 0
6 /sdcard vfat /dev/block/mmcblk1p1 (null) 0
7 /emmc vfat /dev/block/mmcblk0p11 (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
I:Processing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "recovery"
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=0
ro.factorytest=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=smdkc210
ro.revision=8
ro.emmc=0
dpm.allowpolicy=1
init.svc.recovery=running
init.svc.adbd=stopping
ro.build.product=smdkc210
ro.product.device=smdkc210
ro.radio.noril=yes
status.battery.state=Slow
status.battery.level=5
status.battery.level_raw=50
status.battery.level_scale=9
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
fd: 16
ev: 3 53 198
fd: 16
ev: 3 54 532
fd: 16
ev: 3 48 44
fd: 16
ev: 3 50 4
fd: 16
ev: 3 57 0
fd: 16
ev: 3 59 16
fd: 16
ev: 3 60 5
fd: 16
ev: 0 2 0
event: 198 532
down
fd: 16
ev: 0 0 0
fd: 16
ev: 3 53 198
fd: 16
ev: 3 54 532
fd: 16
ev: 3 48 0
fd: 16
ev: 3 50 4
fd: 16
ev: 3 57 0
fd: 16
ev: 3 59 16
fd: 16
ev: 3 60 5
fd: 16
ev: 0 2 0
event: 198 532
event: 198 532
up
fd: 16
ev: 0 0 0
failed to open /sys/class/android_usb/android0/state: No such file or directory
fd: 16
ev: 3 53 201
fd: 16
ev: 3 54 590
fd: 16
ev: 3 48 45
fd: 16
ev: 3 50 4
fd: 16
ev: 3 57 0
fd: 16
ev: 3 59 16
fd: 16
ev: 3 60 5
fd: 16
ev: 0 2 0
event: 201 590
down
fd: 16
ev: 0 0 0
fd: 16
ev: 3 53 201
fd: 16
ev: 3 54 590
fd: 16
ev: 3 48 0
fd: 16
ev: 3 50 4
fd: 16
ev: 3 57 0
fd: 16
ev: 3 59 16
fd: 16
ev: 3 60 5
fd: 16
ev: 0 2 0
event: 201 590
event: 201 590
up
fd: 16
ev: 0 0 0
failed to open /sys/class/android_usb/android0/state: No such file or directory
Fixing permissions...
sh: fix_permissions: not found
Done!
fd: 16
ev: 3 53 258
fd: 16
ev: 3 54 314
fd: 16
ev: 3 48 53
fd: 16
ev: 3 50 5
fd: 16
ev: 3 57 0
fd: 16
ev: 3 59 0
fd: 16
ev: 3 60 7
fd: 16
ev: 0 2 0
event: 258 314
down
fd: 16
ev: 0 0 0
fd: 16
ev: 3 53 258
fd: 16
ev: 3 54 314
fd: 16
ev: 3 48 0
fd: 16
ev: 3 50 4
fd: 16
ev: 3 57 0
fd: 16
ev: 3 59 0
fd: 16
ev: 3 60 7
fd: 16
ev: 0 2 0
event: 258 314
event: 258 314
up
fd: 16
ev: 0 0 0
failed to open /sys/class/android_usb/android0/state: No such file or directory
Click to expand...
Click to collapse
mrbat said:
yea i got nothing to lose now, i surely will give a shot.
but here is the log file i got from CWM if anyone can get anything from it :
Click to expand...
Click to collapse
Take Your Time And Just Follow The Directions, Download The Files And Copy/Paste The Codes. Again Alles Wird Gut. Believe Me It Happened To Me Many Times Before.

Cannot re-flash Teclast X98 Air II 64GB (HG9M)

I'm having problems with my X98 Air II 64GB (HG9M)
I removed the Windows installation - I just didn't use it, so decided to let Android use the whole device - However, the Windows partition was not visible from Android.
The device has been freezing and various apps crashing so I decided to completely overhaul.
I updated the BIOS to DROIDBOOT: VERSION 2.0 (Android Only Version) and then wanted to re-flash the ROM with one of the Mirek190 Lollipop versions. HOWEVER, this is where my real problems start.
For some reason the device will not factory reset - It just reboots to android.
I cannot get in to REBOOT DROIDBOOT or RECOVERY - I can see the options but the following error is visible in the options screen:
----------------------------------
FASTBOOT INIT...
E:installer device ignored
FASTBOOT CMD WAITING...
E:Failed to mount device '/dev/block/sda1' as installer partition using fs_type 'vfat'
ition using fs_type 'vfat'
E:installer device ignored
E:installer device ignored
E:No valid installer medium found.
Could not open /sys/devices/virtual/backlight
------------------------------------
I can access the device from ADB (on my Mac) via terminal and can create new partitions using FASTBOOT from there also.
What I want to do is completely start from scratch - repartition the whole 64gb device and flash to android.
Any advice on how I can do that with no access to DROIDBOOT?
It feels like it should be simple, but for some reason it seems to be impossible.
Thank you!
**UPDATED**
Here are the outputs of various directories on the device:
[email protected]:/ # ls -all
drwxr-xr-x root root 2016-12-07 14:46 acct
drwxrwx--- system cache 2016-12-06 10:43 cache
lrwxrwxrwx root root 1970-01-01 01:00 charger -> /sbin/healthd
drwxr-xr-x root root 2016-09-10 12:34 config
lrwxrwxrwx root root 2016-12-07 14:46 d -> /sys/kernel/debug
drwxrwx--x system system 2016-12-07 14:47 data
-rw-r--r-- root root 354 1970-01-01 01:00 default.prop
drwxr-xr-x root root 2016-12-07 15:12 dev
lrwxrwxrwx root root 2016-12-07 14:46 etc -> /system/etc
drwxr-xr-x root root 2016-09-10 12:31 factory
-rw-r--r-- root root 14913 1970-01-01 01:00 file_contexts
-rw-r--r-- root root 938 1970-01-01 01:00 fstab
-rw-r--r-- root root 938 1970-01-01 01:00 fstab.anzhen4_mrd7
-rw-r--r-- root root 322 1970-01-01 01:00 fstab.charger.anzhen4_mrd7
-rw-r--r-- root root 322 1970-01-01 01:00 fstab.ramconsole.anzhen4_mrd7
-rwxr-x--- root root 645284 1970-01-01 01:00 init
-rwxr-x--- root root 15615 1970-01-01 01:00 init.anzhen4_mrd7.rc
-rwxr-x--- root root 21988 1970-01-01 01:00 init.aosp.rc
-rwxr-x--- root root 2021 1970-01-01 01:00 init.avc.rc
-rwxr-x--- root root 712 1970-01-01 01:00 init.baylake.sh
-rwxr-x--- root root 558 1970-01-01 01:00 init.bt.rc
-rwxr-x--- root root 956 1970-01-01 01:00 init.bt.vendor.rc
-rwxr-x--- root root 8571 1970-01-01 01:00 init.common.rc
-rwxr-x--- root root 5185 1970-01-01 01:00 init.debug.rc
-rwxr-x--- root root 278 1970-01-01 01:00 init.diag.rc
-rwxr-x--- root root 993 1970-01-01 01:00 init.dump.rc
-rwxr-x--- root root 1065 1970-01-01 01:00 init.environ.rc
-rwxr-x--- root root 141 1970-01-01 01:00 init.extra.rc
-rwxr-x--- root root 227 1970-01-01 01:00 init.firmware.rc
-rwxr-x--- root root 1604 1970-01-01 01:00 init.gps.rc
-rwxr-x--- root root 2939 1970-01-01 01:00 init.modem.rc
-rwxr-x--- root root 976 1970-01-01 01:00 init.net.eth0.sh
-rwxr-x--- root root 477 1970-01-01 01:00 init.platform.gengfx.rc
-rwxr-x--- root root 4713 1970-01-01 01:00 init.platform.usb.rc
-rwxr-x--- root root 1272 1970-01-01 01:00 init.rc
-rwxr-x--- root root 1349 1970-01-01 01:00 init.recovery.anzhen4_mrd7.rc
-rwxr-x--- root root 775 1970-01-01 01:00 init.sensor.rc
-rwxr-x--- root root 1927 1970-01-01 01:00 init.trace.rc
-rwxr-x--- root root 3885 1970-01-01 01:00 init.usb.rc
-rwxr-x--- root root 419 1970-01-01 01:00 init.watchdog.rc
-rwxr-x--- root root 357 1970-01-01 01:00 init.watchdog.sh
-rwxr-x--- root root 976 1970-01-01 01:00 init.wifi.rc
-rwxr-x--- root root 1078 1970-01-01 01:00 init.wifi.vendor.rc
-rwxr-x--- root root 301 1970-01-01 01:00 init.zygote32.rc
-rw-r--r-- root root 351 1970-01-01 01:00 intel_prop.cfg
drwxr-xr-x root root 1970-01-01 01:00 lib
drwxrwx--- system log 2016-12-07 14:46 logs
drwxrwxr-x media media 2016-12-07 14:46 media
drwxrwxr-x root system 2016-12-07 14:46 mnt
dr-xr-xr-x root root 2016-12-07 14:46 proc
-rw-r--r-- root root 2614 1970-01-01 01:00 property_contexts
-rw-r--r-- root root 42 1970-01-01 01:00 props.platform.rc
-rw-r--r-- root root 231 1970-01-01 01:00 props.rc
drwxr-xr-x root root 1970-01-01 01:00 res
-rw-r--r-- root root 240 1970-01-01 01:00 rfkill_bt.sh
drwx------ root root 2015-07-20 04:28 root
drwxr-x--- root root 1970-01-01 01:00 sbin
lrwxrwxrwx root root 2016-12-07 14:46 sdcard -> /storage/emulated/legacy
-rw-r--r-- root root 534 1970-01-01 01:00 seapp_contexts
-rw-r--r-- root root 80 1970-01-01 01:00 selinux_version
-rw-r--r-- root root 136700 1970-01-01 01:00 sepolicy
-rw-r--r-- root root 10344 1970-01-01 01:00 service_contexts
drwxr-x--x root sdcard_r 2016-12-07 14:46 storage
dr-xr-xr-x root root 2016-12-07 14:46 sys
drwxr-xr-x root root 1970-01-01 01:00 system
drwxr-xr-x root root 2016-12-07 14:46 tmp-mksh
-rw-r--r-- root root 3181 1970-01-01 01:00 ueventd.anzhen4_mrd7.rc
-rw-r--r-- root root 629 1970-01-01 01:00 ueventd.modules.blacklist
-rw-r--r-- root root 4688 1970-01-01 01:00 ueventd.rc
lrwxrwxrwx root root 2016-12-07 14:46 vendor -> /system/vendor
[email protected]:/data # ls -all
drwxr-x--- root root 2016-12-07 07:20 .android
-rw------- root root 2 2016-09-10 12:34 .layout_version
-rw------- root root 976 2016-12-07 14:47 ArchiDroidInit.log
drwxrwxr-x system system 2016-12-07 15:01 anr
drwxrwx--x system system 2016-12-07 07:15 app
drwx------ root root 2016-09-10 12:34 app-asec
drwxrwx--x system system 2016-09-10 19:23 app-lib
drwxrwx--x system system 2016-09-10 12:34 app-private
drwx------ system system 2016-12-07 14:47 backup
lrwxrwxrwx root root 2016-09-10 12:34 bugreports -> /data/data/com.android.shell/files/bugreports
drwxrwx--x root root 2016-09-10 12:34 dalvik-cache
drwxrwx--x system system 2016-12-07 07:02 data
drwxr-xr-x root root 2016-12-06 08:01 data-lib
drwxr-x--- root log 2016-09-10 12:34 dontpanic
drwxrwx--- drm drm 2016-09-10 12:36 drm
drwxrwx--- gps system 2016-12-07 14:46 gps
drwx------ media media 2016-12-07 14:46 hdcp
drwxr-x--x root root 2016-12-07 07:42 local
drwxrwx--- root root 1970-01-01 01:00 lost+found
drwxrwx--- media_rw media_rw 2016-09-10 12:36 media
drwxrwx--- mediadrm mediadrm 2016-09-10 12:34 mediadrm
-rwxrwxrwx root root 2 2016-09-10 12:36 mirek190.02
drwxrwx--t system misc 2016-09-10 12:34 misc
drwx------ root root 2016-12-07 14:47 property
drwxrwx--x system system 2016-09-10 12:34 resource-cache
drwx--x--x system system 2016-09-10 12:34 security
drwxrwxr-x system system 2016-12-07 15:17 system
drwxr-xr-x system system 2016-12-07 07:21 tombstones
drwx--x--x system system 2016-09-10 12:34 user
[email protected]:/dev # ls -all
-rw------- root root 0 2016-12-07 14:46 .app_process_lock
---------- root root 0 2016-12-07 14:46 .coldboot_done
-rw------- root root 0 2016-12-07 14:46 .su.d
-r--r--r-- root root 131072 2016-12-07 14:48 __properties__
crw-rw-r-- system radio 10, 51 2016-12-07 14:46 alarm
crw-rw-rw- root root 10, 56 2016-12-07 14:46 ashmem
lrwxrwxrwx root root 2016-12-07 14:46 bcu -> /sys/bus/platform/devices/crystal_cove_bcu/msic_voltage
crw-rw-rw- root root 10, 57 2016-12-07 14:46 binder
drwxr-xr-x root root 2016-12-07 14:46 block
drwxr-xr-x root root 2016-12-07 14:46 bus
lrwxrwxrwx root root 2016-12-07 14:46 card0 -> /dev/dri/card0
crw------- root root 5, 1 2016-12-07 14:46 console
crw------- root root 203, 0 2016-12-07 14:46 cpu0
crw------- root root 203, 1 2016-12-07 14:46 cpu1
crw------- root root 203, 2 2016-12-07 14:46 cpu2
crw------- root root 203, 3 2016-12-07 14:46 cpu3
crw------- root root 10, 47 2016-12-07 14:46 cpu_dma_latency
crw------- root root 10, 44 2016-12-07 14:46 cpu_freq_min
drwxr-xr-x system system 2016-12-07 14:46 cpuctl
crw------- root root 10, 236 2016-12-07 14:46 device-mapper
drwxr-xr-x root root 2016-12-07 14:46 dri
lrwxrwxrwx root root 2016-12-07 14:46 fg -> /dev/max170xx
drwxrwx--- root system 2016-12-07 14:48 fscklogs
crw-rw-rw- root root 1, 7 2016-12-07 14:46 full
crw------- root root 10, 229 2016-12-07 14:46 fuse
drwxrwx--- gps system 2016-12-07 14:46 gps
drwxr-xr-x root root 2016-12-07 14:46 graphics
crw------- root root 89, 1 2016-12-07 14:46 i2c-1
crw------- root root 89, 11 2016-12-07 14:46 i2c-11
crw------- root root 89, 12 2016-12-07 14:46 i2c-12
crw------- root root 89, 13 2016-12-07 14:46 i2c-13
crw------- root root 89, 14 2016-12-07 14:46 i2c-14
crw------- root root 89, 15 2016-12-07 14:46 i2c-15
crw------- root root 89, 16 2016-12-07 14:46 i2c-16
crw------- root root 89, 17 2016-12-07 14:46 i2c-17
crw------- root root 89, 2 2016-12-07 14:46 i2c-2
crw------- root root 89, 3 2016-12-07 14:46 i2c-3
crw------- root root 89, 4 2016-12-07 14:46 i2c-4
crw------- system system 89, 5 2016-12-07 14:46 i2c-5
crw------- root root 249, 0 2016-12-07 14:46 iio:device0
drwxr-xr-x root root 2016-12-07 14:46 input
crwxrwx--- system system 10, 61 2016-12-07 14:46 intel_fg
crw------- media media 10, 49 2016-12-07 14:46 intel_sst_ctrl
crw------- root root 10, 58 2016-12-07 14:46 keychord
drwxrwx--x u0_a72 u0_a72 2016-12-07 14:47 kingroot.req.cache
crw------- root root 1, 2 2016-12-07 14:46 kmem
crw------- root root 1, 11 2016-12-07 14:46 kmsg
-rw-r----- root root 32 2016-12-07 14:47 kulck
drwxr-xr-x root root 2016-12-07 14:46 log
crw------- root root 10, 237 2016-12-07 14:46 loop-control
crw------- root root 10, 227 2016-12-07 14:46 mcelog
crw-rw---- root radio 242, 0 2016-12-07 14:46 mdm_ctrl0
crw-rw---- root camera 253, 0 2016-12-07 14:46 media0
crw-rw---- system system 10, 60 2016-12-07 14:46 mei
crw-rw---- system system 10, 59 2016-12-07 14:46 meimm
crw------- root root 1, 1 2016-12-07 14:46 mem
drwx------ root system 2016-12-07 14:46 memcg
crw-r----- root diag 202, 0 2016-12-07 14:46 msr0
crw-r----- root diag 202, 1 2016-12-07 14:46 msr1
crw-r----- root diag 202, 2 2016-12-07 14:46 msr2
crw-r----- root diag 202, 3 2016-12-07 14:46 msr3
crw-rw---- root mtp 10, 43 2016-12-07 14:46 mtp_usb
crw------- root root 10, 46 2016-12-07 14:46 network_latency
crw------- root root 10, 45 2016-12-07 14:46 network_throughput
crw-rw-rw- root root 1, 3 2016-12-07 14:46 null
crw------- root root 10, 144 2016-12-07 14:46 nvram
crw------- root root 1, 4 2016-12-07 14:46 port
crw-rw---- radio vpn 108, 0 2016-12-07 14:46 ppp
crw-rw-rw- root root 5, 2 2016-12-07 15:17 ptmx
drwxr-xr-x root root 2016-12-07 14:46 pts
crw-rw-rw- root root 1, 8 2016-12-07 14:46 random
crw-rw---- bluetooth bluetooth 10, 62 2016-12-07 14:46 rfkill
-rwxr-xr-x root root 395004 2016-12-07 14:46 rt.sh
crw-r----- system system 254, 0 2016-12-07 14:46 rtc0
drwxr-xr-x root root 2016-12-07 14:46 snd
drwxr-xr-x root root 2016-12-07 14:47 socket
-rw------- root root 0 2016-12-07 15:12 startupk23784
-rw------- root root 0 2016-12-07 15:00 startupk31803
-rw------- root root 0 2016-12-07 14:46 startupk641
crw-rw---- system system 10, 50 2016-12-07 14:46 sw_sync
crw-rw-rw- root root 5, 0 2016-12-07 14:46 tty
crw-rw---- root system 4, 0 2016-12-07 14:46 tty0
crw------- root root 4, 1 2016-12-07 14:46 tty1
crw------- root root 4, 10 2016-12-07 14:46 tty10
crw------- root root 4, 11 2016-12-07 14:46 tty11
crw------- root root 4, 12 2016-12-07 14:46 tty12
crw------- root root 4, 13 2016-12-07 14:46 tty13
crw------- root root 4, 14 2016-12-07 14:46 tty14
crw------- root root 4, 15 2016-12-07 14:46 tty15
crw------- root root 4, 16 2016-12-07 14:46 tty16
crw------- root root 4, 17 2016-12-07 14:46 tty17
crw------- root root 4, 18 2016-12-07 14:46 tty18
crw------- root root 4, 19 2016-12-07 14:46 tty19
crw------- root root 4, 2 2016-12-07 14:46 tty2
crw------- root root 4, 20 2016-12-07 14:46 tty20
crw------- root root 4, 21 2016-12-07 14:46 tty21
crw------- root root 4, 22 2016-12-07 14:46 tty22
crw------- root root 4, 23 2016-12-07 14:46 tty23
crw------- root root 4, 24 2016-12-07 14:46 tty24
crw------- root root 4, 25 2016-12-07 14:46 tty25
crw------- root root 4, 26 2016-12-07 14:46 tty26
crw------- root root 4, 27 2016-12-07 14:46 tty27
crw------- root root 4, 28 2016-12-07 14:46 tty28
crw------- root root 4, 29 2016-12-07 14:46 tty29
crw------- root root 4, 3 2016-12-07 14:46 tty3
crw------- root root 4, 30 2016-12-07 14:46 tty30
crw------- root root 4, 31 2016-12-07 14:46 tty31
crw------- root root 4, 32 2016-12-07 14:46 tty32
crw------- root root 4, 33 2016-12-07 14:46 tty33
crw------- root root 4, 34 2016-12-07 14:46 tty34
crw------- root root 4, 35 2016-12-07 14:46 tty35
crw------- root root 4, 36 2016-12-07 14:46 tty36
crw------- root root 4, 37 2016-12-07 14:46 tty37
crw------- root root 4, 38 2016-12-07 14:46 tty38
crw------- root root 4, 39 2016-12-07 14:46 tty39
crw------- root root 4, 4 2016-12-07 14:46 tty4
crw------- root root 4, 40 2016-12-07 14:46 tty40
crw------- root root 4, 41 2016-12-07 14:46 tty41
crw------- root root 4, 42 2016-12-07 14:46 tty42
crw------- root root 4, 43 2016-12-07 14:46 tty43
crw------- root root 4, 44 2016-12-07 14:46 tty44
crw------- root root 4, 45 2016-12-07 14:46 tty45
crw------- root root 4, 46 2016-12-07 14:46 tty46
crw------- root root 4, 47 2016-12-07 14:46 tty47
crw------- root root 4, 48 2016-12-07 14:46 tty48
crw------- root root 4, 49 2016-12-07 14:46 tty49
crw------- root root 4, 5 2016-12-07 14:46 tty5
crw------- root root 4, 50 2016-12-07 14:46 tty50
crw------- root root 4, 51 2016-12-07 14:46 tty51
crw------- root root 4, 52 2016-12-07 14:46 tty52
crw------- root root 4, 53 2016-12-07 14:46 tty53
crw------- root root 4, 54 2016-12-07 14:46 tty54
crw------- root root 4, 55 2016-12-07 14:46 tty55
crw------- root root 4, 56 2016-12-07 14:46 tty56
crw------- root root 4, 57 2016-12-07 14:46 tty57
crw------- root root 4, 58 2016-12-07 14:46 tty58
crw------- root root 4, 59 2016-12-07 14:46 tty59
crw------- root root 4, 6 2016-12-07 14:46 tty6
crw------- root root 4, 60 2016-12-07 14:46 tty60
crw------- root root 4, 61 2016-12-07 14:46 tty61
crw------- root root 4, 62 2016-12-07 14:46 tty62
crw------- root root 4, 63 2016-12-07 14:46 tty63
crw------- root root 4, 7 2016-12-07 14:46 tty7
crw------- root root 4, 8 2016-12-07 14:46 tty8
crw------- root root 4, 9 2016-12-07 14:46 tty9
crw-rw---- root radio 245, 0 2016-12-07 14:46 ttyGS0
crw------- root root 245, 1 2016-12-07 14:46 ttyGS1
crw------- root root 245, 2 2016-12-07 14:46 ttyGS2
crw------- root root 245, 3 2016-12-07 14:46 ttyGS3
crw-rw---- bluetooth net_bt_stack 4, 128 2016-12-07 15:04 ttyMFD0
crw-rw---- gps gps 4, 129 2016-12-07 14:46 ttyMFD1
crw------- root root 4, 64 2016-12-07 14:46 ttyS0
crw-rw---- bluetooth bluetooth 4, 65 2016-12-07 14:46 ttyS1
crw------- root root 4, 66 2016-12-07 14:46 ttyS2
crw------- root root 4, 67 2016-12-07 14:46 ttyS3
crw-rw---- system vpn 10, 200 2016-12-07 14:46 tun
crw-rw---- system net_bt_stack 10, 239 2016-12-07 14:46 uhid
crw-rw---- system net_bt_stack 10, 223 2016-12-07 14:46 uinput
crw-rw-rw- root root 1, 9 2016-12-07 14:46 urandom
drwxrwx--- shell shell 2016-12-07 14:46 usb-ffs
crw-rw---- root usb 10, 42 2016-12-07 14:46 usb_accessory
crw------- root root 10, 41 2016-12-07 14:46 usb_dvc_dfx
crw------- root root 10, 40 2016-12-07 14:46 usb_dvc_trace
crw-rw---- root camera 81, 9 2016-12-07 14:46 v4l-subdev0
crw-rw---- root camera 81, 10 2016-12-07 14:46 v4l-subdev1
crw-rw---- root camera 81, 11 2016-12-07 14:46 v4l-subdev2
crw-rw---- root camera 81, 12 2016-12-07 14:46 v4l-subdev3
crw-rw---- root camera 81, 13 2016-12-07 14:46 v4l-subdev4
crw-rw---- root camera 81, 14 2016-12-07 14:46 v4l-subdev5
crw-rw---- root camera 81, 15 2016-12-07 14:46 v4l-subdev6
crw-rw---- root camera 81, 16 2016-12-07 14:46 v4l-subdev7
crw-rw---- root camera 81, 17 2016-12-07 14:46 v4l-subdev8
crw------- root root 7, 0 2016-12-07 14:46 vcs
crw------- root root 7, 1 2016-12-07 14:46 vcs1
crw------- root root 7, 128 2016-12-07 14:46 vcsa
crw------- root root 7, 129 2016-12-07 14:46 vcsa1
crw------- root root 10, 63 2016-12-07 14:46 vga_arbiter
crw-rw---- root camera 81, 0 2016-12-07 14:46 video0
crw-rw---- root camera 81, 1 2016-12-07 14:46 video1
crw-rw---- root camera 81, 2 2016-12-07 14:46 video2
crw-rw---- root camera 81, 3 2016-12-07 14:46 video3
crw-rw---- root camera 81, 4 2016-12-07 14:46 video4
crw-rw---- root camera 81, 5 2016-12-07 14:46 video5
crw-rw---- root camera 81, 6 2016-12-07 14:46 video6
crw-rw---- root camera 81, 7 2016-12-07 14:46 video7
crw-rw---- root camera 81, 8 2016-12-07 14:46 video8
crw------- root root 10, 130 2016-12-07 14:46 watchdog
crw-r--r-- root root 10, 48 2016-12-07 14:46 xt_qtaguid
crw-rw-rw- root root 1, 5 2016-12-07 14:46 zero
[email protected]:/dev/block # ls -all
lrwxrwxrwx root root 2016-12-07 14:46 by-name -> /dev/block/platform/80860F14:00/by-name
brw------- root root 7, 0 2016-12-07 14:46 loop0
brw------- root root 7, 1 2016-12-07 14:46 loop1
brw------- root root 7, 2 2016-12-07 14:46 loop2
brw------- root root 7, 3 2016-12-07 14:46 loop3
brw------- root root 7, 4 2016-12-07 14:46 loop4
brw------- root root 7, 5 2016-12-07 14:46 loop5
brw------- root root 7, 6 2016-12-07 14:46 loop6
brw------- root root 7, 7 2016-12-07 14:46 loop7
brw------- root root 179, 0 2016-12-07 14:46 mmcblk0
brw------- root root 179, 1 2016-12-07 14:46 mmcblk0p1
brw------- root root 179, 10 2016-12-07 14:46 mmcblk0p10
brw------- root root 179, 11 2016-12-07 14:46 mmcblk0p11
brw------- root root 179, 12 2016-12-07 14:46 mmcblk0p12
brw------- root root 179, 13 2016-12-07 14:46 mmcblk0p13
brw------- root root 179, 14 2016-12-07 14:46 mmcblk0p14
brw------- root root 179, 15 2016-12-07 14:46 mmcblk0p15
brw------- root root 179, 2 2016-12-07 14:46 mmcblk0p2
brw------- root root 179, 3 2016-12-07 14:46 mmcblk0p3
brw------- root root 179, 4 2016-12-07 14:46 mmcblk0p4
brw------- root root 179, 5 2016-12-07 14:46 mmcblk0p5
brw------- root root 179, 6 2016-12-07 14:46 mmcblk0p6
brw------- root root 179, 7 2016-12-07 14:46 mmcblk0p7
brw------- root root 179, 8 2016-12-07 14:46 mmcblk0p8
brw------- root root 179, 9 2016-12-07 14:46 mmcblk0p9
drwxr-xr-x root root 2016-12-07 14:46 platform
brw------- root root 1, 0 2016-12-07 14:46 ram0
brw------- root root 1, 1 2016-12-07 14:46 ram1
brw------- root root 1, 10 2016-12-07 14:46 ram10
brw------- root root 1, 11 2016-12-07 14:46 ram11
brw------- root root 1, 12 2016-12-07 14:46 ram12
brw------- root root 1, 13 2016-12-07 14:46 ram13
brw------- root root 1, 14 2016-12-07 14:46 ram14
brw------- root root 1, 15 2016-12-07 14:46 ram15
brw------- root root 1, 2 2016-12-07 14:46 ram2
brw------- root root 1, 3 2016-12-07 14:46 ram3
brw------- root root 1, 4 2016-12-07 14:46 ram4
brw------- root root 1, 5 2016-12-07 14:46 ram5
brw------- root root 1, 6 2016-12-07 14:46 ram6
brw------- root root 1, 7 2016-12-07 14:46 ram7
brw------- root root 1, 8 2016-12-07 14:46 ram8
brw------- root root 1, 9 2016-12-07 14:46 ram9
drwx------ root root 2016-12-07 14:46 vold
[email protected]:/dev/block/platform/80860F14:00/by-name # ls -all
lrwxrwxrwx root root 2016-12-07 14:46 ESP -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2016-12-07 14:46 boot -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2016-12-07 14:46 cache -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2016-12-07 14:46 config -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2016-12-07 14:46 data -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2016-12-07 14:46 factory -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2016-12-07 14:46 fastboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2016-12-07 14:46 logs -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2016-12-07 14:46 misc -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2016-12-07 14:46 panic -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2016-12-07 14:46 recovery -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2016-12-07 14:46 reserved -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2016-12-07 14:46 reserved_1 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2016-12-07 14:46 system -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2016-12-07 14:46 test -> /dev/block/mmcblk0p7
[email protected]:/sdcard # ls -all
drwxrwx--- root sdcard_r 2016-12-07 14:47 .DataStorage
drwxrwx--- root sdcard_r 2016-12-06 09:03 .UTSystemConfig
drwxrwx--- root sdcard_r 2016-10-16 11:22 .adobe-digital-editions
-rw-rw---- root sdcard_r 85 2016-09-18 12:34 .avg
-rw-rw---- root sdcard_r 7 2016-09-10 21:09 .enref
drwxrwx--- root sdcard_r 2016-12-07 14:50 .estrongs
-rw-rw---- root sdcard_r 36 2016-09-10 20:18 .profig.os
-rw-rw---- root sdcard_r 1410620113 2016-10-16 11:49 161016_update.zip
drwxrwx--- root sdcard_r 2016-09-28 14:27 AccuWeather
drwxrwx--- root sdcard_r 2016-09-10 12:37 Alarms
drwxrwx--x root sdcard_r 2016-09-18 20:20 Android
drwxrwx--- root sdcard_r 2016-09-10 22:00 Books
drwxrwx--- root sdcard_r 2016-09-10 21:05 Calibre_Companion
drwxrwx--- root sdcard_r 2016-12-06 10:09 DCIM
drwxrwx--- root sdcard_r 2016-10-16 11:22 Digital Editions
drwxrwx--- root sdcard_r 2016-11-20 08:18 Documents
drwxrwx--- root sdcard_r 2016-12-07 07:07 Download
drwxrwx--- root sdcard_r 2016-09-10 19:16 Dropsync
drwxrwx--- root sdcard_r 2016-09-18 20:21 Fonts
drwxrwx--- root sdcard_r 2016-12-06 08:09 KingUser
drwxrwx--- root sdcard_r 2016-12-06 07:52 Kingroot
drwxrwx--- root sdcard_r 2016-09-10 12:37 Movies
drwxrwx--- root sdcard_r 2016-09-10 12:37 Music
drwxrwx--- root sdcard_r 2016-09-10 12:22 Notifications
drwxrwx--- root sdcard_r 2016-10-01 15:58 Pictures
drwxrwx--- root sdcard_r 2016-09-10 12:37 Podcasts
drwxrwx--- root sdcard_r 2016-09-10 12:37 Ringtones
drwxrwx--- root sdcard_r 2016-09-18 15:31 Subtitles
drwxrwx--- root sdcard_r 2016-12-06 08:00 Tencent
drwxrwx--- root sdcard_r 2016-10-25 02:09 TitaniumBackup
-rw-rw---- root sdcard_r 4885284 2016-10-16 11:05 TitaniumBackup-7.5.0.zip
drwxrwx--- root sdcard_r 2016-10-10 07:08 Tumblr
-rw-rw---- root sdcard_r 16777216 2016-12-07 15:11 aboot.img
drwxrwx--- root sdcard_r 2016-09-10 14:46 backups
drwxrwx--- root sdcard_r 2016-12-06 11:33 clockworkmod
drwxrwx--- root sdcard_r 2016-09-28 19:42 com.facebook.orca
-rw-rw---- root sdcard_r 427769 2016-12-07 14:48 dropsync.log
drwxrwx--- root sdcard_r 2016-10-16 11:22 eBooks
drwxrwx--- root sdcard_r 2016-09-10 22:00 kindle
drwxrwx--- root sdcard_r 2016-12-06 08:01 kinguserdown
-rw-rw---- root sdcard_r 80 2016-12-06 08:02 kr-stock-conf
drwxrwx--- root sdcard_r 2016-12-07 15:01 logs
drwxrwx--- root sdcard_r 2016-12-06 10:09 mgyapp
drwxrwx--- root sdcard_r 2016-12-06 10:18 qqsecure
-rw-rw---- root sdcard_r 2527 2016-11-13 08:35 snp_log.txt
drwxrwx--- root sdcard_r 2016-09-18 20:10 yahoo
am-lt11226mlatform-tools jeremyboucher$ adb shell
[email protected]:/ # ls
acct
cache
charger
config
d
data
default.prop
dev
etc
factory
file_contexts
fstab
fstab.anzhen4_mrd7
fstab.charger.anzhen4_mrd7
fstab.ramconsole.anzhen4_mrd7
init
init.anzhen4_mrd7.rc
init.aosp.rc
init.avc.rc
init.baylake.sh
init.bt.rc
init.bt.vendor.rc
init.common.rc
init.debug.rc
init.diag.rc
init.dump.rc
init.environ.rc
init.extra.rc
init.firmware.rc
init.gps.rc
init.modem.rc
init.net.eth0.sh
init.platform.gengfx.rc
init.platform.usb.rc
init.rc
init.recovery.anzhen4_mrd7.rc
init.sensor.rc
init.trace.rc
init.usb.rc
init.watchdog.rc
init.watchdog.sh
init.wifi.rc
init.wifi.vendor.rc
init.zygote32.rc
intel_prop.cfg
lib
logs
media
mnt
proc
property_contexts
props.platform.rc
props.rc
res
rfkill_bt.sh
root
sbin
sdcard
seapp_contexts
selinux_version
sepolicy
service_contexts
storage
sys
system
tmp-mksh
ueventd.anzhen4_mrd7.rc
ueventd.modules.blacklist
ueventd.rc
vendor

No logcat output

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

SpO2 TPK

Is there a way to extract the SpO2 tpk file from the Galaxy Watch 3 ? I have both watches GW3 and Active 2. I am planning to sideload the SpO2 on the Active 2. Thanks.
A
Blood Oxygen is NO Standalone TPK nor WGT...
It is inside the "magic" Samsung Health package:
Code:
com.samsung.shealth_gear
B
This crap is started as Widget... no idea how exactly it is enablde/disabled for France etc...
Maybe by Plugin APK crap...
C
Code:
tizen-manifest.xml
From Version 4.12.1200
Code:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<manifest xmlns="http://tizen.org/ns/packages" api-version="5.5.0.1" package="com.samsung.shealth_gear" version="[B]4.12.1200[/B]">
<profile name="wearable"/>
<ui-application
At end of manifest....
Code:
</widget-class>
<[COLOR="Red"][B]widget-class classid[/B][/COLOR]="[COLOR="Red"]oxygensaturation[/COLOR]" max-instance="1" update-period="0">
<!-- DREAM_HEALTH_HEADER_BLOOD_OXYGEN -->
<label xml:lang="ar-ae">الأكسجين في الدم</label>
<label xml:lang="ar-il">الأكسجين في الدم</label>
<label xml:lang="as-in">তেজৰ অক্সিজেন</label>
<label xml:lang="az-az">Qanda oksigen həcmi</label>
<label xml:lang="be-by">Кісларод у крыві</label>
<label xml:lang="bg-bg">Кислород в кръвта</label>
<label xml:lang="bn-bd">রক্তে অক্সিজেন</label>
<label xml:lang="bn-in">রক্তে অক্সিজেন</label>
<label xml:lang="bo-cn">血氧</label>
<label xml:lang="bs-ba">Kisik u krvi</label>
<label xml:lang="ca-es">Oxigen en sang</label>
<label xml:lang="cs-cz">Hladina kyslÃ*ku v krvi</label>
<label xml:lang="da-dk">Iltmætning i blodet</label>
<label xml:lang="de-at">Blutsauerstoff</label>
<label xml:lang="de-ch">Blutsauerstoff</label>
<label xml:lang="de-de">Blutsauerstoff</label>
<label xml:lang="el-gr">Οξυγόνο αίματος</label>
<label xml:lang="en-au">Blood oxygen</label>
<label xml:lang="en-ca">Blood oxygen</label>
<label xml:lang="en-gb">Blood oxygen</label>
<label xml:lang="en-ie">Blood oxygen</label>
<label xml:lang="en-nz">Blood oxygen</label>
This leads to
D
Search in BTG6 GW3 Firmwares... leads to this inside rootfs.img instead csc.img...
Code:
usr/apps/com.samsung.w-home/bin/[B]w-home[/B]
Code:
oxygensaturation[B]@[/B]com.samsung.shealth.widget
E
I am at the moment only smart enough to call apps via Commands...
https://forum.xda-developers.com/showpost.php?p=83481485&postcount=2007
But no idea how this Widget crap...
Code:
F
No Firmwarefiles for Tizen 5.5 leaked to do stupid tests inside Firmware...
I mean no CTH8 nor CTI4 for SM-R820...
Maybe somebody have faster solution for testing... :angel:
Best Regards
Edit 1.
Nice Video:
https://www.youtube.com/watch?v=qyul_jA8kWI
Here we can see 2 ways of start...
A
By open Shealth TPK on Watch...
B
Widget crap....
Edit 2.
Sitting on WC... ehm I mean during hard work..
Got an idea...
Watch Face maybe could call such kind of Widget...
But first I have checked BTG6 Firmware from GW3 for text string:
Code:
com.samsung.shealth.widget
Found this script... so we are agin in SQLite database world...
Code:
#!/bin/bash
#
# RW Update Script for 3.0 -> 4.0
PATH=/bin:/usr/bin:/sbin:/usr/sbin
source /usr/share/upgrade/rw-update-macro.inc
get_version_info
#db
HOMEDB=/opt/usr/home/owner/apps_rw/com.samsung.w-home/data/.home.db
if [ ! -e $HOMEDB ]; then
HOMEDB=/opt/usr/apps/com.samsung.w-home/data/.home.db
fi
if [ "$OLD_VER" = "unknown" ]; then
echo "upgrade home DB HOME DB:$HOMEDB"
/usr/bin/sqlite3 $HOMEDB "update home set id = 'com.samsung.app-shortcut-widget' where id='com.samsung.app-widget.widget';"
/usr/bin/sqlite3 $HOMEDB "update home set id = '[email protected]' where id = 'com.samsung.shealth.widget.pedometer';"
/usr/bin/sqlite3 $HOMEDB "update home set id = '[email protected]' where id = 'com.samsung.shealth.widget.hrlog';"
/usr/bin/sqlite3 $HOMEDB "update home set id = '[email protected]' where id = 'com.samsung.shealth.widget.exercise';"
/usr/bin/sqlite3 $HOMEDB "update home set id = '[email protected]' where id = 'com.samsung.shealth.widget.heartrate';"
/usr/bin/sqlite3 $HOMEDB "update home set id = '[email protected]' where id = 'com.samsung.shealth.widget.intake';"
/usr/bin/sqlite3 $HOMEDB "update home set id = '[email protected]' where id = 'com.samsung.shealth.widget.together';"
/usr/bin/sqlite3 $HOMEDB "update home set id = '[email protected]' where id = 'com.samsung.shealth.widget.together.leaderboard';"
/usr/bin/sqlite3 $HOMEDB "update home set id = '[email protected]' where id = 'com.samsung.shealth.widget.together.challenge';"
/usr/bin/sqlite3 $HOMEDB "update home set id = '[email protected]' where id = 'com.samsung.shealth.widget.floor';"
/usr/bin/sqlite3 $HOMEDB "update home set id = '[email protected]' where id = 'com.samsung.w-calendar2.widget.next-event';"
/usr/bin/sqlite3 $HOMEDB "update home set id = 'com.samsung.w-contacts2.widget.multiple' where id = 'com.samsung.w-contacts2.widget.single';"
/usr/bin/sqlite3 $HOMEDB "update home set id = 'com.samsung.w-magazine-widget-app' where id = 'org.tizen.magazine-widget';"
/usr/bin/com.samsung.app-widget-upgrade
fi
if [[ "$OLD_VER" = "3.0"* ]]; then
echo "upgrade home DB 3.0* to 4.0 HOME DB:$HOMEDB"
/usr/bin/sqlite3 $HOMEDB "delete from home where id = '[email protected]';"
fi
Will check if i can find Watch Face as template...
Maybe easier here to "spoof"...
Best Regards
Watch Face seems dead end too...
But paths from Shell script leads to this:
Code:
D:\SDB\SDB260>sdb pull /opt/usr/apps/com.samsung.w-home/data/.home.db
pulled .home.db 100% 16KB
1 file(s) pulled. 0 file(s) skipped.
/opt/usr/apps/com.samsung.w-home/data/.home.db 106 KB/s (16384 bytes in 0.150s)
Code:
D:\SDB\SDB260>sdb pull /opt/usr/home/owner/apps_rw/com.samsung.w-home/data/.home.db
pulled .home.db 100% 16KB
1 file(s) pulled. 0 file(s) skipped.
/opt/usr/home/owner/apps_rw/com.samsung.w-home/data/.home.db 123 KB/s (16384 bytes in 0.130s)
1:1 same file from both locations as it seems...
adfree said:
Watch Face seems dead end too...
But paths from Shell script leads to this:
Code:
D:\SDB\SDB260>sdb pull /opt/usr/apps/com.samsung.w-home/data/.home.db
pulled .home.db 100% 16KB
1 file(s) pulled. 0 file(s) skipped.
/opt/usr/apps/com.samsung.w-home/data/.home.db 106 KB/s (16384 bytes in 0.150s)
Code:
D:\SDB\SDB260>sdb pull /opt/usr/home/owner/apps_rw/com.samsung.w-home/data/.home.db
pulled .home.db 100% 16KB
1 file(s) pulled. 0 file(s) skipped.
/opt/usr/home/owner/apps_rw/com.samsung.w-home/data/.home.db 123 KB/s (16384 bytes in 0.130s)
1:1 same file from both locations as it seems...
Click to expand...
Click to collapse
Looks like we are getting somewhere here. Any files you need for me to check from my Active 2 watch. ?
My setup is are as follows
Phone: Huawei Mate 20 Pro
Watch: Samsung Active 2
Active 2 Watch CSC is now KOO changed using Combination FW and Netodin
Originally it was on 4 0 0 .7 , changed to 4 0 0 .6 after Netodin CSC update
Installed bp.tpk and ecg.tpk via sdb.
then via Samsung OTA it became 4 0 0 .8 then another Samsung OTA came
and it is now 5.5.0. 1. Both Ecg and BP are working using Samsung Health Monitor 167
For better investigation... my SM-R760...
Code:
sh-3.2# cd /opt/usr/home/owner/apps_rw/com.samsung.w-home/data/
sh-3.2# ls -a1l
total 124
drwxrwsr-x 3 owner system_share 4096 Oct 1 05:03 .
drwxr-xr-x 5 owner users 4096 Apr 28 10:04 ..
-rw-r--r-- 1 owner system_share 16384 Oct 2 15:51 .apps.db
-rw-r--r-- 1 owner system_share 12824 Oct 1 05:03 .apps.db-journal
-rw-r--r-- 1 owner system_share 16384 Oct 2 15:51 .home.db
-rw-r--r-- 1 owner system_share 12824 Oct 2 15:51 .home.db-journal
drwxr-sr-x 2 owner system_share 4096 Oct 1 05:04 .pref
-rw-r--r-- 1 owner system_share 20480 Oct 2 15:51 .widget_suggestion.db
-rw-r--r-- 1 owner system_share 16928 Oct 1 05:03 .widget_suggestion.db-journal
sh-3.2# cd /opt/usr/apps/com.samsung.w-home/data/
sh-3.2# ls -a1l
total 124
drwxrwsr-x 3 owner system_share 4096 Oct 1 05:03 .
drwxr-xr-x 5 owner users 4096 Apr 28 10:04 ..
-rw-r--r-- 1 owner system_share 16384 Oct 2 15:51 .apps.db
-rw-r--r-- 1 owner system_share 12824 Oct 1 05:03 .apps.db-journal
-rw-r--r-- 1 owner system_share 16384 Oct 2 15:51 .home.db
-rw-r--r-- 1 owner system_share 12824 Oct 2 15:51 .home.db-journal
drwxr-sr-x 2 owner system_share 4096 Oct 1 05:04 .pref
-rw-r--r-- 1 owner system_share 20480 Oct 2 15:51 .widget_suggestion.db
-rw-r--r-- 1 owner system_share 16928 Oct 1 05:03 .widget_suggestion.db-journal
sh-3.2# mkdir testme
sh-3.2# ls -a1l
total 128
drwxrwsr-x 4 owner system_share 4096 Oct 2 15:56 .
drwxr-xr-x 5 owner users 4096 Apr 28 10:04 ..
-rw-r--r-- 1 owner system_share 16384 Oct 2 15:51 .apps.db
-rw-r--r-- 1 owner system_share 12824 Oct 1 05:03 .apps.db-journal
-rw-r--r-- 1 owner system_share 16384 Oct 2 15:51 .home.db
-rw-r--r-- 1 owner system_share 12824 Oct 2 15:51 .home.db-journal
drwxr-sr-x 2 owner system_share 4096 Oct 1 05:04 .pref
-rw-r--r-- 1 owner system_share 20480 Oct 2 15:51 .widget_suggestion.db
-rw-r--r-- 1 owner system_share 16928 Oct 1 05:03 .widget_suggestion.db-journal
drwxrwsrwx 2 root system_share 4096 Oct 2 15:56 testme
sh-3.2# cd /opt/usr/home/owner/apps_rw/com.samsung.w-home/data/
sh-3.2# ls -a1l
total 128
drwxrwsr-x 4 owner system_share 4096 Oct 2 15:56 .
drwxr-xr-x 5 owner users 4096 Apr 28 10:04 ..
-rw-r--r-- 1 owner system_share 16384 Oct 2 15:51 .apps.db
-rw-r--r-- 1 owner system_share 12824 Oct 1 05:03 .apps.db-journal
-rw-r--r-- 1 owner system_share 16384 Oct 2 15:51 .home.db
-rw-r--r-- 1 owner system_share 12824 Oct 2 15:51 .home.db-journal
drwxr-sr-x 2 owner system_share 4096 Oct 1 05:04 .pref
-rw-r--r-- 1 owner system_share 20480 Oct 2 15:51 .widget_suggestion.db
-rw-r--r-- 1 owner system_share 16928 Oct 1 05:03 .widget_suggestion.db-journal
drwxrwsrwx 2 root system_share 4096 Oct 2 15:56 testme
A
Aha, seems only 1 folder...
So I need only 1 time play with file
Code:
.home.db
B
Code:
D:\SDB\SDB260>sdb pull /opt/usr/home/owner/apps_rw/com.samsung.w-home/data/ .\ftd4\widget
pulled .widget_suggestion.db-journal 100% 16KB
pulled .home.db 100% 16KB
pulled .apps.db 100% 16KB
pulled .apps.db-journal 100% 12KB
pulled .home.db-journal 100% 12KB
pulled .widget_suggestion.db 100% 20KB
pulled 55157627a4c4b5a9bdfc405a197f194d84543b01 100% 44 B
pulled f657e4e15e35a0c1fa53c462020df9ebec5c19ce 100% 36 B
pulled 3cbacb5376e2dee294232c956838fc1954985ea5 100% 49 B
pulled ec6b88021747c602dffdafe2e809beb84d820488 100% 43 B
pulled 1e3463dc2080de6e30d6f7ee28b65fcdfa33d0d5 100% 49 B
pulled d6ea693302f3e6a1b8bb827892323e8ed76a4274 100% 42 B
12 file(s) pulled. 0 file(s) skipped.
/opt/usr/home/owner/apps_rw/com.samsung.w-home/data/ 126 KB/s (96087 bytes in 0.740s)
Maybe more clear what is inside db...
C
If I push with SDB then... hmmm... maybe this is why it fails... maybe...
Code:
sh-3.2# cd /opt/usr/home/owner/apps_rw/com.samsung.w-home/data/
sh-3.2# ls -a1l
total 128
drwxrwsr-x 4 owner system_share 4096 Oct 2 16:13 .
drwxr-xr-x 5 owner users 4096 Apr 28 10:04 ..
-rw-r--r-- 1 owner system_share 16384 Oct 2 15:51 .apps.db
-rw-r--r-- 1 owner system_share 12824 Oct 1 05:03 .apps.db-journal
[COLOR="Red"]-rwxr-xrwx[/COLOR] 1 root system_share 16384 Oct 2 02:14 .home.db
-rw-r--r-- 1 owner system_share 12824 Oct 2 15:51 .home.db-journal
drwxr-sr-x 2 owner system_share 4096 Oct 1 05:04 .pref
-rw-r--r-- 1 owner system_share 20480 Oct 2 15:51 .widget_suggestion.db
-rw-r--r-- 1 owner system_share 16928 Oct 1 05:03 .widget_suggestion.db-journal
drwxrwsrwx 2 root system_share 4096 Oct 2 15:56 testme
Pulled files via SDB from my SM-R820...
Not all possible but few... :good: :good:
Compared with BTG6 Firmware rootfs.img from GW3...
Code:
spo2 app is not enabled. [COLOR="Red"][B]skip[/B][/COLOR]
This is inside...
Code:
/usr/apps/com.samsung.w-manager-service/bin/[COLOR="Red"][B]w-manager-service[/B][/COLOR]
Best Regards
I have now rooted Tizen 5.5 for my SM-R820... CTH8...
Need to prepare few things and backup,,,
Then I will "simple" edit:
Code:
home_default_items.xml
in Default Folder of CSC Preconfig crap...
Code:
<?xml version="1.0" encoding="UTF-8"?>
<data>
<favorite>
<packagename>[email protected]</packagename>
<classname>[email protected]</classname>
<screen>0</screen>
<cellX>0</cellX>
<cellY>0</cellY>
</favorite>
<favorite>
<packagename>com.samsung.app-shortcut-widget</packagename>
<classname>com.samsung.app-shortcut-widget</classname>
<screen>1</screen>
<cellX>1</cellX>
<cellY>0</cellY>
</favorite>
<favorite>
<packagename>[email protected]</packagename>
<classname>[email protected]</classname>
<screen>0</screen>
<cellX>1</cellX>
<cellY>0</cellY>
</favorite>
<favorite>
<packagename>[email protected]</packagename>
<classname>[email protected]</classname>
<screen>0</screen>
<cellX>1</cellX>
<cellY>1</cellY>
</favorite>
<favorite>
<packagename>com.samsung.weather-widget</packagename>
<classname>com.samsung.weather-widget</classname>
<screen>1</screen>
<cellX>0</cellX>
<cellY>0</cellY>
</favorite>
<favorite>
<packagename>[email protected]</packagename>
<classname>[email protected]</classname>
<screen>2</screen>
<cellX>0</cellX>
<cellY>0</cellY>
</favorite>
</data>
Maybe I add or I replace...
Code:
[COLOR="Red"][B]oxygensaturation[/B][/COLOR]@com.samsung.shealth.widget
We will see if this is enough...
Best Regards
How did you root 5.5? I haven't been able to find any info on rooting these other than some old rooted firnwares
Code:
sdb root on
sdb shell mount -vo remount,rw /opt/system/csc/
sdb push SW_Configuration.xml /opt/system/csc/mps/CSC/
sdb push home_default_items.xml /opt/system/csc/preconfig/DEF/usr/homescreen/
First attempt...
Changed 1 Byte to prevent CTI4 FOTA...
@betterl8thannvr
Your Model Name is what?
Because I've play with my SM-R820...
Best Regards
@adfree ah, mine fails when I try sdb root on
>sdb root on
* The version of SDB client (2.3.0) is not same with that of SDB server (4.2.12).
It may cause version compatibility problems.
It is recommended to use SDB server with version 2.3.0. *
Permission denied
Any idea how to get around that?
Edit: I have SM-R825U
sdb root can be done once you connect with Tizen Studio right ?
First attempt not bring Blood Oxygen to me...
Second attempt...
Code:
D:\SDB\SDB260>sdb root on
Switched to 'root' account mode
D:\SDB\SDB260>sdb shell mount -vo remount,rw /opt/system/csc/
mount: /dev/mmcblk0p16 mounted on /opt/system/csc.
D:\SDB\SDB260>sdb shell mkdir /opt/system/csc/preconfig/DBT/usr/homescreen/
mkdir: cannot create directory `/opt/system/csc/preconfig/DBT/usr/homescreen/': No such file or directory
D:\SDB\SDB260>sdb shell
sh-3.2# cd /opt/system/csc/preconfig/DBT/
sh-3.2# ls -a1l
total 8
drwxr-xr-x 4 root root 1024 Jun 16 16:10 .
drwxr-xr-x 71 root root 1024 Jun 16 16:10 ..
drwxr-xr-x 2 root root 1024 Jun 16 16:10 feature
drwxr-xr-x 2 root root 1024 Jun 16 16:10 preset
sh-3.2# mkdir usr
sh-3.2# cd usr
sh-3.2# mkdir homescreen
sh-3.2# exit
exit
D:\SDB\SDB260>sdb push home_default_items.xml /opt/system/csc/preconfig/DBT/usr/homescreen/
pushed home_default_items.xml 100% 1KB
1 file(s) pushed. 0 file(s) skipped.
home_default_items.xml 7 KB/s (1387 bytes in 0.180s)
D:\SDB\SDB260>sdb shell
sh-3.2# cd /opt/system/csc/preconfig/DBT/usr/homescreen/
sh-3.2# ls -a1l
total 7
drwxrwxrwx 2 root root 1024 Oct 3 14:03 .
drwxrwxrwx 3 root root 1024 Oct 3 14:03 ..
-rwxr-xrwx 1 root root 1387 Oct 3 07:49 home_default_items.xml
sh-3.2# reboot
Rebooting.
@EQMOD
You need Root aka Super User aka su Binary inside Firmware... this is Linux stuff...
@betterl8thannvr
You are in similar situation like me...
No latest files leaked...
ATF2 is latest leaked Files for netOdin...
So much harder to get Root Access...
I have at the moment limited time to explain nor to make the files for you...
Maybe next days more time...
Best Regards
adfree said:
First attempt not bring Blood Oxygen to me...
Second attempt...
Code:
D:\SDB\SDB260>sdb root on
Switched to 'root' account mode
D:\SDB\SDB260>sdb shell mount -vo remount,rw /opt/system/csc/
mount: /dev/mmcblk0p16 mounted on /opt/system/csc.
D:\SDB\SDB260>sdb shell mkdir /opt/system/csc/preconfig/DBT/usr/homescreen/
mkdir: cannot create directory `/opt/system/csc/preconfig/DBT/usr/homescreen/': No such file or directory
D:\SDB\SDB260>sdb shell
sh-3.2# cd /opt/system/csc/preconfig/DBT/
sh-3.2# ls -a1l
total 8
drwxr-xr-x 4 root root 1024 Jun 16 16:10 .
drwxr-xr-x 71 root root 1024 Jun 16 16:10 ..
drwxr-xr-x 2 root root 1024 Jun 16 16:10 feature
drwxr-xr-x 2 root root 1024 Jun 16 16:10 preset
sh-3.2# mkdir usr
sh-3.2# cd usr
sh-3.2# mkdir homescreen
sh-3.2# exit
exit
D:\SDB\SDB260>sdb push home_default_items.xml /opt/system/csc/preconfig/DBT/usr/homescreen/
pushed home_default_items.xml 100% 1KB
1 file(s) pushed. 0 file(s) skipped.
home_default_items.xml 7 KB/s (1387 bytes in 0.180s)
D:\SDB\SDB260>sdb shell
sh-3.2# cd /opt/system/csc/preconfig/DBT/usr/homescreen/
sh-3.2# ls -a1l
total 7
drwxrwxrwx 2 root root 1024 Oct 3 14:03 .
drwxrwxrwx 3 root root 1024 Oct 3 14:03 ..
-rwxr-xrwx 1 root root 1387 Oct 3 07:49 home_default_items.xml
sh-3.2# reboot
Rebooting.
@EQMOD
You need Root aka Super User aka su Binary inside Firmware... this is Linux stuff...
@betterl8thannvr
You are in similar situation like me...
No latest files leaked...
ATF2 is latest leaked Files for netOdin...
So much harder to get Root Access...
I have at the moment limited time to explain nor to make the files for you...
Maybe next days more time...
Best Regards
Click to expand...
Click to collapse
What happened after reboot ?
thanks @adfree, I think I can figure out how to root on ATF2, but you said you had root on 5.5, so I am quite curious about how to do that without the leaked files.
I will keep poking at it.
Hmm, well, flashing back to ATF2 is being troublesome. It fails every time, so I now have a small, expensive brick.
<ID:0/001> 192.168.49.1
<ID:0/001> Odin engine v(ID:1.0000)..
<ID:0/001> File analysis..
<ID:0/001> SetupConnection..
<ID:0/001> Initialzation..
<ID:0/001> Set PIT file..
<ID:0/001> DO NOT TURN OFF TARGET!!
<ID:0/001> Get PIT for mapping..
<ID:0/001> Get PIT Transmission
<ID:0/001> Firmware update start..
<ID:0/001> SingleDownload.
<ID:0/001> cm.bin
<ID:0/001>
<ID:0/001> XmitData
<ID:0/001> Complete(Write) operation failed.
<ID:0/001> Removed!!
<OSM> All threads completed. (succeed 0 / failed 1)
Code:
XmitData
Is IMHO out of luck transfer Error...
I have fixed this by trying again...
@betterl8thannvr
Your GW2 still have working:
Code:
download wirelss
About ATF2 I can only remember I have uploaded "corrected" CSC, because invalid file inside...
Will check my HDD...
Best Regards
Tiny progress...
A
Seems I found my mistake...
SDB push change Permissions to file...
Code:
D:\SDB\SDB260>sdb push .home.db /opt/usr/apps/com.samsung.w-home/data/
pushed .home.db 100% 16KB
1 file(s) pushed. 0 file(s) skipped.
.home.db 84 KB/s (16384 bytes in 0.190s)
D:\SDB\SDB260>sdb shell
sh-3.2# cd /opt/usr/apps/com.samsung.w-home/data/
sh-3.2# ls -a1l
total 124
drwxrwsr-x 3 owner system_share 4096 Oct 5 00:33 .
drwxr-xr-x 5 owner users 4096 Oct 3 14:10 ..
-rw-r--r-- 1 owner system_share 16384 Oct 3 14:53 .apps.db
-rw-r--r-- 1 owner system_share 12824 Oct 3 14:53 .apps.db-journal
-rwxr-xrwx 1 root system_share 16384 Oct 3 21:27 .home.db
-rw-r--r-- 1 owner system_share 12824 Oct 5 00:04 .home.db-journal
drwxr-sr-x 2 owner system_share 4096 Oct 3 14:15 .pref
-rw-r--r-- 1 owner system_share 20480 Oct 3 14:15 .widget_suggestion.db
-rw-r--r-- 1 owner system_share 16928 Oct 3 14:15 .widget_suggestion.db-journal
sh-3.2# chmod 644 .home.db
sh-3.2# ls -a1l
total 124
drwxrwsr-x 3 owner system_share 4096 Oct 5 00:33 .
drwxr-xr-x 5 owner users 4096 Oct 3 14:10 ..
-rw-r--r-- 1 owner system_share 16384 Oct 3 14:53 .apps.db
-rw-r--r-- 1 owner system_share 12824 Oct 3 14:53 .apps.db-journal
-rw-r--r-- 1 root system_share 16384 Oct 3 21:27 .home.db
-rw-r--r-- 1 owner system_share 12824 Oct 5 00:04 .home.db-journal
drwxr-sr-x 2 owner system_share 4096 Oct 3 14:15 .pref
-rw-r--r-- 1 owner system_share 20480 Oct 3 14:15 .widget_suggestion.db
-rw-r--r-- 1 owner system_share 16928 Oct 3 14:15 .widget_suggestion.db-journal
So I have to correct it...
But this require ROOT...
Tested .home.db from GW3...
Blood Oxygen still blocked...
Hmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm.
So this means IMHO... I have to replace
Code:
com.samsung.w-home.home-service
https://forum.xda-developers.com/showpost.php?p=83626487&postcount=6
Best Regards
adfree said:
Tiny progress...
A
Seems I found my mistake...
SDB push change Permissions to file...
Code:
D:\SDB\SDB260>sdb push .home.db /opt/usr/apps/com.samsung.w-home/data/
pushed .home.db 100% 16KB
1 file(s) pushed. 0 file(s) skipped.
.home.db 84 KB/s (16384 bytes in 0.190s)
D:\SDB\SDB260>sdb shell
sh-3.2# cd /opt/usr/apps/com.samsung.w-home/data/
sh-3.2# ls -a1l
total 124
drwxrwsr-x 3 owner system_share 4096 Oct 5 00:33 .
drwxr-xr-x 5 owner users 4096 Oct 3 14:10 ..
-rw-r--r-- 1 owner system_share 16384 Oct 3 14:53 .apps.db
-rw-r--r-- 1 owner system_share 12824 Oct 3 14:53 .apps.db-journal
-rwxr-xrwx 1 root system_share 16384 Oct 3 21:27 .home.db
-rw-r--r-- 1 owner system_share 12824 Oct 5 00:04 .home.db-journal
drwxr-sr-x 2 owner system_share 4096 Oct 3 14:15 .pref
-rw-r--r-- 1 owner system_share 20480 Oct 3 14:15 .widget_suggestion.db
-rw-r--r-- 1 owner system_share 16928 Oct 3 14:15 .widget_suggestion.db-journal
sh-3.2# chmod 644 .home.db
sh-3.2# ls -a1l
total 124
drwxrwsr-x 3 owner system_share 4096 Oct 5 00:33 .
drwxr-xr-x 5 owner users 4096 Oct 3 14:10 ..
-rw-r--r-- 1 owner system_share 16384 Oct 3 14:53 .apps.db
-rw-r--r-- 1 owner system_share 12824 Oct 3 14:53 .apps.db-journal
-rw-r--r-- 1 root system_share 16384 Oct 3 21:27 .home.db
-rw-r--r-- 1 owner system_share 12824 Oct 5 00:04 .home.db-journal
drwxr-sr-x 2 owner system_share 4096 Oct 3 14:15 .pref
-rw-r--r-- 1 owner system_share 20480 Oct 3 14:15 .widget_suggestion.db
-rw-r--r-- 1 owner system_share 16928 Oct 3 14:15 .widget_suggestion.db-journal
So I have to correct it...
But this require ROOT...
Tested .home.db from GW3...
Blood Oxygen still blocked...
Hmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm.
So this means IMHO... I have to replace
Code:
com.samsung.w-home.home-service
https://forum.xda-developers.com/showpost.php?p=83626487&postcount=6
Best Regards
Click to expand...
Click to collapse
Could you upload both binaries here. (GW3, GA2) and home.db Let me check both
@EQMOD
Soon I have rooted CTI4 uploaded for SM-R820...
Your Model Name is exactly what?
In your posts I see only GWA2...
Best Regards
adfree said:
@EQMOD
Soon I have rooted CTI4 uploaded for SM-R820...
Your Model Name is exactly what?
In your posts I see only GWA2...
Best Regards
Click to expand...
Click to collapse
its SM-R820

Categories

Resources