yashsingh1/xdaforums huggingface dataset:
[Pixel C Q&A, Help & Troubleshooting] fgaine:
First, bit of background: I am not an Android developer or even a computer geek in any way but I can follow precise instructions to a positive result. I have for instance had in the past the following devices and managed to root every single one of them sometimes in 10 minutes, sometimes with a lot more difficulty: B&N Nook, Samsung Galaxy SII, Nexus 5, Nexus 7, Nexus 9, Sony Xperia Z3 Compact, Chuwi Hi10 Pro.

Now, I have just purchased a Pixel C and I have been tearing my hair out for the best part of 48 hours just trying to install the Google USB driver and fastboot bootloader driver on it. I previously had my Windows 10 PC set up with working ADB and fastboot (sdk tools only, no Android Strudio). As proof, I recently rooted my Nexus 9 on it. With the Pixel C I tried:

-Nexus root toolkit and every single method of driver installation possible

-I then downloaded Android studio - didn't change a thing

-I then try to unlock the bootloader the manual way (command prompt inside of platform-tools - fail since the driver won't install.)

-I even wiped out my Windows install and reinstalled it fresh with Android Strudio

- I do get the device seen as an mtp device

-I do get adb function (I can reboot the device to bootloader)

-Yes I did enable usb debug and 'oem bootloader unlock'

-when I try to install te Google driver to the tablet as mtp device in Device Manager I get the message "the best driver is already installed" (no matter what Google usb driver I use, the one downloaded by Android Studio or the one I downloaded separately)

-I have also always disabled driver signature enforcement in Windows before trying to update the driver.

I am extremely puzzled and feeling defeated. If someone can tell me of something that passed me by, please tell me. If the Pixel C can be rooted on a Windows 10 PC, please tell me something I don't know...

Please note: I made the possibly mistake of letting the Pixel C update to 7.1.2 before doing anything.

Please Help!
[Pixel C Q&A, Help & Troubleshooting] badwiring:
This may or may not be a helpful response. I had the same problem and never, ever solved it. I read a gazillion articles and all sorts of detailed instructions about how to remove and update drivers. I tried for days and nothing ever worked. That's not to say that it can't be done, but I had to give up.

Do you have access to a Windows 7 computer? That will get you through the unlocking process and initial installation of TWRP. After that you won't need your PC for anything except transferring files so the drivers won't be a big issue.
[Pixel C Q&A, Help & Troubleshooting] fgaine:
Thanks, so it would be a problem with Windows 10? And you manage to solve it with Win7?

I don't have a Windows 7 PC but I tried to run a Win7 virtual machine, and it can't recognise the tablet as an mtp device. So, fail.

I can't believe we're the only 2 who've had that issue and that this is not generating more help and tips. Nevermind...
[Pixel C Q&A, Help & Troubleshooting] kjwaugh:
Try the skipsoft tool kit thread.

I am not an expert, but the thread offers many insights into this problem. I got the drivers installed properly after some thorough failure too. Keep at it. I did it successfully about 9 months ago - long enough for me to completely forget how I did it. The answer will be there.
[Pixel C Q&A, Help & Troubleshooting] dkryder:
nexus root toolkit by wugfresh supports pixel c. good info on drivers found there.
[Pixel C Q&A, Help & Troubleshooting] chinimen:
https://www.vichaunter.org/como-se-hace/instalar-controladores-no-firmados-windows-10

Enviado desde mi SM-N9005 mediante Tapatalk
[Pixel C Q&A, Help & Troubleshooting] fgaine:
Hi. Thanks. I have been reading about the issue across the Internet for 3 days now and keep seeing the same instructions which lead nowhere...
[Pixel C Q&A, Help & Troubleshooting] fgaine:
As said in the original post, I used (and always have) the Nexus root toolkit. I also tried every single driver installation method in it and out of it - several times each...
[Pixel C Q&A, Help & Troubleshooting] fgaine:
Thanks. Although my Spanish is no longer that good I believe it instructs how to disable driver signature in Windows. As I specified in my original post, I have done that.
[Pixel C Q&A, Help & Troubleshooting] chinimen:
Ok then you only have to install the drivers manually with the nexus root toolkit

Enviado desde mi SM-N9005 mediante Tapatalk
[Pixel C Q&A, Help & Troubleshooting] dkryder:
have you tried the legacy drivers install?
[Pixel C Q&A, Help & Troubleshooting] fgaine:
That's one of the very first things I did, mate If you have read my post. ,?
[Pixel C Q&A, Help & Troubleshooting] chinimen:
First you have to disable the use of unsigned drivers as indicated and then install the drivers manually from nexus root toolkit. If you read your message and I did it in that order. a greeting

Enviado desde mi SM-N9005 mediante Tapatalk
[Pixel C Q&A, Help & Troubleshooting] fgaine:
Hi. I didn't know about the Skipsdoft toolkit. Sounds good, I will give that a go. :good:
[Pixel C Q&A, Help & Troubleshooting] fgaine:
Is that using the NRT?..
[Pixel C Q&A, Help & Troubleshooting] fgaine:
Thanks again. But that's what I did. Didn't work...
[Pixel C Q&A, Help & Troubleshooting] tim.malone:
I always have this problem, and it always comes down to me forgetting that the device needs a different driver in ADB mode than it does in fastboot mode. Or, at least, it needs the driver installed in each mode. If you haven't already, make sure you get it working in ADB, then go through the steps again while the device is in fastboot mode. Maybe you've already made sure of that, but the last time I needed to do it, after hours of pulling out my hair, I realized that I wasn't doing all the steps of removing drivers and then installing the correct ones while the Pixel was in fastboot.
[Pixel C Q&A, Help & Troubleshooting] dkryder:
when using device manager , left click on action then select add legacy hardware, then next, then install hardware i manually select from a list, then next, hopefully android device is at top of list, if not look for any adb/fastboot , like portable device but the point is to find a adb/fastboot early legacy device and select that, then next, then select the driver from the list and hit next. should be done.

let me ask you when you installed android studio, did you go to sdk manager and select usb drivers then install. then go to users/username/appdata/local/android/sdk/extras/google/usb_driver and right click .inf file and select install and let windows install the driver(s)?
[Pixel C Q&A, Help & Troubleshooting] fgaine:
Hi. Yes I did but it keeps saying there are no suitable drivers in the folder. When I check myself there is indeed no .inf file in it.
[Pixel C Q&A, Help & Troubleshooting] choder:
I have had no luck. Using both the skipsoft and the wugfresh tool.

My pixel c is locked asking for a pin and I never put a pin lock into it. What a piece of $h!t this tablet has been.
[Pixel C Q&A, Help & Troubleshooting] dkryder:
i would bring up sdkmanager and see if usb drivers box is checked. if it is , uncheck it and see if it uninstalls, then re-install by checking it again. if unchecked, then check it to install drivers. it seems that the drivers were never installed by sdkmanager. because windows is not finding them when you right click install. so you might also try some 3rd party adb/fastboot driver packages.
[Pixel C Q&A, Help & Troubleshooting] fgaine:
Thanks dkryder. I followed your instructions. However I was wrong, the Google USB .inf driver had been there in the right folder all the time. I can't understand why Windows won't install it, even with driver signature disabled. Puzzles me...
[Pixel C Q&A, Help & Troubleshooting] dkryder:
there are a few 3rd party adb/fastboot packages for windows machines & google has a separate package also. this is from xda earlier this year.

https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads/

i'd take anything/everything approach at this point. you could also try a live linux cd to boot to a linux o/s and work from there. also read this,

https://developer.android.com/studio/run/oem-usb.html#InstallingDriver

https://developer.android.com/studio/run/win-usb.html
[Pixel C Q&A, Help & Troubleshooting] choder:
I was able to boot into stock recovery and reset the device. Then booted the device and used a Windows 7 machine along with http://www.wugfresh.com/ tool kit to install the drivers. Now Oreo is installed, so its time to sell this piece of junk.
[Pixel C Q&A, Help & Troubleshooting] jatilq:
I'm on a mac and also installed win10 for this purpose. I'm not sure if this would work, but have you tried to use a Linux live disk/usb to test it. I never needed drivers for the Macbook Pro, I think *nix doesn't need them.
[Pixel C Q&A, Help & Troubleshooting] fgaine:
I haven't used Linux for many years and I've never done rooting in it so it would be a steep learning curve. But it might be the way to go as my tablet is still not rooted after over a week!..
[Pixel C Q&A, Help & Troubleshooting] jatilq:
Since you're on a Mac, you shouldn't have to install Linux. Your laptop should see the device without drivers. Just Download platform-tools (adb and fastboot)
[Pixel C Q&A, Help & Troubleshooting] wintermute000:
FWIW this works for me guys.

1.) Go to the android SDK download page - https://developer.android.com/studio

