Develop Bugs

Hardware ID Missing after rooting......

Hello.
I used the Toolkit to root my Note 2, and I had to use option 4 on the rooting menu, Install Custom Recovery, Install via Recovery to get it to work. I tried several times via the Odin tool and Twrp recovery, and the phone kept booting into Android Recovery instead of Twrp recovery.
I finally used Odin to flash back to stock ROM that I got here, but, along the way, even though the Toolkit was able to connect to my Note 2, I get the Hardware ID missing, and I cannot connect to it any longer like I could after I installed the initial drivers.
Anything I can do and stay rooted?

Change usb ports or restart your device. Mine did it last night and I fixed it by doing both..

I have the same problem.
Changing ports and restarting in most cases didn't help and only in few cases I managed to access files on the phone via USB.
Any other suggestion how to solve this?

don't use windows..

Ditto
dstenc said:
I have the same problem.
Changing ports and restarting in most cases didn't help and only in few cases I managed to access files on the phone via USB.
Any other suggestion how to solve this?
Click to expand...
Click to collapse
glen4cindy said:
Hello.
I used the Toolkit to root my Note 2, and I had to use option 4 on the rooting menu, Install Custom Recovery, Install via Recovery to get it to work. I tried several times via the Odin tool and Twrp recovery, and the phone kept booting into Android Recovery instead of Twrp recovery.
I finally used Odin to flash back to stock ROM that I got here, but, along the way, even though the Toolkit was able to connect to my Note 2, I get the Hardware ID missing, and I cannot connect to it any longer like I could after I installed the initial drivers.
Anything I can do and stay rooted?
Click to expand...
Click to collapse
I was able to gain root back using the toolkit. I flashed stock rom image I believe the ROM from the factory then flashed back stock recovery. Went back in after I updated and re-rooted to flash the triangle away. Now I need to unroot and after speaking with Sprint Rep on phone and trying a few things they advised me to take it to store to let them try it. I believe ALL of my problems started when I tried to use Mobile Odin Pro to flash the latest update to LJC (should I have been on stock recovery?). It started to flash then stopped and went into CWM recovery which is the recovery that the toolkit flashed. I for some strange reason was going to flash the update from there except I didn't have it in the right place on my sd card (couldn't access it GOD I'm a Dumbass!). God help me cause I'm too stupid to even understand what side loading is let alone how to do it. If some kind soul would take pity on me and pm me I could get a handle on the differences between HTC and Samsung. Anyway need to unroot now. Oh I keep seeing in the flash counter saying 1 but I'm on stock rom with stock kernel and stock recovery how do I get it to zero. Using triangle away. Anyway to check counter with stock recovery?
OH yeah does anyone keep getting "Internal Error Code 1500" in addition to the hardware id is missing?
Thanks to everyone that takes time to help idiots like me. I promise I CAN learn.
Charles

chrisc627 said:
Change usb ports or restart your device. Mine did it last night and I fixed it by doing both..
Click to expand...
Click to collapse
Thank you...Unlike user: dstenc, the above procedure fixed my issue. As has been the case many times, XDA helpful users to the rescue!
:laugh: :good:

Just to report that for now I've found woraround. I've installed old drivers 1.4.103.0 and now both Kies and file access works.
Still looking for final solution with latest drivers.

Could you walk me through your fix?
dstenc said:
Just to report that for now I've found woraround. I've installed old drivers 1.4.103.0 and now both Kies and file access works.
Still looking for final solution with latest drivers.
Click to expand...
Click to collapse
Hi dstenc,
Would you be so kind as too help me do what you did? I don't have kies on my pc, did you get the old drivers from the s3 forum? I would love to give it a shot.
Thanks for any help
Charles

Could you walk me through your fix?
Mods please delete double post sorry

