Develop Bugs

[Q] Root, OTG, and USB Storage Questions

I know my way around fastboot, adb, command line pretty well, but I just got my N7(2013) last night, so in that sense, I'm a Noob.
Questions:
Can I just root with SuperSU without TWRP? Or will the stock recovery not let me do that? i.e. is there a signed SuperSU? I would rather keep my stock recovery, if possible.
After I root, do USB storage devices connected via an OTG cable "Just Work"? Do I have to manually mount them? Does it enable a Menu?
Is there any way to enable USB Storage (The other way, when N7 is connected to PC) once I root? Is anybody working on this?

Linuxslate said:
Can I just root with SuperSU without TWRP? Or will the stock recovery not let me do that? i.e. is there a signed SuperSU? I would rather keep my stock recovery, if possible.
Click to expand...
Click to collapse
Suggest you do
fastboot boot twrp.img
instead of flashing twrp onto the tablet's recovery partition
This will run twrp temporarily to install SuperSU's update.zip but will leave stock recovery on your tablet untouched.
Linuxslate said:
After I root, do USB storage devices connected via an OTG cable "Just Work"? Do I have to manually mount them? Does it enable a Menu?
Click to expand...
Click to collapse
Recognition is automatic. Mounting is not. So yes, you need to mount them. Whether you do that manually or through a helper app like stickmount is up to you
Linuxslate said:
Is there any way to enable USB Storage (The other way, when N7 is connected to PC) once I root? Is anybody working on this?
Click to expand...
Click to collapse
Doubtful. N7 doesn't have a real sdcard partition formated fat32. It has a simulated sdcard kept in the /data/media folder. MTP/PTP are the only ways Google wants to support storage going forward.

Thanks, sfhub;
Great trick about running twrp once.
That way I can have root, and my stock recovery.
Thanks for the other info, too.

No MTP or Storage show on PC
I am running windows 7 64 bit and I have managed to get root on my new Nexus 7, but now when I plug my tablet into the PC it says on the tablet connected as media device, but it never shows up anywhere on my pc so that I can transfer files on to it. The nexus 7 never shows up as an extra drive or as an media device. Please help. can not seem to find any info on this problem. the usb icon at the bottom of the screen does say eject nexus 7 when I click on it, and if I have usb debugging turned on it says ADB device connected but I still can not see it anywhere on the pc. Please help

Are you running stock or custom ROM?
If you running stock, you can try disabling USB debugging or try this:
http://forum.xda-developers.com/showthread.php?t=2391236
If you are on custom ROM, it appears there may be an MTP issue with some ROMs.

Yes I am using the stock rom .all I did was root it and I have tried with no success with usb debugging turn Off as well. I have even tried to uninstall the drivers I used to root the tablet , but can not find them to uninstall or delete them

In devmgmt.msc the device is either listed under
Android Phone
Imaging device
Portable device
Unknown
Do you see any ? or unknown devices?

In Devices and Printers in the control panel its listed under Unspecified as Nexus 7 but you can not do anything with it there but right click on it and hit eject or properties and it says Google Nexus ADB interface ___ Android Device ___ status working properly and that's it .In Device manager it listed as Android Device ___ Google Nexus ADB Interface.
I Got it Thank you Thank you. I was able to uninstall the drivers there in the Device manager, unpluged the Nexus 7 plugged it back in it install the correct drivers and I am now able to mount my device as a MTP device and transfer files. Thanks again for the Help.

I put Android File Transfer on my Macs:
http://www.android.com/filetransfer/
and gmtp on My Ubuntu Ultrabook, and on my old Xubuntu desktop.
I put the SD card in the Ultrabook, and copied everything I wanted to the N7(2013).
In all cases, it worked pretty much plug and play, but I still consider it a work-around.

[Q] usb/debugging not found

I've been running CyanogenMod 10.2 on my rooted HTC One for a good long while now. Since the ROM worked so well, I never had the need to connect the phone to a computer via USB in quite some time. A few months ago, when I attempted to transfer some photos, I ran into a weird and frustrating road block; my phone is simply not being recognized by any computer <see here>
I have updated all drivers
I have enabled debugging in Developer Options
I have tried rebooting Fastboot in bootloader
I have tried using the toolkits
I have tried everything I think I know
The weird part is that the phone charges via USB connected to the computer.
Since it didn't effect much, I just figured it was a glitch and I never ran into a problem again--that is, until today. I hadn't used my MHL adapter with the HTC One (only my GNexus), but after reviewing an intended installation of a Pioneer Appradio, I wanted to ensure that my One would work with the MHL. Hooking up my One to the Samsung MHL adapter (and power supply of course), I get no display on my television.
I am now beginning to wonder if the USB port is damaged. Visual inspection doesn't reveal anything, but I am curious if anyone has had this problem and would appreciate any help. Is there any way to test if I've fouled up the port?

Does the phone recognize that it is connected to a pc? Can you access the phones storage from your pc?

