Register Guidelines E-Books Search Today's Posts Mark Forums Read

Go Back   MobileRead Forums > E-Book Readers > Onyx Boox

Notices

Reply
 
Thread Tools Search this Thread
Old 01-20-2020, 07:34 PM   #31
diabl0w
Connoisseur
diabl0w will become famous soon enoughdiabl0w will become famous soon enoughdiabl0w will become famous soon enoughdiabl0w will become famous soon enoughdiabl0w will become famous soon enoughdiabl0w will become famous soon enough
 
Posts: 87
Karma: 527
Join Date: Sep 2019
Device: Max3
Quote:
Originally Posted by nystagmus View Post
Would this root work on the note2? it is supposed to be similar internaly, isnt it?
does it have unlocked bootloader?
diabl0w is offline   Reply With Quote
Old 01-21-2020, 06:14 AM   #32
mbarvian
Junior Member
mbarvian began at the beginning.
 
Posts: 2
Karma: 10
Join Date: Aug 2019
Device: none
Thanks a lot for posting this! Did you ever find a safer method to regain the split screen functionality? I'm also really hoping to get that working.
mbarvian is offline   Reply With Quote
Old 01-21-2020, 08:37 AM   #33
Waiting4somethin
Addict
Waiting4somethin is a jewel in the roughWaiting4somethin is a jewel in the roughWaiting4somethin is a jewel in the roughWaiting4somethin is a jewel in the roughWaiting4somethin is a jewel in the roughWaiting4somethin is a jewel in the roughWaiting4somethin is a jewel in the roughWaiting4somethin is a jewel in the roughWaiting4somethin is a jewel in the roughWaiting4somethin is a jewel in the roughWaiting4somethin is a jewel in the rough
 
Posts: 249
Karma: 7162
Join Date: Dec 2017
Device: Wexler Flex One, NookST, n96ml+
I wish you could run linux natively on the device. Perhaps you can? It's an expensive thing to mess around with though.

Edit: something like this perhaps: https://unix.stackexchange.com/quest...android-device

But I've never tried something like that. And I don't own one.

Last edited by Waiting4somethin; 01-22-2020 at 07:54 AM.
Waiting4somethin is offline   Reply With Quote
Old 01-22-2020, 10:50 AM   #34
uniqdom
Member
uniqdom knows what time it isuniqdom knows what time it isuniqdom knows what time it isuniqdom knows what time it isuniqdom knows what time it isuniqdom knows what time it isuniqdom knows what time it isuniqdom knows what time it isuniqdom knows what time it isuniqdom knows what time it isuniqdom knows what time it is
 
Posts: 17
Karma: 2270
Join Date: Jul 2013
Device: Boox Max3
I'm also interested in running a native full GNU/Linux distro, or a custom ROM like LineageOS. I'm not an expert, I would like to help and learn. If you have more information about our device or some thoughts about how to continue please send it.


I have been getting a bit of information, maybe it was posted in another thread. We have the .config file to build a kernel (but we are missing, at least, the cyttsp5 touchscreen source), we have the DTB and the DTS (hopefully in a usable form).

Mido Device (Xiaomi Redmi note 4) have the same SOC that our max3 have. This device has LineageOS 16.0 support. I have this phone and I have built LOS 16 for it, it works fine. I installed Device Info HW app to get information of both devices. Hw info shown in that app in images uploaded here.

Kernel version
Code:
Max3:/ $ uname -a
Linux localhost 3.18.120-perf-g09985b4 #62 SMP PREEMPT Wed Oct 23 21:53:20 CST 2019 aarch64
The vendor's config file that was used to build 3.18.120-perf-g09985b4 is attached to his post. It was taken by running "zcat /proc/config.gz" in max3


I crossed my fingers and tried to compile a vanilla 3.18.120 Linux kernel, but It ended with errors:
Code:
make[2]: *** No rule to make target 'firmware/cyttsp5/cyttsp5_fw_pid00_max3.bin', needed by 'firmware/cyttsp5/cyttsp5_fw_pid00_max3.bin.gen.o'.  Stop.
Looking at the .config file, the problem is that we need the sources of cyttsp5 (touchscreen):
Code:
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=y
CONFIG_FIRMWARE_IN_KERNEL=y
CONFIG_EXTRA_FIRMWARE="cyttsp5/cyttsp5_fw_pid00_max3.bin cyttsp5/cyttsp5_fw_note2.bin"
CONFIG_EXTRA_FIRMWARE_DIR="firmware"
Other problems may arise later. The vendor (Onyx or Boox, or maybe both) MUST release the source code of the kernel to comply with the GPLv2. And also, as I understand, by mixing GPL and non GPL they might be in troubles.

The following warning was taken from https://cateee.net/lkddb/web-lkddb/EXTRA_FIRMWARE.html
WARNING: If you include additional firmware files into your binary kernel image that are not available under the terms of the GPL, then it may be a violation of the GPL to distribute the resulting image since it combines both GPL and non-GPL work. You should consult a lawyer of your own before distributing such an image.


A bit about the SOC/CPU: MSM8953 Octa-core ARM Cortex-A53 2GHz 64-bit Processor (Snapdragon 625)
Code:
Max3:/ $ cat /proc/cpuinfo
processor    : 0
BogoMIPS    : 38.40
Features    : fp asimd evtstrm aes pmull sha1 sha2 crc32
CPU implementer    : 0x41
CPU architecture: 8
CPU variant    : 0x0
CPU part    : 0xd03
CPU revision    : 4

processor    : 1
BogoMIPS    : 38.40
Features    : fp asimd evtstrm aes pmull sha1 sha2 crc32
CPU implementer    : 0x41
CPU architecture: 8
CPU variant    : 0x0
CPU part    : 0xd03
CPU revision    : 4

processor    : 2
BogoMIPS    : 38.40
Features    : fp asimd evtstrm aes pmull sha1 sha2 crc32
CPU implementer    : 0x41
CPU architecture: 8
CPU variant    : 0x0
CPU part    : 0xd03
CPU revision    : 4

processor    : 3
BogoMIPS    : 38.40
Features    : fp asimd evtstrm aes pmull sha1 sha2 crc32
CPU implementer    : 0x41
CPU architecture: 8
CPU variant    : 0x0
CPU part    : 0xd03
CPU revision    : 4

processor    : 4
BogoMIPS    : 38.40
Features    : fp asimd evtstrm aes pmull sha1 sha2 crc32
CPU implementer    : 0x41
CPU architecture: 8
CPU variant    : 0x0
CPU part    : 0xd03
CPU revision    : 4

processor    : 5
BogoMIPS    : 38.40
Features    : fp asimd evtstrm aes pmull sha1 sha2 crc32
CPU implementer    : 0x41
CPU architecture: 8
CPU variant    : 0x0
CPU part    : 0xd03
CPU revision    : 4

processor    : 6
BogoMIPS    : 38.40
Features    : fp asimd evtstrm aes pmull sha1 sha2 crc32
CPU implementer    : 0x41
CPU architecture: 8
CPU variant    : 0x0
CPU part    : 0xd03
CPU revision    : 4

processor    : 7
BogoMIPS    : 38.40
Features    : fp asimd evtstrm aes pmull sha1 sha2 crc32
CPU implementer    : 0x41
CPU architecture: 8
CPU variant    : 0x0
CPU part    : 0xd03
CPU revision    : 4

