Do any of you use your Nexus 7 with Windows 10? - Nexus 7 (2013) Q&A

Do any of you use your Nexus 7 2013 with Windows 10?

ev1lchris said:
Do any of you use your Nexus 7 2013 with Windows 10?
Click to expand...
Click to collapse
Yes, have used it several times when changing ROMs. Not having any issues with reading or moving files.

cyaclone said:
Yes, have used it several times when changing ROMs. Not having any issues with reading or moving files.
Click to expand...
Click to collapse
Do you use USB 3.0?

I use it with both my USB 2.0 and USB 3.0 ports and everything works fine. We need a little more information if you want us to help with your question, for instance, Are you running an insider build of Windows 10? What ROM are you running on your Nexus 7? What Kernel are you using? Have you tried other cables? Other ports?

I was running Stock Marshmallow. I use the latest TWRP and want to push files to the device.
Every time I plug it in I get a "Device Descriptor Request Failed" error. No driver installation helps.

I have had this problem a couple of times. It wasn't anything to do with Windows 10 in my case and I could only solve it by flashing a previous stock image. This, of course, will wipe the device.

don969 said:
I have had this problem a couple of times. It wasn't anything to do with Windows 10 in my case and I could only solve it by flashing a previous stock image. This, of course, will wipe the device.
Click to expand...
Click to collapse
Really? That makes sense.
The problem is I can't push any files to the device. I don't have the stock image just sitting around on the tablet's drive.
If I format the device or do a factory wipe or reset would that work? Maybe I could get my connectivity back?

Did you go through the full driver step by step process like in Wugfresh's toolkit? Sounds to me like there's a driver **** up and it needs killing via USBdeview. You can try factory resetting the device prior to this just to rule that out.
If you have a phone, you can use something like SuperBeam on the play store to send the factory image for your N7 from your phone to the N7 with reasonable speed and low failure rate (unlike standard BT file sharing). If you have an OTG USB adapter and a flash drive, you can transfer files this way too. There are also PC to Android Wifi file senders too, I don't have any to recommend unfortunately as my preferred version is in re-development by a university student that lacks time since the re-development.

Are there steps according to Wug? I've tried a lot of stuff that I have read on the web including the Microsoft site.
I've been doing a lot of uninstalling and reinstalling in Device Manager. I've changed the settings quite a bit including disabling the USB 3 power saving features.
The only thing I haven't really done is a format or formal factory reset. I've done some Wipes in TWRP. Usually just Dalvik and Cache but I think once I accidently did Data.
TWRP tells me that I have no OS but when I use the File Manager it shows that my directory structure and files are intact.
Should I be going for a format or factory reset?

Related

