Database Info

[q] stuck in recovery mode

First time poster, long time lurker. I downloaded TWRP and installed the recovery image but soft bricked my phone. Silly me remembered I had a backup made in CWM but not in TWRP. This is when you say to run boot.img but unfortunately I can not get the drivers to install properly on my Windows 7 x64 machine, due to not having them on here to begin with. So I have no One X drivers on the computer, I have MIUI and CM10 downloaded but can not get them to load due to not flashing properly, and TWRP with no backup. I have followed all the forums to delete drivers, re-install HTC Sync, manually point to the drivers but no dice. So.....what should I do :fingers-crossed:

Mode please close, I have resolved the issue.

Please post your solution for the benefit of others. That is how this forum works, its basically a database of issues and solutions that everyone can use.
I also think you are/were confused. The phone doesn't need to be working to get the drivers on your PC. You can download them from a variety of places. If you have HTC Sync properly installed, the drivers needed to connect your phone (USB mount, adb, fastboot, etc.) are installed. But if you have connection problems, updating these drivers or re-installing them will sometimes resolve the issue.
It seems that all you needed to do is get the drivers properly installed, then mount USB and put the ROM on the phone's SD, and flash boot.img using fastboot.

You're absolutely right. The solution was that I kept looking for fastboot to identify the device, and in my head that mean I couldn't push or flash to it. So I ended up just flashing TWRP recovery again, then it booted to CM10. Now im dealing with a whole new issue, but I'm going to work through it before I post again. Thanks.

[q] twrp 2.5.0.0

Hello,
I followed Hasoon's all-in-one root toolkit and flashed the included TWRP 2.5.0.0 onto my AT&T HTC One X. Now I cannot do anything, whatever I do, it tells me "Unable to mount /cache". Could you please help me? I can't mount the sdcard to the computer either, so I am sort of stuck.
Thanks!
Simone

simsale said:
Hello,
I followed Hasoon's all-in-one root toolkit and flashed the included TWRP 2.5.0.0 onto my AT&T HTC One X. Now I cannot do anything, whatever I do, it tells me "Unable to mount /cache". Could you please help me? I can't mount the sdcard to the computer either, so I am sort of stuck.
Thanks!
Simone
Click to expand...
Click to collapse
Can you format the SD card in TWRP?

exad said:
Can you format the SD card in TWRP?
Click to expand...
Click to collapse
I was able to wipe it. However, it still gave all these same unable to mount /cache error messages. The data is gone though.
When I connect the mounted device to the computer it still doesn't recognize it.
Thanks!
Simone

simsale said:
I was able to wipe it. However, it still gave all these same unable to mount /cache error messages. The data is gone though.
When I connect the mounted device to the computer it still doesn't recognize it.
Thanks!
Simone
Click to expand...
Click to collapse
Does the PC not recognize that anything is connected or does it detect that its plugged in but can't find the driver?
What rom is currently installed on the phone?

exad said:
Does the PC not recognize that anything is connected or does it detect that its plugged in but can't find the driver?
What rom is currently installed on the phone?
Click to expand...
Click to collapse
Currently I think it recognizes the phone as a media device (or similar, I forgot the name), not as a disk drive. I am on a Mac, and I have Android File Transfer installed, which then tells me that the device cannot be opened. On Windows it couldn't be opened either although it talked about a driver issue. I currently only have a Mac, but from Monday I could work on a Windows machine again.
The ROM currently being installed is the original AT&T provided ROM.
Thanks so much!
Simone

simsale said:
Currently I think it recognizes the phone as a media device (or similar, I forgot the name), not as a disk drive. I am on a Mac, and I have Android File Transfer installed, which then tells me that the device cannot be opened. On Windows it couldn't be opened either although it talked about a driver issue. I currently only have a Mac, but from Monday I could work on a Windows machine again.
The ROM currently being installed is the original AT&T provided ROM.
Thanks so much!
Simone
Click to expand...
Click to collapse
What version? IS it already installed on your phone? I'm trying to find out if you require MTP drivers or not. Latest version of sense/stock Roms require MTP driver to access the SD card.
In any case I wouldn't suggest using any version of TWRP above 2.3.3.1
So, I would download twrp 2.3.3.1 and check the md5
then fastboot flash recovery recoveryfilename.img
fastboot erase cache
fastboot reboot-bootloader
select recovery from bootloader then try to mount sdcard with twrp.

