Hey guys. I have a Wifi-only 32GB Dell Venue 8 Pro. I had a problem where anytime the camera was opened, the tablet would BSOD. After some research I determined that there was a problem with the then-new chipset drivers. I downloaded the old one and all was fine again. Later, it self-updates to the latest faulty drivers. I again install old drivers, but by mistake I installed the wrong chipset's drivers. Now I BSOD on boot, every single time. How can I fix this? I've tried safe mode (which doesn't let me install the correct drivers), and other things. I had previously stupidly deleted the recovery partition to save space, and now I am at a loss on what to do. I'm thinking that what is needed is a recovery disk image from a USB flashdrive, but I do not have one. Where could I get one?
Alright well I seem to have finally fixed my own problem. I disabled the Processor controllers and other components marked with a warning sign from Safe Mode in the device manager. Had to use a mouse and use some creativity to open the control panel. One of them was causing the BSOD.
The tablet would then boot into Windows, so I went back to the UEFI settings and reset it to default settings. This enabled Wi-Fi. I was then able to slowly go back and update driver software from dell's website. It's all good now, and I'm downloading Windows 10074. I bricked it back in January so it was stuck in 9926.
Related
Hi,
I'm having some issues where the MTP driver fails to load. Tried all the obvious stuff and did a lot of reading of forums and stuff but can't find a fix. Could anyone help me to fix it please?
Here's what hardware I have and what I've tried so far:
Tab Pro 8.4 16gb wifi UK model, rooted.
Connected via cable to Dell XPS 17, latest USB drivers installed, win 7 x64.
First of all, I enabled USB debugging and windows installed drivers for all except MTP.
Tried installing the Samsung driver package, same problem. Uninstalled at present.
Installed kies, didn't work, wouldn't even connect to the device. Uninstalled.
Followed the instructions on the wiki but the suite software installs the driver succesfully but then windows won't accept the driver. Tried the workarounds in the wiki but still no luck.
Tried rebooting the tablet and leaving the cable connected.
Tried wiping the cache.
Tried restarting both the tablet and laptop after reinstalling software and drivers, still no luck.
Found several workarounds on my travels, one was a command line for windows to add to usergroup ( it's on the laptop downstairs, will add it to the post tomorrow).
One post said to change a registry entry...really? Tried that, and another registry trick, but still no.
Using the same laptop, I had similar problems trying to flash a custom rom onto an s4, but the CM installer worked first time. I've done a fresh install of win 7 since then.
Can anyone shed any light on this for me please? Is there any kind of workaround? Running out of ideas!
Thanks
Fixed this, well, kind of. Here's a quick rundown of what I did, for people like me who are struggling with connection problems.
I thought I had tried everything, was going to dump the whole thing and then remembered that I'd fixed some previous USB problems (sound card) by doing a clean boot.
First, remove Kies.
The only other thing that is required are the samsung mobile drivers from their website. I tried with and without and this would only work with them installed.
Restart your tablet, make sure MTP is selected.
You can find out how to do a clean boot for you version of windows here.
Leave your device connected via USB cable. Once you have clean booted into windows, windows will attempt to install the drivers from windows update, let it do this. It can take a minute or two to complete. You should then see a green tick in the notification area rather than the dreaded red cross.
If, for some reason, the driver doesn't install first time, you can unplug and then plug back in the USB cable and this should do the trick.
What I did find, is that the connection wasn't consistent, I could restart either my laptop or tablet and then it wouldn't connect, so I'd have to go through the above process again to get it to connect.
Doing this allowed me to flash the Clockworkmod recovery with odin 3.09, but for whatever reason, I was still unable to use the recommended Eimdall suite to flash cyanogenmod.
In the end, I downloaded the CM11 zip file to my tablet (via http) and then used ES file manager to move it to the SDCard root and then clockworkmod picked it up from there.
Also, once CM was installed, there were no connection problems at all, as far as I can see.
Hopefully this will help others in the same predicament.
So I saw that Samsung had pushed out the Lollipop updates a while back. I thought I'd do an upgrade. I've rooted, which I assume is the reason(or Knox - or both) that I can't do the OTA. So I figure I'll plug in and find out how to push the update...at which point I learn that although I am able to charge fine, my tablet is not connecting to any PCs. I've tried 3 different computers, 2 running Windows 8.1, and one running WIndows 7. No luck. The Windows 7 machine initially said it loaded an unknown USB device, but after I installed the Samsung drivers, it does the same thing as all the others, acts like it doesn't see anything. No device in device manager.
So, I'm not sure how to proceed. I feel like I should get USB functioning before trying to update? I can still boot recovery and try stuff from the SD card as well. Regardless, I'm not sure what I should do first, I'm concerned that USB connectivity appears to be broken.
Thanks!
Does mtp work? Can you see your internal storage and sd card?
You may have disabled mtp in your recovery on accident or on purpose and forgot you did. I would check that first.
acdbrn2000 said:
You may have disabled mtp in your recovery on accident or on purpose and forgot you did. I would check that first.
Click to expand...
Click to collapse
You can't disable mtp in stock recovery and even if you could it wouldn't affect download mode.
Thanks for the ideas. I got it going. Apparently I have 3 MicroUSB cables that are unsuitable for data use. Super annoying!
Hi Guys,
A weird one here for you, I'm already contemplating throwing my phone at a wall that's how long I've been trying to fix it.
I have a LG G3 D855 Gold 32gb model purchased via Kogan in Australia.
The unit is now on Android 5.0 (no updates available for 5.1+) - Software Version V20i-SEA-XX with Build number LRX21R.A1440645925.
This phone is non-rooted with stock ROM etc.
So the issue at hand, I upgraded my Win7 PC via the upgrade option to Win10 to retain my games/files etc.
Now when connecting the phone to the PC it only goes to charging mode and I am unable to click on it within the drop-down to change it to anything else.
I have tried LG G3 drivers, Googles generic drivers, ADB suite drivers. I am unable to adb find the phone, I do not have an Acer Composite device in Device Manager.
Win 10 keeps saying the device is not recognised/malfunctioned.
Tried different cords, double checked the connector on the phone for any dust specs etc.
My PC refuses to work with any driver I have thrown at it, however in each scenario with various drivers, warnings still persist in Device Manager.
Some of the drivers force the phone to connect/reconnect and cause the "ping" sound each time it disconnects and reconnects (with malfunction warning prompts).
This is on Win10 with 64bit Home edition.
I am at my wits end and can't think of anything I haven't tried beyond a factory reset of my phone (hoping not to at this stage as I'm thinking it's driver-related).
It won't let me tether or anything via USB also, same goes with USB debugging, no change.
Lastly which may also help narrow it down, with the phone plugged in BEFORE it gets to the OS, I can change between PTP/MTP and USB charge, however once the Win10 OS loads up, it disconnects/malfunctions and lists Charge Only.
And yes, this phone can connect on my Win7 small PC which I use for testing crap out on.
Any ideas guys?
Let me know if any log files or anything is required.
At this stage I am unable to do a root to the phone (due to adb issues etc) nor can I connect to the internal phone system unless I use in the in-built file explorer.
Edit: *SOLVED*
Ok so turns out the issue is, and this is just my case, my motherboard has various utilities, one of which is a USB 3.0 boost option.
When I did an upgrade to Windows 10, it somehow screwed up various programs on my PC including registry etc.
I reinstalled the particular utility (I was actually trying to fix my graphics clock etc so happy coincidence) which also re-installs the USB 3.0 Boost software which in turn has fixed my USB Ports.
So if you have a custom built PC (my Motherboard being a Rampage 4 Formula). Check the Mobo Utilities/Drivers for any conflicts.
I have the exact same problem, and I can't seem to find a solution for months now. It's really annoying and depressing
nicholsonr said:
Hi Guys,
A weird one here for you, I'm already contemplating throwing my phone at a wall that's how long I've been trying to fix it.
I have a LG G3 D855 Gold 32gb model purchased via Kogan in Australia.
The unit is now on Android 5.0 (no updates available for 5.1+) - Software Version V20i-SEA-XX with Build number LRX21R.A1440645925.
This phone is non-rooted with stock ROM etc.
So the issue at hand, I upgraded my Win7 PC via the upgrade option to Win10 to retain my games/files etc.
Now when connecting the phone to the PC it only goes to charging mode and I am unable to click on it within the drop-down to change it to anything else.
I have tried LG G3 drivers, Googles generic drivers, ADB suite drivers. I am unable to adb find the phone, I do not have an Acer Composite device in Device Manager.
Win 10 keeps saying the device is not recognised/malfunctioned.
Tried different cords, double checked the connector on the phone for any dust specs etc.
My PC refuses to work with any driver I have thrown at it, however in each scenario with various drivers, warnings still persist in Device Manager.
Some of the drivers force the phone to connect/reconnect and cause the "ping" sound each time it disconnects and reconnects (with malfunction warning prompts).
This is on Win10 with 64bit Home edition.
I am at my wits end and can't think of anything I haven't tried beyond a factory reset of my phone (hoping not to at this stage as I'm thinking it's driver-related).
It won't let me tether or anything via USB also, same goes with USB debugging, no change.
Lastly which may also help narrow it down, with the phone plugged in BEFORE it gets to the OS, I can change between PTP/MTP and USB charge, however once the Win10 OS loads up, it disconnects/malfunctions and lists Charge Only.
And yes, this phone can connect on my Win7 small PC which I use for testing crap out on.
Any ideas guys?
Let me know if any log files or anything is required.
At this stage I am unable to do a root to the phone (due to adb issues etc) nor can I connect to the internal phone system unless I use in the in-built file explorer.
Click to expand...
Click to collapse
Try the drivers from this site
http://forum.xda-developers.com/showthread.php?t=2785089
ludoke said:
Try the drivers from this site
http://forum.xda-developers.com/showthread.php?t=2785089
Click to expand...
Click to collapse
Using the drivers on that page you have advised gives the following.
Device Manager shows a Warning on it in USB controllers as "LGE Mobile USB Composite Device". It automatically "malfunctions" according to Windows 10 and I can't change the connection interface on the phone.
Going into the properties on that device in Device Manager lists the following;
This device cannot start. (Code 10)
A device which does not exist was specified.
http://forum.xda-developers.com/lg-g3/help/answer-windows-8-8-1-detecting-lollipop-t2967574
This also works for win 10
If u find this helpful rember the thanks button
TheMadScientist420 said:
http://forum.xda-developers.com/lg-g3/help/answer-windows-8-8-1-detecting-lollipop-t2967574
This also works for win 10
If u find this helpful rember the thanks button
Click to expand...
Click to collapse
This didn't work. Already tried
Fixed my problem
I've had the same issue with my LG G3 in being unable to connect the device to my laptop. I'm not sure if the cause was a phone software update or the upgrade from Windows 8.1 to Windows 10. Either way, I searched and fixed it tonight by installing updated drivers. Hope this helps others as well.
Hmmm, I cannot post the link! technobuzz dot net lg g3 drivers
To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!
Hi All, sorry this is a fairly long post.
i recently "Upgraded" my SM-P605 to Android 9 and it has been working fine.
i have, however, been experiencing connectivity issue with file transfer via USB.
i have tried several cables (3 Genuine) including a brand new "Generic" cable and keep getting the "device descriptor request failed" error.
i have also tried multiple PC's, loaded all recommended Samsung drivers and finally relented and replaced the USB port in the tablet itself, which still did not fix the problem.
Convinced after all of this it must be software related, i then decided to re-install and earlier version of Android which i copied over to the Tablets internal memory.
i logged into TWRP and wiped the tablet ready to reinstall Android 7. and when i tried it says the zip file is corrupted.
i now have a tablet that wont load the zip file i have, wont read from an SD card in the tablet or OTG (via TWRP) and is unable to connect to a PC via a usb cable..
if anyone could offer any suggestions i would be extremely grateful as i dont want to "Dump" this tablet as i use it daily for work..
Why it does not read the SD card? I would expect that should work and should be the safest bet here...
-Maybe the zip file really is corrupt, which can be easily told by unpacking via pc.
-If the tablet can still charge the battery usb is most likely okay.
-Sdcards can fail by becoming read-only. Most easy to tell by unsuccessfully trying to format them in the tablet or pc , but e. g. under Windows you seemingly can successfully delete and copy stuff, everything as it should even after forced refresh via F5. But after reinserting the card or rebooting the previous state is back.
-ADB has been enabled in developer settings? Then you normally get a notification where you can modify usb mode. Charge-only won't work, but most of the rest should do (Dcim/mtp/msp...) .
-And all the time Windows has to recognize the device via PnP and auto-install drivers for the current usb mode. Besides the aforementioned storage drivers for flashing and communication a modem driver and virtual COM ports must be auto-installed.
In this department i had lots of trouble with a phone based on an old TI OMAP SoC under any Windows newer than seven. Only Download mode invoked on the phone itself was still working and only zseful to restore stock rom, while in the more flexible Fastboot mode the phone wasn't recognized by Windows.
Samsung devices seem to support Fastboot only, but call it Download mode.
To come to an end, if everything fails i'd recommend to install stock rom in "download recovery" (Fastboot?) mode via Kies. If this also fails try to put the P605 manually into Download mode (Power and Volume minus or plus), no need to press home button, as often advised. After this, work your way back to Twrp, custom rom and root.
@crwzar80
Try connecting the tablet to a Windows 7 PC/laptop, making sure it's on an Administrator account (so it can autoload/download needed stuff). Not Windows 10 or even 8.1, but Windows 7.
I had the same problem a while back ago; if your attempt with this method succeeds then report back; I had an unconfirmed hypothesis about this issue.
Hello, and thanks in advance for for everyone's help (and patience if my post exasperates). This is my 4th OP phone and i've come to rely on MSM heavily as i tend to overflash ROMs etc. Although i've had issues (always evenutally resolved) in the past with getting MSM to restore, this is the first time i feel truly stymied. While playing around with TWRP i ended up having one of the A/B slots seemingly unrecoverable. Even during MSM it would get stuck on DSP.img. I eventually got fastboot to manually write that partition and i thought all was well. However during a flash of a custom ROM the phone crashed (i think t was an external event rather than related to my previous issues) in any event since that point the phone seems to be hard bricked. I can't get to the bootloader or the screen to come on at all. When plugged into Win 10 it is recognized and i can QDLoader 9008 to show up in the device manager. It even starts to work on MSM showing as connected when hitting enum. However after the initial "firehose download" it times out after 18-20 seconds. By unplug/replug etc i can sometimes get it go a bit father but then it stops at Param preload and will go no further.
Thoughts? Questions or detail i missed to help you help me?
re install the driver from device manager try dif port and cable.............
make sure no av shutting it down and good luck!
let me stress try a DIFFERENT PORT AND A DIFFERENT CABLE dunno how many times i can say that even if you got 3 cables go get a new one to rule it out also press hold power up 30 sec before you press hold to get in firehose
Install this on your pc Here. Add your device, use 8 PRO since 9 Pro isn't listed. Choose boot to EDL, and run MSM once your phone in EDL
Click the box to use lite firehose, then enum until it says connected, then start.
You said windows recognized it and so did msm
But I still gotta ask
Did you do the driver verification removal on the windows 10?
Also is it the right msm version/oos?
Use the original USB calbe, better if its a USB C TO A not to C as the C controllers on pcs are kind of weird with these kinda situations.
If you are using the same windows and drivers that worked on your old phones (Haven't formatted or uninstalled the drivers since) then nothing to be done here, but you have try to installing them with windows driver signature turned off. (Qualcomm drivers and oneplus drivers)
make sure the phone booted to EDL too.
These will solve 99% of msmtools problems usually.
try this