Here are some basic info I gathered after first touch of this phone.
First thing everybody will do is turning off very loud boot logo sound:
Setting - Sound:
Power up sound - off
How to enter specific android modes when starting phone
- buttons Power + VolumeUp
Boot menu items - Recovery/Bootloader (fastboot)/Normal
- select Boot menu item with VolumeUp, confirm item with VolumeDown
- enter Recovery menu from Recovery no command screen with Power + VolumeUp
- select Recovery menu item with VolumeUp and VolumeDown, confirm item with Power
- buttons Power + VolumeDown
Another Boot menu with not english characters/words (somebody translate it pls)
How to enter Safe mode (3rd party apps will not be loaded)
- press/hold Power button until power menu shows up during normal android session
- tap/hold Power off option
- choose OK to reboot in Safe mode
Here are also some data from filesystem.
Code:
$ mount
rootfs on / type rootfs (ro,seclabel)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime,gid=3009,hidepid=2)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,seclabel,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt type tmpfs (rw,seclabel,relatime,mode=755,gid=1000)
none on /config type configfs (rw,relatime)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
pstore on /sys/fs/pstore type pstore (rw,seclabel,relatime)
/dev/block/dm-0 on /system type ext4 (ro,seclabel,relatime,data=ordered)
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/userdata on /data type ext4 (rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,resuid=10010,data=ordered)
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/cache on /cache type ext4 (rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered)
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/protect1 on /protect_f type ext4 (rw,seclabel,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered)
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/protect2 on /protect_s type ext4 (rw,seclabel,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered)
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/nvdata on /nvdata type ext4 (rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered)
adb on /dev/usb-ffs/adb type functionfs (rw,relatime)
tmpfs on /storage type tmpfs (rw,seclabel,relatime,mode=755,gid=1000)
/dev/fuse on /mnt/runtime/default/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/read/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/write/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/block/vold/public:179,129 on /mnt/media_rw/XXXX-XXXX type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/fuse on /mnt/runtime/default/XXXX-XXXX type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/XXXX-XXXX type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/read/XXXX-XXXX type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/write/XXXX-XXXX type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
$ cat build.prop
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=NRD90M.07.009
ro.build.version.full=Blur_Version.25.071.009.panell_23_dl.retail.en.US
ro.skuid=07
ro.wind.version.inner=EMEA_A158L_K100_DS_V1.0B09
ro.wind.display.id=Moto C Plus-user 7.0 NRD90M.07.009 009
ro.mot.build.product.increment=NRD90M.07.009
ro.boot.hardware.sku=XT1723
ro.wind.fccid=IHDT56WE1
ro.build.display.id=NRD90M.07 009
ro.build.version.incremental=009
ro.build.wind.version=Plat:EMEA_A158L_K100_DS_V1.0B09Outer:End
ro.product.hardware=WKHMA1B2-2
ro.build.version.sdk=24
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=7.0
ro.build.version.security_patch=2017-04-05
ro.build.version.base_os=motorola/panell_23_dl/panell_dl:7.0/NRD90M.07.009/009:user/release-keys
ro.build.date=Fri May 12 01:11:56 CST 2017
ro.build.date.utc=1494522716
ro.build.type=user
ro.build.user=gujintao
ro.build.host=SOFT30-83
ro.build.tags=release-keys
ro.build.flavor=full_A158-user
ro.product.model=Moto C Plus
ro.product.brand=motorola
ro.product.name=panell_23_dl
ro.product.device=panell_dl
ro.product.board=MT6737
ro.product.emailsignature=
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.cpu.abilist=armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=
ro.product.manufacturer=motorola
ro.product.locale=en-US
ro.wifi.channels=
ro.board.platform=mt6737m
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=panell_23_dl-user 7.0 NRD90M.07.009 release-keys
ro.build.fingerprint=motorola/panell_23_dl/panell_dl:7.0/NRD90M.07.009/009:user/release-keys
ro.build.characteristics=default
ro.wind.mtp_name=XT1723
# end build properties
ro.setting.dateformat=yyyy-MM-dd
ro.wind_default_stk_name=
#
# from device/ginreen/A158/system.prop
#
#
# system.prop for generic sdk
#
rild.libpath=mtk-ril.so
rild.libargs=-d /dev/ttyC0
# MTK, Infinity, 20090720 {
wifi.interface=wlan0
# MTK, Infinity, 20090720 }
# MTK, mtk03034, 20101210 {
ro.mediatek.wlan.wsc=1
# MTK, mtk03034 20101210}
# MTK, mtk03034, 20110318 {
ro.mediatek.wlan.p2p=1
# MTK, mtk03034 20110318}
# MTK, mtk03034, 20101213 {
mediatek.wlan.ctia=0
# MTK, mtk03034 20101213}
#
wifi.tethering.interface=ap0
#
ro.opengles.version=196609
#ro.kernel.qemu=1
#ro.kernel.qemu.gles=0
wifi.direct.interface=p2p0
#dalvik.vm.heapgrowthlimit=128m
#dalvik.vm.heapsize=256m
# USB MTP WHQL
ro.sys.usb.mtp.whql.enable=0
# Power off opt in IPO
sys.ipo.pwrdncap=2
ro.sys.usb.storage.type=mtp
# USB BICR function
ro.sys.usb.bicr=no
# USB Charge only function
ro.sys.usb.charging.only=yes
# audio
ro.camera.sound.forced=0
ro.audio.silent=0
ro.zygote.preload.enable=0
# [email protected] add 2016/11/28 begin
# fix Feature N/A : hide navigatio bar
# temporary enables NAV bar (soft keys)
qemu.hw.mainkeys=1
# [email protected] add 2016/11/28 end
ro.kernel.zio=38,108,105,16
#ro.kernel.qemu=1
#ro.kernel.qemu.gles=0
#ro.boot.selinux=disable
## lcm add for [email protected] begin at 20161109
ro.sf.lcd_density=320
## lcm add for [email protected] end at 20161109
# performance
ro.mtk_perf_simple_start_win=1
ro.mtk_perf_fast_start_win=1
ro.mtk_perf_response_time=1
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.carrier=unknown
persist.sys.timezone=Asia/Shanghai
ro.config.notification_sound=Moto.mp3
ro.product.minmatch=7
ro.config.alarm_alert=Oxygen.ogg
ro.config.ringtone=Moto.mp3
ro.com.android.dateformat=yyyy-MM-dd
ro.mediatek.chip_ver=S01
ro.mediatek.platform=MT6737M
ro.telephony.sim.count=2
persist.radio.default.sim=0
ro.config.low_ram=true
ro.wind_def_runtime_test=1
ro.wind_def_sdn_on=1
ril.specific.sm_cause=0
bgw.current3gband=0
ril.external.md=0
ro.sf.hwrotation=0
persist.radio.fd.counter=150
persist.radio.fd.off.counter=50
persist.radio.fd.r8.counter=150
persist.radio.fd.off.r8.counter=50
drm.service.enabled=true
fmradio.driver.enable=1
ril.first.md=1
ril.flightmode.poweroffMD=0
ril.telephony.mode=0
dalvik.vm.mtk-stack-trace-file=/data/anr/mtk_traces.txt
mediatek.wlan.chip=CONSYS_MT6735
mediatek.wlan.module.postfix=_consys_mt6735
ril.radiooff.poweroffMD=1
ro.frp.pst=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/frp
ro.product.first_api_level=24
ro.mtk_protocol1_rat_config=Lf/Lt/W/G
ro.mediatek.version.branch=alps-mp-n0.mp1
ro.mediatek.version.release=alps-mp-n0.mp1-V1.0.2_gr6737m.35.le.n_P61
ro.mediatek.version.sdk=4
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=7.0_r7
ro.num_md_protocol=2
persist.radio.multisim.config=dsds
ro.mtk_besloudness_support=1
ro.mtk_wapi_support=1
ro.mtk_bt_support=1
ro.mtk_wappush_support=1
ro.mtk_agps_app=1
ro.mtk_audio_tuning_tool_ver=V1
ro.mtk_wlan_support=1
ro.mtk_ipo_support=1
ro.mtk_gps_support=1
ro.mtk_omacp_support=1
ro.mtk_search_db_support=1
ro.mtk_dialer_search_support=1
ro.mtk_dhcpv6c_wifi=1
ro.have_aacencode_feature=1
ro.mtk_fd_support=1
ro.mtk_oma_drm_support=1
ro.mtk_widevine_drm_l3_support=1
ro.mtk_eap_sim_aka=1
ro.mtk_fm_recording_support=1
ro.mtk_send_rr_support=1
ro.mtk_emmc_support=1
ro.mtk_tetheringipv6_support=1
ro.telephony.default_network=9,9
ro.mtk_shared_sdcard=1
ro.mtk_enable_md1=1
ro.mtk_aal_support=1
ro.mtk_pq_support=2
ro.mtk_pq_color_mode=1
ro.mtk_miravision_support=1
ro.mtk_wifi_mcc_support=1
ro.mtk_radiooff_power_off_md=1
ro.mtk_bip_scws=1
ro.mtk_world_phone_policy=0
ro.mtk_perfservice_support=1
ro.mtk_cam_mfb_support=0
ro.mtk_lte_support=1
ro.mtk_cam_cfb=1
ro.sim_refresh_reset_by_modem=1
ro.mtk_external_sim_only_slots=0
ro.mtk_bg_power_saving_ui=1
ro.have_aee_feature=1
ro.sim_me_lock_mode=0
ro.mtk_dual_mic_support=0
ro.mtk_is_tablet=0
persist.mtk_nlp_switch_support=1
persist.mtk_ims_support=1
ro.mtk_multiple_ims_support=1
persist.mtk_volte_support=1
persist.mtk.volte.enable=1
persist.mtk_vilte_support=1
ro.mtk_vilte_ut_support=0
wfd.dummy.enable=1
wfd.iframesize.level=0
ro.mediatek.project.path=device/ginreen/A158
persist.mtk.wcn.combo.chipid=-1
persist.mtk.wcn.patch.version=-1
persist.mtk.wcn.dynamic.dump=0
service.wcn.driver.ready=no
service.wcn.coredump.mode=0
persist.mtk.connsys.poweron.ctl=0
ro.com.android.mobiledata=true
persist.radio.mobile.data=0,0
persist.meta.dumpdata=0
dalvik.vm.heapgrowthlimit=128m
dalvik.vm.heapsize=256m
persist.radio.mtk_dsbp_support=1
persist.mtk_dynamic_ims_switch=1
persist.radio.mtk_ps3_rat=G
ro.boot.opt_c2k_lte_mode=0
ro.boot.opt_md1_support=5
ro.boot.opt_lte_support=1
persist.log.tag.AT=I
persist.log.tag.RILMUXD=I
persist.log.tag.RILC-MTK=I
persist.log.tag.RILC=I
persist.log.tag.RfxMainThread=I
persist.log.tag.RfxRoot=I
persist.log.tag.RfxRilAdapter=I
persist.log.tag.RfxController=I
persist.log.tag.RILC-RP=I
persist.log.tag.RIL-DATA=I
ro.boot.opt_using_default=1
mtk.vdec.waitkeyframeforplay=1
ro.sys.sdcardfs=1
persist.runningbooster.support=1
persist.runningbooster.upgrade=1
ro.media.maxmem=500000000
ro.wind_timeformat_is_24=0
ro.wind_timeformat_is_12=0
ro.wind_config_wifi_name=1
ro.wind_def_sml_support=1
ro.wind_def_sml_dualsim=1
ro.wind_unlock_digits=16
ro.wind_show_stk_name_from_sim=0
ro.wind.enable_adb_user_build=1
ro.wind_country_code_support=1
ro.wind_def_mirror_support=1
ro.com.google.apphider=on
ro.com.google.clientidbase=android-motorola
ro.com.google.clientidbase.ms=android-motorola
ro.com.google.clientidbase.yt=android-motorola
ro.com.google.clientidbase.am=android-motorola
ro.com.google.clientidbase.gmm=android-motorola
ro.wind_def_signal_five=0
ro.wind_battery_now_current=1
ro.wind_gensor_shake_control=1
ro.wind_camera_fool_proof=1
ro.wind_def_pro_a158=1
ro.wind_def_optr_a158_emead=1
ro.wind_def_optr_a158_emead1g=1
ro.wind_def_optr_a158_emeas=0
ro.wind_def_optr_a158_apd=0
ro.wind_def_optr_a158_lad=0
ro.wind_def_optr_a158_las=0
ro.wind_def_optr_a158_lbd=0
ro.wind_def_optr_a158_lbd_pa=0
ro.wind_sar_sensor_test=0
drm.forwardlock.only=true
ro.wind_def_language_fromsim=1
ro.wind_disable_sddialog=1
ro.wind_lbd_factory_version=0
ro.wind_default_apn_deletable=1
persist.sys.dalvik.vm.lib.2=libart.so
dalvik.vm.isa.arm.variant=cortex-a53
dalvik.vm.isa.arm.features=default
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.expect.recovery_id=0x2d0b3d1909c7aae3c5a8dd61756413dc0fa95443000000000000000000000000
$ cat /proc/filesystems
nodev sysfs
nodev rootfs
nodev ramfs
nodev bdev
nodev proc
nodev cgroup
nodev tmpfs
nodev debugfs
nodev sockfs
nodev pipefs
nodev configfs
nodev devpts
ext3
ext2
ext4
vfat
msdos
iso9660
fuseblk
nodev fuse
nodev fusectl
nodev pstore
nodev selinuxfs
nodev mtd_inodefs
nodev functionfs
cat /proc/partitions
major minor #blocks name
254 0 474596 zram0
179 0 15267840 mmcblk0
179 1 3072 mmcblk0p1
179 2 5120 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 10240 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 16384 mmcblk0p7
179 8 16384 mmcblk0p8
179 9 8192 mmcblk0p9
179 10 10240 mmcblk0p10
179 11 512 mmcblk0p11
179 12 2048 mmcblk0p12
179 13 6144 mmcblk0p13
179 14 8192 mmcblk0p14
179 15 5120 mmcblk0p15
179 16 5120 mmcblk0p16
179 17 1024 mmcblk0p17
179 18 32768 mmcblk0p18
179 19 37888 mmcblk0p19
179 20 2768896 mmcblk0p20
179 21 409600 mmcblk0p21
179 22 11848192 mmcblk0p22
179 23 44032 mmcblk0p23
179 24 16384 mmcblk0p24
179 96 4096 mmcblk0rpmb
179 64 4096 mmcblk0boot1
179 32 4096 mmcblk0boot0
179 128 61071360 mmcblk1
179 129 61070336 mmcblk1p1
253 0 2725672 dm-0
$ uname -a
Linux localhost 3.18.35+ #1 SMP PREEMPT Fri May 12 01:32:41 CST 2017 armv7l
BTW mmcblk1 is 64GB sdcard formated in the same phone as portable (working normaly)
Please Root Nd install TWRP on moto C plus,,.
So any hope to get twrp for this soon?
Think S bro.. but This phone Is deffarent between ,, present Moto phones ,,. I was tried To unlock Bootloader ,,
failed
Traid Commands
"fastboot oem get_unlock_data"
"fastboot oem unlock"
"fastboot flashing unlock"
Error : unknown command
Some body say .. bootloader unlocking command plz
Both Ubuntu and Windows 10 is listing the phone in fastboot mode on command "fastboot devices"
But 'fastboot oem get_unlock_data' is not working
how to remove FRP........ MOTO C PLUS..........
jkkk88 said:
Here are some basic info I gathered after first touch of this phone.
First thing everybody will do is turning off very loud boot logo sound:
Setting - Sound:
Power up sound - off
How to enter specific android modes when starting phone
- buttons Power + VolumeUp
Boot menu items - Recovery/Bootloader (fastboot)/Normal
- select Boot menu item with VolumeUp, confirm item with VolumeDown
- enter Recovery menu from Recovery no command screen with Power + VolumeUp
- select Recovery menu item with VolumeUp and VolumeDown, confirm item with Power
- buttons Power + VolumeDown
Another Boot menu with not english characters/words (somebody translate it pls)
How to enter Safe mode (3rd party apps will not be loaded)
- press/hold Power button until power menu shows up during normal android session
- tap/hold Power off option
- choose OK to reboot in Safe mode
Here are also some data from filesystem.
BTW mmcblk1 is 64GB sdcard formated in the same phone as portable (working normaly)
Click to expand...
Click to collapse
But i am not enable to root my lenovo-motorola moto c plus / XT1723.. i can't even select my device in this xda app.. because there is no option of moto c plus.. so i can't even select my device..
Same problem with moto c ?
the motorola has a MTK chip
I guess MTK processor can be rooted directly by flashing SuperSU.. Not sure! I am not trying because it might brick the phone! :/
moto c plus
anybody have moto c plus..stock firmware
---------- Post added at 02:54 PM ---------- Previous post was at 02:53 PM ----------
abhi212b said:
I guess MTK processor can be rooted directly by flashing SuperSU.. Not sure! I am not trying because it might brick the phone! :/
Click to expand...
Click to collapse
anybody have moto c plus stock firmware?
---------- Post added at 02:55 PM ---------- Previous post was at 02:54 PM ----------
abhi212b said:
I guess MTK processor can be rooted directly by flashing SuperSU.. Not sure! I am not trying because it might brick the phone! :/
Click to expand...
Click to collapse
anybody have moto c plus stock firmware?
No bro.. not yet! otherwise, I would have tried rooting...
shr!pad said:
anybody have moto c plus..stock firmware
---------- Post added at 02:54 PM ---------- Previous post was at 02:53 PM ----------
anybody have moto c plus stock firmware?
---------- Post added at 02:55 PM ---------- Previous post was at 02:54 PM ----------
anybody have moto c plus stock firmware?
Click to expand...
Click to collapse
Try this bro : xt1721 16+2gb http://forum.gsmdevelopers.com/showthread.php?t=40275&highlight=Xt1721
hello the link works for the xt1723 16+1gb
or there is a root for this model
Hello all, I just got my hands on one of these for dirt cheap!, Very impressive battery life on it.
Is there a solution yet for rooting and or a custom rom being looked at?
John
Folks. How can I boot this phone in safe mode when I'm using full disk encryption ?
This phone got stuck in a "Lenovo" logo in the "second boot" phase, after I enter my pattern to unlock the phone. I suspect there is no free disk space left in memory and it fails to boot because of that -- Lenovo apps are not know for their quality and may not check the remaining space before trying to write something, so it makes some sense. Apart from that, phone looks ok: I can use some features from the lock screen like emergency calls (but haven't tried to actually complete a call to police, for obvious reasons), the screen shows the text message I configured and I can even take screenshots! (it was an accident, I have no idea why they left this feature there or where these files are saved when disk is encrypted).
I also wiped the caches from the recovery menu, but it didn't changed anything.
So, before resorting to a factory reset (and lose all data I haven't backed-up since December) I'll try to enter the safe mode and see if it boots. When I long-click the "Power off" from the lock screen, it changes to the "Reboot to safe mode" confirmation screen -- but it never shows the "Safe mode" text in the corner and I suppose it tries to boot normally. How can I put it in an actual safe mode?
Cannot Unlock
Sorry if this is the wrong place to post this...I'm new to 'droid hacking and was told that I have to unlock the bootloader before messing with custom recoveries.
Problem is, the command fastboot oem get_unlock_data returns FAILED (remote: unknown command) and I can't find anything anywhere to help with this. Does anyone know what's going on here?
it is possible to root without unlocking the bootloader I made them on motorcycle lenovo xt1723 1gb + 16gb with a tutorial xda
https://forum.xda-developers.com/an...de-flash-twrp-root-moto-c-plus-t3718668:bien:
Related
After hours reading tons of posts I got my ADP1 (Android Developer Phone1) rooted. My current setup is
Phone: ADP1 G1 | 32B | HTC Dream
Rom: COS-DS (http://forum.xda-developers.com/showthread.php?t=950765)
Recovery: Amon RA-Dream-v1.7.0 (http://forum.xda-developers.com/showthread.php?t=566669)
Radio: 2.22.28.25 (http://forum.xda-developers.com/showthread.php?t=831139)
SPL: 1.33.0013d (http://forum.xda-developers.com/showthread.php?t=831139)
microSD: 96MB swap + 512MB ext4 + FAT32
Code:
~ # free
total used free shared buffers
Mem: 112616 110680 1936 0 604
Swap: 23548 20476 3072
Total: 136164 131156 5008
# cat /proc/partitions
major minor #blocks name
7 0 668 loop0
7 1 4508 loop1
7 2 1760 loop2
31 0 256 mtdblock0
31 1 5120 mtdblock1
31 2 2560 mtdblock2
31 3 93184 mtdblock3
31 4 27648 mtdblock4
31 5 93952 mtdblock5
253 0 23552 zram0
179 0 992000 mmcblk0
179 1 398437 mmcblk0p1
179 2 500000 mmcblk0p2
179 3 93562 mmcblk0p3
~ # mount
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mtdblock3 on /system type yaffs2 (ro,relatime)
/dev/block/mtdblock5 on /data type yaffs2 (rw,nosuid,nodev,relatime)
/dev/block/mtdblock4 on /cache type yaffs2 (rw,nosuid,nodev,relatime)
/dev/block/loop0 on /system/lib/modules type squashfs (ro,relatime)
/dev/block/loop1 on /system/fonts type squashfs (ro,relatime)
/dev/block/loop2 on /system/xbin type squashfs (ro,relatime)
/dev/block/vold/179:2 on /sd-ext type ext4 (rw,nodev,noatime,nodiratime,barrier=1,data=ordered,noauto_da_alloc)
/dev/block/vold/179:1 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:1 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
I would like to know if there is any optimization?
Why should I do the customMTD? (http://forum.xda-developers.com/showthread.php?p=7061471#post7061471)
I'm not using ClockworksMOD as described by COS-DS. Should I? (http://forum.xda-developers.com/showthread.php?t=950765)
My partition order is different as described by COS-DS. Does it matter?
Using customMTD you could assign your cache memory (around 27MB) as internal memory.
Clockwork, I don't like much, but this is my personal opinion. Advantage(?) of Clockwork: you can flash unsigned zip files.
Partition layout probably matters, because on system startup there is a chance, that they are not mounted.
Sent from my Gingerbread on Dream using XDA App
I found customMTD to be difficult to install (I did it with firerat's Magpie ROM), but worth it for the extra space it gave me. Prior to, I was getting low on disk space messages and random shutdowns galore.
I don't recall why, but during my research I recall learning that Amon-Ra is stable and Clockwork isn't if you're going to use customMTD.
Please if someone have, upload your backedup mmcblk0_start with partition configuration data from mmcblk0p8, my tablet has only 7 partitions although My flash.cfg makes 8 partitions and last one is mmcblk0p8 with size FFFF... But after flashing it I get always same thing- when i boot into ubuntu and check my partitions I get only last one mmcblk0p7 who is data, so I can't flash second boot image and make dualboot+recovery. On picasso.init.rc i get just some words and digits, so I can not do anything with it, I tryed all EUU's, but get the same. So please if you can, upload it, if it wery hard then jus system.img it will be better than nothing. Thanks and sorry for bad English.
There is no such partition. It is only defined this way in nvflash flash.cfg but whole space is taken by the user data parition, which takes as much space as it can get (depending on emmc size) and this last one is not actually created.
yaworski said:
There is no such partition. It is only defined this way in nvflash flash.cfg but whole space is taken by the user data parition, which takes as much space as it can get (depending on emmc size) and this last one is not actually created.
Click to expand...
Click to collapse
So what I need to do that I can flash second boot image, and why mmcblk0p7 in nvflash .cfg is about just 7 or more megabytes? And http://projects.pappkartong.se/a500/ do you read it, in that table is write 8 partitions and mmcblk0p8 is data, then it is strange. Thanks for reply. Sorry for bad english.
Tautvaldas said:
Please if someone have, upload your backedup mmcblk0_start with partition configuration data from mmcblk0p8, my tablet has only 7 partitions although My flash.cfg makes 8 partitions and last one is mmcblk0p8 with size FFFF... But after flashing it I get always same thing- when i boot into ubuntu and check my partitions I get only last one mmcblk0p7 who is data, so I can't flash second boot image and make dualboot+recovery. On picasso.init.rc i get just some words and digits, so I can not do anything with it, I tryed all EUU's, but get the same. So please if you can, upload it, if it wery hard then jus system.img it will be better than nothing. Thanks and sorry for bad English.
Click to expand...
Click to collapse
If you don't have a mmcblk0p8 I would be interested to see what /proc/partitions and /proc/mounts looks like.
With mmcblk0p8:
Code:
$ cat /proc/partitions
major minor #blocks name
179 0 31259648 mmcblk0
179 1 5120 mmcblk0p1
179 2 8192 mmcblk0p2
179 3 614400 mmcblk0p3
179 4 1253376 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 102400 mmcblk0p6
179 7 10240 mmcblk0p7
179 8 29253632 mmcblk0p8
$
$ cat /proc/mounts
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p3 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p8 /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p4 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p6 /system/vendor ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
$
The partition table parsed from raw dump of /dev/block/mmcblk:
Code:
nvtegrapart: #0 [BCT ] start=0 size=6144 (6)
nvtegrapart: #1 [PT ] start=2048 size=1024 (1)
nvtegrapart: #2 [EBT ] start=3072 size=8192 (8)
nvtegrapart: #3 [GP1 ] start=11264 size=2048 (2)
nvtegrapart: #4 [SOS ] start=13312 size=10240 (10)
nvtegrapart: #5 [LNX ] start=23552 size=16384 (16)
nvtegrapart: #6 [APP ] start=39936 size=1228800 (1200)
nvtegrapart: #7 [CAC ] start=1268736 size=2506752 (2448)
nvtegrapart: #8 [MSC ] start=3775488 size=8192 (8)
nvtegrapart: #9 [FLX ] start=3783680 size=204800 (200)
nvtegrapart: #10 [AKB ] start=3988480 size=20480 (20)
nvtegrapart: #11 [UDA ] start=4008960 size=58507264 (57136)
nvtegrapart: #12 [GPT ] start=62516224 size=1024 (1)
Try the thread called rollback from ics leak, it has a rooted 3.2 image so uh, good luck with that
Sent from my A501 using xda app-developers app
Wery strange now, I got mmcblk0p8, but when I flash second boot image then my data is gone (can't boot into tegraowners 170 ROM) it says that can't use data partition and need data reset, after that it is same thing again. In root 3.2.1 is same as EUUs, same,.cfg, maybe I'm doing something wrong. Sorry for bad english. Now I have a501 stock ROM in my a500 and I will try flash second boot again. And thanks for replies.
Taks for help, it seems working now, maybe I should check what ROM I am using next time thanks. Sorry for bad english.
Haha i don't know who your referring to but uh if it worked , your welcome
Sent from my A501 using xda app-developers app
Hi can anyone dump the recovery.img off thier galaxy s3mini. Im going to try and make a cwm but need this .img. i think its easier for people that a rooted there phones. Thanks in advance
Sent from my GT-I9300 using xda premium
you can get it sinply by extract recovery.img from the firmware.
avicohh said:
you can get it sinply by extract recovery.img from the firmware.
Click to expand...
Click to collapse
Its not in the firmware unfortunately
Sent from my GT-I9300 using xda premium
No it isn't. I already tried and failed.
Maybe we can extract it through ADB SHELL.
Currently i get:
$ cat /proc/mounts
cat /proc/mounts
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /dev/shm tmpfs rw,relatime,mode=755,gid=1000 0 0
none /debug debugfs rw,relatime 0 0
/dev/block/mmcblk0p22 /system ext4 ro,noatime,errors=panic,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p12 /modemfs ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p23 /cache ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p11 /efs ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p24 /preload ext4 ro,noatime,errors=panic,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p25 /data ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/mmcblk0p19 /mnt/.lfs j4fs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
$
But which one is the recovery ???
Try modem.
quendil said:
Maybe we can extract it through ADB SHELL.
Currently i get:
$ cat /proc/mounts
cat /proc/mounts
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /dev/shm tmpfs rw,relatime,mode=755,gid=1000 0 0
none /debug debugfs rw,relatime 0 0
/dev/block/mmcblk0p22 /system ext4 ro,noatime,errors=panic,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p12 /modemfs ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p23 /cache ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p11 /efs ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p24 /preload ext4 ro,noatime,errors=panic,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p25 /data ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/mmcblk0p19 /mnt/.lfs j4fs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
$
But which one is the recovery ???
Click to expand...
Click to collapse
Lol i dont have a clue. Could you try downloading this tool http://forum.xda-developers.com/showthread.php?t=1703488 its for normal galaxy s3. When installed click any firmware version and then select option to make nandroid backup through adb to computer. You need to have root to do it. Thanks again
Sent from my GT-I9300 using xda premium
I don't think recovery partition is mounted in normal boot. Try adb in recovery mode?
Skickat från min GT-P7500 via Tapatalk 2
---------- Post added at 01:30 PM ---------- Previous post was at 12:50 PM ----------
In terminal, cat /proc/partition gives me:
$ export PATH=/data/local/bin:$PATH
$ su
# cat /proc/partitions
major minor #blocks name
7 0 14585 loop0
7 1 2111 loop1
7 2 4190 loop2
7 3 5229 loop3
7 4 47849 loop4
7 5 2111 loop5
7 6 4190 loop6
7 7 13545 loop7
179 0 7634944 mmcblk0
179 1 128 mmcblk0p1
179 2 384 mmcblk0p2
179 3 1024 mmcblk0p3
179 4 1024 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 1024 mmcblk0p10
179 11 16384 mmcblk0p11
179 12 16384 mmcblk0p12
179 13 16384 mmcblk0p13
179 14 51200 mmcblk0p14
179 15 64 mmcblk0p15
179 16 14336 mmcblk0p16
179 17 2048 mmcblk0p17
179 18 2048 mmcblk0p18
179 19 16384 mmcblk0p19
179 20 16384 mmcblk0p20
179 21 16384 mmcblk0p21
179 22 1228800 mmcblk0p22
179 23 860160 mmcblk0p23
179 24 327680 mmcblk0p24
179 25 4945920 mmcblk0p25
179 64 2048 mmcblk0boot1
179 32 2048 mmcblk0boot0
179 96 32113664 mmcblk1
179 97 16056320 mmcblk1p1
179 98 16048128 mmcblk1p2
254 0 14584 dm-0
254 1 2110 dm-1
254 2 4189 dm-2
254 3 5229 dm-3
254 4 47848 dm-4
254 5 2110 dm-5
254 6 4189 dm-6
254 7 13545 dm-7
7 8 21861 loop8
254 8 21861 dm-8
7 9 29138 loop9
254 9 29137 dm-9
7 10 13545 loop10
254 10 13545 dm-10
7 11 2111 loop11
254 11 2110 dm-11
7 12 5229 loop12
254 12 5229 dm-12
7 13 55125 loop13
254 13 55125 dm-13
7 14 2111 loop14
254 14 2110 dm-14
7 15 15624 loop15
254 15 15624 dm-15
#
Skickat från min GT-I8190
ops.. i forgot something.
the recovery built in the kernal, its more complicated then S3.
C:\Android>adb reboot recovery
C:\Android>adb shell
$ cat /proc/mounts
cat /proc/mounts
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/mmcblk0p1 /mnt/.lfs j4fs rw,relatime 0 0
/dev/block/mmcblk0p22 /system ext4 rw,nodev,noatime,nodiratime,barrier=1,data=ordered 0 0
$
This is what I get in recovery mode. Hope it helps
Edit: Or not, damn it!
avicohh said:
ops.. i forgot something.
the recovery built in the kernal, its more complicated then S3.
Click to expand...
Click to collapse
Why do they have to make things so confusing. I dont think im able to do it now
Sent from my GT-I9300 using xda premium
You were right, it is in the kernel. I've managed to disassemble boot.img and found a recovery in there. This indeed complicates things.
Benzonat0r said:
You were right, it is in the kernel. I've managed to disassemble boot.img and found a recovery in there. This indeed complicates things.
Click to expand...
Click to collapse
Oh, damn! We need someone like chainfire to get this device goin' custom!
Skickat från min GT-P7500 via Tapatalk 2
Benzonat0r said:
You were right, it is in the kernel. I've managed to disassemble boot.img and found a recovery in there. This indeed complicates things.
Click to expand...
Click to collapse
Can you extract that recovery.img i will then try and add cwm to it. What operating system are yiu using to unpack boot.img?
Sent from my GT-I9300 using xda premium
Windows 7 emulating Linux via Cygwin + dsixda's Android Kitchen
This it an extracted boot.img, the recovery is in here.
Benzonat0r said:
Windows 7 emulating Linux via Cygwin + dsixda's Android Kitchen
This it an extracted boot.img, the recovery is in here.
Click to expand...
Click to collapse
Ahh yeah ive dont that but there is no recovery.img in there
Sent from my GT-I9300 using xda premium
There's no image in there no, but I think it's integrated in it, just like in Galaxy Ace 2 there's no recovery.img in the stock firmware but the recovery its packed directly in kernel.bin
Benzonat0r said:
There's no image in there no, but I think it's integrated in it, just like in Galaxy Ace 2 there's no recovery.img in the stock firmware but the recovery its packed directly in kernel.bin
Click to expand...
Click to collapse
Yeah thats what i thought. Looks like im going to have to set up ubuntu to create it. Not many tools made for windows. Hopefully can get it set up in the next week. Dont hold me to it though as ive never done anything like this before. I usually do theming over at the galaxy s3 intetnational forum. Only problem is people are going to have to try it out for me if i can get it together as my girlfriend has the s3mini and doesnt like me doing thing to her phone.
Sent from my GT-I9300 using xda premium
Hahahaha that's totally understandable man girls are like that don't sweat it. We'd appreciate that very much.
Thing is that I don't have a spare hard drive to install Ubuntu and my disk space is nearly full, around 8 gigs free of 2TB of space.
hey i build a cwm version on koushik-lion for Galaxy S3 mini (alias Golden) ... its cwm recovery 6.0.2.7 Touch recovery.img - 6.10 MB but i don´t know how i can test it..... because its my first samsung device and I don´t want to brick it .... can i try "fastboot flash recovery recovery.img" or .... I hope someone knows a way ...
ps: link to recovery-builder: http://jenkins.cyanogenmod.com/job/recovery/14184/
Hi
To cut a long story short I went about trying to extend my system partition using GNU Parted and it has failed terribly to the point I have bricked my tablet. At the moment I have managed to execute the command
Code:
fastboot boot twrp-3.2.3-0-flo.img
but this is running from RAM as I'm unable to flash any of the partitions as they are "missing".
This is the my original partition table:-
Code:
Number Start End Size File system Name Flags
1 67108864B 156745727B 89636864B fat16 radio
2 201326592B 204472319B 3145728B modemst1
3 204472320B 207618047B 3145728B modemst2
4 268435456B 283795455B 15360000B ext4 persist
5 335544320B 336343039B 798720B m9kefs1
6 336343040B 337141759B 798720B m9kefs2
7 402653184B 403451903B 798720B m9kefs3
8 403451904B 406597631B 3145728B fsg
9 469762048B 471298047B 1536000B sbl1
10 471298048B 472834047B 1536000B sbl2
11 472834048B 474931199B 2097152B sbl3
12 474931200B 480174079B 5242880B aboot
13 480174080B 480698367B 524288B rpm
14 536870912B 553648127B 16777216B boot
15 603979776B 604504063B 524288B tz
16 604504064B 604505087B 1024B pad
17 604505088B 606041087B 1536000B sbl2b
18 606041088B 608138239B 2097152B sbl3b
19 608138240B 613381119B 5242880B abootb
20 613381120B 613905407B 524288B rpmb
21 613905408B 614429695B 524288B tzb
22 671088640B 1551892479B 880803840B ext2 system
23 1551892480B 2139095039B 587202560B ext4 cache
24 2147483648B 2148532223B 1048576B misc
25 2214592512B 2225078271B 10485760B recovery
26 2281701376B 2281709567B 8192B DDR
27 2281709568B 2281717759B 8192B ssd
28 2281717760B 2281718783B 1024B m9kefsc
29 2348810240B 2348843007B 32768B metadata
30 2415919104B 15468576255B 13052657152B ext4 userdata
From some reading on the internet Linux can only have 4 primary partitons. All I know is that I have 30 partitions and I don't know what partition type to set them to; primary, logical and extended.
I've played around with the three partition types but I get an error message saying "Too many primary partitions".
Could someone shine some light here please?
Many thanks
Will
Bump
Bump
Don't know if it helps, but here is some partition info from stock flo:
Code:
[email protected]:/ $ cat /proc/partitions
major minor #blocks name
179 0 15388672 mmcblk0
179 1 87536 mmcblk0p1
179 2 3072 mmcblk0p2
179 3 3072 mmcblk0p3
179 4 15000 mmcblk0p4
179 5 780 mmcblk0p5
179 6 780 mmcblk0p6
179 7 780 mmcblk0p7
179 8 3072 mmcblk0p8
179 9 1500 mmcblk0p9
179 10 1500 mmcblk0p10
179 11 2048 mmcblk0p11
179 12 5120 mmcblk0p12
179 13 512 mmcblk0p13
179 14 16384 mmcblk0p14
179 15 512 mmcblk0p15
179 16 1 mmcblk0p16
179 17 1500 mmcblk0p17
179 18 2048 mmcblk0p18
179 19 5120 mmcblk0p19
179 20 512 mmcblk0p20
179 21 512 mmcblk0p21
179 22 860160 mmcblk0p22
179 23 573440 mmcblk0p23
179 24 1024 mmcblk0p24
179 25 10240 mmcblk0p25
179 26 8 mmcblk0p26
179 27 8 mmcblk0p27
179 28 1 mmcblk0p28
179 29 32 mmcblk0p29
179 30 13029359 mmcblk0p30
127|[email protected]:/ $ df
Filesystem Size Used Free Blksize
/dev 903.9M 76.0K 903.8M 4096
/sys/fs/cgroup 903.9M 12.0K 903.9M 4096
/mnt 903.9M 0.0K 903.9M 4096
/system 827.8M 823.8M 4.0M 4096
/cache 551.7M 10.6M 541.2M 4096
/data 12.2G 5.1G 7.1G 4096
/persist 14.5M 4.2M 10.2M 4096
/storage 903.9M 0.0K 903.9M 4096
/mnt/runtime/default/emulated: Permission denied
/storage/emulated 12.2G 5.1G 7.1G 4096
/mnt/runtime/read/emulated: Permission denied
/mnt/runtime/write/emulated: Permission denied
1|[email protected]:/ $ mount
rootfs / rootfs ro,seclabel,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,seclabel,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,nomblk_io_submit,errors=panic,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,nomblk_io_submit,errors=panic,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,nodelalloc,data=ordered 0 0
tmpfs /storage tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
/dev/fuse /mnt/runtime/default/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/read/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/write/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
This is my first foray into Wear OS. I seem to always end up with some locked down devices. It Always teaches me a thing or two though! Because all is not lost it seems. I've been trying to compile what I can see from the device into one spot. Information on this series of watches is spread out all over the place. Let me explain what I've found out about The MK Access Bradshaw, that makes me think there is a light at the end of the tunnel. If you have experience with these watches or the Fossil Q sister series, please share. Links to the Fossil Q firmware would be amazing at this point.
Code:
----------------------------------------------
Michael Kors Access Bradshaw Device Info
----------------------------------------------
MODEL: MKT5006
CHIPSET: SD Wear 2100
RAM: 512 MB
STORAGE: 4 GB
SCREEN: 1.4 inch
RESOLUTION: 320x290 pixels (309 ppi)
WEAR OS: 2.6
BUILD: fossil/gar/gar
8.0.0/OWD6.180205.022/53356216
user/release-keys
----------------------------------------------
1. FASTBOOT MODE
[adb reboot bootloader]
----------------------------------------------
PRODUCT_NAME - gar
VARIANT - PFW2
PHASE - SA
BOOTLOADER VERSION - GAR.EINSTEIN_0.083.00
BASEBAND VERSION - N/A
HW_CONFIG - 1
SERIAL NUMBER - XXXXXXXXX (9 Digits)
** A Direct Pin Connection is Needed
to utilize the Fastboot Protocol.
** Fastboot appears active and functional
and only missing a physical connection
** A Pin Connection can be made.
Now, when we finally make it into the recovery mode, we are presented with standard Android Oreo Recovery options. Including the Recovery Logs. It is in these logs I have found A LOT of Information. They have the Log Daemon configured to 'eng'. But I noticed that simply using the 'adb reboot recovery' command, would start recovery mode but never show the recovery menu before rebooting back to the system.
The recovery menu only ever appears for me when I boot into recovery mode from fastboot mode.
Code:
----------------------------------------------
2. RECOVERY MODE
[Boot to Recovery from Bootloader]
----------------------------------------------
* The Recovery Log displays the Recovery FSTAB
* Build.Prop Contents Can also been seen.
* ro.logd.kernel=eng
It is very verbose. But without actual access to the cache partition there is no way to copy & paste, or pull the logs from the watch. My "last_log" entry is from when I updated the device from WearOS 2.2 to version 2.6. In that log, so much of the nitty gritty partition details are revealed, here are a few I've wrote down so far:
Code:
/cache/recovery/last_log:
-----------------------------
0 /system ext4 /dev/block/platform/soc/7824900.sdhci/by-name/system 0
1 /cache ext4 /dev/block/platform/soc/7824900.sdhci/by-name/cache 0
2 /data ext4 /dev/block/platform/soc/7824900.sdhci/by-name/userdata -16384
3 /sdcard vfat /dev/block/mmcblk1p1 0
4 /boot emmc /dev/block/platform/soc/7824900.sdhci/by-name/boot 0
5 /recovery emmc /dev/block/platform/soc/7824900.sdhci/by-name/recovery 0
6 /misc emmc /dev/block/platform/soc/7824900.sdhci/by-name/misc 0
7 /oem ext4 /dev/block/platform/soc/7824900.sdhci/by-name/oem 0
8 /tmp ramdisk ramdisk 0
ro.sys.fw.use_trim_settings=true
ro.sys.fw.trim_enable_memory=1073741824
ro.sys.fw.trim_empty_percent=100
ro.sys.fw.trim_cache_percent=100
ro.sys.fw.empty_app_percent=50
ro.sys.umsdirtyratio=20
ro.boot.hardware=gar
ro.boot.baseband=apq
ro.boot.console=null
ro.boot.ceibootmode=0
ro.boot.bootdevice=7824900.sdhci
ro.board.platform=msm8909
ro.build.host=abfarm648
ro.product.cpu.abi=armeabi-v7a
ro.boot.verifiedbootstate=green
ro.boot.authorized_kernel=true
ro.logd.kernel=eng
ro.bootimage.build.date=Thu Aug 9 00:39:05 UTC 2018
[11.364486]Verifying update package...
I:comment is 1476 bytes; signature is 1458 bytes from end.
I:signature (offset: 10127db, length: 5ac):
That log continues on with all of the signature, but on the watch screen it is quite a few pages long. But continues on during the whole verification process. And it really does say in so many words what it is doing and when. The log explains exactly what data it is putting where, and where the developers forgot to set expected values that the system must choose a default for.
What I need to do now is go through the log with an OCR App that can take pictures of the screen and extract the text. I believe the two most recent log files on my watch could explain just how to get at the bootloader & kernel. They definitely tell you where to go find the eFuse. Because even though it has Green Verified Boot Status, the boot log shows a few things for verified boot were never actually implemented. I'm working on getting these logs now.
Enable Developer Options:
Settings > System > About > Tap Build Number until it unlocks.
Connecting to ADB:
1.) Enable Developer Options
2.) Disable Bluetooth
3.) Connect Device to Wi-Fi
4.) Settings > Dev Options > ADB Debugging
5.) Settings > Dev Options > Debug Over Wi-Fi
6.) From a command line, start the adb server and then use this command with the watch's wifi ip address: "adb connect <ip_address>:5555"
7.) Run command "adb devices" and hit the yes button on the watch face to accept the connection.
Replacement 1st Gen Fossil Watch Chargers (2016-2017 Watches):
1.) 1st Party Marc Jacob's MJT0001/MKT0001
2.) 3rd Party Soarking Fossil Charger
Once I find a repair manual or schematic to this thing, I think I'm going to work on creating a cable to connect to the board for fastboot access.
MEMINFO
Code:
MemTotal: 455000 kB
MemFree: 8228 kB
MemAvailable: 179528 kB
Buffers: 2216 kB
Cached: 179400 kB
SwapCached: 7136 kB
Active: 153580 kB
Inactive: 154504 kB
Active(anon): 63348 kB
Inactive(anon): 64340 kB
Active(file): 90232 kB
Inactive(file): 90164 kB
Unevictable: 256 kB
Mlocked: 256 kB
SwapTotal: 338936 kB
SwapFree: 222520 kB
Dirty: 0 kB
Writeback: 0 kB
AnonPages: 125548 kB
Mapped: 78400 kB
Shmem: 1216 kB
Slab: 41732 kB
SReclaimable: 13440 kB
SUnreclaim: 28292 kB
KernelStack: 8544 kB
PageTables: 20392 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 566436 kB
Committed_AS: 26409868 kB
VmallocTotal: 499712 kB
VmallocUsed: 95544 kB
VmallocChunk: 291668 kB
MOUNTS
Code:
rootfs / rootfs ro,seclabel,size=205932k,nr_inodes=51483 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=221356k,nr_inodes=55339,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime,gid=3009,hidepid=2 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,seclabel,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt tmpfs rw,seclabel,relatime,size=221356k,nr_inodes=55339,mode=755,gid=1000 0 0
none /config configfs rw,relatime 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
pstore /sys/fs/pstore pstore rw,seclabel,relatime 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
/dev/block/platform/soc/7824900.sdhci/by-name/system /system ext4 ro,seclabel,relatime,discard 0 0
/dev/block/platform/soc/7824900.sdhci/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/platform/soc/7824900.sdhci/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/platform/soc/7824900.sdhci/by-name/modem /firmware vfat ro,context=u:object_r:firmware_file:s0,relatime,uid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/platform/soc/7824900.sdhci/by-name/oem /oem ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/platform/soc/7824900.sdhci/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,errors=panic,data=ordered 0 0
tmpfs /storage tmpfs rw,seclabel,relatime,size=221356k,nr_inodes=55339,mode=755,gid=1000 0 0
/data/media /mnt/runtime/default/emulated sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=1015,multiuser,mask=6,derive_gid 0 0
/data/media /storage/emulated sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=1015,multiuser,mask=6,derive_gid 0 0
/data/media /mnt/runtime/read/emulated sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,multiuser,mask=23,derive_gid 0 0
/data/media /mnt/runtime/write/emulated sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,multiuser,mask=7,derive_gid 0 0
PARTITIONS
Code:
major - minor - #blocks name
-------------------------------------
254 - 0 - 262144 zram0
179 - 0 - 3817472 mmcblk0
179 - 1 - 65536 mmcblk0p1
179 - 2 - 512 mmcblk0p2
179 - 3 - 512 mmcblk0p3
179 - 4 - 512 mmcblk0p4
179 - 5 - 512 mmcblk0p5
179 - 6 - 768 mmcblk0p6
179 - 7 - 768 mmcblk0p7
179 - 8 - 1024 mmcblk0p8
179 - 9 - 1536 mmcblk0p9
179 - 10 - 1536 mmcblk0p10
179 - 11 - 1536 mmcblk0p11
179 - 12 - 1 mmcblk0p12
179 - 13 - 1024 mmcblk0p13
179 - 14 - 8 mmcblk0p14
179 - 15 - 10240 mmcblk0p15
179 - 16 - 32 mmcblk0p16
179 - 17 - 16 mmcblk0p17
179 - 18 - 32768 mmcblk0p18
179 - 19 - 32768 mmcblk0p19
179 - 20 - 512 mmcblk0p20
179 - 21 - 1024 mmcblk0p21
179 - 22 - 1024 mmcblk0p22
179 - 23 - 32768 mmcblk0p23
179 - 24 - 32768 mmcblk0p24
179 - 25 - 1024 mmcblk0p25
179 - 26 - 512 mmcblk0p26
179 - 27 - 512 mmcblk0p27
179 - 28 - 16384 mmcblk0p28
179 - 29 - 256 mmcblk0p29
179 - 30 - 256 mmcblk0p30
179 - 31 - 256 mmcblk0p31
259 - 0 - 256 mmcblk0p32
259 - 1 - 65536 mmcblk0p33
259 - 2 - 655360 mmcblk0p34
259 - 3 - 2310127 mmcblk0p35
179 - 32 - 4096 mmcblk0rpmb
DF Utility
Code:
Filesystem 1K-blocks Used Available Use% Mounted on
---------------------------------------------------------------------------
rootfs 205932 3460 202472 2% /
tmpfs 221356 532 220824 1% /dev
tmpfs 221356 0 221356 0% /mnt
/dev/block/mmcblk0p34 645056 630224 0 100% /system
/dev/block/mmcblk0p33 60400 1632 57460 3% /cache
/dev/block/mmcblk0p1 65488 22240 43248 34% /firmware
/dev/block/mmcblk0p28 12016 64 11628 1% /oem
/dev/block/mmcblk0p35 2237680 690400 1530896 32% /data
/data/media 2237680 690400 1530896 32% /storage/emulated
Since making this thread, this update no longer seems to be available. I think I am also leaving XDA, my words here have caused me too much trouble.