exad said:
What version? IS it already installed on your phone? I'm trying to find out if you require MTP drivers or not. Latest version of sense/stock Roms require MTP driver to access the SD card.
In any case I wouldn't suggest using any version of TWRP above 2.3.3.1
So, I would download twrp 2.3.3.1 and check the md5
then fastboot flash recovery recoveryfilename.img
fastboot erase cache
fastboot reboot-bootloader
select recovery from bootloader then try to mount sdcard with twrp.
Click to expand...
Click to collapse
I see, this all sounds like I need to wait for a windows machine.
I am not sure what ROM version, unfortunately. I bought the phone in December from AT&T, and it all looks like it asks for MTP drivers. I will try this with a Windows machine and then get back to this post - thank you so very much for your help.
Simone

simsale said:
I see, this all sounds like I need to wait for a windows machine.
I am not sure what ROM version, unfortunately. I bought the phone in December from AT&T, and it all looks like it asks for MTP drivers. I will try this with a Windows machine and then get back to this post - thank you so very much for your help.
Simone
Click to expand...
Click to collapse
Yes, you would need mtp drivers for the latest software version. They are included with the latest HTC sync.

exad said:
Yes, you would need mtp drivers for the latest software version. They are included with the latest HTC sync.
Click to expand...
Click to collapse
Alright, I have tried this with the latest HTC Sync manager: the MTP Drivers however won't install. I have tried with the One X+ of my Dad (which is also brand new, so probably requires the newest version also), and it installs fine and appears as a media device in the explorer. Mine however does not do anything, and driver installation says it fails to install the driver. I have tried manually installing the drivers, however, it seems to have to do with the phone because when I disconnect it suddenly Windows 7 is able to install those drivers, and as mentioned before it also works with a functional phone.
Next week I will be back at work and I have a Windows 8 machine there. I don't have high hopes that it works there, but since there seems to be an MTP driver issue with Win7, maybe there's a chance.
Is there anything else I could do?
Thanks!
PS: don't use your vacation time to root your phone...haha.

simsale said:
Alright, I have tried this with the latest HTC Sync manager: the MTP Drivers however won't install. I have tried with the One X+ of my Dad (which is also brand new, so probably requires the newest version also), and it installs fine and appears as a media device in the explorer. Mine however does not do anything, and driver installation says it fails to install the driver. I have tried manually installing the drivers, however, it seems to have to do with the phone because when I disconnect it suddenly Windows 7 is able to install those drivers, and as mentioned before it also works with a functional phone.
Next week I will be back at work and I have a Windows 8 machine there. I don't have high hopes that it works there, but since there seems to be an MTP driver issue with Win7, maybe there's a chance.
Is there anything else I could do?
Thanks!
PS: don't use your vacation time to root your phone...haha.
Click to expand...
Click to collapse
OK, so on Windows 8 I am able to install the driver, and it does not fail like in Win7, but I still can't access the mounted storage. The message of the device is:
This device cannot start. (Code 10)
The process hosting the driver for this device has terminated.​
Is there anything else I can do, or should I rather get a new phone?

simsale said:
Is there anything else I can do, or should I rather get a new phone?
Click to expand...
Click to collapse
Did you do all of what exad said in his earlier post (quoted below) already?
exad said:
So, I would download twrp 2.3.3.1 and check the md5
then fastboot flash recovery recoveryfilename.img
fastboot erase cache
fastboot reboot-bootloader
select recovery from bootloader then try to mount sdcard with twrp.
Click to expand...
Click to collapse

lauterm said:
Did you do all of what exad said in his earlier post (quoted below) already?
Click to expand...
Click to collapse
Yes, in fact, I cannot connect to the phone with this strange driver issue, which means none of the commands actually do anything.

