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
Related
Hello! I just rooted my Eris yesterday and when I plug my phone into my computer it doesn’t come up on my phone and ask me how I want to dock it (it is checked to ask on the phone itself) . When I first plugged it in and it tried to install the drivers it failed. Over at developer.android.com where I got and installed SDK it said to use pda.net to install drivers, which I did. So now my computer recognizes the phone and I can push apps over however the phone still will not give me the option to mount as a drive. Is there anyway I can make it mount so I can browse files in file explorer. Thank you in advance.
i'm assuming you are on a Windows PC...
firstly, are you able to mount as storage in Recovery?
also, not sure about the pdanet method (never used it)... but i know that if you install HTC Sync it should work fine (link below).
http://www.htc.com/us/support/droid-eris-verizon/downloads/
i'm assuming you are on a Windows PC...
Click to expand...
Click to collapse
Sorry, yes. Windows Vista 32bit
To be honest, I'm not sure what I did but it works now. I plugged it into my laptop to charge and it wanted to mount with no problems. I Just tried it on my PC and it also worked. Even worked with the same usb cord I used last night so that rules out a cord problem
Thanks though. I didn't even think about trying it in recovery mode. If it happens again I will see where that gets me
Despite many tutorials I am still not able to connect to my HTC Desire X (unlocked, S-ON, HBoot 1.25.002) for executing the fastboot-cmd.
I am not on USB3, tried different USB-ports, tried to install the Google USB driver (v11) manually - but still no luck. In bootloader the message 'FASTBOOT USB' is visible and highlighted. In Windows the device has a yellow exclamationmark (unknown device), category 'USB serial bus controllers'. It used to work fine, on the same computer. Updating to Windows 8.1 could be a cause. If my phone is in normal mode and connected to the PC I am able to drag files to and from the phone. ADB is working also, 'ADB devices' shows my phone.
What can I do more to recognize the phone for executing fastboot? Or is something else needed to do? Thx!
I can't give you link right now but use the search there was a way to use fastboot under windows 8.
Ps:
Try this https://cloud.mail.ru/public/e0429e9c057f/usb_driver_r08-windows.zip
Thx for your reply, still no luck :crying: I have searched more and more and problem solved :highfive:
This thread (click on link to view) helped me the most and has the files which are needed. The suggested KB-solution didn't work so use the old-dirty trick (and USB.zip) which is inside the thread mentioned. After executing the batch-file you probably still need to copy the files manually.
"As you all may now, Microsoft pushed the new driver stack in Windows 8.1 so ALL (not only USB 3.0) devices must provide a BOS descriptor. Sony ADB and Fastboot doesn't, so Windows fails to enumerate the device which is reported in Device Manager as error code 43. This also may help if you have a USB drive or mouse and it stopped working after you upgraded from Windows 8 to Windows 8.1."
"It's not any kind of magic - it just replaces Windows 8.1's usbhub.sys and usbport.sys with Windows 8's ones. Old files don't check for BOS descriptor so Fastboot can work."
Also just having the very same issue, haha its extremely frustrating. got adb to work when phones on but not when off
Might have just killed my usb ports
thank god for backups
Inside the mentioned thread are some solutions, i.e. #44
Just use the command: "sfc /scannow" from an elevated command prompt... the original usb drivers will be restored.
Or rename the .bak files of the two copied files to the original ones?
RuudM said:
Inside the mentioned thread are some solutions, i.e. #44
Just use the command: "sfc /scannow" from an elevated command prompt... the original usb drivers will be restored.
Or rename the .bak files of the two copied files to the original ones?
Click to expand...
Click to collapse
Luckily I had a backup, hmm still no drivers work might have to downgrade windows8.0
Going to leave this in case someone is still having this problem:
http://forum.xda-developers.com/htc-one-s/general/guide-fix-fastboot-windows-8-1-t2858337
And if you don't have the drivers AND don't want to install HTC Sync Manager:
http://forum.xda-developers.com/showthread.php?t=2222501
Hey guys.
I have Samsung galaxy ace 5839i (stock for 5830i) and I am using it for a few years, but this problem came for the first time.
Always, when I try to connect my mobile to pc using cable, it just won't connect, it won't even show me the notification of connecting.
Before this problem, I connected it to fedora linux and it was succesful, but now? It won't show me that USB sign even in windows.
Any help?
Thanks in advance
@LiQuDiAk, basically s5839i and s5830 i are identical in many areas ,, few questions though,, did you root your device or you are on android 2.3.6 stock version / kernel 2.6.35.7 ?
when you are in your windows device manager ( while you are connected , do you see any exclamation / question marks in front of the corresponding driver), you can always uninstall your old driver, reboot , then try compiled driver in attachment , and reboot to take proper effect in your registry (tested on win xp/7 -32bit) . Also check your device settings>Application>Development > USB Debugging and make sure the option is checked. now lets check your debugging mode through ADB command and see if your device is being recognized. download platform zip attachment, unzip it and put the folder someplace like your desktop. Now open your command prompt (cmd) through whatever means you are comfortable and change directory (cd) to the unzip folder or simply open your folder and drag/drop adb.exe into your CMD to be in the right place very fast. Then type "adb devices" without quotation marks and report for more troubleshooting .Assuming your Samsung cable is not faulty of course.
@ehsanotaku Yes i did root my phone on pheonix fire rom. No i do not see any. And debugging is checked, that was my first guess why it was causing this. I was checking, whether my device is recognized in linux (only available OS in present) and it was NOT, but the cable is not faulty, because it was charging my phone... but i will do recognize process on windows, hope it will get better. But thanks so far!
so, the driver didnt help, but the adb devices got me something long which i do not completely understand (i am a girl and not IT) so...
LiQuDiAk said:
so, the driver didnt help, but the adb devices got me something long which i do not completely understand (i am a girl and not IT) so...
Click to expand...
Click to collapse
off topic though, gender discrimination is prejudice,, sorry if you are offended . Learning from each other despite your gender,does not undermine your knowledge EVER mate You might find it hard to believe, but I am quite novice in android stuff myself ( learning a great deal from some female members though ).
Back to topic at hand now,,,So let Perfectly Clear take away the time-consuming tasks and fix some stuff ..1. so you can not access your sdcard's content from either systems,, even if you try some live bootable Ubuntu disk/flash into your system and boot it up,, you can't access the mount drive content , right?
2. screenshot of your device manger while you are connected always help mate
3. those long streams of numbers and words is supposed to be your device name , it means your device is communicating with your pc ( /sdcard/ should not be corrupted). You can push (copy ) some vital files to your device with following command :
again same path >> put some file into your desktop (drag/drop to cmd)
i.e: "adb push C:\Users\ehsanotaku\Desktop\test.txt /sdcard/"
back to your device and check root of your files with whatever file explorer you got to approve the theory
4. forgot to ask , just to be on the safe side your device is not in boot loop process, stuck on samsung splash screen or something like that, right?
okay, thanks!
1. I cannot access it trough USB to mobile way, but from SD card adapter, yeah I can (it is just the weird feeling, when you always have to put out your sd and do it that way, i would like to sort this out)
2. http://s1.postimg.org/nkta50u3x/Untitleddas.png I suppose the unknown device is my phone.
3. Just a question, my phone is not connected, i cannot access it and this doesn't help
4. Nope, it is working, i can access everything, just this connecting problem i have. anything else is running smoothly.
Let's say any of this will work, do you think flashing a stock rom will help? I am not sure, if this is problem of rom or not, so...
And maybe i wasn't clear (my bad if not) but when i plug the cable in my device and pc, pc will make this sound of new device found, but it wont show me anything, so my phone. It will charge, but it wont connect, it is behaving like it is on a charger and not connected to the phone.
@LiQuDiAk, Hasty actions are done in a hurry, sometimes without the necessary care or thought. Now let's not leap to any conclusion about your Android custom Rom and flashing back to stock. lets focus on your first most obvious problems,which is driver related.
You didn't declare your flavor of windows: i.e: Windows x86 based-PC;professional 7
Not so sure of your OS Name/Version and System Type, search "system information" in your search box.
Your task manger depicted ACPI x64 ( 64-bit system, no wonder previous 32-bit compatible didn't work out for you ).
Symptoms observed so far:
1. USB cable only charges ( remember your USB cable data line might be the culprit. Just in case of only charging,checking with another set recommended. Your USB port might be problem, some dirt or faulty data line, checking with another USP port doesn't heart though.
2. Windows recognizes something more (like in your case, struggling to find proper corresponding driver), but cannot see it as a Samsung android device (cannot allocate the installed USB drivers to the device).
-If you got Kies (Samsung proprietary software) installed on your PC, delete it with a descent uninstaller program such as CCleaner free version .Kies might cause driver conflict , use it as only last resort , if all drivers failed to communicate with s5830i device.
-Also Uninstall your previous given driver same way, now restart , back to system and grab set of universal Samsung Drivers from attachment .
3.Can't see your "USB connected" in Android notification bar, so you cant click on it and mount your storage data part while you are connected to your PC.
-Normally, when you plug in your Android device, Windows will recognize it as an MTP (Media Transfer Protocol) device and quietly mount it.
However, if you’ve ever attempted to unlock your device such as to install a new ROM or root it, then such miss behaviors might be expected occasionally .
Before i go for more troubleshooting , please provide a full screenshot from your "About Phone" page in your settings . I am quite curious about this phoenix Rom you have mentioned though . I am quite familiar with at least dozen of discontinued/ported projects, but never heard of such ported Rom from other models into s5830i .
Couple of solutions :
Navigate to your settings,Storage and touch the upper-right corner for the “USB computer connection” options, if you have this part available.
make sure “Media device (MTP)” is selected. ( if you have USB Utilities section or whatever added section in your custom settings go there . Selecting that will do the trick. If it does not, then you likely have a driver problem.
Open your device manager, Right click on your unrecognized device in question,choose update driver software, choose Browse my computer,find it through given x64 drivers in your package ,Restart. ( After a successful installation, restart your PC, you must have something like the picture in attachment ) .
Problem was not resolved, Uncheck your debugging option,power off your phone. Now hold Volume(+) + Home + Power for a couple of seconds simultaneously to get to your Samsung Recovery or your Clockwork Recovery, choose Reboot( might be some process/service in your background, which interfere with your Auto USB connected feature of your device. See if the problem is being resolved .
Problems have been persisting, we might need to format your SD card, but before that, insert it into your card reader, in your file explorer window choose Tools>Folder options>select view tab> tick your select hidden file.folders. Now copy all of your SD card's contents into some folder, safe inside your PC.
We can format your card through your clockwork mod recovery console, or some partition tools such as free mini partition wizard,,
problem still persist? let me know
Hey
After some rest with this, my mobile got it solved (dunno why, just once tried to do it and it works.)
So, thank you very much with your answers!!!!
And about that screenshots, I will PM you
But, really, thanks a lot, mate!!!!
Hey xda members,
My name is Pierre, from France and new owner of X820 version 6GB 64GB (from Aliexpress).
I made a big mistake yesterday, wiping from TWRP all data (Sytem, applications etc.)
Now if I put "ON" again, it is just showing "EUI" logo, without end
I have still access to TWRP but no backup, not .img loaded in the phone.
I can't connect and load from USB the ROM, so I am honestly lost.
If you have just any idea,how to solve it! Please let me know
Thank you very much, and good evening,
TWRP has a backup solution for you. I did this same misstake like you.
In Advanced settings you can run ADB SIDELOAD.
I hope you have proper ADB drivers in your PC and command prompt in Windows is your friend.
With ADB SIDELOAD you can install ROM from your PC via USB to your bricked phone. ADB uses whole base of commands to control what you can do.
Follow this steps:
https://forum.xda-developers.com/showthread.php?t=2318497
Twrp also supports MTP so you should also be able to copy a rom on the sdcard when in twrp.
just use:
fastboot boot twrp.img (if TWRP you have in twrp.img file)
mobile boot in TWRP
then
adb push rom_file.zip /sdcard
after OK just install that rom from SDCARD via TWRP...
Thank you Razor, mikey and cr3pt !
If I am not mistaken, you provide me: 2 different solutions (ADB Sileload or abd push ROM).
It does mean, if I select the "one more easy" :
1. I boot in TWRP my phone
2. connect by USB (ADB drivers must be installed). Usually it is written MTP or "Android" but I can't see the external drive in Win10.
3 Then adb push rom_file.zip /sdcard in the Wincommand
4. wait and after disconnect USB
Then I will find the ROM to install in my phone.
Is it correct?
Yes
If you have TWRP, connect the phone to your computer, mount storage in TWRP, copy the rom of your choice, and install it. That simple
Sent from my Le X821 using Tapatalk
I use TWRP and always just drag and drop the ROM zip from PC to the phone's internal storage and it shows up in TWRP under install. It's super easy. As long as you have the correct drivers installed on your PC you shouldn't need to use adb.
kanagawaben said:
I use TWRP and always just drag and drop the ROM zip from PC to the phone's internal storage and it shows up in TWRP under install. It's super easy. As long as you have the correct drivers installed on your PC you shouldn't need to use adb.
Click to expand...
Click to collapse
Hey
My computer (Win 10) does NOT recognized sometimes: MTP, or sometime "Android". So in fact, I never the external storage in my windows.
That is why I can not simply "drop" unfortunately.
Should I maybe install ADB again?
install ADB, all necessary drivers. without that you can only dream about correct fix'a
piyerre said:
Hey
My computer (Win 10) does NOT recognized sometimes: MTP, or sometime "Android". So in fact, I never the external storage in my windows.
That is why I can not simply "drop" unfortunately.
Should I maybe install ADB again?
Click to expand...
Click to collapse
I'd try to start again clean. First completely remove adb and android device drivers from your computer. Then boot your phone into TWRP and connect it by usb to your computer and see if it auto installs the right drivers. If not, I guess you have to find where to download them from to install manually.
cr3pt said:
install ADB, all necessary drivers. without that you can only dream about correct fix'a
Click to expand...
Click to collapse
Can you give me please a link with the correct ADB and the correct drivers.?
I can't see the external drive even if adb devices gives me OK result.
Thank you,
you don't need external drive - correct is adb device. just push file when is visible in device manager
Hello !
It does work perfect, I finally use the "adb push" function!
Thank you very much all
cr3pt said:
just use:
fastboot boot twrp.img (if TWRP you have in twrp.img file)
mobile boot in TWRP
then
adb push rom_file.zip /sdcard
after OK just install that rom from SDCARD via TWRP...
Click to expand...
Click to collapse
It works! Thank you very very much!
Bro Its is new security added in windows 10... U can only install official and signed drivers in windows 10.. U should turn it off.. only then u can access adb and fastboot...
One more thing bro...
If u have lost every thing, but u r able to boot in twrp, then follow me:
1. Download any rom for le max 2 U want to
2. After downloading,copy it in ur pendrive
3.Boot in twrp
4.connect the pendrive to ur device using OTG adapter
5.Mount USB storage
6.wipe every thing again.
7.After installation,reboot
8.first boot may take time and then wgwghrussuwgskaaiiawg (U know the rest??)
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.