Database Info

SailfishOS 3 for Photon Q and siblings

Code:
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it!
SailfishOS 3 for Photon Q
Continuation from 2.0 thread to keep most important information in first post. Thanks to vevgeniev for initial port, without it I would never buy Photon Q.
Repo with my apps is added to image. Packages can by installed via terminal:
Code:
devel-su zypper in "package name"
Images
{
"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"
}
Click to expand...
Click to collapse
Installation
Download and flash cm-11-20150626-SNAPSHOT-XNG3CAO1L8-moto_msm8960_jbbl.zip via twrp-3.0.2-0-asanti_c.img according to ordinary cm instruction. Use ext4 filesystem for /data partition. Boot to android and make sure everything works.
Download SailfishOS 4 image (open browser in private mode if onedrive ask you to login) and flash it over cyanogenmod. It's compressed tarball so installation may take even 10 minutes.
OTA
Read about Stop Releases and make backup using TWRP
Code:
/usr/share/sfos-moto_msm8960_jbbl-adaptation/upgrade.sh
# after reboot execute pkcon refresh to update all repositories
For any issues with upgrade.sh script download more up-to-date version, add --verbose argument or execute commands from real-upgrade.sh manually: https://build.sailfishos.org/packag...bl:4.4.0.68/sfos-moto_msm8960_jbbl-adaptation
At first boot tracker might slow down phone and eat a lot of storage. If it's too resource hungry move your media files out of device or create .nomedia empty file to exclude particular directory from tracker. Then force reset it:
Code:
tracker reset --hard
Custom Bootlogo
vevgeniev created a custom bootlogo:
Instruction how to use it
Known issues
Half screen mirror glitch occurs sometimes. Blank/unblank display fixes it
Sometimes removing files does not have any effect, i.e. free space doesn't increase and sdcard can't be unmounted. Could be easily triggered by mtp or dd usage. For sdcard access use FileZilla (SFTP).
QProcess:startDetached can hang randomly. Workaround added to fingerterm. Looks like it's bug in Qt and it is not photon q specific: https://together.jolla.com/question/202337/bug-fingerterm-terminal-freezes-after-opening-new-window
There are no 2.XG, 3.XG network indicators.
glReadPixels() return empty content in some cases. This means no screen recording, screenshots and thumbnails in browser. Workaround for screenshots added to lipstick.
All bugs at first boot are features.
FAQ
Q: How to run apk?
A: It's not android, you can't
Q: Can I switch between hardware keyboard layouts?
A: Default xkb layout switch shortcut: "shift + sym". You need to also set second keyboard layout:
dconf write /desktop/lipstick-jolla-home/layout "'us,ru'"
Click to expand...
Click to collapse
In newer releases layouts can be enabled in settings and switched via "shift + space"
Tips
Fast way to restart lipstick:
shift + tab + k
Alt + Tab like switching (if you have sailfishos-alttab-patch installed):
OK + tab
To disable volume media keys:
dconf write /apps/photonq-helper/mediaKeysEnabled 0
batt_health can cause reported battery capacity decrease which I am not sure works correctly at least on my aging battery. It's disabled since 3.3.0 in 2 places in /init.target.rc. Therefore btry will not report Aged Capacity anymore.
To use h264 (hardware accelerated) decoder in youtube set in about:config media.mediasource.webm.enabled to false
user name is still 'nemo' instead 'defaultuser' even for latest releases
Changelog
4.4.0.68
* Partially usable browser. Javascript doesn't cause crash on almost all sites like in 4.0-4.3 sfos. Tabs in landscape mode are unusable.
* Using browser probably breaks video encoding/decoding ('vid_dec_open() max number of clientslimit reached' in dmesg). Killing minimediaservice/browser usually helps.
* Disabled sailjail, and enabled start up boosters back.
* Few general sfos bugs more (see patchmanager catalogue for my patches)
4.3.0.15 - No for daily use, just required Stop Release
4.2.0.21 - No for daily use, just required Stop Release
4.1.0.24 - No for daily use, just required Stop Release
4.0.1.48
Broken browser
3.4.0.24 - Latest usable version
Fix memory leak when taking screenshot
Add workaround for remembering wlan state after reboot in airplane mode
Media keys works only in locked screen
3.3.0.16
NFC pn544 plugin added
batt_health disabled in /init.target.rc
glibc 2.30, gcc 8.3
3.1.0.12
kernel: hold volume up/down to select next/previous song
droid-hal-init: disable mpdecision due to constant cpu usage
3.0.3.9
Patch glibc for 3.0 kernel
3.0.2.8
Handle system and data partition automatically
New methods to wake up sensors
3.0.1.11
kernel: Fix crashes caused by new firewall rules
kernel: Experimental multi LUNs support
droidmedia: Fix random audio/video fail in browser
usb-moded: Mass storage was dropped in upstream. Use patched one
Click to expand...
Click to collapse
XDA:DevDB Information
SailfishOS 3 for Photon Q, ROM for the Motorola Photon Q 4G LTE
Contributors
elros34, vevgeniev
Source Code: https://github.com/elros34?utf8=✓&tab=repositories&q=msm8960&type=&language=
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2018-11-23
Last Updated 2019-08-20

Thanks for maintaining this for our devices @elros34
I have been meaning to try Sailfish for some time on my RAZR HD (xt926) and i finally got around to it the other day only to find that it wont boot up.
As per the 2.0 thread i can flash CM11 and that will boot and work fine but once i flash Sailfish over the top it wont boot past the bootloader unlocked logo. I have tried both the xt907 and photonq zips but neither will boot.
The xt907 zip did shown some signs of something happening since the led would light up either orange or white but after leaving it for 45 mins with no other signs of life i gave up on it.
Please find attached a list of my device drivers using the following command:
Code:
ls -alR /dev
Are there any chances of this running on my xt926 ?

Thanks, so it has xt907 like partition table, you can't use photon q image. LED glowing means system is booting.
Boot to TWRP then:
Code:
rm /data/.stowaways/sailfishos/init_disable_telnet
Now reboot, connect phone to usb and telnet to it:
Code:
telnet 192.168.2.15 2323
In windows you can use putty but it's hard to copy logs from it.
Then wait a while so logs are complete and run:
Code:
dmesg
journalctl --no-page
logcat
evdev_trace -I

elros34 said:
Thanks, so it has xt907 like partition table, you can't use photon q image. LED glowing means system is booting.
Boot to TWRP then:
Code:
rm /data/.stowaways/sailfishos/init_disable_telnet
Now reboot, connect phone to usb and telnet to it:
Code:
telnet 192.168.2.15 2323
In windows you can use putty but it's hard to copy logs from it.
Then wait a while so logs are complete and run:
Code:
dmesg
journalctl --no-page
logcat
evdev_trace -I
Click to expand...
Click to collapse
Thanks @elros34
Please find attached the various logs from my xt926.
Note i'm still running Sailfish 2.1.3.7, i figured it would be easier to start with that but if needed i can re-run these on 3.0.0.8
I have no idea what most of it means for the most part but a few errors did stand out to me in particular
Code:
Dec 12 20:20:16 Sailfish systemd[1407]: Failed to start The lipstick UI.
Could this possibly explain why its not booting any further?

Lipstick fails to start because xt926 use different touchscreen driver. Change "/dev/touchscreen" to "/dev/input/event1" in /var/lib/environment/compositor/droid-hal-device.conf
Also paste output of:
Code:
udevadm info -a /dev/input/event1

