Related
I tried to use the previous version of kies to upgrade my gs2 but it never worked. Update would be from:
[KF3/phone:ke7/csc:KD1] to [KI4/phone:KI1/csc:kh2]
Which I'm sure is a big step forward as I haven't been able to update forever. I thought that once I updated Kies I'd finally be able to update my phone. Now when I connect my s2 and hit update firmware, as soon as it asks to backup it loses the connection to the s2. I've reinstalled drivers twice to no avail.
Does Kies just blow as a software or am I doing something wrong.
Kies blows big time - utterly useless... useless at upgrading, useless at backing up. According to their twitter @samsungkies - "Seamless experience with Smarter Kies". That's a joke of a statement. Go with Odin my friend, much less aggro and it works all the time.
^ I so much agree to that post.
Kies never worked for me, not even when my SGS II was used with the stock rom that shipped with it. While there was an update out for quite a long time (> 1 month) it still was showing my version as being current.
Odin is so much better or just as simple: flashing from CWM.
husaam said:
Kies blows big time - utterly useless... useless at upgrading, useless at backing up. According to their twitter @samsungkies - "Seamless experience with Smarter Kies". That's a joke of a statement. Go with Odin my friend, much less aggro and it works all the time.
Click to expand...
Click to collapse
I briefly looked at Odin not too long ago, it looked sort of confusing. I'm in another country currently and spend most of my time either (50+ hours a week) working on projects here or exploring the country. As such I don't have much time to learn a new program if it's too confusing. But I'll give it a try and hopefully get to say goodbye to kies forever.
edit: Do I need to root* my s2 to use odin?
aDroidtoRemember said:
I briefly looked at Odin not too long ago, it looked sort of confusing. I'm in another country currently and spend most of my time either (50+ hours a week) working on projects here or exploring the country. As such I don't have much time to learn a new program if it's too confusing. But I'll give it a try and hopefully get to say goodbye to kies forever.
Click to expand...
Click to collapse
It's actually quite simply. Most ROMS come with only one file. That can be flashed via PDA. Do NOT, I repeat, do NOT, I repeat once again, do NOT, and again: do NOT! tick ANY option in ODIN, unless stated specifically in the ROM's instructions and even then tripple check that you're really about to flash a SGS II firmware.
So as long as you get the right firmware, do not tick anything and just flash it via PDA you should be quite safe. There's always a minimal risk, even if you do everything right but it's very very small.
Try This!
RUN Kies onces its loaded connect phone it will say connecting phone within a short period of time and error message will load, click onto the error message a new window will open, now it will have something like 4 stages. 1st stage will say disconnect cable from phone, once you have done this click on next or the follow up stage. Now this will or should Repair drivers, and now install drivers again once this has been done connect phone and phone will now load in Kies.
XP users may have to reboot PC for driver take effect.
Hope this hepls you.
PS:THIS problem only happen to me on live update, download new kies manually install no problems. Win 7 64bit
Looking at Odin for the first time can be a bit confusing. Once you know the score tho its very easy and quick. Flashing intras files for example is a complete doddle as it's 1 tar file
Sent from my GT-I9100 using xda premium
Nyssa1104 said:
RUN Kies onces its loaded connect phone it will say connecting phone within a short period of time and error message will load, click onto the error message a new window will open, now it will have something like 4 stages. 1st stage will say disconnect cable from phone, once you have done this click on next or the follow up stage. Now this will or should Repair drivers, and now install drivers again once this has been done connect phone and phone will now load in Kies.
XP users may have to reboot PC for driver take effect.
Hope this hepls you.
PS:THIS problem only happen to me on live update, download new kies manually install no problems. Win 7 64bit
Click to expand...
Click to collapse
I've reinstalled the drivers using the connection error troubleshoot, and the phone connects fine to kies. It just loses connection to kies when I try to update the firmware. When I have more time I will most likely just use Odin but I don't want to root my phone in order to do it. Is rooting necessary?
Once you get your head around Odin, its a piece of cake.
Look for Intratech's Official i9100 Firmwares thread in the Original Android Development section, you'll find everything you could possibly need in there (instructions, firmwares etc)
aDroidtoRemember said:
I've reinstalled the drivers using the connection error troubleshoot, and the phone connects fine to kies. It just loses connection to kies when I try to update the firmware. When I have more time I will most likely just use Odin but I don't want to root my phone in order to do it. Is rooting necessary?
Click to expand...
Click to collapse
OK Odin is easy just read the Q&A
link pls...
i just upgraded to 2.1 also and now can't upgrade firmware, just keeps looping in disconnecting and reconnecting never upgrading firmware
Since nobody answered yet... No u don't needa root to get Odin work
Sent from my GT-I9100 using Tapatalk
i have had the same connect - disconnect or backup problems with kies (my version is 2.0.3) and have always blamed it on kies but once i tried to restart the phone, everything worked smoothly and i could do all kinds of operations with it. My phone is rooted and the current fw version is XWKJ1 original.
Sent from my GT-I9100 using XDA App
mertakb said:
i have had the same connect - disconnect or backup problems with kies (my version is 2.0.3) and have always blamed it on kies but once i tried to restart the phone, everything worked smoothly and i could do all kinds of operations with it. My phone is rooted and the current fw version is XWKJ1 original.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
you're are correct for 2.0.3 but the new 2.1 is totally screwed up, crashed my windows even
Gavin.csy said:
i just upgraded to 2.1 also and now can't upgrade firmware, just keeps looping in disconnecting and reconnecting never upgrading firmware
Click to expand...
Click to collapse
Just read a solution that works for me on the Dutch tweakers.net website:
- In Windows fully uninstall Kies.
- Download the latest Kies version and reinstall.
After that the upgrade worked for me.
janderk said:
Just read a solution that works for me on the Dutch tweakers.net website:
- In Windows fully uninstall Kies.
- Download the latest Kies version and reinstall.
After that the upgrade worked for me.
Click to expand...
Click to collapse
do you have the link for the download, i still find 2.0.3 only, nothing directly 2.1
Windows 7pro (32bit) absolutely none of the problems listed here or on other threads (regardless of stock/custom anything) but.. Odin is easy if you follow instructions and seems much more reliable (see intratechs thread in dev section for instructions)
Sent from my GT-I9100 using xda premium
It finally worked for me, i don't know what happened why it suddenly decided to work/
One difference i noticed is i got a notification 'Samsung Modem succesfully installed' which i did not get for the past 2 hours of restarting,uninstalling ,installing. It just suddenly came when i connected the phone
Kies is really crazy as hell
I think you may just have to turn off your anti-virus/firewall software while you update. It worked for me.
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
SOLVED: see post #5 & #8
I've been trying to root my T807T and everyone with one on the forums here has reported that all T805 stuff works just fine on it.
I have installed USB drivers, USB Debugging set to on. Been using Odin 3.07 as well as 3.09.
I tried multiple USB ports and two computers and a whole lot of different wires (including original ones).
I disabled my Anti-virus and do not have Kies installed.
I am not a newbie to flashing and have been rooting Samsungs since the first Galaxy S Vibrant all those years ago. I have never seen anything like this.
Everything I try to flash in Odin comes up with FAIL! after about halfway through flashing. I can restart my tablet and everything works fine, but this is making it impossible to root.
FAIL occurs right after "NAND Write"
Any/all help is very much appreciated. If anyone is NYC local and can give it a shot, that'd be great.
Thanks everyone.
I would suggest taking a look at this thread. http://forum.xda-developers.com/showthread.php?p=54393309
Install kies and reinstall drivers with kies probably would help?
DUHAsianSKILLZ said:
I would suggest taking a look at this thread. http://forum.xda-developers.com/showthread.php?p=54393309
Install kies and reinstall drivers with kies probably would help?
Click to expand...
Click to collapse
I've read that thread before, not the same issue. But thanks for the heads up nevertheless
postulio said:
I've read that thread before, not the same issue. But thanks for the heads up nevertheless
Click to expand...
Click to collapse
I would uninstall the drivers and try to install the drivers from kies. Other than that, Im not sure why it wouldnt work.
I have been digging a lot on the issue. Of course I haven't been able to find a whole lot other then it appears 95 percent of these nand write issues are with samsung devices. Make sure that in settings>general>security reactivation lock is OFF. Also try removing your SIM card and the SD card if you have one. Then proceed to flash. We have the exact same model, firmware, build, etc etc. I can't think of a logical reason why it won't work. I'd be inclined to believe it's a communication issue between tablet and computer at this point. Completely stumped on this one however I will keep digging for you.
DUHAsianSKILLZ said:
I would uninstall the drivers and try to install the drivers from kies. Other than that, Im not sure why it wouldnt work.
Click to expand...
Click to collapse
no go.
postulio said:
no go.
Click to expand...
Click to collapse
Does your tar have .md5 at the end of the filename? I think it should fail earlier if this is the problem but maybe its not being properly verified? Its just a shot in the dark but try removing the .md5 if its there and just flash the straight .tar file. Or retry download maybe you got a corrupt copy.
Sent from my Nexus 7 using XDA Free mobile app
Ripx88 said:
I have been digging a lot on the issue. Of course I haven't been able to find a whole lot other then it appears 95 percent of these nand write issues are with samsung devices. Make sure that in settings>general>security reactivation lock is OFF. Also try removing your SIM card and the SD card if you have one. Then proceed to flash. We have the exact same model, firmware, build, etc etc. I can't think of a logical reason why it won't work. I'd be inclined to believe it's a communication issue between tablet and computer at this point. Completely stumped on this one however I will keep digging for you.
Click to expand...
Click to collapse
HAHAHAHA BINGO!!!!
woooo!
cfautoroot: BAM! worked first try.
everybody dance.
Thank you very much for this genius tidbit. I must've enabled it the first day I got the tablet and forgot all about it as It's never been an option on any of my other devices.
Huge thanks to both of you guys for bending over backwards trying to find a solution as to why the flashing wasn't working. Now we know.
Pretty clever of Samsung to hide an Odin flash lockout switch within the actual OS (as opposed to recovery).
I need to restore my Tab S. I installed Windows on Parallels in order to root it and have been using CM12.
Now no matter what I do Odin fails to see my Tab when in download mode so I can't use it (I've spent all day doing everything forums reccomend - swapping cables, ports, un/installing KIES, blah, blah - 'Windows sees the Tab, but Odin just does not. Heimdall on the Mac just does nothing as it needs a PIT file I don't have and can't find.
Isn't there a way to restore stock firmware with TWRP? Or a rooted near stock ROM that I can unroot?
Any help would be much appreciated.
zemblance said:
I need to restore my Tab S. I installed Windows on Parallels in order to root it and have been using CM12.
Now no matter what I do Odin fails to see my Tab when in download mode so I can't use it (I've spent all day doing everything forums reccomend - swapping cables, ports, un/installing KIES, blah, blah - 'Windows sees the Tab, but Odin just does not. Heimdall on the Mac just does nothing as it needs a PIT file I don't have and can't find.
Isn't there a way to restore stock firmware with TWRP? Or a rooted near stock ROM that I can unroot?
Any help would be much appreciated.
Click to expand...
Click to collapse
I feel your pain, but I think a full windows installation is the only way to get round this. I've tried windows in a Virtualbox and had the same results as you. Googling shows TWRP can restore a backup but I can't see any option to load stock and there's nowhere I can see to download a PIT file
But would this be worth a try? http://www.samsung.com/uk/support/usefulsoftware/KIES/
I take it then you didn't make a full backup in recovery, which is sort of the whole point in flashing it in the first place?
Your issue could be a missing driver.
Reinstall the Samsung driver on the host and make sure it is the guest operating system that is connecting to the usb port not the host.
Also do you know Windows can be installed to a usb drive?
http://lifehacker.com/how-to-run-a-portable-version-of-windows-from-a-usb-dri-1565509124
Mahasamatman said:
I feel your pain, but I think a full windows installation is the only way to get round this. I've tried windows in a Virtualbox and had the same results as you. Googling shows TWRP can restore a backup but I can't see any option to load stock and there's nowhere I can see to download a PIT file
But would this be worth a try? http://www.samsung.com/uk/support/usefulsoftware/KIES/
Click to expand...
Click to collapse
Yup I think you're right, installing Boot Camp for the 1st time. One upside is that when I've finished with Windows I'm gonna put on Ubuntu (for the first time in 10 years!), getting bored of OS X and use hardly any of the Apple apps on it anyway...
Tried KIES for Mac but it doesn't seem to recognise custom ROM'd Tabs. Cheers.
ashyx said:
I take it then you didn't make a full backup in recovery, which is sort of the whole point in flashing it in the first place?
Your issue could be a missing driver.
Reinstall the Samsung driver on the host and make sure it is the guest operating system that is connecting to the usb port not the host.
Also do you know Windows can be installed to a usb drive?
http://lifehacker.com/how-to-run-a-portable-version-of-windows-from-a-usb-dri-1565509124
Click to expand...
Click to collapse
Actually buddy methinks you're onto something. Just downloaded Samsung PC Studio and that installed a 'gadget serial' driver that ODIN seems to recognise! :laugh:
Success!
OK - posting this in case another 'me' is searching for the same. Both commenters were helpful. Thanks.
It was a weird trial and error of installing both KIES and Samsung PC studio, that installed all the necessary drivers, the restore took minutes using Odin 3.09. I also had to try a few different USB cables as it seemed choosy, so Parallels can work though it all seems a bit pot lucky!
I now have a 'fresh' install of KK. Not sure if it will show up as a Knox tripper.
The Samsung usb drivers can be downloaded here: http://www.mediafire.com/download/a4hd8y0c1iakysk/Samsung-Usb-Driver-v1.5.49.0.exe
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!