cmlusco said:
Does the phone recognize that it is connected to a pc? Can you access the phones storage from your pc?
Click to expand...
Click to collapse
No and no

I installed Flashify and did install CWM 6.0.4.7 to see if it would help, but to no avail

Have you tried adb with a different rom or stock via ruu? If it still dosent work then, either your usb port or your cable is messed up.

cmlusco said:
Have you tried adb with a different rom or stock via ruu? If it still dosent work then, either your usb port or your cable is messed up.
Click to expand...
Click to collapse
I have tried adb, but the device never is recognized.
I'm currenty transferring my TWRP backup via WiFi.
I planned on switching to CM11 and see if I can't get it to work after that.

[GUIDE] How to flash recovery image Nvidia Shield TV using FASTBOOT hardware method

All of the instructions I found for doing this weren't exactly clear, so I'm writing this out in a way that even dummies like me can understand. So, my Nvidia Shield TV got soft bricked when I tried to update my TWRP to this version.
First, you have two options for the cables:
This: http://www.monoprice.com/Product?p_id=9724
and this: http://www.monoprice.com/product?p_id=5443
Plug them into each other so they're just 1 cable now.
The second option is to use a USB to micro USB data/charging cable, like the one that it came with.
Here are the steps, read it completely through 1 time before doing anything. I find that makes things easier to understand when you're ready to actually do it.
Install FASTBOOT DRIVERS: https://developer.nvidia.com/gameworksdownload#?search=SHIELD Family Windows USB
Install Minimal FASTBOOT & ADB: http://forum.xda-developers.com/showthread.php?t=2317790
Download OS Image: https://developer.nvidia.com/gameworksdownload
Extract the OS Image to your desktop.
Go to the installation folder for Minimal FASTBOOT & ADB and copy its contents into the OS Image folder you just created.
Open a Windows command prompt in this folder.
Make sure power cable & USB OTG cable on NSATV are UNPLUGGED.
Make sure HDMI cable is PLUGGED IN.
Plug the standard USB end of the USB OTG cable pair into a PC.
*** DO THE STEPS BELOW IN THE EXACT ORDER ***
Plug in USB OTG end of the USB OTG cable pair into NSATV.
Plug in the power cable. The next step follows quick.
Quickly touch and hold the power button until the FASTBOOT screen appears on your TV, then release.
Now, go back to your PC.
In the Windows command prompt, type: fastboot devices
Make sure the fastboot device appears.
If you see your fastboot device, then you can follow the instructions in the HowTo-Flash-Recovery-Image.txt file.
I hope this helps. If there's any part that's confusing, let me know and I'll edit it.

Yeah, you guys are awsome, it worked!!!!!
Thanks so much for all your help and advice :good:

You could also just use the charge cable that you get for your controllers rather than buying the extra cables, it works fine.
Sent from my HTC One M9 using Tapatalk

gffmac said:
You could also just use the charge cable that you get for your controllers rather than buying the extra cables, it works fine.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
It doesn't need an OTG cable?

Nope, using the supplied cable just connect the micro usb end to shield other to PC and bobs your uncle ?
Sent from my HTC One M9 using Tapatalk

any idea if this will work for my shield 16GB? since i was updating it to 3.0 this morning and the electric went now all it does it boot right to TWRP recovery. also i still have access to fastboot.

beefy143 said:
any idea if this will work for my shield 16GB? since i was updating it to 3.0 this morning and the electric went now all it does it boot right to TWRP recovery. also i still have access to fastboot.
Click to expand...
Click to collapse
It should?

tried and no it does not just left at the nvidia boot creen with the odd black screen reboot back to the nvidia symbol any ideas as to what i can do to fix my shield?

beefy143 said:
tried and no it does not just left at the nvidia boot creen with the odd black screen reboot back to the nvidia symbol any ideas as to what i can do to fix my shield?
Click to expand...
Click to collapse
Follow the instructions EXACTLY. I have the 16Gb model and mine was doing the same thing as yours.

Just to repeat what others said the back of the shield TV has a microusb port so you don't need a otg cable just use any standard microusb cable you have laying around plug small end into shield TV and big end to laptop/computer

Hi!
I tried but failed. The issue is, that it reboots directly after showing the recovery menu.
Only see it 2 seconds, then reboot. No reaction on menu choices...
I guess it happened when I tried to copy the SD card to another one.

You should be using fast boot to do this. Plus, there's no SD card in the instructions. Not sure what you are trying to do.

JoCamel said:
Hi!
I tried but failed. The issue is, that it reboots directly after showing the recovery menu.
Only see it 2 seconds, then reboot. No reaction on menu choices...
I guess it happened when I tried to copy the SD card to another one.
Click to expand...
Click to collapse
Try again without an sd card attached maybe. Also try 'fastboot boot recovery.img' instead of flashing it.

Neo3D said:
[*]In the Windows command prompt, type: fastboot devices
[*]Make sure the fastboot device appears.
[*]If you see your fastboot device, then you can follow the instructions
Click to expand...
Click to collapse
Hi
All fine up to that point... Fastboot Devices... nothing shows up!
? anyone?
My box is stock, I have not messed with it at all.

