Right, Ive had my TF201 for a good while now and I successfully rooted it once before. However I lost my root at one point when doing updates without realising the possibility of that happening. Now I hadnt bothered to look in to the matter too much over the past 6 or so months but now that I started dabbling with my tablet again I've come to realise that no matter which machine I connect the prime, it wont be recognized by ADB.
I've tried with Windows 7 64 and 32 bit machines and one ubuntu (I even tried to manually route the ADB to right tracks, but no avail).
When connecting to Windows machine, only unknown device shows up in the device manager and the drivers cannot be applied to the device.
Now I'm no expert in this whole topic, otherwise I wouldnt be where I am right now but the only conclusion is that my device is bricked to some degree. Can someone help me clean up my mess? >.< -or is it even possible to begin with?
Current situation: The device is sitting at Android 4.1.1 and Firmware 10.4.2.17 and the device is asus unlocked. Since the device isnt rooted my Voodoo OTA Rootkeeper and ROM Manager are completely useless because they were installed after the (possible) bricking happened.
Where should I go next?
ichihaifu said:
Right, Ive had my TF201 for a good while now and I successfully rooted it once before. However I lost my root at one point when doing updates without realising the possibility of that happening. Now I hadnt bothered to look in to the matter too much over the past 6 or so months but now that I started dabbling with my tablet again I've come to realise that no matter which machine I connect the prime, it wont be recognized by ADB.
I've tried with Windows 7 64 and 32 bit machines and one ubuntu (I even tried to manually route the ADB to right tracks, but no avail).
When connecting to Windows machine, only unknown device shows up in the device manager and the drivers cannot be applied to the device.
Now I'm no expert in this whole topic, otherwise I wouldnt be where I am right now but the only conclusion is that my device is bricked to some degree. Can someone help me clean up my mess? >.< -or is it even possible to begin with?
Current situation: The device is sitting at Android 4.1.1 and Firmware 10.4.2.17 and the device is asus unlocked. Since the device isnt rooted my Voodoo OTA Rootkeeper and ROM Manager are completely useless because they were installed after the (possible) bricking happened.
Where should I go next?
Click to expand...
Click to collapse
Sounds like the cable is faulty. Borrow a new one to test or get a cheap one off eBay.
flumpster said:
Sounds like the cable is faulty. Borrow a new one to test or get a cheap one off eBay.
Click to expand...
Click to collapse
While I find that unlikely, I will try to look for a new one. But meanwhile lets assume that its not indeed the case, is there anything I could do at that point?
ichihaifu said:
While I find that unlikely, I will try to look for a new one. But meanwhile lets assume that its not indeed the case, is there anything I could do at that point?
Click to expand...
Click to collapse
Why do you find that unlikely?
There are cases exactly the same as yours all over this forum where the cable can charge the prime but cannot be used to install drivers etc.
http://forum.xda-developers.com/showpost.php?p=37662700&postcount=539
http://forum.xda-developers.com/showthread.php?p=39303129&highlight=cable#post39303129
flumpster said:
Why do you find that unlikely?
There are cases exactly the same as yours all over this forum where the cable can charge the prime but cannot be used to install drivers etc.
http://forum.xda-developers.com/showpost.php?p=37662700&postcount=539
http://forum.xda-developers.com/showthread.php?p=39303129&highlight=cable#post39303129
Click to expand...
Click to collapse
Hmm, alright. Just because I havent really roughed up the cable at all and everything worked fine until the said date.
But for now theres no way to try another cable, I'l look for new one next week.
ichihaifu said:
Right, Ive had my TF201 for a good while now and I successfully rooted it once before. However I lost my root at one point when doing updates without realising the possibility of that happening. Now I hadnt bothered to look in to the matter too much over the past 6 or so months but now that I started dabbling with my tablet again I've come to realise that no matter which machine I connect the prime, it wont be recognized by ADB.
I've tried with Windows 7 64 and 32 bit machines and one ubuntu (I even tried to manually route the ADB to right tracks, but no avail).
When connecting to Windows machine, only unknown device shows up in the device manager and the drivers cannot be applied to the device.
Now I'm no expert in this whole topic, otherwise I wouldnt be where I am right now but the only conclusion is that my device is bricked to some degree. Can someone help me clean up my mess? >.< -or is it even possible to begin with?
Current situation: The device is sitting at Android 4.1.1 and Firmware 10.4.2.17 and the device is asus unlocked. Since the device isnt rooted my Voodoo OTA Rootkeeper and ROM Manager are completely useless because they were installed after the (possible) bricking happened.
Where should I go next?
Click to expand...
Click to collapse
I gained root on 4.1.x via twrp and supersu, just after unlocking it. I am not shure if reinstalling 4.1.was really useful...but I did.
I factory reset my kindle fire and I went through the setup and it started updating and when it was finished it went black. After I realized it was bricked I tried the unbrick tool but I couldn't get my kindle to stay connected to my computer for long enough to use it. Can anyone help me out?
Seanballer94 said:
I factory reset my kindle fire and I went through the setup and it started updating and when it was finished it went black. After I realized it was bricked I tried the unbrick tool but I couldn't get my kindle to stay connected to my computer for long enough to use it. Can anyone help me out?
Click to expand...
Click to collapse
This is how you unbrick ;
http://forum.xda-developers.com/fire-hd/development/unbrick-fire-hd-6-7-flashing-lollipop-t3405797
Don't rush it, take your time !
/reader.sh not working .. its just hang there .............
aamszia said:
/reader.sh not working .. its just hang there .............
Click to expand...
Click to collapse
I am running into the same issue. I had rooted the Fire 6 (4th gen) and it has SuperSU Installer on it still after I thought I had restored back to factory and this is preventing me from doing any updates. I also no longer have the recovery option (VolUp+Power), it just blinks and reboots so I don't even have TWRP. I tried following the restore process above using a Boot USB but the READER.SH does nothing. I read it was maybe the USB hardware in the computer so I've tried 5 different computers all with the same result, both with a regular USB cord and fastboot cord. READER.SH just does nothing and I have to CTRL+C out. I'd say try other computers to see if that works. Anyone have any idea why mine isn't working?
ccbst10 said:
I am running into the same issue. I had rooted the Fire 6 (4th gen) and it has SuperSU Installer on it still after I thought I had restored back to factory and this is preventing me from doing any updates. I also no longer have the recovery option (VolUp+Power), it just blinks and reboots so I don't even have TWRP. I tried following the restore process above using a Boot USB but the READER.SH does nothing. I read it was maybe the USB hardware in the computer so I've tried 5 different computers all with the same result, both with a regular USB cord and fastboot cord. READER.SH just does nothing and I have to CTRL+C out. I'd say try other computers to see if that works. Anyone have any idea why mine isn't working?
Click to expand...
Click to collapse
I know this is old, but so you have the all the drivers installed and showing up in your computer's device manager?
The unbrick process and iso posted do not work with the newer FireOS versions starting with FireOS 5.3.1. Ask me how I know besides that it is posted a the top of this thread: https://forum.xda-developers.com/fire-hd/development/unbrick-fire-hd-6-7-flashing-lollipop-t3405797
I have two bricked devices in my closet. Do not think there has been any movement on finding a way around it.
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.
/title
since draxie's utility links are down, i'm following the tutorial. i got as far as making the unlock.code (although i may have done it wrong since i was on cm11 for safestrap when using get_code.bat, so i'll redo it after i fix the issue mentioned) and installing the adb drivers. however, i'm having issues.
despite the fact i can see the drivers as an ADB device, it refuses to show in adb devices or recognize at all in adb, and adb is enabled. no amount of changing the setting or replugging the device does it work.
this prevents me from flashing the vuln aboot or twrp cubed at all in shell. i had to install and uninstall safestrap and cm11 like 2 times just to copy the files in. they are in the root of /sdcard/ and / (just in case i guess?)
i have a kindle fire hdx7, thor, on fire os 4.5.2 (can't remember full ver. number). it's rooted properly. unsure as to what to do next.
thanks for any help.
Few questions
What OS is on your PC ?
Are you using the official amazon drivers or Other?
Have you tried using a different usb cable and USB port (USB3 causes issues)
Mr McBoatface said:
Few questions
What OS is on your PC ?
Are you using the official amazon drivers or Other?
Have you tried using a different usb cable and USB port (USB3 causes issues)
Click to expand...
Click to collapse
1. win 8.1 x64
2. official lab126 drivers
3. yeah.
however, the problem was resolved by using a PC (a old dell inspiron e1505 on win7 ultimate x86) that was never used for ADB.
process went smoothly and i'm running on cm13 right now.
It's amazing what a change in hardware can do Enjoy the unlocked tablet
Mr McBoatface said:
It's amazing what a change in hardware can do Enjoy the unlocked tablet
Click to expand...
Click to collapse
Including cables which so many take for granted but are often subpar.
Davey126 said:
Including cables which so many take for granted but are often subpar.
Click to expand...
Click to collapse
My two recent purchased HDX arrived yesterday bought on ebay both sold faulty 1 not charging the other with a crack in the screen that slighty limits the use of touch screen top left hand corner affected. It's fine for video playback as the crack is on the black border.
Anyway I was expecting to have to change the internal usb cables on the non-charging one..... but it's perfect not a thing wrong with it. Didn't even use contact cleaner it just worked, 3 different chargers all fine. Previous owner had a dodgy cable.
Have to stop buying these damn tablets :laugh: