yashsingh1/xdaforums huggingface dataset:
[Sony Xperia E1] thurblunt:
Aproveitando o gancho, também estou precisando de um apk stock... Apaguei sem querer o apk responsável por fazer buscas de mídia pelo celular. Não aparece nenhuma mídia no player nem na galeria mais. A solução que achei foi ir nas Configs > Aplicativos e abrir esse "armazenamento de mídia" e limpar seus dados. Mas foi aí que realizei que eu tinha apagado ele kkkk Agora estou caçando o apk original.

Se puderem me ajudar, o apk é o "Armazenamento de mídia" (com.android.providers.media).

Criei um tópico também pedindo ajuda, mas seria melhor com vocês, já que meu inglês não é muito bom kkkkk

Valeu guys :).
[XDA Assist] dj57:
This is a customer's device that was brought in with apparent charging problem. After locating proper charging port replacement and installing it, the device is charging, but will not start. I have tried all the various boot combinations and to device still refuses to boot. There is no apparent damage to screen, but even my computer will not recognize the device as a storage device. Is there any ideas what might be the problem? Is this device beyond repair?
[XDA Assist] xanthrax:
Hi !

I want you to be sure that there is no hardware damage and for this you must go to a service center.

Without fixing it is not worth trying software fixes attempts

Good luck !
[Touch Dual, MDA Touch Plus ROM Development] Tileco:
Hello people, there is some one hith PT ROM for HTC Touch Dual Please?????!!!!!

Thanks...

Kind Regards....
[Touch Dual, MDA Touch Plus ROM Development] ernomo:
original or cooked?
[Touch Dual, MDA Touch Plus ROM Development] Tileco:
Original or Cooked is not important...

Safe is very IMPORTANT... ;)

Regards...
[Touch Dual, MDA Touch Plus ROM Development] jvieira:
need it too!
[Touch Dual, MDA Touch Plus ROM Development] gui567:
so do i

i'm searching a portuguese rom for my dual touch that i bought in italy. its possible to instal it in an italian language and transformed in one with portuguese language? can someone tells me if its possible?

Thanks a lot
[Touch Dual, MDA Touch Plus ROM Development] joaosousa:
No, i don't think it is a good idea. Do you have hardspl?

I have the TMN official rom...

You can get it here:

http://netrunnerat.4shared.com/

But you can't flash it without hardspl... read about that first.
[Touch Dual, MDA Touch Plus ROM Development] gui567:
Thanks joaosousa, where can i find a tutorial step-by-step for instaling this rom in my italian Dual Touch, and all the tools like hardspl or another one....

Thanks a lot for your help
[Touch Dual, MDA Touch Plus ROM Development] joaosousa:
A good way to start is reading the niki threads. All the info you need is provided here in xda-developers forum.
[ZenFone 2 Q&A, Help & Troubleshooting] dicamarques:
I bought my phone from a chinese seller, its the 1.8ghz 4GB Ram and 16gb internal memory version.

It already had the WW version of LL, I followed a guide in the asus forums and reflashed the recovery and the rom from ww (just to be sure it was not in the chinese rom)

Afterwards I did adb sideload to MM. So far so good.

But if I go to the recovery there are several issues, first off when I boot to the recovery it appears the "Error!" screen, I searched and if I power button and volume up quick, I get to the recovery. And before choosing to enter the recovery, fastboot mode??, there are some status messages and they show the product name, variant, etc. Some of them show unknown, BL_Version, HW_Version, Signing, Secure_boot

Is there any fix for this? Is it safe to unlock the bootloader like this? I think I might have a diferent bootloader, ie MM FW with LL BL.

Thanks
[ZenFone 2 Q&A, Help & Troubleshooting] sukhwant717:
buddy you don't have any issue with your device. and the error screen while entering recovering mode is usual. if you don't like that flash twrp. you will overcome that issue. also fasboot screen showing versions as unknown is also not an issue.
[ZenFone 2 Q&A, Help & Troubleshooting] dicamarques:
Well I unlocked the bootloader, installed twrp and rooted using the new Toolkit available here and it still says BOOTLOADER STATUS: UNKNOWN in the toolkit window.

Also, now when I boot it theres an error screen saying that cant verifiy some signature, right before asus logo, is it because of the Unlock of the bootloader?
[Shield Android TV General] DummyPLUG:
Use as your own risk! a wrong keylayout may totally disable the input device. Tested on Shield TV 2017 16GB

