Develop Bugs

[Q] Custom ROM that allows adb debugging?

Hi,
I develop Android app, last time i tried, some custom ROMs disable debugging via eclipse and adb.
What ROMs are recommended for a developer like me?
Thanks

kenyi25 said:
Hi,
I develop Android app, last time i tried, some custom ROMs disable debugging via eclipse and adb.
What ROMs are recommended for a developer like me?
Thanks
Click to expand...
Click to collapse
I have been pulling my hair out trying to figure out why I can no longer connect to my Desire HD via eclipse since I rooted my phone two days ago and installed the virtuous unity rom. It connects temporarily then gives the following errors:
Code:
[2011-06-29 23:23:44 - adb]This application has requested the Runtime to terminate it in an unusual way.
[2011-06-29 23:23:44 - adb]Please contact the application's support team for more information.
[2011-06-29 23:23:44 - DeviceMonitor]Adb connection Error:An existing connection was forcibly closed by the remote host
I can open up a shell and type commands on the device, but the debugging doesn't work. When you google these errors it is usually people not having enabled usb debugging on their phone. I have of course done this.
I spent a large amount of time uninstalling droid explorer and moving adb.exe and adbwinapi.dll's around today trying to fix this issue before realising it's the phone not the PC.
I took my wifes HTC ChaCha with stock ROM, connected it and it works fine in eclipse, same cable, just different phone.
I can't believe as this poster suggests that this is standard with custom ROMs.
I tried the leedroid sense 3 ROM but this too had the same issue. Each time I did a full wipe before installing the ROM, and I installed nothing on the phone before testing.
Whats going on?

Phew, finally somebody with the same issue. Could somebody try Raidroid 1.32.405.6 to see if it works then?
Sent from my Desire HD using Tapatalk

jkoljo said:
Phew, finally somebody with the same issue. Could somebody try Raidroid 1.32.405.6 to see if it works then?
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Hi jkoljo,
Thanks for the suggestion. I tried Raidroid 1.32.405.6, but unfortunately I had exactly the same issue.
I also tried the suggestions in the following thread which suggested setting persist.service.adb.enable=0 in default.prop, but this didn't work either.
http://forum.xda-developers.com/showthread.php?t=1051798&highlight=adb
Any other ideas? I'm willing to try anything you can suggest. It's really weird that even with an almost stock ROM the issue is still there...

CheesyPeteza said:
It's really weird that even with an almost stock ROM the issue is still there...
Click to expand...
Click to collapse
Exactly. There is basically no additional mods in raidroid, only root. Does it have unsecured boot.img? So if you go to terminal emulator (get it from market), does it open up with $ or #?

It starts with $, but if I sudo to root I get the superuser app requesting permission then I get root with the # prompt.
I thougt that was the way it was supposed to work, should I be going straight in as root? Should I uninstall the superuser app?

OK. With everything else ruled out clutching at straws I tried taking the sdcard out and it started working!
I put the sdcard back in and immediately it stopped working.
So it's something to do with the sdcard...
This should be solvable through a process of elimination.
I need to go to bed now, but tomorrow I'll try a spare completely blank sdcard and start the elimination process from that. Hopefully it is just a file on the sdcard causing the problem, not the presence of an sdcard itself.

I spoke to soon, looks like I just got lucky and it happened to work when I took the sdcard out. Occasionally it will work for a minute then it will stop working again. I'm no closer to solving this.

Same issue
I have installed custom ROM on my SPICE MI 270 and it does not connect to ADB. Though it showed only once in the "list of devices" but thereafter i have never been able to connect it. Please help.

ajparag said:
I have installed custom ROM on my SPICE MI 270 and it does not connect to ADB. Though it showed only once in the "list of devices" but thereafter i have never been able to connect it. Please help.
Click to expand...
Click to collapse
Unfortunately, you're in the Desire HD forums, so it's hard to help you when you're using different hardware. For all I know, the Spice MI could have known ADB connection problems. I would recommend finding forums specific to your hardware.

Trying to Root - Driver install issue

I've literally tried every method on the internet to root the GSM Galaxy Nexus and I keep getting stuck at the very beginning: I can't get past the driver step and making sure the computer recognizes the phone as an ADB device. I've tried Samsung driver install, pdaNET drivers and just about any other method and I still can't get my computer to show that the device is a ADB device and therefore cannot root the phone.
Its a Play Store Galaxy Nexus running 4.0.4
all help is incredibly appreciated. I've been working on this problem since Friday.
I'm on a 64bit Windows 7 on a Dell XPS 15 computer

