yashsingh1/xdaforums huggingface dataset:
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
Touch screen works, now we need to get it to detect system partition and work without wiping userdata
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] koyo:
Touch screen does not work for me. Also, I want to clear something up. When I said resize/repair doesn't work until you factory reset, I wasn't basing it off of the E6 TWRP, I was basing it from my usage of the G6 and G7 Power TWRPs.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
Boot into twrp, open adb, and type these commands:

adb shell
mount /dev/block/bootdevice/by-name/vendor /vendor -o ro
ls /vendor/lib/modules

then send me the result.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Spaceminer:
If you guys have FEC and forced verity enabled, installing without wiping won't be possible. I'm looking at disabling that again. I need to fix up wistron, so I can check later. If it exists it's in the kernel or ramdisk/init, I forget which.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
I've tried to flash a dm-verity disabler but it will either say "failed to mount /data" or just "Updater process ended with ERROR: 1 Error Installing Zip File"
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] koyo:
1|surfna:/ # ls /vendor/lib/modules

abov_sar.ko audio_mbhc.ko audio_usf.ko focaltech_mmi.ko snd_soc_tfa9874.ko

audio_adsp_loader.ko audio_native.ko audio_wcd9335.ko mcDrvModule.ko sx932x_sar.ko

audio_analog_cdc.ko audio_pinctrl_wcd.ko audio_wcd9xxx.ko mmi_annotate.ko tps61280.ko

audio_apr.ko audio_platform.ko audio_wcd_core.ko mmi_info.ko tzlog_dump.ko

audio_cpe_lsm.ko audio_q6.ko audio_wcd_cpe.ko mmi_sys_temp.ko utags.ko

audio_digital_cdc.ko audio_q6_notifier.ko audio_wsa881x.ko modules.alias watchdogtest.ko

audio_hdmi.ko audio_stub.ko audio_wsa881x_analog.ko modules.dep

audio_machine_ext_sdm450.ko audio_swr.ko drv2624_mmi.ko pronto_wlan.ko

audio_machine_sdm450.ko audio_swr_ctrl.ko exfat.ko sensors_class.ko

I can send a screenshot if the text is too messy for you
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Spaceminer:
Try manually mounting /data
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
Try this:

insmod /vendor/lib/modules/McDrvModule.co
insmod /vendor/lib/modules/drv2624_mmi.ko
insmod /vendor/lib/modules/sx932x_sar.ko

And then see if the touch works.

I'm not entirely sure it will since yours might be a wistron panel, but it still might.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] koyo:
It says it doesn't have the required key. And using the mount command in the earlier command doesn't do anything because when I try to mount -t ext4, it says Device or resource busy
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
I'm not sure what you'd do in that situation, I'll need [MENTION=7718083]Spaceminer[/MENTION] to jump in from here.

---------- Post added at 12:28 PM ---------- Previous post was at 12:28 PM ----------

Edit: XDA Double posted, snip
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] koyo:
To finally answer [MENTION=7718083]Spaceminer[/MENTION] question about the panel supplier, it is indeed djn.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
Mine's also djn, so I'm not sure why yours isn't working.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] koyo:
I think my issue is I haven't been following the instructions to a tee. I'm going back and re-reading the posts I missed and stuff
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
Alright.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] koyo:
I went back and re-read the posts several times and I'm convinced my phone is just cursed. Gonna need [MENTION=7718083]Spaceminer[/MENTION] help for this

---------- Post added at 02:39 PM ---------- Previous post was at 02:39 PM ----------

Double post. Dont mind this part
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Spaceminer:
See this post, use d2-twrp.img. The touchscreen should work from the start if I'm not mistaken. Then you can copy whatever you need to flash from your pc to internal or external storage and use twrp's menus to install it. I think you could also manually enable adb at that point if you wanted to.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
Adb is already enabled because (if I'm not mistaken) it's based on the G7 Play. However, [MENTION=7072887]koyo[/MENTION] 's problem is that the touch screen doesn't work on that one.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] koyo:
Unfortunately the touchscreen does not work from the start for me.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] koyo:
I think I narrowed the problem down to one thing. I've been trying to use insmod to load the drivers but I'm getting the Required Key not Found thing. Enoki had that before but somehow he got past it and was able to load the drivers. As for me, I'm not so fortunate yet.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
I'm not sure why it began working for me, but hopefully we can figure this out.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
What we need to do is figure out what driver the touch screen for yours is. Maybe your phone needs a different ADB driver in TWRP? Try to load a driver in adb one more time and see if it works.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
I flashed stock on my e6 and then tried to flash again. No touch screen, and required key not available error. Does it need a verity key to work properly?
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Spaceminer:
It shouldn't need one since it doesn't actually boot the OS.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
Then why would it require a key to load the driver?
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Spaceminer:
ADB keys. Not verity keys. TWRP only runs in permissive mode so verity is ignored. Which ADB/fastboot are you using?
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
Platform tools zip file
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] koyo:
I'm using the Minimal ADB and Fastboot if that matters
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Drexdaa:
hi, I flash the twrp.img

