Hello to everyone.
I'm having a problem with my hero. I've just updated OTA with the original 2.1 OS from 2.73.405.5 to 3.32.405.1, and I lost the USB conectivity. There is no notification coming up when I plug the USB cable. I've tried different OS and cables and nothing seems to work. The phones can be charged through USB and the PC recognize it when I turn it on holding the volume down button and it says "Fastboot USB". Does anyone knows how to fix it or go back to the previous version, given that I don't have a propper USB connectivity?
By the way, I've contacted HTC support and they told me that I had to send the phone to the repair pipeline. I bought it through ebay, and I live in Chile, so that is not a real option to me.
same problem with me ! i hav no idea what the problem is happend when i flashed a 2.1 rom aswell!!
Can you get adb working? There are guides in various places.
If adb works, you can be sure it's not the whole usb playing up.
tried flashing 3 roms, modaco, radug and now kimera... none working.
can connect in fastboot, it shows up in device manager as android 1.0
ive tried 3 different usb cables and 4 differet pcs, still there is no response on my phone !!!
using villian rom 10.0 rite now.
okay it boots up into fastboot and fastboot usb shows up on the screen in red,
BUT when i use the "adb devices" command in adb it doesnt show the device,
it is showing as android 1.0 in devices and printers (windows 7)
Try deleting all the drivers using usbdeview (google it) and let windows re-install them when you boot into the custom rom. Have you tried turning on USB-MS in AmonRA recovery?
Another thing would be to try a non-2.1 custom rom and see whether that makes a difference (would be very surprised).
I think it is not a windows driver problem, because I've tried several USB cables and PCs, even a MAC, and nothing seems to work. I've tried to go back to the original 1.5 using the HEROIMG.zip method, but wont let me and says I have a newer version so it cant go back.
I think the only resource left for me is to send it back for repair... to bad.
ffelis said:
I think it is not a windows driver problem, because I've tried several USB cables and PCs, even a MAC, and nothing seems to work. I've tried to go back to the original 1.5 using the HEROIMG.zip method, but wont let me and says I have a newer version so it cant go back.
I think the only resource left for me is to send it back for repair... to bad.
Click to expand...
Click to collapse
I would hold off for now from sending it back.
If fastboot shows it up, then there's still hope. That means the hardware is fine. I remember spending many hours helping someone with this issue over at http://hero.modaco.com (look up my posts as username pulser, and it was early 2010 IIRC).
I can't remember how it got resolved. But if you can use a goldcard, you can try and roll it back to 1.5 using HEROIMG.zip. Without goldcard, it won't work
ffelis said:
I think it is not a windows driver problem, because I've tried several USB cables and PCs, even a MAC, and nothing seems to work. I've tried to go back to the original 1.5 using the HEROIMG.zip method, but wont let me and says I have a newer version so it cant go back.
I think the only resource left for me is to send it back for repair... to bad.
Click to expand...
Click to collapse
I have the same problem. you are able to solve?
I installed the original ROM 1.5, but are not able to restore the original recovery
I have the same issue Tried on different comps and on both XP and 7...
Btw what do you mean with the goldcard? I still got my original nand from back in august 2009..
bump, anybody?..
Try a ROM reset,
Menu > Settings > Privacy > Factory data reset.
This will erase all settings on the phone to go back to default settings so please make sure all your data is backed up. (Numbers et al)
Related
My vibrant got soft bricked yesterday, I am able to get it into download mode and I have ODIN all lines up to revert to stock, but windows 7 64bit says USB device not recognized. I have tried everything to get it to read. I have tried installing every driver i could get my hand on and i just cannot get the computer to recgnize my phone! Any help would be greatly appreciated.
I have the exact same problem. I updated my Vibrant using Kies Mini for windows 7 64bit. After the installation, my phone restarted, the welcome logo and S came up. After that the screen went black and it vibrated every 5 seconds. The 4 touch controls lit up if i touched them and they stayed lit.
I got into recovery mode and clear all data and format my microUSB as well but it wouldn't solve the problem.
I got into download mode but my Windows said USB device not recognized CODE 43. I tried to manually install Samsung Android USB driver but I got error code 10.
so I couldn't ODIN it back.
Can anyone help?
You're both sure you're using the right Odin (for 64)?
This is weird.
I Just tried again today and my computer recognized it instantly. I was able to flash to stock 2.1
What I did was insert my sim card in the phone today. Yesterday I didn't put my sim card in.
Another way to do it I've realized is to try to use a computer with xp on it and odin 1.7 (I believe). The newer windows vista, 7, etc. Are a lot more picky and difficult to work with sometimes.
Sent from my SGH-T959 using XDA Premium App
Make sure you installed the Samsung driver that is for 64 bit.
Then, make sure you have admin rights, sometimes depending on how the computer was set up you may not be high enough on the root directory. This is especially true when one family is using the same computer and all have their own personal account/profile. If both of those things are ok and you are sure, Then:
Install this This is what i am using on my win7 64 pro i know it works. So, if this does not work then I would guess it is your users rights you haven't resolved yet.
Good luck
Yeah I tried 3 different computers. 2 with xp and the original one in my post, nothing worked. I figured i was screwed so i just went to use the insurance i had on it but they wouldn't let me because it isn't broken lost or stolen. They told me to contact tmobile. So I did. I went onto tmobile.com and chatted with someone who had me try to get it into the recovery screen that a previous poster said he was able to do but i couldn't get into it so he said we could exchange it. I gave him all the info and he sent one out.
steven1193 said:
Yeah I tried 3 different computers. 2 with xp and the original one in my post, nothing worked. I figured i was screwed so i just went to use the insurance i had on it but they wouldn't let me because it isn't broken lost or stolen. They told me to contact tmobile. So I did. I went onto tmobile.com and chatted with someone who had me try to get it into the recovery screen that a previous poster said he was able to do but i couldn't get into it so he said we could exchange it. I gave him all the info and he sent one out.
Click to expand...
Click to collapse
I've done the same with my phone. Talked to a TMobile rep, they diagnosed it as a USB port issue. New phone on the way.
I had the same issue on my computer with any of my USB 2.0 ports. Thought what the hell, I'll try plugging into my USB 3.0 port and BAM! It worked.
Have been on Gingerbread with HTC unlock.
Did 1 try of the Bear s-0ff, and it only booted to green Bear screen.
Did boot image install with PH98IMG in hboot, but it won't take
a recovery done with PH98IMG. Does not charge with any cable nor
does any computer see the phone. Fastboot does not go to fastboot-USB
on any other computer either. It will boot into the rom that was on it,
but not recovery.
Please suggest ideas to get USB to connect for charge or fastboot again.
Thanks.
Bump.
Similar problem here, although S-OFF, ICS leaked firmware, and Nils Business ICS 3.4 running fine. Phone charges from outlet, but cannot connect to PC, fastboot USB, charge mode or drive mode. Is it hardware?
If I try to connect and fail, then reboot, the connection dialogue comes up even if on the AC adapter, and if I then connect to PC, I get pulsing "USB Device Not Recognized" messages, but the "drives" don't connect (and the drivers *are* properly installed.)
For what it's worth, I *can* access the cards (internal and external) in Amon Ra 3.15; I *can* run a Nandroid and a restore. I can even run adb via wifi, I just can't connect to PC. However, after trying to do so, then rebooting, the handset things it's connected if I'm plugged into AC.
Really bizarre.
I'm having this issue at home on my windows 7 pc, but at work, on my windows XP machine, it has no problem recognizing the device. At home it just says "Unable to recognize device". I tried using widgetsoid, but that didn't work either.
Don't know about anyone else, but for me, at least, it appears to be a hardware problem. Rolled back to stock 2.01 RUU and still unable to connect, and unit thinks it's connected when it's not. Rolled back forward and will learn to deal with it or return for warranty claim.
Dumped down the innertubes from my Rezound.
no usb
Followup:
Con247 sent me suggestions, directions, and a flashable
to try and get my Zound to charge again. No luck.
I called VZN support, got a nice refurb, and am waiting to
see if old one is accepted or charged back to me.
michaelbsheldon said:
Followup:
Con247 sent me suggestions, directions, and a flashable
to try and get my Zound to charge again. No luck.
I called VZN support, got a nice refurb, and am waiting to
see if old one is accepted or charged back to me.
Click to expand...
Click to collapse
Yup. Con was helping me out, too, behind the scenes. (Dude is amazing).
Please let me know what happens. I know how to roll back to stock and get the hboot to even say LOCKED without TAMPERED, even though it says S-OFF. I'm just looking for a time frame when I have time to restore everything from this unit to any replacement.....and s-off that unit, of course.
Have you checked that it's not the computer causing the problem. I have 2 Windows 7 laptops and 1 would not recognize my phone even though I installed the same HTC drivers on both. Eventually I got it resolved by reinstalling the entire HTC Sync package with the drivers from that, then removing the sync program.
b5fan said:
Have you checked that it's not the computer causing the problem. I have 2 Windows 7 laptops and 1 would not recognize my phone even though I installed the same HTC drivers on both. Eventually I got it resolved by reinstalling the entire HTC Sync package with the drivers from that, then removing the sync program.
Click to expand...
Click to collapse
Thanks, but I've tried with 3 different PC's, 3 different USB cables, 3 different SD cards, and 3 different RUU's. On all 3, the Rezound fails to connect, and then, on reboot, even if it's FIRST REBOOT AFTER RUU, it boots up thinking it's already connected to PC offering me "charge" or "drive mode." If I select drive mode, it dismounts internal and external sdcard, and won't remount them once I disconnect without reboot. If I select charge, then pull the cable, it reminds me to connect, but at least realizes it's *not* connected.
And fastboot usb not obtainable under hboots 2.11, 2.21, 2.25 and Juopunut's ICS hboot.
So, that's why I"m pretty sure it's a hardware issue at this point.
All sorts of issues here.
I am no longer able to install new ROMs on my Aria. In the past I have flashed many ROMs on the phone. Recently I flashed an ICS rom but I did not like the way it was working so I went back to Cyanogenmod 7.1 RC1. Now for whatever reason, I am unable to flash any other ROMs. I put the new rom on the SD card like I always had then boot to CWM, go to install from SD card and it says that there are no files there. Which is not true and its not the SD card because I can still see the files with a file manager. When I select the ROM from inside ROM Manager it goes through the process but stops shortly after starting the install. I have heard that using a different version of CWM may work but when I try to download one from ROM manager it says an error occurred when trying to download. Also when I hook the phone up to my PC it doesnt recognize that it is plugged in other than its charging. (yes it is the original USB cord and USB debugging is on).
A few details: This phone has never connected with my current/new PC. It did work at one time with my old one. While trying to fix this I did a complete wipe of the phone, the first time I hooked it up to my current PC I got the whole new hardware detected thing on my PC and USB debug was active on the phone, but I don't know if I accidently hit a wrong option on my PC but it went right away and has never connected again.
I also noticed that the phone is S-ON, I thought/assumed it was S-OFF before. Could it have some how turned back on? I cant get it back off now since I cant use ADB without USB Debug connected.
I no longer use this Aria for daily use (replaced with One X ) so I am open to some possible "extreme" ideas of trying to fix this.
Thanks for any help. This is driving me nuts.
I'd probably do the following:
1) Format SD card fresh using this program, which can fix some problems with the way SD cards are formatted. It can fix stuff that formatting with Windows or from the phone directly won't fix. Worth a try first since it's relatively easy and will rule out the possibility that the SD card just got got corrupted or something.
2) If that doesn't work, and if you have HBOOT 1.02 or older, run the 2.2.2 RUU on the phone to completely reset everything. Then use Revolutionary to S-OFF the device again, and install one of the CWM builds here: http://forum.xda-developers.com/showpost.php?p=25490394&postcount=66 . Hopefully whatever the problem is will be corrected by doing all that.
If you have HBOOT 1.03, let me know and I'll tell you what else you need to do first. (This won't work without downgrading to 1.02.)
drumist said:
I'd probably do the following:
1) Format SD card fresh using this program, which can fix some problems with the way SD cards are formatted. It can fix stuff that formatting with Windows or from the phone directly won't fix. Worth a try first since it's relatively easy and will rule out the possibility that the SD card just got got corrupted or something.
2) If that doesn't work, and if you have HBOOT 1.02 or older, run the 2.2.2 RUU on the phone to completely reset everything. Then use Revolutionary to S-OFF the device again, and install one of the CWM builds here: http://forum.xda-developers.com/showpost.php?p=25490394&postcount=66 . Hopefully whatever the problem is will be corrected by doing all that.
If you have HBOOT 1.03, let me know and I'll tell you what else you need to do first. (This won't work without downgrading to 1.02.)
Click to expand...
Click to collapse
Thanks. I will give that a try.
drumist said:
2) If that doesn't work, and if you have HBOOT 1.02 or older, run the 2.2.2 RUU on the phone to completely reset everything. Then use Revolutionary to S-OFF the device again, and install one of the CWM builds here: http://forum.xda-developers.com/showpost.php?p=25490394&postcount=66 . Hopefully whatever the problem is will be corrected by doing all that.
If you have HBOOT 1.03, let me know and I'll tell you what else you need to do first. (This won't work without downgrading to 1.02.)
Click to expand...
Click to collapse
How can I run this if I can not establish a connection to my PC? (I have HBOOT version 0.57.0000)
I tried the SD card format and it did not work.
I also noticed an error when first booting into recovery that says something along the lines of I do not have enough internal memory. I have wiped the data on this phone a few times so I cant imagine anything being actually full.
chadd74 said:
How can I run this if I can not establish a connection to my PC? (I have HBOOT version 0.57.0000)
I tried the SD card format and it did not work.
I also noticed an error when first booting into recovery that says something along the lines of I do not have enough internal memory. I have wiped the data on this phone a few times so I cant imagine anything being actually full.
Click to expand...
Click to collapse
Install this first: http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
Then try running the RUU again.
chadd74 said:
How can I run this if I can not establish a connection to my PC? (I have HBOOT version 0.57.0000)
I tried the SD card format and it did not work.
I also noticed an error when first booting into recovery that says something along the lines of I do not have enough internal memory. I have wiped the data on this phone a few times so I cant imagine anything being actually full.
Click to expand...
Click to collapse
I have tried installing that before (tried again this time too) and it doesn't help. I still have no connection to the phone. I have Windows 7 if that helps anything.
I've found the most reliable way to get them to communicate is to put the phone into fastboot mode before connecting it to the computer, then running the RUU again. (If you don't know, to get to fastboot mode, select fastboot from the hboot menu.)
drumist said:
I've found the most reliable way to get them to communicate is to put the phone into fastboot mode before connecting it to the computer, then running the RUU again. (If you don't know, to get to fastboot mode, select fastboot from the hboot menu.)
Click to expand...
Click to collapse
That didn't work either. I am thinking it has something to do with the PC. I installed that driver package you just put up there but is it possible that it didn't install correctly? How could I check that? When I installed it, it never gave any confirmation or anything. Just gave a load screen then went away.
chadd74 said:
That didn't work either. I am thinking it has something to do with the PC. I installed that driver package you just put up there but is it possible that it didn't install correctly? How could I check that? When I installed it, it never gave any confirmation or anything. Just gave a load screen then went away.
Click to expand...
Click to collapse
You can try going to the uninstall programs list in control panel and uninstall anything related to HTC, rebooting, then installing the drivers I linked to again. Otherwise I'd just try on another computer if you can.
Edit: Also, before even trying that, you might just try different USB ports on the computer. If you are connecting to a USB 3.0 port (blue port), try a non-3.0 port (black port).
drumist said:
You can try going to the uninstall programs list in control panel and uninstall anything related to HTC, rebooting, then installing the drivers I linked to again. Otherwise I'd just try on another computer if you can.
Edit: Also, before even trying that, you might just try different USB ports on the computer. If you are connecting to a USB 3.0 port (blue port), try a non-3.0 port (black port).
Click to expand...
Click to collapse
Well,sort of good news here. I had tried different USB ports before but thought I would give it another go, it still was not connecting. So in a bit of a fit of rage I took the micro usb cord at shoved it quite hard into the phone. Well the connection flickered. So it appears over the years the USB slot had gotten a nice amount of pocket lint or whatnot jammed tight in there to where it would connect enough to charge but not enough for a PC connection. I cleaned it all out the best I could and what do you know, it worked.
Foiled by pocket lint.... SMH.
I loaded the 2.2.2 RUU and will give the rest of the problems a go tomorrow and post an update. Thanks again for all the help.
Looks like everything is working like it used to.
Thanks again.
People!, I'm about to pull all my hair out on this one
Vibrant is soft bricked in a boot loop after a incomplete flash, I am able to get it into download mode but both my windows machines say USB device isnot recognized, and thus, I cant use ODIN to return to stock. When I try to manually point windows to the samsung drivers I get nothing…
So far I have tried drivers from:
-Bay_wolf's AIO Vibrant Toolbox 2.5
-USB drivers for vibrant from samsung support site
-Drivers from samsung keyes
Side notes that might help: I was perviously using a Hellybean Rom. My device displays "Galaxy S gt-9000" on boot... not sure when that came to be but maybe some rom changed some important recognition stuff??...
I found this thread http://forum.xda-developers.com/showthread.php?t=1008383 but no help...
Any help would be greatly appreciated!!
Try a different USB cable. This happens more than you'd think. Even cables that have worked just fine hundreds of times.
Also.... Locate the drivers in system/device manager and delete them manually and try to install them again. Unplug device and install fresh ones from either aio toolbox or Kies, then plug phone back in.
Best of luck!
Toast6977 said:
Try a different USB cable. This happens more than you'd think. Even cables that have worked just fine hundreds of times.
Also.... Locate the drivers in system/device manager and delete them manually and try to install them again. Unplug device and install fresh ones from either aio toolbox or Kies, then plug phone back in.
Best of luck!
Click to expand...
Click to collapse
Thanks a ton for reply but, sadly, no dice.
Tried connecting the phone, getting the "unrecognized device" prompt, finding "unknown device" in device manager, right clicking to uninstall. rebooting my machine, using various install methods to re-install drivers, re-connecting, and nothing.. same issue...
I lost the original cable a while back, but can't accept that NONE of the other 5 cables used are all broke... specially if the computer recognizes something going on... is it worth buying a new one?
Losing hope here, been like this for 4 days now, think it's time to go get a new phone. :crying:
Even so, it would have been nice to get what was a perfectly working phone back if only to keep it as a mp3 payer.
If anybody in New York, NY has a working odin set up that can do this for me, I have a 6 pack of your favorite beer with your name on it.
It could be a hardbrick such as bootloader getting corrupted that happened to my Sony Xperia Play (now an expensive paper weight).
I assume you boot into download mode by holding the two volume buttons, then connect the cable? Have you tried on a different PC? It can also be the weak powered USB port on the PC. Also when you uninstall the Samsung driver, check the option to also delete USB driver and uninstall any drivers. Also which version of the driver are you using, have you tried version Samsung USB Driver 1.5.3? And the drivers from here: http://www.samsung.com/us/support/owners/product/SGH-T959ZKATMB#
For what its worth, the gt i9000 screen appears after your on a custom GB boot loader and Odin back to stock (or probably Odin flashing any other ROM) you can change it by flashing the GB boot loader again. My phone says its a i9000 too, but I'm just about lazy enough to not bother changing it, lol.
So that's unrelated.
eksasol said:
It could be a hardbrick such as bootloader getting corrupted that happened to my Sony Xperia Play (now an expensive paper weight).
I assume you boot into download mode by holding the two volume buttons, then connect the cable? Have you tried on a different PC? It can also be the weak powered USB port on the PC. Also when you uninstall the Samsung driver, check the option to also delete USB driver and uninstall any drivers. Also which version of the driver are you using, have you tried version Samsung USB Driver 1.5.3? And the drivers from here: http://www.samsung.com/us/support/owners/product/SGH-T959ZKATMB#
Click to expand...
Click to collapse
Ok, faith momentarily restored. But I have questions:
-What do you mean when you say "check the option to also delete USB driver and uninstall any drivers"? I dont get such a prompt from right clicking on "unknown device" and selecting uninstall? Is there another method to uninstalling drivers?
-In the link attached, I can only find "Device(Install),USB Driver (Software) (ver.1.0)" not the 1.5.3 version mentioned. What am i doing wrong here? currently searching google for the 1.5.3 but finding nothing.
I get into download mode by holding volume- up + power. Have 2 PCs ( win xp and win 7) and a mac running mountain lion (but never ever have been able to get Heimdall to work, so devoting time to odin.)
Thank you for the time + help, guys, I really do appreciate it in the time of utter un-nerdness.
If the device is already installed it will have a check box that said "Delete the driver software for this device." If its unknown then obviously not. By "uninstall any driver", I mean uninstall any Android drivers you current have installed and reboot before you reinstall the new driver.
Although I doubt it will make a difference than the one I linked above, you can try the Samsung driver version 1.5.3: http://www.mediafire.com/?r0uc3h413qcy80z
If you did manage to get into download mode and see this: http://images.google.com/search?num=10&hl=en&site=&tbm=isch&source=hp&q=download+mode
Then it mean there is a very good chance you can restore the phone, if you can find a computer to recognize it and Odin to see a COM port.
I definitely think it would be worth the money to go buy an OEM USB cord. I can't tell you how many times I have seen this and a new USB is the fix.
sent from the depths of helly bean
OK guys...
My friend, who also owns a Vibrant, let me borrow the cable that came with the phone for the last 2 days.
Tried to make ODIN work on both PCs at home, gave Heimdall a shot on my mac, even hijacked a computer at work for the better part of the morning and freshly installed USB drivers 1.5.3 before connecting. All for nothing... “Unknown device” across the board....
At first I felt that with being able to get into download and have SOME kind of a reaction from connecting to PC had to be a good sign. Almost completely convinced that there is some unknown, unworkable hardware problem present. Definitely, officially, unremarkably out of ideas here.
Nothing is beautiful and everything hurts.
Last thoughts? Options at this point?
Also, tried One-click Unbrick tool on mac. I got a "is your phone plugged in, is it on download mode?" error, but anyone reading this down the line with a similar problem should check it out.
http://forum.xda-developers.com/showthread.php?p=15330252
So... now that I think with hindsight, I did something pretty stupid, and I'm going to need some help, since I have no idea what to do.
I have a Nexus 9 tablet, and I never liked it. The OS is just so slow and laggy, and it overheats, and it has many other problems. Quite a couple of times, I installed custom ROM's and so on, and I never had a problem. Let me explain what I did now.
Around a month ago, while looking on the internet, I heard this thing that if I install the original software, but with no encryption, it would work better. It sounded cool at the time, so I downloaded the Nexus Root Toolkit, and did it.
Everything went well. But then I heard about a custom ROM that was apparently working even better, Dirty Unicorns, so using the same toolkit, I installed it. For the first time, my Nexus 9 actually worked the way it is supposed to work, but the custom ROM still had its problems, it crashed from time to time. I was thinking about possibly returning or selling the tablet, so that's why using the Toolkit, I reinstalled the original software. But, if I went all the steps, and also locked the OEM, my device then showed a flag saying that it was a development device, while booting up. So, after messing around with the settings of the Toolkit a little, I decided to reinstall the software, but leave the bootloader unlocked.
But after some time, I reinstalled my Windows, and I also reinstalled the Toolkit. But that's when I started to have problems. My tablet wouldn't connect to my laptop anymore. I used the toolkit and uninstalled drivers, reinstalling others quite a couple of times, and that's where I think that I messed something up. I managed to eventually connect my tablet, and I rooted it, after rooting it, I connected it again. But adb wasn't working for some reason. A little annoyed, I simply copy pasted the zip file of CM13 into my tablet's internal storage, and I rebooted it to the recovery, TWRP. But the recovery failed to flash it, saying something about an Error 7.
Now that I think about it, I was stupid, since after that, I performed a complete factory reset, resetting my TWRP backup too. I tried to connect it again, nothing. It didn't connect at all. I plug it in, my computer doesn't even recognize that something is plugged in. No Nexus 9, no Android Device, no anything. I booted it in fastboot mode, and it worked, my computer recognized it, and after I downloaded a ROM zip file again, I tried to connect the tablet back and flash it manually, but nothing. It didn't recognize anything anymore.
I tried to reinstall the drivers countless times. I deleted what I had, reinstalled it, nothing. I uninstalled and reinstalled the Toolkit. But strangely, now, even if I know that I installed the Google USB drivers, and the ADB drivers, as I even installed Android SDK, if I use USB Deview, it doesn't show me any of them. I can't see any Google or ADB drivers, although I tried installing them multiple times. So now, I'm stuck with a tablet with TWRP and no OS, which I can't connect to my PC, and I can't use ADB or fastboot.
Is it something from my laptop? I can't check to see if it will connect to another PC right now, so I don't know for sure. Is there any way to delete all the traces from my (failed) attempts at reinstalling the drivers, and to install them again properly? Or is it something from the tablet itself? I don't have an OS, so I can't enable USB debugging.
So, shortly, I have no idea what's happening. And I'm quite obviously a noob in all of these. Can anyone help me? Please?
If you boot into the bootloader and from a command prompt type fastboot devices you don't get anything?
Sent from my Nexus 9 using XDA-Developers mobile app
I still couldn't get ADB to work, but I managed to work out fastboot. It may be something from my USB cable, it works perfectly.
I flashed the original software back, and I'll go to check my cable, although I feel kinda stupid that I didn't think about that in the first place.
Thanks for the help anyway.
If fastboot is working and bootloader is unlocked, you can still install a factory image.
Depending of your device download for wifi Version:
https://dl.google.com/dl/android/aosp/volantis-mob30p-factory-2cb57a1b.tgz
If you habe the LTE variant:
https://dl.google.com/dl/android/aosp/volantisg-mob30p-factory-ae9ce05a.tgz
Extract the files and put them into the same directory link fastboot and execute the flash-all.bat
WARNING: Any data will be erased!!! Also TWRP
Now it should boot up with stock firmware.
If you want your device decrypted install twrp. format the internal storage and flash the pure nexus rom which i can highly recommend and is decrypted by default. Dont forget do flash gapps
my issue is same
what if someone USB- debug is not enabled , is there any possibility to do that , i have a device nexus 9 , rooted it it went into bootloop then i factory reset it , and now my adb is not communicating , if there is any options?
rohanzakie said:
what if someone USB- debug is not enabled , is there any possibility to do that , i have a device nexus 9 , rooted it it went into bootloop then i factory reset it , and now my adb is not communicating , if there is any options?
Click to expand...
Click to collapse
Use fastboot, not adb.
what if fastboot isn't working, either?
uberSkeptic said:
what if fastboot isn't working, either?
Click to expand...
Click to collapse
Is the tablet in fastboot mode?
madbat99 said:
Is the tablet in fastboot mode?
Click to expand...
Click to collapse
Yup. I can boot into the bootloader, and from there (or from TWRP) into fastboot, but no computer I've connected it to (and I've tried many) will recognize it. Doesn't show up in Device Manger or lsusb, doesn't show up from either "adb devices" or "fastboot list devices" (the latter just hangs there saying "Waiting for any device"). The USB on the tablet itself is fine, and I even replaced the USB daughter-board just to be safe.
uberSkeptic said:
Yup. I can boot into the bootloader, and from there (or from TWRP) into fastboot, but no computer I've connected it to (and I've tried many) will recognize it. Doesn't show up in Device Manger or lsusb, doesn't show up from either "adb devices" or "fastboot list devices" (the latter just hangs there saying "Waiting for any device"). The USB on the tablet itself is fine, and I even replaced the USB daughter-board just to be safe.
Click to expand...
Click to collapse
Hi, uberSkeptic...
Just a quick thought... Have you tried a different USB cable?
Rgrds,
Ged.
Edit & Additional...
The command is not fastboot list devices... it's fastboot devices
One last point... Ensure your Nexus 9 is definitely booted into fastboot mode and not just HBOOT (the bootloader). Take a look at the two screenshots below - your Nexus 9 should look like the screenshot on the right, the one with my green explanatory text.
Apologies for the poor image quality; there's no way of taking a screenshot in the bootloader, so I had to take photographs instead.
Hope this helps and good luck.
Thanks for the advice and going so far as to photograph the hboot/fastboot screens, but unfortunately I have indeed tried multiple USB cables, including the OEM's and I've definitely successfully gotten the tablet into fastboot but it doesn't show on the computer with either fastboot command (devices or devices list).
uberSkeptic said:
Thanks for the advice and going so far as to photograph the hboot/fastboot screens, but unfortunately I have indeed tried multiple USB cables, including the OEM's and I've definitely successfully gotten the tablet into fastboot but it doesn't show on the computer with either fastboot command (devices or devices list).
Click to expand...
Click to collapse
I'm out of ideas then.
One of my first thoughts was possible Windows driver problems, but as you mentioned you'd tried it on several different computers, that didn't seem to be a likely cause of the problem - I mean, you'd expect at least one of 'em to work! Maybe somebody else can help with a solution.
GedBlake said:
I'm out of ideas then.
One of my first thoughts was possible Windows driver problems, but as you mentioned you'd tried it on several different computers, that didn't seem to be a likely cause of the problem - I mean, you'd expect at least one of 'em to work! Maybe somebody else can help with a solution.
Click to expand...
Click to collapse
Sadly, me too. I even tried using a flash drive with a micro-USB connector on it, which I used to use to do nandroid backups, but now TWRP doesn't even "notice" that the USB drive is there (or any USB drive connected via an OTG cable).
Too bad, too - the tablet is otherwise in great condition and even has a custom-painted backplate (long story).
Thanks for trying to help, though!
uberSkeptic said:
...The USB on the tablet itself is fine, and I even replaced the USB daughter-board just to be safe.
Click to expand...
Click to collapse
Mmm...
uberSkeptic said:
...I even tried using a flash drive with a micro-USB connector on it, which I used to use to do nandroid backups, but now TWRP doesn't even "notice" that the USB drive is there (or any USB drive connected via an OTG cable).
Click to expand...
Click to collapse
Mmm... (scratches head, raises eyebrow quizzically)...
If I was Hercule Poirot and this was a murder case, and with all the suspects gathered in one room, prior to revealing a brilliant deduction... I'd be casting very dark glances in the direction of your Nexus 9's USB port right now as the likely culprit here.
Think about it. Different computers. Different USB cables. An OTG cable... And none of them work. What's the one thing they all have in common?
Answer: The USB port on the Nexus 9 itself, and where you've replaced the USB daughter-board.
Maybe, possibly, that replacement don't go so well. Maybe there's some unknown problem with it. I can't comment too much on this, 'cos it outside the scope of my knowledge - I'm a software guy; circuit boards and dismantling devices to fix 'em isn't something I'm comfortable with. I always think I'm going to damage something or rip a wire out somewhere, so I bow to your superior knowledge in this area, as I may be talking complete cobblers here. It certainly wouldn't be the first time.
Anyway... Sorry I wasn't able to help find a working solution for you. If anything occurs to me that might help, I'll be sure to let you know.
Rgrds,
Ged.
I would be suspect if the replacement as well if it weren't for the fact that I did it only AFTER the other symptoms/problems appeared. Hence the replacement (which is known good because the battery charges no problem). There cables and everything inside the tablet tests just fine... It feels like the firmware for USB is somehow corrupt or something.
Thanks for all the advice, though. ?
So I can't believe I didn't think of this before, but when I run "dmesg" from the terminal app included w/ TWRP, I see that there a TON of errors, mostly referencing problems accessing the recovery image. I could screenshot it, if anyone at all might be able to tell me a little more specifically what the dmesg log is trying to tell me...