2.) Download the CLI tools only - sdk-tools-windows-3859397.zip

3.) Unzip

4.) go to the /tools/bin folder and run sdk-manager --list. You should see the google USB driver listed as extras;google;usb_driver

5.) run sdk-manager "extras;google;usb_driver" to install the driver. THIS DOES NOT ACTUALLY INSTALL ANYTHING - it just downloads it to the /extras folder.

6.) put your device into fastboot mode.

7.) Go to device manager, find the unknown device. Update the driver manually and point to the INF file in the extras folder that sdk-manager just downloaded.

FWIW minimal ADB drivers etc and a bunch of other all-in-one type of packages didn't work for fastboot (only ADB), but the above worked for fastboot.

Its faintly ridiculous that its this difficult AND not really documented for a power-user (maybe its somewhere in the dev doco)
[Pixel C Q&A, Help & Troubleshooting] bjveee:
Google USB Driver still won't take

I installed the full Android Studio and know I have the latest "android_winusb.inf" file. I admit I was at a loss how to run "sdk-manager --list" I did attempt to run the sdk-manager --list in a command line terminal and it choked on it. I transplanted the "android_winusb.inf" file into the Wugfresh Development kit data\drivers\Drivers_Google folder and attempted to get it recognized while in fastboot mode. The browse my computer only shows me the amd64 and i386 files. I know I placed the "android_winusb.inf" file in the Drivers_Google file but it is still not recognized. By the way the Windows 10 is setup to accept unsigned drivers already. I have TWRP 3.1.1 still installed and all my problems started when I decided to update from RR-N-v5.8.3-20170623-dragon-Official\. I attempted to just flash RR-O-V6.1.0-20180611-dragon-Unofficial\. I flashed the updated opengapps for June and flashed supersu-v2.82. I then flashed the June 2018 vendor image from the still functioning TWRP. I immediately got a successful sequence and then it came back with something or other was corrupted and I needed to send it back to Google to fix it. Is it possible to sideload a new signed version of one of the OTA images with a flash.all which will wipe my TWRP recovery with just the ADB driver alone. Know matter what I do I just cannot get it to install a updated Google fastboot driver. I can get it to a successful ADB response with a serial number. I don't know what I did but Google knows I was messing with their system and seem to have locked me out. I still have a fully functioning TWRP that I can load anything on a thumb drive and install using the usb-otg. I really hate to flash.all and loose my TWRP root. Help!!! I just about can't function without my Pixel C tablet and consider all others sub-standard. I simply have a brain fart everytime I pick up a Apple tablet! The Samsung S3 is sub-standard to me. I'm really sure I'm not hosed to the point of no return on the Pixel C tablet. Help!!!!!!!!!!!
[Pixel C Q&A, Help & Troubleshooting] hawkjm73:
If you haven't already chucked your pixel for something else, you might try running adb and fastboot from another Android. Xda has the files compiled for Android, or you can grab the systemless module for Magisk. Then just connect with an otg cable and run the commands from a terminal app. No drivers, no mess. You might need to select "transfer files" from the USB notification.
[Pixel C Q&A, Help & Troubleshooting] bjveee:
Windows drivers still being impossible! Linux fixed it all!