If you are using 3rd party remote on Shield TV some key may not work as intent, or you want to remap the key for another function, for example I had a xiaomi remote (just $4 dollar) which the home key not working.

Although you use custom IME (such as mkr Multilanguage Keymap Redefiner) or some keyboard remap app (such as buttons remapper), which work but not perfect, some function may not work such as double press the home button to show recent app list, or conflict with shield tv controller button (buttons remapper disable the voice search button on my shield controller), and you may need to change every time for each different remote/controller.

Luckly android allow you to use specific key layout for each different remote.

1. flash the developer image, which is pre-rooted, or root it yourself

2. adb shell

3. cat /proc/bus/input/devices

Now you will have a list of connected remote/controller, take a note of the Vendor number and the Product number​

4. adb pull /system/usr/keylayout

5a. modify a exist keylayout file, or create a new one. The file name should be Vendor_XXXX_Product_XXXX.kl, Don't change the Generic.kl

5b. use any keytest app to check the key scancode, I am using "Multilanguage Keymap Redefiner"

for example my xiaomi remote home key scancode is "102", which map to MOVE_HOME by default, so I create a new file "Vendor_2717_Product_3200.kl", the file will be like this:​

key 28 DPAD_CENTER

key 102 HOME

key 103 DPAD_UP

key 105 DPAD_LEFT

key 106 DPAD_RIGHT

key 108 DPAD_DOWN

key 114 VOLUME_DOWN

key 115 VOLUME_UP

key 116 POWER

key 127 MENU

key 158 BACK​

Any key not listed will be disable, so make sure you have all key listed

6. copy the file back to shield tv:

adb root

adb disable-verity

adb reboot

adb root

adb remount

adb push "layout file" /system/usr/keylayout​

7. reboot.

P.S. Don't change the Generic.kl, change the keylayout file one at each time

Shield TV remote Home button is map to HOME, and the dpad center is map to DPAD_CENTER, so other remote which map to MOVE_HOME and ENTER (such as my xiaomi remote) will need this mod

The shield TV come with lot of keylayout file for many different controller/remote, I see MI, wii,xbox 360, but there seems no amazon

I had attach the keylayout file pull from my sheild tv, may be you can take a look which controller/remote is support offically​
[Shield Android TV General] Kylistar:
I cant do adb remount, it says I have to be root, and when I do adb root first it seems to pass but it still says I have to be root when i try adb remount.

How do I set my /system to r/w instead of r/o? I have tried adb mount o rw,remount /system but it wont do anything.. also the command you tell me to use, "adb disable-verity" says:

disable-verity only works for userdebug builds

Can you please help me?
[Shield Android TV General] DummyPLUG:
you need to root it yourself or using the developer firmware in here:

https://developer.nvidia.com/gameworksdownload#?search=SHIELD

note that future OTA may fail because it will send you normal firmware even you are on developer firmware
[Shield Android TV General] Kylistar:
I did root my nvidia shield. It is supposed to be rooted, I got super user(superSU) installed on it and Everything..
[Shield Android TV General] DummyPLUG:
you mean mount -o remount,rw /system didn't work? but I suppose it can't as verity will prevent it, I hear SU in 7.0 will disable verity but I didn't try it before, sorry about this.
[Shield Android TV General] Kylistar:
I actually got the kl file into the system/usr/keylayout directory now, using TWRP

with these steps:

Reboot to Bootloader

Type “adb reboot bootloader” and hit enter. The Shield TV should reboot into the bootloader screen.

Fastboot with TWRP

Type “fastboot devices” and make sure your Shield TV is visible.

If your Shield TV is listed, type “fastboot boot twrprecovery.img”

in the TWRP i can chose mount and check system, then i was able to move the .kl file from the sdcard to the keylayout directory, still my nvidia shield doesnt give it the new settings.. its given the same configuration as my nvidia controllers. I have double checked that Vendor nr and Product nr is the same as the controllers.

here's my .kl file:

# ps4

key 304 BUTTON_X

key 305 BUTTON_A

key 306 BUTTON_B

key 307 BUTTON_Y

key 308 BUTTON_L1

key 309 BUTTON_R1

key 310 BUTTON_L2

key 311 BUTTON_R2

key 312 BACK

key 313 HOME

key 314 BUTTON_THUMBL

key 315 BUTTON_THUMBR

key 316 BUTTON_START

looks correct?

Thanks for your time!
[Shield Android TV General] DummyPLUG:
Yes TWRP can write into system, but last time when I try it trigger the verity protection sometime, don't investigate it though as I am lazy and just use the developer build since then. (another reason I semi brick my shield a few time with twrp)

