yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] Yahoo Mike:
You could try recovering the tablet with LMSA. See this post. You'll lose all your existing data and setup on the tablet, though.

Not sure what went wrong for you. Do you have a TB-X605F with Snapdragon 450 SOC? The existing TWRP is only for the SDA450. I'm working on one for the M10s with SDA429.
[General Questions and Answers] crosis99:
Thanks for the response. Yes mine has the Snapdragon 450. I will investigate the LMSA. Been messing around all day but made no progress -- not even QPST is working out.
[LG V40 Questions & Answers] hooutoo:
I realize that this is a know problem and have searched countless threads. Has anyone managed to find a fix. I'm trying to switch from Sprint to Simple Mobile and as a lot of others have seen, the Sprint APN setting is grayed out (locked). I'm running a V50 and yes I know it's a long shot. BTW, for those wondering, Sprint doesn't have 5G in my area yet so I see no reason to pay Sprint for 5G service that they're not providing. And yes Sprint is a scumbag company! LOL

Thanks in advance.
[LG V40 Questions & Answers] hooutoo:
Just a heads up on grayed out apn. I slip an old Google Fi sim into my v50 an went to APN setting dialog screen. Low and behold for first time all Sprint apns weren't there and 4 new entries, all for Fi were. Unfortunately, I couldn't complete the activation because my Fi sim card is bad, which I all ready knew was a problem, it's too old. Have since ordered a new sim which I should have next week. If this works, F*** Sprint!

Oh, btw the cards free.
[LG V40 Questions & Answers] TheMadScientist:
Should be able to get into the hidden menus through dialer codes and add it. Root may be needed for short cut master
[Touch Dual, MDA Touch Plus General] nickamous:
Please can some one help me. This is driving me crazy.

I got a brand new Touch Dual from Best Buy on Tuesday. It syncs up with my exchange server fine. I can read entire emails, too. But when I click on an attachment to download, it fails every time. Does anybody have a fix for this problem?
[Nexus 7 Q&A, Help & Troubleshooting] Phero100:
Hello,

I wanted to install aosp_grouper on my Nexus /, but after wiping the connection becam elabile during dlahing. Now I cannot connect the Nexus anymore to my PC via the Nexus root toolkit. The device shows only the Google logo and an open lock. Hard reset does not result in anything different.

Is there a way to reconnect to my PC or do I have to throw away the device?

Many thanks for your help.
[Nexus 7 Q&A, Help & Troubleshooting] GedBlake:
Hi, Phero100...

Your device should be recoverable, because...

This indicates that the bootloader is still good, and the device is not hardbricked.

I've never used a toolkit myself, preferring to use fastboot commands instead, so I can't comment too much on the Nexus root toolkit you mention in your post. But it's possible you may get a response from the toolkit by booting your Nexus 7 into fastboot mode, as follows...

From a powered off state, press VOL-DOWN and then simultaneously press POWER-ON. Hold both buttons for 15 seconds or until the device boots into the bootloader.

If you don't get anywhere with the toolkit you're using, I suggest you just reflash the Nexus 7 back to Google factory stock using fastboot.

Take a look at my response to another XDA member, from a couple of days ago, where I elaborate on fastboot flashing in more detail...

https://xdaforums.com/showpost.php?p=80387547&postcount=2

...and of course there are other detailed guides elsewhere on XDA.

Good luck:)

Rgrds,

Ged.
[Nexus 7 Q&A, Help & Troubleshooting] Phero100:
Dear Ged,

thanks, but it does work only partially. Although I got a new image on the Nexus, an opened android man with Start at the top (fastboot mode?), neither the toolkit nor Windows 10 makes any connection to my Nexus. Anyway, without connection I can't do anything.

How can I connect to the Nexus 7 now?
[Nexus 7 Q&A, Help & Troubleshooting] rahimali:
If it does turn out to be a Windows driver problem, in my experience the Universal Naked Drivers work the best.
[Nexus 7 Q&A, Help & Troubleshooting] Phero100:
Hi Ged,

