Related
Basically I have no rom on my phone, I have tried sideloading and everything and it could not work. However, I noticed under devices that instead of saying HTC it says android phone and I am unable to access it. I have tried going into properties, however it refuses to let me uninstall or or update drivers. Does anyone know anyway for my phone to recognize it as a HTC and not just an android phone? Maybe then I can bump a rom or sideload it onto my phone. Also when I sideload it shows HTC XXXXXXXXXX when i typ in cmd adb devices. In CWM it says sideload started. When I go to adb sideload derp.zip it gives me a massive wall of text and my phone doesn't show any files being transferred and says its still waiting for them to start transfer.
Any ideas?
Worst case scenario you think I could take it to T-Mobile and ask them to do a factory reset on it?
derpyherpes said:
Basically I have no rom on my phone, I have tried sideloading and everything and it could not work. However, I noticed under devices that instead of saying HTC it says android phone and I am unable to access it. I have tried going into properties, however it refuses to let me uninstall or or update drivers. Does anyone know anyway for my phone to recognize it as a HTC and not just an android phone? Maybe then I can bump a rom or sideload it onto my phone. Also when I sideload it shows HTC XXXXXXXXXX when i typ in cmd adb devices. In CWM it says sideload started. When I go to adb sideload derp.zip it gives me a massive wall of text and my phone doesn't show any files being transferred and says its still waiting for them to start transfer.
Any ideas?
Worst case scenario you think I could take it to T-Mobile and ask them to do a factory reset on it?
Click to expand...
Click to collapse
That used to happen to me with another phone I had and what I would do to solve it was uninstall the "android phone" driver (with the device connected at all times), then scan for hardware changes and it would reinstall the driver correctly.
I haven't experienced this issue with this phone but worked in the past with other HTC phones, hope it helps
Sent from my Nexus 7 using Tapatalk 2
megabiteg said:
That used to happen to me with another phone I had and what I would do to solve it was uninstall the "android phone" driver (with the device connected at all times), then scan for hardware changes and it would reinstall the driver correctly.
I haven't experienced this issue with this phone but worked in the past with other HTC phones, hope it helps
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Also, you may need to regedit uninstall. Search and delete all "android" references in your registry. Reboot. Install generic android drivers.
But definitely try the simpler method first!
Tried both of the solutions and neither one worked I am at my wit's end lol
Anythign else I can try?
derpyherpes said:
Tried both of the solutions and neither one worked I am at my wit's end lol
Anythign else I can try?
Click to expand...
Click to collapse
Assume you've also tried installing generic HTC drivers?
I accidentally bricked my Nexus 9 recently. It won't boot up, and I'm getting the red "your device is corrupt" message. Normally, you would connect the device to your computer via USB and use the Android Debug Bridge to unlock the bootloader, and flash a new system image. However, the tablet doesn't show up when I connect it to my laptop and run ./adb devices. Anybody know why this could be happening? More specifics:
* I walked around outside with it, and it rained lightly a bit. It had a case and screen protector on it, so I didn't worry. Later, I noticed that the speakers were acting funny, but rebooting seemed to fix that. Later, USB Debugging with Android Studio wasn't working, and it wasn't showing that it had been unplugged when it had been. Then, I tried to install 6.0.1 OTA, and that failed, bricking the device, and I got the "your device is corrupt message."
* I cracked open the back cover to peek inside for moisture, but I didn't see any. (I didn't take the cover all the way off though, didn't wanna have to reattach the camera.
* I have tried factory reset from the bootloader a few times -- I don't think I gave it enough time the first time, the second time it ran out of battery, and the third time I let it run overnight while it was plugged in. When I checked it in the morning, it had powered down, and nothing seemed to have changed.
* I have the latest version of ADB and platform-tools, and I've got some experience with the SDK. I also tried using different USB cables to connect, no luck there.
* I can't access the OS at all, just the bootloader and recovery mode.
* The tablet is a black 32GB Nexus 9, formerly running stock 6.0.0. The laptop I'm using is Linux Mint 17.2.
* The bootloader is locked, I never had any reason to unlock it. I didn't enable OEM Unlocking in the Developer Options in the OS either, but that shouldn't prevent it from connecting to the ADB.
* I got into recovery mode, and wiped the cache partition, but that didn't seem to do anything.
* I got it from BestBuy more than a year ago, so I'm pretty sure it's out of warranty.
Does anybody have any ideas about how I could get my tablet to connect to the ADB? Thanks.
Have you tried this?
http://forum.xda-developers.com/nexus-9/help/marshmallow-ota-update-bricked-nexus-9-t3334871
if it doesnt works maybe I have the same problem that you have.. (read that topic and read my comments :/)
No, I hadn't tried sideloading the OTA, thanks! I tried it, and it worked, so now I'm all set! Thanks so much!
Apparently adb devices only works when the device is fully booted into the OS, but fastboot devices and adb sideload will work when you're in recovery mode, the way I understand it.
Sorry you're having trouble, hope you find a solution!
weirdo16 said:
I accidentally bricked my Nexus 9 recently. It won't boot up, and I'm getting the red "your device is corrupt" message. Normally, you would connect the device to your computer via USB and use the Android Debug Bridge to unlock the bootloader, and flash a new system image. However, the tablet doesn't show up when I connect it to my laptop and run ./adb devices. Anybody know why this could be happening? More specifics:
* I walked around outside with it, and it rained lightly a bit. It had a case and screen protector on it, so I didn't worry. Later, I noticed that the speakers were acting funny, but rebooting seemed to fix that. Later, USB Debugging with Android Studio wasn't working, and it wasn't showing that it had been unplugged when it had been. Then, I tried to install 6.0.1 OTA, and that failed, bricking the device, and I got the "your device is corrupt message."
* I cracked open the back cover to peek inside for moisture, but I didn't see any. (I didn't take the cover all the way off though, didn't wanna have to reattach the camera.
* I have tried factory reset from the bootloader a few times -- I don't think I gave it enough time the first time, the second time it ran out of battery, and the third time I let it run overnight while it was plugged in. When I checked it in the morning, it had powered down, and nothing seemed to have changed.
* I have the latest version of ADB and platform-tools, and I've got some experience with the SDK. I also tried using different USB cables to connect, no luck there.
* I can't access the OS at all, just the bootloader and recovery mode.
* The tablet is a black 32GB Nexus 9, formerly running stock 6.0.0. The laptop I'm using is Linux Mint 17.2.
* The bootloader is locked, I never had any reason to unlock it. I didn't enable OEM Unlocking in the Developer Options in the OS either, but that shouldn't prevent it from connecting to the ADB.
* I got into recovery mode, and wiped the cache partition, but that didn't seem to do anything.
* I got it from BestBuy more than a year ago, so I'm pretty sure it's out of warranty.
Does anybody have any ideas about how I could get my tablet to connect to the ADB? Thanks.
Click to expand...
Click to collapse
If you were using a waterproof case it should not be damaged and even without a waterproof case you shouldn't get water damage in light rain. The speakers thing happened to someone with a S7 after they put it under water but it went away.
Can you charge the tablet. Maybe the USB port is broken and needs to be replaced.
One small tip : Before I run the OTA update I always enable OEM Unlock so I can flash if it bricks. My Nexus 9 has never got bricked for a OTA but it could happen
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...
Please don't drop the "wrong thread" bomb on me. My experience in forums is, you ask a question and you get 50% told to reboot, 40% told you're in the wrong thread, 9.9% other nonsensical things, and the 0.1% would be an actual attempt at a solution.
Here's the thing. My v10 is not going to have its bootloader locked by running fastboot. I have tried every single solution. No matter what, the computer never sees my phone on fastboot. All the drivers are right, re-installed nearly twenty times now too. I've tried the light, minimal version of adb. The full version. That other version I didn't quite get why it was different. And in all permutations with all driver installation attempts.
Don't know if this has anything to do with anything, but the phone has never once successfully booted into recovery by holding down power and down-volume. Nor power and up-volume. Not once. I have only ever been able to get it to do so with the "adb reboot recovery" command, just as, before I installed the xPosed module, "Quick Boot," there was no way I could get into bootloader other than "adb reboot bootloader" command. Because of course bootloader sees the phone in all states except fastboot.
No, if I plug it in while on bootloader, nothing happens on the computer. Nothing installs. No little yellow triangle thingie shows up suddenly in my computer's Device Manager. Ever. So there's no way to make the driver upgrade to whatever it needs.
Only one time has "fastboot devices" ever shown this device, and that was the moment I unlocked it to root it in the first place.
And now that this device has proven to be without a doubt the worst thing I've ever, ever owned, and I am sick to death of all its problems and screw-ups, I have absolutely no way whatsoever to relock the bootloader and do something to exchange it. Unless anybody knows any other way for me to do this without the use of my computer. Anybody? Please help. I can't even stand looking at this phone any more, much less use it without it making me want to kill puppies and babies and throw exploding Samsung 7s at little old ladies just to watch them burn.
All help is appreciated. Except, as I said, what I usually get 99.9% of the time from forums. Thanks.
Oh, wait, mandatory emoji storm... sorry, almost forgot: :cyclops::good::silly::laugh:
Oh, before anything, I forgot to add...
I tried every USB port, with multiple USB wires, on both computers, one old and one new, one Windows 7 and one Windows 10, and again, in all permutations. There is no possible way this should be this frickin' difficult.
thestumblingblock said:
I tried every USB port, with multiple USB wires, on both computers, one old and one new, one Windows 7 and one Windows 10, and again, in all permutations. There is no possible way this should be this frickin' difficult.
Click to expand...
Click to collapse
Had the same problem. I highly suggest if you have even a 16gb flash drive to download and install Ubuntu onto it. It takes just a few minutes to get setup and fastboot will detect your device almost immediately. Launch Ubuntu in live boot (from the usb drive) and you can then try it out and it should work fine. This was the only option that worked for me after trying just about every option online I could find.
Once on Ubuntu right-click the desktop and open Terminal and put in the following without quotes around it: "sudo apt-get install android-tools-adb android-tools-fastboot" follow the prompt and within a few seconds you should be able to issue both adb and fastboot commands properly.
theinspector said:
I highly suggest if you have even a 16gb flash drive to download and install Ubuntu onto it..... Once on Ubuntu right-click the desktop and open Terminal and put in the following without quotes around it: "sudo apt-get install android-tools-adb android-tools-fastboot" follow the prompt and within a few seconds you should be able to issue both adb and fastboot commands properly.
Click to expand...
Click to collapse
Sounds like something totally new for me to learn, but I do have a pretty good size flashdrive. So, here goes something. I'll report back how it works. I'm glad to hear there's at least something to try because as you no doubt saw from my tone, I really felt like I'd been totally Kobiyashi Maru'ed here.
Because technology hates me in every way, I cannot get Ubuntu to work at all. I give up. I'm gonna go ahead with that puppy-kicking plan. I am just DONE.
Don't know much about fastboot and all that stuff, mainly because I have Verizon VS990 version with bootloader that can't be unlocked.
Having said that with Windows 7 or 10 did you install and open all that fastboot stuff as administrator? Because if you didn't do all the required steps as administrator that might cause this to not work on Windows.
beavis5706 said:
Having said that with Windows 7 or 10 did you install and open all that fastboot stuff as administrator?
Click to expand...
Click to collapse
Sir, if you came up with the answer to this (and that means me taking the time tomorrow to try it again) you will forever have me bowing down to you in the most embarrassing way imaginable. I'll letcha know how this goes.
Nope. Nothing. If I touch it, it refuses to work. I tried to make an Ubuntu boot stick, but every effort to do so gave me nothing but errors so I don't even know if that would work. Meanwhile the phone only gets worse, and I'm stuck with it, and out $600, and there's nothing that can be done. This is without a doubt the worst. And I am so f#$^%&^ing done with technology right now, you have no idea.
TL;DR Samsung s10e, stock Android 10, soft-bricked itself during security update. Want photos. Starts reliably in Android Recovery Mode. Can't see from PC - nothing from cmd window with ADB either.
My Samsung s10e (US, Verizon) soft-bricked itself a couple days ago. I wanna grab my photos before factory reset / flashing the OS. It starts in Recovery Mode, and Samsung includes a "mount /system" option, but I haven't found a good description of what that does. Anyways, I've tried to plug it in via USB to both Win 10 and Ubuntu, but neither see the device at all (not in Device Manager as Unknown Device for instance, just nothing).
I have computer expertise, but not with Android, so I tried following some tutorials and downloaded ADB. I made sure the s10e drivers were installed on my PC as well. When I run "adb devices" the list is empty. I downloaded Google USB Driver, but it appears like I am supposed to install that on the phone, not on the PC, so that's no help right now. I came to realize that I needed the phone to have a custom recovery tool previously installed. I also came across this thread, but it's 6+ years old so I was a little wary of following the advice. What am I missing to be able to connect through ADB, is that thread still valid, is there an easier way? Is there another way to mount the device and navigate the files through my PC? If I could just magically go to C:\Android and press copy/paste, that's all I need. Any other suggestions - like a magic way to fix the initial problem without clearing my data?
Bonus Question: what does "clear my app data" do? Should I try that, or will I lose my native photos? I'm okay losing the Snapchat/Facebook ones for the sake of getting the rest. Booting in Safe Mode is currently not helping, but the debug menu suggests that may help it (doubtful) to do the clear.
Any advice would be greatly appreciated!
P.S. I did also find this thread which dampened my hopes a bit....but some of the answers seemed slightly conflicting
Edit: btw, I think I might have turned on developer options at some point, but not sure if I ever turned on USB debugging. Not sure if that matters now or not. Otherwise, the phone is completely non-custom.