Database Develop

need help to access usb debugging

ok i am trying to get the phone to connect to usb debugging mod
i have already instaled cf lag fix which is done by usb debugging
now i want to uninstall it
so each time i connect the phone and start cflagfix it gives an error message and then says that i should check the phone and connect it
in the command prompet when i type the adb devices thingy i see my phone and the serial number
what am i doind wrong here ?
ps i was so angry that i flashed jm5 again with re partition
the lagfix effect is gone but is it really gone ??? or do i need to uninstall it ?

in windows check into Device Manager
and make sure there is no question mark or exclamation mark
my PC USB is crazy every now and then it will not know it's the same phone connected
so, perhaps your Windows might be suffering from something simple like that
another thing you can do is to connect it another PC / laptop and do your ADB tricks from there

[Q] Rooting KJ4 with zergrush doesn't work

Hey there,
i had LB2 (german version) on the n7000 before i bought it, so i flashed back to KJ4. But when i run the zergrush it's stuck at "--- WAITING FOR DEVICE".
In the device manager i have the gtn7000 as mtp device, the usb-debugging is turned on and unknown sources too. So what could be the problem now?
I had installed kies, but now i have deinstalled it and installed SAMSUNG_USB_Driver_for_Mobile_Phones_x86 but its still not working. Odin can see the device.
I am glad about any helpful comment !
Greetings
Okay odin doesn't see the device anymore :-/, so it could still be a problem with the driver?! Which driver should it be if i would like to select the driver manually? There are so many folders with inf files in it...

zentaury said:
Hey there,
i had LB2 (german version) on the n7000 before i bought it, so i flashed back to KJ4. But when i run the zergrush it's stuck at "--- WAITING FOR DEVICE".
In the device manager i have the gtn7000 as mtp device, the usb-debugging is turned on and unknown sources too. So what could be the problem now?
I had installed kies, but now i have deinstalled it and installed SAMSUNG_USB_Driver_for_Mobile_Phones_x86 but its still not working. Odin can see the device.
I am glad about any helpful comment !
Greetings
Okay odin doesn't see the device anymore :-/, so it could still be a problem with the driver?! Which driver should it be if i would like to select the driver manually? There are so many folders with inf files in it...
Click to expand...
Click to collapse
It is definitely a driver problem. Try to uninstall any drivers you have and reboot. Then download one of the drivers at the top of this page (Choose a 32- or 64-bit Windows drivers, I don't know which one you've got). Reboot again after installation. Connect your Note to one of the USB slots at the back of your PC - not at the front or at the side - wait for Windows to install additional drivers (5 or 6 of them) and try again.

Now i am getting till:
* daemon not running. starting it now *
* daemon started successfully *
And again stuck :/.
I have Win7 32bit, turned the antivirus software off, doenst do anything, installed/uninstalled/rebooted several times, disconnected/connected device...

It works?! "ADB.exe devices" didnt show the n7000 but now it do so everything was working fine now. Thx!

[Q] Rooting problems

HI all,
i cant seems to root my device, i followed doomlords guide strictly, but the command prompt never goes beyond "WAITING FOR DEVICE"
i don't know what the problems is, i believe i have installed all the drivers.
can any one help?

Li-polymers said:
HI all,
i cant seems to root my device, i followed doomlords guide strictly, but the command prompt never goes beyond "WAITING FOR DEVICE"
i don't know what the problems is, i believe i have installed all the drivers.
can any one help?
Click to expand...
Click to collapse
Have you turned on USB Debugging under Settings>Developer Options>Debugging ??
If you haven't, then turn it on and then try rooting :silly:

Li-polymers said:
HI all,
i cant seems to root my device, i followed doomlords guide strictly, but the command prompt never goes beyond "WAITING FOR DEVICE"
i don't know what the problems is, i believe i have installed all the drivers.
can any one help?
Click to expand...
Click to collapse
"WAITING FOR DEVICE" is sign u have to active this option SETTINGS -> DEVELOPER OPTIONS -> USB Debugging :highfive:

I did that, I'm not that ignorant.
Sent from my C5303 using xda app-developers app

Tried Connecting the USB cable to some other free USB port in your computer??
Or you could try uninstalling the drivers under Device manager...and then reconnecting the USB cable..:fingers-crossed:

By the way, i followed DoomLord tutorial to root the phone. Is it possible to "unroot" the phone then ? Without losing the change ?
In fact i needed to be root to change a system file to fix wifi

ramcool789 said:
Tried Connecting the USB cable to some other free USB port in your computer??
Or you could try uninstalling the drivers under Device manager...and then reconnecting the USB cable..:fingers-crossed:
Click to expand...
Click to collapse
thanks for the tip, re-installing drivers solved the issue. thanks again.

[Q] Note 4 boots to download mode but Kies and Odin can't detect it. Hard Bricked?