the.kl looks correct, to see what is the problem try remove one of those key from the .kl, if shield load the file correctly that key should be disable, if not then the .kl file is not work.

I can't remember if the file need to be in unix EOL style or not, that means if you edit it in windows notepad it may not work, try notepad++ or pspad. (I may mix up with bt_config.conf, which I use to maually pair my xiaomi remote)
[Shield Android TV General] Kylistar:
It looks like my shield wont recognize the files im putting in there, I tried replacing the Generic file with a modified one, after that the ps4 controller wont work at all, Before it just had the wrong buttons, then i tried changing back to the original file and the shield wont read it.

This should mean the reason my new .kl file for the ps4 controller wasnt recognized because of this.

Any idea what I do now? How do I get it to recognize the files? How do I get at least the generic back if that is not possible?

And yes, I do use pspad.
[Shield Android TV General] DummyPLUG:
If you replace the generic file and it didn't work this mean the file is something wrong, the first thing I come in my mind is the file still using windows (CRLF) not Unix (LF), but as you said even you copy the original .kl back to shield it still didn't work then may be the dm-verity kick in

if it is dm-verity kick in the best and easiest way to recovey is flash the firmware again, as it is hard to modify the current system block to have the same hash as original one
[Shield Android TV General] bubbablacksmith:
I am having the same issue as above. My Shield doesn't recognize the changes made to the .kl file I edited.

I have a rooted Shield running on the latest Shield software 7.0.2 and a Fire TV Stick Remote connected.

I used cat /proc/bus/input/devices to see the remote uses vendor 1949 product 0404 key layout.

I went to system/usr/keylayouts, navigated to that kl file and then modified the 2 keys I wanted to change. Rewind and fast forward. I changed them to VOL_DOWN and VOL_UP.

I saved the changes and rebooted.

However they still act as MEDIA_REWIND and MEDIA_FAST_FORWARD.

I have verified the changes are still showing in the key layout file. I don't understand why it's not working.

The last time I rooted my Shield, I was using another Fire TV remote (the Alexa Voice Remote), which uses 1949 0407.kl file.

I modified that one to make the same changes and it worked. I could control the volume.

Since then though, I've factory reset the Shield am rooted onced again and this time I am using this fire tv stick remote, but can't seem to get the changes to the key layout file to actually take affect and I don't understand why it's not working. What is different than when I modified the other remote? Makes no sense.

EDIT: Ok so I figured it out basically right after making this post. I was trying to use VOL_UP and VOL_DOWN, which I could have sworn was the correct key code and what I used with my other Fire TV remote before I factory reset. However I tried again, this time though using VOLUME_UP and VOLUME_DOWN and it worked properly.

Damn, I'm dumb. Now it's working exactly how I wanted it to.

I am guessing by using the wrong key code, thus rendering it useless, it was falling back to the key code used for the same key ID in the generic.kl file?
[Shield Android TV General] michau83:
thanks, i will try
[Shield Android TV General] michau83:
How do we know the vendor number for external remote? I tried on android box and there is no system under /proc
[Shield Android TV General] iaminfa:
how do i set the proper chmod when running the push command to put the file onto the device?
[Shield Android TV General] eagledipesh:
Thanks for this, but I am trying to use Mi remote with voice control

Everything works except the Google assistant button, it brings up assistant but doesn't detect any voice from remote.
[Shield Android TV General] daniel_loft:
Can something similar be done with an IR remote?

I'd love to have more buttons that I could use for all kinds of automations.

Thanks!
[Shield Android TV General] Rahatul Islam Prince:
How to open app using this method? Suppose I want to open google chrome, how would I do that? @DummyPLUG
[Nova Launcher] FaLLenJinX:
Hey guys. I have an idea. Is there any way to make your wallpaper blurry just on some screens? By that I mean I'd really like to have a normal wallpaper on my main homescreen but if I swiped to my second screen the wallpaper would smoothly become blurry. Thanks for any advice. :)
[Nova Launcher] 95先生:
This app can set different wallpapers for each screen:laugh:.

