How well does it work?
Umidigi S5 pro partition layout, flashing custom rom
Hi. It would be cool to have some custom rom in it. It's really great hardware (except kind of ****ty fingerprint sensor). Software part at the moment is good too (stock android 10), but it got like 2 updates and probably will stay like that forever. That's how Umidigi's business plan works, so anyone paying that low price should be OK with that.
It's great, but even at this moment it's vulnerable to at least one remote code execution flaw. We should do something about it.
So why not just flash generic GSI treble lineage build by AndyYan? If you query any search engine, article on getdroidtips will appear, it contains few simple steps.
The problem is it has weird partition layout. I'm familiar with linux, but not so much with android yet. And this build looks like highly customized one.
This is a list of all used partitions.
Adb shell, command S5_Pro:/ $ ls -al /dev/block/platform/bootdevice/by-name/ ouputs:
Code:
total 0
drwxr-xr-x 2 root root 1020 2020-07-21 15:50 .
drwxr-xr-x 3 root root 980 2020-07-21 15:50 ..
lrwxrwxrwx 1 root root 16 2020-07-21 15:50 boot -> /dev/block/sdc35
lrwxrwxrwx 1 root root 16 2020-07-21 15:50 boot_para -> /dev/block/sdc22
lrwxrwxrwx 1 root root 16 2020-07-21 15:50 cache -> /dev/block/sdc41
lrwxrwxrwx 1 root root 16 2020-07-21 15:50 cam_vpu1 -> /dev/block/sdc28
lrwxrwxrwx 1 root root 16 2020-07-21 15:50 cam_vpu2 -> /dev/block/sdc29
lrwxrwxrwx 1 root root 16 2020-07-21 15:50 cam_vpu3 -> /dev/block/sdc30
lrwxrwxrwx 1 root root 16 2020-07-21 15:50 dtbo -> /dev/block/sdc37
lrwxrwxrwx 1 root root 15 2020-07-21 15:50 expdb -> /dev/block/sdc5
lrwxrwxrwx 1 root root 16 2020-07-21 15:50 flashinfo -> /dev/block/sdc43
lrwxrwxrwx 1 root root 15 2020-07-21 15:50 frp -> /dev/block/sdc6
lrwxrwxrwx 1 root root 16 2020-07-21 15:50 gz1 -> /dev/block/sdc31
lrwxrwxrwx 1 root root 16 2020-07-21 15:50 gz2 -> /dev/block/sdc32
lrwxrwxrwx 1 root root 16 2020-07-21 15:50 lk -> /dev/block/sdc33
lrwxrwxrwx 1 root root 16 2020-07-21 15:50 lk2 -> /dev/block/sdc34
lrwxrwxrwx 1 root root 16 2020-07-21 15:50 logo -> /dev/block/sdc36
lrwxrwxrwx 1 root root 16 2020-07-21 15:50 md1img -> /dev/block/sdc21
lrwxrwxrwx 1 root root 16 2020-07-21 15:50 md_udc -> /dev/block/sdc12
lrwxrwxrwx 1 root root 16 2020-07-21 15:50 metadata -> /dev/block/sdc13
lrwxrwxrwx 1 root root 15 2020-07-21 15:50 misc -> /dev/block/sdc3
lrwxrwxrwx 1 root root 16 2020-07-21 15:50 nvcfg -> /dev/block/sdc10
lrwxrwxrwx 1 root root 16 2020-07-21 15:50 nvdata -> /dev/block/sdc11
lrwxrwxrwx 1 root root 16 2020-07-21 15:50 nvram -> /dev/block/sdc20
lrwxrwxrwx 1 root root 16 2020-07-21 15:50 otp -> /dev/block/sdc18
lrwxrwxrwx 1 root root 15 2020-07-21 15:50 para -> /dev/block/sdc4
lrwxrwxrwx 1 root root 16 2020-07-21 15:50 persist -> /dev/block/sdc14
lrwxrwxrwx 1 root root 23 2020-07-21 15:50 preloader_a -> /dev/block/mmcblk0boot0
lrwxrwxrwx 1 root root 23 2020-07-21 15:50 preloader_b -> /dev/block/mmcblk0boot1
lrwxrwxrwx 1 root root 50 2020-07-21 15:50 preloader_emmc_a -> /dev/block/platform/bootdevice/by-name/preloader_a
lrwxrwxrwx 1 root root 50 2020-07-21 15:50 preloader_emmc_b -> /dev/block/platform/bootdevice/by-name/preloader_b
lrwxrwxrwx 1 root root 50 2020-07-21 15:50 preloader_ufs_a -> /dev/block/platform/bootdevice/by-name/preloader_a
lrwxrwxrwx 1 root root 50 2020-07-21 15:50 preloader_ufs_b -> /dev/block/platform/bootdevice/by-name/preloader_b
lrwxrwxrwx 1 root root 15 2020-07-21 15:50 proinfo -> /dev/block/sdc1
lrwxrwxrwx 1 root root 16 2020-07-21 15:50 protect1 -> /dev/block/sdc15
lrwxrwxrwx 1 root root 16 2020-07-21 15:50 protect2 -> /dev/block/sdc16
lrwxrwxrwx 1 root root 15 2020-07-21 15:50 recovery -> /dev/block/sdc2
lrwxrwxrwx 1 root root 16 2020-07-21 15:50 scp1 -> /dev/block/sdc24
lrwxrwxrwx 1 root root 16 2020-07-21 15:50 scp2 -> /dev/block/sdc25
lrwxrwxrwx 1 root root 16 2020-07-21 15:50 sec1 -> /dev/block/sdc19
lrwxrwxrwx 1 root root 16 2020-07-21 15:50 seccfg -> /dev/block/sdc17
lrwxrwxrwx 1 root root 16 2020-07-21 15:50 spmfw -> /dev/block/sdc23
lrwxrwxrwx 1 root root 16 2020-07-21 15:50 sspm_1 -> /dev/block/sdc26
lrwxrwxrwx 1 root root 16 2020-07-21 15:50 sspm_2 -> /dev/block/sdc27
lrwxrwxrwx 1 root root 16 2020-07-21 15:50 super -> /dev/block/sdc40
lrwxrwxrwx 1 root root 16 2020-07-21 15:50 tee1 -> /dev/block/sdc38
lrwxrwxrwx 1 root root 16 2020-07-21 15:50 tee2 -> /dev/block/sdc39
lrwxrwxrwx 1 root root 16 2020-07-21 15:50 userdata -> /dev/block/sdc42
lrwxrwxrwx 1 root root 15 2020-07-21 15:50 vbmeta -> /dev/block/sdc7
lrwxrwxrwx 1 root root 15 2020-07-21 15:50 vbmeta_system -> /dev/block/sdc8
lrwxrwxrwx 1 root root 15 2020-07-21 15:50 vbmeta_vendor -> /dev/block/sdc9
And fastboot getvar all gives:
Code:
(bootloader) max-download-size: 0x8000000
(bootloader) variant:
(bootloader) logical-block-size: 0x1000
(bootloader) erase-block-size: 0x0
(bootloader) hw-revision: ca00
(bootloader) battery-soc-ok: yes
(bootloader) battery-voltage: 4291mV
(bootloader) partition-size:sgpt: 8000
(bootloader) partition-type:sgpt: raw data
(bootloader) partition-size:flashinfo: 1000000
(bootloader) partition-type:flashinfo: raw data
(bootloader) partition-size:userdata: 3a68ef8000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: 1b000000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:super: e0000000
(bootloader) partition-type:super: raw data
(bootloader) partition-size:tee2: 900000
(bootloader) partition-type:tee2: raw data
(bootloader) partition-size:tee1: 500000
(bootloader) partition-type:tee1: raw data
(bootloader) partition-size:dtbo: 800000
(bootloader) partition-type:dtbo: raw data
(bootloader) partition-size:logo: 800000
(bootloader) partition-type:logo: raw data
(bootloader) partition-size:boot: 2000000
(bootloader) partition-type:boot: raw data
(bootloader) partition-size:lk2: 200000
(bootloader) partition-type:lk2: raw data
(bootloader) partition-size:lk: 200000
(bootloader) partition-type:lk: raw data
(bootloader) partition-size:gz2: 2000000
(bootloader) partition-type:gz2: raw data
(bootloader) partition-size:gz1: 2000000
(bootloader) partition-type:gz1: raw data
(bootloader) partition-size:cam_vpu3: f00000
(bootloader) partition-type:cam_vpu3: raw data
(bootloader) partition-size:cam_vpu2: f00000
(bootloader) partition-type:cam_vpu2: raw data
(bootloader) partition-size:cam_vpu1: f00000
(bootloader) partition-type:cam_vpu1: raw data
(bootloader) partition-size:sspm_2: 100000
(bootloader) partition-type:sspm_2: raw data
(bootloader) partition-size:sspm_1: 100000
(bootloader) partition-type:sspm_1: raw data
(bootloader) partition-size:scp2: 600000
(bootloader) partition-type:scp2: raw data
(bootloader) partition-size:scp1: 600000
(bootloader) partition-type:scp1: raw data
(bootloader) partition-size:spmfw: 100000
(bootloader) partition-type:spmfw: raw data
(bootloader) partition-size:boot_para: 1a00000
(bootloader) partition-type:boot_para: raw data
(bootloader) partition-size:md1img: 9600000
(bootloader) partition-type:md1img: raw data
(bootloader) partition-size:nvram: 4000000
(bootloader) partition-type:nvram: raw data
(bootloader) partition-size:sec1: 200000
(bootloader) partition-type:sec1: raw data
(bootloader) partition-size:otp: 3000000
(bootloader) partition-type:otp: raw data
(bootloader) partition-size:seccfg: 800000
(bootloader) partition-type:seccfg: raw data
(bootloader) partition-size:protect2: 800000
(bootloader) partition-type:protect2: ext4
(bootloader) partition-size:protect1: 800000
(bootloader) partition-type:protect1: ext4
(bootloader) partition-size:persist: 305e000
(bootloader) partition-type:persist: ext4
(bootloader) partition-size:metadata: 2000000
(bootloader) partition-type:metadata: raw data
(bootloader) partition-size:md_udc: 169a000
(bootloader) partition-type:md_udc: ext4
(bootloader) partition-size:nvdata: 4000000
(bootloader) partition-type:nvdata: ext4
(bootloader) partition-size:nvcfg: 2000000
(bootloader) partition-type:nvcfg: ext4
(bootloader) partition-size:vbmeta_vendor: 800000
(bootloader) partition-type:vbmeta_vendor: raw data
(bootloader) partition-size:vbmeta_system: 800000
(bootloader) partition-type:vbmeta_system: raw data
(bootloader) partition-size:vbmeta: 800000
(bootloader) partition-type:vbmeta: raw data
(bootloader) partition-size:frp: 100000
(bootloader) partition-type:frp: raw data
(bootloader) partition-size:expdb: 1400000
(bootloader) partition-type:expdb: raw data
(bootloader) partition-size:para: 80000
(bootloader) partition-type:para: raw data
(bootloader) partition-size:misc: 80000
(bootloader) partition-type:misc: raw data
(bootloader) partition-size:recovery: 2000000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:proinfo: 300000
(bootloader) partition-type:proinfo: raw data
(bootloader) partition-size:pgpt: 8000
(bootloader) partition-type:pgpt: raw data
(bootloader) partition-size:preloader: 400000
(bootloader) partition-type:preloader: raw data
(bootloader) serialno: S5PRO20200004200
(bootloader) off-mode-charge: 1
(bootloader) warranty: no
(bootloader) unlocked: yes
(bootloader) secure: no
(bootloader) kernel: lk
(bootloader) product: k85v1_64
(bootloader) is-userspace: no
(bootloader) slot-count: 0
(bootloader) version-baseband: MOLY.LR13.R1.MP.V55
(bootloader) version-bootloader: k85v1_64-722dd20--20200702183212
(bootloader) version-preloader:
(bootloader) version: 0.5
all: Done!!
finished. total time: 0.005s
So you can't just flash system partition, it's not even there.
We should look closer at this device because it has great potential, but it does not look like a low hanging fruit to flash custom rom :cyclops:
Ok, it's not super custom layout, just dynamical partitioning was used. There are docs on
Code:
https://source.android.com/devices/tech/ota/dynamic_partitions/implement (new account, can't post links)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Have you managed to get TWRP on the recovery partition? I have root but, unable to flash recovery proper
tetrig said:
Ok, it's not super custom layout, just dynamical partitioning was used. There are docs on
Code:
https://source.android.com/devices/tech/ota/dynamic_partitions/implement (new account, can't post links)
Click to expand...
Click to collapse
hermeez said:
Have you managed to get TWRP on the recovery partition? I have root but, unable to flash recovery proper
Click to expand...
Click to collapse
Currently I have a Device tree setup : https://github.com/DrDrache/umidigis5pro_TWRP
and already pulled the minimal manifest of TWRP - sadly I cannot get a quick compile (see code error below)
I havn't built a recovery in YEARS (6?) - so if we could find someone to give me the pointers; I can finish I think.
Code:
[email protected]:~/TWRP-SRC$ lunch omni_S5_PRO-eng
WARNING: device/umidigi/S5_PRO/omni.dependencies file not found
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=16.1.0
TARGET_PRODUCT=omni_S5_PRO
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_ARCH=arm64
TARGET_ARCH_VARIANT=armv8-a
TARGET_CPU_VARIANT=cortex-a53
TARGET_2ND_ARCH=arm
TARGET_2ND_ARCH_VARIANT=armv7-a-neon
TARGET_2ND_CPU_VARIANT=generic
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-5.8.1-xanmod1-x86_64-Ubuntu-20.04.1-LTS
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
HOST_BUILD_TYPE=release
BUILD_ID=QQ3A.200805.001
OUT_DIR=/home/drache/TWRP-SRC/out
ROM_BUILDTYPE=HOMEMADE
============================================
[email protected]:~/TWRP-SRC$ mka recoveryimage
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=16.1.0
TARGET_PRODUCT=omni_S5_PRO
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_ARCH=arm64
TARGET_ARCH_VARIANT=armv8-a
TARGET_CPU_VARIANT=cortex-a53
TARGET_2ND_ARCH=arm
TARGET_2ND_ARCH_VARIANT=armv7-a-neon
TARGET_2ND_CPU_VARIANT=generic
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-5.8.1-xanmod1-x86_64-Ubuntu-20.04.1-LTS
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
HOST_BUILD_TYPE=release
BUILD_ID=QQ3A.200805.001
OUT_DIR=/home/drache/TWRP-SRC/out
ROM_BUILDTYPE=HOMEMADE
============================================
device/umidigi/S5_PRO/omni_S5_PRO.mk was modified, regenerating...
device/umidigi/S5_PRO/omni_S5_PRO.mk was modified, regenerating...
[ 99% 260/261] finishing build rules ...
vendor/omni/build/tasks/kernel.mk:111: warning: ***************************************************************
vendor/omni/build/tasks/kernel.mk:112: warning: * Using prebuilt kernel binary instead of source *
vendor/omni/build/tasks/kernel.mk:113: warning: * THIS IS DEPRECATED, AND WILL BE DISCONTINUED *
vendor/omni/build/tasks/kernel.mk:114: warning: * Please configure your device to download the kernel *
vendor/omni/build/tasks/kernel.mk:115: warning: * source repository to
vendor/omni/build/tasks/kernel.mk:116: warning: * for more information *
vendor/omni/build/tasks/kernel.mk:117: warning: ***************************************************************
FAILED: ninja: '/home/drache/TWRP-SRC/out/target/product/S5_PRO/obj/STATIC_LIBRARIES/bootctrl._intermediates/export_includes', needed by '/home/drache/TWRP-SRC/out/target/product/S5_PRO/obj/SHARED_LIBRARIES/[email protected]_intermediates/import_includes', missing and no known rule to make it
18:58:17 ninja failed with: exit status 1
#### failed to build some targets (01:32 (mm:ss)) ####
Hi @dr_drache!
Have you figured something out, yet? I can also list all the partitions from Fastboot, but cannot flash a working custom GSI ROM. What I found really interesting, as you all mentioned before, is that the device has a super partition, but for example the ,,GSI checker" app says that the device is very likely a-only.
I am also thinking about trying to build the recovery for the UMIDIGI S5 Pro after watching and reading some tutorials I guess...
I am just interested in your progress.
Dear fellow Developers!
I have wonderful news! I successfully compiled a TWRP Recovery from source as a late night program for myself, but it was definitely worth it! I used the stock recovery image from the V1.3 stock ROM.
We are in the finish line, however I attached a screenshot and there are some problems need to be fixed.
The problems are:
E: unable to update logical partition: /system_image
E: unable to update logical partition: /vendor_image
E: unable to update logical partition: /product_image
Failed to mount 'system_root' (Permission denied)
I will leave a link here to the recovery image, built by me: MEGA
Every help is welcome, because we are really close now to make a working recovery for this phone and to start flashing custom GSIs!
Thank you!
Edit:
You can flash the recovery from fastboot and you can also use the SP Flash Tool to flash it.
Edit 2:
There is a photo of the building, I think that there warnings are not relevant, are they?
Update:
After editing some lines in the /etc/fstab file from ,,ro" to ,,rw" and then doing a mount -a the filesystems are successfully mounted, however trying to flash a GSI to the system partition drops the next error: Size of image is larger than target device
Also there is this interesting super partition and flashing the GSI there is working, but after that the device can't reboot to the OS, it boots to fastboot after the first failed boot. I think that we need to figure out how to correctly mount the filesystems or to resize the system partition or not and how to find it's original mount point.
Update 2:
So I found this on source.android.com: ,,Devices with dynamic partitions (whether it launches with or retrofits dynamic partitions) must not use system-as-root. The Linux kernel can't interpret the super partition and so can't mount system itself. system is now mounted by first-stage init, which resides in the ramdisk." How should we ,,find" now the /system partition? Because I didn't find it either through TWRP. I guess we have no other choice, than wait for the TWRP developers to figure this super partition layout out. I will keep up with the developments and will compile the recovery again, if progress has been made.
I think the reboot to recovery is related to some system partition. I remember that flashing GSI on a Mi9 SE caused the same behaviour after a full wipe.
Just recently bought S5 pro phone from official umidigi eBay store for AU$177. Very happy with purchase, great value plus doesn't have a notch or hole punch display.
After some searching and some trial and error, i can flash GSI images to device.
1) Unlock the bootloader
fastboot flashing unlock
and pressing Vol+
2)Boot to stock recovery.
fastboot reboot recovery
3)Select from recovery menu Wipe data/factory reset
4)Select from recovery menu Wipe cache partition
5)Select from recovery menu Enter Fastboot (fastbootd)
fastboot -w (CAUTION: deletes userdata, storage)
6)Delete product partition
fastboot delete-logical-partition product
7)Flash GSI to system partition
fastboot flash --u system lineage-18.1-20210411-UNOFFICIAL-treble_arm64_bvS.img
8)Reboot to normal fastboot (not fastbootd)
Flash the stock vbmeta.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Select from recovery menu Reboot system now
Not Working so far:
In screen fingerprint reader. Thinks reader is at back of phone, not sure how to fix.
Does TWRP allow for /system partition resizing thus keeping /product partition intact? Wondering if the product partition is needed for fingerprint to work?
Hello!
Oh my God how did you figure this out by yourself? I completely gave up when I saw the terrible partition layout. I will try to flash one GSI following your guidance. So is it actually possible to avoid using TWRP and to flash GSIs from fastbootd? I thought Umidigi made it impossible with the lack of write permissions. If what you are saying here is true, then in theory we also can perform these steps from my beta TWRP, however I saw some updates on the project, maybe I will compile it again later.
Thank you so much for your help! I will post updates after flashing the GSI.
By the way, how is this phone AB? I didn't think that it supports seamless updates.
I honestly didn't figure it out, followed this good post below, it's a different Umidigi device but apply's to S5 Pro too.
UMIDIGI Power 3 - Android 10
All info current as of 05/12/2021 I'm editing this original post to update what I've cobbled together from various forums. I do not take credit for any of the below. Nor the responsibility if you brick your phone. So, proceed with caution and at...
forum.xda-developers.com
Keen to try steps 15, resize product and system partitions & Unpacking and repacking super.img when i have some time as i would like fingerprint functionality.
Your TWRP image would be great to have, for backups etc and system edit's without root.
Arm64 A only images bootlooped, but A/B arm64 worked.
Thanks for the link, I will check it out! I am also concerned about the fingerprint reader, since we don't really have kernel sources as far as I know. It would be great to keep the /product somehow. So basically the treble checker app gives false information about the system layout, because it said that the S5 Pro is a-only...
Halwer said:
Thanks for the link, I will check it out! I am also concerned about the fingerprint reader, since we don't really have kernel sources as far as I know. It would be great to keep the /product somehow. So basically the treble checker app gives false information about the system layout, because it said that the S5 Pro is a-only...
Click to expand...
Click to collapse
Hi, Halwer Treble Info shows that the S5 Pro uses an A/B operating system and that it supports VNDK and is an arm64. Try using this app as it reports the phone correctly.
The S5 PRO does not support seamless upgrades so you must enter recovery to install upgrades.
It also reports that it uses Dynamic Partitions (super partition) and that you can only flash high-level partitions through fastbootd as other methods will report an error saying the partition does not exist.
Hello,
I am still not sure, look at this screenshot!
I mean in general this is really not a big deal. GSI ROMs tend to act a little weird with partition layouts, anyway.
The big deal will be a working TWRP in my opinion.
Halwer said:
Thanks for the link, I will check it out! I am also concerned about the fingerprint reader, since we don't really have kernel sources as far as I know. It would be great to keep the /product somehow. So basically the treble checker app gives false information about the system layout, because it said that the S5 Pro is a-only...
Click to expand...
Click to collapse
Andy Yan has brought out another GSI version lineage-18.1-20210512-UNOFFICIAL-treble_arm64_bvS.img.xz
Good news!
I will also try to build a more up to date version of TWRP when more commits arrive on GitHub. It would be good to be able to resize the system partition from TWRP, so we don't have to touch or remove the /product partition.
Halwer said:
Hello,
I am still not sure, look at this screenshot!
I mean in general this is really not a big deal. GSI ROMs tend to act a little weird with partition layouts, anyway.
The big deal will be a working TWRP in my opinion.
View attachment 5314185
Click to expand...
Click to collapse
Try Trebel Info instead as it seems to report the phone correctly as an A/B with unsupported seamless system updates. This seems to be what others are finding as the A-only OS causes boot loops.
Okay, thanks. Interesting.
Was able to flash a custom super.img following this guide:
https://forum.xda-developers.com/t/...r-img-and-flashing-our-modifications.4196625/
I editet product.img, deleting Google preinstalled apps in /system/app. (Thus increasing system.img space)
Was also able to flash a super.img via Halwer twrp after editing /etc/fstab file from ,,ro" to ,,rw" and then doing a mount -a.
Currently using HavocOS, but unfortunaly some bugs, even with product partition ( i think GSI's dont use anyway??):
Fingerprint reader
No Data toggle in quick settings
Bluetooth calls (mic sounds echo)
Usb C headphone's not working
After i find best way to backup current config, might try Andy Yan latest version.
Amazing news!
I am very happy to see that my recovery proved useful, since I am not a developer I don't really know what has to be done, to make this obscure hardware work.
Related
We already have a dump of KKV51, but that is not the actual rom that devices ship with preinstalled.
They ship with KMV78N, which we do not have a dump of for the g watch.
The main issue is enabling adb without having it force an update first.
Here's how to enable adb on it: [How-To] Android Wear: Enable Debugging, Take Screenshots, Unlock The Bootloader, And Root The LG G Watch
TheManii said:
Android wear runs, well android.
I would like to request that someone that has a wear to dump the rom that is preinstalled on it, and to make note if there it prompts for an ota on first setup.
I don't know how to enable adb on it, but I would expect that it would be available, for the moment merely doing a
Code:
adb pull /system
will be as much as anyone can expect.
In the event it actually supports fastboot, I'd also like to request a
Code:
fastboot get-var all
Click to expand...
Click to collapse
Can't you disconnect the phone from internet? I can try to do a dump when I get mine tomorrow morning
trh1341 said:
Can't you disconnect the phone from internet? I can try to do a dump when I get mine tomorrow morning
Click to expand...
Click to collapse
If it's like current nexii rom (and given that the rom is made by google, i have no reason to doubt this), it might not let you use it until you have a sucessful connection to the internet which means the ability for it to force download an ota.
The ota is already out, so if it does immediately download the ota, you might not have the chance to dump it beforehand.
Is this still needed. Mine is still in box. Just got home.
I can attempt by disconnecting the pc from net and try to adb and pull a dump from fastboot via USB if cradle allows it. Otherwise I have Bluetooth.
Sent from my SCH-I545 using Tapatalk
Edit: I tried.... not connected to Phone. Hit reset button I could get to device info KKV51 loaded on mine out of the box. Sorry not a prize winner.... Unless you meant thus build.
I am still going to dump anyway if I can get adb to show online. It won't bring up authorization prompt. I'm done trying. I just want to set it up to use now. Sorry
I tricked it... It's dumping now. I hope no apks from my phone installed from this ... doesn't look like it.
http://www.mediafire.com/download/mlc7aw35ewsy9km/KKV51.zip
cat /proc/partitions
major minor #blocks name
179 0 3817472 mmcblk0
179 1 1024 mmcblk0p1
179 2 512 mmcblk0p2
179 3 512 mmcblk0p3
179 4 512 mmcblk0p4
179 5 512 mmcblk0p5
179 6 1024 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 512 mmcblk0p9
179 10 2048 mmcblk0p10
179 11 512 mmcblk0p11
179 12 16384 mmcblk0p12
179 13 16384 mmcblk0p13
179 14 22528 mmcblk0p14
179 15 22528 mmcblk0p15
179 16 22528 mmcblk0p16
179 17 512 mmcblk0p17
179 18 512 mmcblk0p18
179 19 262144 mmcblk0p19
179 20 262144 mmcblk0p20
179 21 3182592 mmcblk0p21
179 22 495 mmcblk0p22
179 32 4096 mmcblk0rpmb
fastboot getvar all
(bootloader) max-download-size: 0x10000000
(bootloader) display-panel:
(bootloader) version-hardware: rev_11
(bootloader) version-baseband: N/A
(bootloader) version-bootloader: DORYZ10e
(bootloader) version-cdma: N/A
(bootloader) variant: dory 4GB
(bootloader) serialno: 03c3ca6d02a28867
(bootloader) carrier: None
(bootloader) secure-boot: yes
(bootloader) unlocked: no
(bootloader) product: dory
(bootloader) partition-size:aboot: 80000
(bootloader) partition-type:aboot: emmc
(bootloader) partition-size:boot: 1600000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:recovery: 1600000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:system: 10000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:userdata: c2400000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: 10000000
(bootloader) partition-type:cache: ext4
(bootloader) partition-sizeersist: 1000000
(bootloader) partition-typeersist: ext4
all:
finished. total time: 0.096s
Bill Yi said:
hi All,
Today, we pushed a kernel project for kitkat-wear release. The kernel source can be found on the android-msm-dory-3.10-kitkat-wear branch in the kernel/msm project. It has the following tags:
android-4.4w_r9 Factory-ROM
android-4.4w_r10 Update #1
bill
Click to expand...
Click to collapse
There is a 2nd factory rom now, I need a dump of it if anyone happens to recieve a new g watch with the 2nd factory rom.
I still do not have a dump of KMV78N also.
HTC One M8 ATT GSM Converted from Stock Sense > ViperRom > CM11 > GPE Conversion (Firmware Included)
I have two of these devices mine worked fine when I moved to the Skydragon 5.0 Rom, I installed the firmware, followed the instructions in the thread, no issues. On my other phone this has been an issue.
On the phone in questions it is unlocked, rooted, S-Off. Here are the issues I am experiencing and what I have tried.
Issue: Cannot install custom recovery (philz,cwm or TWRP)
- Tried via fastboot - Reports successful, no change.
- Tried via hboot - Reports Update Failed, Reboot, no change.
- Tried via TWRP application - TWRP crashes, no change
Issue: Any changes made to the phone are reverted on reboot including app updates, installations, progress in media, anything.
Issue: In fastboot usb mode, if I enter the command "fastboot oem rebootRUU" the phone will simply reboot, so I have to try to flash firmware via hboot.
Issue: The phone will randomly reboot.
I have tried:
1. Flashing custom recoveries. (multiple ways, multiple version, multiple types)
2. Flashing RUU (multiple via hboot, all fail)
3. Flashing FUU (via windows) (Stock, Full Wipe, It reboots the phones and then claims no USB connection)
4. e2fsck -fn the /dev/block/mmcblk0p47 - Reports Errors cannot be fixed. I can't do anything with the drive mounted, and cannot access adb in recovery so, not sure...
5. wp_mod.ko ( can insmod while the phone is booted, any changes to the install-recovery.sh are lost on reboot so it does not stick)
6. Tried flashing the partition fix 1.54 splash for the GPE converted devices (again via hboot, failed)
7. Different cables, different USB ports, and every other guides I could find on XDA
8. Tried factory reset from recovery and phone OS.
I have available to me on the phone
Stock GPE Recovery - No ADB shell
ADB access while phone is booted, including root shell
Fastboot access in bootloader, minus ability to access rebootRUU
Here is some data output below, and if I can provide anything else I am more than happy to do so. Appreciate any help you all can provide me on this.
--GETVAR--
$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.14.21331931.LA02_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.16.1700.16
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT43KWM01872
(bootloader) imei: <redacted>
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: a1aef34e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.016s
--BANNER--
*** Unlocked ***
M8_UL_CA PVT SHIP S-OFF
CID-GOOGL001
HBOOT-3.18.0.0000
RADIO-1.14.21331931.LA02_2G
OpenDSP-v32.2.2-00542-M8974.0213
OS-1.16.1700.16
eMMC-boot 2048
Mar 21 2014, 22:29:15.0
--ROOT DF--
[email protected]_m8:/ # df
Filesystem Size Used Free Blksize
/dev 913.8M 128.0K 913.6M 4096
/sys/fs/cgroup 913.8M 12.0K 913.7M 4096
/mnt/asec 913.8M 0.0K 913.8M 4096
/mnt/obb 913.8M 0.0K 913.8M 4096
/system 1006.7M 786.2M 220.5M 4096
/data 26.3G 3.6G 22.7G 4096
/cache 678.4M 10.8M 667.6M 4096
/devlog 29.5M 20.4M 9.1M 4096
/fataldevlog 19.6M 13.5M 6.2M 4096
/firmware/radio 199.8M 44.3M 155.5M 4096
/firmware/adsp 199.8M 8.9M 190.9M 4096
/firmware/wcnss 199.8M 3.8M 196.0M 4096
/custdata 49.2M 4.0M 45.2M 4096
/mnt/shell/emulated 26.3G 3.6G 22.7G 4096
/storage/emulated 913.8M 0.0K 913.8M 4096
/mnt/media_rw/ext_sd 29.8G 4.1G 25.8G 4096
--LSMOD--
[email protected]_m8:/ # lsmod
wlan 3543984 0 - Live 0x00000000 (O)
adsprpc 21680 3 - Live 0x00000000
ecryptfs 88689 0 - Live 0x00000000
dm_crypt 22668 0 - Live 0x00000000
texfat 178608 0 - Live 0x00000000 (PO)
--FSCK OUTPUT--
[email protected]_m8:/sdcard2/untitled folder # ./fsck.ext4 -f -n /dev/block/platform/m>
e2fsck 1.42.9 (28-Dec-2013)
Warning! /dev/block/platform/msm_sdcc.1/by-name/userdata is mounted.
Warning: skipping journal recovery because doing a read-only filesystem check.
Pass 1: Checking inodes, blocks, and sizes
Deleted inode 83039 has zero dtime. Fix? no
Inodes that were part of a corrupted orphan linked list found. Fix? no
Inode 164419 was part of the orphaned inode list. IGNORED.
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: -(328880--328887) -524802 +524803 -(560736--560754) -(4719168--4719203) -(4796672--4796759)
Fix? no
Free blocks count wrong for group #17 (13436, counted=13417).
Fix? no
Free blocks count wrong for group #146 (5013, counted=4925).
Fix? no
Free blocks count wrong (5946355, counted=5946561).
Fix? no
Inode bitmap differences: -83039 -164419
Fix? no
Free inodes count wrong (1733054, counted=1733358).
Fix? no
/dev/block/platform/msm_sdcc.1/by-name/userdata: ********** WARNING: Filesystem still has errors **********
/dev/block/platform/msm_sdcc.1/by-name/userdata: 20034/1753088 files (4.8% non-contiguous), 1065997/7012352 blocks
4|[email protected]_m8:/sdcard2/untitled folder #
***UPDATE*** I was able to get the phone into RUU mode via this command:
adb -s HT43KWM01872 shell /system/bin/reboot oem-78
So here is the output of my attempt to flash a custom recovery as well as flash the RUU. The RUU flash completes with the failure, but before I am able to re-flash it. The device reboots and I am back into the OS.
rr at RR-MBP in ~/Desktop
$ fastboot flash recovery openrecovery-twrp-2.6.3.3-m8_0.6.img
target reported max download size of 1830715392 bytes
sending 'recovery' (11164 KB)...
OKAY [ 1.191s]
writing 'recovery'...
OKAY [ 0.674s]
finished. total time: 1.866s
rr at RR-MBP in ~/Desktop
$ fastboot flash zip RUU-HTC_One_M8_GPE_4.4.4-2.12.1700.1.zip
target reported max download size of 1830715392 bytes
sending 'zip' (567002 KB)...
OKAY [ 19.168s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) total_image_number=7
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
(bootloader) current_image_number=0
(bootloader) current_image_number=1
(bootloader) current_image_number=2
(bootloader) current_image_number=3
(bootloader) current_image_number=4
(bootloader) current_image_number=5
(bootloader) current_image_number=6
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 20.477s
I am fully willing to pay for anyone's time in helping solve this, paypal or bitcoin. I am out of ideas.
Ok, have you tried renaming the RUU to 0PBIMG and hboot flashing ? Let me know what happens...the 2.12.1700.1 RUU has stock recovery, so remove it b4 you flash the renamed RUU.
jxcorex28 said:
Ok, have you tried renaming the RUU to 0PBIMG and hboot flashing ? Let me know what happens...the 2.12.1700.1 RUU has stock recovery, so remove it b4 you flash the renamed RUU.
Click to expand...
Click to collapse
Thanks for your response, I appreciate it. I have indeed tried the RUU that way, it will either say "update failed" or it will attempt the update and the phone reboots and I am back to this weird saved state. I had some advice from graffixnyc to try booting from a recovery (non-flased) which I have all cause the phone to reboot and lose any changes. I have also tried the RUU.EXE for the Dev Edition, GPE Edition, Stock and all of them start to run and then reboot and lose connection.
Something on the phone has somehow saved a state that it returns to on every reboot. So you can even rm -rf the entire /system from an adb shell su'd as root. It will delete everything, and when you reboot the phone, its all right back to the same state. You can add, modify, delete, anything on the device you want, but as soon as it reboots it will lose it.
The reboot is what is killing me on every front. The only thing that I found that was odd is yesterday I tried running the RUU.exe for the dev edition and running two at the same time. What happened is the first one detected my firmware as 2.12 which is incorrect, the second one that ran (while the first one was still running) reported the firmware as 1.16 (correct). However while that "seemed" to get farther, the phone rebooted, and...you guessed it... all changes were lost.
So what on earth would allow the device to have this "saved "state" that it returns to? If I delete files via rm -rf then I would expect I am either not actually interacting with the filesystem or it is overwriting it with a saved img from somewhere? Confused as hell by this.
*edit* I even tried DD every partition I could from adb shell and nothing took from a known good stock backup. Nothing took.
Here is the output from trying to run the fastboot commands that graffixnyc had suggested to me.
System> About Phone
--Model Number: HTC ONE_M8
--Android Version: 4.4.4
--Baseband Version: 1.14.21331931.LA02_2G_20.30A.4145.01L
--Kernel Version: 3.4.0-gb1b6fb1 | [email protected] #1v| Mon Jul 16 18:49:22 CST 2014
--Build Number: KTU84P.H1 release keys
Phone:
adb
$ adb devices
List of devices attached
HT43KWM01872 device
$ adb reboot bootloader
*** Unlocked ***
M8_UL_CA PVT SHIP S-OFF
CID-GOOGL001
HBOOT-3.18.0.0000
RADIO-1.14.21331931.LA02_2G
OpenDSP-v32.2.2-00542-M8974.0213
OS-1.16.1700.16
eMMC-boot 2048
Mar 21 2014, 22:29:15.0
$ fastboot devices
HT43KWM01872 fastboot
$ fastboot boot 1.16.1700.16.recoverygpe.img
creating boot image...
creating boot image - 25167872 bytes
downloading 'boot.img'...
OKAY [ 1.607s]
booting...
OKAY [ 0.002s]
finished. total time: 1.608s
Phone Flashed Black Screen then back to bootloader:fastboot usb
$ fastboot boot stock\ recovery\ 1.12.1540.17\ recovery.img
creating boot image...
creating boot image - 25167872 bytes
downloading 'boot.img'...
OKAY [ 1.599s]
booting...
OKAY [ 0.002s]
finished. total time: 1.600s
Phone Flashed Black Screen then back to bootloader:fastboot usb
$ fastboot boot stock\ recovery\ 1.22.980.1\ recovery.img
creating boot image...
creating boot image - 25167872 bytes
downloading 'boot.img'...
OKAY [ 1.592s]
booting...
OKAY [ 0.002s]
finished. total time: 1.594s
Phone Flashed Black Screen then back to bootloader:fastboot usb
$ fastboot boot 3.11.1700.5.recovery.img
creating boot image...
creating boot image - 13539328 bytes
downloading 'boot.img'...
OKAY [ 1.249s]
booting...
OKAY [ 0.002s]
finished. total time: 1.250s
$ fastboot oem writecid 11111111
...
(bootloader) Start Verify: 0
(bootloader) Input CID is super CID
(bootloader) Start Verify: 0
OKAY [ 0.025s]
finished. total time: 0.025s
$ fastboot oem readcid
...
(bootloader) cid: 11111111
OKAY [ 0.010s]
finished. total time: 0.010s
Tried fastboot booting from the 4 recovery again with supercid, but after each phone screen flash to black the cid was reset to GOOGL001
Tried booting to RUU mode and repeating the commands above, with same result.
Just for kicks I tried adb shell , su, remounted / as rw. Then ran "rm -rf /" (don't do that ever) which ran and deleted stuff until the phone rebooted. Well, guess what. Phone rebooted and it's like nothing happened. Right back to the saved state. Time to jtag this thing?
good evening
Help solve the problem.
Watch A1612, there was a customized firmware with a Russian.
I tried to roll it 2,8,0,5 did not work, the clock just does not start, an eternal reboot.
I tried to roll back to 1.3.0n by the instructions
https://forum.xda-developers.com/smartwatch/amazfit/tutorial-unbrick-huami-amazfit-t3547300
The firmware was installed, when trying to update on OTA to 1.3.8a immediately after the reboot I receive an inscription on the screen "ERROR" and an exclamation mark.
Help me please.
Thank you
C:\adb\huangheUS-1.3.0n>fastboot getvar all
(bootloader) version-bootloader: U-Boot 2013.07-00096-gf3b140c
(bootloader) version-baseband: N/A
(bootloader) version-hardware: V1.1 20130322
(bootloader) version-cdma: N/A
(bootloader) variant: watch
(bootloader) serialno: 0123456789abcdef
(bootloader) product: watch
(bootloader) secure: no
(bootloader) unlocked: yes
(bootloader) uart-on: NO
(bootloader) partition-size:bootloader: 0x0000
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:recovery: 0x1000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:boot: 0x2000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:system: 0x3000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x4000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x5000
(bootloader) partition-type:userdata: ext4
(bootloader) max-download-size: 0x4000000
all:
Finished. Total time: 0.280s
Flash latest INTL stock, then before you start it:
Code:
adb wait-for-device
adb shell reboot bootloader
fastboot erase data
fastboot erase cache
fastboot erase userdata
fastboot reboot
lfom said:
Flash latest INTL stock, then before you start it:
Code:
adb wait-for-device
adb shell reboot bootloader
fastboot erase data
fastboot erase cache
fastboot erase userdata
fastboot reboot
Click to expand...
Click to collapse
Did you mean - flash latest international ROM 2.8.0.5 and after implement your code?
Could you please describe in more details?
Thanks
ExtrimVF said:
Did you mean - flash latest international ROM 2.8.0.5 and after implement your code?
Could you please describe in more details?
Thanks
Click to expand...
Click to collapse
Exactly what you said (and that's what I said previously).
lfom said:
Exactly what you said (and that's what I said previously).
Click to expand...
Click to collapse
I've done exactly what you said.
Installed latest ROM by this link
https://forum.xda-developers.com/smartwatch/amazfit/fw-tool-stock-firmware-installers-2017-t3725494
and run script what you gave me.
Now i have always booting watch
Please help
ExtrimVF said:
I've done exactly what you said.
Installed latest ROM by this link
https://forum.xda-developers.com/smartwatch/amazfit/fw-tool-stock-firmware-installers-2017-t3725494
and run script what you gave me.
Now i have always booting watch
Please help
Click to expand...
Click to collapse
Try this if you are on Windows:
Code:
adb wait-for-device & adb reboot wipe
or this on Linux/macOS:
Code:
adb wait-for-device; adb reboot wipe
If you still cannot boot, I suggest and you use the code I gave you before to fully erase data on watch, then use the unbrick tutorial but flash an old firmware like 1.3.0 first, then try to boot watch.
Could you please help me to find right instruction and rom package?
Based on the below bootloader information and the 'ls -l /dev/block/platform/mtk-mdsc.0/by-name' results, can anyone help me understand whether I am able to copy a new boot or recovery image to my generic MediaTek tablet using dd. I am able to access fastboot, but fastboot doesn't seem to have very many commands available, or it has proprietary fastboot commands specific to this generic device. In fact, there is a dedicated partition named 'flashinfo' that I can copy using dd but I do not know how to view (decompile) this .img file. I have pulled an .img file from every partition if this would be helpful to someone willing to take the time to help me out. Any direction would be greatly appreciated.
############################
Bootloader Information:
(bootloader) max-download-size: 0x8000000
(bootloader) partition-size:userdata: 32000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: 1a800000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: ff000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:metadata: 2360000
(bootloader) partition-type:metadata: raw data
(bootloader) partition-size:tee2: 500000
(bootloader) partition-type:tee2: raw data
(bootloader) partition-size:tee1: 500000
(bootloader) partition-type:tee1: raw data
(bootloader) partition-size:expdb: a00000
(bootloader) partition-type:expdb: raw data
(bootloader) partition-size:logo: 800000
(bootloader) partition-type:logo: raw data
(bootloader) partition-sizeara: 80000
(bootloader) partition-typeara: raw data
(bootloader) partition-size:secro: 600000
(bootloader) partition-type:secro: ext4
(bootloader) partition-size:recovery: 1000000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:boot: 1000000
(bootloader) partition-type:boot: raw data
(bootloader) partition-size:lk: 60000
(bootloader) partition-type:lk: raw data
(bootloader) partition-size:seccfg: 40000
(bootloader) partition-type:seccfg: raw data
(bootloader) partition-sizeersist: 3000000
(bootloader) partition-typeersist: ext4
(bootloader) partition-sizerotect2: a00000
(bootloader) partition-typerotect2: ext4
(bootloader) partition-sizerotect1: a00000
(bootloader) partition-typerotect1: ext4
(bootloader) partition-size:nvram: 500000
(bootloader) partition-type:nvram: raw data
(bootloader) partition-sizeroinfo: 300000
(bootloader) partition-typeroinfo: raw data
(bootloader) partition-sizereloader: 40000
(bootloader) partition-typereloader: raw data
(bootloader) off-mode-charge: 1
(bootloader) warranty: yes
(bootloader) unlocked: no
(bootloader) secure: yes
(bootloader) kernel: lk
(bootloader) product: ALONG8163_E_86VM
(bootloader) version: 0.5
all: Done!!
Finished. Total time: 0.018s
How do I unlock this bootloader? Can I use dd to replace a partition based on the bootloader data provided? Notably I tried using dd to copy a Magisk_Patched.img to the boot partition, but both efforts resulted in a bootloop
(I also noticed that the lk (Linux Kernel) and boot partitions are distinct on this device. Is this unusual? Is it possible that this is why Magisk is not working?)
###########################
Results from 'ls -lF /dev/block/platform/mtk-mdsc.0/by-name':
please post in proper sections questions go to q/a
Is this a Hiteker tablet?
If so I have got the same tablet, rooted it, and installed TWRP
Still having OTG driver issues.
Yes
Would you share the TWRP image?
Twilight Time said:
Is this a Hiteker tablet?
If so I have got the same tablet, rooted it, and installed TWRP
Still having OTG driver issues.
Click to expand...
Click to collapse
Yes.
Would you share the TWRP image?
excaliber8878 said:
Based on the below bootloader information and the 'ls -l /dev/block/platform/mtk-mdsc.0/by-name' results, can anyone help me understand whether I am able to copy a new boot or recovery image to my generic MediaTek tablet using dd. I am able to access fastboot, but fastboot doesn't seem to have very many commands available, or it has proprietary fastboot commands specific to this generic device. In fact, there is a dedicated partition named 'flashinfo' that I can copy using dd but I do not know how to view (decompile) this .img file. I have pulled an .img file from every partition if this would be helpful to someone willing to take the time to help me out. Any direction would be greatly appreciated.
############################
Bootloader Information:
(bootloader) max-download-size: 0x8000000
(bootloader) partition-size:userdata: 32000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: 1a800000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: ff000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:metadata: 2360000
(bootloader) partition-type:metadata: raw data
(bootloader) partition-size:tee2: 500000
(bootloader) partition-type:tee2: raw data
(bootloader) partition-size:tee1: 500000
(bootloader) partition-type:tee1: raw data
(bootloader) partition-size:expdb: a00000
(bootloader) partition-type:expdb: raw data
(bootloader) partition-size:logo: 800000
(bootloader) partition-type:logo: raw data
(bootloader) partition-sizeara: 80000
(bootloader) partition-typeara: raw data
(bootloader) partition-size:secro: 600000
(bootloader) partition-type:secro: ext4
(bootloader) partition-size:recovery: 1000000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:boot: 1000000
(bootloader) partition-type:boot: raw data
(bootloader) partition-size:lk: 60000
(bootloader) partition-type:lk: raw data
(bootloader) partition-size:seccfg: 40000
(bootloader) partition-type:seccfg: raw data
(bootloader) partition-sizeersist: 3000000
(bootloader) partition-typeersist: ext4
(bootloader) partition-sizerotect2: a00000
(bootloader) partition-typerotect2: ext4
(bootloader) partition-sizerotect1: a00000
(bootloader) partition-typerotect1: ext4
(bootloader) partition-size:nvram: 500000
(bootloader) partition-type:nvram: raw data
(bootloader) partition-sizeroinfo: 300000
(bootloader) partition-typeroinfo: raw data
(bootloader) partition-sizereloader: 40000
(bootloader) partition-typereloader: raw data
(bootloader) off-mode-charge: 1
(bootloader) warranty: yes
(bootloader) unlocked: no
(bootloader) secure: yes
(bootloader) kernel: lk
(bootloader) product: ALONG8163_E_86VM
(bootloader) version: 0.5
all: Done!!
Finished. Total time: 0.018s
How do I unlock this bootloader? Can I use dd to replace a partition based on the bootloader data provided? Notably I tried using dd to copy a Magisk_Patched.img to the boot partition, but both efforts resulted in a bootloop
(I also noticed that the lk (Linux Kernel) and boot partitions are distinct on this device. Is this unusual? Is it possible that this is why Magisk is not working?)
###########################
Results from 'ls -lF /dev/block/platform/mtk-mdsc.0/by-name':
Click to expand...
Click to collapse
You can push the image using dd. I have replaced the system, boot, and recovery img using this method. I used a gen 2 tablet with Material Terminal to connect using adb. You first have to put the adb keys in the root of the gen 2 tablet to connect to a gen 3. Let me know if this helps
excaliber88787 said:
Yes Would you share the TWRP image? Yes. Would you share the TWRP image?
Click to expand...
Click to collapse
excaliber88787 said:
Yes Would you share the TWRP image? Yes. Would you share the TWRP image?
Click to expand...
Click to collapse
Twilight Time said:
You can push the image using dd. I have replaced the system, boot, and recovery img using this method. I used a gen 2 tablet with Material Terminal to connect using adb. You first have to put the adb keys in the root of the gen 2 tablet to connect to a gen 3. Let me know if this helps
Click to expand...
Click to collapse
I am no longer in a situation where I have any tablet images. On a technicality my situation has changed for the much better after 32 years. I made the TWRP when I had nothing but time on my hands, now time is a premium to me.
Twilight Time said:
I am no longer in a situation where I have any tablet images. On a technicality my situation has changed for the much better after 32 years. I made the TWRP when I had nothing but time on my hands, now time is a premium to me.
Click to expand...
Click to collapse
Twilight Time said:
I am no longer in a situation where I have any tablet images. On a technicality my situation has changed for the much better after 32 years. I made the TWRP when I had nothing but time on my hands, now time is a premium to me.
Click to expand...
Click to collapse
excaliber88787 said:
Yes
Would you share the TWRP image?
Yes.
Would you share the TWRP image?
Click to expand...
Click to collapse
hey did you ever get to change your os on your tablet?if so i got same1 can you assist
excaliber88787 said:
Would you share the TWRP image?
Click to expand...
Click to collapse
port for Alldocube iplay10 pro Android 9 sdk 28 display res 1200*1920 proc MT8163 kernel Linux version 4.9.117 ([email protected] // TWRP 3.0.2
ro.sf.lcd_density=240
ro.sf.hwrotation=0
busybox is static from Android 9
-----------------------------------------
donor teclast A10S Android 7.1.2 sdk 25 display res 1200*1920 proc MT8163 kernel Linux version 3.18.35 ([email protected]// TWRP 3.3.1
ro.sf.hwrotation=180
------------------------------------------
donor Teclast P80h (D4C5) TWRP 3.0.2-1 tablet is Android 5.1 sdk 22 kernel Linux version 3.10.72 ([email protected] ... and display res 1280*800 proc MT8163 // TWRP 3.0.2-1
ro.sf.hwrotation=0
10.91 MB file on MEGA
mega.nz
---------------------------------------
port for U804mc . tablet is Android 5.1 sdk 22 kernel Linux version 3.10.72 ([email protected] ... and display res 1024*600 proc MT8163 // recovery-P80Hv5.img // TWRP 3.0.2
MTK Header
ro.sf.lcd_density=160
ro.sf.hwrotation=180
---------------------------------------
donor Alldocube iPlay 10 . tablet is Android 6. sdk 23 kernel Linux version 3.18.22 . ... and display res 1920*1080 proc MT8163 // TWRP 3.1.1
MTK Header
ro.sf.lcd_density=280
-------------------------------------
port for Alldocube iPlay 8 . tablet is Android 6. sdk 23 kernel Linux version 3.18.22 . ... proc MT8163 // TWRPi8 3.1
MTK Header
ro.sf.lcd_density=180
------------------------------------------
donor Aquaris_M8 tablet is Android 6 //display res 1280 x 800 // proc MT8163 // twrp-3.6.2_9-
ro.sf.lcd_density=180
Download twrp-3.6.2_9-0-Aquaris_M8.img
Download page for twrp-3.6.2_9-0-Aquaris_M8.img
dl.twrp.me
----------------------------------------
port for Alldocube iplay10 pro Android 9 sdk 28 display res 1200*1920 proc MT8163 kernel Linux version 4.9.117 ([email protected] // TWRP 3.3.1
ro.sf.lcd_density=240
ro.sf.hwrotation=0
busybox is static from Android 9
---------------------------------------------
[TWRP][RECOVERY] Asus ZenPad 8.0 Z380M (locked bootloader ok)
This is for real, folks. The first working custom recovery for Asus ZenPad 8.0 Z380M and a method to flash it under a locked bootloader. This took quite a bit of work to make, partly due to having to find a way to bypass the locked bootloader...
forum.xda-developers.com
donor Asus ZenPad 8.0 Z380M tablet is Android 7 sdk 25 //display res1280x800 // proc MT8163 // kernel Linux version 3.18.35+ ([email protected]) (gcc version 4.9 20150123 (prerelease) (GCC) ) #1 SMP PREEMPT Fri Jan 12 13:14:25 CST 2018 // TWRP 3.2.1
ro.sf.hwrotation=0
MTK Header
-------------------------------------------------
[RECOVERY] TWRP for Onn Android Tablets (unofficial) - 2019-11-30
TWRP Custom Recovery for the Onn Android Tablet series This is the first fully-featured custom recovery for Walmart's MediaTek-based Onn tablets: ONA19TB002, ONA19TB003 and ONA19TB007. TWRP needs no introduction. If you have come here, you...
forum.xda-developers.com
donor Android 9 sdk 28 proc MT8163 // twrp 3.3.1_9
ro.sf.hwrotation=270 landscape
----------------------------------------------
port for Alldocube iplay10 pro Android 9 sdk 28 display res 1200*1920 proc MT8163 kernel Linux version 4.9.117 ([email protected] // TWRP 3.3.1
ro.sf.lcd_density=240
ro.sf.hwrotation=0
replace /sbin/libminuitwrp.so for hwrotation=0
Thanks for your help
I'll try it
Hello
Can you email me when you get a chance??
I really want to hear from you.
[email protected]
Twilight Time said:
I am no longer in a situation where I have any tablet images. On a technicality my situation has changed for the much better after 32 years. I made the TWRP when I had nothing but time on my hands, now time is a premium to me.
Click to expand...
Click to collapse
Are you doing good??
Hopefully you can get a chance to say hello soon...
Da3mo9z said:
Thanks for your help
I'll try it
Click to expand...
Click to collapse
Did you make a backup? unlock your tablet? If you give me the link to your firmware on google disk I'll try to help you with TWRP.....I need stock recovery boot scatter and some files, depends on your Android version
Hi all,
I am a newbie to custom ROM's world and this is my attempt to it. My device is Moto G5s Plus.
To start with I had an encrypted phone running Android 8. Encryption was mandatory to install some work related apps. Because of sluggish performance I thought to install custom ROM.
Here are the steps I followed:
1. Installed minimal ADB on my laptop running Win10. Connected phone and successfully unlocked bootloader.
2. Rebooted phone in recovery mode and installed 'PixelExperience_Plus_sanders-11.0-20210310-1753-OFFICIAL.zip'.
3. Rebooted the device and everything was working fine till now (restored from google backup and restarted several times to make sure things were working fine).
4. Now as I mentioned I need to encrypt phone for bussiness reasons. So I selected 'Settings->Encrypt Phone'. For very small time a green iconed screen appeared and then phone rebooted.
5. After reboot, a screen with google logo (G) with a small progress bar (kept moving left to right and vice-versa) appeared. I left it for more than 12 hours still hung at same screen.
6. Now I tried to wipe Dalvik/ART cache and cache. This is where problem started happening. I tried few other things (could not recollect exactly). I even tried to erase 'data' from fastboot using 'fastboot erase userdata'.
7. When nothing worked, I thought of installing Pixel Experience 11 plus again from TWRP. The process went smooth but towards the end it showed:
'Failed to mount '/data' (invalid argument)' error.
I am attaching snapshots and logs. Its been more than 3 days being stuck on this issue. Really appreciate any help.
Please let me know if any info is required.
Also since I dont have any data to worry about, so I am open to any suggestion (wipe/format). I have SD card and OTG with me.
Once the phone is up and running, I need to encrypt it back. So please suggest steps while keeping this requirement in mind.
Look for this issue on youtube and you'll find the steps to fix it.
It looks like you have a corrupt file system.
You can fix it using TWRP.
Good luck !
Hi,
I tried multiple steps to fix this issue but none helped.
As for now looks like I have made some progress. What I did was i flashed official firmware for Moto G5s plus as mentioned on below page:
Flash official firmware Moto G5s Plus [sanders]
So far, we have had the guides for you to unlock the bootloader in Moto G5s Plus or how to install TWRP on Moto G5s Plus and today, I am going to show you how to download and Install stock ROM in Moto G5s Plus. So if you probably have already...
forum.xda-developers.com
With this I got the device up and running with Android 7. Below is the full log of fastboot getvar all command:
<<<
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all > and7_var
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C2.06
(bootloader) product: sanders
(bootloader) board: sanders
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SAMSUNG RC14MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY322C5JGB
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: E89B73CE00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 356477084164615
(bootloader) meid:
(bootloader) date: 10-13-2017
(bootloader) sku: XT1804
(bootloader) battid: SB18C15119
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon Jul 13 4:57:41 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/sanders_n/sanders_n:7.1.1
(bootloader) ro.build.fingerprint[1]: /NPSS26.116-26-4/4:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.26.201.4.sanders.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-03800-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g419eefd0-000
(bootloader) kernel.version[1]: 54-g1b4a83e ([email protected]) (gcc ve
(bootloader) kernel.version[2]: rsion 4.9 20150123 (prerelease) (GCC) )
(bootloader) kernel.version[3]: #1 SMP PREEMPT Mon Oct 16 22:03:44 CDT 2
(bootloader) kernel.version[4]: 017
(bootloader) sbl1.git: git=MBM-NG-VC2.06-0-gb564bed
(bootloader) rpm.git: git=MBM-NG-VC2.06-0-g5578f74
(bootloader) tz.git: git=MBM-NG-VC2.05-1-g425b927
(bootloader) devcfg.git: git=MBM-NG-VC2.05-1-g425b927
(bootloader) keymaster.git: git=MBM-NG-VC2.05-1-g425b927
(bootloader) cmnlib.git: git=MBM-NG-VC2.05-1-g425b927
(bootloader) cmnlib64.git: git=MBM-NG-VC2.05-1-g425b927
(bootloader) prov.git: git=MBM-NG-VC2.05-1-g425b927
(bootloader) aboot.git: git=MBM-NG-VC2.06-0-g1e22c44
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retin
all: listed above
finished. total time: 0.121s
>>>
Now i have Android 7 up and running. Now I opened TWRP again, and flashed 'PixelExperience_Plus_sanders-11.0-20210310-1753-OFFICIAL.zip'. Though this process works fine but after reboot it is again stuck at Google logo (G) screen.
Please help. I have spent 2-3 days working this out.
Regards.
Hey man.
In order to flash PE 11, like the ROM topic says, you "MUST" be on latest modem baseband ...
You "ONLY" obtain that by flashing the latest OREO 8.1 ROM.
So, you should flash latest Oreo you have and update it till there are no more updates.
Read PE 11 topic again. There you can find out about what i'm saying here.
Hope this helps and again,
Good luck !
Thanks a lot Damage1972 for showing the way forward
Between how did you figured out if this is the issue here?
Based on your suggestion, I flashed stock Android v8.1 and updated it till there are no updates. Phone was rebooting fine. After this, I flashed PE 11 plus and again phone is stuck at Google logo (G) screen.
Between below are logs:
<<
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C2.12
(bootloader) product: sanders
(bootloader) board: sanders
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SAMSUNG RC14MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY322C5JGB
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: E89B73CE00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 534773760
(bootloader) reason: Volume down key pressed
(bootloader) imei: 356477084164615
(bootloader) meid:
(bootloader) date: 10-13-2017
(bootloader) sku: XT1804
(bootloader) carrier_sku:
(bootloader) battid: SB18C15119
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon Jul 13 9:30:53 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/sanders_n/sanders_n:8.1.0
(bootloader) ro.build.fingerprint[1]: /OPS28.65-36-14/63857:user/release
(bootloader) ro.build.fingerprint[2]: -keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.271.12.sanders.re
(bootloader) ro.build.version.full[1]: tail.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gfde333e (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Tue Aug 13 15:23:08 CDT 2019
(bootloader) sbl1.git: git=MBM-NG-VC2.12-0-g698fb2f
(bootloader) rpm.git: git=92e5e21-dirty
(bootloader) tz.git: git=d95e83f
(bootloader) devcfg.git: git=d95e83f
(bootloader) keymaster.git: git=d95e83f
(bootloader) cmnlib.git: git=d95e83f
(bootloader) cmnlib64.git: git=d95e83f
(bootloader) prov.git: git=d95e83f
(bootloader) aboot.git: git=MBM-NG-VC2.12-0-g07ff23c
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retin
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
finished. total time: 0.065s
>>
Please suggest.
Thanks and Regards.
No problem,man.
About the issue, it's listed on the pre requests in order to flash PE 11 !
It's very clear written on the first page and comments on the topic.
Carefully read the ROM's topic before flashing...
About your phone still stuck on boot : did you go through the steps to correct your phone file system ? And (sorry to ask you this) how did you flash the ROM ?
Did you do a Clean Flash ?
Check your messages.
Also, try this , that's what worked for me :
How to fix unable to mount data internal storage 0mb in twrp permanently :
Note : This will wipe/format your Data partion and your data will be reset. INSTRUCTIONS : 1) Reboot your device into TWRP Recovery. 2) Go to Wipe menu. 3) Go to Advance Wipe. 4) Select Data and go to Repair or Change File System. 5) Click...
forum.xda-developers.com
So few updates:
1. Looks like my mount data internal storage 0 mb issue is resolved (flashed stock ROM and then custom ROM and did not see this error).
2. Regarding how I flashed stock ROM Android 8.1. I downloaded 'Motorola_Moto_G5S_Plus_XT1804_SANDERS_RETAIL_8.1.0_OPSS28.65-36-9_CID50_8.1.0.zip' image from:
Motorola Moto G5S Plus XT1804 Stock ROM Firmware (Flash File)
Download the official Motorola Moto G5S Plus XT1804 Stock Firmware (Flash File) for your Motorola Smartphone. We also provide all other Motorola Stock Firmware.
motostockrom.com
and executed below commands in order:
<<
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition sanders81/gpt.bin
fastboot flash bootloader sanders81/bootloader.img
fastboot flash modem sanders81/NON-HLOS.bin
fastboot flash fsg sanders81/fsg.mbn
fastboot flash dsp sanders81/adspso.bin
fastboot flash logo sanders81/logo.bin
fastboot flash boot sanders81/boot.img
fastboot flash recovery sanders81/recovery.img
fastboot flash system sanders81/system.img_sparsechunk.0
fastboot flash system sanders81/system.img_sparsechunk.1
fastboot flash system sanders81/system.img_sparsechunk.2
fastboot flash system sanders81/system.img_sparsechunk.3
fastboot flash system sanders81/system.img_sparsechunk.4
fastboot flash system sanders81/system.img_sparsechunk.5
fastboot flash system sanders81/system.img_sparsechunk.6
fastboot flash system sanders81/system.img_sparsechunk.7
fastboot flash system sanders81/system.img_sparsechunk.8
fastboot flash system sanders81/system.img_sparsechunk.9
fastboot flash system sanders81/system.img_sparsechunk.10
fastboot flash oem sanders81/oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot flash fsg sanders81/fsg.mbn
fastboot oem fb_mode_clear
fastboot reboot
>>
After that I was able to turn ON phone with Android 8.1.0. Checked for updates and installed them (i guess there were 3 security updates). Once done, entered bootloader and installed TWRP and flashed PE 11 plus. After reboot, it is again stuck at google logo (G) screen.
One more suggestion i need: Since I have spent a lot of time debugging this and ultimately I have to encrypt my phone. So below queries:
A. Is there any known issue with PE 11 plus on my G5S plus? If so, any workaround?
B. Is it discouraged to encrypt G5S plus running PE 11?
C. I am using 'Settings->Encrypt Phone' to encrypt phone. Should I try any other way?
Thanks and Regards.
andromeda1410 said:
A. Is there any known issue with PE 11 plus on my G5S plus? If so, any workaround?
B. Is it discouraged to encrypt G5S plus running PE 11?
C. I am using 'Settings->Encrypt Phone' to encrypt phone. Should I try any other way?
Thanks and Regards.
Click to expand...
Click to collapse
Correct. Encryption doesn't work yet on PE 11 (actually it doesn't work on most Sanders ROMs). If encryption + SELinux enforcing is important for you, stock ROM is the only option.
Thanks sBinnala for help. At this point I am convinced that I will not install custom ROM. So I want to have stock ROM (Android 8.1) preferably.
Thing is yesterday I installed Android 8.1 stock rom (exact steps mentioned above), worked fine. Flashed PE 11 plus and phone got stuck at google logo screen. Searched again and though it to be some modem related issue hence I did below steps as mentioned on https://forum.xda-developers.com/t/rom-11-sanders-pixelexperience-normal-plus-aosp.4247243/ by Jorge:
<<
It is recommended that you are using the latest firmware for the Moto G (5S) Plus.
to update via twrp:
Modem only:
https://sourceforge.net/projects/ne...5-36-14_v2.0-modem-only_20210307.zip/download
Modem, Fsg & dsp:
https://sourceforge.net/projects/ne...S28.65-36-14_v2.0-modem_20210307.zip/download
>>
So I flashed Modem, Fsg & dsp: (second zip) and re-flashed PE 11 plus. Again that did not worked. Now again I tried to flash stock Android 8.1 ROM. It worked but now it is not detecting SIM., showing IMEI as 0 or not available.
I have found multiple pages on similar issue but none is working. Looks like this issue is because of persist file and epf partition which I dont have (infact i dont have any backup).
So can someone please help me in installing stock Android 8.1 which should work fine (sim should be detected). Any help will be deeply appreciated.
Edit: Tried installing Validus and following steps mentioned on https://forum.xda-developers.com/t/...ork-imei-0-after-flashing-custom-rom.3745474/ but issue not resolved.
If it matters, mine is 4 GB/64 GB, XT 1804 variant.
On some threads, i found inconsistency in architecture (like 32 bit and 64 bit). What is that? I know i have 32 bit TWRP running on a 64 bit Windows 10 machine. I am not sure about stock ROM architecture. Can someone tell me how to check stock ROM architecture?
On another notes: I have tried flashing below stock roms but none of them are working fine (device boots but unable to recognize SIM):
- Motorola_Moto_G5S_Plus_XT1804_SANDERS_RETAIL_8.1.0_OPSS28.65-36-9_CID50_8.1.0_Android8.1.zip
- SANDERS_NPSS26.116-26-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml_Android7.zip
- SANDERS_NPSS26.116-61-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
- Stock-Sanders_OPS28.65-36-14_v2.0-modem_20210307.zip
- Validus-sanders-8.1.Beta.1.3-OFFICIAL-20180128-0506.zip
Regards.
Further update:
Looks like I have created a backup using TWRP of original ROM (which was Android 8.1 but encrypted). Zipped it using Android app and then I transferred it to Windows laptop (later realized i should not have done it). Unzipped in android device and placed it in OTG. Restored using TWRP but it is not booting.
Can I do anything now? That is, should I preserve any file which I can later use with stock Android 8.1 ROM which can help me with getting sim signal/IMEI number back.
sBinnala said:
Correct. Encryption doesn't work yet on PE 11 (actually it doesn't work on most Sanders ROMs). If encryption + SELinux enforcing is important for you, stock ROM is the only option.
Click to expand...
Click to collapse
Encryption works flawlessly with Arrow 11 vanilla.
Thanks everyone for helping me here.
Current situation:
Yes, I have a backup of stock ROM created using TWRP just after unlocking bootloader. The problem with this backup could be:
a. My phone was earlier encrypted.
b. As I was trying a lot of things and given I have 8 GB memory card, I took the backup on memory card, zipped it on memory card (using android app on phone) and then transferred to my PC. Later i transferred it back to memory card, unzipped using other Android phone and restored using TWRP.
As a result I am unable to boot my phone, It stucks at 'Your device may be unlocked ....' screen.
I have stock ROM for Android7 and Android8. I can flash any of them using fastboot. Phone boots ok but the only problem is, it is not detecting my sim card any more. IMEI number is also gone/disabled.
My phone has unlocked bootloader but is still not-rooted (and I would like to keep it this way).
Given i have spent last few days in trying various things, i have changed my expectations to below:
I no longer want any custom ROM.
I just want my phone to boot fine and every functionality like sim detection, IMEI etc to work fine (though i am fine with any android version but would prefer Android 8).
So basically I want to start fresh and have any fully-functional Android on my moto G5S plus Sanders XT1804 4 GB/64GB, dual SIM, Indian variant.
Regards.
okayk said:
Encryption works flawlessly with Arrow 11 vanilla.
Click to expand...
Click to collapse
Arrow isn't enforcing - it's permissive, which in itself is a huge security risk. Like I said, we don't have a ROM which supports both SELinux enforcing and encryption at the same time.
andromeda1410 said:
Thanks everyone for helping me here.
Current situation:
Yes, I have a backup of stock ROM created using TWRP just after unlocking bootloader. The problem with this backup could be:
a. My phone was earlier encrypted.
b. As I was trying a lot of things and given I have 8 GB memory card, I took the backup on memory card, zipped it on memory card (using android app on phone) and then transferred to my PC. Later i transferred it back to memory card, unzipped using other Android phone and restored using TWRP.
As a result I am unable to boot my phone, It stucks at 'Your device may be unlocked ....' screen.
I have stock ROM for Android7 and Android8. I can flash any of them using fastboot. Phone boots ok but the only problem is, it is not detecting my sim card any more. IMEI number is also gone/disabled.
My phone has unlocked bootloader but is still not-rooted (and I would like to keep it this way).
Given i have spent last few days in trying various things, i have changed my expectations to below:
I no longer want any custom ROM.
I just want my phone to boot fine and every functionality like sim detection, IMEI etc to work fine (though i am fine with any android version but would prefer Android 8).
So basically I want to start fresh and have any fully-functional Android on my moto G5S plus Sanders XT1804 4 GB/64GB, dual SIM, Indian variant.
Regards.
Click to expand...
Click to collapse
Normally in such cases, restoring EFS backup will do the trick. Have you already tried that?
After days of investigation, debugging and trying out everything which any post said, I have resolved my issue now. I now have a fully functional Android 8.1 installed on my phone, I am able to make calls, IMEI number is back.
In interest of wider public let me post what worked for me:
Note:
My device is Moto G5S Plus XT1804, 4 GB/64 GB, Retin Channel, India based phone. It is unrooted but has unlocked bootloader.
I have tried a lot many things, flashed many ROMs from different channels but none of them worked.
Below is what worked for me.
Probable issue: During flashing gpt.bin I was getting below error:
<<
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.074s
>>
I guess this is the core issue. I searched on it and got many forums. Finally below solution worked for me:
Downloaded stock Android 8.1 rom 'stockrom.net_XT1804_SANDERS_RETIN_8.1.0_OPS28.65-36-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip' for my device from: https://www.stockrom.net/2020/04/xt1804-retin-oreo-ops28-65-36-14.html
Unzipped this file and placed it at 'C:\Program Files (x86)\Minimal ADB and Fastboot'.
Created my own batch file using instructions mentioned in 'stockrom.net_XT1804_SANDERS_RETIN_8.1.0_OPS28.65-36-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml/flashfile.xml'.
Imp note: Do not use fastboot commands mentioned on any forum. Every rom (custom/stock) has a flashfile.xml or servicefile.xml. Open this file and create your own batch file with steps in order mentioned in xml file.
Booted my phone in fastboot mode (volume down + power). Connected phone with PC using usb cable.
Launch 'Minimal ADB and Fastboot' on windows PC. Note: i am attaching all tools that i used to rest version related questions.
Run the batch file you created in step #3.
With these steps, I was able to get my phone up and running. Thanks a lot to all members for their help.
Regards.
Reference links:
How to Restore Stock Firmware on Moto G (All Models)
Follow this guide to restore stock firmware on Moto G. The instructions will work for Moto G 1st Gen, 2nd Gen, 3rd Gen, 4th Gen, Moto G5/Moto G5 Plus, and Moto G5S/Moto G5S Plus. The Moto G series is…
www.thecustomdroid.com
G5s Plus XT1804 RETIN (SANDERS) 8 Oreo StockRom OPS28.65-36-14
Download Firmware + Tutorial Completo para Instalação Stock Rom Moto G5s Plus XT1804 (SANDERS) Android 8.1.0 Oreo Loop, Boot Infinito ou Hard Reset
www.stockrom.net
Tutorial – Instalação Stock Rom Motorola no Modo Fastboot (Snapdragon, Moto G, Moto E, Moto X, Moto Z, Moto C, Moto M, One) + Video Tutorial - Stock Rom
Como instalar firmware nos motorolas com processadores snapdragon, moto g1 ao g7, procedimento simples, instalador com 1 clique, sem linhas de comando.
www.stockrom.net
(These pages are in non-english. I used google translator for understanding it)