ceabbott2 said:
Hi dstenc,
Would you be so kind as too help me do what you did? I don't have kies on my pc, did you get the old drivers from the s3 forum? I would love to give it a shot.
Thanks for any help
Charles
Click to expand...
Click to collapse
I don't remember link. I googled so you might try that way.
Just FYI, even with older drivers I have sporadic Hardware ID Missing error, but far too less than with the latest version.

I'm posting this to keep it to the top of this board.
This is my second Note 2 in 2 weeks. I returned the first one because it stated Hardware ID missing, so within my first 2 weeks Sprint gave me a new one thinking that it was my phone. While at the Sprint store, and not yet rooted, we installed the unit and removed the unit 15 times to see if we could get it to have the Missing Hardware ID to pop up, it DIDN'T pop up once, so I thought I was good to go.
I came home and did the common root method that uses Galaxy Note 2 Toolbox. I IMMEDIATELY started getting the Missing Hardware ID again.
So now that we have it localized, what could be missing or creating a problem from the root procedure from the Galaxy Note Toolbox 2???
What I find really strange is that many are not experiencing this problem or they are just living with it.
I even tried the USB Switcher that appeared to install and does switch between Mass Storage and MTP, but although my PC makes the upward noise that sounds like it is installing and recognizing the USB Mass Storage, it doesn't end up recognizing it. It was ZATTA's build but he said it didn't work for his Galaxy 3 or Note 2 either.
Will anyone find a cure????
This will be no fun to have to deal with for the next 2 years.
Chime in PLEASE!!!!!! Even if it's only to insult me, I don't care if you have a cure.
Regards
Dave

if you do Google search, it's a known issue. From what I read, it's a driver issue. Some have had luck using the older Samsung USB drivers. You have downloand them, and install, and have your PC completely disconnected from the internet before plugging in your GN2 after the install. Appaarently the drivers on Microsoft's servers are bad; may be the wrong device.
I've done this, and still have the issue. I just find I don't have plug and unplug the USB cable as much.
What I have seen, the PC does connect to the GN2. It just doesn't recognize it as a storage device. It wants to use it as a modem, probably from the tethering capabilities with a USB OTG cable.
It may not be so much that it's not wide spread, but more that not everyone uses the GN2 as storage device or connects it their PC.

I dont think this is all due to Windows issue. This is what i notice before and after root.
If you have restore to Original Stock ROM, you will notice that your device doesnt encounter this issue.
If you have rooted your device Custom ROM or Flash CMW (this resulted as Binary Counter increased), you would have Hardware Missing Id issue. Somehow the MTP is not working.
If you have Flash your device with a pre rooted stock rom, there is no issue at all until you flash CMW where flashing increase counter.
How i notice this, i have root/unroot my device like 20 times since i got my device.
The issue is here is more of where Binary Counter Increase, in Windows 7 you would face Hardware ID Missing issue. Restart and connect to other USB port will not work.
Some how we need to no let the Binary Counter changed and Triangle Away is only useful if you want to return you device to original state.

knightfox said:
I dont think this is all due to Windows issue. This is what i notice before and after root.
If you have restore to Original Stock ROM, you will notice that your device doesnt encounter this issue.
If you have rooted your device Custom ROM or Flash CMW (this resulted as Binary Counter increased), you would have Hardware Missing Id issue. Somehow the MTP is not working.
If you have Flash your device with a pre rooted stock rom, there is no issue at all until you flash CMW where flashing increase counter.
How i notice this, i have root/unroot my device like 20 times since i got my device.
The issue is here is more of where Binary Counter Increase, in Windows 7 you would face Hardware ID Missing issue. Restart and connect to other USB port will not work.
Some how we need to no let the Binary Counter changed and Triangle Away is only useful if you want to return you device to original state.
Click to expand...
Click to collapse
Yep I think you may be on to something. Because when I rooted I tried both TWRP and CWM and then I had to go back to stock to get to apply the LJC update. Ever since I have had the chameleon error and Handsfree activation issues. Oh my counter always says 1 and I can't remove it with triangle away. I think it says custom binary yes and the counter says 1. I am using a laptop with Windows 7 and it now recognizes the device just can't stop the errors on start up.
Charles
Sent from my SPH-L900 using xda premium

