Related
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.
Hi guys. Im a noob, first post here and need some help. Be searching all day for how to load a stock rom to my device GT-N5110.
Heres the low down.
Purchased in Australia. No updates applied.
Success rooted with framaroot.Was running framaroot for more than a month
Install busy box today in normal mode I think. I chose the safe option.
Edited build.prop product model so I could install Navigon
Navigon working fine
Now..........
Unable to change the product name back using es explorer or file expert.
Thought it would change after restart but device entered bootloop. I think busybox was the culprit.
Discovered recovery mode and did factory data reset. Can acces odin screen on device too.
Device boots but hangs on language selection screen
I have found and downloaded stock rom for it that I found here somehow
I tried "Mrjraider" tutorial "how to flash back to a stock rom"
but odin crashes whenever I load the rom file and it wont recognize my GN8.0
Computer runs on windows 8. Kies is up to date too. Kies reconizes device but is unable to update or anything
Was running odin in win xp sp3 with administrator
can try on a win7 computer tomorrow.
This is the name of the file its about 1.2 Gb....... N5110UEDMD1_N5110XARDMD1_HOME.tar.md5 do I need to rename this or something
There was also a .dll that was in the package, wtf with that?????
be looking through this forum all day and night and cant quite find what im looking for. If what I seek is here please point me to it. Or if any one here in Brisbane, can fix it for me,What are your thoghts? PM me.
Just want my baby back working again.
Sorry, wrong section please delete mod
If I'm not mistaken, remove Kies, then try using Odin. Also, dll is a Windows file. I could be wrong about Kies, but I think I remember reading that it conflicts with Odin.
Sent from my SGH-T889 using Xparent Skyblue Tapatalk 2
Yesterday I installed same firmware in my computer runing win7 with Odin and Kies installed at the same time without problems. You don't need to rename the file, dll is a library for windows and needs to be on the same folder as the md5 file. Just remember to put the Note in download mode in order to get the firmware installed by Odin.
I have a thread in the development forum with the only file you need just flash in odin and done.
Sent from my GT-N5110 using Tapatalk 2
Tutorial is ok, problem seems to be elsewhere.
I have Windows 8 (x64) too, and Odin works i my case, i successfully flashed (and restored counter) N5110 before returning tablet to shop (it was exchange for N5100). Kill all Kies components via task manager, i have two more things in processes when i quit Kies. Next, try another version of Odin, but I remember one ROM from SamMobile, which crashed every Odin i had, so its may be this problem. Try another version of ROM - older, if exists. If crashes Odin too or not exists, try uninstall both Kies and Samsung USB driver, dowload toolkit from xda (http://forum.xda-developers.com/showthread.php?t=2251033) and install new driver via toolkit.
In rare cases may be problem in your computer, so try another one without installing Kies. I wish you luck.
Edit - That big file is ROM, dll is not needed for Odin. Run Odin, press PDA, select your rom. Turn tablet off, connect to comupter by original or hi-quality short cable, set tablet into download mode (hold vol- and home, press power on for 2 secs, select continue by pressing vol+). If all is ok, first field in Odin change color to yellow (i think), then press "Start".
Thanks to all. Let you know how I go. Odin 4.43 keeps crashing when loading the rom, on both my win8 laptop and fresh installed win 7 pc. Uninstalled everything from laptop except nero. Nothing installed on pc except modem drivers and Samsung drivers. I will redownload the rom. I think it may have become corrupt. Cheers
ok success. this is what I did. eventually got the rom to sit in odin without crashing it by simply renaming file by deleting the .tar.md5 extention. clicked off the file to save the rename. Right click on it again to rename and type the extension back in. Loaded it in odin and it worked. File name in odin showed up with duplicate file extention eg .tar.md5.tar.md5 but it worked. Odin 4.43 would not detect my device. Senior Moderator Mskip toolkit for Samsung galaxy note 8 would not detect my device .This was very frustrating
Used odin 3.07
loaded rom in pda. Found in janjannsen99 development thread.
connected device ,odin 3.07 detected it, unlike 4.43 for some reason.
clicked start.
Walla. Im a happy man.
This is the kind of story that are the most scary. Now I am kind afraid of root my note 8 or do anything unofficial.
Anyway, best wishes to you.
mickatron said:
Thanks to all. Let you know how I go. Odin 4.43 keeps crashing when loading the rom, on both my win8 laptop and fresh installed win 7 pc. Uninstalled everything from laptop except nero. Nothing installed on pc except modem drivers and Samsung drivers. I will redownload the rom. I think it may have become corrupt. Cheers
ok success. this is what I did. eventually got the rom to sit in odin without crashing it by simply renaming file by deleting the .tar.md5 extention. clicked off the file to save the rename. Right click on it again to rename and type the extension back in. Loaded it in odin and it worked. File name in odin showed up with duplicate file extention eg .tar.md5.tar.md5 but it worked. Odin 4.43 would not detect my device. Senior Moderator Mskip toolkit for Samsung galaxy note 8 would not detect my device .This was very frustrating
Used odin 3.07
loaded rom in pda. Found in janjannsen99 development thread.
connected device ,odin 3.07 detected it, unlike 4.43 for some reason.
clicked start.
Walla. Im a happy man.
Click to expand...
Click to collapse
That's what I use odin 3.07 . Don't use the other versions for some reason they don't work
Secondly guys when you download that file in my thread tO your computer it has to be extracted first you only Click PDA In ODIN and use the file you just extracted with the tar md5 extension. Thats it. That ss.dll file has no purpose its just there and you need not even bother with it.
Sent from my GT-N5110 using Tapatalk 2
I am also trying to restore my US-based Note 8.0 WIFI (still on 4.1.2), but couldn't figured out which ROM file I need to download.
Could you tell me the filename? I am using the Note 8.0 toolkit.
ROM
lanwarrior said:
I am also trying to restore my US-based Note 8.0 WIFI (still on 4.1.2), but couldn't figured out which ROM file I need to download.
Could you tell me the filename? I am using the Note 8.0 toolkit.
Click to expand...
Click to collapse
Will these two links help you:
Link 1
Link 2
AkiOrpheus said:
Will these two links help you:
Link 1
Link 2
Click to expand...
Click to collapse
I have checked that, but I don't see US Note 8.0. The search seems broken to, since United States is not shown in the list of country for Note 8.0
No one knows how to get the stock US based ROM?
lanwarrior said:
No one knows how to get the stock US based ROM?
Click to expand...
Click to collapse
@lanwarrior
U have to register on sammobile.com to download firmwares (stock ROM). Put the model as SGH-i467 and u will the file
AkiOrpheus said:
Will these two links help you:
Click to expand...
Click to collapse
people keep posting to go to sammobile but every time i look there isn't a rom labeled for the US, and they dont give an explanation of what rom would be the equivilant or even if any of them would be. Should I use UK version? is it the same as the US?
I'm having the same exact issue as OP and I can get into download mode and i have odin 3.07 but i am just looking for the exact rom to load and cant find an exact answer so far. I've already messed up my tablet enough today so I don't want to flash the wrong rom and make things worse lol.
K
O
F
ps I looked for janjansen's thread in development and did not see it, am I missing something? anyone got a link?
ok I did some more reading around the web and found that a lot of people used the UK version as I kinda suspected. Would have been nice to get confirmation on that but its cool, I flashed it, no problem, and now I'm setting up the chainfire root and getting back all my apps. So all in all it took a few days but I'm back on my feet *sigh of relief*
K
O
F
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!