Posted this on the general discussion section but have had no replies, hopefully someone here can help?
Hi everyone, first, this is my first post, new to the forums, at least as a registered user. I have a problem with my phone. I know most of you are wondering why I have not just read the other posts on the forums, but I have. I have attempted every solution to the problem posted previously.
Background: Phone: Samsung charge.
I was being impatient and did not want to wait for the gingerbread update form Verizon. I flashed the leaked gingerbread 2.3.4 onto my phone using odin. Everything went great. I was able to use my phone with no problems except shortened battery life, but nothing major. About a month ago the battery life was impossible to maintain and there were some software bugs, like clicks during calls, startup taking forever, around 2 minutes on average!, and random restarts that never happened before. I decided to look up some fixes and found that verizon and samsung had released GB 2.3.6 for the charge. I got excited and decided I wanted to get that, but I could not via OTA. I read some forum posts and they mentioned attempting a factory reset on the phone then trying OTA update. I went ahead with factory reset and everything went fine. My startup time is around 25 seconds now and no random clicks or gliches, but still not on 2.3.6, which was the whole point. I then decided to just flash the stock 2.3.6 rom to the phone.
Problem: When I plug my phone in to multiple computers it will charge but not connect to the computer. This means on my Mac it does not show as an external drive, which it has in the past. On my windows 7 machine it says that drivers were installed but could not be used (I can get the exact quote if needed.) I attempted to go into device manager and solve problem that way but it shows my phone as "unknown device". I have tried to enter download mode when hooked up to windows computers and no connection is found.
Possible solutions attempted and their outcomes:
1. As stated, I attempted the method shown in a thread on droid forums for installing the samsung drivers. I have attempted multiple times to install the drivers on my windows machine and the device remains "unknown".
2. I have attempted multiple cables on multiple computers, both mac and windows 7. No change.
3. I have installed adb and attempted to locate devices using adb devices command on mac. No devices found.
4. I have attempted all methods with both usb debugging checked and unchecked.
5. I have tried every possible usb port I have.
Ideas/questions I have had that I have no idea are possible or how to fix!
Would a factory reset take away the ability to connect to a computer from my phone. So, is there a piece of software in the build I have that controls the connection between the computer and the phone, an identifier of sorts, which is now missing, now that I have reset the leaked ROM.
Is there a way to flash a new ROM without connecting to a computer, via the sd card, and what is that? I have read some things in other posts but am too much of a n00b to understand most of them when using sdcards.
ANY help will be greatly appreciated. PLEASE PLEASE PLEASE!!! I have been at this for at least 6 hours, sifting through forums, searching google, attempting fixes that others have stated worked for them, only to fail every time. Thank you all.
have you try on a different pc?
maybe on your PC there is some problem with the drivers.
Moreover to connect via
adb u must enable Debug mode on your device in the application menu.
To flash kernel or other directly from your sd you can use the clockwordmode, but to install it you must before
install it and i fear you must use your cable connection
Sent from my GT-I9100 using XDA App
I have tried multiple PCs and a mac, even windows on bootcamp. I have installed drivers on every one, even uninstalled and reinstalled on one. One PC, my laptop was a fresh windows install (it was a linux box but I needed windows to use Odin). I was in debug mode and not in debug mode when attempting adb. Thanks for the suggestions though. As I said, I have tried numerous things and am completely stuck! so frustrating!
"I attempted to go into device manager and solve problem that way but it shows my phone as "unknown device"
Exactly there... you can try to force device to install a different driver.
Double click the unknown device then driver then update driver then find software in your computer then choose manually from a list of device drivers in your computer then show all devices you should see "android adb interface" or something related to google or android.
Try it... i hope this can help you.
Hello,
I hope that I am not asking a already existing question again, if so, please send me the link and I will follow the instructions there.
I could not find anything, so far, but I am nearly going mad after a day of trying to unbrick my phone.
So, I had CM 11 Snapshot M10 installed, the current clockworkmod, bootloader unlocked through htcdev.
Today I wanted to do a full wipe (including /sdcard, because there were tons of files which I didn't know, lately).
I don't know why, but i ended up wiping /system and /sdcard at the same time.
Now I don't have any system on the phone in order to boot and get adb or mount the phone as a USB drive, and no firmware on the phone which I could flash. I really have no idea how I can get any rom onto the phone, now...
I tried official RUUs ("Please download the RUU which fits your phone), ADB sideload with CWM ("no devices found"), ADB sideload with TWRP (same as with CWM), and now I am running out of ideas...
Does anyone have an idea how to or get ADB sideload working (USB drivers are installed on my PC, but it doesn't seem to work), or how to get a RUU wiorking (I would like to go back to the stock rom anyway, I miss sense by now), or any other way how to revive my phone?
I do have access to the bootloader, fastboot is working, and so is the recovery. Is there any information you would need?
It is an enrc2b international, no branding. CID is HTC__102.
fastboot getvar version-main outputs 2.18.401.3
I really hope that someone can help me out...
Moritz
Adb sideload needs up to 5min to recognise the device.
Or you flash twrp recovery. Which has mtp support (access via windows explorer)
If crusader's suggestion didn't work then:
Try to use a different USB port. If USB 2.0 use USB 3.0 and vice versa.
If that doesn't work too, try running cmd as admin.
Last resort : install Ubuntu or any other Linux distro, and install dev tools on it (check for guides ) .. I have a similar issue to yours when it comes to windows, restarting to Linux always works for me
Thanks for the tips so far...
Waiting for ADB did not change, and my PC (Win 8.1 x64) doesn't recognise the phone with TWRP in mtp.
I reinstalled the google drivers now (had outdated ones), and I am reinstalling the htc drivers too.
Then I'll try a USB 3.0 port, if that doesn't help I will have to try Linux...
Thanks so far!
Thanks for the tips so far...
Waiting for ADB did not change, and my PC (Win 8.1 x64) doesn't recognise the phone with TWRP in mtp.
I reinstalled the google drivers now (had outdated ones), and I am reinstalling the htc drivers too.
Then I'll try a USB 3.0 port, if that doesn't help I will have to try Linux...
Thanks so far!
EDIT: looks like my htc drivers were simply retarded. They worked as long as the phone booted into the OS, but failed if I was in the recovery.
Reinstalling worked.
I will now flash CM11 again, does anyone have an idea how to get the RUUs working, or get Sense back in another way?
I lost my old backup with Sense
elektrobastler said:
Thanks for the tips so far...
Waiting for ADB did not change, and my PC (Win 8.1 x64) doesn't recognise the phone with TWRP in mtp.
I reinstalled the google drivers now (had outdated ones), and I am reinstalling the htc drivers too.
Then I'll try a USB 3.0 port, if that doesn't help I will have to try Linux...
Thanks so far!
EDIT: looks like my htc drivers were simply retarded. They worked as long as the phone booted into the OS, but failed if I was in the recovery.
Reinstalling worked.
I will now flash CM11 again, does anyone have an idea how to get the RUUs working, or get Sense back in another way?
I lost my old backup with Sense
Click to expand...
Click to collapse
Someone posted his backup files somewhere here on the forums...
First look at your CID (found at the top of the boot loader)
And secondly you can just install sense-based ROMs like viper or revolutionHD (I think that's what it was called) .. RevolutionHD is just stock sense basically with a few performance improvements.
Thank you very much!
You really saved my day
I was able to install CM11 now, it booted.
I instantly shut it down again, though, because I will now try RevolutionHD.
Stock sense (especially the gallery and camera app, never found anything comparable so far) with a few improvements sounds just awesome.
Exactly what I was hoping for, but I never imagined someone had actuall done it!!
Downloading it now, I think this will stay my ROM for the next year(s), depending on how long my X+ will keep on working...
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...
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.