MAC cannot see Nexus 7, please help - Nexus 7 (2013) Q&A

I have installed the latest version of Paranoid Android. My MAC can no longer see the Nexus 7. Android File Transfer is giving an error message.
My USB Debugging is enabled in the Developer Section.
What else can be causing it?
Any suggestions?

Make sure MTP is checked.
Settings>Storage>3 Dots Small Menu(top right)>USB Computer connection>MTP
If that doesn't work, or is already checked then check the md5 of the ROM zip to be sure it downloaded correctly, then install it again by a full wipe.

NekroWolfen said:
Make sure MTP is checked.
Settings>Storage>3 Dots Small Menu(top right)>USB Computer connection>MTP
If that doesn't work, or is already checked then check the md5 of the ROM zip to be sure it downloaded correctly, then install it again by a full wipe.
Click to expand...
Click to collapse
Thanks very much, checking MTP solved the issue.

Related

Updated version to enable Unknown Sources

This is the latest release of my fix (June 14, 2011). This version addresses the Market ID and Moto Blur issue.
This version does not require the use of scripts on the phone. It uses ADB and sqlite3 (both are included in the zip file).
I created a new thread here because the older version was so full of bugs and comments about said bugs I figured it was time to start fresh, seeing how I am using a different method (the method I should have used to begin with) for this hack. Also, this should have been in development to begin with.
I have not had a chance to test the latest version, aside from verifying the awk command works as exptected. The rest is a strong educated guess, mixed with a re-tooling of it to just use Android Debug Bridge to do what I was having scripts do in the past. Should be much more reliable.
IF YOU DECIDE TO USE THESE INSTRUCTIONS: PLEASE, read through this page entirely from top to bottom at least once prior to doing anything. This way, if you are unsure on anything, you can ask the questions you need answers to. I am not liable for anybody messing up their phone because they didn't think to read the F'n manual prior to following these steps.
If you don't read this through completely before starting, and you brick your system, Don't come crying to me. I warned you.
This version makes it close to impossible to brick the system, but I left that bit in to cover my arse.
If you do not have the phone rooted, download the second zip file, and install the drivers found below:
Motorola Driver(install before you run the batch file)
You will need to enable USB Debugging:
On your phone,go to Settings->Applications->Development->Check "USB Debugging"
Latest version installs busybox for you, but if it doesn't, the script will pause for you to check, and tell you how to quit out of my script before proceding. If you have issues with that, let me know. I haven't tested this version, but by all accounts, it should be more reliable than my previous iterations, with the plus side of not having to purchase an app.
I have not tested it, so you may still need to tell it to install, but it should install the apk.
1. Download the attachment located in this post.
Unzip to a folder on your desktop.
PLUG IN YOUR PHONE NOW!!!
Double click on the batch file ("enable_unknown_sources.bat"). You may have to run as administrator, but I don't think so. Built on Windows XP (I'm a linux guy who wrote this at work in a couple minutes)
When it prompts for you to OK the super user for "unknown", look at your phone. It should have a prompt. If not, it may be ok. We will see....
once your phone has rebooted, you phone will have "unknown sources" enabled already. Don't worry about rebooting. The batch file did that for you.
Quite a bit less work than before. Good news: it's done! never to worry about it again...unless you upgrade....
DISCLAIMER:
DO NOT FOLLOW ANY OF MY STEPS IF YOU ARE UNSURE OF WHAT YOU ARE DOING! I have done my best to ensure that the instructions are accurate, but I made mistakes in the first revision, so who's to say that I didn't miss something this go 'round as well? If you decide to follow this walk-through, your actions are an agreement to not hold me liable if your phone becomes a pretty brick. I am not responsible for what you do with this information. If you have no idea how to do any portion of these instructions, you can either walk away (best idea), or ask for help here.
I am also not the 2nd shooter on the grassy knoll, nor am I the cause of all your woes throughout life. I always wanted to say that in a disclaimer.
Thanks to Vahnyyz for reminding me that I forgot to have you enable USB Debugging.
IF YOU HAVE PROBLEMS:
Have you installed the Motorola Drivers?
Do you have Debugging enabled?
If the answer to the 2 questions above are "yes, damnit! Give me a good answer, and stop wasting my time with these stupid questions", then you will need to tell me at what point the scripts fail. I will look into the problem as fast as I can.
so I tried the program you put on and everything because I haven't been able to root my phone as of yet, but the file I downloaded that included rooting did not work, everytime I ran the application it stated that "Device Not Found" and my phone is connected through USB at the moment.
Forgot a part
Thanks for letting me know about your issue. You need to do the following:
Ensure you have installed the drivers on you computer
Ensure USB Debugging is turned on
To enable USB Debugging, (on your phone...duh) go to Settings->Applications->Development->Check "USB Debugging"
as soon as I run the. bat file, command screen tells me to make sure that busybox is installed, which it is, to unplug phone, go to, busybox and install. Wife's phone is already rooted, once I hit next, "unknown" will pop up on the screen for a second and then....nothing.
Need to fix that to state "....after you ensure busybox is installed, plug phone back in"
Just plug the phone back up prior to proceding
Sent from my GT-I9000 using XDA App
How is the no blur version coming along....anxiously waiting for that!
JBallin4life27 said:
How is the no blur version coming along....anxiously waiting for that!
Click to expand...
Click to collapse
I am running into a problem I believe is caused by an older version of clockworkmod. I am trying to see if I can get a newer version running.
The issue:
It appears that the update file I generate is incompatable with the updater built into the version of ClockWorkMod I am running. Anybody have a newer build of the CWM I can use for testing?
jonsjava said:
I am running into a problem I believe is caused by an older version of clockworkmod. I am trying to see if I can get a newer version running.
The issue:
It appears that the update file I generate is incompatable with the updater built into the version of ClockWorkMod I am running. Anybody have a newer build of the CWM I can use for testing?
Click to expand...
Click to collapse
I had CM6 running on my motorola backflip and still have all the files saved on my computer...would it be in there somewhere and would that be useful to you?
JBallin4life27 said:
I had CM6 running on my motorola backflip and still have all the files saved on my computer...would it be in there somewhere and would that be useful to you?
Click to expand...
Click to collapse
I'm needing the second stage recovery file to make ClockWorkMod something newer than 2.x.x Needing to have it somewhere in the neighborhood of 3.x
jonsjava said:
I'm needing the second stage recovery file to make ClockWorkMod something newer than 2.x.x Needing to have it somewhere in the neighborhood of 3.x
Click to expand...
Click to collapse
Yea lol...no idea what that all means...sorry i'm not any help

