Develop Bugs

[Q] Code 43

I recently broke my HOX+ and got a GNex for my replacement. Whenever I try to connect it, using another cable (Nexus 7) because its stock cable did not come with the phone (used) I get that pop up which says "Unable to recognize device" or sometimes an error. Though on all events, I get something called Error 43.
Anyone know how to fix this? Ive tried fixing to usb port. It is all stock. I just want to connect so I can root this thing.

Mikeonic said:
I recently broke my HOX+ and got a GNex for my replacement. Whenever I try to connect it, using another cable (Nexus 7) because its stock cable did not come with the phone (used) I get that pop up which says "Unable to recognize device" or sometimes an error. Though on all events, I get something called Error 43.
Anyone know how to fix this? Ive tried fixing to usb port. It is all stock. I just want to connect so I can root this thing.
Click to expand...
Click to collapse
Try installing samsung mtp drivers..
Sent from my Galaxy Nexus

Ive tried
mixtapes08 said:
Try installing samsung mtp drivers..
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I have tried installing drivers...still nothing..

I do assume you're using windows?
And my apologies, are you getting this error message when you try to root?
Were these the MTP drivers you installed?
http://www.samsung.com/us/support/owners/product/SCH-I515MSAVZW

iLeopard said:
I do assume you're using windows?
And my apologies, are you getting this error message when you try to root?
Were these the MTP drivers you installed?
http://www.samsung.com/us/support/owners/product/SCH-I515MSAVZW
Click to expand...
Click to collapse
Yes, Windows 7. Those were the ones and I want to root, but I can't even connect my phone. I'll plug in my GNex and it will charge through the computer though it will not be recognized nor connected for storage purposes.

Mikeonic said:
Yes, Windows 7. Those were the ones and I want to root, but I can't even connect my phone. I'll plug in my GNex and it will charge through the computer though it will not be recognized nor connected for storage purposes.
Click to expand...
Click to collapse
One thing you may want to try if you havent yet:
My Computer -> Right Click -> Properties -> Device Manager (On Sidebar) -> Find the GNex Drivers currently installed and remove them and reinstall (Re-plug) your phone so that the drivers can re-install.
Is this a used or new replacement?

iLeopard said:
One thing you may want to try if you havent yet:
My Computer -> Right Click -> Properties -> Device Manager (On Sidebar) -> Find the GNex Drivers currently installed and remove them and reinstall (Re-plug) your phone so that the drivers can re-install.
Is this a used or new replacement?
Click to expand...
Click to collapse
Unfortunately, the device appears as Unknown Device. It was my Uncles and it was able to work for him. So it bothers me how its not for me. At times even, when I connect the USB to the Device, it causes my Computer to Shut Down abnormally. So, either something is wrong and I need to fix it...or this phone is haunted,

Mikeonic said:
Unfortunately, the device appears as Unknown Device. It was my Uncles and it was able to work for him. So it bothers me how its not for me. At times even, when I connect the USB to the Device, it causes my Computer to Shut Down abnormally. So, either something is wrong and I need to fix it...or this phone is haunted,
Click to expand...
Click to collapse
Even after deleting it?
Did he by chance have it rooted prior to the ownership change?
Is the result replicated in other computers? If you haven't tried, do so. That way you can eliminate either your PC or the GNex as the culprit.

iLeopard said:
Even after deleting it?
Did he by chance have it rooted prior to the ownership change?
Is the result replicated in other computers? If you haven't tried, do so. That way you can eliminate either your PC or the GNex as the culprit.
Click to expand...
Click to collapse
He was stock at all times. Though when I got it, it seemed to be freshly restored...but 5 minutes into using the phone, it froze and gave a fixed screen of something being flashed...though even after I factory restored it again...It wont connect to my All in One PC, Desktop or Laptop, every other device I own connects properly .

