So i've been wiping my phone and erased my OS so it doesn't boot up properly and i'm stuck at the logo.
I've been trying around with different drivers yet Windows doesn't let me access my phone via pc
i can enter the twrp menu. I have been searching for a few hours but havent found anything that made it work again.
What can i do/use to make my pc recognize my phone and install a new os? :/
Search Google for your 'device name' and 'unbrick'
Do you have USB with OTG? Might help
Sent from my MI 6 using Tapatalk
Thanks for the advice, i tried said way before using FlashOne but had trouble installing the correct drivers
It seems to be working for now, at least its currently flashing
Heyyo, sometimes windows forgets how to set up the driver. I have no idea if it's something to do with TWRP, device tree or kernel but yeah it's an odd one... My guess is it might be kernel as it doesn't include the USB OTG fix for the Le Max 2 that a recent LOS 14.1 LeEco MSM8996 kernel update brought which is what TWRP uses for device and kernel.
Hopefully on the next TWRP version it will include it.
Device Manager > select unknown device driver > update driver > let me choose > (Standard MTP Device) > USB MTP Device > apply and so fourth
Otherwise? You can use this command with adb to get the files onto your device
adb push NameOfFile.zip /sdcard
That will put the files onto the sdcard folder of your phone as it is only the MTP driver that Windows sometimes fails to set up where as the ADB driver for Android is universal.
Related
Ok hopefully this helps someone. After flashing the amazing AOKP ROM (literally best ROM I've ever flashed...Holy stable batman) I noticed that on Win7 x86 or x64 that USB file transfer to/from SD card worked fine...as did Odin but Windows could not find a driver for my phone anymore. This creeped me out because this meant adb would not be able to connect. Running the adb devices command would not show anything.
I tried 3 different Win 7 machines and a WinXP machine all of them used to work but now they didn't I read the FAQ, I goggle searched xda and droid forums and tried everything, cables, switching USB ports, phone settings, dev settings, new usb drivers but, I could no longer get adb to connect.
So I started looking closely at the Samsung USB drivers I have on my machines which worked fine on stock ROMs, and a few other custom ROMs (not blaming AOKP no disrespect) and I found that the hardware id for my device changed and the device string wasn't referenced in any of the USB drivers files. So I forced the correct driver to install and it worked! So if that is all you need to know cool, if you some of you need the steps here they are:
I'm assuming you already have Samsung USB drivers and adb from the SDK installed (if not there's tons of info on this site to get both)
I'm also assuming you installed the USB drivers so they are in the default location, if you extracted a zip file or something you will need the path to the USB drivers
Last assumption... I tried 3 different versions of Samsung USB drivers and for each one the ssadadb2.inf that has the ADB driver was in the USB Drivers\16_Shrewsbury folder...If you don't find it there do a search in the USB Drivers folder and reference that location for step 13
Click Start button, then right-click Computer, then click Manage
Click Device Manager
Expand Other devices, you should see SCH-I500 with the yellow exclaimation point
Right-click it then click Update Driver Software
Click Browse my computer for driver software
Click Let me pick from a list of drivers
Scroll up, highlight Show All Devices, click Next
Click Have Disk
Click Browse
Browse to C:\Program Files\SAMSUNG\USB Drivers\16_Shrewsbury
Double-click ssadadb2.inf, click Open, Click OK
Highlight SAMSUNG Android Composite ADB Interface, click Next
You will get an "Update Driver Warning" saying cannot verify compatibility with your hardware, click Yes
You should see Windows has successfully updated your driver software, click Close
Back in device manager under ADB Interface you should see the driver name you just added....the entry under Other devices should be gone
Connect your data USB cable (not a charging only cable...if you can't tell the difference just be sure you used this cable for data before)
Open a cmd prompt (start>run>cmd enter if you didn't know)
browse to where you installed adb and type "adb devices"
You should see your device and a serial number again....back in business
Like I said no disrespect to AOKP I rock my B31 (soon to be 32) Pink Unicorn proudly This hopefully applies to anyone who had a hardware id change from any ROM.
Hello , well im sorry to bother you guys but i just cant seem to connect through ADB using any Cyanogenmod rom but adb seems to work on stock roms. Ive tried everything reinstalling drivers and using different cables but nothing seems to work , could anyone help me out?
Try this and see what the outcome is good luck
All credit goes to oc3rulz for finding this.
http://forum.xda-developers.com/show...&postcount=814
Originally Posted by oc3rulz
I have CM7 installed and I just got Windows to recognize the SDCARD via USB Mounting!!!!
Now again I am using Windows 7 so the steps are almost exactly the same. I literally just changed the device to a USB Mass Storage device and it worked!
Lol after trying so many drivers and it being the generic driver makes me angry. Here's what I did.
1. Right click on My Computer, go to Properties.
2. Go to Device Manager
3. Find your My HTC (should be the second one Android USB Device), right click on it and select Update Driver Software
4. Then select Browse My Computer for Software
5. Then choose Let Me Pick which driver to install on the bottom.
6. Then choose USB Mass Storage Device
Then it takes some time to think and viola! All working! However we are not DONE!
EDIT: So the next step I did after experienced issues remounting after unplugging the phone. I have change the MTP to ADB Testing Interface and things seem to be mounting everytime. Rebooted phone and PC, both worked again so I think this may be a working solution.
Now go to MTP.
1. Right click on My Computer, go to Properties.
2. Go to Device Manager
3. Find your MTP (should be under Unknown Devices), right click on it and select Update Driver Software
4. Then select Browse My Computer for Software
5. Then choose Let Me Pick which driver to install on the bottom.
6. Then choose Google Inc. and the Driver is ADB Testing Interface.
ENJOY!
Hi,
I need to get my V30 listed as adb device in the command, but I experience big problems with this normally simple step.
I have a rooted Nvidia Shield, so a little experience with adb, but I'm too stupid to get my V30 recognized as an adb device. USB debugging is activated on the phone for sure, but I have the impression it's not because I don't know what is going on.
I have tried different things, and uninstalled the phone driver between my different approaches with the USBDeview tool.
install adb-setup-1.4.3 completely + connect V30 -> run command from the adb.exe directory on my hard drive -> no devices listed/found
used a USB 2.0 port instead of USB 3.0, still nothing.
tried to install the Google USB driver via device manager manually by selecting "android_winusb.inf" file, but Windows says the device is already installed with the newest version. It's listed under "portable devices", no clue how I can change this. My shield tablet was listed under other devices as well as adb device etc....you know what I mean. So I have no idea why the V30 makes so much problems here.
I installed the Android SDK and downloaded Google driver from there to use them for the V30 driver installation -> Windows 10 says already installed, no chance. When I uncheck the box "compatible hardware", I can only choose between some MTP device drivers, no adb or google driver or anything like that. :crying:
I tried restarting both, PC and LG V30, did a reset to factory settings of my V30.....no chance. I would like to disable some bloatware apps and use the SD card as internal storage (formatting function of the SD card as internal storage isn't available, silly I know). So no root for now, just a little extra functionality. I don't know what to do, please help me. :crying:
JogibaerNr1 said:
Hi,
I need to get my V30 listed as adb device in the command, but I experience big problems with this normally simple step.
I have a rooted Nvidia Shield, so a little experience with adb, but I'm too stupid to get my V30 recognized as an adb device. USB debugging is activated on the phone for sure, but I have the impression it's not because I don't know what is going on.
I have tried different things, and uninstalled the phone driver between my different approaches with the USBDeview tool.
install adb-setup-1.4.3 completely + connect V30 -> run command from the adb.exe directory on my hard drive -> no devices listed/found
used a USB 2.0 port instead of USB 3.0, still nothing.
tried to install the Google USB driver via device manager manually by selecting "android_winusb.inf" file, but Windows says the device is already installed with the newest version. It's listed under "portable devices", no clue how I can change this. My shield tablet was listed under other devices as well as adb device etc....you know what I mean. So I have no idea why the V30 makes so much problems here.
I installed the Android SDK and downloaded Google driver from there to use them for the V30 driver installation -> Windows 10 says already installed, no chance. When I uncheck the box "compatible hardware", I can only choose between some MTP device drivers, no adb or google driver or anything like that. :crying:
I tried restarting both, PC and LG V30, did a reset to factory settings of my V30.....no chance. I would like to disable some bloatware apps and use the SD card as internal storage (formatting function of the SD card as internal storage isn't available, silly I know). So no root for now, just a little extra functionality. I don't know what to do, please help me. :crying:
Click to expand...
Click to collapse
try installing the lg usb drivers mobileusbdrivers.com/2017/10/lg-v30-usb-drivers-download.html
madhouse24 said:
try installing the lg usb drivers mobileusbdrivers.com/2017/10/lg-v30-usb-drivers-download.html
Click to expand...
Click to collapse
This worked for me.
Sent from my VS996 using Tapatalk
Device USB\VID_1004&PID_62CE&MI_00\6&8563cbe&1&0000 requires further installation.
Lg Drivers 4.2.0 Installed. Running Windows 10 x64.
Also the phone doesn't even recognize it's connected to a PC unless USB Debugging is turned on, i.e doesn't give options for transferring files , charging device, Transfer photos etc from the pull down menu.
When in usb debugging mode if i select Transfer Photos the PC recognizes it, but not if I select transfer files.
Any ideas?
Spaceboy60 said:
Any ideas?
Click to expand...
Click to collapse
Hi
have you checked if the device is recognised in the device manager?
Especially after changing to file transfer?
If there is a error code in the device manager the driver cannot be installed.
First to check is c:\Windows\INF\setupapi.dev.log - here its explained what didnt worked.
logg.sar said:
Hi
have you checked if the device is recognised in the device manager?
Especially after changing to file transfer?
If there is a error code in the device manager the driver cannot be installed.
First to check is c:\Windows\INF\setupapi.dev.log - here its explained what didnt worked.
Click to expand...
Click to collapse
Well I did get it working after reinstalling drivers, in MTP mode anyway.
However after installing the lg drivers and booting into download mode g5 shows as "unknown device" in device manager.
Think there's something wrong with phone, when I try installing a custom ROM instead of loading the default language initially it shows the last language I used, screen goes black when I make phone calls (all roms now, even after formatting data (instead of wipe)) and when I backup with TWRP, there's always a problem restoring the image: basically half the apps I had are gone upon first boot After restoring, a lot of apks won't install (says they're corrupt (they're not)), some play store apps won't install, lots of apps crash etc.
Need to restore to stock but since my device isn't even recognised under windows device manager there's no way to use uppercut/LGUP.
Hello!
I have recently bought this phone with installed custom ROM and I wanted to install another one. And then I downloaded the ROM and formatted the phone from TWRP and I just connected it to the PC and there was nothing.. I searched for hours I tried so many adb drivers, usb drivers, etc and I couldn't detect the phone in the ADB powershell nor transfer any files. The only progress I managed to do is side loading it.. The ADB detected it and then I tried adb push (the exact name of the file) /sdcard and after that (error: closed) appeared.. I think the main reason is because before I formatted the phone I didn't allow the usb debuging but apparently you can't allow it from the recovery... I don't have any type-c OTGs laying around.. How in the world am I supposed to transfer the ROM to my phone? Please help me! Thank you!
way2easy said:
Hello!
I have recently bought this phone with installed custom ROM and I wanted to install another one. And then I downloaded the ROM and formatted the phone from TWRP and I just connected it to the PC and there was nothing.. I searched for hours I tried so many adb drivers, usb drivers, etc and I couldn't detect the phone in the ADB powershell nor transfer any files. The only progress I managed to do is side loading it.. The ADB detected it and then I tried adb push (the exact name of the file) /sdcard and after that (error: closed) appeared.. I think the main reason is because before I formatted the phone I didn't allow the usb debuging but apparently you can't allow it from the recovery... I don't have any type-c OTGs laying around.. How in the world am I supposed to transfer the ROM to my phone? Please help me! Thank you!
Click to expand...
Click to collapse
Okey, I just managed to use adb push without side loading just in the twrp and I don't know how to delete the post so excuse me for the spam!
Heyyo, I'm the maintainer of official builds of TWRP for the LeEco Le Max 2.
Usually for TWRP it can sometimes mess up USB mode if the device is plugged into a PC before it fully boots to TWRP.
Windows for some reason messes up the driver install for MTP as well. Usually of this happened you will need to manually go into device manager and select update driver on it and manually select the driver to install like this:
https://photos.app.goo.gl/nRYfpAZ0i50GuM512