if i not enable debug? how to do?

fredphoesh said:
Hi
All fine up to that point... Fastboot Devices... nothing shows up!
? anyone?
My box is stock, I have not messed with it at all.
Click to expand...
Click to collapse
Could be a driver issue? Make sure the drivers are properly installed and working? Try rebooting?

Will these steps work with the 2017 16GB version? Cause I want to have full Android on the Shield but the processes I've seen are pretty confusing.

I want to try this, will this work with the new 5.2 update?

Jabadabaduu!! It solved my problem
Hey Neo
First of all, your guide saved my day! - Thanx!
I know this must be a strange question, but is the person on your XDA profile picture, and the one that has written the article really the same person ?

Neo3D said:
All of the instructions I found for doing this weren't exactly clear, so I'm writing this out in a way that even dummies like me can understand. So, my Nvidia Shield TV got soft bricked when I tried to update my TWRP to this version.
First, you have two options for the cables:
This: http://www.monoprice.com/Product?p_id=9724
and this: http://www.monoprice.com/product?p_id=5443
Plug them into each other so they're just 1 cable now.
The second option is to use a USB to micro USB data/charging cable, like the one that it came with.
Here are the steps, read it completely through 1 time before doing anything. I find that makes things easier to understand when you're ready to actually do it.
Install FASTBOOT DRIVERS: https://developer.nvidia.com/gameworksdownload#?search=SHIELD Family Windows USB
Install Minimal FASTBOOT & ADB: http://forum.xda-developers.com/showthread.php?t=2317790
Download OS Image: https://developer.nvidia.com/gameworksdownload
Extract the OS Image to your desktop.
Go to the installation folder for Minimal FASTBOOT & ADB and copy its contents into the OS Image folder you just created.
Open a Windows command prompt in this folder.
Make sure power cable & USB OTG cable on NSATV are UNPLUGGED.
Make sure HDMI cable is PLUGGED IN.
Plug the standard USB end of the USB OTG cable pair into a PC.
*** DO THE STEPS BELOW IN THE EXACT ORDER ***
Plug in USB OTG end of the USB OTG cable pair into NSATV.
Plug in the power cable. The next step follows quick.
Quickly touch and hold the power button until the FASTBOOT screen appears on your TV, then release.
Now, go back to your PC.
In the Windows command prompt, type: fastboot devices
Make sure the fastboot device appears.
If you see your fastboot device, then you can follow the instructions in the HowTo-Flash-Recovery-Image.txt file.
I hope this helps. If there's any part that's confusing, let me know and I'll edit it.
Click to expand...
Click to collapse
Awesome, works like a charm

Unable to enable USB File Transfer or connect with ADB.

I'm on DP3 and had flashed elementalx with temp TWRP. Now I am unable to get file transfer nor ADB to pull up on my phone. I'm unable to upgrade to DP4 due to custom kernel, and can't use ADB to restore boot.

taylor310 said:
I'm on DP3 and had flashed elementalx with temp TWRP. Now I am unable to get file transfer nor ADB to pull up on my phone. I'm unable to upgrade to DP4 due to custom kernel, and can't use ADB to restore boot.
Click to expand...
Click to collapse
Try different USB A to USB C cables and ports for starters, and make sure your platform-tools are up to date. You may have to factory reset to get pc to phone connection. And even then there are no guarantees. ?

I was able to get it working. I turned of USB debugging and back on and now it connected.
Phew!

taylor310 said:
I was able to get it working. I turned of USB debugging and back on and now it connected.
Phew!
Click to expand...
Click to collapse
Oh nice! There's another possible solution to the ever growing list of....OH CRAP! My pc isn't recognizing my device anymore!

[solved] Recover Data: Touchscreen doesn't respond, fastboot only, Stock Android One

Hey gals and guys,
my girlfriend dropped her Xiaomi A2 lite and no the touchscreen doesn't respond. The phone has the stock Android One and I can only access fastboot.
Code:
fastboot devices
recognizes the phone.
The recovery is the stock recovery.
Code:
adb devices
won't recognize the phone and gives me an empty line as output
I also can't access the phone via usb with my filebrowser. If I try, the phone makes a "bing"-sound and the filebrowser gives me:
Code:
unable to open MTP device
I am using archlinux and I also have a windows device available.
Is there any chance on getting pictures etc from the phone?
Any suggestions besides getting a replacement for the touchscreen?
Thank you so much.

Connecting via USB probably needs you to click something.
I'm guessing developer mode is not enabled...
If you've got a micro USB OTG cable, you could plug a mouse in.
If you boot TWRP (fastboot boot twrp-3.3.1-dees-troy.img) you should be able to get adb and usb transfers working. Don't need to install it, just boot it. Not sure if that works without unlocked bootloader.

If you've got a micro USB OTG cable, you could plug a mouse in.
Click to expand...
Click to collapse
This did the trick.
Thank you