Mikeonic said:
He was stock at all times. Though when I got it, it seemed to be freshly restored...but 5 minutes into using the phone, it froze and gave a fixed screen of something being flashed...though even after I factory restored it again...It wont connect to my All in One PC, Desktop or Laptop, every other device I own connects properly .
Click to expand...
Click to collapse
Wierd. Did you try a reset through the stock recovery or just defaults from the security menu?
Here's what I've done. I've pulled my drivers and compressed them. Update the "Unknown Device" from the Device Manager by pointing it to the extracted DLL's and see if that will work.
Drivers

iLeopard said:
Wierd. Did you try a reset through the stock recovery or just defaults from the security menu?
Here's what I've done. I've pulled my drivers and compressed them. Update the "Unknown Device" from the Device Manager by pointing it to the extracted DLL's and see if that will work.
Drivers
Click to expand...
Click to collapse
Been trying and it wont let me push those files and when I do, I get Code Error 10

Mikeonic said:
Been trying and it wont let me push those files and when I do, I get Code Error 10
Click to expand...
Click to collapse
Pushing them? Sorry for my poor explanation. Those files you downloaded are my working drivers that I managed to pull from:
C:\Windows\system32\DRIVERS\UMDF
C:\Windows\system32\DRIVERS\
C:\Windows\system32\
All you have to do is press START -> Type "Device Manager" -> Select the "Unknown Device" -> Press "Update Driver" -> "Browse my computer for driver software" -> Hit "Browse" and point to the folder were the DLL's are located in your computer (Once you have decompressed the archive of course)

iLeopard said:
Pushing them? Sorry for my poor explanation. Those files you downloaded are my working drivers that I managed to pull from:
C:\Windows\system32\DRIVERS\UMDF
C:\Windows\system32\DRIVERS\
C:\Windows\system32\
All you have to do is press START -> Type "Device Manager" -> Select the "Unknown Device" -> Press "Update Driver" -> "Browse my computer for driver software" -> Hit "Browse" and point to the folder were the DLL's are located in your computer (Once you have decompressed the archive of course)
Click to expand...
Click to collapse
It says there are no files in the folder...

UPDATE
It says it FOUND Drivers though cannot execute actions due to error 43

Mikeonic said:
UPDATE
It says it FOUND Drivers though cannot execute actions due to error 43
Click to expand...
Click to collapse
Honestly, I'm stumped. The drivers should have installed correctly regardless. This leads me to believe that its the GN acting up. Again, when you did a reset on it; Did you do it from the Security Submenu or from the Stock Recovery?
Is the device recognized under fastboot? ADB usually works fine there.

iLeopard said:
Honestly, I'm stumped. The drivers should have installed correctly regardless. This leads me to believe that its the GN acting up. Again, when you did a reset on it; Did you do it from the Security Submenu or from the Stock Recovery?
Is the device recognized under fastboot? ADB usually works fine there.
Click to expand...
Click to collapse
It was through the Settings SubMenu, I'll try a Fast boot

Mikeonic said:
It was through the Settings SubMenu, I'll try a Fast boot
Click to expand...
Click to collapse
Also try a factory reset via Stock Recovery. You should find it under the Fastboot menu

iLeopard said:
Also try a factory reset via Stock Recovery. You should find it under the Fastboot menu
Click to expand...
Click to collapse
Still nothing....this is hopeless

Mikeonic said:
Still nothing....this is hopeless
Click to expand...
Click to collapse
Wow, I'm truly amazed how nothing seemed to work. I don't think 1-Click Temp-Root Methods work on the GN, in which case you would use the terminal to Perm-Root it.
This happens on all computers?
Tried Different USB ports?
Rebooting PC?

iLeopard said:
Wow, I'm truly amazed how nothing seemed to work. I don't think 1-Click Temp-Root Methods work on the GN, in which case you would use the terminal to Perm-Root it.
This happens on all computers?
Tried Different USB ports?
Rebooting PC?
Click to expand...
Click to collapse
I will try getting a new USB, maybe a stock if I can find and see if that works. Wish I could root without a USB...Thank You for your help. I will update if anything.

