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.
Related
so the title pretty much sums it up, im on a mac 10.7.2 and trying to root my sgs2, im new to rooting so im still trying to figure everything out but ive followed multiple guides. they all end with "claiming interface failed" can someone help me with this please?
I'm guessing you're using heimdal? Just covering the ground work. Have you tested out if it can be accessed through adb? And that it can mount the sdcard to the computer?
Sent from my páhhōniē
ElectronicYank said:
so the title pretty much sums it up, im on a mac 10.7.2 and trying to root my sgs2, im new to rooting so im still trying to figure everything out but ive followed multiple guides. they all end with "claiming interface failed" can someone help me with this please?
Click to expand...
Click to collapse
Not sure this is the kind of help you're looking for but I'd tried rooting with heimdal on mac 10.7.2 also, for about 5 hours with no success! Booted up Parallels (Win 7) and flashed with odin first time. Some have reported success using heimdal on 10.7.2 but I tried everything I could find with no luck. All that to say, if you have access to a pc just root on that and start enjoying your phone!
Or check out mobile Odin. Can flash everything you need with just your phone, and not trip the flash counter. Which means you can just download Entropy512's kernel and you'll have cwm. And from there flash any rom you want.
Sent from my páhhōniē
gr8hairy1 said:
Or check out mobile Odin. Can flash everything you need with just your phone, and not trip the flash counter. Which means you can just download Entropy512's kernel and you'll have cwm. And from there flash any rom you want.
Sent from my páhhōniē
Click to expand...
Click to collapse
isnt that only if your phone is rooted?
gr8hairy1 said:
I'm guessing you're using heimdal? Just covering the ground work. Have you tested out if it can be accessed through adb? And that it can mount the sdcard to the computer?
Sent from my páhhōniē
Click to expand...
Click to collapse
yes i installed heimdall 1.3.1
idk what you mean by testing it through adb and how mounting the sd card is part of the process though
im a noob to all this so i apologize for my stupidity in advance
I can't help with using Heimdall on Lion 10.7.2, but...
You should be able to root using SuperOneClick v2.2. This program uses the ZergRush Exploit and is supported on mac with mono v1.2.6 or better.
If you try this, please post back to let us know if it worked for you.
As I understand it, Heimdall seems to have a LOT of problems with Lion.
Entropy512 said:
As I understand it, Heimdall seems to have a LOT of problems with Lion.
Click to expand...
Click to collapse
thats unfortunate news
creepyncrawly said:
I can't help with using Heimdall on Lion 10.7.2, but...
You should be able to root using SuperOneClick v2.2. This program uses the ZergRush Exploit and is supported on mac with mono v1.2.6 or better.
If you try this, please post back to let us know if it worked for you.
Click to expand...
Click to collapse
am i running any serious risks by trying this?
None that I've heard. Just used it tonight on my friends sgsii. Worked with no issues.
Sent from my páhhōniē
gr8hairy1 said:
None that I've heard. Just used it tonight on my friends sgsii. Worked with no issues.
Click to expand...
Click to collapse
Working from a Windows pc?
creepyncrawly said:
Working from a Windows pc?
Click to expand...
Click to collapse
Oops, forgot the op is using mac. Yeah windows 7.
Sent from my páhhōniē
ya ive been trying this guide here and this one
but they both bring up the same error
i tried to use bootcamp and put windows 7 on but for some reason my mac wont let me now
Just download zergrush root and samsung Kies. Put it on any windows box and you'll be all done with root in probably less than 15 min, from start to finish.
For sure you'll be able to get things working on your Mac at some point. But no sense in also being frustrated you can root your phone. Keep the stress level low
Sent from my páhhōniē
ElectronicYank said:
ya ive been trying this guide here and this one
but they both bring up the same error
i tried to use bootcamp and put windows 7 on but for some reason my mac wont let me now
Click to expand...
Click to collapse
Have you tried SuperOneClick on Lion yet? I'd be really interested to know if it will work for you.
creepyncrawly said:
Have you tried SuperOneClick on Lion yet? I'd be really interested to know if it will work for you.
Click to expand...
Click to collapse
is there a version for lion?
ElectronicYank said:
is there a version for lion?
Click to expand...
Click to collapse
I've never use Mac computers. Did you read CLShortFuse's SuperOneClick thread? He states that the program works on mac after installing mono 1.2.6 or greater. He doesn't say anything specific about Lion. Please go to his thread at SuperOneClick v2.2 and look at the information.
If you decide to try this, and I can't think of any reason why you shouldnt at least try, then your results will be important so we can tell other mac users if this method works or not.
Good luck, I hope it works.
i downloaded everything but there isnt a real guide for mac's
ElectronicYank said:
i downloaded everything but there isnt a real guide for mac's
Click to expand...
Click to collapse
Can't help you there. From reading a little bit in the SuperOneClick thread, it looks like it might be a little more involved than just installing mono and then the program. All I can suggest is search his thread.
Or... maybe it would be easier to find a Windows pc you can borrow and root from there.
i searched the thread for a couple of hours and couldnt find anything useful
Hey guys,
I've been searching for an answer for days now and I finally decided to make an account here on XDA.
I recently unlocked the bootloader of my Atrix (I have superuser and all) and now I want to upload a custom ROM (CM7). I followed the steps on the CM7 thread for installation yet I was left scratching my head and eventually was extremely frustrated after many reboots, configurations, and even a hard reset!
I used ROM Manager to get CWM, I flashed the latest version, and entered recovery mod, both from the app and manually. Nothing - just the Android Recovery. Tried many times, sometimes I was given a "failed to boot 2, starting RSD mode" error but most of the times I was just taken to the normal recovery.
I read somewhere that the install-recovery.sh file found in the system had to be deleted so I downloaded ES File Explorer, enabled root and writing and successfully deleted it (or so I thought), I was taken to the android recovery again! When I checked the file explorer again, install-recovery.sh was back... I have tried many times and it keeps on returning.
What am I doing wrong? I don't even know how to use fastboot, I am a noob and 90% of the language used on this forum is foreign to me hahaha (I traded my iPhone 4 for the Atrix less than two weeks ago). Also, I accidentally deleted my install-recovery.sh.bak file, is that important?
Any help would be appreciated.
Thanks,
Kevin.
Alright, calm down, and dont panic, I was a noob too, just dont do anything rash and this'll be fine. First off, the install-recovery.sh.bak thing, or whatever you said it was called, is just a backup of whatever it was replacing, hence the .bak file extension. Now, you can still get into Android right, everything boots correctly and whatnot, or are you not able to boot right now? Also, it says youre unlocked for sure, correct? Like, when you boot, it says Unlocked up in the corner? We're going to get you through this, just answer these questions first
Hey,
Sorry if I sounded dramatic haha, just typed off the top of my head.
Thanks for clarifying regarding the bak file. No, it does not say unlocked at the top corner when booting, i assumed having the superuser app meant that I was unlocked/bootloader unlocked. The am I missing something here?
Also, my phone is totally functional. In fact, I am typing this on it
Killer0Kevin said:
Hey,
Sorry if I sounded dramatic haha, just typed off the top of my head.
Thanks for clarifying regarding the bak file. No, it does not say unlocked at the top corner when booting, i assumed having the superuser app meant that I was unlocked/bootloader unlocked. The am I missing something here?
Click to expand...
Click to collapse
Yeah, your not unlocked at all... maybe rooted, but not unlocked. See my signature for noob guide.
Sent from my MB860 using xda premium
I have been trying all day to unlock the bootloader with no success lol
I can't install RSDlite, it gives me error 29** or something like that, have tried multiple download links and I cannot install the x64 driver, my desktop is running 32 bit which is probably the issue I'm guessing... Any alternates? It gives me a "processor type not compatible" error.
Killer0Kevin said:
I have been trying all day to unlock the bootloader with no success lol
I can't install RSDlite, it gives me error 29** or something like that, have tried multiple download links and I cannot install the x64 driver, my desktop is running 32 bit which is probably the issue I'm guessing... Any alternates? It gives me a "processor type not compatible" error.
Click to expand...
Click to collapse
Have you tried the automatic unlock linked to in Swift's N00B guide? It doesn't get any easier than that.
It's packaged with RSDLite 5.3.1. It's the one I used to unlock. Don't see why it wouldn't still work. There's a link to Motorola's driver page there as well.
Do not use the CWM packaged with it though, it's outdated. Flash romracer's or ROM Manager's.
ghost_og said:
Have you tried the automatic unlock linked to in Swift's N00B guide? It doesn't get any easier than that.
It's packaged with RSDLite 5.3.1. It's the one I used to unlock. Don't see why it wouldn't still work. There's a link to Motorola's driver page there as well.
Do not use the CWM packaged with it though, it's outdated. Flash romracer's or ROM Manager's.
Click to expand...
Click to collapse
Yes I have.
I followed all the steps and eventually it got to the unique ID part, no ID was shown, googled it and found out that I had to use RSDlite first, but there's my problem.. Also tried the fastboot oem method, same problem.
Killer0Kevin said:
Yes I have.
I followed all the steps and eventually it got to the unique ID part, no ID was shown, googled it and found out that I had to use RSDlite first, but there's my problem.. Also tried the fastboot oem method, same problem.
Click to expand...
Click to collapse
You had mentioned you were trying to use the x64 drivers on a 32-bit machine. Did you ever get around to installing the correct x86 ones from the Motorola site?
ghost_og said:
You had mentioned you were trying to use the x64 drivers on a 32-bit machine. Did you ever get around to installing the correct x86 ones from the Motorola site?
Click to expand...
Click to collapse
No, I have not. Would you find sending me the link? I don't know where to start haha
I will try on my other desktop later after I finish my homework
Killer0Kevin said:
No, I have not. Would you find sending me the link? I don't know where to start haha
I will try on my other desktop later after I finish my homework
Click to expand...
Click to collapse
See my previous post, #7. If you go to that automatic unlock thread, there is a link to the Motorola drivers page in the instructions. Look at the prerequisites.
Got it working, thanks guys!
I'm sorry if there is something already posted here somewhere about the rezound, but I haven't seen anything...yet...lol.
I've been trying to root my rezound ALL DAY and can't seem to figure anything out apparently.
If someone could help me out with sending me a link to the best way of unlocking bootloader and then rooting my phone. I had a dinc2 previously and that was not as hard to root compared to the rezound IMO. So please, if someone can take the time for me and help me out with getting my phone unlocked and rooted I would greatly appreciate it a TON!!!
Try this out http://forum.xda-developers.com/showthread.php?t=1648578
http://bit.ly/N3cfpa
hey guys thanks for replying back....I'm still getting no luck whatsoever with unlocking the bootloader.....I'm doing everything (or so I think I am) right with the steps on htcdev.com and when I get to the command prompt and type in fastboot oem get_identifier_token...this is what comes up
'fastboot' is not recognized as an internal or external command,
operable program or batch file.....now I have NO CLUE what the heck to do!! I'm getting pissed off lol. I could really use some help here. thanks
You need to change the directory to where your fastboot is located.
Sent from my ADR6425LVW using xda premium
EmerikL said:
You need to change the directory to where your fastboot is located.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Fastboot is located in the Android folder that i created....I found out my problem. My laptop isn't recognizing my phone at all. I read about this on a few forums about a lot of other people having this same issue with the rezound.....I try to install drivers on my pc for my phone to be recognized but its still not working....How did you or anyone else on here get their pc to recognize their phone???
npainter7 said:
Fastboot is located in the Android folder that i created....I found out my problem. My laptop isn't recognizing my phone at all. I read about this on a few forums about a lot of other people having this same issue with the rezound.....I try to install drivers on my pc for my phone to be recognized but its still not working....How did you or anyone else on here get their pc to recognize their phone???
Click to expand...
Click to collapse
Did you install HTC Sync properly? And have you tried installing the android usb drivers using SDK Manager?
kzoodroid said:
Did you install HTC Sync properly? And have you tried installing the android usb drivers using SDK Manager?
Click to expand...
Click to collapse
Yep I've installed htc sync multiple times now and SDK manager as well. Still a no go. It's really frustrating I can even unlock my [email protected]#$%& phone lol. After I install SDK manager, is there something else I have to do to it??? I think I have everything ready to unlock my device but once I click fastboot OEM get identifier token it says waiting for device and doesn't do anything after that. Freakin sucks
Yeah make sure you have the HTC drivers installed. I had the same issue in Jan when I rooted mine, drivers weren't there.
Posted from my Rooted and ICS'd Rezound
Fastbird said:
Yeah make sure you have the HTC drivers installed. I had the same issue in Jan when I rooted mine, drivers weren't there.
Posted from my Rooted and ICS'd Rezound
Click to expand...
Click to collapse
I'm pretty sure I had them downloaded. Just to make sure, what is included in the drivers?? That way I know everything is there when its downloaded.
npainter7 said:
Yep I've installed htc sync multiple times now and SDK manager as well. Still a no go. It's really frustrating I can even unlock my [email protected]#$%& phone lol. After I install SDK manager, is there something else I have to do to it??? I think I have everything ready to unlock my device but once I click fastboot OEM get identifier token it says waiting for device and doesn't do anything after that. Freakin sucks
Click to expand...
Click to collapse
After you install Android SDK the directions on the HTCdev site tell you to run sdk manager and download the Android SDK Tools and Android SDK Platfrom-tools. What I did was to take this a step further and also install the Google USB Driver which is listed in ADB Manager under Extras and also the API's for GB and ICS. The API's really aren't necessary but I don't think ADB will recognize the phone without the Google USB Drivers.
npainter7 said:
I'm pretty sure I had them downloaded. Just to make sure, what is included in the drivers?? That way I know everything is there when its downloaded.
Click to expand...
Click to collapse
This may not work for you, but one time my drivers weren't working because I plugged my phone into a USB 3.0 port, so when I used a USB 2.0 port, it worked fine.
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
hi everyone.. I recently upgraded my phone to the LG G2, and in doing so I have kept my Droid DNA for the purpose of getting into rooting, and customizing. I have always been fascinated with smart phones , and operating systems, and would like to get to know how to dig into them. I know stock systems very well, and optimize every phone I get up to the stock allowance. Now I want to lift my limitations, and this is the perfect phone to do it with. so if yu could please kindly give me some advice on where to start,. I have been lurking these forums for quite some time, and I find it overwhelming, since I don't know a good starting point. I will continue reading/learning before I tap into this OS, but I just need to know basics, then I will begin to understand the framework..if I have this in the wrong section, im sorry, ill find it if you move it. if you can help , thanks in advance.
findinghomer said:
hi everyone.. I recently upgraded my phone to the LG G2, and in doing so I have kept my Droid DNA for the purpose of getting into rooting, and customizing. I have always been fascinated with smart phones , and operating systems, and would like to get to know how to dig into them. I know stock systems very well, and optimize every phone I get up to the stock allowance. Now I want to lift my limitations, and this is the perfect phone to do it with. so if yu could please kindly give me some advice on where to start,. I have been lurking these forums for quite some time, and I find it overwhelming, since I don't know a good starting point. I will continue reading/learning before I tap into this OS, but I just need to know basics, then I will begin to understand the framework..if I have this in the wrong section, im sorry, ill find it if you move it. if you can help , thanks in advance.
Click to expand...
Click to collapse
I suppose unlocking and S-off should be your starting point, if I understand the question correctly.
If your DNA is on the latest firmware 3.x.x then Rumrunner will get this done for you.
Then install a custom Recovery, ClockWorkMod (CWM) or TeamWinRecoveryProject (TWRP).
Back up your OE Rom by making Nandroid (done in recovery).
After that you can flash whatever ROM you choose.
I have 2 DNAs, on one I have ViperDNA 2.5.0 and on the other CyanogenMod 11.0 nightly.
Above all, have fun :good:
Thanks, Yes... that does answer my question. And I am on firmware 3. Android 4.2.2. Is there any specific advice you can give me to avoid any fatal errors?
btw. what lead me to create a this thread, was that I heard I need rumrunner , so I went to the website, DL the file. after extracting the file for my device, and executing soju.exe, when it ask if im aware of the implications or whatever "type yes or no" when I type yes, It just keeps asking me over and over lol. so I got no where. so I did some digging and found tons of different threads ,, some of which say use this file.... or that tool kit, or this program.... or that method, some that seem to no longer works etc. so it just confused me on what I need to do with my particular phone. 4.2.2 firmware 3 sense 5.0
findinghomer said:
btw. what lead me to create a this thread, was that I heard I need rumrunner , so I went to the website, DL the file. after extracting the file for my device, and executing soju.exe, when it ask if im aware of the implications or whatever "type yes or no" when I type yes, It just keeps asking me over and over lol. so I got no where. so I did some digging and found tons of different threads ,, some of which say use this file.... or that tool kit, or this program.... or that method, some that seem to no longer works etc. so it just confused me on what I need to do with my particular phone. 4.2.2 firmware 3 sense 5.0
Click to expand...
Click to collapse
This http://forum.xda-developers.com/showthread.php?t=2559232 should be all you need for unlock and S-off.
This http://forum.xda-developers.com/showthread.php?t=1994662 is the Recovery I use, TWRP.
When using Rumrunner you must follow the instructions EXACTLY.
Make sure your drivers are working properly.
Make sure your device is recognized by ADB and Fastboot.
Rumrunner assumes you have studied, and are familiar with ADB and Fastboot commands.
If not read this http://forum.xda-developers.com/showthread.php?t=879701
Make sure your firewall and any anti virus are disabled.
Enjoy :fingers-crossed:
Make sure you use a capital y when typing yes, everything needs to be exact.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Jaggar345 said:
Make sure you use a capital y when typing yes, everything needs to be exact.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yip that was it. figured out adb/fastboot commands out too. So I am finally getting a start. I really appreciate it guys. thanks
.'
'Eg
Wanting to do the same thing
So I am also trying to do this same thing, on same firmware and sense versions, but when rumrunner gets to the very first step were it reboots into the bootloader, it never gets past the waiting for fastboot stage. My phone just sits at the bootloader menu and the countdown runs out. I am not sure what I am doing wrong. Any help is appreciated.
Mr.Schneider said:
So I am also trying to do this same thing, on same firmware and sense versions, but when rumrunner gets to the very first step were it reboots into the bootloader, it never gets past the waiting for fastboot stage. My phone just sits at the bootloader menu and the countdown runs out. I am not sure what I am doing wrong. Any help is appreciated.
Click to expand...
Click to collapse
Sounds like either your ADB or Fastboot are not working properly.
Fix them and you should be fine.
Mr.Schneider said:
So I am also trying to do this same thing, on same firmware and sense versions, but when rumrunner gets to the very first step were it reboots into the bootloader, it never gets past the waiting for fastboot stage. My phone just sits at the bootloader menu and the countdown runs out. I am not sure what I am doing wrong. Any help is appreciated.
Click to expand...
Click to collapse
What os are you running? Like sdamark said it sounds like your drivers aren't installed properly.
Sent from my Droid DNA using Tapatalk
I have Windows 8.1 on the computer I'm trying this on. I just read that might cause some problems. I'm going to try it on my Windows 7 laptop in a little bit and see if that helps
Sent from my HTC DROID DNA
Mr.Schneider said:
I have Windows 8.1 on the computer I'm trying this on. I just read that might cause some problems. I'm going to try it on my Windows 7 laptop in a little bit and see if that helps
Sent from my HTC DROID DNA
Click to expand...
Click to collapse
Windows 8.1 does not get along with the dna. It's best to use Windows 7
Sent from my HTC Droid DNA using XDA Premium 4 mobile app
Jaggar345 said:
Windows 8.1 does not get along with the dna. It's best to use Windows 7
Sent from my HTC Droid DNA using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That's not entirely true. You have to disable driver signature enforcement in Windows 8.x then install the ADB driver. Microsoft doesn't want anyone unknowingly installing drivers by accident. They make it so that you know what you are doing and doing it on purpose.
http://youtu.be/NM1MN8QZhnk?t=29s
Got it!
I did all the same things on my Windows 7 laptop and it worked perfectly the first time. It really was Windows 8.1 that was the problem. I'll be sure to follow that link and make sure all the rest of my drivers work in the future. Thanks.