simsale said:
Yes, in fact, I cannot connect to the phone with this strange driver issue, which means none of the commands actually do anything.
Click to expand...
Click to collapse
Are you rebooting to bootloader to do the fastboot commands? In bootloader it should say Fastboot in red. Then after a couple seconds that should change to Fastboot USB. I don't think fastboot needs the specific drivers to be on the PC like mounting the SD card requires.

lauterm said:
Are you rebooting to bootloader to do the fastboot commands? In bootloader it should say Fastboot in red. Then after a couple seconds that should change to Fastboot USB. I don't think fastboot needs the specific drivers to be on the PC like mounting the SD card requires.
Click to expand...
Click to collapse
Well, when I turn on the phone, all I get is the TWRP interface. Mounting from there doesn't do anything. I am not in fact in bootloader. Maybe I am doing something wrong here!!

simsale said:
Well, when I turn on the phone, all I get is the TWRP interface. Mounting from there doesn't do anything. I am not in fact in bootloader. Maybe I am doing something wrong here!!
Click to expand...
Click to collapse
You are definitely doing something wrong. fastboot commands only work within bootloader/fastboot and adb commands only work while the rom is loaded up or in sideload mode in TWRP. It's assumed you know this prior to rooting.

simsale said:
Well, when I turn on the phone, all I get is the TWRP interface. Mounting from there doesn't do anything. I am not in fact in bootloader. Maybe I am doing something wrong here!!
Click to expand...
Click to collapse
Turn off the phone. Then hold volume down and briefly press the power button. Don't let go of volume down until it gets to the boot loader screen. Wait for fast bot USB to display. Then you can try exad's fast boot commands.
Sent from my One X using xda app-developers app

lauterm said:
Turn off the phone. Then hold volume down and briefly press the power button. Don't let go of volume down until it gets to the boot loader screen. Wait for fast bot USB to display. Then you can try exad's fast boot commands.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Oh, thanks so much. I actually did know this from rooting my old phone - I guess I forgot.
It doesn't go into Fastboot USB though, stays at Fastboot. Is there another trick? Thanks so much!

use cwm

simsale said:
Oh, thanks so much. I actually did know this from rooting my old phone - I guess I forgot.
It doesn't go into Fastboot USB though, stays at Fastboot. Is there another trick? Thanks so much!
Click to expand...
Click to collapse
It should change to FASTBOOT USB if you are plugged into a computer. If you connected to the computer after you got to bootloader mode, you might have to press volume up or down to get it to switch to FASTBOOT USB Maybe this is the root of your problem. Have you tried multiple USB cables? Is there any crud in the micro-USB port on your phone? It's a little odd that the micro-USB port would break in a manner that charging would still work but not data connections, but I'm starting to wonder if that isn't the case.

lauterm said:
It should change to FASTBOOT USB if you are plugged into a computer. If you connected to the computer after you got to bootloader mode, you might have to press volume up or down to get it to switch to FASTBOOT USB Maybe this is the root of your problem. Have you tried multiple USB cables? Is there any crud in the micro-USB port on your phone? It's a little odd that the micro-USB port would break in a manner that charging would still work but not data connections, but I'm starting to wonder if that isn't the case.
Click to expand...
Click to collapse
OK, I managed to get into Fastboot USB and now have the SDcard mounted. I'll try flashing a new ROM now. Is this one you'd recommend?
http://forum.xda-developers.com/showthread.php?t=1868236&highlight=+rom+
Thanks so much!!
Simone

Can't connect to laptop

I wanted to install a new rom, and so I did all the wipes and formated system, before this I updated my recovery and I think this is why my laptpo dosent recognise my phone once I mountUSB in recovery...any ideas?

dark'em said:
I wanted to install a new rom, and so I did all the wipes and formated system, before this I updated my recovery and I think this is why my laptop dosent recognise my phone once I mountUSB in recovery...any ideas?
Click to expand...
Click to collapse
You got to uninstall the drivers of (Windows 7) for the usb ports from the "device Manager". and reinstall the drivers. Else try to connect to another system. You might be lucky. I had a similar problem and i tried this about 5 times as i had multiple usb ports and wasnt able to pinpoint which one was having the problem. Also uninstall any adb drivers or any other tools related to nexus. then try to reconnect and check it out. Even if this dosent work you might need to reinstall the ROM on your device after doing a complete factory reset/datawipe.