[Q] Problems in adb/fastboot

Hey all,
I've been rooting phones for a little bit, so when I got my Nexus 7 a couple weeks ago and found that it was as simple as "fastboot oem unlock", I was thrilled. However, it ended up not being that simple, of course.
At first I couldn't get the device to show up for ADB or fastboot at all, even though Windows recognized the device. I downloaded the zip file of the drivers from Google, no luck. Downloaded a new version of the Android SDK, and used the adb/fastboot from it, and then ADB was able to see the N7 and was able to reboot it into the bootloader. However, once in the bootloader, it stops recognizing that the N7 is connected again. Trying "fastboot oem unlock" just causes the program to display <waiting for device> indefinitely.
So that's where I'm stuck now, I haven't been able to find any concrete details on this that are for the N7 2013 (pretty much everything I've found has either not been helpful or has been related to the original N7). Anyone able to help from here? Thanks!

Do u have USB debugging enabled in developer settings? Try turning your USB computer connection to PTP from MTP if you haven't already in storage settings. Then a pop-up will come on your n7 asking to approve your computer to see it. Tell it yes
>^.^< Sent From Meow HTC One

DowntownJeffBrown said:
Do u have USB debugging enabled in developer settings? Try turning your USB computer connection to PTP from MTP if you haven't already in storage settings. Then a pop-up will come on your n7 asking to approve your computer to see it. Tell it yes
>^.^< Sent From Meow HTC One
Click to expand...
Click to collapse
Thanks for the suggestions. Alas, I tried these things. The problem exists now when I'm in the bootloader, which is where fastboot won't recognize that the device is attached.

tigerxchaos said:
Thanks for the suggestions. Alas, I tried these things. The problem exists now when I'm in the bootloader, which is where fastboot won't recognize that the device is attached.
Click to expand...
Click to collapse
When you have the device connected to your computer when it's at the Bootloader screen, what does Device Manager show on your computer? Does it recognize the tablet but doesn't know what it is? You may need to install the drivers when you have the device in the Bootloader menu. I use the Google USB Driver (which you can download in the SDK Manager), right click on the device in Device Manager, select "Update Driver Software", "Browse my computer for driver software", "Let me pick from a list of device drivers on my computer", then browse the list. It may be listed under Android Device, Google...just look down the list, then select the appropriate driver. I believe from there you can select "Android Bootloader Interface", and that should let fastboot commands work.
You may need to reboot the computer.

Make sure you are using the usb cable that came from asus.

Thanks for the help. I tried the process again on a different computer, and eventually got it to work. I was able to unlock bootloader and flash TWRP 2.6.3.0. However, I was only able to mount System, Cache, and USB-OTG as partitions in TWRP, so I couldn't figure out where to drop the SuperSU binary .zip file. I tried rebooting, and (this may have been a mistake) installed the TWRP SU binaries on the way out. Now the device is stuck in a bootloop. Not sure if it was related to the SU binaries or the fact that I couldn't load any sort of data partition. Any thoughts?
EDIT: Apparently the root instructions don't make it clear that you will lock your data partition if you don't boot the device after unlocking the bootloader. I went straight into TWRP from the bootloader after unlocking it, and got a password request. Hit "Cancel" and it let me into TWRP, but factory reset failed. I had to wipe data, wipe cache, then reboot, then do a factory reset and now I'm back in.

[Q] My computer not recognizing MTP AT ALL

Hey guys. I been here for like 4 hours just dabbling with everything. And cannot seem to find any solution to this...
I have uninstall all drivers and restarted like ten times now doing the same process over and over, cleaning up each file carefully of the nexus or any android device.
My problem is when i plug in my nexus 7 2nd gen, it seems to not even detect squat.
I have usb debug enabled
my MTP is on
( if i switch to PTP i can access the folder)
Ive done fresh start on everything i even look through device and try changing the option to MTP and STILL DOES not work
I don't even see my nexus 7 in my HDD external or anything, nothing pops up but an ADB success driver, and when i changed it to MTP a MTP success driver with STILL no luck....
I just bought it today and it worked fine earlier, now when i root it and stuff it seems to be glitchy with my MTP
I even factory reset everything i couldn't access my ADB
any help would be appreciated

