yashsingh1/xdaforums huggingface dataset:
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Spaceminer:
You're learning fast... This is excellent work! I can probably make the touchscreen work with this one. Fingers crossed, I'll give it a go. Try those adb commands and see if it'll get you past the swipe screen. I can give you commands to load drivers if adb will work.

---------- Post added at 05:07 PM ---------- Previous post was at 05:00 PM ----------

You have a snapdragon 435. The US ones do anyhow.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] koyo:
Weird. Things like CPU-Z and websites were telling me I have a Snapdragon 430. I was wrong
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
Can't run the adb commands because now my phone isn't picked up in adb with this twrp img.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Spaceminer:
If you swapped the default prop from stock then you'll need to change some adb flags. All the needed ones are near the top of the images that I've edited so far if you take a look. Have you tried the kernel trick already with your new one?
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
I only changed the stuff in the split_image folder (and possibly changed some text on the splash screen to be something immature), so idk if I changed the prop. If I did, what are the flags I need to change? Also, I did try the kernel trick, as I replaced everything in the split image folder with the stuff from the stock recovery (and added dtbo and something else because they weren't there.)

---------- Post added at 04:06 PM ---------- Previous post was at 03:28 PM ----------

Also, where are the adb flags located?
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Spaceminer:
I'm actually fixing that right now, and making scripts to load your drivers to see if touch will work. It's at the top of the default.prop or prop.default. I always forget which. One is just a symlink.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
Oh, alright. Thank you!
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Spaceminer:
No problem. This is based off your u2 port. Hopefully touch works this time. I'm thrilled you got it to the point that wiping data isn't needed. You might've lead me to a fix that we need for the G7 Play's TWRP in the process. I have one more test incoming after this. If either of these bootloop, then I might just need to add verity keys.

twrp-touchtest1.img

twrp-touchtest2.img
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
It doesn't bootloop, but the touch screen still isn't working and adb won't recognize my phone either.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Spaceminer:
Looks like an adb flag was wrong. Try touch and adb for this one.

twrp-touchtest3.img
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
Same ordeal, no touch or adb.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Spaceminer:
Well this is a head scratcher to say the least. I guess we can take a break for now and I'll do some research in the meantime. We're damn close, but something is obviously still off. It's really been a pleasure working with you on this so far.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
Yeah. I'm going to find some other phones with the same chipset and also try to learn how to make the touch screen work on the images.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Spaceminer:
No sooner than I made that statement did I realize something else that might be amiss. The fstabs. I decided to check, and there was a slot select flag for vendor, which might've prevented the touchscreen drivers from loading. I'm really going to take a short break after this one, but I couldn't help but try it.

twrp-touchtest4.img
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
First, I just want to thank you for all you've done so far. You're a legend. Secondly, I'll see how much I can learn by looking at it and trying to get the adb drivers and touch to work. Take as much time as you need on your break, and don't stress yourself.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Spaceminer:
You can learn a lot. Look in /ramdisk/sbin for a file named load_drivers.sh (might be slightly off with the name) Open it with a text editor. That's how drivers are loaded for the G7 Play in twrp. Check one of the recent attempts I made. You should find the script in any of them. My best guess is that you might use a different display panel than wistron.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
How can I figure out the panel w/o root?
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Spaceminer:
Run this command. It shouldn't need root.

cat /sys/devices/virtual/graphics/fb0/panel_supplier
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
Seems the panel supplier for my phone is djn. Looking at the code in load_drivers.sh, the panel is a djn nova_36525_mmi.

Then I ran a google search the panel name and found some code you provided on the G7 forum https://xdaforums.com/g7-play/development/recovery-dirty-ported-twrp-g7-play-t3947205/page40, which I might be able to use to make the touch screen work! I'll get back to you later to let you know the result.

Edit: Still no touch screen so far, going to keep trying.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Spaceminer:
I'm sure this is the heart of the issue. The load_drivers.sh script actually has an entry for that panel supplier, you might want to check it out if you haven't already.

I somehow missed that in the excitement of the moment. It's so close to done.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
I can't be entirely sure of the issue, but this is my best guess. I think this is where the error lies:

panel_supplier=$(cat /sys/devices/virtual/graphics/fb0/panel_supplier 2> /dev/null)

I don't have any logs to back this up, but I think it might not be able to access that path and therefore isn't loading any drivers. Here's my plan: Find a way to get the drivers, store them locally in the image, and then have twrp load the drivers that way instead of loading it from the system, as it might not be mounted.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Spaceminer:
That's actually how the script checks your panel supplier so it knows which driver to load. You don't need root for it so access isn't an issue. The 2> null is just how you throw away a result so it doesn't spam the terminal output.

---------- Post added at 11:31 PM ---------- Previous post was at 11:29 PM ----------

@EnokiPPT

If you can somehow get adb working, you can run insmod on the vendor drivers to get the touchscreen working. With adb you should be able to run...

insmod /vendor/lib/modules/*.ko

If that doesn't work you can run ls to get a list of vendor modules, then insmod each of them one by one until touch starts working like this...

ls /vendor/lib/modules
insmod /vendor/lib/modules/name_of_first_driver_here.ko

Then just go down the line checking the touchscreen after each try.

Basically the problem is, we need one of the init.rc files in the ramdisk to run that load_drivers.sh script. It's also possible you use a newer driver and the current entry is invalid, or that you just need to load an additional driver along with it. The jist is, we need to insmod those drivers either through one of the init.rc files, or through adb commands. Either would pull it off. rc files + script is ideal though and more practical.

Edit: Also open /ramdisk/etc/twrp.fstab with a text editor. Check the mount lines and delete ;slotselect from the flags sections if any of them have it.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
It's getting late, so I'll do all of that tomorrow
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
None of the lines in the fstabs have ;slotselect so It's fine there, but what do I need to modify to get adb working? This will probably be the last question I have until I can get started on my own.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Spaceminer:
The honest answer is, I don't know. All the normal things that would make adb run correctly aren't working. I have one more guess, otherwise I'll have to do some serious research. Inside your stock recovery ramdisk, in the sbin folder, there's a binary named adbd. Placing that in the sbin of twrp might make adb work. That binary is responsible for adb insecure as far as I can tell. It's definitely worth a shot.

I downloaded your kernel sources and took a look at the configs. You share trees with the following devices. This should help us out a bit. The arm32 binder64 devices are the best bet since they already have matching architecture. All of these have twrp available. The G7 Play is the only one using an unofficial build.

Moto G6 (Ali) - arm32 binder64

Moto G7 Play (Channel) - arm32 binder64

Moto G7 (River) - arm64

Moto G7 Power (Ocean) - arm64
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
I might have figured out the issue! On your twrp-fixed.img file somewhere around page 12, the phone was recognized, but was also unauthorized, which was causing the error when trying to do adb shell. Was there a file for the adb keys? I'm going to try this:

cp /sdcard/adbkey.pub /data/misc/adb/adb_keys

while the phone is booted normally. With luck, I can extract the file from the phone itself and put it in the twrp img to see if it will work.

Edit: [MENTION=7072887]koyo[/MENTION] you still here? I need someone with root to run these commands and then send me the file:

cp /data/misc/adb/adb_keys /sdcard

adb pull /sdcard/adb_keys .
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] koyo:
I am here now. I'll get right on that
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Spaceminer:
Try booting normally, enable debugging in Dev settings, run...

adb devices
adb shell

Select always allow on the prompt on your phone, and authorize your PC. Then try booting up twrp. Adb keys are stored in C:\Users\YOUR_USER_NAME\.android on Windows. You need to copy the adbkey.pub to your adb/fastboot folder.

Then try this command when twrp is booted up.

adb push adbkey.pub /data/misc/adb/adb_keys
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] koyo:
I got /system/bin/sh: adb not found
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Spaceminer:
See my post right above this. It might help you guys out.

Edit: This post.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] koyo:
I think something might be up with my E6 personally because I can't even get to the splash screen using twrp touch test 4. I might have to do that wipe thing though I saw earlier that it wasn't necessary.

EDIT: post fastboot -w, I still cannot get past the Motorola splash screen. Im doing fastboot boot twrp-image-name if that is worth your concern.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Spaceminer:
You probably have a different model. There's at least 2 different ones. My wife has an xt2005-5 and it uses a wistron display panel, but there's other models that use dsbj or something like that.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] koyo:
Mine is a XT2005-3
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
Strange. I'll look into this more, thank you.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Spaceminer:
There's a few of those for different countries. You can find the display panel name by running the command,

cat /sys/devices/virtual/graphics/fb0/panel_supplier

The solution would be, unpack your stock recovery, unpack twrp, replace twrp's split image folder with the one from stock. Then find cmdline in the split image folder and open it with a text editor. Delete the whole verity key id line at the end. Change buildvariant=user to =eng then add this line.

androidboot.selinux=permissive

It should look like this at the end when you're done.

buildvariant=eng androidboot.selinux=permissive

Then delete the 2 files with avb and sig in name in the split image folder. And repack it. If aik fails to repack it, then run the repack.bat file as admin.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
Mine too. It's weird, considering that mine boots twrp and yours isn't, and yours is rootable with the magisk method and mine isn't.

Is your carrier MetroPCS? If not, maybe that explains the difference.

Side note: XT2005-3 models usually have djn panels, but I think it could vary.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Spaceminer:
This wouldn't be unlikely at all. I saw this with the Moto G6 Play and G7 Play. We had multiple types of display panels even amongst models with the exact same number. Carrier or country was always the reason.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
Followed these instructions and flashed the image. We're now a step farther! Touch screen is still a no-go, but now when I plug it in with twrp running, "unknown device" shows up in the file manager, but I still get the error that the phone is unauthorized when trying to run any commands.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] koyo:
I dont activate any of my phones but yes its supposed to be for MetroPCS
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
Mine's also a non-activated MetroPCS version. I'm not sure which country mine is from since I got it secondhand, but as [MENTION=7718083]Spaceminer[/MENTION] said, it probably boils down to them being for different countries
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Spaceminer:
Did you try copying your adb keys from your PC and pushing them when twrp is booted up? I posted some instructions 1 page back. I'm curious if that works.

Edit: Page 15, post #149. There's a direct link one page back, 1st post.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
Trying to boot twrp doesn't work. It sticks on the boot logo and then goes to the OS normally.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Spaceminer:
I'll try running some tests. My wife is off work today and she's on graveyard shift so I have a few hours to try fixing the touch screen and adb. I feel like I can make it happen. It's the U2 port you made that doesn't bootloop correct?
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
I haven't tried booting the U2 port, but when I flashed it, it booted into twrp without needing a userdata wipe. Though my userdata wasn't modified after wiping it a few flashes before the U2 one, so I'm not entirely sure.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] koyo:
I copied the split image folder of stock recovery (if you mean the resulting folder of unpacking an img which contains the ramdisk folder) to the twrp touchscreen test4 split image folder but it only boots into stock recovery asking me if I want to factory reset.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
Welcome back! I ported the moto G6 official twrp (thanks [MENTION=7718083]Spaceminer[/MENTION] for the idea), see if you can boot that. Here's how:

Flash stock recovery as a precaution

fastboot flash recovery name_of_stock_recovery.img

Wipe userdata (otherwise it won't get past the splash screen)

fastboot -w

Flash TWRP (make sure you put the img file in the same place as adb.exe)

fastboot flash recovery twrp_ali-based.img

Then navigate to recovery from fastboot mode. Let me know if this works for you.

EDIT: Forgot the link! My bad https://drive.google.com/open?id=1ZCT2Q0oEvajvBQdg_VZBSHNNyxIAQm1a

Another edit: Here's how to make a dirty port:

Step 1: Download and extract Android Image Kitchen (extract it twice, renaming the zip in between)

Step 2: Paste the image you want to unpack into the folder with all the files

Step 3: Run unpackimg.bat

Step 5: Go to the other AIK folder and paste the stock recovery image, then unpack it.

Step 6: Remove the split-img folder in the TWRP img and replace it with the one from stock

Step 7: Repack the TWRP image and flash it

Bonus: \ramdisk\twres has stuff you can customize to give twrp a nice look.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] koyo:
Let me get this straight: You ported the G6 TWRP to E6 or you ported the G6 TWRP to..? Because my G6 has a working TWRP I dont need another.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
I ported the G6 TWRP to the E6 one.

I also have a G6, but It's a tracfone model and can't be oem unlocked.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] koyo:
This one did boot, but no touchscreen. Im at a screen "Swipe to Allow Modifications." I have an adbkey.pub in the root folder so I guess this is where you guide me to help you

EDIT: I put the adbkey.pub in the root folder but it's still not detecting adb. [MENTION=7718083]Spaceminer[/MENTION] [MENTION=10519503]EnokiPPT[/MENTION]
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
Is your phone recognized in adb? If not, I'm gonna need [MENTION=7718083]Spaceminer[/MENTION] to take it from here.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] koyo:
It's not unfortunately

---------- Post added at 05:54 PM ---------- Previous post was at 05:53 PM ----------

Do you think maybe the system-as-root nature of the phone has something to do with it?
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
Quite honestly, I have no idea.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Spaceminer:
Try this version I just edited from your G6 port. The sh script points to vendor properly now. Just unzip it first.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Spaceminer:
Nah, you use system as root and so do all the devices in your tree. You need a twrp that's compatible with it anyways so the G6 should do fine. My G7 Play's twrp might worthwhile to port from as well. I'm not sure if that driver script set up to load correctly in the G6's twrp. It is in the G7 Play though. We actually rely on it.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
Still no touch screen or recognition by adb. Does G6 use a/b partitioning?
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] koyo:
No. G6 is A-only
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Spaceminer:
Yes. But it shouldn't matter if the fstabs in /ramdisk/etc don't have slotselect for any of the partition mounts.

---------- Post added at 06:23 PM ---------- Previous post was at 06:21 PM ----------

You're right I forgot about that.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] :
Okay. I'm going to try porting from the g7 play twrp you mentioned.

---------- Post added at 05:00 PM ---------- Previous post was at 04:23 PM ----------

I GOT THE ADB DRIVERS WORKING!

I ported the G7 twrp you made and replaced some stuff, flashed it, and boom! Now I just need to find where you posted the instructions in this thread.
[Moto E6 ROMs, Kernels, Recoveries, & Other Develop] Spaceminer:
Try one of these when you have time. Just search for insmod to find my posts about that.

twrp-dtbo.img

---------- Post added at 07:07 PM ---------- Previous post was at 07:04 PM ----------

You might need to run this before the insmod commands will work.

mount /dev/block/bootdevice/by-name/vendor /vendor -o ro
insmod /vendor/lib/modules/*.ko
[Xiaomi Poco F1 Guides, News, & Discussion] shivanshusuraj:
here is join group link

in this group only allowed poco f1 user all telegram news share on this group and

any useful youtube video for poco f1

MOD EDIT: LINK REMOVED

dont pm any member or no call allowed
[Xiaomi Poco F1 Guides, News, & Discussion] the Doctor:
MODERATOR NOTICE:

Per the forum rules, using XDA to promote social media is not allowed:

Refer to the sticky in this section titled "Telegram and Whatsapp Channels - Going Forward" for more information.

THREAD CLOSED
[Android Stick & Console Computers General] Kaoticsolja:
So I have a Android providing hotspot for an Amazon fire stick. But while hotspot is active, screen cast is not available. Im looking for a work around to bypass this. Is there a way to cast to a fire stick without wifi on? I also have another device available as it seems to helps with chrome cast but does not help with fire stick so far.thanks in advance
[Touch Cruise General] deechte:
The NOS has released a nice application to display dutch news, traffic and more. It is said to contain some streaming TV-channels as well.

However, my Polaris doesn't show the streaming-media tab at all. No matter if I'm connected to the internet through HSDPA, Wifi or USB. Can any of you dutch users out there confirm that it works or doesn't work for you either?

There is a FAQ that says:

Ik kan wel de applicatie openen maar ik kan geen video bekijken. Wat gaat er mis?

Het probleem kan verschillende oorzaken hebben:

1. Foute instellingen van de mediaspeler: Zorg ervoor dat de mediaspeler hetzelfde toegangspunt gebruikt als de applicatie. Zorg ervoor dat er geen beperkingen in de instellingen van de mediaspeler zijn(zoals proxy settings). Vraag uw operator welk toegangspunt geschikt is voor videostreaming.

2. Geen breedband data toegang: Zorg ervoor dat u een breedband verbinding heeft. Minimaal 3G/UMTS. Raadpleeg hiervoor de handleiding van uw toestel

Let op! Video streaming is niet altijd onderdeel van uw onbeperkt data abonnement. Neem contact op met uw operator.

Windows Media Player doesn't have any access point settings. My HTC streaming media app has internet as setting. I'm using the standard NL HTC-ROM.
[Touch Cruise General] BobaFeTT_NL:
Yep, I can confirm, I don't have an option to see streaming media either :(
[Touch Cruise General] kariem112:
same here... no streaming :(

Tried on a Tytn2..... no streaming as well
[Touch Cruise General] deechte:
That's not very hopeful! :(
[Touch Cruise General] real187:
het werkt idd nog niet naar behoren.

ik heb zelfde probleem.
[Touch Cruise General] bodelier:
If everybody please would read carefully on the nos website... it states that streaming will be available in the future.. so when te euro 2008 begins or with the olympics probably....
[Touch Cruise General] deechte:
Reading carefully on several sites, like for instance tweakers.net, I see that many people are already watching streams via the application. Furthermore, the 'journaal' should already be there, only more streams will come in the future.
[Touch Cruise General] NikMel:
A quote from nos website:

In theorie moet onze TC dat wel aan kunnen maar ik heb het appi ff geanalyseerd en het blijkt dat dat niet kan.

Ik ben nu bezig met het voor elkaar krijgen van dat ding.
[Touch Cruise General] deechte:
I hope you get it working!!
[Touch Cruise General] diemetdiesnor:
This was a answer of the NOS.

http://tweakers.net/reacties.dsp?Action=Posting&ParentID=2597764
[Touch Cruise General] deechte:
Thanks.

Wouldn't it be possible to use a java-version in Jbed instead?
[OnePlus 7T Questions & Answers] ak88900:
I was just listening to my Music - the Play Music suddenly crashed. Then I force stopped the app and launched YouTube - which crashed too.

This led me to reboot my phone - The PHONE IS NOW IN BOOTLOOP. I am not able to flash it in fastboot / recovery - because I am unable to go there and I am unable to find any fastboot / ROM from OnePlus as well.

Here is my brand new phone - not booting up.

HELP
[OnePlus 7T Questions & Answers] Some_Random_Username:
Contact OnePlus customer support and they should arrange a remote session.
[OnePlus 7T Questions & Answers] dlads:
Connect to a computer and boot to recovery / bootloader. Should be able to recover from there.

Connecting to a computer is important. If you can't get there with just the phone then try that.

If not then contact OnePlus.
[OnePlus 7T Questions & Answers] cultofluna:
Did you manage to fix it?
[OnePlus 7T Questions & Answers] ak88900:
Update : After this, I had my touch not work for a couple of hours.

But This happened when I recovered my backup from Oneplus 6. I used Oneplus Switch for the restore. May be that may be the issue.

A complete factory reset with out restore is working just fine till now. However, I am working with Amazon to get the phone replaced. Hope this wont happen to anyone else.
[OnePlus 7T Questions & Answers] vicky2131:
Good that it's back alive. But the problem seems to be with OnePlus switch app. I have read few more complaints of the switch app.

If suppose you replace setup the new device from scratch and don't copy from an old phone (same issue will surely happen) since issue is with the app.