elros34 said:
Lipstick fails to start because xt926 use different touchscreen driver. Change "/dev/touchscreen" to "/dev/input/event1" in /var/lib/environment/compositor/droid-hal-device.conf
Also paste output of:
Code:
udevadm info -a /dev/input/event1
Click to expand...
Click to collapse
Thanks @elros34 its working now after changing the touchscreen driver boots up fine. I'm not seeing any immediate issues but will see how i get on with it. First impressions are very good, a really nice os i'm actually surprised at how fast and fluid it is.
Here is the output of
Code:
udevadm info -a /dev/input/event1
Code:
sh-3.2# udevadm info -a /dev/input/event1
Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.
looking at device '/devices/i2c-3/3-0048/input/input1/event1':
KERNEL=="event1"
SUBSYSTEM=="input"
DRIVER==""
looking at parent device '/devices/i2c-3/3-0048/input/input1':
KERNELS=="input1"
SUBSYSTEMS=="input"
DRIVERS==""
ATTRS{name}=="melfas-ts"
ATTRS{phys}=="3-0048/input0"
ATTRS{properties}=="2"
ATTRS{uniq}==""
looking at parent device '/devices/i2c-3/3-0048':
KERNELS=="3-0048"
SUBSYSTEMS=="i2c"
DRIVERS=="melfas-ts"
ATTRS{drv_debug}=="Debug Setting: 0"
ATTRS{drv_reset}=="Reset: HIGH"
ATTRS{hw_irqstat}=="Interrupt line is HIGH."
ATTRS{ic_reflash}=="No firmware loading in progress."
ATTRS{irq_enabled}=="Interrupt: 1"
ATTRS{latency_debug}=="Latency Debug Setting: 0"
ATTRS{latency_times}==""
ATTRS{latency_values}=="Touch Latency Time: Average 0uS, High 0uS,0 interrupts of 0 were slow"
ATTRS{name}=="melfas-ts"
looking at parent device '/devices/i2c-3':
KERNELS=="i2c-3"
SUBSYSTEMS=="i2c"
DRIVERS==""
ATTRS{name}=="QUP I2C adapter"
I'll also see if i can convert some of the other xt925 and xt926 users for testing.

Absolutely love this - haven't had a single problem yet. Thank you so much elros34.

Could somebody check what "getprop ro.product.device" returns for xt926 or xt907 with sailfish installed?

mounting /dev/mmcblk0p39 on /data failes
Hi,
at first i would like to thank you for building SFOS3 for the Photon Q series, i bought another XT907 to finally get SF running on this pretty nice and tiny handset.
As @drkdeath5000 i stuck at the bootloader unlocked screen but with another problem as the touchscreen driver for his XT926.
I think it's a problem with the partition table here the error from /init.log
mount: mounting /dev/mmcblk0p39 on /data failed: No such file or directory
I followed the installation instructions you provided and flashed cm11, which is booting without issues. I already tried it with and without wiping dalvik/cache, with and without booting to cm11 first. So i would really appreciate your help. If i can provide some more detail just tell me.
Best regards
André

rkdeath5000 get further because he used old xt907 image, you can't use photon q image in XT907.
I have tried to support all devices in one image. I even prepared untested script to update kernel but need a nice way to distingnues between devices. No feedback so far.
Few days ago I came up with different an idea how to auto detect correct partitions in all devices but so far I am struggling with some serious issue in 3.0.2 so I am not sure when I will release it.

elros34 said:
Could somebody check what "getprop ro.product.device" returns for xt926 or xt907 with sailfish installed?
Click to expand...
Click to collapse
On my XT907 it returns scorpion_mini

Thank you for your fast response,
as you recommended Version Alpha3 is running but of course i would like to run SFOS3 So i would like to help you in any way possible.
Best regards
André

If you could test whether this image works (boots without issue and touchscreen works) then it would be great. This is image I just built with new method to detect correct partitions but without all needed patches for middleware so other bugs are not important for now.

Thank you so much! I can hardly tell you how happy you made me I always wanted i tiny handset running on SFOS and finally after i already had given up on that your rom make it happen.
I just started some basic testing on it, as i want to wait for the screen protector before starting to really use it so i'll give you a feedback on the rom later.

3.0.2.8 Released as OTA and new image probably for all moto_msm8960_jbbl devices.
Also I created new patch for Alt+Tab (OK + Tab key) like switching between windows. It's added to my obs repo.

So far the new version alpha9 installs without issues on the XT907. Right now i have just one problem, as in version alpha8 I'm not able to send text messages (SMS). I tried different sim cards from two different networks, so i think it's a problem within the ROM. How could i help you on this? Maybe collecting some logs?

What about Alpha3 or android? To boot android you don't have to flash whole system, just boot cm11 kernel via fastboot. Have you tried to set "Prefer 3G" in cellular settings?
To get most basic logs, reboot phone and try to send sms, then:
Code:
dmesg
journalctl --no-page
logcat -b radio
If it's something more serious then you will need to follow:
https://jolla.zendesk.com/hc/en-us/articles/203761078-How-to-collect-SMS-logs-

Thanks so much for 3.0.2.8 - works great. Really hope you're able to give us a 3.0.3 with the updated browser.
Don't know if you have any interest/knowledge on Maemo Leste or PMOS, but since you're the most knowledgeable person on the Photon Q, just wondered if you could hazzard a guess as to how possible it might be to get them working on this device further down the line?
Thanks again.

Yes, updated browser is tempting so I will definitely bring 3.0.3 when it will be available for ported devices.
Unfortunately I have never ported Leste or Postmarketos so I have limited knowledge here.
With Photon there are several issue like: no sim without modification and no flex cable to buy. Also we are stuck with android drivers and ancient 3.0 kernel with no chance for upstream. It means to run anything (in usable form) other than android we need libhybris. I think there are better devices with more active developers for these systems: droid 4 - have ongoing upstream efforts, Fxtec pro1 for sure will have 4.x or even 5.x kernel. That's why you will not find photon in actively supported devices in postmarketos or leste site.
- Leste use hildon-desktop (x window manager) so it would be probably not trivial to get libhybris based ui acceleration if it's possible at all. Is that os even daily usable?
- After a quick read of Postmarketos wiki looks like it support wayland based compositor like weston so it is a good sign. I was able to run libhybris accelerated weston in ubuntu chroot in sailfish. It has some touch issues but it may be because I run it nested in lipstick. From what I understand if device doesn't have upstream kernel then postmarketos requires ported halium and lxc containers. That might be not possible because of 3.0 kernel but you will never know until you try.
Take everything I said with a grain of salt and start porting. For halium you will probably need newer base than cm11. There are few important commits which are needed otherwise kernel will not work.

SMS issue could be general ofono bug: https://together.jolla.com/question...installing-3028/?answer=205366#post-id-205366
Jolla is focused on android8 base so older bases are neglected. Upstream libhybris is also broken for hybris-11 base.

[ROM][UNOFFICIAL][10] LineageOS 17.0 for K-touch i9 mini-phone (Anica i9) (MT6739)