Jubakuba said:
If your Command Prompt displays the message "waiting for device" your driver wasn't successfully installed.
Close the Command Prompt window and open Device manager while your phone is still plugged in. (Search for it using the search option).
Right Click the "Android" option and select Update Driver. Choose to "Browse My Computer" and "Let Me Pick From A List." Pick the Samsung driver with the newest date and install it. Now retry the code above.
Click to expand...
Click to collapse
Try this.

I've tried updating via device manager. The problem is, it always says its up to date or when I manually select one it still doesn't work. Should I just not pick the newest driver? Pick an older version when selecting a new driver?
EDIT: also, another issue is that with Wug's when it searches for the adb device is searches in an odd folder that doesn't exist and I can't figure out how to change where it looks
Sent from my Galaxy Nexus using xda app-developers app

Or download the GNex Toolkit. Was having driver issues as well today (they were installed but for some strange reason Windows didn't recognize it anymore) and used the ones that come with this toolkit to reinstall through device manager. Of course as always with these things, use at your own risk, fiddling with drivers can be tricky .

What are you getting from your adb devices command? I had a problem with mine showing as consistantly offline. I had to change from a frontal USB port (usually a bad idea anyway) to a rear port. Some device/computer combinations make adb unhappy when using a USB hub, which most frontal USB ports essentially are.

Cilraaz said:
What are you getting from your adb devices command? I had a problem with mine showing as consistantly offline. I had to change from a frontal USB port (usually a bad idea anyway) to a rear port. Some device/computer combinations make adb unhappy when using a USB hub, which most frontal USB ports essentially are.
Click to expand...
Click to collapse
When I use WugFresh and check for ADB it checks a nonexistent directory and returns an error. I found another method on google (I think the webpage was Foolproof method or something) and I check through command prompt and when I do it says List of Devices: then a blank line underneath
EDIT: just installed the GNex toolkit and drivers, plugged in, adb devices and it returned the blank line
EDIT 2.0: I just witnessed the most beautiful thing in the world. I plugged in again and it miraculously worked. I think I might tear up and cry a little

Yeah, for some reason the USB Driver in the Android SDK does NOT work. This was incredibly frustrating when I was trying to unlock my phone originally. I spent probably 30 minutes googling and trying different driver downloads.
I have attached the ones I used that DO work.

So here is the new story:
unlocked bootloader but it did not factory reset. It rebooted and my phone is as it was.
When I went to do fastboot boot boot.gsm.img, It says boot.img downloads and then it takes me to the google logo screen and gets stuck

The 4th Derivative said:
So here is the new story:
unlocked bootloader but it did not factory reset. It rebooted and my phone is as it was.
When I went to do fastboot boot boot.gsm.img, It says boot.img downloads and then it takes me to the google logo screen and gets stuck
Click to expand...
Click to collapse
I've never rooted an already installed ROM for the Galaxy Nexus, but might I ask why you're not just installing a pre-rooted ROM from recovery? It'll save you a lot of headaches for sure. Even if you're not into custom builds, there's plenty of AOSP pre-rooted builds out there

Gunthy` said:
I've never rooted an already installed ROM for the Galaxy Nexus, but might I ask why you're not just installing a pre-rooted ROM from recovery? It'll save you a lot of headaches for sure. Even if you're not into custom builds, there's plenty of AOSP pre-rooted builds out there
Click to expand...
Click to collapse
I don't think the pre-rooted ROMs get OTAs, or do they? I've been trying to root on stock so I can still get OTAs and I like how stable it is. I've messed with other ROMs on other phones and I almost always go to stock or CM but I'd rather stick to stock on this for now

Okay I can understand that. However do realize that once you install an OTA, your root will probably be gone and you'll have to root manually once more ...

i actually delete any driver and use the pdanet works just fine, i had the same problem that you. is just mather of patience.

Gunthy` said:
Okay I can understand that. However do realize that once you install an OTA, your root will probably be gone and you'll have to root manually once more ...
Click to expand...
Click to collapse
Yea re-rooting is fine. I really only need root for a few days to get my phone set up but K really don't need root privileges in everyday use so losing root once I've done what I need is ok

Gunthy` said:
Okay I can understand that. However do realize that once you install an OTA, your root will probably be gone and you'll have to root manually once more ...
Click to expand...
Click to collapse
Maybe not. SuperSU has a feature to keep root when installing an OTA.
The 4th Derivative said:
Yea re-rooting is fine. I really only need root for a few days to get my phone set up but K really don't need root privileges in everyday use so losing root once I've done what I need is ok
Click to expand...
Click to collapse
Man.. as easy as this:
Go to bixie's jb rom thread, he has there linked a supersu+busybox cwm flashable zip, dl that and copy it to the device. Dl also a non-touch cwm image.
Unlock your bootloader, bla bla follow guides on how to set up/use fastboot, BOOT cwm (not flash it) with 'fastboot boot cwm.img', flash that supersu zip, reboot. Done, you rooted jb, install voodoo root keeper or something, back up root. Thats one way how to root a Nexus. You can even relock your bootloader after you finished customizing.
Sent from my i9250

Sorry guys, forgot to post last night. I finally got root. Thanks to all who helped! You all made my life so much easier

The 4th Derivative said:
Sorry guys, forgot to post last night. I finally got root. Thanks to all who helped! You all made my life so much easier
Click to expand...
Click to collapse
hey, i have the same problem as you do on updating the usb driver. mind telling me how you do it? thanks!

I put it in a different USB port (my sata+ if it matters) and found a method online. I cant remember where on mobile but I'll look it up once I'm home
Sent from my Galaxy Nexus

The 4th Derivative said:
I put it in a different USB port (my sata+ if it matters) and found a method online. I cant remember where on mobile but I'll look it up once I'm home
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
its okay already. i have found the solution. thanks

The 4th Derivative said:
So here is the new story:
unlocked bootloader but it did not factory reset. It rebooted and my phone is as it was.
When I went to do fastboot boot boot.gsm.img, It says boot.img downloads and then it takes me to the google logo screen and gets stuck
Click to expand...
Click to collapse
EDIT

USB doesn't work

I have problem with my USB port, when I plug my phone to PC, it is not recognized, even in the fastboot mode it says only fasboot no usb fastboot, and that is the main issue because I am not able to flash kernel or RELOCK phone and try revert it back to stock ROM. Only in HBOOT my computer detect my device but as Unknown device... It's some kind of brick or something ? :crying:

get the latest drivers.
Sent from my HTC One V using xda app-developers app

mihirengg19 said:
get the latest drivers.
Sent from my HTC One V using xda app-developers app
Click to expand...
Click to collapse
I have them and I tried connect my phone to other computers too, but nothing changed.

Do one thing.
1 connect phone to computer.
2. cd to your fastboot/adb folder.
3. Type
adb devices.
Reply
Sent from my One V using xda app-developers app

He has unlocked bootloader that means he has already setup the environment adb+fastboot.
Sent from my HTC One V using xda app-developers app

Yes, with my old Desire everithing works just fine, but with OneV... nothing.
Is there any other way how to flash new kernel ? Something like using right name of zip and flash it in Hboot ? Is that possible ?

mihirengg19 said:
He has unlocked bootloader that means he has already setup the environment adb+fastboot.
Sent from my HTC One V using xda app-developers app
Click to expand...
Click to collapse
Yes point..
But still can you tell what shows under adb devices?
Sent from my One V using xda app-developers app

soham_sss said:
Yes point..
But still can you tell what shows under adb devices?
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
This:
C:\Users\------>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
C:\Users\----->

'adb server is out of date' just happened to me out of nowhere.but I am able to use fastboot and adb commands.check if u have ticked fastboot or not in settings-power.
Does it say error:device offline?
That happened to me yesterday bcos apparently I had checked off fastboot.when I ticked it,device was recognised.
Sent from my HTC One V using xda app-developers app

anydors said:
This:
C:\Users\------>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
C:\Users\----->
Click to expand...
Click to collapse
Huh? Before starting adb try this
adb kill-server
Then adb devices
Report.
Also which Rom are you now on?
Have you checked if android debugging in settings>developer options is enabled?
Sent from my HTC One V using xda app-developers app

mihirengg19 said:
'adb server is out of date' just happened to me out of nowhere.but I am able to use fastboot and adb commands.check if u have ticked fastboot or not in settings-power.
Does it say error:device offline?
That happened to me yesterday bcos apparently I had checked off fastboot.when I ticked it,device was recognised.
Sent from my HTC One V using xda app-developers app
Click to expand...
Click to collapse
Where exactly I can find this because there is nothing like that in my settings.
soham_sss said:
Huh? Before starting adb try this
adb kill-server
Then adb devices
Report.
Also which Rom are you now on?
Have you checked if android debugging in settings>developer options is enabled?
Sent from my HTC One V using xda app-developers app
Click to expand...
Click to collapse
C:\Users\------>adb kill-server
C:\Users\----->adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\Users\----->cd C:\ADB\android-sdk-windows\tools
C:\ADB\android-sdk-windows\tools>adb devices
List of devices attached
C:\ADB\android-sdk-windows\tools>
I have in my phone Ujelly from Lloir,
yes I have it enabled.

Check your PC device manager, is it My HTC listed under android USB Devices ?
Also check who is the Driver provider, date, version under My HTC Properties

I'm having a similar problem as the OP I think...
I don't remember the exact sequence of everything I've done so far, but here's a brief overview:
(Bought a GSM carrier unlocked One V on eBay)
Used Hasoon2000's All-in-One Toolkit to unlock bootloader (confirmed with the *** UNLOCKED *** line in the bootloader, whereas beforehand it said locked instead)
Used the AIO Toolkit to flash TWRP 2.3.3.0
Tried to use ROM Manager app to flash PACman 20.1, didn't work
Used TWRP to backup ROM, wiped everything, installed PACman 20.1, rebooted
After being stuck on white HTC boot screen, wiped everything again, went through same process as above but flashed kernel this time using AIO Toolkit before rebooting
The result was the white HTC boot screen with red developer warning text that I'm sure you've read about elsewhere, but the phone would not fully boot
I went through this process at least a few more times with the same result every time
The next thing I was going to try to do was manually flash the kernel, but when in the bootloader, my phone isn't detected by my computer (there's literally no entry in Device Manager for any sort of device). I'm running Windows 8 and I've installed HTC Sync and everything else necessary according to several tutorials (but make sure it's closed when trying to do stuff with Command Prompt). There were some issues with my computer detecting my phone when I was initially doing stuff in the bootloader with the AIO Toolkit (when stock 4.0 ICS was still on my phone), but I think it was because I had the data cable plugged into USB 3.0, because when I plugged it into the 2.0 port, the AIO Toolkit was able to do it's thing. I'm not sure if my phone is bricked or not, but for some reason my original ROM backup is gone, as when I try to restore through TWRP, there's no file/folder there to use.
I would just manually re-flash the stock ROM at this point, but due to the fact that my phone isn't detected at all in the bootloader, I can't run anything in Command Prompt and have it actually do anything (for example, when I type in "FASTBOOT DEVICES," nothing is returned except for a blank line).
Sorry for any incorrect terminology here, but I'm a fairly beginner-level guy. Normally, though, I can easily follow tutorials and have successfully rooted a few phones in the past... for some reason the One V is just giving me a bit of trouble. Any help anyone could provide would be greatly appreciated. Thanks in advance!
EDIT: Actually, I just realized that under Devices and Printers, there is a device called "Android 1.0" that is malfunctioning, but there is no way to update the driver for it.
EDIT 2: Over the past half hour or 45 minutes, I've been searching a bunch of other forums, and I tried flashing the ROM again (but get a bootloop), and the conclusion I've come to is that I've done everything correctly, but I simply need to flash a Hellboy kernel to get it to actually boot. But, since I can't connect via USB, I don't know how to flash it...

R: USB doesn't work
@tmacfan
When that happens you should boot into fastboot and connect your phone, go to device manager and there will be a malfunctioning device, locate the driver manually Wich is in htc sync folder. If it can't find the driver, copy it to the desktop (the whole folder, not just the driver) and try to locate it there
Sent from my HTC One V using xda app-developers app

mr_nooby said:
@tmacfan
When that happens you should boot into fastboot and connect your phone, go to device manager and there will be a malfunctioning device, locate the driver manually Wich is in htc sync folder. If it can't find the driver, copy it to the desktop (the whole folder, not just the driver) and try to locate it there
Sent from my HTC One V using xda app-developers app
Click to expand...
Click to collapse
Thanks for the advice, but the problem is that no device appears in the Device Manager. Under the Devices and Printers, there is one, but I don't think there are the usual options of manually locating the driver. Any idea on that?

R: USB doesn't work
Yes you can manually locate it. You said there is a android malfunctioning, click on its properties, update driver, you should be able to choose whether you want to look in the Internet for a driver or locate it from your pc.
Sent from my HTC One V using xda app-developers app

mr_nooby said:
Yes you can manually locate it. You said there is a android malfunctioning, click on its properties, update driver, you should be able to choose whether you want to look in the Internet for a driver or locate it from your pc.
Sent from my HTC One V using xda app-developers app
Click to expand...
Click to collapse
Okay yeah, thanks, I actually figured out how to do it yesterday. For some reason, the malfunctioning device wasn't showing up under Device Manager, but it was under Devices and Printers, and as you said, I could click on properties there and go through the same procedure. Thanks.
Also, locating the driver manually like that fixed the problem, and I was able to flash the needed kernel. For some reason, I couldn't get PACman to work (I'm 98% sure I had everything correct, including kernel and everything), but on my first attempt of flashing CM10, I was able to get that to work, so that's the ROM I'm running right now.
Thanks for taking the time to help me out!

R: USB doesn't work
tmacfan532 said:
Okay yeah, thanks, I actually figured out how to do it yesterday. For some reason, the malfunctioning device wasn't showing up under Device Manager, but it was under Devices and Printers, and as you said, I could click on properties there and go through the same procedure. Thanks.
Also, locating the driver manually like that fixed the problem, and I was able to flash the needed kernel. For some reason, I couldn't get PACman to work (I'm 98% sure I had everything correct, including kernel and everything), but on my first attempt of flashing CM10, I was able to get that to work, so that's the ROM I'm running right now.
Thanks for taking the time to help me out!
Click to expand...
Click to collapse
That's what we are here for
Sent from my HTC One V using xda app-developers app

cannot flash kernel, Doesnt become Fastboot usb
sohamssd said:
Do one thing.
1 connect phone to computer.
2. cd to your fastboot/adb folder.
3. Type
adb devices.
Reply
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
D:\Fastboot>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
emulator-5554 device

Nexus 7 wont connect to computer via MTP

When I connect my Nexus 7 to my windows 7 computer it is not recognized in MTP, but is when I change it to PTP. When I connect my 1st gen Nexus 7 to the same computer it is recognized fine and I am able to transfer files. I have all the drivers installed and adb works when I am in PTP I just cant transfer any files. Has anyone else experienced this problem or is there maybe something wrong with my Nexus?

Check out this thread. I was experiencing similar issues although I didn't test out PTP .
Sent from my Galaxy Nexus using xda app-developers app

Disregard. I figured it out. It was a driver issue after all.

How did you fix it? I have the same problem. Is root needed to view transfer files via USB?

My N7 2013 won't connect with my Macbook Pro. I already have the Android File Transfer app, which works fine with my Nexus 4, but it won't recognize the Nexus 7 2013. It charges, but no connection. Anyone have any ideas?

lucastmw said:
My N7 2013 won't connect with my Macbook Pro. I already have the Android File Transfer app, which works fine with my Nexus 4, but it won't recognize the Nexus 7 2013. It charges, but no connection. Anyone have any ideas?
Click to expand...
Click to collapse
Might be a silly question but did you enable USB debugging in developer tools.
Sent from my Galaxy Nexus using xda premium

jmileti said:
Might be a silly question but did you enable USB debugging in developer tools.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yes, I tried it with debugging on and off.

thaliagoo said:
How did you fix it? I have the same problem. Is root needed to view transfer files via USB?
Click to expand...
Click to collapse
Root is not needed to transfer files via USB. I just uninstalled the previous driver and updated to the latest and that worked for me.

No matter what, I always keep getting error code 10, device cannot be started when I install the new nexus 7 drivers Android ADB device (from the previous posts- Nexus 7 root). I'm not even trying to root, just trying to install drivers correctly.

thaliagoo said:
No matter what, I always keep getting error code 10, device cannot be started when I install the new nexus 7 drivers Android ADB device (from the previous posts- Nexus 7 root). I'm not even trying to root, just trying to install drivers correctly.
Click to expand...
Click to collapse
These are the drivers I used... http://developer.android.com/sdk/win-usb.html

fixed mine by just forcing it to reinstall the drivers.

fstbusa said:
fixed mine by just forcing it to reinstall the drivers.
Click to expand...
Click to collapse
How did you force it do that? I've actually never ran into this problem. Windows 8 is what I'm running.

dirtyfingers said:
These are the drivers I used... http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
It is definitely a driver issue. I had to uninstall my drivers and then manually install others, because I had a Nexus 7 2012. Those drivers were showing up as *up to date* according to windows, but the device was not working. Total clean install worked to correct it.

Xirix12 said:
How did you force it do that? I've actually never ran into this problem. Windows 8 is what I'm running.
Click to expand...
Click to collapse
In device manager, go to the properties of each android device. I had one near the top of the list and one lower under portable devices. Click update driver and navigate to your updated drivers folder.
It should update them. The device listed under portable devices had mtp as part of the title so I figured that one was the problem.
Sent from my Nexus 7 using xda app-developers app

To anybody who comes to this thread looking for help.
Go to device manager, and under devices remove the Google ADB Driver. This drove me nuts. All of my nexus devices wouldn't connect because they lacked an external SD.
Sent from my Nexus 7 using XDA Premium HD app

I've tried every suggestion in all of these threads so far & nothing worked. Even after I deleted the ADB drivers, windows 7 would automatically reinstall them. When I tried to update the drivers, win7 said they already had the best drivers (ADB).
Here's what worked for me:
I had to turn off USB debugging, delete the ADB drivers in Device Manager, then reboot the device while it's still plugged in. Windows recognized the device as an MTP device & installed the drivers before it even fully booted.

i installed the drivers from the link in this thread and still no luck, i am running the latest paranoid android rom, and tried it on 8 different computers with 23 different cables and no luck - would it help if i flashed a stock rom ? otherwise i dont know what to do - any help would be appreciated, thanks, chris
edit flashed a stock rom and now it is working again - came right up on my pc, i am selling it today to buy the 32gb and just wanted to get me twrp backups off it

golfinggino said:
i installed the drivers from the link in this thread and still no luck, i am running the latest paranoid android rom, and tried it on 8 different computers with 23 different cables and no luck - would it help if i flashed a stock rom ? otherwise i dont know what to do - any help would be appreciated, thanks, chris
edit flashed a stock rom and now it is working again - came right up on my pc, i am selling it today to buy the 32gb and just wanted to get me twrp backups off it
Click to expand...
Click to collapse
I have the same problem. When I was using stock ROM I could connect fine to my PC. When I installed CM10.2 I can not longer connect. i have no problem when I try it with my phone though.

huizingajm said:
I have the same problem. When I was using stock ROM I could connect fine to my PC. When I installed CM10.2 I can not longer connect. i have no problem when I try it with my phone though.
Click to expand...
Click to collapse
After helping someone with Paranoid ROM, I think the problem you are experiencing may be on the ROM/kernel side. Part of the problem is the custom ROM was sending out different USB IDs from stock. I was able to help them force the recognition of the MTP device from a driver standpoint on windows, but the MTP device wouldn't start up when windows tried to initialize it.

sfhub said:
After helping someone with Paranoid ROM, I think the problem you are experiencing may be on the ROM/kernel side. Part of the problem is the custom ROM was sending out different USB IDs from stock. I was able to help them force the recognition of the MTP device from a driver standpoint on windows, but the MTP device wouldn't start up when windows tried to initialize it.
Click to expand...
Click to collapse
I switched kernels to stock to jassy to tiny. None of them work so it has to be the ROM. I am just going to use WiFi transfer of files. Nothing major right now while everything is still new to 4.3.

[Q] Nexus 7 2013

hello. please help me, I do not know who to ask. at one point, my computer does not recognize the tablet. came out inscription unknown device. I tried to connect the tablet to other computers, all to no avail. then I made a factorial reset. that is completely erased tablet, in the hope that it will solve the problem. but he also failed to recognize. What shall I do?? I tried to connect via a USB flash drive OTG. but the tablet does not see any stick. I trust only your help

sergio1231 said:
hello. please help me, I do not know who to ask. at one point, my computer does not recognize the tablet. came out inscription unknown device. I tried to connect the tablet to other computers, all to no avail. then I made a factorial reset. that is completely erased tablet, in the hope that it will solve the problem. but he also failed to recognize. What shall I do?? I tried to connect via a USB flash drive OTG. but the tablet does not see any stick. I trust only your help
Click to expand...
Click to collapse
I have the same problem. I fixed it before on my nexus 10 by trying a different kernel. Let me me know if it helps.
Sent from my Nexus 7 using XDA Premium HD app

Do you have the correct drivers installed? If so, you could uninstall and reinstall them. Also, have you tried PTP connection rather than MTP?
Sent from my XT1080 using XDA Free mobile app

Jhall8 said:
Do you have the correct drivers installed? If so, you could uninstall and reinstall them. Also, have you tried PTP connection rather than MTP?
Sent from my XT1080 using XDA Free mobile app
Click to expand...
Click to collapse
Been there done that and have always eventually been able to get it back so the computer sees the device as mtp. Wugs toolkit has always been helpful
To me. I like the step by step directions for manually updating the drivers and configuring them correctly in adb AND fastboot.
Bit I have come to an impass..........I am currently on the latest carbon nightly, with f2fs file storage for data and cache. My computer will not recognize the device in mtp and I am unable to pass files with a USB cable. I am wondering if my computer has to be compatible with f2fs, because iam sure that it is not. Will this make a difference PR should I once again uninstall and reinstall the drivers configuring them correctly?
Sent from my Nexus 7 using XDA Premium 4 mobile app

1
I'm telling you that there is no firmware on the tablet. what do you advise.

sergio1231 said:
I'm telling you that there is no firmware on the tablet. what do you advise.
Click to expand...
Click to collapse
Plug it in to a computer.
Boot into recovery if you have one
Adb devices......hopefully it shows and work from there.
Or boot into bootloader mode (after getting the twrp IMG)
Fastboot flash recovery......
Then you can side load your favorite OS
Sent from my Nexus 7 using XDA Premium 4 mobile app

aircooledbusses said:
Been there done that and have always eventually been able to get it back so the computer sees the device as mtp. Wugs toolkit has always been helpful
To me. I like the step by step directions for manually updating the drivers and configuring them correctly in adb AND fastboot.
Bit I have come to an impass..........I am currently on the latest carbon nightly, with f2fs file storage for data and cache. My computer will not recognize the device in mtp and I am unable to pass files with a USB cable. I am wondering if my computer has to be compatible with f2fs, because iam sure that it is not. Will this make a difference PR should I once again uninstall and reinstall the drivers configuring them correctly?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
this worked for me im just passing along a possible fix http://forum.xda-developers.com/showthread.php?t=2383146&page=389 post #3888 is the one I followed and been no problems since. also cpl days before in my sdk program google had updated drivers which may or may not have played a roll. before this I could not pass files with mtp only ptp would allow my device to appear. hope it helps!
edit also should note I did device manager then android devices removed drivers in there. plugged in n7 and the adb composite interface drivers installed and that was it. if that doesn't do it make sure sdk has updated google driver which should be 10.0.0 or something don't quite remember exact #

jblaze10 said:
this worked for me im just passing along a possible fix http://forum.xda-developers.com/showthread.php?t=2383146&page=389 post #3888 is the one I followed and been no problems since. also cpl days before in my sdk program google had updated drivers which may or may not have played a roll. before this I could not pass files with mtp only ptp would allow my device to appear. hope it helps!
edit also should note I did device manager then android devices removed drivers in there. plugged in n7 and the adb composite interface drivers installed and that was it. if that doesn't do it make sure sdk has updated google driver which should be 10.0.0 or something don't quite remember exact #
Click to expand...
Click to collapse
Thanks jblaze. I've been able to function pretty well usind adb. Sort of glad cuz it forced me to learn some pretty essential stuff I have been getting along with for far too long.
Sent from my Nexus 7 using XDA Premium 4 mobile app

aircooledbusses said:
Thanks jblaze. I've been able to function pretty well usind adb. Sort of glad cuz it forced me to learn some pretty essential stuff I have been getting along with for far too long.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ur right, I wish I knew more about it. I'm in that phase now where I'm digging thru Xda for info such as adb backups among other things. Hey no prob, take it easy.
Sent from my Nexus 7 using Tapatalk