Someone said that manually updating the adb usb driver in devices should show you a choice, choose mtp. It should then sort itself out properly.

n9900229 said:
Hey guys. I been here for like 4 hours just dabbling with everything. And cannot seem to find any solution to this...
I have uninstall all drivers and restarted like ten times now doing the same process over and over, cleaning up each file carefully of the nexus or any android device.
My problem is when i plug in my nexus 7 2nd gen, it seems to not even detect squat.
I have usb debug enabled
my MTP is on
( if i switch to PTP i can access the folder)
Ive done fresh start on everything i even look through device and try changing the option to MTP and STILL DOES not work
I don't even see my nexus 7 in my HDD external or anything, nothing pops up but an ADB success driver, and when i changed it to MTP a MTP success driver with STILL no luck....
I just bought it today and it worked fine earlier, now when i root it and stuff it seems to be glitchy with my MTP
I even factory reset everything i couldn't access my ADB
any help would be appreciated
Click to expand...
Click to collapse
On your Nexus, open "settings", click on "Storage", click on options(3 vertical dots on the top right corner), click on "USB PC Connection", now check MTP option.
Try connecting to your PC (or Mac) now. I didn't have to do that on a stock build, but for some reason I had to do it on a couple of custom roms. Hope it helps ya out...

Try enabling USB debugging. I know it sounds odd but its helped me with my devices.
Sent from my Nexus 7 using Tapatalk 4

do this only if you can see PTP on PC
On PC check device manger, on Android if there is ADB driver - uninstall it
On N7 set to MTP, debug off and reboot with N7 USB cable connected to PC
It should re-install the ABD drivers on PC before N7 fully boots up
You will be back in action.

n9900229 said:
I have usb debug enabled
my MTP is on
Click to expand...
Click to collapse
Actually for me, it's the opposite. If usb debugging is on I can't access the device to view files. Try disabling it?

yea thanks though everyone I got it to work. I had my old nexus and new drivers mixing up my ports for some reason not being able to access it at all

Device not detected.

Ok so I'm trying to flash L. All of my drivers are updated, I downloaded them again and installed just to be sure, but when I have my Nexus plugged in it still isn't detected, and yes USB debugging is on. I tried adb reboot bootloader and nothing, then I manually went into the bootloader and typed the flash-all command and it stayed stuck on waiting for device. Very frustrating, any help is appreciated.

C-4Nati said:
Ok so I'm trying to flash L. All of my drivers are updated, I downloaded them again and installed just to be sure, but when I have my Nexus plugged in it still isn't detected, and yes USB debugging is on. I tried adb reboot bootloader and nothing, then I manually went into the bootloader and typed the flash-all command and it stayed stuck on waiting for device. Very frustrating, any help is appreciated.
Click to expand...
Click to collapse
Try changing to PTP.
FWIW, I solved my driver issue this way. And mine works with ptp, mtp, debugging on or off.
You can also try using Koushs drivers, but it only is a half-measure fix.
Also sometimes you have to revoke usb auths, and unlock the device and look for the key fingerprint prompt when you first plug it into usb, and reaccept it.

mdamaged said:
Try changing to PTP.
FWIW, I solved my driver issue this way. And mine works with ptp, mtp, debugging on or off.
You can also try using Koushs drivers, but it only is a half-measure fix.
Also sometimes you have to revoke usb auths, and unlock the device and look for the key fingerprint prompt when you first plug it into usb, and reaccept it.
Click to expand...
Click to collapse
Didn't work, followed your steps in the other thread. I guess I'll just have to wait until a flashable zip for L :/
edit- And btw I tried it on both of my hard drives, one with windows 8 and one with windows 7, didn't work on either.

