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.
Related
Hello,
My phone had been experiencing a host of problems, so I formatted all partitions. (/sdcard, /system, /cache, /data, /boot)
I planned on using the "mount USB storage" to transfer a copy of CM10 to the sdcard and flash that from recovery,
but the device does not appear in my computer or device manager in windows, and Linux doesn't see it either.
In it's current state, it's soft bricked, is there anything I can do to fix it?
It now says "fastboot mode - no boot or recovery IMG", and I have no drivers to communicate with it under adb or fastboot.
Thanks,
-Max
Use this guide to recover your device.
Thanks, but my issue is that I can't install the drivers, could it be a windows 8 thing?
Everything seems to require that I enter USB debugging first, which is impossible for me now.
I think the ADB driver is impossible to install, unless I can do it over CWM, and every fastboot driver I've tried has failed too.
How did you erase everything? Was it through fastboot or CWM?
I did it through CWM. I had just recently installed Windows 8, and hadn't connected it since then so no drivers are installed.
maxmalynowsky said:
I did it through CWM. I had just recently installed Windows 8, and hadn't connected it since then so no drivers are installed.
Click to expand...
Click to collapse
In my opinion, its safer to erase everything from fastboot.
If fastboot recognizes your phone, then you can erase or install whatever you want.
If fastboot does not recognize your phone, then you can't erase it. You then need to find out why. Bad drivers, wrong folders, bad usb cable...In the meantime you phone will still work.
On my windows 7 box, under the administrator account, it took a while to set up the drivers, don't know why, but windows would not take it at first.
Maybe you can mail the phone to a xda member to get it going again...
maxmalynowsky said:
Hello,
My phone had been experiencing a host of problems, so I formatted all partitions. (/sdcard, /system, /cache, /data, /boot)
I planned on using the "mount USB storage" to transfer a copy of CM10 to the sdcard and flash that from recovery,
but the device does not appear in my computer or device manager in windows, and Linux doesn't see it either.
In it's current state, it's soft bricked, is there anything I can do to fix it?
It now says "fastboot mode - no boot or recovery IMG", and I have no drivers to communicate with it under adb or fastboot.
Thanks,
-Max
Click to expand...
Click to collapse
I am sorry to hear about your phone. You are not alone I did the exact same thing a few days ago. Don't beat yourself up I have done that enough for both of us. Through my research into this i found there a few things that you might try (I don't own a PC so I haven't yet)
To get the drivers, I read a couple people had success downloading PDANet and installing them that way. I think they are located in "legacy drivers"
From the original "root, un-root" thread for your model download the stock boot img and try to flash that using ADB
follow the instructions to un-root and start over with rooting.
I also was going to look into Wug's toolkit (in the dev section) it looks like that may be an easy option to flash a working boot and recovery img.
I hope this helps please let me know.
I gave up to quick and ordered a GNex but I'm not touching that until I get my NS4G sorted out (my faith in my abilities is shaken and I could not handle bricking a brand new phone). I will be going to a friends house tonight to use their PC and try to get my NS running. I will be back to let you known what works and what doesn't. If you try or find anything would you please post? Two heads working on this issue are better then one. Thanks and good luck.
Sent from my temp PC36100 while my Nexus is sick using Tapatalk 2
*** success ***
The solution was an easy one thanks to our developers, the hard part was finding the answer and of course, beating myself up for making the mistake in the first place. Here's what you do...
Leave your phone with the battery out for a while. Download "Wug's Nexus Toolkit" In found it in the NS4G dev section but I believe it covers all variants (not sure which you have) at the select your model and custom JB ROM download the drivers (from the actual toolkit) turn on, plug in and select flash stock img, relock boot loader, pick the stock ROM you want and press go and your phone will be flashed and reboot in under a minute. Sign in on your phone (the toolkit should auto populate your new ROM and then just follow the steps to unlock, flash and install a custom recovery then pick any ROM you want and start over.
I really hope this helps you as I'm sure you find the whole situation as stomach-churning as I did. Please PM me and let me know.
If it does work please leave a thank you or donation to the dev for creating such an awesome tool. Again, good luck hope you get your nex back online.
Sent from my Galaxy Nexus using Tapatalk 2
The Nexus Toolkit was actually my first option, it's helped me out before. I went back and tried installing the drivers using the 3 options it gives. # 3 & #2, RAW and Samsung signed drivers don't work. Option #1, the PDAnet drivers didn't work last time I tried it (all 3 options require USB debugging enabled). However, I just tried #1 again by turning on the device in CWM and that seemed to work, but I'm not sure (installation went according to the guide). However, once I tried to flash stock img, it gave me errors about not being able to reach the device in fastboot. Can you elaborate on those two steps, driver installation and flashing? As soon as I can get fastboot to recognize my device I can pretty much take it from there. BTW, I've got a i9020A and using NRT 1.6.1; and what's the significance of leaving the phone with the battery out for a while?
Mine was in the box with the battery out overnight. When I had access to a PC and plugged it in it said something at the bottom of the fastboot screen in grey that it did not before and I actually think that was the trick (System normal or system OK or something like that and when replugged to the USB the message just repeated and stacked up on the lower left of the fastboot screen). Try letting the phone sit for a while. All driver options failed for me except the tool kit.
Sent from my Galaxy Nexus using Tapatalk 2
Tried your fix, but the phone remains unable to have it's drivers installed. It's always giving "USB device not recognized" errors no matter what I do. I'm just going to shelf it and accept my loss. Thanks for the help though!
edit: Tried using some Linux tools, much greater success! This guide finally got my device listed under fastboot: http://forum.xda-developers.com/showthread.php?t=1447040
edit2: Up and running again with the android-tools-fastboot package for Linux and a standard stock image flash: http://forum.xda-developers.com/showthread.php?t=1572307
I am so glad to hear it! I stayed subscribed to the nexus s forum just to keep up on your progress and to try and help. Good for you.
Sent from my Galaxy Nexus using Tapatalk 2
I am attempting to flash TWRP so that I can root and flash Cromi X to my tablet. ADB works fine, restarts/reboots into recovery, recognizes device. Fastboot does NOT see my device, does NOT reboot, and I am left stuck at "waiting for device" when I attempt to flash TWRP while in fastboot. In addition, my computer recognizes the TF700 while it is in launcher, but when I boot it into the bootloader/flashboot mode it does not recognize my tablet. I have attempted multiple times in multiple locations on my computer to get it to install & use the android_WinUSB.inf driver, but it refuses. I have uninstalled and reinstalled the drivers while the tablet is in on mutiple times. I don't know what else to do at this point; please help.
Device Details: ASUS tf700t, 10.6.1.14.8 firmware installed, unlocked, no root
Computer: Windows 7 x64
GoliboiVolk said:
I am attempting to flash TWRP so that I can root and flash Cromi X to my tablet. ADB works fine, restarts/reboots into recovery, recognizes device. Fastboot does NOT see my device, does NOT reboot, and I am left stuck at "waiting for device" when I attempt to flash TWRP while in fastboot. In addition, my computer recognizes the TF700 while it is in launcher, but when I boot it into the bootloader/flashboot mode it does not recognize my tablet. I have attempted multiple times in multiple locations on my computer to get it to install & use the android_WinUSB.inf driver, but it refuses. I have uninstalled and reinstalled the drivers while the tablet is in on mutiple times. I don't know what else to do at this point; please help.
Click to expand...
Click to collapse
Are you using windows?
Did you try this?
Transformer Toolkit v2.0.1
Root your device with motochopper: http://forum.xda-developers.com/showthread.php?t=2230763
and from the playstore download and install goomanager and from goomanager install TWRP.
Then from TWRP flash CROMi-X
GoliboiVolk said:
I am attempting to flash TWRP so that I can root and flash Cromi X to my tablet. ADB works fine, restarts/reboots into recovery, recognizes device. Fastboot does NOT see my device, does NOT reboot, and I am left stuck at "waiting for device" when I attempt to flash TWRP while in fastboot. In addition, my computer recognizes the TF700 while it is in launcher, but when I boot it into the bootloader/flashboot mode it does not recognize my tablet. I have attempted multiple times in multiple locations on my computer to get it to install & use the android_WinUSB.inf driver, but it refuses. I have uninstalled and reinstalled the drivers while the tablet is in on mutiple times. I don't know what else to do at this point; please help.
Device Details: ASUS tf700t, 10.6.1.14.8 firmware installed, unlocked, no root
Computer: Windows 7 x64
Click to expand...
Click to collapse
monecani's advice should work, although it would be good to have fastboot access to your tablet.
Weird - it seems the ADB drivers work but the fastboot drivers don't.
Try the drivers attached?
berndblb said:
monecani's advice should work, although it would be good to have fastboot access to your tablet.
Weird - it seems the ADB drivers work but the fastboot drivers don't.
Try the drivers attached?
Click to expand...
Click to collapse
Well I had tried motochopper around 20x before (and sadly, I am not exaggerating there) without it working once, but I felt that I should at least give it one more shot before saying I couldn't use it and of course now that I had asked for help it does work. lol; the IT curse strikes again. Thanks for that, monecani.
The drivers, on the other hand, are not working. :/ Windows is letting me try to install them now at least (before it was telling me there was "no compatible drivers" when I was literally having it select the ASUS specific ADB USB drivers, or just telling me that it had determined that my usb drivers that were in no way functioning were completely up to date), but then it fails install and says "This device cannot start. (Code 10)". I was able to install the drivers you gave me when the device was in launcher, but they didn't help me in fastboot, and actually interfered with my device being recognized properly by anything. I had to roll back the drivers to run motochopper.
I kinda agree with you on fastboot being something I don't strictly need, but would still be a good idea for me to have access to. Plus, I'm that special kind of person who cannot let something just be broken. It drives me crazy to know that something's wrong, even if I almost never use it, or even never use it.
Guys, i need some help.
I was able to install the Viper ROM without any problems. But when i did a factory reset, i'm now stuck on the HTC ONE screen. I can still get to the recovery without issue. But i can't reflash it because i don't have anything in my sdcard to flash.
I found somebody had this issue too:
http://forum.xda-developers.com/show...2518736&page=3
I'm trying to push the rom into my sd card but i can't get my computer to recognize my phone! It's having the HTC MCP device driver issue (code 10). Tried installing HTC sync and that didn't help. Tried uninstalling the driver, but it won't allow me to install driver after i uninstall. Tried to update the driver but Windows is saying driver is up to date and won't let me update. Without getting my phone to be recognized by my computer, i can't push anything into my phone.
I posted in the Viper forum and i was told that maybe i need to reflash the boot.img since I'm on S-On. Which i think is the case.
The thing is i can't flash boot.img because of this MTP issue. I tried different cables with different USB ports. Nothing's working. When i plug in with HTC One, it recognizes fine. But when i plug in with One S, it's back to that MTP issue.
Anybody has any suggestions?
Thanks!
kc73837 said:
Guys, i need some help.
I was able to install the Viper ROM without any problems. But when i did a factory reset, i'm now stuck on the HTC ONE screen. I can still get to the recovery without issue. But i can't reflash it because i don't have anything in my sdcard to flash.
I found somebody had this issue too:
http://forum.xda-developers.com/show...2518736&page=3
I'm trying to push the rom into my sd card but i can't get my computer to recognize my phone! It's having the HTC MCP device driver issue (code 10). Tried installing HTC sync and that didn't help. Tried uninstalling the driver, but it won't allow me to install driver after i uninstall. Tried to update the driver but Windows is saying driver is up to date and won't let me update. Without getting my phone to be recognized by my computer, i can't push anything into my phone.
I posted in the Viper forum and i was told that maybe i need to reflash the boot.img since I'm on S-On. Which i think is the case.
The thing is i can't flash boot.img because of this MTP issue. I tried different cables with different USB ports. Nothing's working. When i plug in with HTC One, it recognizes fine. But when i plug in with One S, it's back to that MTP issue.
Anybody has any suggestions?
Thanks!
Click to expand...
Click to collapse
same problem ....sm1 please help
hassam_2010 said:
same problem ....sm1 please help
Click to expand...
Click to collapse
Fixed it!! i used CWM sideload. Go into recovery, then go into sideload. Connect your usb, then open adb. type "adb devices" just to make sure you're connected.
Now, you want to flash the ROM again. Download the zip file and put it into the same folder as adb. then type this command: adb sideload <filename of update.zip> and you're good to go!
Let me know if you have any questions!!
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?
Hello!
I have tried to upgraded my phone to Lineage 18.1 but it did not work.
This is what I did so far:
1) Installed the NEWEST TWRP and unfortunately I have deleted the OS. After that, the USB connection worked fine and I was able to see all files on my phone.
2) I've found a stock recovery.img that I have used and then the problem started. After installing that recovery.img file now I have TWRP (older version) 2.7.0.0 and:
a) when connected through USB , my computer does make sound, but it does NOT recognize my phone any more. Yes, I do have the newest USB drivers installed
b) when connected through USB and when I run this command: fastboot devices, then it DOES shows my device number, but it DOES NOT any devices using adb command.
c) when booting into fastboot, the phone shows just the black screen with the android faded icon.
d) I can boot into TWRP but there is no system or recovery files in there and it look like it's just useless.
I'm not sure what to do next. It looks like the phone is soft-bricked.
Any help will be appreciated.
Thank you
the first thing i would try is flashing twrp 3.6 (the newest) using fastboot. not sure why you would flash an old recovery version. if data recovery is not an issue then the opo is even fixable after a hardbrick (i used to have it). i used the color os method but that was ages ago. now there is a slightly easier way somewhere here on xda if you want the opo to in out of the box condition.
maybe try the whole thing using a secondary old laptop (if possible) or a virtual machine. otherwise i have no idea. sounds like a lot of trial and error might be needed. good luck.