What do you mean 'partially'?

That I do not get a connection ot Windows.

Where did you get this image from, and why is it on your Nexus 7? It should be on your Windows 10 box - unzipped, with the contents in the same folder as the fastboot and ADB executables, and these are likely to be found in your toolkit folder.

aosp_grouper-7.1.2-ota-20190823.eng.ds.zip

from: https://androidfilehost.com

Yes - that is fastboot mode.

------------------------------------

What happens when you run this command from your PC?

fastboot devices

Do you see your N7's unique serial number confirming you have a valid fastboot connection - eg., something like this...

019d2424b14050b fastboot

Yes

Have you read this guide...

https://xdaforums.com/showthread.php?t=1907796

Not yet, but i will do.

On the other hand, if I try the toolkit again, to unlock boatloader it tries several times, but says that it is a connectivity issue. It seems to me that it cannot be the USB port/cable, because otherwise it would not be detected by windows. Furthermor, USB connection worked before until the decribed error occurred. Therefore, I assume that it might be a driver problem.
[Nexus 7 Q&A, Help & Troubleshooting] GedBlake:
Ahh, my apologies ~ I thought you where referring to a Google Factory Image, not...

aosp_grouper-7.1.2-ota-20190823.eng.ds.zip

I have no familiarity with that image file, having never used it myself. If, as you say, it's on your Nexus 7's internal storage, you may be able to flash it using TWRP custom recovery, assuming you have TWRP flashed to the recovery partition. If not, then this brings us back to your problem, because TWRP needs to be flashed with fastboot...

You can find the download links (and instructions) for the Nexus 7 TWRP .img files at this link...

https://twrp.me/asus/asusnexus72012wifi.html

There are two download mirror links at this website, one for Europe and the other for America. Select the one that works best for you.

To flash TWRP, your Nexus 7 should be booted into fastboot mode, and from your laptop/PC, type this command in...

fastboot flash recovery [name-of-twrp.img file]

I usually rename the rather lengthy TWRP .img file to something short, like twrp.img, so the fastboot command is much easier to type, and would look like this...

fastboot flash recovery twrp.img

-------------------------------------------------

What is particularly puzzling about all of this, is the following...

You answered 'Yes' to this question, and you do see your Nexus 7's unique serial number ~ this means you have a valid and usable fastboot connection to your Windows 10 PC. Logically then, your toolkit should work, and fastboot flash commands certainly should.

With regard to unlocking the bootloader, you might want to try this...

fastboot oem unlock

You should see a confirmation request screen on your Nexus 7, like the screenshot below.

Rgrds,

Ged.
[Nexus 7 Q&A, Help & Troubleshooting] Phero100:
Dear Ged,

I know manage to get everything running until flashing. The error occurs again, but hti time I red it correctly. It says zip file is corrupt. That is surprising to me given the source I downloaded the file from. I will now try a different custom ram.
[Samsung Galaxy S10 5G Questions & Answers] Mr_Stabs:
After looking at the list of devices that is scheduled to receive the android 10 update, I can't help but notice that the 5G isn't actually listed in that long list of devices. Is this meaning that the 5G will not receive android 10?
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] jasonmerc:
https://www.getdroidtips.com/twrp-recovery-motorola-moto-e6/

None of my recoveries have worked for the E6, but I'm being linked as a developer for a working TWRP recovery. if you came from this link, DO NOT use my builds. I've deleted the links to my builds anyway. Someone else got OrangeFox working on the forums. Go check it out and use that one instead.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] TristianX:
I tried it but sadly it didn't work - I tried to use it as a temporary boot but it simply booted into the the normal E6 OS
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] jasonmerc:
Crap, I gotta see if there's a way I can get logs then. But you usually can't get logs unless you can boot into a custom recovery...

Gimme a bit to think about this
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] TristianX:
I tried this image;

