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.
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.
Guys I have already rooted my sgs3 and used many other roms. but few months earlier i put 4.3 stock rom to my device.
even now my phone is getting detected via odin(when it is turned on) and kies. But when i put it into the download mode phone isnt getting detected by odin. what i actually need to do it install custom recovery and root this device.
but now framaroot is not working and i have tried many other apks. please help me out
SLDarKprince said:
Guys I have already rooted my sgs3 and used many other roms. but few months earlier i put 4.3 stock rom to my device.
even now my phone is getting detected via odin(when it is turned on) and kies. But when i put it into the download mode phone isnt getting detected by odin. what i actually need to do it install custom recovery and root this device.
but now framaroot is not working and i have tried many other apks. please help me out
Click to expand...
Click to collapse
Aren't you just missing some drivers? Maybe try to reinstall them: http://forum.xda-developers.com/showthread.php?t=961956
Also make sure to allow drivers to interact with your device if anything prompts while in Odin.
Android Debugging activated?
blint6 said:
Aren't you just missing some drivers? Maybe try to reinstall them: http://forum.xda-developers.com/showthread.php?t=961956
Also make sure to allow drivers to interact with your device if anything prompts while in Odin.
Click to expand...
Click to collapse
Have you tried installing Sammy's USB driver?
And I'm presuming the device IS on download mode already (I don't believe it appears on Odin while on normal mode)
1. yes i have already installed drivers and phone is detecting via KIES and ODIN when it is turned on.. it suddenly disconnect whenever i put into download mode.
2. yep usb debugging is activated...
3. Im using 4.3 stock rom.. arent there any other way to root this device without pc .. coz i checked lot of forums but none helped me..
4. my pc - windows 10. but i dont think that it will be a issue coz it's detected when it's turned on (means not using download mode).
SLDarKprince said:
1. yes i have already installed drivers and phone is detecting via KIES and ODIN when it is turned on.. it suddenly disconnect whenever i put into download mode.
2. yep usb debugging is activated...
3. Im using 4.3 stock rom.. arent there any other way to root this device without pc .. coz i checked lot of forums but none helped me..
4. my pc - windows 10. but i dont think that it will be a issue coz it's detected when it's turned on (means not using download mode).
Click to expand...
Click to collapse
Bumping Up this thread since i have really same issue, as in literally the same.
Anyone can help me/us?
xaiury said:
Bumping Up this thread since i have really same issue, as in literally the same.
Anyone can help me/us?
Click to expand...
Click to collapse
mate you have to try a different PC or a port. I have fixed my issue using another PC
Download vroot PC Latest Version VRoot 1.7.8
http://www.vrootdownload.com
Downloading mode only..
I have tried 10000000000000000000000000000 tips tricks and almost everything in this and other websites.. but there is no solution for this:
I have GT-I9300 Pathetic galaxy SIII and since I tried flashing recovery to this it goes into download mode... and its been there ever since.. i have downloaded 32 different kind of drivers claiming Samsung drivers.., buying and trying 8 different USB Cables, formatted my laptop 3 time in order to get it detected by ODIN 3.04 to 3.12... or kies or Smart switch.. working on this piece of crap since 3 weeks day and night but getting nowhere,... If any one knows a way to get it fixed... EVEN IF IT NOT DETECTED BY ODIN OR KIES.
PLZ HELP....
Gr8mobiPro said:
I have tried 10000000000000000000000000000 tips tricks and almost everything in this and other websites.. but there is no solution for this:
I have GT-I9300 Pathetic galaxy SIII and since I tried flashing recovery to this it goes into download mode... and its been there ever since.. i have downloaded 32 different kind of drivers claiming Samsung drivers.., buying and trying 8 different USB Cables, formatted my laptop 3 time in order to get it detected by ODIN 3.04 to 3.12... or kies or Smart switch.. working on this piece of crap since 3 weeks day and night but getting nowhere,... If any one knows a way to get it fixed... EVEN IF IT NOT DETECTED BY ODIN OR KIES.
PLZ HELP....
Click to expand...
Click to collapse
Relax.. I understand how frustrating it can be.
I need a detail explanation of what you did to get it into that state and what you've tried. A bullet point list will suffice. I just need to know so I can work out how buggered it is and where to go from here.
I need to know which PC operating system you're using, which variant of s3 you have including its region (this can be determined by the sticker in the battery compartment unless you already know.
There is a possibility it is your os not detecting the device because of drivers but if you've tried formatting and starting over then it shouldn't have any issues. The only other option is to manually edit the drivers ".cat" file with the s3's actual physical address before installing the drivers, but this is in extreme circumstances when the os is not "playing ball".
Also remove kies or at least stop all of its running processes when using odin.
My advice at this stage is to manually remove all drivers from the pc OS regarding the s3 and wait until we figure out where the s3 is at. I have a gdrive with some useful stuff that I know works on Windows XP flawlessly. https://drive.google.com/folderview?id=0B4vTiHTBB629ZW5vQndpbjFnblk
One question though.. When you pull the battery out and reinsert it. Does the phone automatically boot to download mode, is it stuck there permanently or does it boot loop?.
Beamed in by telepathy.
shivadow said:
Relax.. I understand how frustrating it can be.
I need a detail explanation of what you did to get it into that state and what you've tried. A bullet point list will suffice. I just need to know so I can work out how buggered it is and where to go from here.
I need to know which PC operating system you're using, which variant of s3 you have including its region (this can be determined by the sticker in the battery compartment unless you already know.
There is a possibility it is your os not detecting the device because of drivers but if you've tried formatting and starting over then it shouldn't have any issues. The only other option is to manually edit the drivers ".cat" file with the s3's actual physical address before installing the drivers, but this is in extreme circumstances when the os is not "playing ball".
Also remove kies or at least stop all of its running processes when using odin.
My advice at this stage is to manually remove all drivers from the pc OS regarding the s3 and wait until we figure out where the s3 is at. I have a gdrive with some useful stuff that I know works on Windows XP flawlessly. https://drive.google.com/folderview?id=0B4vTiHTBB629ZW5vQndpbjFnblk
One question though.. When you pull the battery out and reinsert it. Does the phone automatically boot to download mode, is it stuck there permanently or does it boot loop?.
Beamed in by telepathy.
Click to expand...
Click to collapse
1st of all I want to thank you bro for reply...
Now..
I am using Windows 10 64bit, using Samsung galaxy sIII GT-I9300 Indian single sim varient.
I rooted it using KingoRoot successfully but I found I wasn't able to get SuperSU and without that I was not able to use root fun properly so I tried to flash the same with flashFire.. it failed as it require SuperSU. So I tried installing TWRP recovery from playstore and it started flashing and after reboot, It stuck on the Downloading mode.. No matter how many buttons I tried pushing combined it stuck on downloading mode...
I tried almost all method on YouTube and websites but it still don't work. Worst thing .. I tried fixing the same by Kies as well as ODIN but .. I never detect my phone.. when i connect my phone after uninstalling and Or installing the samsung driver and Kies as well.. windows didn't recognise it.
I am about to give up n this and almost ready to smash the phone with wall hammer and throw it under my car tyres but I committed myself not to do that before 14th May.
The problem is most likely Windows 10 64bit. I'm quite sure the drivers don't agree with them.
You're going to have to find an older OS and try it. Either use a virtual machine or dual boot and load up a real OS like XP. Then we can begin the proper problem solving. I hate putting percentages on things but I'm 90% confident that windows 10 is an issue here, mainly for the fact it is 64bit and the drivers aren't made for that.
As for button combo's if they don't work while booting and it goes straight to download mode then there is a big problem and it could be bricked. You can try holding just the power button for about 15 seconds while in download mode and it "should" attempt to reboot. If not then as I said, big issue ahead.
No matter what you need to get it seen by odin so get yourself xp somehow and use the stuff on my gdrive. You need to get yourself a copy of the latest firmware for your phone, ready to flash via odin should you get it to see the phone.
Beamed in by telepathy.
Windows 10 to win7
shivadow said:
The problem is most likely Windows 10 64bit. I'm quite sure the drivers don't agree with them.
You're going to have to find an older OS and try it. Either use a virtual machine or dual boot and load up a real OS like XP. Then we can begin the proper problem solving. I hate putting percentages on things but I'm 90% confident that windows 10 is an issue here, mainly for the fact it is 64bit and the drivers aren't made for that.
As for button combo's if they don't work while booting and it goes straight to download mode then there is a big problem and it could be bricked. You can try holding just the power button for about 15 seconds while in download mode and it "should" attempt to reboot. If not then as I said, big issue ahead.
No matter what you need to get it seen by odin so get yourself xp somehow and use the stuff on my gdrive. You need to get yourself a copy of the latest firmware for your phone, ready to flash via odin should you get it to see the phone.
Beamed in by telepathy.
Click to expand...
Click to collapse
I have moved to windows 10 to win7.. and tried all over again (in the process to downgrade the same i formatted by all drive.. thanks to my idiot brother)..
i tried all the same thing again but still no luck..
now trying windows XP 32 bit in virtual machine.
i will let you know..
and i am thinking to hand it over to samsung service center.. lets see what they can do?
Gr8mobiPro said:
I have moved to windows 10 to win7.. and tried all over again (in the process to downgrade the same i formatted by all drive.. thanks to my idiot brother)..
i tried all the same thing again but still no luck..
now trying windows XP 32 bit in virtual machine.
i will let you know..
and i am thinking to hand it over to samsung service center.. lets see what they can do?
Click to expand...
Click to collapse
If you can afford to have them look at it then it's up to you but you will be billed for it as the s3 is out of warranty. They haven't made the s3 for about 3 years now.
Beamed in by telepathy.
shivadow said:
If you can afford to have them look at it then it's up to you but you will be billed for it as the s3 is out of warranty. They haven't made the s3 for about 3 years now.
Beamed in by telepathy.
Click to expand...
Click to collapse
I know.. hopefully it will be done under my expectation.. or last thing I know to donate the same to hammer and trash bin :cyclops:
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...
Hi guys,
I have been searching for hours but I can't seem to find how to fix my problem.
I have a new Z5 Compact that I was trying to flash with the stock firmware but I somehow managed to brick it. I don't think I had the drivers installed properly when I tried to flash with flashtool but since flashtool didn't even detect my phone or appear to begin flashing it I don't know how I bricked it. Anyway after trying for hours to fix it on my own I can't seem to find the information that I need. I have installed the drivers properly as far as I can tell by allowing unsigned drivers on windows 10 but whenever I boot to flash mode the phone isn't detected. Nothing even comes up in Device Manager so there are no options to update drivers or anything. I just hold the volume down button, plug in the usb, the LED briefly flashes red before holding on green and then nothing happens. Neither Flashtool or PC Companion detect the phone and I have tried this on 2 different laptops running Windows 7 and Windows 10. If anyone has any instructions on how to get this to work on Ubuntu I'm willing to try that too as I also have Ubuntu installed but I am really at a loss for what else I can try.
Any help would be greatly appreciated.
Thank you
tokococo said:
Hi guys,
I have been searching for hours but I can't seem to find how to fix my problem.
I have a new Z5 Compact that I was trying to flash with the stock firmware but I somehow managed to brick it. I don't think I had the drivers installed properly when I tried to flash with flashtool but since flashtool didn't even detect my phone or appear to begin flashing it I don't know how I bricked it. Anyway after trying for hours to fix it on my own I can't seem to find the information that I need. I have installed the drivers properly as far as I can tell by allowing unsigned drivers on windows 10 but whenever I boot to flash mode the phone isn't detected. Nothing even comes up in Device Manager so there are no options to update drivers or anything. I just hold the volume down button, plug in the usb, the LED briefly flashes red before holding on green and then nothing happens. Neither Flashtool or PC Companion detect the phone and I have tried this on 2 different laptops running Windows 7 and Windows 10. If anyone has any instructions on how to get this to work on Ubuntu I'm willing to try that too as I also have Ubuntu installed but I am really at a loss for what else I can try.
Any help would be greatly appreciated.
Thank you
Click to expand...
Click to collapse
sounds dumb but have you tried a different port and different cable? i ran into the same problem and found out one of the ports on my laptop doesnt work for data. flashtool is a major pain, it took me three pcs to find one that it worked with and then it took a good 5 tries and reboots to have a successful flash. flashing twrp and then xpower would be easier imo.
civicsr2cool said:
sounds dumb but have you tried a different port and different cable? i ran into the same problem and found out one of the ports on my laptop doesnt work for data. flashtool is a major pain, it took me three pcs to find one that it worked with and then it took a good 5 tries and reboots to have a successful flash. flashing twrp and then xpower would be easier imo.
Click to expand...
Click to collapse
Yeah, I have tried 7 ports and 3 cables across two different pcs. There's a desktop I can try on but I'll wait until tomorrow. It's really frustrating. I just wanted to root so that I could batch install my apps from Titanium but now I have got a brick. In the time that I have spent trying to fix it I could have selected and installed all the apps individually.
tokococo said:
Yeah, I have tried 7 ports and 3 cables across two different pcs. There's a desktop I can try on but I'll wait until tomorrow. It's really frustrating. I just wanted to root so that I could batch install my apps from Titanium but now I have got a brick. In the time that I have spent trying to fix it I could have selected and installed all the apps individually.
Click to expand...
Click to collapse
keep trying, it'll work after you figure out whats wrong with your install, flashtool is real finnicky. If your already soft bricked and only want root id suggest fastboot twrp 3.0.2 then flash xpower 3.0 and be done with it. the only real reason to use flashtool is to flash a new image onto the phone because you cant take an ota.
civicsr2cool said:
keep trying, it'll work after you figure out whats wrong with your install, flashtool is real finnicky. If your already soft bricked and only want root id suggest fastboot twrp 3.0.2 then flash xpower 3.0 and be done with it. the only real reason to use flashtool is to flash a new image onto the phone because you cant take an ota.
Click to expand...
Click to collapse
Thanks for your help. So I can do that without unlocking the boot loader?
tokococo said:
Thanks for your help. So I can do that without unlocking the boot loader?
Click to expand...
Click to collapse
bootloader has to be unlocked before doing any of this.
civicsr2cool said:
bootloader has to be unlocked before doing any of this.
Click to expand...
Click to collapse
Oh, you mean to do that once I have fixed my current issue.
Hmm, I seem to be having a smiliar issue, except instead of flashmode, mine isn't detected in fastboot mode, tried a crap load of drivers and usb ports etc..
EDIT: Got it fixed after following this guide
http://forum.xda-developers.com/z5-compact/general/unlock-bootloader-z5-compact-t3236237
RaunoT said:
Hmm, I seem to be having a smiliar issue, except instead of flashmode, mine isn't detected in fastboot mode, tried a crap load of drivers and usb ports etc..
EDIT: Got it fixed after following this guide
http://forum.xda-developers.com/z5-compact/general/unlock-bootloader-z5-compact-t3236237
Click to expand...
Click to collapse
I tried following that guide but when I try to install the driver it just says "The INF file you selected does not support this method if installation". You didn't happen to have that problem and find a workaround did you?
Just an update on what I have tried if anyone has any suggestions...
I tried inserting a SIM in case that would make any difference. I have also tried it on a desktop pc as well as the two laptops now which is windows 7, 8.1 and 10. The Windows 8.1 attempt was a clean install and I used the advanced boot method to enable the installation of unsigned drivers. I had high hopes for that but it didn't work. What I find curious is there is no activity when I plug the phone in, in flash mode. If I plug it in, in fastboot mode it searches for drivers and the device appears in device manager but with flash mode I get nothing. I'm beginning to think that perhaps the device itself has a faulty flash mode.
tokococo said:
I tried following that guide but when I try to install the driver it just says "The INF file you selected does not support this method if installation". You didn't happen to have that problem and find a workaround did you?
Click to expand...
Click to collapse
Sadly no :/
I managed to flash a Z5 Compact with the same model number without any issues on the same computer that won't detect my handset so I'm pretty sure that it's an issue specific to this handset. Thanks everyone for their suggestions.