yashsingh1/xdaforums huggingface dataset:
[Android General] cabbieBot:
holy mother of god this was not an experience I want to relive again. It fried my USB ports like some of the other posters, leaving me unable to control my PC directly. TeamViewer saved my ass, because I was able to remote into it from my laptop and troubleshoot that way. I was havin a hell of a time trying to pry the files out of the /system32/drivers directory because it's sealed up tight as a Caitlyn Jenner's junk. I sent the windows8.1 BAK files to dropbox with the right-click context menu option, and then removed the BAK extension, deleted the windows8 USB files from the folder with the franken-usb. batch file (most awesome soul-selling hacky batch file name ever, btw, i appreciated that, OP), dropped the windows8.1 USB files in their place, then re-ran the batch file, rebooted, and back in business. phew.

That was fun :) Now I'm right back where I started, trying to get my PC to talk to my phone over fastboot. The Microsoft fix posted in this thread didn't work for me either, as it said it wasn't applicable to my machine.
[Android General] abdullah_s5570:
works!

just to confirm that this (the method & files from janek2012) works. However, I had to manually copy those two files in the zipped folder to /system32/drivers. just in case keep a backup of the two files being replaced.

Earlier my S5570 was not being recognized while it was in download/flash mode.. Windows 8.1 was reporting error code 43. After replacing the two files and restarting, the phone was detected. Then I was able to flash my stock rom with Odin.

Thanks :).
[Android General] arefkn:
windows 10

