Ok guys I am pretty new to this all this so please bear with me with my bad words. I decided to install a custom rom on to my nexus 7 http://nexus7root.com/nexus-7-roms/c-rom-for-nexus-7-android-4-4-4multi-window/ (mind you I had a rooted kitkat os installed on my tablet before hand) I installed it and everything went fine. Porblem is when I plug my nexus 7 into my computer, the 26 gigs of space I should have (you know so you can do file management droping pics and vids and such) was not there. I dont understand, no matter what computer I was using ANYWHERE I was always able to simply plug my tablet in and start file management. What am I doing wrong? do i need to install drivers ON the nexus 7? if you say I need to install drivers on to my p.c then please explain (weather it was linux or windows I could do file management on there computer with out having to install anything ahead of time.) so what gives? please help.
Simplest first, under Settings>Storage>Menu (upper right on stock)>USB computer connection, is MTP still checked? I'm not familiar with that rom so not sure about locations.
Based on what you said, it seems the PC is recognizing the N7. Check device manager to make sure there are no exclamation marks. You can also "update driver software" or even uninstall it. Windows should then install the device the next time you connect.
After those ideas:
Have you done several reboots? Was it a clean install? You can always run the install again but try wiping cache in recovery first.
You'll get other replies if someone knows the exact situation for your rom.
ritchea said:
Simplest first, under Settings>Storage>Menu (upper right on stock)>USB computer connection, is MTP still checked? I'm not familiar with that rom so not sure about locations.
Based on what you said, it seems the PC is recognizing the N7. Check device manager to make sure there are no exclamation marks. You can also "update driver software" or even uninstall it. Windows should then install the device the next time you connect.
After those ideas:
Have you done several reboots? Was it a clean install? You can always run the install again but try wiping cache in recovery first.
You'll get other replies if someone knows the exact situation for your rom.
Click to expand...
Click to collapse
YOU ARE ****ING AWSOME. I am pretty savy with computer's but never did I know there was a actual option to flick mtp on and off. that said I never ever would have guess to check there. I was stuck up in the developers mode trying to figure out if my usb setting was off. THANK YOU THANK YOU THANK YOU. now I dont have to go back to my old rom.
Thanks. Glad I helped.
Sent from my Nexus 5 using Tapatalk
Related
Is there a way to check if my phone has successfully rooted i.e. what would show in the software section of "about phone" and how would that differ from the standard generic rom?
Had a coupld of error during rooting but it appeared to go all the way through but just want to make sure!
Thanks
Youll have a programme called superuser permissions!
Lets hope we beat fulham on sunday
Spot on, I'm rooted! Only issue now is that I can't get into recovery mode on my windows 7 machine. Had to borrow a mates xp machine which I now don't have access to so bugger all point rooting seen as I can't install custom roms!
Are we likely to eventually get the ability to flash straight from the memory card?
Bit nervous about the weekend, if we slip up Tottenham will go 3rd. Not sure I could live with the shame!
you could install ubuntu? its a small os. you literally download wubi and it does it all for you!
lol yes i know! we should win though, andrei is back lol
Gooner4_1998 said:
Spot on, I'm rooted! Only issue now is that I can't get into recovery mode on my windows 7 machine. Had to borrow a mates xp machine which I now don't have access to so bugger all point rooting seen as I can't install custom roms!
Are we likely to eventually get the ability to flash straight from the memory card?
Bit nervous about the weekend, if we slip up Tottenham will go 3rd. Not sure I could live with the shame!
Click to expand...
Click to collapse
huh? I still can get into the recovery mode using windows 7 64 bit without problem. just make sure u run as administrator.
Can't get it to work on windows 7 for love nor money! Using 64 bit edition if it makes any odds. I assumed that I was running as admin but just in case, how would I make 100% sure? Basically fails to connect every time.
Made a bootable usb with Linux on it but had no idea what I was doing once I got in! Tried running the recovery-linux.sh file in the terminal but no luck! Terminal popped up and disappeared just as quickly. Couldn't work out how to run it direct from the terminal to see the feedback!
Does the phone get recognized by your computer before you run the recovery? Do you hear the USB duh-duh device connected sound? If it fails to connect, it's just because USB hasn't found it yet. Give it a minute or check if it's missing drivers. You can ensure you're running as admin by just right clicking and selecting run as adminstrator. It should pop up a box asking if you're sure.
I routinely get into recovery on x64 Win 7, so it's not an OS thing. Keep at it, you can use your own computer.
Gooner4_1998 said:
Can't get it to work on windows 7 for love nor money! Using 64 bit edition if it makes any odds. I assumed that I was running as admin but just in case, how would I make 100% sure? Basically fails to connect every time.
Made a bootable usb with Linux on it but had no idea what I was doing once I got in! Tried running the recovery-linux.sh file in the terminal but no luck! Terminal popped up and disappeared just as quickly. Couldn't work out how to run it direct from the terminal to see the feedback!
Click to expand...
Click to collapse
Right click on command prompt, choose run as administrator i think.
Phone is connected and I can see it in devices and printers section. All drivers are installed as well. Not sure what the issue is. I'm also unable to connect to HTC sync. Had the phone replaced so its not a hardware issue. Very frustrating!
I just unrooted and installed the leaked radio update so i would have less bugs with the froyo ROMS.
I installed the radio perfectly fine, but now unrevoked isn't working for me.
I deleted all of the previous files and reinstalled them (sdk folder, usb drivers, reflash)
when i run the reflash tool, it gets stuck after rebooting, says "waiting for reboot..."
any help or ideas?
EDIT: as the phone rebooted, it changed to "Flashing recovery image. Do not touch your phone!" but instead of going into recovery, it just continued to restart the phone as usual
What exactly did you do to make yr phone reboot? Manually power cycle? Battery pull?
IIRC, something very similar happened to me with unrev 3.0. I was sure I had the google sdk drivers on my xp box, so I just plugged 'er in and ran the rooting tool. Later I found out the htc drivers were there the whole time, which as we all know interferes with rooting.
So the first thing would be to double-check your drivers, eliminate other USB devices from the setup, disable doubletwist or other apps that talk to the phone.
I did get rooted with the wrong driver in place, but I had to help the process along at one point. I believe I did that by opening a dos box and doing 'adb reboot recovery' from \sdk\tools when the unrevoked script appeared to be stuck waiting for a reboot.
You do have to make sure it reboots to recovery, not normal OS, as recovery boot sequence is where the root exploit takes place...
Do you have HTC Sync installed on your computer? Remove it if so.
cantare said:
What exactly did you do to make yr phone reboot? Manually power cycle? Battery pull?
IIRC, something very similar happened to me with unrev 3.0. I was sure I had the google sdk drivers on my xp box, so I just plugged 'er in and ran the rooting tool. Later I found out the htc drivers were there the whole time, which as we all know interferes with rooting.
So the first thing would be to double-check your drivers, eliminate other USB devices from the setup, disable doubletwist or other apps that talk to the phone.
I did get rooted with the wrong driver in place, but I had to help the process along at one point. I believe I did that by opening a dos box and doing 'adb reboot recovery' from \sdk\tools when the unrevoked script appeared to be stuck waiting for a reboot.
You do have to make sure it reboots to recovery, not normal OS, as recovery boot sequence is where the root exploit takes place...
Click to expand...
Click to collapse
i didn't do anything to get it to reboot, the reflash tool rebooted the phone for me.
i'm 99% sure all other drivers are gone and only the google ones are there. I checked under device manager, but maybe i missed it? is there some secret spot they hide in? (thats not sarcasm btw lol)
I'm gonna try rebooting the phone from a dos box. when typing the commands.....
1-cd\sdk\tool
2-adb reboot recovery??
just wanna make sure.
thanks for your help too
douger1957 said:
Do you have HTC Sync installed on your computer? Remove it if so.
Click to expand...
Click to collapse
nope, i got rid of it as far as i know
Make sure you delete the RUU file on the SD card. Something like pb456img (can't remember the exact file name, and tapatalk search sucks).
Also, make sure you turn usb debugging back on as ruu turns it off I believe.
Sent from Incredible using Tapatalk.
got it! i did it all on another computer from scratch and it worked!
thanks for all of your help
JWorth said:
got it! i did it all on another computer from scratch and it worked!
thanks for all of your help
Click to expand...
Click to collapse
ya i had the same problem, tried unrevoked from a new machine, it worked. must have been old drivers or possibly some sync software. didnt' spend enough time to narrow it down because honestly, once I got re-root, who cares?!
glad you got it rooted!
a couple notes for anyone reading: first, unrevoked has its own set of modified drivers for their root tool... not the same as stock google sdk drivers, at least where the Bootloader ADB driver is concerned.
JWorth said:
i'm 99% sure all other drivers are gone and only the google ones are there. I checked under device manager, but maybe i missed it? is there some secret spot they hide in? (thats not sarcasm btw lol)
Click to expand...
Click to collapse
for future reference, getting rid of drivers in windows can involve a bit of blind faith (unless you know the registry etc. like the back of your hand). Often Windows will auto-install a driver you don't want if you let it do the 'automatic' wizard thing.
if you have a restore point from before any drivers were loaded, it's simplest to use that provided it doesn't screw up other things.
or you can use the uninstaller tool that came with the old drivers, and then the installer that comes with the new ones, and pray it worked.
ultimately, if there are still problems, best practice is to run device manager, turn on the "view->show hidden devices" option, plug in the device if it's removable, and then right-click & uninstall ALL related device entries. For the DInc that would include entries under Android-anything, HTC-anything, possible entries under Modems and Other/Unknown.
Then reboot, run whatever driver installer package you have, plug in the device again, and check that nothing fell under Other/Unknown Devices. If there are such entries in dev mgr, right-click each one to "update driver", then browse to the proper .inf file in your driver package folder. If Windows ever pops up the Driver Install Wizard, you choose the manual options (don't search/not this time/choose from list/Have Disk...) and navigate to the appropriate .inf.
Hi and thanks for taking the time to read this
My brother tried to do the update of his nexus through the phone download (not through the sd card or connecting to a computer). Since this it will not start up and if i go to download mode it says that it is downloading constantly (have left for hours).
I can make it to the clockworkmod recovery v6.0.1.0 but unfortunately my brother didnt make a backup before trying to update to 4.2 jellybean.
The unfortunate part of this equation is that i cant access the phone via usb as the drivers wont install and the phone doesnt have an sd card slot except the sim card slot. So placing the correct files on the phone is proving too hard for me to complete.
Sorry if this situation has been covered before but i have searched for about 1.5 hours now to no avail. I would very much appreciate if someone can take me through how to get this phone working in any way possible (i dont care if he loses all data and goes back to stock).
Regards
Sam from New Zealand
samakbuchanan said:
Hi and thanks for taking the time to read this
My brother tried to do the update of his nexus through the phone download (not through the sd card or connecting to a computer). Since this it will not start up and if i go to download mode it says that it is downloading constantly (have left for hours).
I can make it to the clockworkmod recovery v6.0.1.0 but unfortunately my brother didnt make a backup before trying to update to 4.2 jellybean.
The unfortunate part of this equation is that i cant access the phone via usb as the drivers wont install and the phone doesnt have an sd card slot except the sim card slot. So placing the correct files on the phone is proving too hard for me to complete.
Sorry if this situation has been covered before but i have searched for about 1.5 hours now to no avail. I would very much appreciate if someone can take me through how to get this phone working in any way possible (i dont care if he loses all data and goes back to stock).
Regards
Sam from New Zealand
Click to expand...
Click to collapse
CWM recovery offers the ADB interface. I would:
1. get the naked driver package (see Efrant's guide)
2. boot device into recovery and connect usb cable
3. open windows device manager, find your device and manually update the driver
4. use adb to backup the /sdcard to your computer
5. flash 4.2 stock images using fastboot
6. done
Petrovski80 said:
CWM recovery offers the ADB interface. I would:
1. get the naked driver package (see Efrant's guide)
2. boot device into recovery and connect usb cable
3. open windows device manager, find your device and manually update the driver
4. use adb to backup the /sdcard to your computer
5. flash 4.2 stock images using fastboot
6. done
Click to expand...
Click to collapse
op, if you just want to get the device to working state again, and dont care about any data:
1. get the naked driver package (see Efrant's guide)
2. boot device into bootloader and connect usb cable
3. open windows device manager, find your device and manually update the driver
5. flash 4.2 stock images using fastboot
step 3 is the same, the same procedure, the same driver; windows is dumb so you have to tell it again when device is in bootloader (which, btw, is NOT the same as download mode).
Hi and thank you for the replies.
I have downloaded the naked driver but cant get it to work. I have followed the steps to make it work but i get to the device manager and there is no option for uninstalling current driver (as it has none currently). It only has update driver software (which if i use windows to search for it cant find any) and properties. The Galaxy Nexus icon in the device manager has the yellow exclamation mark sign on it. I can
When i try to manually find the naked driver it comes up with the following error
Windows found driver software for your device but encountered an error while attempting to install it.
Google Galaxy Nexus ADB Interface
Access Denied.
Where to from here lads, i appreciate the input
samakbuchanan said:
Hi and thank you for the replies.
I have downloaded the naked driver but cant get it to work. I have followed the steps to make it work but i get to the device manager and there is no option for uninstalling current driver (as it has none currently). It only has update driver software (which if i use windows to search for it cant find any) and properties. The Galaxy Nexus icon in the device manager has the yellow exclamation mark sign on it. I can
When i try to manually find the naked driver it comes up with the following error
Windows found driver software for your device but encountered an error while attempting to install it.
Google Galaxy Nexus ADB Interface
Access Denied.
Where to from here lads, i appreciate the input
Click to expand...
Click to collapse
if you're using windows 7, i read something about you need to disable windows digital driver signature check, or something in those lines.
can't help any further on that subject, since i'm a Linux user (Windows knowledge is very limited) and also that is an operating system's issue and would be better discussed in a Windows forum, IMO.
bk201doesntexist said:
if you're using windows 7, i read something about you need to disable windows digital driver signature check, or something in those lines.
can't help any further on that subject, since i'm a Linux user (Windows knowledge is very limited) and also that is an operating system's issue and would be better discussed in a Windows forum, IMO.
Click to expand...
Click to collapse
Thank you for another helpful reply! Yes i am using windows 7 - i will try to perform the task now - results soon. In the meantime if anyone else knows instructions on how to do this i would love to hear
I am at work and dont have administrator settings on windows 7 so i went to an older computer and started fastboot.exe. I went to recover and there was the IP address of the computer went to that and recovered. From there i went to reboot and now i am just getting a Google in the middle of the phone (as before). I will wait some time to see if it will start up now. If not what is my plan?
So i havent got any closer to having a usable phone.
Im up to this step:
"flash 4.2 stock images using fastboot" how do i do this? i have fastboot and i have the stock image
samakbuchanan said:
So i havent got any closer to having a usable phone.
Im up to this step:
"flash 4.2 stock images using fastboot" how do i do this? i have fastboot and i have the stock image
Click to expand...
Click to collapse
[HOW-TO] [GSM & CDMA] Return to stock for ALL Galaxy Nexus phones (latest JOP40C)
Thanks for that i had since found that and have printed it and will work through each step methodically. I have the stock image on download.
I have spent the best part of my working day on it now. Fingers crossed it all works out.
Thanks to all who have helped me through this far
I've been trying to play with some of the ROM's of Pokemon games recently and i've been using the Pokemon ROM editor to edit the games ROM's. This was before i rooted my nexus 7. Be aware that I haven't flashed any other ROM's or played with any kernels or device mechanics yet and the device was still connecting as MTP before I had rooted and for a while after i had rooted. I can connect it as PTP, but that's not useful when you need to take the whole .nds file for a game off your device. I'm not quite sure what's causing it, but I can tell you what i've already tried so far.
I've reinstalled the ADB drivers and every single part of my Nexus 7 from both PC's that I plugged it into, then enabled MTP and reconnected them, but Windows gives me a driver not found error and so ends the driver solution. I've connected it to more than one PC, one of which had not had the device connected to it ever before, yet it still it didn't appear. (Both PCs are running windows 7), so that means it's either Windows 7 doesn't like Google and wants to screw them by not showing their devices (which is unlikely) or the nexus 7 is just being derpy (which is likely). I've tried different cables, but i assume the cable is alright seeing as it can charge and connect as PTP.
I'm not really sure where else to go from here and i kinda need to edit that ROM soon as my Electabuzz needs to evolve and I need to change his evolution conditions so he evolves at level 56 instead of by trade. There's a random piece of info for you. Also, if i get any solutions that require software downloads, please link to the software or files. I'm pretty new to android tinkering and I don't know all of the terms yet.
EDIT: I don't understand this anymore. At first, PTP was working, now i tried it on a laptop, It didn't work, then i tried it on the PC again and now both PTP and MTP are suddenly working again...
Why does android continue to just fix itself automatically? This is the third time!
SassMaster said:
EDIT: I don't understand this anymore. At first, PTP was working, now i tried it on a laptop, It didn't work, then i tried it on the PC again and now both PTP and MTP are suddenly working again...
Why does android continue to just fix itself automatically? This is the third time!
Click to expand...
Click to collapse
Sounds to me like you have a driver or cable/usb port issue. One of these two links might be useful. Installing a USB driver and [FIX] MTP with USB debugging. Sometimes you might need to go into the device manager and uninstall the driver AND driver software then do a fresh install of the driver. You might want to do a reboot of the computer after uninstalling the driver. I've been lucky and never had problems but my brother had problems and we basically just had to uninstall and reinstall the driver.
SassMaster said:
Why does android continue to just fix itself automatically? This is the third time!
Click to expand...
Click to collapse
To add to what was said above you will need to disables driver security enforcement in order to install the drivers. This will put your computer in test mode and allow you to install non signed drivers. You will also need to manually install the drivers in device manager. I assume you already tried settings > storage > click three dots in the upper right hand side of the screen > click USB connection > select MTP.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
LinearEquation said:
To add to what was said above you will need to disables driver security enforcement in order to install the drivers. This will put your computer in test mode and allow you to install non signed drivers. You will also need to manually install the drivers in device manager. I assume you already tried settings > storage > click three dots in the upper right hand side of the screen > click USB connection > select MTP.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Absolutely right! I also forgot to mention that I have my Windows 7 desktop and laptop both set to Not automatically install drivers which I think makes it easier, at least for me.
You're all wrong! MTP is one big witchery!! It has a mind of its own! It's going to work when you don't need and expect it! It's going to fail when you need and expect it! MTP comes from Microsoft, the house of dark witchcraft and wizardry that gave birth to ugly and sad things like Kin and its misscarried brother Kin 2, Windows Vista and a cursed, evil, dark and lonely soul called Zune! The legend and tales of Gates tell that on Judgement Day, Zune will enslave his very own strain just to take revenge on humanity! Fear the day of revenge! Fear the day of Zune!...
Dropped phone, broken screen/digitizer, doesn't respond to touch
Was able to see the screen a bit yesterday but now its almost all black. I mainly just need my photos off it. Tried an RMA to replace the screen but they said they had to wipe everything first
Is there any way I can pull the photos off it? I haven't tried an otg yet, but I also can't see the screen, so im not sure it would help
Is there a screen sharing program I could get w/o first installing it on my phone?
I think my phone may be rooted, i forget if i ever did, but i dont have TWRP installed on it? (i dont super know what that is but i see other people talking about it)
Any thoughts on how to pull photos off it? I tried the adb devices but the cmd prompt doesn't seem to recognize the phone
Im quite sure I have debugging enabled, just coudln't get the file transfer button hit
Adb pull command should work, but you need to sort the drivers first (I'm guessing that's the issue).
Sent from my OnePlus 3 using Tapatalk
Explorer23 said:
Adb pull command should work, but you need to sort the drivers first (I'm guessing that's the issue).
Sent from my OnePlus 3 using Tapatalk
Click to expand...
Click to collapse
Ok cool, how would i go about sorting the drivers? o.0
jsaden said:
Ok cool, how would i go about sorting the drivers? o.0
side note.... wth is this image verification lol, ive tried like 30 of them, why is it so hard to post lol ><
Click to expand...
Click to collapse
Sorry, can't give definite answer, I know that I had an issue with drivers (device wasn't properly recognized) and tried pretty much everything that Google suggested ... Until it finally started working. I have no idea exactly what solved the issue, it was over a year and a half ago. The next time I clean installed Windows (10 in both cases) it was smart enough to automatically find right drivers.
So ... I'm guessing Googling something like "OnePlus 3 Windows # drivers" should find something useful?
About image verification: are you talking about anti-bot system that checks if you're human? Wouldn't know much about that, never personally had issues with it, but also very rarely see it on XDA as I'm nearly always checking this forum in Tapatalk app.
Sent from my OnePlus 3 using Tapatalk
jsaden said:
Ok cool, how would i go about sorting the drivers? o.0
Click to expand...
Click to collapse
If you had earlier connected your phone to the PC and authorised the PC connection on your phone, then it is a simple issue of disabling driver signature verification on Win 10 and installing the OnePlus drivers on it. Search for and download the correct drivers to your PC. Hold down Shift key and restart the PC. Choose Troubeshoot>Advanced Options>Startup Options and click Restart. On restarting, there will be a list of options. Choose 7 in the Options or click F7 on your keyboard and you will boot into the disabled mode. Now connect your phone and go to Device Manager in PC. Choose the phone which may be showing up as Unknown or with an yellow flag and right click and choose Update Driver. Navigate to the downloaded driver and install it. Now your phone should be properly recognised. Use adb pull command to copy whatever files you need to. Note that this driver signature verification disabling is temporary and when you restart the PC in the normal way, the PC will go back to the normal mode. But the installed drivers will still function.
Hope this helps.
tnsmani said:
If you had earlier connected your phone to the PC and authorised the PC connection on your phone, then it is a simple issue of disabling driver signature verification on Win 10 and installing the OnePlus drivers on it. Search for and download the correct drivers to your PC. Hold down Shift key and restart the PC. Choose Troubeshoot>Advanced Options>Startup Options and click Restart. On restarting, there will be a list of options. Choose 7 in the Options or click F7 on your keyboard and you will boot into the disabled mode. Now connect your phone and go to Device Manager in PC. Choose the phone which may be showing up as Unknown or with an yellow flag and right click and choose Update Driver. Navigate to the downloaded driver and install it. Now your phone should be properly recognised. Use adb pull command to copy whatever files you need to. Note that this driver signature verification disabling is temporary and when you restart the PC in the normal way, the PC will go back to the normal mode. But the installed drivers will still function.
Hope this helps.
Click to expand...
Click to collapse
Oh wow, do you know if this works on Win7? And also I can't see my screen at all, so could I do adb pull of entire folder or hardrive kind of thing? I mainly just want phots, but i've never done adb stuff so not sure how it works
Had the same issue with my Lenovo P2. Only i didn't have debugging enabled. If you have, screen mirroring should be an easy solution. You could just see ur phone screen on ur computer that way. What helped me was to forceboot the phone to recovery with the hardware buttons, then connect it to ur pc. TWRP will automatically launch MTP. When u backed up evrything, you can wipe ur device through adb
jsaden said:
Oh wow, do you know if this works on Win7? And also I can't see my screen at all, so could I do adb pull of entire folder or hardrive kind of thing? I mainly just want phots, but i've never done adb stuff so not sure how it works
Click to expand...
Click to collapse
I don't know about Win 7. It will work on Win 10. Most likely, this should not be needed in Win 7 at all as the drivers should install whether signed or not.
Regarding copying data, a simple command of "adb pull /sdcard" will copy all the folders, files, data etc to your PC. You can also specify where you want the data copied to, simply add the path to the command above. This will work whether your screen works or not. Of course, there are other methods of copying data, you can search for it if you need it.