Hello guys, im really in trouble. I have a general mobile e tab 5 tablet and i'm living some problems. This tablet don't have an microsd card so i can't setup anything from microsd. Don't have an os and when i connect to computer it's not being visible. I setup sdk android tools, fastboot or smth. This didn't work too. I'm updated the java things and it's still not working. I can't wiping datas, it's giving error like "failed to mount '/cache' and '/data' (invalid arguments), Unable to mount storage" and i can't doing any little thing. Im totally stucked, no way, im thinking only i can fix it from terminal but i don't know what i should to write I don't know what i should to do. Really i need help guys. Also ADB sideload not working too as i said, it's not being visible on computer. (Sorry for bad English.)
Is it detected by your computer (showes in device manager) but no storage or is it not detected at all?
You may need to install/reinstall usb drivers for ADB?
bailey239 said:
Is it detected by your computer (showes in device manager) but no storage or is it not detected at all?
You may need to install/reinstall usb drivers for ADB?
Click to expand...
Click to collapse
Nothing being detected, also i'm always keep opened the fastboot (from adb shell, sdk tools) with command "fastboot flashall"
You can check the picture. (I couldn't insert to image because i don't have 10 messages. )
i.hizliresim .com/aXk3nQ.png
I did everything, i deleted every usb drivers and setup again. At the same time i deleted from device manager every usb port and i setup again all of them. It's not detectable. In twrp MTP enabled and im opening adb sideload.
Just judging from the image you provided, it looks like your drivers are not installed properly. There are a few different drivers you can try, googles, Universal Naked Driver, Motorola, etc. I would suggest trying a different route than the one you took already. Your device is not being recognized, it must be related to the adb USB drivers.
bailey239 said:
Just judging from the image you provided, it looks like your drivers are not installed properly. There are a few different drivers you can try, googles, Universal Naked Driver, Motorola, etc. I would suggest trying a different route than the one you took already. Your device is not being recognized, it must be related to the adb USB drivers.
Click to expand...
Click to collapse
Can you help me about the links?
remove any spaces.
http ://koush.com/post/universal-adb-driver
http ://adbdriver.com/
https ://androidmtk.com/download-universal-adb-driver
http ://visualgdb.com/KB/usbdebug-manual/
I setup all of them, google usb drivers and also tablet usb drivers but nothing is working. I'm gonna cry actually.
Note: I think problem is TWRP. But another problem is computer is never seeing tablet because of TWRP. Tablet don't have a microsd card connection. No OS. Hard hard hard bricked. If i connect a USB Flash Memory to my tablet, can it work?
@AKagNA
Be specific with your device info. You still able to go in recovery, try flashing it with stock firmware, Please please please make sure you get proper firmware for your device, please read this information HERE before proceeding, it might take few minutes but this is useful,Also hit thanks button and share if you find it useful
Thanks
Salman
Salman Al-Badgail said:
@AKagNA
Be specific with your device info. You still able to go in recovery, try flashing it with stock firmware, Please please please make sure you get proper firmware for your device, please read this information HERE before proceeding, it might take few minutes but this is useful,Also hit thanks button and share if you find it useful
Thanks
Salman
Click to expand...
Click to collapse
Hello Salman, i tried to setup stock firmware with every usb driver and flash tool. I swear i tried everything and also i'm a programmer. I'm really understand the computer. But nothing is happenning. Even computer doesnt seeing the tablet.(Sorry for bad Eng..)
You could use flashfire download it from the playstore and download a new rom. Can you boot into os?
_Exeedy_ said:
You could use flashfire download it from the playstore and download a new rom. Can you boot into os?
Click to expand...
Click to collapse
There is no OS and i can't boot it.
Related
Happy Holidays Everyone!!!
Phone:
Tmobile T959 aka Samsung Vibrant
It is on stock Froyo 2.2
It has the 3E recovery.
I tried on 2 computers but I can NOT connect via USB it gives me USB malfunction error. The phone does charge. I can put it into download mode vie the 3 finger trick. When you connect it does give you the option to click the green Android icon Connect to USB. So it is talking to the computer, the usb is not totally dead.
Problem:
I need to root this phone. I can not use 1 click or anything else because I think there is a problem with the USB port. I can get files onto the phone via wifi or using the external sd card.
I tried using the update.zip file BUT because I am on the 3E recovery it will say signature failed. I can not run the install.bat to get it back to 2E recovery. I can not use ODIN because the Windows will not detect the phone properly.
What workaround can I use to root this phone? How would I use terminal on the phone?
HOW WOULD YOU ROOT THE PHONE IF YOUR USB PORT WAS "broken"?
THANKS for helping!
As far as I'm aware, you can't root your phone without the USB port working as most (if not all) root methods send their commands and files through ADB. Your pretty much stuck, unless your phone is under warranty. In that case, just go to your carrier and see if they'll give you a replacement device.
TheAndroidGod said:
As far as I'm aware, you can't root your phone without the USB port working as most (if not all) root methods send their commands and files through ADB. Your pretty much stuck, unless your phone is under warranty. In that case, just go to your carrier and see if they'll give you a replacement device.
Click to expand...
Click to collapse
It's out of warranty
I think there may be a way to do it via terminal emulator on the phone.
If this is possible, can someone please post how to do it.
anyone with a work around?
damn!
Am I stuck or does anyone have a way for me to root this phone without the using the USB connection (USB does charge, It will know when you connect to the pc for USB storage BUT windows will say not recognized. I tried it on 4 other pc's same results. I think something is wrong with the OS of the phone. I think the previous owner tried to update with Kies and it messed up the phone. The phone does boot and works.
droiduzr2 said:
damn!
Am I stuck or does anyone have a way for me to root this phone without the using the USB connection (USB does charge, It will know when you connect to the pc for USB storage BUT windows will say not recognized. I tried it on 4 other pc's same results. I think something is wrong with the OS of the phone. I think the previous owner tried to update with Kies and it messed up the phone. The phone does boot and works.
Click to expand...
Click to collapse
Try to install phone drivers for the computer i had to do that for my phone.
maikzen said:
Try to install phone drivers for the computer i had to do that for my phone.
Click to expand...
Click to collapse
I did all of that.
I think something is wrong with the phone's OS that is effecting the usb port.
How do I root this phone WITHOUT the USB port?
There has to be a way!
Can you determinate VID&PID of phone?
I can get into the device with airdroid and see the system files.
Which files do I need (or which apps) and where do I copy them manually to get it rooted?
droiduzr2 said:
I can get into the device with airdroid and see the system files.
Which files do I need (or which apps) and where do I copy them manually to get it rooted?
Click to expand...
Click to collapse
Is there not a device forum where you might could get some better information? My thinking is, a lot of the people (or most of the people) who may know some workarounds can probably help, but they don't check this section very often or at all.
Even if there's not a section for that model, I'm thinking there's probably one quite similar. Also a lot of times, a big portion of the userbase of one phone, will migrate to the same model when they upgrade.
Just throwing out some ideas in case that's helpful. My only advice on the problem itself is that I would look further into the driver issue. I've helped several people with very similar issues that we finally were able to correct.
Have you tried to ADB the device just to pull the serial? With USB debugging enabled. Have you installed the SDK and tried the naked drivers? There's some things to pursue possibly so you can have more information for the person who helps you get things straightened out.
Specs: Windows 8 64-bit. Clean and restored HTC EVO 3D. HBOOT 1.58.0000.
I have tried almost everything, but I can't get my phone recognized in fastboot mode.
I tried what was listed here: http://forum.xda-developers.com/showthread.php?p=39218156#post39218156
_kevn_ said:
I was able to get mine working with the combo of
1. uninstalling any HTC sync or sync manager and the HTC BMP USB Driver. Basically anything HTC.
2. Install HTC sync. Not sync manager. Go to the HTC support page and you'll see both listed. If you go to the specific phone support page it might not be there. (One S doesn't have the sync program, just sync manager iirc.)
3. Download PDAnet. When installing, It'll give a warning that you already have drivers installed and ask if you want to fix them or leave as is. I chose it to fix and it went though its process and I had working drivers after that.
I think this was already suggested before. I going back and giving thanks wherever due after this post. (On the mobile app right now)
Other easy way if you're using a One S is to download Hasoon2000's All-On-One Toolkit. He's updated the drivers for windows 8. I haven't tried it yet as mine are working so haven't had the need. I would assume his tool for any of the other phones he supports would have the updated drivers too.
Click to expand...
Click to collapse
And the phone is recognized fine when in regular mode. Though, whenever I reboot the phone into the Bootloader using adb, it restarts into the fastboot, but it doesn't change to "Fastboot USB" and shortly after I get a "USB Device Not Recognized" on my PC and it saying something about it malfunctioning. So I get stuck on "Waiting for device" when trying out this command "fastboot oem get_identifier_token."
Any ideas? I'm trying to unlock the bootloader and root so that I can install custom ROMs and kernels.
Hey there! Sorry my fix didn't work for you.
My question is, are you running windows 8 or 8.1? The reason I ask is because the 8.1 update has broken fastboot apparently. I don't remember the last time I tried on my computer to see if fastboot still works or not since I updated to 8.1.
If you are running 8.1 windows then the guide at droid-now.com seems to have worked for many people. Go to that site and search fastboot fix windows 8.1 or you could just Google that too I guess. I would paste the link right now but my phone is being stupid and not letting me paste it ATM. :-|
If that doesn't work then you may be able get what you need done by dual booting into Ubuntu if you feel comfortable doing so. You could easily make a bootable flash drive that you could boot into just for an emergency. I just used one for about 4 days while fixing my computer after I accidentally erased the partition tables of my hard drive, trying to make a permanent installation of Ubuntu. Got it fixed BTW! ats self on back:
Keep us posted if you get it fixed or have any more questions! I hope I've been at least a little helpful. I'll try to help any more I can if possible!
Good luck!
Kevin
transmitted via skynet
_kevn_ said:
Hey there! Sorry my fix didn't work for you.
My question is, are you running windows 8 or 8.1? The reason I ask is because the 8.1 update has broken fastboot apparently. I don't remember the last time I tried on my computer to see if fastboot still works or not since I updated to 8.1.
If you are running 8.1 windows then the guide at droid-now.com seems to have worked for many people. Go to that site and search fastboot fix windows 8.1 or you could just Google that too I guess. I would paste the link right now but my phone is being stupid and not letting me paste it ATM. :-|
If that doesn't work then you may be able get what you need done by dual booting into Ubuntu if you feel comfortable doing so. You could easily make a bootable flash drive that you could boot into just for an emergency. I just used one for about 4 days while fixing my computer after I accidentally erased the partition tables of my hard drive, trying to make a permanent installation of Ubuntu. Got it fixed BTW! ats self on back:
Keep us posted if you get it fixed or have any more questions! I hope I've been at least a little helpful. I'll try to help any more I can if possible!
Good luck!
Kevin
transmitted via skynet
Click to expand...
Click to collapse
I am running Windows 8.1, however it looks like the fix only applies to Intel motherboards connecting through USB 3.0 ports. I do have USB 3.0 ports, but my motherboard is AMD and my USB3 controller reads "VIA USB 3.0 eXtensible Host Controller - 0100 (Microsoft)." I'm not sure that the fix applies to me, unfortunately. Also, I am not connecting my phone to my PC using the USB3.0 ports.
I tried downloading the USB 3.0 Drivers for Windows 8 64-bit on the manufacturer's website for my motherboard (http://www.gigabyte.us/products/product-page.aspx?pid=4305), but when I try to update my drivers to the ones I got from the website it says that the Microsoft provided ones are the most recent/ up to date drivers.
Daniuhl said:
Specs: Windows 8 64-bit. Clean and restored HTC EVO 3D. HBOOT 1.58.0000.
I have tried almost everything, but I can't get my phone recognized in fastboot mode.
I tried what was listed here: http://forum.xda-developers.com/showthread.php?p=39218156#post39218156
And the phone is recognized fine when in regular mode. Though, whenever I reboot the phone into the Bootloader using adb, it restarts into the fastboot, but it doesn't change to "Fastboot USB" and shortly after I get a "USB Device Not Recognized" on my PC and it saying something about it malfunctioning. So I get stuck on "Waiting for device" when trying out this command "fastboot oem get_identifier_token."
Any ideas? I'm trying to unlock the bootloader and root so that I can install custom ROMs and kernels.
Click to expand...
Click to collapse
Be Advised, there is perhaps a way , you wil find in the link below, but be sure to use the right intel driver And only if you hae an intel chipset for usb3 , please read the comments and my bad experience :
Under win8.1/X64 that if you have(like me) an Intel 8 /c220 (or with a 4th generation like intel I7 4770k) you may encounter a big mess , and perhaps you''l have to do a clean install of win 8.1 : all the usb2 DEVICES were disconnected after the first iusb3xhc.inf driver install !! So no more usb/Bluetooth keyboard+mouse , fortunately i had an old ps2 keyboard and i was able to delete only with "tab/alt Tab/ctrl tab" keys the
"intel usb3 extensible " line in device manager, and as soon as i done a refresh (ALT+A) in device manager the previous driver(Microsoft) was reinstalled by win 8.1 andall the usb2 devices connected (mouse/keyb/hub etc)
http://plugable.com/2012/12/01/windo...#comment-19066
see there there's in the last comments at the bottom , Andrew(tks to him!)a link + modified drivers for intel8/c220)
and for me it worked mouse/keyB were functional during all the process
next step check the fastboot adb is working now
Here you go... http://forum.xda-developers.com/showthread.php?t=2061435
A later post I made (I havent updated the OP, shame on me...) is a link to some universal drivers from CWM that works fantastic! - http://forum.xda-developers.com/showthread.php?p=40108463#post40108463
Before trying this I would goto your device manager and right click on the currently installed drivers and uninstall them before installing the drivers again.
Hope that helps. I am using the link found in that second link and fastboot and adb works perfect. Also, while you can boot into fastboot, stock 1.58 will not let you run a lot of fastboot commands and will need to flash a different hboot.
Hello pretty nooby ;however, im stuck i recently wanted to try an older cm10.2 rom from the unstable newer ones and decided to go back to cm11 and i decided to reformat my data leaving me emptiness. I am now stuck with not being able to coneect to a device or external storage i can charge though. so please help any solution? im pretty sure i didnt enable mtp and put on debugging... Thx in advance
Edit: this phone doesnt support otg how may i cant connect adb it says waiting for device when i try to flash twrp
fizzlemcdizzle said:
Hello pretty nooby ;however, im stuck i recently wanted to try an older cm10.2 rom from the unstable newer ones and decided to go back to cm11 and i decided to reformat my data leaving me emptiness. I am now stuck with not being able to coneect to a device or external storage i can charge though. so please help any solution? im pretty sure i didnt enable mtp and put on debugging... Thx in advance
Click to expand...
Click to collapse
1. Did you have ADB and fastboot drivers installed?
2. Did you enable USB Debugging?
3. Use USB cable that came with your phone.
luqman98 said:
1. Did you have ADB and fastboot drivers installed?
2. Did you enable USB Debugging?
3. Use USB cable that came with your phone.
Click to expand...
Click to collapse
i enabled usb debugging
original cable
adb fast boot i tried to install...
luqman98 said:
1. Did you have ADB and fastboot drivers installed?
2. Did you enable USB Debugging?
3. Use USB cable that came with your phone.
Click to expand...
Click to collapse
im now installing the 4.3 drivers
this should fix it
fizzlemcdizzle said:
im now installing the 4.3 drivers
this should fix it
Click to expand...
Click to collapse
Did nada my device cant be recognized i get it recognized and a hazardous driver sign. I cant boot into os i reformatted data now im stuck in cwm and bootloader pretty unique also because this phone doenst allow otg helppp!!!
whilst trying to update the "Android" drivers it says the third-party inf does not contain digital signature verification
from this thread
http://forum.xda-developers.com/showthread.php?t=1583801
i also once im in cwm get a new driver name for my device ls970 my phone name
fizzlemcdizzle said:
whilst trying to update the "Android" drivers it says the third-party inf does not contain digital signature verification
from this thread
http://forum.xda-developers.com/showthread.php?t=1583801
i also once im in cwm get a new driver name for my device ls970 my phone name
Click to expand...
Click to collapse
Search for your LG's drivers at their website or around the net and install.
Sent from my GT-S5300 using Tapatalk 2
luqman98 said:
Search for your LG's drivers at their website or around the net and install.
Sent from my GT-S5300 using Tapatalk 2
Click to expand...
Click to collapse
i have now do i have to locate and update with this driver?
i have installed the drivers like 5 time and the wizard said it was installed succesfully now what do i do?
am i missing a step?
fizzlemcdizzle said:
i have installed the drivers like 5 time and the wizard said it was installed succesfully now what do i do?
am i missing a step?
Click to expand...
Click to collapse
Flash stock ROM here: http://www.mylgphones.com/sprint-lg-optimus-g-ls970-software-update-ls970zvc.html
Or I'm wrong?
I don't know why my device won't be recognized I heard it might be a kernal from another thread with a similar situation.
fizzlemcdizzle said:
I don't know why my device won't be recognized I heard it might be a kernal from another thread with a similar situation.
Click to expand...
Click to collapse
Man you really don't have a clue do you!!
Why in hell would you need OTG to flash a rom? Do you even know what OTG is?
Stop ignoring people that give you the solution too. It's really bad manners.
So download the stock rom and flash it.
You should spend a day reading up first before you damage the phone permanently.
Sorry if not being clear I have been listening my phone has a hardware issue and I'm not to much of a noob have tried each comment. I'm not to nooby but I have downloaded the drivers my device is not being recognized correctly I have a hazardous icon in device manager on my android phone lg ls970. My phone does not support otg I'm trying to install .zips through a flash drive and otg cable. I'm sorry if waisting peoples time with my apparently nooby question. Please c correct me if I'm wrong thanks for the support.
Let me be clearer I'm sorry for not spelling it out well enough. I have installed drivers many times I have installed the driver however my phone is not being recognized correctly I have uninstalled and tried again. Otg which I looked it up pretty handy in these situations, doesn't work for this phone (due to outputting)I had a cm10.2 kernal which may have had something do do with this. I have come to believe that its a hardware problem with the female port I will try again on another computer tomorrow and see.
What I want to know is why it still recognizes something and if its fixable?
Thx
I have fixed thanks luqman98 it was a problem with windows not allowing me to install drivers due to 8.1 update
http://www.winbeta.org/news/windows...ly-watermark-finally-removed-hotfix-kb2902864
thx
Hey!
This is my first time posting, but I have read tons of threads on here over the last year or so with my Droid DNA.
A while ago, I rooted my DNA, and unlocked the Bootloader, and used moonshine for S-OFF. I now want to undo all that I have done. Wiping data is no issue, I backed up all my info. I plan to get a new phone soon. Basically, I can't get adb drivers to work. So I deleted my drivers, and installed the ones mentioned in the thread linked below, and I can't find how to get these drivers to work.
My plan is to follow this thread, using step 3 (for moonshine). I have TWRP installed, and flashed the lock_bootlader.zip file provided there. I cannot get adb to work, however, for the next step. For example, "adb devices" returns no devices. And thus i cannot use adb commands. When I run "adb devices", it shows this. What do I do??
Thanks
Some more clarification:
I might also add that Device manager shows my phone as "HTC6435LVW", under "Portable Devices". It seems to recognize it as an MTP Device when I try to update the drivers, and won't let me update the drivers, because "The best driver software for your device is already installed".
In addition, HTC Sync Manager does not recognize my phone either. I should mention that I already chose "Reset Phone" from the Settings menu, and then also did a Factory Reset from TWRP.
I'm so confused by all this - Why can't I get ADB to recognize it?? I have been and will continue to be searching for solutions to this problem here on XDA and also on Google. And do I even need to do all this to give my phone back to Verizon?
Try getting the drivers from PDAnet. If you are using Windoze 8 or 8.1 , good luck.
RLGL said:
Try getting the drivers from PDAnet. If you are using Windoze 8 or 8.1 , good luck.
Click to expand...
Click to collapse
I tried that, it gets stuck at the USB Driver Installation page, when it asks to connect your phone. I have USB debugging enabled, and I even installed PdaNet on my phone to try to use their "USB Mode". The DNA has not USB options for Mass Storage, etc like the pdanet driver help page ( pdanet . co / driver ) (It wont let me post a link because I'm a new user, sorry) tells me to look for.
Windows device manager does not recognize it as an Android phone, but instead as a portable device, could this be a problem?
Thanks for your reply
I am very interested in this as I am having a similar problem. This is the guide I attempted numerous times with no success http://forum.xda-developers.com/showthread.php?t=2293919.
av ed said:
I am very interested in this as I am having a similar problem. This is the guide I attempted numerous times with no success http://forum.xda-developers.com/showthread.php?t=2293919.
Click to expand...
Click to collapse
Ok thanks I will try this when I get home. Glad to see I'm not the only one with the problem!
EDIT: Thats the thread I am following, as I stated in the OP.
[/URL]
antrom1818 said:
I tried that, it gets stuck at the USB Driver Installation page, when it asks to connect your phone. I have USB debugging enabled, and I even installed PdaNet on my phone to try to use their "USB Mode". The DNA has not USB options for Mass Storage, etc like the pdanet driver help page ( pdanet . co / driver ) (It wont let me post a link because I'm a new user, sorry) tells me to look for.
Windows device manager does not recognize it as an Android phone, but instead as a portable device, could this be a problem?
Thanks for your reply
Click to expand...
Click to collapse
My device manager shows 2 entries:
Portable device
HTC6435LVW
and
Android USB Device
My HTC
You did not state the OS your computer has.........
See post from Santod040
RLGL said:
[/URL]
My device manager shows 2 entries:
Portable device
HTC6435LVW
and
Android USB Device
My HTC
You did not state the OS your computer has.........
See post from Santod040
Click to expand...
Click to collapse
Windows 7, and my Device Manager does NOT show the Android USB Device>My HTC. Thats the problem that I am asking for help with, the USB drivers.
antrom1818 said:
Windows 7, and my Device Manager does NOT show the Android USB Device>My HTC. Thats the problem that I am asking for help with, the USB drivers.
Click to expand...
Click to collapse
Try a different cable.
RLGL said:
Try a different cable.
Click to expand...
Click to collapse
Thanks for the suggestion, I will try it when I get home and report back with an edit to this post!
EDIT: Nope, didn't work. Momentarily, I got it to install drivers. During that time, adb worked but not fastboot. So then I deleted the drivers to try to reinstall for fastboot, and now neither of them works.
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...