"r2: Superboot" not working

Tried to post this in the developers forum in the correct thread but I'm restricted - sorry mods but if you could move this post, that would be ace?
I've tried following the instructions for using the r2: Superboot process to root my phone, but having trouble with it.
I've installed the drivers that came in the zip - with the phone switched on as normal, Windows recognises it no problem, as does ADB. When I put the phone into the bootloader, Windows doesn't recognise it - showing in device manager as "Android 1.0" and making a funny beep as the USB is plugged in. Neither ADB or Fastboot recognise the phone as being attatched.
Just bought the phone today, sim free, in the UK, so possibly a different hardware or software version to those who've got it working?
When running normally, "About Phone" shows as Android version 4.0.1, Kernel 3.0.1-ge2433f2 [email protected] #1 and Build number ITL41D.
In the bootloader it shows Fastboot Mode, Product Name - tuna, Varient - magura, HW Version 9, Bootloader Version - PRIMEKJ10, Signing - production, Lock State - locked.
Anyone got any ideas where to go from here?
Thanks
Make sure you turn on ADB Debugging from the settings menu and plug it into your pc.
Then run:
adb devices
See if its there. If so, continue
You need to force the drivers to install in fastboot mode first. Download the 'drivers' files from *THIS* forum and try them it worked for me (make sure you are in fastboot mode when you install them). You will also need to unlock the bootloader first which will wipe your phone including sdcard so make sure you have any files you need backed up first.
Mark.
Ah, fella, you're a superstar!
Done it now, can tweak my phone just how I want it now.
Thanks so much for your help
mskip said:
You will also need to unlock the bootloader first which will wipe your phone including sdcard so make sure you have any files you need backed up first.
Mark.
Click to expand...
Click to collapse
I have been assuming that 'wipe your phone' means wipe it of anything the user has put on it, but that the OS remains; is that correct?
Yeh, it resets it to the same state as when you first get the phone, wiping any personal data and any changes you've made to the system
Have to say I'm impressed though, it remembered by Wifi password and downloaded all my apps again without me doing anything! I'm liking ICS so far!
scooby359 said:
Yeh, it resets it to the same state as when you first get the phone, wiping any personal data and any changes you've made to the system
Have to say I'm impressed though, it remembered by Wifi password and downloaded all my apps again without me doing anything! I'm liking ICS so far!
Click to expand...
Click to collapse
The Wifi password and app restoration is all in the cloud just pointing that out lol
scooby359 said:
Yeh, it resets it to the same state as when you first get the phone, wiping any personal data and any changes you've made to the system
Have to say I'm impressed though, it remembered by Wifi password and downloaded all my apps again without me doing anything! I'm liking ICS so far!
Click to expand...
Click to collapse
Your passwords and all your list of apps from the market are stored under your google account so when you sign back in on a new phone (or wiped one) and synch with your phone all your market apps under that account are re-downloaded and certain information is restored.
Mark.
I don't remember that happening on my old Desire.. that just something I've missed or new to ICS?
I've noticed ICS brings up my bookmarks from Chrome on my PC, that's deffinately a new trick!
scooby359 said:
I don't remember that happening on my old Desire.. that just something I've missed or new to ICS?
I've noticed ICS brings up my bookmarks from Chrome on my PC, that's deffinately a new trick!
Click to expand...
Click to collapse
Could be you didn't enable personal data backup, or Sense doesn't do that (my guess)
And the Chrome bookmark sync is one of the things I'm definitely looking forward to with ICS I know I can do it with some apps right now but having features be native is always nice

