Related
Previously I had installed on my phone (I believe, but could be mistaken) a Twilight Kernel and Hurricane v1.6 Rom. Well, I had nothing but problems with the rom, and put up with them for some time, just because I didn't have time to go through and find a rom I liked and flash it. I decided to do just that yesterday.
Apparently my mind broke and I did something wrong (probably numerous things). I had first attempted to put the shiney new CWM9 with Shadow Kernel on, rather, I made the mistake of trying to just put the Shadow Kernel on after having done a full (triple) wipe on my phone. I got the boot loop for the kernel since there was no rom (duh) loaded. Okay, no problem, I'll toss a rom on the SD and boot into CW3 and flash it? Yeah, not so much. I got a short "Samsung" logo boot loop and could not get into CW3 after that.
So, I Odin'd it back to EL30, thinking I'll just start from fresh, right?
Wrong.
Next in the series of mistakes I made, I forgot that I had already downloaded and installed the Samsung drivers (don't ask, my brain was apparently on leave yesterday) and attempted to re-install them. They did not like this and would not progress and I had to End Process the install from Task Manager. I then uninstalled the drivers completely fearing that I may have corrupted them by trying to re-install and then EP'ing them.
I then re-installed them, or so I thought. Plug phone in and start again with One Click Root. Fail. The script couldn't find my device.
Hours of searching and trying different things later, script still couldn't find my device, though I now have both the phone recognizing there is a USB connection, and the computer has stopped yelling at me that there are no drivers (I believe it finally gave up and installed the Windows drivers for it). But still can't get it rooted or do anything but stock stuff.
So..
1:Samsung drivers won't install, running Windows 7-64 Ultimate; error at end of install just states: "The MMS InstallWizard was not successfully installed SAMSUNG USB Driver for Mobile Phones v1.3.450.0."
2hone previously recognized USB Debug mode, but no longer. Will only Recognize standard USB connection, and with the connection made to PC, the script will not recognize the device.
3:adb for all intensive purposes does not appear to be loading..per the message from the script "Root was not obtained after 60 seconds. Make sure the phone is connected and that adb is working. If adb shell isn't root, reboot the phone and try the script again." I've rebooted numerous times, but I'm pretty certain that since it's not going into Debug, it's just not being recognized.
I have even tried Gingerbreak with no luck, just continuously sits on the rooting screen, but never proceeds (upwards 45 minutes I let it go).
Please please please please help me fix all the mistakes I did and get this thing working again and get the damned drivers installed proper.
(Baseband-S: D700.0.55.EL30, Kernel version 2.6.35.7, Build number: Gingerbread.EL30)
Note* I am happy with any root/kernel/rom at this point, I don't care, I just want the damned thing rooted again.
And of course after I finally cave and post for help, I find the thread where it clearly states OneClick Root no longer works for Gingerbread...so we'll add that into the mistakes I made...
Question still stands, how do I get this rooted again?
Qbking77 youtube him...
Or I could do it for you remotely via teamviewer... either way
Sent from my SPH-D700 using xda premium
AtrophiedAnnie said:
And of course after I finally cave and post for help, I find the thread where it clearly states OneClick Root no longer works for Gingerbread...so we'll add that into the mistakes I made...
Question still stands, how do I get this rooted again?
Click to expand...
Click to collapse
If you are up and running EL30 just Google How to Root Samsung Epic on EL30 and a qbking77 youtube video will pop up and all the links are there as well for the files you need. If you are not up and running then you need to go into the Roll Up sticky thread in Development and click on How to Restore a semi-bricked Samsung Epic....all links are there for that including 64bit drivers.
Sent from my SPH-D700 using xda premium
Found it all, getting it working now. Thanks all. We'll chalk this up to ...noobi-ness....(ignoring that I've been rooted and doing this for a year now... >.> )
AtrophiedAnnie said:
Found it all, getting it working now. Thanks all. We'll chalk this up to ...noobi-ness....(ignoring that I've been rooted and doing this for a year now... >.> )
Click to expand...
Click to collapse
Sounds more like serious root rust to me. Gotta keep up...lol. Samsung tries to make it harder to root...that works for 5 minutes around here...LOL.
Sent from my SPH-D700 using xda premium
IT'S DONE!!! Again thank you both so much1
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
Hi,
So I have a brand new SII that T-Mobile sent me when my old one's power button broke. The phone was running unrooted, stock Android 4.0.4
I decided to upgrade to Jellybean as discussed here, and by following the directions on T-Mobile's website. Before I started, I double checked that I had Android version 4.0.4, and that my baseband version was T989UVLI1.
Downloaded Kies, updated Kies to the latest version, turned on USB debugging, plugged in phone, started upgrade.
Got a message saying upgrade had failed, and to try Kies firmware emergency recovery. I've tried running emergency recovery a few times with no luck.
Any suggestions on what to do from here?
Yea just root it and then install the rooted version of the new update.
So apparently not all USB ports are created equal. I switched ports on my Macbook Pro and firmware recovery worked like a charm...must be a driver issue with Kies.
B. Dre said:
Yea just root it and then install the rooted version of the new update.
Click to expand...
Click to collapse
I figured rooting wasn't the best idea since the firmware was already screwed up...as long as it got screwed up from Kies + T-Mobile's instructions I could get a new phone, but if I tried rooting and the phone was already so screwed up that it didn't work, then they might have raised a stink about the warranty.
GilEste, which macbook do you have? I just upgraded to the latest one and can't get my phone to communicate to either of my USB ports.
Sent from my SAMSUNG-SGH-T989 using xda premium
phil.culler said:
GilEste, which macbook do you have? I just upgraded to the latest one and can't get my phone to communicate to either of my USB ports.
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
I have a mid 2012 macbook pro with retina display. For me, Kies detected the phone from both ports, but kept having errors with the left port. The right port worked for emergency firmware recovery.
The exact same thing happened to me. The update failed and emergency recovery failed.
I tried a different PC and it could not recognize the phone (on that one for some reason kies was locked at 25% cpu of 4 cores and running really slow).
I went back to the original PC and tried different ports, even a USB 3.0 add-on card without success.
I will try exchanging the phone today, but I still want to take the replacement to JB and I have another 2 phones that need the update.
Thanks
I got the replacement phone and almost immediately tried the update on yet another PC. This time the update was successful and I am seeing how things go. Now I have 2 more phones to update.
I don't know why it worked this time, but on the other PCs it would sometimes fail to detect the phone right away and might require unplugging and plugging back in.
On the PC that worked it did not have any issues. Maybe if there are any issue prior to the update, that is a sign that you should try a different PC.
Hello. Ive been 3 days with no phone now and am at my wits' end. I converted to developer, and in trying to clean install a ROM, messed something up...badly.
I can flash TWRP or CWM both through Odin, but no roms work at all. All of them get stuck at system.img.ext4 for about 10 minutes and then it fails. I cant flash anything through recovery, either, because neither recovery program can read my SD card for some reason. Ive read up on similar issues, but all of the fixes involve formatting the SD card through a functioning ROM, which isnt a possibility for me. I am desperate at this point...very desperate. Also, Ive tried the XDA IRC rooms but i'm not sure if i even join them correctly, as for days i cant get even a single letter response from any of the listed participants. Ive gotta be doing something wrong. Any help would be greatly appreciated. At this point i dont care if i lock my bootloader forever i just NEED a working phone.
Smartswitch doesnt work because it wont recognize my device, and when prompted for a S/N, nothing works...ive tried everything from the IMEI to the SIM s/n from the original package sleeve.
SOLVED:. talked to Samsung reps and confirmed that the note4 in fact has no serial number and that function if the recovery tool doesn't work for them. Did a day or researching on ADB stuff, which was new to me, and got cm13 successfully working via side load. After that, cm formatted the memory card to he readable, and all seems right in my note4 world for now.
8wrlobo said:
SOLVED:. talked to Samsung reps and confirmed that the note4 in fact has no serial number and that function if the recovery tool doesn't work for them. Did a day or researching on ADB stuff, which was new to me, and got cm13 successfully working via side load. After that, cm formatted the memory card to he readable, and all seems right in my note4 world for now.
Click to expand...
Click to collapse
So what exactly did you do been trying to get a rom to work on mine that I did the dev convert on. I was on the latest ota update. Got it rooted and flashed a different kernel got it to boot on stock firmware but can't get any other rom to install and boot.
Sent from my SM-N910V using XDA-Developers mobile app
slowpoke2006 said:
So what exactly did you do been trying to get a rom to work on mine that I did the dev convert on. I was on the latest ota update. Got it rooted and flashed a different kernel got it to boot on stock firmware but can't get any other rom to install and boot.
Sent from my SM-N910V using XDA-Developers mobile app
Click to expand...
Click to collapse
Yeah Odin and sd card options all fell flat on their faces for me...I never did figure out the system.img.ext4 hangup I got from odin.
In the end, I used Odin (3.9 iirc) to flash twrp. Flashing two or cwm both never gave me any trouble. From there, I downloaded the cm13 latest build from the thread here and followed this guide (http://forum.xda-developers.com/showthread.php?t=2317986). Sideload failed for me as well, but I was able to push the rom to my phone.
I downloaded a adb/fastboot program (https://androidmtk.com/download-minimal-adb-and-fastboot-tool) and in the x86 program files folder for it, made a new folder called FML lol and moved the ROM zip folder into it. Then did
abd push ___________.zip /sdcard/_________.zip. (note that I don't remember exact adb commands...it had been hours of frustration. Definitely consult the experts (not me) here before trying what I did. In the end it worked great. Good luck.
It was my first experience with adB stuff and tons of trialife and and error but I sure learned tons after all the research and frustration.
8wrlobo said:
Yeah Odin and sd card options all fell flat on their faces for me...I never did figure out the system.img.ext4 hangup I got from odin.
In the end, I used Odin (3.9 iirc) to flash twrp. Flashing two or cwm both never gave me any trouble. From there, I downloaded the cm13 latest build from the thread here and followed this guide (http://forum.xda-developers.com/showthread.php?t=2317986). Sideload failed for me as well, but I was able to push the rom to my phone.
I downloaded a adb/fastboot program (https://androidmtk.com/download-minimal-adb-and-fastboot-tool) and in the x86 program files folder for it, made a new folder called FML lol and moved the ROM zip folder into it. Then did
abd push ___________.zip /sdcard/_________.zip. (note that I don't remember exact adb commands...it had been hours of frustration. Definitely consult the experts (not me) here before trying what I did. In the end it worked great. Good luck.
It was my first experience with adB stuff and tons of trialife and and error but I sure learned tons after all the research and frustration.
Click to expand...
Click to collapse
OK so once you were able to get the rom pushed to your phone it installed fine? I just can't get them to install and boot right. What version were you on and did you do safe updates? Guess I'll have to start a new thread on it
Sent from my SM-N910V using XDA-Developers mobile app
I was/am at PA1. I did the smartswitch emergency recovery to stock PA1 and then redid the developer conversion, before having a hangup and wiping everything with twrp...like everything (BAD idea). That is what caused all my odin and sd card woes to begin with.
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!