So I went through the casual thread and followed all the instructions
I've used the Zadig to push new drivers
I've refreshed my pc twice
I've uninstalled and reinstalled Samsung drivers
I've disabled digitally signed drivers in Windows 8
I've tried several USB ports as well
I've even tried on a Windows 7 pc and I can't make any progress.
I need some help. I'm completely stumped at this point. I don't know where things are going wrong.
Here's the link to my log for casual. If anyone has any ideas or suggestions, I'd greatly appreciate it.
pastebin.com/mmAXTZm7
Casual Nightly build R532 works with Windows 8!!!
I used a nightly build R532 and that worked with Windows 8!!!
I was getting the boot loop trying to install drivers.
I closed Casual and while my phone was still in download mode, I used the zadig fix found in the Casual thread (look for the troubleshooting link)
I ran Casual again, and it worked!
dlegendary0ne said:
I used a nightly build R532 and that worked with Windows 8!!!
I was getting the boot loop trying to install drivers.
I closed Casual and while my phone was still in download mode, I used the zadig fix found in the Casual thread (look for the troubleshooting link)
I ran Casual again, and it worked!
Click to expand...
Click to collapse
I don't know if this is the end all be all fix for Windows 8 users, if R532 doesn't work, just try the different nightly builds and see if they work. From what I read in the Casual thread, the earlier nightly builds seem to work better for Windows 8. I hope this helps someone!
Are you sure you're using the right version? Go here and make sure the casual version you used is the one for whichever version of android you have to start with.
dlegendary0ne said:
I used a nightly build R532 and that worked with Windows 8!!!
I was getting the boot loop trying to install drivers.
I closed Casual and while my phone was still in download mode, I used the zadig fix found in the Casual thread (look for the troubleshooting link)
I ran Casual again, and it worked!
Click to expand...
Click to collapse
stueycaster said:
Are you sure you're using the right version? Go here and make sure the casual version you used is the one for whichever version of android you have to start with.
Click to expand...
Click to collapse
I'm sure. I was using the VRAMC3 version which matched my version of Android. The official build didn't work, but the R532 nightly build, along with the Zadig fix did work for Windows 8. Thanks for the link!
dlegendary0ne said:
I'm sure. I was using the VRAMC3 version which matched my version of Android. The official build didn't work, but the R532 nightly build, along with the Zadig fix did work for Windows 8. Thanks for the link!
Click to expand...
Click to collapse
Great! I had to ask because it wasn't mentioned in any of the previous posts.
Sent from my SCH-I605 using Tapatalk 2
stueycaster said:
Great! I had to ask because it wasn't mentioned in any of the previous posts.
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
No worries! I just assumed everyone had the update by now. But you know what they say about assumptions... Lol
Related
It would, at this time to be prepared for s-off, making sure you have all htc drivers install, sdk tools and the like, have you recovery.img ready to go and your supersu zip in the proper place, don't wait to the last minute to do this, then your ready to go.
I've been working on gathering everything up. I'm unlocked so I need to relock, install update, unlock and get root back yet. I've been holding off cause I hate to give up viper and go back to stock.
Where would one start? I don't know where to get sdk....not to mention how to use it. Do you think you could come up with a list of you have the time? Every phone I've rooted has had unlock tools (unrevoked for og Inc and alpha rev for Inc 2)
Linch89 said:
Where would one start? I don't know where to get sdk....not to mention how to use it. Do you think you could come up with a list of you have the time? Every phone I've rooted has had unlock tools (unrevoked for og Inc and alpha rev for Inc 2)
Click to expand...
Click to collapse
go to unlimited.io and you can get latest htc drivers and adb sdk tools too, they have links there. you can get recovery from hasoons tool. we don't have a root tool yet, it's coming.i should say s-off tool
as far as using adb and sdk tools, should be some instruction here somewhere, search the forums for it you should find it.
Thanks boss yeah I know no tool yet
Aldo101t said:
go to unlimited.io and you can get latest htc drivers and adb sdk tools too, they have links there. you can get recovery from hasoons tool. we don't have a root tool yet, it's coming.i should say s-off tool
as far as using adb and sdk tools, should be some instruction here somewhere, search the forums for it you should find it.
Click to expand...
Click to collapse
Do we need root tool, or can we just flash recovery then su binary?
Sent from my Nexus 7 using Tapatalk 2
jamminjon82 said:
Do we need root tool, or can we just flash recovery then su binary?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
you can't flash recovery til you either get s-off or unlocked bootloader, you can't flash SU til you have recovery, so.
Aldo101t said:
you can't flash recovery til you either get s-off or unlocked bootloader, you can't flash SU til you have recovery, so.
Click to expand...
Click to collapse
I was saying once you have s-off
Sent from my DROID SPYDER using Tapatalk 2
I'd say get a ROM ready, once u get s-off, u can install recovery, then install a ROM.
the superuser root .zip is only needed if you plan to use the stock ROM.
I am so going to have to take my laptop to town to get to Wi-Fi to update Windows so I can root my phone.
To quote the juggernaut, "sh!t I've been ready to f!ck"
Sent from my DROID SPYDER using Tapatalk 2
Aldo101t said:
go to unlimited.io and you can get latest htc drivers
Click to expand...
Click to collapse
Whether I try to use the drivers from unlimited.io or the ones linked by jose51197 in the automatic unlock post I can't get them to install on my computer. I'm running 64-bit Windows 8 Release Preview Version 6.2 (Build 8400). OldNut5 mentioned that it worked for him on 64-bit Windows 8 Pro, so I don't think my operating system is the problem. As soon as the installer starts running, it shows an error message which reads:
Code:
The Driver Installer is not supported for this Operating System!
Has anyone else had this problem? I tried running it as administrator, as well as running it in compatibility mode for both Windows 7 and Windows XP (SP3), but it always produced the same error. Am I missing something obvious, or does this only work on the Pro version of Windows 8 for some reason?
altayh said:
Whether I try to use the drivers from unlimited.io or the ones linked by jose51197 in the automatic unlock post I can't get them to install on my computer. I'm running 64-bit Windows 8 Release Preview Version 6.2 (Build 8400). OldNut5 mentioned that it worked for him on 64-bit Windows 8 Pro, so I don't think my operating system is the problem. As soon as the installer starts running, it shows an error message which reads:
Code:
The Driver Installer is not supported for this Operating System!
Has anyone else had this problem? I tried running it as administrator, as well as running it in compatibility mode for both Windows 7 and Windows XP (SP3), but it always produced the same error. Am I missing something obvious, or does this only work on the Pro version of Windows 8 for some reason?
Click to expand...
Click to collapse
Drivers are designed to work for a specific operating system. I personally haven't been able to get a single driver for any device to work on Windows 8 that was designed for Windows 7. Vista drivers more often than not did work on Windows 7, though. Go figure.
In this thread, someone says they installed the most recent version of HTC Sync on Windows 8 and managed to get the drivers working. Try that.
EDIT: Just tried this on Windows 8 and it worked perfectly.
IceDragon59 said:
EDIT: Just tried this on Windows 8 and it worked perfectly.
Click to expand...
Click to collapse
Thanks a bunch! Installing HTC Sync didn't help, but this worked perfectly.
bleh, just use linux and you dont need to worry about drivers
nitsuj17 said:
bleh, just use linux and you dont need to worry about drivers
Click to expand...
Click to collapse
To be honest I dual-boot my computer and primarily use Ubuntu, but the automatic bootloader unlock guide was written for Windows with a handy zip of executables and a batch script, and I didn't want to have to figure out how to properly install adb on Ubuntu as well as risk messing something up if there happens to be a Linux-only issue.
It's nice to know that it should work on Ubuntu without any need for the drivers. I assume this is how I would have to install adb. It's a shame I can't just "sudo apt-get install adb" it...
altayh said:
To be honest I dual-boot my computer and primarily use Ubuntu, but the automatic bootloader unlock guide was written for Windows with a handy zip of executables and a batch script, and I didn't want to have to figure out how to properly install adb on Ubuntu as well as risk messing something up if there happens to be a Linux-only issue.
It's nice to know that it should work on Ubuntu without any need for the drivers. I assume this is how I would have to install adb. It's a shame I can't just "sudo apt-get install adb" it...
Click to expand...
Click to collapse
looks like a decent guide
So I have finally gotten around to unlocking the bootloader so I can install the Atrix-MROM flash to stop having the battery and overheating issues that seem to be present with the latest update. I've been trying to use the procedure outlined in this thread: http://forum.xda-developers.com/showthread.php?t=1182871 , but when I reach the RSD Lite stage the driver cannot be found. I believe this is the flash interface driver going off of what I've seen, but I'm also a little new to all this. I've tried searching the threads and found nothing, and did a little googling. Any info on where I can get the driver or some other fix? And sorry if this has actually been solved, but I couldn't find anything.
onemanwlfpk said:
So I have finally gotten around to unlocking the bootloader so I can install the Atrix-MROM flash to stop having the battery and overheating issues that seem to be present with the latest update. I've been trying to use the procedure outlined in this thread: http://forum.xda-developers.com/showthread.php?t=1182871 , but when I reach the RSD Lite stage the driver cannot be found. I believe this is the flash interface driver going off of what I've seen, but I'm also a little new to all this. I've tried searching the threads and found nothing, and did a little googling. Any info on where I can get the driver or some other fix? And sorry if this has actually been solved, but I couldn't find anything.
Click to expand...
Click to collapse
do you have the proper drivers installed for rsd? there's a 32 bit and a 64 bit version
Sent from my MB860 using xda app-developers app
palmbeach05 said:
do you have the proper drivers installed for rsd? there's a 32 bit and a 64 bit version
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
What I have is the latest Moto drivers from the webpage, and the script that was uploaded unto the thread listed. Are you saying that the source of my problem is that like a noob I missed a set of drivers and that's why when I connect the phone in RSD mode it doesn't work?
onemanwlfpk said:
What I have is the latest Moto drivers from the webpage, and the script that was uploaded unto the thread listed. Are you saying that the source of my problem is that like a noob I missed a set of drivers and that's why when I connect the phone in RSD mode it doesn't work?
Click to expand...
Click to collapse
If you say you do have the latest drivers from Motorola, you should be fine. I'm not sure what RSD version is coming with the automatic bootloader, but I know that there is an updated one, its 5.7. There might be an updated one from that, but that's at least what I have. Try searching and using that and post what happens.
palmbeach05 said:
If you say you do have the latest drivers from Motorola, you should be fine. I'm not sure what RSD version is coming with the automatic bootloader, but I know that there is an updated one, its 5.7. There might be an updated one from that, but that's at least what I have. Try searching and using that and post what happens.
Click to expand...
Click to collapse
Okay, so I found and installed RSD 6.1.4, and double checked my drivers. The moto drivers are version 6.0.0. Attached is a print screen of what happens as I try to connect and use RSD.
Just a hunch. Consider trying to add the drivers manually. Go into the device manager, update driver software, let me pick, then look around. I dunno what they'll be called or, if they will even be there. But it is worth a shot for sure.
If that doesn't work then you might think about trying a different usb cable/usb port/pc/32 or 64bit versions. Sucks, but been there done that one... Hoping that one of those helps you.
Good luck.
JdgM3NT4L said:
Just a hunch. Consider trying to add the drivers manually. Go into the device manager, update driver software, let me pick, then look around. I dunno what they'll be called or, if they will even be there. But it is worth a shot for sure.
If that doesn't work then you might think about trying a different usb cable/usb port/pc/32 or 64bit versions. Sucks, but been there done that one... Hoping that one of those helps you.
Good luck.
Click to expand...
Click to collapse
Yeah I ended up trying the process on my desktop that runs WinXP instead. Worked like a charm so now I've moved on to the rest of the process. Thanks for the advice on that. Must be something wonky with my laptop.
onemanwlfpk said:
Yeah I ended up trying the process on my desktop that runs WinXP instead. Worked like a charm so now I've moved on to the rest of the process. Thanks for the advice on that. Must be something wonky with my laptop.
Click to expand...
Click to collapse
Glad to hear that you got it. Nice work!
It could be a wonky lappy. Myself I think it is because I try to adb and stuff for a lot of different devices on my pc. Seems like if only one device has ever been installed everything is fine. But once I start adding more devices and drivers to the pc it get confused and a lot of things just do not work. I either have to do some serious driver cleanup, or switch machines to be effective. I've moved on to a Samsung phone, but my Wife and Daughter still rock their Atrix(s(?)) So I try to use my lappy for those and my desktop for my Sammys. So far so good here.
Back in March I was rooted, running a cool sense 5 based custom ROM and happy. But the phone had other ideas. It stopped recognizing the SIM card and the replacement phone Verizon sent was on the latest firmware which we couldn't hack. I couldn't deal with the stock configuration after having the custom ROM so I binned the phone and went back to my old GS3 hoping to someday be able to go back to the DNA.
If I understand things correctly, that day has come and we can root the current firmware equipped phones.....Correct? I've read thru a number of posts and all it has done is left me confused and hesitant to give it a shot.
Can someone help me out with the correct steps, methods and procedures to root my stock, S-on DNA running the latest OTA firmware (2.06)? Any help is greatly appreciated!!
http://forum.xda-developers.com/showthread.php?t=2314771
scheirere said:
Back in March I was rooted, running a cool sense 5 based custom ROM and happy. But the phone had other ideas. It stopped recognizing the SIM card and the replacement phone Verizon sent was on the latest firmware which we couldn't hack. I couldn't deal with the stock configuration after having the custom ROM so I binned the phone and went back to my old GS3 hoping to someday be able to go back to the DNA.
If I understand things correctly, that day has come and we can root the current firmware equipped phones.....Correct? I've read thru a number of posts and all it has done is left me confused and hesitant to give it a shot.
Can someone help me out with the correct steps, methods and procedures to root my stock, S-on DNA running the latest OTA firmware (2.06)? Any help is greatly appreciated!!
Click to expand...
Click to collapse
So I just follow the steps listed in the link above and I'll be ready to flash a custom ROM? No HTC unlock code and such?
Correct.
Sent from my HTC6435LVW using Tapatalk 4 Beta
beaups said:
Correct.
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
Ok, gave it a shot with the windows version and didn't succeed. Followed the instructions and definitely made sure there was no trace of HTC Sync on the computer. When I run the Distiller.exe file, everything seems to run OK for test 1 (rebooting into bootloader) and test 2 (booting device) were the phone reboots like normal. Then the script says rebooting into bootloader (again) and sits there waiting for fastboot. It times out after 60 seconds and says connection failed. usb connection error.
Any ideas on were to go from here?
You need fastboot drivers.
Sent from my HTC6435LVW using Tapatalk 4 Beta
Moonshine works great
Sent from my HTC6435LVW using xda app-developers app
Suggestions on were I can get those fastboot drivers?
Google HTC fastboot drivers. If you are on win8 with usb 3 ports only you can expect issues.
Sent from my HTC6435LVW using Tapatalk 4 Beta
Googled HTC fastboot driver and it looks like I need HTCDriver3.0.0.007.exe . If I google HTC android drivers I can find another file HTCDriver_4.2.0.001.exe. Tried them both on my home windows 7 machine with a USB2 port. Nothing changed. Same results.
So I tried the window XP computer at my office that I originally used to root the old DNA. Got a little further this time. I get a message that temproot has failed. I also get a lot of stuff going on with "other devices" drivers when I watch my device manager. Is this normal during the process?
scheirere said:
Googled HTC fastboot driver and it looks like I need HTCDriver3.0.0.007.exe . If I google HTC android drivers I can find another file HTCDriver_4.2.0.001.exe. Tried them both on my home windows 7 machine with a USB2 port. Nothing changed. Same results.
So I tried the window XP computer at my office that I originally used to root the old DNA. Got a little further this time. I get a message that temproot has failed. I also get a lot of stuff going on with "other devices" drivers when I watch my device manager. Is this normal during the process?
Click to expand...
Click to collapse
Ok temproot failing means factory reset time. You should be good after that.
Sent from my HTC6435LVW using Tapatalk 4 Beta
That did the trick!! Factory reset and the older XP machine. God, how much I missed the custom roms for this phone. It totally transforms the device.
As for the Moonshine process, like I said, it worked for me but I did run into a few more speed bumps. Everytime the phone would reboot, I had to squash the HTCsync install. I guess it's something on the phone as I searched hi and low to find anything like it on the computer, with no luck. Anyhow, I would just cancel out everytime the message appeared on the screen. If I didn't cancel out, the moonshine script would time out and fail.
Just wanted to follow up on this in case someone else has similar issues.
Thanks again, guys!
So I can't move files off or on to my device by dragging and dropping any more.
I have searched and found stuff about MTP drivers and work arounds but have not found anything that works. Anyone have any ideas about a fix.
I am running OSE, the latest build.
OSE DNA
johnwaug said:
So I can't move files off or on to my device by dragging and dropping any more.
I have searched and found stuff about MTP drivers and work arounds but have not found anything that works. Anyone have any ideas about a fix.
I am running OSE, the latest build.
OSE DNA
Click to expand...
Click to collapse
Could this be an issue with that specific ROM? My works fine with Window 8.1 64bit on either CM11 or AOSPA v4 beta. Have you tried PTP mode?
I guess I might have to flash another rom to find out.
OSE DNA
Might want to dig deeper.. only thing you can't do with Windows 8/8.1 is use fastboot ... as far as I know.
Sent from my HTC6435LVW using Tapatalk
Flashed CM 11 and connected right away.
CM 11 DNA & Tab 10.1 4.4.2
jbarcus81 said:
Might want to dig deeper.. only thing you can't do with Windows 8/8.1 is use fastboot ... as far as I know.
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
Fastboot works on windows 8.0.
The update to 8.1 broke the drivers. No fastboot.
Just spent last night removing that update from my computer. Pain in the a.. but now my fastboot drivers are back up and working fine.
sdamark said:
Fastboot works on windows 8.0.
The update to 8.1 broke the drivers. No fastboot.
Just spent last night removing that update from my computer. Pain in the a.. but now my fastboot drivers are back up and working fine.
Click to expand...
Click to collapse
How did u remove the 8.1 update?
mopartonyg said:
How did u remove the 8.1 update?
Click to expand...
Click to collapse
Mouse to lower right corner of screen >settings. >change pc settings. Then I think its the middle option >restart pc and save files.
Note... be sure to backup the files it says you will lose, and anything important.
This takes windows back to when your computer was new. Now I'm on a clean install of Windows 8.0 :good: and all my drivers work again
sdamark said:
Fastboot works on windows 8.0.
The update to 8.1 broke the drivers. No fastboot.
Just spent last night removing that update from my computer. Pain in the a.. but now my fastboot drivers are back up and working fine.
Click to expand...
Click to collapse
I'm back on Windows 7 for now.. trying to acquire a new DVD of my Windows 8 because of a scratch too deep to fix (as far as I can tell) ... I was on Windows 8.1 but corrupted data forced me to format (I broke it, haha!) and could only get my Windows 7 DVD to work.. Oh well.. been on the fence about linux so I may jump ship.
For me personally it was an mtp setting in the ROM I had forgot to check.
Sent from my HTC6435LVW using xda app-developers app
I have successfully rooted and installed a few roms. I have updated radios and even installed the new sense 5.5 rom. It locked my phone, so I have been trying to unlock it for a couple of days. I have used htc dev unlock and win droid versions. I've used three different windows versions. Still no PC recognizes my phone. Is there a common fix? I have read and found none here, nor online.
pah3000 said:
I have successfully rooted and installed a few roms. I have updated radios and even installed the new sense 5.5 rom. It locked my phone, so I have been trying to unlock it for a couple of days. I have used htc dev unlock and win droid versions. I've used three different windows versions. Still no PC recognizes my phone. Is there a common fix? I have read and found none here, nor online.
Click to expand...
Click to collapse
Try again with ubuntu. Make sure to sudo su.
Sent from my EVO using Tapatalk
Do you have htc sync driver installed?
numel007 said:
Try again with ubuntu. Make sure to sudo su.
Sent from my EVO using Tapatalk
Click to expand...
Click to collapse
I have lubuntu installed on an xp netbook. I'll look it up and try, thanks.
Valsorim said:
Do you have htc sync driver installed?
Click to expand...
Click to collapse
Yes. It's recognized until I reboot to bootloader. Two evenings on this!
Are you selecting the Fastboot option when you get to the bootloader?
Sent from my EVO LTE
Not using Windows 8.1 w/USB 2.0, are you? Because if so, you'll have to use a hacky workaround.
Captain_Throwback said:
Not using Windows 8.1 w/USB 2.0, are you? Because if so, you'll have to use a hacky workaround.
Click to expand...
Click to collapse
Ha, yes I was! So I tried other ports. Then tried XP net book, to no avail. Everything works fine on the rom, and I saw your post about re-unlocking. I've never been stumped before. May try a windows7 laptop tonight. Not too familiar with Ubuntu. Thanks.
numel007 said:
Try again with ubuntu. Make sure to sudo su.
Sent from my EVO using Tapatalk
Click to expand...
Click to collapse
Just finished. Same message: <waiting for device>
I assume you tried a different cable already, right?
Captain_Throwback said:
I assume you tried a different cable already, right?
Click to expand...
Click to collapse
Yessir. First used the replacement I bought, then the original. Only used the original trying Ubuntu. It must be something I'm missing. I really appreciate all the input.
Seems intriguing that some experience same problem with new released RUU.