Related
Ok, I have a N7000 with stock gb and KK2 kernel and I want to load the Paranoid Android ICS rom. First I see that I must route my phone, so I tried following the instructions at:
http://www.android.gs/how-to-root-samsung-galaxy-note-n7000/
These instructions make it sound darn simple, but perhaps I am really dumb? Ok, so first I downloaded the latest kies as well as "CF-Root-SGN_ZS_MUL_KK1-v5.0-CWM5.rar"
After installing kies, I got it to connect to my note although not without heart ache. Eventually I found that it would only work if I first disabled USB debugging. But that wasn't enough. Then I had to reboot the phone. (Without that step it wouldn't work). It wasn't clear to me if I even needed to make it connect to kies. The instructions didn't say I needed to. Ok, so then I start "not-rooted-yet.bat" which displays this:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
(3) enable "UNKNOWN SOURCES"
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
(7) !!! PUT A CF-ROOT zImage FILE IN THE zImage FOLDER !!!
I can only easily do items 2-5. It's hard for me to imagine that I should just ignore the other 3 items.
Instruction #1 confused me. How do I accomplish that? It seems that the adb drivers come with the android sdk but the instructions don't say anything about installing that. That seems like a big deal and if it was required it seems that it would surely be mentioned?
Plus I found this post which also indicates that the sdk is not required.
> victorlht88:
> no u don't need the android sdk to root.
> just install kies, plug your phone with usb debugging enabled
> and let it install the drivers.
> restart your comp and plug your phone in (download mode),
> downgrade the firmware (if need be) with odin and simply
> root using cf root.
> its not that tough.
However those instructions seem about as clear as mud, since if I plug in my phone with usb debugging enabled, kies just hung forever saying "connecting".
Do the adb drivers get installed just by installing kies or do you somehow have to coerce kies to do this?
And then there is step 6. But I don't get any prompt of any kind when I plug in the phone to the pc.
And then there is step 7. I don't know what this means, but my guess is that I have to copy the zimage\zimage file to somewhere on the phone. However where exactly? There is no zImage folder on my phone! Plus even if there was, I couldn't copy anything to it after checking "USB debugging" (mass storage mode) I can no longer see my phone in explorer. What happens when I plug the phone in is that the phone says "USB connected" and then two new drives appear on my PC. However if I try to click on either of those I see "No disk drive. Insert a disk and try again". I even tried rebooting my pc, but then I get even more than two new drives showing up briefly, but they always give the same error message as before.
... yet I know that thousands of people have routed their phones ... so I am left pretty mystified. If anyone can clarify these instructions it would help me greatly, and maybe others as well.
Thanks
~Paul
Follow dr. Ketans thread in the development section.
And once on download mode with usb connected, CLOSE KIES. Otherwise odin will not work.
Sent from my GT-N7000 using xda app-developers app
Hi, your guide is taken from here. I think there is a missing step, which is to download the InitialCFRootFlasher.zip from the end of post #2, and you need to follow the instruction step "1.2. If you are not rooted yet: Using the zergRush exploit".
Btw, adb drivers are included when you install Kies in your PC. Once Kies is installed, you have to close it. Make sure your phone is in USB debugging mode before starting the procedure.
praetorius said:
Follow dr. Ketans thread in the development section.
Click to expand...
Click to collapse
Ok, those instructions seemed more clear. Different script as well although perhaps not significantly so? In any case it worked. I'm not rooted! Thanks all
~Paul
you said your kernel is kk2, then why did you use CF Root KK1?
Cf root kernel for KK1 and KK2 is same.
So last night I tried unlocking my bootloader so I could root my HTC One, but I've had one issue. Whenever I get to the part where you make the back up of my apps I get the following message "adb: unable to connect for backup". My phone is conncected, and I have USB debugging enabled. I also checked the device status and it keeps reporting it as offline. I don't quite know what to do, if anyone can help it'll be appreciated.
First off, I barely know anything with regards to phones as I still learning. However, last night had a similar issue and ended up having to use cmd prompt to navigate to adb and then used it to see the device.
MrTechie890 said:
So last night I tried unlocking my bootloader so I could root my HTC One, but I've had one issue. Whenever I get to the part where you make the back up of my apps I get the following message "adb: unable to connect for backup". My phone is conncected, and I have USB debugging enabled. I also checked the device status and it keeps reporting it as offline. I don't quite know what to do, if anyone can help it'll be appreciated.
Click to expand...
Click to collapse
New security enhancements in android 4.2.2 builds (and above) require the end user to explicitly grant adb access to any connecting computers before that connecting machine can successfully issue any adb commands to your device. When you connect a 4.2.2 (and above) android device to your machine (with USB debugging enabled) for the first time, you should be prompted with a confirmation message to allow or disallow USB debugging. This message will display your computers unique RSA key fingerprint and provide you a checkbox to “Always allow from this computer”. Check this box and select ‘OK’. Your device should no longer be listed as ‘offline’
If you don’t see this prompt then you should try the following:
With your device connected via usb and the toolkit running, toggle USB debugging off/on in Settings > ‘Developer Options’ and see if the prompt comes up
Also try unplugging and re-plugging the usb connection.
BD619 said:
New security enhancements in android 4.2.2 builds (and above) require the end user to explicitly grant adb access to any connecting computers before that connecting machine can successfully issue any adb commands to your device. When you connect a 4.2.2 (and above) android device to your machine (with USB debugging enabled) for the first time, you should be prompted with a confirmation message to allow or disallow USB debugging. This message will display your computers unique RSA key fingerprint and provide you a checkbox to “Always allow from this computer”. Check this box and select ‘OK’. Your device should no longer be listed as ‘offline’
If you don’t see this prompt then you should try the following:
With your device connected via usb and the toolkit running, toggle USB debugging off/on in Settings > ‘Developer Options’ and see if the prompt comes up
Also try unplugging and re-plugging the usb connection.
Click to expand...
Click to collapse
I've already done this. I had usb debugging enable since I started this. I even tried unplugging and replugging multiple times while trying to do this. Are there any other settings I need to enable?
MrTechie890 said:
I've already done this. I had usb debugging enable since I started this. I even tried unplugging and replugging multiple times while trying to do this. Are there any other settings I need to enable?
Click to expand...
Click to collapse
You have to help us with a little more info -- ADB and Fastboot just *have* to work or you'll get nowhere:
1) What OS are you using? Version included;
2) Plug in your phone, open a command window in the appropriate place and type: adb devices
Tell us the output.
If you don't get a device listed, either your drivers are bogus on your machine and need to reload, or you're not getting USB debugging setup correctly (not sure how you miss that, so I'd think the former).
tdhite said:
You have to help us with a little more info -- ADB and Fastboot just *have* to work or you'll get nowhere:
1) What OS are you using? Version included;
2) Plug in your phone, open a command window in the appropriate place and type: adb devices
Tell us the output.
If you don't get a device listed, either your drivers are bogus on your machine and need to reload, or you're not getting USB debugging setup correctly (not sure how you miss that, so I'd think the former).
Click to expand...
Click to collapse
The version of android I'm using is 4.3, for my computer I'm using OSX 10.9, and the code that is listed when I search for my device through adb is FA3A8S902431.
MrTechie890 said:
The version of android I'm using is 4.3, for my computer I'm using OSX 10.9, and the code that is listed when I search for my device through adb is FA3A8S902431.
Click to expand...
Click to collapse
Then try this:
adb backup
That should create a backup file called: backup.ab
tdhite said:
Then try this:
adb backup
That should create a backup file called: backup.ab
Click to expand...
Click to collapse
Still get the same issue I've been getting. I typed that command in, it just tells me all the options for adb, and I then retried the other command I was using and squat.
MrTechie890 said:
Still get the same issue I've been getting. I typed that command in, it just tells me all the options for adb, and I then retried the other command I was using and squat.
Click to expand...
Click to collapse
I know you don't want to read this, but you'll need to read all about Macs and this issue. A quick Google on "adb unable to connect for backup mac" brings up all sorts of folks fighting exactly what you are. I don't have a Mac -- use Linux almost exclusively, but it all appears related to either usb debugging, or a connection timeout setting.
tdhite said:
I know you don't want to read this, but you'll need to read all about Macs and this issue. A quick Google on "adb unable to connect for backup mac" brings up all sorts of folks fighting exactly what you are. I don't have a Mac -- use Linux almost exclusively, but it all appears related to either usb debugging, or a connection timeout setting.
Click to expand...
Click to collapse
For me, doing it on Linux wouldn't be a huge issue but since I have a mac as my primary machine I'm trying to make due with it.
I think I just firgured it out actually. I just had to install the android sdk, I was using the abd files provided from a tutorial. anyhow, thanks for trying to help tdhite.
Hi everybody,
I have a 64-bit PC with Windows 7 Ultimate Service Pack 1 and a Samsung Galaxy S Advance GT-I9070 with Android 4.1.2.
I can't install a driver in order to make Windows recognize correctly the phone when I connect it via USB cable.
I've installed and uninstalled Samsung Kies many times with no results. I've also tried some Samsung driver from Windows Update with no success...
When I connect the phone, it is recognized as a MTP Device and the driver installation starts, but always ends with an error, as shown in the attached screen-shot image.
What can I do?
Thank you very very much.
Note: in another PC with WinXP I have no problems.
Firstly make sure phone can run MTP (make sure if you delete MTP releated stuff in system you won't able connect it. Re-flash with Odin) Now if you don't have problem with phone then uninstall drivers & KIES from Windows. Don't just do a uninstall clear temp files, dll files, registry entries (you can use CCleaner) then install THIS DRIVERS.
explanation
King ov Hell said:
Firstly make sure phone can run MTP (make sure if you delete MTP releated stuff in system you won't able connect it. Re-flash with Odin) Now if you don't have problem with phone then uninstall drivers & KIES from Windows. Don't just do a uninstall clear temp files, dll files, registry entries (you can use CCleaner) then install THIS DRIVERS.
Click to expand...
Click to collapse
Hello, thank you for your answer.
How can I make sure my phone can run MTP?
For the complete uninstall, is it enough to run CCleaner, uninstall Kies and then perform the Registry Cleaner in CCleaner?
Thank you
ZioAlfredo said:
Hello, thank you for your answer.
How can I make sure my phone can run MTP?
For the complete uninstall, is it enough to run CCleaner, uninstall Kies and then perform the Registry Cleaner in CCleaner?
Thank you
Click to expand...
Click to collapse
Did you root phone ? or installed a ROM or you just using it stock ?
I noticed something too; if you any have PIN or Password you have to unlock phone otherwise MTP not works. Unlock it and try too.
CCleaner will *probably* be enough but if you want to make sure go to regedit.exe and go to;
Code:
HKEY_CURRENT_USER/Software/
Then delete KIES & USB Driver stuff (don't delete system USB configs & drivers just Samsung's softwares )
EDIT: In start menu click to RUN (or whatever I don't now it's name in English, you're entering a text) Then write
Code:
%AppData%
Then delete KIES & Samsung folders and files.
I've just Updated the phone firmware from Android 2.3.6 to 4.1.2 with Samsung Kies on my WinXP PC.
I've deleted all Samsung Kies registry entries.
Now I'm going to install the driver you suggested...
Let me see results...
King ov Hell said:
Let me see results...
Click to expand...
Click to collapse
Failure... The same as always
ZioAlfredo said:
Failure... The same as always
Click to expand...
Click to collapse
...
I've also installed Windows MTP Porting Kit, but it still fails...
Any idea?..
I think it is the configuration of this PC, because in another brand new PC with Windows 7 I've installed Kies and it all went right.
ZioAlfredo said:
I've also installed Windows MTP Porting Kit, but it still fails...
Any idea?..
I think it is the configuration of this PC, because in another brand new PC with Windows 7 I've installed Kies and it all went right.
Click to expand...
Click to collapse
Have you tried to reboot phone? I lost mtp after charging phone over wall charger. Everytime I need to reboot after charging to get it connected to pc.
Sent from my GT-I9070 using Tapatalk
This may be a bit silly but is important to ask.
Was your PC connected connected to the internet while installing the drivers??
Did you unplug your phone while the drivers were being installed??
anantttt said:
This may be a bit silly but is important to ask.
Was your PC connected connected to the internet while installing the drivers??
Did you unplug your phone while the drivers were being installed??
Click to expand...
Click to collapse
Yes to all.
shut_down said:
Have you tried to reboot phone? I lost mtp after charging phone over wall charger. Everytime I need to reboot after charging to get it connected to pc.
Sent from my GT-I9070 using Tapatalk
Click to expand...
Click to collapse
I've just tried to reboot the phone before connecting it to the PC, but I get the same error (see attachments).
Last year I managed to connect the phone to this PC, but, in any case the connection got interrupted after a while (see this thread).
I don't know what to do...
I had the same problem when i formatted my PC 2 days ago. I did some trial and error and it worked.
1. Dont use any USB Hub if you are using.
2. Remove the Pattern lock or any password security etc. Go to lock screen and select 'None'. (I dont know why but windows doesn't recognise if the device is locked)
3. Have Kies installed. Even new version worked for me. I used 2.5.13043_14
4.Connect your device with the USB cable (Should have MTP option selected which is by default)
5. Windows automatically recognises now and installs the necessary files.
P.S:- Remove the security pattern, etc. It really works.
If worked then pls reply.
Hello,
I've disable any screen lock on my phone and I've connected the USB cable to another USB port (a 3.0 USB port) and Windows magically recognized correctly the device! (no Kies installed, only drivers)
Anyway, after some minutes of usage (cut-paste of files). Windows stopped recognizing the device...
If I disconnect the phone and then connect it back, Windows still recognizes it, but I have few minutes until the device stops being recognized and no file on it can be read...
See attached pictures
ZioAlfredo said:
Hello,
I've disable any screen lock on my phone and I've connected the USB cable to another USB port (a 3.0 USB port) and Windows magically recognized correctly the device! (no Kies installed, only drivers)
Anyway, after some minutes of usage (cut-paste of files). Windows stopped recognizing the device...
If I disconnect the phone and then connect it back, Windows still recognizes it, but I have few minutes until the device stops being recognized and no file on it can be read...
See attached pictures
Click to expand...
Click to collapse
Did you download newest version of drivers? I see in your screenshot it says 2012, on mine it is 2014.
Did you set Windows to gather drivers automaticaly from the internet?
shut_down said:
Did you download newest version of drivers? I see in your screenshot it says 2012, on mine it is 2014.
Did you set Windows to gather drivers automaticaly from the internet?
Click to expand...
Click to collapse
This is how my PC recognizes my phone. The driver seems to be old, but I've configured Windows for downloading drivers automatically and that is all it can do.
Today, th PC did not recognized the phone at once. Then I unmounted and mounted back the MicroSD card and the PC recognized it.
But, after few seconds of folder browsing, the PC lost the connection. I'm thinking that the problem is the SD card.
Solved!
Solved!
It was the USB cable.
I replaced it with an original one and now it works.
Thank you everybody for your effort!
Hey guys, a fellow flasher here. I've tried everything ( really everyhting i know ) but still i cant get my op3t to get recognized in adb or in fastboot.
It's just shows nothing under the list of adb device. Also in drivers section i cant make that exclamation go which means that drivers arent installed properly, but i've tried every driver and toolkit but none of them are of any help as when i go to update driver and select the option to browse to update the driver i cant find the google one. And when i connect my phone with debugging on it shows( in the right bottom corner ) drivers for adb installing but after about 5 seconds it shows failed-no driver found.
P.S-windows 7 is being used and driver enforcing is off also ive used the same pc to flash and unlock my oneplus one many times.
Help!!!
Try another USB port, another driver source, open console as admin, restart your PC after installing driver etc... there are many options... Did you try the command "fastboot devices"?
redukt said:
Try another USB port, another driver source, open console as admin, restart your PC after installing driver etc... there are many options... Did you try the command "fastboot devices"?
Click to expand...
Click to collapse
Thank you but I've tried all this but no luck.
But I've got it working now.
Things I did-
Download android SDK manager, run it as admin, while connected to internet download the Google drivers under extras section, connected op3t with debugging on, go to drivers section, update that driver manually by selecting the google folder in the android SDK folder under extras and now it's good to go!..
BTW do you suggest that should I unlock bootloader and flash twrp the traditional way or use that unified toolkit?
hi folks!
I recently bought a sm-t713 and i can't get my pc to recognize it in linux or windows.. i want to root and unlock the bootloader but odin cant even see it.. and its not an issue with not having debugging on. thats all turned on. Please advise. thanks!
Nobody knows why? I have oem unlock "on"
debugging "on"
But I cant get my comp to see the device..Have Samsung drivers installed. Still no luck.
How can I fix this? all it does is charge when I hook it to pc but can't transfer files.
sorry double post
Same issue here. I've had no luck sorting it out.
Gutterball said:
hi folks!
I recently bought a sm-t713 and i can't get my pc to recognize it in linux or windows.. i want to root and unlock the bootloader but odin cant even see it.. and its not an issue with not having debugging on. thats all turned on. Please advise. thanks!
Click to expand...
Click to collapse
USB Debugging and MTP use different drivers and are different protocols.
Open a command prompt in windows then type:
adb devices
You should get a response with a serial number if USB debugging is working.
If so then it's likely an MTP driver problem or MTP isn't enabled.
In developer options under USB configuration, ensure MTP is enabled.
If so check the device is detected as an MTP device in windows device manager.
ashyx said:
USB Debugging and MTP use different drivers and are different protocols.
Open a command prompt in windows then type:
adb devices
You should get a response with a serial number if USB debugging is working.
If so then it's likely an MTP driver problem or MTP isn't enabled.
In developer options under USB configuration, ensure MTP is enabled.
If so check the device is detected as an MTP device in windows device manager.
Click to expand...
Click to collapse
What the USB configuration is set to is actually moot. When the device is plugged in to a PC the tablet will bring up a notification stating what mode the USB port is in and also provide the option to change that to MTP mode (Transfer files), provided the drivers are correctly installed and all is in working order. By changing USB configuration to MTP the tablet shows up immediately on the PC but you still have to switch to "Transfer file" mode before you can move files between devices. Either way the results are the same and it takes the same number of steps. I always leave my USB configuration in "System Default" and I have never had any issues.
ashyx said:
USB Debugging and MTP use different drivers and are different protocols.
Open a command prompt in windows then type:
adb devices
You should get a response with a serial number if USB debugging is working.
If so then it's likely an MTP driver problem or MTP isn't enabled.
In developer options under USB configuration, ensure MTP is enabled.
If so check the device is detected as an MTP device in windows device manager.
Click to expand...
Click to collapse
Thanks for helping! under device manager the tablet is showing as a mass storage controller not an mtp device. Even though in the tablet itself I have it set to mtp under developer options.
When I do the command "adb devices" I get this message
C:\Users\Brian\Downloads\platform-tools_r28.0.0-windows\platform-tools>adb devices
List of devices attached
nothings there
Also I was reading this is happening because of the newest stock update from Samsung.. is that true?
Gutterball said:
Thanks for helping! under device manager the tablet is showing as a mass storage controller not an mtp device. Even though in the tablet itself I have it set to mtp under developer options.
When I do the command "adb devices" I get this message
C:\Users\Brian\Downloads\platform-tools_r28.0.0-windows\platform-tools>adb devices
List of devices attached
nothings there
Also I was reading this is happening because of the newest stock update from Samsung.. is that true?
Click to expand...
Click to collapse
No response from the adb command suggests you don't have the correct adb drivers installed or the device isn't being detected at all.
Have you installed the ADB drivers?
I would try a different cable first. Is Windows device manager detecting the device if it's plugged in/unplugged?
ashyx said:
No response from the adb command suggests you don't have the correct adb drivers installed or the device isn't being detected at all.
Have you installed the ADB drivers?
I would try a different cable first. Is Windows device manager detecting the device if it's plugged in/unplugged?
Click to expand...
Click to collapse
Still having trouble here, too.
After flashing a ROM and attempting to install what was probably the wrong Gapps version, I'm now getting a boot loop into TWRP, and the device is still not recognized. I can boot into 'Download Mode', but the device is still not being seen by my PC. I have tried multiple times to install the USB drivers, but Odin 3.12.3 is still not seeing the tablet.
Much as I hate installing hokey, bloated software, would KIES be helpful here?
So, all is not lost (yet) - I can still access TWRP, but I'm not sure where to go from here.
Thanks in advance for any ideas you have.
I
BillTheCat said:
Still having trouble here, too.
After flashing a ROM and attempting to install what was probably the wrong Gapps version, I'm now getting a boot loop into TWRP, and the device is still not recognized. I can boot into 'Download Mode', but the device is still not being seen by my PC. I have tried multiple times to install the USB drivers, but Odin 3.12.3 is still not seeing the tablet.
Much as I hate installing hokey, bloated software, would KIES be helpful here?
So, all is not lost (yet) - I can still access TWRP, but I'm not sure where to go from here.
Thanks in advance for any ideas you have.
Click to expand...
Click to collapse
Considering download mode is totally OS independent and neither uses adb nor mtp drivers it seems the issue is either incorrectly installed usb drivers or faulty cable, device or port issues.
Boot to Download mode, open device manager then plug in the usb cable.
Windows should detect the device as a USB composite device.
If there is no detection then there is a communication issue between device and PC which could be any one of the afore mentioned reasons.
No matter what windows should show some sort of detection as soon as the device is plugged in.
No detection means no matter what drivers are installed its not going to work.
It's probably worth uninstalling the usb ports then rebooting.
Then trying again.
ashyx said:
I
Considering download mode is totally OS independent and neither uses adb nor mtp drivers it seems the issue is either incorrectly installed usb drivers or faulty cable, device or port issues.
Boot to Download mode, open device manager then plug in the usb cable.
Windows should detect the device as a USB composite device.
If there is no detection then there is a communication issue between device and PC which could be any one of the afore mentioned reasons.
No matter what windows should show some sort of detection as soon as the device is plugged in.
No detection means no matter what drivers are installed its not going to work.
It's probably worth uninstalling the usb ports then rebooting.
Then trying again.
Click to expand...
Click to collapse
Well, I'll be dipped in $hit.
What's the probability that one guy could have three dodgy USB cables? Used one, wiggled it around and the PC recognized the device. Looks like I'm in for a quick trip to WallyWorld. Thanks!
ashyx said:
No response from the adb command suggests you don't have the correct adb drivers installed or the device isn't being detected at all.
Have you installed the ADB drivers?
I would try a different cable first. Is Windows device manager detecting the device if it's plugged in/unplugged?
Click to expand...
Click to collapse
yeah, windows device manager detects it as a mass storage controller. I installed the driver from samsung site. Cant be the cord cause it works with the phone. Even linux mint wont pick it up either. Any ideas? Thanks again for helping this is driving me nuts!
Gutterball said:
yeah, windows device manager detects it as a mass storage controller. I installed the driver from samsung site. Cant be the cord cause it works with the phone. Even linux mint wont pick it up either. Any ideas? Thanks again for helping this is driving me nuts!
Click to expand...
Click to collapse
Are you able to connect to the device in TWRP, either ADB or MTP?
ashyx said:
Are you able to connect to the device in TWRP, either ADB or MTP?
Click to expand...
Click to collapse
nope don't have twrp installed. and adb or mtp wont detect it. how can I install twrp? don't I need to bootloader unlock this first? And I cant do it if its not recognized by the comp right?
Gutterball said:
nope don't have twrp installed. and adb or mtp wont detect it. how can I install twrp? don't I need to bootloader unlock this first? And I cant do it if its not recognized by the comp right?
Click to expand...
Click to collapse
Are you certain this is a genuine Samsung and not a copy?
Can you post the build details from the app Phone Info.
ashyx said:
Are you certain this is a genuine Samsung and not a copy?
Can you post the build details from the app Phone Info.
Click to expand...
Click to collapse
screenshot is in the attachment.