Thanks
WIN:
OS Name Microsoft Windows 10 Pro
Version 10.0.19044 Build 19044
TAB:
-----------------------------------------
Device: Amazon Fire HD 10 (2017)
Codename: suez
FireOS Version: 5.7.0.0 (659662020)
Android Version: 5.1.1
Security Patch: 2019-07-01
Chipset: MT8173
- Things that MIGHT be different:
- I had to glitch this tab via the ground point to write custom recovery
- TWRP v3.6.1_9-2
- Stock rom with no ROOT, not sure if that matters for user creation.
View attachment 5874275
Can't create a user AT ALL, so ADB on new users I don't have is a non-issue lol.
As you can see here I can enter the username but the button I would used to create the user is black, and inactive (unclickable) so no new users.
I am using the "send text" field maybe this video will make it more clear?
View attachment 5874295
All I can figure is that it's an encoding issue/ and illegal charters with sending "&" over ADB. Kind like how "?" can't be in file names on NTFS file systems, or you can't have spaces in folder directories (then must be wrapped in "" quotes) when running commands or bat scripts via command prompts. Or how Spaces in URLS must be encoded as "%20". I figure it's just an ADB idiosyncrasy, but maybe there is some wrapper method to avoid it?
I am able to just type in the & symbols manually, or use scrcpy so it's a total non-issue, but I figure if it can be fixed without much fuss might as well fix it
---
And just to pre-emt any discussion on the subject I am 1000% certain scrcpy is not creating a conflict/causing/contributing to the issue, because up until writing this post I had never installed it, downloaded it, or used it, on ANY system. So it was not, and has not, been present since the issue started.
So I was having the issues I am having now, BEOFRE scrcpy was present on any system I have ever used this tablet on

---
> driver issues ... versions of ADB
Doubt. IIRC, This has been an issue across multiple windows installs. I'm building a new machine again soon so I'll see if I am misremembering, I'll try again after a re-install.
That said just out of due diligence I grabbed a fresh set of ADB drivers from Google, and tried those. Same result from ADB keyboard and the "&" symbol. Same result for creating users.
Out of curiosity is there:
- Stock rom with no ROOT, not sure if that matters for user creation.
- A preferred method of removing ADB drivers and cleaning up?
- A preferred set of ADB drivers for this Tablet, or range of devices?
> a wild guess.
Valid. I'm guessing it's NOT driver issues though since all the other ADB commands sent to the Fire TAB are doing their job and functioning correctly. I have seen stranger thing happen so i would not be at all surprised if this was inexplicably an issue :/