Related
Hello Everybody i just got my viewpad 7 2.2 froyo i want to root it ... when i open superoneclick and click root it stucks and doesn't respond
According to this thread "If there is no activity for more than 30 seconds and the terminal display is stuck at 'Running rageagainstthecage....' remove the USB plug momentarily and plug back in." Hope that helps. Good Luck!
hanmin said:
As mentioned above, the AGPS uses server information (via cellular network) to locate the GPS satellite for a quicker fix and hash conditions. For a 4KM tunnel, I'm sure that your phone would have lost both GPS and network signal.
Click to expand...
Click to collapse
hi
try ginger break it worked for me i have gvn apk im my olivepad thread take it try it
Sent from my CSL-MI410 using xda premium
i got the same problem...
It stucks at waiting for device... I've tried pluging it off and back in...
you guy`s try a different usb port i had a simuliar problem with sut restoring the stock rom and i switch port and it worked youy can always try
haree said:
hi
try ginger break it worked for me i have gvn apk im my olivepad thread take it try it
Click to expand...
Click to collapse
Could never get Super One Click 1.7 to work, it just hangs on "Waiting for device" each and every time, no matter what usb port I use or known good cable out of my desk.
Gingerbreak appears to work, I have SuperUser installed, but I cant connect to the device with ADB Shell. lakehousetech's guide basically comes to a halt at the stock backup phase. I cannot get ADB Shell to find any devices period.
elister said:
Could never get Super One Click 1.7 to work, it just hangs on "Waiting for device" each and every time, no matter what usb port I use or known good cable out of my desk.
Gingerbreak appears to work, I have SuperUser installed, but I cant connect to the device with ADB Shell. lakehousetech's guide basically comes to a halt at the stock backup phase. I cannot get ADB Shell to find any devices period.
Click to expand...
Click to collapse
first run setup when connect device then leave the syng prog runninggo to dos shell
enter viewpads cdrom letter here it is g:\ you have to check youre`s
the type adb shell
dont forget superuser on youre viewpad ask for permission grant it hope this wil work
Its also worth noting that I cannot actually boot into a recovery mode. On my HTC phone, I press down volume and power at the same time and it will boot into a BIOS/Recovery screen. Ive read that I need to do something similar with my Viewpad, which is to press volume down, volume up and power on in order to boot into this menu, but nothing ever happens. I get the birds splash screen for a few seconds, then the screen goes black.
elister said:
Its also worth noting that I cannot actually boot into a recovery mode. On my HTC phone, I press down volume and power at the same time and it will boot into a BIOS/Recovery screen. Ive read that I need to do something similar with my Viewpad, which is to press volume down, volume up and power on in order to boot into this menu, but nothing ever happens. I get the birds splash screen for a few seconds, then the screen goes black.
Click to expand...
Click to collapse
yes and keep pressing them all the time until it say`s left upper screen enter recovery screen if that does not work are youre buttons ok do they work?
Alleycatzero said:
yes and keep pressing them all the time until it say`s left upper screen enter recovery screen if that does not work are youre buttons ok do they work?
Click to expand...
Click to collapse
Yes the buttons do work (this is brand new, not even 24 hours has passed), in a normal operation mode, volume goes up and down. On my HTC phone, it was very easy to boot into this recovery mode, so this process of getting clockworkrecovery mod installed isnt totally new to me. Seems like its going to be hit or miss on this tablet.
elister said:
Yes the buttons do work (this is brand new, not even 24 hours has passed), in a normal operation mode, volume goes up and down. On my HTC phone, it was very easy to boot into this recovery mode, so this process of getting clockworkrecovery mod installed isnt totally new to me. Seems like its going to be hit or miss on this tablet.
Click to expand...
Click to collapse
it supposed to be easy with youre pad to don`t know what els then sorry
so, the only way to root is via gingerbreak? SuperOneClick doesn't work right?
armando101 said:
so, the only way to root is via gingerbreak? SuperOneClick doesn't work right?
Click to expand...
Click to collapse
Ive made several dozen attempts to get Super One Click to work (wasted a few hours) and its just a big bowl of fail. Gingerbreak 1.2 is flawless, takes minutes and installs Superuser.
elister said:
Ive made several dozen attempts to get Super One Click to work (wasted a few hours) and its just a big bowl of fail. Gingerbreak 1.2 is flawless, takes minutes and installs Superuser.
Click to expand...
Click to collapse
never had any problems with super one click. make sure the right drivers are installed, open sync (syncusb.exe) and disable your firewall
kwbr said:
never had any problems with super one click. make sure the right drivers are installed, open sync (syncusb.exe) and disable your firewall
Click to expand...
Click to collapse
Are you sure? Lakehousetech's guide to using Super One Click 1.7 does not mention syncusb.exe. Because of this, Im wondering if the rest fo the guide is correct, because even with my device rooted with Gingerbreak, the rest of the guide does not work.
http://forum.xda-developers.com/showthread.php?t=1015005
Hello guys, I'm new here. I'm also facing the same problem in rooting my VP7. Tried different versions of SOC, stuck up on "waiting for device" and SOC stops responding. Tried also GingerBreak, installed and click Root Device and waited for ages and nothing happens. Almost followed all the guides posted here in XDA.
What am I missing? I'm about to give up. Thanks in advance.
same problems....
I am actually in Germany, have a european Viewpad7 and spent hours and days to try to root it. To no avail.
I first read the postings in forums and websites, downloaded the newest (and then the successively older) versions of SuperOneClick 2.2.3. and tried - nothing, its stuck every time before connecting to the device.
Tried different USB-ports, enabled always USB-debugging, tried it with SD-card in or out - nothing. Same result with older versions of SuperOneClick (even using the alternate ADB-parser in "Advanced") - always stuck at the same place before connecting to the device. But - Windows sees the tablet and the card, because the usual window opens (for deciding what to do with the data on the card). Copying pics or music to the card is no problem.
Then - I left the SOC-Road for Gingerbreak. Installed, SD-card removed, runnig forever (25 minutes was the longest I let it run) - nothing. No reboot, no stopping of that little wheel proving that the program is not stuck and runs.
Now, before downloading another potential program for rooting, I became member here at XDA, looking for help.
I run Froyo 2.2.2, last viewsonic update is installed on the Viewpad (bought end of december last year).
I would be glad if someone of the "gurus" here could help me, because I spent three days now and I still don't see the light at the end of the tunnel....
Gerd
boriflash1 said:
... in Germany, have a european Viewpad7 and spent hours and days to try to root it. To no avail ... run Froyo 2.2.2, last viewsonic update is installed on the Viewpad (bought end of december last year) ... and I still don't see the light at the end of the tunnel....
Gerd
Click to expand...
Click to collapse
Okay, let's try a fresh approach to rooting the Vpad7 (does your specs. looked similar to mine under my signature below ?) What computer OS are you running - Vista, Win7 or XP Pro/SP3 like one of my older system?
Might I suggest, if you have access to/borrow one - start with a clean PC (I keep an older Dell laptop, XP Pro/SP3 with OEM drivers and basics installed and running, plus Antivirus & Firewall running (easily turned off/shut down as needed) - and easy enough to reformat or restore (if necessary) -
Setup a subfolder on the drive(s) with all the Vpad7 apps, drivers, devices, patches, etc. so that it's easily accessible; and, do the same for ADB & shell/busybox, etc. so that you can run command lines directly from the c:\ prompt (arrrh ...... the good old DOS days)
You might want to have an extra mini-usb cable (OEM or generic) available that is tested to work with similar devices - to play with "trying" out different USB 2.0 ports as needed.
It's possible that one of the self-configured/auto-installed usb drivers from the Vpad7 might be conflicting or competing as you run SuperOneClick (I sticked with v1.7x as newer ones tend to be more problematic per various posts I've read over the past 6+ months.) Turn off pc's anti-virus & firewall, etc. and do a reboot to clear the pc of any background running programs - and pay attention to any prompts, messages, beeps and alerts that pop-up as you proceed (as they often provide important clues to the likely sources of problem)
Follow the posted directions, step-by-step and do it carefully - upon initial connection, does it see a usb connection, recognize the device, attempt to use/run usb driver installation, etc. If it seemed to stalled while connecting or looking for device/drivers - try quickly removing & reconnecting the Vpad7 to the mini-usb cable, sometimes - this trick it into the "mode" to work (one of our HTC DI2 easily gained root but the 2nd. & newer one would "install" for over 3 hours, then a "clean/stock" fresh pc with the connection trick did it - rooted)
If this is still "no good" or you continue to run into problems - please post with any specific error messages or pop-up during the failed attempt, and let's see what can be done then.
Letitride said:
Okay, let's try a fresh approach to rooting the Vpad7 (does your specs. looked similar to mine under my signature below ?) What computer OS are you running - Vista, Win7 or XP Pro/SP3 like one of my older system?
Click to expand...
Click to collapse
Dear Letitride, first of all thank you very much for trying to help. Let me answer your questions one by one.
My computer runs on Vista home, its a laptop and has all the official windows updates. Four USB-ports, all of them working (checked with my external hard drive). When plugging-in the Viewpad, the window with the options how to open the data on the SD-card immediately opens.
I do not know how to access the data on the Viewpad like you did, but I definitely have Froyo 2.2.2. and the last official update, official rom.
Letitride said:
Might I suggest, if you have access to/borrow one - start with a clean PC (I keep an older Dell laptop, XP Pro/SP3 with OEM drivers and basics installed and running, plus Antivirus & Firewall running (easily turned off/shut down as needed) - and easy enough to reformat or restore (if necessary) -
Click to expand...
Click to collapse
Sorry, I don't know anyone at the moment (as I am travelling) with another computer I could use. So I guess I have to stick with mine. But when I do a restart, all applications running before should be terminated anyway. I could also move all the data without any problem to and from the Viewpad's SD-card.
Letitride said:
Setup a subfolder on the drive(s) with all the Vpad7 apps, drivers, devices, patches, etc. so that it's easily accessible; and, do the same for ADB & shell/busybox, etc. so that you can run command lines directly from the c:\ prompt (arrrh ...... the good old DOS days)
Click to expand...
Click to collapse
Now you lost me. Which drive? Laptop drive? Where do I get the VPad7 apps, drivers, etc? I have to have them before copying them in any subfolder (subfolder of which folder by the way?). Same question for ADB, shell, busybox. Sorry for my stupidity, I am into Windows, but not into Android....And even in Windows I must confess that I almost did not run anything from command lines. Never needed to....
Letitride said:
You might want to have an extra mini-usb cable (OEM or generic) available that is tested to work with similar devices - to play with "trying" out different USB 2.0 ports as needed.
Click to expand...
Click to collapse
I even have three cables and 4 ports and I interchanged already all of them.
Letitride said:
It's possible that one of the self-configured/auto-installed usb drivers from the Vpad7 might be conflicting or competing as you run SuperOneClick (I sticked with v1.7x as newer ones tend to be more problematic per various posts I've read over the past 6+ months.)
Click to expand...
Click to collapse
Already did. I tried them from 1.6 on upwards... No success.
Letitride said:
Turn off pc's anti-virus & firewall, etc. and do a reboot to clear the pc of any background running programs - and pay attention to any prompts, messages, beeps and alerts that pop-up as you proceed (as they often provide important clues to the likely sources of problem)
Click to expand...
Click to collapse
I turned of windows firewall, Avira and the Viewpads antivirus. No success
Letitride said:
Follow the posted directions, step-by-step and do it carefully - upon initial connection, does it see a usb connection
Click to expand...
Click to collapse
YES
Letitride said:
recognize the device,
Click to expand...
Click to collapse
Hmmm.,... it recognizes the SD-card, but not the device. That is also the problem when using SOC....it is stuck at ...looking for device....
Letitride said:
attempt to use/run usb driver installation, etc. If it seemed to stalled while connecting or looking for device/drivers - try quickly removing & reconnecting the Vpad7 to the mini-usb cable,
Click to expand...
Click to collapse
DID, but it did not move of change anything when SOC is stuck.
Letitride said:
sometimes - this trick it into the "mode" to work (one of our HTC DI2 easily gained root but the 2nd. & newer one would "install" for over 3 hours, then a "clean/stock" fresh pc with the connection trick did it - rooted) - If this is still "no good" or you continue to run into problems - please post with any specific error messages or pop-up during the failed attempt, and let's see what can be done then.
Click to expand...
Click to collapse
I do not get any error messages - neither from the Viewpad, nor from Windows. SOC simply stops working, the window gets white and then when I try to close it, it simply states that SOC has a problem in closing. On the second click, it closes.
I hope I was a specific as possible, excuse once again my ignorance concerning android. It definitely seems that my laptop sees the storage device, but not the Viewpad itself. Changing cable or changing USB-ports did not fix that.
Thanks again. I really appreciate your help.
Gerd
boriflash1 said:
I do not get any error messages - neither from the Viewpad, nor from Windows. SOC simply stops ... gets white and ... simply states that SOC has a problem in closing. On the second click, it closes ... ignorance concerning android ... my laptop sees the storage device, but not the Viewpad itself. Changing cable or changing USB-ports did not fix that.
Gerd
Click to expand...
Click to collapse
Edited your details to try to keep it short - it read like there some of the device drivers might be missing or need to be installed.
My laptop was reformatted last month running Vista Business & from my notes, when the Vpad was 1st. connected, it recognized the new hardware (Qualcomm USB device) and proceed to install 3 drivers, enabled a virtual CD-ROM drive with additional setup files, and when it was done including a reboot, the laptop has 6 new hardware/device drivers - and both the new virtual CD-ROM and USB removable device available & working, with USB debugging enabled and once the USB drive was turned on (default is off)
Have you tried to go to Control Panel, click & uninstall all the related USB drivers, including a PC Tools apps auto-configured by the Vpad7 ?
Then, shutdown & reboot the laptop - reconnect the Vpad and let it re-install everything from the beginning. (also, do you have a spare mSD card, an older 8GB or even 4GB mSD would be useful ?)
As for the sub/folder - I was referring to creating to making a subfolder on your laptop's drive, and saving/moving all of the vpad7 related donwloads, SOC and custom Roms, etc. to this folder (and subfolders as necessary to keep it organized.) I put the adB and busybox files, etc. here too as downloaded - in order to run adB using the command prompt per instructions - this Android & linux based "stuff" is new to many of us, but to have fun is to allocate some time to learn them. There are links here on XDA on the basics & it's worthwhile reading.
Also, did the Vpad7 install PC Tools, which is used to sync. files between the laptop & the V?
So after flashing 10/17/15 release of Tesla Arc_Flash I am unable to connect to the phone through adb without deleting the driver and adding it as an adb device. I have installed the LG G3 Verizon drivers but I am still not able to connect. In the device manager it shows that the drivers aren't there but also that they are there as a portable device. hxxp://tinypic.com/r/30ua82f/8
Also the command prompt is below. Brand new adb server started.
hxxp://tinypic.com/r/71myr4/8
Any help would be appreciated. If you need logs or anything else I am happy to provide it. Also since I feel this may get asked... Yes I have USB Debugging turned on. Have tried with Root for adb on and off and nothing seems to work. I can get it to connect through network but I don't want to constantly have to look for the IP address and port. This was also an issue in the previous release of Arc_Flash so please let me know.
Hi! Exactly what drive did you install and where did you get it from? Here is where I get the driver from http://www.lg.com/us/support-mobile/lg-LGVS985. Try rebooting the PC (without the phone connected) after installing the driver. Using the original cable that came with it, connect the phone to a different USB 2.0 port than you had tried previously - it can take up to 10 minutes to finish loading the driver. When it's complete Device Manager should have a listing for the phone in the Modem section, which isn't currently listed in your screenshot. Until you can get that solved you won't be able to reach it with adb.
Have you searched the Tesla ROM thread to see if anyone else has had the issue, in case it's specific to Tesla?
roirraW "edor" ehT said:
Hi! Exactly what drive did you install and where did you get it from? Here is where I get the driver from. Try rebooting the PC (without the phone connected) after installing the driver. Using the original cable that came with it, connect the phone to a different USB 2.0 port than you had tried previously - it can take up to 10 minutes to finish loading the driver. When it's complete Device Manager should have a listing for the phone in the Modem section, which isn't currently listed in your screenshot. Until you can get that solved you won't be able to reach it with adb.
Have you searched the Tesla ROM thread to see if anyone else has had the issue, in case it's specific to Tesla?
Click to expand...
Click to collapse
I searched the ROM thread but found nothing matching what I am experiencing but I followed everything even close to it. I installed those drivers just now and restarted both computer and phone. Still comes up as an unknown driver. There is no modem section inside of the computer still. I can manually add the drivers but it still doesn't seem to help.
Also to add. I also have tried to add it as a modem and it gives Windows Error code (10) that it can not start the driver. I forgot to mention. Windows 10.
Well, I've connected to my phone via adb and used the LG flash tools on Windows 10 last week or the week before, although I have my insider updates set to Fast Ring and I kinda regret it because there was a recent huge push of a beta Windows, and they've broken how I had my video associations set up and I can't get my subtitles to work any more either. Sorry for off topic. My point is since Windows 10 is considered a constant "change in progress", and especially for people like me who joined to get "insider" builds, it's hard to tell what makes things not work. My main reason for even being on Windows 10 is to see what they come up with in their insider builds, but I guess when it mucks with my video enjoying ability, I start losing my patience.
I would seriously consider trying a different PC, or if you have the capability of performing a fresh Windows installation, even of Windows 10, that very possibly would fix it. Or if you just recently, within the last 30 days, upgraded from an earlier Windows to Windows 10, and didn't perform a clean installation, you can revert the upgrade through the the Windows settings. No idea if reverting would solve the problem, either, though.
As @bweN diorD pointed out in another similar thread just yesterday or the day before, when someone in your situation ends up trying a different PC, then everything goes smoothly. As far as the cause, there's too many variables.
If you can't use anyone else's PC, there's an outside chance that you could even do it at a library computer, as long as you don't reboot the PC (which I usually recommend after initially installing the driver, but sometimes things work fine without that). Rebooting a library PC usually undoes all changes, putting it back exactly the way it was.
Let us know how you make out.
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...
Long story short, i did not unlock my bootloader, as this was for my son and I didn't want to get into a habit of updating roms, blah blah blah. Well lessons learned, for the 2nd month in a row an OTA broke my sons tablet, bootloop, can't mount cache to wipe. Last time I was able to plug it in, reload the OTA via ADB sideload. However, no such luck this time. I cannot get windows 10 to see the tablet at all. nothing happens at all when I plug it in. No dings, nothing pops up in device manager, nothing shows up if I scan for it. This is consistent while its bootlooping, hboot, fastboot and in adb sideload from recovery. I've tried several micro USB cables. I do recall having similar issues last month, but eventually one of my cables worked. I do not have that cable with me at the moment and not even sure if it would work this time.
Let's pretend by some miracle I can get this recognized again to reload the OTA, is there anyway I can backup my son's data prior to unlocking the bootloader and rooting? Should have known it would be better to keep it unlocked and rooted.....
ok so fastboot factory reset, did not help, i again had bootloop, wiped cache and that seem to actually be successful this time, but still bootlooping when trying to boot up, and cannot get windows to recognize it any way shape or form in fastboot, recovery, hboot, recovery adb sideload, windows never recognizes it, tried a 2nd machine same result, windows doesn't even attempt to install a driver. The only thing left for me to try is the recovery wipe data/factory reset, which I will be trying shortly once I get some juice, unless someone has a better idea. I'm already past the point of data recovery anyway I presume....son is going to be so disappointed.....
I'll have to say having owned the nexus 7, nexus 7 2, galaxy nexus, nexus 5, nexus 6, nexus 6p and the nexus 9....the Nexus 9 has been the biggest piece of junk...
Sorry I didn't see this sooner. I've had exactly the same issue (N9 not being recognized when it had been windows 10, too. What worked for me, twice, was removing all drivers related to usb then allowing pc to re-install thereby giving me the opportunity to grant the pc/tablet permanent access. I can't remember if I had to choose HBOOT to be recognized. The first time, I followed Wug's NRT toolkit for removal and re-install of drivers (adb). The second time, I think I just used usb deview to wipe drivers. Of course, this messed up the situation for my N5 and N5x (the only device not unlocked and rooted). Those drivers repopulated though. At least you had the foresight to tick off "enable OEM unlocking " as well as adb debugging. Now, if you must, you can start from the beginning.
Yes, I've never had a Nexus device quote like this one. Of the new HTC Nexus phones are priced as suggested, my N5 won't get updated this year. I cannot trust htc after this experience and definitely will not pay a premium to repeat this experience.
Unlocked bootloader has no effect on flashing ota's.
Sent from my Nexus 9 using Tapatalk
Yeah, the problem seems to be with the port, as holding one of a various amount of cables just the right way at least gets W10 to recognize it and install drivers, but it immediately detaches and can no longer see the device. It's unfortunate, as I'm not sure right now what to replace his N9 with. Pixel is just to expensive, and everything else seems to be getting pretty dated.
March 22 2019 - Solved because I'm an idiot. Story on page 2
Trying to Flash TWRP, but the adb packages and driver's I been using that I can find all over the internet just aren't freaking working.
Specifically it's just Fastboot giving me problems, It doesn't even detect devices.
What I need help with:
Adb communicating with Fastboot
How far I got:
Unlocked bootloader (unlock symbol when booting)
Installed plethora of Adb Driver's via Google, Xiaomi, Qualcomm
Used USBDeview to uninstall all drivers even from my past devices and try reinstalling just drivers involving Xiaomi, Poco ect...
What does work:
Adb commands recognized in Miui
Adb commands recognized in Miui Recovery as sideload (after selecting pc suite option)
Miui unlocking tool (was able to unlock and can still detect the device unlocked in Fastboot)
In Miui File Transfer & PTP mode
What I tried:
Different USB ports 2.0 & 3.0 directly in the back of the PC and the front hub
Different USB C cords with and without extension cord (even though that shouldn't matter)
Different drivers old and new
Powershell & CMD as administrator.
What's already been done before you suggest it:
2nd computer, different ports, satanic ritual, different cords, turning PC on and off again after driver installs.
Trying methods from First 5 results when you Google anything along the lines of "Poco f1 adb Fastboot not recongnized"
Uninstalling drivers and retrying
USB Debugging on, duh.
Oem unlock on, duh.
Basically it's this, clearly the device is being recongnized and being talked to, just able to unlock the device via Xiaomi unlock tool is proof enough of that it's detected in and out of Fastboot, but in a adb window via powershell or cmd-here, it's just not recongnized my device in Fastboot. In Miui or recovery theres no issue, they communicate fine.
Or if there's an alternative way to install TWRP that doesn't involve Fastboot I'm all ears on that.
If you can temporarily root it (which I wouldn't how to without fastboot) you could write the recovery directly onto its partition.
(https://blog.matt.wf/flash-your-recovery-image-via-adb-shell-on-android/)
But I suppose you want to flash the recovery to get root. So did you try different stable roms with the Mi Flash tool? Maybe your fastboot got corrupted and it could be solved with an oreo rom. Not sure about rollback protection though.
Ah and to eliminate driver issues: you could always use a live distro like manjaro on a usb stick, install the adb package and check whether fastboot is working in the terminal.
I always go back to linux when windows has its funny moments ._.
lolmensch said:
If you can temporarily root it (which I wouldn't how to without fastboot) you could write the recovery directly onto its partition.
(https://blog.matt.wf/flash-your-recovery-image-via-adb-shell-on-android/)
But I suppose you want to flash the recovery to get root. So did you try different stable roms with the Mi Flash tool? Maybe your fastboot got corrupted and it could be solved with an oreo rom. Not sure about rollback protection though.
Ah and to eliminate driver issues: you could always use a live distro like manjaro on a usb stick, install the adb package and check whether fastboot is working in the terminal.
I always go back to linux when windows has its funny moments ._.
Click to expand...
Click to collapse
I want the recovery so I have an option that isn't miui.
My phone isn't slow, but it's running more than a fair share of mi bloat.
lolmensch said:
If you can temporarily root it (which I wouldn't how to without fastboot) you could write the recovery directly onto its partition.
(https://blog.matt.wf/flash-your-recovery-image-via-adb-shell-on-android/)
But I suppose you want to flash the recovery to get root. So did you try different stable roms with the Mi Flash tool? Maybe your fastboot got corrupted and it could be solved with an oreo rom. Not sure about rollback protection though.
Ah and to eliminate driver issues: you could always use a live distro like manjaro on a usb stick, install the adb package and check whether fastboot is working in the terminal.
I always go back to linux when windows has its funny moments ._.
Click to expand...
Click to collapse
Also can you roll back to 8.1 without twrp, root, or adb?
I tried rolling back via the update screen and selecting the package/downgrade, but Miui won't allow installing/flashing older software, which is something I tried before.
No one else has this problem?
Chocolina said:
No one else has this problem?
Click to expand...
Click to collapse
Why not try Flashify? It comes in the form of an apk and it only requires root, no fastboot. Through it, you can flash TWRP.
Are you connecting the phone to an Intel computer or an AMD? AMD Ryzen has an issue.
tnsmani said:
Why not try Flashify? It comes in the form of an apk and it only requires root, no fastboot. Through it, you can flash TWRP.
Are you connecting the phone to an Intel computer or an AMD? AMD Ryzen has an issue.
Click to expand...
Click to collapse
Don't you need TWRP to install root?
I haven't rooted 1st and then did recovery since the Nexus 5 days, every device I've had since has had root guides that wanted me to fastboot flash the recovery first and install root that way.
And i dont know if my pc is Ryzen, not a pc gamer so all I have is on board, but it is old amd machine running windows 10. I also don't have a monitor these days, I have my pc setup to accept remote desktop so I interact with it that way because it's rare I need a pc these days
All I know is adb works with miui and recovery (sideload) fine, it's fastboot giving me problems, and all the root guides require fastboot
Also same exact issue regarding my mi pad I just got too
https://forum.xda-developers.com/mi-pad-4/help/please-help-troubleshoot-xiaomi-t3910249
lolmensch said:
If you can temporarily root it (which I wouldn't how to without fastboot) you could write the recovery directly onto its partition.
(https://blog.matt.wf/flash-your-recovery-image-via-adb-shell-on-android/)
But I suppose you want to flash the recovery to get root. So did you try different stable roms with the Mi Flash tool? Maybe your fastboot got corrupted and it could be solved with an oreo rom. Not sure about rollback protection though.
Ah and to eliminate driver issues: you could always use a live distro like manjaro on a usb stick, install the adb package and check whether fastboot is working in the terminal.
I always go back to linux when windows has its funny moments ._.
Click to expand...
Click to collapse
Tell me more about this Linux/your method
I never used Linux, so I don't know what I'd do to get it or if I could boot it temporarily off of another form of storage or something.
Chocolina said:
Trying to Flash TWRP, but the adb packages and driver's I been using that I can find all over the internet just aren't freaking working.
Specifically it's just Fastboot giving me problems, It doesn't even detect devices.
Click to expand...
Click to collapse
Are you running a Ryzen PC ? Xiaomi drivers have been reported to have problems with Ryzen builds.
Dose the roms solve touch issue???????
MasterFURQAN said:
Are you running a Ryzen PC ? Xiaomi drivers have been reported to have problems with Ryzen builds.
Click to expand...
Click to collapse
How would I know if it's ryzen?
It's a prebuilt from 5 or more years ago
Chocolina said:
How would I know if it's ryzen?
It's a prebuilt from 5 or more years ago
Click to expand...
Click to collapse
If it's more than 5 years old, then it's not ryzen. Fyi Ryzen is the newest range of CPUs from AMD.
I went out and bought an Intel laptop and it still won't work!!
Found and addressed my issue, and it was because of my Stupidity and old habits keeping me from following directions. But I'm also a little angry at the directions themselves for omitting information that would have been useful to me.
So an old habit of mine is before flashing anything in fastboot, I alway run adb commands to see if my phone, fastboot, and windows are all taking to each other and playing nice. Every phone and device I've had until now hasn't had an issue.
If adb or other apps was showing me my connected devices in System and in Recovery, then why the hell wouldn't it do so in fastboot. So old habits with all my devices since 2012 have been reinforcing my behavior for years until I got this Xiaomi Pocophone and Xiaomi Mi Pad. So as a requisite I've always had and continued to check my devices in adb and performing a reboot test before performing a flash just to make sure the device was listening and taking commands.
The problem with the dozens of guides and videos I watched, none of them said that checking for device first didn't always work, so before flashing recovery I kept trying everything I could to get devices to read back in fastboot or accept a reboot command.
Then In one of the half of dozen xiaomi mi pad adb packages I downloaded, someone wrote a simple script that did the flash anyway even though checking to see the device was recognized came up empty.
Apparently I could have been sending flash commands all this time despite devices showing a blank.
So I did so on pocophone to find out devices and reboot commands didn't work but apparently flashing commands do.
I went out and bought (with the intent to return) a ****ty Intel laptop (made by RCA lmao) just to come to the conclusion that I should have just followed the guides in the first place and save myself trouble instead of relying on my past knowledge and habits.
Chocolina said:
Found and addressed my issue, and it was because of my Stupidity and old habits keeping me from following directions. But I'm also a little angry at the directions themselves for omitting information that would have been useful to me.
So an old habit of mine is before flashing anything in fastboot, I alway run adb commands to see if my phone, fastboot, and windows are all taking to each other and playing nice. Every phone and device I've had until now hasn't had an issue.
If adb or other apps was showing me my connected devices in System and in Recovery, then why the hell wouldn't it do so in fastboot. So old habits with all my devices since 2012 have been reinforcing my behavior for years until I got this Xiaomi Pocophone and Xiaomi Mi Pad. So as a requisite I've always had and continued to check my devices in adb and performing a reboot test before performing a flash just to make sure the device was listening and taking commands.
The problem with the dozens of guides and videos I watched, none of them said that checking for device first didn't always work, so before flashing recovery I kept trying everything I could to get devices to read back in fastboot or accept a reboot command.
Then In one of the half of dozen xiaomi mi pad adb packages I downloaded, someone wrote a simple script that did the flash anyway even though checking to see the device was recognized came up empty.
Apparently I could have been sending flash commands all this time despite devices showing a blank.
So I did so on pocophone to find out devices and reboot commands didn't work but apparently flashing commands do.
I went out and bought (with the intent to return) a ****ty Intel laptop (made by RCA lmao) just to come to the conclusion that I should have just followed the guides in the first place and save myself trouble instead of relying on my past knowledge and habits.
Click to expand...
Click to collapse
Thank you for the info. I learnt something new today.
I also have the same habit of checking whether the adb devices and fastboot devices commands work before starting any flashing. However I don't check the reboot command. It still is a good habit notwithstanding what you have discovered. What happened to you has not happened to me so far, so I am filing this knowledge for future use if the occasion arises.
tnsmani said:
Thank you for the info. I learnt something new today.
I also have the same habit of checking whether the adb devices and fastboot devices commands work before starting any flashing. However I don't check the reboot command. It still is a good habit notwithstanding what you have discovered. What happened to you has not happened to me so far, so I am filing this knowledge for future use if the occasion arises.
Click to expand...
Click to collapse
It was a headache because my precautions weren't working. Next time I'm just going to check if it'll take flash commands anyway before asking for help.
On the plus side, I got to learn what a laptop made by RCA is like. It's **** sure, I'd expected as much, but it was as bad, if not worse than those $99 "windows 8" tablets from 2014-2015 running those archaic Intel Z3735 Atom series processors. Stay away