Database Users

[Solved] MTD driver installation issues

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.

[Q] Nexus 7 hangs on Google screen (tried fixes in other threads here but no result)

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!

[Q] N7 4.4 update issues?

Not sure if I'm the only one, and if I am that really sucks, but I got tired of waiting for the OTA and decided to install the update via the fastboot method, unlocked my bootloader installed without a problem.
However the issue now seems to stem from transferring media files to my tablet, which I never had a problem doing, a pop up window will tell me that android.media.storage has stopped, giving me an option to report and to simply tap okay.
Not sure reporting ever does anything, and if it does I've never seen it change a single thing at all, but after I tap okay or send the report, any files transferring will just exit out, then if I unplug my usb and plug it back in, it doesn't seem to recognize the tablet at all.
I've so far remedied this, not sure if it's a permanent fix or temporary, by going into settings>apps>all, then from there tapping the app, clearing data and cache, restarting my tablet with a hard reset and it seems to be working for the moment.
However transferring files since the update are sluggish at best, and taking a 356MB folder of images used to take maybe a few minutes, 5 or 7 at the most, now it's hanging there at times with the transfer time increasing.
As a matter of fact I'm transferring said 356MB folder right now and it's stuck at 10 minutes to finish and hasn't moved for about 10 minutes.
If anybody else is having these problems, can you suggest ways you've fixed it? Or do I simply need to either do a factory reset or straight up flash it again to fix the problem?
Also, I made another article detailing my problems with updating, which I've since fixed obviously, but Recovery Mode isn't anywhere to be found, I do the regular method and before it showed the android with the red triangle and below him it would say no command, now it just shows the android with the same triangle with no wording underneath at all.
I've also re-downloaded the official factory image 4.4 from google's developer site and tried to manually flash recovery onto it, and it says that it succeeded but then when it goes back to fastboot and I choose recovery it loads then shows me the android with the red triangle.
I've even tried downgrading back to 4.3 but it tells me during the rewrite of the bootloader that there's a signature mismatch.
In addition, this should be the last revision to my issue, I've even tried re-flashing 4.4 and now that's kicking back an error saying there's a signature mismatch, so I can't go into recovery, I can't downgrade, I can't flash a recovery image to my tablet, I think I screwed up in ever updating to 4.4.

Im having the same problem with Media Storage when transferring pictures via Android File Transfer on Mac, tried it on Windows also, same problem.
It happens with my Nexus 4 on KitKat also!!
I still havent found a way to fix it, did you (OP) ever find a fix?
Cheers
Stewart

StuMcBill said:
Im having the same problem with Media Storage when transferring pictures via Android File Transfer on Mac, tried it on Windows also, same problem.
It happens with my Nexus 4 on KitKat also!!
I still havent found a way to fix it, did you (OP) ever find a fix?
Cheers
Stewart
Click to expand...
Click to collapse
Nope no fix yet, I haven't tried transferring a large number of files since, oddly enough, I finally did get the OTA update and it installed 4.4 again.
It didn't take long and the file size was puny, only about 32MB, I assume it installed what was missing, but I haven't noticed anything out of the ordinary since the official updated kicked in.

Yeah I have the latest OTA also, but I am still having the same issue!!

StuMcBill said:
Yeah I have the latest OTA also, but I am still having the same issue!!
Click to expand...
Click to collapse
Not really sure why it's different for you, like I said I got tired of waiting for the OTA and manually flashed the factory image, that's when the problems started, but after a few days I got a notification that the new update was ready which really confused me.
But I installed the downloaded update without a hitch, booted like normal and I just finished transferring a 100MB folder of images to my N7 without an error popping up on my tablet saying something crashed, so I can only assume for the moment until I transfer a larger folder, that the DL'd update fixed the problem.
I've also heard people flashing it again, or side loading it, or even a factory reset would fix the problem, but there weren't many replies as to this actually fixing the data transfer problem.

Problem with downloading ota update kitkat 4.4
I have stock rom and waited for the ota update. It came this morning and while downloading twice the verification failed.i rebooted and the screen came up download failed and had a retry button which i tried to activate and does nothing, The screen has been stuck on the return download for over 12 hours. My wifi connection is strong. Any ideas?