paydy12 said:
You got to uninstall the drivers of (Windows 7) for the usb ports from the "device Manager". and reinstall the drivers. Else try to connect to another system. You might be lucky. I had a similar problem and i tried this about 5 times as i had multiple usb ports and wasnt able to pinpoint which one was having the problem. Also uninstall any adb drivers or any other tools related to nexus. then try to reconnect and check it out. Even if this dosent work you might need to reinstall the ROM on your device after doing a complete factory reset/datawipe.
Click to expand...
Click to collapse
Thanks but I used fastboot and it worked, the problem was with the new recovery

[Q] Unbricked successfully, ADB broken?

Howdy, folks. I recently bricked my tablet thanks to a bad install of CWM, but following Buster's guide I was able to successfully reflash stock firmware and the device runs fine when booted up now.
However, now ADB is not detecting my device. At all. I have tried running the kill-server and start-server commands to see if that would do the trick to no avail. I'm not even receiving an error saying "device not found." Rather, the device listing is left blank whenever I enter the devices command into the command prompt. I can still send commands via fastboot, but I'm concerned that there's something here that I'm missing, or that I have somehow managed to completely bork the motherboard. I have already tried uninstalling and reinstalling the Asus usb drivers, in addition to the ADB drivers/software to no avail.
Does anyone have any suggestions to getting ADB to work for my tablet again? I have scoured the web, particularly these forums, for days looking for an answer, but haven't turned anything up yet. Any help would be greatly appreciated.

Does usb debugging is on?

Graiden05 said:
Does usb debugging is on?
Click to expand...
Click to collapse
Yes, USB debugging is enabled; yes that was the first thing I checked.
Any other ideas?

If You use asus drivers it worth to try universal naked driver.

Graiden05 said:
If You use asus drivers it worth to try universal naked driver.
Click to expand...
Click to collapse
I'll give that a shot this evening.

Graiden05 said:
If You use asus drivers it worth to try universal naked driver.
Click to expand...
Click to collapse
I just installed the naked drivers and tried again, but that didn't work either. Fastboot still works just fine, but I'm still at a complete loss as to how to get adb working again.
Thanks for your help thus far.

Hmm... How windows show tablet when You connect it to PC?

Graiden05 said:
Hmm... How windows show tablet when You connect it to PC?
Click to expand...
Click to collapse
Yeah everything *looks* normal, and appears to be acting normally whenever I have the tablet plugged in. When my tablet is booted up and connected to my pc, I can transfer files to and from with no issue. Also when it's plugged in, there are two different entries under the device manager (one for adb and the other for the tablet itself). It's only when I have my tablet running in bootloader mode that things don't seem to want to work correctly.
I even ran netstat last night to see if there were any programs/services using the same port as adb, and even that turned up nothing. Is it possible that I somehow inadvertently altered the settings on my tablet's motherboard when I installed a bad version of CWM, per my original post?

It shouldn't be posible to brick anything on motherboard with just flash wrong recovery. It might be just "too smart" windows, that reject to use adb driver on same device that alredy used by mtp one. It wasn't a problem before?

Graiden05 said:
It shouldn't be posible to brick anything on motherboard with just flash wrong recovery. It might be just "too smart" windows, that reject to use adb driver on same device that alredy used by mtp one. It wasn't a problem before?
Click to expand...
Click to collapse
It wasn't a problem until I flashed the wrong version of CWM, got stuck in a boot-loop and fixed the problem using fastboot to completely wipe my tablet and start over from scratch.
Edit: I suppose I could try a fresh install of Windows.

Try first remove all drivers and software for tablet. Then install universal naked driver.