Thank you for your response and effort! I know people tend not to respond to Junior members questions. Can be a black hole to help sometimes. I understand most things have to be self taught primarily but it does help when someone makes an effort.

I've got the Pixel C updated to July with the Resurrection Remix Rom and Magisk. I found BusyBox did not work with supersu and I was forced to beat the Magisk bootloop problem to death. When they say reflash the stock boot.img after moding it with Magisk, it still didn't work! I went to bed and dreamt up the solution literally. They don't mean the "stock" Google boot.img. They mean the "stock" RR boot.img. I flashed TWRP. Installed RR rom zip, gapps zip, and then rebooted back to the TWRP recovery ONLY. NOT the RR system yet. At that point you have the stock RR boot.img in place. At that point I installed Magisk.zip with TWRP and then finally rebooted into the system rom. Everything worked simple as you please. Oh I forgot to mention it worked as long as I was installing all the zips from a usb-otg thumb drive. I had problems if I attempted to place anything on the internal data partition before it was finally rooted with Magisk. I probably sh flash-all.sh installed the Google stock July image ten times before I dreamed up the "stock" RR was what I needed!

Now I'm trying to puzzle out if I have any use for toybox in place of busybox. So far I haven't found a NEED for it. I instictively WANT a busybox/toybox. I don't know why yet.

And yes I still have a problem with all my other android devices on Windows. I'm not sure I even want to mess with it anymore. I don't play games. My only attraction is just solving the technical problems. I have enough fun with those on the linux distros and I seem to solve those with a whole lot more support material out there.

Thanx again for your response!
[Pixel C Q&A, Help & Troubleshooting] hawkjm73:
Hey, glad to help. This tablet has been such a beautiful albatross, I'd hate for it to get lost in software purgatory. Knowledge written is knowledge remembered.