Introduction
This is the LineageOS 17.0 (non-GSI) port for K-touch i9 a.k.a Anica i9. Due to the lack of kernel source code, this port comes with a prebuilt kernel image, but the ramdisk has been updated to support a proper System-as-Root system partition as is required by Android 10.
This is ONLY compatible with the MT6739 variant of this phone.
About the phone
The K-touch i9 is an ultra-mini phone produced by K-touch (Ktouch / Anica) based on the MT6739 SoC. I got the phone purely due to its interesting size (similar to the Palm phone) and the desire to port real custom ROMs to it to see if they can work well. I mainly use it as a backup phone, so this port might not be thoroughly tested enough for daily drive.
Known Issues
- Some particular animation / gifs will skip frames or repeat incorrectly
Images
{
"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"
}
Flashing instructions
1. Unlock the phone (reboot to bootloader by holding volume up on boot, run `fastboot flashing unlock` and confirm)
2. Flash TWRP image from here
3. Reboot to recovery (hold volume up and choose Recovery accordingly)
4. Backup all stock partitions whatever way you like (especially boot / vendor)
5. Flash this LOS 17 port image and format data
6. Reboot and enjoy
Please note that after flashing this LOS 17 image, you have to restore the stock boot.img before being able to install A-only Android 10 GSIs again. Although you MIGHT be able to boot phh A/B GSI 10 on the boot.img of this LOS 17 port, please note that this is not tested and you still need to shrink the image size before phh GSIs can work -- the same as the A-only situation.
Why not GSI
There is no reason why not to use a phh GSI on this phone, given that phh GSIs work pretty well and I have actually fixed a few bugs for it too and I absolutely love it. However we can't play with some certain things, for example, transitioning to System-as-Root, in a GSI, and that's why I started this port just for fun. Also this device has such a small system partition that GSIs won't work out-of-the-box and require some manual adjustments just for the device, which kind of defeats the purpose. Nevertheless, I will contribute my fixes to GSIs so that things will work as well on GSIs as on my device-specific ROM ports.
Downloads
20191025: https://www.androidfilehost.com/?fid=4349826312261605900
Alternatively, you may check the latest updates to both the TWRP and the LOS 17 port on my GitHub
Source code
https://github.com/PeterCxy/android_device_ktouch_i9
There is no kernel source code available for this device, unfortunately.
Credits
all the people that have worked on MTK devices before me.

twrp link does not work

theleftykid said:
twrp link does not work
Click to expand...
Click to collapse
It works here. It links to a GitHub release page where you can download recovery.img for TWRP

Hi,
I bought this phone, but with different CPU- MT6580, 5MP camera at the back, would this ROM be compatible with it well?
I've tried to flash the TWRP recovery, but it failed - "FAILED (remote: size too large)" so it mean the recovery image not compatible with my phone?
This device is really nice, but huge let down by the operation sys. The battery drain really fast, always "phone idle" take place at the top of battery consuming chart.
Thank you!

hi, i have tried to flash the twp from your github site. i get an error that flashing was FAILED, file is too large. my unit is Ktouch/anica i9s with October 2019 update.
is there any chance you can upload the original recovery.img as well pls.. thank you.

theleftykid said:
hi, i have tried to flash the twp from your github site. i get an error that flashing was FAILED, file is too large. my unit is Ktouch/anica i9s with October 2019 update.
is there any chance you can upload the original recovery.img as well pls.. thank you.
Click to expand...
Click to collapse
Based on the previous comment before you, you seem to have the MT6580 version of the phone. This means you have a different and smaller gpt than the one from the OP that uses MT6739. You can't flash this ROM or any recovery from the MT6739 since they have different hardware and different partition layout. If you flash something, it will end with a nice brick
Cheers!

Rortiz2 said:
Based on the previous comment before you, you seem to have the MT6580 version of the phone. This means you have a different and smaller gpt than the one from the OP that uses MT6739. You can't flash this ROM or any recovery from the MT6739 since they have different hardware and different partition layout. If you flash something, it will end with a nice brick
Cheers!
Click to expand...
Click to collapse
Well, I’m sending myne back to get the mt3739 so I could mount 128gb sd card and to try this buil. It look promissing.

theleftykid said:
hi, i have tried to flash the twp from your github site. i get an error that flashing was FAILED, file is too large. my unit is Ktouch/anica i9s with October 2019 update.
is there any chance you can upload the original recovery.img as well pls.. thank you.
Click to expand...
Click to collapse
You boot into the original OS and the recovery will be back.

Thank you for this ROM.
I used it on my K-touch i10. Its the same as the i9 but the shape is slightly different.
I have the 3gb - 64gb version and it seems OK.
I had to use BiTGApps-Q for Playstore to appear.
I also had to go into the USB developer options to set up file transfer from a PC.
And no wallpaper app from holding on home screen.
I hope you keep this up to date else I might have to try and work out how to apply security patches.
Thanks again
EDIT. Oh so are you saying I could just try and install the GSI?
Edit. OK so Wellbeing and problems with Gapps is to do with Android 10 and gapps.

I also found twrp hard to control. The swipe action and pressing near the edge was difficult.
I don't have face recognition to unlock, not sure if that's because lineage os doesn't have it or the i9 doesn't, but certainly possible on my i10.
The swipe action in lineage is also difficult.
Thanks again. Just want to let you know.
Edit. Also a problem for me is when it's charging, touch screen gives the odd ghost press when used.
Ive found forcedoze useful with this phone.

Works with K-Touch M16?
Theoretically speaking this Rom should work in the K-Touch M16 as it has the exact same specs, processors, etc. Being the only difference is that it has a fingerprint sensor.
So I was wondering does anyone know if this custom ROM and TWRP works on the K-Touch M16.?

how do i download this rom. there are no active links available!

PeterCxy said:
Downloads
20191025: https://www.androidfilehost.com/?fid=4349826312261605900
Alternatively, you may check the latest updates to both the TWRP and the LOS 17 port on my GitHub
Source code
https://github.com/PeterCxy/android_device_ktouch_i9
There is no kernel source code available for this device, unfortunately.
.
Click to expand...
Click to collapse
From the first post

m16 tried
I have tried this with my M16, which is very similar to i9, same cpu same spec, got fingerprint though... no luck, unable to boot into recovery, anyone successfully done?

It worked with my K-touch i10.
I guess you should start looking at TWRP. If you have the same processor you should be able to get TWRP going.
Sorry no help here, maybe try a TWRP forum or something.

chinese bootloader
hi, i just got the phone so i wanted to flash this rom. but my bootloader is in chinese and i don't speak/read chinese.
can anyone here please help me get trough the bootloader so i do all the steps correctly.
i attached the picture from bootloader and also what google translate offers for translation.
does volume up and down works correctly on your devices? on my it just jumps one step down and up on ether up key or down key when i press and hold the key ti gradually turns volume up on ether up or down key.

I have an i10 and am no expert.
When I reboot and hold up-volune I get 3 options. Recovery, Fastboot and Normal in that order.
Are you sure your phone is the mt3769. As I had an i10 which was was MT6580 and I got those options. I did have Fastboot though. Sorry don't still have it for reference.

I just found out on youtube this menu should pop up when you press volume down + power on. But on my phone it also boots to this menu when i press volume up + power on. Guess i received defective volume buttons on my phone. Too bad as it is such a nice little phone.

Are you able to use the volume keys to move up and down the menu you took a picture of? Moving in this menu and selecting should be the up and down volume keys. Guess then you could see for sure if you have a key problem.
I did manage to take my phone apart as when I dropped it I managed to disconnect the screen cable inside but was lucky to be able to fix it.
---------- Post added at 12:23 PM ---------- Previous post was at 11:44 AM ----------
PeterCxy said:
...you still need to shrink the image size before phh GSIs can work...
...
Also, this device has such a small system partition that GSIs won't work out-of-the-box and require some manual adjustments just for the device, which kind of defeats the purpose. Nevertheless, I will contribute my fixes to GSIs so that things will work as well on GSIs as on my device-specific ROM ports.
Click to expand...
Click to collapse
Hello I'd like to update this for myself. I thought I'd use the GSI image but you say it needs resizing before use. Can you give me any pointers as to how you do this?