C-4Nati said:
Ok so I'm trying to flash L. All of my drivers are updated, I downloaded them again and installed just to be sure, but when I have my Nexus plugged in it still isn't detected, and yes USB debugging is on. I tried adb reboot bootloader and nothing, then I manually went into the bootloader and typed the flash-all command and it stayed stuck on waiting for device. Very frustrating, any help is appreciated.
Click to expand...
Click to collapse
These are the steps that I've used and have never had any problems with drivers. My brother had the same problem that your having a while back and these steps cleared up his driver problems. Maybe it's worth a shot.
First of all I NEVER let windows automatically install drivers except for a very short time period after a clean install of windows. It makes life easier if windows doesn't jump the gun and try to install what it thinks will work. I always get drivers directly from the manufacturer. After you stop windows from trying to do it's automatic driver install thing plug in your N7 to your computer and open device manager (I usually just type dev in the start search box of W7), find your device, right click and choose Uninstall, check the box for Delete the driver software for this device. When it finishes doing that reboot your computer and unplug your N7. Once your computer has completely booted back up plug in your N7 and open the device manager again. Find your N7 again, right click Update driver software then choose Browse my computer. Find your folder (including the subfolders) with the drivers and let it install, once it finishes unplug your N7 for a few seconds then plug it back in and hopefully it should be all good. If your want it I have a copy of the usb drivers at dropbox from my recently updated sdk install. I would just extract the folder and point the install to the whole folder, if you included subfolders at the install it will find what it needs inside the folder. Make sure you authorize your computer with usb debugging. Good luck! ; )

wantabe said:
These are the steps that I've used and have never had any problems with drivers. My brother had the same problem that your having a while back and these steps cleared up his driver problems. Maybe it's worth a shot.
First of all I NEVER let windows automatically install drivers except for a very short time period after a clean install of windows. It makes life easier if windows doesn't jump the gun and try to install what it thinks will work. I always get drivers directly from the manufacturer. After you stop windows from trying to do it's automatic driver install thing plug in your N7 to your computer and open device manager (I usually just type dev in the start search box of W7), find your device, right click and choose Uninstall, check the box for Delete the driver software for this device. When it finishes doing that reboot your computer and unplug your N7. Once your computer has completely booted back up plug in your N7 and open the device manager again. Find your N7 again, right click Update driver software then choose Browse my computer. Find your folder (including the subfolders) with the drivers and let it install, once it finishes unplug your N7 for a few seconds then plug it back in and hopefully it should be all good. If your want it I have a copy of the usb drivers at dropbox from my recently updated sdk install. I would just extract the folder and point the install to the whole folder, if you included subfolders at the install it will find what it needs inside the folder. Make sure you authorize your computer with usb debugging. Good luck! ; )
Click to expand...
Click to collapse
Thanks mate, didn't work though so I'm not sure what is going on. I'll just wait until zips get created but thanks for the help guys.

Broken Screen/Digitizer need backup

Dropped phone, broken screen/digitizer, doesn't respond to touch
Was able to see the screen a bit yesterday but now its almost all black. I mainly just need my photos off it. Tried an RMA to replace the screen but they said they had to wipe everything first
Is there any way I can pull the photos off it? I haven't tried an otg yet, but I also can't see the screen, so im not sure it would help
Is there a screen sharing program I could get w/o first installing it on my phone?
I think my phone may be rooted, i forget if i ever did, but i dont have TWRP installed on it? (i dont super know what that is but i see other people talking about it)
Any thoughts on how to pull photos off it? I tried the adb devices but the cmd prompt doesn't seem to recognize the phone
Im quite sure I have debugging enabled, just coudln't get the file transfer button hit

Adb pull command should work, but you need to sort the drivers first (I'm guessing that's the issue).
Sent from my OnePlus 3 using Tapatalk

Explorer23 said:
Adb pull command should work, but you need to sort the drivers first (I'm guessing that's the issue).
Sent from my OnePlus 3 using Tapatalk
Click to expand...
Click to collapse
Ok cool, how would i go about sorting the drivers? o.0