I installed win10 yesterday and facing this problem.
[Android General] radicaldoc:
sorted mine i wasn't in fastboot mode...idiot
[Android General] sausje85:
Yep same here, seems like MS used the old files in Windows 10 (at least, that's my guess)...

Fresh installed showing this issue and upgraded one from 8.0 (that could detect it perfect before the upgrade) showing the same.
[Android General] rafaelbrandao:
Hi,

Tried that on Windows 10 and ended up with a BSOD on boot. Now I'm trying to revert it throught command prompt in recovery. How can I revert to original drivers?

Tried sfc /scanfile and /scannow, it says there is a repair pending upon restart, but when I reboot nothing changes and I still get a BSOD. Also, the usbport.sys.bak and usbhub.sys.bak that should be there as backup seem to have been vanished. When I rename the files it seems that Windows keeps getting it back to the original. :(

Anyone could shed some on light on this, pls?

EDIT: Nevermind, I was dealing with system32 files on the virtual X: drive, that's why I couldnt find backup files and windows "kept" rolling backup. Backup files were correctly placed on my c:\windows\system32. Thank god! :D
[Android General] alamatnitotoy:
i have windows 10 and same issue
[Android General] ErMeglio:
Win10 and exact same issues here: fastboot unusable :(
[Android General] kchaisu:
I used fastboot.reg and it is working for me both Windows 8.1 and still working for me when updated to Windows 10 64 bit as well. Thanks just for info.
[Android General] jwalb99705:
OMFG

HOLY CRAP!!!!! this was so simple and it worked perfectly! I have tried about 10k ways and this is the only one. I hope you dont mind that i spend the rest of the day reposting this to every other FAQ site with this problem to help others. I want to spread it around.
[Android General] petric1:
Not working at all on windows 10 .Whats the holdup with driver making ??Latest windows and flashtool isn't usable at all??
[Android General] kommando:
Win 10 64 bit, all methods did not work except the VVVVPPPPRRRR method which did, bit hard deciphering the ID but mine was also 0BB40FF00100 for a HTC Desire S

Spoke too soon, worked for 30 mins and then stopped being recognised, had to reinstall USB hub drivers as they were corrupted and now when I plug the phone in it shows in Device Manager as a Bluetooth LE UP24.
[Android General] kommando:
Finally got it working using system restore and then applying fastboot.reg and rebooting, but it still wanted to add the Bluetooth UP24 driver everytime and every 3rd or so connection failed until a reboot on the laptop. Eventually got 2 desire S's updated from stock 2.35 to CM11 and both are working well. Windroid Universal was flaky and other than getting the Token ID I had to use fastboot via cmd old school to unlock the boot loader, it was ok for flashing TWRP but could not flash SuperSU.
[Android General] NoobWonder:
What about for Windows 10?
[Android General] shalu awzme:
how we fix in win 10

how we can fix enumeration in windows 10
[Android General] CodeVanya:
wow that Windows Update did the trick!
[Android General] jason xmas:
i f**kin love u ,, have been trying to fix the problem for 6 HOURS !! and then i opened this link ,, THX
[Android General] _/=-)+(-=\_:
Thanks man! Was struggling for hours and this was the only thing that helped in no time!
[Android General] edwinDAP:
please help me

how to restore back like before applying the update ? because my usb can not be used after following the steps above
[Android General] effepas:
I'm facing the same issue in W10 64bit and all the methods I tried did not fixed the problem, even the vvvvpppprrrr one is not working. Some advice? :(
[Android General] kchaisu:
I have been using Fastboot and ADB package on Windows 10, 64bit version on HTC Desire S for a long time. I have noticed that ADB is working on recovery mode: however, FASBOOT on BOOTLOADER mode was not working even FASTBOOT.REG was applied though. Recently, I noticed that I forgot to turn the device on to debugging mode, so after turning on FASTBOOT ON DEBUGGING mode every thing is working fine. There are a lot of issued on the forum even the same problems with different supporting info of which is not sufficient to support the answer. We might expect people to know their supporting info by default, in fact, it is not, so no answer has never been given to their questions. Thanks.
[Android General] Merken_:
Please consider this post : http://xdaforums.com/showpost.php?p=69234983&postcount=6

---------- Post added at 12:51 PM ---------- Previous post was at 12:51 PM ----------

Please consider this post : http://xdaforums.com/showpost.php?p=69234983&postcount=6
[Android General] jayalaba:
Regards![/QUOTE]

After 15 different try, This is the one helped me to get through. Thanks very much for your time and courtesy. God Bless You.

Bala
[Nokia Lumia 920] natividad:
Was it normal for the Nokia Lumia 925 to get hot when playing games?
[Nokia Lumia 920] gee2012:
Off course, when the cpu works at full load heat will build up and the device will feel hot(ter).
[Nokia Lumia 920] natividad:
Many thanks on your feedback.... :)
[Sprint Samsung Galaxy S III] easyrider77:
I installed the nightly cm11 cm-11-20140104-NIGHTLY-d2spr.zip and gapps 4.4, and an ics modem, then rebooted, and all I get is a black screen after the Samsung logo. After that it doesn't go anywhere just stays that way. I can get into recovery again just fine.

Steps I have done are as follows:

Wipe data/factory reset

wipe cache partition

wipe dalvik

Install rom (above zip file)

install pa gapps 4.4

install ICS modem SPH-L710_LI3_Modem

I have tried 3 different types of recovery, CWM touch, CWM normal, and Philz recovery, all three ways result in the same black screen after the Samsung logo.

Someone suggested I needed the MG2 bootloader so I used this rom on this thread http://androidforums.com/boost-mobile-galaxy-s3-all-things-root/758586-odin-backup-sph-l710_mg2.html and got MG2 successfully installed and up and operational.

I thought maybe it was because gapps was giving me issues so I decided to install cm11 without anything else to rule out anything else, and make sure it wasn't the rom itself.....same black screen after the Samsung logo.

I then suspected the recoveries so installed different ones to rule them out, did the steps over again with each recovery, and still same black screen after the Samsung logo.

I am in the process of downloading other KK roms, but until then, does anyone have any ideas what I may have missed or am doing wrong....if anything or perhaps what the cause f this can be and how to fix it?

I've done this what seems a million times on my S2 so it's not like I'm not familiar with the process and how to do things, I just can't seem to get it working on this phone.
[Sprint Samsung Galaxy S III] Whiplashh:
Unless it is a typo, this is the Sprint S3 forum. You are lucky you didn't mess up your phone using our modem. 2nd, if you are on an S3, you need the latest clockworkmod recovery and need to be on md4. I would not take update to MK3, but you can flash the modem and it will work much better. ?

-Whiplashh

Sent from a Premium Xda app using the Flo Nexus 7.
[Sprint Samsung Galaxy S III] easyrider77:
issue resolved.
[Sprint Samsung Galaxy S III] ciaccmo:
What did you do to resolve this issue?
[Galaxy Note 3 Q&A, Help & Troubleshooting] Dimitris Dinozzo:
Hello everyone

last night i have flash for first time on my NOTE 3 SM-N9005 a custom kernel named (leanKernel: minimalistic kernel v1.8)

now on any boot i see a red message (kernel is not seandroid enforcing) but my phone work normal :silly: ..

now to my question ...what does this warning (kernel is not seandroid enforcing) ?

i see this for the first time ..
[Galaxy Note 3 Q&A, Help & Troubleshooting] radicalisto:
The kernel isn't signed by Samsung is all, it's normal and no need to worry.
[Galaxy Note 3 Q&A, Help & Troubleshooting] Dimitris Dinozzo:
Thank you for your fast and simple answer:laugh::good:
[Galaxy Note 3 Q&A, Help & Troubleshooting] Armazia:
I got the same thing here. But when you go back to an official kernel, will the notification be gone?
[Galaxy Note 3 Q&A, Help & Troubleshooting] ultramag69:
Yes, but Knox will still be 0x1...
[Galaxy Note 3 Q&A, Help & Troubleshooting] Armazia:
Knew that. but I was wondering about that notification.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] arieltools:
I'm having the same problem for a week now...

I was on the street with my BA making calls and all went Ok. I use it for my work, so I do lots of calls a day. Suddenly, I realized, when I call, that the other can not hear me, nor can I hear them! The counter is running, the screen says "Connected". I haven't done anything to change the configuration, nor it have dropped it from my pocket.

I'¡m getting crazy. I don't know what I've done wrong.

Things tried unsuccessfully: Crying or Very sad

-Lots of device resets..... Between tryes and Updates.

- Reinstalled WM5 using a different ROM. Now I have TM 1.3. [http://xdaforums.com/viewtopic.php?t=42632]

- Upgraded Radio to 1.15 (previously, I had 1.13)

- Used a Bluetooth headset. It worked, I could hear the sound from the phone, at least. Only thru the bluetooth headphone. Still, I could not hear any phone-sound from the loudspeaker when I turned off the headphone and the bluetooth headset were disabled, even with the Bluetooth signal ON, as suggested on other post. Each try with a new call. The weird thing is that I CAN hear the loudspeaker when I hear music or the system sounds... :?

- "Installed" the Unidirectional patch (copied the AudioGW.dll file over the old one successfully, reset, etc..)

- Turned off the device and leave it off for a while. Take off the SIM card, touch it (cosmic vibrations Embarassed) Sometimes, before, the SIM card went a little nuts if I resetted the device too much -maybe Confused- or if I got the battery off...

- Last, I've downgraded :( to the latest WM2003 ROM. Formatted the Storage Space and resseted the Registry Hive. No change. All else is working.

My options are finishing :oops:....

Sorry if this has been posted before, but, at this point, when I've been tried almost (I think) everything, i couldn't find anything relevant using search.

Please, any help will be greatly appreciated!!! Maybe I can use at least a link to another thread..

Thanks
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] indra9110:
try downgrade your RADIO to 1.13
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] arieltools:
I've allready upgraded to 1.15 because of this problem. Anyway, I've downgraded just now and nothing:( same problem..... also: I can not get the handsfree-loudspeaker mode (pressing the "call" button for a while). Just nothing happens

Let's hope mamaich or other cracks read this post :(

Thanks for ur answer

HEEEEEEEEEEEEEEEELPPPPPPPPPPPPPPPP :(((
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] indra9110:
ow... DONT PANIC !!! try flashing once again ... including ROM & RADIO
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] arieltools:
Rom & Radio flashed again. At no avail :(

I've used, lastly, the "standard" Rom posted on I-mate website (www.clubimate.com) [ROM: 1.40.00 WWE; Radio: 1.12.00; Protocol: 1337.42], just to checkout and everything (regarding this problem) remains the same.

I've, however, noticed that, before, when I used the volume slider up, first the PDA-volume went up, later the phone-volume. Now it only fully moves up the PDA-volume. I think this have something to do...

Again: Please, help me!!!

Thanks for your answer!!
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] arieltools:
Still the same after 3 flashing sessions :( :( :(

Two days ago, I've sent an e-mail to I-Mate. They have answered me yesterday telling me to hard-reset :?:evil: and if that doesn't work, to send the device to France or Portugal for fixing. Here on Spain there's no place where to send it.

I think it should be a software problem (maybe) that's why I'm asking help here.. Also, the problem with the volume slider up only occurs on W2003, not on WM5

What should I do?? :oops:

Anyone?? HELLOO?
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] arran83:
i've had this problem for a long time, and tried so many different patches non worked, but there is a way to deal with this issue u need to keep ur bluetooth on all da time or remove the file BTTrayCE from this directory

Mydevice>windows>start up

and copy this file to ur storage card if later u want to use ur Bluetooth so wat removing of this file does is that the icon in of bluetooth in tray bar will not appear automatically after u restart ur machine .

hope this helps
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] arieltools:
At no avail :(, but many thanks anyway.

I've seen this solution on other posts and I've tried it before. Without luck :(

Even the 'bluetooth on all the time' alternative. Without luck :(

Also, I'm now on TuMa 1.3 (WM5). The file relative to bluetooth on the startup folder is "BTIcon", wich I have moved as you stated. Without luck :(

Maybe the file you tell is for WM2003 ?? Could it be? Is the file named 'BTTrayCE' on WM2003 and 'BTIcon' on WM5?

I'm really desperate.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] arran83:
umm yeah i'm sorry, mine is running WM2003, maybe u should try downgrading to 2003 as well since i've done it and now i'm having less problems, i really don see much of advantage in using 2005, good luck.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] arran83:
ok here is a patch that is supposed to fix this problem but hasn't worked on mine, i just attach it here it might work on urs, or u might already have used it.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] deepakr:
Sometime back, I had come across a post on a similar problem. I think what you have is a erratic headphone jack..I believe there is a micro (?)switch in there which connects headset and disconnects speakerphone.

I had a similar problem sometime back, and just put the headphone jack in there, jiggled it a bit and it started working. basically released the switch. your symptoms point to a similar problem...does not have anything to do with Radio ROM. Has not given me problem since then
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] deepakr:
here you go..

http://xdaforums.com/viewtopic.php?t=33207
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] arieltools:
Yup, I've seen this forum before. If it has to do with a headphone problem, then It shouldn't be heard anytime, and I CAN hear music and such from the device when it isn't in a call. Anytime I put the device on the "call" state (dialing, connected, hold, etc..) the sound goes out. :-S

So, it should not be a headphones problem.... should it??
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] arieltools:
Yes, I will, for nth time... No solution yet... I will apply the Unidirectional patch again on WM2003 to see... Keep you posted..

:cry:
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] arieltools:
OK, I've tried, for nth time, going back to WM2003SE (112 T-Mobile) and applying the unidirectional patch I've found here (I think is the same posted on the I-mate site I've tested before) and NOTHING changes...

Still the same problem.

Any clues? :oops:
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] matrix70:
hi !

try like me... in bt setting-->accessibility-->disable all access options..

to me this little trick cut off every problems on use the phone....

hi
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] arieltools:
OK, I'll give a try :? (Again going to WM2003, as I think is that what you have right?)
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] pjax:
No Sound on BA