Graiden05 said:
Try first remove all drivers and software for tablet. Then install universal naked driver.
Click to expand...
Click to collapse
Update: finally got adb to detect my device. Ended up removing everything Android-related from my desktop and re-downloaded/installed everything, including usb drivers. That did the trick.
Thanks again for the help.

USB driver problems, drivers not being kept

So after trying to find a straightforward guide for installing the USB drivers for my OPO, almost every link says to use the OnePlus One toolkit, so I followed the 'manage drivers' section of the toolkit but for some reason, whenever I come to use my phone with my PC, the drivers seem to wipe themselves out! After I've done the initial driver installation, everything works fine, but after a day or 2, when when I plug my phone in, it will show 'unknown device' or it will show 'A0001' but with an exclamation mark next to it in the device manager and my phone isn't recognized. I'm using windows 7 x64 and the original red OPO cable.
I must be doing something wrong with these drivers, does anyone have a guide for deleting old drivers and reinstalling drivers for the OPO?
Edit: Ive reinstalled them again using the toolkit guide but I dont know if they will keep again, either way, im flashing blisspop now, maybe its an issue with 5.0 stock rom or something?

donk165 said:
So after trying to find a straightforward guide for installing the USB drivers for my OPO, almost every link says to use the OnePlus One toolkit, so I followed the 'manage drivers' section of the toolkit but for some reason, whenever I come to use my phone with my PC, the drivers seem to wipe themselves out! After I've done the initial driver installation, everything works fine, but after a day or 2, when when I plug my phone in, it will show 'unknown device' or it will show 'A0001' but with an exclamation mark next to it in the device manager and my phone isn't recognized. I'm using windows 7 x64 and the original red OPO cable.
I must be doing something wrong with these drivers, does anyone have a guide for deleting old drivers and reinstalling drivers for the OPO?
Edit: Ive reinstalled them again using the toolkit guide but I dont know if they will keep again, either way, im flashing blisspop now, maybe its an issue with 5.0 stock rom or something?
Click to expand...
Click to collapse
I had similar issue with lollipop ROMs, didn't find any solution except flashing fastboot images of CMOS12 or simply downgrading to CM11S.

Mr hOaX said:
I had similar issue with lollipop ROMs, didn't find any solution except flashing fastboot images of CMOS12 or simply downgrading to CM11S.
Click to expand...
Click to collapse
Fair enough, well i'm thinking I may move back to CM11S if things don't work out on Blisspop. If I turn off USB debugging and then switch to camera (PTP) mode and then back to MTP mode, my phone then connects fine. I wanted it to connect so I could copy my Titanium backup files off the phone and onto the PC. In the end, my mate told me about Airdroid and I managed to download them through that as a ZIP file. For some reason, the titanium backup folder isn't visible from your computer, I tried copying it to the DCIM folder and it just gave me a 1kb file. I also tried a new folder called backups and it was empty when I looked on my PC, but the files were visible when using Airdroid and also when I used a file browser on my phone.
Weird stuff!

Just wanted to bump this and see if anyone has a solution or even just an explanation.
Whenever I plug my OPO into my PC (with the original cable), the device, A0001 is found but is shown in Device Manager with an exclamation point. If I then right click on it and chose uninstall, and then reconnect the phone, it will connect and work fine for MTP/PTP modes. If I put USB debugging on, the MTP doesn't always work after. But no matter what, if I shutdown my PC, and then come to connect the phone the next day etc, I have to do the uninstall of the driver then reconnect for MTP to work. Pretty frustrating!
Anyone know why the phone isn't remembered by my PC correctly? I'm on Windows 7 x64 if that means anything.

I'm moving back to stock ROM soon so I'll see then if its something to do with the unlocked bootloader or using a custom ROM. I'll report back if I have any luck

Bumping this again, its still the same on 6.0. I don't fancy moving back to stock ROM, I like CM over Cyanogen OS, but this problem is really frustrating. Every single time I connect the phone to the PC, it will come up as A0001 but with an exclamation mark next to it in Device Manager, if I right click and uninstall the driver, then reconnect the phone, it works fine then. But if I restart my PC, it does the same thing where it cant find the right driver for the phone.
Is there anything I can try to fix this?