jsaden said:
Ok cool, how would i go about sorting the drivers? o.0
side note.... wth is this image verification lol, ive tried like 30 of them, why is it so hard to post lol ><
Click to expand...
Click to collapse
Sorry, can't give definite answer, I know that I had an issue with drivers (device wasn't properly recognized) and tried pretty much everything that Google suggested ... Until it finally started working. I have no idea exactly what solved the issue, it was over a year and a half ago. The next time I clean installed Windows (10 in both cases) it was smart enough to automatically find right drivers.
So ... I'm guessing Googling something like "OnePlus 3 Windows # drivers" should find something useful?
About image verification: are you talking about anti-bot system that checks if you're human? Wouldn't know much about that, never personally had issues with it, but also very rarely see it on XDA as I'm nearly always checking this forum in Tapatalk app.
Sent from my OnePlus 3 using Tapatalk

jsaden said:
Ok cool, how would i go about sorting the drivers? o.0
Click to expand...
Click to collapse
If you had earlier connected your phone to the PC and authorised the PC connection on your phone, then it is a simple issue of disabling driver signature verification on Win 10 and installing the OnePlus drivers on it. Search for and download the correct drivers to your PC. Hold down Shift key and restart the PC. Choose Troubeshoot>Advanced Options>Startup Options and click Restart. On restarting, there will be a list of options. Choose 7 in the Options or click F7 on your keyboard and you will boot into the disabled mode. Now connect your phone and go to Device Manager in PC. Choose the phone which may be showing up as Unknown or with an yellow flag and right click and choose Update Driver. Navigate to the downloaded driver and install it. Now your phone should be properly recognised. Use adb pull command to copy whatever files you need to. Note that this driver signature verification disabling is temporary and when you restart the PC in the normal way, the PC will go back to the normal mode. But the installed drivers will still function.
Hope this helps.

tnsmani said:
If you had earlier connected your phone to the PC and authorised the PC connection on your phone, then it is a simple issue of disabling driver signature verification on Win 10 and installing the OnePlus drivers on it. Search for and download the correct drivers to your PC. Hold down Shift key and restart the PC. Choose Troubeshoot>Advanced Options>Startup Options and click Restart. On restarting, there will be a list of options. Choose 7 in the Options or click F7 on your keyboard and you will boot into the disabled mode. Now connect your phone and go to Device Manager in PC. Choose the phone which may be showing up as Unknown or with an yellow flag and right click and choose Update Driver. Navigate to the downloaded driver and install it. Now your phone should be properly recognised. Use adb pull command to copy whatever files you need to. Note that this driver signature verification disabling is temporary and when you restart the PC in the normal way, the PC will go back to the normal mode. But the installed drivers will still function.
Hope this helps.
Click to expand...
Click to collapse
Oh wow, do you know if this works on Win7? And also I can't see my screen at all, so could I do adb pull of entire folder or hardrive kind of thing? I mainly just want phots, but i've never done adb stuff so not sure how it works

Had the same issue with my Lenovo P2. Only i didn't have debugging enabled. If you have, screen mirroring should be an easy solution. You could just see ur phone screen on ur computer that way. What helped me was to forceboot the phone to recovery with the hardware buttons, then connect it to ur pc. TWRP will automatically launch MTP. When u backed up evrything, you can wipe ur device through adb

jsaden said:
Oh wow, do you know if this works on Win7? And also I can't see my screen at all, so could I do adb pull of entire folder or hardrive kind of thing? I mainly just want phots, but i've never done adb stuff so not sure how it works
Click to expand...
Click to collapse
I don't know about Win 7. It will work on Win 10. Most likely, this should not be needed in Win 7 at all as the drivers should install whether signed or not.
Regarding copying data, a simple command of "adb pull /sdcard" will copy all the folders, files, data etc to your PC. You can also specify where you want the data copied to, simply add the path to the command above. This will work whether your screen works or not. Of course, there are other methods of copying data, you can search for it if you need it.