free30 said:
Are you able to use the volume keys to move up and down the menu you took a picture of? Moving in this menu and selecting should be the up and down volume keys. Guess then you could see for sure if you have a key problem.
I did manage to take my phone apart as when I dropped it I managed to disconnect the screen cable inside but was lucky to be able to fix it.
Click to expand...
Click to collapse
i am unable to enter the correct bootloader that gives you three options you mentioned before. i already contacted the seller to see what we can do cause i just received the phone. on this chinese menu i can navigate only down (pressing volume up or down moves the selection down) and i can select the item via power button.

[OFFICIAL/UNOFFICIAL] LineageOS 19.1 for Amlogic G12*/SM1 Family Devices

{
"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"
}
Amlogic G12*/SM1 Family Devices
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 19.1 thread for the Amlogic G12*/SM1 SoC family of devices.
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed:
Official Builds:
deadpool - Google ADT-3
wade - Dynalink TV Box (4K)
Disclaimer: My unofficial builds have full Android TV Google Apps and some other goodies included. OTA's roll roughly once a month. Support not guaranteed or implied.
Unofficial Builds:
deadpool - Google ADT-3
dopinder - Walmart Onn UHD Box
sabrina - Chromecast with Google TV
wade - Dynalink TV Box (4K)
We also support a few development boards, but at least (for now, until we have time to write up instructions), you're on your own to figure out the install process and set things up:
m5 - Banana Pi M5
odroidc4 - Odroid C4
radxa0 - Rock Pi Radxa Zero
EDIT: The development boards don't boot on LineageOS 19.1 at the moment for some reason, we're looking into it.
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
Recent apps/Multitasking menu doesn't launch.
(sabrina only) The remote firmware sometimes gets hung up, you can reboot to solve this issue.
(dopinder/sabrina) L1 is currently broken, this is what is holding up official builds for these devices.
Notes:
GApps are baked in on Unofficial builds - No, I will not be building without GApps included for this device. These builds are built, packaged, and signed by me, and not affiliated with LineageOS whatsoever.
Firmware is shipped in the ROM package for this device, so you'll end up on the newest version of compatible firmware after install. Please don't touch firmware partitions after install.
On the unofficial OTA is provided the same way officials would have them.
Find any more on an official build? Report them according to this guide.
FAQ:
Does L1 Widevine DRM break when I unlock my bootloader?
Nope, it works fine. L1 certificates, and the mechanism that reports is all still exist and work as expected.
Can I haz Netflix?
Yup! Play Store has it for you. Unless you're on dopinder or sabrina, but that will be fixed soon hopefully.
Is this Android TV or Google TV?
Android TV, with some of the better components of Google TV.
Can I go back to stock and relock the bootloader?
Yeah, grab the factory image for your device and flash it just like you would for a Pixel device, you can find the factory images here. Don't know it I'd relock though, consider that process largely untested on these device. Especially on sabrina, where you can't necessarily re-unlock should you ever want to.
Are these the stock codenames for these devices?
Astute observation, no, they are not. The ADT-3 is actaully `adt3`, but earlier in production is was `deadpool`, which is much cooler. The Dynalink box internally is extremely similar to the ADT-3, so we coined it `wade` after Wade Wilson, AKA deadpool. The Onn box is in the same family, but different enough to coin it `dopinder`, after, well, go watch Deadpool the movie I guess. sabrina is actually the codename given by Google - no clue as to the reason.
Does it pass SafetyNet?
Maybe - the only sure fire way it Magisk, as our boot loader is unlocked and can't be relocked safely.
Does the stock remote work?
Yup, just like it would on stock, in-remote-microphone and all! If it's an IR remote like wade's, it will even work in recovery!
Can we we support higher resolution than 4K, higher FPS, or HDR on non-certified screens?
Nope.
I have a very similar device! Can I install these builds and use them?
No. Please don't do that. You will brick your device, as we include firmware and bootloader images.
If you're a developer looking to help port to a new device, contact me.
Kernel Source: https://github.com/LineageOS/android_kernel_amlogic_linux-4.9
Contributors:
npjohnson
bgcngm
stricted
webgeek1234
deadman96385
trautamaki
luca020400
aleasto

i probably will write up install instructions for the `BananaPi-M5` and `Odroid C4` Soon™
its a bit more complicated than just booting into recovery and flashing it unfortunately

I managed to install this on the onn 4k tv box (I used a usb keyboard and flash drive in the recovery) and everything went fine while installing but now I'm just stuck at the boot animation. I've left it on for at least 30 minutes and it never goes anywhere. Here's the serial log: https://paste.ee/p/7PAxS
It pretty much just stops there except for the occasional healthd battery message.

Do these builds support Signature Spoofing to replace GApps with MicroG?

Big Dumb Object said:
Do these builds support Signature Spoofing to replace GApps with MicroG?
Click to expand...
Click to collapse
No, as MicroG doesn't emulate what Android TV needs. Different GMSCore.

lmore377 said:
I managed to install this on the onn 4k tv box (I used a usb keyboard and flash drive in the recovery) and everything went fine while installing but now I'm just stuck at the boot animation. I've left it on for at least 30 minutes and it never goes anywhere. Here's the serial log: https://paste.ee/p/7PAxS
It pretty much just stops there except for the occasional healthd battery message.
Click to expand...
Click to collapse
yeah, aware of the issue, it's video firmware not loading, building new builds now.
But for what it's worth, you don't need a keyboard or drive - you can adb sideload it over usb - easiest method, just like the wiki describes.

npjohnson said:
No, as MicroG doesn't emulate what Android TV needs. Different GMSCore.
Click to expand...
Click to collapse
Sad. I vaguely recalled something about that, but couldn't find any concrete proof when asked.
Please consider releasing the full Android as it was with Shield TV. I believe it will be in demand, given the negative attitude of a lot of power users towards Android TV.

Big Dumb Object said:
Sad. I vaguely recalled something about that, but couldn't find any concrete proof when asked.
Please consider releasing the full Android as it was with Shield TV. I believe it will be in demand, given the negative attitude of a lot of power users towards Android TV.
Click to expand...
Click to collapse
Eh, maybe once we're in a more functional state (eg. Hardware OMX gets fixed).

npjohnson said:
yeah, aware of the issue, it's video firmware not loading, building new builds now.
But for what it's worth, you don't need a keyboard or drive - you can adb sideload it over usb - easiest method, just like the wiki describes.
Click to expand...
Click to collapse
I couldn't figure out how to navigate the recovery menu. I tried the button on the side like in the stock recovery but pressing it did nothing and holding it would change the highlight color to green but it didn't actually run the option that was highlighted. It was detecting the button presses (there were keyevents in the serial log) so it isn't just a broken button. I tried doing adb sideload without selecting the option but I just got `adb: sideload connection failed: closed`

lmore377 said:
I couldn't figure out how to navigate the recovery menu. I tried the button on the side like in the stock recovery but pressing it did nothing and holding it would change the highlight color to green but it didn't actually run the option that was highlighted. It was detecting the button presses (there were keyevents in the serial log) so it isn't just a broken button. I tried doing adb sideload without selecting the option but I just got `adb: sideload connection failed: closed`
Click to expand...
Click to collapse
okay, figured it out, you need to hand flash DTB before booting recovery, will update instructions