https://play.google.com/store/apps/details?id=com.go.multiplewallpaper
[Xiaomi Redmi 2 Questions & Answers] lovely cat:
the miui rom based on android N has released in several xiaomi devices and miui patchrom,but our device hasnt got any news. the new 'recond screen' only provide in android M and N but we only have android L and never updated.pls who will make a rom based on los 14.1 and give us a surprise?:)
[Xiaomi Redmi 2 Questions & Answers] LuanHalaiko:
MiUI is ****, stay with lineageOS
[Xiaomi Redmi 2 Questions & Answers] lovely cat:
but miui is based on los(aosp) yes?
[Xiaomi Redmi 2 Questions & Answers] LuanHalaiko:
LOL, miui is NOT LineageOS, idk if it is based on aosp, but LineageOS xD
[Xiaomi Redmi 2 Questions & Answers] ROCKY_ME:
Lol....mini is ****** but miui Hellas by gakelan is not.Using about 2 weeks.Didnt have a single issue.

Battery back up is insane (5-5.15 hrs SOT...damn ) on LTE,Butter smooth, Lot of themes.

But still on Lollypop. :(
[Xiaomi Redmi 2 Questions & Answers] lovely cat:
and simply me gave us an aosp rom based on N

Who will make it into miui?
[Xiaomi Redmi 2 Questions & Answers] lovely cat:
whose here
[LG V20 Guides, News, & Discussion] Damisa-Sarki:
I flashed the Google assistant some time ago and everything was fine but yesterday I decided to do some minor build prop edits and accidentally bricked my phone. Now that's fine because they have multiple ways of unbricking the T-Mobile LG v20. But when I tried to unbricking it using LGup nothing works because it registers my phone as a pixel and now my phone can't be restored. So take it from me..Don't do it!!! It isn't worth the loss. I have a brick now. An official lg v20 brick. Sigh

EDIT:

IM EDITING THIS TO ADD WHAT I DID.

Here's the story

I was trying to revert to stock with the build prop so I could upgrade my phone. so I edited the prob and removed the lines I added to get Google assistant in the first place but it crashed and when I entered TWRP to push the build prop. When that didn't work I flashed the stock tot file which got my phone working but I wanted to upgrade so I found the page in XDA to flash the kdz with LGup which I was doing but half way through it failed and Twrp was gone which started this snow ball effect.
[LG V20 Guides, News, & Discussion] CharlzO_2000:
Do you not have TWRP you can reboot into, and re-flash a backup or new ROM?
[LG V20 Guides, News, & Discussion] Damisa-Sarki:
Nope, the only thing my phone does it boot into the mode where it says "Firmware update" mode. I really think I destroyed my phone.
[LG V20 Guides, News, & Discussion] slayerh4x:
Take it to the store and tell them it happend when the phone was updating.
[LG V20 Guides, News, & Discussion] Damisa-Sarki:
That's actually a pretty good idea. I'm going as soon as TMobile opens.
[LG V20 Guides, News, & Discussion] Leonarddale:
I had the same problem. ADB didn't recognize my device to run command to reboot recovery. I found that ADB did pick it up while doing a factory reset. Even tho it was the original LG factory reset screen it would use TWRP to perform the reset but would automatically reboot after. So I had a command window opened with adb reboot-recovery typed then I rebooted into the original factory reset and selected yes twice. As soon as TWRP screen came up and I heard the windows chime recognizing the device I hit enter in command window to reboot recovery and it rebooted into TWRP normally where I was able to restore from backup. If you time it right you can get back to TWRP. Hope this helps
[LG V20 Guides, News, & Discussion] planetbeen:
This.
[LG V20 Guides, News, & Discussion] shadowxaero:
That is very strange, I recently bricked my phone to the point where I didn't have a system at all on it. When you boot to firmware update mode (power + volume up) and pluged it in LGUp recognized it instantly. You have the correct DLL for your device right?
[LG V20 Guides, News, & Discussion] Damisa-Sarki:
My issue was that when I flashed the assistant mod it turned my device name into " google pixel" so when I hooked it up to lgup it read it as a pixel and failed the restore every time. That was the issue I couldnt change the name of my devixe back to the v20.
[LG V20 Guides, News, & Discussion] Damisa-Sarki:
I disnt have anything on my phone. No twrp and I couldnt install it. The assistant mod changed my device name to PIXEL and when id connect it to the pc it read as a pixel and failed every update I LG V20 I pushed to it..that was a new type of brick lol. But I told t mobile that if I what happened and I got another one.
[LG V20 Guides, News, & Discussion] SpasilliumNexus:
These old assistant mods would be taken down. The only thing needed to enable it without spoofing a phone as a Pixel is adding "ro.opa.eligible_device=true" to build.prop, and the Google app updated via Play Store.
[LG V20 Guides, News, & Discussion] shadowxaero:
That's the thing my phone didn't have a system on it at all and LGUp read it as what it was. When you on the firmware screen it should read based on hardware ID right? Have you tried using LG bridge? Are you on the T-Mobile variant?
[LG V20 Guides, News, & Discussion] Negan:
This is a contributing factor in why these companies lock bootloaders. People do stupid things because they don't know what they're doing and then others encourage them to just return it and get a new one and lie. Not cool at all. How about don't root your phone if you don't know what you're doing.
[LG V20 Guides, News, & Discussion] Damisa-Sarki:
WTF! With your logic no one would learn anything.

My phone was rooted just fine. How was I suppose to know that after I flashed the stock build prop my phone was going to stay as a pixel device?? That wasn't stupid of me that was trial and error. Something stupid is if I did it again. No one specified that my phone would stay as a pixel device, go read the instructions and tell me where it says that. Also, I have "Jump on demand" so I used one of my jumps to get a brand new phone..So I paid a price for it. It wasn't just "me lying and getting a free phone" I still paid for it I paid for my mistake and Yes initially I lied but still paid and am still paying for this phone. Plus I have an s7 edge and a Huawei honor note 8 all rooted and have never ran into any issues. Why?? Because I never did what people instructions told me not to do. I always follow instructions. I've been rooting phones since I was a milk drinker all the way back to the G1 days. I'm very careful but if instructions don't cover all the basis then what?? PEOPLE, including me should continue to root and try new things. But you can't blame them if YOU(not you in particular but in general) as a developer make something and can't catch all the bugs(it isn't The developers/modders fault either)..Modding is a giant community of trial and error. The only people at fault are idiots who don't read and do some ****. Other than that we are all out here finding our way with these new devices. So yes, I have a new v20 that I paid for with MY "Jump on demand" plan that is now rooted and unlocked. Now am I going to use the Google assistant mod again?? No, because that would be stupid of me. Now get off my post.

