Hero had a hardware fault w/ the SD slot(good thing too! I dropped it last week and had a bit of rub on the top left that was bothering the hell out of me)
Was going to go get it replaced tonight, but for some damn reason the RUU won't work.
I have the latest RUU(1.56?)
Tried with phone w/ and without USB debugging
Went into fastboot mode(which made W7 install drivers for Android 1.0?) yet the RUU still won't recognize the phone.
I'm not computer illiterate, I'm just having problems with this damn RUU.
Halp?
What's the error you're getting?
The RUU basically says like
"Finding your Android Device" for about 30 seconds then says it cannot find it.
error 170...
ahh we meet again
i've helped a few people through this but i don't want to spoil the fun..
read this
all the way through it has the steps needed to get you up and going.
what os are you running?
just read windows 7..
try right clicking and "run as administrator"
thedudejdog said:
error 170...
ahh we meet again
i've helped a few people through this but i don't want to spoil the fun..
read this
all the way through it has the steps needed to get you up and going.
what os are you running?
just read windows 7..
try right clicking and "run as administrator"
Click to expand...
Click to collapse
I've read this before, I got it from geekfor.me
My windows 7 has the real administrator account enabled, running as administrator won't do anything.
intx said:
I've read this before, I got it from geekfor.me
My windows 7 has the real administrator account enabled, running as administrator won't do anything.
Click to expand...
Click to collapse
ok.
basically my next question is do you want my help or not?
i know how to make it work for you, at least three other people have gotten it to run by following my directions.
thedudejdog said:
ok.
basically my next question is do you want my help or not?
i know how to make it work for you, at least three other people have gotten it to run by following my directions.
Click to expand...
Click to collapse
Why wouldn't I want help?
ok try this.
type "adb devices"
if that sees your phone type reboot into fastboot then type "fastboot devices"
if that sees your phone then run the ruu
adb devices sees it.
boot into fastboot, fastboot devices sees it.
run the RUU, error 170 still >_<
intx said:
adb devices sees it.
boot into fastboot, fastboot devices sees it.
run the RUU, error 170 still >_<
Click to expand...
Click to collapse
have you tried this?
realmrealm said:
For some of the people running into problems with Windows 7 you may want to try:
1. Right-click on the executable file "ARUWizard.exe" and then go to "properties"
2. I believe there is a tab called "Compatibility" or something, click on it.
3. there should be a place for you to click next to a "run this program in compatibility mode" put a check there
4. below that there should be a drop down box, try choosing "Windows XP SP3" (or something similar to that)
5. near the bottom should be a place to check "run as administrator" check that.
6. click "ok" and then try running the program again.
I'm in front of a windows xp computer right now, not windows 7, so excuse me if i don't remember the options correctly, but I should be pretty close.
I also don't even know if this will work, but it's definitely worth a shot.
-AndyS-
Click to expand...
Click to collapse
or this?
10 char...
flipzmode said:
Possible resolutions would be:
1) Putting it in to fast boot and trying it again. Check your error log if it fails and seeing if it identified your phone this time.
2) Open a command prompt and "cd" to the folder where your \sdk\tools\ folder and type in "adb devices" and hit enter and see if it sees your phone. If not then that's your problem. If it DOES see your phone then enter the following command
3) adb shell reboot oem-78 -- that will reboot your phone in to RUU-ready fastboot. If you had the RUU still open then close it. Then open it and try running again.
Click to expand...
Click to collapse
or this?
crunchybutternut said:
Just had a thought.. after updating my HTC Sync software the adb included with my RUU might be out of date. I copied adb.exe, AdbWinApi.dll and fastboot.exe from C:\AndroidSDK\Tools and overwrote the files in the RUU folder. Then I ran it without a hitch.. weird, eh?
Click to expand...
Click to collapse
Tried the first two things, neither helped
I figured out part of the problem though. I had to dig up some 64 bit drivers.
I got the RUU to recognize my phone and it sends it to the bootloader and gets stuck on Waiting for bootloader then errors 170 out.
I'll try copying the files over now.
Replacing those 3 files did the trick!
Thanks
intx said:
Replacing those 3 files did the trick!
Thanks
Click to expand...
Click to collapse
no problem, when i did it i tried all of those steps at once, so i wasn't sure which one fixed it for me. so now (in theory) it should work for you on that machine every time.
wont run and get "ARUGlobal.dll can not be found" even tho im looking right at it....
Related
I tried unlocking the bootloader with fastboot and every time i try i get "waiting for device" i tried in on two different computers. Please if anyone can help i'll really appreciate that.
Dennis Rambarran said:
I tried unlocking the bootloader with fastboot and every time i try i get "waiting for device" i tried in on two different computers. Please if anyone can help i'll really appreciate that.
Click to expand...
Click to collapse
I keep getting that on my desktop (W7U 64-bit), but not on my laptop (W7HP 32-bit). Tried installing the Android SDK and USB drivers (successfully) yet?
Be sure and install java.
This should fix your problem. (I have windows 7 home premium 64 bit, was getting the same issues).
http://javadl.sun.com/webapps/download/AutoDL?BundleId=36668
*facepalm* My god, it's already turning into the same mess as on the Dream Dev forum... all the "please help" questions...
But, this forum is new, so I guess it's easy to get confused. Just so you know, though, this belongs in general, or in Q&A when they get one of those.
About your problem... plug your phone in and see what happens. Do not mount it. Does windows prompt you to install a driver? If not, open a terminal (yeah yeah, command prompt, whatever) and type adb devices. You may need to install the driver.
I installed the SDK and drivers but I get the same problem, BTW - I'm running windows XP SP2. I'm at this for 2 hrs now this is frustrating...
http://forum.xda-developers.com/showthread.php?t=613217
charkosh said:
Be sure and install java.
This should fix your problem. (I have windows 7 home premium 64 bit, was getting the same issues).
http://javadl.sun.com/webapps/download/AutoDL?BundleId=36668
Click to expand...
Click to collapse
Java is *not* needed for this.
Once you have your drivers installed, as linked by Mikey, ensure that you have usbdebugging enabled.
"fastboot devices" will let you know if you have your n1 ready to go or not. Sorry, fastboot-windows devices.
typed fastboot-windows devices and nothing happens
in cmd
fastboot devices (shows my serial) but when I try to fastboot flash recovery recovery-clockwork-herring.img it keeps saying error: device not found and I cant for the life of me figure out what's wrong. I have tweeted a few people with no luck...
Try this
shug24 said:
in cmd
fastboot devices (shows my serial) but when I try to fastboot flash recovery recovery-clockwork-herring.img it keeps saying error: device not found and I cant for the life of me figure out what's wrong. I have tweeted a few people with no luck...
Click to expand...
Click to collapse
Try resetting your phone and your computer then try again
like a reboot? that hasn't helped yet...
yeah exactly- hmmm try re-installing the drivers
where can I find the samsung drivers and I am trying to do that again now.. but I am not sure what drivers you are talking about specifically.
shug24 said:
where can I find the samsung drivers and I am trying to do that again now.. but I am not sure what drivers you are talking about specifically.
Click to expand...
Click to collapse
you have to get the drivers through android sdk
(with phone usb connected)
device manager
Android Device
right click
update drivers
click browse my computer then next and then click install
if it doesnt give you that option let me know
okay I am having problems there. First, it doesn't recognize an android device, it says unknown device and it won't take any drivers I have followed the pdanet steps, and I have tried the galaxy s drivers with no luck...
okay there is your problem now we are getting somewhere,
do you have android sdk
if yes do you know how to install packages
I have tried this on two 64bit machines and one x86 the one I am on now.. and can't get it to work. I feel like a total newb but this is not a new thing to me ( rooting/unlocking etc) I have had a g1 since the release, then a nexus one since release and just got the nexus s yesterday and have struggled with this one..
what do you mean by install packages, and I appreciate your help
okay no problem it took me a bit to figure it out too.....there arent samsung drivers for this phone they come straight from google through android sdk. im assuming you have it and im going to assume its in this directory if you did eveything right with your n1
c:/androidsdk
in the directory there is a file called SDK setup.exe open it
once it opens do yourself a favor and click cancel dont ask why just do it
now thats out of the way there is 5 options on the left pane of the android sdk window click settings.
then at the bottom of that window is a box under misc. by force http..make sure its checked
then on the left pane goto then available packages
click them all to save yourself trouble and then on the bottom right install packages
let me know when thats done
doing it now - not sure if this helps or not but I had done this last night on a different pc - unfortunately that is at home and I am on my work laptop right now.
and... done.
okay now go back into the device manager and right click on unknown device
update/re-install/install whichever it says then when it asks search or browse
BROWSE
c:/androidsdk/googleusb driver
and watch the magic happen
okay a few things: first it says e: now for the phone under portable devices second, there is no google usb drivers, so I tried it just under the AndroidSDK folder and all the following and it said:
The best driver software for your device is already installed. WPD Filesystem Volume Driver
thoughts?
go back to the sdk setup.exe expand the boxes under available packages and read me what you see
is this where you are asking me to display from? http://www.twitpic.com/3gwnus
OR here: http://www.twitpic.com/3gwo9i
let me save you the trouble
unzip cut and paste to your androidsdk folder
http://www.multiupload.com/Y3T61793BP
yes and paste the file i sent you into that folder
now it still says the best driver is already installed...
uninstall your phone
I am trying to root my D802 device according to the following thread.
http://forum.xda-developers.com/showthread.php?t=2448887
I can find my device with adb devices. good. Then leaving the cmd window open, I double click root.bat: a new window pops up asking me to press any key. Doing so immediately closes the root.bat window and of course doesn't root the device. Does anyone has any clue what's wrong?
I have D802. Windows xp. Installed usb drivers. Enabled debugging mode.
I have tried to run the bat as administrator as well as limited privilege user. No difference.
PLEASE HELP!!!!
Same Problem
I am having same exact issue..windows 7 would love some help on this! Just need root for adblock and I am set this device rocks! +rid bloatware but thats a given.
eadred said:
I am trying to root my D802 device according to the following thread.
http://forum.xda-developers.com/showthread.php?t=2448887
I can find my device with adb devices. good. Then leaving the cmd window open, I double click root.bat: a new window pops up asking me to press any key. Doing so immediately closes the root.bat window and of course doesn't root the device. Does anyone has any clue what's wrong?
I have D802. Windows xp. Installed usb drivers. Enabled debugging mode.
I have tried to run the bat as administrator as well as limited privilege user. No difference.
PLEASE HELP!!!!
Click to expand...
Click to collapse
Well, glad to not be the only one. Let's find what we have in common, maybe we'll find where it comes from. Do you also have windows xp? Have you by any chance windowblinds installed? Have you run as administrator? Anything particular otherwise?
Same Problem
I have Windows 7 and no windows blinds...I have tried different ports and also ran as administrator. I have successfully rooted OG Droid, Droid Bionic , and Galaxy Nexus. I think I got spoiled by how easy the Nexus was to root and change roms. Love the G2 just need to get the root to stick. Every time I hit a key to continue from root bat the command window closes. I was able to read quickly a line that says unknown error has occured. Not sure why this is happening. I have tried two different drivers LG VZW_United_WHQL_v2.11.1.exe and LGUnitedMobileDriver.exe with no luck.
Using the application usbdeview, I can't see the lg driver even though I have installed it. Is it the same for you?
Actually a lg driver is indeed listed
LGE Android Phone AndroidNet Sooner Single ADB Interface Vendor Specific No Yes No No 02231cddcf4eb680 19.10.2013 19:25:05 19.10.2013 23:37:42 1004 631f 2.32 ff 42 01 andnetadb ADB Interface DriverNet lgandnetadb.sys USB Google, Inc AndroidNet Sooner Single ADB Interface 3.10.0.0 USB\Vid_1004&Pid_631f\02231cddcf4eb680
Same Problem
The drivers say installed correctly......in the command window after you check adb devices it comes back with model number and more numbers. When it looks for the device and carrier I get /f was unexpected at the time. Thinking about uninstalling all the drivers and trying for the umteenth time. You running any virus protection wonder if that has any effect?
maclv said:
The drivers say installed correctly......in the command window after you check adb devices it comes back with model number and more numbers. When it looks for the device and carrier I get /f was unexpected at the time. Thinking about uninstalling all the drivers and trying for the umteenth time. You running any virus protection wonder if that has any effect?
Click to expand...
Click to collapse
Not sure what you mean. On my side, if I write adb devices in a command prompt, I only get one line of numbers and beside it: 'device'. And that's it. Do you get additonal infos?
When I run the root.bat, I can hardly read the text before it closes, but from what I saw and completing with the text that you can get by editing the root.bat, I tend to think that the following is written before it closes:
Looking for device...
.\adb.exe wait-for-device
Determining carrier...
On a chat before, someone suggested me to right click the root.bat and clic edit to view the content of the bat. And then manualy reproduce in adb by pushing the necessary files and such... But I haven't yet given hope that it works with the bat. But maybe you feel like giving it a shot.
I have ESET as antivirus
Same Problem
No luck manual editing the root bat. When I type adb device it list VS980_4G - and a set of numbers
I was wondering if I should try another root method. I have seen on an italian forum someone who rooted with a chinese method. I have no time right now, but I might test it in a few days.
http://translate.google.com/transla...&hl=en&langpair=auto|en&tbb=1&ie=windows-1252
Btw in which country are you? I bought my mobile phone from digitec in switzerland.
I bought mine from Verizon in the US. Deleted all previous drivers....trying fresh install see if that helps
Sent from my VS980 4G using Tapatalk
maclv said:
I bought mine from Verizon in the US. Deleted all previous drivers....trying fresh install see if that helps
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
please let me know if you get through. I'm stuck and willing to return the device. it's killing me
Tried on another computer. Was done within second. It will remain a mystery why it didn't work on mine. But hey, done is done! :good:
I will try on another cpu hmmmm
Sent from my VS980 4G using Tapatalk
hit windows key+r,enter cmd then hit run.
then navigate via cd c:\folder\folderthatcontainsroot.bat
then open root.bat by typing it in cmd.
that should stop tje autoclosing of cmd when opening via windows Explorer.
Sent from my LG-D802
Thank you for the tip. I was able to get root switching to a different cpu. .but glad I will be able to use my main cpu in the future. Thank you both for the help.
Sent from my VS980 4G using Tapatalk
Hey guys ive been pretty stoked to root and rom my g2 now that im bored of LG's UI haha i have been trying to use the IOroot method but something about the drivers is giving me such a hard time! i installed them but every time i open a command window and type in "adb devices" nothing is coming up so obviously its not being able to read my device which isnt alowing me to root my phone any help would be greatly appriciated! thanks in advance
I was having trouble, finally went to LG site to download drivers
Sent from my VS980 4G using XDA Premium 4 mobile app
adb is a special android thing. You need to install it to just use it anywhere. Do this:
1. Create a folder on your desktop (you can call it root or whatever you want).
2. Extract IORoot into folder created in step one.
3. SHIFT RIGHT CLICK and do "open command window here" (This is the most important).
4. type
Code:
adb devices
5. if you devices shows run the root.bat file to root your device.
Look at this for a little more help.
http://forum.xda-developers.com/showthread.php?t=2515978
djraimondi said:
adb is a special android thing. You need to install it to just use it anywhere. Do this:
1. Create a folder on your desktop (you can call it root or whatever you want).
2. Extract IORoot into folder created in step one.
3. SHIFT RIGHT CLICK and do "open command window here" (This is the most important).
4. type
Code:
adb devices
5. if you devices shows run the root.bat file to root your device.
Look at this for a little more help.
http://forum.xda-developers.com/showthread.php?t=2515978
Click to expand...
Click to collapse
IVe done this so many times haha... the problem is when i type that into the command window nothing comes up under listed devices and ive downloaded and installed the drivers from several different locations including the LG website... could it be the ethernet thing that im missing? because thats the only thing i dont believe ive done cause this is a hastle xD ive had no problems rooting in the past
Cyko.Tech67 said:
IVe done this so many times haha... the problem is when i type that into the command window nothing comes up under listed devices and ive downloaded and installed the drivers from several different locations including the LG website... could it be the ethernet thing that im missing? because thats the only thing i dont believe ive done cause this is a hastle xD ive had no problems rooting in the past
Click to expand...
Click to collapse
Do you have the phone listed correctly for what mode to be in when you plug in the USB cord???
hd-renegade said:
Do you have the phone listed correctly for what mode to be in when you plug in the USB cord???
Click to expand...
Click to collapse
i have tried both with Charge only mode and MTP
Cyko.Tech67 said:
i have tried both with Charge only mode and MTP
Click to expand...
Click to collapse
This is just a thought, but maybe, power the phone off, power the PC off. Turn them both back on, re-read the instructions on how to root the phone. It sort of sounds like you could be missing just a little thing on the instructions. You may also try a different USB port on your PC too. I rooted mine back on iRoot 6 so I would have to think that iRoot 10 should be better then what I used.
hd-renegade said:
This is just a thought, but maybe, power the phone off, power the PC off. Turn them both back on, re-read the instructions on how to root the phone. It sort of sounds like you could be missing just a little thing on the instructions. You may also try a different USB port on your PC too. I rooted mine back on iRoot 6 so I would have to think that iRoot 10 should be better then what I used.
Click to expand...
Click to collapse
I just dont think im installing the drivers right because ive tried everyone and their mothers usb ports and ive tired it on 4-5 computers there has to be something im missing with the drivers because the process just wont start Daemon will succsesfully start running than nothing...
Cyko.Tech67 said:
I just dont think im installing the drivers right because ive tried everyone and their mothers usb ports and ive tired it on 4-5 computers there has to be something im missing with the drivers because the process just wont start Daemon will succsesfully start running than nothing...
Click to expand...
Click to collapse
It has been a while sense I rooted mine, but I think the fix for me was getting the drivers from the LG Site and using the LG Flash tool.
hd-renegade said:
It has been a while sense I rooted mine, but I think the fix for me was getting the drivers from the LG Site and using the LG Flash tool.
Click to expand...
Click to collapse
whats the flash tool for?
I think I ended up flashing back to LG stock. Sorry it has been a while sense I played with that stuff.
Sent from my VS980 4G using Tapatalk HD
I had the same issue. I installed these lg drivers, not sure if they had anything to do with it because it still didn't work. What finally worked was when I turned off debug and may have been in mtp connection. Obviously after you have to put back in debug and ethernet connection to follow the ioroot method.
dp917 said:
I had the same issue. I installed these lg drivers, not sure if they had anything to do with it because it still didn't work. What finally worked was when I turned off debug and may have been in mtp connection. Obviously after you have to put back in debug and ethernet connection to follow the ioroot method.
Click to expand...
Click to collapse
alright one more question and thanks for the fast replies guys! i appriciate it but im not to nifty with computer tech as i am Smartphone xD laptops still have an ethernet mode correct? and if so where do i go to enable it?
Cyko.Tech67 said:
alright one more question and thanks for the fast replies guys! i appriciate it but im not to nifty with computer tech as i am Smartphone xD laptops still have an ethernet mode correct? and if so where do i go to enable it?
Click to expand...
Click to collapse
Ethernet mode is in enabled in your phone. Settings > scroll to bottom "pc connection."
dp917 said:
Ethernet mode is in enabled in your phone. Settings > scroll to bottom "pc connection."
Click to expand...
Click to collapse
awesome thanks so much guys a thanks to both of you ill try it when i get home and let ya know how it went
Cyko.Tech67 said:
awesome thanks so much guys a thanks to both of you ill try it when i get home and let ya know how it went
Click to expand...
Click to collapse
Let the folks here know how you make out.
hd-renegade said:
Let the folks here know how you make out.
Click to expand...
Click to collapse
unfortunatly with ethernet on i am still getting the same results... its just not recognizing my device? at least now in the notification bar i get the notification that USB debugging is on so i guess im making progress? uggh this is getting pretty annoying any thoughts guys?
Run it directly from local drive root. IE C:/ Windows 7? Control alt delete. End the stale adb process, you should see two, one not performing sitting around 2000 kb ram and the other using ram. End that and it should force adb to kick in. I had to do this on win 7 multiple times with dif phones. It's like it locks up when finding the com port or whatever the hell it's doing. I take no blame if you screw up your device this way. I have resorted to a virtual xp for all my phone needs as not everything works in Linux.
Here's how rooted my phone with IORoot:
Unzipped IORoot to root of my hard drive
Plugged in phone with usb (make sure debug mode is enabled). When prompted to choose connection, choose modem. You should see debug icon appear in status bar. If not, choose Ethernet.
Opened IORoot folder. Hold down shift and right click an empty area and choose 'open command window'
Type adb devices. If device shows up, proceed. With normal root procedure.
Steamer86 said:
Run it directly from local drive root. IE C:/ Windows 7? Control alt delete. End the stale adb process, you should see two, one not performing sitting around 2000 kb ram and the other using ram. End that and it should force adb to kick in. I had to do this on win 7 multiple times with dif phones. It's like it locks up when finding the com port or whatever the hell it's doing. I take no blame if you screw up your device this way. I have resorted to a virtual xp for all my phone needs as not everything works in Linux.
Click to expand...
Click to collapse
simon_lefisch said:
Here's how rooted my phone with IORoot:
Unzipped IORoot to root of my hard drive
Plugged in phone with usb (make sure debug mode is enabled). When prompted to choose connection, choose modem. You should see debug icon appear in status bar. If not, choose Ethernet.
Opened IORoot folder. Hold down shift and right click an empty area and choose 'open command window'
Type adb devices. If device shows up, proceed. With normal root procedure.
Click to expand...
Click to collapse
Not sure if it matters but I am running 64 bit Windows 8
- In the instructions didn't you have to change a setting for the Com Port to get it to see the phone??
- Did you ever get the prompt on your phone to accept the Connection. I can not remember what it was, but it only comes up once, and I am not referring to the USB connection IE Ethernet??
- Are you sure you have Developer Options turned on?? The step where you keep tapping on the Developer thing and then the phone finally gives you the Developer Options??
When I try to flash something via ADB on my computer it doesn't work because I get an error message that multiple terminals are open. I'm not good with command line stuff on the computer and usually figure out a way around it so I can flash what I need to, but the next time I need to flash something I'm in the same boat again with the same error message. Is there a way to close everything that is supposedly running so I don't get that error?
jhs39 said:
When I try to flash something via ADB on my computer it doesn't work because I get an error message that multiple terminals are open. I'm not good with command line stuff on the computer and usually figure out a way around it so I can flash what I need to, but the next time I need to flash something I'm in the same boat again with the same error message. Is there a way to close everything that is supposedly running so I don't get that error?
Click to expand...
Click to collapse
Hello,
What's the output of:
adb devices
Also, can you paste the exact error displayed on the command prompt?
You could try:
adb kill-server
Which kill the adb.exe process
Then:
adb start-server
Cheers...
Updated Android platform tools and when I flashed the latest bootloader didn't get that error again. The update must have cleared up the problem. Hopefully it won't happen again. Is there something you are supposed to do after flashing to ensure that the terminal doesn't rename open in the background in windows?
jhs39 said:
Updated Android platform tools and when I flashed the latest bootloader didn't get that error again. The update must have cleared up the problem. Hopefully it won't happen again. Is there something you are supposed to do after flashing to ensure that the terminal doesn't rename open in the background in windows?
Click to expand...
Click to collapse
Hello,
By "rename" you meant "remain" ?
I don't think so... But you can right click on your windows taskbar and open task manager.
Look at processes and see if ADB.exe is still running. You can also tic:
"Show processes for all users" and see here...
Cheers...