npjohnson said:
okay, figured it out, you need to hand flash DTB before booting recovery, will update instructions
Click to expand...
Click to collapse
Sounds good. One more question, is this build using a 64-bit kernel? I'd like to use the app for my drone on a big screen and this box would've been perfect if the stock kernel wasn't 32-bit.

lmore377 said:
Sounds good. One more question, is this build using a 64-bit kernel? I'd like to use the app for my drone on a big screen and this box would've been perfect if the stock kernel wasn't 32-bit.
Click to expand...
Click to collapse
64-bit kernel, 32-bit userspace - aiming to do 64 bit userspace someday.

Do you have an ETA for when the next builds will be done?

lmore377 said:
Do you have an ETA for when the next builds will be done?
Click to expand...
Click to collapse
they're uploaded now - sorry, got caught up putting out fires at work all day today lol

npjohnson said:
they're uploaded now - sorry, got caught up putting out fires at work all day today lol
Click to expand...
Click to collapse
I'll try it and flashing dtb for the button in recovery in a bit

lmore377 said:
I'll try it and flashing dtb for the button in recovery in a bit
Click to expand...
Click to collapse
DTBO/DTB - they need to be in sync.

npjohnson said:
DTBO/DTB - they need to be in sync.
Click to expand...
Click to collapse
I flashed the two (I got them from here) and now the button and usb otg don't work at all. I tried to flash back to stock but the box got stuck on the can't load android system screen and it was ignoring all my attempts at interacting with it (it was even ignoring Ctrl+C in uboot), but luckily I managed to boot into the lineage os recovery by putting it on a flash drive and holding down the button then wiping /misc thru the serial console.

lmore377 said:
I flashed the two (I got them from here) and now the button and usb otg don't work at all. I tried to flash back to stock but the box got stuck on the can't load android system screen and it was ignoring all my attempts at interacting with it (it was even ignoring Ctrl+C in uboot), but luckily I managed to boot into the lineage os recovery by putting it on a flash drive and holding down the button then wiping /misc thru the serial console.
Click to expand...
Click to collapse
I'll look into this... Can you try flashing the newest build through lineage recovery and wipe data?

npjohnson said:
I'll look into this... Can you try flashing the newest build through lineage recovery and wipe data?
Click to expand...
Click to collapse
Is there any way to activate sideload mode through adb shell or the serial console? Again, since the button isn't working (still works in uboot so it isn't a hardware issue) with the new dtb I can't navigate through the recovery menu.

lmore377 said:
Is there any way to activate sideload mode through adb shell or the serial console? Again, since the button isn't working (still works in uboot so it isn't a hardware issue) with the new dtb I can't navigate through the recovery menu.
Click to expand...
Click to collapse
Adb reboot sideload works, maybe just reboot sideload?
I'll go grab an Onn box at Walmart tmrw afternoon.
I know it works as 3 of our developers have and use it.
Just a matter of install process it seems...

[GUIDE] Assurance Wireless KonnectONE Moxee m2160 (MH-T6000) Rooting Guide

Assurance Wireless
KonnectONE Moxee m2160
4G-LTE Smartphone
Model No. MH-T6000
{
"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"
}
Rooting Guide​
OVERVIEW:
This guide outlines simplified instructions for rooting the Assurance Wireless Moxee MH-T6000 4G-LTE smartphone. To cater this guide to new and inexperienced members, I have provided a stock boot image pre-patched with the Magisk v26.1 systemless root solution.
PREREQUISITES:
First and foremost, you need an unlocked bootloader. If your bootloader is not yet unlocked, complete that task and then return here. XDA hosts a plethora of how-to guides on standard bootloader unlocking. You will also need a Windows PC or laptop running the Minimal ADB & Fastboot Tools (link provided below). It should be noted that this guide can be carried out on a Mac or Linux computer as well; however, for purposes of this guide, I am focusing solely on a Windows setup. It is highly recommended that your device be running firmware build number MH-T6000V1.0.OB010, with the March 5, 2023 security patch level. As OTA updates are rolled out for this device, I will try to keep this guide updated with a patched boot image that corresponds with the latest firmware build.
Finally, you will need the factory supplied, or a quality equivalent USB-A to USB-C charging/syncing cable.
DISCLAIMER:
By proceeding further, you are assuming sole responsibility for the integrity and operability of your smartphone. Rooting your device is a task that carries with it the inherent risk of bricking or otherwise rendering your phone inoperable. While this guide has been thoroughly tested on my own device, you have been warned. Proceed at your own risk.
INSTRUCTIONS:​
Download the ADB & Fastboot tools from the link below and install the program on your PC or laptop;​
Open your Windows File Explorer, navigate to your C: drive, Program Files x86, and locate the Minimal ADB & Fastboot folder. Copy this folder and paste it to your desktop. (This step is not required, but is recommended for easier access of the ADB & Fastboot path);​
Download the patched boot image from the below link and save the image in your ADB & Fastboot folder. Note: the filename for the patched boot image is patched_boot.img. The flashing commands assume that you leave the filename unchanged;​
Boot your phone into fastboot mode by first powering your device off, and then holding the power and volume down keys simultaneously until fastboot mode appears on your device display;​
Connect your smartphone to your Windows computer using the factory supplied or a quality equivalent USB-A to USB-C charging/syncing cable;​
Open your ADB & Fastboot folder and double click cmd-here.exe to open a command window. Execute this command to verify a proper fastboot connection:
Code:
fastboot devices
If properly connected, the command window will return an alphanumeric string consistent with your device serial number;​
Once a proper connection has been verified, execute this command:
Code:
fastboot flash boot patched_boot.img
Now execute:
Code:
fastboot reboot
Upon reboot, open your app drawer and tap on the Magisk app or its placeholder stub. Ensure you are connected to the internet, grant any permissions, and follow any prompts given by Magisk to update to the full version in order to complete the root environment setup. Magisk may reboot your device during this process.​
That's it. You're now rooted via the Magisk v26.1 systemless root solution.​
IMPORTANT NOTE:
In the unfortunate event that you get stuck in a boot loop or brick your device using this guide, my guide on unbricking this smartphone will get you back up and running fairly quickly. This guide can be used to restore both soft bricked and hard bricked devices. You can then return here and give rooting another go.
Moxee MH-T6000 Unbricking Guide​DOWNLOADS:
• Minimal ADB & Fastboot v1.4.3
• Magisk Patched Boot Image
THANKS & MENTIONS:
A huge thanks and shout-out to @omb714.1980 for donating the Moxee smartphone that made this rooting guide possible. You are a scholar and a gentleman, good sir. Thanks also to KonnectONE support specialist Faith Flores for releasing to me the factory firmware for this device.​

