Related
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
So I offered to put a custom ROM on my wife's Galaxy S II T989, because she likes my S3. First problem was it would NOT root. It would install the superuser app but it wouldn't verify as rooted, says the su binaries were not installed... Ok. I wanted to use the CM11 Kit Kat Rom, so the instructions said that I had to be rooted so I kept looking and finally found one for su v0.92, it failed in CW recovery so I tried it using Odin, and again it failed. So I rebooted the phone to try again later and it is now stuck in a boot loop. I have read that Odin can be a little finicky so I kept trying and to no avail. I even tried Heimdall Suite and it said that it detected my device but after I tried to install the root package that way it said device could not be detected and threw an error. I couldn't figure that out, so I verified that the USB drivers were installed and they were. The forum says I have what's called a soft bricked phone and to download a recovery kernel for it and it should fix the problem, but I can't find one for android version 4.1.2.
I have tried two different USB cords, and two different USB ports and nothing. I am just so lost confused. I completely abandoned Android after Froyo and went to a Windows Phone for over 2 years but recently came back because of the lack of app support. I used to flash ROMs on my LG Optimus T all the time without a problem. Things have changed I guess. I'm pretty sure that my wife is going to have a cow when she wakes up this morning. Any help that anyone can provide would be most helpful. Thanks in advance!
So I fixed the problem with the boot loop. Odin finally wanted to cooperate this time. I downloaded a stock time and extracted the md5 file out of it and flashed it using Odin v1.85 with defaukt options checked and it worked! I hope this helps someone who was having the same problem I was with the Galaxy T989.
Sent from my SGH-T999 using xda app-developers app
Hi guys,
I've just rooted my Galaxy Tab S 10.5 and I'm trying to flash in a firmware downloaded from Sammobile, I've tried to use Odin 3.07 and 3.09 but in both always appears to me a FAIL message, I've tried to plug and unplug the tablet from my pc many times but I don't know what I'm doing wrong. I followed all the instructions I found but nothing happens.
Have you tried to re-downloading the rom and trying again? Check if your drivers are installed correctly and the only thing I would suggest is downloading the same tab s rom but like a UK version or..
DUHAsianSKILLZ said:
Have you tried to re-downloading the rom and trying again? Check if your drivers are installed correctly and the only thing I would suggest is downloading the same tab s rom but like a UK version or..
Click to expand...
Click to collapse
Which is the best country FW with italian language support? I'm trying to upload the new FW with the same pc I've used to root my Tab S.
Regarding the odin fail. I have 3 usb ports on my laptop but only 1 works for me when using odin. Maybe you could try a different port?
do you got kies running i reinstall my note 2 did fail too but i find i got kies running in background uninstall that crap now i just samsung drive left for it
Garby81 said:
Hi guys,
I've just rooted my Galaxy Tab S 10.5 and I'm trying to flash in a firmware downloaded from Sammobile, I've tried to use Odin 3.07 and 3.09 but in both always appears to me a FAIL message, I've tried to plug and unplug the tablet from my pc many times but I don't know what I'm doing wrong. I followed all the instructions I found but nothing happens.
Click to expand...
Click to collapse
Not to sound repetitive of what others have already suggested, but there is definitely logic in re-downloading a ROM in that some downloads get accidentally corrupted in the transfer process. Hence the purpose of the md5 validity check. Also, in searching for Samsung usb drivers for the sm-t800 I came across at least 3 bundles having different drivers and quantities within them. The 1st one recognized the tablet but not Odin. The 2nd one recognized both, but Odin kept failing. Needless to say that after the 1st two bundles didn't work I thought that I had not followed the instructions carefully. That I had done something wrong, so I kept trying with those same crappy drivers again and again until someone suggested I try to download them again. I realized I hadn't tried the 3rd bundle yet. When I did, everything worked great.
In other words, never be reluctant when things fail, to try a different approach or to start all over again from scratch.
Hope this helps.
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
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!