[Q] Rooting Help? USB Not Working In Download Mode - Sprint Galaxy Note 4 Q&A, Help & Troubleshooting

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

Related

[Guide][TOOL] FASTBOOTROOT (deprecated)

(DEPRECATED)
I no longer support or care to support this is someone wants to take over and deal with this and the complaints go for it. It has not been tried on the 2.2.2 version of android in case you want to try it.
Tired of all those funky ways of rooting? Wanna just push a button and be rooted?
Guess what I've got something for you.
Introducing FastbootRoot (patent not pending) for the virgin mobile optimus v
FastbootRoot was designed with simplicity in mind. The easy to use ui makes rooting your lg optimus easy and quick without all those adb commands. It takes the guess work out ( is this right, what does he mean by that? ) of rooting your phone.
Features:
flash a custom recovery
this feature only flashes a custom recovery without rooting your phone giving you the ability to back up your current system without root. I put this in here in case of needing to return the phone for warranty matters
flash the entire shebang
This flashes a new boot image, a new system image*, and custom recovery.
Revert to stock
thanks to destundead we now have the stock system image and boot combined with my stock recovery we are good to go
New experimental install windows xp fastboot drivers
My goal is to fully automate this process and to make this as painless as possible for the new users. This new feature is untested and will either work or it won't. Give me some feedback if it does or doesn't.
--------------------------How to Use--------------------------
Download fastbootroot from here and place it on your desktop.
Download the usb drivers from here
On your phone turn on usb debugging by pushing menu, then settings, then applications, then development, and then usb debugging.
Install the drivers ( I find that rebooting after the drivers have been installed will install a whole new set of drivers. I recommend this method)
unzip fastbootroot and inside double click the fastbootroot file. Make your selection and your done.
Here's a video on using it and a little explanation
watch it here
WHAT THE FUTURE HOLDS:
no need to install usb drivers
Enjoy this and remember this works fully on windows 7 and I tested it myself. No matter what there's always room for user error though in which case I take no responsibility if things go wrong.
PROBLEMS AND COMPLAINTS
Some people are reporting problems like drivers not installing or other things. First off if you have a problem you need to state exactly what operating system you are using (windows 7, windows vista, or windows xp).
This only works with the virgin mobile optimus v. Make sure you have the virgin mobile optimus v (not a optimus t, m or a picture of the v pasted on top of a w490)
Tell me what you did exactly don't lie. I know from experience when someone says, 'I did this I definitely didn't do that', whether or not they are holding something back. The more info you can give the better if your holding something back that's gonna delay the process.
This is free. I ask for donations but they aren't required at all. So when your asking for more things remember this is free.
Like my work donate to me herehttps://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=FEP8NQ8J49MX8
*the new system image is stock with root, flash_image and busybox installed
It's fully automated?
Sent from my VM670 using XDA App
overthinkingme said:
It's fully automated?
Sent from my VM670 using XDA App
Click to expand...
Click to collapse
yep the only thing that you gotta do is download fastbootroot and the lg drivers. It will take care of everything else for you. I will say that I've tested this and my earlier variant of it quite a few times. I even made a video for the other one.
Downloading this now. will give it a try. Thanks!
--bornagainpenguin
This is for lg optimus v for virgin mobile, right?
Sent from my SGH-T959 using Tapatalk
i get a write error suspended reset port change on my phone when trying to run this? it says waiting on device on the fast boot system? any ideas what im doin wrong thanks
shaynes vibrant said:
i get a write error suspended reset port change on my phone when trying to run this? it says waiting on device on the fast boot system? any ideas what im doin wrong thanks
Click to expand...
Click to collapse
your in fastboot by now you should be good unless you did something crazy. What will happen is windows will automatically install the fastboot drivers and do it's thing and you'll be good
Asadullah said:
your in fastboot by now you should be good unless you did something crazy. What will happen is windows will automatically install the fastboot drivers and do it's thing and you'll be good
Click to expand...
Click to collapse
This does not seem to be happening. How can I abort the fastboot procedure so I can reboot and try again?
--bornagainpenguin
Hello? Please someone be there who can help me!
The detection sequence you describe did not work, Windows is not finding the drivers properly. Is it safe to reboot the machine while in fastboot? Can I unplug the USB without bricking my phone?
--bornagainpenguin
If nothing has flashed, I'm sure you're fine. It dependant on how far it got .
Would op mind posting the manual way to root through fast boot?
Sent from my VM670 using XDA App
bornagainpenguin said:
Hello? Please someone be there who can help me!
The detection sequence you describe did not work, Windows is not finding the drivers properly. Is it safe to reboot the machine while in fastboot? Can I unplug the USB without bricking my phone?
--bornagainpenguin
Click to expand...
Click to collapse
yes your okay to unplug your phone the process either works all the way or not at all I'm confused as to why it didn't install the drivers though. I guess I'll just have to add them to the batch
overthinkingme said:
If nothing has flashed, I'm sure you're fine. It dependant on how far it got .
Click to expand...
Click to collapse
How do I know?
Right now the screen says:
Code:
Fastboot mode started
gpio_12c: invalid khz: 0
b1: i2c write error
udc_start()
-- suspend --
--reset --
-- portchange --
-- reset --
-- portchange --
STALL GET_DESCRIPTOR 128 6 1006 0 18
-- reset --
-- portchange --
-- reset --
-- portchange --
I removed the battery and the phone restarted without issues. Not sure why things did not go the way they're supposed to--could it be because I had the drivers from the ROMTOOLS package installed before? NOTE: Prior to trying this procedure I uninstalled all of those and rebooted before installing the drivers linked here.
Another thought, OP says he is running Windows Seven; I am on Windows XP. Could this have anything to do with my trouble?
--bornagainpenguin
UPDATE: I tried installing the drivers included with the ROMTOOLS package and my phone was recognized again. No luck when trying to run fastboot. Not sure why this is happening or why I am unable to use the drivers OP linked to. They seem to install when clicked but the system doesn't seem to think the drivers apply to this phone for some reason...
Okay what happened was your fastboot drivers didn't install correctly I'm in the process of uploading a video to show you how to install the fastboot drivers.
I wrote this while before your last post yes there is a problem with windows xp. It doesn't download them like it would on windows 7. I can test all day long on windows 7 but not on xp. The method in the video should work for xp users
Asadullah said:
Okay what happened was your fastboot drivers didn't install correctly I'm in the process of uploading a video to show you how to install the fastboot drivers
Click to expand...
Click to collapse
I appreciate the effort, but unless the video is closed captioned it may not do me much good. I am hard of hearing (one of the reasons why I picked this phone was its high T4 rating which works well with my hearing aids and telecoil adapter --think headphones for hard of hearing people) so cannot always hear audio on videos very good.
--bornagainpenguin
bornagainpenguin said:
I appreciate the effort, but unless the video is closed captioned it may not do me much good. I am hard of hearing (one of the reasons why I picked this phone was its high T4 rating which works well with my hearing aids and telecoil adapter --think headphones for hard of hearing people) so cannot always hear audio on videos very good.
--bornagainpenguin
Click to expand...
Click to collapse
It's recorded in 780 hd using camstasia. Even if you can't hear it you'll be able to follow along the process is very simple
http://www.youtube.com/watch?v=aTE30yd-P_U
here's the video
I've integrated the fastboot drivers into the next release for windows xp I need a beta tester before I release this.
Does this just root our existing system, or does it install a whole new rooted image (requiring us to reinstall all of our programs and settings)?
I have XP, by the way. If it just roots, I would be willing to beta test (but if it doesn't work, if it doesn't work, I want to be able to get back to where I was as my phone works well).
This is F*****KIN GREAT!!!! Thanks!!
I'm having bootloop issues and I see a post here which suggests that one way to fix the situation is with fastboot. Do you know if fastboot can help me? If so, how?
--bornagainpenguin

