yashsingh1/xdaforums huggingface dataset:
[Tasker Tips & Tricks] SomebodySysop:
Finally figured this out. Problem is, the text written into field has a leading space and is duplicated every time I repeated the command. Or rather, the last text pasted is added to %CLIP and inserted into field with new text after each command.

I had assumed I could not use AutoInput->write->field id because I could never get it to work. After hours of trial and error, I finally realized I was missing the correct field id in the write action. Located correct field id, removed leading space from %avcommnofilter and used "write" instead of "focus" to avoid pasting from %CLIP. And now it works.

For the benefit of others who find themselves in the same situation, here is the code that worked for me:

Profile: GV TouchTask (6)
Event: AutoVoice Recognized [ Configuration:Command: "google voice text (regex)" ]
Enter: GV Text (13)
A1: Launch App [ App:Voice Data: Exclude From Recent Apps:eek:ff Always Start New Copy:eek:n ]
A2: Wait [ MS:0 Seconds:1 Minutes:0 Hours:0 Days:0 ]
A3: Actions [ Configuration:Action: Tap Method: Point (x,y) Selection: 948 1944 Timeout (Seconds):10 ]
A4: Wait [ MS:0 Seconds:1 Minutes:0 Hours:0 Days:0 ]
A5: Variable Set [ Name:%Space To: Recurse Variables:eek:ff Do Maths:eek:ff Append:eek:ff ]
A6: Variable Search Replace [ Variable:%avcommnofilter Search:%Space Ignore Case:eek:ff Multi-Line:eek:ff One Match Only:eek:n Store Matches In: Replace Matches:eek:n Replace With: ]
A7: AutoInput Action [ Configuration:Type: Text
Value: To
Text to Write : %avcommnofilter
Action : Write Timeout (Seconds):20 ]

My goal was to launch Google voice and start new conversion (send text message), searching for the contact name in my command. Neither Google assistant or Google now will send text messages using Google voice.

I created AutoVoice recognized event based on command "google voice text".

A1 launches Google voice app.

A2 waits 1 second

A3 presses the "start conversation" button on the app's home page. I used TouchTask to press the "start conversation" button, but could have used AutoInput to do the same thing.

A4 waits 1 second

A5 creates variable %Space that just contains one keyboard space character

A6 removes leading (first) space from %avcommnofilter (the contact keyword name in the command)

A7 used AutoInput action "write" to enter contact keyword into "To" field. This was the key -- discovering the field id of the field whee I wanted to write the text. joaomgcd says you can find it using "easy setup". I found it using UI Query.

The end result is that a list of contacts matching the keyword in my command. I just pick the one I want to send text to.

Hopefully I'll get better at this. I hope more newbies will take the time to explain how they fix their problems.

Thank you for the assistance.
[Samsung Galaxy S8+ Questions & Answers] Viryllo:
Does anyone know/own a magnetic USB type C charger for the s8+ that feature quick charge.

I want to know how well they hold up before getting one.
[Samsung Galaxy S8+ Questions & Answers] ssgunner20:
Dont hold your breath. If they are anything like the ones for the s7 edge they were crap and very cheap made. Easily disconnects from the cable. Didnt always fast charge. Need to ensure it attaches right if not it may not charge at all or charge at normal speed. Would not buy another ever again.
[Samsung Galaxy S8+ Questions & Answers] shushine4nep2ne:
https://www.amazon.com/gp/aw/s/ref=...+fast+charge&sprefix=magnetic+usb+type+c+fast

Can't vouch if any of them ACTUALLY fast charge. A customer does claim out works on an S8 though.
[Samsung Galaxy S8+ Questions & Answers] Viryllo:
Thanks for the feedback guys. I've reviewed numerous ones on Amazon and most of them are mixed. I'll keep on digging.

I'll post a link If I find something decent that gets the job done.
[Samsung Galaxy S8+ Questions & Answers] Zulfigar:
Please keep us updated!
[Samsung Galaxy S8+ Questions & Answers] Viryllo:
Will do. I know the phone is still pretty new. So I'll give developers of the mag chargers for the s8 a little more time.
[Samsung Galaxy S8+ Questions & Answers] Curtai:
I'd like to find one so that I could just leave it connected and not have to worry about breaking my charging port..
[Shield Android TV Q&A, Help & Troubleshooting] bobzer:
Hi,

I never root or do anykind of development or advance usage of my shield 2015 pro,