I've rooted and flashed ROMs on three previous android phones but I still consider myself something of a noob.
I have a SM-N910T that I've had for a couple of months. I was trying to flash TWRP for the first time. Windows detected the phone (as it always has in the past) and Odin detected the phone. Halfway through the download the process failed and Odin threw up an error message.
Now I get 'Firmware upgrade encountered an issue' with a straight boot. I can boot into download mode on the phone but neither Windows, Odin, or Kies can detect the phone as far as I can tell. There don't appear to be any 'unknown devices' in Device Manager. I've tried different usb ports, different cables, and tried both my laptop and desktop (both are 64-bit windows 8.1) with multiple reboots.
I'm assuming from this point that the phone is hard bricked, but I wanted to see if anyone more knowledgeable had any ideas or input.

Well this is interesting. I can't guarantee this will work, but lets try . . .
1st. Pull the battery from your phone
2nd. Disconnect all usbs from your computer and reboot it
3rd. Once your computer turns back on - open kies 3, click Tools, and then click Reinstall Device Driver. Once finished, close out of kies
4th. Manually boot phone into download mode (Vol down + Home)
5th. Open ODIN and connect phone up to computer
Let me know if the device shows in ODIN before doing anything.

Thanks for taking the time to look at my problem 147aaron.
I followed your steps carefully and ODIN still doesn't see the phone.

halfsmart said:
Thanks for taking the time to look at my problem 147aaron.
I followed your steps carefully and ODIN still doesn't see the phone.
Click to expand...
Click to collapse
Does windows make that noise that something has been connected when you hook it up? If not, it sounds like you are going to have to have it sent in for repair.

I have now also tried installing Heimdall on my Ubuntu laptop and it also fails to detect the phone:
ERROR: Failed to detect compatible download-mode device.​

147aaron said:
Does windows make that noise that something has been connected when you hook it up? If not, it sounds like you are going to have to have it sent in for repair.
Click to expand...
Click to collapse
No, it does not (it did before the failed flash). I figured as much, thanks for trying to help.
I'm guessing that the 'premium handset protection' insurance won't cover this?

halfsmart said:
I have now also tried installing Heimdall on my Ubuntu laptop and it also fails to detect the phone:
ERROR: Failed to detect compatible download-mode device.​
Click to expand...
Click to collapse
Just checking, did you run as Sudo? Or have you set udev permissions. I always forget this the first time when flashing a phone via linux.

First check that your phone is inserted to a USB2.0 port.
Secondly turn the phone completely off for a few seconds, then manually boot into download. Don't let it boot into download mode by just pressing power!
Finally after plugging it in type dmesg in the terminal, it should show your phone connecting as an USB device.
If not post the output of dmesg > dmesg.log

inconceeeivable said:
Just checking, did you run as Sudo? Or have you set udev permissions. I always forget this the first time when flashing a phone via linux.
Click to expand...
Click to collapse
Good catch. However, running as sudo I still get the same error.

halfsmart said:
Good catch. However, running as sudo I still get the same error.
Click to expand...
Click to collapse
Shoot. Sorry man.

Seems like you have a bad phone.

sfjuocekr said:
First check that your phone is inserted to a USB2.0 port.
Secondly turn the phone completely off for a few seconds, then manually boot into download. Don't let it boot into download mode by just pressing power!
Finally after plugging it in type dmesg in the terminal, it should show your phone connecting as an USB device.
If not post the output of dmesg > dmesg.log
Click to expand...
Click to collapse
Unless I reading it wrong (I'm a command-line noob as well) all USB events took place within the first couple of seconds after booting the laptop. I plugged in the phone probably a minute or so after I got to the desktop, so I don't think it's registering. [EDIT: I typed sudo dmesg | grep -i usb and scanned down the time codes on the list]
Here's the dmesg.log:

Just going to throw this out there but have your checked that reactivation lock is unchecked

fcpelayo said:
Just going to throw this out there but have your checked that reactivation lock is unchecked
Click to expand...
Click to collapse
I'm certain that I never enabled anything like that, and on the downloading screen it says 'REACTIVATION LOCK(KK): OFF'
according to a quick google reactivation lock is only available on Verizon and US Cellular models..

I was talking about the one under settings and security. But if this isn't the problem then sorry idk.

fcpelayo said:
I was talking about the one under settings and security. But if this isn't the problem then sorry idk.
Click to expand...
Click to collapse
I think we're talking about the same thing. Either way, thanks for taking the time, I appreciate it.

Can't get prompt for RSA fingerprint

Hello, I upgraded my nexus 6 using the factory image file 7.1.1 shamu-n6f26q-factory and everything is working fine. I got Developer Options visible so I can use the Nexus Root Toolkit by WugFresh like I always do and I cant get the pop-up where is says this PC allows ect or the "prompt for RSA fingerprint" as its called in the directions. I tried different USB ports and I tried selecting the different options and still no pop-up. Any Ideas?

OMG.... Please delete post! I have been messing with this for over an hour pluging and unpluging ect. and all it was is I turned debuging on but I didnt scroll down and tick the usb debuging on... Sorry guys its fixed!