I mispressed in twrp earlier today when my phone speaker stopped working and none of my calls went through, SMS and everything else worked flawlessly tho.
Well, the thing is now, i've deleted all the data on the phone incl. internal storage and can't mount "USB" in either ADB or twrp (what's left of a functioning TWRP)
Driver's on my system says they cant recognize my phone and i've tried all the drivers and tips i found online with Windows 8.1 USB3 drivers ect.
Tried connecting with fastboot and adb in both OSX virtual machine, booted a ubuntu PC and on Windows 8.1 both on my stationary and laptop.
none of them can connect to the phone :/
Any ideas ?
downloading a RUU now and will see how that goes, 1gb left to download from a slow server...
EDIT: RUU didn't help at all, connection error..
EDIT 2: GOT IT WORKING ;D
Fix:
- Install Windows XP 32bit on a standalone partition and run Fastboot commands to push a new recovery into the phone, boot into recovery and mount storage to transfer ROM onto internalstorage for install.
Related
NOTE: my problem is not like the other two threads where usb mass storage dosent work...
I can successfully mount my sd card on my pc via the notification ITS just the problem of developing/debuging connections made between G1 and PC
Somebody please help me I have adp1 when I bought all was fine but recently, don't know why bubuging dosent work means all adb and fastboot commands don't work on my g1 I have tried re installing the drivers but they fail to install so it hangs at adb devices or saying waiting for device. Also I have tried installing ubuntu to do that but here too it says the same stuff waiting for devices
Even the usb debug mode is enabled....
I have also tried flashing rc29 then other jf versions but can't flash system images via fastboot even flashed HSPL again n now I am trying to flash system image via update.zip
Is it
"format SYSTEM"
"Write_raw_image system.img PACKAGE:SYSTEM" SOMETHING LIKE THIS found in JF update script what I have to include in update script ???
Please help...[/B]
I have the same problem, I can mount the sd card but now the G1 won't let me use adb or fastboot on two computers where it previously did : /
go into control panel and go to Device Manager and try uninstalling the usb mass storage device that corresponds with your device, then unplug and replug the usb to your phone and let it reinstall the drivers and see if that fixes it...
-BMFC
you can't write_raw_image:SYSTEM through and update, I've tried it before and it fails (I'm trying to determine why). I'd recommend flashing another rom (you can still use recovery, right?) and then trying. Try JF 1.51 since it's known good.
What did you do to the phone before loosing adb and fastboot.
Also, have you tried "adb root" and then "adb remount"?
sangeet.003 said:
NOTE: my problem is not like the other two threads where usb mass storage dosent work...
I can successfully mount my sd card on my pc via the notification ITS just the problem of developing/debuging connections made between G1 and PC
Somebody please help me I have adp1 when I bought all was fine but recently, don't know why bubuging dosent work means all adb and fastboot commands don't work on my g1 I have tried re installing the drivers but they fail to install so it hangs at adb devices or saying waiting for device. Also I have tried installing ubuntu to do that but here too it says the same stuff waiting for devices
Even the usb debug mode is enabled....
I have also tried flashing rc29 then other jf versions but can't flash system images via fastboot even flashed HSPL again n now I am trying to flash system image via update.zip
Is it
"format SYSTEM"
"Write_raw_image system.img PACKAGE:SYSTEM" SOMETHING LIKE THIS found in JF update script what I have to include in update script ???
Please help...[/B]
Click to expand...
Click to collapse
I had a problem with adb awhile back it was doing the same thing what I did was read the hell out of threads and I used this tool called USBDeview. I opened up the program and anything that had android or htc I uninstalled all the drivers, then I rebooted my cpu and plugged my phone into usb cord and it worked. Here's the link to the app http://www.softpedia.com/get/System/System-Info/USBDeview.shtml try it out its worth a shot
lol. Funny how you guys try and help him 6 months later.
Im sure he figured it out by now since he had no follow up for such a long time.
some ppl just dont read thats sad...u rght now they want 2 help..maybe they need help themselves
Some help is better then no help
try this
you should uninstall it and the reinstall it but this time pick chose from Pacific location or something like that and chose the htc adb interface device with the green icon i believe it is like the second one or something on it this is on xp computers i forgot what it looked like on my vista computer
I have two phones. ADB works on one but not the other. I device manager, HTC Android Phone USB device shows up for both but ADB interface only appears for one phone but not the other.
What gives?
maybe u should try the steps again------->>> http://forum.xda-developers.com/showthread.php?t=532719
Hey, i have had this problem for a bit now, but it is really starting to bug me.
I have a dual boot computer, one is fedora, the other windows 7. When i decided to root my nexus one, i did it through windows, so i got the SDK, installed the drivers and rooted the phone.
Some time later (after flashing and restoring from desire rom back to CM 5) my computer can no longer recognise the device properly Windows will say it fails to recognise the device (code 43), and will not let me re-install the drivers. Saying they are up to date even after i uninstall the drivers then re-install them.
I have given up on fedora too, since no command ever seems to work on fedora beyond yum install xxx. Trying to get "fastboot devices" in fedora brings up "command not found" or something to that effect.
I wouldn't be too worried, but not everything comes as an update.zip, and i would like to try out the undervolted kernel some time.
Note: i can still mount the SD card fine.
EDIT: i can Mount the SD on Fedora, but not windows.
Things you can try out:
1. Completely uninstall and remove the driver from the system and connect the phone and install the drive when prompted. (try in safe mode as well)
2. Try other USB ports.
3. Try turning off USB debug, connect the phone and then turn on USB debug.
4. Try on another PC and rule out any problem with ur phone.
5. Reinstall Windows!!!
Thanks for the suggestions, i tried everything there short of re-installing windows.
As soon as i plug in the device windows will bring up the error message, it will not call it a nexus one, an unknown device. Any attempt to install the new drivers and windows will say that better drivers are already installed.
I also figured out that it will not work on fedora because it is not configured, but the only guide to fastboot and linux i have found is for ubuntu, and some of the commands wont work on fedora.
I tried it on another computer, an XP, it would not install on there either, i tried to use my mums N1 afterwards to see if it would install, it didn't but there are a number of reasons why it may not.
Any other suggestions? or could someone point me to a fedora guide for fastboot?
Im used to being able to remove the sdcard on my previous phones and did not forward think what would happen if a flash went bad on my htc one. Basically, I tried wiping and flashing ARHD 10.0 and I believe I should have updated the radios first. In any case, I did a wipe and now have no os to boot. I can get into the bootloader and fastboot usb just fine. I have cw touch recovery and can run that fine also. When in recovery I cannot mount the sdcard to move files. When I try to adb push them, I get the error that the device is not detected. I have installed htc sync. In my device manager it shows an "Other device" with "One" underneath and an exclamation mark - drivers not installed. I would have thought HTC sync would have fixed this but I even tried the google adb usb driver and windows doesnt like it. I have this problem on WinXP 32-bit and also the same issue on my Win7 64-bit. If I can get ADB functioning, I think I can fix this and really dont want to resort to the RUU via fast boot. What am I missing? Thanks.
This is getting frustrating now, no matter what I do I get this message: "USB Device Not Recognised"
Here is what I have tried:
Connect on android
Connect as MTP
Different USB cable (5 to be precise)
DIfferent USB port
WebOS recovery
Reinstall Novacom Drivers
Restart PC
Restart Touchpad
I have no idea what else I can try, no matter what I do, this annoying message persists!
Platform? ROM?
What's the ROM you are using? Also, which platform is your PC on? Linux/Windows/Mac?
In case you are on some 5.1.x ROM, I would recommend a nandroid backup and flashing a known 4.4.4 ROM which might tell you if it's your hardware or just Android. If you were on a stable ROM earlier where USB was working, then I would recommend trying that. :fingers-crossed:
Similar Issue.
My TP actually works (sort of) via MTP but it frequently disconnects when transferring files and freezes my explorer window. I tried to use Mass Storage on PAC KitKat FINAL and windows reports that it can't find a driver for it and when I try to reboot into recovery it only mounts a tiny SD Card partition of some 800mb. This probably won't be answered but whatever. I've been trying to solve this issue the past 8 hours. I have nothing to lose.
Blaze Viper said:
My TP actually works (sort of) via MTP but it frequently disconnects when transferring files and freezes my explorer window. I tried to use Mass Storage on PAC KitKat FINAL and windows reports that it can't find a driver for it and when I try to reboot into recovery it only mounts a tiny SD Card partition of some 800mb. This probably won't be answered but whatever. I've been trying to solve this issue the past 8 hours. I have nothing to lose.
Click to expand...
Click to collapse
hi, had some trouble with my win7 PC detecting touchpad (using JC's 4.4 Cm11), although ADB was installed - I couldn't see it as a storage drive despite the driver installing. touchpad was connected via MTP.
what worked for me was on windows - go to Device Installation Settings (drivers) and choose never install from windows update. Then under device manager -> android device -> uninstall. reconnect and it should work properly. hope that helps
I have had a very eventful few hours and I'll do my best to explain. Earlier this morning I was rooted, twrp installed and running FreedomOS. I had this bright idea of flashing a file I had downloaded from the OP3T website. It was a firmware file (either the first option, the option before OB5). Everything was running smoothly until I got home and tried using fastboot at which point it just sticks on waiting for device. All normal options are checked (adb files installed, debugging selected, the works), but now I can not use fastboot what so ever. I did at one point sideload an OTA using adb sideload (filename.zip). I have tried just about every adb option I can think of to include: 15 second ADB and minimal adb and fastboot. I even deleted the OP3T drivers from my computer, reinstalled those drivers. I followed an article through technobuzz: http://www.technobuzz.net/download-oneplus-3-usb-drivers/
http://www.technobuzz.net/setup-adb-fastboot-drivers-for-nexus-oneplus-samsung-or-any-android/
I have been using adb and fastboot with no issues up til Open Beta 5 and now my PC and another PC is giving me crap and it's iritating the %%%k out of me.
adb reboot recovery works, adb devices work - showing that the device is connected. I checked the device manager and only found the portable devices. It's like my computer somehow magically deleted the adb driver and will not allow me to install an adb driver. I have no logs to check out....15 second adb was suppose to place a log file on the desktop, but it doesnt....it wont install
Here's what Im on:
OB5 (7.1.1) with stock recovery. I can not use fastboot commands. Here are some pics
http://imgur.com/a/y7iFE
http://imgur.com/a/SVVMg You should see something that says, "Android Device or ADB", but nothing - just MTP
http://imgur.com/a/62msw
I'm using windows 10, device signature is off
Essentially I just want to be able to fastboot flash TWRP and gain root.
Has anyone else experienced any kind of issues with OB5 and adb/fastboot
Btw I had the entire Android SDK installed on another computer and that did not work either....Any assistance would be greatly appreciated. I'm talking about you @redpoint73, lol
Oh boy, I've been summoned! I have to say, I'm not anywhere near knowledgeable yet with the 3T as I was with my past devices. But I'll try.
I assume you are properly trying fastboot commands while in fastboot mode (not in OS or recovery)? I assume so, since you already said it worked fine before the update. But it never hurts to ask the obvious, as a lot of folks forget that adb and fastboot work a bit differently (fastboot only in fastboot mode, adb only in OS or recovery - debugging only needed for adb, not fastboot).
Do you have the OP3T drivers installed? These are the files that Windows always opens whenever I connect the phone (while booted into phone OS), select File Transfer, and it gives the option to open the folder. Although I don't think you even need the drivers for fastboot to work. I unlocked the bootloader and flashed TWRP before I ever installed the OnePlus drivers. The generic fastboot drivers worked fine. But it's worth a try, to install the OP drivers.
I don't even know where to begin or how to reply to what you just said @redpoint73. I haven't attempted to use adb/fastboot commands since yesterday, so i have no idea as to rather it will work or not. If you have teamviewer, I can give your access to a backdoor to show you as it's easier to show then explain. Have you ever noticed when you download a zip from here: http://downloads.oneplus.net/devices/oneplus-3t/#title-section
it never saves the file as Open Beta 3, 4, or etc. It saves the file as this long-named file.zip rather than being something easy to understand. Im able to understand it now, but a few moments ago I wasnt. I "have" downloaded the OP3T drivers on multiple occasions with no success to to fastboot only adb. My computer recognizes the device though. When I go into device manager checking things out. I will have an option that says, "portable devices". when you select that option you'll go across through some contextual menus where you wind up seeing MTP. You should see MTP if you successfully installed the OP3T devices, but at the same time you should be able to see an option that says something along the lines of ADB or Android Debug Bridge, vice versa. My computer does not say that and I have no idea where to go from here. I have no logs or anything helping me out, so it's like finding a needle in the haystack. I do know that I have all of the prereq's such as debugging selected from developers options within the phone, device signature turned off through Windows, adb/fastboot installed, OP3T drivers installed - you know the works you usually need in order to get everything working right. What I might end up doing is just reformatting my entire laptop, installing a fresh copy of windows, fresh copy of adb/fastboot and going from there. My bootloader is unlocked and has been since I've owned the device. As of right now I'm on OB5 with stock recovery. Yesterday I tried three times to sideload one of the downloads from this site: http://downloads.oneplus.net/devices/oneplus-3t/#title-section
. However, my phone would end up saying, "installation failed" when Im in sideload mode. I'm thinking that might have something to do with a botched download from the OP3T server.
Looks like you found your solution here: https://forum.xda-developers.com/showpost.php?p=72046709&postcount=20
Fastboot/adb is usually as simple as reinstalling drivers, etc. as opposed to reformat the PC as you were considering. Reinstalling adb/fastboot was a good idea also, as I don't think I would have thought of that (although it makes perfect sense). So good job working it out!