My tablet is running CM10.1 and TWRP is on it. Past a few common issues, nothing a bit of research hasn't fixed. I can't find what went wrong on this issue. Everything was peachy last week and all drivers worked. I rooted the tablet last month.
Now I can't see the tablet on (2 machines) Windows 7 64bit and I keep getting error code 10 while trying to get the MTP driver in. Both machines give the same error code. On all 18 USB ports, front and rear.
I suspect there is an EBKAC here, but everything I've tried has ruled that out.
Steps taken to fix the driver issue:
rollback via restore, both driver rollback and (wizard) full OS restore
Installed Android SDK - used the USB driver
found driver package on forums
allowed auto-find in Windows hardware wizard
Installed Asus Sync package
manually removed drivers in device store and edited the registry hives - Allowed to rebuild
created a voodoo doll for the ghost of Scooby Doo and danced nekkid in the snow
The tablet shows in device manager, while in camera mode. But not showing storage drives (in Explorer.) In MTP mode it fails to load driver - No drivers = nothing shows in Explorer..
An update, for those in the future users who may find this thread and seek a solution. Sorry about 2xposting. I feel a double post is best, instead of an OP edit.
I did get the issue resolved, but I wiped the device twice and it somehow started to work. Not sure of the cause, or giving an actual known solution. I'm pretty sure I got lucky, by trial and error. Following normal documented troubleshooting on xda. I will share the steps that I took. Which helped get it working.
Here is what I did:
I did all the wiping I could in the latest (contemporary) TWRP. Minus formatting anything.
Used my recovery image of choice, via TWRP and reinstalled it. Let the device settle for 20 minutes after it fully rebooted. (I connected via wireless [n300] @72mbps)
I confirmed it connected and detected.
I rebooted the device into recovery mode and entered TWRP again. Wiping everything I could. Minus formatting anything. I then installed the build I wanted, in this case: CM10.1, sans gapps.
I let the device settle for 20 minutes after it fully rebooted.
I was then able to successfully connect the device. Via the usual means of getting the Asus MTP driver in. Once this milestone was achieved. I then installed gapps. Explorer now shows as expected and I can resume on with other niggling issues for the device.
Related
After some moderate success with One-Click-Root (it failed after giving root and installing CWM), I can't seem to get my Epic to behave on either my laptop or desktop. It still recognizes drivers, but whether it's in Debugging Mode or not, it seems the connection freezes. On XP, explorer.exe locks up unless I unplug the phone. On reinstalling drivers and plugging in the phone, it'll install the phone drivers halfway, halt, and won't continue installing unless I pull the USB cable and reconnect. I've tried resetting the phone with different stock firmware versions but can't seem to get around the problem. When I try to reapply One-Click-Root, half the time it doesn't see the phone, or it halts near the beginning.
Here's what's recently flashed:
Firmware version: 2.2.1
Baseband version: S700.0.5S.EC05
Kernel Version: 2.6.32.9
Build Number: FROYO.EB13
I'm under limited understanding that the baseband and build are a mis-match, but at this point I'm trying anything to get this thing to work. Otherwise it seems I can only flash ROMs via ODIN, and most only seem to support CWM. I've searched for almost a day and haven't seen anyone else with this problem.
Thanks everyone for your time.
Have you tried a different USB cable? EDIT: Also, this should be in Q&A.
Ah, my apologies about posting in the wrong board. I've tried the stock cable, one from RadioShack, and another from an Evo.
I should also note that with or without Debug, the microSD refuses to be explorable on either platform of Windows.
I'd suggest you Odin to stock, then restart the process from there.
I bit the bullet and downloaded Sprint's update, originally believing anything official was evil. So far the update is making things work. I got One-Click-Root to work without a hitch. I'll update on whether or not CWM and a custom ROM works.
CWM v3.0.0.6 has successfully installed. Bonsai4All ROM successfully installed. Mounting with or without Debug still not working, however.
Hello there everyone.
First off, I know this might seem like a subject that's already been covered. Trust me, I've spent the last few days going through every thread I could find on here trying everything out as well as other threads on tips on the net. So I'm posting this because I've tried everything and run out of troubleshooting methods to have a go with. The experts here may relish the challenge of solving this one. Or tear their hair out just like I'm doing. Hence my username. I'm worn out after countless hours of doing this.
Background:
I had a rooted Nexus 7 with superuser and TWRP. Jellybean 4.2.1 update would never work, always got an assert failed or some other error when it tried to do so. I then decided to go back to a previous backup in case something had gone wrong since in order to get on with installing the update.
Previous backup loaded fine. Unfortunately WiFi was not working and just kept on searching forever. After lots of googling and trying all the fixes with my router and so on which failed to solve anything, took the advice of going back to a factory reinstall.
Reinstalled, booted up, selected language on Google Welcome Screen then onto Wifi screen. Stuck on seaching forever. More googling and took advice. Decided to do Nexus Root Toolkit's flash stock+unroot to get back to clean state. After install there's an issue that just won't go away and that is:
Problem:
Google Nexus 7 (Wifi model) won't go past Google screen (this is not the coloured logo, just the word "Google" in white).
Associated problems:
Going into recovery just shows the same screen or sometimes an android lying on its back with a red triangle.. So no stock recovery available. Using fastboot to lock and unlock the bootoader as a recommended fix has no apparent effect with the result just being the same Google screen (padlock icon unolocked or locked depending upon locking status) even after a long wait.
Flash stock+Unroot in Nexus Root Toolkit has the same result. I left the thing on for a long time each time after a factory install because of advice saying to wait and still the same screen all that time. Longest time was 6 hours left on due to frustration and waiting to see if anything at all would happen. It didn't.
I can't access ADB in bootloader. I can only access ADB when the device is in TWRP or CWM menus. (In other words Nexus Root Toolkit complains it can't connect when I'm in the bootloader for example if I want to do any operation that requires ADB, but doesn't complain when in in those two recovery menus). Nexus Toolkit will quite happily do the Flash stock+ unroot and get to the screen where it says wait a while for device to reboot and you can press any key to exit.
I have wiped system, cache, boot, recovery, userdata using both fastboot and JROM Flasher. I can install TWRP or CWD using the Nexus Toolkit and wipe stuff using those but still no joy. I have gone through every permutation many times step by step. I have even used different Jellybean factory images from 4.1.0 to 4.2.1 as well as past backups with the same result each time.
Have used soft bricked and device is on options in Roolkit. No joy.
I have also disconnected the battery as part of the troubleshooting process.
Basically, nothing I can do using the information I've been able to get hold of can get past that screen.
Other quirks:
I have also noticed when installing a factory image a message comes up:
writing bootloader FAILED (remote: (invalid state))
It continues with the rest of the installation however as normal.
Also PdaNet comes up with the message:
Wrong WinUSB Pipes found
If I try Connect Internet (USB) option.
I have downloaded Nexus 7 tablet USB driver revision R06 and tried to use them but my PC will only recongise the device as an MTP device with failed driver install when the tablet is in that endless Google screen.
With the install of the Naked Universal Driver it only recognises the device in the Device Manager as Google Nexus 7 Bootloader Interface.
Driver tests in Nexus Root Toolkit fail. It advises enabling USB debugging as one of the fixes which of course I cannot do as I can't boot up to reach those options.
From this I surmise there is some problem with the drivers. I have tried on two different PCs as well.
Software I have used in all my efforts: Nexus Root Toolkit 1.6.2, Gnex, JROMFlasher, TWRP, CWM, PdaNet, SDK Manager, Nexus 7 tablet USB driver revision R06, Naked Universal Driver 0.72 .
I'd appreciate any advice (apart from sending the thing back), epescially if it's in a step by step easy to follow format. So basically, my question is, how do I fix this? Is it possible to fix?
Many thanks in advance!
I just thought I'd update this, mainly to let people know what to do if they find they have a similar problem to the above.
Basically, as said before none of the fixes worked. I spent a huge amount of time trying everything. So in order to save people massive amounts of time who have pretty much the same problems as I had and spending hours upon hours trying fixes like I did, then the best thing to do is to return your Nexus 7 to where you bought it for a return.
Mine was subsequently discovered to have a hardware fault so I was basically trying to fix the impossible. If you find yourself in the same boat after trying the fixes, and they don't work after a couple of tries, don't do it multiple times like I did. It's just easier, less frustrating and will save you much hair loss, anger and general irritation to let Asus fix it.
Yes, I know some of us get a bee in our bonnet about fixing it ourselves and see returning it as the last resort (like me), but anyway, trust me, just send it back, and save yourselves the trouble in a case like the above.
My tablet has arrived back repaired and works again. The hardware fault was covered by the warranty.
I hope anyone who encounters the same issues as I have manages to find this of use in the future!
Hi,
As the tittle suggest, I've managed to brick my phone.
The phone isn't responding at all, and acts as though the battery is pulled out. When I connect it to my PC, it shows up as QHSUSB_DLOAD, and there are no drivers.
Note that this is the same PC I used to flash cyanogenmod 10.2, so I have all the required samsung drivers. Also, it's the odin doesn't detect my phone.
The last steps I took before my phone died:
1) installed App2SD
2) partitioned my SD
3) installed and configured linux swap
4) restarted
After that, the phone got angry and just wouldn't respond. I didn't even have time to transfer any of my apps to the SD.
The phone has a custom rom installed (cyanogenmod 10.2). Already took it to a service place, with no luck..
Any ideas?
Thanks
johney9 said:
Hi,
As the tittle suggest, I've managed to brick my phone.
The phone isn't responding at all, and acts as though the battery is pulled out. When I connect it to my PC, it shows up as QHSUSB_DLOAD, and there are no drivers.
Note that this is the same PC I used to flash cyanogenmod 10.2, so I have all the required samsung drivers. Also, it's the odin doesn't detect my phone.
The last steps I took before my phone died:
1) installed App2SD
2) partitioned my SD
3) installed and configured linux swap
4) restarted
After that, the phone got angry and just wouldn't respond. I didn't even have time to transfer any of my apps to the SD.
The phone has a custom rom installed (cyanogenmod 10.2). Already took it to a service place, with no luck..
Any ideas?
Thanks
Click to expand...
Click to collapse
You're in a rough spot here. You only have two possible options:
1) See if someone with your phone can make a debrick img file similar to this idea -
http://forum.xda-developers.com/showthread.php?t=2660566
I haven't seen anyone say they have tried something similar on your phone, but the only other option will be...
2) JTAG Service such as this -
http://mobiletechvideos.mybigcommerce.com/
If you're getting QHSUSB drivers, you're past the help of conventional unbricking methods using tools like Kies, Odin, or Heimdall.
Thanks, you've given me some hope! I have some data I would really like to restore..
I'll try and post back here if I get some results
johney9 said:
Hi,
As the tittle suggest, I've managed to brick my phone.
The phone isn't responding at all, and acts as though the battery is pulled out. When I connect it to my PC, it shows up as QHSUSB_DLOAD, and there are no drivers.
Note that this is the same PC I used to flash cyanogenmod 10.2, so I have all the required samsung drivers. Also, it's the odin doesn't detect my phone.
The last steps I took before my phone died:
1) installed App2SD
2) partitioned my SD
3) installed and configured linux swap
4) restarted
After that, the phone got angry and just wouldn't respond. I didn't even have time to transfer any of my apps to the SD.
The phone has a custom rom installed (cyanogenmod 10.2). Already took it to a service place, with no luck..
Any ideas?
hope anyone kan fix my problem i returned back to the stock rom 4.0.4 after i was on cm 12 then tried to ger back to cm11 the wifi and the bluetooth is not working on both cm11 and cm12 what can i do
Click to expand...
Click to collapse
"com.android.phone has stopped working" since last update, no help my clean install
Hey,
since i installed the latest update i always get the error message "com.android.phone stopped working".
I tried by fixing it by wiping the device, but there was no effect. The error occurs again every second, so the device isn't usable any more.
I tried to flash another factory image by using Skipsofts Unified Android Toolkit, but this hasn't worked either. I get the error: "error, rebooting in fastboot mode" - after this the application freezes.
Has anyone an idea how i can fix this problem?
thanks for your help!
I'm also having the same problem. Updated N10 last week with the latest OTA and then the N10 crapped out completely with the same error "com.android.phone stopped working". Why phone process when this is a tablet? Did the clean cache, hard reset, no luck. Did it a couple of times and made it worst because now I have a new error (Out of Storage). Try the fastboot to refresh it to the stock rom and no luck. It's not taking it (0% transfer). ADB command seems to work but I have no idea how to do it with ADB to restore the image. Plus now that I'm out of space, I can't transfer any of the image. Is there such a thing as remote format the ROM?
I contacted google and got transferred multiple times to different dept at Samsung. No luck. Samsung told me to take the N10 to Best Buy to Samsung experience store. The guy who work there is such a douche, he was telling me that he doesn't have the image for N10 and he said he didn't even know that N10 is Samsung. Great job with the training Samsung. To make the matter worst, he was trying to be funny by saying "the good news is that they have many other Samsung tablets that I can purchase new". What an moron. What makes him think that I want to buy another Samsung when they couldn't even figure out how to fix the one they previously made and updated.
So the Samsung tech support told me that I have to send it back to them to be flashed. Not sure how much that will cost me to fix the problem they created since it's already out of warranty. Is there another way to do it?
Getting very frustrated as well.
Solution to corrupted OTA update for N10
Gosh.. What do you know. I finally got my N10 fixed after I vented my frustration with Samsung. The problem was because my USB driver was not detected properly thus the fastboot is not working. So here are the steps I did to fix the problem.
Step 1. Hold down Power, Volume Up, and Volume Down button together until your Nexus 10 reboots into fastboot bootloader mode.
Step 2. Connect a microUSB cable from your Nexus 10 to your computer.
Step 3. Make sure you already have the firmware then uncompress it. If you didn't, here is the latest N10 Lollipop from Google website.
https://developers.google.com/android/nexus/images
This is the image I used, the latest Lollipop
Step 4. Make sure you have USB drivers installed for Windows (Since I'm using Windows 10, this are the step I'm showing).
If you see “Android 1.0” instead, update the drivers with these drivers. Once you have updated the driver, your device manager should now show “Android Bootloader Interface”.
This was the step that was missing for me.
Step 5. Make sure you have Android SDK installed especially the platform-tools. Follow Android SDK installation steps by Google.
Step 6. Make sure the path where you install the Android SDK/platform-tools is in the windows environment. If not, open up the "command prompt" and type this.
HTML:
SET PATH=%PATH%;D:\Android\android-sdk\platform-tools
D:\Android\Android-sdk\platform-tools is where I installed the android-sdk
Step 7. Go to the directory where you uncompressed the firmware, find the file "flash-all.bat", double click it. Watch it does the magic.
That's it. Now your N10 is back to original latest Lollipop Firmware for N10. Hope this help..... Good luck...
WestDude
thanks, i'll give it a try
thanks a lot, its working again!
Awesome.
Any idea on how to do it on mac?
I started having issues with my phone and tried to fix them. The problem was simple. The sensors stoped working. First I tried a hard reset (didn't work). Installed Lineage OS. Didn't fix the issue and made some errors form the install. Tried the stock ROM. I tried two of them with the first one I discovered that it was a problem with the firmware of the sensors. The I tried an older version thinking that the firmware wouldn't be compatible and that it would work better. (I'm not entirely sure but I think it was this version MPD24.65-18.1)
The installation went well without problems. The firmware was (again) downgraded (and later upgraded without asking permission). The big issue is that my phone now is unable to connect with the computer. When I plug it it starts to charge but nothing more happens. The computer isn't aware that it has anything plugged (according to the ports). So I cannot run adb and cannot change anything on the phone. I tried to install from a SD card on the recovery mode but I think I'm not doing it as it should. I plug the card and run the updater from the SD. The first thing that is odd is that it actually displays the internal memory. And then when I run either a OTA.zip or a compress of a build named PG86IMG.zip I get a verification error.
I do not know what to do. I would like either to have working sensors or the 7.1.1 version.
Phone:XT1563 16 gb
Computer:Mac