Viva La Android said:
Assurance Wireless
Moxee MH-T6000 4G-LTE
View attachment 5893661
Rooting Guide​
OVERVIEW:
This guide outlines simplified instructions for rooting the Assurance Wireless Moxee MH-T6000 4G-LTE smartphone. To cater this guide to new and inexperienced members, I have provided a stock boot image pre-patched with the Magisk v26.1 systemless root solution.
PREREQUISITES:
First and foremost, you need an unlocked bootloader. If your bootloader is not yet unlocked, complete that task and then return here. You will also need a Windows PC or laptop running the Minimal ADB & Fastboot Tools (link provided below). It should be noted that this guide can be carried out on a Mac or Linux computer as well; however, for purposes of this guide, I am focusing solely on a Windows setup. It is highly recommended that your device be running firmware build number MH-T6000V1.0.OB010, with the March 5, 2023 security patch level. Finally, you will need the factory supplied, or a quality equivalent USB-A to USB-C charging/syncing cable.
DISCLAIMER:
By proceeding further, you are assuming sole responsibility for the integrity and operability of your smartphone. Rooting your device is a task that carries the inherent risk of bricking or otherwise rendering your phone inoperable. While this guide has been thoroughly tested on my own device, you have been warned. Proceed at your own risk.
INSTRUCTIONS:​
Download the ADB & Fastboot tools from the link below and install the program on your PC or laptop;​
Open your Windows File Explorer, navigate to your C: drive, Program Files x86, and locate the Minimal ADB & Fastboot folder. Copy this folder and paste it to your desktop. (This step is not required, but is recommended for easier access of the ADB & Fastboot path);​
Download the patched boot image from the below link and save the image in your ADB & Fastboot folder;​
Boot your phone into fastboot mode by first powering your device off, and then holding the power and volume down keys simultaneously until fastboot mode appears on your device display;​
Connect your smartphone to your Windows computer using the factory supplied or a quality equivalent USB-A to USB-C charging/syncing cable;​
Open your ADB & Fastboot folder and double click cmd-here.exe to open a command window. Execute this command to verify a proper fastboot connection:
Code:
fastboot devices
If properly connected, the command window will return an alphanumeric string consistent with your device serial number;​
Once a proper connection has been verified, execute this command:
Code:
fastboot flash boot patched_boot.img
Now execute:
Code:
fastboot reboot
Upon reboot, open your app drawer and tap on the Magisk app or its placeholder stub. Ensure you are connected to the internet, grant any permissions, and follow any prompts given by Magisk to update to the full version in order to complete the root environment setup. Magisk may reboot your device during this process.​
That's it. You're now rooted via the Magisk v26.1 systemless root solution.​
DOWNLOADS:
• Minimal ADB & Fastboot v1.4.3
• Magisk Patched Boot Image
THANKS & MENTIONS:
A huge thanks and shout-out to @omb714.1980 for donating the Moxee smartphone that made this rooting guide possible. You are a scholar and a gentleman, good sir. Thanks also to the KonnectONE support team for releasing to me the factory firmware for this device.​
Click to expand...
Click to collapse
Lol. Now you post this. After unsuccessfully scouring the internet for the stock firmware. I finally did the same as you and simply reached out to konnectone and asked for it. I just came here to see if there was anyone here that is by far more knowledgeable than myself (not hard) interested to have the firmware and would post a guide like this one. Well done!
Would you happen to have a twrp recovery compiled for this device by chance? Or if not but planning on it would you let me know please. I would appreciate it!

scottfan81 said:
Lol. Now you post this. After unsuccessfully scouring the internet for the stock firmware. I finally did the same as you and simply reached out to konnectone and asked for it. I just came here to see if there was anyone here that is by far more knowledgeable than myself (not hard) interested to have the firmware and would post a guide like this one. Well done!
Would you happen to have a twrp recovery compiled for this device by chance? Or if not but planning on it would you let me know please. I would appreciate it!
Click to expand...
Click to collapse
I just got KonnectONE to agree to release firmware a couple of days before you mentioned having firmware. It's been a long wait indeed.
I don't have source code to compile TWRP; only the firmware. I will be attempting to port a TWRP build for this phone very soon. My legal battle with KonnectONE was in regards to source code under the General Public License 2.0. Because they were ultimately unable to provide kernel source, their legal team and support department finally acquiesced to provide firmware to device owners upon written request. I compromised for the firmware release, but was not able to get kernel source code for building TWRP. I am pretty confident that a ported TWRP can be ironed out as a stable build. I already have the base build selected.

Thank you so much! I have 3 of these devices and been waiting lol. I see the stock kernel has hot-plug . What's some good tuning profiles? I tried to debloat permanently with LP but it didn't work. I think it's read-only so I flashed the magisk overlay for rw and going to play. We definitely need TWRP! I see a port may be in the works. Awesome. Thanks again

Viva La Android said:
I just got KonnectONE to agree to release firmware a couple of days before you mentioned having firmware. It's been a long wait indeed.
I don't have source code to compile TWRP; only the firmware. I will be attempting to port a TWRP build for this phone very soon. My legal battle with KonnectONE was in regards to source code under the General Public License 2.0. Because they were ultimately unable to provide kernel source, their legal team and support department finally acquiesced to provide firmware to device owners upon written request. I compromised for the firmware release, but was not able to get kernel source code for building TWRP. I am pretty confident that a ported TWRP can be ironed out as a stable build. I already have the base build selected.
Click to expand...
Click to collapse
They never replied when I emailed them about it several months ago . This is so awesome. I got rid of most of the lag with kernel manager. Kudos

Argonon said:
They never replied when I emailed them about it several months ago . This is so awesome. I got rid of most of the lag with kernel manager. Kudos
Click to expand...
Click to collapse
Several months ago they weren't releasing firmware to the public. I got it released by battling with them over open source code and I ultimately compromised for factory firmware. It was only recently made public.
Yeah I've noticed a nice performance boost too with some debloating and sone kernel tweaks. I'm using EX Kernel Manager. Keep in mind this device uses dynamic partitioning (super.img). As such, even with root, it isn't always possible to mount /system r/w. I extracted the super.img on a PC and then mounted /system, /vendor and /product, debloated, and then repacked and reflashed super img.

Awesome. I don't have a good pc now unfortunately. I do have viper4android repackaged version with driver and effects pre-installed. I used smart pack kernel manager to tweak kernel. The device is very useable now! I have a Blu View 3 android 11 mtk device id love to root but can't even unlock bootloader. Maybe I should look into emailing them

Argonon said:
Awesome. I don't have a good pc now unfortunately. I do have viper4android repackaged version with driver and effects pre-installed. I used smart pack kernel manager to tweak kernel. The device is very useable now! I have a Blu View 3 android 11 mtk device id love to root but can't even unlock bootloader. Maybe I should look into emailing them
Click to expand...
Click to collapse
BLU won't unlock your bootloader. It is locked per contractual agreement with the branded carrier of the phone. However, if it's MediaTek, you may be able to use MTK Client to exploit the bootloader into an unlocked state.

Viva La Android said:
Several months ago they weren't releasing firmware to the public. I got it released by battling with them over open source code and I ultimately compromised for factory firmware. It was only recently made public.
Yeah I've noticed a nice performance boost too with some debloating and sone kernel tweaks. I'm using EX Kernel Manager. Keep in mind this device uses dynamic partitioning (super.img). As such, even with root, it isn't always possible to mount /system r/w. I extracted the super.img on a PC and then mounted /system, /vendor and /product, debloated, and then repacked and reflashed super img.
Click to expand...
Click to collapse
Would you plz share your super.img ? I'm on latest firmware and have attached screenshot of build etc.... I understand if you can't or don't want to. Can I pull mine since I'm rooted? Problem is I have a old Chromebook that I installed endeavor os on its arch based Linux but I don't have much hard drive space to do work