Hi there. Have pda2k, rom-1.40.00, radio-1.12.00. Have previously lost sound during call. Can be heard but cannot hear. Phone have been exchanged under warrantee, but new phone developed same problem after using BT to connect with PC. Currently I turn on the speakerphone in order to converse. Any help?
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] arieltools:
Re: No Sound on BA

I can not turn on the speakerpone.....
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] Yol:
I also have a similar problem - when in phone mode, other side can hear me but i cannot hear them, if i plug a headset with microphone the other side hear me and i also have sound from other side.

if i unplug the headset, i cannot hear the other side but the other side can hear me.

are there microswitches inside the headset plug for both microphone and speaker (two microswitches) ?

thanks, yol.
[Galaxy S II Q&A, Help & Troubleshooting] SuperDooperTrooper:
Hi Everyone,

I am new to this forum, and since I kept coming back here (Thanks to QBKing77 for all his helpful videos on youtube), I decided to create an account because I needed some help.

I was endlessly searching reading posts over and over again before updating my Galaxy S2 to the new Android release, and just when I was about to give up because I was so frustrated, it somehow magically worked. I was able to get my phone update to the new Android 4.4 ICS release ( I think). I can't really find any help on how to identify which is Gingerbread and which is ICS.

Anyway, the whole reason I am here is that I need help trying to re-configure my phone to the Boost Mobile network. I thought I could do that through the APN settings, but for some reason it did not work. My phone still seems to think that it is on the Sprint Network. Does anybody know how to reset the settings to the Boost Mobile Network or is there a Boost Mobile Android 4.4 ROM Download?