[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!!!

Linux & Heimdall

Just want to flash TWRP and root sm-t700 using linux anyone tried this?
Sent from my Moto G using XDA Free mobile app
Want this also. No Windows available here at home nor at work.
Thanks All
I'm also a Linux only PC user but have concluded that l have two options. One is a Windows Virtualbox environment using an old Windows OS (e.g. XP, Vista) that I own. My concern with this option is the reliability of the VM's USB connection. I have used it successfully to update firmware on a TV remote but would be more cautious in an activity which may brick an expensive device.
The more reliable option is to use a USB Hard drive bay and an old unused 30-40GB hard drive (Sata or IDE) or a 32-64GB bootable USB flash drive to install a Windows OS and boot off it just when up need Odin or KIES 3.
All of my research and reading conclude that Heidelberg and/or the Java alternative combined with recent Samsung devices are not ready yet so these other options are safer and faster to set up and use at this time.
If you do not presently have a copy of a Windows OS you likely can find a friend who has a old unused XP CD lying around.
Up to a week ago when I bought my Tab S I only had Nexus devices (10 and 5) so their Linux ADB capability made any firmware changes a breeze. Too bad Google does not enforcement ADB as a standard. Let OEM's put out their own KIES equivalents, as much of that functionality can be worked around anyway (e.g. network shares).
Sent from my SM-T800 using XDA Premium HD app
3DSammy said:
I'm also a Linux only PC user but have concluded that l have two options. One is a Windows Virtualbox environment using an old Windows OS (e.g. XP, Vista) that I own. My concern with this option is the reliability of the VM's USB connection. I have used it successfully to update firmware on a TV remote but would be more cautious in an activity which may brick an expensive device.
Click to expand...
Click to collapse
The way I understand it (I might be horribly wrong is that you should be ok if all you're going to do is to flash a custom recovery, not an entire ROM since only the recovery partition would be affected.
If you do not presently have a copy of a Windows OS you likely can find a friend who has a old unused XP CD lying around.
Click to expand...
Click to collapse
There are actually legal ways of downloading Windows for free. One is to download a copy from Microsoft itself. Google for "Windows evaluation copy". This will get you a perfectly free copy of Windows 8.1. The only catch, besides the need to register and give some personal info, is that your Windows installation will time out after 30 days, which should be more than enough time to flash a custom recovery onto your Android device.
I've also heard of a probably legal way to download a copy of Windows 7 from a licensed online distributor. This was supposed to be a backup copy of the OEM version (for those who lost or damaged their Windows installer), which needs to be activated with a valid key. However, you can run your Windows install without activation also for 30 days.
Speaking of legal, I'm actually more concerned about the legality of Odin. Does anybody have any idea who authored the software?
Odin is samsungs official software.
Microsoft also has VM images for download, which are meant for testing Internet Explorer versions... They also have limited lifetime, but if you want a VM it's a faster option.
Too lazy to Google for the url, cause I'm on the phone and all
EDIT: http://dev.modern.ie/tools/vms/
Real or virtual Windows is the only way to go. Heimdall or anything that uses its code doesn't work on the tab s.
fred_be9300 said:
Microsoft also has VM images for download, which are meant for testing Internet Explorer versions... They also have limited lifetime, but if you want a VM it's a faster option.
Too lazy to Google for the url, cause I'm on the phone and all
EDIT: http://dev.modern.ie/tools/vms/
Click to expand...
Click to collapse
Seems to be the better option if you don't want to bother with the process of virtual disk setup and OS installation. Like you said it's also a much smaller download if you choose the IE6 on XP VM (1GB vs. the 3GB+ needed for Windows 7/8). But does the VM copy actually provide USB access? I'm asking because I usually use KVM/QEMU rather than VirtualBox, which is quite hard to set up from the command line compared to KVM.
Gondwanaland said:
But does the VM copy actually provide USB access?
Click to expand...
Click to collapse
I don't know. I guess that's depends more on the features of the VM player software (VMware, kvm, VirtualBox, ..) than on the VM. I've never tried using USB within a VM.
fred_be9300 said:
I don't know. I guess that's depends more on the features of the VM player software (VMware, kvm, VirtualBox, ..) than on the VM. I've never tried using USB within a VM.
Click to expand...
Click to collapse
USB's working fine. I just checked with the IE8 on WinXP image for Virtualbox, which I ran under KVM! Tip for KVM users the zip archive contains a file with an .ova extension. This appears to be a standard Unix tar archive that in turn contains two files with .vdmk and .ovf extensions. The .vdmk file is the Virtualbox image that you can run through KVM in read-only mode. If you want to save changes, you need to convert the image to KVM's native qcow2 format. Note: I only tested if Odin can recognize a Samsung device is connected. I haven't actually tried flashing an image, yet.
Gondwanaland said:
... Note: I only tested if Odin can recognize a Samsung device is connected. I haven't actually tried flashing an image, yet.
Click to expand...
Click to collapse
If you attempt to flash please post your results either way, thanks.
Sent from my SM-T800 using XDA Premium HD app
Successful Odin flashing from a Virtualbox VM
I have successfully flashed Samsung stock firmware to a SM-T800 from a Virtualbox Windows 7 VM guest with Odin v3.10 and a Ubuntu 14.04 host. The guide is general to Windows VMs. I set up both an XP and Windows 7 which had both KIES3 and Odin v3.10 access to the SM-T800 but only flashed with the Win7 VM.
[How-To] Linux, Virtualbox and ODIN for your Samsung device
Also I rooted without tripping KNOX using this guide:
[GUIDE] How to root without tripping knox - Kitkat and Lollipop, Locked bootloader
It's also quite easy to create a bootable version of Windows on a usb drive.
Use Heimdall, worked for me
lucasavalos said:
Just want to flash TWRP and root sm-t700 using linux anyone tried this?
Sent from my Moto G using XDA Free mobile app
Click to expand...
Click to collapse
I just installed TWRP 3.1.1; then Lineage 14.1
Here's my setup:
Target: SM-T700
Workstation: Arch Linux, system update 2011-11-11
Heimdall 1.4.2
Run heimdall command line as root, one command per boot works and if I got an error I needed to unplug the battery to get another successful command
Try
Code:
#heimdall print-pit
and if that works and reboots your device then
Code:
#heimdall flash --RECOVERY twrp-3.1.1-0-klimtwifi.img --no-reboot
Then unplug the battery, boot straight to recovery; failing recovery boot on first try overwrites your TWRP recovery image.
Good luck!
Unplug the battery? On a T700? Interesting lol.

Nextbook Flexx 11 how to dual boot android and 8.1/10

ok! where to even start...
I like many got this 2in1 at wal-mart and I live it. unfortunately I like many am not yet familiar with the new UEFI bootloader bios SOC stuff
heres what I do know and please correct me if im wrong. also please tell me if this 2 in 1 is and can be flashed the same as the asus t100
ok the Flexx11 has a bayntrail-t CR quad core processor 1.33-1.83ghz model Z3735F the t100 is3740
11.6" screen ips touchscreen at 1366x768 res
Efun is the corp and yifang vers.NX1106.1.02.008\139
THE BIOS IS YFG0315009112
it is a 32bit EFI bootloader
the reason I mention all of this is I have tried several times to dualboot androoid and each time ruined the computer and had to return it and I simply no longer wish to return it and love it to much to get something else
the first try the time began to lag and was unfixable for some reason the second time i somehow lost the keys booting and formatted wrong or something and the tablet bricked it would remain black with keyboard lit and no button combo could get it back no boot at all.
I am currently using AMIDUOS to run android kitkat and I love it but from what I understand it isnt compatible with win10 and really still isnt the same as the full android being on the tablet although really really close and awesome
but honestly I have been doing this stuff for years and now with this new windows secure boot and system on a chip stuff im lost
ever get anywhere with this?
I'm curious as well.
It has to be possible. I say that because I recently owned a ChuWi dual-boot device with the same Baytrail processor and SOC.
I wonder if it wouldn't be possible to take a system dump from one of the chuwi dualboot devices and flash it to the nextbook.
Sent from my Ascend Mate 2 using XDA Free mobile app
I'm also interested in doing this. It appears that the Nextbook Ares has the same hardware (minus 1GB RAM) but has Android. I contacted Nextbook to see if I could get a copy of the Ares Android firmware but was denied. If someone with the Ares could upload a backup that would be helpful.
I was finally able to get this working using this method...
https://hitricks.com/guide-how-to-dual-boot-remix-os-with-windows-uefi-legacy
So far I was able to get it to boot from a partition on the main drive as a test. In the process of installing to a secondary partition on my sd card. We'll see how it goes.
I wasnt able to get the boot menu that he shows but after going through the steps I then had an Android OS boot option in the bios boot menu. Pretty awesome! Runs great. Tried running Dead Trigger 2 as a test with full graphics. Ran perfectly.
I just bought one of these yesterday, and it shipped with Windows 10 Home 32-bit. I'm trying to install the 64-bit version but it won't boot from USB. Turns out it doesn't support 64-bit OSes. Where can I find recovery images for this? I messed up and now I don't have audio or touchscreen drivers.
64 bit processor?
I just bought one of these yesterday, and it shipped with Windows 10 Home 32-bit. I'm trying to install the 64-bit version but it won't boot from USB. Turns out it doesn't support 64-bit OSes. Where can I find recovery images for this? I messed up and now I don't have audio or touchscreen drivers.
Click to expand...
Click to collapse
Alright, I'm slightly confused now. Looking at system specs for mine it says it has an x64 based processor. Doesn't that mean it should be able to handle 64-bit OS? Even though it comes with 32-bit? If possible I would like to put 64-bit on it as well, but I'd like to be sure that that's not going to break it.
GeneticJulia said:
Alright, I'm slightly confused now. Looking at system specs for mine it says it has an x64 based processor. Doesn't that mean it should be able to handle 64-bit OS? Even though it comes with 32-bit? If possible I would like to put 64-bit on it as well, but I'd like to be sure that that's not going to break it.
Click to expand...
Click to collapse
It just won't boot the USB. At all. Unless it's 32-bit.
rowdyrocket said:
I was finally able to get this working using this method...
https://hitricks.com/guide-how-to-dual-boot-remix-os-with-windows-uefi-legacy
So far I was able to get it to boot from a partition on the main drive as a test. In the process of installing to a secondary partition on my sd card. We'll see how it goes.
I wasnt able to get the boot menu that he shows but after going through the steps I then had an Android OS boot option in the bios boot menu. Pretty awesome! Runs great. Tried running Dead Trigger 2 as a test with full graphics. Ran perfectly.
Click to expand...
Click to collapse
I'm loving Remix OS on here with dual boot. Having some issues though and I really want this to work.
Main and I mean main issue is no sound at all, no rotation is next in line and Bluetooth isn't working. Everything else works great.
This is so awesome its like Android lollipop with windows desktop functionality. Now if I can get the bugs fixed I will be in android hog heaven.
GREAT FIND BRO!!!!! EXACTLY what I was looking for maybe even better than.
for those interested here is the XDA section for all things REMIX OS
http://forum.xda-developers.com/remix
By the way for those who may want to know I installed dual boot onto the hard drive it went with no issues.Here's some tips for flexx 11
1. I used a partition manager such as easy partition manager to partition the C: drive regardless of what the tutorial said. Couldn't use windows disk management. I deleted the recovery for an extra 5 gigs (make a backup if you do) I used about 19 gigs from the C: drive and made an E: NTFS.
2.Also do not use the remix files from that tutorial use the ones here from the main site http://www.jide.com/remixos-for-pc they are newer and the ones from the other post where incomplete. Also the newer ones on the site now include OTA updating which is totally awesome.
3. I'm hoping this will help someone..... After I was all finished I expected it to dual boot as any other dual boot restart and then i would see options for the OS's not the case here I got stuck on this I was using easy BCD and trying all sorts of stuff, once I looked at the tut a little closer I realized you don't need any of that. Once your all done do a restart and it will go back to windows as usual. Now go to settings, then recovery, then advanced startup and choose from devices I think its the second option on the left list. There you will find Android OS click that and it will take you to your dual boot options. Sounds a lot more complicated than it really is. But believe me once you know this your better off.
And that's all I've got please and I mean please post here with any fixes especially for sound and if you have questions I will try to help.
Thanks
PS: I AM GETTING OCASIONAL LOCK UPS, MEANING THE OS FREEZES AND I HAVE TO RESTART BY HOLDING POWER.
Im not sure if this is good news or not...
Using the methos outlined I was not able to get audio bluetooth autorotate and other things to work but after a bit of digging I found out that remix os has an image specifically for nextbook baaytrail (Our PC) here: http://www.jide.com/remixos/devices
click other upper left.....
I cannot find instructions to install this though and using the other install instructions from here fail because the only part of the file to replace is the system image.
I also attempted the other install methods and easy BCD does not work for this PC
So if anyone can help to install this file specifically for our computer as well as verify that it works and what works and how you installed would be great
OK this is really cool I have made headway sort of.
I have installed kit kat android-x86-4.4-r3.img using the Androidx86-Installv24-5800.exe installer and i have rotation, root and it works pretty good for the most part wifi works great so far no bluetooth, it freezes during shut down and the major issue as in most cases is the sound. Im not sure about the camera now that I think about but i will check and report back here.
I really want the sound working on this and I woud be bigtime happy this forum could be solved as far as im concerned
From what I understand there is a bug with baytrail and linux where the spp port is pointed automatically to the usb or something. but for the life of me after weeks of scouring the internet cannot find a laymens guide to a simple fix for this. I'm really not even sure there is one because I'm yet find a rock solid confirmation of a solution
Update: camera doesn't work either
So far the 4.4.3 port is the best. I just can't seem to find any help whatsoever so its looking like so close yet so far away. Its a pure shame that audio and a few other major bugs are the only things in the way of this being a fully working and easy dual boot method.
I have bought a nextbook flexx10 but am unable to install remix OS. I have followed all the steps highlighted before.
1. partitioned the drive with gparted to make a 10G NTFS drive
2. downloaded android x86 5.1.1 iso and remix iso from jide website.
3. used android installer and android 5.1.1 iso to install the image
4. used 7zip to uncompress the remix iso
5. then copied over the 4 necessary files from remix to the drive to the android drive
6. copied over grub.cfg
Now, I do see the entry for androidOS but when I select that, I just get a message at the center of my screen that says "AndroidOS boot failed" and a blue OK button in DOS like font. thats it.. I am interested in knowing if any additional BIOS settings needs to be tweaked.
furthermore, I have tried installing android x86 6.0 by formating the same partition as ext4. All proceeded well and i got to the last screen that said "Run android-x86 now" or reboot. I removed the USB and was able to get into android. (some missing functionality). But when i reboot into windows and try to boot into androis, I get the same message of Andoid boot failed..
Thus I need to know if there's some BIOS settings related to permissions or sorts that i'm missing.
thanks
murlig123 said:
I have bought a nextbook flexx10 but am unable to install remix OS. I have followed all the steps highlighted before.
1. partitioned the drive with gparted to make a 10G NTFS drive
2. downloaded android x86 5.1.1 iso and remix iso from jide website.
3. used android installer and android 5.1.1 iso to install the image
4. used 7zip to uncompress the remix iso
5. then copied over the 4 necessary files from remix to the drive to the android drive
6. copied over grub.cfg
Now, I do see the entry for androidOS but when I select that, I just get a message at the center of my screen that says "AndroidOS boot failed" and a blue OK button in DOS like font. thats it.. I am interested in knowing if any additional BIOS settings needs to be tweaked.
furthermore, I have tried installing android x86 6.0 by formating the same partition as ext4. All proceeded well and i got to the last screen that said "Run android-x86 now" or reboot. I removed the USB and was able to get into android. (some missing functionality). But when i reboot into windows and try to boot into androis, I get the same message of Andoid boot failed..
Thus I need to know if there's some BIOS settings related to permissions or sorts that i'm missing.
thanks
Click to expand...
Click to collapse
Sorry for the late reply, use the installer and create a separate drive using C: like a D: or E: and get android 4.4 the .IMG that should work for you and the installer should do everything for you.
So use the uefi android installer after you partition a drive to load android 4.4 the uefi IMG
Its just going to piss you off though because there's no audio and seemingly no way to fix it, which is a crying shame ��
P.S. typically secure boot is off in the bios on this machine, but if by any chance you turned it on or the newer ones come that way make sure it is off or this will not work.
UEFI Settings
So I can get to a menu with 6 icons (2 rows and 3 columns) by running the "shutdown.exe /r /o" command and then going to Troubleshoot>Advanced Options>UEFI Firmware Settings and clicking restart. The problem is that when I get to this menu the touchscreen and keyboard do not work, and I can only move the highlighter up and down, not left and right. Hopefully one you guys have figured this out. I contacted the Nextbook support desk and they were no help at all.
korycooper said:
So I can get to a menu with 6 icons (2 rows and 3 columns) by running the "shutdown.exe /r /o" command and then going to Troubleshoot>Advanced Options>UEFI Firmware Settings and clicking restart. The problem is that when I get to this menu the touchscreen and keyboard do not work, and I can only move the highlighter up and down, not left and right. Hopefully one you guys have figured this out. I contacted the Nextbook support desk and they were no help at all.
Click to expand...
Click to collapse
Okay. So I was able to test this one of my co workers Nextbook and it seems like its a problem with mine.
This might be beneficial for us Flexx 11 users. It's a full port of Remix 2.0 to the Ares 8 with everything working except the camera rotation issue. Very promising. I've heard the hardware is similar. Working on attempting to install on mine. Anyone else tried it?
http://forum.xda-developers.com/remix/supported-devices/port-remix-os-2-0-nextbook-ares-8-t3498015
Hey guys,
NextBook Flexx 11, 64Gb, NXW116QC264, Windows 10
I'm really interested in trying to install Remix OS in Dual boot. However, in my trials, I goofed up my tablet. I found an image, but it turned out to be a Windows 8.1 image, and it wiped everything from my tablet. I had originally had Windows 10 on it.
Could someone perhaps be able to send me the recovery partition of their Nextbook; as long as they had Win10 installed. Maybe if I dump a Win10 recovery partition, I can do a repair on it and restore Win10 to the system.
I can't find the stock/factory rom for the Win10 version of the Flexx.
Thanks in advance,
Kori
KorishanTalshin said:
Hey guys,
NextBook Flexx 11, 64Gb, NXW116QC264, Windows 10
I'm really interested in trying to install Remix OS in Dual boot. However, in my trials, I goofed up my tablet. I found an image, but it turned out to be a Windows 8.1 image, and it wiped everything from my tablet. I had originally had Windows 10 on it.
Could someone perhaps be able to send me the recovery partition of their Nextbook; as long as they had Win10 installed. Maybe if I dump a Win10 recovery partition, I can do a repair on it and restore Win10 to the system.
I can't find the stock/factory rom for the Win10 version of the Flexx.
Thanks in advance,
Kori
Click to expand...
Click to collapse
Just to be clear...(and this goes for everyone wondering in the future) it was windows 10, from the factory??? Last i checked
they only shipped with windows 8.1 or android, depending on the model...If not and you put windows 10 on there, back when it was free, you just use the media creation tool from Microsoft to update windows 8.1 to Windows 10 (after restoring windows 8.1)... it can do this because most tablets have unchangeable hardware, so no cd key is required...it's like how your md5 hash verifies your downloaded files, Windows provides Microsoft with your hardwares md5 hash signature and if it is in the list, then it activates the pc/tablet... but, it only works if you got it free, not if you bought it... if you bought win10 then you will need your cd-key when you re-install, while the other steps are same as above... just note, that for the free upgrade there was NO cd-key, therefore in that instance, if it asked you for a key, you would leave it blank, which you can do in any case, and add your key in from Windows if needed...
And... as for the others having sound issues in Android, I read something about a reason for that having to do with something called an... 'audio stack', I think it was??? Not 100% sure what it meant, but basically, it is designed so the audio hardware only works in windows, I think... (so they can make more money, by making you buy the android tablet separately...)
hope this helps someone who stumbles upon this thread...
Wiebenor said:
Just to be clear...(and this goes for everyone wondering in the future) it was windows 10, from the factory??? Last i checked
they only shipped with windows 8.1 or android, depending on the model...If not and you put windows 10 on there, back when it was free, you just use the media creation tool from Microsoft to update windows 8.1 to Windows 10 (after restoring windows 8.1)... it can do this because most tablets have unchangeable hardware, so no cd key is required...it's like how your md5 hash verifies your downloaded files, Windows provides Microsoft with your hardwares md5 hash signature and if it is in the list, then it activates the pc/tablet... but, it only works if you got it free, not if you bought it... if you bought win10 then you will need your cd-key when you re-install, while the other steps are same as above... just note, that for the free upgrade there was NO cd-key, therefore in that instance, if it asked you for a key, you would leave it blank, which you can do in any case, and add your key in from Windows if needed...
And... as for the others having sound issues in Android, I read something about a reason for that having to do with something called an... 'audio stack', I think it was??? Not 100% sure what it meant, but basically, it is designed so the audio hardware only works in windows, I think... (so they can make more money, by making you buy the android tablet separately...)
hope this helps someone who stumbles upon this thread...
Click to expand...
Click to collapse
I realize this is a dead thread, but I had to chime in... I bought my NextBook Flexx 11 from Walmart 3 or 4 years ago and it shipped with Windows 10 Home, not Windows 8.1... However, IMHO, Windows 10 is a resource hog on this little device. I'm currently looking in to installing Linux...

Out Of The Blue ZE551ML Internal Storage No Longer Accessible In Windows 7

I only connect my ZE551ML to my Windows 7 x64 when I've got to do firmware updates or transfer music, and I haven't done either in a while.
On my "MTP USB Device" driver I'm now getting: This device cannot start. (Code 10)
The ASUS Android Composite ADB and PC Link Interface drivers are loaded and fine.
Things that I've tried:
- the Asus android drivers
- the Intel android drivers
- the universal ADB drivers.
- different USB cables
- different USB slots
The perplexing thing is that the image that allows you to install "ASUS ZenUI PC Suite" is available as a CD drive, "PC Link" works when mirroring my phone onto my computer and using ADB from a command prompt can see my device.
I don't know what I've installed between the last time it worked to now, and I'm at wit's end with what I can do.
Anyone have a suggestion at a possible next step?
Do you by any chance have Windows 7N (one without media player)?
Mine did the same when i connected the missus MTK device.
Unfortunately i need hers to stay for future updates and for using MTK flashtools too.
Great news is the( share link ) built in asus app in M - never used it before until this , click asus share link app on phone whilst connect to PC (for the first installation) and then you can transfer to an from pc to sd (either sd) in share link settings.
Then after - uses your network for transfer ,no cables , saves charge port i guess and its -- Fast !
USBdeview can be used if you want to see/want/remove if old/new drivers might be causing conflicts but am quite happy with the share link app now,ps i`m on windows 10 and too also not sure whether an update came whilst installing MTK destroyed it too
chiudikas said:
Do you by any chance have Windows 7N (one without media player)?
Click to expand...
Click to collapse
No, I'm running Home Premium, and have both media player and media center.
timbernot said:
Mine did the same when i connected the missus MTK device.
Unfortunately i need hers to stay for future updates and for using MTK flashtools too.
Great news is the( share link ) built in asus app in M - never used it before until this , click asus share link app on phone whilst connect to PC (for the first installation) and then you can transfer to an from pc to sd (either sd) in share link settings.
Then after - uses your network for transfer ,no cables , saves charge port i guess and its -- Fast !
USBdeview can be used if you want to see/want/remove if old/new drivers might be causing conflicts but am quite happy with the share link app now,ps i`m on windows 10 and too also not sure whether an update came whilst installing MTK destroyed it too
Click to expand...
Click to collapse
I'm still on Lollipop... Though it does have a sharelink app as well. I've tried setting it up, and on my phone it can't see my microSD card.
I'll give USBdeview a go and see if uninstalling all the Samsung/Asus/Intel drivers does anything.
It's the strangest thing... why would I be able to see it in ADB, be able to install the PC Link programs from the ROM and yet not be able to see internal storage?
azthemansays said:
No, I'm running Home Premium, and have both media player and media center.
I'm still on Lollipop... Though it does have a sharelink app as well. I've tried setting it up, and on my phone it can't see my microSD card.
I'll give USBdeview a go and see if uninstalling all the Samsung/Asus/Intel drivers does anything.
It's the strangest thing... why would I be able to see it in ADB, be able to install the PC Link programs from the ROM and yet not be able to see internal storage?
Click to expand...
Click to collapse
Share link app - 3 dots -settings - storage location - click on /sdcard -- opens up to show internal sd and whatever your ext sd is called --select your choice -- click OK , you may have to allow rights to it in file manager :good:
Usbdeview should be ok
Why it happens ? conflicts with drivers i suspect
timbernot said:
Share link app - 3 dots -settings - storage location - click on /sdcard -- opens up to show internal sd and whatever your ext sd is called --select your choice -- click OK , you may have to allow rights to it in file manager :good:
Click to expand...
Click to collapse
That's the issue, when I get to that point it only shows "Internal Storage." As an aside, my phone's bootloader is unlocked and it's rooted.
*EDIT* - When I get to the part where I choose the directory, the file manager comes up with the "Recent" page. if I press the menu button, I get the option to hide SD card and file size, but in the list to the left it only lists "Internal Storage"
timbernot said:
Usbdeview should be ok
Why it happens ? conflicts with drivers i suspect
Click to expand...
Click to collapse
I just removed all the drivers that I could tell were related and am about to reboot.
phone settings - storage -- eject sd -- remount , set up sd for ext storage ? Never used this before so am at a loss , my ext sd was there when i clicked on /sdcard along side internal and after OK i followed on screen commands to allow it . Again , this is in M and never used it before on LP.
When you open file manager , your sd is there alongside internal or blanked out ?
Good luck hope you get it sorted , keep us posted BBFN
timbernot said:
phone settings - storage -- eject sd -- remount , set up sd for ext storage ? Never used this before so am at a loss , my ext sd was there when i clicked on /sdcard along side internal and after OK i followed on screen commands to allow it . Again , this is in M and never used it before on LP.
When you open file manager , your sd is there alongside internal or blanked out ?
Good luck hope you get it sorted , keep us posted BBFN
Click to expand...
Click to collapse
Still run into the same issue after remounting. It lets me select my internal, but not my SD. I guess it'll have to do for the time being - use it to move from computer to internal, then move it from internal to external.
And Removing selective ones in USBdeview still gave me the same issue:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
so I went ahead and uninstalled all the ones that were for the specific USB slot, and am about to reset. Fingers crossed...
Ok try the info in ASUS file manager
open file manger , 3 dots , about , help and feedback , 2nd box down
ps , the time you spent trying to fix this
upgrade to M latest , better battery etc etc
timbernot said:
Ok try the info in ASUS file manager
open file manger , 3 dots , about , help and feedback , 2nd box down
ps , the time you spent trying to fix this
upgrade to M latest , better battery etc etc
Click to expand...
Click to collapse
I can't upgrade to M without being able to transfer files to my phone :laugh::crying:
And more importantly, I don't know if upgrading would change anything when it comes to the Windows 7 drivers. I keep trying to update driver to the Asus ones, but it keeps reverting to the generic "MTP USB Device" one. I've even tried to go into the windows inf files and remove that generic driver, but then windows won't accept the Asus ones at all.
When I go into the "feedback and help" section I get an error:
I've just about had it up to here with this phone. At the beginning it was giving me similar issues but I managed to sort it out... and now we're back to the issues that occurred back near the phone's launch. Full goddamn circle.
What build /date in settings ?
We gonna get you updated v soon .
First you need to unroot it.
Then fastboot flash stock recovery which corresponds with your build..
Then adb sideload a fresh copy of the build your on .You know how to perform these tasks above ???
If not , we do it soon
last but least don't smash it up
Have a read thru here to get general idea what needs doing
http://forum.xda-developers.com/zenfone2/help/how-recovery-t3514205
---------- Post added at 02:53 AM ---------- Previous post was at 02:44 AM ----------
azthemansays said:
I can't upgrade to M without being able to transfer files to my phone :laugh::crying:
And more importantly, I don't know if upgrading would change anything when it comes to the Windows 7 drivers. I keep trying to update driver to the Asus ones, but it keeps reverting to the generic "MTP USB Device" one. I've even tried to go into the windows inf files and remove that generic driver, but then windows won't accept the Asus ones at all.
When I go into the "feedback and help" section I get an error:
I've just about had it up to here with this phone. At the beginning it was giving me similar issues but I managed to sort it out... and now we're back to the issues that occurred back near the phone's launch. Full goddamn circle.
Click to expand...
Click to collapse
keep cal.m
timbernot said:
What build /date in settings ?
We gonna get you updated v soon .
First you need to unroot it.
Then fastboot flash stock recovery which corresponds with your build..
Then adb sideload a fresh copy of the build your on .You know how to perform these tasks above ???
If not , we do it soon
last but least don't smash it up
keep cal.m
Click to expand...
Click to collapse
Haha, thank you. I'll try to stay calm.
I'm sitting at 194 right now and the security patch level was last updated July 1, 2016.
This phone is my daily driver and I need to go to bed, but I'll Titanium Backup the apps and make a nandroid backup tomorrow as soon as I get home from work so I can start flashing.
It's been awhile... should I flash back the stock recovery before I unroot? And it's been giving me issues with the micro SD card occasionally unmounting on it's own as well as Google Play services crashing at random times (I've tried all the tricks & tips up to uninstalling it to get rid of corrupted installation, but it still persists)... Should I do a factory reset after flashing the stock image just to try to clear everything up? I'd have to move everything to my microSD card first though...
azthemansays said:
Haha, thank you. I'll try to stay calm.
I'm sitting at 194 right now and the security patch level was last updated July 1, 2016.
This phone is my daily driver and I need to go to bed, but I'll Titanium Backup the apps and make a nandroid backup tomorrow as soon as I get home from work so I can start flashing.
It's been awhile... should I flash back the stock recovery before I unroot? And it's been giving me issues with the micro SD card occasionally unmounting on it's own as well as Google Play services crashing at random times (I've tried all the tricks & tips up to uninstalling it to get rid of corrupted installation, but it still persists)... Should I do a factory reset after flashing the stock image just to try to clear everything up? I'd have to move everything to my microSD card first though...
Click to expand...
Click to collapse
First - transfer your stuff to pc off internal thru sharelink
unroot , flash back stock recovery .194 - reboot to recovery , update over adb , adb sideload .196 stock firmware , which should be renamed to MOFD_SDUPDATE and put in your fastboot/adb folder previously
adb cmd >
adb sideload MOFD_SDUPDATE.zip
set up not connecting to wifi - skip everything you can-- factory reset .
Set up correctly this time . Run for 3 days without any modifications . Make sure everything is running correctly :good:
timbernot said:
First - transfer your stuff to pc off internal thru sharelink
Click to expand...
Click to collapse
Already running into issues with the first step. Share Link gets to about 100mb transferred, then my phone's screen blacks out and is non-responsive, though it shows touchscreen presses (I have that turned on in developer settings). The transfer hits around 200mb and then the transfer gets cancelled. It's also rebooted twice.
This is getting to ludicrous levels.
*EDIT* - I tried uninstalling all the USB controllers in Windows Device manager in case they were corrupted, but I'm still getting the same failure with the generic "MTP USB Device" being installed instead of the Asus one and still getting that yellow exclamation mark. When I try to update it to the Asus one, it fails and disappears when I unplug and replug the phone. This is maddening because it was working in October...
*EDIT 2* - I'm thinking of testing it on another windows installation... I've got some spare HD space that i could partition and install another copy of my Win 7 on to see if it's my Windows or phone that's corrupted. If it's not my phone, I'll be able to transfer everything out...
Hey some news , after reading what you are experiencing - I remembered i have another lappy with windows 10 on in bedroom wardrobe - Not been used for nearly a yr , fired it up with wifi off and both my drives are visible
So , mine IS either MTK driver conflict or a windows update or both
Whatever , i will update it today and test further.
This does`nt explain your sharelink probs tho, mine transferred 443mbs of CM14.1 in 3 mins just now with the same prob you have.
Use file manager instead to transfer to ext SD. Instead of sharelink
And go about sorting it out , with whats already mentioned and with the fresh copy of 7 - hopefully it is windows and not the phone you said you had probs with from new
So it failed to install the driver in the new Windows 7 install, but somehow booting into recovery allowed me to access and copy everything off of internal storage. But of course, booting back into normal mode breaks it again.
I'm just going through backing up my SMS and using Titanium backup for the apps and I'll be ready to take the next step.
azthemansays said:
So it failed to install the driver in the new Windows 7 install, but somehow booting into recovery allowed me to access and copy everything off of internal storage. But of course, booting back into normal mode breaks it again.
I'm just going through backing up my SMS and using Titanium backup for the apps and I'll be ready to take the next step.
Click to expand...
Click to collapse
Are you familiar with flashtools ?
It's just another method to flash a raw file in fastboot boot loader state .and boots you into system by itself after about 10 mins..but I'm a bit unsure you should use it with the probs re screen blanking earlier with share app.
Maybe we keep that as a last resort
good luck
timbernot said:
Are you familiar with flashtools ?
It's just another method to flash a raw file in fastboot boot loader state .and boots you into system by itself after about 10 mins..but I'm a bit unsure you should use it with the probs re screen blanking earlier with share app.
Maybe we keep that as a last resort
good luck
Click to expand...
Click to collapse
My usual method of Flashing OTAs and ROMS was using this guide. I'm not familiar with flashtools, but I've used Odin before and I'm a quick study.
Now, I've got a few things that I would normally take back to stock/remove before unrooting and updating:
- Adaway hosts files
- busybox
- Viper4android sound.conf mod
- build.prop modification for permissive SELinux
- might be more but I can't remember.
I also recall flashing a new kernel at some point, but it was a while ago and I don't remember how to find out if what I have now is stock or not. I think it was this one.
Do I need to worry about taking all that back to stock before reflashing .194?
I usually edit the OTAs so I could flash them with TWRP, so I never had to flash stock recovery back in the past... what's the ADB name for the recovery partition?
*EDIT* - I'm also not familiar with all this new stuff like Magisk 8 and seamless root. Is this the go-to method for rooting 6.0? I like the sound of being able to root and unroot on the fly to bypass root detection by apps. I think I want to flash CleanSTOCK rather than just stock MM if it's less bloated.
azthemansays said:
My usual method of Flashing OTAs and ROMS was using this guide. I'm not familiar with flashtools, but I've used Odin before and I'm a quick study.
Now, I've got a few things that I would normally take back to stock/remove before unrooting and updating:
- Adaway hosts files
- busybox
- Viper4android sound.conf mod
- build.prop modification for permissive SELinux
- might be more but I can't remember.
I also recall flashing a new kernel at some point, but it was a while ago and I don't remember how to find out if what I have now is stock or not. I think it was this one.
Do I need to worry about taking all that back to stock before reflashing .194?
I usually edit the OTAs so I could flash them with TWRP, so I never had to flash stock recovery back in the past... what's the ADB name for the recovery partition?
*EDIT* - I'm also not familiar with all this new stuff like Magisk 8 and seamless root. Is this the go-to method for rooting 6.0? I like the sound of being able to root and unroot on the fly to bypass root detection by apps. I think I want to flash CleanSTOCK rather than just stock MM if it's less bloated.
Click to expand...
Click to collapse
Lets just get you up and running stock for a few days -- No mods ok ?
I think its best we flash raw at bootloader state , refresh here i will add files to download ready and info how to:good:
Flashtools - http://www.mediafire.com/file/sm76jyyz8t1axmz/AsusFlashToolInstaller_1.0.0.17.rar install and run as admin
Raw collection of and thanks go to Realyoti there - choose .196, bottom one last of the LP
https://yadi.sk/d/FijRoAVJtvRiG
Video
Ignore the first 2:17 mins - fast forward to 2:18 mins for flashtool flash and adding raw and general settings > choose wipe data to prevent any bugs from previous state
Note -- you just let it complete on its own , the video goes to show how to correct serial number , you dont need to -- once it starts flashing - let it finish
https://www.youtube.com/watch?v=PmbRaJijIBs&feature=youtu.be
When up n running say a thank you to Realyoti here please
http://forum.xda-developers.com/zenfone2/general/z008-z00a-z00d-z00x-raw-fw-collection-t3448966
timbernot said:
Lets just get you up and running stock for a few days -- No mods ok ?
Click to expand...
Click to collapse
Haha, sorry for putting the cart before the donkey at the end there...
But I was asking if I need to remove any/all of these mods before flashing the raw file? And does the raw file also include the recovery partition? That's why I was asking where to flash "recovery.img" to go from TWRP to stock recovery...
Just 19% into transferring all my Titanium backups to Google Drive right now.

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