Samsungs older drivers: uploaded.net/file/hdh0f1xd

[Q] MTP Driver Install Fail

Hi all,
Got my new S III on Jan. 1. Love it. Gave me an opportunity to use my old Cappy to experiment with. Flashed a couple of ROMS already and really love it. OK..so here's the problem. The only thing I have done with the S III is root it using the QCOM Toolkit. When I downloaded the drivers and plugged in phone it said that if a device number was showing that all drivers had installed. Don't really know if the MTP driver loaded at that time or not...but the device number was there and I proceeded to root the phone. Now when I try to connect to PC I get the dreaded MTP driver failed error message. Did a TON of research on this and tried EVERYTHING...still no joy. I am running Windows 7 Home Premium and even tried using my XP Pro machine...still no joy. Would love to flash a ROM on the new S III but no way to copy to SD card without PC connection.
Phone is A T&T SGH-1747 4.04 Version.
OK to reduce the number of "have you tried's" I have: tried various cables, uninstall reinstall Kies..Kies driver repair, uninstalled/reinstalled all Samsung drivers. Tried the MTP/PTP toggle idea. Plugged in with USB debugging ON and OFF. Sooooo tired of getting the MTP USB Device Driver failed message!!!
Any new ideas out there?

do a factory reset on ur phone
uninstall/install drivers again http://www.samsung.com/us/support/owners/product/SGH-I747MBBATT
after u install drivers open odin and connect phone. it should be recognized

MoeisHere said:
do a factory reset on ur phone
uninstall/install drivers again
after u install drivers open odin and connect phone. it should be recognized
Click to expand...
Click to collapse
Thanks Moe. Yeah I was afraid of that. Just got all my apps restored. Oh well. Well worth it if it works. Thanks again!

Factory reset is the only option that worked for me, and I tried everything you listed above. Also, based on prior posts, I plugged it into my computer before I signed into my google accounts.

sjroberts98 said:
Factory reset is the only option that worked for me, and I tried everything you listed above. Also, based on prior posts, I plugged it into my computer before I signed into my google accounts.
Click to expand...
Click to collapse
Right SJ...I had heard that also. I really hope it works because if I do a factory reset and lose all my apps and data and it doesn't work...I am gonna lose it! LOL!

HELP! Firmware Won't Upgrade!

I'm having problems completing a firmware upgrade on my wife's Galaxy S2. It's at ICS and I want to get it to Jelly Bean. We're using the horrible Samsung program Kies, which is hosting the update to us. It sees the S2 fine... No problems there. It identifies the phone and tells us there's a newer firmware version we can download. Every time I perform the update, it downloads the firmware and when it reboots the phone, I get an error that the device can't be found and I should try again. When I go in device manager, I see an exclamation point on Samsung Mobile USB CDC Composite Device and it says the device couldn't be started.
It looks as thought, when the phone reboots to download the firmware from the laptop after the laptop has the firmware, Kies isn't seeing the phone. So I did vol-up-down to get it in programming mode and then reinitiated the download. That little trick doesn't work since Kies isn't identifying the device.
I've checked that I have the most current drivers, which I do. I've uninstalled them and reinstalled them and uninstalled Kies and reinstalled Kies and still get the error. I've also already updated the firmware on my Galaxy S3 using Kies on this computer and it worked fine. Now when I do it on my wife's S2, it bombs.
I then loaded Kies on another laptop and it's even worse. It downloads the firmware update and the entire application totally crashes.
I've gone to T-Mobile and they can't help with anything. They suggested turning USB Debugging on in the Developer Options on the phone, which I did. Still, nothing.
I located the hooks in the registry editor for the CDC composite device driver and everything *looks* good, as far as I can tell. Driver is dated 1/23/2013. As I said, it updated the firmware on my S3 fine... It just won't do it on my wife's S2. I don't know what to do.
Can anyone provide any advice or help? I've spent about 11 hours on this over two days and am running out of ideas.
-Paul