I was just warning people so they wouldn't make the same mistake as me.
[LG V20 Guides, News, & Discussion] twistedvip:
Whats the stupid part is how you managed to erase TWRP and lose access to fastboot on your device. Not that your changed something in build.prop. His logic is not flawed, whatever you did to lose access to the two essential parts of having a rooted phone is the flaw here.

Also simply doing build.prop edits should not make you lose access to TWRP nor being able to access fastboot - or did you relock your bootloader?
[LG V20 Guides, News, & Discussion] Damisa-Sarki:
In stead of assuming what happened with my device how about y'all ask me the details first. But coming off the bat assuming that I just did foolishness is asinine.

I was trying to revert to stock with the build prop so I could upgrade my phone. so I edited the prob and removed the lines I added to get Google assistant in the first place but it crashed and when I entered TWRP to push the build prop. When that didn't work I flashed the stock tot file which got my phone working but I wanted to upgrade so I found the page in XDA to flash the kdz with LGup which I was doing but half way through it failed and Twrp was gone which started this snow ball effect.

So once again where's the stupidity on my part when I didn't know that my phone was still going to be labeled a a pixel after a factory reset? Please, both of you have several seats in the back.

All I'm doing is warning people about what could possibly happen. Y'all can miss me with your unnecessary opinions and comments.
[LG V20 Guides, News, & Discussion] twistedvip:
No I appreciate you wanting to warn the community, but you most certainly did not post that story. You posted saying you got bricked from doing edits to your build.prop and then because of using a Google assitant mod you are hard bricked. Post that entire story as a warning because even having your phone appear as a Pixel won't do any harm - but flashing a .kdz and having it fail midway may indeed cause harm. Lack of details causes much misinformation to spread around quickly :)
[LG V20 Guides, News, & Discussion] Damisa-Sarki:
My bad I'll edit it. And apologies for the response tone.
[LG V20 Guides, News, & Discussion] Negan:
It's called taking responsibility. You had a phone with root and did something stupid. Instead of taking responsibility you lie and tell them the phone is defective. That is 100% your fault. I bet it worked fine before you started messing with it. Whatever man I'm gonna let this be but you can bet that when these companies look at the supposed drfrctive returned phones and see they have been tamperred with and that people are being dishonest to get a new phone when they're the sole reason the phone stopped working, eventually they will all say screw it and just lock everything down.

Hopefully you learned from this.
[LG V20 Guides, News, & Discussion] Damisa-Sarki:
Actually the phone had a few random rebootsa and use to freeze on stock. I decided to keep it because of the note 7 fiasco and I was too frustrated and pissed to return it and then they ran out. So this was well over due. But once again you know nothing Jon snow. And yes I did lie but this device already had issues. Soooo???