however, it always loading...doesn't work
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] koyo:
WHich one did you download? Unfortunately, we might still be at the stage where using fastboot -w (This formats your device. WARNING) is still needed before flashing the TWRP.

Also, touch screen may potentially not be fixed yet.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] ddougg:
Hey before I flash some questions should I flash of pg1 or pg 19 image? Should I do ADB commands insmod focaltech&*2624? Lib drivers? Push no verity zip?

I am rooted Magisk recovery on E6 surfna metropcs
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
This forum has died

---------- Post added at 11:33 AM ---------- Previous post was at 11:30 AM ----------

Edit: No-verity doesn't work because of something to do with data (don't quote me on that), so that's an impossible for now.

Flash d2-twrp and then run fastboot -w (will wipe data), then choose recovery in fastboot mode. If touch screen doesn't work, type adb shell and insmod the appropriate drivers. Mine tells me that the required key isn

't available, but yours might not.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Spaceminer:
That's correct. The init file found in /system_root forces dm-verity and encryption even if the vendor fstab is patched. Basically after you format with twrp, and you start to boot the OS, if either isn't enabled, it'll wipe data again and enable both, then continue booting. I believe either /system_root/init needs to be patched, or twrp needs decryption support. I'm working on both right now. It's problem for multiple Motorola devices.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] koyo:
It's not impossible because I used the adb twrp command to flash verity zip and it did work. Unfortunately, after that, I tried to flash some custom ROM GSIs which boot looped and I had to flash back to stock which undid the verity.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
Any progress?

I got root to work on my E6 (finally) but TWRP touchscreen still isn't working for me.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Spaceminer:
No progress yet. I'm actually very out of commission right now. I had a slew of problems already and they all just got worse. About 2 months ago, I ruptured a disk in my back. Then I reinjured it a few weeks later. I have a kidney stone that I still need to pass. And yesterday morning I tripped on my kids toys and had a nasty fall. The incident yesterday left me with a concussion and a broken hand. Unfortunately I'm a complete train wreck for the time being. It might be a while.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] xtermmin:
Picked up a Moto E6 to mess around with (I like Moto's cheap E-series phones). Got d2-twrp flashed, and used that to flash disable-dm-verity (touchscreen doesn't work, so I plugged in a usb mouse), with various reboots and wipes in between. OS boots, twrp sticks, phone does not get encrypted. However, I just can't seem to get Magisk to stick, both flashing via TWRP (no errors when flashing the ZIP, but Manager doesn't detect it when in OS) and via patching boot.img. It does work if I patch stock recovery and replace TWRP with it, though.

One interesting thing I noticed is that if I flash TWRP, mount System, make a change to a file in /system/system (like renaming an APK so that an app doesn't load in the OS), when I boot into the OS normally (normal boot.img), the app still shows up, but when I flash magisk-patched-recovery and boot the OS using that, that app does not show up. So, it's almost like a normal boot ignores any changes made to /system, while a magisk-patched-recovery boot does take those changes into account. And it still remains the case when I reboot between the two. And if I re-flash TWRP and browse to the file via File Manager, I still see the change I made, even if I boot into the OS normally. Weird, although I'm not too up-to-speed with the latest security procedures and A/B slots and all that (current phone is pre-treble).

Anyway, some of this may be obvious or well-known, just thought I'd share my findings/experience so far.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Spaceminer:
Most people don't know this. It happened to me when I debloated my G7 Play. I used twrp to remove system apps. Booted up and they were still there. As soon as I rooted, all the changes I had made showed up. I can't figure how or why it happens. The changes by twrp should be permanent without root and seen immediately, but it will never show up until after you root. It's one the strangest things I've seen.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] the-her0:
if my new E6 doesn't break, I'll do another GSI thread here
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] LgPWNd:
GSI

That would be great, I have wasted hours trying to find a gsi and get it to boot...

No luck

From what i can tell it has to be an arm a/b system image even tho its not an a/b device

If you have an image that boots please link to it here .

Thanks
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] the-her0:
It's a Binder64 A/B (System as Root makes it A/B) device.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] the-her0:
thread about the Quack GSI I'm using RN, the specific variant is Arm32-Binder64-AB Gapps.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] LgPWN'd:
Welp, I guess no one's interested in the ROM restore pack Or the twrp with working screen...?

K well I'll probably just keep it to me self then.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Ruuel:
I'm extremely interested as I recently lost Magisk root on my e6. And that's after faithfully rebooting only to recovery and avoiding OTAs at all costs.