Yeah, Windows as been frustrating as all get out lately. It's near impossible to track down the "why" when something is wonky. Mine sits on my desk just to play games that want a mouse and keyboard.

In future, note you can pull the individual images out of the factory package. Unzip the zip inside the zip, and you should get boot, recovery, system, cache, and vendor images. (For the pixel c, anyway. Other devices may have a somewhat different set.) You can individually flash these as "fastboot flash boot boot.img" and similar. Also, you can pull the "-w" out of the bat and sh flash-all files to flash without wiping data. Only useful if you are on stock, but good to have handy.

There is a BusyBox Magisk module, but I haven't found anything on Android that needed it for quite some time.
[Pixel C Q&A, Help & Troubleshooting] jontseng:
For the record (and I don't know if its still relevant) I was trying to do the whole unlock bootloader thing today (guess as we aren't getting pie may as well jump). This device had never been messed around with before so was completely stock 8.1 /w official updates. Obviously ran into the same issue - can't get USB drivers that work with my Windows 10 box.

What worked for me (no guarantees!)

1) Install Nexus root toolkit.

2) Reboot windows into troubleshooting mode with "Disable driver signature enforcement" mode on.

3) Attach Pixel C booted into fastboot (I think - whichever mode makes it show up as unknown usb device in device mgr).

4) Go to device manager, update drivers on the device. Point to the Nexus root toolkit directory.

No idea if this will work for others, but FYI.

I was using driver signature disabled bc when I tried to update under normal windows it was giving me INF not found.

Disclaimer: I am a complete script kiddie. Haven't used a CLI in vengeance since DOS 6.0.

J
[Pixel C Q&A, Help & Troubleshooting] Everio9000:
It works for me. Finally I got Fastboot in my Pixel C. Thank you so much.
[Pixel C Q&A, Help & Troubleshooting] HolyChickenGuy:
Hey guys big relieve here because i was able to install the drivers within 30 seconds :P

just download the winb usb drivers from google,

extract the zip to somewhere you can find it back

boot the pixel c to fastboot mode

connect the pixel c to the pc

open device manager

find the device with the yellow triangle

right click > update driver > browse my pc > let me pick > have a disk > locate the folder and open the win usb file > next > bootloader interface > install

Done!
[Pixel C Q&A, Help & Troubleshooting] mortysantiago:
Holy HotChickenGuy that worked. After a couple hours of failing, this worked. Thanks.
[Pixel C Q&A, Help & Troubleshooting] SamuelAt:
Thank you! Thank you:-) Dude you the man! I could not install Google's drivers because the phone was in file transfer configuration for usb. Once I logged into bootloader ( i.e. fastboot mode ) I was able to install the driver. I am so happy:-)
[AT&T Samsung Galaxy S8+ Guides, News, & Discussion] tserv95:
Just a heads up guys Root is out for the S8+ and the S8 on all carriers in the USA! Head over to the main forums and check it out. Figured I'd post this here to give people some guidance before this possibly gets patched up.
[AT&T Samsung Galaxy S8+ Guides, News, & Discussion] b0Ne83:
Is this a permanent root with no issues?
[AT&T Samsung Galaxy S8+ Guides, News, & Discussion] Raz12:
everyone either already knows this already or our AT&T section is just dead lol.
[Galaxy A3, A5, A7, A8, A9 Q&A, Help & Troubleshoot] Hami00:
Hi!

I was not aware of this issue before I rooted my Galaxy A5 2016. Android 7.0

To unroot it Ii install the latest firmware using Kies but after that I wasn't able to use Knox.

It shows this error when I try to open Knox

"My Knox cannot be installed because unauthorized software has been installed on your device."

Please help me to fix this...
[Galaxy A3, A5, A7, A8, A9 Q&A, Help & Troubleshoot] PJng89:
No way to return back.
[LG V20 Questions & Answers] PakRatJR:
Original post was moved. Sorry.
[Wing, P4350 Herald Upgrading] merddyn:
Have been reading all the forums and had used the info here to put a custom ROM on my T-Mobile Wing. Unfortunately my Wing is now suffering a hardware problem and has to go back for a warranty replacement. This could obviously be a problem if it has a non-standard ROM on it. Because of this, I went ahead and grabbed the RUU_Atlas_TMO_US_4[1].10.531.3_4.1.13.37_02.83.90_Ship.exe file via the threads and attempted to reflash my phone.

I am running the flash attempt from a physical Windows XP system. My phone is fully charged. I have an active partnership set up with the phone and active via ActiveSync. I start the flash process and the phone reboots into bootloader mode as expected. The flash process gets to 1% then the phone reboots into regular mode again and the RUU reports that the flash failed.