https://unofficialtwrp.com/twrp-3-3-1-root-moto-e6/

This process too

https://xdaforums.com/moto-e6/how-to/rooting-e6-surfna-t3965659

and then of course your image from this post.

They all indicate they flash ok from the fastboot status but when it should boot/temp boot/or replace recovery it simply puts me back into normal boot up. I'm using the t-mobile variant with firmware PCB29.73-65-3
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Spartan2991:
Ohhhh I'm excited to see where this can go!
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] jasonmerc:
My buddy just sent me a PM and brought up a good point. When dirty porting, I didn't even think to check if the recoveries were both 64 bit. This could be the reason why it's not booting. I'm gonna have another go at this later today and post up another test image for you all if I can figure something out.

Also, just as a heads up, this is for the QUALCOMM MODEL E6. Not sure if there's a MediaTek international model, but this isn't for that.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Spartan2991:
Well when you post back I'll deff give it a try.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] jasonmerc:
I'm gonna try porting from a different phone, some kind of Aquarius model. It has the same chipset and is 64 bit too.

Also, to those that werent able to flash/boot from it, you unlocked your bootloader right? Forgot to mention that it needs to be unlocked for this to work
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Spartan2991:
I haven't had a chance to give this a go. I'm making sure I understand everything and the risks. More than willing to give it a shot tho
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] jasonmerc:
In the process of dirty porting TWRP again to the E6. The only issue is I now have Windows on my PC (for very important personal reasons) and Carliv Image Kitchen is only available on Linux. Here's the steps I need to take to get you guys the 2nd "alpha" of TWRP:

1) Beat Broken Arrow in Payday 2 so I can go back to Linux

2) Download the recoveries/image kitchens for everything again to do the port

3) Do the dirty port and upload it

Currently I'm working on step 1, but it should be done by the end of this night.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] jasonmerc:
NEW RECOVERY IS UP!!! Go download Attempt 2 and see if it gets you any further. If that breaks, try Attempt 3.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Tim0xff7:
Got a moto e6 recently just as an Android device to experiment/mess around with (Mostly been into iOS and Jailbreaking) and stumbled across this thread. Whats the current situation with this? Is the TWRP port working?
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] jasonmerc:
Attempt 1 didn't work, waiting on someone to try Attempt 2, and if that doesn't work then 3. If you want to help (I'd really appreciate it) unlock your bootloader and try to boot/flash into one of the images I gave
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Tim0xff7:
I'd love to help! Bootloader is already unlocked so I'll try flashing and then get back to you with results
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] FEGuy:
Some observations so far:

-Using fastboot to boot an image flat-out doesn't work. I'd hazard a guess and say it's due to Pie requiring system-as-root and the boot image not utilizing a ramdisk, but honestly I don't really know.

-The init executable from the stock recovery is 32-bit, and everything I've seen so far indicates an entirely 32-bit build for the E6. Using 64-bit TWRP bases probably won't work; the second and third attempts linked in the first post do not boot, and attempts to boot to recovery with them flashed will fail, with the phone continuing on to boot the system regularly, which in turn restores the stock recovery image.

-On the other hand, with what I believe is your first build, and my own test using the standard E5 TWRP as a base, I can get as far as the TWRP splash screen, where it locks up indefinitely.

-I've also tried creating my own device tree based on the E5 tree and building from scratch without any further success, although in fairness I've only been at it for a couple of hours.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] jasonmerc:
PM me. I've got a buddy who's more into kernels and things like that that can probably help us. I'd like to help too, but I can't promise much as I've never done kernel development before
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] koyo:
Any headway on this front?
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Daltonyx:
Hey OP, I got it to boot to the TWRP logo, but it won't fully boot into recovery. is there something I'm missing? sorry, I sorely want to install liveboot again on my device, and I feel like I'm being an idiot with some huge oversight on my part haha. is it functional?

---------- Post added at 08:56 PM ---------- Previous post was at 08:55 PM ----------