And I'm sure I'm not alone, I'd be grateful for any info toward a solution. Thanks for your efforts so far!
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] nc12683:
Hook me up doggy I wanna test I'm bored with this toy
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] pvsgh:
Can you post your version of TWRP, may be start a new thread?
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
I don't have this device but was recruited to help out building from source. Please test for booting. You will need to extract the tar file, I couldn't upload otherwise.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
Here is a second image to try. Both these are OrangeFox btw. Once source is sorted and booting, I have 7 different recoveries that are able to be built.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] ANDROID2468:
Hello, I have some experience with porting Roms from source. Someone is gifting a Moto e6 ( Verizon) in August.

So I got a question:

So does anyone know if you can flash a recovery from the international version on the carrier specific device? (I don't have the device to test it.)

Ex: x2005-1 recovery --> x2005-5 device
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Ruuel:
That same question occurred to me and I almost tried it, but concern over possibly hard bricking a phone I've had for only two months made me think twice.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] ANDROID2468:
I don't think it will hard brick your device since we have an official bootloader unlock.

I don't think this device has ARB (Anti rollback ) I will look into it. But even if it does, I never heard of recovery having an arb.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] ANDROID2468:
I use telegram.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] the-her0:
you're a bit over stating, there's three of us working on it there, and I'm off half the time working on other projects
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] ANDROID2468:
Yeah, I probably won't be much help because I don't own it atm (I'm getting it in August)
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] LgPWN'd:
Well actually,

My Team is working on it there.

And u are there to test and try to reach the same point as me with your device.

If we can find more people to test we can get this all streamlined for everyone.

Going to write a program to help get everyone to where I'm at programmatically.

It will likely be a bash script to start with.

Does anyone else here run Linux or is this another case of everybody uses windows?

If everyone is going to use windows we'll need to do the program in Python likely

As it's better than batch

Any comments?

Any tester's?
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] fernando669:
Twrp para moto E6 play

Olá amigo tudo bem???

Gostaria de saber se o twrp que você está desenvolvendo pega neste modelo de smartphone e6 play,procurei diversos tutoriais de como instalar o twrp no meu aparelho mais não acho jeito algum,se você poder me dá uma resposta ficarei muito grato
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] koyo:
Perdon por mi mal espanol pero lo no trabajo con E6 Play. Es por E6 y E6 solo
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Az Biker:
* * * Thread Cleaned * * *

Please do not post links to off-site blogs, groups or other sites UNLESS you are the OP and those groups support THIS development thread. Recent post with links to off-site groups have been deleted.

Please read Forum Rules:

5. Create a thread topic or post a message only once, this includes external links & streaming media.

Self-promotion is forbidden, this includes blogs, social media and video channels etc. Random links will be removed.

Any further posting of this nature will be deleted and result in the author's account being reviewed for restriction or removal.

Thanks for everyone's cooperation
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Az Biker:
Please post in English. If a second language is required, please post it below the English comment and I have done here. Thank you.

Por favor publique en inglés. Si se requiere un segundo idioma, publíquelo debajo del comentario en inglés y lo he hecho aquí. Gracias.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Spaceminer:
It does. Just like some Sammy devices. If you fail to reboot using recovery even once, then you're screwed and recovery gets replaced with stock. It's likely that they implemented FEC on the recovery partition. We have it on the G7 Play in our boot/recovery image. Magisk mirrors get around it, but the only way to disable it is through a custom kernel. It might be possible to hex patch it out, but I've never been able to. It also gets disabled by default if a GSI is flashed. FEC is a pain in the ass.

You can try "strings recovery.img | grep fec" and see if it returns anything. It might take some prodding but in all likelihood it's in there somewhere.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] iwantthis:
Have you tried sunsytems Motorola boot unlock and recovery replace?
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
what is this and where do I find it?
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] gking707:
Can you please share this? I have 2 e6's, the boost variant -4 and the international version -5.

the touchscreen works on neither, and the international version doesnt mount properly. twrp itself bootloops. not a phone reset, but twrp/recovery restarts repeatedly.

but yes, please share.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Cringineer:
Custom Rom/TWRP for Moto e6 XT2005-5 Surfna?

Ive been having insane difficulty in attempting to get TWRP to work, along with any sort of custom roms (probably because there isnt any)

October 9th - 12 I was working on just rooting and unlocking bootloader for my device (Yes it took me this long), I ended up bricking the device but managed to fix it (at the expense of always getting the "Bad Key" when rebooting) The device is now rooted and bootloader unlocked. (Used Magisk) Not to mention, there is no stock firmware for my specific device online, nor can I get the original.

But now comes my problem of finding custom roms, and extra goodies for my device because its a weird device.

I have recently discovered that my SIM card will not work (no SIM card). And as thats the whole reason I have my device, I really need help on fixing that. Ive already rebooted, cleared caches, airplane mode, removed sim and battery. No luck so far