Hardware    : Qualcomm Technologies, Inc MSM8953
build.prop:
Code:
adb pull /system/build.prop
cat build.prop
[DEVICE_PROVISIONED]: [1]
[af.fast_track_multiplier]: [1]
[audio.deep_buffer.media]: [true]
[audio.offload.min.duration.secs]: [30]
[audio.offload.video]: [true]
[av.debug.disable.pers.cache]: [1]
[dalvik.vm.appimageformat]: [lz4]
[dalvik.vm.dex2oat-Xms]: [64m]
[dalvik.vm.dex2oat-Xmx]: [512m]
[dalvik.vm.dex2oat-minidebuginfo]: [true]
[dalvik.vm.dexopt.secondary]: [true]
[dalvik.vm.heapgrowthlimit]: [192m]
[dalvik.vm.heapmaxfree]: [8m]
[dalvik.vm.heapminfree]: [4m]
[dalvik.vm.heapsize]: [512m]
[dalvik.vm.heapstartsize]: [16m]
[dalvik.vm.heaptargetutilization]: [0.75]
[dalvik.vm.image-dex2oat-Xms]: [64m]
[dalvik.vm.image-dex2oat-Xmx]: [64m]
[dalvik.vm.isa.arm.features]: [default]
[dalvik.vm.isa.arm.variant]: [cortex-a53]
[dalvik.vm.isa.arm64.features]: [default]
[dalvik.vm.isa.arm64.variant]: [generic]
[dalvik.vm.stack-trace-dir]: [/data/anr]
[dalvik.vm.usejit]: [true]
[dalvik.vm.usejitprofiles]: [true]
[debug.atrace.tags.enableflags]: [0]
[debug.egl.hw]: [0]
[debug.enable.sglscale]: [1]
[debug.force_rtl]: [0]
[debug.gralloc.enable_fb_ubwc]: [0]
[debug.mdpcomp.logs]: [0]
[debug.sf.enable_hwc_vds]: [1]
[debug.sf.hw]: [0]
[debug.sf.latch_unsignaled]: [1]
[debug.sf.recomputecrop]: [0]
[dev.bootcomplete]: [1]
[dev.pm.dyn_samplingrate]: [1]
[hwservicemanager.ready]: [true]
[init.svc.adbd]: [running]
[init.svc.adsprpcd]: [running]
[init.svc.alarm-hal-1-0]: [running]
[init.svc.audioserver]: [running]
[init.svc.bootanim]: [stopped]
[init.svc.cameraserver]: [running]
[init.svc.cnss-daemon]: [running]
[init.svc.display-color-hal-1-0]: [running]
[init.svc.dpmQmiMgr]: [running]
[init.svc.dpmd]: [running]
[init.svc.drm]: [running]
[init.svc.energy-awareness]: [stopped]
[init.svc.flash_recovery]: [stopped]
[init.svc.gatekeeper-1-0]: [running]
[init.svc.gatekeeperd]: [running]
[init.svc.health-hal-2-0]: [running]
[init.svc.healthd]: [running]
[init.svc.hidl_memory]: [running]
[init.svc.hwservicemanager]: [running]
[init.svc.incidentd]: [running]
[init.svc.installd]: [running]
[init.svc.irsc_util]: [stopped]
[init.svc.keymaster-3-0]: [running]
[init.svc.keystore]: [running]
[init.svc.lmkd]: [running]
[init.svc.logd]: [running]
[init.svc.logd-reinit]: [stopped]
[init.svc.media]: [running]
[init.svc.mediadrm]: [running]
[init.svc.mediaextractor]: [running]
[init.svc.mediametrics]: [running]
[init.svc.netd]: [running]
[init.svc.perf-hal-1-0]: [running]
[init.svc.qcamerasvr]: [running]
[init.svc.qcom-c_core-sh]: [stopped]
[init.svc.qcom-c_late-sh]: [stopped]
[init.svc.qcom-c_main-sh]: [stopped]
[init.svc.qcom-post-boot]: [stopped]
[init.svc.qcom-sh]: [stopped]
[init.svc.qdutils_disp-1-0]: [running]
[init.svc.qteeconnector-hal-1-0]: [running]
[init.svc.qti-testscripts]: [stopped]
[init.svc.qti_esepowermanager_service]: [running]
[init.svc.ril-daemon]: [stopped]
[init.svc.servicemanager]: [running]
[init.svc.soter-1-0]: [running]
[init.svc.ssgqmigd]: [running]
[init.svc.ssgtzd]: [running]
[init.svc.statsd]: [running]
[init.svc.storaged]: [running]
[init.svc.surfaceflinger]: [running]
[init.svc.swfingerprint-hal-1.0]: [running]
[init.svc.thermal-engine]: [running]
[init.svc.thermalservice]: [running]
[init.svc.time_daemon]: [running]
[init.svc.tombstoned]: [running]
[init.svc.touchmisc]: [stopped]
[init.svc.tui_comm-1-0]: [running]
[init.svc.ueventd]: [running]
[init.svc.usbd]: [stopped]
[init.svc.vendor.atfwd]: [stopped]
[init.svc.vendor.audio-hal-2-0]: [running]
[init.svc.vendor.bluetooth-1-0-qti]: [running]
[init.svc.vendor.camera-provider-2-4]: [running]
[init.svc.vendor.cas-hal-1-0]: [running]
[init.svc.vendor.cnd]: [running]
[init.svc.vendor.configstore-hal]: [running]
[init.svc.vendor.drm-clearkey-hal-1-1]: [running]
[init.svc.vendor.drm-hal-1-0]: [running]
[init.svc.vendor.fps_hal]: [running]
[init.svc.vendor.gralloc-2-0]: [running]
[init.svc.vendor.hvdcp_opti]: [running]
[init.svc.vendor.hwcomposer-2-1]: [running]
[init.svc.vendor.ims_rtp_daemon]: [running]
[init.svc.vendor.imsdatadaemon]: [running]
[init.svc.vendor.imsqmidaemon]: [running]
[init.svc.vendor.imsrcsservice]: [running]
[init.svc.vendor.ipacm]: [running]
[init.svc.vendor.light-hal-2-0]: [running]
[init.svc.vendor.media.omx]: [running]
[init.svc.vendor.memtrack-hal-1-0]: [running]
[init.svc.vendor.msm_irqbalance]: [running]
[init.svc.vendor.perfservice]: [running]
[init.svc.vendor.power-hal-1-0]: [running]
[init.svc.vendor.qcom-usb-sh]: [stopped]
[init.svc.vendor.qcrild]: [stopped]
[init.svc.vendor.qrtr-ns]: [running]
[init.svc.vendor.qseecomd]: [running]
[init.svc.vendor.rmt_storage]: [running]
[init.svc.vendor.sensors-hal-1-0]: [running]
[init.svc.vendor.tftp_server]: [running]
[init.svc.vendor.thermal-hal-1-0]: [running]
[init.svc.vendor.wifi_hal_legacy]: [running]
[init.svc.vndservicemanager]: [running]
[init.svc.vold]: [running]
[init.svc.wcnss-service]: [running]
[init.svc.wificond]: [running]
[init.svc.wifidisplayhalservice]: [running]
[init.svc.zygote]: [running]
[init.svc.zygote_secondary]: [running]
[keyguard.no_require_sim]: [true]
[log.tag.stats_log]: [I]
[media.aac_51_output_enabled]: [true]
[media.msm8956hw]: [0]
[media.settings.xml]: [/vendor/etc/media_profiles_vendor.xml]
[mm.enable.smoothstreaming]: [true]
[mmp.enable.3g2]: [true]
[net.bt.name]: [Android]
[net.qtaguid_enabled]: [1]
[net.tcp.2g_init_rwnd]: [10]
[net.tcp.buffersize.default]: [4096,87380,524288,4096,16384,110208]
[net.tcp.buffersize.edge]: [4093,26280,35040,4096,16384,35040]
[net.tcp.buffersize.evdo]: [4094,87380,524288,4096,16384,262144]
[net.tcp.buffersize.gprs]: [4092,8760,11680,4096,8760,11680]
[net.tcp.buffersize.hsdpa]: [4094,87380,1220608,4096,16384,1220608]
[net.tcp.buffersize.hspa]: [4094,87380,1220608,4096,16384,1220608]
[net.tcp.buffersize.hspap]: [4094,87380,1220608,4096,16384,1220608]
[net.tcp.buffersize.hsupa]: [4094,87380,1220608,4096,16384,1220608]
[net.tcp.buffersize.lte]: [2097152,4194304,8388608,262144,524288,1048576]
[net.tcp.buffersize.umts]: [4094,87380,110208,4096,16384,110208]
[net.tcp.buffersize.wifi]: [524288,2097152,4194304,262144,524288,1048576]
[net.tcp.default_init_rwnd]: [60]
[persist.backup.ntpServer]: [0.pool.ntp.org]
[persist.data.netmgrd.qos.enable]: [true]
[persist.debug.coresight.config]: [stm-events]
[persist.debug.wfd.enable]: [1]
[persist.demo.hdmirotationlock]: [false]
[persist.fuse_sdcard]: [true]
[persist.hwc.enable_vds]: [1]
[persist.hwc.mdpcomp.enable]: [true]
[persist.mm.sta.enable]: [0]
[persist.qfp]: [false]
[persist.radio.multisim.config]: [dsds]
[persist.rild.nitz_long_ons_0]: []
[persist.rild.nitz_long_ons_1]: []
[persist.rild.nitz_long_ons_2]: []
[persist.rild.nitz_long_ons_3]: []
[persist.rild.nitz_plmn]: []
[persist.rild.nitz_short_ons_0]: []
[persist.rild.nitz_short_ons_1]: []
[persist.rild.nitz_short_ons_2]: []
[persist.rild.nitz_short_ons_3]: []
[persist.sys.boot.reason]: [shutdown,userrequested]
[persist.sys.dalvik.vm.lib.2]: [libart.so]
[persist.sys.locale]: [en-US]
[persist.sys.timezone]: [America/Santiago]
[persist.sys.usb.config]: [mtp]
[persist.sys.usb.ffbm-02.func]: [mtp]
[persist.sys.webview.vmsize]: [147551200]
[persist.timed.enable]: [true]
[persist.vendor.camera.display.lmax]: [1280x720]
[persist.vendor.camera.display.umax]: [1920x1080]
[persist.vendor.data.mode]: [concurrent]
[persist.vendor.dpm.tcm]: [2]
[persist.vendor.qcomsysd.enabled]: [1]
[pm.dexopt.ab-ota]: [speed-profile]
[pm.dexopt.bg-dexopt]: [speed-profile]
[pm.dexopt.boot]: [verify]
[pm.dexopt.first-boot]: [quicken]
[pm.dexopt.inactive]: [verify]
[pm.dexopt.install]: [speed-profile]
[pm.dexopt.priv-apps-oob]: [false]
[pm.dexopt.priv-apps-oob-list]: [ALL]
[pm.dexopt.shared]: [speed]
[ril.subscription.types]: [NV,RUIM]
[rild.libargs]: [-d /dev/smd0]
[rild.libpath]: [/vendor/lib64/libril-qc-qmi-1.so]
[ro.actionable_compatible_property.enabled]: [false]
[ro.adb.secure]: [1]
[ro.af.client_heap_size_kbyte]: [7168]
[ro.allow.mock.location]: [0]
[ro.baseband]: [msm]
[ro.bluetooth.library_name]: [libbluetooth_qti.so]
[ro.board.platform]: [msm8953]
[ro.boot.baseband]: [msm]
[ro.boot.bootdevice]: [7824900.sdhci]
[ro.boot.bootreason]: [shutdown,userrequested]
[ro.boot.console]: [ttyHSL0]
[ro.boot.emmc]: [true]
[ro.boot.flash.locked]: [0]
[ro.boot.hardware]: [qcom]
[ro.boot.keymaster]: [1]
[ro.boot.serialno]: [fa389685]
[ro.boot.verifiedbootstate]: [orange]
[ro.boot.veritymode]: [enforcing]
[ro.bootimage.build.date]: [Tue Oct 29 11:17:49 CST 2019]
[ro.bootimage.build.date.utc]: [1572319069]
[ro.bootimage.build.fingerprint]: [Onyx/Max3/Max3:9/2019-10-29_11-13_2.2.1_4da93f1/836:user/dev-keys]
[ro.bootloader]: [unknown]
[ro.bootmode]: [unknown]
[ro.build.characteristics]: [tablet,nosdcard]
[ro.build.date]: [Tue Oct 29 11:17:49 CST 2019]
[ro.build.date.utc]: [1572319069]
[ro.build.description]: [Max3-user 9 2019-10-29_11-13_2.2.1_4da93f1 836 dev-keys]
[ro.build.display.id]: [2019-10-29_11-13_2.2.1_4da93f1]
[ro.build.fingerprint]: [Onyx/Max3/Max3:9/2019-10-29_11-13_2.2.1_4da93f1/836:user/dev-keys]
[ro.build.flavor]: [Max3-user]
[ro.build.host]: [ubuntu-build13]
[ro.build.id]: [2019-10-29_11-13_2.2.1_4da93f1]
[ro.build.product]: [Max3]
[ro.build.system_root_image]: [true]
[ro.build.tags]: [dev-keys]
[ro.build.type]: [user]
[ro.build.user]: [jenkins]
[ro.build.version.all_codenames]: [REL]
[ro.build.version.base_os]: []
[ro.build.version.codename]: [REL]
[ro.build.version.incremental]: [836]
[ro.build.version.min_supported_target_sdk]: [17]
[ro.build.version.preview_sdk]: [0]
[ro.build.version.release]: [9]
[ro.build.version.sdk]: [28]
[ro.build.version.security_patch]: [2018-10-05]
[ro.carrier]: [unknown]
[ro.com.android.dataroaming]: [true]
[ro.config.alarm_alert]: [Alarm_Classic.ogg]
[ro.config.notification_sound]: [pixiedust.ogg]
[ro.config.ringtone]: [Ring_Synth_04.ogg]
[ro.crypto.state]: [unencrypted]
[ro.cutoff_voltage_mv]: [3400]
[ro.dalvik.vm.native.bridge]: [0]
[ro.debuggable]: [0]
[ro.device_owner]: [false]
[ro.emmc_size]: [16GB]
[ro.expect.recovery_id]: [0xbbc59ffb896ea5179762d500eee33f71b04a81b5000000000000000000000000]
[ro.fm.transmitter]: [false]
[ro.frp.pst]: [/dev/block/bootdevice/by-name/config]
[ro.hardware]: [qcom]
[ro.hardware.nfc_nci]: [nqx.default]
[ro.hwui.drop_shadow_cache_size]: [6]
[ro.hwui.gradient_cache_size]: [1]
[ro.hwui.layer_cache_size]: [48]
[ro.hwui.path_cache_size]: [32]
[ro.hwui.r_buffer_cache_size]: [8]
[ro.hwui.text_large_cache_height]: [1024]
[ro.hwui.text_large_cache_width]: [2048]
[ro.hwui.text_small_cache_height]: [1024]
[ro.hwui.text_small_cache_width]: [1024]
[ro.hwui.texture_cache_flushrate]: [0.4]
[ro.hwui.texture_cache_size]: [72]
[ro.location.osnlp.package]: [com.google.android.gms]
[ro.location.osnlp.region.package]: []
[ro.logd.size]: [1M]
[ro.logd.size.stats]: [64K]
[ro.memperf.enable]: [false]
[ro.memperf.lib]: [libmemperf.so]
[ro.oem_unlock_supported]: [1]
[ro.opengles.version]: [196610]
[ro.product.board]: [msm8953]
[ro.product.brand]: [Onyx]
[ro.product.cpu.abi]: [arm64-v8a]
[ro.product.cpu.abilist]: [arm64-v8a,armeabi-v7a,armeabi]
[ro.product.cpu.abilist32]: [armeabi-v7a,armeabi]
[ro.product.cpu.abilist64]: [arm64-v8a]
[ro.product.device]: [Max3]
[ro.product.locale]: [en-US]
[ro.product.manufacturer]: [ONYX]
[ro.product.model]: [Max3]
[ro.product.name]: [Max3]
[ro.product.vendor.brand]: [Onyx]
[ro.product.vendor.device]: [Max3]
[ro.product.vendor.manufacturer]: [ONYX]
[ro.product.vendor.model]: [Max3]
[ro.product.vendor.name]: [Max3]
[ro.property_service.version]: [2]
[ro.qualcomm.cabl]: [2]
[ro.radio.noril]: [yes]
[ro.revision]: [0]
[ro.secure]: [1]
[ro.serialno]: [fa389685]
[ro.sf.hwrotation]: [270]
[ro.sf.lcd_density]: [212]
[ro.telephony.call_ring.multiple]: [false]
[ro.telephony.default_network]: [22,20]
[ro.treble.enabled]: [true]
[ro.vendor.build.date]: [Tue Oct 29 11:17:49 CST 2019]
[ro.vendor.build.date.utc]: [1572319069]
[ro.vendor.build.fingerprint]: [Onyx/Max3/Max3:9/2019-10-29_11-13_2.2.1_4da93f1/836:user/dev-keys]
[ro.vendor.build.security_patch]: [2018-08-05]
[ro.vendor.extension_library]: [libqti-perfd-client.so]
[ro.vendor.gpu.available_frequencies]: [650000000 560000000 510000000 400000000 320000000 216000000 133330000 ]
[ro.vendor.gt_library]: [libqti-gt.so]
[ro.vendor.product.cpu.abilist]: [arm64-v8a,armeabi-v7a,armeabi]
[ro.vendor.product.cpu.abilist32]: [armeabi-v7a,armeabi]
[ro.vendor.product.cpu.abilist64]: [arm64-v8a]
[ro.vendor.qti.am.reschedule_service]: [true]
[ro.vendor.qti.sys.fw.bservice_age]: [5000]
[ro.vendor.qti.sys.fw.bservice_enable]: [true]
[ro.vendor.qti.sys.fw.bservice_limit]: [5]
[ro.vendor.use_data_netmgrd]: [true]
[ro.vndk.lite]: [true]
[ro.vndk.version]: [28]
[ro.wifi.channels]: []
[ro.zygote]: [zygote64_32]
[sdm.debug.disable_skip_validate]: [1]
[security.perf_harden]: [1]
[selinux.restorecon_recursive]: [/data/misc_ce/0]
[service.bootanim.exit]: [1]
[service.sf.present_timestamp]: [1]
[sys.boot.reason]: [shutdown,userrequested]
[sys.boot_completed]: [1]
[sys.logbootcomplete]: [1]
[sys.oem_unlock_allowed]: [0]
[sys.rescue_boot_count]: [1]
[sys.retaildemo.enabled]: [0]
[sys.sysctl.extra_free_kbytes]: [42539]
[sys.uidcpupower]: []
[sys.usb.config]: [mtp,adb]
[sys.usb.configfs]: [0]
[sys.usb.controller]: [7000000.dwc3]
[sys.usb.ffs.ready]: [1]
[sys.usb.state]: [mtp,adb]
[sys.user.0.ce_available]: [true]
[sys.vendor.shutdown.waittime]: [500]
[sys.wifitracing.started]: [1]
[telephony.lteOnCdmaDevice]: [1]
[vendor.audio_hal.period_size]: [192]
[vendor.camera.hal1.packagelist]: [com.skype.raider,com.google.android.talk]
[vendor.camera.lowpower.record.enable]: [1]
[vendor.debug.enable.gamed]: [0]
[vendor.gralloc.disable_ubwc]: [1]
[vendor.gralloc.enable_fb_ubwc]: [0]
[vendor.vidc.dec.downscalar_height]: [1088]
[vendor.vidc.dec.downscalar_width]: [1920]
[vendor.vidc.disable.split.mode]: [1]
[vendor.vidc.enc.disable.pq]: [true]
[vendor.vidc.enc.disable_bframes]: [1]
[vidc.enc.dcvs.extra-buff-count]: [2]
[vold.has_adoptable]: [1]
[vold.has_quota]: [1]
[vold.has_reserved]: [0]
[vold.post_fs_data_done]: [1]
[wifi.interface]: [wlan0]
Mounted partitions:
Code:
Max3:/dev # mount
rootfs on / type rootfs (rw,seclabel)
/dev/root on / type ext4 (ro,seclabel,relatime)
tmpfs on /sbin type tmpfs (rw,seclabel,relatime,size=1821996k,nr_inodes=455499,mode=755)
/sbin/.magisk/block/system_root on /sbin/.magisk/mirror/system_root type ext4 (ro,seclabel,relatime)
/sbin/.magisk/block/system_root on /sbin/charger type ext4 (ro,seclabel,relatime)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,size=1821996k,nr_inodes=455499,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)
tmpfs on /mnt type tmpfs (rw,seclabel,nosuid,nodev,noexec,relatime,size=1821996k,nr_inodes=455499,mode=755,gid=1000)
/dev/block/dm-0 on /vendor type ext4 (ro,seclabel,relatime,discard)
none on /acct type cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct)
debugfs on /sys/kernel/debug type debugfs (rw,seclabel,relatime)
none on /config type configfs (rw,nosuid,nodev,noexec,relatime)
none on /dev/cpuctl type cgroup (rw,nosuid,nodev,noexec,relatime,cpu)
pstore on /sys/fs/pstore type pstore (rw,seclabel,nosuid,nodev,noexec,relatime)
tracefs on /sys/kernel/debug/tracing type tracefs (rw,seclabel,relatime)
/dev/block/mmcblk0p51 on /data type ext4 (rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered)
/dev/block/mmcblk0p26 on /cache type ext4 (rw,seclabel,nosuid,nodev,noatime,data=ordered)
/dev/block/mmcblk0p1 on /vendor/firmware_mnt type vfat (ro,context=u:object_r:firmware_file:s0,relatime,gid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro)
/dev/block/mmcblk0p12 on /vendor/dsp type ext4 (ro,seclabel,nosuid,nodev,relatime,data=ordered)
/dev/block/mmcblk0p27 on /mnt/vendor/persist type ext4 (rw,seclabel,nosuid,nodev,noatime,data=ordered)
/dev/block/mmcblk0p32 on /onyxconfig type ext4 (rw,seclabel,nosuid,nodev,relatime,data=ordered)
tmpfs on /storage type tmpfs (rw,seclabel,nosuid,nodev,noexec,relatime,size=1821996k,nr_inodes=455499,mode=755,gid=1000)
/sbin/.magisk/block/vendor on /sbin/.magisk/mirror/vendor type ext4 (ro,seclabel,relatime,discard)
/sbin/.magisk/block/data on /sbin/.magisk/mirror/data type ext4 (rw,seclabel,relatime,discard,noauto_da_alloc,data=ordered)
adb on /dev/usb-ffs/adb type functionfs (rw,relatime)
/data/media on /mnt/runtime/default/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=1015,multiuser,mask=6,derive_gid,default_normal)
/data/media on /storage/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=1015,multiuser,mask=6,derive_gid,default_normal)
/data/media on /mnt/runtime/read/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,multiuser,mask=23,derive_gid,default_normal)
/data/media on /mnt/runtime/write/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,multiuser,mask=7,derive_gid,default_normal)
Partition list:
Code:
Max3:/dev # ls -la block/by-name/                                                                                                                                                                                 
total 0
drwxr-xr-x 2 root root 1060 1970-02-12 23:31 .
drwxr-xr-x 5 root root 1700 1970-02-12 23:31 ..
lrwxrwxrwx 1 root root   21 1970-02-12 23:31 DDR -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root   21 1970-02-12 23:31 aboot -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root   21 1970-02-12 23:31 abootbak -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root   21 1970-02-12 23:31 apdp -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root   21 1970-02-12 23:31 boot -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root   21 1970-02-12 23:31 cache -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root   21 1970-02-12 23:31 cmnlib -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root   21 1970-02-12 23:31 cmnlib64 -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root   21 1970-02-12 23:31 cmnlib64bak -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root   21 1970-02-12 23:31 cmnlibbak -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root   21 1970-02-12 23:31 config -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root   21 1970-02-12 23:31 devcfg -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root   21 1970-02-12 23:31 devcfgbak -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root   21 1970-02-12 23:31 devinfo -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root   21 1970-02-12 23:31 dip -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root   21 1970-02-12 23:31 dpo -> /dev/block/mmcblk0p49
lrwxrwxrwx 1 root root   21 1970-02-12 23:31 dsp -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root   20 1970-02-12 23:31 fsc -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root   21 1970-02-12 23:31 fsg -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root   21 1970-02-12 23:31 keymaster -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root   21 1970-02-12 23:31 keymasterbak -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root   21 1970-02-12 23:31 keystore -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root   21 1970-02-12 23:31 limits -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root   21 1970-02-12 23:31 lksecapp -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root   21 1970-02-12 23:31 lksecappbak -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root   21 1970-02-12 23:31 logdump -> /dev/block/mmcblk0p50
lrwxrwxrwx 1 root root   21 1970-02-12 23:31 mcfg -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root   21 1970-02-12 23:31 mdtp -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root   21 1970-02-12 23:31 misc -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root   20 1970-02-12 23:31 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root   21 1970-02-12 23:31 modemst1 -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root   21 1970-02-12 23:31 modemst2 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root   21 1970-02-12 23:31 mota -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root   21 1970-02-12 23:31 msadp -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root   21 1970-02-12 23:31 oem -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root   21 1970-02-12 23:31 onyxconfig -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root   21 1970-02-12 23:31 persist -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root   21 1970-02-12 23:31 recovery -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root   20 1970-02-12 23:31 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root   20 1970-02-12 23:31 rpmbak -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root   20 1970-02-12 23:31 sbl1 -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root   20 1970-02-12 23:31 sbl1bak -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root   21 1970-02-12 23:31 sec -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root   21 1970-02-12 23:31 splash -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root   20 1970-02-12 23:31 ssd -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root   21 1970-02-12 23:31 syscfg -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root   21 1970-02-12 23:31 system -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root   20 1970-02-12 23:31 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root   20 1970-02-12 23:31 tzbak -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root   21 1970-02-12 23:31 userdata -> /dev/block/mmcblk0p51
lrwxrwxrwx 1 root root   21 1970-02-12 23:31 vendor -> /dev/block/mmcblk0p25
Partitions size:
Code:
for file in /dev/block/by-name/*
do
    echo -n "$file" 
    blockdev --getsize64 $file | awk -v pfix="$1" -v sfix="$2" 'BEGIN { 
          split( "Byt KiB MiB GiB TiB PiB", unit )
          uix = uct = length( unit )
          for( i=1; i<=uct; i++ ) val[i] = (2**(10*(i-1)))-1
       }{ if( int($1) == 0 ) uix = 1; else while( $1 < val[uix]+1 ) uix--
          num = $1 / (val[uix]+1)
          if( uix==1 ) n = "%5d   "; else n = "%8.2f"
          printf( "%s"n" %s%s\n", pfix, num, unit[uix], sfix ) 
       }'
done

/dev/block/by-name/DDR   32.00 KiB
/dev/block/by-name/aboot    1.00 MiB
/dev/block/by-name/abootbak    1.00 MiB
/dev/block/by-name/apdp  256.00 KiB
/dev/block/by-name/boot   64.00 MiB
/dev/block/by-name/cache  256.00 MiB
/dev/block/by-name/cmnlib    1.00 MiB
/dev/block/by-name/cmnlib64    1.00 MiB
/dev/block/by-name/cmnlib64bak    1.00 MiB
/dev/block/by-name/cmnlibbak    1.00 MiB
/dev/block/by-name/config   32.00 KiB
/dev/block/by-name/devcfg  256.00 KiB
/dev/block/by-name/devcfgbak  256.00 KiB
/dev/block/by-name/devinfo    1.00 MiB
/dev/block/by-name/dip    1.00 MiB
/dev/block/by-name/dpo    8.00 KiB
/dev/block/by-name/dsp   16.00 MiB
/dev/block/by-name/fsc    1.00 KiB
/dev/block/by-name/fsg    1.50 MiB
/dev/block/by-name/keymaster    1.00 MiB
/dev/block/by-name/keymasterbak    1.00 MiB
/dev/block/by-name/keystore  512.00 KiB
/dev/block/by-name/limits   32.00 KiB
/dev/block/by-name/lksecapp  128.00 KiB
/dev/block/by-name/lksecappbak  128.00 KiB
/dev/block/by-name/logdump   64.00 MiB
/dev/block/by-name/mcfg    4.00 MiB
/dev/block/by-name/mdtp   32.00 MiB
/dev/block/by-name/misc    1.00 MiB
/dev/block/by-name/modem   88.00 MiB
/dev/block/by-name/modemst1    1.50 MiB
/dev/block/by-name/modemst2    1.50 MiB
/dev/block/by-name/mota  512.00 KiB
/dev/block/by-name/msadp  256.00 KiB
/dev/block/by-name/oem  224.00 MiB
/dev/block/by-name/onyxconfig   32.00 MiB
/dev/block/by-name/persist   32.00 MiB
/dev/block/by-name/recovery   64.00 MiB
/dev/block/by-name/rpm  512.00 KiB
/dev/block/by-name/rpmbak  512.00 KiB
/dev/block/by-name/sbl1  512.00 KiB
/dev/block/by-name/sbl1bak  512.00 KiB
/dev/block/by-name/sec   16.00 KiB
/dev/block/by-name/splash   11.00 MiB
/dev/block/by-name/ssd    8.00 KiB
/dev/block/by-name/syscfg  512.00 KiB
/dev/block/by-name/system    3.00 GiB
/dev/block/by-name/tz    2.00 MiB
/dev/block/by-name/tzbak    2.00 MiB
/dev/block/by-name/userdata   52.87 GiB
/dev/block/by-name/vendor    1.00 GiB
Partitons size in bytes:
Code:
for file in /dev/block/by-name/*
do
    echo -n "$file  " 
    blockdev --getsize64 $file
done

/dev/block/by-name/DDR  32768
/dev/block/by-name/aboot  1048576
/dev/block/by-name/abootbak  1048576
/dev/block/by-name/apdp  262144
/dev/block/by-name/boot  67108864
/dev/block/by-name/cache  268435456
/dev/block/by-name/cmnlib  1048576
/dev/block/by-name/cmnlib64  1048576
/dev/block/by-name/cmnlib64bak  1048576
/dev/block/by-name/cmnlibbak  1048576
/dev/block/by-name/config  32768
/dev/block/by-name/devcfg  262144
/dev/block/by-name/devcfgbak  262144
/dev/block/by-name/devinfo  1048576
/dev/block/by-name/dip  1048576
/dev/block/by-name/dpo  8192
/dev/block/by-name/dsp  16777216
/dev/block/by-name/fsc  1024
/dev/block/by-name/fsg  1572864
/dev/block/by-name/keymaster  1048576
/dev/block/by-name/keymasterbak  1048576
/dev/block/by-name/keystore  524288
/dev/block/by-name/limits  32768
/dev/block/by-name/lksecapp  131072
/dev/block/by-name/lksecappbak  131072
/dev/block/by-name/logdump  67108864
/dev/block/by-name/mcfg  4194304
/dev/block/by-name/mdtp  33554432
/dev/block/by-name/misc  1048576
/dev/block/by-name/modem  92274688
/dev/block/by-name/modemst1  1572864
/dev/block/by-name/modemst2  1572864
/dev/block/by-name/mota  524288
/dev/block/by-name/msadp  262144
/dev/block/by-name/oem  234881024
/dev/block/by-name/onyxconfig  33554432
/dev/block/by-name/persist  33554432
/dev/block/by-name/recovery  67108864
/dev/block/by-name/rpm  524288
/dev/block/by-name/rpmbak  524288
/dev/block/by-name/sbl1  524288
/dev/block/by-name/sbl1bak  524288
/dev/block/by-name/sec  16384
/dev/block/by-name/splash  11534336
/dev/block/by-name/ssd  8192
/dev/block/by-name/syscfg  524288
/dev/block/by-name/system  3221225472
/dev/block/by-name/tz  2097152
/dev/block/by-name/tzbak  2097152
/dev/block/by-name/userdata  56765160960
/dev/block/by-name/vendor  1073741824
After backup (dd'ing) all the partitions except userdata, getting a bit of (maybe irrelevant) information about them:
Code:
file *

abootbak.img:     ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), statically linked, no section header
aboot.img:        ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), statically linked, no section header
apdp.img:         data
boot.img:         Android bootimg, kernel, page size: 2048, cmdline (console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom msm_rtb.filter=)
cache.img:        Linux rev 1.0 ext4 filesystem data, UUID=eef8962e-ca84-4d60-8631-74035c5ca535 (needs journal recovery) (extents) (large files) (huge files)
cmnlib64bak.img:  ELF 64-bit LSB pie executable, ARM aarch64, version 1 (SYSV), statically linked, no section header
cmnlib64.img:     ELF 64-bit LSB pie executable, ARM aarch64, version 1 (SYSV), statically linked, no section header
cmnlibbak.img:    ELF 32-bit LSB pie executable, ARM, EABI5 version 1 (SYSV), statically linked, no section header
cmnlib.img:       ELF 32-bit LSB pie executable, ARM, EABI5 version 1 (SYSV), statically linked, no section header
config.img:       data
DDR.img:          data
devcfgbak.img:    ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), statically linked, no section header
devcfg.img:       ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), statically linked, no section header
devinfo.img:      data
dip.img:          data
dpo.img:          data
dsp.img:          Linux rev 1.0 ext4 filesystem data, UUID=af32c008-2a39-7e5b-a5dc-201456d93103, volume name "dsp" (extents) (large files)
fsc.img:          data
fsg.img:          data
keymasterbak.img: ELF 32-bit LSB pie executable, ARM, EABI5 version 1 (SYSV), statically linked, no section header
keymaster.img:    ELF 32-bit LSB pie executable, ARM, EABI5 version 1 (SYSV), statically linked, no section header
keystore.img:     data
limits.img:       data
lksecappbak.img:  ELF 32-bit LSB pie executable, ARM, EABI5 version 1 (SYSV), statically linked, no section header
lksecapp.img:     ELF 32-bit LSB pie executable, ARM, EABI5 version 1 (SYSV), statically linked, no section header
logdump.img:      data
mcfg.img:         data
mdtp.img:         data
misc.img:         data
modem.img:        DOS/MBR boot sector, code offset 0x3c+2, OEM-ID "MSDOS5.0", sectors/cluster 32, root entries 512, Media descriptor 0xf8, sectors/FAT 22, sectors/track 63, heads 255, sectors 180224 (volumes > 32 MB), serial number 0xbc614e, unlabeled, FAT (16 bit)
modemst1.img:     data
modemst2.img:     data
mota.img:         data
msadp.img:        data
oem.img:          data
onyxconfig.img:   Linux rev 1.0 ext4 filesystem data, UUID=ec4af486-7c9d-4c6a-ad35-1461ae70597c, volume name "onyxconfig" (needs journal recovery) (extents) (large files) (huge files)
persist.img:      Linux rev 1.0 ext4 filesystem data, UUID=b7dc6105-0a57-4ae9-b8a2-a289a1dd2cb7 (needs journal recovery) (extents) (large files) (huge files)
recovery.img:     Android bootimg, kernel, ramdisk, page size: 2048, cmdline (console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom msm_rtb.filter=)
rpmbak.img:       ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), statically linked, no section header
rpm.img:          ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), statically linked, no section header
sbl1bak.img:      ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), statically linked, no section header
sbl1.img:         ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), statically linked, no section header
sec.img:          data
splash.img:       data
ssd.img:          data
syscfg.img:       data
system.img:       Linux rev 1.0 ext2 filesystem data, UUID=cceb8c6f-186d-56f9-9474-2ed82d7f7a22 (extents) (large files) (huge files)
tzbak.img:        ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), statically linked, no section header
tz.img:           ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), statically linked, no section header
vendor.img:       Linux rev 1.0 ext2 filesystem data, UUID=e11181d5-ddc5-5ea2-9b01-0d80251c6df5, volume name "vendor" (extents) (large files) (huge files)
I had a bit of problems trying to extract the DTB, it only seems to work with this tool https://github.com/PabloCastellano/extract-dtb, I don't know why. It was my first time getting a DTB, so I could be doing something wrong with other tools.

To extract the dtb from boot.img:
Code:
git clone https://github.com/PabloCastellano/extract-dtb
./extract-dtb.py ../path_to/boot.img
To decompile the DTB to a DTS, I used device-tree-compiler package from the Debian repo. I was talking with a guy that didn't understand why I would use that tool instead of an Android (LineageOS) tool. The thing is that I tryed with the dtc tool generated from LineageOS build tools, but it failed (syntax error \n Fatal Error: Unable to parse input tree), but Debian's tool seems to work (but gave a a lot of warnings).

Code:
sudo apt  install device-tree-compiler
dtc dtb/01_dtbdump_Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dtb -o Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts

Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (reg_format): /soc/fingerprint:reg: property has invalid length (4 bytes) (#address-cells == 1, #size-cells == 1)
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unit_address_vs_reg): /soc: node has a reg or ranges property, but no unit name
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unit_address_vs_reg): /soc/qcom,cpu-bwmon: node has a reg or ranges property, but no unit name
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unit_address_vs_reg): /soc/cpr4-ctrl@b018000/thread@0: node has a unit name, but no reg property
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unit_address_vs_reg): /soc/sound: node has a reg or ranges property, but no unit name
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unit_address_vs_reg): /soc/sound-9335: node has a reg or ranges property, but no unit name
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unit_address_vs_reg): /soc/fingerprint: node has a reg or ranges property, but no unit name
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unit_address_vs_reg): /memory: node has a reg or ranges property, but no unit name
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unit_address_vs_reg): /reserved-memory/venus_region@0: node has a unit name, but no reg property
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unit_address_vs_reg): /reserved-memory/secure_region@0: node has a unit name, but no reg property
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unit_address_vs_reg): /reserved-memory/qseecom_region@0: node has a unit name, but no reg property
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unit_address_vs_reg): /reserved-memory/adsp_region@0: node has a unit name, but no reg property
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unit_address_vs_reg): /reserved-memory/gpu_region@0: node has a unit name, but no reg property
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unit_address_format): /soc/i2c@78b6000/tc358762@0b: unit name should not have leading 0s
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unit_address_format): /soc/i2c@7af5000/wacom@09: unit name should not have leading 0s
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unit_address_format): /reserved-memory/splash_region@0x92001000: unit name should not have leading "0x"
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unit_address_format): /reserved-memory/pstore_region@0x91400000: unit name should not have leading "0x"
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (pci_device_reg): Failed prerequisite 'reg_format'
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (pci_device_bus_num): Failed prerequisite 'reg_format'
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (simple_bus_reg): Failed prerequisite 'reg_format'
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (i2c_bus_reg): Failed prerequisite 'reg_format'
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (spi_bus_reg): Failed prerequisite 'reg_format'
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (avoid_unnecessary_addr_size): /soc/qcom,cci@1b0c000: unnecessary #address-cells/#size-cells without "ranges" or child "reg" property
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unique_unit_address): /soc/qcom,smp2p-modem@0x0b011008: duplicate unit-address (also used in node /soc/qcom,smp2p-wcnss@0x0b011008)
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unique_unit_address): /soc/qcom,smp2p-modem@0x0b011008: duplicate unit-address (also used in node /soc/qcom,smp2p-adsp@0x0b011008)
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unique_unit_address): /soc/qcom,smp2p-wcnss@0x0b011008: duplicate unit-address (also used in node /soc/qcom,smp2p-adsp@0x0b011008)
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unique_unit_address): /soc/qcom,kgsl-iommu@1c40000: duplicate unit-address (also used in node /soc/arm,smmu-kgsl@1c40000)
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unique_unit_address): /soc/clock-controller@b111000: duplicate unit-address (also used in node /soc/apm@b111000)
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unique_unit_address): /soc/spi@78b7000: duplicate unit-address (also used in node /soc/i2c@78b7000)
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unique_unit_address): /soc/qcom,gcc@1800000: duplicate unit-address (also used in node /soc/qcom,gcc-mdss@1800000)
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unique_unit_address): /soc/qcom,gcc@1800000: duplicate unit-address (also used in node /soc/qcom,gcc-gfx@1800000)
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unique_unit_address): /soc/qcom,gcc-mdss@1800000: duplicate unit-address (also used in node /soc/qcom,gcc-gfx@1800000)
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unique_unit_address): /soc/qcrypto@720000: duplicate unit-address (also used in node /soc/qcedev@720000)
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unique_unit_address): /soc/qcom,msm-cam@1b00000: duplicate unit-address (also used in node /soc/qcom,irqrouter@1b00000)
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unique_unit_address): /soc/qcom,lpm-levels/qcom,pm-cluster@0/qcom,pm-cluster-level@0: duplicate unit-address (also used in node /soc/qcom,lpm-levels/qcom,pm-cluster@0/qcom,pm-cluster@0)
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unique_unit_address): /soc/qcom,lpm-levels/qcom,pm-cluster@0/qcom,pm-cluster-level@1: duplicate unit-address (also used in node /soc/qcom,lpm-levels/qcom,pm-cluster@0/qcom,pm-cluster@1)
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unique_unit_address): /soc/i2c@78b8000/qcom,actuator@0: duplicate unit-address (also used in node /soc/i2c@78b8000/qcom,eeprom@0)
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unique_unit_address): /soc/i2c@78b8000/qcom,eeprom@2: duplicate unit-address (also used in node /soc/i2c@78b8000/qcom,camera@2)
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unique_unit_address): /reserved-memory/other_ext_region@0: duplicate unit-address (also used in node /reserved-memory/modem_region@0)
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unique_unit_address): /reserved-memory/other_ext_region@0: duplicate unit-address (also used in node /reserved-memory/adsp_fw_region@0)
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unique_unit_address): /reserved-memory/modem_region@0: duplicate unit-address (also used in node /reserved-memory/adsp_fw_region@0)
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unique_unit_address): /reserved-memory/other_ext_region@0: duplicate unit-address (also used in node /reserved-memory/wcnss_fw_region@0)
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unique_unit_address): /reserved-memory/modem_region@0: duplicate unit-address (also used in node /reserved-memory/wcnss_fw_region@0)
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unique_unit_address): /reserved-memory/adsp_fw_region@0: duplicate unit-address (also used in node /reserved-memory/wcnss_fw_region@0)
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unique_unit_address): /reserved-memory/other_ext_region@0: duplicate unit-address (also used in node /reserved-memory/venus_region@0)
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unique_unit_address): /reserved-memory/modem_region@0: duplicate unit-address (also used in node /reserved-memory/venus_region@0)
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unique_unit_address): /reserved-memory/adsp_fw_region@0: duplicate unit-address (also used in node /reserved-memory/venus_region@0)
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unique_unit_address): /reserved-memory/wcnss_fw_region@0: duplicate unit-address (also used in node /reserved-memory/venus_region@0)
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unique_unit_address): /reserved-memory/other_ext_region@0: duplicate unit-address (also used in node /reserved-memory/secure_region@0)
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unique_unit_address): /reserved-memory/modem_region@0: duplicate unit-address (also used in node /reserved-memory/secure_region@0)
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unique_unit_address): /reserved-memory/adsp_fw_region@0: duplicate unit-address (also used in node /reserved-memory/secure_region@0)
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unique_unit_address): /reserved-memory/wcnss_fw_region@0: duplicate unit-address (also used in node /reserved-memory/secure_region@0)
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unique_unit_address): /reserved-memory/venus_region@0: duplicate unit-address (also used in node /reserved-memory/secure_region@0)
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unique_unit_address): /reserved-memory/other_ext_region@0: duplicate unit-address (also used in node /reserved-memory/qseecom_region@0)
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unique_unit_address): /reserved-memory/modem_region@0: duplicate unit-address (also used in node /reserved-memory/qseecom_region@0)
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unique_unit_address): /reserved-memory/adsp_fw_region@0: duplicate unit-address (also used in node /reserved-memory/qseecom_region@0)
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unique_unit_address): /reserved-memory/wcnss_fw_region@0: duplicate unit-address (also used in node /reserved-memory/qseecom_region@0)
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unique_unit_address): /reserved-memory/venus_region@0: duplicate unit-address (also used in node /reserved-memory/qseecom_region@0)
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unique_unit_address): /reserved-memory/secure_region@0: duplicate unit-address (also used in node /reserved-memory/qseecom_region@0)
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unique_unit_address): /reserved-memory/other_ext_region@0: duplicate unit-address (also used in node /reserved-memory/adsp_region@0)
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unique_unit_address): /reserved-memory/modem_region@0: duplicate unit-address (also used in node /reserved-memory/adsp_region@0)
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unique_unit_address): /reserved-memory/adsp_fw_region@0: duplicate unit-address (also used in node /reserved-memory/adsp_region@0)
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unique_unit_address): /reserved-memory/wcnss_fw_region@0: duplicate unit-address (also used in node /reserved-memory/adsp_region@0)
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unique_unit_address): /reserved-memory/venus_region@0: duplicate unit-address (also used in node /reserved-memory/adsp_region@0)
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unique_unit_address): /reserved-memory/secure_region@0: duplicate unit-address (also used in node /reserved-memory/adsp_region@0)
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unique_unit_address): /reserved-memory/qseecom_region@0: duplicate unit-address (also used in node /reserved-memory/adsp_region@0)
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unique_unit_address): /reserved-memory/other_ext_region@0: duplicate unit-address (also used in node /reserved-memory/gpu_region@0)
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unique_unit_address): /reserved-memory/modem_region@0: duplicate unit-address (also used in node /reserved-memory/gpu_region@0)
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unique_unit_address): /reserved-memory/adsp_fw_region@0: duplicate unit-address (also used in node /reserved-memory/gpu_region@0)
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unique_unit_address): /reserved-memory/wcnss_fw_region@0: duplicate unit-address (also used in node /reserved-memory/gpu_region@0)
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unique_unit_address): /reserved-memory/venus_region@0: duplicate unit-address (also used in node /reserved-memory/gpu_region@0)
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unique_unit_address): /reserved-memory/secure_region@0: duplicate unit-address (also used in node /reserved-memory/gpu_region@0)
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unique_unit_address): /reserved-memory/qseecom_region@0: duplicate unit-address (also used in node /reserved-memory/gpu_region@0)
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (unique_unit_address): /reserved-memory/adsp_region@0: duplicate unit-address (also used in node /reserved-memory/gpu_region@0)
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (gpios_property): /soc/tpiu@6020000: Missing property '#gpio-cells' in node /soc/ad-hoc-bus@580000/slv-snoc-bimc-0 or bad phandle (referred from nidnt-gpio[0])
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (gpios_property): /soc/i2c@78b6000/wsa881x-i2c-codec@e:qcom,msm-gpios: property size (25) is invalid, expected multiple of 4
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (gpios_property): /soc/i2c@78b6000/wsa881x-i2c-codec@f:qcom,msm-gpios: property size (25) is invalid, expected multiple of 4
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (gpios_property): /soc/sound:qcom,msm-gpios: property size (38) is invalid, expected multiple of 4
Qualcomm_Technologies,_Inc._MSM8953_+_PMI8950_QRD_SKU3.dts: Warning (gpios_property): /soc/sound-9335:qcom,msm-gpios: Could not get phandle node for (cell 0)
The DTS file was attached to this post.

I think that somebody has posted this link earlier but I don't know where: Information about Max3 in FCC (Federal Communications Commission), showing internal and external photos of the device, among other documents:
https://fccid.io/XR3-MAX3


Now a few questions:
1.- We have the stock filesystem under a partition and it is mounted as /. Can we put a new filesystem (maybe build a Debian filesystem) under /new_filesystem in the same partition, and set a kernel boot parameter to set the root_filesystem to that /new_filesystem folder?

With that, we could have a native Debian system running without even have to have a recovery, without even have to flash a new system, just by creating that directory and setting a boot parameter.

In a similar way, I have used GRUB in a desktop computer to boot from an ISO file inside an HDD partition, I'm wondering if we could do somethign similar.

2.- Aren't they required to release their kernel source? Are they infringing the GPL License?

3.- Can we get the sources of cyttsp5 from another project and try to compile it ourselfs?

4.- Since Max3 and Mido device have the same SOC, can we use a LineageOS filesystem for Mido device in Max3? If that's a yes, maybe we we can combine it with what I asked in question #1.
Attached Files
File Type: zip DTS_and_kernel_config.zip (71.9 KB, 345 views)

Last edited by uniqdom; 01-22-2020 at 10:58 AM.
uniqdom is offline   Reply With Quote
Old 01-23-2020, 05:08 PM   #35
Waiting4somethin
Addict
Waiting4somethin is a jewel in the roughWaiting4somethin is a jewel in the roughWaiting4somethin is a jewel in the roughWaiting4somethin is a jewel in the roughWaiting4somethin is a jewel in the roughWaiting4somethin is a jewel in the roughWaiting4somethin is a jewel in the roughWaiting4somethin is a jewel in the roughWaiting4somethin is a jewel in the roughWaiting4somethin is a jewel in the roughWaiting4somethin is a jewel in the rough
 
Posts: 249
Karma: 7162
Join Date: Dec 2017
Device: Wexler Flex One, NookST, n96ml+
I didn't know about same partition booting. Someone said its possible maybe. https://askubuntu.com/questions/4057...ngle-partition

I'm just an average linux user really, so I'm afraid I probably can't offer any good advice. And I have absolutely no android tinkering experience whatsoever. I understand from your post that flashing is required to install lineageos but also to install linux. I suppose if it were me I might try to boot linux from a usb sdcard to test how linux runs on it before trying to override the whole system. But as you can probably see I don't know how it works. There are some tech wizards around here though.

I hope you get it working. With a light keyboard that would be a 400g 13" eink linux laptop, get a tiling window manager and hotkey programs and you have feather weight eye strain free computing.

Anyway sorry I cant be of more help.
Waiting4somethin is offline   Reply With Quote
Old 01-23-2020, 06:13 PM   #36
diabl0w
Connoisseur
diabl0w will become famous soon enoughdiabl0w will become famous soon enoughdiabl0w will become famous soon enoughdiabl0w will become famous soon enoughdiabl0w will become famous soon enoughdiabl0w will become famous soon enough
 
Posts: 87
Karma: 527
Join Date: Sep 2019
Device: Max3
No custom ROMs or kernels, how do you think we would build that stuff without source code? Unless one of you know where to get source code but I dont. Legally, Onyx needs to supply us with source code because of GPL licensing of Linux, but they wont do it.

for Linux just run termux, unless your feeling dangerous then run Linux Deploy

For split screen, no, that is the one thing I really recommend not trying unless you are willing to risk data loss.
diabl0w is offline   Reply With Quote
Old 01-23-2020, 06:14 PM   #37
diabl0w
Connoisseur
diabl0w will become famous soon enoughdiabl0w will become famous soon enoughdiabl0w will become famous soon enoughdiabl0w will become famous soon enoughdiabl0w will become famous soon enoughdiabl0w will become famous soon enough
 
Posts: 87
Karma: 527
Join Date: Sep 2019
Device: Max3
really if you want linux just use Boox as a monitor for a true Linux machine like desktop or raspberry pi
diabl0w is offline   Reply With Quote
Old 01-24-2020, 07:41 AM   #38
mePy2
Junior Member
mePy2 began at the beginning.
 
Posts: 8
Karma: 10
Join Date: Jan 2020
Device: Max2 Pro
Many thanks!
mePy2 is offline   Reply With Quote
Old 02-01-2020, 07:18 PM   #39
onyxbooxmax3
Junior Member
onyxbooxmax3 began at the beginning.
 
Posts: 4
Karma: 10
Join Date: Feb 2020
Device: Onyx Boox Max3
power off not working

When I power off my onyx boox max 3 the blue led on the power button keeps blinking.
There does not seem to be a way to completely power down the device in its stock configeration.
I did consider rooting the device and installing a power off utility from f-droid or google play but the process for rooting still looks pretty speculative to me.

Is there something I am omitting when I try to power down the device completely.
The battery life in the supposed power down state is of the order of 36 h which suggests to me that it is still drawing significant current in its appearent off state.

Thanks
onyxbooxmax3 is offline   Reply With Quote
Old 02-07-2020, 12:33 AM   #40
diabl0w
Connoisseur
diabl0w will become famous soon enoughdiabl0w will become famous soon enoughdiabl0w will become famous soon enoughdiabl0w will become famous soon enoughdiabl0w will become famous soon enoughdiabl0w will become famous soon enough
 
Posts: 87
Karma: 527
Join Date: Sep 2019
Device: Max3
Quote:
Originally Posted by onyxbooxmax3 View Post
When I power off my onyx boox max 3 the blue led on the power button keeps blinking.
There does not seem to be a way to completely power down the device in its stock configeration.
I did consider rooting the device and installing a power off utility from f-droid or google play but the process for rooting still looks pretty speculative to me.

Is there something I am omitting when I try to power down the device completely.
The battery life in the supposed power down state is of the order of 36 h which suggests to me that it is still drawing significant current in its appearent off state.

Thanks
your doing something wrong, hold power button for 10 seconds without charging cable plugged in... then your device is off, simple as that
diabl0w is offline   Reply With Quote
Old 02-09-2020, 04:37 AM   #41
winstonma
Zealot
winstonma format shifts faster than booting Windowswinstonma format shifts faster than booting Windowswinstonma format shifts faster than booting Windowswinstonma format shifts faster than booting Windowswinstonma format shifts faster than booting Windowswinstonma format shifts faster than booting Windowswinstonma format shifts faster than booting Windowswinstonma format shifts faster than booting Windowswinstonma format shifts faster than booting Windowswinstonma format shifts faster than booting Windowswinstonma format shifts faster than booting Windows
 
Posts: 107
Karma: 120918
Join Date: Nov 2013
Device: Onyx Boox Nova
Quote:
Originally Posted by diabl0w View Post
**I am not responsible for any damage to your device, and I am sure this probably voids your warranty**

Hello everyone,

I am hoping the potential of the Max 3 can be unlocked with the help of you guys, the community. To start it off, I found a way to obtain root on the Max 3. Hopefully, others can now help develop further.

The root method uses Magisk in recovery mode. You can read about it here under "Knowing Your Device": https://topjohnwu.github.io/Magisk/install.html

Our device uses "system as root" and is a NON-A/B partitioned device.

This means that we take our modified recovery.img and flash it to the recovery partition, then when we boot into recovery mode, Magisk automatically boots into a rooted system.

The only problem with this, is that Max3 has no way of booting to recovery using hardware buttons, and adb reboot recovery bypasses magisk and goes to recovery. This isnt a big deal, but just means that any time reboot you will lose root.

To gain root, run "adb reboot-bootloader" , then the screen will not look like anything happened due to e-ink, but if you run "fastboot devices" your device should appear. then you just run "fastboot boot magisk_patched.img"

make sure your bootloader is unlocked first, i believe it already is from factory "fastboot flashing unlock"

I have uploaded the patched recovery here: https://anonfiles.com/i7t1Gb6fnf/magisk_patched_img

One of the first things I propose to look into is restoring the native android Recents screen so that we can put apps into Multi-window mode.

The problem is that onyx removed this ability and have their own "OnyxRecentsActivity". I have already tried to modify the SystemUI.apk, but can't get the system to run properly with the modified file. I think its a signature issue. Maybe someone with more knowledge can help
Hi, I know this discuss Max3 but this thread is very similar to what I want to do.

I have a Nova and I already rooted the device using KingRoot. However I would like replace KingRoot with Magisk. I am not sure but I guess I missed the boot.img from the system. So how could I dump the boot.img from a rooted Android device? Or there are better ways to get this done?

Thanks in advance
winstonma is offline   Reply With Quote
Old 02-12-2020, 01:32 AM   #42
onyxbooxmax3
Junior Member
onyxbooxmax3 began at the beginning.
 
Posts: 4
Karma: 10
Join Date: Feb 2020
Device: Onyx Boox Max3
Holding power button for 10+ sec causes the device to reset and reboot.
There is a software power down option which is activated by holding the power button for about 2-3 sec .. It offers power off and reset.
Pushing power off brings up the power off screen but the power button led blinks at about 1 sec intervals and the battery drains over about 36 h in its power down state.
onyxbooxmax3 is offline   Reply With Quote
Old 02-12-2020, 01:54 PM   #43
diabl0w
Connoisseur
diabl0w will become famous soon enoughdiabl0w will become famous soon enoughdiabl0w will become famous soon enoughdiabl0w will become famous soon enoughdiabl0w will become famous soon enoughdiabl0w will become famous soon enough
 
Posts: 87
Karma: 527
Join Date: Sep 2019
Device: Max3
Quote:
Originally Posted by onyxbooxmax3 View Post
Holding power button for 10+ sec causes the device to reset and reboot.
There is a software power down option which is activated by holding the power button for about 2-3 sec .. It offers power off and reset.
Pushing power off brings up the power off screen but the power button led blinks at about 1 sec intervals and the battery drains over about 36 h in its power down state.
What firmware version are you on? youre experiences are different than mine

You can reboot to recovery and power off from the recovery menu and compare your results
diabl0w is offline   Reply With Quote
Old 02-13-2020, 12:16 AM   #44
onyxbooxmax3
Junior Member
onyxbooxmax3 began at the beginning.
 
Posts: 4
Karma: 10
Join Date: Feb 2020
Device: Onyx Boox Max3
I have identified the issue.

In order to protect the usb c port in the Max 3 I installed a magnetic usb-a to usb-c plug in the port for the purposes of charging it.
When I remove this I have found the device powers off correctly .. (i.e. no led in the hardware power button flashing in power off state)

Also when I install a usb-c usb-c magnetic connector that brings out all 20 pins .. the issue does not occur.

Obviously the usb-a to usb-c plug is shorting some of the usb -c pins in the device .. I am not fully familiar with the usb -c standard but I imagine that there is potential for
the sinking of sufficient current to drain the battery in the powered off state to drain the battery in the way I described.

Has this sort of issue been identified previously? If so what is a proven fix which will allow me to use a magnetic connector for charging (with the intention of reducing physical wear on the connector)
onyxbooxmax3 is offline   Reply With Quote
Old 02-13-2020, 10:12 PM   #45
diabl0w
Connoisseur
diabl0w will become famous soon enoughdiabl0w will become famous soon enoughdiabl0w will become famous soon enoughdiabl0w will become famous soon enoughdiabl0w will become famous soon enoughdiabl0w will become famous soon enough
 
Posts: 87
Karma: 527
Join Date: Sep 2019
Device: Max3
i did say remove the charging cable from the device in my original post... and yes, when debugging an issue like that, the first thing you should be removing modifications from a stock device

Quote:
Originally Posted by onyxbooxmax3 View Post

Has this sort of issue been identified previously? If so what is a proven fix which will allow me to use a magnetic connector for charging (with the intention of reducing physical wear on the connector)
Quote:
Originally Posted by onyxbooxmax3 View Post
Also when I install a usb-c usb-c magnetic connector that brings out all 20 pins .. the issue does not occur.
looks proven to me

Last edited by diabl0w; 02-13-2020 at 10:16 PM.
diabl0w is offline   Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Rooted Nook Simple Touch or rooted Onyx C67ML or Kobo Aura One with kreader? ALinkToTao Which one should I buy? 5 12-08-2017 12:06 PM
Ended Onyx Max 13inch eReader *Rooted* mdesro Flea Market 1 11-27-2016 06:27 PM
Difference Between Rooted v. Non-Rooted Ermine hilaryfrompa enTourage eDGe 38 02-04-2012 03:01 PM
rooted nook touch vs rooted sony prs-t1 sk1 Which one should I buy? 0 01-28-2012 11:09 AM
kindle 3 max. 3gb oder max. 3500 bücher kakakanno Amazon Kindle 8 08-22-2010 03:27 AM


All times are GMT -4. The time now is 12:48 AM.


MobileRead.com is a privately owned, operated and funded community.