Hi there,
I'm having problems when trying to install a ROM through the 'install zip from sideload' feature in ClockworkMod 6.0.4.3. My Windows 8.1 PC can't recognize the device at all while in the sideload (Mounting USB storage works perfectly). The device doesn't show up when I type
Code:
adb devices
in the command prompt, even when I run it as an administrator. It can't be the recovery because I've tried downloading from different places and tried to flash about 3 times.
Is anyone else having this problem? Or has had this problem in the past but has solved it already?
Thanks in advance
Do you have usb debugging enabled on the phone? It's under the developer options.
Swiftflikk said:
Hi there,
I'm having problems when trying to install a ROM through the 'install zip from sideload' feature in ClockworkMod 6.0.4.3. My Windows 8.1 PC can't recognize the device at all while in the sideload (Mounting USB storage works perfectly). The device doesn't show up when I type
Code:
adb devices
in the command prompt, even when I run it as an administrator. It can't be the recovery because I've tried downloading from different places and tried to flash about 3 times.
Is anyone else having this problem? Or has had this problem in the past but has solved it already?
Thanks in advance
Click to expand...
Click to collapse
Adb sideload should be working fine. Make sure you're not using a 3.0 usb hub.
Sent from my HTC One Max using Tapatalk!
Related
I had this problem just this week after i think i updated to latest CW recovery as my optimus one doesnt get detected anymore when connected to pc, making it impossible for me to obtain flashable zip files for my fone. SD card is working fine. USB debugging is unticked. Please tell me how to solve this as I tried to reflash old recovery but still cannot connect using usb.tried flashing backup but i was greeted by md5 mismatch error.Anyways...md5 issue has been solved but the usb thing still doesnt works
Somebody help me please
DistantFather said:
I had this problem just this week after i think i updated to latest CW recovery as my optimus one doesnt get detected anymore when connected to pc, making it impossible for me to obtain flashable zip files for my fone. SD card is working fine. USB debugging is unticked. Please tell me how to solve this as I tried to reflash old recovery but still cannot connect using usb.tried flashing backup but i was greeted by md5 mismatch error.Anyways...md5 issue has been solved but the usb thing still doesnt works
Click to expand...
Click to collapse
Just enable USB debugging and type in 'adb devices' from command prompt. (For adb to work you need Android SDK)
If it reports as some device as detected, things can be worked out.
developer++ said:
Just enable USB debugging and type in 'adb devices' from command prompt. (For adb to work you need Android SDK)
If it reports as some device as detected, things can be worked out.
Click to expand...
Click to collapse
Figured it out by installing lg driver again
Thanks
Well I accidentally erased my OS and now I TWRP can not mount USB storage.
I tried pushing through adb but it said "device not found".
I tried connecting in fastboot usb but windows can not install driver.
I have no ROM on my storage and I'm stuck.
I really need help, please.
First install a working SDK/ADB tool folder (link in my signature)
Then the sideload should work via TWRP, it takes sometime to activate but stay tune it will work.
From there you should be able to recover a ROM
Lucky Thirteen said:
First install a working SDK/ADB tool folder (link in my signature)
Then the sideload should work via TWRP, it takes sometime to activate but stay tune it will work.
From there you should be able to recover a ROM
Click to expand...
Click to collapse
ADB does not work for some reason even though I followed your steps. Windows starts installing drivers and ends up failing.
GTFX said:
ADB does not work for some reason even though I followed your steps. Windows starts installing drivers and ends up failing.
Click to expand...
Click to collapse
Which Windows version you have? Is your account an Administrator one? Did you enable USB Debugging on your phone?
Can you can try those drivers?
I have the drivers installed, but I don't know about USB debugging. I did enable it on my previous ROM if that helps but since I cleared all my data, I have nothing in my storage and I also can't access it via TWRP.
I tried your adb steps but it still tells me "device not found".
And I'm on Win7 x64 and using an admin account.
Have you tried this?
http://forum.xda-developers.com/showthread.php?p=35897885
Sent from my HTC One X+ using Tapatalk 2
Got it all worked out, thanks for the help.
Installed the latest drivers once again, downloaded the SDK files given on HTCDev and it adb pushed the ROM.
Worked like a charm.
I was trying to do this http://forum.xda-developers.com/showthread.php?t=2577826 and got up to replacing system.odex and everything crashed now it wont get past yellow load screen. I have safestrap but dont have more than one backup. Every time i run Adb come up with error:closed .I thought factory reset would fix but didnt now ive lost hope. HDX7 Help needed pls
and i tryed adb on multiple computer with no luck + different drivers. does show up in devices
Solved
that usual guy said:
and i tryed adb on multiple computer with no luck + different drivers. does show up in devices
Click to expand...
Click to collapse
Needed to input adb sideload rom.zip (Zip was also in file name but shouldn't be) and flashed to stock firm ware
Reflash?
Fixed
johnwaters said:
Reflash?
Click to expand...
Click to collapse
I fixed it by installing a new rom from adb
May i ask you a question?
How to connect adb?? i'm not connect adb...what is your os? win?or linux?
um.. please tell me the tutorial how to connect adb?
cjdfyd2 said:
How to connect adb?? i'm not connect adb...what is your os? win?or linux?
um.. please tell me the tutorial how to connect adb?[/QUOTE
I had safestrap so I put it in adb sideloader mode. And your device should be detected in device manager, if not install the right drivers. then go in cmd and navigate to adb file in platform tools from the package you should've downloaded. Then enter adb USB devices and it should show it connected. -windows xp
Click to expand...
Click to collapse
When I "Swipe to wipe" in twrp, twrp instantly resets.
I can not swipe to wipe.
I successfully had rooted access and twrp installed with Slimroms on Nexus 9 running correctly.
I Tried to install an 8.0 Oreo rom but it crashes and resets on the google screen.
when i try to return to old roms I get "Error 7" in Twrp.
and I can no longer swipe to wipe or factory reset.
Anyone know how to fix this issue so I can return to 7.1.2 SlimRoms?
the nexus 9 no longer shows up in windows or under ADB Devices.
So i cant access adb functions.
did my bootloader have a problem?
it seems twrp is crashing when its trying to format or wipe mounts ?
Have you tried flashing the latest firmware from Google with fastboot? That's where I would start.
Sent from my SM-T820 using XDA-Developers Legacy app
Can i do that with only twrp?
Does flashboot require adb access from a pc? I cant seem to get the device to show under windows or adb.
Can i use a memory stick and twrp to install those ?
Ill try tonight if thats possible without pc adb acess.
RecIV said:
Can i do that with only twrp?
Does flashboot require adb access from a pc? I cant seem to get the device to show under windows or adb.
Can i use a memory stick and twrp to install those ?
Ill try tonight if thats possible without pc adb acess.
Click to expand...
Click to collapse
No, can't do it in TWRP. If you're having trouble, try wugfresh toolkit. It's no longer updated but you can use it to flash a factory image that you download yourself. Toolkit might help with your issue of not being recognized by your PC.
Wugflash cant recognize the device if windows cant also.
I tried.
I can get into twrp and fastboot. But i have no connection to pc, except for usb memory stick.
The device says unlocked inside of fastboot.
Why cant i connect to adb windows? Ive installed usb drivers many times for many different phones and pcs. I dont think thats the problem.
RecIV said:
Wugflash cant recognize the device if windows cant also.
I tried.
I can get into twrp and fastboot. But i have no connection to pc, except for usb memory stick.
The device says unlocked inside of fastboot.
Why cant i connect to adb windows? Ive installed usb drivers many times for many different phones and pcs. I dont think thats the problem.
Click to expand...
Click to collapse
I've had to do it few times to get it to recognize device. That's the only reason I suggested wugs. It has quick options to retry driver install. But manually is better of course. Windows 10 gave me a heck of a time with driver's.
Hi,
My Nord 2 have latest update DN2103_11_A.17, and I wanted to enable VoLTE.
My computer can't detect my phone in ADB when in recovery mode, it detects only when just powered on normaly and connected.
I have latest Android plateform tools installed on computer.
Any Idea of what's wrong ?
Thanks
Adb drivers and permissions.
Try in Linux, easier
I have exactly the same problem on my OneNeplus Nord 2. I installed the MediaTek_Preloader_USB_VCOM_Drivers drivers in auto mode and even in manual mode under Windows 10. When I type adb reboot recovery the smartphone reboots in recovery mode even if it tells me seems strange see photo (sorry very small text...) but then no other orders are accepted. Same problem in bootloader mode. So I can't unlock the bootloader. Any help is welcome...
Hey I had the same issue with fastboot device not showing up. Fastboot with other devices on my PC had never been an issue.
This Fixed it for me:
Open "Device Manager" from the Windows start menu.
Your device should be listed there as "Android Device" (with a yellow indication for missing driver)
Right click the device and select "Update Driver".
Click Browse my computer for drivers.
Click Let me pick from a list of available drivers on my computer.
From the list select "Android Bootloader Interface". It is possible that you need to deselect the "Show compatible hardware" button.
Good luck.
cukierkas said:
Adb drivers and permissions.
Try in Linux, easier
Click to expand...
Click to collapse
Hi, thanks I'll try. Any specific driver for Linux?
I've read that adb in recovery mode doesn't work since A.14 update, and I'm on A.17. Anyone Can confirm that?