Attached is a picture I took showing the Version and Kernel.
[Galaxy Note 3 General] mongoose3800:
I am posting this as it is very hard to wade through information in forums. I'm hoping the following will be useful to those, who like me, experienced battery drain caused by Android Wake Locks after upgrading to MJ7 / MK2.

I am 100% certain the battery drain in MJ7/MK2 is caused by connecting to WIFI networks in environments that have multiple AP's. i.e. once WIFI roams from one AP to another the battery drain starts. All my testing confirms this - consistently. I have actually tested being connected to one AP in a multiple AP environment for a long period and observed no wake locks on Android OS. Yet as soon I move to another location (i.e when I make it roam) the wake lock and battery drain starts. All this rubbish about clearing cache, factory resetting, nobbling your phone and so on are all stabs in the dark - It's the reboot that temporarily fixes it so people mistakenly put two and two together. So, if you use WIFI in a large building with multiple AP's try forgetting the network and not connecting to WIFI with multiple AP's. If you have already connected to a SSID with multiple AP's reboot your phone because once the battery drain starts it does not seem to stop until you reboot. You don't have to disable WIFI at all as scanning does not cause the wake lock. I have tested this thoroughly and so far I have not had any battery drain since not connecting to SSIDs with multiple APs. I can also back this up as I can create battery drain at will by simply connecting to a WIFI environment with an SSID distributed over multiple AD's.