Am I missing something?

Update: apparently I was missing something. I had read the thread indicating the phone reboots at 1% and 30% (though mine only rebooted at 1%), but I assumed it would go back into the boot loader automatically which it didn't. On a hunch I tried forcing it into the boot loader and the RUU continued. Weird.
[Wing, P4350 Herald Upgrading] ivanmmj:
Have you HardSPLed your phone before? If you have, you have to bypass the SPL... Rumor goes, flashing the stock RUU WITH USPL will do this for you. I haven't tried it so I don't know if this will work or brick the device.
[Wing, P4350 Herald Upgrading] R_phAn:
I had my phone picked up for warranty this very day. It was running Itje's latest ROM before the 6.1 update, but it totally died on my the other day. So now I'm hoping they won't mind too much about the hard-spl ing and the flashing and the overclocking *cough*

Good luck restoring your phone though. Maybe they won't care, I'm hoping for that :P
[Wing, P4350 Herald Upgrading] DaMyth:
I basically took ivanmmj's advice and wrote a lil guide, I hope it gets sticky'd. http://xdaforums.com/showthread.php?t=364543
[Wing, P4350 Herald Upgrading] ivanmmj:
Glad to hear it worked. ^_^ I think that's the second account I hear of it working, so it must be something that DOES work.
[Wing, P4350 Herald Upgrading] wshader:
Not to raise the dead but good thing I found this thread, worked or me too. Anyone know anything about the warranty replacements tmobile sends out? I'm assuming a refurbished model but anyone know the type o condition they are in?
[Wing, P4350 Herald Upgrading] ivanmmj:
The model that I got as a replacement, oh so long ago, has been working like a champ since I got it. It looked brand new, but then again, the original had problems not too long after I first got it, when the Wing was still a pretty new device.
[Wing, P4350 Herald Upgrading] wshader:
Thats good to know, should only have to last me a month or two seeing how tmobile in their infinate wisdom lost the cell tower near my house a few months ago and contract is done on the 29th.... hello tilt!! (or touch pro :))
[General Questions and Answers] edo101:
How do I move my album art, screenshots, downloads to SD card automatically.

I kow how to change my storage settings for videos and pics to my sd card but not the native stuff that are automatically moved to the phones internal storage

My phone is running low on storage and some of it has to do with my media files. How do ensure that whenever i do something like take a screenshot, it will be saved on my microsd card as opposed to internal phone storage

I have a Note Edge(Note 4 essentially)
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Kill-Switch:
Hello Xda today i'd like to present Note8 Ported apps :)​

So shall we begin ??

1. Clock

https://mega.nz/#!CNdTVZpJ!vKJqAqCFeOVFK6uyQ4SHXzg1LFeVPUxW3zn4FHd1b8A

2. TouchWiz Launcher

https://mega.nz/#!vAlGwaSC!OYemYS1Ug7osp0n0aTkN3KhK6nllZNT5Y5nJAHsJprM

3. Device Manager

https://mega.nz/#!GcEBmDSa!l2Fkd5igA5aDGttkVwqLH2EusN_h7ffoDY78PzfmMxg

4. Weather

https://mega.nz/#!rMEmhaRJ!Nl5SbzNHfUOfP3DdPgKeAOwhKY5CyNwBl3kl1KIB8rw

5. LIve Draw

https://mega.nz/#!2BVlQD4K!J04e-8SOnz028n3V83GZOrDCE0Z-VZHjRr8CGNG3GZ0

You need to install N8 Keyboard by alexis from this thread.

https://xdaforums.com/galaxy-s8/sam...s-device-development/note8-apps-port-t3662555

6. Gallery

https://mega.nz/#!bRtQjb7B!hJQLFjeR3k4vjom20T8uq1YcfAAg9e9KycKB68Cb_z0

7. My Files

https://mega.nz/#!PBdHBRyK!Jfkwi3KHZaXFrdCI8-q08xZAfMiMslrbuklXEO5vxLw

More are coming :)

Credits :

[MENTION=3026895]DaOldMan[/MENTION]

[MENTION=4637718]ananjaser1211[/MENTION]

[MENTION=276902]whoever[/MENTION] got us that dump :)
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] aboraide.alhareeze:
Thank you .. Great work
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Hassan_Ezzo:
With my best wishes

أرسلت من SM-G935F بإستخدام تاباتلك
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] brahma666:
Will it work on note 3?
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Kill-Switch:
No it wont work because note3 is MM and these apps require Nougat to work.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] brahma666:
You're right, I did not think [emoji4]
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] DaOldMan:
Great job my friend !

I am waiting for some ports of those apps to mm :)