but about 15days ago it just deside do not boot anymore :(. i don't think it got the last update, so i have no clue why it suddenly not boot anymore :(

The green light is there, but there is no output.

i tried to invoke the android fastboot with this nethod : http://nvidia.custhelp.com/app/answ...NNXg0SmNhUFlvNHpHMGkwM29mRlZxTVdQUVElMjElMjE=

i also tried to factory reset with :

http://nvidia.custhelp.com/app/answ...hen-you-are-unable-to-access-android-settings

but didn't succeed to see anything, there is no output at all (the TV says so, and i try other stuff the TV works)

i don't know what to do ?

is it actually bricked ? can i do somthing about it ?

Thank you in advance :)

Bobzer
[Shield Android TV Q&A, Help & Troubleshooting] lavero.burgos:
You didn't mention it so i ask, did you try with other HDMI cables? If still no go and as it is the pro which is more tricky, then better request RMA.

Have you also tried running fastboot commands blindly? I mean do the steps to boot into fastboot/bootloader mode, then if you haven't installed windows drivers try to do so, check device manager, does it recognize your device? What does it show?. If your device is recognized by your PC in fastboot mode and you succeed to install drivers then that will tell us something, otherwise is hard brick but still could be a hardware issue.

Sent from my Tapatalk beta Hub

If I helped hit the Thanks button. Follow Me! ~ DroidMote user ~ Full Android for Shield TV and Nexus Player
[Shield Android TV Q&A, Help & Troubleshooting] bobzer:
Hi,

thanks for trying to help me,

I tried the cable with another device so the cable is fine