My battery life is again fantastic and I am happy now that I know the cause.

Pretty poor testing by Samsung/Google as I see in past versions of Android Roaming has been an issue.
[Galaxy Note 3 General] stanley08:
Funny thing is that when i am using mobile data the drain is worse, So I'm pretty sure this is not the main issue man. Also, I have a Mobile 'WiFi' router. Only me has WiFi connection in my entire hostel. So I don't really think it's the issue. Good finds tho! It will definitely help someone. Cheers! :)
[Galaxy Note 3 General] vndnguyen:
Agree with stanley, this is not the only cause.
[Galaxy Note 3 General] mongoose3800:
39089665568

Agreed. There are many things that will cause elevated use. But Im talking the rapid drain that occurs when you're not using the phone. Ever since taking the action I describbed my battery life has been excellent. Eg 94% after 14 odd hours with no use. And, I'm still connecting to my home wifi. Beforehand it could be below 60% with no use and this is the real problem people are talking about. Hope that makes sense.
[Galaxy Note 3 General] aydc:
Actually it's the opposite. If you set up your modem to have a separate AP for the phone and isolate it from the rest of the network, you'll have much better battery life on wifi because you'll stop your phone from waking up by broadcast packets.
[Galaxy Note 3 General] Nazty111:
I don't get it. What am I supposed to do exactly? :confused::confused:
[Galaxy Note 3 General] PlutoDelic:
What about unicast traffic? i know the Client Isolation sort of "VLAN"s every client associated, just wondering if that might affect client to client communication?

Good point btw, im also wondering how many services wake the damn thing up, waking up over network is more an enterprise workstation scenario...to me it sounds like HotSpot 2.0 services being active, but i have not enabled it.

HS2.0 can let client and AP sort of talk without associating.
[Galaxy Note 3 General] aydc:
Most modems have a sort of 'guest mode' or allow you to open another access point and isolate it from the rest of the network. If you connect your phone to this guest access point or isolated access point, your phone will reach internet without problems, but will not reach the local network through the router. Nor will any other device on the network reach your phone.

Most of the problems with Wifi draining battery, like wifi wakelocks, occurs because devices on the network keep sending packets to the phone waking it up. With the method I describe above, you will isolate your phone and the phone will remain in deep sleep, significantly increasing battery life.