Root access and tethering but stock?

Hello,
I know nothing about rooting so I may be using the wrong terms. I've read a number of people are having issues with their phones after they've rooted or changed to rom or something. I've also read you can run stock(?) but be rooted (or something like that) so you won't have any issues.
Is there a way to give root access without really changing anything about your phone other than enabling tethering? I really only want to enabling tethering. Oh and the sonicwall client says the phone must be rooted or have root access or something before I can run it.
Yeah that can be done, but once you're rooted, you'll end up flashing roms lol
Sent from my SPH-D710 using xda premium
Instructions on how to get root with stock kernel here: http://forum.xda-developers.com/showthread.php?t=1273730
I followed the instructions to the tee and it worked perfectly. I have wifi tethering working now.
Thanks. If anyone has been flashing or rooting on Samsung Androids for a while, what do you think the chance is that I'll be able to do the over the air update for this phone when it comes out if I do root it?
boe said:
Thanks. If anyone has been flashing or rooting on Samsung Androids for a while. What do you think the chance is that I'll be able to do the over the air update for this phone when it comes out if I do root it?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=18038477&postcount=46
The other thread is long and convoluted, pm me if you need anymore details, but the original threads in development by ACS are quite clear and easy to follow.
nabbed said:
http://forum.xda-developers.com/showpost.php?p=18038477&postcount=46
The other thread is long and convoluted, pm me if you need anymore details, but the original threads in development by ACS are quite clear and easy to follow.
Click to expand...
Click to collapse
Thanks. I appreciate you taking the time to reply. To be honest I really don't know what you said though. I'm sure it is simple and obvious but I don't know squat about modifying my android phone so I'm not sure what you said really means.
Anyone know if there are any videos I can follow along to get to where I need to be. I think if someone tries to explain it to me in text I'll get lost and people will get frustrated with my lack of android knowledge.
boe said:
Thanks. I appreciate you taking the time to reply. To be honest I really don't know what you said though. I'm sure it is simple and obvious but I don't know squat about modifying my android phone so I'm not sure what you said really means.
Anyone know if there are any videos I can follow along to get to where I need to be. I think if someone tries to explain it to me in text I'll get lost and people will get frustrated with my lack of android knowledge.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1268037
http://forum.xda-developers.com/showthread.php?t=1273647
Here's what you will be doing:
1) Use "Odin" method to flash kernel+cwm recovery (.tar file) from your computer to the phone.
2) Use recovery to flash su.zip from the phone itself.
3) Same as 1 but stock kernel+recovery.
Here's how to do it:
1) Install Samsung Kies software on your computer. It installs usb drivers necessary to communicate to the phone.
2) Install odin software on your computer. Download .tar file for kernel+cwm.
3) Open odin, follow directions in the first thread to point to the .tar file you download from the same thread.
4) Shut down phone. Use key combination to reboot the phone into "download mode". Connect phone to computer with usb cable. Use odin on computer to commence flash of .tar file. Phone will reboot.
5) Download su.zip from the first thread. Place it on usb storage of the phone.
6) Shut down phone again. Hold down Volume Up and power buttons until you see orange menu. That's CWM recovery.
5) Choose install .zip from sdcard (it really installs from usb storage, not from sdcard). Choose select zip on sd card. Navigate to su.zip, confirm.
Then use the menus to go back and reboot the phone.
6) Download stock kernel+recovery from second thread. Start from step 3 above to flash the stock .tar file.
EDIT: Oh yeah, there's a video in the first thread. Not sure how useful it is though.
EDIT2: The video is old. It has conflicting information with the stuff in the first thread. Use it very cautiously, use the links to download from the first thread. You also don't need .pit file. Only .tar files.
EDIT3: these are the file links:
Kies: link
odin: http://forums.acsyndicate.net/ACS/Odin3 v1.85.zip
CWM+kernel .tar: http://forums.acsyndicate.net/ACS/acs-eb30-clockwork-epic-touch-4g-sep-20-4-00-pm.tar
su.zip: http://www.multiupload.com/TD3X6TM9O1
stock .tar: http://www.inspiringandroid.com/mirrors/devices/epic4gtouch/kernels/acs-eg30-stock-kernel-pulled.tar
Thanks! I'll give it a try.
I installed KIES it says "reconnect the device in Samsung Kies (PC Studio) mode. Current connection mode not supported by Kies. I'm not sure how to connect it in Samsung Kies mode.
Odin 1.85 shows it connected as ID0 (com5)
I only have auto reboot selected and the check for PDA as well as the acs-eb30 ewm file.
The phone says downloading but the first box in odin says fail.
Not sure if it is safe to reboot phone.
To answer a question you asked earlier, if you root and take an OTA update the chances are very good you'll lose root. If you're rooted and want to stay that way, wait until devs work with the update and come up with a "root-safe" version.
.....
boe said:
Thanks! I'll give it a try.
I installed KIES it says "reconnect the device in Samsung Kies (PC Studio) mode. Current connection mode not supported by Kies. I'm not sure how to connect it in Samsung Kies mode.
Odin 1.85 shows it connected as ID0 (com5)
I only have auto reboot selected and the check for PDA as well as the acs-eb30 ewm file.
The phone says downloading but the first box in odin says fail.
Not sure if it is safe to reboot phone.
Click to expand...
Click to collapse
You don't need to run kies to use Odin. Kies is only installed for usb drivers.
I'm not sure what would happen if you had both running at the same time.
If you want to use Kies later, you would need to uncheck USB Debugging on the phone in Settings/Applications/Development.
The phone says "downloading" regardless of whether it is flashing the kernel or not. Did you follow the instructions from the first thread?
4. Open Odin3 V1.85 and on the left side ONLY have AUTO reboot checked (VERY IMPORTANT)
6. Check the PDA slot and then press the PDA button and navigate to the Tar file and select it
7. Now power off your Epic Touch.
8. Once fully powered off, press and hold volume down, home key, and power button at the SAME time.*This will take you into Odin mode.
9. Plug your phone into your PC.
10. You should see COM# (the number doesn't matter) in the ID:COM box
11. Press start and let it run through the process!*
Click to expand...
Click to collapse
There's a step missing, but I suppose they didn't mention it since it's fairly obvious. I don't know if it matters...
The step is 8a) When you see odin prompt to continue, confirm to enter odin mode.
Also make sure that those .tar files downloaded correctly.
Thanks - you nailed it. If you have kies running you can't get odin to update the phone. My phone is all updated - ran all the steps.
Do I use a built in app on it for tethering or add an app?
boe said:
Thanks - you nailed it. If you have kies running you can't get odin to update the phone. My phone is all updated - ran all the steps.
Do I use a built in app on it for tethering or add an app?
Click to expand...
Click to collapse
I think you need Wifi Tether. Search for it, it's gonna be on code.google.com. I myself don't use it, but I heard it works pretty much out of the box w/o tweaking.
nabbed said:
I think you need Wifi Tether. Search for it, it's gonna be on code.google.com. I myself don't use it, but I heard it works pretty much out of the box w/o tweaking.
Click to expand...
Click to collapse
My sonicwall client works great with root access. I haven't been able to get the wifi tether to work yet. I can't find the device if I enable security. I can't seem to find the right BT drivers when my computer finds it via BT. If I disable security I can findi it via wifi but with our without acccess control disabled I can't actually complete the wifi connection.
Update - I did get it to connect via tether after all. I hadn't ever had an issue connecting to about 20 wireless networks with my laptop but I did notice a 5002 event churning away in the event viewer when I tried to connect. I updated my wireless drivers and I'm all set!
Thanks for all the help and patience!!!

