Hello,
I have a big problem and try to solve it now longer than 4 hours...
I have an old phone (HTC Desire Eye) and tried to install Lineage 14.1 but it stucks on the loading screen and did always some virbrations but after >15 min it was still in the loading screen.
So I wiped everything except the twrp recovery system and now I try to copy the lineage-zip and gapps on the storage again but the device is marked as offline! So I can't use the sideload command for example.
I reinstalled all drivers and everything but nothing helped.
The device is listed as Android Phone under Universal Serial Bus device in the Device Manager if I use it in the twrp recovery mode.
If I use adb devices it is listed as offline.
If I go into fastboot mode it is listed as My HTC under Android USB Devices in the Device Manager.
If I use adb devices the phone isn't even recoginzed.
And if I try to install an other driver while it is connected as Android Phone, Windows says that the best drivers are already installed.
Please help me I can't use my phone at all now ...
okey luckily this phone has an sd card slot so I used that for the rom. But has the offline device something to do that you have to activate usb debugging in the devoptions? But what to do if there is no rom installed expect the twrp?
Related
winxp sp3 sony tablet s when put in recovery mode for flashing the mtp driver
shows yellow (!).when i try to install driver manually it trys to start but comes
back with code 10.with tablet in normal mode winxp sees mtp & adb drivers.
the problem is only with recovery mode.tryed all i can think of and read all
solutions but driver still fails to start.so i can,t flash fw!. i really need help with
this one. please someone help i`ll give you a big thanks. i know i am not the
only one with this problem.i hope this is clear enough.
Same problem here:
Everything's fine in normal boot, but in recovery mode, I can't install the MPT driver. Win7pro. It tries to install, but ends up with a Code28 (something in the INF file is invalid, can't tell the english error message, because I have German Win7).
This seems to cause my problem flashing to R5a by AiO or the auto flasher by condi.
I get the exact error message on the tablet, as shown in post #72 in this thread:
[FW R5A WIFI/3G] NEW! custom preROOTed newest stock nbx03 R5A with R1A's recovery
Trying since four nights...
At least I managed to flash and root to 4.0.3 R2a from the "unrootable" 3.2 R10 by flashing via recovery mode to Sony original ICS R2a (downloadable from sony) and then using the AIO 5.3 to root. Don't know why this way is not published here... Tried updating to 3.2.1 etc, nothing worked... the found the links to sony's fw and thought "WTF! Let's try ICS R2a, worst case is an also unrootable Tablet but with ICS". Worked, and was rootable then.
Just ignore the problem. I believe seeing the alerted MTP USB Device in Windows Device Manager when your tablet is in Recovery Mode is being cause by your tablet's borked Android System Recovery Revision 36 (i.e., Rev.36). This problem did not occur with earlier revisions of Android System Recovery. Normally, no MTP USB Device (or Sony Tablet S) should be displayed or even installed for Recovery Mode because a tablet in Recovery Mode cannot provide MTP functionality. Recovery Mode only requires Android Composite ADB Device be installed. Normal Mode, however, requires both Android Composite ADB Device (but only when the tablet's USB Debugging is turned on) and MTP USB Device, which Windows Device Manager renames and displays as Sony Tablet S.
You are basically right... it was ADB drivers, not MTP.
I tried all possible drivers from the list, also some "phone" devices. And YES!! Windows accepted one of them...
After that, I had no problem flashing my tablet to ICS R5a!!
please, could somebody who has writing permission in the dev forums, tell Condi, that the AiO 5.3 tools tells you to check this driver ONLY AFTER you are NOT stuck in "status7" error!!!!!
You do NOT get the message in the terminal box, IF you are stuck.
That would have saved me one or two nights trial and error...
But, after all, I have a nice working ICS R5a on my tablet S
I will post a how-to for other 3.2 kernel10
that explains a lot. so i need to find another adb driver that works in recovery mode and
not worry about mtp driver?.
phc1234 said:
that explains a lot. so i need to find another adb driver that works in recovery mode and
not worry about mtp driver?.
Click to expand...
Click to collapse
Right.
In device manager, it's "android phone" (?), when you select driver manually, then I think it was the same as on the first install, so the third ADB device in the drivers list.
Windows fools you, it installs an MTP driver, and thus keeps you from using your brain
Install ADB drivers, check whether your tablet will be correctly recognized in both modes... then at least the all in one tool with custom zip will work (hopefully).
Why the flasher did not work? Don't know. looking again at my error messages, I would guess, that the busybox was not working correctly. I don't know if you have to install busybox before, manually. I thought everything was integrated into the flasher...
android phone dosent show in device manager
ThreeEyes said:
Right.
In device manager, it's "android phone" (?), when you select driver manually, then I think it was the same as on the first install, so the third ADB device in the drivers list.
Windows fools you, it installs an MTP driver, and thus keeps you from using your brain
Install ADB drivers, check whether your tablet will be correctly recognized in both modes... then at least the all in one tool with custom zip will work (hopefully).
Why the flasher did not work? Don't know. looking again at my error messages, I would guess, that the busybox was not working correctly. I don't know if you have to install busybox before, manually. I thought everything was integrated into the flasher...
Click to expand...
Click to collapse
[edit]
thats the problem android phone dosent show up in device manager. tryed on 3 wixp computers and nothing no way
ti install adb drivers.
phc1234 said:
[edit]
thats the problem android phone dosent show up in device manager. tryed on 3 wixp computers and nothing no way
ti install adb drivers.
Click to expand...
Click to collapse
But by manually updating the driver and choosing manually, you can assign ANY driver to any device - it may not work or even do some damage to the system, but basically, it's your choice!
Take the device with the "!" and give it the right driver...
"CAT" above is right with rel5 and 5a that they changed the recovery rev to 36 and this rendered the
tablet s from loading any mtp driver or seeing the android phone entry in device manager so no way
to install adb driver.this has killed conis AIO tool flashing firmware and roms until someone breaks
the lockdown sony put in.
I'm running windows 8.1. My device shows fine while booted into android under adb devices, but once I boot into fastboot, the device no longer shows. I've tried re-installing the driver several different ways but to no avail. Can anyone help me please? I need to flash stock recovery.
Use command fastboot devices to see it while in fastboot. Adb devices is for when it is booted.
3L3C7R0 said:
I'm running windows 8.1. My device shows fine while booted into android under adb devices, but once I boot into fastboot, the device no longer shows. I've tried re-installing the driver several different ways but to no avail. Can anyone help me please? I need to flash stock recovery.
Click to expand...
Click to collapse
I'm running windows 7 and have yet to get mine to see the device. Good luck.
3L3C7R0 said:
I'm running windows 8.1. My device shows fine while booted into android under adb devices, but once I boot into fastboot, the device no longer shows. I've tried re-installing the driver several different ways but to no avail. Can anyone help me please? I need to flash stock recovery.
Click to expand...
Click to collapse
put device in fastboot.
got pc, setting, system, device manager. towards top click my htc and update drivers. dont search automatically, coose device from list.
when the list comes up, you should see a few different drivers listed. choose one and try.
if one dont work, try another
Ps make sure you usb drivers are up to date. i had to install updated axhi usb drivers for my motherboards usb 3.0
As the title suggests, bootloader unlocked no problem, tablet was connecting to ADB at the time, tried to flash recovery which as far as I can tell was not successful (I can't boot to recovery, get the injured Android icon), now I can't connect to ADB (get the "List of devices attached" result). So I'm completely stuck, can't move forward, can't go back to stock, what do I do?
Edit: Apparently it's an issue with my PC, my wife's PC worked fine, why it worked to unlock the bootloader and then stopped I have no idea. Can anyone link me to a solution to get ADB working on my PC again? I tried removing/re-installing drivers, rebooting, you name it, no luck.
With your device booted into recovery or the system do you get anything in device manager? If you get a device with a yellow exclamation mark, right click it. Go to where it allows you to choose a driver from a list on your computer. Select adb android composite (or something like that)
Sent from my Nexus 5 using XDA Free mobile app
Thanks for replying.
So before unlocking the bootloader, with USB debugging enabled I could get the tablet to connect using the ADB driver and could access it with ADB but could not access storage for file transfer, with USB debugging disabled and switching the driver manually to the MTP driver I could access storage but not ADB. I have had other device drivers installed on this PC for my Galaxy phones, I had issues initially with the tablet connecting but showing a yellow exclamation mark, then I removed all of the Android USB devices using USBDeview and installed the 15 second ADB tool to get it working, I'm on Windows 8.1 BTW.
After unlocking the bootloader, with USB debugging enabled I cannot get the tablet to connect using the ADB driver and but it does show as an ADB device with no yellow exclamation mark, I just get the "List of devices attached" result and anything that tries to access the device via ADB hangs or fails. I can still switch the driver to MTP and access the storage just fine.
My wife's PC is a Win7 box and has never had android drivers or ADB installed, I used the 15 Second ADB installer on her PC and the tablet works for ADB and storage access with USB debugging turned on, so there's something I'm missing that needs to be wiped out or reset on my box.
Hey all.
I use a Redmi Note 3 (Snapdragon) and upto now I used CM13. I wanted to switch back to MIUI 8, as it supports LTE, so I tried to flash the MIUI ROM using TWRP. My device bricked and doesnt go past the loading screen. The bootloader also got locked and my device is also not being detected in adb command prompt. In device manager, I can only see ADB Bootloader driver but not any other. I tried installing ADB drivers again but it doesnt work. I believe I did not enable USB debugging. I have a TWRP backup of the previous ROM on my pc but is there any way to flash it?
Please help
Hi , I am new to xda and was previously viewing the posts of other users only, now I have an issue with one of my devices. I have a phicomm passion 660 in INDIA AKA Phicomm P660 in Europe.issue is the digitizer is broken ,USB debug is not enabled, ADB and Fastboot doesn't recognise the device as it appears to be issue with Google USB drivers( which is obvious due USB debug not enabled), all I want to do is use optical mouse to use the device again for DEDICATED VR VIEWING, I can boot the device to Fastboot and in normal boot the pc recognises the device as MTP, I tried steps from many other posts but since the device is not recognised by ADB , the result is ground zero,cant install cwm through sdcard due signature verification error.so any help or direction to relevant posts would be very helpful
For whatever reason fastboot on my PC (win10) doesn't detect my phone, adb detects it fine when it's in recovery or booted normally, I cannot send fastboot commands as it says waiting for device. I've tried a few things like the LG Mobile Driver and a universal driver but it still isn't working. Any ideas?
Just to clarify I am in Fastboot mode when trying this.
Edit: Also tried the Google USB drivers from the SDK manager, didn't make a difference
I ended up simply doing it on an Ubuntu installation. Works perfectly on there, not sure why Win10 doesn't work though.
My problem is solved.