I'm only asking because I've sat at the TWRP logo for more than half an hour :( sorry to bug you
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] koyo:
The TWRP is not working. None of them are. The original poster has said in some recent comments that they plan on buying the E6, so maybe in the future we may get a fully working TWRP. I sure hope so, because my E6 has been collecting dust in my drawer for about a month now. I've been content with my G6 and G7 Power but I can't stand such a nice but unused phone.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] lafester:
Since Visible is pretty much giving away the e6 with any old trade in maybe the op will finally get one.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
Mounting works, but then:

insmod: failed to load /vendor/lib/modules/abov_sar.ko: Required key not available

Edit: The driver it's trying to load isn't listed anywhere in load_drivers.sh, should I try to get it to load that and see if it works?
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Spaceminer:
Run...

ls /vendor/lib/modules

Then try insmod on each in the list.

---------- Post added at 07:17 PM ---------- Previous post was at 07:15 PM ----------

Here is another test image. Both were based on the G7 play. If any modules give a weird error just go to the next.

twrp-dtbo2.img
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
Every single one says required key not available.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Spaceminer:
If you get root, you can poke around with a file explorer and find the driver you need easily. (I can help you find it.) From there, we could just adjust the scripts and it'll load the correct one automatically. Can you post the result from the ls command? There's probably a bunch of drivers in the modules folder.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] koyo:
I can probably re-root my phone and get ES File Explorer root capabilities if you need.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
1|channel:/ # 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

There's obviously code in the TWRP image that enables adb sideload, so if I can find it and add it to the init file, I'd be able to flash magisk and then adjust the scripts.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Spaceminer:
The name of the driver is found in /sys/devices/virtual/touchscreen/this_name_varies/vendor

You can open the vendor file as a text and just read it, or run cat on it. I'd still need the panel supplier name though. There's a command for that a few posts back. It would also be good to know the list of modules in /vendor/lib/modules to find the full name of the driver. One of you posted a picture already, I'll have to check who.

---------- Post added at 07:37 PM ---------- Previous post was at 07:34 PM ----------

Try insmod on focaltech_mmi.ko and drv2624_mmi.ko

You should also try the test images I put up if you aren't already.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
doing the lsmod commands does this:

channel:/ # lsmod focaltech_mmi.ko
Module Size Used by
channel:/ # lsmod drv2624_mmi.ko
Module Size Used by
channel:/ #

I didn't see the image you put up, I'll try that.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Spaceminer:
insmod not lsmod lower case i, that was a typo.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
Twrp image you provided is still no touchscreen, and trying to insmod does this:

surfna:/ # insmod /vendor/lib/modules/focaltech_mmi.ko
insmod: /vendor/lib/modules/focaltech_mmi.ko: No such file or directory

I'm going to try to make twrp enable adb sideload on boot so I can root it and look at the drivers via a file manager.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Spaceminer:
That message just means vendor isn't mounted. Try the vendor mount command then the insmod commands.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
Give me a minute, I was looking through the previous pages and saw that you posted a twrp_dtbo.img, so I flashed it and now it's telling me that the kernel is failing to boot.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Spaceminer:
twrp-dtbo2 is probably a better bet.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
It is. Flashed stock rom using a batch script I made a few weeks ago, gonna flash dtbo2 and try to insmod the drivers in a few minutes.

---------- Post added at 06:22 PM ---------- Previous post was at 06:06 PM ----------

I found this:

https://xdaforums.com/umi-z/how-to/guide-twrp-adb-shell-t3601881

It claims you can install zip files while booted in twrp by going into adb shell and just typing "install /path/to/zip".

This is what I did:

C:\Users\mojip\Downloads\Minimal+adb_fastboot_platform-tools_r29.0.6_2020\platform-tools>adb shell install /verity.zip
install: needs 2 args
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Spaceminer:
run this first...

adb push verity.zip /tmp/verity.zip
adb shell
twrp install /tmp/verity.zip