Can't Odin from FB27!

Hey guys,
I installed FB27 + radio through CWM. I was previously on EL29. I want to get back to EL29, so I did the following:
Boot into windows (daily driver is osx)
Put phone into DL mode
Start Odin-oc el29
connect phone to usb
watch as nothing happens, then windows says, "Unrecognized device (code 42)"
So i closed out everything, then opened Kies. It said it had an update, so I installed it, which included some driver updates.
I retraced my steps from above.
I tried installing the samsung driver package, still nothing.
Odin was working just fine before, and I hadn't changed anything in windows. I don't even use windows unless i'm using odin!
Any help is appreciated, I would like to get back to EL29!
[update]
This is likely a windows problem, not a problem with FB27. Sorry for causing any panic
few questions
what version of odin/are you using the self-extracting auto odin back?
http://forum.xda-developers.com/showthread.php?t=1433101
have you removed the kies/samsung drivers, then reinstalled? if you're having problems and it's related to the drivers (which it may be), sometimes you have to remove not just reinstall.
also, have you tried a different usb cord? sounds stupid i know, but they get **** stuck in the ends, or otherwise damaged, and cause weird issues in situations like this but otherwise work fine.
i just odined back last night using the package in the thread above, and it worked fine.
Just to make sure, you do have samsung kies installed, right? You need their drivers.
exabrial said:
Hey guys,
I installed FB27 + radio through CWM. I was previously on EL29. I want to get back to EL29, so I did the following:
Boot into windows (daily driver is osx)
Put phone into DL mode
Start Odin-oc el29
connect phone to usb
watch as nothing happens, then windows says, "Unrecognized device (code 42)"
So i closed out everything, then opened Kies. It said it had an update, so I installed it, which included some driver updates.
I retraced my steps from above.
I tried installing the samsung driver package, still nothing.
Odin was working just fine before, and I hadn't changed anything in windows. I don't even use windows unless i'm using odin!
Any help is appreciated, I would like to get back to EL29!
Click to expand...
Click to collapse
From your post you're trying to do the odin all in one self extractor... have you tried just using odin to flash the EL29 stock recovery repack and then flash through CWM from there?
http://forum.xda-developers.com/showthread.php?t=1390393&highlight=rogue
http://goo-inside.me/kernels/TeamRo.../rogue_ET-recoveryonly-1.1.4-rc0-odin.tar.md5
exabrial said:
Hey guys,
I installed FB27 + radio through CWM. I was previously on EL29. I want to get back to EL29, so I did the following:
Boot into windows (daily driver is osx)
Put phone into DL mode
Start Odin-oc el29
connect phone to usb
watch as nothing happens, then windows says, "Unrecognized device (code 42)"
So i closed out everything, then opened Kies. It said it had an update, so I installed it, which included some driver updates.
I retraced my steps from above.
I tried installing the samsung driver package, still nothing.
Odin was working just fine before, and I hadn't changed anything in windows. I don't even use windows unless i'm using odin!
Any help is appreciated, I would like to get back to EL29!
Click to expand...
Click to collapse
If regular ODIN is working fine, look in the 2nd post, section #A2. There are regular ODIN packages for EL29.
http://forum.xda-developers.com/showthread.php?t=1433101
Personally I would try to figure out why ODIN OneClick isn't working because it might indicate some problem, but I understand if someone wants the quickest solution.
Use another cable besides samsungs crappy pos
Sent from my SPH-D710 using Tapatalk
Also try a simple reboot. Sometimes if I run sfhub's one click then Odin I have to reboot in between but only sometimes
Sent from my Nexus S 4G using xda premium
sfhub said:
If regular ODIN is working fine, look in the 2nd post, section #A2. There are regular ODIN packages for EL29.
http://forum.xda-developers.com/showthread.php?t=1433101
Personally I would try to figure out why ODIN OneClick isn't working because it might indicate some problem, but I understand if someone wants the quickest solution.
Click to expand...
Click to collapse
I have used EL29, EG30 of yours several times without any problems sfhub. I don't know why I occasionally need to reboot in between one click and regular Odin but its no big deal. 90% of the time I dont
Sent from my Nexus S 4G using xda premium
exabrial said:
watch as nothing happens, then windows says, "Unrecognized device (code 42)"
Click to expand...
Click to collapse
According to Microsoft, code 42 means there is a problem with multiple instances of the driver and the solution is a reboot (as John pointed out)
My theory as to why it is happening is there is a problem either in the USB driver or in ODIN OneClick with shutting down the USB bus when the flash is done, so next time you run it there is already an instance. Another possibility is if you use different USB ports on the computer between sessions, then the USB driver might get confused and keep multiple instances.
http://support.microsoft.com/kb/310123
Code 42
Windows cannot load the device driver for this hardware because there is a duplicate device already running in the system. (Code 42)
Recommended resolution
A duplicate device was detected. This error occurs when a bus driver incorrectly creates two identically named sub-processes (known as a bus driver error), or when a device with a serial number is discovered in a new location before it is removed from the old location. You may be able to resolve this problem by restarting your computer.
Restart your computer
Click Start, click Shut Down, and then select Restart in the Shut Down Windows dialog box to restart the computer.
Click to expand...
Click to collapse
Ok, so the best thing to try then is to uninstall Kies and the samsung driver package. I'm a windows nub, (I've haven't used windows since 1999) how do I make sure that any existing drivers that have been installed for a particular port are also wiped out? My fear is that removing kies won't remove any drivers that have been installed against a particular device... or is that not true.
exabrial said:
Ok, so the best thing to try then is to uninstall Kies and the samsung driver package. I'm a windows nub, (I've haven't used windows since 1999) how do I make sure that any existing drivers that have been installed for a particular port are also wiped out? My fear is that removing kies won't remove any drivers that have been installed against a particular device... or is that not true.
Click to expand...
Click to collapse
I don't think you should have to do all of that. Where EXACTLY are you in the process?
Sent from my SPH-D710 using xda premium
JohnCorleone said:
I don't think you should have to do all of that. Where EXACTLY are you in the process?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Same as my initial post. I'm currently at work Just trying to develop a POA.
According to MSFT, the error code 42 is not a problem with driver installation. It is a problem at runtime with multiple instances of the driver.
Did a reboot not work? Perhaps there are problems with the driver in the 64-bit and 32-bit locations?
I've rebooted the crap outta it already...
Anyway, uninstalled Kies, and samsung drivers package, and QPST for the hell of it. Rebooted, reinstalled Kies, now I get Error code 43...
I tried "search for a better driver" and pointed it to the samsung kies folder to no avail.
exabrial said:
I've rebooted the crap outta it already...
Anyway, uninstalled Kies, and samsung drivers package, and QPST for the hell of it. Rebooted, reinstalled Kies, now I get Error code 43...
I tried "search for a better driver" and pointed it to the samsung kies folder to no avail.
Click to expand...
Click to collapse
Are you on 64-bit? Sometimes the drivers need to be placed in the 32-bit location.
Have you gone over the general USB connection troubleshooting here:
http://forum.xda-developers.com/showpost.php?p=19443755&postcount=142
Sorry, I go through a lot of threads and PMs so sometimes lose track of what people tried and didn't try.
I'm not at all experienced with Mobil ODIN, but wouldn't it be possible to forego the computer completely to get back to EL29?
It depends on the situation. In this case, probably yes. Mobile ODIN needs your phone to be able to boot into Android and needs you to be rooted, which the OP probably is. ODIN can handle situations where your phone won't even boot into Android.
sfhub said:
It depends on the situation. In this case, probably yes. Mobile ODIN needs your phone to be able to boot into Android and needs you to be rooted, which the OP probably is. ODIN can handle situations where your phone won't even boot into Android.
Click to expand...
Click to collapse
True, but he doesn't sound soft bricked, which is why the thought crossed my mind.
sfhub said:
Are you on 64-bit? Sometimes the drivers need to be placed in the 32-bit location.
Have you gone over the general USB connection troubleshooting here:
http://forum.xda-developers.com/showpost.php?p=19443755&postcount=142
Sorry, I go through a lot of threads and PMs so sometimes lose track of what people tried and didn't try.
Click to expand...
Click to collapse
It's quite alright, I appreciate the help. I followed the directions in that post, and am getting the same problem... It is windows7 64bit. basically, installed the drivers to C:\Program Files (x86)\Samsung\USB Drivers
I guess I'll try mobile Odin... windows hasn't improved any over the last 10 years I see.
Can someone help me I have the same problem it happened to me about a week ago when i tried flashing one of calk's rom and then all i know is that triangle disappeared from the samsung animation and then my computer will not recognize it.I've looked here and google and cannot find a solution!!!PLEASE help me!!I've noticed people with similar problems but no help.
Also I got mobile odin and tried to unroot but I am afriad I wont be able to root again since it will not discover my device.