Viva La Android said:
Several months ago they weren't releasing firmware to the public. I got it released by battling with them over open source code and I ultimately compromised for factory firmware. It was only recently made public.
Yeah I've noticed a nice performance boost too with some debloating and sone kernel tweaks. I'm using EX Kernel Manager. Keep in mind this device uses dynamic partitioning (super.img). As such, even with root, it isn't always possible to mount /system r/w. I extracted the super.img on a PC and then mounted /system, /vendor and /product, debloated, and then repacked and reflashed super img.
Click to expand...
Click to collapse
Would you plz share your super.img ? I'm on latest firmware and have attached screenshot of build etc.... I understand if you can't or don't want to. Can I pull mine since I'm rooted? Problem is I have a old Chromebook that I installed endeavor os on its arch based Linux but I don't have much hard drive space to do work
Viva La Android said:
I just got KonnectONE to agree to release firmware a couple of days before you mentioned having firmware. It's been a long wait indeed.
I don't have source code to compile TWRP; only the firmware. I will be attempting to port a TWRP build for this phone very soon. My legal battle with KonnectONE was in regards to source code under the General Public License 2.0. Because they were ultimately unable to provide kernel source, their legal team and support department finally acquiesced to provide firmware to device owners upon written request. I compromised for the firmware release, but was not able to get kernel source code for building TWRP. I am pretty confident that a ported TWRP can be ironed out as a stable build. I already have the base build selected.
Click to expand...
Click to collapse
I have 3 of these devices. I surly can test TWRP port if needed

Argonon said:
Would you plz share your super.img ? I'm on latest firmware and have attached screenshot of build etc.... I understand if you can't or don't want to. Can I pull mine since I'm rooted? Problem is I have a old Chromebook that I installed endeavor os on its arch based Linux but I don't have much hard drive space to do work
I have 3 of these devices. I surly can test TWRP port if needed
Click to expand...
Click to collapse
Sure. I don't mind sharing my super.img. I'll need to upload it and then I'll message you a link. It's pretty much exactly 2.5 GB in file size, so I'll first compress it to a zip before uploading.

The edited one. Just clarifying so appreciated

Argonon said:
The edited one. Just clarifying so appreciated
Click to expand...
Click to collapse
I don't yet have all my mods made to the /super partition in that regard. Having encountered some force close issues with certain apps, I debloated from scratch and and have now begun my kernel tweaks and edits to the.varuous .prop files. So when finished, I'll share both my boot.img and super.img.

Just the stock super.img would be fine then. I think I can figure how to decompile, debloat and recompile then flash.

Argonon said:
Just the stock super.img would be fine then. I think I can figure how to decompile, debloat and recompile then flash.
Click to expand...
Click to collapse
MH-T6000 super.img unmodified

I was experimenting and flashed the super.img with dsu side loader apk as a gsi lol. The app description said can replace various partitions and I was just trying to get system rw on the dsu loader. I know that makes no sense. What windows 11 compatible software do you recommend to unpack, repack etc? I see a few magisk modules but not quite sure how to use. Like ro2rw magisk module

Viva La Android said:
MH-T6000 super.img unmodified
Click to expand...
Click to collapse
Thank you!

Argonon said:
Thank you!
Click to expand...
Click to collapse
When I have completed debloating, kernel tweaks and .prop files edits of the OS, I'll share my modified super.img and boot.img. I have a TWRP v3.6.0 port build that is currently booting properly on this phone. But, I have bugs to work out on logical partition mounting, as well as the backup & restore functionality.

Argonon said:
I was experimenting and flashed the super.img with dsu side loader apk as a gsi lol. The app description said can replace various partitions and I was just trying to get system rw on the dsu loader. I know that makes no sense. What windows 11 compatible software do you recommend to unpack, repack etc? I see a few magisk modules but not quite sure how to use. Like ro2rw magisk module
Click to expand...
Click to collapse
Check out CRB Android Kitchen here on XDA. Great for unpacking / repacking partition images, including super.img.

Viva La Android said:
When I have completed debloating, kernel tweaks and .prop files edits of the OS, I'll share my modified super.img and boot.img. I have a TWRP v3.6.0 port build that is currently booting properly on this phone. But, I have bugs to work out on logical partition mounting, as well as the backup & restore
Click to expand...
Click to collapse
Have you had anymore luck with this

[ROM] Modified Stock Android 11 (Go Edition) ROM for KonnectONE Moxee m2160 (MH-T6000) 4G-LTE

Android 11 (Go Edition)
Modified Stock ROM​
{
"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"
}
Assurance Wireless
KonnectONE Moxee m2160
4G-LTE Smartphone
Model No. MH-T6000​
OVERVIEW:
This is a heavily modified build of the stock Android 11 (Go Edition) ROM which comes preinstalled on the KonnectONE Moxee m2160 smartphone. Please note that, while flashing this ROM will not network unlock your device, the ROM does include added support for most GSM based providers on devices which have previously been network unlocked.
In a nutshell, this modified build focuses on the removal of bloatware and a slimmed-down, more responsive stock OS experience. In addition, once installed, the ROM supports full R/W mounting of all logical partitions encompassed within /super. (The unmodified stock ROM, notwithstanding Magisk systemless root, restricts proper R)W mounting of these partitions due to the stringent codebase changes which implemented the dynamic partition scheme back with the release of Android 10.) This ROM also disables force encryption to /userdata (DFE), disables AVB/dm-verity, and includes several mods for improved performance and responsiveness. While certainly nothing special in terms of custom development for the Moxee m2160, this ROM should provide users with a sufficient daily driver ROM with an optimized stock feel.
FEATURES & BUILD INFO:
• Based on firmware build MH-T6000V1.0.0B010
• Kernel version: 4.19.157-perf
• Security patch level: March 5, 2023
• GMS version: 11_202111.go
• VNDK version: 30
• Quick boot sequence
• Systemless root via Magisk v26.1
• Enabled Power Stamina mode for better battery life
• /system mounts R/W
• /system_ext mounts R/W
• /product mounts R/W
• /vendor mounts R/W
• Force encryption of /userdata disabled (DFE)
• OTA notifications & persists disables
• AVB/dm-verity disabled
• Stock launcher locked in memory
• Zipaligned /system/app & /system/priv-app
•Zipaligned /system_ext/app & /system_ext/priv-app
• Zipaligned /product/app & /product/priv-app
• Custom TCP congestion algorithm presets
• Heavily debloated w/minimal Google framework
• Kernel level performance optimizations
• Google Pixel 2 dark bootanimation
• Optimized RAM management
• Schedutil tuned CPU governor parameters
• Enabled fast charging (1100 mAh stable)
• GSM support for network unlocked devices
PREREQUISITES:​
An unlocked bootloader ​
A PC or laptop running on Windows 7, 8.1, 10 or 11​
Smartphone must be running Firmware Build No. MH-T6000V1.0.0B010​
The SDK Platform Tools on your Windows computer (link provided below)​
Installation of the proper ADB & Fastboot device drivers on your Windows computer​
The factory supplied, or a quality sufficient, USB-A to USB-C syncing/charging cable​
A reliable internet connection for downloading the required files ​
NOTE: We will not be using a custom recovery for installation of this ROM, but rather the dynamic user space implementation of fastboot mode, formally called FastbootD. This fastboot protocol was first introduced with the release of Android 10, and is primarily utilized for the management of dynamic partitions (devices with a /super partition).
DISCLAIMER:
This guide involves the invasive procedure of flashing the partitions of your device, thus modifying the configuration of the device from its factory stock state. This is always inherently risky to the integrity and operability of your mobile device. By proceeding further, you are assuming sole responsibility for the functionality and physical wellbeing of your mobile phone, thus absolving me of any liability in the event things go badly. This ROM has, however, been tested thoroughly on my own device with no negative issues. Moreover, in the unfortunate event your device becomes bricked or otherwise inoperable by way of a botched adherence to this guide, my firmware restoration guide for this device can restore both soft and hard bricked phones. Moxee m2160 Unbricking Guide
INSTRUCTIONS:
WARNING:
These instructions include steps for initiating a factory data reset, a procedure which will effectively erase all saved user data, app data, app preferences, photos, videos, music, documents and other media files from your smartphone. Make a backup at this point of all data, files and media that you wish to preserve.​
Download the SDK Platform Tools from the link below and extract the contents of the archive to an empty folder on the desktop of your Windows computer​
Download the ROM from the link below and extract the contents of the archive to your platform tools directory created in the previous step​
Because this ROM has been modified to disable DFE force encryption, it is first necessary to format the /userdata partition. With your phone in a powered off state, press the Volume Up & Power keys simultaneously until the Moxee logo appears on your display, at which time you should release the Power key, but continue holding Volume Up until an Android logo and a corresponding No Command notification appears on your phone display. Now quickly press and hold Power, tap Volume Down and then Volume Up to enter stock recovery mode.​
Use the Volume Down key to navigate to the Wipe data/factory reset option, then press Power to select. Confirm this selection on the next screen to initiate the factory data reset.​
Once the factory reset is complete, navigate to the option to Enter Fastboot, then press Power to select. Your phone should now boot to FastbootD mode.​
In the platform tools folder created in the first step, click on cmd-here.exe, then right click and opt to run it as an administrator. A command window will be launched. Now connect your Moxee m2160 to your Windows computer using a sufficient USB-A to USB-C data syncing/charging cable.​
In order to verify proper fastboot communication between your phone and PC, execute the following command:
Code:
fastboot devices
If properly connected, the command window will yield an alphanumeric value consistent with your mobile phone serial number.​
Execute the following commands once a proper fastboot connection has been verified. Note, the user may copy these commands and paste the full text to the fastboot command window for systematic execution:​
Code:
fastboot flash boot boot.img
fastboot flash vbmeta vbmeta.patched.img
fastboot flash vbmeta_system vbmeta_system.patched.img
fastboot flash vbmetabak vbmetabak.patched.img
fastboot flash vbmeta_systembak vbmeta_systembak.patched.img
fastboot erase super
fastboot flash super super_rw.img
fastboot erase metadata
fastboot erase cache
fastboot erase DDR
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
** Please note that the super_rw.img file is large in size. Fastboot may initially give a header magic notification error. However, the super_rw.img will then be allocated into a number of smaller sparsechunk files, which will subsequently be flashed to your device one at a time, until complete. Just remain patient during this process. This can take five minutes or more, but the process will not require any user action.​
Upon first reboot following installation, and after completing initial device setup, open your app drawer and search for the Magisk app or its stub placeholder. Open Magisk, grant any requested permissions, and follow any prompts by Magisk to update the version or complete setting up the root environment. If you do not see the Magisk app or stub, download the Magisk v26.1 APK from the link provided below and install the app on your phone. Be sure to then open Magisk and follow all prompts.​
DOWNLOADS:
• SDK Platform Tools r34.0.3
• Modified Stock ROM Package
• Official Magisk Releases / GitHub Repo
BUGS:
Please report any bugs or instabilities you may encounter using this modified stock ROM. Those who know how to submit an official bug report are urged to do so. Otherwise, please give a concise and detailed description of the issue, including photos or screenshots if possible. I will work diligently to patch any reported bugs or instabilities.Moxee m2160 Firmware Restoration & Unbricking Guide​