premington said:
I'm having problems completing a firmware upgrade on my wife's Galaxy S2. It's at ICS and I want to get it to Jelly Bean. We're using the horrible Samsung program Kies, which is hosting the update to us. It sees the S2 fine... No problems there. It identifies the phone and tells us there's a newer firmware version we can download. Every time I perform the update, it downloads the firmware and when it reboots the phone, I get an error that the device can't be found and I should try again. When I go in device manager, I see an exclamation point on Samsung Mobile USB CDC Composite Device and it says the device couldn't be started.
It looks as thought, when the phone reboots to download the firmware from the laptop after the laptop has the firmware, Kies isn't seeing the phone. So I did vol-up-down to get it in programming mode and then reinitiated the download. That little trick doesn't work since Kies isn't identifying the device.
I've checked that I have the most current drivers, which I do. I've uninstalled them and reinstalled them and uninstalled Kies and reinstalled Kies and still get the error. I've also already updated the firmware on my Galaxy S3 using Kies on this computer and it worked fine. Now when I do it on my wife's S2, it bombs.
I then loaded Kies on another laptop and it's even worse. It downloads the firmware update and the entire application totally crashes.
I've gone to T-Mobile and they can't help with anything. They suggested turning USB Debugging on in the Developer Options on the phone, which I did. Still, nothing.
I located the hooks in the registry editor for the CDC composite device driver and everything *looks* good, as far as I can tell. Driver is dated 1/23/2013. As I said, it updated the firmware on my S3 fine... It just won't do it on my wife's S2. I don't know what to do.
Can anyone provide any advice or help? I've spent about 11 hours on this over two days and am running out of ideas.
-Paul
Click to expand...
Click to collapse
First u got check USB debugging ON (on the phone)
disable anti virus on the pc/laptop
kies will put your phone into download mode and will take awhile (Kies is super slow) for good reasons
Also consider rooting your phone and install custom recovery (CWM) and flash all the rom(s) you wish [if that's an option]
hit Thanks if i helped

Thanks for the help, Sam.
I'll try it again with the virus protection off. I disabled the Windows firewall and that did nothing. I've tried it about 12 to 15 times, which takes a long time because Kies takes so long to download what it needs.
Can I root a T-Mobile phone? I used to have a Motorola Atrix 2 and rooted that and did manual firmware and ROM upgrades, but that was an unlocked and rooted phone. I'm afraid I may screw up the phone or my T-Mobile service by rooting it and doing custom installs. Does anyone have experience with this on a T-Mobile phone they purchased at T-Mobile? I don't want to mess the phone up.
At this point, I think that's the only way I'm going to go Jelly Bean on my wife's phone.
-Paul

Rooting your s2 is simple and easy to do. Go to the dev section and look at the threads on how to do it.
You will use Odin to flash a custom recovery such a TWRP whick will install supersu. At that point you can flash the ROM of your choice and not have to deal with Kies anymore.
Hope this helps
Sent from my SAMSUNG-SGH-T989 using xda premium

use this as a ref. http://galaxys2root.com/galaxy-s2-root/how-to-root-t-mobile-galaxy-s2-sgh-t989/
make sure to backup your current ROM as soon as your get root& cwm
after that u can flash any rom here is a list :http://www.androidmodmarket.com/ModMarket/Devices/Device-XDA-F-1332.html
i think u will like a clean fast 4.2.2 (jb) rom like slimbean....
try 'em & see which one u like......xda is your best bet for help & just about anything ROM
hit thanks if u like

sam.balia1012 said:
use this as a ref. http://galaxys2root.com/galaxy-s2-root/how-to-root-t-mobile-galaxy-s2-sgh-t989/
make sure to backup your current ROM as soon as your get root& cwm
after that u can flash any rom here is a list :http://www.androidmodmarket.com/ModMarket/Devices/Device-XDA-F-1332.html
i think u will like a clean fast 4.2.2 (jb) rom like slimbean....
try 'em & see which one u like......xda is your best bet for help & just about anything ROM
hit thanks if u like
Click to expand...
Click to collapse
This is all great information... Thanks so much. I've pressed "Thanks" to each of you. :good:
-Paul

Putting a 100$ bounty for someone to fix my phone (SGH-i317M)

I am at my wits end to try to repair my phone. It is softbricked and responds to download mode only.
I've had chat with xda members and read threads on it:
http://forum.xda-developers.com/chef-central/android/nand-write-start-fail-odin-soluction-t2851096
http://forum.xda-developers.com/galaxy-note-10-1/help/help-help-unbricking-galaxy-note-10-1-t2872125
and many others. in the end, my phone is still stuck with the NAND Write Start error with odin.
I know it happened after i tried creating a backup of my phone in recovery mode (phone was rooted with cf auto root and had a version of CWM on it). CWM gave me a warning about possibly bricking the phone, i agreed to the warning beacuse it always worked in the past, but when i rebooted, it was bricked this time.
this phone is not dead but samsung won't fix it beacuse it is rooted. I refuse to throw it away. I have read many people have it this error since kitkat 4.4 so surely there is a fix somewhere. I am hoping somebody will be more resourceful/experienced than i am.
I have tried changing to several different USB ports, without a hub, using original cables (bunch of different ones too) in many many different order and fashion. I tried enough variation to be convinced it is statistically impossible that all my hardware that was previously working for flashing has stopped working all at once. aka - it is not a usb port or data cable problem
may be related to data charging port on the phone though I highly suspect it given how it started.
I tried different roms, different versions of odin, i tried depackaging and repackaging roms, i simply do not know what to do anymore.
i tried reflashing with kies but kies just dies on me.
i tried flashing it with adb but adb won't even connect. when i plug the phone windows recognizes it and usb driver seems to work ok (not getting an error)
I have uninstalled and reinstalled drivers several times, rebooting in between installs. no difference.
i tried flashing different bootloaders as well as entire roms, no difference
I tried changing the pit file but that failed as well (odin couldn't even write the pit so my phone is not dead even if i failed pitting it)
i have access to both windows and ubuntu linux if it makes a difference.
Here are the terms of the bounty:
Price : 100$ (payable by paypal from eniac0 @ "some google mail domain starting with gm"
goal : find a fix that works on the latest firmware for SGH-i317M (Rogers, Canada)
how : i don't know but i need to be able to reproduce it. I am not new to flashing but anything advanced will need to be explained clearly.
I don't really know how this sorts of request usually turns out but i am serious. you even got my google mail address to bill me up if i fail to pay.

have you given a look at this thread? http://forum.xda-developers.com/showthread.php?t=2711825 it might give you some ideas to help you out. also did you try flashing a new recovery to see if you could at least get it to boot to that?
dont care about the bounty just trying to toss something out there that may help you

Did you ever try flashing the stock recovery - JUST the stock recovery - through Odin?
If not, grab the recovery.img and make your own tarball for Odin in Linux.
Hopefully that will flash and get you closer.

eniac0 said:
I am at my wits end to try to repair my phone. It is softbricked and responds to download mode only.
...
i have access to both windows and ubuntu linux if it makes a difference.
Click to expand...
Click to collapse
Since you mentioned Ubuntu, you can also try using heimdall instead of odin... http://glassechidna.com.au/heimdall/ . Unfortunately, I think it may be a hardware problem?
Since you are willing to pay to have it fixed, if all else fails, you can always send it off to http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-note-jtag-brick-repair/. It will actually be cheaper than what you are offering to pay ~$40 + shipping
good luck

Thanks all for your help, I've messed around and gotten no closer. I'm beginning to lean on a hardware failure, perhaps from the usb data port either that or the way bootloaders are packaged in kitkat 4.4 is different. which is why initially this thread gave me hope: http://forum.xda-developers.com/chef-central/android/nand-write-start-fail-odin-soluction-t2851096 but i tried far too many times now to believe I'm going to succeed. In fact, I've gotten confused as to what i tried, in which order, with which rom. I'm basically trying anything and that's a recipe for bricking the phone for good. so i've stopped.
I'll also thank kozmo21 for the link to the repair shop. i was unaware this existed, as a last resort I'll be sending them my phone. If it turns out they are able to repair it, I'll honor my word and give you something for having been part of the solution.

eniac0 said:
I am at my wits end to try to repair my phone. It is softbricked and responds to download mode only.
I've had chat with xda members and read threads on it:
http://forum.xda-developers.com/chef-central/android/nand-write-start-fail-odin-soluction-t2851096
http://forum.xda-developers.com/galaxy-note-10-1/help/help-help-unbricking-galaxy-note-10-1-t2872125
and many others. in the end, my phone is still stuck with the NAND Write Start error with odin.
I know it happened after i tried creating a backup of my phone in recovery mode (phone was rooted with cf auto root and had a version of CWM on it). CWM gave me a warning about possibly bricking the phone, i agreed to the warning beacuse it always worked in the past, but when i rebooted, it was bricked this time.
this phone is not dead but samsung won't fix it beacuse it is rooted. I refuse to throw it away. I have read many people have it this error since kitkat 4.4 so surely there is a fix somewhere. I am hoping somebody will be more resourceful/experienced than i am.
I have tried changing to several different USB ports, without a hub, using original cables (bunch of different ones too) in many many different order and fashion. I tried enough variation to be convinced it is statistically impossible that all my hardware that was previously working for flashing has stopped working all at once. aka - it is not a usb port or data cable problem
may be related to data charging port on the phone though I highly suspect it given how it started.
I tried different roms, different versions of odin, i tried depackaging and repackaging roms, i simply do not know what to do anymore.
i tried reflashing with kies but kies just dies on me.
i tried flashing it with adb but adb won't even connect. when i plug the phone windows recognizes it and usb driver seems to work ok (not getting an error)
I have uninstalled and reinstalled drivers several times, rebooting in between installs. no difference.
i tried flashing different bootloaders as well as entire roms, no difference
I tried changing the pit file but that failed as well (odin couldn't even write the pit so my phone is not dead even if i failed pitting it)
i have access to both windows and ubuntu linux if it makes a difference.
Here are the terms of the bounty:
Price : 100$ (payable by paypal from eniac0 @ "some google mail domain starting with gm"
goal : find a fix that works on the latest firmware for SGH-i317M (Rogers, Canada)
how : i don't know but i need to be able to reproduce it. I am not new to flashing but anything advanced will need to be explained clearly.
I don't really know how this sorts of request usually turns out but i am serious. you even got my google mail address to bill me up if i fail to pay.
Click to expand...
Click to collapse
Have you tried going to sammobile and download the newest firmware and only flashing that in odin?

Use CF auto root. Put the phone in download mode and flash it in Odin. I soft bricked my phone and it fixed it.
Also this guy had great walk through videos on how to do everything you need.
http://www.rootjunky.com/samsung/samsung-galaxy-note-2/
If it works to fix your phone. Keep your money. I'll take the karma points for putting you on the correct path.
Sent from my SHIELD Tablet using XDA Free mobile app

ShrekOpher said:
Use CF auto root. Put the phone in download mode and flash it in Odin. I soft bricked my phone and it fixed it.
Also this guy had great walk through videos on how to do everything you need.
http://www.rootjunky.com/samsung/samsung-galaxy-note-2/
If it works to fix your phone. Keep your money. I'll take the karma points for putting you on the correct path.
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
More than likely its a bootloader issue my phone did that and all i did was flash the bootloader then it worked again but hes done so much idk what he needs now that's y i said to try a firmware to see if that helps

Download toolkit and select option to push file into phone.
Download a ROM of your choosing, push it into your phone, restart in recovery mode and select file.

Update?
Did you get it fixed? Just my two cents, in case you didnt, I had a similar problem and alll I did to fix it was flash the JediMasterX2 ROM with CWM and everything worked out.

[Q] Rooting Help? USB Not Working In Download Mode

I have a Sprint Samsun Galaxy Note 4, in the USA. I'm trying to root my device - I've read online tutorials, watched videos, and it doesn't seem to be working. Here's what happens:
1. Downloaded CF Auto Root for my device, unzipped it.
2. Set up ODIN.
3. Set phone to download mode, plugged in to PC.
4. Did not see the blue light, figured I didn't have the right drivers.
5. Turned phone back on, and noticed that ODIN light now works (as do file transfers), but downloaded new drivers anyway.
6. Uninstalled old drivers, rebooted.
7. Installed new drivers, rebooted.
8. Placed phone in download mode again, same issue.
Any ideas?

Did you wait a couple of minutes between steps 3 and 4 before giving up. I just re-did this last night; I didn't time it but my PC must have taken a minute to show COM to be ready to start Odin on the stock tar.
I was also having USB driver issues and reinstalled. My PC has been having USB issues in general with Windows 8.1 updates; had to uninstall and reinstall the same PC generic USB driver. Circa 2009 era PC needs an overhaul or replacement.
BTW, if you're using an older CF Auto root, CF went back to Odin 3.07 and updated to superSU v2.45

I did, because I was unsure what was going on. This is only the second time I've rooted a phone, so I was unsure what would happen if I pulled the battery. I think I waited about 20 minutes while looking online to figure out what was going on.
I'm not sure what you mean by an older version. I downloaded the version for my phone from chainfire.eu

http://redirect.disqus.com/url?url=...&thread=3459253652&zone=thread&area=discovery
http://redirect.disqus.com/url?url=...&thread=3443914612&zone=thread&area=discovery
Some questions I should have asked earlier: USB debugging enabled? Using USB 2.0? Tried different USB cables?

Yes, device debugging is enabled. First thing I did on my phone after activation =)
I'm not sure how to tell if I'm using USB 2.0 or 3.0.
I did try a different cable. I don't think the cable would be the issue since it works when the phone is on normally, though?
I'm going to follow the troubleshooting guide in the links you posted, see if that helps =)

Yes, device debugging is enabled. First thing I did on my phone after activation =)
I'm not sure how to tell if I'm using USB 2.0 or 3.0.
I did try a different cable. I don't think the cable would be the issue since it works when the phone is on normally, though?
I'm going to follow the troubleshooting guide in the links you posted, see if that helps =)
PS. Did you use Kingo to root your note 4? I might give it a try.

No, I just posted links for the thoroughness of checks. I used CF Auto root. Good luck.

Did not work either. It DOES say I'm connected, went through the reboot, but then just starts over again. /sigh

I'm thinking the MTP might be the issue, but I don't seem to have a MSD option on my note 4?

Any more ideas?

What Windows version are using? If it's 8.1, has it been updated? There was a USB 2.0 update that fixed some devices reporting as compatible greater than 2.0 but not handled correctly by Windows 8.1 but was OK with Windows 8.0 and below. Windows 8.1 got an update July, 2014, that should have fixed that but not all were fixed; there's a link for reporting exceptions with a log but I'm not sure that applies to you.
Have you tried using the USB port on test of PC case?
Maybe being more specific about your PC and what you've tried would help.
From there, if anyone else has some suggestions, please advise.

faile486 said:
I have a Sprint Samsun Galaxy Note 4, in the USA. I'm trying to root my device - I've read online tutorials, watched videos, and it doesn't seem to be working. Here's what happens:
1. Downloaded CF Auto Root for my device, unzipped it.
2. Set up ODIN.
3. Set phone to download mode, plugged in to PC.
4. Did not see the blue light, figured I didn't have the right drivers.
5. Turned phone back on, and noticed that ODIN light now works (as do file transfers), but downloaded new drivers anyway.
6. Uninstalled old drivers, rebooted.
7. Installed new drivers, rebooted.
8. Placed phone in download mode again, same issue.
Any ideas?
Click to expand...
Click to collapse
Press volume up to confirm download mode?

rawintellect said:
Press volume up to confirm download mode?
Click to expand...
Click to collapse
Yes, that has to be done to get to download mode? I'm at the screen where it says 'Downloading...Do not turn of the target!!'

faile486 said:
Did not work either. It DOES say I'm connected, went through the reboot, but then just starts over again. /sigh
Click to expand...
Click to collapse
I'm sorry but I don't recall seeing this reply because I don't understand it now. I may have overlooked it?
Are you saying the phone appears to download but boot loops? You should see success and 0 failures prior to auto boot. Is that the CF Auto root flash in Odin or another Odin flash like recovery or stock tar? If that's happening, did you try to pull battery and delete cache and dalvik cache in recovery? Is the phone semi bricked or just not rooted? Can you Odin the recovery tar for TWRP recovery? If so, you could just flash the superSU zip file in TWRP.
http://download.chainfire.eu/supersu
Another suggestion, if you're getting anywhere with Odin, you should close and reopen Odin if doing multiple flashes. Close after each flash; i.e., power down, flash stock tar, close Odin, open Odin, flash CF Auto root, close Odin, flash recovery (download mode steps omitted since you know that already).
Again, someone might could help with detailed setup details and steps taken. Sorry if I'm not following well; I'd like to help, if possible.

samep said:
What Windows version are using? If it's 8.1, has it been updated? There was a USB 2.0 update that fixed some devices reporting as compatible greater than 2.0 but not handled correctly by Windows 8.1 but was OK with Windows 8.0 and below. Windows 8.1 got an update July, 2014, that should have fixed that but not all were fixed; there's a link for reporting exceptions with a log but I'm not sure that applies to you.
Have you tried using the USB port on test of PC case?
Maybe being more specific about your PC and what you've tried would help.
From there, if anyone else has some suggestions, please advise.
Click to expand...
Click to collapse
I'm using Windows 7. Using another PC is a good idea, I'll try that.

faile486 said:
I'm using Windows 7. Using another PC is a good idea, I'll try that.
Click to expand...
Click to collapse
Didn't realize the auto correct suggested wrong word. I meant rear USB of PC case but trying another PC is also suggested.
Windows 7 means most of my suggestions regarding the drivers may not apply to you. Off topic: upgrading to Windows 8 from Windows Vista had me searching for needed applications and tools omitted from Windows 8. Windows 7 is more developer ready than Windows 8. Simply rooting should be OK with either version as long as drivers and Windows updates are up to date and not broken.
Try those ideas; if still no success, consider the suggestions and questions I gave in the reply earlier today.

samep said:
Didn't realize the auto correct suggested wrong word. I meant rear USB of PC case but trying another PC is also suggested.
Windows 7 means most of my suggestions regarding the drivers may not apply to you. Off topic: upgrading to Windows 8 from Windows Vista had me searching for needed applications and tools omitted from Windows 8. Windows 7 is more developer ready than Windows 8. Simply rooting should be OK with either version as long as drivers and Windows updates are up to date and not broken.
Try those ideas; if still no success, consider the suggestions and questions I gave in the reply earlier today.
Click to expand...
Click to collapse
I don't know what I did differently on the 18 ****ING TIME but it finally worked! Your thanks meter has been duly increased =)

faile486 said:
I don't know what I did differently on the 18 ****ING TIME but it finally worked! Your thanks meter has been duly increased =)
Click to expand...
Click to collapse
Glad to see you among the rooted in Sprint Note 4 XDA. Hopefully your solution can be repeated for future updates. Lollipop well be here some day.

Does Kingo root Trip Knox?
Sent from my SM-N910P using XDA Free mobile app