[Q] battery issue-- root fix, but...

Hello Everyone,
new member and first time poster here! What a community!
I've run into some serious battery drainage after installing 4.1.2 on my AT&T Note II; the battery will sometimes drain 15-20% an hour in standby mode, sometimes less but still drastically worse than before the updates when I'd get a solid day and a half. It seems to think that the SD card is constantly ejecting and so it will remount periodically-- this, I'm sure, is the chief issue. After browsing around here and googling for a couple hours last night, I've seen various "fixes" involving my external microSD card, but none of them seem to help.
Anyway, I've been wanting to root and flash a custom ROM for a while now, but have been lazy; alas, I am finally compelled to do it today. This all brings me to my question:
Why won't Win 7 recognize my note II? I know there have been many posts here at XDA regarding the terrible samsung drivers etc., yet everyone seems to be rooting their noteII, sIII etc. just fine! I've installed the correct drivers, rebooted a couple time-- nothing! I'm hoping this issue has been resolved and I'm just overlooking the thread... can anyone provide any insight? Can't wait to root my first phone!
Thanks in advance
20% per hour on standby is a ridiculous amount. .
Did you take an OTA to update the device ??
Either way. ..
That level of drainage needs a fresh start. ..for sure. .
I would consider pushing a rooted stock build via Odin first. ..to confirm your device is okay.
Verify your driver package and download Odin for the test. ..
You need to track the battery drain issue first. ..imho
gregsarg said:
20% per hour on standby is a ridiculous amount. .
Did you take an OTA to update the device ??
Either way. ..
That level of drainage needs a fresh start. ..for sure. .
I would consider pushing a rooted stock build via Odin first. ..to confirm your device is okay.
Verify your driver package and download Odin for the test. ..
You need to track the battery drain issue first. ..imho
Click to expand...
Click to collapse
solid-- that's exactly what I'll do.
Btw, maybe 15-20% is a bit inflated; that is how it feels though, I haven't really kept track or checked. I just noticed a big difference and, one morning after having snoozed my alarm on the phone, unplugging it and gone back to sleep, my fully charged note was at 80% when I opened my eyes, maybe a couple hours later. I do have odin installed but how am I to do any of that if the phone isn't recognizable?
sorry for the silly questions; I'm brand new to odin and all of this mind you-- am i missing something here?
oh, and yes- the update was OTA
With Odin...be sure you have the drivers installed and your phone is in download mode.
wahbob said:
With Odin...be sure you have the drivers installed and your phone is in download mode.
Click to expand...
Click to collapse
my phone was definitely in download mode (held vol down, power, and home).
I guess im just not sure how to install drivers with odin. I just downloaded the samsung mobile device usb drivers .exe and ran it... thanks for the reply.
Yes...download mode on the device...
If your PC drivers are set up properly....you wont have any trouble with the device being recognized.
It sounds like the drivers are messed up still....g
Edit :
Pull the drivers from the development section under the "everything" thread...and not from the general internet or kies..
and if you have kies installed....dump it....g
gregsarg said:
Yes...download mode on the device...
If your PC drivers are set up properly....you wont have any trouble with the device being recognized.
It sounds like the drivers are messed up still....g
Edit :
Pull the drivers from the development section under the "everything" thread...and not from the general internet or kies..
and if you have kies installed....dump it....g
Click to expand...
Click to collapse
went to the development board and found this thread http://forum.xda-developers.com/showthread.php?t=1987541 which just links to samsung's official site from which i downloaded my presumably faulty drivers.
hexagondun said:
went to the development board and found this thread http://forum.xda-developers.com/showthread.php?t=1987541 which just links to samsung's official site from which i downloaded my presumably faulty drivers.
Click to expand...
Click to collapse
Are you running an anti-virus program on your PC ?? I assume yes, and depending on the maker of the AV package, the program may interfere with the drivers being installed properly.
AV programs often bind critical steps in the function of drivers and views them as unsafe...
Try disabling the AV program while downloading and installing the Drivers from samsung.....g
gregsarg said:
Are you running an anti-virus program on your PC ?? I assume yes, and depending on the maker of the AV package, the program may interfere with the drivers being installed properly.
AV programs often bind critical steps in the function of drivers and views them as unsafe...
Try disabling the AV program while downloading and installing the Drivers from samsung.....g
Click to expand...
Click to collapse
well, rather than disabling, I completely uninstalled my antivirus software, then uninstalled the drivers, rebooted, reinstalled the drivers, rebooted again, and still the pc wont recognize the phone. tried it on my father's windows machine with the same results. I have never had such a hard time with drivers in my entire life. What a frustrating process!
any other suggestions?
Odublica singularly
Try a different cable.
hexagondun said:
well, rather than disabling, I completely uninstalled my antivirus software, then uninstalled the drivers, rebooted, reinstalled the drivers, rebooted again, and still the pc wont recognize the phone. tried it on my father's windows machine with the same results. I have never had such a hard time with drivers in my entire life. What a frustrating process!
any other suggestions?
Click to expand...
Click to collapse
SXBB said:
Try a different cable.
Click to expand...
Click to collapse
Agreed......
The OEM cable is preferred....g
SXBB said:
Try a different cable.
Click to expand...
Click to collapse
+1
And also what he said^^^^^^
I'll add this, if still not working then try another usb port or another computer...
It may help!
Sent from my SAMSUNG-SGH-I317 using Tapatalk 4 Beta