Instructions were great and I had no problems following them. I did have an error when I first entered the command "fastboot erase DDR" but only because I did not capitalize DDR. My only issue is I cannot get past the phone set up when first booting because it says there is an update and can not pass verification and there is no option to skip. And in my case I don't have a computer still so cannot use qfil to return to full stock to update. Any suggestions?

scottfan81 said:
Instructions were great and I had no problems following them. I did have an error when I first entered the command "fastboot erase DDR" but only because I did not capitalize DDR. My only issue is I cannot get past the phone set up when first booting because it says there is an update and can not pass verification and there is no option to skip. And in my case I don't have a computer still so cannot use qfil to return to full stock to update. Any suggestions?
Click to expand...
Click to collapse
Okay. At the time I completed modifications on the ROM, the latest OTA had not yet rolled out. What I'll do is add another mod to kill the OTA service entirely. That should prevent any issues like you're facing. I'll expedite this task and will let you know just as soon as I've made the fix and changed out the ROM file with the new one. Thanks for your feedback. By the way you won't have to repeat the process, but will only need to flash the super_rw.img file.
Update: I have disabled system updates and OTA notifications. Proved trickier than I thought, since system updates on Android Go Edition are governed by Google Play Services. I had to decompile the Google Services apk, manually disable the individual system update service and listeners, then recompile and reinstall the Google Services core app. I am presently uploading the new super_rw.img.
One thing that should work for you in the meantime, while I get these new files uploaded, is to perform another factory data reset. During initial boot and setup, opt to complete setup offline, without connecting to WiFi or a mobile data network. Accordingly, your device will not be able to check for pending system updates and you should, therefore, be able to complete setup.

Viva La Android said:
Okay. At the time I completed modifications on the ROM, the latest OTA had not yet rolled out. What I'll do is add another mod to kill the OTA service entirely. That should prevent any issues like you're facing. I'll expedite this task and will let you know just as soon as I've made the fix and changed out the ROM file with the new one. Thanks for your feedback. By the way you won't have to repeat the process, but will only need to flash the super_rw.img file.
Click to expand...
Click to collapse
That would be awesome. I really appreciate your help.

scottfan81 said:
That would be awesome. I really appreciate your help.
Click to expand...
Click to collapse
The files should be finished uploading within the next 15 minutes or so. I will then update the download link and will inform you here when that's done.

@scottfan81, the latest files are uploaded and the download link has been updated accordingly.

Viva La Android said:
@scottfan81, the latest files are uploaded and the download link has been updated accordingly.
Click to expand...
Click to collapse
That's great! I just got done with my dinner and going to download it now. I will let you know how it goes. And I did see that I only need to flash the super_rw.img file. So I should know shortly.

scottfan81 said:
That's great! I just got done with my dinner and going to download it now. I will let you know how it goes. And I did see that I only need to flash the super_rw.img file. So I should know shortly.
Click to expand...
Click to collapse
Do a factory reset beforehand. Then flash the super_rw.img

@Viva La Android
I haven't had any luck since my last post. Before I posted about the verification issue I had when setting up my phone I made sure I double checked that I did not have the option to skip the update as you suggested. That was not an option for some reason and that is when I came here. I have followed your steps with the new super.rw.img you updated but I am worse off than I was before. Now I cannot do anything as the phone is not recognizing any network or available WiFi connections. I have tried a factory reset and started over from your first step with no success. I should also include that since flashing the updated super.rw.img file, when the phone first boots the screen quickly flashes black and blue for about 10 seconds before finally starting the set up process then I get 2 error messages. The first being "system UI isn't responding" and second "Android setup keeps stopping" After all of that the setup starts and that's as far as I can go because I can't connect to anything. Trying to give you as many details I can think of. Before the screen flashing when powering on the phone, the boot animation just function properly. Only between the boot animation and setup process do I experience the rapid black and blue screen for roughly 10-15 seconds. I am including some screenshots of the error messages and setup screens showing no connections available. I almost forgot. I also tried manually adding my network and scan qr code with no success.

Unfortunately I have physically damaged my device beyond any hope of restoring it, so I won't be able to support this device any longer -- until & unless I can get a replacement display. But before my device went kaplut, I did test this ROM and had no issues. I wish I could be more help.
I would recommend performing all steps over again from the top -- formatting /userdata before doing anything. Have you tried by completing all the steps over?