manow91 said:
I have stock rom and waited for the ota update. It came this morning and while downloading twice the verification failed.i rebooted and the screen came up download failed and had a retry button which i tried to activate and does nothing, The screen has been stuck on the return download for over 12 hours. My wifi connection is strong. Any ideas?
Click to expand...
Click to collapse
Take anything I say with a grain of salt as I'm not the greatest guy to ask for help, I only really ask questions here and I'm just going to suggest what to do, if you do it is up to you and I take no responsibility for your device having further issues.
1. Hard reset your device and upon it rebooting, check for the update again and try downloading it again
2. If that doesn't work then back up your data
3. After backing up your data do a factory reset on your device and once you've booted back up to Android, check for the update again and install
4. If that doesn't work, I'm not sure what else to suggest, this is what I would do to try and fix the problem, but for my situation it was unique in that I tried fixing it various ways that seemed to make it worse before it got somehow better.
I hope issuing a factory reset works for you, if not then that hard reset does when you try to redownload the update.

JohnathanKatz said:
Take anything I say with a grain of salt as I'm not the greatest guy to ask for help, I only really ask questions here and I'm just going to suggest what to do, if you do it is up to you and I take no responsibility for your device having further issues.
1. Hard reset your device and upon it rebooting, check for the update again and try downloading it again
2. If that doesn't work then back up your data
3. After backing up your data do a factory reset on your device and once you've booted back up to Android, check for the update again and install
4. If that doesn't work, I'm not sure what else to suggest, this is what I would do to try and fix the problem, but for my situation it was unique in that I tried fixing it various ways that seemed to make it worse before it got somehow better.
I hope issuing a factory reset works for you, if not then that hard reset does when you try to redownload the update.
Click to expand...
Click to collapse
Thanks for your reply back. Yep i also thought of the same 4 step solution as yourself but i also heard from 2 people that had the same thing happen to them and they thought it could be a goggle server problem, So i am going to wait to see if it sorts itself out over the next few days

manow91 said:
Thanks for your reply back. Yep i also thought of the same 4 step solution as yourself but i also heard from 2 people that had the same thing happen to them and they thought it could be a goggle server problem, So i am going to wait to see if it sorts itself out over the next few days
Click to expand...
Click to collapse
That could be too, just thought I'd take a shot, hope it works out for you.:good:

Trying To Recovery N10 (old version).

Hi guys,
I have searched around the forums and still unsure, weary of what to do. I got my nexus when they first came out. I used it for a while and eventually unlocked it so that i could get certain apps that needed root access. I dont think i flashed a custom rom on it though. I havnt updated android to 4.4 yet. Its been a long time since i updated anything. Hence the start of my dilemma. I went to backup my tablet. It told me SuperUser or the bootloader needed to be updated. So im like oh fine update. Tablet then restarts brings me to my boot screen and says downloading target do not turn off. Its been stuck like this and nothing happens. I held down the power and rocker buttons and got back to boot option screen. Here's where im lost and dont remember what to do. I have tried start, recovermode, restartbootloader, and nothing seems to work. They all bring me back to the dead little android guy ​
Here's the device info.
product name: manta
variant: wifi
h/w version 8
bootloader version: mantam03
carrier info: none
serial: ****
lock state: unlocked
reboot mode flag: recovery
I slightly recall when i first unlocked it using twrp or clockworkmod? I could be wrong. Either way i no longer have the rootkit nor the computer i originally used to unlock it. What software do i need to install to get me back up and running. I was worried i may brick it if i installed the wrong version kit. That maybe newer version wouldn't work with my n10 because it was running an old version. Any advice would be much appreciated.

Jshannon22 said:
... I was worried i may brick it if i installed the wrong version kit. That maybe newer version wouldn't work with my n10 because it was running an old version. Any advice would be much appreciated.
Click to expand...
Click to collapse
Considering that you have not used the N10 in a very long time your user data may not be all that important so here are some options.
1) You could flash the factory image for Android 5 which will wipe out your user data but give you a clean system including stock recovery.
2) You could flash the factory image for Android 5 but first you need to change the "flash-all".(bat,sh) script by removing the "-w" option which will prevent your userdata from being wiped. That takes some knowledge to edit the script but all you need is a simple text editor.
After either of those options you can root and replace your recovery. Root before you change your recovery or you will run into an issue due to specific changes in Android 5.
Instructions for installing a factory image.
Nexus 10 lollipop factory image.
How to install Android Lollipop factory image on Nexus 5, 7 and 10 (and keep your data)
Good Luck