[Help] Another Note 4 Soft Bricked

Hello,
I know you're probably thinking, "omg another note bricked thread". Yes, but I spent many hours of research and couldn't find a thread with my exact problem.
A little background:
I rooted my phone and everything was fine and dandy. I let a friend borrow my phone for a minute and they decided that it would be funny to uninstall google play. I installed the apk from online and had nothing but problems. The app would crash as soon as i started downloading anything. I looked into solutions and did everything from editing the host file to wiping the caches. Nada. The "solutions" just caused other errors. I decided to wipe and reinstall from my backup.
I realized after that because Google Play is a system file, my restore was useless. I decided to wipe everything and reflash the stock firmware with Odin. I downloaded the right one for the verizon model on 5.1.1. Odin sent the file to the device. Just before finishing there was an error and the phone rebooted anyway.
Upon booting the phone now lacked an OS and gave the "use the verizon repair assistant to reinstall the operating system" message. I tried the software (from a friends s5) on 3 different computers and it wouldn't work on any.
I figured, no problem, I will just reflash to stock with Odin again. Only this time my computer no longer recognizes the phone when I put it into download mode. Ive installed and reinstalled the drivers, changed the order of connecting the cables, and when the phone is booted. Nothing works.
The phone can only boot regularly (but lacks an OS) or go to download mode. Recovery doesn't work. Any ideas? Help would greatly be appreciated as the nearest phone repair center is close to 40 miles away
Tl;dr
Phone doesnt have an OS, can boot to download mode, but isn't recognized by computer. The basic troubleshooting steps haven't worked.
Hi urban.. I'm not to technical, but was reading your post. I hit a little confused... Your using the s5 Verizon recovery, not Odin image right
Also try uninstalling the Windows drivers and reinstall after you connect to computer
Sent from my SM-N920V using Tapatalk
Bern612 said:
Hi urban.. I'm not to technical, but was reading your post. I hit a little confused... Your using the s5 Verizon recovery, not Odin image right
Also try uninstalling the Windows drivers and reinstall after you connect to computer
Sent from my SM-N920V using Tapatalk
Click to expand...
Click to collapse
I tried the verizon recovery for the S5 (I don't have it for the note) and the software wouldn't load. Originally I reflashed the phone with an Odin image but now Odin doesn't recognize the phone.
Yup, I've tried that many times on different computers. Thanks though.
Urban415 said:
Hello,
I know you're probably thinking, "omg another note bricked thread". Yes, but I spent many hours of research and couldn't find a thread with my exact problem.
A little background:
I rooted my phone and everything was fine and dandy. I let a friend borrow my phone for a minute and they decided that it would be funny to uninstall google play. I installed the apk from online and had nothing but problems. The app would crash as soon as i started downloading anything. I looked into solutions and did everything from editing the host file to wiping the caches. Nada. The "solutions" just caused other errors. I decided to wipe and reinstall from my backup.
I realized after that because Google Play is a system file, my restore was useless. I decided to wipe everything and reflash the stock firmware with Odin. I downloaded the right one for the verizon model on 5.1.1. Odin sent the file to the device. Just before finishing there was an error and the phone rebooted anyway.
Upon booting the phone now lacked an OS and gave the "use the verizon repair assistant to reinstall the operating system" message. I tried the software (from a friends s5) on 3 different computers and it wouldn't work on any.
I figured, no problem, I will just reflash to stock with Odin again. Only this time my computer no longer recognizes the phone when I put it into download mode. Ive installed and reinstalled the drivers, changed the order of connecting the cables, and when the phone is booted. Nothing works.
The phone can only boot regularly (but lacks an OS) or go to download mode. Recovery doesn't work. Any ideas? Help would greatly be appreciated as the nearest phone repair center is close to 40 miles away
Tl;dr
Phone doesnt have an OS, can boot to download mode, but isn't recognized by computer. The basic troubleshooting steps haven't worked.
Click to expand...
Click to collapse
Had a similar experience myself. I also tried using the Verizon update/repair assistant for another device and it did not work. I ultimately ended up borrowing a Note 4, installing the upgrade/repair assitant from that phone onto my pc (enable USB autoplay, then choose to install the software that runs when you connect the phone). The software installed from another Note4 was able to repair my phone without issue.
Tepidlake said:
Had a similar experience myself. I also tried using the Verizon update/repair assistant for another device and it did not work. I ultimately ended up borrowing a Note 4, installing the upgrade/repair assitant from that phone onto my pc (enable USB autoplay, then choose to install the software that runs when you connect the phone). The software installed from another Note4 was able to repair my phone without issue.
Click to expand...
Click to collapse
Interesting. Was your computer unable to recognize the phone as well? How did you borrow another Note 4? I have scoured the internet and haven't been able to find the software online. Would you be able to PM it to me? I would greatly appreciate it as I do not have immediate access to another Note.
ODIN can be finicky with USB cables and ports. Try switching cables and make sure that you're on a USB port that comes straight from the PC and not a hub.
Try uninstalling the Samsung USB driver, reboot the computer then reinstall.
I'm not sure why you were using S5 software when Note 4 is so readily available. I'm not sure that I can recommend using the Marshmallow firmware yet in ODIN. I would use the 5.1.1 version and do the full firmware flash.
what i've done.
Hello Urban415, earlier today my phone decided to take a dump as well gave me that same message with the yellow triangle, i had flashed a bad image (file name : N910VVRU2BPA1_StockRestore.tar.md5) which then gave me that problem.
//-=-=
I went onto Sam Mobile's site, created an account(its free! to download the firmware, it's needed.)
I had to download N910VVRU2BOG5 - 5.0.1 (it took me 2 hours to DL off their site :\ due to free account... but whatevs)
In order to bring my phone back to life also the version of Odin i used was 3.10.6..
My phone was rooted as well and was using N910VVRU2BPA1 - 5.1.1
//-=-=
Hope this helps ! My note 4 Model # : Sm-n910v, bought refurb off ebay.
P.S. Excuse my grammar, punctuation, etc, etc. Also! running Windows 7 x64 and Verizon's assistant didn't work for me either. not even on my windows 8.1 laptop =x!
douger1957 said:
ODIN can be finicky with USB cables and ports. Try switching cables and make sure that you're on a USB port that comes straight from the PC and not a hub.
Try uninstalling the Samsung USB driver, reboot the computer then reinstall.
I'm not sure why you were using S5 software when Note 4 is so readily available. I'm not sure that I can recommend using the Marshmallow firmware yet in ODIN. I would use the 5.1.1 version and do the full firmware flash.
Click to expand...
Click to collapse
I have tried with 2 cords, and am not using a hub. I also already uninstalled, rebooted and installed. Anything else?
The S5 software is only the verizon restore assistant because that is the only samsung software I had available to me. I am not using the firmware for that phone on my note. I tried to do the full 5.1.1 firmware flash, but can only do that when my computer recognizes the device.
SolFox84 said:
Hello Urban415, earlier today my phone decided to take a dump as well gave me that same message with the yellow triangle, i had flashed a bad image (file name : N910VVRU2BPA1_StockRestore.tar.md5) which then gave me that problem.
//-=-=
I went onto Sam Mobile's site, created an account(its free! to download the firmware, it's needed.)
I had to download N910VVRU2BOG5 - 5.0.1 (it took me 2 hours to DL off their site :\ due to free account... but whatevs)
In order to bring my phone back to life also the version of Odin i used was 3.10.6..
My phone was rooted as well and was using N910VVRU2BPA1 - 5.1.1
//-=-=
Hope this helps ! My note 4 Model # : Sm-n910v, bought refurb off ebay.
P.S. Excuse my grammar, punctuation, etc, etc. Also! running Windows 7 x64 and Verizon's assistant didn't work for me either. not even on my windows 8.1 laptop =x!
Click to expand...
Click to collapse
Glad that you got your device to work. Thanks for the information about the Verizon assistant software. Guess it's not just me.
My problem isn't the firmware and finding it online. My problem is that my computer now refuses to recognize the phone as a usb device. I have tried the usual recommended troubleshooting steps to no avail. Did you have this problem?
I'm reaching about as far as I can go, but: did you try to do a factory reset in recovery? I had that work in freeing up a connection issue in ADB once.
@Urban415 I was googling and found one guy who had a similar issue as you... It was for an older device. But what he did was uninstalled the assistant. Then plugged in his phone and reinstalled the software and it installed the correct drivers... Also I'm not to android savvy, but just a thought. If your using the s5 assistant wouldn't it have to download a note 4 image for it to recognize it. Maybe that's why it's not working. Because it doesn't have the note 4 drivers and image??? Just a thought
Sent from my SM-N920V using Tapatalk
Just saying this on top of my head but I have seen system images for the system itself and another with the firmware included. Maybe try the one with the firmware included?
Sent from my SM-N910V using Tapatalk
Urban415 said:
Interesting. Was your computer unable to recognize the phone as well? How did you borrow another Note 4? I have scoured the internet and haven't been able to find the software online. Would you be able to PM it to me? I would greatly appreciate it as I do not have immediate access to another Note.
Click to expand...
Click to collapse
Hey, sorry it took so long to get back.
As I recall my phone was not visible to ADB or Kies while it was displaying the Verizon Repair Assistant screen erreor screen. I suspect that in that state, only the Repair Assistant is able to talk to the phone.
I ended up waiting for my wife to get home (she has the same phone as me) and borrowing her phone to install the assistant software. The software recognized my phone, though it took a minute or two, even though Kies couldn't see it. The assistant downloaded the firmware and flashed it. Phone good as new.
Urban415 said:
I have tried with 2 cords, and am not using a hub. I also already uninstalled, rebooted and installed. Anything else?
The S5 software is only the verizon restore assistant because that is the only samsung software I had available to me. I am not using the firmware for that phone on my note. I tried to do the full 5.1.1 firmware flash, but can only do that when my computer recognizes the device.
Glad that you got your device to work. Thanks for the information about the Verizon assistant software. Guess it's not just me.
My problem isn't the firmware and finding it online. My problem is that my computer now refuses to recognize the phone as a usb device. I have tried the usual recommended troubleshooting steps to no avail. Did you have this problem?
Click to expand...
Click to collapse
similar thing happened to me but on my 2013 nexus 7. I had to download and use "Minimal ADB and Fastboot" and manually (using Commands within windows command-line-interface) restore my device while it was in "fastboot mode". prior to that tried using "WUGsNexus Root ToolKit " which help instruct the user; with screenshots on how to uninstall drivers that might conflict with one another with the use of another program named "USBDeview". that didn't work for me unfortunately . but for i cannot for sure say if its a "Maybe my windows need a refresh/clean slate" or I missed a step.
Thank you to everyone that helped me in this thread. After trying several new cables, uninstalling and re-installing drivers, rebooting, and playing around with software compatibility software, my problem has been solved.
I have now reflashing stock firmware, rooted, and backed up the phone. Cheers!

Categories

Resources