Drivers for this device??

Hey guys, sorry i looked everywhere and i cant find the download. I got to ASUS' site and it said select your OS and the drop-down had no options. I'm trying to do a helium restore, I'm unrooted. If anyone could post a direct link that would be awesome, thanks.
Use the latest Google USB drivers
Writeup
http://developer.android.com/sdk/win-usb.html
Direct download
https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
sfhub said:
Use the latest Google USB drivers
Writeup
http://developer.android.com/sdk/win-usb.html
Direct download
https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
Click to expand...
Click to collapse
Those didn't work for me. Not sure why yet. Couldn't update them. Might be a windoze 8 thing, not sure yet...
mssam said:
Those didn't work for me. Not sure why yet. Couldn't update them. Might be a windoze 8 thing, not sure yet...
Click to expand...
Click to collapse
go in devmgmt.msc and either force update the drivers from there for the appropriate devices (usually the ones with ? marks) or delete the devices, unplug/plug back and let the driver install process proceed, pointing the driver search at the folder where you unpacked the zip file above.

[Q] MTP USB Device?

I thought I was doing great after uninstalling bloatware. However, when I tried to connect my Note 2 to my PC via USB I received the error that MTP USB Device driver could not be loaded. Apparently I must have uninstalled something on my Note 2 that is not allowing me to connect to the PC via USB. I have been searching for days, read many postings with the same problem, downloading various Driver apps to no avail. I even downloaded and installed Samsung Drivers which also did not work. I still can use my USB plug from NOTE 2 to my Flash Drive to get stuff transfered to/from Note2/PC.
It never ends. Fix one thing and then another pops up. LOL
What else can I say except - H-E-L-P.
What de-bloater tool did you use ?
Does it show the apps it uninstalled ?
By default any de-bloater should only delete apps from /system/app and
/data/app.
Have you considered starting over by flashing root injected stock Rom?
Sent from my SGH-T889 using xda app-developers app
ciphercodes said:
What de-bloater tool did you use ?
Does it show the apps it uninstalled ?
By default any de-bloater should only delete apps from /system/app and
/data/app.
Have you considered starting over by flashing root injected stock Rom?
Click to expand...
Click to collapse
I did not use any de-bloater. I used Titanium Backup Pro (TBP) and have a complete list of all apks uninstalled.
In TBP under Backup/Restore all apks uninstalled are listed. Plus, I kept a list of all that I deleted.
No, I have not considered starting over by flashing root injected stock ROM. Thought about it, however, if I
do flash, I'm back to square one.
If I don't resolve this one problem, I will remain at this point until new OS comes out. I do have a work around for time being.
I do appreciate your help, time and concern. Thank you.
What really amazes me is that this problem is all over the Internet and I can't find a simple solution. I have Googled it,
been on here doing searches, reading postings, etc. I have even tried Driver Booster.
asctony said:
I did not use any de-bloater. I used Titanium Backup Pro (TBP) and have a complete list of all apks uninstalled.
In TBP under Backup/Restore all apks uninstalled are listed. Plus, I kept a list of all that I deleted.
No, I have not considered starting over by flashing root injected stock ROM. Thought about it, however, if I
do flash, I'm back to square one.
If I don't resolve this one problem, I will remain at this point until new OS comes out. I do have a work around for time being.
I do appreciate your help, time and concern. Thank you.
What really amazes me is that this problem is all over the Internet and I can't find a simple solution. I have Googled it,
been on here doing searches, reading postings, etc. I have even tried Driver Booster.
Click to expand...
Click to collapse
Sometimes we miss something small and obvious. Have you disabled USB debugging mode in Developer options?
AE74 said:
Sometimes we miss something small and obvious. Have you disabled USB debugging mode in Developer options?
Click to expand...
Click to collapse
Yes, I just tried that based on your suggestion. However, still got the same: MTP USB Device error. Thanks for your help.
asctony said:
Yes, I just tried that based on your suggestion. However, still got the same: MTP USB Device error. Thanks for your help.
Click to expand...
Click to collapse
Can you check your phone setting by dialing *#7284#?
Method 3 on the link below.
http://www.danrichard.com/2013/06/1...nect-to-pc-via-usb-with-unknown-device-error/
AE74 said:
Can you check your phone setting by dialing *#7284#?
Method 3 on the link below.
http://www.danrichard.com/2013/06/1...nect-to-pc-via-usb-with-unknown-device-error/
Click to expand...
Click to collapse
Tried this and again no success.
Method 3 – Ensure you have the right settings By default my phone was already set to the right settings for USB file transfers so I’ll assume most of these ship with the same configuration, hence why I have this as method 3. I found this on a forum and while it did not work for me, it seems a few other folks declared it a success.
1. Launch the phone key pad on your note and press *#7284# (don’t forget to start with that * symbol!) When you press the last pound sign (#) this will bring up an option that will allow you to change your USB connection settings (modem or PDA) – change it to PDA.
I did not get any option that allowed me to change the USB Connection settings when I entered *#7284#. So I dialed that number and got an error Unable to process request.
Tried new USB cable and it still tried to load/install device drivers but not successful. Same error MTP USB Device Failed.
Thanks again for trying to help. I do appreciate your help and time. Still looking for a resolution.
asctony said:
Tried this and again no success.
Method 3 – Ensure you have the right settings By default my phone was already set to the right settings for USB file transfers so I’ll assume most of these ship with the same configuration, hence why I have this as method 3. I found this on a forum and while it did not work for me, it seems a few other folks declared it a success.
1. Launch the phone key pad on your note and press *#7284# (don’t forget to start with that * symbol!) When you press the last pound sign (#) this will bring up an option that will allow you to change your USB connection settings (modem or PDA) – change it to PDA.
I did not get any option that allowed me to change the USB Connection settings when I entered *#7284#. So I dialed that number and got an error Unable to process request.
Tried new USB cable and it still tried to load/install device drivers but not successful. Same error MTP USB Device Failed.
Thanks again for trying to help. I do appreciate your help and time. Still looking for a resolution.
Click to expand...
Click to collapse
Perhaps you may not have the system file Phone Utility 1.0.0 or corrupted.
AE74 said:
Perhaps you may not have the system file Phone Utility 1.0.0 or corrupted.
Click to expand...
Click to collapse
Yes, I do have Phone UTL as shown in TBP. How do I access it? I can't under the Method 3.
asctony said:
Yes, I do have Phone UTL as shown in TBP. How do I access it? I can't under the Method 3.
Click to expand...
Click to collapse
I am trying to find out if you have all the files and compare with my files to find out why I can access phone utility and you can't. Your issue may be the driver or files idk. Tbh, I am not an expert. Just another android enthusiast trying to help. I have Tweaked Rom so mine may be different. I have found 2 system files in TBU, Service Mode and MTP Application. Do you have them also? Does service mode work for you when you dial, for example, *#0011#?
SUCCESS-Thanks to Y-O-U!!!!
AE74 said:
I am trying to find out if you have all the files and compare with my files to find out why I can access phone utility and you can't. Your issue may be the driver or files idk. Tbh, I am not an expert. Just another android enthusiast trying to help. I have Tweaked Rom so mine may be different. I have found 2 system files in TBU, Service Mode and MTP Application. Do you have them also? Does service mode work for you when you dial, for example, *#0011#?
Click to expand...
Click to collapse
Yes, I uninstalled both of those. Re-installed both Service Mode and MTP Application, powered off both PC and Note 2. Rebooted, USBd Note 2 to PC and SUCCESS!!!!!!!!!
Thank you very much for your help!!!!! You are no longer a Jr. U R A SR!!!