I'm having similar issues! When trying to install lollipop over sideload it always errors and states not enough space.
I've formated all the data so I'm at a loss.
Any ideas to install lollipop?
Sent from my Galaxy Nexus using XDA Free mobile app

I'm concerned I've bricked the device. To be honest I'd be happy just to get kitkat back!
When the device powers up it automatically goes into a "no command" bootloop. With the android on its side with an exclamation point sign coming out.
Holding power and the volume it then goes to the android recovery where I have four options: reboot, apply update from adb, factory reset, wipe cache.
When in command, typing adb devices shows my device.
Using adb sideload I've tried to update, but I always get the error "creating parent of system/app/KoreanIME/KoreanIME.apk failed. error no space left on device
E:Error in /tmp/update.zip
status 7 installation aborted"
So I downloaded the kitkat image and tried to run the script "flash all". But then the command screen just says "waiting for device"
After all that failed, I tried to hold power and the volume button when it restarts. That takes me to the odin screen, where it just states "downloading, do not remove target" The volume buttons do nothing. pressing the power button just reboots.
Any help would be much appreciated!

I have the same issue. There does not seem to be a way to install any (old) version of android. All I get is the same error message "creating parent of system/app/KoreanIME/KoreanIME.apk failed. error no space left on device
E:Error in /tmp/update.zip status 7 installation aborted"
I did not root my device nor did I install a custom rom. I just started installing the OTA update and that's when the tablet got stuck in the boot loop thingy.
I also searched the internet and all I found were similar instructions on how to install factory images etc. using adb sideload.... as I mentioned, following those instructions lead to the error message.
I can' believe this.
Thanks for your help

I also have similar issue. I had non rooted Kitkat 4.4.4 installed on N10. I received update intimation to Lollipop hence downloaded the update. While installing, message regarding error came followed with message "No command" . Now nothing is done further. Even tablet is not getting power off. Periodically screen displaying Google is coming followed with message "No command" I just checked. I can enter in to download and recovery. I now downloaded also Lollipop update for manual updating.
While connecting to PC, it starts searching for driver and after sometime message flashed "Driver not installed successfully" might be due to non detection of MTP. In such case if I try to maually install then ADB also is not recognising the connected device. As novice even I do not know to install ADB sideloaded.
Can you suggest how best I can revive N10?
Regards,

