Search the Community
Showing results for tags 'Android'.
What happened - too much data got deleted during system cleanup Target Model - Xiaomi Redmi 6a, official ROM, no root data stored on internal memory We are aiming at recovering WhatsApp message history, but other data would be cool too. Since the phone is not mine, I cannot promise data will not get overwriten, but I told multiple times to resist from browsing web, facebook etc. I tried Googling out, but none of the websites I checked seemed not worth too much trust... There are some pieces of software told to be capable of solving my prob, but what I need is probably a recommendation from trusted source, best backed with personal experience...
Hello all, this is something that has been making my mind boggle. As you fellow forum members certainly know, Android has been giving its versions codenames starting from Cupcake upto Pie. And as you may have noticed, Android 10 was not given the name of any confectionery item. My opinion on this is: Android 10 should have been given a name of Android Q- for Qubani-ka-Meetha (it's a popular Indian sweet made of apricots, wiki page will be linked here). How many of you fellow MSFN members share my opinion and agree with what I say? Please let me know your opinion about this. https://en.wikipedia.org/wiki/Qubani-ka-Meetha
Good News ! http://blog.livedoor.jp/blackwingcat/archives/1918790.html I tried USB tethering with iPad mini 4. http://blog.livedoor.jp/blackwingcat/archives/1918650.html I tried USB tethering with Nexus 5X. It requires RNDIS Driver for Windows 2000.
I found this, which isn't really universal since it defines a bunch of specific device IDs to identify them and is outdated anyway. There's also this pull request posted on that project's GitHub page and also another repo containing a dead link to already singed driver (or more precisely, signed INF that identifies ADB interface by the universal compatible ID). So what are my options? Anyone found such a driver/INF that can be just installed and forgotten about or do I have to go the signing the modified android_winusb.inf with self-signed certificate route if I don't want to disable driver signature enforcement and such? So far, my phone has used like 6 different device IDs to identify itself and under certain circumstances, I even have to re-install the official driver/INF for it to work again and confirming that I do want it installed, even if device ID doesn't match. Windows should really have universal ADB driver at this point, like it does for USB mass storage devices...