DEVICE SPECS:

Build: PPBS29.73-123-11

Version: Android 9

(No baseband because of brick)

Model: XT2005-5

I appreciate any help, Thanks
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] ddougg:
Cringineer" been having insane difficulty in attempting to get TWRP to work...

I appreciate any help, Thanks"

I haven't gotten twrp to work just magisk in recovery mode ? no roms. Have you tried the Lenovo smart assistant app? It will download your firmware and flash you back to stock. Saves your new firmware to Magisk with after you get the sim working. Best wishes
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] egoss84:
My usb connection stop working but it still charge my phone. I can't transfer anything
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Cringineer:
Lenovo doesnt have my firmware, Ive got magisk and it works, I have root and my phone is fine. I still get a bad key during boot but doesnt matter as the phone still boots and works. Thing is I cant use this phone for calling and texting because of the brick and lack of firmware.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Viva La Android R.I.P.:
What firmware build are you needing, or are you still needing a firmware package? Bad key is perfectly normal when flashing either the /boot partition or the /recovery partition with an unlocked bootloader. In fact, if you were not seeing a "bad key" notification, something would be major wrong. There are some custom Moto boot logos that will conceal the "bad key" or "N/A" notifications during boot up.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Cringineer:
XT2005-5 Moto e6

Surfna 29.73 123 11

The issue now, is that I do not have an IMEI code on my phone anymore. So I cant call or text using my phone. You'd have to talk to me in dm's or Discord. As I cant sign up for the telegram thing because, I have no number. Thanks
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Viva La Android R.I.P.:
You have your IMEI number. It's there written to the /pds partition. Your current firmware mismatch is creating a scenario whereas your baseband firmware isn't recognizing or properly reading your IMEI. Your firmware package is here https://mirrors.lolinet.com/firmware/moto/surfna/official/RETCA/ This is the official firmware from Lenovo/Motorola's servers Download the last package on the list, the one from 9/14/2020. It matches the build number you referenced. You're going to need either the platform tools from the Android SDK, or you can use the Minimal ADB & Fastboot tools (v1.4.3). It works on Windows 10/8/7. Here is a direct link https://drive.google.com/file/d/1Qj4XzdXcq_YDhQ6bcipBx-vCg3rNj_Lz/view?usp=drivesdk. Here are the fastboot commands for installing this firmware package. NOTE: this will erase all userdata on your device. Make a backup of all files and data you wish to keep:

fastboot oem fb_mode_set

fastboot flash partition gpt.bin

fastboot flash bootloader bootloader.img

fastboot flash dtbo dtbo.img

fastboot flash modem NON-HLOS.bin

fastboot flash fsg fsg.mbn

fastboot erase modemst1

fastboot erase modemst2

fastboot flash dsp adspso.bin

fastboot flash boot boot.img

fastboot flash recovery recovery.img

fastboot flash logo logo.bin

fastboot flash system system.img_sparsechunk.0

fastboot flash system system.img_sparsechunk.1

fastboot flash system system.img_sparsechunk.2

fastboot flash system system.img_sparsechunk.3

fastboot flash system system.img_sparsechunk.4

fastboot flash system system.img_sparsechunk.5

fastboot flash system system.img_sparsechunk.6

fastboot flash system system.img_sparsechunk.7

fastboot flash system system.img_sparsechunk.8

fastboot flash system system.img_sparsechunk.9

fastboot flash vendor vendor.img

fastboot flash oem oem.img

fastboot erase DDR

fastboot erase cache

fastboot erase userdata

fastboot oem fb_mode_clear

fastboot reboot

[MENTION=11192751]Cringineer[/MENTION] unless you relock your bootloader upon flashing this stock firmware, you will continue to see a "bad key" or "N/A" notification during boot. This is merely indicative of your device being oem unlocked. This is not an error. You'll also get a "signed with bad key" notification when flashing the /boot and /recovery partitions while in a bootloader unlocked state. Your device is fully able to install OTA updates while bootloader unlocked. So unless it's for warranty purposes, there's not much benefit to relocking your bootloader.

OP, I apologize for the off-topic post in your custom recovery thread. Oh wow, [MENTION=5006327]jasonmerc[/MENTION] I just noticed you're the OP. I see you're a Moto lover like myself. Small world here on XDA.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Cringineer:
My device is now reading IMEI and works fine now, thank you so much. Ive been stuck trying to fix that for over a month now. It was impossible to find any instructions for my XT2005-5. So, from the bottom of my heart, thank you so much <3
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Viva La Android R.I.P.:
My friend you are indeed welcome. I'm truly glad the firmware package done the trick. So now if anything goes wrong while rooting, modding, flashing, etc., this guide should get you back on track.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] egoss84:
E/Root> STD-ERR >> /system/bin/sh: <stdin>[8]: usb: not foundc