Guys,
I also had the exact problem. What finally worked for is to flash custom recovery (TWRP latest version) with "fastboot flash recovery <recovery.img>" command.
Then from the recovery I installed custom ROM (http://forum.xda-developers.com/showthread.php?t=1998585), as the official ROM also failed.
Hope it will help someone.

Shleim, this seems to just have worked out fine. Many thanks for your help!
I'm still kinda wondering why it wouldn't work with the official ROM. In any case, this is by far better than having a bricked tablet and at least now I know it still works.
Awesome, thanks for this tip!!!

fliuwoek said:
Shleim, this seems to just have worked out fine. Many thanks for your help!
I'm still kinda wondering why it wouldn't work with the official ROM. In any case, this is by far better than having a bricked tablet and at least now I know it still works.
Awesome, thanks for this tip!!!
Click to expand...
Click to collapse
No worries, glad it helped you.

Nexus Player stuck on " Can't Load Android System. Your Data may be corrupt"

Nexus Player stuck on " Can't Load Android System. Your Data may be corrupt"
Hi, my Nexus Player is stuck on " Can't Load Android System. Your Data may be corrupt. If you continue to get this message you may need to perform a factory data reset......."
When I do the factory reset it brings me back to this screen. My son told me it happened after an update.
I can't get it to do anything else.
Is there a solution?

I’m experiencing this same issue now. Stock Oreo, unrooted. Anybody have any ideas?

Same happening here. Unrooted, Stock Oreo. Happened after an update.
Have attempted to get USB connected in recovery to ADB push the factory image with no luck.
Device not showing up on windows or mac.

ratmandu said:
Same happening here. Unrooted, Stock Oreo. Happened after an update.
Have attempted to get USB connected in recovery to ADB push the factory image with no luck.
Device not showing up on windows or mac.
Click to expand...
Click to collapse
So Google is hard-bricking our devices with no replacements in sight? This is crazy. This isn't the only thread about this.

taino211 said:
So Google is hard-bricking our devices with no replacements in sight? This is crazy. This isn't the only thread about this.
Click to expand...
Click to collapse
I wouldn't quite go so far as to imply that they are doing it on purpose. It is most likely lack of testing of updates going out, since it is an old, and now unsupported device.

This happens to my nexus player too, after update push from google.. Apparently google pretty much bricking all nexus player by pushing bad firmware update. I can see class action lawsuit coming if google doesn't fix this soon

Successful restoration of factory image into nexus player
Andy Jawa said:
This happens to my nexus player too, after update push from google.. Apparently google pretty much bricking all nexus player by pushing bad firmware update. I can see class action lawsuit coming if google doesn't fix this soon
Click to expand...
Click to collapse
Update, I did follow the direction posted on another forum and was successful on restoring my nexus player. Here's the procedure that I found working for me. I had to flash it couple of times since the latest image doesn't seem to fix it. Also the usb driver tool doesn't seem to work properly on my windows 7 laptop, but works in windows 10, but it may just be my Win7 laptop that has too much security restriction.
Here's the procedure.. good luck. Sorry, since I'm newbie, xda won't let me post actual link, I have to remove the http, but it is a good link, you just have to paste it into browser
1. Download Google USB driver from : developer.android.com/studio/run/oem-usb
2. Download and unzip ADB and Fastboot tools: developer.android.com/studio/releases/platform-tools
3. Download and unzip Nexus Player Factory Image: developers.google.com/android/images#fugu
I tried the lastest one : 8.0.0 (OPR2.170623.027, Nov 2017) , but it crashed again. I then loaded the 8.0.0 (OPR6.170623.021, Sep 2017), and it seems to work so far. I disabled the auto-update on the play store just to be safe, but not sure if this would prevent the OTA.
4. Open command prompt window and go to the unzipped folder for the fugu image
5. Add path to the ADB/fastboot tool into system PATH, example:
PATH=%PATH%;D:\Dnload\platform-tools_r28.0.0-windows
6. Get into bootloader of Nexus player using this procedure:
- unplug power of NP
- Press the button on the bottom of NP, keep it pressed and plug-in power
- keep it pressed for about 8 sec, and release, it would go into fastboot mode, showing you the current setting and boot option with default of "normal boot"
- press button one time to stop it from doing normal boot
7. Plug microUSB cable between NP and your PC, and install driver (unzipped in step 1) if asked.
8. Back on your command prompt, type "fastboot devices", it should show the nexus device, if nothing is listed, there's still driver issue that need to be fixed.
9. Now we can follow the instruction to flash the factory image from developers.google.com/android/images. I will summarize the step below that work for my nexus player (pre 2015 device)
- unlock bootloader by issuing command: "fastboot oem unlock". You should see the status updated on the screen to unlocked.
- Execute the "flash-all" script. This script installs the necessary bootloader, baseband firmware(s), and operating system.
You should see the activity on screen, like downloading state. While the script is running, it would also reboot the nexus player into bootloader, and waiting for the NP to come back up into bootloader. Once it comes back up, the script would resume. In case the player doesn't go back into bootloader, do step 6 to manually get into bootloader
- After the script completes, for security you should lock the bootloader again, by going back into bootloader (see step 6) and issuing command: "fastboot oem lock"

Mine started doing this also, it sits at the GOOGLE screen for a while, flashes/reboots once in a while and then eventually goes to the NO COMMAND screen.
I flashed it back to 7.0.0 NRD90R and it booted up fine, setup things and it worked fine even after the OTA to 8.0, but something else updates soon after that and fails again.
I just flashed the 8.0.0 OPR2.170623.027 before I left for work so we'll see what state it's in when I get home.
My second one is fine so far.

Mines dead too, stock, no root.
I will try flashing older version and see.

Wow, WTF is happening to the Nexus Player?
My Nexus Player have been unused for the last few months (I think I just upgraded it Oreo to test it when it went out), what can I do to save it from the sudden death?
Can I power it up without WiFi and block updates or something?

Just saw this on the google forum.
Can't load Android System (https://productforums.google.com/for...us/Ski0fFZ0pZM)
Quote:
GEL1966 via Nexus Help Forum
I was encouraged by a reddit user to open this: https://issuetracker.google.com/114276277 He suggested I get as many people I could to "star" the issue. Hopefully it yields something other than an "escalation". Will post any news.

My Nexus Player has been at Android 8.0.0 for a while.
I hope I didn't jinx it by posting here
If it quits working, I still have a Roku and a fireTV.
Sent from my SM-G930T using Tapatalk