TWRP Error 70 on Nexus 7 2013

I recently rooted my Nexus 7 2013 and flashed liquid remix 9.0. That's working great, but I cannot flash the open_gapps-arm-9.0-pico-20201028 . I'm getting an error 70 (even with pico). The partition size is 837 MB with 822 MB used. Thinking that the backup of the previous system is using that space, I deleted that (under the Restore tab) and even though the backup is gone, the backup size is still showing 822 MB.
Any suggestions? I just want to install Google Playstore to download other apps. I tried downloading the playstore apk file into the internal storage, it installed but crashes upon opening.
Any advice?
Thank you!
David
ddflink said:
I recently rooted my Nexus 7 2013 and flashed liquid remix 9.0. That's working great, but I cannot flash the open_gapps-arm-9.0-pico-20201028 . I'm getting an error 70 (even with pico). The partition size is 837 MB with 822 MB used. Thinking that the backup of the previous system is using that space, I deleted that (under the Restore tab) and even though the backup is gone, the backup size is still showing 822 MB. Any suggestions? I just want to install Google Playstore to download other apps. I tried downloading the playstore apk file into the internal storage, it installed but crashes upon opening.
Any advice? Thank you! David
Click to expand...
Click to collapse
Yes, flash sysrepart-max.zip, reboot back to TWRP and proceed with 'pico' install.
Incidentally, while pico is mostly sufficient there are exceptions for special apps like Google Wellbeing or Pay, check my post re 'aroma'.
k23m said:
Yes, flash sysrepart-max.zip, reboot back to TWRP and proceed with 'pico' install.
Incidentally, while pico is mostly sufficient there are exceptions for special apps like Google Wellbeing or Pay, check my post re 'aroma'.
Click to expand...
Click to collapse
Thank you k23m for your reply. I tried flashing the file and i'm getting a zip signature verification error.
ddflink said:
Thank you k23m for your reply. I tried flashing the file and i'm getting a zip signature verification error.
Click to expand...
Click to collapse
I untoggled the signature verification and it worked! Thank you SO much!!
ddflink said:
Thank you k23m for your reply. I tried flashing the file and i'm getting a zip signature verification error.
Click to expand...
Click to collapse
In TWRP settings disable "Zip signature verification".
If still error, flash twrp-3.3.1-0, reboot and try again.
If still error, get the CROSS bundle, run relog.bat and attach "relog-xxxxxx.zip" to your post. If you do not have Windows, run 'relog' from a WinPE-booted flash drive. If you do not have WinPE, install get-logs-sdcard.zip in TWRP, find 'logs.tgz' in the root of internal storage and post it here.
EDIT - it was was too late
:good:
k23m said:
In TWRP settings disable "Zip signature verification".
If still error, flash twrp-3.3.1-0, reboot and try again.
If still error, get the CROSS bundle, run relog.bat and attach "relog-xxxxxx.zip" to your post. If you do not have Windows, run 'relog' from a WinPE-booted flash drive. If you do not have WinPE, install get-logs-sdcard.zip in TWRP, find 'logs.tgz' in the root of internal storage and post it here.
EDIT - it was was too late
:good:
Click to expand...
Click to collapse
Thank you k23m. One other question. Everything is running fine except accessing the device through the PC's usb. The computer recognizes that a device is connected, it's charging, yet it only appears under devices and printers as an Unspecified Device. Do i need new drivers? The Nexus 7 was recognized before rooting it.
Thank you
David
ddflink said:
Thank you k23m. One other question. Everything is running fine except accessing the device through the PC's usb. The computer recognizes that a device is connected, it's charging, yet it only appears under devices and printers as an Unspecified Device. Do i need new drivers? The Nexus 7 was recognized before rooting it. Thank you David
Click to expand...
Click to collapse
Hello again, maybe you've forgotten to switch from charging to data transfer mode in Android? If not, then hardware issue is likely, rooting is not responsible for it.
Boot TWRP and verify if MTP works. If not, then check these issues.
If it happens intermittently then the USB port's "dry joints" are likely. In this case you can get it going temporarily with gentle downward pressure on the USB plug.
:fingers-crossed:
k23m said:
Hello again, maybe you've forgotten to switch from charging to data transfer mode in Android? If not, then hardware issue is likely, rooting is not responsible for it.
Boot TWRP and verify if MTP works. If not, then check these issues.
If it happens intermittently then the USB port's "dry joints" are likely. In this case you can get it going temporarily with gentle downward pressure on the USB plug.
:fingers-crossed:
Click to expand...
Click to collapse
I didn't realize I needed to change the Default USB Configuration in Developer Options. Now works! Thank you!! :highfive:
ddflink said:
I didn't realize I needed to change the Default USB Configuration in Developer Options. Now works! Thank you!! :highfive:
Click to expand...
Click to collapse
Hi there k23m, it's been a while and having some issues with GPS on the nexus 7 using the liquid remix. When in settings the location option only says sensors only, high accuracy isn't option. It doesn't seem to connect to any GPS. Any suggestions? Thanks

Categories

Resources