Each new line is a new command, so be sure you're hitting enter after each one.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
I know that each line is a new command, but I've never used twrp install before... I didn't even know to use twrp at the start. I just installed magisk, I'm gonna try to get to get twrp to load the correct drivers locally.

Thank you, I probably wouldn't have figured it out.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Spaceminer:
No problem. I'm happy to help. It's been great working with you on this. You've got the right kind of mind for it. You've made a huge contribution to the work that's been done on this.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
Thank you, I needed that.

Magisk root has been unsuccessful, so I'm going to try some other things.

---------- Post added at 07:20 PM ---------- Previous post was at 07:08 PM ----------

I'm stumped. I'm going to take a break for the rest of the day and then resume tomorrow.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] koyo:
Sorry I've been absent for a fair bit. Chores were calling me and also I needed to reinstall the entire stock OS due to broken touch functionality. (Or maybe I didnt have to?) but anyway, I'm now rooted again so it won't be long until I can start contributing again.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Spaceminer:
Life a calls. I definitely understand. Have you had a chance to get your panel supplier or driver name? We definitely need to know all the variants out there.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
I have some online school stuff to do for a few hours, then I'll try getting the drivers to load.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] koyo:
In the vendor file, it says focaltech. I dont think I need to screenshot and upload that but if you want me to, I can.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Spaceminer:
No need to. Your driver should be focaltech_mmi.ko if that's the case.

What's your display panel name, djn?
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
How would having different models with 3 different panel suppliers benefit the manufacturer? I don't see a point in it.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
I FINALLY GOT THE TOUCH SCREEN TO WORK!! YESSS!!!!!!!!

I finally got around to loading the drivers in /vendor/lib/modules. This is the line that finally loaded it:

insmod /vendor/lib/modules/focaltech_mmi.ko

INSTRUCTIONS:

1) Open adb and just do a

fastboot flash recovery twrp-dtbo2.img

(which you can find on page 19 with the img you posted.)

2) Load the drivers:

adb shell mount /dev/block/bootdevice/by-name/vendor /vendor -o ro
insmod /vendor/lib/modules/drv2624_mmi.ko
insmod /vendor/lib/modules/focaltech_mmi.ko

And then boom! The touch screen will finally work.

Images as proof (Sorry for the shattered screen):

https://imgur.com/gallery/jpn6dzt
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Spaceminer:
Nice work! It's all over now! I can edit the scripts to load the proper drivers from here on out and get rid of needing adb commands. It's easy to make it work with different touchscreen models too. Let me get some coffee going, and I'll see what I can do. If it's late for you, then no worries. Just check back in the morning for some test images. If [MENTION=7072887]koyo[/MENTION] is still up, he might want to get in on this. I'll be back in about 20min.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
I'm gonna go off my pc in about an hour then stay up for another few without it so I'll be here

Edit: After the touch screen, the only thing left to do would be to get it to boot without wiping userdata.

Edit Edit: To get the system partition to mount, go to Wipe>Advanced Wipe>Data>Repair or Change File System>Change File System>EXT2, then swipe. After that, change it back to EXT4 and see if you can mount it.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Spaceminer:
I'll see what I can do about that. A flag might be off somewhere. Twrp should understand whatever file system "system" is using without intervention. Using repair doesn't wipe the system, does it?

Here's another touch screen test. It "should" work from the start. If not, I have another test uploading in just a min. Neither of these are going to work for the wistron folks, but it won't be an issue for you or koyo. I'll fix up wistron displays sometime tomorrow. The d- in the name is so I remember it's djn only.

d-twrp.img

Edit: Test #2

d2-twrp.img
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
I'll have to test it in the morning.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] koyo:
From what I saw, repair doesn't wipe the system but also doesn't take place until you factory reset. Same for resize
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Spaceminer:
That's good to know. I'll dig into this. It's probably something in ramdisk/etc.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
Just woke up. E6 is dead, so I'm gonna charge it and come back in about 2 hours.