i tried the fastboot blindly but no success (maybe/probably/hopefully i don't do it correctly )

about windows i didn't saw it on windows at all, but that wasn't worry me at that time because i didn't know where to look, so i thought it was maybe normal

about driver no idea of what should i do. during my search i saw little bit about adb

all my search bring me to topic where people did stuff to there shield (root, try rom , etc) i didn't do anything so i don't know what information is relevant for me or not

tonight i will install driver and try again.

just to summarize :

After installing the driver:

- if i see the device in the device manager there is hope

- if not it's hard brick and so i can do nothing ?

if that true ?

thanks you
[Shield Android TV Q&A, Help & Troubleshooting] Ichijoe:
I would have a look at the SSHD to SSD migration Threads here on XDA (Shield TV), and attempt to make a backup of the SSHD. (If possible). This will of course be of MAJOR IMPORTANCE if you wish to retain any of the Widevine L1 DRM Provider Content (e.g. Amazon, and Netflix. etc.. etc...)

It seems to me that the Bootloader got wiped / corrupted (Which is actually the good news), or the SSHD has died. (Well it probably can't get worse than that.)

In the SSD Migration Thread there is a link to download an Backed up version of someone else's Shield TV. I managed to use this to recover a hard bricked Shield before. My mistake was not making a backup of the Security Sectors of that Device, and I lost all those Services.

It is however possible to rewrite that backup over a working backup to recover the correct L1 Widevine Keys though. IF YOU REMEMBER to make that Backup first. So it's probably​ not too late to do that. The worst case scenario? Your just gonna lose a buttload of DRM Services that you may, or may not even depend on. If your more of a Kodi Person, than this shouldn't even affect you much. But, of course it would be wiser to try and, retain those Widevine Keys if possible.
[Shield Android TV Q&A, Help & Troubleshooting] lavero.burgos:
Right, if your PC recognize your shield in fastboot mode then it means is alive. When people have hard bricked their devices by corrupted bootloader some are able to boot into APX mode, which confirms their device won't be able to recover (unless Nvidia release the tools), but for others the device won't even turn on.

If your pc recognizes your shield tv in fastboot mode and you are able to install windows drivers and you get an id when typing fastboot devices in cmd, then there is a 50/50 chance of recovering, don't forget the possibility of hardware failure.

The following video can help you, just follow until i open command line and start typing fastboot commands but you just have to type "fastboot devices" command nothing​ else, if you get an id it means that the link with your shield tv is successful.

https://youtu.be/LQaYb4oVHVc

Report back!. Oh but still try other good hdmi cable(s), i tell you for experience, weird **** happens. I have had weird issues with hdmi port and hdmi cable (Amazon basics brand) in the past.
[Shield Android TV Q&A, Help & Troubleshooting] bobzer:
thanks, for the idea, i'll first check with the driver.

and after i'll backup the drive at the same time i'll check if there is smart value. in case is the drive which is in a bad state
[Shield Android TV Q&A, Help & Troubleshooting] bobzer:
to entering the fastboot mode the only way is pressing for about 3sec after powering up or thanks to the drivers it will enter automatically ?

thanks i can't watch it right now but i'll as soon as possible tonight

I will thanks
[Shield Android TV Q&A, Help & Troubleshooting] lavero.burgos:
Better to do it manually as i show in the video, the other method from windows never worked for me and for many.
[Shield Android TV Q&A, Help & Troubleshooting] bobzer:
ok thanks

looking forward to try this
[Shield Android TV Q&A, Help & Troubleshooting] bobzer:
so i'm currently trying and sadly i can confirm that the green light is on, cable plug to shield but not recognize at all in the device manager
[Shield Android TV Q&A, Help & Troubleshooting] bobzer:
i did exactly as explained and the nothing happend except that the green light turn off

so when i plug the cable i remove my fing and put it back on the shield and waiting and after a few second the light goes off and stay off but windows still not recognize :(
[Shield Android TV Q&A, Help & Troubleshooting] Ichijoe:
Did you follow this Guide?* Essentially you make this backup in Two parts uninspiredly called "firstpart.bin" (Which is the first Six Gigabytes of the SSHD which also encompasses​ the unique DRM Keys for your Shield.). The lastpart.bin is more or less just the list of checksums for the GPT Partitions.

I wouldn't expect that you would, could or should be able to see anything from the Drive. As most of it is written in a RAW Partition. That is personally beyond my knowledge of how to mount it. That's why you have to make *.bin files which you can then view with a Hex Editor. If you wanted to.

*https://xdaforums.com/shield-tv/general/guide-migrate-to-ssd-hdd-size-satv-pro-t3440195
[Shield Android TV Q&A, Help & Troubleshooting] bobzer:
i did follow this topic but the problem is that dd doesn't works event fdisk don't work :(

root@debian8:/mnt/raid/backup/shield# fdisk -l /dev/sdb
fdisk: impossible d'ouvrir /dev/sdb: Aucun fichier ou dossier de ce type

it's fdisk telling me that it can't open my drive sdb no file or directory

i even tried ddrecue so i feel like i'm screwed :(

but i don't understand because i never saw this kind of problem with dd, i mean even a damage drive i always could start at least , copy a few bytes ... i don't understand what i miss ... :(
[Shield Android TV Q&A, Help & Troubleshooting] Ichijoe:
Did you remember to enter elevated root first?

$ sudo -s

If you don't do this, or you just throw up a sudo fdisk -l. I don't think it'll work. You have to be in an elevated root shell first.

Then you can use:

# fdisk -l

To list all the Drives currently in your System. Which will be more complicated depending on how many Drives you have.

Again this should list all the Drives currently on your System. You can easily, spot the Shields SSHD by the fact that it is exactly 499GB. Within in this context is the Drive Address. For me this has always been /dev/sda. Where as the local OS was on dev/sdb.

So when you get to this point:

dd if=/dev/sdX of=firstpart.bin count=6899870

You need to replace sdX with the correct Address of the Shield TVs SSHD. This will then hopefully create a ~3GB File called 'firstpart.bin'

Likewise

dd if=/dev/sdX bs=512 skip=976773158 of=lastpart.bin

Will create a 5kb File that hosts the Partition Map?

Again you have to replace sdX with the correct Address where the Shield TVs SSHD is hosted.
[Shield Android TV Q&A, Help & Troubleshooting] bobzer:
thanks I will double check tonight but i'm pretty sure that i was root
[Shield Android TV Q&A, Help & Troubleshooting] bobzer:
fdisk don't see the disk :(

i don't know what to do

I bought a new adapter because at first i thought it could be the adapter but no it's the drive that is like dead. so i bought a new drive but because i can't get a backup of the old one i don't know what to do :(

can i find somewhere a full backup that i could put in my drive ?

thx
[Shield Android TV Q&A, Help & Troubleshooting] bobzer:
i try to copy with dd and ddrescue, until now i got 0 bytes rescued :( so i guess my only luck would be to get a backup somewhere else, but even there would i be able to run netflix ?
[Shield Android TV Q&A, Help & Troubleshooting] lavero.burgos:
You should contact Nvidia for replacement, hardware died, not your fault. Unfortunately if you didn't backup the relevant partitions containing your keys, then no you wont be able to watch Netflix.

Sent from my Tapatalk beta Hub

If I helped hit the Thanks button. Follow Me! ~ DroidMote user ~ Full Android for Shield TV and Nexus Player
[Shield Android TV Q&A, Help & Troubleshooting] cu6apum:
Hiyas. Welcome a fresh corpse.

Shield 2015, non-pro, bricked by flashing a wrong image.

Bricked well, no adb, no screen, no button - just green led on powerup.

Nvidia says there's no official service in our swamps (lovely, huh) and I'm up to myself.

Anyone with succesful revival? Thanks guys.
[Samsung Galaxy S7 Questions and Answers] RealALCoL:
Hi this phone is aweaome but in certain circunstances overheat and reboot loop then crash i have to put on ice to work normally how can i fix this? I got 6.0.1, thanks in advance
[Defy Q&A, Help & Troubleshooting] dapyejis:
Hi My defy(MB525& green lens) is not show anything.

several years ago I tried defy+ Rom

installed CM11(Ver. 4.4.2 & showing MB526). but I want new ROM I tried TWRP installed after brick.

I little bit confuse (defy or Defy+) first I tried to defy+ SBF but stuck, and defy SBF Stuck.

another Defy+SBF.

Now My defy is just black screen....

RSD is "connected" My defy, but I can't start bootloader( anything show text) and No MOTO mark...

what should I do?

similarly this thread: https://xdaforums.com/showthread.php?t=1382667&page=2
[General Questions and Answers] aff3p:
Which files are checked by "locked" bootloaders? Want to root locked phone.

//Skip to the last paragraph if you don't care about the context of the question

Hi, I'm looking to get a few applications requiring root onto a device with a locked bootloader. I'm a programmer, but not an android programmer, and my linux skills are only mediocre. Until recently I had an S5 active (also locked) using TWRP and a custom ROM, but the "waterproof" feature didn't work when I fell in a river with it. I've long since forgotten how I managed to get it working, it involved reading threads here for about 2 days until I figured out enough to get it working.

The only specific items I want to install that require root are a whitelist-style firewall and xprivacy. My plan of attack, unless I find anything more promising, is don't immediately allow the new phone (CAT S60) to get updates, get temporary root with dirtycow, then attempt to modify something that is both A) running in root context and B) the bootloader won't complain about. The problem is that I have no idea which things the bootloader is checking.

What I can't figure out is which files are actually "verified" by the bootloader on Android? Just the initramfs? The entire root partition (i.e. everything outside userspace) as well? Is it a short enough checksum that it could be defeated by padding the image until it reaches the same checksum?
[General Questions and Answers] specnaz157:
yeah let us know if you can get it to root , lot of people are banging their head over this on this forum
[General Questions and Answers] Droidriven:
I believe it checks the entire /system partition during boot just before/as the kernel loads it to verify whether /system has been modified.

I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[Verizon Samsung Galaxy S6] hibby50:
I got the lte to work with the apn settings, although it keeps breaking after a little while but that's a separate issue. The main issue is I cant make or receive calls, which I thought would be the easiest part. SMS even sends and receives! I searched high and low for an answer but can't find any and no dialer codes are working.
[Android Auto General] Xcaptain:
Since there is no thread that specifically lists Android Auto compatibility maybe we can start one here.

Topway/Unbranded Allwinner T3, Quadcore A9 1.6GHz, Android 5.1.2 — NOT Compatible.View attachment 4178863
[Galaxy Grand Prime Android Development] arsh@63338:
Do you want google assistant in your device. Then watch this video. You can now get assistant in all of your devices. [youtube]zHwEAGkDrnE[/youtube]
[Moto G4 Questions & Answers] *XAOS*:
So recently I bricked my deviced and I had to flash the original image that the phone came with - I have moto G4 XT1625.

My phone is unlocked although I have unsuccessfully tried to relock it.

Problem: Once I flashed the original version of android which was Marshmallow 6.0 I am unable to update to 7.0 as I had before I bricked my device.

How can I update to Nougat 7.0 and relock it. I cannot find any image for Nougat 7.0 anywhere as that is not the original for the Moto G4. Any ideas?

Edit: I tried relocking it the 2 ways -

1. fastboot oem lock

2. fastboot oem lock begin and then reflashing all the firmware and then locking
[Moto G4 Questions & Answers] zonggestsu:
Nougat stock image

https://androidfilehost.com/?fid=673368273298955218
[Moto G4 Questions & Answers] *XAOS*:
Sure?

Do you know if this would be an official ROM or is this a custom copy where I wont get updates?
[Moto G4 Questions & Answers] zonggestsu:
Its the the official image. You should be able to flash it then remove your bootloader if you feel like it. Word of warning, it looks like, at least from my experience, that the g4 bootloader doesn't properly check the images properly unless you invoke

fastboot oem lock

twice. Then you can start flashing over the images such as oem.img and system.img_sparsechunck.0

The bootloader.img and gpt.bin need to be flashed before this though.
[Moto G4 Questions & Answers] *XAOS*:
Thank you!!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] popeye2755:
Hi, does anybody have a link to the original UK HTC ROM?

Thanks
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] sambartle:
I'll bite..

I don't think there is a UK HTC ROM?

You maybe want the World Wide English one?

Sam
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] popeye2755:
Thanks for the reply Sam!

Cheers

John
[Sprint Samsung Galaxy S6] digitalchaos1980:
Hi y'all, first off I have the G920P, just recently upgraded to Nougat QC7 stock ROM, modified and running the SkyHigh kernel v5.01 with Magisk v12. Everything runs pretty smooth, even got Liveboot working successfully (there's a reason I mention Liveboot.) Now I decided to try to get Viper4Android to work. Of course, installing the standard apk fails when it comes to installing the driver. So I tried the V4A Magisk module and it installed fine, however on reboot, my Liveboot no longer works and when opening the V4A app it asks to install the driver, I hit yes and it says it successfully installed and to please reboot. I reboot and of course Liveboot still doesn't show, but otherwise it boots fine. Once I re-open the V4A app it is asking me to install the driver yet again, and the whole system at times seems a bit unstable until I disable the V4A module in Magisk Manager. Does anyone have any ideas, or has anyone gotten this to successfully work? If so I'd love a suggestion lol. I really would like to keep my Liveboot working, but I'd kinda like to get Viper working too. Thanks in advance for any help, suggestions, ideas, etc. :)

Chuck
[Sprint Samsung Galaxy S6] koop1955:
I could not get the V4A module to install under Magisk 12; however, it works just fine with Magisk 13.

This is the version that I used: https://www.androidfilehost.com/?fid=745425885120735287

Magisk Uninstaller (should not be needed, but if you want it) is here: https://www.androidfilehost.com/?fid=745425885120735289

NOTE: You are, I believe using the [MENTION=4988866]tdhite[/MENTION] kernel, which is based in Magisk 12. Not sure what the impact of installing Magisk 13 will be.
[Sprint Samsung Galaxy S6] tdhite:
The kernel is fine with Magisk v13 (beta, to be sure is all that is released there). Magisk v13 beta still has problems, so beware. The SkyHigh kernel and module are v13 compatible as much as v12, just so you know. The reason v12 is packaged in is v12 is the only stable Magisk version at this point.

The bigger issue is Magisk v13 beta working stably and reliably, but if you are willing to debug its failures, it's ok. There should be no need to uninstall to upgrade if you want to play. Reloading the kernel flash will cleanly load up v12 if all goes badly.
[Sprint Samsung Galaxy S6] digitalchaos1980:
[MENTION=3816775]koop1955[/MENTION] Thank you for that information! I will bookmark those so I can get back to them once v13 is reliable and stable enough for my kernel :)

[MENTION=4988866]tdhite[/MENTION] Thanks bud as Well! I think I will just stay where I am until the kernel and v13 play nicely. Just got this thing as perfect as I can for now, well other than ram use creeping up, but that's only every now and then, and for another topic. I *might* get my nandroid current and play a little if I get bored and want to tinker. I guess I can safely assume then the reason Liveboot stops working with the V4A module installed is because of Magisk v12...?

Thank you to both of you guys for the help and advice. At least now I know it's not some dumb issue with my device lol. :)

Chuck
[Sprint Samsung Galaxy S6] koop1955:
[MENTION=5382499]digitalchaos1980[/MENTION] and [MENTION=4988866]tdhite[/MENTION], I have had a good experience with one particular version of Magisk 13, which is why I added it to my AFH. Other and newer versions...not so much. To be expected with a work in progress.

At some point, Magisk 13 will be final and we can move forward.
[Sprint Samsung Galaxy S6] digitalchaos1980:
No doubt! Version 13 gives me something to look forward to for sure :)

Chuck
[Sprint Samsung Galaxy S6] Wasef x:
if you kindly Tell me the process how did you end up using Live boot in magisk , It would be very helpful . I have tried various method but failed
[Sprint Samsung Galaxy S6] tdhite:
Just to be sure, folks realize there is full equalizer support in my SkyHigh kernel and the bands are all adjustable, even per channel if desired, in Synapse, right? Just noting in case that's all you need, because it is a no-CPU-load way of getting it done.