TWRP Error 70 on Nexus 7 2013 - Nexus 7 (2013) Q&A

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

Related

[SOLVED] Rooting HDC Galaxy Note 2 Mega (MTK6577)

Hi guys!
Just recently I bought the "HDC Galaxy Note 2" off of fastcardtech. I got it a few days ago, am fairly pleased with it except for the slight miscalibrated touch screen. There are some apps on various markets aiming to fix this by re-applying new calibrations. The problem is that you'll have to be rooted in order to run them.
The phone comes with a built-in calibration setting, called "Als_ps calibration", which you can utizile to correct the sensor. Alas, it only corrects the phone's recognition of obstacles placed above it, so that you accidentaly wouldn't press any undesired button during a call.
Phone: http://www.fastcardtech.com/Galaxy-Note-2-Mega
Here's what I've done so far!
Enabled USB-debugging and installed USB-drivers. [MT65xx_USB_Driver.zip]
Tried the bin4ry root method, normal mode. [Root_with_Restore_by_Bin4ry_v18.zip]
This method:
http://forum.xda-developers.com/showthread.php?t=1886460
Everything works just fine until the phone reboots. Bin4ry is then unable to mount or copy the last files needed to apply root permission, see attached picture.
I have attached my specs in a screenshot, nevermind the quality, t'was done by another crap-camera! Sorry ;]
Any kind soul who can help me root this thing?
Edit:
Rooting this device has been made possible by GT35pro. See posts below.
same problem
KristN91 said:
Hi guys!
Just recently I bought the "HDC Galaxy Note 2" off of fastcardtech. I got it a few days ago, am fairly pleased with it except for the slight miscalibrated touch screen. There are some apps on various markets aiming to fix this by re-applying new calibrations. The problem is that you'll have to be rooted in order to run them.
The phone comes with a built-in calibration setting, called "Als_ps calibration", which you can utizile to correct the sensor. Alas, it only corrects the phone's recognition of obstacles placed above it, so that you accidentaly wouldn't press any undesired button during a call.
Phone: http://www.fastcardtech.com/Galaxy-Note-2-Mega
Here's what I've done so far!
Enabled USB-debugging and installed USB-drivers. [MT65xx_USB_Driver.zip]
Tried the bin4ry root method, normal mode. [Root_with_Restore_by_Bin4ry_v18.zip]
This method:
http://forum.xda-developers.com/showthread.php?t=1886460
Everything works just fine until the phone reboots. Bin4ry is then unable to mount or copy the last files needed to apply root permission, see attached picture.
I have attached my specs in a screenshot, nevermind the quality, t'was done by another crap-camera! Sorry ;]
Any kind soul who can help me root this thing?
Click to expand...
Click to collapse
omg i have the exact same problem, did you get a solution? PLEASE i need to root it so bad
CWM installed and rooted the HDC galaxy note 2 MAGE / MEGA
rebmoe said:
omg i have the exact same problem, did you get a solution? PLEASE i need to root it so bad
Click to expand...
Click to collapse
I just created the cwm recovery and root. The link is on my blog. The zip file is password protected so be sure to get it from my blog page.
http://gt35pro-mobile-gadgets.blogspot.sg/2013/02/cmw-recovery-english-and-root-for-hdc.html
After you have clockwork mod recovery, use it to flash the root access into the phone.
Have fun!
KristN91 said:
Hi guys!
Just recently I bought the "HDC Galaxy Note 2" off of fastcardtech. I got it a few days ago, am fairly pleased with it except for the slight miscalibrated touch screen. There are some apps on various markets aiming to fix this by re-applying new calibrations. The problem is that you'll have to be rooted in order to run them.
The phone comes with a built-in calibration setting, called "Als_ps calibration", which you can utizile to correct the sensor. Alas, it only corrects the phone's recognition of obstacles placed above it, so that you accidentaly wouldn't press any undesired button during a call.
Phone: http://www.fastcardtech.com/Galaxy-Note-2-Mega
Here's what I've done so far!
Enabled USB-debugging and installed USB-drivers. [MT65xx_USB_Driver.zip]
Tried the bin4ry root method, normal mode. [Root_with_Restore_by_Bin4ry_v18.zip]
This method:
http://forum.xda-developers.com/showthread.php?t=1886460
Everything works just fine until the phone reboots. Bin4ry is then unable to mount or copy the last files needed to apply root permission, see attached picture.
I have attached my specs in a screenshot, nevermind the quality, t'was done by another crap-camera! Sorry ;]
Any kind soul who can help me root this thing?
Click to expand...
Click to collapse
Kristen, where you able to re-calibrate after rooting; I just ordered this phone last week so I want to be prepared if need be.
londonflu said:
Kristen, where you able to re-calibrate after rooting; I just ordered this phone last week so I want to be prepared if need be.
Click to expand...
Click to collapse
The one I got did not have that screen calibration problem. Everything works good. Anyway, root is available now.
Superb!
Thank you for sorting this out!
-KristN91
Extra Guide
Follow the link provided by GT35pro in his first post.
To everyone attempting this flash;
!! First of all, copy the Superuser.zip to the root of your internal phone memory or external SD Card.!!
* Use a high-quality mini-USB cable (The one that comes with your phone should work just fine)
* Connect your MEGA to your pc, without the battery inserted.
(This device will connect and disconnect, when it's visible, be sure to grab it and follow the next step)
* Make sure that you have the right drivers for MTK65xx preloader "mtk65xx Vcom driver" and install them through the Device Manager.
* Insert your battery again, with the cable still connected, and install the second MTK65xx preloader.
* Disconnect phone from pc and remove the battery
* Start up Smart flash Tool and select the scatter file included in the package.
* Now, select and tick the checkbox for Recovery only. Smart Flash Tool will complain about the flash, due to it not containing all the appropriate files needed for a "secure boot". Nevermind that pop-up and proceed with downloading.
* Start Download
* Insert the battery and connect your phone to your pc, with that, the flashing should start.
* Boot Phone into recovery mode (pwr button and vol - or vol +) and install superuser from ZIP-file.
* After reboot you should be rooted.
///////////////
Fun Fact!
I actually managed to install a pre-rooted HDC S7100 rom on my MEGA.
The port isn't 100% accurate
-Invalid IMEI, this was fixed by Talkingmobile's guide; " how to write imei number for MTK 65XX " -Just google it!
-Auto-rotation is unavailable, no fix yet.
-Als_pl calibration is unavailable (resulting in active screen during call)
Besides that, the rom is arguably better than the MEGA's original N7100 rom, in terms of visual presentation.
Smooth transitions, vivid and vibrant colors would be a good example of aspects that would come out as improved over the original rom.
Interested in the S7100 rom? Just PM me and I'll provide the link.
Cheers!
S_ft_need_download_all_fail (4050)
I'm trying for several days, but always get this error in the flash tool: S_FT_NEED_DOWNLOAD_ALL_FAIL (4050)
Tried on Windows 7 x64, Windows 7 x32 and Windows XP SP3 (x32). Only on the Windows XP computer I was able to make a backup with Flash Tool using the Read Back option.
When I try to flash the red bar goes to 100% then the error message shows...
Does anyone get this error aswell, and did someone manage to solve this?
Please help, I'm in desperate need for root because I need touch screen calibration.
Thnx!!
YES! SUCCES!! I managed to root my HDC Mage :laugh: Did use another method though, check http://forum.xda-developers.com/showthread.php?t=2160490 if you are interested.
Anyway, now back to calibrating the touchscreen. What tools are good do fix touchscreen issues? I already tried http://forum.xda-developers.com/showthread.php?t=934500, but I still am not satisfied.
Thnx :good:
Just curious, if anyone that owns an HDC, is actually located in the USA?
londonflu said:
Just curious, if anyone that owns an HDC, is actually located in the USA?
Click to expand...
Click to collapse
Nope, the Netherlands. Why do you ask?
Sent from my GT-I9000 using xda app-developers app
jg77 said:
Nope, the Netherlands. Why do you ask?
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
Because I tried to order 5 different phones from China including Fastcardtech; they couldn't ship for some reason; even got an empty box from ZOPO mobile. I ended up buying the BLU here in the US, I'm kind of glad it happened, since now I have an N'vidia Tegra 4 CPU, that runs circles around the dual-core phones.
I did order one more phone on ebay from China, been waiting for 2 weeks now. MAKES ME WONDER IF THEY EVEN ACTUALLY SHIP TO THE US AT ALL?
Thank to Paypal I was able to get refunded everytime.
KristN91 said:
Follow the link provided by GT35pro in his first post.
To everyone attempting this flash;
!! First of all, copy the Superuser.zip to the root of your internal phone memory or external SD Card.!!
* Use a high-quality mini-USB cable (The one that comes with your phone should work just fine)
* Connect your MEGA to your pc, without the battery inserted.
(This device will connect and disconnect, when it's visible, be sure to grab it and follow the next step)
* Make sure that you have the right drivers for MTK65xx preloader "mtk65xx Vcom driver" and install them through the Device Manager.
* Insert your battery again, with the cable still connected, and install the second MTK65xx preloader.
* Disconnect phone from pc and remove the battery
* Start up Smart flash Tool and select the scatter file included in the package.
* Now, select and tick the checkbox for Recovery only. Smart Flash Tool will complain about the flash, due to it not containing all the appropriate files needed for a "secure boot". Nevermind that pop-up and proceed with downloading.
* Start Download
* Insert the battery and connect your phone to your pc, with that, the flashing should start.
* Boot Phone into recovery mode (pwr button and vol - or vol +) and install superuser from ZIP-file.
* After reboot you should be rooted.
///////////////
Fun Fact!
I actually managed to install a pre-rooted HDC S7100 rom on my MEGA.
The port isn't 100% accurate
-Invalid IMEI, this was fixed by Talkingmobile's guide; " how to write imei number for MTK 65XX " -Just google it!
-Auto-rotation is unavailable, no fix yet.
-Als_pl calibration is unavailable (resulting in active screen during call)
Besides that, the rom is arguably better than the MEGA's original N7100 rom, in terms of visual presentation.
Smooth transitions, vivid and vibrant colors would be a good example of aspects that would come out as improved over the original rom.
Interested in the S7100 rom? Just PM me and I'll provide the link.
Cheers!
Click to expand...
Click to collapse
I took out the battery then connect it to the pc and open device manager, it show mtk65xx preloader then the phone disconnect its self and connect back every two seconds is there a way to fix this pls
thank you
I took out the battery then connect it to the pc and open device manager, it show mtk65xx preloader then the phone disconnect its self and connect back every two seconds is there a way to fix this pls
farazafs said:
I took out the battery then connect it to the pc and open device manager, it show mtk65xx preloader then the phone disconnect its self and connect back every two seconds is there a way to fix this pls
Click to expand...
Click to collapse
Did you install all necessary drivers?
Sent from my GT-I9000 using xda app-developers app
---------- Post added at 08:21 AM ---------- Previous post was at 08:17 AM ----------
farazafs said:
I took out the battery then connect it to the pc and open device manager, it show mtk65xx preloader then the phone disconnect its self and connect back every two seconds is there a way to fix this pls
Click to expand...
Click to collapse
Did you install all necessary drivers? How does sp flash tool respond when you download the recovery?
Sent from my GT-I9000 using xda app-developers app
jg77 said:
Did you install all necessary drivers?
Sent from my GT-I9000 using xda app-developers app
---------- Post added at 08:21 AM ---------- Previous post was at 08:17 AM ----------
Did you install all necessary drivers? How does sp flash tool respond when you download the recovery?
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
I can Install all necessary drivers, when I Power OFF phone and connect it to my PC, in device manager it can show MT65xx Preloader (Com 9) connected n within 3 sec it can be disconnected.... in SP Flash Tool i can select recovery then press download button... then again i can connect phone, it's give me some 80xx error. it's mean that device not connect.
farazafs said:
I can Install all necessary drivers, when I Power OFF phone and connect it to my PC, in device manager it can show MT65xx Preloader (Com 9) connected n within 3 sec it can be disconnected.... in SP Flash Tool i can select recovery then press download button... then again i can connect phone, it's give me some 80xx error. it's mean that device not connect.
Click to expand...
Click to collapse
An 80Xx error does not always mean device not connected. It can also mean there is something not right in the scatterfile (error 8038). You should take a look at the sp flash tool logfiles. You can post them here so I can have a look.
jg77 said:
An 80Xx error does not always mean device not connected. It can also mean there is something not right in the scatterfile (error 8038). You should take a look at the sp flash tool logfiles. You can post them here so I can have a look.
Click to expand...
Click to collapse
Attached snapshot given below... always when I tried to flash Recovery from SP Flash Tool it's only give me this error.
farazafs said:
Attached snapshot given below... always when I tried to flash Recovery from SP Flash Tool it's only give me this error.
Click to expand...
Click to collapse
There is something wrong in the layout of the scatterfile. Can you post the logiles of sp flash tool? Just zip them all together.
I have had the exactly the same error with my HDC Mage. I just had to rename a small section of the scatterfile and then it was all good.

MAC cannot see Nexus 7, please help

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.

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

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

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?

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.

Categories

Resources